NETGEAR GS418TPP User Manual page 233

8-Port or 16-Port Gigabit Smart Managed Pro Switch Model GS418TPP, GS510TLP, and GS510TPP
Table 61. IPv6 Statistics information (continued)
Field
Received Datagrams Discarded
Due To Header Errors
Received Datagrams Discarded
Due To MTU
Received Datagrams Discarded
Due To No Route
Received Datagrams With Unknown
Protocol
Received Datagrams Discarded
Due To Invalid Address
Received Datagrams Discarded Dut
To Truncated Data
Received Datagrams Discarded
Other
Received Datagrams Reassembly
Required
Datagrams Successfully
Reassembled
Datagrams Failed To Reassemble
Datagrams Forwarded
Configure Routing
Description
The number of input datagrams discarded due to errors in their IPv6
headers, including version number mismatch, other format errors, hop
count exceeded, errors discovered in processing their IPv6 options, and
so on.
The number of input datagrams that could not be forwarded because their
size exceeded the link MTU of outgoing interface.
The number of input datagrams discarded because no route could be
found to transmit them to their destination.
The number of locally addressed datagrams received successfully but
discarded because of an unknown or unsupported protocol. This counter
is incremented at the interface to which these datagrams were addressed,
which might not be the input interface for some of the datagrams.
The number of input datagrams discarded because the IPv6 address in
their IPv6 header's destination field was not a valid address to be received
at this entity. This count includes invalid addresses (for example, ::0) and
unsupported addresses (such as addresses with unallocated prefixes).
For entities that are not IPv6 routers 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 discarded because datagram frame didn't
carry enough data.
The number of input IPv6 datagrams for which no problems were
encountered to prevent their continued processing, but that were
discarded for reasons such as lack of buffer space. This counter does not
include any datagrams discarded while awaiting reassembly.
The number of IPv6 fragments received that needed to be reassembled at
this interface. This counter is incremented at the interface to which these
fragments were addressed, which might not be the input interface for
some of the fragments.
The number of IPv6 datagrams successfully reassembled. This counter is
incremented at the interface to which these datagrams were addressed,
which might not be necessarily the input interface for some of the
fragments.
The number of failures detected by the IPv6 reassembly algorithm (for
whatever reason: timed out, errors, and so on). This is not necessarily a
count of discarded IPv6 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. This counter is incremented at the
interface to which these fragments were addressed, which might not be
the input interface for some of the fragments.
The number of output datagrams that this entity received and forwarded to
their final destinations. In entities that do not act as IPv6 routers, this
counter includes only those packets that were source-routed through this
entity, and the source-route processing was successful. For a successfully
forwarded datagram the counter of the outgoing interface is incremented.
233 User Manual