Configuring an Ethernet Range

Configuring Packet Acceptance and Response Based on Config (Non-Forwardable)

Configuring Packet Acceptance and Response Based on Config (Non-Forwardable)

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "ptpPtpEntity": {
          "children": [
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/3",
                  "ptpDestinationMac": "non-forwardable",
                  "ptpRxNoMatch": "accept"
                }
              }
            },
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/2",
                  "ptpDestinationMac": "non-forwardable",
                  "ptpRxNoMatch": "accept"
                }
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <ptp-items>
    <if-items>
      <PtpIf-list>
        <id>eth1/3</id>
        <ptpDestinationMac>non-forwardable</ptpDestinationMac>
        <ptpRxNoMatch>accept</ptpRxNoMatch>
      </PtpIf-list>
      <PtpIf-list>
        <id>eth1/2</id>
        <ptpDestinationMac>non-forwardable</ptpDestinationMac>
        <ptpRxNoMatch>accept</ptpRxNoMatch>
      </PtpIf-list>
    </if-items>
  </ptp-items>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</id>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

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/2-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.

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.

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.

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.

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.

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)

Deleting Packet Acceptance and Response Based on Config (Non-Forwardable)

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "ptpPtpEntity": {
          "children": [
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/3",
                  "ptpDestinationMac": "non-forwardable",
                  "ptpRxNoMatch": "accept"
                }
              }
            },
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/2",
                  "ptpDestinationMac": "non-forwardable",
                  "ptpRxNoMatch": "accept"
                }
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <ptp-items>
    <if-items>
      <PtpIf-list>
        <id>eth1/3</id>
        <ptpDestinationMac>non-forwardable</ptpDestinationMac>
        <ptpRxNoMatch>accept</ptpRxNoMatch>
      </PtpIf-list>
      <PtpIf-list>
        <id>eth1/2</id>
        <ptpDestinationMac>non-forwardable</ptpDestinationMac>
        <ptpRxNoMatch>accept</ptpRxNoMatch>
      </PtpIf-list>
    </if-items>
  </ptp-items>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</id>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

This example is only applicable with the N9K-C93180YC-FX3S Platform and will take effect when 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/2-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.

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.

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.

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.

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.

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)

Configuring Drop Packet and No Response (Non-Forwardable)

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "ptpPtpEntity": {
          "children": [
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/3",
                  "ptpDestinationMac": "non-forwardable",
                  "ptpRxNoMatch": "drop"
                }
              }
            },
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/2",
                  "ptpDestinationMac": "non-forwardable",
                  "ptpRxNoMatch": "drop"
                }
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <ptp-items>
    <if-items>
      <PtpIf-list>
        <id>eth1/3</id>
        <ptpDestinationMac>non-forwardable</ptpDestinationMac>
        <ptpRxNoMatch>drop</ptpRxNoMatch>
      </PtpIf-list>
      <PtpIf-list>
        <id>eth1/2</id>
        <ptpDestinationMac>non-forwardable</ptpDestinationMac>
        <ptpRxNoMatch>drop</ptpRxNoMatch>
      </PtpIf-list>
    </if-items>
  </ptp-items>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</id>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

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/2-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.

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.

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.

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.

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.

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)

Deleting Drop Packet and No Response (Non-Forwardable)

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "ptpPtpEntity": {
          "children": [
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/3",
                  "ptpDestinationMac": "non-forwardable",
                  "ptpRxNoMatch": "accept"
                }
              }
            },
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/2",
                  "ptpDestinationMac": "non-forwardable",
                  "ptpRxNoMatch": "accept"
                }
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <ptp-items>
    <if-items>
      <PtpIf-list>
        <id>eth1/3</id>
        <ptpDestinationMac>non-forwardable</ptpDestinationMac>
        <ptpRxNoMatch>accept</ptpRxNoMatch>
      </PtpIf-list>
      <PtpIf-list>
        <id>eth1/2</id>
        <ptpDestinationMac>non-forwardable</ptpDestinationMac>
        <ptpRxNoMatch>accept</ptpRxNoMatch>
      </PtpIf-list>
    </if-items>
  </ptp-items>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</id>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

This example is only applicable with the N9K-C93180YC-FX3S Platform and will take effect when 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/2-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.

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.

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.

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.

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.

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)

Configuring Packet Acceptance and Response Based on Received Packet (Non-Forwardable)

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "ptpPtpEntity": {
          "children": [
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/3",
                  "ptpDestinationMac": "non-forwardable",
                  "ptpRxNoMatch": "follow-rx"
                }
              }
            },
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/2",
                  "ptpDestinationMac": "non-forwardable",
                  "ptpRxNoMatch": "follow-rx"
                }
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <ptp-items>
    <if-items>
      <PtpIf-list>
        <id>eth1/3</id>
        <ptpDestinationMac>non-forwardable</ptpDestinationMac>
        <ptpRxNoMatch>follow-rx</ptpRxNoMatch>
      </PtpIf-list>
      <PtpIf-list>
        <id>eth1/2</id>
        <ptpDestinationMac>non-forwardable</ptpDestinationMac>
        <ptpRxNoMatch>follow-rx</ptpRxNoMatch>
      </PtpIf-list>
    </if-items>
  </ptp-items>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</id>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

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/2-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.

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.

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.

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.

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.

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)

Deleting Packet Acceptance and Response Based on Received Packet (Non-Forwardable)

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "ptpPtpEntity": {
          "children": [
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/3",
                  "ptpDestinationMac": "non-forwardable",
                  "ptpRxNoMatch": "accept"
                }
              }
            },
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/2",
                  "ptpDestinationMac": "non-forwardable",
                  "ptpRxNoMatch": "accept"
                }
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <ptp-items>
    <if-items>
      <PtpIf-list>
        <id>eth1/3</id>
        <ptpDestinationMac>non-forwardable</ptpDestinationMac>
        <ptpRxNoMatch>accept</ptpRxNoMatch>
      </PtpIf-list>
      <PtpIf-list>
        <id>eth1/2</id>
        <ptpDestinationMac>non-forwardable</ptpDestinationMac>
        <ptpRxNoMatch>accept</ptpRxNoMatch>
      </PtpIf-list>
    </if-items>
  </ptp-items>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</id>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

This example is only applicable with the N9K-C93180YC-FX3S Platform and will take effect when 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/2-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.

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.

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.

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.

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.

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)

Configuring Packet Acceptance and Response Based on Config (Forwardable)

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "ptpPtpEntity": {
          "children": [
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/3",
                  "ptpDestinationMac": "forwardable",
                  "ptpRxNoMatch": "accept"
                }
              }
            },
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/2",
                  "ptpDestinationMac": "forwardable",
                  "ptpRxNoMatch": "accept"
                }
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <ptp-items>
    <if-items>
      <PtpIf-list>
        <id>eth1/3</id>
        <ptpDestinationMac>forwardable</ptpDestinationMac>
        <ptpRxNoMatch>accept</ptpRxNoMatch>
      </PtpIf-list>
      <PtpIf-list>
        <id>eth1/2</id>
        <ptpDestinationMac>forwardable</ptpDestinationMac>
        <ptpRxNoMatch>accept</ptpRxNoMatch>
      </PtpIf-list>
    </if-items>
  </ptp-items>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</id>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

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/2-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.

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.

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.

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.

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.

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)

Deleting Packet Acceptance and Response Based on Config (Forwardable)

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "ptpPtpEntity": {
          "children": [
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/3",
                  "ptpDestinationMac": "non-forwardable",
                  "ptpRxNoMatch": "accept"
                }
              }
            },
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/2",
                  "ptpDestinationMac": "non-forwardable",
                  "ptpRxNoMatch": "accept"
                }
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <ptp-items>
    <if-items>
      <PtpIf-list>
        <id>eth1/3</id>
        <ptpDestinationMac>non-forwardable</ptpDestinationMac>
        <ptpRxNoMatch>accept</ptpRxNoMatch>
      </PtpIf-list>
      <PtpIf-list>
        <id>eth1/2</id>
        <ptpDestinationMac>non-forwardable</ptpDestinationMac>
        <ptpRxNoMatch>accept</ptpRxNoMatch>
      </PtpIf-list>
    </if-items>
  </ptp-items>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</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/2-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.

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.

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.

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.

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.

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)

Configuring Drop Packet and No Response (Forwardable)

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "ptpPtpEntity": {
          "children": [
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/3",
                  "ptpDestinationMac": "forwardable",
                  "ptpRxNoMatch": "drop"
                }
              }
            },
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/2",
                  "ptpDestinationMac": "forwardable",
                  "ptpRxNoMatch": "drop"
                }
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <ptp-items>
    <if-items>
      <PtpIf-list>
        <id>eth1/3</id>
        <ptpDestinationMac>forwardable</ptpDestinationMac>
        <ptpRxNoMatch>drop</ptpRxNoMatch>
      </PtpIf-list>
      <PtpIf-list>
        <id>eth1/2</id>
        <ptpDestinationMac>forwardable</ptpDestinationMac>
        <ptpRxNoMatch>drop</ptpRxNoMatch>
      </PtpIf-list>
    </if-items>
  </ptp-items>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</id>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

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/2-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.

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.

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.

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.

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.

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)

Deleting Drop Packet and No Response (Forwardable)

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "ptpPtpEntity": {
          "children": [
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/3",
                  "ptpDestinationMac": "non-forwardable",
                  "ptpRxNoMatch": "accept"
                }
              }
            },
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/2",
                  "ptpDestinationMac": "non-forwardable",
                  "ptpRxNoMatch": "accept"
                }
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <ptp-items>
    <if-items>
      <PtpIf-list>
        <id>eth1/3</id>
        <ptpDestinationMac>non-forwardable</ptpDestinationMac>
        <ptpRxNoMatch>accept</ptpRxNoMatch>
      </PtpIf-list>
      <PtpIf-list>
        <id>eth1/2</id>
        <ptpDestinationMac>non-forwardable</ptpDestinationMac>
        <ptpRxNoMatch>accept</ptpRxNoMatch>
      </PtpIf-list>
    </if-items>
  </ptp-items>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</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/2-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.

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.

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.

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.

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.

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)

Configuring Packet Acceptance and Response Based on Received Packet (Forwardable)

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "ptpPtpEntity": {
          "children": [
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/3",
                  "ptpDestinationMac": "forwardable",
                  "ptpRxNoMatch": "follow-rx"
                }
              }
            },
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/2",
                  "ptpDestinationMac": "forwardable",
                  "ptpRxNoMatch": "follow-rx"
                }
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <ptp-items>
    <if-items>
      <PtpIf-list>
        <id>eth1/3</id>
        <ptpDestinationMac>forwardable</ptpDestinationMac>
        <ptpRxNoMatch>follow-rx</ptpRxNoMatch>
      </PtpIf-list>
      <PtpIf-list>
        <id>eth1/2</id>
        <ptpDestinationMac>forwardable</ptpDestinationMac>
        <ptpRxNoMatch>follow-rx</ptpRxNoMatch>
      </PtpIf-list>
    </if-items>
  </ptp-items>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</id>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

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/2-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.

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.

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.

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.

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.

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)

Deleting Packet Acceptance and Response Based on Received Packet (Forwardable)

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "ptpPtpEntity": {
          "children": [
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/3",
                  "ptpDestinationMac": "non-forwardable",
                  "ptpRxNoMatch": "accept"
                }
              }
            },
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/2",
                  "ptpDestinationMac": "non-forwardable",
                  "ptpRxNoMatch": "accept"
                }
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <ptp-items>
    <if-items>
      <PtpIf-list>
        <id>eth1/3</id>
        <ptpDestinationMac>non-forwardable</ptpDestinationMac>
        <ptpRxNoMatch>accept</ptpRxNoMatch>
      </PtpIf-list>
      <PtpIf-list>
        <id>eth1/2</id>
        <ptpDestinationMac>non-forwardable</ptpDestinationMac>
        <ptpRxNoMatch>accept</ptpRxNoMatch>
      </PtpIf-list>
    </if-items>
  </ptp-items>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</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/2-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.

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.

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.

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.

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.

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 Override of Some PTP Profile Parameters on an Interface

Configuring Override of Some PTP Profile Parameters on an Interface

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "ptpPtpEntity": {
          "children": [
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/3",
                  "profileOverride": "yes"
                }
              }
            },
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/2",
                  "profileOverride": "yes"
                }
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <ptp-items>
    <if-items>
      <PtpIf-list>
        <id>eth1/3</id>
        <profileOverride>true</profileOverride>
      </PtpIf-list>
      <PtpIf-list>
        <id>eth1/2</id>
        <profileOverride>true</profileOverride>
      </PtpIf-list>
    </if-items>
  </ptp-items>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</id>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

This example is only applicable with the N9K-C93180YC-FX3S platform and allows for over-riding the range and defaults set by a configured profile on PTP-enabled interfaces.

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/2-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.

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.

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.

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.

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.

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

Deleting Override of Some PTP Profile Parameters on an Interface

POST http://<mgmt0_IP>/api/mo/sys.json

{
  "topSystem": {
    "children": [
      {
        "ptpPtpEntity": {
          "children": [
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/3",
                  "profileOverride": "no"
                }
              }
            },
            {
              "ptpPtpIf": {
                "attributes": {
                  "id": "eth1/2",
                  "profileOverride": "no"
                }
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <ptp-items>
    <if-items>
      <PtpIf-list>
        <id>eth1/3</id>
        <profileOverride>false</profileOverride>
      </PtpIf-list>
      <PtpIf-list>
        <id>eth1/2</id>
        <profileOverride>false</profileOverride>
      </PtpIf-list>
    </if-items>
  </ptp-items>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</id>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

This example is only applicable with the N9K-C93180YC-FX3S platform and allows for over-riding the range and defaults set by a configured profile on PTP-enabled interfaces.

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/2-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.

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.

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.

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.

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.

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