Configuring OSPFv3 on an Ethernet Interface

Configuring the IPv6 Routing Process to Not Include Secondary IPv6 Addresses

Configuring the IPv6 Routing Process to Not Include Secondary IPv6 Addresses
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "ospfv3Entity": {
          "children": [
            {
              "ospfv3If": {
                "attributes": {
                  "advSecondary": "no",
                  "area": "1.2.3.4",
                  "id": "eth1/2",
                  "instance": "SampleString_123"
                }
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <ospfv3-items>
    <if-items>
      <If-list>
        <id>eth1/2</id>
        <advSecondary>false</advSecondary>
        <area>1.2.3.4</area>
        <instance>SampleString_123</instance>
      </If-list>
    </if-items>
  </ospfv3-items>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/2</id>
      </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/2
 ipv6 router ospfv3 SampleString_123 area 1.2.3.4 secondaries none


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

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


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


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
advSecondaryscalar:Bool
Advertise secondary IPv6 addressesSELECTION: true or false
DEFAULT: true
areaospfv3:AreaId
(string:Basic)
Area associated with interfaceA sequence of characters
idnw:IfId
(base:IfIndex)
An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100
instanceospfv3:InstanceName
(naming:Name)
OSPFv3 instance name used with area command
MAX SIZE: 20


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 the Config to Not Include Secondary IPv6 Addresses

Deleting the Config to Not Include Secondary IPv6 Addresses
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "ospfv3Entity": {
          "children": [
            {
              "ospfv3If": {
                "attributes": {
                  "advSecondary": "yes",
                  "area": "",
                  "id": "eth1/2",
                  "instance": ""
                }
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <ospfv3-items>
    <if-items>
      <If-list>
        <id>eth1/2</id>
        <advSecondary>true</advSecondary>
        <area></area>
        <instance></instance>
      </If-list>
    </if-items>
  </ospfv3-items>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/2</id>
      </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/2
 no ipv6 router ospfv3 SampleString_123 area 1.2.3.4 secondaries none


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

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


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


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
advSecondaryscalar:Bool
Advertise secondary IPv6 addressesSELECTION: true or false
DEFAULT: true
areaospfv3:AreaId
(string:Basic)
Area associated with interfaceA sequence of characters
idnw:IfId
(base:IfIndex)
An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100
instanceospfv3:InstanceName
(naming:Name)
OSPFv3 instance name used with area command
MAX SIZE: 20


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 OSPF MTU Mismatch Detection

Disabling OSPF MTU Mismatch Detection
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "ospfv3Entity": {
          "children": [
            {
              "ospfv3If": {
                "attributes": {
                  "id": "eth1/2",
                  "mtuIgnore": "yes"
                }
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <ospfv3-items>
    <if-items>
      <If-list>
        <id>eth1/2</id>
        <mtuIgnore>true</mtuIgnore>
      </If-list>
    </if-items>
  </ospfv3-items>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/2</id>
      </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/2
 ospfv3 mtu-ignore


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/2]
ospfv3If sys/ospfv3/if-[eth1/2]


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


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
mtuIgnorescalar:Bool
Disable OSPF MTU mismatch detectionSELECTION: true or false


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 the Config for Disabling OSPF MTU Mismatch Detection

Deleting the Config for Disabling OSPF MTU Mismatch Detection
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "ospfv3Entity": {
          "children": [
            {
              "ospfv3If": {
                "attributes": {
                  "id": "eth1/2",
                  "mtuIgnore": "no"
                }
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <ospfv3-items>
    <if-items>
      <If-list>
        <id>eth1/2</id>
        <mtuIgnore>false</mtuIgnore>
      </If-list>
    </if-items>
  </ospfv3-items>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/2</id>
      </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/2
 no ospfv3 mtu-ignore


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/2]
ospfv3If sys/ospfv3/if-[eth1/2]


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


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
mtuIgnorescalar:Bool
Disable OSPF MTU mismatch detectionSELECTION: true or false


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 OSPF Shutdown on this Interface

Configuring OSPF Shutdown on this Interface
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "ospfv3Entity": {
          "children": [
            {
              "ospfv3If": {
                "attributes": {
                  "adminSt": "disabled",
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/2"
                }
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <ospfv3-items>
    <if-items>
      <If-list>
        <id>eth1/2</id>
        <adminSt>disabled</adminSt>
      </If-list>
    </if-items>
  </ospfv3-items>
  <intf-items>
    <phys-items>
      <PhysIf-list>
        <id>eth1/2</id>
      </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/2
 ospfv3 shutdown


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/2]
ospfv3If sys/ospfv3/if-[eth1/2]


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


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
adminSt
nw:IfAdminSt
scalar:Enum8
The administrative state of the object or policy.SELECTION:
  • 1 - enabled
  • 2 - disabled
  • DEFAULT: enabled(1)
  • idnw: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 OSPF Shutdown on this Interface

    Deleting OSPF Shutdown on this Interface
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "adminSt": "enabled",
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/2</id>
            <adminSt>enabled</adminSt>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <PhysIf-list>
            <id>eth1/2</id>
          </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/2
     no ospfv3 shutdown


    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/2]
    ospfv3If sys/ospfv3/if-[eth1/2]


    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


    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
    adminSt
    nw:IfAdminSt
    scalar:Enum8
    The administrative state of the object or policy.SELECTION:
  • 1 - enabled
  • 2 - disabled
  • DEFAULT: enabled(1)
  • idnw:IfId
    (base:IfIndex)
    An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100


    Related Documentation

    For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

    http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

    See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

    https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

    https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Configuring the Cost Associated with Interface

    Configuring the Cost Associated with Interface 
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "cost": "15994",
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/2</id>
            <cost>15994</cost>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <PhysIf-list>
            <id>eth1/2</id>
          </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/2
     ospfv3 cost 15994


    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/2]
    ospfv3If sys/ospfv3/if-[eth1/2]


    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


    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
    costospfv3:IfCost
    (scalar:Uint16)
    Cost associated with interface
    RANGE: [0 , 65535]
    DEFAULT: unspecified
    idnw: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 the Cost Associated with Interface

    Deleting the Cost Associated with Interface 
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "cost": "unspecified",
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/2</id>
            <cost>0</cost>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <PhysIf-list>
            <id>eth1/2</id>
          </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/2
     no ospfv3 cost 15994


    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/2]
    ospfv3If sys/ospfv3/if-[eth1/2]


    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


    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
    costospfv3:IfCost
    (scalar:Uint16)
    Cost associated with interface
    RANGE: [0 , 65535]
    DEFAULT: unspecified
    idnw:IfId
    (base:IfIndex)
    An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100


    Related Documentation

    For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

    http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

    See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

    https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

    https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Configuring the Dead Interval

    Configuring the Dead Interval 
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "deadIntvl": "41985",
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/2</id>
            <deadIntvl>41985</deadIntvl>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <PhysIf-list>
            <id>eth1/2</id>
          </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/2
     ospfv3 dead-interval 41985


    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/2]
    ospfv3If sys/ospfv3/if-[eth1/2]


    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


    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
    deadIntvlospfv3:DeadIntvl
    (scalar:Uint32)
    Dead interval, interval during which at least one hello packet must be received from a neighbor before the router declares that neighbor as down
    RANGE: [0 , 65535]
    DEFAULT: unspecified
    idnw: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 the Dead Interval

    Deleting the Dead Interval 
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "deadIntvl": "unspecified",
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/2</id>
            <deadIntvl>0</deadIntvl>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <PhysIf-list>
            <id>eth1/2</id>
          </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/2
     no ospfv3 dead-interval 41985


    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/2]
    ospfv3If sys/ospfv3/if-[eth1/2]


    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


    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
    deadIntvlospfv3:DeadIntvl
    (scalar:Uint32)
    Dead interval, interval during which at least one hello packet must be received from a neighbor before the router declares that neighbor as down
    RANGE: [0 , 65535]
    DEFAULT: unspecified
    idnw:IfId
    (base:IfIndex)
    An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100


    Related Documentation

    For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

    http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

    See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

    https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

    https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Configuring the Hello Interval

    Configuring the Hello Interval 
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "helloIntvl": "47323",
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/2</id>
            <helloIntvl>47323</helloIntvl>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <PhysIf-list>
            <id>eth1/2</id>
          </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/2
     ospfv3 hello-interval 47323


    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/2]
    ospfv3If sys/ospfv3/if-[eth1/2]


    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


    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
    helloIntvlospfv3:HelloIntvl
    (scalar:Uint16)
    Interval between hello packets that OSPFv3 sends on the interface
    RANGE: [1 , 65535]
    DEFAULT: 10
    idnw: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 the Hello Interval

    Deleting the Hello Interval 
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "helloIntvl": "10",
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/2</id>
            <helloIntvl>10</helloIntvl>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <PhysIf-list>
            <id>eth1/2</id>
          </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/2
     no ospfv3 hello-interval 47323


    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/2]
    ospfv3If sys/ospfv3/if-[eth1/2]


    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


    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
    helloIntvlospfv3:HelloIntvl
    (scalar:Uint16)
    Interval between hello packets that OSPFv3 sends on the interface
    RANGE: [1 , 65535]
    DEFAULT: 10
    idnw: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 an Instance Id

    Configuring an Instance Id
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "id": "eth1/2",
                      "instanceId": "1"
                    }
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/2</id>
            <instanceId>1</instanceId>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <PhysIf-list>
            <id>eth1/2</id>
          </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/2
     ospfv3 instance 1


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

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


    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


    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
    instanceIdospfv3:InstanceID
    (scalar:UByte)
    OSPFv3 instance identifier under interface
    RANGE: [0 , 255]
    DEFAULT: 0


    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 Instance Id

    Deleting an Instance Id
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "id": "eth1/2",
                      "instanceId": "0"
                    }
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/2</id>
            <instanceId>0</instanceId>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <PhysIf-list>
            <id>eth1/2</id>
          </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/2
     no ospfv3 instance 1


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

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


    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


    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
    instanceIdospfv3:InstanceID
    (scalar:UByte)
    OSPFv3 instance identifier under interface
    RANGE: [0 , 255]
    DEFAULT: 0


    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 Router Priority

    Configuring the Router Priority
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "id": "eth1/2",
                      "prio": "1"
                    }
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/2</id>
            <prio>1</prio>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <PhysIf-list>
            <id>eth1/2</id>
          </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/2
     ospfv3 priority 1


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

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


    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


    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
    prioospfv3:DesigPrio
    (scalar:UByte)
    Router priority, used in determining the designated router on this network
    RANGE: [0 , 255]
    DEFAULT: 1


    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 the Router Priority

    Deleting the Router Priority
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "id": "eth1/2",
                      "prio": "1"
                    }
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/2</id>
            <prio>1</prio>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <PhysIf-list>
            <id>eth1/2</id>
          </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/2
     no ospfv3 priority 1


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

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


    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


    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
    prioospfv3:DesigPrio
    (scalar:UByte)
    Router priority, used in determining the designated router on this network
    RANGE: [0 , 255]
    DEFAULT: 1


    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 Retransmission Interval

    Configuring Packet Retransmission Interval 
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "id": "eth1/2",
                      "reTxIntvl": "9126"
                    }
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/2</id>
            <reTxIntvl>9126</reTxIntvl>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <PhysIf-list>
            <id>eth1/2</id>
          </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/2
     ospfv3 retransmit-interval 9126


    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/2]
    ospfv3If sys/ospfv3/if-[eth1/2]


    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


    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
    reTxIntvlospfv3:ReTxIntvl
    (scalar:Uint16)
    Retransmit interval, the time between LSA retransmissions
    RANGE: [1 , 65535]
    DEFAULT: 5


    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 Retransmission Interval

    Deleting Packet Retransmission Interval 
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "id": "eth1/2",
                      "reTxIntvl": "5"
                    }
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/2</id>
            <reTxIntvl>5</reTxIntvl>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <PhysIf-list>
            <id>eth1/2</id>
          </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/2
     no ospfv3 retransmit-interval 9126


    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/2]
    ospfv3If sys/ospfv3/if-[eth1/2]


    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


    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
    reTxIntvlospfv3:ReTxIntvl
    (scalar:Uint16)
    Retransmit interval, the time between LSA retransmissions
    RANGE: [1 , 65535]
    DEFAULT: 5


    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 Transmission Delay

    Configuring Packet Transmission Delay 
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "id": "eth1/2",
                      "txDelay": "376"
                    }
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/2</id>
            <txDelay>376</txDelay>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <PhysIf-list>
            <id>eth1/2</id>
          </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/2
     ospfv3 transmit-delay 376


    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/2]
    ospfv3If sys/ospfv3/if-[eth1/2]


    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


    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
    txDelayospfv3:TxDelay
    (scalar:Uint16)
    Transmit delay, estimated time needed to send an LSA update packet
    RANGE: [1 , 450]
    DEFAULT: 1


    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 Transmission Delay

    Deleting Packet Transmission Delay 
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "id": "eth1/2",
                      "txDelay": "1"
                    }
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/2</id>
            <txDelay>1</txDelay>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <PhysIf-list>
            <id>eth1/2</id>
          </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/2
     no ospfv3 transmit-delay 376


    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/2]
    ospfv3If sys/ospfv3/if-[eth1/2]


    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


    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
    txDelayospfv3:TxDelay
    (scalar:Uint16)
    Transmit delay, estimated time needed to send an LSA update packet
    RANGE: [1 , 450]
    DEFAULT: 1


    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 BFD on the Interface
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "bfdCtrl": "unspecified",
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/2</id>
            <bfdCtrl>unspecified</bfdCtrl>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <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
      no ospfv3 bfd


    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
    topSystem sys
    ospfv3Entity sys/ospfv3
    ospfv3If sys/ospfv3/if-[eth1/2]
    interfaceEntity sys/intf
    l1PhysIf sys/intf/phys-[eth1/2]


    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
    bfdCtrlospfv3:BfdControl
    (scalar:Enum8)
    Bidirectional Forwarding Detection (BFD) controlSELECTION:
    0 - unspecified
    1 - enabled
    2 - disabled
    DEFAULT: unspecified
    idnw:IfId
    (base:IfIndex)
    An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100


    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


    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 Multi-Area Associated with Interface

    Configuring Multi-Area Associated with Interface
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "id": "eth1/2"
                    },
                    "children": [
                      {
                        "ospfv3MultiArea": {
                          "attributes": {
                            "multiareaid": "1.2.3.4"
                          }
                        }
                      }
                    ]
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/2</id>
            <multiarea-items>
              <MultiArea-list>
                <multiareaid>1.2.3.4</multiareaid>
              </MultiArea-list>
            </multiarea-items>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <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
      ipv6 router ospfv3 SampleString_123 multi-area 1.2.3.4


    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
    topSystem sys
    ospfv3Entity sys/ospfv3
    ospfv3If sys/ospfv3/if-[eth1/2]
    ospfv3MultiArea sys/ospfv3/if-[eth1/2]/multiarea-1.2.3.4
    interfaceEntity sys/intf
    l1PhysIf sys/intf/phys-[eth1/2]


    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


    ospfv3MultiArea Properties

    The following table contains information about the ospfv3MultiArea 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
    multiareaidospfv3:AreaId
    (string:Basic)
    Holds multi area identifier (ID)A sequence of characters


    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


    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 Multi-Area Associated with Interface

    Deleting Multi-Area Associated with Interface
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "id": "eth1/2"
                    },
                    "children": [
                      {
                        "ospfv3MultiArea": {
                          "attributes": {
                            "multiareaid": "1.2.3.4",
                            "status": "deleted"
                          }
                        }
                      }
                    ]
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/2</id>
            <multiarea-items>
              <MultiArea-list nc:operation="delete">
                <multiareaid>1.2.3.4</multiareaid>
              </MultiArea-list>
            </multiarea-items>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <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
      no ipv6 router ospfv3 SampleString_123 multi-area 1.2.3.4


    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
    topSystem sys
    ospfv3Entity sys/ospfv3
    ospfv3If sys/ospfv3/if-[eth1/2]
    ospfv3MultiArea sys/ospfv3/if-[eth1/2]/multiarea-1.2.3.4
    interfaceEntity sys/intf
    l1PhysIf sys/intf/phys-[eth1/2]


    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


    ospfv3MultiArea Properties

    The following table contains information about the ospfv3MultiArea 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
    multiareaidospfv3:AreaId
    (string:Basic)
    Holds multi area identifier (ID)A sequence of characters
    statusmo:ModificationStatus
    (scalar:Bitmask32)
    The upgrade status. This property is for internal use only.SELECTION:
    2 - created
    4 - modified
    8 - deleted
    16 - replaced


    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


    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

    Configure ospfv3 authentication disable

    Configure ospfv3 authentication disable  
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "id": "eth1/2"
                    },
                    "children": [
                      {
                        "ospfv3IfAuthNewP": {
                          "attributes": {
                            "authType": "disable"
                          }
                        }
                      }
                    ]
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/2</id>
            <auth-items>
              <authType>disable</authType>
            </auth-items>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <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 Ethernet1/2
      ospfv3 authentication disable


    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
    topSystem sys
    ospfv3Entity sys/ospfv3
    ospfv3If sys/ospfv3/if-[eth1/2]
    ospfv3IfAuthNewP sys/ospfv3/if-[eth1/2]/auth
    interfaceEntity sys/intf
    l1PhysIf sys/intf/phys-[eth1/2]


    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


    ospfv3IfAuthNewP Properties

    The following table contains information about the ospfv3IfAuthNewP 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
    authTypeospfv3:AuthType
    (scalar:Enum8)
    Authentication types which can be md5, sha1 or disable.SELECTION:
    0 - none
    1 - md5
    2 - sha1
    3 - disable


    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


    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

    Delete ospfv3 authentication disable

    Delete ospfv3 authentication disable  
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "id": "eth1/2"
                    },
                    "children": [
                      {
                        "ospfv3IfAuthNewP": {
                          "attributes": {
                            "authType": "disable"
                          }
                        }
                      }
                    ]
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/2</id>
            <auth-items>
              <authType>disable</authType>
            </auth-items>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <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 Ethernet1/2
      no ospfv3 authentication disable

    Configure ospfv3 authentication ipsec spi spi_id md5 authentication key

    Configure ospfv3 authentication ipsec spi spi_id md5 authentication key
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "id": "eth1/1"
                    },
                    "children": [
                      {
                        "ospfv3IfAuthNewP": {
                          "attributes": {
                            "authKey": "762bc328e3bdf23528634c34c4ee38d6e2113d0f74c1176d75968a592447ede0",
                            "authKeyEncrType": "3des",
                            "authType": "md5",
                            "spi": "4294967293"
                          }
                        }
                      }
                    ]
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/1"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/1</id>
            <auth-items>
              <authKey>762bc328e3bdf23528634c34c4ee38d6e2113d0f74c1176d75968a592447ede0</authKey>
              <authKeyEncrType>3des</authKeyEncrType>
              <authType>md5</authType>
              <spi>4294967293</spi>
            </auth-items>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <PhysIf-list>
            <id>eth1/1</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 Ethernet1/1
      ospfv3 authentication ipsec spi 4294967293 md5 3 762bc328e3bdf23528634c34c4ee38d6e2113d0f74c1176d75968a592447ede0


    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
    topSystem sys
    ospfv3Entity sys/ospfv3
    ospfv3If sys/ospfv3/if-[eth1/1]
    ospfv3IfAuthNewP sys/ospfv3/if-[eth1/1]/auth
    interfaceEntity sys/intf
    l1PhysIf sys/intf/phys-[eth1/1]


    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


    ospfv3IfAuthNewP Properties

    The following table contains information about the ospfv3IfAuthNewP 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
    authKeyospfv3:AuthKey
    (string:Password)
    Key used for authentication
    authKeyEncrTypeospfv3:AuthKeyEncrType
    (scalar:Enum8)
    Authentication key encryption type which can be Cleartext, 3DES or CiscoType7SELECTION:
    0 - cleartext
    3 - 3des
    7 - cisco-type-7
    DEFAULT: cleartext
    authTypeospfv3:AuthType
    (scalar:Enum8)
    Authentication types which can be md5, sha1 or disable.SELECTION:
    0 - none
    1 - md5
    2 - sha1
    3 - disable
    spiospfv3:AuthSpi
    (scalar:Uint32)
    Security Parameter Index
    RANGE: [256 , 4294967295]


    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


    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 ospfv3 authentication ipsec spi spi_id md5 authentication key

    Deleting ospfv3 authentication ipsec spi spi_id md5 authentication key
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "id": "eth1/1"
                    },
                    "children": [
                      {
                        "ospfv3IfAuthNewP": {
                          "attributes": {
                            "status": "deleted"
                          }
                        }
                      }
                    ]
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/1"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/1</id>
            <auth-items nc:operation="delete">
            </auth-items>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <PhysIf-list>
            <id>eth1/1</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 Ethernet1/1
      no ospfv3 authentication ipsec spi 4294967293 md5 3 762bc328e3bdf23528634c34c4ee38d6e2113d0f74c1176d75968a592447ede0


    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
    topSystem sys
    ospfv3Entity sys/ospfv3
    ospfv3If sys/ospfv3/if-[eth1/1]
    ospfv3IfAuthNewP sys/ospfv3/if-[eth1/1]/auth
    interfaceEntity sys/intf
    l1PhysIf sys/intf/phys-[eth1/1]


    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


    ospfv3IfAuthNewP Properties

    The following table contains information about the ospfv3IfAuthNewP 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
    authKeyospfv3:AuthKey
    (string:Password)
    Key used for authentication
    authKeyEncrTypeospfv3:AuthKeyEncrType
    (scalar:Enum8)
    Authentication key encryption type which can be Cleartext, 3DES or CiscoType7SELECTION:
    0 - cleartext
    3 - 3des
    7 - cisco-type-7
    DEFAULT: cleartext
    authTypeospfv3:AuthType
    (scalar:Enum8)
    Authentication types which can be md5, sha1 or disable.SELECTION:
    0 - none
    1 - md5
    2 - sha1
    3 - disable
    spiospfv3:AuthSpi
    (scalar:Uint32)
    Security Parameter Index
    RANGE: [256 , 4294967295]


    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


    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

    Configure ospfv3 authentication ipsec spi spi_id sha1 authentication key

    Configure ospfv3 authentication ipsec spi spi_id sha1 authentication key 
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "id": "eth1/1"
                    },
                    "children": [
                      {
                        "ospfv3IfAuthNewP": {
                          "attributes": {
                            "authKey": "762bc328e3bdf2352a976463948902c115ecc62a7c1270a00de09adb4dd4a8cbc5f2769f1fa9c847",
                            "authKeyEncrType": "3des",
                            "authType": "sha1",
                            "spi": "4294967292"
                          }
                        }
                      }
                    ]
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/1"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/1</id>
            <auth-items>
              <authKey>762bc328e3bdf2352a976463948902c115ecc62a7c1270a00de09adb4dd4a8cbc5f2769f1fa9c847</authKey>
              <authKeyEncrType>3des</authKeyEncrType>
              <authType>sha1</authType>
              <spi>4294967292</spi>
            </auth-items>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <PhysIf-list>
            <id>eth1/1</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 Ethernet1/1
      ospfv3 authentication ipsec spi 4294967292 sha1 3 762bc328e3bdf2352a976463948902c115ecc62a7c1270a00de09adb4dd4a8cbc5f2769f1fa9c847


    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
    topSystem sys
    ospfv3Entity sys/ospfv3
    ospfv3If sys/ospfv3/if-[eth1/1]
    ospfv3IfAuthNewP sys/ospfv3/if-[eth1/1]/auth
    interfaceEntity sys/intf
    l1PhysIf sys/intf/phys-[eth1/1]


    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


    ospfv3IfAuthNewP Properties

    The following table contains information about the ospfv3IfAuthNewP 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
    authKeyospfv3:AuthKey
    (string:Password)
    Key used for authentication
    authKeyEncrTypeospfv3:AuthKeyEncrType
    (scalar:Enum8)
    Authentication key encryption type which can be Cleartext, 3DES or CiscoType7SELECTION:
    0 - cleartext
    3 - 3des
    7 - cisco-type-7
    DEFAULT: cleartext
    authTypeospfv3:AuthType
    (scalar:Enum8)
    Authentication types which can be md5, sha1 or disable.SELECTION:
    0 - none
    1 - md5
    2 - sha1
    3 - disable
    spiospfv3:AuthSpi
    (scalar:Uint32)
    Security Parameter Index
    RANGE: [256 , 4294967295]


    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


    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 ospfv3 authentication ipsec spi spi_id sha1 authentication key

    Deleting ospfv3 authentication ipsec spi spi_id sha1 authentication key 
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "id": "eth1/1"
                    },
                    "children": [
                      {
                        "ospfv3IfAuthNewP": {
                          "attributes": {
                            "status": "deleted"
                          }
                        }
                      }
                    ]
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/1"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/1</id>
            <auth-items nc:operation="delete">
            </auth-items>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <PhysIf-list>
            <id>eth1/1</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 Ethernet1/1
      no ospfv3 authentication ipsec spi 4294967292 sha1 3 762bc328e3bdf2352a976463948902c115ecc62a7c1270a00de09adb4dd4a8cbc5f2769f1fa9c847


    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
    topSystem sys
    ospfv3Entity sys/ospfv3
    ospfv3If sys/ospfv3/if-[eth1/1]
    ospfv3IfAuthNewP sys/ospfv3/if-[eth1/1]/auth
    interfaceEntity sys/intf
    l1PhysIf sys/intf/phys-[eth1/1]


    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


    ospfv3IfAuthNewP Properties

    The following table contains information about the ospfv3IfAuthNewP 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
    authKeyospfv3:AuthKey
    (string:Password)
    Key used for authentication
    authKeyEncrTypeospfv3:AuthKeyEncrType
    (scalar:Enum8)
    Authentication key encryption type which can be Cleartext, 3DES or CiscoType7SELECTION:
    0 - cleartext
    3 - 3des
    7 - cisco-type-7
    DEFAULT: cleartext
    authTypeospfv3:AuthType
    (scalar:Enum8)
    Authentication types which can be md5, sha1 or disable.SELECTION:
    0 - none
    1 - md5
    2 - sha1
    3 - disable
    spiospfv3:AuthSpi
    (scalar:Uint32)
    Security Parameter Index
    RANGE: [256 , 4294967295]


    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


    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 BFD on the Interface

    Configuring BFD on the Interface
    
    'feature bfd' is required for these commands.
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "bfdCtrl": "enabled",
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/2</id>
            <bfdCtrl>enabled</bfdCtrl>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <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
      ospfv3 bfd


    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
    topSystem sys
    ospfv3Entity sys/ospfv3
    ospfv3If sys/ospfv3/if-[eth1/2]
    interfaceEntity sys/intf
    l1PhysIf sys/intf/phys-[eth1/2]


    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
    bfdCtrlospfv3:BfdControl
    (scalar:Enum8)
    Bidirectional Forwarding Detection (BFD) controlSELECTION:
    0 - unspecified
    1 - enabled
    2 - disabled
    DEFAULT: unspecified
    idnw:IfId
    (base:IfIndex)
    An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100


    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


    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 BFD on the Interface

    Deleting BFD on the Interface
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "ospfv3Entity": {
              "children": [
                {
                  "ospfv3If": {
                    "attributes": {
                      "bfdCtrl": "unspecified",
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          },
          {
            "interfaceEntity": {
              "children": [
                {
                  "l1PhysIf": {
                    "attributes": {
                      "id": "eth1/2"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        
    }
    
    <System>
      <ospfv3-items>
        <if-items>
          <If-list>
            <id>eth1/2</id>
            <bfdCtrl>unspecified</bfdCtrl>
          </If-list>
        </if-items>
      </ospfv3-items>
      <intf-items>
        <phys-items>
          <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
      no ospfv3 bfd


    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
    topSystem sys
    ospfv3Entity sys/ospfv3
    ospfv3If sys/ospfv3/if-[eth1/2]
    interfaceEntity sys/intf
    l1PhysIf sys/intf/phys-[eth1/2]


    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
    bfdCtrlospfv3:BfdControl
    (scalar:Enum8)
    Bidirectional Forwarding Detection (BFD) controlSELECTION:
    0 - unspecified
    1 - enabled
    2 - disabled
    DEFAULT: unspecified
    idnw:IfId
    (base:IfIndex)
    An identifier .Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100


    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


    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