NETGEAR M4300 User Manual page 294

Fully managed stackable switches
Hide thumbs Also See for M4300:
Table of Contents

Advertisement

M4300 Series and M4300-96X Fully Managed Switches User Manual
Table 105. IP Basic Statistics (continued)
Field
IpInUnknownProtos
IpInDiscards
IpInDelivers
IpOutRequests
IpOutDiscards
IpOutNoRoutes
IpReasmTimeout
IpReasmReqds
IpReasmOKs
IpReasmFails
IpFragOKs
IpFragFails
IpFragCreates
IpRoutingDiscards
IcmpInMsgs
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 that were
discarded (for lack of buffer space). 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 that local IP user protocols (including
ICMP) supplied to IP in requests for transmission. 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 that
were discarded for reasons such as lack of buffer space. 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. This counter includes any
packets counted in ipForwDatagrams that meet this no-route criterion.
This includes any datagrams that a host cannot route because all of its
default gateways are down.
The maximum number of seconds for which received fragments are
held while they are awaiting reassembly at this entity.
The number of IP fragments received that were 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, and so on). 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 were fragmented at this entity.
The number of IP datagrams that were discarded because they needed
to be fragmented at this entity but could not be, for reasons such as
their Don't Fragment flag was set.
The number of IP datagram fragments that were generated as a result
of fragmentation at this entity.
The number of routing entries that were discarded even though they
were 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 that the entity received. This
counter includes all those counted by icmpInErrors.
Routing
294

Advertisement

Table of Contents
loading

This manual is also suitable for:

M4300-96x

Table of Contents