Configuring IP Prefix Lists
IP prefix lists match the IP packet or route against a list of prefixes and prefix lengths. You can create an IP prefix list for IPv4 and create an IPv6 prefix list for IPv6. You can configure the prefix list entry to match the prefix length exactly or to match any prefix with a length that matches the configured range of prefix lengths.
For more information, see the Cisco Nexus 9000 Series NX-OS Unicast Routing Configuration Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-installation-and-configuration-guides-list.html/
Configuring the Exact Prefix Length to be Matched (Permit)
Note: This example was added in Release 9.2(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 prefix-list List_1 seq 1243 permit 1.2.3.4/24 eq 25 mask 2.4.6.8
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 |
rpmEntity |
sys/rpm |
rtpfxRuleV4 |
sys/rpm/pfxlistv4-{[name]} |
rtpfxEntry |
sys/rpm/pfxlistv6-{[name]}/ent-{order} |
rtpfxRuleV4 Properties
The following table contains information about the rtpfxRuleV4 properties in the DME 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 | pol:ObjName (naming:Name256) | Object name | MAX SIZE: 64 |
rtpfxEntry Properties
The following table contains information about the rtpfxEntry properties in the DME 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 |
action | rtflt:Action (scalar:Enum8) | Action | SELECTION: 0 - deny 1 - permit DEFAULT: permit |
criteria | rtpfx:Criteria (scalar:Enum8) | Criteria | SELECTION: 0 - exact 1 - inexact DEFAULT: exact |
fromPfxLen | l3:IpPfxLen (scalar:Uint16) | The start of a range used to describe the prefix length if the criteria is not an exact match. | RANGE: [0 , 128] DEFAULT: 0 |
mask | address:Ip
| mask | Value must match ipv4 or ipv6 known format |
order | rtflt:Order (scalar:Uint32) | Order | RANGE: [1 , 4294967294] |
pfx | address:Ip
| Specifies the OSPF route prefix. | Value must match ipv4 or ipv6 known format |
toPfxLen | l3:IpPfxLen (scalar:Uint16) | The end of a range to describe the prefix length if the criteria is not an exact match. | RANGE: [0 , 128] DEFAULT: 0 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting the Exact Prefix Length to be Matched (Permit)
Note: This example was added in Release 9.2(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 prefix-list List_1 seq 1243 permit 1.2.3.4/24 eq 25 mask 2.4.6.8
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 |
rpmEntity |
sys/rpm |
rtpfxRuleV4 |
sys/rpm/pfxlistv4-{[name]} |
rtpfxEntry |
sys/rpm/pfxlistv6-{[name]}/ent-{order} |
rtpfxRuleV4 Properties
The following table contains information about the rtpfxRuleV4 properties in the DME 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 | pol:ObjName (naming:Name256) | Object name | MAX SIZE: 64 |
rtpfxEntry Properties
The following table contains information about the rtpfxEntry properties in the DME 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 |
order | rtflt:Order (scalar:Uint32) | Order | RANGE: [1 , 4294967294] |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring the Exact Prefix Length to be Matched (Deny)
Note: This example was added in Release 9.2(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 prefix-list List_1 seq 1243 deny 1.2.3.4/24 eq 25 mask 2.4.6.8
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 |
rpmEntity |
sys/rpm |
rtpfxRuleV4 |
sys/rpm/pfxlistv4-{[name]} |
rtpfxEntry |
sys/rpm/pfxlistv6-{[name]}/ent-{order} |
rtpfxRuleV4 Properties
The following table contains information about the rtpfxRuleV4 properties in the DME 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 | pol:ObjName (naming:Name256) | Object name | MAX SIZE: 64 |
rtpfxEntry Properties
The following table contains information about the rtpfxEntry properties in the DME 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 |
action | rtflt:Action (scalar:Enum8) | Action | SELECTION: 0 - deny 1 - permit DEFAULT: permit |
criteria | rtpfx:Criteria (scalar:Enum8) | Criteria | SELECTION: 0 - exact 1 - inexact DEFAULT: exact |
fromPfxLen | l3:IpPfxLen (scalar:Uint16) | The start of a range used to describe the prefix length if the criteria is not an exact match. | RANGE: [0 , 128] DEFAULT: 0 |
mask | address:Ip
| mask | Value must match ipv4 or ipv6 known format |
order | rtflt:Order (scalar:Uint32) | Order | RANGE: [1 , 4294967294] |
pfx | address:Ip
| Specifies the OSPF route prefix. | Value must match ipv4 or ipv6 known format |
toPfxLen | l3:IpPfxLen (scalar:Uint16) | The end of a range to describe the prefix length if the criteria is not an exact match. | RANGE: [0 , 128] DEFAULT: 0 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting the Exact Prefix Length to be Matched (Deny)
Note: This example was added in Release 9.2(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 prefix-list List_1 seq 1243 deny 1.2.3.4/24 eq 25 mask 2.4.6.8
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 |
rpmEntity |
sys/rpm |
rtpfxRuleV4 |
sys/rpm/pfxlistv4-{[name]} |
rtpfxEntry |
sys/rpm/pfxlistv6-{[name]}/ent-{order} |
rtpfxRuleV4 Properties
The following table contains information about the rtpfxRuleV4 properties in the DME 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 | pol:ObjName (naming:Name256) | Object name | MAX SIZE: 64 |
rtpfxEntry Properties
The following table contains information about the rtpfxEntry properties in the DME 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 |
order | rtflt:Order (scalar:Uint32) | Order | RANGE: [1 , 4294967294] |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring the Minimum and Maximum Prefix Length to be Matched (Permit)
Note: This example was added in Release 9.2(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 prefix-list List_1 seq 1243 permit 1.2.3.4/24 ge 25 le 25 mask 2.4.6.8
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 |
rpmEntity |
sys/rpm |
rtpfxRuleV4 |
sys/rpm/pfxlistv4-{[name]} |
rtpfxEntry |
sys/rpm/pfxlistv6-{[name]}/ent-{order} |
rtpfxRuleV4 Properties
The following table contains information about the rtpfxRuleV4 properties in the DME 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 | pol:ObjName (naming:Name256) | Object name | MAX SIZE: 64 |
rtpfxEntry Properties
The following table contains information about the rtpfxEntry properties in the DME 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 |
action | rtflt:Action (scalar:Enum8) | Action | SELECTION: 0 - deny 1 - permit DEFAULT: permit |
criteria | rtpfx:Criteria (scalar:Enum8) | Criteria | SELECTION: 0 - exact 1 - inexact DEFAULT: exact |
fromPfxLen | l3:IpPfxLen (scalar:Uint16) | The start of a range used to describe the prefix length if the criteria is not an exact match. | RANGE: [0 , 128] DEFAULT: 0 |
mask | address:Ip
| mask | Value must match ipv4 or ipv6 known format |
order | rtflt:Order (scalar:Uint32) | Order | RANGE: [1 , 4294967294] |
pfx | address:Ip
| Specifies the OSPF route prefix. | Value must match ipv4 or ipv6 known format |
toPfxLen | l3:IpPfxLen (scalar:Uint16) | The end of a range to describe the prefix length if the criteria is not an exact match. | RANGE: [0 , 128] DEFAULT: 0 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting the Minimum and Maximum Prefix Length to be Matched (Permit)
Note: This example was added in Release 9.2(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 prefix-list List_1 seq 1243 permit 1.2.3.4/24 ge 25 le 25 mask 2.4.6.8
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 |
rpmEntity |
sys/rpm |
rtpfxRuleV4 |
sys/rpm/pfxlistv4-{[name]} |
rtpfxEntry |
sys/rpm/pfxlistv6-{[name]}/ent-{order} |
rtpfxRuleV4 Properties
The following table contains information about the rtpfxRuleV4 properties in the DME 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 | pol:ObjName (naming:Name256) | Object name | MAX SIZE: 64 |
rtpfxEntry Properties
The following table contains information about the rtpfxEntry properties in the DME 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 |
order | rtflt:Order (scalar:Uint32) | Order | RANGE: [1 , 4294967294] |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring the Minimum and Maximum Prefix Length to be Matched (Deny)
Note: This example was added in Release 9.2(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 prefix-list List_1 seq 1243 deny 1.2.3.4/24 ge 25 le 25 mask 2.4.6.8
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 |
rpmEntity |
sys/rpm |
rtpfxRuleV4 |
sys/rpm/pfxlistv4-{[name]} |
rtpfxEntry |
sys/rpm/pfxlistv6-{[name]}/ent-{order} |
rtpfxRuleV4 Properties
The following table contains information about the rtpfxRuleV4 properties in the DME 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 | pol:ObjName (naming:Name256) | Object name | MAX SIZE: 64 |
rtpfxEntry Properties
The following table contains information about the rtpfxEntry properties in the DME 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 |
action | rtflt:Action (scalar:Enum8) | Action | SELECTION: 0 - deny 1 - permit DEFAULT: permit |
criteria | rtpfx:Criteria (scalar:Enum8) | Criteria | SELECTION: 0 - exact 1 - inexact DEFAULT: exact |
fromPfxLen | l3:IpPfxLen (scalar:Uint16) | The start of a range used to describe the prefix length if the criteria is not an exact match. | RANGE: [0 , 128] DEFAULT: 0 |
mask | address:Ip
| mask | Value must match ipv4 or ipv6 known format |
order | rtflt:Order (scalar:Uint32) | Order | RANGE: [1 , 4294967294] |
pfx | address:Ip
| Specifies the OSPF route prefix. | Value must match ipv4 or ipv6 known format |
toPfxLen | l3:IpPfxLen (scalar:Uint16) | The end of a range to describe the prefix length if the criteria is not an exact match. | RANGE: [0 , 128] DEFAULT: 0 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting the Minimum and Maximum Prefix Length to be Matched (Deny)
Note: This example was added in Release 9.2(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 prefix-list List_1 seq 1243 deny 1.2.3.4/24 ge 25 le 25 mask 2.4.6.8
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 |
rpmEntity |
sys/rpm |
rtpfxRuleV4 |
sys/rpm/pfxlistv4-{[name]} |
rtpfxEntry |
sys/rpm/pfxlistv6-{[name]}/ent-{order} |
rtpfxRuleV4 Properties
The following table contains information about the rtpfxRuleV4 properties in the DME 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 | pol:ObjName (naming:Name256) | Object name | MAX SIZE: 64 |
rtpfxEntry Properties
The following table contains information about the rtpfxEntry properties in the DME 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 |
order | rtflt:Order (scalar:Uint32) | Order | RANGE: [1 , 4294967294] |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring the Explicity Match Mask (Permit)
Note: This example was added in Release 9.2(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 prefix-list List_1 seq 1243 permit 1.2.3.4/24 mask 2.4.6.8
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 |
rpmEntity |
sys/rpm |
rtpfxRuleV4 |
sys/rpm/pfxlistv4-{[name]} |
rtpfxEntry |
sys/rpm/pfxlistv6-{[name]}/ent-{order} |
rtpfxRuleV4 Properties
The following table contains information about the rtpfxRuleV4 properties in the DME 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 | pol:ObjName (naming:Name256) | Object name | MAX SIZE: 64 |
rtpfxEntry Properties
The following table contains information about the rtpfxEntry properties in the DME 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 |
action | rtflt:Action (scalar:Enum8) | Action | SELECTION: 0 - deny 1 - permit DEFAULT: permit |
criteria | rtpfx:Criteria (scalar:Enum8) | Criteria | SELECTION: 0 - exact 1 - inexact DEFAULT: exact |
fromPfxLen | l3:IpPfxLen (scalar:Uint16) | The start of a range used to describe the prefix length if the criteria is not an exact match. | RANGE: [0 , 128] DEFAULT: 0 |
mask | address:Ip
| mask | Value must match ipv4 or ipv6 known format |
order | rtflt:Order (scalar:Uint32) | Order | RANGE: [1 , 4294967294] |
pfx | address:Ip
| Specifies the OSPF route prefix. | Value must match ipv4 or ipv6 known format |
toPfxLen | l3:IpPfxLen (scalar:Uint16) | The end of a range to describe the prefix length if the criteria is not an exact match. | RANGE: [0 , 128] DEFAULT: 0 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting the Explicity Match Mask (Permit)
Note: This example was added in Release 9.2(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 prefix-list List_1 seq 1243 permit 1.2.3.4/24 mask 2.4.6.8
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 |
rpmEntity |
sys/rpm |
rtpfxRuleV4 |
sys/rpm/pfxlistv4-{[name]} |
rtpfxEntry |
sys/rpm/pfxlistv6-{[name]}/ent-{order} |
rtpfxRuleV4 Properties
The following table contains information about the rtpfxRuleV4 properties in the DME 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 | pol:ObjName (naming:Name256) | Object name | MAX SIZE: 64 |
rtpfxEntry Properties
The following table contains information about the rtpfxEntry properties in the DME 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 |
order | rtflt:Order (scalar:Uint32) | Order | RANGE: [1 , 4294967294] |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring the Explicity match mask (Deny)
Note: This example was added in Release 9.2(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 prefix-list List_1 seq 1243 deny 1.2.3.4/24 mask 2.4.6.8
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 |
rpmEntity |
sys/rpm |
rtpfxRuleV4 |
sys/rpm/pfxlistv4-{[name]} |
rtpfxEntry |
sys/rpm/pfxlistv6-{[name]}/ent-{order} |
rtpfxRuleV4 Properties
The following table contains information about the rtpfxRuleV4 properties in the DME 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 | pol:ObjName (naming:Name256) | Object name | MAX SIZE: 64 |
rtpfxEntry Properties
The following table contains information about the rtpfxEntry properties in the DME 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 |
action | rtflt:Action (scalar:Enum8) | Action | SELECTION: 0 - deny 1 - permit DEFAULT: permit |
criteria | rtpfx:Criteria (scalar:Enum8) | Criteria | SELECTION: 0 - exact 1 - inexact DEFAULT: exact |
fromPfxLen | l3:IpPfxLen (scalar:Uint16) | The start of a range used to describe the prefix length if the criteria is not an exact match. | RANGE: [0 , 128] DEFAULT: 0 |
mask | address:Ip
| mask | Value must match ipv4 or ipv6 known format |
order | rtflt:Order (scalar:Uint32) | Order | RANGE: [1 , 4294967294] |
pfx | address:Ip
| Specifies the OSPF route prefix. | Value must match ipv4 or ipv6 known format |
toPfxLen | l3:IpPfxLen (scalar:Uint16) | The end of a range to describe the prefix length if the criteria is not an exact match. | RANGE: [0 , 128] DEFAULT: 0 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting the Explicity match mask (Deny)
Note: This example was added in Release 9.2(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 prefix-list List_1 seq 1243 deny 1.2.3.4/24 mask 2.4.6.8
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 |
rpmEntity |
sys/rpm |
rtpfxRuleV4 |
sys/rpm/pfxlistv4-{[name]} |
rtpfxEntry |
sys/rpm/pfxlistv6-{[name]}/ent-{order} |
rtpfxRuleV4 Properties
The following table contains information about the rtpfxRuleV4 properties in the DME 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 | pol:ObjName (naming:Name256) | Object name | MAX SIZE: 64 |
rtpfxEntry Properties
The following table contains information about the rtpfxEntry properties in the DME 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 |
order | rtflt:Order (scalar:Uint32) | Order | RANGE: [1 , 4294967294] |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring the Minimum Prefix Length to be Matched (Permit)
Note: This example was added in Release 9.2(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 prefix-list List_1 seq 1243 permit 1.2.3.4/24 ge 25 mask 2.4.6.8
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 |
rpmEntity |
sys/rpm |
rtpfxRuleV4 |
sys/rpm/pfxlistv4-{[name]} |
rtpfxEntry |
sys/rpm/pfxlistv6-{[name]}/ent-{order} |
rtpfxRuleV4 Properties
The following table contains information about the rtpfxRuleV4 properties in the DME 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 | pol:ObjName (naming:Name256) | Object name | MAX SIZE: 64 |
rtpfxEntry Properties
The following table contains information about the rtpfxEntry properties in the DME 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 |
action | rtflt:Action (scalar:Enum8) | Action | SELECTION: 0 - deny 1 - permit DEFAULT: permit |
criteria | rtpfx:Criteria (scalar:Enum8) | Criteria | SELECTION: 0 - exact 1 - inexact DEFAULT: exact |
fromPfxLen | l3:IpPfxLen (scalar:Uint16) | The start of a range used to describe the prefix length if the criteria is not an exact match. | RANGE: [0 , 128] DEFAULT: 0 |
mask | address:Ip
| mask | Value must match ipv4 or ipv6 known format |
order | rtflt:Order (scalar:Uint32) | Order | RANGE: [1 , 4294967294] |
pfx | address:Ip
| Specifies the OSPF route prefix. | Value must match ipv4 or ipv6 known format |
toPfxLen | l3:IpPfxLen (scalar:Uint16) | The end of a range to describe the prefix length if the criteria is not an exact match. | RANGE: [0 , 128] DEFAULT: 0 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting the Minimum Prefix Length to be Matched (Permit)
Note: This example was added in Release 9.2(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 prefix-list List_1 seq 1243 permit 1.2.3.4/24 ge 25 mask 2.4.6.8
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 |
rpmEntity |
sys/rpm |
rtpfxRuleV4 |
sys/rpm/pfxlistv4-{[name]} |
rtpfxEntry |
sys/rpm/pfxlistv6-{[name]}/ent-{order} |
rtpfxRuleV4 Properties
The following table contains information about the rtpfxRuleV4 properties in the DME 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 | pol:ObjName (naming:Name256) | Object name | MAX SIZE: 64 |
rtpfxEntry Properties
The following table contains information about the rtpfxEntry properties in the DME 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 |
order | rtflt:Order (scalar:Uint32) | Order | RANGE: [1 , 4294967294] |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring the Minimum Prefix Length to be Matched (Deny)
Note: This example was added in Release 9.2(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 prefix-list List_1 seq 1243 deny 1.2.3.4/24 ge 25 mask 2.4.6.8
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 |
rpmEntity |
sys/rpm |
rtpfxRuleV4 |
sys/rpm/pfxlistv4-{[name]} |
rtpfxEntry |
sys/rpm/pfxlistv6-{[name]}/ent-{order} |
rtpfxRuleV4 Properties
The following table contains information about the rtpfxRuleV4 properties in the DME 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 | pol:ObjName (naming:Name256) | Object name | MAX SIZE: 64 |
rtpfxEntry Properties
The following table contains information about the rtpfxEntry properties in the DME 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 |
action | rtflt:Action (scalar:Enum8) | Action | SELECTION: 0 - deny 1 - permit DEFAULT: permit |
criteria | rtpfx:Criteria (scalar:Enum8) | Criteria | SELECTION: 0 - exact 1 - inexact DEFAULT: exact |
fromPfxLen | l3:IpPfxLen (scalar:Uint16) | The start of a range used to describe the prefix length if the criteria is not an exact match. | RANGE: [0 , 128] DEFAULT: 0 |
mask | address:Ip
| mask | Value must match ipv4 or ipv6 known format |
order | rtflt:Order (scalar:Uint32) | Order | RANGE: [1 , 4294967294] |
pfx | address:Ip
| Specifies the OSPF route prefix. | Value must match ipv4 or ipv6 known format |
toPfxLen | l3:IpPfxLen (scalar:Uint16) | The end of a range to describe the prefix length if the criteria is not an exact match. | RANGE: [0 , 128] DEFAULT: 0 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting the Minimum Prefix Length to be Matched (Deny)
Note: This example was added in Release 9.2(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 prefix-list List_1 seq 1243 deny 1.2.3.4/24ge 25 mask 2.4.6.8
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 |
rpmEntity |
sys/rpm |
rtpfxRuleV4 |
sys/rpm/pfxlistv4-{[name]} |
rtpfxEntry |
sys/rpm/pfxlistv6-{[name]}/ent-{order} |
rtpfxRuleV4 Properties
The following table contains information about the rtpfxRuleV4 properties in the DME 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 | pol:ObjName (naming:Name256) | Object name | MAX SIZE: 64 |
rtpfxEntry Properties
The following table contains information about the rtpfxEntry properties in the DME 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 |
order | rtflt:Order (scalar:Uint32) | Order | RANGE: [1 , 4294967294] |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring the Maximum Prefix Length to be Matched (Permit)
Note: This example was added in Release 9.2(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 prefix-list List_1 seq 1243 permit 1.2.3.4/24 le 25 mask 2.4.6.8
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 |
rpmEntity |
sys/rpm |
rtpfxRuleV4 |
sys/rpm/pfxlistv4-{[name]} |
rtpfxEntry |
sys/rpm/pfxlistv6-{[name]}/ent-{order} |
rtpfxRuleV4 Properties
The following table contains information about the rtpfxRuleV4 properties in the DME 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 | pol:ObjName (naming:Name256) | Object name | MAX SIZE: 64 |
rtpfxEntry Properties
The following table contains information about the rtpfxEntry properties in the DME 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 |
action | rtflt:Action (scalar:Enum8) | Action | SELECTION: 0 - deny 1 - permit DEFAULT: permit |
criteria | rtpfx:Criteria (scalar:Enum8) | Criteria | SELECTION: 0 - exact 1 - inexact DEFAULT: exact |
fromPfxLen | l3:IpPfxLen (scalar:Uint16) | The start of a range used to describe the prefix length if the criteria is not an exact match. | RANGE: [0 , 128] DEFAULT: 0 |
mask | address:Ip
| mask | Value must match ipv4 or ipv6 known format |
order | rtflt:Order (scalar:Uint32) | Order | RANGE: [1 , 4294967294] |
pfx | address:Ip
| Specifies the OSPF route prefix. | Value must match ipv4 or ipv6 known format |
toPfxLen | l3:IpPfxLen (scalar:Uint16) | The end of a range to describe the prefix length if the criteria is not an exact match. | RANGE: [0 , 128] DEFAULT: 0 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting the Maximum Prefix Length to be Matched (Permit)
Note: This example was added in Release 9.2(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 prefix-list List_1 seq 1243 permit 1.2.3.4/24 le 25 mask 2.4.6.8
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 |
rpmEntity |
sys/rpm |
rtpfxRuleV4 |
sys/rpm/pfxlistv4-{[name]} |
rtpfxEntry |
sys/rpm/pfxlistv6-{[name]}/ent-{order} |
rtpfxRuleV4 Properties
The following table contains information about the rtpfxRuleV4 properties in the DME 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 | pol:ObjName (naming:Name256) | Object name | MAX SIZE: 64 |
rtpfxEntry Properties
The following table contains information about the rtpfxEntry properties in the DME 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 |
order | rtflt:Order (scalar:Uint32) | Order | RANGE: [1 , 4294967294] |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring the Maximum Prefix Length to be Matched (Deny)
Note: This example was added in Release 9.2(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 prefix-list List_1 seq 1243 deny 1.2.3.4/24 le 25 mask 2.4.6.8
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 |
rpmEntity |
sys/rpm |
rtpfxRuleV4 |
sys/rpm/pfxlistv4-{[name]} |
rtpfxEntry |
sys/rpm/pfxlistv6-{[name]}/ent-{order} |
rtpfxRuleV4 Properties
The following table contains information about the rtpfxRuleV4 properties in the DME 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 | pol:ObjName (naming:Name256) | Object name | MAX SIZE: 64 |
rtpfxEntry Properties
The following table contains information about the rtpfxEntry properties in the DME 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 |
action | rtflt:Action (scalar:Enum8) | Action | SELECTION: 0 - deny 1 - permit DEFAULT: permit |
criteria | rtpfx:Criteria (scalar:Enum8) | Criteria | SELECTION: 0 - exact 1 - inexact DEFAULT: exact |
fromPfxLen | l3:IpPfxLen (scalar:Uint16) | The start of a range used to describe the prefix length if the criteria is not an exact match. | RANGE: [0 , 128] DEFAULT: 0 |
mask | address:Ip
| mask | Value must match ipv4 or ipv6 known format |
order | rtflt:Order (scalar:Uint32) | Order | RANGE: [1 , 4294967294] |
pfx | address:Ip
| Specifies the OSPF route prefix. | Value must match ipv4 or ipv6 known format |
toPfxLen | l3:IpPfxLen (scalar:Uint16) | The end of a range to describe the prefix length if the criteria is not an exact match. | RANGE: [0 , 128] DEFAULT: 0 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting the Maximum Prefix Length to be Matched (Deny)
Note: This example was added in Release 9.2(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 prefix-list List_1 seq 1243 deny 1.2.3.4/24 le 25 mask 2.4.6.8
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 |
rpmEntity |
sys/rpm |
rtpfxRuleV4 |
sys/rpm/pfxlistv4-{[name]} |
rtpfxEntry |
sys/rpm/pfxlistv6-{[name]}/ent-{order} |
rtpfxRuleV4 Properties
The following table contains information about the rtpfxRuleV4 properties in the DME 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 | pol:ObjName (naming:Name256) | Object name | MAX SIZE: 64 |
rtpfxEntry Properties
The following table contains information about the rtpfxEntry properties in the DME 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 |
order | rtflt:Order (scalar:Uint32) | Order | RANGE: [1 , 4294967294] |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html