Configuring PTP Clock Correction
Configuring the Frequency Correction From Hardware or Software
Configuring the Frequency Correction From Hardware or Software
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
"platformEntity": {
"children": [
{
"platformEntityExtended": {
"attributes": {
"ptpCorrHw": "yes"
}}}]}}
{
imdata:[]
}
<System>
<pltfm-items>
<entityextd-items>
<ptpCorrHw>true</ptpCorrHw>
</entityextd-items>
</pltfm-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ptp correction hardware
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 |
---|---|
platformEntity | sys/pltfm |
platformEntityExtended | sys/pltfm/entityextd |
platformEntityExtended Properties
The following table contains information about the platformEntityExtended 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 | Values |
---|---|---|---|
ptpCorrHw | scalar:Bool | Ptp frequnecy correction from hardware or software | SELECTION: true or false DEFAULT: true |
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:
Deleting the Frequency Correction From Hardware or Software
Deleting the Frequency Correction From Hardware or Software
POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
{
"platformEntity": {
"children": [
{
"platformEntityExtended": {
"attributes": {
"ptpCorrHw": "no"
}}}]}}
{
imdata:[]
}
<System>
<pltfm-items>
<entityextd-items>
<ptpCorrHw>false</ptpCorrHw>
</entityextd-items>
</pltfm-items>
</System>
Note: This example was added in Release 9.3(5).
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.
no ptp correction hardware
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 |
---|---|
platformEntity | sys/pltfm |
platformEntityExtended | sys/pltfm/entityextd |
platformEntityExtended Properties
The following table contains information about the platformEntityExtended 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 | Values |
---|---|---|---|
ptpCorrHw | scalar:Bool | Ptp frequnecy correction from hardware or software | SELECTION: true or false DEFAULT: true |
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:
Enabling Increasing Number of PTP Sessions per System by Offloading Some Timers to Linecard
Enabling Increasing Number of PTP Sessions per System by Offloading Some Timers to Linecard
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"offload": "enabled"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<offload>enabled</offload>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ptp offload
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
offload | ptp:AdminSt (scalar:Enum8) | PTP offload enable/disable | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
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:
Disabling Increasing Number of PTP Sessions per System by Offloading Some Timers to Linecard
Disabling Increasing Number of PTP Sessions per System by Offloading Some Timers to Linecard
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"offload": "disabled"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<offload>disabled</offload>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
no ptp offload
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
offload | ptp:AdminSt (scalar:Enum8) | PTP offload enable/disable | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
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:
Configuring the Domain Clock Class Threshold
Configuring the Domain Clock Class Threshold
POST http://<mgmt0_IP>/api/mo/sys/ptp.json
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpDomain": {
"attributes": {
"clockClassThreshold": "1",
"domain": "1"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<domain-items>
<PtpDomain-list>
<domain>1</domain>
<clockClassThreshold>1</clockClassThreshold>
</PtpDomain-list>
</domain-items>
</ptp-items>
</System>
Note:
- Supported on N3K-C3548P-XL platform
- This example was added in Release 9.3(5).
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.
ptp domain 1 clock-class-threshold 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 |
---|---|
ptpPtpEntity | sys/ptp |
ptpPtpDomain | sys/ptp/domain-1 |
ptpPtpDomain Properties
The following table contains information about the ptpPtpDomain 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 | Values |
---|---|---|---|
clockClassThreshold | scalar:Uint16 | Domain clock-class-threshold value | RANGE: [0 , 255] DEFAULT: 248 |
domain | scalar:Uint16 | PTP Clock Domain value | RANGE: [0 , 127] |
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:
Deleting the Domain Clock Class Threshold
Deleting the Domain Clock Class Threshold
POST http://<mgmt0_IP>/api/mo/sys/ptp.json
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpDomain": {
"attributes": {
"clockClassThreshold": "248",
"domain": "1"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<domain-items>
<PtpDomain-list>
<domain>1</domain>
<clockClassThreshold>248</clockClassThreshold>
</PtpDomain-list>
</domain-items>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
no ptp domain 1 clock-class-threshold 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 |
---|---|
ptpPtpEntity | sys/ptp |
ptpPtpDomain | sys/ptp/domain-1 |
ptpPtpDomain Properties
The following table contains information about the ptpPtpDomain 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 | Values |
---|---|---|---|
clockClassThreshold | scalar:Uint16 | Domain clock-class-threshold value | RANGE: [0 , 255] DEFAULT: 248 |
domain | scalar:Uint16 | PTP Clock Domain value | RANGE: [0 , 127] |
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:
Configuring the Domain Priority
Configuring the Domain Priority
POST http://<mgmt0_IP>/api/mo/sys/ptp.json
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpDomain": {
"attributes": {
"domain": "1",
"priority": "1"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<domain-items>
<PtpDomain-list>
<domain>1</domain>
<priority>1</priority>
</PtpDomain-list>
</domain-items>
</ptp-items>
</System>
Note:
- Supported on N3K-C3548P-XL platform
- This example was added in Release 9.3(5).
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.
ptp domain 1 priority 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 |
---|---|
ptpPtpEntity | sys/ptp |
ptpPtpDomain | sys/ptp/domain-1 |
ptpPtpDomain Properties
The following table contains information about the ptpPtpDomain 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 | Values |
---|---|---|---|
domain | scalar:Uint16 | PTP Clock Domain value | RANGE: [0 , 127] |
priority | scalar:Uint16 | Priority value for PTP Domain | RANGE: [0 , 255] DEFAULT: 255 |
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:
Deleting the Domain Priority
Deleting the Domain Priority
POST http://<mgmt0_IP>/api/mo/sys/ptp.json
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpDomain": {
"attributes": {
"domain": "1",
"priority": "255"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<domain-items>
<PtpDomain-list>
<domain>1</domain>
<priority>255</priority>
</PtpDomain-list>
</domain-items>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
no ptp domain 1 priority 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 |
---|---|
ptpPtpEntity | sys/ptp |
ptpPtpDomain | sys/ptp/domain-1 |
ptpPtpDomain Properties
The following table contains information about the ptpPtpDomain 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 | Values |
---|---|---|---|
domain | scalar:Uint16 | PTP Clock Domain value | RANGE: [0 , 127] |
priority | scalar:Uint16 | Priority value for PTP Domain | RANGE: [0 , 255] DEFAULT: 255 |
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:
Configuring PTP Multi-Domain
Configuring PTP Multi-Domain
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"multiDomain": "enabled"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<multiDomain>enabled</multiDomain>
</ptp-items>
</System>
Note:
- Supported on N3K-C3548P-XL platform
- This example was added in Release 9.3(5).
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.
ptp multi-domain
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
multiDomain | ptp:AdminSt (scalar:Enum8) | PTP multi-domain enable/disable | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
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:
Deleting PTP Multi-Domain
Deleting PTP Multi-Domain
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"multiDomain": "disabled"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<multiDomain>disabled</multiDomain>
</ptp-items>
</System>
Note:
- Supported on N3K-C3548P-XL platform
- This example was added in Release 9.3(5).
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.
no ptp multi-domain
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
multiDomain | ptp:AdminSt (scalar:Enum8) | PTP multi-domain enable/disable | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
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:
Configuring PTP Multi-Domain Transition-Attributes Priority1
Configuring PTP Multi-Domain Transition-Attributes Priority1
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"multiDomainTransPriority1": "1"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<multiDomainTransPriority1>1</multiDomainTransPriority1>
</ptp-items>
</System>
Note:
- Supported on N3K-C3548P-XL platform
- This example was added in Release 9.3(5).
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.
ptp multi-domain transition-attributes priority1 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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
multiDomainTransPriority1 | scalar:Uint16 | PTP multi-domain transition-attributes Priority 1 value | RANGE: [0 , 255] DEFAULT: 255 |
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:
Deleting PTP Multi-Domain Transition-Attributes Priority1
Deleting PTP Multi-Domain Transition-Attributes Priority1
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"multiDomainTransPriority1": "255"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<multiDomainTransPriority1>255</multiDomainTransPriority1>
</ptp-items>
</System>
Note:
- Supported on N3K-C3548P-XL platform
- This example was added in Release 9.3(5).
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.
no ptp multi-domain transition-attributes priority1 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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
multiDomainTransPriority1 | scalar:Uint16 | PTP multi-domain transition-attributes Priority 1 value | RANGE: [0 , 255] DEFAULT: 255 |
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:
Configuring PTP Multi-Domain Priority Domain Conversion Priority2 Value
Configuring PTP Multi-Domain Priority Domain Conversion Priority2 Value
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"multiDomainTransPriority2": "1"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<multiDomainTransPriority2>1</multiDomainTransPriority2>
</ptp-items>
</System>
Note:
- Supported on N3K-C3548P-XL platform
- This example was added in Release 9.3(5).
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.
ptp multi-domain transition-attributes priority2 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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
multiDomainTransPriority2 | scalar:Uint16 | PTP multi-domain transition-attributes Priority 2 value | RANGE: [0 , 255] DEFAULT: 255 |
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:
Deleting PTP Multi-Domain Priority Domain Conversion Priority2 Value
Deleting PTP Multi-Domain Priority Domain Conversion Priority2 Value
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"multiDomainTransPriority2": "255"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<multiDomainTransPriority2>255</multiDomainTransPriority2>
</ptp-items>
</System>
Note:
- Supported on N3K-C3548P-XL platform
- This example was added in Release 9.3(5).
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.
no ptp multi-domain transition-attributes priority2 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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
multiDomainTransPriority2 | scalar:Uint16 | PTP multi-domain transition-attributes Priority 2 value | RANGE: [0 , 255] DEFAULT: 255 |
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:
Configuring Marker Packet Interval
Configuring Marker Packet Interval
POST http://<mgmt0_IP>/api/mo/sys/clock.json
{
"datetimeClock": {
"children": [
{
"datetimeTTag": {
"attributes": {
"ttagMarkerInterval": "3"
}}}]}}
{
imdata:[]
}
<System>
<clock-items>
<ttag-items>
<ttagMarkerInterval>3</ttagMarkerInterval>
</ttag-items>
</clock-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ttag-marker-interval 3
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 |
---|---|
datetimeClock | sys/clock |
datetimeTTag | sys/clock/ttag |
datetimeTTag Properties
The following table contains information about the datetimeTTag 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 | Values |
---|---|---|---|
ttagMarkerInterval | scalar:Uint32 | PTP ttag marker interval in seconds | RANGE: [1 , 4] DEFAULT: 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:
Deleting Marker Packet Interval
Deleting Marker Packet Interval
POST http://<mgmt0_IP>/api/mo/sys/clock.json
{
"datetimeClock": {
"children": [
{
"datetimeTTag": {
"attributes": {
"ttagMarkerInterval": "1"
}}}]}}
{
imdata:[]
}
<System>
<clock-items>
<ttag-items>
<ttagMarkerInterval>1</ttagMarkerInterval>
</ttag-items>
</clock-items>
</System>
Note: This example was added in Release 9.3(5).
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.
no ttag-marker-interval 3
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 |
---|---|
datetimeClock | sys/clock |
datetimeTTag | sys/clock/ttag |
datetimeTTag Properties
The following table contains information about the datetimeTTag 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 | Values |
---|---|---|---|
ttagMarkerInterval | scalar:Uint32 | PTP ttag marker interval in seconds | RANGE: [1 , 4] DEFAULT: 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:
Configuring PTP Clock Identity
Configuring PTP Clock Identity
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"clockIdentity": "D8:B1:90:71:E9:03"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<clockIdentity>D8:B1:90:71:E9:03</clockIdentity>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ptp clock-identity d8b1.9071.e903
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
clockIdentity | address:MAC | PTP clock-identity MAC Address | Value must match MM:MM:MM:SS:SS:SS format |
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:
Deleting PTP Clock Identity
Deleting PTP Clock Identity
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"clockIdentity": "00:BE:75:A2:F3:C1"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<clockIdentity>00:BE:75:A2:F3:C1</clockIdentity>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
no ptp clock-identity d8b1.9071.e903
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
clockIdentity | address:MAC | PTP clock-identity MAC Address | Value must match MM:MM:MM:SS:SS:SS format |
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:
Configuring PTP Grandmaster Capability
Configuring PTP Grandmaster Capability
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"gmCapConvergenceTime": "30",
"grandmasterCapable": "enabled"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<gmCapConvergenceTime>30</gmCapConvergenceTime>
<grandmasterCapable>enabled</grandmasterCapable>
</ptp-items>
</System>
Note:
- Supported on N3K-C3548P-XL platform
- This example was added in Release 9.3(5).
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.
ptp grandmaster-capable
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
gmCapConvergenceTime | scalar:Uint16 | PTP grandmaster-capable convergence-time value | RANGE: [3 , 2600] DEFAULT: 30 |
grandmasterCapable | ptp:GmCapable (scalar:Enum8) | PTP grandmaster-capable enable/disable | SELECTION: 0 - disabled 1 - enabled DEFAULT: enabled |
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:
Deleting PTP Grandmaster Capability
Deleting PTP Grandmaster Capability
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"gmCapConvergenceTime": "30",
"grandmasterCapable": "disabled"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<gmCapConvergenceTime>30</gmCapConvergenceTime>
<grandmasterCapable>disabled</grandmasterCapable>
</ptp-items>
</System>
Note:
- Supported on N3K-C3548P-XL platform
- This example was added in Release 9.3(5).
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.
no ptp grandmaster-capable
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
gmCapConvergenceTime | scalar:Uint16 | PTP grandmaster-capable convergence-time value | RANGE: [3 , 2600] DEFAULT: 30 |
grandmasterCapable | ptp:GmCapable (scalar:Enum8) | PTP grandmaster-capable enable/disable | SELECTION: 0 - disabled 1 - enabled DEFAULT: enabled |
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:
Configuring PTP Convergence Time in Seconds
Configuring PTP Convergence Time in Seconds
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"convergenceTime": "427"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<convergenceTime>427</convergenceTime>
</ptp-items>
</System>
Note:
- Supported on N3K-C3548P-XL platform
- This example was added in Release 9.3(5).
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.
ptp convergence-time 427
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
convergenceTime | scalar:Uint16 | PTP convergence-time value | RANGE: [3 , 2600] |
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:
Deleting PTP Convergence Time in Seconds
Deleting PTP Convergence Time in Seconds
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"convergenceTime": "0"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<convergenceTime>0</convergenceTime>
</ptp-items>
</System>
Note:
- Supported on N3K-C3548P-XL platform
- This example was added in Release 9.3(5).
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.
no ptp convergence-time 427
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
convergenceTime | scalar:Uint16 | PTP convergence-time value | RANGE: [3 , 2600] |
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:
Configuring PTP Clock Sync to Auto Adjust Frequency
Configuring PTP Clock Sync to Auto Adjust Frequency
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"clockSyncAuto": "yes"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<clockSyncAuto>true</clockSyncAuto>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ptp clock-sync auto
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
clockSyncAuto | scalar:Bool | PTP clock-sync auto yes/no | SELECTION: true or false |
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:
Deleting PTP Clock Sync to Auto Adjust Frequency
Deleting PTP Clock Sync to Auto Adjust Frequency
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"clockSyncAuto": "no"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<clockSyncAuto>false</clockSyncAuto>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
no ptp clock-sync auto
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
clockSyncAuto | scalar:Bool | PTP clock-sync auto yes/no | SELECTION: true or false |
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:
Configuring Management Packet Support
Configuring Management Packet Support
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"mgmt": "enabled"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<mgmt>enabled</mgmt>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ptp management
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
mgmt | ptp:Mgmt (scalar:Enum8) | PTP management packet support enable/disable | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
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:
Deleting Management Packet Support
Deleting Management Packet Support
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"mgmt": "disabled"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<mgmt>disabled</mgmt>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
no ptp management
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
mgmt | ptp:Mgmt (scalar:Enum8) | PTP management packet support enable/disable | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
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:
Configuring Tolerance for Mean-Path-Delay Variation
Configuring Tolerance for Mean-Path-Delay Variation
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"toleranceMPDState": "enabled",
"toleranceMPDVal": "10.000000"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<toleranceMPDState>enabled</toleranceMPDState>
<toleranceMPDVal>10.000000</toleranceMPDVal>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ptp delay tolerance mean-path 10
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
toleranceMPDState | ptp:AdminSt (scalar:Enum8) | PTP tolerance mean path delay threshold enable/disable | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
toleranceMPDVal | ptp:ToleranceThreshold (scalar:Float) | PTP tolerance mean path delay threshold | RANGE: [1 , 100] DEFAULT: 1.0 |
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:
Deleting Tolerance for Mean-Path-Delay Variation
Deleting Tolerance for Mean-Path-Delay Variation
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"toleranceMPDState": "disabled"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<toleranceMPDState>disabled</toleranceMPDState>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
no ptp delay tolerance mean-path 10
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
toleranceMPDState | ptp:AdminSt (scalar:Enum8) | PTP tolerance mean path delay threshold enable/disable | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
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:
Configuring for Reverse-Path Delay Variation
Configuring for Reverse-Path Delay Variation
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"toleranceRPDState": "enabled",
"toleranceRPDVal": "10.000000"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<toleranceRPDState>enabled</toleranceRPDState>
<toleranceRPDVal>10.000000</toleranceRPDVal>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ptp delay tolerance reverse-path 10
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
toleranceRPDState | ptp:AdminSt (scalar:Enum8) | PTP tolerance reverse path delay threshold enable/disable | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
toleranceRPDVal | ptp:ToleranceThreshold (scalar:Float) | PTP tolerance reverse path delay threshold | RANGE: [1 , 100] DEFAULT: 1.0 |
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:
Deleting for Reverse-Path Delay Variation
Deleting for Reverse-Path Delay Variation
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"toleranceRPDState": "disabled"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<toleranceRPDState>disabled</toleranceRPDState>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
no ptp delay tolerance reverse-path 10
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
toleranceRPDState | ptp:AdminSt (scalar:Enum8) | PTP tolerance reverse path delay threshold enable/disable | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
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:
Configuring the Clock Protocol
Configuring the Clock Protocol
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"datetimeClock": {
"attributes": {
"protocol": "none",
"vdcId": "1"
}}}]}}
{
imdata:[]
}
<System>
<clock-items>
<protocol>none</protocol>
<vdcId>1</vdcId>
</clock-items>
</System>
Note: This example was added in Release 9.3(5).
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.
clock protocol none
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 |
---|---|
topSystem | sys |
datetimeClock | sys/clock |
datetimeClock Properties
The following table contains information about the datetimeClock 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 | Values |
---|---|---|---|
protocol | datetime:ClockProtocol (scalar:Enum8) | Protocol Type | SELECTION: 0 - unspecified 1 - ptp 2 - ntp 3 - none DEFAULT: ntp |
vdcId | datetime:VdcId (scalar:Uint16) | Vdc | RANGE: [0, 65535] DEFAULT: 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:
Deleting the Clock Protocol to None
Deleting the Clock Protocol to None
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"datetimeClock": {
"attributes": {
"protocol": "unspecified",
"vdcId": "1"
}}}]}}
{
imdata:[]
}
<System>
<clock-items>
<protocol>unspecified</protocol>
<vdcId>1</vdcId>
</clock-items>
</System>
Note: This example was added in Release 9.3(5).
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.
no clock protocol none
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 |
---|---|
topSystem | sys |
datetimeClock | sys/clock |
datetimeClock Properties
The following table contains information about the datetimeClock 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 | Values |
---|---|---|---|
protocol | datetime:ClockProtocol (scalar:Enum8) | Protocol Type | SELECTION: 0 - unspecified 1 - ptp 2 - ntp 3 - none DEFAULT: ntp |
vdcId | datetime:VdcId (scalar:Uint16) | Vdc | RANGE: [0, 65535] DEFAULT: 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:
Configuring the Clock Protocol to NTP
Configuring the Clock Protocol to NTP
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"datetimeClock": {
"attributes": {
"protocol": "ntp",
"vdcId": "1"
}}}]}}
{
imdata:[]
}
<System>
<clock-items>
<protocol>ntp</protocol>
<vdcId>1</vdcId>
</clock-items>
</System>
Note: This example was added in Release 9.3(5).
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.
clock protocol ntp
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 |
---|---|
topSystem | sys |
datetimeClock | sys/clock |
datetimeClock Properties
The following table contains information about the datetimeClock 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 | Values |
---|---|---|---|
protocol | datetime:ClockProtocol (scalar:Enum8) | Protocol Type | SELECTION: 0 - unspecified 1 - ptp 2 - ntp 3 - none DEFAULT: ntp |
vdcId | datetime:VdcId (scalar:Uint16) | Vdc | RANGE: [0, 65535] DEFAULT: 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:
Deleting the Clock Protocol to NTP
Deleting the Clock Protocol to NTP
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"datetimeClock": {
"attributes": {
"protocol": "unspecified",
"vdcId": "1"
}}}]}}
{
imdata:[]
}
<System>
<clock-items>
<protocol>unspecified</protocol>
<vdcId>1</vdcId>
</clock-items>
</System>
Note: This example was added in Release 9.3(5).
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.
no clock protocol ntp
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 |
---|---|
topSystem | sys |
datetimeClock | sys/clock |
datetimeClock Properties
The following table contains information about the datetimeClock 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 | Values |
---|---|---|---|
protocol | datetime:ClockProtocol (scalar:Enum8) | Protocol Type | SELECTION: 0 - unspecified 1 - ptp 2 - ntp 3 - none DEFAULT: ntp |
vdcId | datetime:VdcId (scalar:Uint16) | Vdc | RANGE: [0, 65535] DEFAULT: 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:
Configuring the Clock Protocol to PTP
Configuring the Clock Protocol to PTP
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"datetimeClock": {
"attributes": {
"protocol": "ptp",
"vdcId": "1"
}}}]}}
{
imdata:[]
}
<System>
<clock-items>
<protocol>ptp</protocol>
<vdcId>1</vdcId>
</clock-items>
</System>
Note: This example was added in Release 9.3(5).
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.
clock protocol ptp
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 |
---|---|
topSystem | sys |
datetimeClock | sys/clock |
datetimeClock Properties
The following table contains information about the datetimeClock 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 | Values |
---|---|---|---|
protocol | datetime:ClockProtocol (scalar:Enum8) | Protocol Type | SELECTION: 0 - unspecified 1 - ptp 2 - ntp 3 - none DEFAULT: ntp |
vdcId | datetime:VdcId (scalar:Uint16) | Vdc | RANGE: [0, 65535] DEFAULT: 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:
Deleting the Clock Protocol to PTP
Deleting the Clock Protocol to PTP
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"datetimeClock": {
"attributes": {
"protocol": "unspecified",
"vdcId": "1"
}}}]}}
{
imdata:[]
}
<System>
<clock-items>
<protocol>unspecified</protocol>
<vdcId>1</vdcId>
</clock-items>
</System>
Note: This example was added in Release 9.3(5).
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.
no clock protocol ptp
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 |
---|---|
topSystem | sys |
datetimeClock | sys/clock |
datetimeClock Properties
The following table contains information about the datetimeClock 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 | Values |
---|---|---|---|
protocol | datetime:ClockProtocol (scalar:Enum8) | Protocol Type | SELECTION: 0 - unspecified 1 - ptp 2 - ntp 3 - none DEFAULT: ntp |
vdcId | datetime:VdcId (scalar:Uint16) | Vdc | RANGE: [0, 65535] DEFAULT: 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:
Configuring the PTP Clock Operation
Configuring the PTP Clock Operation
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"clockOperationOneStep": "enabled"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<clockOperationOneStep>enabled</clockOperationOneStep>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ptp clock-operation one-step
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
clockOperationOneStep | ptp:AdminSt (scalar:Enum8) | PTP Clock Operation One Step PTP enable/disable | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
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:
Deleting the PTP Clock Operation
Deleting the PTP Clock Operation
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"clockOperationOneStep": "disabled"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<clockOperationOneStep>disabled</clockOperationOneStep>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
no ptp clock-operation one-step
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
clockOperationOneStep | ptp:AdminSt (scalar:Enum8) | PTP Clock Operation One Step PTP enable/disable | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
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:
Configuring the Correction Range Threshold Value
Configuring the Correction Range Threshold Value
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"correctionRangeThreshold": "13048003"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<correctionRangeThreshold>13048003</correctionRangeThreshold>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ptp correction-range 13048003
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
correctionRangeThreshold | scalar:Uint32 | PTP correction range threshold | RANGE: [10 , 1000000000] DEFAULT: 100000 |
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:
Deleting the Correction Range Threshold Value
Deleting the Correction Range Threshold Value
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"correctionRangeThreshold": "100000"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<correctionRangeThreshold>100000</correctionRangeThreshold>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
no ptp correction-range 13048003
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
correctionRangeThreshold | scalar:Uint32 | PTP correction range threshold | RANGE: [10 , 1000000000] DEFAULT: 100000 |
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:
Configuring Logging for Corrections Exceeding Threshold Value
Configuring Logging for Corrections Exceeding Threshold Value
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"correctionRangeLogging": "enabled"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<correctionRangeLogging>enabled</correctionRangeLogging>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ptp correction-range logging
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
correctionRangeLogging | ptp:AdminSt (scalar:Enum8) | PTP correction range logging enable/disable | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
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:
Deleting Logging for Corrections Exceeding Threshold Value
Deleting Logging for Corrections Exceeding Threshold Value
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"correctionRangeLogging": "disabled"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<correctionRangeLogging>disabled</correctionRangeLogging>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
no ptp correction-range logging
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
correctionRangeLogging | ptp:AdminSt (scalar:Enum8) | PTP correction range logging enable/disable | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
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:
Configuring Boundary Clock
Configuring Boundary Clock
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"deviceTypeBoundaryClock": "enabled"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<deviceTypeBoundaryClock>enabled</deviceTypeBoundaryClock>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ptp device-type boundary-clock
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
deviceTypeBoundaryClock | ptp:AdminSt (scalar:Enum8) | PTP Device Type Bounday Clock enable/disable | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
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:
Deleting Boundary Clock
Deleting Boundary Clock
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"deviceTypeBoundaryClock": "enabled"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<deviceTypeBoundaryClock>enabled</deviceTypeBoundaryClock>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
no ptp device-type boundary-clock
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
deviceTypeBoundaryClock | ptp:AdminSt (scalar:Enum8) | PTP Device Type Bounday Clock enable/disable | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
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:
Configuring Generalized PTP
Configuring Generalized PTP
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"deviceTypeGeneralizedPtp": "enabled"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<deviceTypeGeneralizedPtp>enabled</deviceTypeGeneralizedPtp>
</ptp-items>
</System>
Note:
- This is only supported on Cisco Nexus 9508 switches with an -R series line card
- This example was added in Release 9.3(5).
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.
ptp device-type generalized-ptp
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
deviceTypeGeneralizedPtp | ptp:AdminSt (scalar:Enum8) | PTP Device Type Generalized PTP enable/disable | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
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:
Deleting Generalized PTP
Deleting Generalized PTP
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"deviceTypeGeneralizedPtp": "disabled"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<deviceTypeGeneralizedPtp>disabled</deviceTypeGeneralizedPtp>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
no ptp device-type generalized-ptp
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
deviceTypeGeneralizedPtp | ptp:AdminSt (scalar:Enum8) | PTP Device Type Generalized PTP enable/disable | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
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:
Configuring PTP Clock Domain
Configuring PTP Clock Domain
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"domainNum": "1"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<domainNum>1</domainNum>
</ptp-items>
</System>
Note:
- Supported on N3K-C3548P-XL platform
- This example was added in Release 9.3(5).
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.
ptp domain 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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
domainNum | scalar:Uint32 | PTP Clock Domain number to use for this clock | RANGE: [0 , 127] DEFAULT: 0 |
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:
Deleting PTP Clock Domain
Deleting PTP Clock Domain
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"domainNum": "0"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<domainNum>0</domainNum>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
no ptp domain 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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
domainNum | scalar:Uint32 | PTP Clock Domain number to use for this clock | RANGE: [0 , 127] DEFAULT: 0 |
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:
Configuring Mean-Path-Delay Threshold Value
Configuring Mean-Path-Delay Threshold Value
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"meanPathDelay": "773091611"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<meanPathDelay>773091611</meanPathDelay>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ptp mean-path-delay 773091611
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
meanPathDelay | scalar:Uint32 | PTP Mean Path Delay | RANGE: [10 , 1000000000] DEFAULT: 1000000000 |
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:
Deleting Mean-Path-Delay Threshold Value
Deleting Mean-Path-Delay Threshold Value
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"meanPathDelay": "1000000000"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<meanPathDelay>1000000000</meanPathDelay>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
no ptp mean-path-delay 773091611
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
meanPathDelay | scalar:Uint32 | PTP Mean Path Delay | RANGE: [10 , 1000000000] DEFAULT: 1000000000 |
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:
Configuring Mean Peer Delay Request Interval Logging
Configuring Mean Peer Delay Request Interval Logging
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"peerDelayReqInterval": "1"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<peerDelayReqInterval>1</peerDelayReqInterval>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ptp pdelay-req-interval 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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
peerDelayReqInterval | scalar:Uint32 | PTP peer delay request interval | RANGE: [0 , 5] DEFAULT: 0 |
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:
Deleting Mean Peer Delay Request Interval Logging
Deleting Mean Peer Delay Request Interval Logging
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"peerDelayReqInterval": "0"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<peerDelayReqInterval>0</peerDelayReqInterval>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
no ptp pdelay-req-interval 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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
peerDelayReqInterval | scalar:Uint32 | PTP peer delay request interval | RANGE: [0 , 5] DEFAULT: 0 |
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:
Configuring PTP Priority1
Configuring PTP Priority1
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"priority1": "1"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<priority1>1</priority1>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ptp priority1 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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
priority1 | ptp:Priority (scalar:Uint32) | PTP priority1 value to use when advertising the clock | RANGE: [0 , 255] DEFAULT: 255 |
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:
Deleting PTP Priority1
Deleting PTP Priority1
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"priority1": "255"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<priority1>255</priority1>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
no ptp priority1 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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
priority1 | ptp:Priority (scalar:Uint32) | PTP priority1 value to use when advertising the clock | RANGE: [0 , 255] DEFAULT: 255 |
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:
Configuring PTP Priority2
Configuring PTP Priority2
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"priority2": "1"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<priority2>1</priority2>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ptp priority2 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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
priority2 | ptp:Priority (scalar:Uint32) | PTP priority2 value to use when advertising the clock | RANGE: [0 , 255] DEFAULT: 255 |
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:
Deleting PTP Priority2
Deleting PTP Priority2
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"priority2": "255"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<priority2>255</priority2>
</ptp-items>
</System>
Note: This example was added in Release 9.3(5).
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.
no ptp priority2 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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
priority2 | ptp:Priority (scalar:Uint32) | PTP priority2 value to use when advertising the clock | RANGE: [0 , 255] DEFAULT: 255 |
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:
Configuring the Source IP Address
Configuring the Source IP Address
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"sourceIp": "1.2.3.4"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<sourceIp>1.2.3.4</sourceIp>
</ptp-items>
</System>
Note:
- This configuration is required before enabling PTP on interfaces.
- This example was added in Release 9.3(5).
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.
ptp source 1.2.3.4
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
sourceIp | address:Ip | PTP source IP address for all the PTP packets in the multicast PTP mode | Value must match ipv4 |
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:
Deleting the Source IP Address
Deleting the Source IP Address
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"attributes": {
"sourceIp": "0.0.0.0"
}}}]}}
{
imdata:[]
}
<System>
<ptp-items>
<sourceIp>0.0.0.0</sourceIp>
</ptp-items>
</System>
Note:
- This configuration can only be deleted when there are no PTP-enabled interfaces.
- This example was added in Release 9.3(5).
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.
no ptp source 1.2.3.4
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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpEntity Properties
The following table contains information about the ptpPtpEntity 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 | Values |
---|---|---|---|
sourceIp | address:Ip | PTP source IP address for all the PTP packets in the multicast PTP mode | Value must match ipv4 |
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:
Configuring a Marker Packet Interval
Configuring a Marker Packet Interval
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ttagTtagEntity": {
"attributes": {
"ttagMarkerInterval": "100"
}}}]}}
{
imdata:[]
}
<System>
<ttag-items>
<ttagMarkerInterval>100</ttagMarkerInterval>
</ttag-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ttag-marker-interval 100
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 |
---|---|
topSystem | sys |
ttagTtagEntity | sys/ttag |
ttagTtagEntity Properties
The following table contains information about the ttagTtagEntity 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 | Values |
---|---|---|---|
ttagMarkerInterval | scalar:Uint32 | PTP ttag marker interval in seconds | RANGE: [1 , 25200] DEFAULT: 60 |
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:
Deleting a Marker Packet Interval
Deleting a Marker Packet Interval
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ttagTtagEntity": {
"attributes": {
"ttagMarkerInterval": "60"
}}}]}}
{
imdata:[]
}
<System>
<ttag-items>
<ttagMarkerInterval>60</ttagMarkerInterval>
</ttag-items>
</System>
Note: This example was added in Release 9.3(5).
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.
no ttag-marker-interval 100
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 |
---|---|
topSystem | sys |
ttagTtagEntity | sys/ttag |
ttagTtagEntity Properties
The following table contains information about the ttagTtagEntity 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 | Values |
---|---|---|---|
ttagMarkerInterval | scalar:Uint32 | PTP ttag marker interval in seconds | RANGE: [1 , 25200] DEFAULT: 60 |
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:
Configuring the Ether Header Ether Type For TTAG
Configuring the Ether Header Ether Type For TTAG
POST http://<mgmt0_IP>/api/mo/sys/clock.json
{
"datetimeClock": {
"children": [
{
"datetimeTTag": {
"attributes": {
"ethtype": "35000"
}}}]}}
{
imdata:[]
}
<System>
<clock-items>
<ttag-items>
<ethtype>35000</ethtype>
</ttag-items>
</clock-items>
</System>
Note:
- Supported on N3K-C3548P-XL platform
- This example was added in Release 9.3(5).
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.
hardware internal mtc-usd ttag-eth-type 35000
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 |
---|---|
datetimeClock | sys/clock |
datetimeTTag | sys/clock/ttag |
datetimeTTag Properties
The following table contains information about the datetimeTTag 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 | Values |
---|---|---|---|
ethtype | scalar:Uint32 | Ethernet header type | RANGE: [0 , 35077] DEFAULT: 0 |
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:
Disabling the Ether Header Ether Type For TTAG
Disabling the Ether Header Ether Type For TTAG
POST http://<mgmt0_IP>/api/mo/sys/clock.json
{
"datetimeClock": {
"children": [
{
"datetimeTTag": {
"attributes": {
"ethtype": "0"
}}}]}}
{
imdata:[]
}
<System>
<clock-items>
<ttag-items>
<ethtype>0</ethtype>
</ttag-items>
</clock-items>
</System>
Note:
- Supported on N3K-C3548P-XL platform
- This example was added in Release 9.3(5).
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.
hardware internal mtc-usd ttag-eth-type 35000
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 |
---|---|
datetimeClock | sys/clock |
datetimeTTag | sys/clock/ttag |
datetimeTTag Properties
The following table contains information about the datetimeTTag 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 | Values |
---|---|---|---|
ethtype | scalar:Uint32 | Ethernet header type | RANGE: [0 , 35077] DEFAULT: 0 |
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: