Configuring OSPFv3 on a P2P Ethernet Interface

Configuring Routing Update Supression on the Interface

Configuring Routing Update Supression on the Interface

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

{
  "topSystem": {
    "children": [
      {
        "ospfv3Entity": {
          "children": [
            {
              "ospfv3If": {
                "attributes": {
                  "id": "eth1/8",
                  "passive": "enabled"
                }
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/8",
                  "medium": "p2p"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <ospfv3-items>
    <if-items>
      <If-list>
        <id>eth1/8</id>
        <passive>enabled</passive>
      </If-list>
    </if-items>
  </ospfv3-items>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/8</id>
        <medium>p2p</medium>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

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


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/8
 medium p2p
  ospfv3 passive-interface


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

MODN
l1PhysIf sys/intf/phys-[eth1/8]
ospfv3If sys/ospfv3/if-[eth1/8]


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 NameData TypeDescriptionValues
idnw:IfId
(base:IfIndex)		An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100
mediuml1:Medium
(scalar:Enum8)		The administrative port medium type.SELECTION:
1 - broadcast
2 - p2p
DEFAULT: broadcast


ospfv3If Properties

The following table contains information about the ospfv3If properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
idnw:IfId
(base:IfIndex)		An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100
passiveospfv3:PassiveControl
(scalar:Enum8)		Suppress routing updates on the interfaceSELECTION:
0 - none
1 - enabled
2 - disabled
DEFAULT: none


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 Routing Update Supression on the Interface

Deleting Routing Update Supression on the Interface

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

{
  "topSystem": {
    "children": [
      {
        "ospfv3Entity": {
          "children": [
            {
              "ospfv3If": {
                "attributes": {
                  "id": "eth1/8",
                  "passive": "disabled"
                }
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/8",
                  "medium": "p2p"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <ospfv3-items>
    <if-items>
      <If-list>
        <id>eth1/8</id>
        <passive>disabled</passive>
      </If-list>
    </if-items>
  </ospfv3-items>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/8</id>
        <medium>p2p</medium>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

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


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/8
 medium p2p
  no ospfv3 passive-interface


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

MODN
l1PhysIf sys/intf/phys-[eth1/8]
ospfv3If sys/ospfv3/if-[eth1/8]


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 NameData TypeDescriptionValues
idnw:IfId
(base:IfIndex)		An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100
mediuml1:Medium
(scalar:Enum8)		The administrative port medium type.SELECTION:
1 - broadcast
2 - p2p
DEFAULT: broadcast


ospfv3If Properties

The following table contains information about the ospfv3If properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
idnw:IfId
(base:IfIndex)		An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100
passiveospfv3:PassiveControl
(scalar:Enum8)		Suppress routing updates on the interfaceSELECTION:
0 - none
1 - enabled
2 - disabled
DEFAULT: none


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 an OSPF Broadcast Multi-Access Network

Configuring an OSPF Broadcast Multi-Access Network

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

{
  "topSystem": {
    "children": [
      {
        "ospfv3Entity": {
          "children": [
            {
              "ospfv3If": {
                "attributes": {
                  "id": "eth1/8",
                  "nwT": "bcast"
                }
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/8",
                  "medium": "p2p"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <ospfv3-items>
    <if-items>
      <If-list>
        <id>eth1/8</id>
        <nwT>bcast</nwT>
      </If-list>
    </if-items>
  </ospfv3-items>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/8</id>
        <medium>p2p</medium>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

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


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/8
 medium p2p
  ospfv3 network broadcast


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

MODN
l1PhysIf sys/intf/phys-[eth1/8]
ospfv3If sys/ospfv3/if-[eth1/8]


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 NameData TypeDescriptionValues
idnw:IfId
(base:IfIndex)		An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100
mediuml1:Medium
(scalar:Enum8)		The administrative port medium type.SELECTION:
1 - broadcast
2 - p2p
DEFAULT: broadcast


ospfv3If Properties

The following table contains information about the ospfv3If properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
idnw:IfId
(base:IfIndex)		An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100
nwTospfv3:NwT
(scalar:Enum8)		Network Type, can be Point-to-point or BroadcastSELECTION:
0 - none
1 - p2p
2 - bcast
DEFAULT: none


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 an OSPF Broadcast Multi-Access Network

Deleting an OSPF Broadcast Multi-Access Network

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

{
  "topSystem": {
    "children": [
      {
        "ospfv3Entity": {
          "children": [
            {
              "ospfv3If": {
                "attributes": {
                  "id": "eth1/8",
                  "nwT": "none"
                }
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/8",
                  "medium": "p2p"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <ospfv3-items>
    <if-items>
      <If-list>
        <id>eth1/8</id>
        <nwT>none</nwT>
      </If-list>
    </if-items>
  </ospfv3-items>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/8</id>
        <medium>p2p</medium>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

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


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/8
 medium p2p
  no ospfv3 network broadcast


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

MODN
l1PhysIf sys/intf/phys-[eth1/8]
ospfv3If sys/ospfv3/if-[eth1/8]


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 NameData TypeDescriptionValues
idnw:IfId
(base:IfIndex)		An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100
mediuml1:Medium
(scalar:Enum8)		The administrative port medium type.SELECTION:
1 - broadcast
2 - p2p
DEFAULT: broadcast


ospfv3If Properties

The following table contains information about the ospfv3If properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
idnw:IfId
(base:IfIndex)		An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100
nwTospfv3:NwT
(scalar:Enum8)		Network Type, can be Point-to-point or BroadcastSELECTION:
0 - none
1 - p2p
2 - bcast
DEFAULT: none


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 an OSPF Point-to-Point Network

Configuring an OSPF Point-to-Point Network

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

{
  "topSystem": {
    "children": [
      {
        "ospfv3Entity": {
          "children": [
            {
              "ospfv3If": {
                "attributes": {
                  "id": "eth1/8",
                  "nwT": "p2p"
                }
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/8",
                  "medium": "p2p"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <ospfv3-items>
    <if-items>
      <If-list>
        <id>eth1/8</id>
        <nwT>p2p</nwT>
      </If-list>
    </if-items>
  </ospfv3-items>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/8</id>
        <medium>p2p</medium>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

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


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/8
 medium p2p
  ospfv3 network point-to-point


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

MODN
l1PhysIf sys/intf/phys-[eth1/8]
ospfv3If sys/ospfv3/if-[eth1/8]


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 NameData TypeDescriptionValues
idnw:IfId
(base:IfIndex)		An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100
mediuml1:Medium
(scalar:Enum8)		The administrative port medium type.SELECTION:
1 - broadcast
2 - p2p
DEFAULT: broadcast


ospfv3If Properties

The following table contains information about the ospfv3If properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
idnw:IfId
(base:IfIndex)		An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100
nwTospfv3:NwT
(scalar:Enum8)		Network Type, can be Point-to-point or BroadcastSELECTION:
0 - none
1 - p2p
2 - bcast
DEFAULT: none


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 an OSPF Point-to-Point Network

Deleting an OSPF Point-to-Point Network

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

{
  "topSystem": {
    "children": [
      {
        "ospfv3Entity": {
          "children": [
            {
              "ospfv3If": {
                "attributes": {
                  "id": "eth1/8",
                  "nwT": "none"
                }
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/8",
                  "medium": "p2p"
                }
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <ospfv3-items>
    <if-items>
      <If-list>
        <id>eth1/8</id>
        <nwT>none</nwT>
      </If-list>
    </if-items>
  </ospfv3-items>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/8</id>
        <medium>p2p</medium>
      </PhysIf-list>
    </phys-items>
  </intf-items>
</System>

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


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/8
 medium p2p
  no ospfv3 network point-to-point


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

MODN
l1PhysIf sys/intf/phys-[eth1/8]
ospfv3If sys/ospfv3/if-[eth1/8]


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 NameData TypeDescriptionValues
idnw:IfId
(base:IfIndex)		An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100
mediuml1:Medium
(scalar:Enum8)		The administrative port medium type.SELECTION:
1 - broadcast
2 - p2p
DEFAULT: broadcast


ospfv3If Properties

The following table contains information about the ospfv3If properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
idnw:IfId
(base:IfIndex)		An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100
nwTospfv3:NwT
(scalar:Enum8)		Network Type, can be Point-to-point or BroadcastSELECTION:
0 - none
1 - p2p
2 - bcast
DEFAULT: none


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