Table of Contents
Advertisement
10.4.1.9 show ipv6 ospf interface stats
This command displays the statistics for a specific interface. The command only displays
information if OSPF is enabled
Syntax
show ipv6 ospf interface stats <slot/port>
<slot/port> - Interface number.
Default Setting
None
Command Mode
Privileged Exec
User Exec
Display Messages
OSPFv3 Area ID: The area id of this OSPF interface.
IP Address: The IP address associated with this OSPF interface.
OSPFv3 Interface Events: The number of times the specified OSPF interface has changed its
state, or an error has occurred.
Virtual Events: The number of state changes or errors that occurred on this virtual link.
Neighbor Events: The number of times this neighbor relationship has changed state, or an error
has occurred.
Packets Received: The number of OSPFv3 packets received on the interface.
Packets Transmitted: The number of OSPFv3 packets sent on the interface.
LSAs Sent: The total number of LSAs flooded on the interface.
LSA Acks Received: The total number of LSA acknowledged from this interface.
LSA Acks Sent: The total number of LSAs acknowledged to this interface.
Sent Packets: The number of OSPF packets transmitted on the interface.
Received Packets: The number of valid OSPF packets received on the interface.
Discards: The number of received OSPF packets discarded because of an error in the packet or an
error in processing the packet.
Bad Version: The number of received OSPF packets whose version field in the OSPF header does
not match the version of the OSPF process handling the packet.
Virtual Link Not Found: The number of received OSPF packets discarded where the ingress
interface is in a non-backbone area and the OSPF header identifies the packet as belonging to the
backbone, but OSPF does not have a virtual link to the packet's sender.
Area Mismatch: The number of OSPF packets discarded because the area ID in the OSPF header
is not the area ID configured on the ingress interface.
Invalid Destination Address: The number of OSPF packets discarded because the packet's
destination IP address is not the address of the ingress interface and is not the AllDrRouters or
AllSpfRouters multicast addresses.
- 574 -
Advertisement
Table of Contents
