NETGEAR GS728TS Admin Manual page 163

GS728TS, GS728TPS, GS752TS, and GS752TPS Gigabit Smart Switches
Field
IpInUnknownProtos
IpInDiscards
IpInDelivers
IpOutRequests
IpOutDiscards
IpOutNoRoutes
IpReasmTimeout
IpReasmReqds
IpReasmOKs
IpReasmFails
IpFragOKs
IpFragFails
IpFragCreates
IpRoutingDiscards
Description
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.
163