Configuring an Ethernet Interface Range

Configuring the Source Id Inserted in the Timestamp (Egress)

Configuring the Source Id Inserted in the Timestamp (Egress)

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

{
  "topSystem": {
    "children": [
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2",
                  "packetTimestampEgressSourceId": "1",
                  "packetTimestampState": "enable-egress"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3",
                  "packetTimestampEgressSourceId": "1",
                  "packetTimestampState": "enable-egress"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/2</id>
        <packetTimestampEgressSourceId>1</packetTimestampEgressSourceId>
        <packetTimestampState>enable-egress</packetTimestampState>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/3</id>
        <packetTimestampEgressSourceId>1</packetTimestampEgressSourceId>
        <packetTimestampState>enable-egress</packetTimestampState>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

Note: This example was added in Release 9.2(3).

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
timestamp egress id 1

Note: The property information for this example was added in Release 9.3(3).

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

MO	DN
topSystem	sys
interfaceEntity	sys/intf
l1PhysIf	sys/intf/phys-{[id]}

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
packetTimestampEgressSourceId	l1:PacketTimestampSourceId (scalar:Uint32)	Egress timestamp Source Id	RANGE: [0 , 8388606] DEFAULT: 0
packetTimestampState	l1:PacketTimestampState (scalar:Enum8)	packet timestamp feature state	SELECTION: 0 - disable 1 - enable-ingress 2 - enable-egress 3 - enable-both DEFAULT: disable

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 Source Ids Inserted in the Timestamp (Egress and Ingress)

Configuring the Source Ids Inserted in the Timestamp (Egress and Ingress)

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

{
  "topSystem": {
    "children": [
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2",
                  "packetTimestampEgressSourceId": "1",
                  "packetTimestampIngressSourceId": "1",
                  "packetTimestampState": "enable-both"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3",
                  "packetTimestampEgressSourceId": "1",
                  "packetTimestampIngressSourceId": "1",
                  "packetTimestampState": "enable-both"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/2</id>
        <packetTimestampEgressSourceId>1</packetTimestampEgressSourceId>
        <packetTimestampIngressSourceId>1</packetTimestampIngressSourceId>
        <packetTimestampState>enable-both</packetTimestampState>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/3</id>
        <packetTimestampEgressSourceId>1</packetTimestampEgressSourceId>
        <packetTimestampIngressSourceId>1</packetTimestampIngressSourceId>
        <packetTimestampState>enable-both</packetTimestampState>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

Note: This example was added in Release 9.2(3).

CLI Commands

interface ethernet 1/2-3
timestamp egress id 1 ingress id 1

Note: The property information for this example was added in Release 9.3(3).

MO	DN
topSystem	sys
interfaceEntity	sys/intf
l1PhysIf	sys/intf/phys-{[id]}

l1PhysIf Properties

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
packetTimestampEgressSourceId	l1:PacketTimestampSourceId (scalar:Uint32)	Egress timestamp Source Id	RANGE: [0 , 8388606] DEFAULT: 0
packetTimestampIngressSourceId	l1:PacketTimestampSourceId (scalar:Uint32)	Ingress timestamp Source Id	RANGE: [0 , 8388606] DEFAULT: 0
packetTimestampState	l1:PacketTimestampState (scalar:Enum8)	packet timestamp feature state	SELECTION: 0 - disable 1 - enable-ingress 2 - enable-egress 3 - enable-both DEFAULT: disable

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 Source Id Inserted in the Timestamp (Ingress)

Configuring the Source Id Inserted in the Timestamp (Ingress)

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

{
  "topSystem": {
    "children": [
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2",
                  "packetTimestampIngressSourceId": "1",
                  "packetTimestampState": "enable-ingress"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3",
                  "packetTimestampIngressSourceId": "1",
                  "packetTimestampState": "enable-ingress"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/2</id>
        <packetTimestampIngressSourceId>1</packetTimestampIngressSourceId>
        <packetTimestampState>enable-ingress</packetTimestampState>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/3</id>
        <packetTimestampIngressSourceId>1</packetTimestampIngressSourceId>
        <packetTimestampState>enable-ingress</packetTimestampState>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

Note: This example was added in Release 9.2(3).

CLI Commands

interface ethernet 1/2-3
timestamp ingress id 1

Note: The property information for this example was added in Release 9.3(3).

MO	DN
topSystem	sys
interfaceEntity	sys/intf
l1PhysIf	sys/intf/phys-{[id]}

l1PhysIf Properties

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
packetTimestampIngressSourceId	l1:PacketTimestampSourceId (scalar:Uint32)	Ingress timestamp Source Id	RANGE: [0 , 8388606] DEFAULT: 0
packetTimestampState	l1:PacketTimestampState (scalar:Enum8)	packet timestamp feature state	SELECTION: 0 - disable 1 - enable-ingress 2 - enable-egress 3 - enable-both DEFAULT: disable

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 Source Ids Inserted in the Timestamp (Ingress and Egress)

Configuring the Source Ids Inserted in the Timestamp (Ingress and Egress)

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

{
  "topSystem": {
    "children": [
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2",
                  "packetTimestampEgressSourceId": "1",
                  "packetTimestampIngressSourceId": "1",
                  "packetTimestampState": "enable-both"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3",
                  "packetTimestampEgressSourceId": "1",
                  "packetTimestampIngressSourceId": "1",
                  "packetTimestampState": "enable-both"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/2</id>
        <packetTimestampEgressSourceId>1</packetTimestampEgressSourceId>
        <packetTimestampIngressSourceId>1</packetTimestampIngressSourceId>
        <packetTimestampState>enable-both</packetTimestampState>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/3</id>
        <packetTimestampEgressSourceId>1</packetTimestampEgressSourceId>
        <packetTimestampIngressSourceId>1</packetTimestampIngressSourceId>
        <packetTimestampState>enable-both</packetTimestampState>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

Note: This example was added in Release 9.2(3).

CLI Commands

interface ethernet 1/2-3
timestamp ingress id 1 egress id 1

Note: The property information for this example was added in Release 9.3(3).

MO	DN
topSystem	sys
interfaceEntity	sys/intf
l1PhysIf	sys/intf/phys-{[id]}

l1PhysIf Properties

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
packetTimestampEgressSourceId	l1:PacketTimestampSourceId (scalar:Uint32)	Egress timestamp Source Id	RANGE: [0 , 8388606] DEFAULT: 0
packetTimestampIngressSourceId	l1:PacketTimestampSourceId (scalar:Uint32)	Ingress timestamp Source Id	RANGE: [0 , 8388606] DEFAULT: 0
packetTimestampState	l1:PacketTimestampState (scalar:Enum8)	packet timestamp feature state	SELECTION: 0 - disable 1 - enable-ingress 2 - enable-egress 3 - enable-both DEFAULT: disable

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 a Timestamp

Deleting a Timestamp

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

{
  "topSystem": {
    "children": [
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2",
                  "packetTimestampState": "disable"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3",
                  "packetTimestampState": "disable"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/2</id>
        <packetTimestampState>disable</packetTimestampState>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/3</id>
        <packetTimestampState>disable</packetTimestampState>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

Note: This example was added in Release 9.2(3).

CLI Commands

interface ethernet 1/2-3
no timestamp

Note: The property information for this example was added in Release 9.3(3).

MO	DN
topSystem	sys
interfaceEntity	sys/intf
l1PhysIf	sys/intf/phys-{[id]}

l1PhysIf Properties

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
packetTimestampState	l1:PacketTimestampState (scalar:Enum8)	packet timestamp feature state	SELECTION: 0 - disable 1 - enable-ingress 2 - enable-egress 3 - enable-both DEFAULT: disable

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 Extra Buffers for this Interface

 Configuring Extra Buffers for this Interface

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

{
  "topSystem": {
    "children": [
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3"
                },
                "children": [
                  {
                    "l1PhysIfExtended": {
                      "attributes": {
                        "bufferBoost": "enable"
                      }
                    }
                  }
                ]
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2"
                },
                "children": [
                  {
                    "l1PhysIfExtended": {
                      "attributes": {
                        "bufferBoost": "enable"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
        <physExtd-items>
          <bufferBoost>enable</bufferBoost>
        </physExtd-items>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</id>
        <physExtd-items>
          <bufferBoost>enable</bufferBoost>
        </physExtd-items>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

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

CLI Commands

interface ethernet 1/2-3
buffer-boost

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
interfaceEntity	sys/intf
l1PhysIf	sys/intf/phys-[eth1/3]
l1PhysIfExtended	sys/intf/phys-[eth1/3]/physExtd
l1PhysIf	sys/intf/phys-[eth1/2]
l1PhysIfExtended	sys/intf/phys-[eth1/2]/physExtd

l1PhysIf Properties

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

l1PhysIfExtended Properties

The following table contains information about the l1PhysIfExtended 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
bufferBoost	l1:BufferBoost (scalar:Enum8)	Disable/enable buffer boost on interface	SELECTION: 0 - disable 1 - enable DEFAULT: enable

l1PhysIf Properties

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

l1PhysIfExtended Properties

Property Name	Data Type	Description	Values
bufferBoost	l1:BufferBoost (scalar:Enum8)	Disable/enable buffer boost on interface	SELECTION: 0 - disable 1 - enable DEFAULT: enable

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 Extra Buffers for this Interface

 Deleting Extra Buffers for this Interface

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

{
  "topSystem": {
    "children": [
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3"
                },
                "children": [
                  {
                    "l1PhysIfExtended": {
                      "attributes": {
                        "bufferBoost": "disable"
                      }
                    }
                  }
                ]
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2"
                },
                "children": [
                  {
                    "l1PhysIfExtended": {
                      "attributes": {
                        "bufferBoost": "disable"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
        <physExtd-items>
          <bufferBoost>disable</bufferBoost>
        </physExtd-items>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</id>
        <physExtd-items>
          <bufferBoost>disable</bufferBoost>
        </physExtd-items>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

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

CLI Commands

interface ethernet 1/2-3
no buffer-boost

Verifying a DME Configuration

MO	DN
topSystem	sys
interfaceEntity	sys/intf
l1PhysIf	sys/intf/phys-[eth1/3]
l1PhysIfExtended	sys/intf/phys-[eth1/3]/physExtd
l1PhysIf	sys/intf/phys-[eth1/2]
l1PhysIfExtended	sys/intf/phys-[eth1/2]/physExtd

l1PhysIf Properties

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

l1PhysIfExtended Properties

Property Name	Data Type	Description	Values
bufferBoost	l1:BufferBoost (scalar:Enum8)	Disable/enable buffer boost on interface	SELECTION: 0 - disable 1 - enable DEFAULT: enable

l1PhysIf Properties

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

l1PhysIfExtended Properties

Property Name	Data Type	Description	Values
bufferBoost	l1:BufferBoost (scalar:Enum8)	Disable/enable buffer boost on interface	SELECTION: 0 - disable 1 - enable DEFAULT: enable

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

Disabling Loop-Free Detection

Disabling Loop-Free Detection

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

{
  "topSystem": {
    "children": [
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3"
                },
                "children": [
                  {
                    "l1PhysIfExtended": {
                      "attributes": {
                        "switchportIsolated": "enable"
                      }
                    }
                  }
                ]
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2"
                },
                "children": [
                  {
                    "l1PhysIfExtended": {
                      "attributes": {
                        "switchportIsolated": "enable"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
        <physExtd-items>
          <switchportIsolated>enable</switchportIsolated>
        </physExtd-items>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</id>
        <physExtd-items>
          <switchportIsolated>enable</switchportIsolated>
        </physExtd-items>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

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

CLI Commands

interface ethernet 1/2-3
switchport isolated

Verifying a DME Configuration

MO	DN
topSystem	sys
interfaceEntity	sys/intf
l1PhysIf	sys/intf/phys-[eth1/3]
l1PhysIfExtended	sys/intf/phys-[eth1/3]/physExtd
l1PhysIf	sys/intf/phys-[eth1/2]
l1PhysIfExtended	sys/intf/phys-[eth1/2]/physExtd

l1PhysIf Properties

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

l1PhysIfExtended Properties

Property Name	Data Type	Description	Values
switchportIsolated	l1:SwitchportIsolated (scalar:Enum8)	Switchport Isolated	SELECTION: 0 - disable 1 - enable DEFAULT: disable

l1PhysIf Properties

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

l1PhysIfExtended Properties

Property Name	Data Type	Description	Values
switchportIsolated	l1:SwitchportIsolated (scalar:Enum8)	Switchport Isolated	SELECTION: 0 - disable 1 - enable DEFAULT: disable

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

Unconfiguring Disabled Loop-Free Detection

Unconfiguring Disabled Loop-Free Detection

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

{
  "topSystem": {
    "children": [
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3"
                },
                "children": [
                  {
                    "l1PhysIfExtended": {
                      "attributes": {
                        "switchportIsolated": "disable"
                      }
                    }
                  }
                ]
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2"
                },
                "children": [
                  {
                    "l1PhysIfExtended": {
                      "attributes": {
                        "switchportIsolated": "disable"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
        <physExtd-items>
          <switchportIsolated>disable</switchportIsolated>
        </physExtd-items>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</id>
        <physExtd-items>
          <switchportIsolated>disable</switchportIsolated>
        </physExtd-items>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

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

CLI Commands

interface ethernet 1/2-3
no switchport isolated

Verifying a DME Configuration

MO	DN
topSystem	sys
interfaceEntity	sys/intf
l1PhysIf	sys/intf/phys-[eth1/3]
l1PhysIfExtended	sys/intf/phys-[eth1/3]/physExtd
l1PhysIf	sys/intf/phys-[eth1/2]
l1PhysIfExtended	sys/intf/phys-[eth1/2]/physExtd

l1PhysIf Properties

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

l1PhysIfExtended Properties

Property Name	Data Type	Description	Values
switchportIsolated	l1:SwitchportIsolated (scalar:Enum8)	Switchport Isolated	SELECTION: 0 - disable 1 - enable DEFAULT: disable

l1PhysIf Properties

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

l1PhysIfExtended Properties

Property Name	Data Type	Description	Values
switchportIsolated	l1:SwitchportIsolated (scalar:Enum8)	Switchport Isolated	SELECTION: 0 - disable 1 - enable DEFAULT: disable

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 Interface Throughput Delay

Configuring Interface Throughput Delay

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

{
  "topSystem": {
    "children": [
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "delay": "16723856",
                  "id": "eth1/3"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "delay": "16723856",
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
        <delay>16723856</delay>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</id>
        <delay>16723856</delay>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

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

CLI Commands

interface ethernet 1/2-3
delay 16723856

Verifying a DME Configuration

MO	DN
interfaceEntity	sys/intf
l1PhysIf	sys/intf/phys-[eth1/3]
topSystem	sys

l1PhysIf Properties

Property Name	Data Type	Description	Values
delay	l1:Delay (scalar:Uint32)	The administrative port delay time.	RANGE: [1 , 16777215] DEFAULT: 1
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 Interface Throughput Delay

Deleting Interface Throughput Delay

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

{
  "topSystem": {
    "children": [
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "delay": "1",
                  "id": "eth1/3"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "delay": "1",
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
        <delay>1</delay>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</id>
        <delay>1</delay>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

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

CLI Commands

interface ethernet 1/2-3
no delay 16723856

Verifying a DME Configuration

MO	DN
interfaceEntity	sys/intf
l1PhysIf	sys/intf/phys-[eth1/3]
topSystem	sys

l1PhysIf Properties

Property Name	Data Type	Description	Values
delay	l1:Delay (scalar:Uint32)	The administrative port delay time.	RANGE: [1 , 16777215] DEFAULT: 1
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 Audo MDIX Mode

 Configuring Audo MDIX Mode

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

{
  "topSystem": {
    "children": [
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3",
                  "mdix": "auto"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2",
                  "mdix": "auto"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
        <mdix>auto</mdix>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</id>
        <mdix>auto</mdix>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

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

CLI Commands

interface ethernet 1/2-3
mdix auto

Verifying a DME Configuration

MO	DN
topSystem	sys
interfaceEntity	sys/intf
l1PhysIf	sys/intf/phys-[eth1/3]
l1PhysIf	sys/intf/phys-[eth1/2]

l1PhysIf Properties

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
mdix	l1:Mdix (scalar:Enum8)	The administrative Mdix mode. The Medium-dependant interface crossover (Mdix) is when the interface automatically detects the required cable connection type (straight through or crossover) and configures the connection appropriately.	SELECTION: 1 - auto 2 - mdi 3 - mdi-x DEFAULT: auto

l1PhysIf Properties

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
mdix	l1:Mdix (scalar:Enum8)	The administrative Mdix mode. The Medium-dependant interface crossover (Mdix) is when the interface automatically detects the required cable connection type (straight through or crossover) and configures the connection appropriately.	SELECTION: 1 - auto 2 - mdi 3 - mdi-x DEFAULT: auto

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 Audo MDIX Mode

 Deleting Audo MDIX Mode

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

{
  "topSystem": {
    "children": [
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/3",
                  "mdix": "mdi"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2",
                  "mdix": "mdi"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
        <mdix>mdi</mdix>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</id>
        <mdix>mdi</mdix>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

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

CLI Commands

interface ethernet 1/2-3
no mdix auto

Verifying a DME Configuration

MO	DN
topSystem	sys
interfaceEntity	sys/intf
l1PhysIf	sys/intf/phys-[eth1/3]
l1PhysIf	sys/intf/phys-[eth1/2]

l1PhysIf Properties

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
mdix	l1:Mdix (scalar:Enum8)	The administrative Mdix mode. The Medium-dependant interface crossover (Mdix) is when the interface automatically detects the required cable connection type (straight through or crossover) and configures the connection appropriately.	SELECTION: 1 - auto 2 - mdi 3 - mdi-x DEFAULT: auto

l1PhysIf Properties

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
mdix	l1:Mdix (scalar:Enum8)	The administrative Mdix mode. The Medium-dependant interface crossover (Mdix) is when the interface automatically detects the required cable connection type (straight through or crossover) and configures the connection appropriately.	SELECTION: 1 - auto 2 - mdi 3 - mdi-x DEFAULT: auto

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 Description

 Configuring a Description

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

{
  "topSystem": {
    "children": [
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "descr": "SampleString_123",
                  "id": "eth1/3"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "descr": "SampleString_123",
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
        <descr>SampleString_123</descr>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</id>
        <descr>SampleString_123</descr>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

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

CLI Commands

interface ethernet 1/2-3
description SampleString_123

Verifying a DME Configuration

MO	DN
topSystem	sys
interfaceEntity	sys/intf
l1PhysIf	sys/intf/phys-[eth1/3]
l1PhysIf	sys/intf/phys-[eth1/2]

l1PhysIf Properties

Property Name	Data Type	Description	Values
descr	naming:Descr1024 string:Basic	Additional descriptive information about the object.	RANGE: Min: "0" Max: "254"
id	nw:IfId (base:IfIndex)	An identifier .	Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100

l1PhysIf Properties

Property Name	Data Type	Description	Values
descr	naming:Descr1024 string:Basic	Additional descriptive information about the object.	RANGE: Min: "0" Max: "254"
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 a Description

 Deleting a Description

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

{
  "topSystem": {
    "children": [
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "descr": "",
                  "id": "eth1/3"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "descr": "",
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
        <descr></descr>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</id>
        <descr></descr>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

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

CLI Commands

interface ethernet 1/2-3
no description SampleString_123

Verifying a DME Configuration

MO	DN
topSystem	sys
interfaceEntity	sys/intf
l1PhysIf	sys/intf/phys-[eth1/3]
l1PhysIf	sys/intf/phys-[eth1/2]

l1PhysIf Properties

Property Name	Data Type	Description	Values
descr	naming:Descr1024 string:Basic	Additional descriptive information about the object.	RANGE: Min: "0" Max: "254"
id	nw:IfId (base:IfIndex)	An identifier .	Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100

l1PhysIf Properties

Property Name	Data Type	Description	Values
descr	naming:Descr1024 string:Basic	Additional descriptive information about the object.	RANGE: Min: "0" Max: "254"
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 Default EtherType for 802.1q Frames

 Configuring Default EtherType for 802.1q Frames

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

{
  "topSystem": {
    "children": [
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "dot1qEtherType": "0x8100",
                  "id": "eth1/3"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "dot1qEtherType": "0x8100",
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
        <dot1qEtherType>33024</dot1qEtherType>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</id>
        <dot1qEtherType>33024</dot1qEtherType>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

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

CLI Commands

interface ethernet 1/2-3
switchport dot1q ethertype 0x8100

Verifying a DME Configuration

MO	DN
topSystem	sys
interfaceEntity	sys/intf
l1PhysIf	sys/intf/phys-[eth1/3]
l1PhysIf	sys/intf/phys-[eth1/2]

l1PhysIf Properties

Property Name	Data Type	Description	Values
dot1qEtherType	l1:DDot1qEtherType (scalar:Uint32)	The administrative port Dot1q ether-type. Dot1q Ether Type configures the TPID value in the VLAN tag field for packets received and sent by the interface.	RANGE: [1536 , 65535] DEFAULT: 0x8100
id	nw:IfId (base:IfIndex)	An identifier .	Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100

l1PhysIf Properties

Property Name	Data Type	Description	Values
dot1qEtherType	l1:DDot1qEtherType (scalar:Uint32)	The administrative port Dot1q ether-type. Dot1q Ether Type configures the TPID value in the VLAN tag field for packets received and sent by the interface.	RANGE: [1536 , 65535] DEFAULT: 0x8100
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 Default EtherType for 802.1q Frames

 Deleting Default EtherType for 802.1q Frames

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

{
  "topSystem": {
    "children": [
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "dot1qEtherType": "0x8100",
                  "id": "eth1/3"
                }
              }
            },
            {
              "l1PhysIf": {
                "attributes": {
                  "dot1qEtherType": "0x8100",
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/3</id>
        <dot1qEtherType>33024</dot1qEtherType>
      </PhysIf-list>
      <PhysIf-list>
        <id>eth1/2</id>
        <dot1qEtherType>33024</dot1qEtherType>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

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

CLI Commands

interface ethernet 1/2-3
no switchport dot1q ethertype 0x8100

Verifying a DME Configuration

MO	DN
topSystem	sys
interfaceEntity	sys/intf
l1PhysIf	sys/intf/phys-[eth1/3]
l1PhysIf	sys/intf/phys-[eth1/2]

l1PhysIf Properties

Property Name	Data Type	Description	Values
dot1qEtherType	l1:DDot1qEtherType (scalar:Uint32)	The administrative port Dot1q ether-type. Dot1q Ether Type configures the TPID value in the VLAN tag field for packets received and sent by the interface.	RANGE: [1536 , 65535] DEFAULT: 0x8100
id	nw:IfId (base:IfIndex)	An identifier .	Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100

l1PhysIf Properties

Property Name	Data Type	Description	Values
dot1qEtherType	l1:DDot1qEtherType (scalar:Uint32)	The administrative port Dot1q ether-type. Dot1q Ether Type configures the TPID value in the VLAN tag field for packets received and sent by the interface.	RANGE: [1536 , 65535] DEFAULT: 0x8100
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