Configuring Unicast RPF for IPv4
This section contains payload examples and CLIs to demonstrate how to use the NX-API REST API to configure Unicast RPF on Cisco Nexus 3000 and 9000 Series switches and to show how the REST APIs correspond to the CLI commands. For more information, see the Cisco Nexus 9000 Series NX-OS Security Configuration Guide.
Configuring Loose Unicast RPF for IPv4 Packets on a Cisco Nexus 9500 Series Switch with an -R Line Card
Configuring Loose Unicast RPF for IPv4 Packets on a Cisco Nexus 9500 Series Switch with an -R Line Card
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ipv4Entity": {
"children": [
{
"ipv4Inst": {
"children": [
{
"ipv4Dom": {
"attributes": {
"name": "default"
},
"children": [
{
"ipv4If": {
"attributes": {
"id": "eth2/3",
"urpf": "loose"
},
"children": [
{
"ipv4Addr": {
"attributes": {
"addr": "172.23.231.240/23"
}}}]}}]}}]}}]}}]}}
{
imdata:[]
}
<System>
<ipv4-items>
<inst-items>
<dom-items>
<Dom-list>
<name>default</name>
<if-items>
<If-list>
<id>eth2/3</id>
<urpf>loose</urpf>
<addr-items>
<Addr-list>
<addr>172.23.231.240/23</addr>
</Addr-list>
</addr-items>
</If-list>
</if-items>
</Dom-list>
</dom-items>
</inst-items>
</ipv4-items>
</System>
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 Ethernet2/3
ip address 172.23.231.240/23
ip verify unicast source reachable-via any
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
topSystem | sys |
ipv4Entity | sys/ipv4 |
ipv4Inst | sys/ipv4/inst |
ipv4Dom | sys/ipv4/inst/dom-{name} |
ipv4If | sys/ipv4/inst/dom-{name}/if-{[id]} |
ipv4Addr | sys/ipv4/inst/dom-{name}/if-{[id]}/addr-{[addr]} |
ipv4Dom Properties
The following table contains information about the ipv4Dom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
name | naming:Name256 (string:Basic) | The name of the object. | MAX SIZE: 63 |
ipv4If Properties
The following table contains information about the ipv4If properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
urpf | ip:UrpfT (scalar:Enum8) | URPF Info | SELECTION: 0 - disabled 1 - strict 2 - loose 3 - loose-allow-default 4 - strict-allow-vni-hosts DEFAULT: disabled |
ipv4Addr Properties
The following table contains information about the ipv4Addr properties in the DME 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 |
---|---|---|---|
addr | address:Ip | Address | Value must match ipv4 or ipv6 known format |
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 Loose Unicast RPF for IPv4 Packets on a Cisco Nexus 9500 Series Switch with an -R Line Card
Disabling Loose Unicast RPF for IPv4 Packets on a Cisco Nexus 9500 Series Switch with an -R Line Card
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ipv4Entity": {
"children": [
{
"ipv4Inst": {
"children": [
{
"ipv4Dom": {
"attributes": {
"name": "default"
},
"children": [
{
"ipv4If": {
"attributes": {
"id": "eth2/3",
"urpf": "disabled"
},
"children": [
{
"ipv4Addr": {
"attributes": {
"addr": "172.23.231.240/23"
}}}]}}]}}]}}]}}]}}
{
imdata:[]
}
<System>
<ipv4-items>
<inst-items>
<dom-items>
<Dom-list>
<name>default</name>
<if-items>
<If-list>
<id>eth2/3</id>
<urpf>disabled</urpf>
<addr-items>
<Addr-list>
<addr>172.23.231.240/23</addr>
</Addr-list>
</addr-items>
</If-list>
</if-items>
</Dom-list>
</dom-items>
</inst-items>
</ipv4-items>
</System>
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 Ethernet2/3
ip address 172.23.231.240/23
no ip verify unicast source reachable-via any
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
topSystem | sys |
ipv4Entity | sys/ipv4 |
ipv4Inst | sys/ipv4/inst |
ipv4Dom | sys/ipv4/inst/dom-{name} |
ipv4If | sys/ipv4/inst/dom-{name}/if-{[id]} |
ipv4Addr | sys/ipv4/inst/dom-{name}/if-{[id]}/addr-{[addr]} |
ipv4Dom Properties
The following table contains information about the ipv4Dom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
name | naming:Name256 (string:Basic) | The name of the object. | MAX SIZE: 63 |
ipv4If Properties
The following table contains information about the ipv4If properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
urpf | ip:UrpfT (scalar:Enum8) | URPF Info | SELECTION: 0 - disabled 1 - strict 2 - loose 3 - loose-allow-default 4 - strict-allow-vni-hosts DEFAULT: disabled |
ipv4Addr Properties
The following table contains information about the ipv4Addr properties in the DME 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 |
---|---|---|---|
addr | address:Ip | Address | Value must match ipv4 or ipv6 known format |
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 Loose Unicast RPF for IPv4 Packets on a Cisco Nexus 9300 Series Switch
Configuring Loose Unicast RPF for IPv4 Packets on a Cisco Nexus 9300 Series Switch
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ipv4Entity": {
"children": [
{
"ipv4Inst": {
"children": [
{
"ipv4Dom": {
"attributes": {
"name": "default"
},
"children": [
{
"ipv4If": {
"attributes": {
"id": "eth2/3",
"urpf": "loose"
},
"children": [
{
"ipv4Addr": {
"attributes": {
"addr": "172.23.231.240/23"
}
}
}
]
}
}
]
}
}
]
}
}
]
}
},
{
"platformEntity": {
"attributes": {
"urpfStatus": "disabled"
}}}]}}
{
imdata:[]
}
<System>
<ipv4-items>
<inst-items>
<dom-items>
<Dom-list>
<name>default</name>
<if-items>
<If-list>
<id>eth2/3</id>
<urpf>loose</urpf>
<addr-items>
<Addr-list>
<addr>172.23.231.240/23</addr>
</Addr-list>
</addr-items>
</If-list>
</if-items>
</Dom-list>
</dom-items>
</inst-items>
</ipv4-items>
<pltfm-items>
<urpfStatus>disabled</urpfStatus>
</pltfm-items>
</System>
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.
system urpf disable
interface Ethernet2/3
ip address 172.23.231.240/23
ip verify unicast source reachable-via any
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
topSystem | sys |
ipv4Entity | sys/ipv4 |
ipv4Inst | sys/ipv4/inst |
ipv4Dom | sys/ipv4/inst/dom-{name} |
ipv4If | sys/ipv4/inst/dom-{name}/if-{[id]} |
ipv4Addr | sys/ipv4/inst/dom-{name}/if-{[id]}/addr-{[addr]} |
platformEntity | sys/pltfm |
ipv4Dom Properties
The following table contains information about the ipv4Dom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
name | naming:Name256 (string:Basic) | The name of the object. | MAX SIZE: 63 |
ipv4If Properties
The following table contains information about the ipv4If properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
urpf | ip:UrpfT (scalar:Enum8) | URPF Info | SELECTION: 0 - disabled 1 - strict 2 - loose 3 - loose-allow-default 4 - strict-allow-vni-hosts DEFAULT: disabled |
ipv4Addr Properties
The following table contains information about the ipv4Addr properties in the DME 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 |
---|---|---|---|
addr | address:Ip | Address | Value must match ipv4 or ipv6 known format |
platformEntity Properties
The following table contains information about the platformEntity properties in the DME 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 |
---|---|---|---|
urpfStatus | nw:AdminSt (scalar:Enum8) | Unicast Reverse Path Forwarding Status | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
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 Loose Unicast RPF for IPv4 Packets on a Cisco Nexus 9300 Series Switch
Disabling Loose Unicast RPF for IPv4 Packets on a Cisco Nexus 9300 Series Switch
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ipv4Entity": {
"children": [
{
"ipv4Inst": {
"children": [
{
"ipv4Dom": {
"attributes": {
"name": "default"
},
"children": [
{
"ipv4If": {
"attributes": {
"id": "eth2/3",
"urpf": "disabled"
},
"children": [
{
"ipv4Addr": {
"attributes": {
"addr": "172.23.231.240/23"
}
}
}
]
}
}
]
}
}
]
}
}
]
}
},
{
"platformEntity": {
"attributes": {
"urpfStatus": "disabled"
}}}]}}
{
imdata:[]
}
<System>
<ipv4-items>
<inst-items>
<dom-items>
<Dom-list>
<name>default</name>
<if-items>
<If-list>
<id>eth2/3</id>
<urpf>disabled</urpf>
<addr-items>
<Addr-list>
<addr>172.23.231.240/23</addr>
</Addr-list>
</addr-items>
</If-list>
</if-items>
</Dom-list>
</dom-items>
</inst-items>
</ipv4-items>
<pltfm-items>
<urpfStatus>disabled</urpfStatus>
</pltfm-items>
</System>
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.
system urpf disable
interface Ethernet2/3
ip address 172.23.231.240/23
no ip verify unicast source reachable-via any
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
topSystem | sys |
ipv4Entity | sys/ipv4 |
ipv4Inst | sys/ipv4/inst |
ipv4Dom | sys/ipv4/inst/dom-{name} |
ipv4If | sys/ipv4/inst/dom-{name}/if-{[id]} |
ipv4Addr | sys/ipv4/inst/dom-{name}/if-{[id]}/addr-{[addr]} |
platformEntity | sys/pltfm |
ipv4Dom Properties
The following table contains information about the ipv4Dom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
name | naming:Name256 (string:Basic) | The name of the object. | MAX SIZE: 63 |
ipv4If Properties
The following table contains information about the ipv4If properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
urpf | ip:UrpfT (scalar:Enum8) | URPF Info | SELECTION: 0 - disabled 1 - strict 2 - loose 3 - loose-allow-default 4 - strict-allow-vni-hosts DEFAULT: disabled |
ipv4Addr Properties
The following table contains information about the ipv4Addr properties in the DME 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 |
---|---|---|---|
addr | address:Ip | Address | Value must match ipv4 or ipv6 known format |
platformEntity Properties
The following table contains information about the platformEntity properties in the DME 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 |
---|---|---|---|
urpfStatus | nw:AdminSt (scalar:Enum8) | Unicast Reverse Path Forwarding Status | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
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 Strict Unicast RPF for IPv4 Packets on a Cisco Nexus 9300 Series Switch
Configuring Strict Unicast RPF for IPv4 Packets on a Cisco Nexus 9300 Series Switch
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ipv4Entity": {
"children": [
{
"ipv4Inst": {
"children": [
{
"ipv4Dom": {
"attributes": {
"name": "default"
},
"children": [
{
"ipv4If": {
"attributes": {
"id": "eth2/2",
"urpf": "strict"
},
"children": [
{
"ipv4Addr": {
"attributes": {
"addr": "172.23.231.240/23"
}
}
}
]
}
}
]
}
}
]
}
}
]
}
},
{
"platformEntity": {
"attributes": {
"urpfStatus": "disabled"
}}}]}}
{
imdata:[]
}
<System>
<ipv4-items>
<inst-items>
<dom-items>
<Dom-list>
<name>default</name>
<if-items>
<If-list>
<id>eth2/2</id>
<urpf>strict</urpf>
<addr-items>
<Addr-list>
<addr>172.23.231.240/23</addr>
</Addr-list>
</addr-items>
</If-list>
</if-items>
</Dom-list>
</dom-items>
</inst-items>
</ipv4-items>
<pltfm-items>
<urpfStatus>disabled</urpfStatus>
</pltfm-items>
</System>
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.
system urpf disable
interface Ethernet2/2
ip address 172.23.231.240/23
ip verify unicast source reachable-via rx
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
topSystem | sys |
ipv4Entity | sys/ipv4 |
ipv4Inst | sys/ipv4/inst |
ipv4Dom | sys/ipv4/inst/dom-{name} |
ipv4If | sys/ipv4/inst/dom-{name}/if-{[id]} |
ipv4Addr | sys/ipv4/inst/dom-{name}/if-{[id]}/addr-{[addr]} |
platformEntity | sys/pltfm |
ipv4Dom Properties
The following table contains information about the ipv4Dom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
name | naming:Name256 (string:Basic) | The name of the object. | MAX SIZE: 63 |
ipv4If Properties
The following table contains information about the ipv4If properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
urpf | ip:UrpfT (scalar:Enum8) | URPF Info | SELECTION: 0 - disabled 1 - strict 2 - loose 3 - loose-allow-default 4 - strict-allow-vni-hosts DEFAULT: disabled |
ipv4Addr Properties
The following table contains information about the ipv4Addr properties in the DME 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 |
---|---|---|---|
addr | address:Ip | Address | Value must match ipv4 or ipv6 known format |
platformEntity Properties
The following table contains information about the platformEntity properties in the DME 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 |
---|---|---|---|
urpfStatus | nw:AdminSt (scalar:Enum8) | Unicast Reverse Path Forwarding Status | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
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 Strict Unicast RPF for IPv4 Packets on a Cisco Nexus 9300 Series Switch
Disabling Strict Unicast RPF for IPv4 Packets on a Cisco Nexus 9300 Series Switch
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ipv4Entity": {
"children": [
{
"ipv4Inst": {
"children": [
{
"ipv4Dom": {
"attributes": {
"name": "default"
},
"children": [
{
"ipv4If": {
"attributes": {
"id": "eth2/2",
"urpf": "disabled"
},
"children": [
{
"ipv4Addr": {
"attributes": {
"addr": "172.23.231.240/23"
}
}
}
]
}
}
]
}
}
]
}
}
]
}
},
{
"platformEntity": {
"attributes": {
"urpfStatus": "disabled"
}
}
}
]
}
}
{
imdata:[]
}
<System>
<ipv4-items>
<inst-items>
<dom-items>
<Dom-list>
<name>default</name>
<if-items>
<If-list>
<id>eth2/2</id>
<urpf>disabled</urpf>
<addr-items>
<Addr-list>
<addr>172.23.231.240/23</addr>
</Addr-list>
</addr-items>
</If-list>
</if-items>
</Dom-list>
</dom-items>
</inst-items>
</ipv4-items>
<pltfm-items>
<urpfStatus>disabled</urpfStatus>
</pltfm-items>
</System>
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.
system urpf disable
interface Ethernet2/2
ip address 172.23.231.240/23
no ip verify unicast source reachable-via rx
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
topSystem | sys |
ipv4Entity | sys/ipv4 |
ipv4Inst | sys/ipv4/inst |
ipv4Dom | sys/ipv4/inst/dom-{name} |
ipv4If | sys/ipv4/inst/dom-{name}/if-{[id]} |
ipv4Addr | sys/ipv4/inst/dom-{name}/if-{[id]}/addr-{[addr]} |
platformEntity | sys/pltfm |
ipv4Dom Properties
The following table contains information about the ipv4Dom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
name | naming:Name256 (string:Basic) | The name of the object. | MAX SIZE: 63 |
ipv4If Properties
The following table contains information about the ipv4If properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
urpf | ip:UrpfT (scalar:Enum8) | URPF Info | SELECTION: 0 - disabled 1 - strict 2 - loose 3 - loose-allow-default 4 - strict-allow-vni-hosts DEFAULT: disabled |
ipv4Addr Properties
The following table contains information about the ipv4Addr properties in the DME 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 |
---|---|---|---|
addr | address:Ip | Address | Value must match ipv4 or ipv6 known format |
platformEntity Properties
The following table contains information about the platformEntity properties in the DME 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 |
---|---|---|---|
urpfStatus | nw:AdminSt (scalar:Enum8) | Unicast Reverse Path Forwarding Status | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
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 Source as Reachable via the Interface on Which a Packet was Received
Configuring the Source as Reachable via the Interface on Which a Packet was Received
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ipv4Entity": {
"children": [
{
"ipv4Inst": {
"children": [
{
"ipv4Dom": {
"attributes": {
"name": "default"
},
"children": [
{
"ipv4If": {
"attributes": {
"id": "eth1/4",
"urpf": "strict"
}
}
}
]
}
}
]
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/4",
"layer": "Layer3",
"userCfgdFlags": "admin_layer"
}
}
}
]
}
}
]
}
}
{
"imdata": []
}
<System>
<ipv4-items>
<inst-items>
<dom-items>
<Dom-list>
<name>default</name>
<if-items>
<If-list>
<id>eth1/4</id>
<urpf>strict</urpf>
</If-list>
</if-items>
</Dom-list>
</dom-items>
</inst-items>
</ipv4-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/4</id>
<layer>Layer3</layer>
<userCfgdFlags>admin_layer</userCfgdFlags>
</PhysIf-list>
</phys-items>
</intf-items>
</System>
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/4
no switchport
ip verify unicast source reachable-via rx
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
topSystem | sys |
ipv4Entity | sys/ipv4 |
ipv4Inst | sys/ipv4/inst |
ipv4Dom | sys/ipv4/inst/dom-{name} |
ipv4If | sys/ipv4/inst/dom-{name}/if-{[id]} |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-{[id]} |
ipv4Dom Properties
The following table contains information about the ipv4Dom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
name | naming:Name256 (string:Basic) | The name of the object. | MAX SIZE: 63 |
ipv4If Properties
The following table contains information about the ipv4If properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
urpf | ip:UrpfT (scalar:Enum8) | URPF Info | SELECTION: 0 - disabled 1 - strict 2 - loose 3 - loose-allow-default 4 - strict-allow-vni-hosts DEFAULT: disabled |
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 |
layer | l1:Layer (scalar:Enum8) | Administrative port layer | SELECTION: 1 - Layer2 2 - Layer3 DEFAULT: Layer2 |
userCfgdFlags | l1:userCfgdFlags (scalar:Bitmask8) | Port User Config Flags | SELECTION: 0 - none 1 - admin_state 2 - admin_layer 4 - admin_router_mac 8 - admin_dce_mode 16 - admin_mtu DEFAULT: none |
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 Source Configured as Reachable via the Interface on Which a Packet was Received
Deleting the Source Configured as Reachable via the Interface on which a Packet was Received
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ipv4Entity": {
"children": [
{
"ipv4Inst": {
"children": [
{
"ipv4Dom": {
"attributes": {
"name": "default"
},
"children": [
{
"ipv4If": {
"attributes": {
"id": "eth1/4",
"urpf": "disabled"
}
}
}
]
}
}
]
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/4",
"layer": "Layer3",
"userCfgdFlags": "admin_layer"
}
}
}
]
}
}
]
}
}
{
"imdata": []
}
<System>
<ipv4-items>
<inst-items>
<dom-items>
<Dom-list>
<name>default</name>
<if-items>
<If-list>
<id>eth1/4</id>
<urpf>disabled</urpf>
</If-list>
</if-items>
</Dom-list>
</dom-items>
</inst-items>
</ipv4-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/4</id>
<layer>Layer3</layer>
<userCfgdFlags>admin_layer</userCfgdFlags>
</PhysIf-list>
</phys-items>
</intf-items>
</System>
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/4
no switchport
no ip verify unicast source reachable-via rx
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
topSystem | sys |
ipv4Entity | sys/ipv4 |
ipv4Inst | sys/ipv4/inst |
ipv4Dom | sys/ipv4/inst/dom-{name} |
ipv4If | sys/ipv4/inst/dom-{name}/if-{[id]} |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-{[id]} |
ipv4Dom Properties
The following table contains information about the ipv4Dom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
name | naming:Name256 (string:Basic) | The name of the object. | MAX SIZE: 63 |
ipv4If Properties
The following table contains information about the ipv4If properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
urpf | ip:UrpfT (scalar:Enum8) | URPF Info | SELECTION: 0 - disabled 1 - strict 2 - loose 3 - loose-allow-default 4 - strict-allow-vni-hosts DEFAULT: disabled |
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 |
layer | l1:Layer (scalar:Enum8) | Administrative port layer | SELECTION: 1 - Layer2 2 - Layer3 DEFAULT: Layer2 |
userCfgdFlags | l1:userCfgdFlags (scalar:Bitmask8) | Port User Config Flags | SELECTION: 0 - none 1 - admin_state 2 - admin_layer 4 - admin_router_mac 8 - admin_dce_mode 16 - admin_mtu DEFAULT: none |
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 Source as Reachable Via Any Interface With Loose Default Route Unicast Reverse Path Forwarding
Configuring the Source as Reachable Via Any Interface With Loose Default Route Unicast Reverse Path Forwarding
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ipv4Entity": {
"children": [
{
"ipv4Inst": {
"children": [
{
"ipv4Dom": {
"attributes": {
"name": "default"
},
"children": [
{
"ipv4If": {
"attributes": {
"id": "eth1/4",
"urpf": "loose-allow-default"
}
}
}
]
}
}
]
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/4",
"layer": "Layer3",
"userCfgdFlags": "admin_layer"
}
}
}
]
}
}
]
}
}
{
"imdata": []
}
<System>
<ipv4-items>
<inst-items>
<dom-items>
<Dom-list>
<name>default</name>
<if-items>
<If-list>
<id>eth1/4</id>
<urpf>loose-allow-default</urpf>
</If-list>
</if-items>
</Dom-list>
</dom-items>
</inst-items>
</ipv4-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/4</id>
<layer>Layer3</layer>
<userCfgdFlags>admin_layer</userCfgdFlags>
</PhysIf-list>
</phys-items>
</intf-items>
</System>
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/4
no switchport
ip verify unicast source reachable-via any allow-default
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
topSystem | sys |
ipv4Entity | sys/ipv4 |
ipv4Inst | sys/ipv4/inst |
ipv4Dom | sys/ipv4/inst/dom-{name} |
ipv4If | sys/ipv4/inst/dom-{name}/if-{[id]} |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-{[id]} |
ipv4Dom Properties
The following table contains information about the ipv4Dom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
name | naming:Name256 (string:Basic) | The name of the object. | MAX SIZE: 63 |
ipv4If Properties
The following table contains information about the ipv4If properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
urpf | ip:UrpfT (scalar:Enum8) | URPF Info | SELECTION: 0 - disabled 1 - strict 2 - loose 3 - loose-allow-default 4 - strict-allow-vni-hosts DEFAULT: disabled |
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 |
layer | l1:Layer (scalar:Enum8) | Administrative port layer | SELECTION: 1 - Layer2 2 - Layer3 DEFAULT: Layer2 |
userCfgdFlags | l1:userCfgdFlags (scalar:Bitmask8) | Port User Config Flags | SELECTION: 0 - none 1 - admin_state 2 - admin_layer 4 - admin_router_mac 8 - admin_dce_mode 16 - admin_mtu DEFAULT: none |
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 Source Configured as Reachable Via Any Interface With Loose Default Route Unicast Reverse Path Forwarding
Deleting a Source Configured as Reachable Via Any Interface With Loose Default Route Unicast Reverse Path Forwarding
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"ipv4Entity": {
"children": [
{
"ipv4Inst": {
"children": [
{
"ipv4Dom": {
"attributes": {
"name": "default"
},
"children": [
{
"ipv4If": {
"attributes": {
"id": "eth1/4",
"urpf": "disabled"
}
}
}
]
}
}
]
}
}
]
}
},
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/4",
"layer": "Layer3",
"userCfgdFlags": "admin_layer"
}
}
}
]
}
}
]
}
}
{
"imdata": []
}
<System>
<ipv4-items>
<inst-items>
<dom-items>
<Dom-list>
<name>default</name>
<if-items>
<If-list>
<id>eth1/4</id>
<urpf>disabled</urpf>
</If-list>
</if-items>
</Dom-list>
</dom-items>
</inst-items>
</ipv4-items>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/4</id>
<layer>Layer3</layer>
<userCfgdFlags>admin_layer</userCfgdFlags>
</PhysIf-list>
</phys-items>
</intf-items>
</System>
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/4
no switchport
no ip verify unicast source reachable-via any allow-default
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
topSystem | sys |
ipv4Entity | sys/ipv4 |
ipv4Inst | sys/ipv4/inst |
ipv4Dom | sys/ipv4/inst/dom-{name} |
ipv4If | sys/ipv4/inst/dom-{name}/if-{[id]} |
interfaceEntity | sys/intf |
l1PhysIf | sys/intf/phys-{[id]} |
ipv4Dom Properties
The following table contains information about the ipv4Dom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
name | naming:Name256 (string:Basic) | The name of the object. | MAX SIZE: 63 |
ipv4If Properties
The following table contains information about the ipv4If properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | nw:IfId (base:IfIndex) | An identifier . | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
urpf | ip:UrpfT (scalar:Enum8) | URPF Info | SELECTION: 0 - disabled 1 - strict 2 - loose 3 - loose-allow-default 4 - strict-allow-vni-hosts DEFAULT: disabled |
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 |
layer | l1:Layer (scalar:Enum8) | Administrative port layer | SELECTION: 1 - Layer2 2 - Layer3 DEFAULT: Layer2 |
userCfgdFlags | l1:userCfgdFlags (scalar:Bitmask8) | Port User Config Flags | SELECTION: 0 - none 1 - admin_state 2 - admin_layer 4 - admin_router_mac 8 - admin_dce_mode 16 - admin_mtu DEFAULT: none |
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: