Edge-Core Direk Tronik 24/48-Port Management Manual page 549

Field
hop count exceeded
unknown protocol
not a router
fragments
total reassembled
reassembly timeouts
reassembly failures
Ipv6 sent
sent generated
forwarded
fragmented
generated fragments
fragmented failed
encapsulation failed
no route
too big
Table 60-4 show ipv6 traffic - display description
Description
Number of packets discarded because its time-to-live (TTL) field was decremented
to zero.
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 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 times the reassembly of a packet timed out.
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 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.
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 number of IPv6 datagrams that have been successfully fragmented at this
output interface.
The number of output datagram fragments that have been generated as a result
of fragmentation at this output interface.
The number of IPv6 datagrams that have been discarded because they needed to
be fragmented at this output interface but could not be.
Failure that can result from an unresolved address or failure to queue a packet.
The number of input datagrams discarded because no route could be found to
transmit them to their destination.
The number of input datagrams that could not be forwarded because their size
exceeded the link MTU of the outgoing interface.
60
show ipv6 traffic
60-17