Configuring PTP on an Interface
Enabling PTP on an Interface
Enabling PTP on an Interface
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"id": "eth1/3",
"ptp": "yes"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<ptp>true</ptp>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-items>
</System>
Note:
- This configuration is required before you apply any other PTP config on an interface.
- 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.
interface ethernet 1/3
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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
ptp | scalar:Bool | PTP enable or disable at interface level | SELECTION: true or false DEFAULT: false |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 PTP on an Interface
Disabling PTP on an Interface
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"id": "eth1/3",
"ptp": "no"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<ptp>false</ptp>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-items>
</System>
Note:
- Deleting this configuration will remove all other PTP configurations on the inteface.
- 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.
interface ethernet 1/3
no 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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
ptp | scalar:Bool | PTP enable or disable at interface level | SELECTION: true or false DEFAULT: false |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 PTP Clock Domain
Configuring a PTP Clock Domain
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"id": "eth1/3",
"ptpInterfaceDomain": "1"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<ptpInterfaceDomain>1</ptpInterfaceDomain>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
ptpInterfaceDomain | scalar:Uint16 | PTP domain value in interface | RANGE: [0 , 127] DEFAULT: 0 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 PTP Clock Domain
Deleting a PTP Clock Domain
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"id": "eth1/3",
"ptpInterfaceDomain": "0"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<ptpInterfaceDomain>0</ptpInterfaceDomain>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
ptpInterfaceDomain | scalar:Uint16 | PTP domain value in interface | RANGE: [0 , 127] DEFAULT: 0 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Cost Associated With the Interface
Configuring the Cost Associated With the Interface
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"id": "eth1/3",
"ptpCost": "1"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<ptpCost>1</ptpCost>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-items>
</System>
Note:
- Supported on N3K-C3548P-XL and N9K-C93180YC-FX3S platforms with PTP telecom profile 8275.1.
- 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.
interface ethernet 1/3
ptp cost 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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
ptpCost | scalar:Uint16 | PTP cost value in interface | RANGE: [0 , 255] DEFAULT: 255 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Cost Associated With the Interface
Deleting the Cost Associated With the Interface
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"id": "eth1/3",
"ptpCost": "128"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<ptpCost>128</ptpCost>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-items>
</System>
Note:
- Supported on N3K-C3548P-XL and N9K-C93180YC-FX3S platforms with PTP telecom profile 8275.1.
- 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.
interface ethernet 1/3
no ptp cost 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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
ptpCost | scalar:Uint16 | PTP cost value in interface | RANGE: [0 , 255] DEFAULT: 255 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Multicast Transmission
Configuring PTP Multicast Transmission
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"id": "eth1/3",
"transmission": "multicast"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<transmission>multicast</transmission>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
ptp transmission multicast
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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
transmission | ptp:TransportMode (scalar:Enum8) | Transport mode for PTP interface with default multicast | SELECTION: 1 - multicast 2 - unicast DEFAULT: multicast |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Unicast Transmission
Configuring PTP Unicast Transmission
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"id": "eth1/3",
"transmission": "unicast"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<transmission>unicast</transmission>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
ptp transmission unicast
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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
transmission | ptp:TransportMode (scalar:Enum8) | Transport mode for PTP interface with default multicast | SELECTION: 1 - multicast 2 - unicast DEFAULT: multicast |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Marker Packet on an Interface
Configuring the Marker Packet on an Interface
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ttagTtagEntity": {
"children": [
{
"ttagTtagIf": {
"attributes": {
"id": "eth1/3",
"ttagMarker": "yes"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ttag-items>
<if-items>
<TtagIf-list>
<id>eth1/3</id>
<ttagMarker>true</ttagMarker>
</TtagIf-list>
</if-items>
</ttag-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
ttag-marker enable
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 |
ttagTtagIf | sys/ttag/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ttagTtagIf Properties
The following table contains information about the ttagTtagIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
ttagMarker | scalar:Bool | ttag marker packet on interface | SELECTION: true or false DEFAULT: false |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Marker Packet on an Interface
Deleting the Marker Packet on an Interface
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ttagTtagEntity": {
"children": [
{
"ttagTtagIf": {
"attributes": {
"id": "eth1/3",
"ttagMarker": "no"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ttag-items>
<if-items>
<TtagIf-list>
<id>eth1/3</id>
<ttagMarker>false</ttagMarker>
</TtagIf-list>
</if-items>
</ttag-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
no ttag-marker enable
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 |
ttagTtagIf | sys/ttag/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ttagTtagIf Properties
The following table contains information about the ttagTtagIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
ttagMarker | scalar:Bool | ttag marker packet on interface | SELECTION: true or false DEFAULT: false |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Sync Interval
Configuring the PTP Sync Interval
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"id": "eth1/3",
"syncIntervalType": "none",
"syncIntervalVal": "-3"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<syncIntervalType>none</syncIntervalType>
<syncIntervalVal>-3</syncIntervalVal>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
ptp sync 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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
syncIntervalType | ptp:TimeCode (scalar:Enum8) | PTP sync interval time code | SELECTION: 1 - none 2 - aes67 3 - smpte-2059-2 DEFAULT: none |
syncIntervalVal | scalar:Sint16 | PTP sync interval value | RANGE: -3 to 1 when type is none -4 to 1 when type is aes67 -7 to 0 when type is smpte-2059-2 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Sync Interval
Deleting the PTP Sync Interval
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"id": "eth1/3",
"syncIntervalType": "none",
"syncIntervalVal": "0"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<syncIntervalType>none</syncIntervalType>
<syncIntervalVal>0</syncIntervalVal>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
no ptp sync 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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
syncIntervalType | ptp:TimeCode (scalar:Enum8) | PTP sync interval time code | SELECTION: 1 - none 2 - aes67 3 - smpte-2059-2 DEFAULT: none |
syncIntervalVal | scalar:Sint16 | PTP sync interval value | RANGE: -3 to 1 when type is none -4 to 1 when type is aes67 -7 to 0 when type is smpte-2059-2 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Sync Interval as AES67-2015
Configuring the PTP Sync Interval as AES67-2015
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"id": "eth1/3",
"syncIntervalType": "aes67",
"syncIntervalVal": "-4"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<syncIntervalType>aes67</syncIntervalType>
<syncIntervalVal>-4</syncIntervalVal>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
ptp sync interval aes67 -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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
syncIntervalType | ptp:TimeCode (scalar:Enum8) | PTP sync interval time code | SELECTION: 1 - none 2 - aes67 3 - smpte-2059-2 DEFAULT: none |
syncIntervalVal | scalar:Sint16 | PTP sync interval value | RANGE: -3 to 1 when type is none -4 to 1 when type is aes67 -7 to 0 when type is smpte-2059-2 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Sync Interval as AES67-2015
Deleting the PTP Sync Interval as AES67-2015
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"id": "eth1/3",
"syncIntervalType": "none",
"syncIntervalVal": "-3"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<syncIntervalType>none</syncIntervalType>
<syncIntervalVal>-3</syncIntervalVal>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
no ptp sync interval aes67 -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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
syncIntervalType | ptp:TimeCode (scalar:Enum8) | PTP sync interval time code | SELECTION: 1 - none 2 - aes67 3 - smpte-2059-2 DEFAULT: none |
syncIntervalVal | scalar:Sint16 | PTP sync interval value | RANGE: -3 to 1 when type is none -4 to 1 when type is aes67 -7 to 0 when type is smpte-2059-2 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Sync Interval as SMPTE-2059-2
Configuring the PTP Sync Interval as SMPTE-2059-2
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"id": "eth1/3",
"syncIntervalType": "smpte-2059-2",
"syncIntervalVal": "0"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<syncIntervalType>smpte-2059-2</syncIntervalType>
<syncIntervalVal>0</syncIntervalVal>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
ptp sync interval smpte-2059-2 0
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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
syncIntervalType | ptp:TimeCode (scalar:Enum8) | PTP sync interval time code | SELECTION: 1 - none 2 - aes67 3 - smpte-2059-2 DEFAULT: none |
syncIntervalVal | scalar:Sint16 | PTP sync interval value | RANGE: -3 to 1 when type is none -4 to 1 when type is aes67 -7 to 0 when type is smpte-2059-2 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Sync Interval as SMPTE-2059-2
Deleting the PTP Sync Interval as SMPTE-2059-2
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"id": "eth1/3",
"syncIntervalType": "none",
"syncIntervalVal": "0"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<syncIntervalType>none</syncIntervalType>
<syncIntervalVal>0</syncIntervalVal>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
no ptp sync interval smpte-2059-2 0
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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
syncIntervalType | ptp:TimeCode (scalar:Enum8) | PTP sync interval time code | SELECTION: 1 - none 2 - aes67 3 - smpte-2059-2 DEFAULT: none |
syncIntervalVal | scalar:Sint16 | PTP sync interval value | RANGE: -3 to 1 when type is none -4 to 1 when type is aes67 -7 to 0 when type is smpte-2059-2 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Delay Request Minimum Interval
Configuring the PTP Delay Request Minimum Interval
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"delayRequestMinIntervalType": "none",
"delayRequestMinIntervalVal": "-1",
"id": "eth1/3"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<delayRequestMinIntervalType>none</delayRequestMinIntervalType>
<delayRequestMinIntervalVal>-1</delayRequestMinIntervalVal>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
ptp delay-request minimum 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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
delayRequestMinIntervalType | ptp:TimeCode (scalar:Enum8) | PTP delay-request minimum interval time code | SELECTION: 1 - none 2 - aes67 3 - smpte-2059-2 DEFAULT: none |
delayRequestMinIntervalVal | scalar:Sint16 | PTP delay-request minimum interval value | -1 to 6 when type is none -4 to 5 when type is aes67 -4 to 5 when type is smpte-2059-2 |
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Delay Request Minimum Interval
Deleting the PTP Delay Request Minimum Interval
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"delayRequestMinIntervalType": "none",
"delayRequestMinIntervalVal": "0",
"id": "eth1/3"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<delayRequestMinIntervalType>none</delayRequestMinIntervalType>
<delayRequestMinIntervalVal>0</delayRequestMinIntervalVal>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
no ptp delay-request minimum 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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
delayRequestMinIntervalType | ptp:TimeCode (scalar:Enum8) | PTP delay-request minimum interval time code | SELECTION: 1 - none 2 - aes67 3 - smpte-2059-2 DEFAULT: none |
delayRequestMinIntervalVal | scalar:Sint16 | PTP delay-request minimum interval value | -1 to 6 when type is none -4 to 5 when type is aes67 -4 to 5 when type is smpte-2059-2 |
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Delay Request Minimum Interval as AES67-2015
Configuring the PTP Delay Request Minimum Interval as AES67-2015
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"delayRequestMinIntervalType": "aes67",
"delayRequestMinIntervalVal": "-4",
"id": "eth1/3"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<delayRequestMinIntervalType>aes67</delayRequestMinIntervalType>
<delayRequestMinIntervalVal>-4</delayRequestMinIntervalVal>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
ptp delay-request minimum interval aes67 -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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
delayRequestMinIntervalType | ptp:TimeCode (scalar:Enum8) | PTP delay-request minimum interval time code | SELECTION: 1 - none 2 - aes67 3 - smpte-2059-2 DEFAULT: none |
delayRequestMinIntervalVal | scalar:Sint16 | PTP delay-request minimum interval value | -1 to 6 when type is none -4 to 5 when type is aes67 -4 to 5 when type is smpte-2059-2 |
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Delay Request Minimum Interval as AES67-2015
Deleting the PTP Delay Request Minimum Interval as AES67-2015
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"delayRequestMinIntervalType": "none",
"delayRequestMinIntervalVal": "-1",
"id": "eth1/3"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<delayRequestMinIntervalType>none</delayRequestMinIntervalType>
<delayRequestMinIntervalVal>-1</delayRequestMinIntervalVal>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
no ptp delay-request minimum interval aes67 -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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
delayRequestMinIntervalType | ptp:TimeCode (scalar:Enum8) | PTP delay-request minimum interval time code | SELECTION: 1 - none 2 - aes67 3 - smpte-2059-2 DEFAULT: none |
delayRequestMinIntervalVal | scalar:Sint16 | PTP delay-request minimum interval value | -1 to 6 when type is none -4 to 5 when type is aes67 -4 to 5 when type is smpte-2059-2 |
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Delay Request Minimum Interval as SMPTE-2059-2
Configuring the PTP Delay Request Minimum Interval as SMPTE-2059-2
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"delayRequestMinIntervalType": "smpte-2059-2",
"delayRequestMinIntervalVal": "-4",
"id": "eth1/3"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<delayRequestMinIntervalType>smpte-2059-2</delayRequestMinIntervalType>
<delayRequestMinIntervalVal>-4</delayRequestMinIntervalVal>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
ptp delay-request minimum interval smpte-2059-2 -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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
delayRequestMinIntervalType | ptp:TimeCode (scalar:Enum8) | PTP delay-request minimum interval time code | SELECTION: 1 - none 2 - aes67 3 - smpte-2059-2 DEFAULT: none |
delayRequestMinIntervalVal | scalar:Sint16 | PTP delay-request minimum interval value | -1 to 6 when type is none -4 to 5 when type is aes67 -4 to 5 when type is smpte-2059-2 |
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Delay Request Minimum Interval as SMPTE-2059-2
Deleting the PTP Delay Request Minimum Interval as SMPTE-2059-2
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"delayRequestMinIntervalType": "none",
"delayRequestMinIntervalVal": "0",
"id": "eth1/3"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<delayRequestMinIntervalType>none</delayRequestMinIntervalType>
<delayRequestMinIntervalVal>0</delayRequestMinIntervalVal>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
no ptp delay-request minimum interval smpte-2059-2 -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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
delayRequestMinIntervalType | ptp:TimeCode (scalar:Enum8) | PTP delay-request minimum interval time code | SELECTION: 1 - none 2 - aes67 3 - smpte-2059-2 DEFAULT: none |
delayRequestMinIntervalVal | scalar:Sint16 | PTP delay-request minimum interval value | -1 to 6 when type is none -4 to 5 when type is aes67 -4 to 5 when type is smpte-2059-2 |
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Announce Interval
Configuring PTP Announce Interval
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"announceIntervalType": "none",
"announceIntervalVal": "1",
"id": "eth1/3"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<announceIntervalType>none</announceIntervalType>
<announceIntervalVal>1</announceIntervalVal>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
ptp announce 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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
announceIntervalType | ptp:TimeCode (scalar:Enum8) | PTP announce interval time code | SELECTION: 1 - none 2 - aes67 3 - smpte-2059-2 DEFAULT: none |
announceIntervalVal | scalar:Sint16 | PTP announce interval value | 0 to 4 when type is none 0 to 4 when type is aes67 -3 to 1 when type is smpte-2059-2 DEFAULT: 1 |
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Announce Interval
Deleting PTP Announce Interval
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"announceIntervalType": "none",
"announceIntervalVal": "1",
"id": "eth1/3"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<announceIntervalType>none</announceIntervalType>
<announceIntervalVal>1</announceIntervalVal>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
no ptp announce 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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
announceIntervalType | ptp:TimeCode (scalar:Enum8) | PTP announce interval time code | SELECTION: 1 - none 2 - aes67 3 - smpte-2059-2 DEFAULT: none |
announceIntervalVal | scalar:Sint16 | PTP announce interval value | 0 to 4 when type is none 0 to 4 when type is aes67 -3 to 1 when type is smpte-2059-2 DEFAULT: 1 |
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Announce Interval as AES67
Configuring PTP Announce Interval as AES67
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"announceIntervalType": "aes67",
"announceIntervalVal": "1",
"id": "eth1/3"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<announceIntervalType>aes67</announceIntervalType>
<announceIntervalVal>1</announceIntervalVal>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
ptp announce interval aes67 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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
announceIntervalType | ptp:TimeCode (scalar:Enum8) | PTP announce interval time code | SELECTION: 1 - none 2 - aes67 3 - smpte-2059-2 DEFAULT: none |
announceIntervalVal | scalar:Sint16 | PTP announce interval value | 0 to 4 when type is none 0 to 4 when type is aes67 -3 to 1 when type is smpte-2059-2 DEFAULT: 1 |
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Announce Interval as AES67
Deleting PTP Announce Interval as AES67
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"announceIntervalType": "none",
"announceIntervalVal": "1",
"id": "eth1/3"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<announceIntervalType>none</announceIntervalType>
<announceIntervalVal>1</announceIntervalVal>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
no ptp announce interval aes67 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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
announceIntervalType | ptp:TimeCode (scalar:Enum8) | PTP announce interval time code | SELECTION: 1 - none 2 - aes67 3 - smpte-2059-2 DEFAULT: none |
announceIntervalVal | scalar:Sint16 | PTP announce interval value | 0 to 4 when type is none 0 to 4 when type is aes67 -3 to 1 when type is smpte-2059-2 DEFAULT: 1 |
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Announce Interval as SMPTE-2059-2
Configuring PTP Announce Interval as SMPTE-2059-2
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"announceIntervalType": "smpte-2059-2",
"announceIntervalVal": "-3",
"id": "eth1/3"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<announceIntervalType>smpte-2059-2</announceIntervalType>
<announceIntervalVal>-3</announceIntervalVal>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
ptp announce interval smpte-2059-2 -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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
announceIntervalType | ptp:TimeCode (scalar:Enum8) | PTP announce interval time code | SELECTION: 1 - none 2 - aes67 3 - smpte-2059-2 DEFAULT: none |
announceIntervalVal | scalar:Sint16 | PTP announce interval value | 0 to 4 when type is none 0 to 4 when type is aes67 -3 to 1 when type is smpte-2059-2 DEFAULT: 1 |
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Announce Interval as SMPTE-2059-2
Deleting PTP Announce Interval as SMPTE-2059-2
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"announceIntervalType": "none",
"announceIntervalVal": "1",
"id": "eth1/3"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<announceIntervalType>none</announceIntervalType>
<announceIntervalVal>1</announceIntervalVal>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
no ptp announce interval smpte-2059-2 -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 |
---|---|
topSystem | sys |
ptpPtpEntity | sys/ptp |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
announceIntervalType | ptp:TimeCode (scalar:Enum8) | PTP announce interval time code | SELECTION: 1 - none 2 - aes67 3 - smpte-2059-2 DEFAULT: none |
announceIntervalVal | scalar:Sint16 | PTP announce interval value | 0 to 4 when type is none 0 to 4 when type is aes67 -3 to 1 when type is smpte-2059-2 DEFAULT: 1 |
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Announce Timeout
Deleting the PTP Announce Timeout
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"announceTimeoutType": "none",
"announceTimeoutVal": "3",
"id": "eth1/3"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<announceTimeoutType>none</announceTimeoutType>
<announceTimeoutVal>3</announceTimeoutVal>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
no ptp announce timeout 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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
announceTimeoutType | ptp:TimeCode (scalar:Enum8) | PTP announce timeout time code | SELECTION: 1 - none 2 - aes67 3 - smpte-2059-2 DEFAULT: none |
announceTimeoutVal | scalar:Sint16 | PTP announce timeout value | RANGE: 2 to 4 when type is none (2 to 10 for 3500 platform) 2 to 10 when type is aes67 2 to 10 when type is smpte-2059-2 DEFAULT: 3 |
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Announce Timeout as AES67-2015
Configuring PTP Announce Timeout as AES67-2015
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"announceTimeoutType": "aes67",
"announceTimeoutVal": "6",
"id": "eth1/3"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<announceTimeoutType>aes67</announceTimeoutType>
<announceTimeoutVal>6</announceTimeoutVal>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
ptp announce timeout aes67 6
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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
announceTimeoutType | ptp:TimeCode (scalar:Enum8) | PTP announce timeout time code | SELECTION: 1 - none 2 - aes67 3 - smpte-2059-2 DEFAULT: none |
announceTimeoutVal | scalar:Sint16 | PTP announce timeout value | RANGE: 2 to 4 when type is none (2 to 10 for 3500 platform) 2 to 10 when type is aes67 2 to 10 when type is smpte-2059-2 DEFAULT: 3 |
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Announce Timeout as AES67-2015
Deleting PTP Announce Timeout as AES67-2015
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"announceTimeoutType": "none",
"announceTimeoutVal": "3",
"id": "eth1/3"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<announceTimeoutType>none</announceTimeoutType>
<announceTimeoutVal>3</announceTimeoutVal>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
no ptp announce timeout aes67 6
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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
announceTimeoutType | ptp:TimeCode (scalar:Enum8) | PTP announce timeout time code | SELECTION: 1 - none 2 - aes67 3 - smpte-2059-2 DEFAULT: none |
announceTimeoutVal | scalar:Sint16 | PTP announce timeout value | RANGE: 2 to 4 when type is none (2 to 10 for 3500 platform) 2 to 10 when type is aes67 2 to 10 when type is smpte-2059-2 DEFAULT: 3 |
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Announce Timeout as SMPTE-2059-2
Configuring PTP Announce Timeout as SMPTE-2059-2
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"announceTimeoutType": "smpte-2059-2",
"announceTimeoutVal": "6",
"id": "eth1/3"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<announceTimeoutType>smpte-2059-2</announceTimeoutType>
<announceTimeoutVal>6</announceTimeoutVal>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
ptp announce timeout smpte-2059-2 6
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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
announceTimeoutType | ptp:TimeCode (scalar:Enum8) | PTP announce timeout time code | SELECTION: 1 - none 2 - aes67 3 - smpte-2059-2 DEFAULT: none |
announceTimeoutVal | scalar:Sint16 | PTP announce timeout value | RANGE: 2 to 4 when type is none (2 to 10 for 3500 platform) 2 to 10 when type is aes67 2 to 10 when type is smpte-2059-2 DEFAULT: 3 |
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Announce Timeout as SMPTE-2059-2
Deleting PTP Announce Timeout as SMPTE-2059-2
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"announceTimeoutType": "none",
"announceTimeoutVal": "3",
"id": "eth1/3"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<announceTimeoutType>none</announceTimeoutType>
<announceTimeoutVal>3</announceTimeoutVal>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
no ptp announce timeout smpte-2059-2 6
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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
announceTimeoutType | ptp:TimeCode (scalar:Enum8) | PTP announce timeout time code | SELECTION: 1 - none 2 - aes67 3 - smpte-2059-2 DEFAULT: none |
announceTimeoutVal | scalar:Sint16 | PTP announce timeout value | RANGE: 2 to 4 when type is none (2 to 10 for 3500 platform) 2 to 10 when type is aes67 2 to 10 when type is smpte-2059-2 DEFAULT: 3 |
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 IPv4 Transport
Configuring PTP IPv4 Transport
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"id": "eth1/3",
"transport": "ipv4"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<transport>ipv4</transport>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
ptp transport ipv4
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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
transport | ptp:TransportType (scalar:Enum8) | Transport type for PTP interface with default IPv4 | SELECTION: 1 - ipv4 2 - eth DEFAULT: ipv4 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 IPv4 Transport
Deleting PTP IPv4 Transport
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"id": "eth1/3",
"transport": "ipv4"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<transport>ipv4</transport>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
no ptp transport ipv4
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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
transport | ptp:TransportType (scalar:Enum8) | Transport type for PTP interface with default IPv4 | SELECTION: 1 - ipv4 2 - eth DEFAULT: ipv4 |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Dynamic PTP Role
Configuring a Dynamic PTP Role
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"id": "eth1/3",
"role": "dynamic"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<role>dynamic</role>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
ptp role dynamic
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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
role | ptp:TransmissionRole (scalar:Enum8) | Transport role for PTP interface with default master | SELECTION: 1 - master 2 - slave 3 - dynamic DEFAULT: dynamic |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Master-Only Role
Configuring a Master-Only Role
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"id": "eth1/3",
"role": "master"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<role>master</role>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
ptp role master
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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
role | ptp:TransmissionRole (scalar:Enum8) | Transport role for PTP interface with default master | SELECTION: 1 - master 2 - slave 3 - dynamic DEFAULT: dynamic |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Slave-Only Role
Configuring a Slave-Only Role
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ptpPtpEntity": {
"children": [
{
"ptpPtpIf": {
"attributes": {
"id": "eth1/3",
"role": "slave"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<ptp-items>
<if-items>
<PtpIf-list>
<id>eth1/3</id>
<role>slave</role>
</PtpIf-list>
</if-items>
</ptp-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/3</id>
</PhysIf-list>
</phys-items>
</intf-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.
interface ethernet 1/3
ptp role slave
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 |
ptpPtpIf | sys/ptp/if-[eth1/3] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/3] |
ptpPtpIf Properties
The following table contains information about the ptpPtpIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | Interface id of port with PTP configuration | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
role | ptp:TransmissionRole (scalar:Enum8) | Transport role for PTP interface with default master | SELECTION: 1 - master 2 - slave 3 - dynamic DEFAULT: dynamic |
l1PhysIf Properties
The following table contains information about the l1PhysIf 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 |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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: