Verifying PTP Counters
Beginning with Cisco NX-OS Release 10.5(2)F, users can view PTP packet counters for all interfaces or for a specified interface.
For more information, see the Cisco Nexus 9000 Series NX-OS System Management Configuration Guide:
Verifying PTP Counters for all Interfaces
Verifying PTP Counters for all Interfaces
POST http://<mgmt0_IP>/api/mo/sys.json
{
"totalCount": "1",
"imdata": [
{
"ptpPktCounters": {
"attributes": {
"dn": "sys/ptp/ephoperpktcounters"
},
"children": [
{
"ptpPktCountersIf": {
"attributes": {
"announuceRx": "217",
"announuceTx": "0",
"delayReqRx": "0",
"delayReqTx": "433",
"delayRespRx": "433",
"delayRespTx": "0",
"followUpRx": "0",
"followUpTx": "0",
"id": "eth1/5",
"managementRx": "0",
"managementTx": "0",
"pDelayFollowUpRx": "0",
"pDelayFollowUpTx": "0",
"pDelayReqRx": "0",
"pDelayReqTx": "0",
"pDelayRespRx": "0",
"pDelayRespTx": "0",
"rn": "if-[eth1/5]",
"signalingRx": "0",
"signalingTx": "0",
"syncRx": "1729",
"syncTx": "0"
}
}
},
{
"ptpPktCountersIf": {
"attributes": {
"announuceRx": "0",
"announuceTx": "0",
"delayReqRx": "0",
"delayReqTx": "0",
"delayRespRx": "0",
"delayRespTx": "0",
"followUpRx": "0",
"followUpTx": "0",
"id": "eth1/9",
"managementRx": "0",
"managementTx": "0",
"pDelayFollowUpRx": "0",
"pDelayFollowUpTx": "0",
"pDelayReqRx": "0",
"pDelayReqTx": "0",
"pDelayRespRx": "0",
"pDelayRespTx": "0",
"rn": "if-[eth1/9]",
"signalingRx": "0",
"signalingTx": "0",
"syncRx": "0",
"syncTx": "0"
}
}
},
{
"ptpPktCountersIf": {
"attributes": {
"announuceRx": "0",
"announuceTx": "217",
"delayReqRx": "433",
"delayReqTx": "0",
"delayRespRx": "0",
"delayRespTx": "433",
"followUpRx": "0",
"followUpTx": "1728",
"id": "eth1/36",
"managementRx": "0",
"managementTx": "0",
"pDelayFollowUpRx": "0",
"pDelayFollowUpTx": "0",
"pDelayReqRx": "0",
"pDelayReqTx": "0",
"pDelayRespRx": "0",
"pDelayRespTx": "0",
"rn": "if-[eth1/36]",
"signalingRx": "0",
"signalingTx": "0",
"syncRx": "0",
"syncTx": "1728"
}
}
},
{
"ptpPktCountersIf": {
"attributes": {
"announuceRx": "0",
"announuceTx": "0",
"delayReqRx": "0",
"delayReqTx": "0",
"delayRespRx": "0",
"delayRespTx": "0",
"followUpRx": "0",
"followUpTx": "0",
"id": "eth1/15",
"managementRx": "0",
"managementTx": "0",
"pDelayFollowUpRx": "0",
"pDelayFollowUpTx": "0",
"pDelayReqRx": "0",
"pDelayReqTx": "0",
"pDelayRespRx": "0",
"pDelayRespTx": "0",
"rn": "if-[eth1/15]",
"signalingRx": "0",
"signalingTx": "0",
"syncRx": "0",
"syncTx": "0"
}
}
},
{
"ptpPktCountersIf": {
"attributes": {
"announuceRx": "0",
"announuceTx": "217",
"delayReqRx": "433",
"delayReqTx": "0",
"delayRespRx": "0",
"delayRespTx": "433",
"followUpRx": "0",
"followUpTx": "1728",
"id": "eth1/35",
"managementRx": "0",
"managementTx": "0",
"pDelayFollowUpRx": "0",
"pDelayFollowUpTx": "0",
"pDelayReqRx": "0",
"pDelayReqTx": "0",
"pDelayRespRx": "0",
"pDelayRespTx": "0",
"rn": "if-[eth1/35]",
"signalingRx": "0",
"signalingTx": "0",
"syncRx": "0",
"syncTx": "1728"
},
"children": [
{
"ptpPktCountersIfUcastIp": {
"attributes": {
"announuceRx": "0",
"announuceTx": "0",
"delayReqRx": "0",
"delayReqTx": "0",
"delayRespRx": "0",
"delayRespTx": "0",
"followUpRx": "0",
"followUpTx": "0",
"ip": "30.30.30.30",
"managementRx": "0",
"managementTx": "0",
"pDelayFollowUpRx": "0",
"pDelayFollowUpTx": "0",
"pDelayReqRx": "0",
"pDelayReqTx": "0",
"pDelayRespRx": "0",
"pDelayRespTx": "0",
"rn": "ip-[30.30.30.30]",
"signalingRx": "0",
"signalingTx": "0",
"syncRx": "0",
"syncTx": "0"
}
}
},
{
"ptpPktCountersIfUcastIp": {
"attributes": {
"announuceRx": "0",
"announuceTx": "217",
"delayReqRx": "433",
"delayReqTx": "0",
"delayRespRx": "0",
"delayRespTx": "433",
"followUpRx": "0",
"followUpTx": "1728",
"ip": "200.1.1.20",
"managementRx": "0",
"managementTx": "0",
"pDelayFollowUpRx": "0",
"pDelayFollowUpTx": "0",
"pDelayReqRx": "0",
"pDelayReqTx": "0",
"pDelayRespRx": "0",
"pDelayRespTx": "0",
"rn": "ip-[200.1.1.20]",
"signalingRx": "0",
"signalingTx": "0",
"syncRx": "0",
"syncTx": "1728"
}
}
}
]
}
}
]
}
},
{
"warning": {
"attributes": {
"text": "backend rv=43700005, Dumped entries into ephemeral objstore"
}
}
}
]
}
CLI Command
The CLI command below is the equivalent of the payload example 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 or the YANG tab to view the XML payload.
show ptp counters all details
Note: Support was added in Release 10.5(2).
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 |
|---|---|
| ephoperpktcounters | sys/ptp/ephoperpktcounters |
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:
Verifying PTP Counters for a Specific Interface
Verifying PTP Counters for a Specific Interface
POST http://<mgmt0_IP>/api/mo/sys.json
{
"totalCount": "1",
"imdata": [
{
"ptpPktCountersIf": {
"attributes": {
"announuceRx": "0",
"announuceTx": "1923",
"delayReqRx": "3843",
"delayReqTx": "0",
"delayRespRx": "0",
"delayRespTx": "3843",
"dn": "sys/ptp/ephoperpktcounters/if-[eth1/36]",
"followUpRx": "0",
"followUpTx": "15320",
"id": "eth1/36",
"managementRx": "0",
"managementTx": "0",
"pDelayFollowUpRx": "0",
"pDelayFollowUpTx": "0",
"pDelayReqRx": "0",
"pDelayReqTx": "0",
"pDelayRespRx": "0",
"pDelayRespTx": "0",
"signalingRx": "0",
"signalingTx": "0",
"syncRx": "0",
"syncTx": "15321"
},
"children": [
{
"ptpPktCountersIfUcastIp": {
"attributes": {
"announuceRx": "0",
"announuceTx": "1923",
"delayReqRx": "3843",
"delayReqTx": "0",
"delayRespRx": "0",
"delayRespTx": "3843",
"followUpRx": "0",
"followUpTx": "15320",
"ip": "2002::80",
"managementRx": "0",
"managementTx": "0",
"pDelayFollowUpRx": "0",
"pDelayFollowUpTx": "0",
"pDelayReqRx": "0",
"pDelayReqTx": "0",
"pDelayRespRx": "0",
"pDelayRespTx": "0",
"rn": "ip-[2002::80]",
"signalingRx": "0",
"signalingTx": "0",
"syncRx": "0",
"syncTx": "15321"
}
}
}
]
}
},
{
"warning": {
"attributes": {
"text": "backend rv=43700005, Dumped entries into ephemeral objstore"
}
}
}
]
}
CLI Command
The CLI command below is the equivalent of the payload example 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 or the YANG tab to view the XML payload.
show ptp counters interface ethernet 1/36 detail
Note: Support was added in Release 10.5(2).
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-[eth1/36] | sys/ptp/ephoperpktcounters/if-[eth1/36] |
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:
Verifying PTP Counters of a Specific Peer IP on a Port
Verifying PTP Counters of a Specific Peer IP on a Port
POST http://<mgmt0_IP>/api/mo/sys.json
{
"totalCount": "1",
"imdata": [
{
"ptpPktCountersIfUcastIp": {
"attributes": {
"announuceRx": "0",
"announuceTx": "1994",
"delayReqRx": "3986",
"delayReqTx": "0",
"delayRespRx": "0",
"delayRespTx": "3986",
"dn": "sys/ptp/ephoperpktcounters/if-[eth1/36]/ip-[192.168.1.1]",
"followUpRx": "0",
"followUpTx": "15888",
"ip": "192.168.1.1",
"managementRx": "0",
"managementTx": "0",
"pDelayFollowUpRx": "0",
"pDelayFollowUpTx": "0",
"pDelayReqRx": "0",
"pDelayReqTx": "0",
"pDelayRespRx": "0",
"pDelayRespTx": "0",
"signalingRx": "0",
"signalingTx": "0",
"syncRx": "0",
"syncTx": "15889"
}
}
},
{
"warning": {
"attributes": {
"text": "backend rv=43700005, Dumped entries into ephemeral objstore"
}
}
}
]
}
CLI Command
The CLI command below is the equivalent of the payload example 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 or the YANG tab to view the XML payload.
show ptp counters interface ethernet 1/36 ipv4 192.168.1.1
Note: Support was added in Release 10.5(2).
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 |
|---|---|
| ip-[192.168.1.1] | sys/ptp/ephoperpktcounters/if-[eth1/36]/ip-[192.168.1.1] |
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: