Configuring RIP
RIP uses User Datagram Protocol (UDP) data packets to exchange routing information in small internetworks. RIPv2 supports IPv4. RIPv2 uses an optional authentication feature supported by the RIPv2 protocol. For more information, see Cisco Nexus 9000 Series NX-OS Unicast Routing Configuration Guide.
Enabling RIP
Enabling RIP
POST http://<mgmt0_IP>/api/mo/sys/acl/timerange.json
"topSystem": {
"children": [
{
"fmEntity": {
"children": [
{
"fmRip": {
"attributes": {
"adminSt": "enabled"
}
}
}
]
}
}
]
}
{
imdata:[]
}
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<edit-config>
<target>
<running/>
</target>
<config>
<System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
<fm-items>
<rip-items>
<adminSt>enabled</adminSt>
</rip-items>
</fm-items>
</System>
</config>
</edit-config>
</rpc>
Note: This example was added in Release 10.5(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.
feature rip
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 |
|---|---|
| fmRip | sys/fm/rip |
Properties
The following table contains information about the timerangeSEQ properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
| Property Name | Data Type | Description | Values |
|---|---|---|---|
| adminSt | fm: AdminState scalar: Enum8 | Admin status of RIP feature. | Selection: 1: enabled 2: disabled Default: disabled (2) |
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:
Creating RIP Instance
Creating RIP Instance
POST http://<mgmt0_IP>/api/mo/sys/acl/timerange.json
{
"topSystem": {
"children": [
{
"ripEntity": {
"children": [
{
"ripInst": {
"attributes": {
"name": "rip_1"
},
"children": [
{
"ripDom": {
"attributes": {
"name": "default"
}
}
}
]
}
}
]
}
}
]
}
}
{
imdata:[]
}
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<edit-config>
<target>
<running/>
</target>
<config>
<System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
<rip-items>
<inst-items>
<Inst-list>
<name>rip_1</name>
</Inst-list>
</inst-items>
</rip-items>
</System>
</config>
</edit-config>
</rpc>
Note: This example was added in Release 10.5(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.
router rip rip_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 |
|---|---|
| ripInst | sys/rip/inst- |
Properties
The following table contains information about the timerangeSEQ properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
| Property Name | Data Type | Description | Values |
|---|---|---|---|
| Name | naming: Name | Router RIP instance name. | MAX SIZE: 20 |
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:
Flushing RIP Routes
Flushing RIP Routes
POST http://<mgmt0_IP>/api/mo/sys/acl/timerange.json
{
"topSystem": {
"children": [
{
"ripEntity": {
"children": [
{
"ripInst": {
"attributes": {
"flushRoutes": "yes",
"name": "rip_1"
},
"children": [
{
"ripDom": {
"attributes": {
"name": "default"
}
}
}
]
}
}
]
}
}
]
}
}
{
imdata:[]
}
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<edit-config>
<target>
<running/>
</target>
<config>
<System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
<rip-items>
<inst-items>
<Inst-list>
<name>rip_1</name>
<flushRoutes>true</flushRoutes>
</Inst-list>
</inst-items>
</rip-items>
</System>
</config>
</edit-config>
</rpc>
Note: This example was added in Release 10.5(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.
router rip rip_1
flush-routes
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 |
|---|---|
| ripInst | sys/rip/inst- |
Properties
The following table contains information about the timerangeSEQ 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 |
|---|---|---|---|
| flushRoutes | Scalar:Bool | Flush routes in RIB during restart. | Selection: True or False Default: False |
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 RIP Instance Isolate
Configuring RIP Instance Isolate
POST http://<mgmt0_IP>/api/mo/sys/acl/timerange.json
{
"topSystem": {
"children": [
{
"ripEntity": {
"children": [
{
"ripInst": {
"attributes": {
"isolate": "yes",
"name": "rip_1"
},
"children": [
{
"ripDom": {
"attributes": {
"name": "default"
}
}
}
]
}
}
]
}
}
]
}
}
{
imdata:[]
}
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<edit-config>
<target>
<running/>
</target>
<config>
<System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
<rip-items>
<inst-items>
<Inst-list>
<name>rip_1</name>
<isolate>true</isolate>
</Inst-list>
</inst-items>
</rip-items>
</System>
</config>
</edit-config>
</rpc>
Note: This example was added in Release 10.5(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.
router rip rip_1
isolate
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 |
|---|---|
| ripInst | sys/rip/inst- |
Properties
The following table contains information about the timerangeSEQ 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 |
|---|---|---|---|
| isolate | scalar:Bool | Isolate this router from RIP. | Selection: True or False Default: False |
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 RIP Metric Direct
Configuring RIP Metric Direct
POST http://<mgmt0_IP>/api/mo/sys/acl/timerange.json
{
"topSystem": {
"children": [
{
"ripEntity": {
"children": [
{
"ripInst": {
"attributes": {
"metricDirect": "yes",
"name": "rip_1"
},
"children": [
{
"ripDom": {
"attributes": {
"name": "default"
}
}
}
]
}
}
]
}
}
]
}
}
{
imdata:[]
}
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<edit-config>
<target>
<running/>
</target>
<config>
<System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
<rip-items>
<inst-items>
<Inst-list>
<name>rip_1</name>
<metricDirect>true</metricDirect>
</Inst-list>
</inst-items>
</rip-items>
</System>
</config>
</edit-config>
</rpc>
Note: This example was added in Release 10.5(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.
router rip rip_1
metric direct 0
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 |
|---|---|
| ripInst | sys/rip/inst- |
Properties
The following table contains information about the timerangeSEQ 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 |
|---|---|---|---|
| metricDirect | scalar:Bool | Direct route cost is zero to be compatible with IOS. | Selection: True or False Default: False |
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 RIP VRF Instance
Configuring RIP VRF Instance
POST http://<mgmt0_IP>/api/mo/sys/acl/timerange.json
{
"topSystem": {
"children": [
{
"ripEntity": {
"children": [
{
"ripInst": {
"attributes": {
"metricDirect": "yes",
"name": "rip_1"
},
"children": [
{
"ripDom": {
"attributes": {
"name": "default"
}
}
}
]
}
}
]
}
}
]
}
}
{
imdata:[]
}
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<edit-config>
<target>
<running/>
</target>
<config>
<System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
<rip-items>
<inst-items>
<Inst-list>
<name>rip_1</name>
<metricDirect>true</metricDirect>
</Inst-list>
</inst-items>
</rip-items>
</System>
</config>
</edit-config>
</rpc>
Note: This example was added in Release 10.5(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.
router rip rip_1
metric direct 0
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 |
|---|---|
| ripInst | sys/rip/inst- |
Properties
The following table contains information about the timerangeSEQ 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 |
|---|---|---|---|
| metricDirect | scalar:Bool | Direct route cost is zero to be compatible with IOS. | Selection: True or False Default: False |
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 VRF Address Family for RIP Instance
Configuring VRF Address Family for RIP Instance
POST http://<mgmt0_IP>/api/mo/sys/acl/timerange.json
{
"topSystem": {
"children": [
{
"ripEntity": {
"children": [
{
"ripInst": {
"attributes": {
"name": "rip_1"
},
"children": [
{
"ripDom": {
"attributes": {
"name": "vrf_1"
},
"children": [
{
"ripDomAf": {
"attributes": {
"type": "ipv4-ucast"
}
}
}
]
}
},
{
"ripDom": {
"attributes": {
"name": "default"
}
}
}
]
}
}
]
}
}
]
}
}
{
imdata:[]
}
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<edit-config>
<target>
<running/>
</target>
<config>
<System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
<rip-items>
<inst-items>
<Inst-list>
<name>rip_1</name>
<dom-items>
<Dom-list>
<name>vrf_1</name>
<af-items>
<DomAf-list>
<type>ipv4-ucast</type>
</DomAf-list>
</af-items>
</Dom-list>
</dom-items>
</Inst-list>
</inst-items>
</rip-items>
</System>
</config>
</edit-config>
</rpc>
Note: This example was added in Release 10.5(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.
router rip rip_1
vrf vrf_1
address-family ipv4 unicast
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 |
|---|---|
| ripDomAf | sys/rip/inst- |
Properties
The following table contains information about the timerangeSEQ 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 |
|---|---|---|---|
| type | Rip:AfT scalar: Enum8 | configure address family. | Selection: 1: ipv4-ucast 2: ipv6-ucast |
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 RIP Address-family Distance
Configuring RIP Address-family Distance
POST http://<mgmt0_IP>/api/mo/sys/acl/timerange.json
{
"topSystem": {
"children": [
{
"ripEntity": {
"children": [
{
"ripInst": {
"attributes": {
"name": "rip_1"
},
"children": [
{
"ripDom": {
"attributes": {
"name": "vrf_1"
},
"children": [
{
"ripDomAf": {
"attributes": {
"distance": "200",
"type": "ipv6-ucast"
}
}
}
]
}
},
{
"ripDom": {
"attributes": {
"name": "default"
}
}
}
]
}
}
]
}
}
]
}
}
{
imdata:[]
}
<running/>
</target>
<config>
<System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
<rip-items>
<inst-items>
<Inst-list>
<name>rip_1</name>
<dom-items>
<Dom-list>
<name>vrf_1</name>
<af-items>
<DomAf-list>
<type>ipv6-ucast</type>
<distance>200</distance>
</DomAf-list>
</af-items>
</Dom-list>
</dom-items>
</Inst-list>
</inst-items>
</rip-items>
</System>
</config>
</edit-config>
</rpc>
Note: This example was added in Release 10.5(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.
router rip rip_1
vrf vrf_1
address-family ipv6 unicast
distance 200
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 |
|---|---|
| ripDomAf | sys/rip/inst-/ |
Properties
The following table contains information about the timerangeSEQ 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 |
|---|---|---|---|
| distance | scalar:UByte | Holds admin distance for routes. | Range [1:255] Default: 120 |
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 RIP Address Family Max-path
Configuring RIP Address Family Max-path
POST http://<mgmt0_IP>/api/mo/sys/acl/timerange.json
{
"topSystem": {
"children": [
{
"ripEntity": {
"children": [
{
"ripInst": {
"attributes": {
"name": "rip_1"
},
"children": [
{
"ripDom": {
"attributes": {
"name": "vrf_1"
},
"children": [
{
"ripDomAf": {
"attributes": {
"maxPaths": "50",
"type": "ipv6-ucast"
}
}
}
]
}
},
{
"ripDom": {
"attributes": {
"name": "default"
}
}
}
]
}
}
]
}
}
]
}
}
{
imdata:[]
}
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<edit-config>
<target>
<running/>
</target>
<config>
<System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
<rip-items>
<inst-items>
<Inst-list>
<name>rip_1</name>
<dom-items>
<Dom-list>
<name>vrf_1</name>
<af-items>
<DomAf-list>
<type>ipv6-ucast</type>
<distance/>
<maxPaths>50</maxPaths>
</DomAf-list>
</af-items>
</Dom-list>
</dom-items>
</Inst-list>
</inst-items>
</rip-items>
</System>
</config>
</edit-config>
</rpc>
Note: This example was added in Release 10.5(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.
router rip rip_1
vrf vrf_1
address-family ipv6 unicast
maximum-paths 50
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 |
|---|---|
| ripDomAf | sys/rip/inst-/ |
Properties
The following table contains information about the timerangeSEQ 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 |
|---|---|---|---|
| maxPaths | scalar:UByte | Holds maximum ECMP paths. | Range [1:64] Default: 16 |
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:
Disabling VRF
Enabling RIP
{
"topSystem": {
"children": [
{
"ripEntity": {
"children": [
{
"ripInst": {
"attributes": {
"name": "100"
},
"children": [
{
"ripDom": {
"attributes": {
"adminSt": "disabled",
"name": "vrf1"
}
}
},
{
"ripDom": {
"attributes": {
"name": "default"
}
}
}
]
}
}
]
}
}
]
}
}
{
imdata:[]
}
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<edit-config>
<target>
<running/>
</target>
<config>
<System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
<rip-items>
<inst-items>
<Inst-list>
<name>100</name>
<dom-items>
<Dom-list>
<name>vrf1</name>
<adminSt>disabled</adminSt>
</Dom-list>
</dom-items>
</Inst-list>
</inst-items>
</rip-items>
</System>
</config>
</edit-config>
</rpc>
Note: This example was added in Release 10.5(2).
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.
shutdown
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
| MO | DN |
|---|---|
| ripDom | sys/rip/inst- |
Properties
The following table contains information about the timerangeSEQ properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
| Property Name | Data Type | Description | Values |
|---|---|---|---|
| adminSt | scalar:Bool | Shutdown RIP instance on the vrf | Selection: True or False Default: False |
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:
Generating a Default Route into RIP
Generating a Default Route into RIP
{
"topSystem": {
"children": [
{
"ripEntity": {
"children": [
{
"ripInst": {
"attributes": {
"name": "100"
},
"children": [
{
"ripDom": {
"attributes": {
"name": "vrf1"
},
"children": [
{
"ripDomAf": {
"attributes": {
"type": "ipv4-ucast"
},
"children": [
{
"ripDefRtLeakP": {
"attributes": {
"always": "yes",
"rtMap": "pass"
}
}
}
]
}
}
]
}
},
{
"ripDom": {
"attributes": {
"name": "default"
}
}
}
]
}
}
]
}
}
]
}
}
{
imdata:[]
}
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<edit-config>
<target>
<running/>
</target>
<config>
<System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
<rip-items>
<inst-items>
<Inst-list>
<name>100</name>
<dom-items>
<Dom-list>
<name>vrf1</name>
<af-items>
<DomAf-list>
<type>ipv4-ucast</type>
<defrtleak-items>
<always>true</always>
<rtMap>pass</rtMap>
</defrtleak-items>
</DomAf-list>
</af-items>
</Dom-list>
</dom-items>
</Inst-list>
</inst-items>
</rip-items>
</System>
</config>
</edit-config>
</rpc>
Note: This example was added in Release 10.5(2).
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.
shutdown
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
| MO | DN |
|---|---|
| ripDefRtLeakP | sys/rip/inst- |
Properties
The following table contains information about the timerangeSEQ 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 |
|---|---|---|---|
| always | scalar:Bool | Always advertise default leak | Selection: True or False Default: False |
| rtMap | string: Basic | Policy to control distribution of default route | MAX SIZE: 63 |
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:
Redistributing IPv4
Redistributing IPv4
{
"topSystem": {
"children": [
{
"ripEntity": {
"children": [
{
"ripInst": {
"attributes": {
"name": "100"
},
"children": [
{
"ripDom": {
"attributes": {
"name": "vrf1"
},
"children": [
{
"ripDomAf": {
"attributes": {
"type": "ipv4-ucast"
},
"children": [
{
"ripInterLeakP": {
"attributes": {
"asn": "none",
"inst": "100",
"proto": "ospf",
"rtMap": "pass"
}
}
}
]
}
}
]
}
},
{
"ripDom": {
"attributes": {
"name": "default"
}
}
}
]
}
}
]
}
}
]
}
}
{
imdata:[]
}
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<edit-config>
<target>
<running/>
</target>
<config>
<System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
<rip-items>
<inst-items>
<Inst-list>
<name>100</name>
<dom-items>
<Dom-list>
<name>vrf1</name>
<af-items>
<DomAf-list>
<type>ipv4-ucast</type>
<interleak-items>
<InterLeakP-list>
<proto>ospf</proto>
<inst>100</inst>
<asn>none</asn>
<rtMap>pass</rtMap>
</InterLeakP-list>
</interleak-items>
</DomAf-list>
</af-items>
</Dom-list>
</dom-items>
</Inst-list>
</inst-items>
</rip-items>
</System>
</config>
</edit-config>
</rpc>
Note: This example was added in Release 10.5(2).
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.
redistribute ipv4
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 |
|---|---|
| ripInterLeakP | sys/rip/inst- |
Properties
The following table contains information about the timerangeSEQ 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 |
|---|---|---|---|
| proto | Scalar: Enum8 | - | Selection: 0: unspecified 1: static 2: direct 3: bgp 4: isis 5: ospf 7: eigrp 8: host 9: rip 10: amt 11: lisp |
| inst | string: Basic | Routing protocol instances | MAX SIZE: 20 |
| Asn | string: Basic | ASN number | Range: [1, 65535] Default: none |
| rtMap | string: Basic | Policy to control distribution of default route perspective | MAX SIZE: 63 Default: false |
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 Timers
Configuring Timers
{
"topSystem": {
"children": [
{
"ripEntity": {
"children": [
{
"ripInst": {
"attributes": {
"name": "100"
},
"children": [
{
"ripDom": {
"attributes": {
"name": "vrf1"
},
"children": [
{
"ripDomAf": {
"attributes": {
"garbageTimer": "500",
"holdTimer": "500",
"timeout": "500",
"type": "ipv4-ucast",
"updateTimer": "500"
}
}
}
]
}
},
{
"ripDom": {
"attributes": {
"name": "default"
}
}
}
]
}
}
]
}
}
]
}
}
{
imdata:[]
}
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<edit-config>
<target>
<running/>
</target>
<config>
<System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
<rip-items>
<inst-items>
<Inst-list>
<name>100</name>
<dom-items>
<Dom-list>
<name>vrf1</name>
<af-items>
<DomAf-list>
<type>ipv4-ucast</type>
<updateTimer>500</updateTimer>
<timeout>500</timeout>
<garbageTimer>500</garbageTimer>
<holdTimer>500</holdTimer>
</DomAf-list>
</af-items>
</Dom-list>
</dom-items>
</Inst-list>
</inst-items>
</rip-items>
</System>
</config>
</edit-config>
</rpc>
Note: This example was added in Release 10.5(2).
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.
timers
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 |
|---|---|
| ripDomAf | sys/rip/inst- |
Properties
The following table contains information about the timerangeSEQ 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 |
|---|---|---|---|
| updateTimer | scalar:Uint32 | Holds RIP update period config | Range:[5, 4294967295] Default: 30 |
| timeout | scalar:Uint32 | Holds RIP route timeout period config | Range:[1, 4294967295] Default: 180 |
| garbageTimer | scalar:Uint32 | Holds RIP route garbage period config | Range:[0, 4294967295] Default: 180 |
| holdTimer | scalar:Uint32 | Holds RIP route holddown period config | Range:[1, 4294967295] Default: 120 |
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 Maximum-paths
Configuring Maximum-paths
{
"topSystem": {
"children": [
{
"ripEntity": {
"children": [
{
"ripInst": {
"attributes": {
"name": "100"
},
"children": [
{
"ripDom": {
"attributes": {
"name": "vrf1"
},
"children": [
{
"ripDomAf": {
"attributes": {
"maxPaths": "30",
"type": "ipv4-ucast"
}
}
}
]
}
},
{
"ripDom": {
"attributes": {
"name": "default"
}
}
}
]
}
}
]
}
}
]
}
}
{
imdata:[]
}
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<edit-config>
<target>
<running/>
</target>
<config>
<System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
<rip-items>
<inst-items>
<Inst-list>
<name>100</name>
<dom-items>
<Dom-list>
<name>vrf1</name>
<af-items>
<DomAf-list>
<type>ipv4-ucast</type>
<maxPaths>30</maxPaths>
</DomAf-list>
</af-items>
</Dom-list>
</dom-items>
</Inst-list>
</inst-items>
</rip-items>
</System>
</config>
</edit-config>
</rpc>
Note: This example was added in Release 10.5(2).
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.
maximum-paths
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 |
|---|---|
| ripDomAf | sys/rip/inst-/ |
Properties
The following table contains information about the timerangeSEQ 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 |
|---|---|---|---|
| maxPaths | scalar:UByte | Holds maximum ECMP paths | Range [1:64] Default: 16 |
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 Default-metric
Configuring Default-metric
{
"topSystem": {
"children": [
{
"ripEntity": {
"children": [
{
"ripInst": {
"attributes": {
"name": "100"
},
"children": [
{
"ripDom": {
"attributes": {
"name": "vrf1"
},
"children": [
{
"ripDomAf": {
"attributes": {
"metric": "10",
"type": "ipv4-ucast"
}
}
}
]
}
},
{
"ripDom": {
"attributes": {
"name": "default"
}
}
}
]
}
}
]
}
}
]
}
}
{
imdata:[]
}
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<edit-config>
<target>
<running/>
</target>
<config>
<System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
<rip-items>
<inst-items>
<Inst-list>
<name>100</name>
<dom-items>
<Dom-list>
<name>vrf1</name>
<af-items>
<DomAf-list>
<type>ipv4-ucast</type>
<metric>10</metric>
</DomAf-list>
</af-items>
</Dom-list>
</dom-items>
</Inst-list>
</inst-items>
</rip-items>
</System>
</config>
</edit-config>
</rpc>
Note: This example was added in Release 10.5(2).
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.
default-metric 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 |
|---|---|
| ripDomAf | sys/rip/inst-/ |
Properties
The following table contains information about the timerangeSEQ 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 |
|---|---|---|---|
| metric | scalar:UByte | Rip Metric Value | Range [1:15] Default: 1 |
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 interface with RIPing Instance
Configuring interface with RIPing Instance
{
"topSystem": {
"children": [
{
"ripEntity": {
"children": [
{
"ripInst": {
"attributes": {
"name": "100"
},
"children": [
{
"ripDom": {
"attributes": {
"name": "default"
},
"children": [
{
"ripIf": {
"attributes": {
"id": "eth1/1"
},
"children": [
{
"ripIfAf": {
"attributes": {
"type": "ipv4-ucast"
}
}
}
]
}
}
]
}
}
]
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/1"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<edit-config>
<target>
<running/>
</target>
<config>
<System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
<rip-items>
<inst-items>
<Inst-list>
<name>100</name>
<dom-items>
<Dom-list>
<name>default</name>
<if-items>
<If-list>
<id>eth1/1</id>
</If-list>
</if-items>
</Dom-list>
</dom-items>
</Inst-list>
</inst-items>
</rip-items>
</System>
</config>
</edit-config>
</rpc>
Note: This example was added in Release 10.5(2).
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.
[no] {ip|ipv6} router rip <tag>
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 |
|---|---|
| ripIfAf | sys/rip/inst- |
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 RIP Shutdown
Configuring RIP Shutdown
{
"topSystem": {
"children": [
{
"ripEntity": {
"children": [
{
"ripInst": {
"attributes": {
"name": "100"
},
"children": [
{
"ripDom": {
"attributes": {
"name": "default"
},
"children": [
{
"ripIf": {
"attributes": {
"adminSt": "disabled",
"id": "eth1/1"
},
"children": [
{
"ripIfAf": {
"attributes": {
"type": "ipv4-ucast"
}
}
}
]
}
}
]
}
}
]
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/1"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<edit-config>
<target>
<running/>
</target>
<config>
<System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
<rip-items>
<inst-items>
<Inst-list>
<name>100</name>
<dom-items>
<Dom-list>
<name>default</name>
<if-items>
<If-list>
<id>eth1/1</id>
<adminSt>disabled</adminSt>
</If-list>
</if-items>
</Dom-list>
</dom-items>
</Inst-list>
</inst-items>
</rip-items>
</System>
</config>
</edit-config>
</rpc>
Note: This example was added in Release 10.5(2).
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.
rip shutdown
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
| MO | DN |
|---|---|
| ripIf | sys/rip/inst- |
Properties
The following table contains information about the timerangeSEQ 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 | Value | Description |
|---|---|---|---|
| adminSt | fm: AdminState scalar: Enum8 | Selection: 1: enabled 2: disabled Default: enabled (1) | Admin state of the RIP on If Af for rip instance shut on interface |
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 Summary Address for IPv4 RIP
Configuring Summary Address for IPv4 RIP
{
"topSystem": {
"children": [
{
"ripEntity": {
"children": [
{
"ripInst": {
"attributes": {
"name": "100"
},
"children": [
{
"ripDom": {
"attributes": {
"name": "default"
},
"children": [
{
"ripIf": {
"attributes": {
"id": "eth1/1"
},
"children": [
{
"ripIfAf": {
"attributes": {
"type": "ipv4-ucast"
},
"children": [
{
"ripRtSum": {
"attributes": {
"addr": "10.10.10.10/16"
}
}
}
]
}
}
]
}
}
]
}
}
]
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/1"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<edit-config>
<target>
<running/>
</target>
<config>
<System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
<rip-items>
<inst-items>
<Inst-list>
<name>100</name>
<dom-items>
<Dom-list>
<name>default</name>
<if-items>
<If-list>
<id>eth1/1</id>
<af-items>
<IfAf-list>
<type>ipv4-ucast</type>
<rtsum-items>
<RtSum-list>
<addr>10.10.10.10/16</addr>
</RtSum-list>
</rtsum-items>
</IfAf-list>
</af-items>
</If-list>
</if-items>
</Dom-list>
</dom-items>
</Inst-list>
</inst-items>
</rip-items>
</System>
</config>
</edit-config>
</rpc>
Note: This example was added in Release 10.5(2).
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.
rip shutdown
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
| MO | DN |
|---|---|
| ripRtSum | sys/rip/inst- |
Properties
The following table contains information about the timerangeSEQ 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 | Value | Description |
|---|---|---|---|
| addr | address:Ip | Prefix for summary address | Address to be used for summarization |
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 Authentication Type for RIP
Configuring Authentication Type for RIP
{
"topSystem": {
"children": [
{
"ripEntity": {
"children": [
{
"ripInst": {
"attributes": {
"name": "100"
},
"children": [
{
"ripDom": {
"attributes": {
"name": "default"
},
"children": [
{
"ripIf": {
"attributes": {
"id": "eth1/1"
},
"children": [
{
"ripIfAf": {
"attributes": {
"type": "ipv4-ucast"
},
"children": [
{
"ripAuthP": {
"attributes": {
"mode": "md5"
}
}
}
]
}
}
]
}
}
]
}
}
]
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/1"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<edit-config>
<target>
<running/>
</target>
<config>
<System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
<rip-items>
<inst-items>
<Inst-list>
<name>100</name>
<dom-items>
<Dom-list>
<name>default</name>
<if-items>
<If-list>
<id>eth1/1</id>
<af-items>
<IfAf-list>
<type>ipv4-ucast</type>
<auth-items>
<mode>md5</mode>
</auth-items>
</IfAf-list>
</af-items>
</If-list>
</if-items>
</Dom-list>
</dom-items>
</Inst-list>
</inst-items>
</rip-items>
</System>
</config>
</edit-config>
</rpc>
Note: This example was added in Release 10.5(2).
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.
ip rip authentication mode { text | 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 |
|---|---|
| ripAuthP | sys/rip/inst- |
Properties
The following table contains information about the timerangeSEQ 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 | Value | Description |
|---|---|---|---|
| mode | scalar:Enum8 | Selection: 0: none 1:text 2: md5 Default: none | Holds Authentication Mode |
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 Authentication Key for RIP
Configuring Authentication Type for RIP
{
"topSystem": {
"children": [
{
"ripEntity": {
"children": [
{
"ripInst": {
"attributes": {
"name": "100"
},
"children": [
{
"ripDom": {
"attributes": {
"name": "default"
},
"children": [
{
"ripIf": {
"attributes": {
"id": "eth1/1"
},
"children": [
{
"ripIfAf": {
"attributes": {
"type": "ipv4-ucast"
},
"children": [
{
"ripAuthP": {
"attributes": {
"keyChain": "key",
"mode": "md5"
}
}
}
]
}
}
]
}
}
]
}
}
]
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/1"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<edit-config>
<target>
<running/>
</target>
<config>
<System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
<rip-items>
<inst-items>
<Inst-list>
<name>100</name>
<dom-items>
<Dom-list>
<name>default</name>
<if-items>
<If-list>
<id>eth1/1</id>
<af-items>
<IfAf-list>
<type>ipv4-ucast</type>
<auth-items>
<mode>md5</mode>
<keyChain>key</keyChain>
</auth-items>
</IfAf-list>
</af-items>
</If-list>
</if-items>
</Dom-list>
</dom-items>
</Inst-list>
</inst-items>
</rip-items>
</System>
</config>
</edit-config>
</rpc>
Note: This example was added in Release 10.5(2).
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.
ip rip authentication key-chain <keychain>
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 |
|---|---|
| ripAuthP | sys/rip/inst- |
Properties
The following table contains information about the timerangeSEQ 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 | Value | Description |
|---|---|---|---|
| keyChain | string:Basic | MAXSIZE: 63 | Holds key chain name |
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 Passive Interface
Configuring Passive Interface
{
"topSystem": {
"children": [
{
"ripEntity": {
"children": [
{
"ripInst": {
"attributes": {
"name": "100"
},
"children": [
{
"ripDom": {
"attributes": {
"name": "default"
},
"children": [
{
"ripIf": {
"attributes": {
"id": "eth1/1"
},
"children": [
{
"ripIfAf": {
"attributes": {
"passive": "yes",
"type": "ipv4-ucast"
}
}
}
]
}
}
]
}
}
]
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/1"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<edit-config>
<target>
<running/>
</target>
<config>
<System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
<rip-items>
<inst-items>
<Inst-list>
<name>100</name>
<dom-items>
<Dom-list>
<name>default</name>
<if-items>
<If-list>
<id>eth1/1</id>
<af-items>
<IfAf-list>
<type>ipv4-ucast</type>
<passive>true</passive>
</IfAf-list>
</af-items>
</If-list>
</if-items>
</Dom-list>
</dom-items>
</Inst-list>
</inst-items>
</rip-items>
</System>
</config>
</edit-config>
</rpc>
Note: This example was added in Release 10.5(2).
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.
ip rip passive-interface
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
| MO | DN |
|---|---|
| ripIfAf | sys/rip/inst- |
Properties
The following table contains information about the timerangeSEQ 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 | Value | Description |
|---|---|---|---|
| passiveIntf | Scalar:Bool | TRUE or FALSE Default: FALSE | Toggles RIP interface passive interface |
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 Split Horizon with Poison Reverse
Configuring Split Horizon with Poison Reverse
{
"topSystem": {
"children": [
{
"ripEntity": {
"children": [
{
"ripInst": {
"attributes": {
"name": "100"
},
"children": [
{
"ripDom": {
"attributes": {
"name": "default"
},
"children": [
{
"ripIf": {
"attributes": {
"id": "eth1/1"
},
"children": [
{
"ripIfAf": {
"attributes": {
"poisonReverse": "yes",
"type": "ipv4-ucast"
}
}
}
]
}
}
]
}
}
]
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/1"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<edit-config>
<target>
<running/>
</target>
<config>
<System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
<rip-items>
<inst-items>
<Inst-list>
<name>100</name>
<dom-items>
<Dom-list>
<name>default</name>
<if-items>
<If-list>
<id>eth1/1</id>
<af-items>
<IfAf-list>
<type>ipv4-ucast</type>
<poisonReverse>true</poisonReverse>
</IfAf-list>
</af-items>
</If-list>
</if-items>
</Dom-list>
</dom-items>
</Inst-list>
</inst-items>
</rip-items>
</System>
</config>
</edit-config>
</rpc>
Note: This example was added in Release 10.5(2).
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.
ip/ipv6 rip poison-reverse
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 |
|---|---|
| ripIfAf | sys/rip/inst- |
Properties
The following table contains information about the timerangeSEQ 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 | Value | Description |
|---|---|---|---|
| poison | Scalar:Bool | TRUE or FALSE Default: FALSE | Toggles RIP poison reverse |
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: