Configuring a VLAN Interface
A VLAN interface, or switch virtual interface (SVI), is a virtual routed interface that connects a VLAN on the device to the Layer 3 router engine on the same device. Only one VLAN interface can be associated with a VLAN, but you need to configure a VLAN interface for a VLAN only when you want to route between VLANs or to provide IP host connectivity to the device through a virtual routing and forwarding (VRF) instance that is not the management VRF. When you enable VLAN interface creation, Cisco NX-OS creates a VLAN interface for the default VLAN (VLAN 1) to permit remote switch administration.
For more information, see the Cisco Nexus 9000 Series NX-OS Interfaces Configuration Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-installation-and-configuration-guides-list.html/
Note: Configuring SVIs requires enabling interface VLAN.
Enabling Interface VLAN
CLI Commands
The CLI commands and options listed below are the equivalent to the payload example displayed in the pane on the right.
feature interface-vlan
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
topSystem |
sys |
fmEntity |
sys/fm |
fmInterfaceVlan |
sys/fm/ifvlan |
fmInterfaceVlan Properties
The following table contains information about the fmInterfaceVlan properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | fm:AdminState (scalar:Enum8) | Admin status | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
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 Interface VLAN
CLI Commands
The CLI commands and options listed below are the equivalent to the payload example displayed in the pane on the right.
no feature interface-vlan
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
topSystem |
sys |
fmEntity |
sys/fm |
fmInterfaceVlan |
sys/fm/ifvlan |
fmInterfaceVlan Properties
The following table contains information about the fmInterfaceVlan properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | fm:AdminState (scalar:Enum8) | Admin status | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
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
Creating and Configuring an SVI Interface
This example creates an SVI named vlan1000.
CLI Commands
The CLI commands and options listed below are the equivalent to the payload example displayed in the pane on the right.
[no] interface vlan <vlan_id>
[no] shutdown
[no] autostate
bandwidth <bw>
carrier-delay <msec>
delay <msec>
description <string>
load-interval {interval seconds {1 | 2 | 3}}
mac-address <mac>
[no] management
medium { broadcast | p2p }
mtu <mtu>
[no] snmp trap link-status
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
sviIf |
sys/intf/svi-{[id]} |
sviIf Properties
The following table contains information about the sviIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
adminSt | l1:AdminSt (scalar:Enum8) | Administrative state | SELECTION: 1 - down 2 - up DEFAULT: down |
autostate | scalar:Bool
| Autostate Enabled? | SELECTION: true or false DEFAULT: true |
bw | svi:Bw (scalar:Uint32) | Specifies the administrative port bandwidth. | RANGE: [1 , 400000000] DEFAULT: 1000000 |
carDel | svi:CarrDelay (scalar:Uint32) | The hold period for which carrier transition, such as L2 interfacing going down, is ignored. | RANGE: [0 , 60000] DEFAULT: 100 |
delay | svi:Delay (scalar:Uint32) | Specifies the administrative port delay. | RANGE: [1 , 16777215] DEFAULT: 1 |
descr | naming:Descr1024 (string:Basic) | Tunnel Description | MAX SIZE: 254 |
inbMgmt | scalar:Bool
| An in-band management interface configuration. | SELECTION: true or false |
loadIntvl1 | svi:LoadIntvl1 (scalar:Uint32) | Load-averaging Interval 1 | RANGE: [60 , 600] DEFAULT: 60 |
mac | address:MAC
| The MAC address. | Value must match MM:MM:MM:SS:SS:SS format |
medium | svi:Medium (scalar:Enum8) | Indicates the administrative port medium type. | SELECTION: 0 - bcast 1 - p2p DEFAULT: bcast |
mtu | svi:Mtu (scalar:Uint32) | The administrative MTU port on the aggregated interface. | RANGE: [64 , 9216] DEFAULT: 1500 |
snmpTrap | scalar:Bool
| SNMP Trap Link Status Enabled? | SELECTION: true or false DEFAULT: true |
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
Querying an SVI Configuration
This example reads the configuration of the SVI named vlan1000
The HTTP request in this example queries the SVI configuration that was set in the previous example.
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
sviIf |
sys/intf/svi-{[id]} |
sviIf Properties
The following table contains information about the sviIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
adminSt | l1:AdminSt (scalar:Enum8) | Administrative state | SELECTION: 1 - down 2 - up DEFAULT: down |
autostate | scalar:Bool
| Autostate Enabled? | SELECTION: true or false DEFAULT: true |
bw | svi:Bw (scalar:Uint32) | Specifies the administrative port bandwidth. | RANGE: [1 , 400000000] DEFAULT: 1000000 |
carDel | svi:CarrDelay (scalar:Uint32) | The hold period for which carrier transition, such as L2 interfacing going down, is ignored. | RANGE: [0 , 60000] DEFAULT: 100 |
childAction | mo:ModificationChildAction scalar:Bitmask32 | Delete or ignore. For internal use only. | SELECTION:
16384u - deleteAll4096u - ignore8192u - deleteNonPresent DEFAULT: 0 |
delay | svi:Delay (scalar:Uint32) | Specifies the administrative port delay. | RANGE: [1 , 16777215] DEFAULT: 1 |
descr | naming:Descr1024 (string:Basic) | Tunnel Description | MAX SIZE: 254 |
dn | reference:BinRef | A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module. | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
inbMgmt | scalar:Bool
| An in-band management interface configuration. | SELECTION: true or false |
iod | scalar:Uint32
| Specifies the IOD. | RANGE: [0, 4294967295] |
loadIntvl1 | svi:LoadIntvl1 (scalar:Uint32) | Load-averaging Interval 1 | RANGE: [60 , 600] DEFAULT: 60 |
loadIntvl2 | svi:LoadIntvl2 (scalar:Uint32) | Load-averaging Interval 2 | RANGE: [60 , 600] DEFAULT: 300 |
loadIntvl3 | svi:LoadIntvl3 (scalar:Uint32) | Load-averaging Interval 3 | RANGE: [60 , 600] DEFAULT: 60 |
mac | address:MAC
| The MAC address. | Value must match MM:MM:MM:SS:SS:SS format |
medium | svi:Medium (scalar:Enum8) | Indicates the administrative port medium type. | SELECTION: 0 - bcast 1 - p2p DEFAULT: bcast |
modTs | mo:TStamp (scalar:Date) | The time when this object was last modified. | SELECTION: 0 - never DEFAULT: never |
monPolDn | reference:BinRef | | |
mtu | svi:Mtu (scalar:Uint32) | The administrative MTU port on the aggregated interface. | RANGE: [64 , 9216] DEFAULT: 1500 |
mtuInherit | scalar:Bool
| A property for specifying if the MTU is inherited from global policy. | SELECTION: true or false DEFAULT: true |
name | naming:Name256 (string:Basic) | The name of the object. | MAX SIZE: 63 |
operSt | svi:OperSt (scalar:Enum8) | The runtime state of the object or policy. | SELECTION: 0 - unknown 1 - up 2 - down 3 - shutdown 4 - out-of-srvc DEFAULT: down |
operStQual | svi:OperStQual (scalar:Enum8) | The chassis operational status qualifier. | SELECTION: 0 - unknown 1 - admin-shut 2 - no-vlan 3 - bad-vlan_t 4 - vlan-down 5 - hwprog-flfm 6 - hwprog-fles 7 - oos 8 - reinit 9 - mtuprog-fail 10 - vrf-unusable 11 - l2st-change 12 - suspended 13 - macalloc-fail 14 - nonrouted-vdc 15 - int-vlan-create-fail 16 - inbMgmt-cfg-fail DEFAULT: unknown |
osSum | nw:OSSum scalar:Enum8 | The operational state summary. | SELECTION:
0 - failed1 - initializing2 - resetting3 - degraded4 - ok DEFAULT: ok(4) |
persistentOnReload | mo:Persistent scalar:Enum8 | NO COMMENTS | SELECTION:
0 - false1 - true DEFAULT: true(1) |
snmpTrap | scalar:Bool
| SNMP Trap Link Status Enabled? | SELECTION: true or false DEFAULT: true |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
uid | scalar:Uint16 | A unique identifier for this object. | |
vlanId | svi:VlanId (scalar:Uint16) | The VLAN ID associated with the SVI. | RANGE: [0 , 4095] DEFAULT: 0 |
vlanT | l2:DomType (scalar:Enum8) | The VLAN type. | SELECTION: 1 - bd-regular 2 - bd-reserved 3 - bd-control 4 - bd-external 5 - ckt-vlan 6 - ckt-vxlan DEFAULT: bd-regular |
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 to Delete Adjacency On Mac Delete
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 vlan 1
ipv6 nd delete-adj-on-mac-delete
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
topSystem |
sys |
ndEntity |
sys/nd |
ndInst |
sys/nd/inst |
ndDom |
sys/nd/inst/dom-default |
ndIf |
sys/nd/inst/dom-default/if-[vlan1] |
interfaceEntity |
sys/intf |
sviIf |
sys/intf/svi-[vlan1] |
ndDom Properties
The following table contains information about the ndDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
name | naming:Name256 string:Basic | The name of the object. | RANGE:
Min: "1"
Max: "128" |
ndIf Properties
The following table contains information about the ndIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
delAdjOnMacDel | nw:AdminSt (scalar:Enum8) | Delete adj on mac delete notif without probe | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
sviIf Properties
The following table contains information about the sviIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Configuration to Delete Adjacency On Mac Delete
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 vlan 1
no ipv6 nd delete-adj-on-mac-delete
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
topSystem |
sys |
ndEntity |
sys/nd |
ndInst |
sys/nd/inst |
ndDom |
sys/nd/inst/dom-default |
ndIf |
sys/nd/inst/dom-default/if-[vlan1] |
interfaceEntity |
sys/intf |
sviIf |
sys/intf/svi-[vlan1] |
ndDom Properties
The following table contains information about the ndDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
name | naming:Name256 string:Basic | The name of the object. | RANGE:
Min: "1"
Max: "128" |
ndIf Properties
The following table contains information about the ndIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
delAdjOnMacDel | nw:AdminSt (scalar:Enum8) | Delete adj on mac delete notif without probe | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
sviIf Properties
The following table contains information about the sviIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Boot-file-url Option
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 vlan 1
ipv6 nd ra bootfile-url SampleString_123
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
topSystem |
sys |
ndEntity |
sys/nd |
ndInst |
sys/nd/inst |
ndDom |
sys/nd/inst/dom-default |
ndIf |
sys/nd/inst/dom-default/if-[vlan1] |
interfaceEntity |
sys/intf |
sviIf |
sys/intf/svi-[vlan1] |
ndDom Properties
The following table contains information about the ndDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
name | naming:Name256 string:Basic | The name of the object. | RANGE:
Min: "1"
Max: "128" |
ndIf Properties
The following table contains information about the ndIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
bootFileUrl | string:Basic
| The URL for a boot file in string | RANGE: [0 , 128] |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
sviIf Properties
The following table contains information about the sviIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Boot-file-url Option Configuration
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 vlan 1
no ipv6 nd ra bootfile-url SampleString_123
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
topSystem |
sys |
ndEntity |
sys/nd |
ndInst |
sys/nd/inst |
ndDom |
sys/nd/inst/dom-default |
ndIf |
sys/nd/inst/dom-default/if-[vlan1] |
interfaceEntity |
sys/intf |
sviIf |
sys/intf/svi-[vlan1] |
ndDom Properties
The following table contains information about the ndDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
name | naming:Name256 string:Basic | The name of the object. | RANGE:
Min: "1"
Max: "128" |
ndIf Properties
The following table contains information about the ndIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
bootFileUrl | string:Basic
| The URL for a boot file in string | RANGE: [0 , 128] |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
sviIf Properties
The following table contains information about the sviIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 to Disable Hardware Flooding
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 vlan 1
ipv6 nd local-proxy 1:2::3:4/24 no-hw-flooding
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
topSystem |
sys |
ndEntity |
sys/nd |
ndInst |
sys/nd/inst |
ndDom |
sys/nd/inst/dom-default |
ndIf |
sys/nd/inst/dom-default/if-[vlan1] |
ndNdLocalProxy |
sys/nd/inst/dom-default/if-[vlan1]/ndlocalproxy-[1:2::3:4/24] |
interfaceEntity |
sys/intf |
sviIf |
sys/intf/svi-[vlan1] |
ndDom Properties
The following table contains information about the ndDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
name | naming:Name256 string:Basic | The name of the object. | RANGE:
Min: "1"
Max: "128" |
ndIf Properties
The following table contains information about the ndIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
ndNdLocalProxy Properties
The following table contains information about the ndNdLocalProxy properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
prefix | address:Ip
| Prefix | Value must match ipv4 or ipv6 known format |
sviIf Properties
The following table contains information about the sviIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 Configuration for Disabling Hardware Flooding
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 vlan 1
no ipv6 nd local-proxy 1:2::3:4/24 no-hw-flooding
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
topSystem |
sys |
ndEntity |
sys/nd |
ndInst |
sys/nd/inst |
ndDom |
sys/nd/inst/dom-default |
ndIf |
sys/nd/inst/dom-default/if-[vlan1] |
ndNdLocalProxy |
sys/nd/inst/dom-default/if-[vlan1]/ndlocalproxy-[1:2::3:4/24] |
interfaceEntity |
sys/intf |
sviIf |
sys/intf/svi-[vlan1] |
ndDom Properties
The following table contains information about the ndDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
name | naming:Name256 string:Basic | The name of the object. | RANGE:
Min: "1"
Max: "128" |
ndIf Properties
The following table contains information about the ndIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
ndNdLocalProxy Properties
The following table contains information about the ndNdLocalProxy properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
prefix | address:Ip
| Prefix | Value must match ipv4 or ipv6 known format |
status | mo:ModificationStatus (scalar:Bitmask32) | Modification status | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
sviIf Properties
The following table contains information about the sviIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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
Installing the Secondary Subnet Routes as Drop Routes
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 vlan 1
ip drop-glean
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
topSystem |
sys |
ipv4Entity |
sys/ipv4 |
ipv4Inst |
sys/ipv4/inst |
ipv4Dom |
sys/ipv4/inst/dom-default |
ipv4If |
sys/ipv4/inst/dom-default/if-[vlan1] |
interfaceEntity |
sys/intf |
sviIf |
sys/intf/svi-[vlan1] |
ipv4Dom Properties
The following table contains information about the ipv4Dom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
name | naming:Name256 string:Basic | The name of the object. | RANGE:
Min: "1"
Max: "128" |
ipv4If Properties
The following table contains information about the ipv4If properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
dropGlean | nw:AdminSt (scalar:Enum8) | ip drop-glean enabled/disabled | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
sviIf Properties
The following table contains information about the sviIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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
Uninstalling the Secondary Subnet Routes as Drop Routes
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 vlan 1
no ip drop-glean
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
topSystem |
sys |
ipv4Entity |
sys/ipv4 |
ipv4Inst |
sys/ipv4/inst |
ipv4Dom |
sys/ipv4/inst/dom-default |
ipv4If |
sys/ipv4/inst/dom-default/if-[vlan1] |
interfaceEntity |
sys/intf |
sviIf |
sys/intf/svi-[vlan1] |
ipv4Dom Properties
The following table contains information about the ipv4Dom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
name | naming:Name256 string:Basic | The name of the object. | RANGE:
Min: "1"
Max: "128" |
ipv4If Properties
The following table contains information about the ipv4If properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
dropGlean | nw:AdminSt (scalar:Enum8) | ip drop-glean enabled/disabled | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
sviIf Properties
The following table contains information about the sviIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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
Enabling SVI Autostate for a VLAN Interface
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 vlan 1
autostate
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
interfaceEntity |
sys/intf |
sviIf |
sys/intf/svi-{[id]} |
sviIf Properties
The following table contains information about the sviIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
autostate | scalar:Bool
| Autostate Enabled? | SELECTION: true or false DEFAULT: true |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Disabling SVI Autostate for a VLAN Interface
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 vlan 1
no autostate
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
interfaceEntity |
sys/intf |
sviIf |
sys/intf/svi-{[id]} |
sviIf Properties
The following table contains information about the sviIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
autostate | scalar:Bool
| Autostate Enabled? | SELECTION: true or false DEFAULT: true |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html