Extreme Networks ExtremeWare XOS Guide Manual page 387

Table 56: Predefined CLEAR-Flow Counters (Continued)
Counter Name
sys_IpInDiscards
sys_IpInDelivers
sys_IpOutRequests
sys_IpOutDiscards
sys_IpOutNoRoutes
sys_IpReasmTimeout
sys_IpReasmReqds
sys_IpReasmOKs
sys_IpReasmFails
sys_IpFragOKs
sys_IpFragFails
sys_IpFragCreates
sys_IcmpInMsgs
sys_IcmpInErrors
sys_IcmpInDestUnreachs
sys_IcmpInTimeExcds
sys_IcmpInParmProbs
sys_IcmpInSrcQuenchs
sys_IcmpInRedirects
sys_IcmpInEchos
sys_IcmpInEchoReps
sys_IcmpInTimestamps
sys_IcmpInTimestampReps
sys_IcmpInAddrMasks
ExtremeWare XOS 11.3 Concepts Guide
1
Description
The number of input IP packets for which no problems were encountered to
prevent their continued processing, but which were discarded (e.g., for lack of
buffer space). Note that this counter does not include any IP packets discarded
while awaiting re-assembly.
The total number of input IP packets successfully delivered to IP user-protocols
(including ICMP).
The total number of IP packets which local IP user-protocols (including ICMP)
supplied to IP in requests for transmission. Note that this counter does not
include any IP packets counted in ipForwDatagrams.
The number of output IP packets for which no problem was encountered to
prevent their transmission to their destination, but which were discarded (e.g.,
for lack of buffer space). Note that this counter would include IP packets
counted in ipForwDatagrams if any such packets met this (discretionary) discard
criterion.
The number of IP packets discarded because no route could be found to
transmit them to their destination. Note that this counter includes any packets
counted in ipForwDatagrams which meet this `no-route' criterion.
The maximum number of seconds which received fragments are held while they
are awaiting reassembly at this entity.
The number of IP fragments received which needed to be reassembled at this
entity.
The number of IP packets successfully re-assembled.
The number of failures detected by the IP re-assembly algorithm (for whatever
reason: timed out, errors, etc.). Note that this is not necessarily a count of
discarded IP fragments since some algorithms (notably the algorithm in RFC
815) can lose track of the number of fragments by combining them as they are
received.
The number of IP packets that have been successfully fragmented at this entity.
The number of IP packets that have been discarded because they needed to be
fragmented at this entity but could not be, e.g., because their Don't Fragment
flag was set.
The number of IP packet fragments that have been generated as a result of
fragmentation at this entity.
The total number of ICMP messages which the entity received. Note that this
counter includes all those counted by icmpInErrors.
The number of ICMP messages which the entity received but determined as
having ICMP-specific errors (bad ICMP checksums, bad length, etc.).
The number of ICMP Destination Unreachable messages received.
The number of ICMP Time Exceeded messages received.
The number of ICMP Parameter Problem messages received.
The number of ICMP Source Quench messages received.
The number of ICMP Redirect messages received.
The number of ICMP Echo (request) messages received.
The number of ICMP Echo Reply messages received.
he number of ICMP Timestamp (request) messages received.
The number of ICMP Timestamp Reply messages received.
The number of ICMP Address Mask Request messages received.
Adding CLEAR-Flow Rules to ACLs
387