Avaya 3.7 - Manual (Page 259)

Using Monitor
Issue 4 May 2005 259
Packets
Logged In Total number of inbound packets that should
have been logged. This number includes
packets that matched filtering rules declared
using either the ‘log option’ or the ‘log action’.
Packets
Logged Out Total number of outbound packets that should
have been logged. This number includes
packets that matched filtering rules declared
using either the ‘log option’ or the ‘log action’.
Skip Log In Number of inbound packets that should have
been logged, but the log buffer was full. Log
records are stored in a fixed size non-circular
buffer. When the buffer is full, no new log
records are written until the buffer is drained
via either the security gateway console or the
VPNmanager.
Skip Log Out Number of outbound packets that should have
been logged, but the log buffer was full. Log
records are stored in a fixed size non-circular
buffer. When the buffer is full, no new log
records are written until the buffer is drained
via either the security gateway console or the
VPNmanager.
Return In Number of inbound packets that matched a
rule requiring that a TCP-Reset or ICMP
packet be sent in response.
Return Out Number of outbound packets that matched a
rule requiring that a TCP-Reset or ICMP
packet be sent in response.
Account In Number of inbound packets that matched a
filtering rule with a declared action of ‘count’.
Account Out Number of outbound packets that matched a
filtering rule with a declared action of ‘count’.
Bad Frag Alloc
In Number of failed attempts to allocate a
Fragment table entry for inbound packets. This
occurs when a filter rule is declared using the
‘keep frag’ option. A packets matching this rule
cause a Fragment table entry to be allocated.
If the table is full, the allocation fails.
Table 23: FilterStats Parameters (continued)
Parameter Description
3 of 7