Configuring an Interface
Configuring Override of Some PTP Profile Parameters on an Interface
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 profile-override
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 |
profileOverride | scalar:Bool
| Allow override of configuration limits imposed by global PTP profile | 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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting Override of Some PTP Profile Parameters on an Interface
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 profile-override
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 |
profileOverride | scalar:Bool
| Allow override of configuration limits imposed by global PTP profile | 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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Packet Acceptance and Response Based on Config (Non-Forwardable)
This example is only supported on the N9K-C93180YC-FX3S platform and will take effect when the ethernet transport is configured on an interface.
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 destination-mac non-forwardable rx-no-match accept
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 |
ptpDestinationMac | ptp:PtpDestinationMac (scalar:Enum8) | PTP destination mac forwardable or non-forwardable | SELECTION: 0 - non-forwardable 1 - forwardable DEFAULT: non-forwardable |
ptpRxNoMatch | ptp:PtpRxNoMatch (scalar:Enum8) | PTP packets destination MAC with RX packet not matching | SELECTION: 0 - accept 1 - drop 2 - follow-rx DEFAULT: accept |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting Packet Acceptance and Response Based on Config (Non-Forwardable)
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 destination-mac non-forwardable rx-no-match accept
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 |
ptpDestinationMac | ptp:PtpDestinationMac (scalar:Enum8) | PTP destination mac forwardable or non-forwardable | SELECTION: 0 - non-forwardable 1 - forwardable DEFAULT: non-forwardable |
ptpRxNoMatch | ptp:PtpRxNoMatch (scalar:Enum8) | PTP packets destination MAC with RX packet not matching | SELECTION: 0 - accept 1 - drop 2 - follow-rx DEFAULT: accept |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Drop Packet and No Response (Non-Forwardable)
This example is only supported on the N9K-C93180YC-FX3S platform and will take effect when the ethernet transport is configured on an interface.
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 destination-mac non-forwardable rx-no-match drop
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 |
ptpDestinationMac | ptp:PtpDestinationMac (scalar:Enum8) | PTP destination mac forwardable or non-forwardable | SELECTION: 0 - non-forwardable 1 - forwardable DEFAULT: non-forwardable |
ptpRxNoMatch | ptp:PtpRxNoMatch (scalar:Enum8) | PTP packets destination MAC with RX packet not matching | SELECTION: 0 - accept 1 - drop 2 - follow-rx DEFAULT: accept |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting Drop Packet and No Response (Non-Forwardable)
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 destination-mac non-forwardable rx-no-match drop
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 |
ptpDestinationMac | ptp:PtpDestinationMac (scalar:Enum8) | PTP destination mac forwardable or non-forwardable | SELECTION: 0 - non-forwardable 1 - forwardable DEFAULT: non-forwardable |
ptpRxNoMatch | ptp:PtpRxNoMatch (scalar:Enum8) | PTP packets destination MAC with RX packet not matching | SELECTION: 0 - accept 1 - drop 2 - follow-rx DEFAULT: accept |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Packet Acceptance and Response Based on Received Packet (Non-Forwardable)
This example is only supported on the N9K-C93180YC-FX3S platform and will take effect when the ethernet transport is configured on an interface.
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 destination-mac non-forwardable rx-no-match follow-rx
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 |
ptpDestinationMac | ptp:PtpDestinationMac (scalar:Enum8) | PTP destination mac forwardable or non-forwardable | SELECTION: 0 - non-forwardable 1 - forwardable DEFAULT: non-forwardable |
ptpRxNoMatch | ptp:PtpRxNoMatch (scalar:Enum8) | PTP packets destination MAC with RX packet not matching | SELECTION: 0 - accept 1 - drop 2 - follow-rx DEFAULT: accept |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting Packet Acceptance and Response Based on Received Packet (Non-Forwardable)
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 destination-mac non-forwardable rx-no-match follow-rx
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 |
ptpDestinationMac | ptp:PtpDestinationMac (scalar:Enum8) | PTP destination mac forwardable or non-forwardable | SELECTION: 0 - non-forwardable 1 - forwardable DEFAULT: non-forwardable |
ptpRxNoMatch | ptp:PtpRxNoMatch (scalar:Enum8) | PTP packets destination MAC with RX packet not matching | SELECTION: 0 - accept 1 - drop 2 - follow-rx DEFAULT: accept |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Packet Acceptance and Response Based on Config (Forwardable)
This example is only supported on the N9K-C93180YC-FX3S platform and will take effect when the ethernet transport is configured on an interface.
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 destination-mac forwardable rx-no-match accept
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 |
ptpDestinationMac | ptp:PtpDestinationMac (scalar:Enum8) | PTP destination mac forwardable or non-forwardable | SELECTION: 0 - non-forwardable 1 - forwardable DEFAULT: non-forwardable |
ptpRxNoMatch | ptp:PtpRxNoMatch (scalar:Enum8) | PTP packets destination MAC with RX packet not matching | SELECTION: 0 - accept 1 - drop 2 - follow-rx DEFAULT: accept |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting Packet Acceptance and Response Based on Config (Forwardable)
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 destination-mac forwardable rx-no-match accept
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 |
ptpDestinationMac | ptp:PtpDestinationMac (scalar:Enum8) | PTP destination mac forwardable or non-forwardable | SELECTION: 0 - non-forwardable 1 - forwardable DEFAULT: non-forwardable |
ptpRxNoMatch | ptp:PtpRxNoMatch (scalar:Enum8) | PTP packets destination MAC with RX packet not matching | SELECTION: 0 - accept 1 - drop 2 - follow-rx DEFAULT: accept |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Drop Packet and No Response (Forwardable)
This example is only supported on the N9K-C93180YC-FX3S platform and will take effect when the ethernet transport is configured on an interface.
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 destination-mac forwardable rx-no-match drop
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 |
ptpDestinationMac | ptp:PtpDestinationMac (scalar:Enum8) | PTP destination mac forwardable or non-forwardable | SELECTION: 0 - non-forwardable 1 - forwardable DEFAULT: non-forwardable |
ptpRxNoMatch | ptp:PtpRxNoMatch (scalar:Enum8) | PTP packets destination MAC with RX packet not matching | SELECTION: 0 - accept 1 - drop 2 - follow-rx DEFAULT: accept |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting Drop Packet and No Response (Forwardable)
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 destination-mac forwardable rx-no-match drop
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 |
ptpDestinationMac | ptp:PtpDestinationMac (scalar:Enum8) | PTP destination mac forwardable or non-forwardable | SELECTION: 0 - non-forwardable 1 - forwardable DEFAULT: non-forwardable |
ptpRxNoMatch | ptp:PtpRxNoMatch (scalar:Enum8) | PTP packets destination MAC with RX packet not matching | SELECTION: 0 - accept 1 - drop 2 - follow-rx DEFAULT: accept |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Packet Acceptance and Response Based on Received Packet (Forwardable)
This example is only supported on the N9K-C93180YC-FX3S platform and will take effect when the ethernet transport is configured on an interface.
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 destination-mac forwardable rx-no-match follow-rx
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 |
ptpDestinationMac | ptp:PtpDestinationMac (scalar:Enum8) | PTP destination mac forwardable or non-forwardable | SELECTION: 0 - non-forwardable 1 - forwardable DEFAULT: non-forwardable |
ptpRxNoMatch | ptp:PtpRxNoMatch (scalar:Enum8) | PTP packets destination MAC with RX packet not matching | SELECTION: 0 - accept 1 - drop 2 - follow-rx DEFAULT: accept |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting Packet Acceptance and Response Based on Received Packet (Forwardable)
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 destination-mac forwardable rx-no-match follow-rx
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 |
ptpDestinationMac | ptp:PtpDestinationMac (scalar:Enum8) | PTP destination mac forwardable or non-forwardable | SELECTION: 0 - non-forwardable 1 - forwardable DEFAULT: non-forwardable |
ptpRxNoMatch | ptp:PtpRxNoMatch (scalar:Enum8) | PTP packets destination MAC with RX packet not matching | SELECTION: 0 - accept 1 - drop 2 - follow-rx DEFAULT: accept |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring PTP Ethernet Transport
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 ethernet
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting PTP Ethernet Transport
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 ethernet
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring the Cost Associated With the Interface
Note: The default value is 128
when an 8275-1
profile is configured.
For an example payload, see [Configuring the Cost Associated With the Interface](Configuring the Cost Associated With the Interface).
Configuring a PTP Role
Note: You cannot change the default value of dynamic
when an 8275-1
profile is configured.
For an example payload, see [Configuring a Dynamic PTP Role](Configuring a Dynamic PTP Role).
Configuring PTP Transmission
Note: You cannot change the default value of multicast
when an 8275-1
profile is configured.
For an example payload, see [Configuring PTP Multicast Transmission](Configuring PTP Multicast Transmission).
Configuring PTP Transport
Note: The default value is ethernet
when an 8275-1
profile is configured and can be modified only when a profile-override
is applied to interface. The ethernet
option is only available on N9K-C93180YC-FX3S platform.
For an example payload, see [Configuring PTP Multicast Transmission](Configuring PTP Multicast Transmission).
Configuring PTP Announce Interval
Note: The default value is -3
when an 8275-1
profile is configured and can be modified only when a profile-override
is applied to the interface.
For an example payload, see [Configuring PTP Announce Interval](Configuring PTP Announce Interval).
Configuring the PTP Delay Request Minimum Interval
Note: The default value is -4
when an 8275-1
profile is configured and can be modified only when a profile-override
is applied to the interface.
For an example payload, see [Configuring the PTP Delay Request Minimum Interval](Configuring the PTP Delay Request Minimum Interval).
Configuring the PTP Sync Interval
Note: The default value is -4
when an 8275-1
profile is configured and can be modified only when a profile-override
is applied to the interface.
For an example payload, see [Configuring the PTP Sync Interval](Configuring the PTP Sync Interval).