Configuring IS-IS in Interface Configuration Mode
Configuring the Hello Authentication Type as Cleartext
Configuring the Hello Authentication Type as Cleartext
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"authType": "clear",
"dom": "default",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<authType>clear</authType>
<dom>default</dom>
</InternalIf-list>
</if-items>
</isis-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
isis authentication-type cleartext
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 |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
authType | isis:AuthT (scalar:Enum8) | Holds Authentication Type value for IS-IS Interface | SELECTION: 1 - clear 2 - md5 3 - unknown DEFAULT: unknown |
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the Hello Authentication Type as Cleartext
Deleting the Hello Authentication Type as Cleartext
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"authType": "unknown",
"dom": "",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<authType>unknown</authType>
<dom></dom>
</InternalIf-list>
</if-items>
</isis-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 isis authentication-type cleartext
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 |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
authType | isis:AuthT (scalar:Enum8) | Holds Authentication Type value for IS-IS Interface | SELECTION: 1 - clear 2 - md5 3 - unknown DEFAULT: unknown |
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring the Authentication Keychain for Level-1 IIHs (Cleartext)
Configuring the Authentication Keychain for Level-1 IIHs (Cleartext)
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"authTypeLvl1": "clear",
"dom": "default",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<authTypeLvl1>clear</authTypeLvl1>
<dom>default</dom>
</InternalIf-list>
</if-items>
</isis-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
isis authentication-type cleartext level-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.
MO | DN |
---|---|
topSystem | sys |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
authTypeLvl1 | isis:AuthT (scalar:Enum8) | Holds IS-IS Level-1 Authentication Type value for Interface | SELECTION: 1 - clear 2 - md5 3 - unknown DEFAULT: unknown |
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the Authentication Keychain for Level-1 IIHs (Cleartext)
Deleting the Authentication Keychain for Level-1 IIHs (Cleartext)
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"authTypeLvl1": "unknown",
"dom": "",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<authTypeLvl1>unknown</authTypeLvl1>
<dom></dom>
</InternalIf-list>
</if-items>
</isis-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 isis authentication-type cleartext level-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.
MO | DN |
---|---|
topSystem | sys |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
authTypeLvl1 | isis:AuthT (scalar:Enum8) | Holds IS-IS Level-1 Authentication Type value for Interface | SELECTION: 1 - clear 2 - md5 3 - unknown DEFAULT: unknown |
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring the Authentication Keychain for Level-2 IIHs (Cleartext)
Configuring the Authentication Keychain for Level-2 IIHs (Cleartext)
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"authTypeLvl2": "clear",
"dom": "default",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<authTypeLvl2>clear</authTypeLvl2>
<dom>default</dom>
</InternalIf-list>
</if-items>
</isis-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
isis authentication-type cleartext level-2
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 |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
authTypeLvl2 | isis:AuthT (scalar:Enum8) | Holds IS-IS Level-2 Authentication Type value for Interface | SELECTION: 1 - clear 2 - md5 3 - unknown DEFAULT: unknown |
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the Authentication Keychain for Level-2 IIHs (Cleartext)
Deleting the Authentication Keychain for Level-2 IIHs (Cleartext)
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"authTypeLvl2": "unknown",
"dom": "",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<authTypeLvl2>unknown</authTypeLvl2>
<dom></dom>
</InternalIf-list>
</if-items>
</isis-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 isis authentication-type cleartext level-2
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 |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
authTypeLvl2 | isis:AuthT (scalar:Enum8) | Holds IS-IS Level-2 Authentication Type value for Interface | SELECTION: 1 - clear 2 - md5 3 - unknown DEFAULT: unknown |
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring the Hello Authentication Type as HMAC-MD5
Configuring the Hello Authentication Type as HMAC-MD5
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"authType": "md5",
"dom": "default",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<authType>md5</authType>
<dom>default</dom>
</InternalIf-list>
</if-items>
</isis-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
isis authentication-type md5
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 |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
authType | isis:AuthT (scalar:Enum8) | Holds Authentication Type value for IS-IS Interface | SELECTION: 1 - clear 2 - md5 3 - unknown DEFAULT: unknown |
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the Hello Authentication Type as HMAC-MD5
Deleting the Hello Authentication Type as HMAC-MD5
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"authType": "unknown",
"dom": "",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<authType>unknown</authType>
<dom></dom>
</InternalIf-list>
</if-items>
</isis-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 isis authentication-type md5
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 |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
authType | isis:AuthT (scalar:Enum8) | Holds Authentication Type value for IS-IS Interface | SELECTION: 1 - clear 2 - md5 3 - unknown DEFAULT: unknown |
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring the Authentication Keychain for Level-1 IIHs (HMAC-MD5)
Configuring the Authentication Keychain for Level-1 IIHs (HMAC-MD5)
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"authTypeLvl1": "md5",
"dom": "default",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<authTypeLvl1>md5</authTypeLvl1>
<dom>default</dom>
</InternalIf-list>
</if-items>
</isis-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
isis authentication-type md5 level-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.
MO | DN |
---|---|
topSystem | sys |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
authTypeLvl1 | isis:AuthT (scalar:Enum8) | Holds IS-IS Level-1 Authentication Type value for Interface | SELECTION: 1 - clear 2 - md5 3 - unknown DEFAULT: unknown |
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the Authentication Keychain for Level-1 IIHs (HMAC-MD5)
Deleting the Authentication Keychain for Level-1 IIHs (HMAC-MD5)
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"authTypeLvl1": "unknown",
"dom": "",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<authTypeLvl1>unknown</authTypeLvl1>
<dom></dom>
</InternalIf-list>
</if-items>
</isis-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 isis authentication-type md5 level-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.
MO | DN |
---|---|
topSystem | sys |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
authTypeLvl1 | isis:AuthT (scalar:Enum8) | Holds IS-IS Level-1 Authentication Type value for Interface | SELECTION: 1 - clear 2 - md5 3 - unknown DEFAULT: unknown |
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring the Authentication Keychain for Level-2 IIHs (HMAC-MD5)
Configuring the Authentication Keychain for Level-2 IIHs (HMAC-MD5)
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"authTypeLvl2": "md5",
"dom": "default",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<authTypeLvl2>md5</authTypeLvl2>
<dom>default</dom>
</InternalIf-list>
</if-items>
</isis-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
isis authentication-type md5 level-2
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 |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
authTypeLvl2 | isis:AuthT (scalar:Enum8) | Holds IS-IS Level-2 Authentication Type value for Interface | SELECTION: 1 - clear 2 - md5 3 - unknown DEFAULT: unknown |
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the Authentication Keychain for Level-2 IIHs (HMAC-MD5)
Deleting the Authentication Keychain for Level-2 IIHs (HMAC-MD5)
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"authTypeLvl2": "unknown",
"dom": "",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<authTypeLvl2>unknown</authTypeLvl2>
<dom></dom>
</InternalIf-list>
</if-items>
</isis-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 isis authentication-type md5 level-2
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 |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
authTypeLvl2 | isis:AuthT (scalar:Enum8) | Holds IS-IS Level-2 Authentication Type value for Interface | SELECTION: 1 - clear 2 - md5 3 - unknown DEFAULT: unknown |
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring the Authentication Keychain for Level-1 IIHs (Metric Interface)
Configuring the Authentication Keychain for Level-1 IIHs (Metric Interface)
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "default",
"id": "eth1/2",
"metricLvl1": "1"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<dom>default</dom>
<metricLvl1>1</metricLvl1>
</InternalIf-list>
</if-items>
</isis-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
isis metric 1 level-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.
MO | DN |
---|---|
topSystem | sys |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
metricLvl1 | isis:Metric (scalar:Uint32) | Holds IS-IS interface Metric level-1 | RANGE: [0 , 16777216] DEFAULT: 16777216 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the Authentication Keychain for Level-1 IIHs (Metric Interface)
Deleting the Authentication Keychain for Level-1 IIHs (Metric Interface)
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "",
"id": "eth1/2",
"metricLvl1": "16777216"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<dom></dom>
<metricLvl1>16777216</metricLvl1>
</InternalIf-list>
</if-items>
</isis-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 isis metric 1 level-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.
MO | DN |
---|---|
topSystem | sys |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
metricLvl1 | isis:Metric (scalar:Uint32) | Holds IS-IS interface Metric level-1 | RANGE: [0 , 16777216] DEFAULT: 16777216 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring the Authentication Keychain for Level-2 IIHs (Metric Interface)
Configuring the Authentication Keychain for Level-2 IIHs (Metric Interface)
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "default",
"id": "eth1/2",
"metricLvl2": "1"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<dom>default</dom>
<metricLvl2>1</metricLvl2>
</InternalIf-list>
</if-items>
</isis-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
isis metric 1 level-2
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 |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
metricLvl2 | isis:Metric (scalar:Uint32) | Holds IS-IS interface Metric level-2 | RANGE: [0 , 16777216] DEFAULT: 16777216 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the Authentication Keychain for Level-2 IIHs (Metric Interface)
Deleting the Authentication Keychain for Level-2 IIHs (Metric Interface)
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "",
"id": "eth1/2",
"metricLvl2": "16777216"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<dom></dom>
<metricLvl2>16777216</metricLvl2>
</InternalIf-list>
</if-items>
</isis-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 isis metric 1 level-2
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 |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
metricLvl2 | isis:Metric (scalar:Uint32) | Holds IS-IS interface Metric level-2 | RANGE: [0 , 16777216] DEFAULT: 16777216 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring the Authentication Keychain for Level-1 IIHs (IPv6 Metric Interface)
Configuring the Authentication Keychain for Level-1 IIHs (IPv6 Metric Interface)
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "default",
"id": "eth1/2",
"mt2MetricLvl1": "1"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<dom>default</dom>
<mt2MetricLvl1>1</mt2MetricLvl1>
</InternalIf-list>
</if-items>
</isis-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
isis ipv6 metric 1 level-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.
MO | DN |
---|---|
topSystem | sys |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
mt2MetricLvl1 | isis:WideMetric (scalar:Uint32) | Holds IS-IS interface IPV6 wide metric value for Level-1 | RANGE: [0 , 16777216] DEFAULT: 16777216 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the Authentication Keychain for Level-1 IIHs (IPv6 Metric Interface)
Deleting the Authentication Keychain for Level-1 IIHs (IPv6 Metric Interface)
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "",
"id": "eth1/2",
"mt2MetricLvl1": "16777216"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<dom></dom>
<mt2MetricLvl1>16777216</mt2MetricLvl1>
</InternalIf-list>
</if-items>
</isis-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 isis ipv6 metric 1 level-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.
MO | DN |
---|---|
topSystem | sys |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
mt2MetricLvl1 | isis:WideMetric (scalar:Uint32) | Holds IS-IS interface IPV6 wide metric value for Level-1 | RANGE: [0 , 16777216] DEFAULT: 16777216 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring the Authentication Keychain for Level-2 IIHs (IPv6 Metric Interface)
Configuring the Authentication Keychain for Level-2 IIHs (IPv6 Metric Interface)
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "default",
"id": "eth1/2",
"mt2MetricLvl2": "1"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<dom>default</dom>
<mt2MetricLvl2>1</mt2MetricLvl2>
</InternalIf-list>
</if-items>
</isis-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
isis ipv6 metric 1 level-2
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 |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
mt2MetricLvl2 | isis:WideMetric (scalar:Uint32) | Holds IS-IS interface IPV6 wide metric value for Level-2 | RANGE: [0 , 16777216] DEFAULT: 16777216 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the Authentication Keychain for Level-2 IIHs (IPv6 Metric Interface)
Deleting the Authentication Keychain for Level-2 IIHs (IPv6 Metric Interface)
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "",
"id": "eth1/2",
"mt2MetricLvl2": "16777216"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<dom></dom>
<mt2MetricLvl2>16777216</mt2MetricLvl2>
</InternalIf-list>
</if-items>
</isis-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 isis ipv6 metric 1 level-2
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 |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
mt2MetricLvl2 | isis:WideMetric (scalar:Uint32) | Holds IS-IS interface IPV6 wide metric value for Level-2 | RANGE: [0 , 16777216] DEFAULT: 16777216 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring the Hello Authenticaiton Keychain for an Ethernet Interface
Configuring the Hello Authenticaiton Keychain for an Ethernet Interface
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"authKey": "SampleString_123",
"dom": "default",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<authKey>SampleString_123</authKey>
<dom>default</dom>
</InternalIf-list>
</if-items>
</isis-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
isis authentication key-chain 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 |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
authKey | isis:AuthKeyN (string:Basic) | Holds Authentication Key for IS-IS Interface | A sequence of characters |
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the Hello Authenticaiton Keychain for an Ethernet Interface
Deleting the Hello Authenticaiton Keychain for an Ethernet Interface
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"authKey": "",
"dom": "default",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<authKey></authKey>
<dom>default</dom>
</InternalIf-list>
</if-items>
</isis-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 isis authentication key-chain 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 |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
authKey | isis:AuthKeyN (string:Basic) | Holds Authentication Key for IS-IS Interface | A sequence of characters |
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring the Authentication Keychain for Level-1 IIHs on an Ethernet Interface
Configuring the Authentication Keychain for Level-1 IIHs on an Ethernet Interface
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"authKeyLvl1": "SampleString_123",
"dom": "default",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<authKeyLvl1>SampleString_123</authKeyLvl1>
<dom>default</dom>
</InternalIf-list>
</if-items>
</isis-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
isis authentication key-chain SampleString_123 level-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.
MO | DN |
---|---|
topSystem | sys |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
authKeyLvl1 | isis:AuthKeyN (string:Basic) | Holds Authentication Key for IS-IS Interface on Level-1 | A sequence of characters |
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the Authentication Keychain for Level-1 IIHs on an Ethernet Interface
Deleting the Authentication Keychain for Level-1 IIHs on an Ethernet Interface
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"authKeyLvl1": "",
"dom": "default",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<authKeyLvl1></authKeyLvl1>
<dom>default</dom>
</InternalIf-list>
</if-items>
</isis-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 isis authentication key-chain SampleString_123 level-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.
MO | DN |
---|---|
topSystem | sys |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
authKeyLvl1 | isis:AuthKeyN (string:Basic) | Holds Authentication Key for IS-IS Interface on Level-1 | A sequence of characters |
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring the Authentication Keychain for Level-2 IIHs on an Ethernet Interface
Configuring the Authentication Keychain for Level-2 IIHs on an Ethernet Interface
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"authKeyLvl2": "SampleString_123",
"dom": "default",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<authKeyLvl2>SampleString_123</authKeyLvl2>
<dom>default</dom>
</InternalIf-list>
</if-items>
</isis-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
isis authentication key-chain SampleString_123 level-2
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 |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
authKeyLvl2 | isis:AuthKeyN (string:Basic) | Holds Authentication Key for IS-IS Interface on Level-2 | A sequence of characters |
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the Authentication Keychain for Level-2 IIHs on an Ethernet Interface
Deleting the Authentication Keychain for Level-2 IIHs on an Ethernet Interface
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"authKeyLvl2": "",
"dom": "default",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<authKeyLvl2></authKeyLvl2>
<dom>default</dom>
</InternalIf-list>
</if-items>
</isis-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 isis authentication key-chain SampleString_123 level-2
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 |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
authKeyLvl2 | isis:AuthKeyN (string:Basic) | Holds Authentication Key for IS-IS Interface on Level-2 | A sequence of characters |
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring Pad IS-IS Hello PDUs to Full MTU on an Ethernet Interface
Configuring Pad IS-IS Hello PDUs to Full MTU on an Ethernet Interface
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "default",
"helloPad": "always",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<dom>default</dom>
<helloPad>always</helloPad>
</InternalIf-list>
</if-items>
</isis-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
isis hello-padding
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 |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
helloPad | isis:HelloPadT (scalar:Enum8) | Holds IS-IS Interface Hello Padding Info | SELECTION: 1 - always 2 - transient 3 - never DEFAULT: always |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring Pad Every Hello on an Ethernet Interface
Configuring Pad Every Hello on an Ethernet Interface
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "default",
"helloPad": "always",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<dom>default</dom>
<helloPad>always</helloPad>
</InternalIf-list>
</if-items>
</isis-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
isis hello-padding always
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 |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
helloPad | isis:HelloPadT (scalar:Enum8) | Holds IS-IS Interface Hello Padding Info | SELECTION: 1 - always 2 - transient 3 - never DEFAULT: always |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting Pad IS-IS Hello PDUs to Full MTU on an Ethernet Interface
Deleting Pad IS-IS Hello PDUs to Full MTU on an Ethernet Interface
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "default",
"helloPad": "transient",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<dom>default</dom>
<helloPad>transient</helloPad>
</InternalIf-list>
</if-items>
</isis-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 isis hello-padding
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 |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
helloPad | isis:HelloPadT (scalar:Enum8) | Holds IS-IS Interface Hello Padding Info | SELECTION: 1 - always 2 - transient 3 - never DEFAULT: always |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring MTU Check for Level-1 on an Ethernet Interface
Configuring MTU Check for Level-1 on an Ethernet Interface
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "default",
"id": "eth1/2",
"mtuCheckLvl1": "yes"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<dom>default</dom>
<mtuCheckLvl1>true</mtuCheckLvl1>
</InternalIf-list>
</if-items>
</isis-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
isis mtu-check level-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.
MO | DN |
---|---|
topSystem | sys |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
mtuCheckLvl1 | scalar:Bool | Enabling Mtu check for IS-IS interface at Level1 | SELECTION: true or false DEFAULT: no |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting MTU Check for Level-1 on an Ethernet Interface
Deleting MTU Check for Level-1 on an Ethernet Interface
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "default",
"id": "eth1/2",
"mtuCheckLvl1": "no"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<dom>default</dom>
<mtuCheckLvl1>false</mtuCheckLvl1>
</InternalIf-list>
</if-items>
</isis-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 isis mtu-check level-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.
MO | DN |
---|---|
topSystem | sys |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
mtuCheckLvl1 | scalar:Bool | Enabling Mtu check for IS-IS interface at Level1 | SELECTION: true or false DEFAULT: no |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring an MTU Check for Level-2 on an Ethernet Interface
Configuring an MTU Check for Level-2 on an Ethernet Interface
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "default",
"id": "eth1/2",
"mtuCheckLvl2": "yes"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<dom>default</dom>
<mtuCheckLvl2>true</mtuCheckLvl2>
</InternalIf-list>
</if-items>
</isis-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
isis mtu-check level-2
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 |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
mtuCheckLvl2 | scalar:Bool | Enabling Mtu check for IS-IS interface at Level2 | SELECTION: true or false DEFAULT: no |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting an MTU Check for Level-2 on an Ethernet Interface
Deleting an MTU Check for Level-2 on an Ethernet Interface
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "default",
"id": "eth1/2",
"mtuCheckLvl2": "no"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<dom>default</dom>
<mtuCheckLvl2>false</mtuCheckLvl2>
</InternalIf-list>
</if-items>
</isis-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 isis mtu-check level-2
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 |
isisEntity | sys/isis |
isisInternalIf | sys/isis/if-[eth1/2] |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-[eth1/2] |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
dom | isis:DomName (l3:VrfName) | Dom to which the interface belongs to | |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
mtuCheckLvl2 | scalar:Bool | Enabling Mtu check for IS-IS interface at Level2 | SELECTION: true or false DEFAULT: no |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring a BFD Interface
Configuring a BFD Interface
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "default",
"id": "eth1/2",
"v4Bfd": "enabled"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<v4Bfd>enabled</v4Bfd>
</InternalIf-list>
</if-items>
</isis-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
isis 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.
MO | DN |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
v4Bfd | isis:BfdT (scalar:Enum8) | Holds IS-IS Interface BFD Configruation | SELECTION: 1 - inheritVrf 2 - enabled 3 - disabled DEFAULT: inheritVrf |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting a BFD Interface
Deleting a BFD Interface
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "",
"id": "eth1/2",
"v4Bfd": "inheritVrf"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<v4Bfd>inheritVrf</v4Bfd>
</InternalIf-list>
</if-items>
</isis-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 isis 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.
MO | DN |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
v4Bfd | isis:BfdT (scalar:Enum8) | Holds IS-IS Interface BFD Configruation | SELECTION: 1 - inheritVrf 2 - enabled 3 - disabled DEFAULT: inheritVrf |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring a CSNP Interval as Level 1
Configuring a CSNP Interval as Level 1
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"csnpIntvlLvl1": "28658",
"dom": "default",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<csnpIntvlLvl1>28658</csnpIntvlLvl1>
</InternalIf-list>
</if-items>
</isis-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
isis csnp-interval 28658 level-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.
MO | DN |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
csnpIntvlLvl1 | isis:CsnpIntvl (scalar:Uint16) | Holds IS-IS Interface Level-1 CSNP Interval | RANGE: [1 , 65535] DEFAULT: 10 |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting a CSCNP Interval as Level 1
Deleting a CSCNP Interval as Level 1
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"csnpIntvlLvl1": "10",
"dom": "",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<csnpIntvlLvl1>10</csnpIntvlLvl1>
</InternalIf-list>
</if-items>
</isis-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 isis csnp-interval 28658 level-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.
MO | DN |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
csnpIntvlLvl1 | isis:CsnpIntvl (scalar:Uint16) | Holds IS-IS Interface Level-1 CSNP Interval | RANGE: [1 , 65535] DEFAULT: 10 |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring a CSCNP Interval as Level 2
Configuring a CSCNP Interval as Level 2
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"csnpIntvlLvl2": "28658",
"dom": "default",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<csnpIntvlLvl2>28658</csnpIntvlLvl2>
</InternalIf-list>
</if-items>
</isis-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
isis csnp-interval 28658 level-2
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 |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
csnpIntvlLvl2 | isis:CsnpIntvl (scalar:Uint16) | Holds IS-IS Interface Level-2 CSNP Interval | RANGE: [1 , 65535] DEFAULT: 10 |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting a CSCNP Interval as Level 2
Deleting a CSCNP Interval as Level 2
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"csnpIntvlLvl2": "10",
"dom": "",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<csnpIntvlLvl2>10</csnpIntvlLvl2>
</InternalIf-list>
</if-items>
</isis-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 isis csnp-interval 28658 level-2
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 |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
csnpIntvlLvl2 | isis:CsnpIntvl (scalar:Uint16) | Holds IS-IS Interface Level-2 CSNP Interval | RANGE: [1 , 65535] DEFAULT: 10 |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring the Hello Interval as Level 1 IIHs
Configuring the Hello Interval as Level 1 IIHs
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"helloIntvlLvl1": "8018",
"dom": "default",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<helloIntvlLvl1>8018</helloIntvlLvl1>
</InternalIf-list>
</if-items>
</isis-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
isis hello-interval 8018 level-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.
MO | DN |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
helloIntvlLvl1 | isis:HelloIntvl (scalar:Uint16) | Holds IS-IS interface Hello Interval Level-1 value | RANGE: [1 , 65535] DEFAULT: 10 |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the Hello Interval as Level 1 IIHs
Deleting the Hello Interval as Level 1 IIHs
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"helloIntvlLvl1": "10",
"dom": "",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<helloIntvlLvl1>10</helloIntvlLvl1>
</InternalIf-list>
</if-items>
</isis-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 isis hello-interval 8018 level-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.
MO | DN |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
helloIntvlLvl1 | isis:HelloIntvl (scalar:Uint16) | Holds IS-IS interface Hello Interval Level-1 value | RANGE: [1 , 65535] DEFAULT: 10 |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring the Hello Interval as Level 2 IIHs
Configuring the Hello Interval as Level 2 IIHs
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"helloIntvlLvl2": "8018",
"dom": "default",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<helloIntvlLvl2>8018</helloIntvlLvl2>
</InternalIf-list>
</if-items>
</isis-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
isis hello-interval 8018 level-2
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 |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
helloIntvlLvl2 | isis:HelloIntvl (scalar:Uint16) | Holds IS-IS interface Hello Interval Level-2 value | RANGE: [1 , 65535] DEFAULT: 10 |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the Hello Interval as Level 2 IIHs
Deleting the Hello Interval as Level 2 IIHs
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"helloIntvlLvl2": "10",
"dom": "",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<helloIntvlLvl2>10</helloIntvlLvl2>
</InternalIf-list>
</if-items>
</isis-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 isis hello-interval 8018 level-2
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 |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
helloIntvlLvl2 | isis:HelloIntvl (scalar:Uint16) | Holds IS-IS interface Hello Interval Level-2 value | RANGE: [1 , 65535] DEFAULT: 10 |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring the Multiplier for Hello Holding Time Level 1
Configuring the Multiplier for Hello Holding Time Level 1
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"helloMultLvl1": "528",
"dom": "default",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<helloMultLvl1>528</helloMultLvl1>
</InternalIf-list>
</if-items>
</isis-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
isis hello-multiplier 528 level-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.
MO | DN |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
helloMultLvl1 | isis:HelloMult (scalar:Uint16) | Holds IS-IS interface Hello Multiplier Level-1 value | RANGE: [3 , 1000] DEFAULT: 3 |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the Multiplier for Hello Holding Time Level 1
Deleting the Multiplier for Hello Holding Time Level 1
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"helloMultLvl1": "3",
"dom": "",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<helloMultLvl1>3</helloMultLvl1>
</InternalIf-list>
</if-items>
</isis-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 isis hello-multiplier 528 level-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.
MO | DN |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
helloMultLvl1 | isis:HelloMult (scalar:Uint16) | Holds IS-IS interface Hello Multiplier Level-1 value | RANGE: [3 , 1000] DEFAULT: 3 |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring the Multiplier for Hello Holding Time Level 2
Configuring the Multiplier for Hello Holding Time Level 2
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"helloMultLvl2": "528",
"dom": "default",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<helloMultLvl2>528</helloMultLvl2>
</InternalIf-list>
</if-items>
</isis-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
isis hello-multiplier 528 level-2
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 |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
helloMultLvl2 | isis:HelloMult (scalar:Uint16) | Holds IS-IS interface Hello Multiplier Level-2 value | RANGE: [3 , 1000] DEFAULT: 3 |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the Multiplier for Hello Holding Time Level 2
Deleting the Multiplier for Hello Holding Time Level 2
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"helloMultLvl2": "3",
"dom": "",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<helloMultLvl2>3</helloMultLvl2>
</InternalIf-list>
</if-items>
</isis-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 isis hello-multiplier 528 level-2
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 |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
helloMultLvl2 | isis:HelloMult (scalar:Uint16) | Holds IS-IS interface Hello Multiplier Level-2 value | RANGE: [3 , 1000] DEFAULT: 3 |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring BFD for IPv6
Configuring BFD for IPv6
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "default",
"id": "eth1/2",
"v6Bfd": "enabled"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<v6Bfd>enabled</v6Bfd>
</InternalIf-list>
</if-items>
</isis-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
isis ipv6 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.
MO | DN |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
v6Bfd | isis:BfdT (scalar:Enum8) | Holds Interface BFD Configruation for IPV6 family | SELECTION: 1 - inheritVrf 2 - enabled 3 - disabled DEFAULT: inheritVrf |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting BFD for IPv6
Deleting BFD for IPv6
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "",
"id": "eth1/2",
"v6Bfd": "inheritVrf"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<v6Bfd>inheritVrf</v6Bfd>
</InternalIf-list>
</if-items>
</isis-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 isis ipv6 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.
MO | DN |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
v6Bfd | isis:BfdT (scalar:Enum8) | Holds Interface BFD Configruation for IPV6 family | SELECTION: 1 - inheritVrf 2 - enabled 3 - disabled DEFAULT: inheritVrf |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring the Metric for IPv6 Topology
Configuring the Metric for IPv6 Topology
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "default",
"id": "eth1/2",
"mt2MetricLvl2": "1"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<mt2MetricLvl2>1</mt2MetricLvl2>
</InternalIf-list>
</if-items>
</isis-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
isis ipv6 metric 1 level-2
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 |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
mt2MetricLvl2 | isis:WideMetric (scalar:Uint32) | Holds IS-IS interface IPV6 wide metric value for Level-2 | RANGE: [0 , 16777216] DEFAULT: 16777216 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the Metric for IPv6 Topology
Deleting the Metric for IPv6 Topology
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "",
"id": "eth1/2",
"mt2MetricLvl2": "16777216"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<mt2MetricLvl2>16777216</mt2MetricLvl2>
</InternalIf-list>
</if-items>
</isis-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 isis ipv6 metric 1 level-2
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 |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
mt2MetricLvl2 | isis:WideMetric (scalar:Uint32) | Holds IS-IS interface IPV6 wide metric value for Level-2 | RANGE: [0 , 16777216] DEFAULT: 16777216 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring the MTU Check on Received Hellos (If Padded) as Level 1
Configuring the MTU Check on Received Hellos (If Padded) as Level 1
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "default",
"id": "eth1/2",
"mtuCheckLvl1": "yes"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<mtuCheckLvl1>true</mtuCheckLvl1>
</InternalIf-list>
</if-items>
</isis-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
isis mtu-check level-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.
MO | DN |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
mtuCheckLvl1 | scalar:Bool | Enabling Mtu check for IS-IS interface at Level1 | SELECTION: true or false DEFAULT: no |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the MTU Check on Received Hellos (If Padded) As Level 1
Deleting the MTU Check on Received Hellos (If Padded) As Level 1
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"id": "eth1/2",
"mtuCheckLvl1": "no"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<mtuCheckLvl1>false</mtuCheckLvl1>
</InternalIf-list>
</if-items>
</isis-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 isis mtu-check level-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.
MO | DN |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
mtuCheckLvl1 | scalar:Bool | Enabling Mtu check for IS-IS interface at Level1 | SELECTION: true or false DEFAULT: no |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring the MTU Check on Received Hellos (If Padded) as Level 2
Configuring the MTU Check on Received Hellos (If Padded) as Level 2
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "default",
"id": "eth1/2",
"mtuCheckLvl2": "yes"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<mtuCheckLvl2>true</mtuCheckLvl2>
</InternalIf-list>
</if-items>
</isis-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
isis mtu-check level-2
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 |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
mtuCheckLvl2 | scalar:Bool | Enabling Mtu check for IS-IS interface at Level2 | SELECTION: true or false DEFAULT: no |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the MTU Check on Received Hellos (If Padded) as Level 2
Deleting the MTU Check on Received Hellos (If Padded) as Level 2
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "",
"id": "eth1/2",
"mtuCheckLvl2": "no"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<mtuCheckLvl2>false</mtuCheckLvl2>
</InternalIf-list>
</if-items>
</isis-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 isis mtu-check level-2
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 |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
mtuCheckLvl2 | scalar:Bool | Enabling Mtu check for IS-IS interface at Level2 | SELECTION: true or false DEFAULT: no |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring Clear N Flag for Prefix
Configuring Clear N Flag for Prefix
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "default",
"id": "eth1/2",
"nFlagClear": "yes"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<nFlagClear>true</nFlagClear>
</InternalIf-list>
</if-items>
</isis-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
isis prefix-attributes n-flag-clear
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 |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
nFlagClear | scalar:Bool | Enabling N flag clear for IS-IS interface | SELECTION: true or false DEFAULT: no |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting Clear N Flag for Prefix
Deleting Clear N Flag for Prefix
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "",
"id": "eth1/2",
"nFlagClear": "no"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<nFlagClear>false</nFlagClear>
</InternalIf-list>
</if-items>
</isis-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 isis prefix-attributes n-flag-clear
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 |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
nFlagClear | scalar:Bool | Enabling N flag clear for IS-IS interface | SELECTION: true or false DEFAULT: no |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring the Priority for Level-1 Routing
Configuring the Priority for Level-1 Routing
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "default",
"id": "eth1/2",
"priorityLvl1": "1"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<priorityLvl1>1</priorityLvl1>
</InternalIf-list>
</if-items>
</isis-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
isis priority 1 level-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.
MO | DN |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
priorityLvl1 | isis:CktPrio (scalar:UByte) | Holds IS-IS Interface Level-1 Circuit Priority | RANGE: [0 , 127] DEFAULT: 64 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the Priority for Level-1 Routing
Deleting the Priority for Level-1 Routing
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "",
"id": "eth1/2",
"priorityLvl1": "64"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<priorityLvl1>64</priorityLvl1>
</InternalIf-list>
</if-items>
</isis-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 isis priority 1 level-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.
MO | DN |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
priorityLvl1 | isis:CktPrio (scalar:UByte) | Holds IS-IS Interface Level-1 Circuit Priority | RANGE: [0 , 127] DEFAULT: 64 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring the Priority for Level-2 Routing
Configuring the Priority for Level-2 Routing
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "default",
"id": "eth1/2",
"priorityLvl2": "1"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<priorityLvl2>1</priorityLvl2>
</InternalIf-list>
</if-items>
</isis-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
isis priority 1 level-2
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 |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
priorityLvl2 | isis:CktPrio (scalar:UByte) | Holds IS-IS Interface Level-2 Circuit Priority | RANGE: [0 , 127] DEFAULT: 64 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the Priority for Level-2 Routing
Deleting the Priority for Level-2 Routing
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "",
"id": "eth1/2",
"priorityLvl2": "64"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<priorityLvl2>64</priorityLvl2>
</InternalIf-list>
</if-items>
</isis-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 isis priority 1 level-2
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 |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
priorityLvl2 | isis:CktPrio (scalar:UByte) | Holds IS-IS Interface Level-2 Circuit Priority | RANGE: [0 , 127] DEFAULT: 64 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring to Pad IS-IS HellO PDUs to Full MTU
Configuring to Pad IS-IS HellO PDUs to Full MTU
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"helloPad": "always",
"dom": "default",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<helloPad>always</helloPad>
</InternalIf-list>
</if-items>
</isis-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
isis hello-padding
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 |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
helloPad | isis:HelloPadT (scalar:Enum8) | Holds IS-IS Interface Hello Padding Info | SELECTION: 1 - always 2 - transient 3 - never DEFAULT: always |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting to Pad IS-IS HellO PDUs to Full MTU
Deleting to Pad IS-IS HellO PDUs to Full MTU
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"helloPad": "transient",
"dom": "",
"id": "eth1/2"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<helloPad>transient</helloPad>
</InternalIf-list>
</if-items>
</isis-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 isis hello-padding
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 |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
---|---|---|---|
helloPad | isis:HelloPadT (scalar:Enum8) | Holds IS-IS Interface Hello Padding Info | SELECTION: 1 - always 2 - transient 3 - never DEFAULT: always |
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring IS-IS Mesh Group
Configuring IS-IS Mesh Group
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "default",
"id": "eth1/2"
},
"children": [
{
"isisMeshGrp": {
"attributes": {
"id": "1"
}
}
}
]
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<meshgrp-items>
<id>1</id>
</meshgrp-items>
</InternalIf-list>
</if-items>
</isis-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
isis mesh-group 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.
MO | DN |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
isisMeshGrp | sys/isis/if-eth1/2/meshgrp1 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
isisMeshGrp Properties
The following table contains information about the isisMeshGrp 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 | isis:MeshGrpId (scalar:Uint32) | Mesh Group Id | RANGE: [1 , 0xffffffff] |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting IS-IS Mesh Group
Deleting IS-IS Mesh Group
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "",
"id": "eth1/2"
},
"children": [
{
"isisMeshGrp": {
"attributes": {
"status": "deleted"
}
}
}
]
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<meshgrp-items nc:operation="delete">
</meshgrp-items>
</InternalIf-list>
</if-items>
</isis-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 isis mesh-group 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.
MO | DN |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
isisMeshGrp | sys/isis/if-eth1/2/meshgrp |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
isisMeshGrp Properties
The following table contains information about the isisMeshGrp 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 |
---|---|---|---|
status | mo:ModificationStatus (scalar:Bitmask32) | Modification status | 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 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:
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:
Configuring to Suppress IS-IS PDU Level 1 and Level 2
Configuring to Suppress IS-IS PDU Level 1 and Level 2
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "default",
"id": "eth1/2",
"passive": "l12"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<passive>l12</passive>
</InternalIf-list>
</if-items>
</isis-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
isis passive-interface level-1-2
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 |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
passive | isis:PassiveIntfT (scalar:Enum8) | Holds IS-IS Passive Interface Info | SELECTION: 1 - l1 2 - l2 3 - l12 4 - noL1 5 - noL2 6 - noL12 7 - inheritDef DEFAULT: inheritDef |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting to Suppress IS-IS PDU Level 1 and Level 2
Deleting to Suppress IS-IS PDU Level 1 and Level 2
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"isisEntity": {
"children": [
{
"isisInternalIf": {
"attributes": {
"dom": "",
"id": "eth1/2",
"passive": "noL12"
}
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<isis-items>
<if-items>
<InternalIf-list>
<id>eth1/2</id>
<passive>noL12</passive>
</InternalIf-list>
</if-items>
</isis-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 isis passive-interface level-1-2
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 |
---|---|
isisInternalIf | sys/isis/if-eth1/2 |
l1PhysIf | sys/intf/phys-eth1/2 |
topSystem | sys |
isisEntity | sys/isis |
interfaceEntity | sys/intf |
isisInternalIf Properties
The following table contains information about the isisInternalIf 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 |
passive | isis:PassiveIntfT (scalar:Enum8) | Holds IS-IS Passive Interface Info | SELECTION: 1 - l1 2 - l2 3 - l12 4 - noL1 5 - noL2 6 - noL12 7 - inheritDef DEFAULT: inheritDef |
l1PhysIf Properties
The following table contains information about the l1PhysIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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: