Ubiquiti EdgeSwitch ES-24-250W Administration Manual page 199

EdgeSwitch Administration Guide
™
Field
IpInReceives
IpInHdrErrors
IpInAddrErrors
IpForwDatagrams
IpInUnknownProtos
IpInDiscards
IpInDelivers
IpOutRequests
IpOutDiscards
IpOutNoRoutes
IpReasmTimeout
IpReasmReqds
IpReasmOKs
IpReasmFails
IpFragOKs
IpFragFails
IpFragCreates
IpRoutingDiscards
IcmpInMsgs
IcmpInErrors
IcmpInDestUnreachs
IcmpInTimeExcds
IcmpInParmProbs
IcmpInSrcQuenchs
IcmpInRedirects
IcmpInEchos
Ubiquiti Networks, Inc.
Routing IP Statistics Fields
Description
The total number of input datagrams received from interfaces, including those received in error.
The number of input datagrams discarded due to errors in their IP headers, including bad checksums,
version number mismatch, other format errors, time-to-live exceeded, errors discovered in processing
their IP options, etc.
The number of input datagrams discarded because the IP address in their IP header's destination
field was not a valid address to be received at this entity. This count includes invalid addresses (e.g.,
0.0.0.0) and addresses of unsupported Classes (e.g., Class E). For entities which are not IP Gateways
and therefore do not forward datagrams, this counter includes datagrams discarded because the
destination address was not a local address.
The number of input datagrams for which this entity was not their final IP destination, as a result of
which an attempt was made to find a route to forward them to that final destination. In entities which
do not act as IP Gateways, this counter includes only those packets which were Source-Routed via this
entity, and the Source-Route option processing was successful.
The number of locally-addressed datagrams received successfully but discarded because of an
unknown or unsupported protocol.
The number of input IP datagrams 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 datagrams discarded while awaiting re-assembly.
The total number of input datagrams successfully delivered to IP user-protocols (including ICMP).
The total number of IP datagrams which local IP user-protocols (including ICMP) supplied to IP
in requests for transmission. Note that this counter does not include any datagrams counted in
IpForwDatagrams.
The number of output IP datagrams 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 datagrams counted in IpForwDatagrams if any such packets met this
(discretionary) discard criterion.
The number of IP datagrams 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. Note that this includes any datagrams which a host cannot route because all of its
default gateways are down.
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 datagrams 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
can lose track of the number of fragments by combining them as they are received.
The number of IP datagrams that have been successfully fragmented at this entity.
The number of IP datagrams 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 datagram fragments that have been generated as a result of fragmentation at this
entity.
The number of routing entries which were chosen to be discarded even though they are valid. One
possible reason for discarding such an entry could be to free-up buffer space for other routing entries.
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.
Configuring Routing
198