Querying OSPFv3
OSPFv3 operational data is a valuable asset for network administrators, offering crucial insights to optimize performance, troubleshoot issues effectively, and maintain a robust and resilient network infrastructure. Querying OSPFv3 is the process of retrieving detailed information about the OSPFv3 routing protocol's operation within a network. Querying OSPFv3 is essential for network troubleshooting, optimization, and capacity planning. It helps in identifying and resolving routing issues before they affect the network's performance or availability. It provides real-time visibility into the network's state, encompassing the status of routers, links, and neighboring devices. Additionally, it aids in optimizing routing tables and ensuring efficient traffic flow.
Querying OSPFv3 Instance details
Querying OSPFv3 Instance details
<rpc xmlns="urn:ie:params:xml:ns:netconf:base:1.0" message-id="101">
<get>
<filter>
<System xmlns="htp://cisco.com/ns/yang/cisco-nx-os-device">
<ospfv3-items>
<inst-items>
<Inst-list>
<name>1</name>
</Inst-list>
</inst-items>
</ospfv3-items>
</System>
</filter>
</get>
</rpc>
Note: This example was added in Release 10.4(3).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
show ospfv3 1
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
| MO | DN |
|---|---|
| Inst | sys/ospfv3/inst-1 |
Inst Properties
The following table contains information about the Inst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
| Property Name | Data Type | Description |
|---|---|---|
| OperErr | scalar:Bitmask | Operational Errors Qualifier |
| memAlert | scalar:Enum8 | OSPFv3 operational memory alert level |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Querying OSPFv3 Dom details
Querying OSPFv3 Dom details
<rpc xmlns="urn:ie:params:xml:ns:netconf:base:1.0" message-id="101">
<get>
<filter>
<System xmlns="htp://cisco.com/ns/yang/cisco-nx-os-device">
<ospfv3-items>
<inst-items>
<Inst-list>
<name>1</name>
<dom-items>
<Dom-list>
<name>vrf1</name>
</Dom-list>
</dom-items>
</Inst-list>
</inst-items>
</ospfv3-items>
</System>
</filter>
</get>
</rpc>
Note: This example was added in Release 10.4(3).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
show ospfv3 1 vrf vrf1
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
| MO | DN |
|---|---|
| Dom | sys/ospfv3/inst-1/dom-default |
Dom Properties
The following table contains information about the Dom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
| Property Name | Data Type | Description |
|---|---|---|
| operSt | scalar:Bitmask | Operational state of VRF |
| operRtrId | ip:RtrId | Operational Router identifier for this VRF |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Querying OSPFv3 Dom Stats
Querying OSPFv3 Dom Stats
<rpc xmlns="urn:ie:params:xml:ns:netconf:base:1.0" message-id="101">
<get>
<filter>
<System xmlns="htp://cisco.com/ns/yang/cisco-nx-os-device">
<ospfv3-items>
<inst-items>
<Inst-list>
<name>1</name>
<dom-items>
<Dom-list>
<name>vrf1</name>
<domstats-items/>
</Dom-list>
</dom-items>
</Inst-list>
</inst-items>
</ospfv3-items>
</System>
</filter>
</get>
</rpc>
Note: This example was added in Release 10.4(3).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
show ospfv3 1 vrf vrf1
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
| MO | DN |
|---|---|
| DomStats | sys/ospfv3/inst-1/dom-default/domstats |
DomStats Properties
The following table contains information about the DomStats properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
| Property Name | Data Type | Description |
|---|---|---|
| ifCnt | scalar:Uint32 | Holds the count of interfaces |
| areaCnt | scalar:Uint32 | Holds the number of area's configured |
| stubAreaCnt | scalar:Uint32 | Holds the count of stub areas |
| nssaAreaCnt | scalar:Uint32 | Count of not-so-stubby area(NSSA) area |
| extAreaCnt | scalar:Uint32 | Holds the count of external areas |
| activeStubAreaCnt | scalar:Uint32 | Holds the count of active stub areas |
| activeNssaAreaCnt | scalar:Uint32 | Active not-so-stubby area(NSSA) area count |
| activeExtAreaCnt | scalar:Uint32 | Holds the active external area count |
| activeAreaCnt | scalar:Uint32 | Holds the count of active areas |
| lastStatsClearTs | scalar:Date | Holds the last statistics clear timestamp |
| peerCnt | scalar:Uint32 | Holds the neighbor/peer count |
| extLsaCnt | scalar:Uint32 | Holds the external linkstate advertisement(LSA) count |
| opaqueAsLsaCnt | scalar:Uint32 | Holds the count of opaque AS LSAs |
| totalAsLsaCnt | scalar:Uint32 | Holds the total AS linkstate advertisement(LSA) count |
| newLsaRxCnt | scalar:Uint32 | Holds the Rx count ofnew link-state advertisement(LSA) |
| newLsaTxCnt | scalar:Uint32 | Holds the Tx count of new link-state advertisement(LSA) |
| areaBdrRtr | scalar:UByte | Status of Area Border Router(ABR) |
| asBdrRtr | scalar:UByte | Holds the status of Autonomous System Boundary Router(ASBR) |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Querying OSPFv3 interface details
Querying OSPFv3 interface details
<rpc xmlns="urn:ie:params:xml:ns:netconf:base:1.0" message-id="101">
<get>
<filter>
<System xmlns="htp://cisco.com/ns/yang/cisco-nx-os-device">
<ospfv3-items>
<if-items>
<If-list>
<id>eth1/1</id>
</If-list>
</if-items>
</ospfv3-items>
</System>
</filter>
</get>
</rpc>
Note: This example was added in Release 10.4(3).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
show ospfv3 interface vrf all
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
| MO | DN |
|---|---|
| If | sys/ospfv3/if-[eth1/1] |
DomStats Properties
The following table contains information about the If properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
| Property Name | Data Type | Description |
|---|---|---|
| Id | ip:RtrId | Interface Identifier of this endpoint |
| operSt | scalar:Enum8 | Interface operational state, can be p2p,loopback, etc. |
| type | scalar:Enum8 | Type of interface, p2p or broadcast etc. |
| flags | scalar:Bitmask32 | Interface flags to indicate state of interface |
| Ipv6Addr | address:Ip | IPv6 address of interface |
| dr | address:Ip | Designated router IPv6 Address |
| bdr | address:Ip | Backup designated router IPv6 Address |
| drId | ip:RtrId | Designated router identifier |
| bdrId | ip:RtrId | Backup designated router identifier |
| lsaCksumSum | scalar:Uint32 | link-state advertisement checksum Sum |
| operCost | scalar:Uint16 | Operational cost of interface |
| operDeadIntvl | scalar:Uint32 | Interface operational dead interval |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Querying OSPFv3 interface stats
Querying OSPFv3 interface stats
xmlns="urn:ie:params:xml:ns:netconf:base:1.0" message-id="101">
<get>
<filter>
<System xmlns="htp://cisco.com/ns/yang/cisco-nx-os-device">
<ospfv3-items>
<if-items>
<If-list>
<id>eth1/1</id>
<ifstats-items/>
</If-list>
</if-items>
</ospfv3-items>
</System>
</filter>
</get>
</rpc>
Note: This example was added in Release 10.4(3).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
show ospfv3 interface vrf all
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
| MO | DN |
|---|---|
| IfStats | sys/ospfv3/if-[eth1/1]/ifstats |
DomStats Properties
The following table contains information about the If properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
| Property Name | Data Type | Description |
|---|---|---|
| evCnt | scalar:Uint32 | Interface events count |
| lsaCnt | scalar:Uint322 | Link-state advertisement(LSA) count |
| peerCnt | scalar:Uint322 | Holds the count of peers/neighbors |
| floodToPeerCnt | scalar:Uint322 | Flood to neighbor count |
| adjCnt | scalar:Uint322 | Holds the count of adjacency |
| grHelperPeerCnt | scalar:Uint322 | Number of peers in GR hitless helper mode |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Querying OSPFv3 Area details
Querying OSPFv3 Area details
xmlns="urn:ie:params:xml:ns:netconf:base:1.0" message-id="101">
<get>
<filter>
<System xmlns="htp://cisco.com/ns/yang/cisco-nx-os-device">
<ospfv3-items>
<inst-items>
<Inst-list>
<name>1</name>
<dom-items>
<Dom-list>
<name>default</name>
<area-items>
<Area-list>
<id>0.0.0.0</id>
</Area-list>
</area-items>
</Dom-list>
</dom-items>
</Inst-list>
</inst-items>
</ospfv3-items>
</System>
</filter>
</get>
</rpc>
Note: This example was added in Release 10.4(3).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
show ospfv3 vrf all
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
| MO | DN |
|---|---|
| Area | sys/ospfv3/inst-1/dom-default/area-0.0.0.0 |
Area Properties
The following table contains information about the If properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
| Property Name | Data Type | Description |
|---|---|---|
| brCnt | scalar:Uint32 | Area border router count |
| asbrCnt | scalar:Uint322 | Autonomous system boundary router count |
| lsaCksumSum | scalar:Uint322 | link-state advertisement checksum sum |
| nssaTransSt | scalar:Enum8 | Not-So-Stubby Area translator state |
| nssaTransStabIntvl | scalar:Uint32 | Not-So-Stubby Area translator stability interval |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Querying OSPFv3 Area Stats
Querying OSPFv3 Area Stats
xmlns="urn:ie:params:xml:ns:netconf:base:1.0" message-id="101">
<get>
<filter>
<System xmlns="htp://cisco.com/ns/yang/cisco-nx-os-device">
<ospfv3-items>
<inst-items>
<Inst-list>
<name>1</name>
<dom-items>
<Dom-list>
<name>default</name>
<area-items>
<Area-list>
<id>0.0.0.0</id>
<areastats-items/>
</Area-list>
</area-items>
</Dom-list>
</dom-items>
</Inst-list>
</inst-items>
</ospfv3-items>
</System>
</filter>
</get>
</rpc>
Note: This example was added in Release 10.4(3).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
show ospfv3 vrf all
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
| MO | DN |
|---|---|
| AreaStats | sys/ospfv3/inst-1/dom-default/area-0.0.0.0/areastats |
Area Properties
The following table contains information about the If properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
| Property Name | Data Type | Description |
|---|---|---|
| areaCreatedTs | scalar:Date | Timestamp of the area created |
| spfRuns | scalar:Uint32 | Number of Shortest Path First (SPF) runs |
| lsaCnt | scalar:Uint32 | Count of link-state advertisements(LSA) |
| lastSpfDuration | scalar:Uint32 | Duration of last Shortest Path First (SPF) |
| ifCnt | scalar:Uint32 | Total number of interfaces |
| activeIfCnt | scalar:Uint32 | Number of active interfaces |
| passiveIfCnt | scalar:Uint32 | Number of passive interfaces |
| lpbkIfCnt | scalar:Uint32 | Number of loopback interfaces |
| adjCnt | scalar:Uint32 | Number of adjacencies formed |
| grHelperPeerCnt | scalar:Uint32 | Graceful restart helper peer count |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Querying OSPFv3 Adjacency details
Querying OSPFv3 Adjacency details
<rpc xmlns="urn:ie:params:xml:ns:netconf:base:1.0" message-id="101">
<get>
<filter>
<System xmlns="htp://cisco.com/ns/yang/cisco-nx-os-device">
<ospfv3-items>
<if-items>
<If-list>
<id>eth1/20</id>
<adj-items>
<AdjEp-list/>
<AdjEp-list>
<id>22.1.0.1</id>
</AdjEp-list>
</adj-items>
</If-list>
</if-items>
</ospfv3-items>
</System>
</filter>
</get>
</rpc>
Note: This example was added in Release 10.4(3).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
show ospfv3 neighbors vrf all
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
| MO | DN |
|---|---|
| AdjEp | sys/ospfv3/if-[eth1/1]/adj-100.1.1.1 |
AdjEp Properties
The following table contains information about the AdjEp properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
| Property Name | Data Type | Description |
|---|---|---|
| Id | ip:RtrId | OSPF adjacency neighbor's router id |
| operSt | scalar:Enum8 | Operational state of OSPF adjacency |
| bfdSt | scalar:Enum8 | Operational Bidirectional Forwarding Detection(BFD) State |
| area | address:IPv4 | OSPF adjacency operational area ID |
| prio | scalar:UByte | Operational neighbor priority |
| dr | address:Ip | Designated router address(DR) |
| Bdr | address:Ip | Backup designated router address(BDR) |
| peerIp | address:Ip | Adjacency peer IP address |
| helloOptions | scalar:Uint32 | Peer options from hello packet |
| dbdOptions | scalar:Uint32 | Peer options from database descriptor(DBD) packet |
| flags | scalar:Bitmask16 | Adjacency flags can be master-self,all-dbdssent,all-dbds-acked and peer-gr-helper |
| peerName | string:Basic | OSPf adjacency Neighbor name |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Querying OSPFv3 Adjacency Stats
Querying OSPFv3 Adjacency Stats
<rpc xmlns="urn:ie:params:xml:ns:netconf:base:1.0" message-id="101">
<get>
<filter>
<System xmlns="htp://cisco.com/ns/yang/cisco-nx-os-device">
<ospfv3-items>
<if-items>
<If-list>
<id>eth1/20</id>
<adj-items>
<AdjEp-list>
<id>22.1.0.1</id>
<adjstats-items/>
</AdjEp-list>
</adj-items>
</If-list>
</if-items>
</ospfv3-items>
</System>
</filter>
</get>
</rpc>
Note: This example was added in Release 10.4(3).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
show ospfv3 neighbors vrf all
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
| MO | DN |
|---|---|
| AdjStats | sys/ospfv3/if-[eth1/1]/adj-100.1.1.1/adjstats |
AdjStats Properties
The following table contains information about the AdjStats properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
| Property Name | Data Type | Description |
|---|---|---|
| stChgCnt | scalar:Uint32 | Number of states changed during OSPF adjacency |
| lastStChgTs | scalar:Date | Timestamp of the latest state change |
| lastNonHelloPktTs | scalar:Date | Timestamp of the last non hello packet received |
| dbdSeqNum | scalar:Uint32 | Database descriptor(DBD) sequence number |
| reqLsaCnt | scalar:Uint32 | Number of outstanding LSAs from last request |
| outstandingLsaCnt | scalar:Uint32 | Number of outstanding LSAs from last request |
| lsaReqRexmitCnt | scalar:Uint32 | Number of retransmissions of LSA request |
| deadTimerExpTs | scalar:Date | Timestamp of the dead timer expiry |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Querying OSPFv3 Traffic
Querying OSPFv3 Traffic
<rpc xmlns="urn:ie:params:xml:ns:netconf:base:1.0" message-id="101">
<get>
<filter>
<System xmlns="htp://cisco.com/ns/yang/cisco-nx-os-device">
<ospfv3-items>
<if-items>
<If-list>
<id>eth1/20</id>
<trstats-items/>
</If-list>
</if-items>
</ospfv3-items>
</System>
</filter>
</get>
</rpc>
Note: This example was added in Release 10.4(3).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
show ospfv3 traffic vrf all
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
| MO | DN |
|---|---|
| TrafficStats | sys/ospfv3/if-[eth1/1]/trstats |
TrafficStats Properties
The following table contains information about the TrafficStats properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
| Property Name | Data Type | Description |
|---|---|---|
| totalPktsRcvd | scalar:Uint32 | Total number of packets received |
| helloPktsRcvd | scalar:Uint32 | Total number of hello packets received |
| dbdPktsRcvd | scalar:Uint32 | Database description packets received |
| lsReqPktsRcvd | scalar:Uint32 | Link-state request packets received |
| lsUpdPktsRcvd | scalar:Uint32 | Link-state update packets received |
| lsAckPktsRcvd | scalar:Uint32 | Link-state ACK packets received |
| rcvdPktsDropped | scalar:Uint32 | Count of received packets dropped |
| errPktsRcvd | scalar:Uint32 | Count of Error packets received |
| errHelloPktsRcvd | scalar:Uint32 | Number of Error hello packets received |
| errDbdPktsRcvd | scalar:Uint32 | Error database description packets received |
| errLsReqPktsRcvd | scalar:Uint32 | Error link-state request packets received |
| errLsUpdPktsRcvd | scalar:Uint32 | Error link-state update packets received |
| errLsAckPktsRcvd | scalar:Uint32 | Error LSACK Packets Received |
| unknownPktsRcvd | scalar:Uint32 | Count of unknown packets received |
| dupRtrIdPktsRcvd | scalar:Uint32 | Duplicate router-id packets received |
| dupSrcAddrPktsRcvd | scalar:Uint32 | Duplicate source address packets received |
| wrongAreaPktsRcvd | scalar:Uint32 | Wrong Area Packets Received |
| invalidSrcAddrPktsRcvd | scalar:Uint32 | Invalid Source Addr Packets Received |
| invalidDestAddrPktsRcvd | scalar:Uint32 | Invalid Destination Addr Packets Received |
| badCRCPktsRcvd | scalar:Uint32 | Bad CRC Packets Received |
| badVersionPktsRcvd | scalar:Uint32 | Bad Version Packets Received |
| badResvFieldPktsRcvd | scalar:Uint32 | Bad Reserved Field Packets Received |
| peerRtrIdChgdPktsRcvd | scalar:Uint32 | Peer RouterId Changed Packets Received |
| peerNotFoundPktsRcvd | scalar:Uint32 | Peer Not Found Packets Received |
| badAuthPktsRcvd | scalar:Uint32 | Bad Authentication Packets Received |
| badLenPktsRcvd | scalar:Uint32 | Bad Length Packets Received |
| passiveIntfPktsRcvd | scalar:Uint32 | Passive Interface Packets Received |
| noOspfIntfPktsRcvd | scalar:Uint32 | No OSPF Interface Packets Received |
| rcvdLsaPktsIgnored | scalar:Uint32 | Received LSA Packets Ignored |
| droppedLsaPktsWhileSPF | scalar:Uint32 | LSA Packets Dropped During SPF |
| droppedLsaPktsWhileGR | scalar:Uint32 | LSA Packets Dropped During GR |
| totalPktsSent | scalar:Uint32 | Total number of packets sent |
| helloPktsSent | scalar:Uint32 | Total number of hello packets sent |
| dbdPktsSent | scalar:Uint32 | Database description packets sent |
| lsReqPktsSent | scalar:Uint32 | Link-state request packets sent |
| lsUpdPktsSent | scalar:Uint32 | Link-state update packets sent |
| lsAckPktsSent | scalar:Uint32 | Link-state ACK packets sent |
| droppedSendPkts | scalar:Uint32 | Total number of dropped send packets |
| errSendPkts | scalar:Uint32 | Total number of error send packets |
| unknownSendPkts | scalar:Uint32 | Count of unknown send packets |
| lsuFirstTxPkts | scalar:Uint32 | Number of first transmission of LSU packets |
| lsuRexmitPkts | scalar:Uint32 | Number of retransmissions of LSU packets |
| lsuForLsreqPkts | scalar:Uint32 | Number of retransmissions of LSU packets |
| lsuPeerTxPkts | scalar:Uint32 | Number of LSU packets sent to a neighbor specifically |
| floodPktSendIpThrottle | scalar:Uint32 | Number of times flooding packets dropped due to IP queue throttling |
| floodPktSendTokenThrottle | scalar:Uint32 | Number of times flooding packets dropped due to token throttling |
| lastStatsClearTs | scalar:Uint32 | Last traffic statistics clear timestamp |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide: