Enterasys SECURESTACK C3 Configuration Manual page 671

Table 22-5 show ipv6 traffic Output Details (Continued)
Output 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 Due
To Truncated Data
Received Datagrams Discarded Other
Received Datagrams Reassembly
Required
Datagrams Successfully Reassembled
Datagrams Failed To Reassemble
Datagrams Forwarded
What It Displays...
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, etc.
Number of input datagrams that could not be forwarded because
their size exceeded the link MTU of outgoing interface.
Number of input datagrams discarded because no route could be
found to transmit them to their destination.
Number of locally-addressed datagrams received successfully but
discarded because of an unknown or unsupported protocol. This
counter increments at the interface to which these datagrams
were addressed, which might not be necessarily the input
interface for some of the datagrams.
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 (for example,
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.
Number of input datagrams discarded because datagram frame
didn't carry enough data.
Number of input IPv6 datagrams for which no problems were
encountered to prevent their continue processing, but which were
discarded (e.g., for lack of buffer space). Note that this counter
does not include datagrams discarded while awaiting re-assembly.
Number of IPv6 fragments received which needed to be
reassembled at this interface. Note that this counter increments at
the interface to which these fragments were addressed, which
might not be necessarily the input interface for some of the
fragments.
Number of IPv6 datagrams successfully reassembled. Note that
this counter increments at the interface to which these datagrams
were addressed, which might not be necessarily the input
interface for some of the fragments.
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 by combining them as they are
received. This counter increments at the interface to which these
fragments were addressed, which might not be necessarily the
input interface for some of the fragments.
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 increments.
show ipv6 traffic
SecureStack C3 Configuration Guide 22-31