Re: Firewall cache error logs

["Sal Stangarone Jr." <sals@xxxxxxxxxxxxxxxxxxxx>]

Yes we have a very similar problem.  We've increased the size of the K drive
to accomodate our over logging firewall.  I think I can find a link to the
instructions if need be, just contact me.  We're working with IBM to try to
resolve this.

Sal Stangarone Jr.
michaels, ross & cole, ltd.

Phone: 630.916.0662
Fax: 630.916.0663

Web: www.mrc-productivity.com
----- Original Message -----
From: <jcrowley@ifasys.com>
To: <MIDRANGE-L@midrange.com>
Sent: Thursday, February 03, 2000 2:57 PM
Subject: Firewall cache error logs


>
>
> Any AS/400 Firewall experts out there?
>
> We have had a problem with firewall cache error logs filling up our
firewall K:
> drive -- this causes firewall logging to end, which shuts down the
firewall and
> thus all our incoming/outgoing email (the lack of external email is
usually our
> first indication of the problem).
>
> We found these error logs by using SBMNWSCMD to search through all the
> subdirectories on the firewall k: drive after a "Firewall logging has
ended"
> message to the Sysop hinted that the k: drive might be full. You
apparently
> can't get to these logs any other way, nor are they documented ANYWHERE
that
> I've found.
>
> If you want to see if you've got any of these error logs, use SBMNWSCMD
and
> enter the command
>    'dir k:\firewall\cache\proxy'
> -- look for files named htterr.xxxxxxxxx where the xx's represent the date
the
> file was generated.
>
> After extensive study, we think that the contents of the firewall cache
are
> being dumped to these error logs each night as our scheduled backups
begin. We
> don't shut down subsystems at this time because occasionally we have
people
> online from home at night. So, we're not sure what is causing this to
happen.
> There is no message in the history log to indicate a problem. Curiously,
we just
> installed a PTF to correct a problem with the performance monitor being
shut
> down when backups begin, but at least we've had error messages that
pointed to
> the PM problem.
>
> We installed V4R4 in December and installed all V4R4 firewall-related PTFs
soon
> after. When we discovered these logs for the first time in January, there
were
> daily versions existing back to mid-October. We have never changed the
firewall
> cache settings from the defaults, so we don't know what happened in
October. A
> search of current PTFs hasn't turned up anything so far.
>
> Our temporary solution is to delete these logs and turn off the firewall
cache
> (which apparently means setting the cache size to 0 -- although the
firewall
> documentation says that caching is available "if you want it", the default
is
> that caching is turned on, and there's no documentation on how to turn it
off).
>
> Has anyone else encountered this situation?
>
> Janet Elam Crowley
> IFA Systems
>
>
>
>
>
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---
>


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---