Edge-Core ECS2100-10T Reference Manual page 677

Table 142: show ipv6 traffic - display description
Field
too big errors
no routes
address errors
unknown protocols
truncated packets
discards
delivers
reassembly request
datagrams
reassembly succeeded
reassembly failed
IPv6 sent
forwards datagrams
requests
Chapter 27
Description
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 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 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 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 total number of datagrams successfully delivered to IPv6 user-
protocols (including ICMP). 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 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 re-assembly 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.
The total number of IPv6 datagrams which local IPv6 user-protocols
(including ICMP) supplied to IPv6 in requests for transmission. Note
that this counter does not include any datagrams counted in
ipv6IfStatsOutForwDatagrams.
– 677 –
| IP Interface Commands
IPv6 Interface
(Continued)