Neighbor Table - NETGEAR XS728T ProSAFE Software Administration Manual

Field
Received Datagrams With Unknown
Protocol
Received Datagrams Discarded
Due To Invalid Address
Received Datagrams Discarded
Due To Truncated Data
Received Datagrams Discarded
Other
Received Datagrams Reassembly
Required
Datagrams Successfully
Reassembled
Datagrams Failed To Reassemble
Datagrams Forwarded

Neighbor Table

To display the IPv6 Neighbor Table page:

1. Click Routing> IPv6 > Advanced > Neighbor Table.
2. Use the Search field to search for IPv6 routes by IPv6 address or interface.
XS728T ProSAFE 28-Port 10-Gigabit L2+ Smart Switch
Description
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 necessarily 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 (e.g., ::0) and
unsupported addresses(e.g., addresses with unallocated prefixes).For
entities which 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 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 number of IPv6 fragments received which needed to be reassembled
at this interface. Note that this counter is incremented at the interface to
which these fragments were addressed which might not be necessarily
the input interface for some of the fragments.
The number of IPv6 datagrams successfully reassembled. Note that 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, etc.). Note that 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
necessarily the input interface for some of the fragments.
The number of output datagrams which this entity received and forwarded
to their final destinations. In entities which do not act as IPv6 routers, this
counter will include only those packets which were Source-Routed via this
entity, and the Source-Route processing was successful.Note that for a
successfully forwarded datagram the counter of the outgoing interface is
incremented.
Routing
98