B
ASIC
IP C
ONFIGURATION
36-31
reassembly failures 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.
Ipv6 sent
sent generated
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.
forwarded 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.
fragmented The number of IPv6 datagrams that have been successfully
fragmented at this output interface.
generated
fragments
The number of output datagram fragments that have been
generated as a result of fragmentation at this output interface.
fragmented failed The number of IPv6 datagrams that have been discarded
because they needed to be fragmented at this output interface
but could not be.
encapsulation
failed
Failure that can result from an unresolved address or failure to
queue a packet.
no route The number of input datagrams discarded because no route
could be found to transmit them to their destination.
too big The number of input datagrams that could not be forwarded
because their size exceeded the link MTU of the outgoing
interface.
Table 36-5 show ipv6 traffic - display description (Continued)
Field Description
To Next Page
Loading...
