Cisco Nexus 3000 and 9000 Series NX-API REST SDK API, Release 9.3(x)
NX-OS 9.3(x)
Configuring PTP Telecom Profile Matching 8275.1
DME
YANG
Copy
POST http://<mgmt0_IP>/api/mo/sys/ptp.json

{
  "ptpPtpEntity": {
    "children": [
      {
        "ptpPtpProfile": {
          "attributes": {
            "profile": "8275-1"
}}}]}}

Response
{
    imdata:[]
}

Copy
<System>
  <ptp-items>
    <profile-items>
      <profile>8275-1</profile>
    </profile-items>
  </ptp-items>
</System>

Configuring a PTP Telecom Profile

Range and Default Values Table

Range and Default Values of Properties Based on Configured Profiles for the N9K-C93180YC-FX3S Platform

Parameter Scope or Configuration Mode Default Profile's Supported Range of Values Default Profile's Default Value 8275.1 Profile's Supported Range of Values 8275-1 Profile's Default Value With 'ptp profile-override' Configured on an Interface Supported Range of Values (Default is Based on Configured Profile)
mode global none none hybrid hybrid no change
domain global 0 to 63 0 24 to 43 24 no change
priority1 global 0 to 255 255 128 128 no change
priority2 global 0 to 255 255 0 to 255 128 no change
cost interface Not configurable Not configurable 0 to 255 128 0 to 255
transport interface ipv4 ipv4 ethernet ethernet ethernet, ipv4
transmission interface multicast, unicast multicast multicast multicast no change
role interface dynamic, master, slave dynamic dynamic dynamic no change
announce interval interface
0 to 4
0 to 4 with aes67
-3 to 1 with smpte-2059-2		 1 -3 -3
-3 to 4
0 to 4 with aes67
-3 to 1 with smpte-2059-2
delay-request minimum interval interface
-1 to 6
-4 to 5 with aes67
-4 to 5 with smpte-2059-2		 0 -4 -4
-4 to 6
-4 to 5 with aes67
-4 to 5 with smpte-2059-2
sync interval interface
-3 to 1
-4 to 1 with aes67
-7 to 0 with smpte-2059-2		 -2 -4 -4
-4 to 1
-4 to 1 with aes67
-7 to 0 with smpte-2059-2

Configuring PTP Telecom Profile Matching 8275.1

Configuring PTP Telecom Profile Matching 8275.1

When a PTP profile is configured, the parameters are automatically set to the defaults shown in the [Range and Default Values Table](#Range and Default Values Table) unless profile-override is applied to a PTP-enabled 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.

ptp profile 8275-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.

MODN
ptpPtpEntity sys/ptp
ptpPtpProfile sys/ptp/profile


ptpPtpProfile Properties

The following table contains information about the ptpPtpProfile 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 NameData TypeDescriptionValues
profileptp:Profile
(scalar:Enum8)		PTP profile to be configuredSELECTION:
1 - 8275-1
2 - default
DEFAULT: default


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 Telecom Profile Matching 8275.1

Deleting PTP Telecom Profile Matching 8275.1

Note: This example was added in Release 9.3(5).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no ptp profile 8275-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.

MODN
ptpPtpEntity sys/ptp
ptpPtpProfile sys/ptp/profile


ptpPtpProfile Properties

The following table contains information about the ptpPtpProfile 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 NameData TypeDescriptionValues
profileptp:Profile
(scalar:Enum8)		PTP profile to be configuredSELECTION:
1 - 8275-1
2 - default
DEFAULT: default


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 a Default PTP Profile

Configuring a Default PTP Profile

When a PTP profile is configured, the parameters are automatically set to the defaults shown in the [Range and Default Values Table](#Range and Default Values Table) unless profile-override is applied to a PTP-enabled 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.

ptp profile default


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.

MODN
ptpPtpEntity sys/ptp
ptpPtpProfile sys/ptp/profile


ptpPtpProfile Properties

The following table contains information about the ptpPtpProfile 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 NameData TypeDescriptionValues
profileptp:Profile
(scalar:Enum8)		PTP profile to be configuredSELECTION:
1 - 8275-1
2 - default
DEFAULT: default


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 PTP Profile Mode as Hybrid

Configuring the PTP Profile Mode as Hybrid

When a PTP profile is configured, the parameters are automatically set to the defaults shown in the [Range and Default Values Table](#Range and Default Values Table) unless profile-override is applied to a PTP-enabled 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.

ptp profile 8275-1
  mode hybrid


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.

MODN
ptpPtpEntity sys/ptp
ptpPtpProfile sys/ptp/profile


ptpPtpProfile Properties

The following table contains information about the ptpPtpProfile 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 NameData TypeDescriptionValues
modeptp:Mode
(scalar:Enum8)		PTP mode for the speciic profile configuredSELECTION:
1 - hybrid
2 - non-hybrid
3 - none
DEFAULT: none
profileptp:Profile
(scalar:Enum8)		PTP profile to be configuredSELECTION:
1 - 8275-1
2 - default
DEFAULT: default


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 Default PTP Profile Mode to None

Configuring the Default PTP Profile Mode to None

When a PTP profile is configured, the parameters are automatically set to the defaults shown in the [Range and Default Values Table](#Range and Default Values Table) unless profile-override is applied to a PTP-enabled 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.

ptp profile default
  mode none


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
ptpPtpEntity sys/ptp
ptpPtpProfile sys/ptp/profile


ptpPtpProfile Properties

The following table contains information about the ptpPtpProfile 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 NameData TypeDescriptionValues
modeptp:Mode
(scalar:Enum8)		PTP mode for the speciic profile configuredSELECTION:
1 - hybrid
2 - non-hybrid
3 - none
DEFAULT: none
profileptp:Profile
(scalar:Enum8)		PTP profile to be configuredSELECTION:
1 - 8275-1
2 - default
DEFAULT: default


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 Clock Domain

Note: The range is 24-43 with a default value of 24 when an 8275-1 profile is configured.

For an example payload, see Configuring PTP Clock Domain.

Configuring PTP Priority1

Note: You cannot change the default value of 128 when an 8275-1 profile is configured.

For an example payload, see Configuring PTP Priority1.

Configuring PTP Priority2

For an example payload, see For an example payload, see Configuring PTP Priority2. `

Next