D-Link 5000 Series Cli Reference Manual page 853

Layer 2/3 managed 10g/25g/40g/100g data center switches
Hide thumbs Also See for 5000 Series:
Table of Contents

Advertisement

5000 Series Layer 2/3 Managed Data Center Switch CLI Reference Guide
show ipv6 traffic [{slot/port | vlan 1-4093 | loopback loopback-id | tunnel tunnet-id}]
Parameters
slot/port
vlan 1-4093
loopback loopback-id
tunnel tunnet-id
Default
The default is None.
Command Mode
Privileged EXEC
Display Parameters
Total Datagrams Received
Received Datagrams
Locally Delivered
Received Datagrams
Discarded Due 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
(Optional) Enter an interface in slot/port format.
(Optional) Enter an interface in VLAN format.
(Optional) Display the configured Loopback interface information.
(Optional) Configure IPv6 Tunnel.
Total number of input datagrams received by the interface, including
those received in error.
Total number of datagrams successfully delivered to IPv6 user-protocols
(including ICMP). This counter increments at the interface to which
these datagrams were addressed, which might not necessarily be the
input interface for some of the datagrams.
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).
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
847

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents