Configuring RPM for IPv4

Setting the Next-Hop Address

Setting the Next-Hop Address

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
"rpmEntity": {
  "children": [
    {
      "rtmapRule": {
        "attributes": {
          "name": "map1"
        },
        "children": [
          {
            "rtmapEntry": {
              "attributes": {
                "action": "permit",
                "order": "10"
              },
              "children": [
                {
                  "rtmapSetNh": {
                    "attributes": {
                      "addr": "1.2.3.4"
}}}]}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <rtmap-items>
      <Rule-list>
        <name>map1</name>
        <ent-items>
          <Entry-list>
            <order>10</order>
            <action>permit</action>
            <nh-items>
              <SetNh-list>
                <addr>1.2.3.4</addr>
              </SetNh-list>
            </nh-items>
          </Entry-list>
        </ent-items>
      </Rule-list>
    </rtmap-items>
  </rpm-items>
</System>

Specifies where output packets that pass a match clause of a route map for policy routing. In this example, the IP address is set to 1.2.3.4.

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.

route-map map1 permit 10
set ip next-hop 1.2.3.4

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 Next-Hop Address

Deleting the Next-Hop Address

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
"rpmEntity": {
  "children": [
    {
      "rtmapRule": {
        "attributes": {
          "name": "map1"
        },
        "children": [
          {
            "rtmapEntry": {
              "attributes": {
                "action": "permit",
                "order": "10"
              },
              "children": [
                {
                  "rtmapSetNh": {
                    "attributes": {
                      "addr": "1.2.3.4",
                      "status": "deleted"
}}}]}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <rtmap-items>
      <Rule-list>
        <name>map1</name>
        <ent-items>
          <Entry-list>
            <order>10</order>
            <action>permit</action>
            <nh-items>
              <SetNh-list xc:operation="delete">
                <addr>1.2.3.4</addr>
              </SetNh-list>
            </nh-items>
          </Entry-list>
        </ent-items>
      </Rule-list>
    </rtmap-items>
  </rpm-items>
</System>

CLI Commands

route-map map1 permit 10
no set ip next-hop 1.2.3.4

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/

Configuring Next-Hop Order as Per CLI Configuration

Configuring Next-Hop Order as Per CLI Configuration

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "topSystem": {
    "children": [
      {
        "rpmEntity": {
          "children": [
            {
              "rtmapRule": {
                "attributes": {
                  "name": "Map_1"
                },
                "children": [
                  {
                    "rtmapEntry": {
                      "attributes": {
                        "action": "permit",
                        "forceOrderV4": "enabled",
                        "order": "10"
                      },
                      "children": [
                        {
                          "rtmapSetNh": {
                            "attributes": {
                              "addr": "2.4.6.8"
                            }
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}

{
    "imdata": []
}

<System>
  <rpm-items>
    <rtmap-items>
      <Rule-list>
        <name>Map_1</name>
        <ent-items>
          <Entry-list>
            <order>10</order>
            <action>permit</action>
            <forceOrderV4>enabled</forceOrderV4>
            <nh-items>
              <SetNh-list>
                <addr>2.4.6.8</addr>
              </SetNh-list>
            </nh-items>
          </Entry-list>
        </ent-items>
      </Rule-list>
    </rtmap-items>
  </rpm-items>
</System>

CLI Commands

route-map Map_1
set ip next-hop 2.4.6.8 force-order

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/media/dme/index.html

Deleting Next-Hop Order as Per CLI Configuration

Deleting Next-Hop Order as Per CLI Configuration

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtmapRule": {
          "attributes": {
            "name": "Map_1"
          },
          "children": [
            {
              "rtmapEntry": {
                "attributes": {
                  "action": "permit",
                  "loadShareV4": "disabled",
                  "order": "10"
                },
                "children": [
                  {
                    "rtmapSetNh": {
                      "attributes": {
                        "addr": "2.4.6.8",
                        "status": "deleted"
}}}]}}]}}]}}

{
    "imdata": []
}

<System>
  <rpm-items>
    <rtmap-items>
      <Rule-list>
        <name>Map_1</name>
        <ent-items>
          <Entry-list>
            <order>10</order>
            <action>permit</action>
            <loadShareV4>disabled</loadShareV4>
            <nh-items>
              <SetNh-list xc:operation="delete">
                <addr>2.4.6.8</addr>
              </SetNh-list>
            </nh-items>
          </Entry-list>
        </ent-items>
      </Rule-list>
    </rtmap-items>
  </rpm-items>
</System>

CLI Commands

route-map Map_1
no set ip next-hop 2.4.6.8 force-order

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/media/dme/index.html

Configuring Load Sharing

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtmapRule": {
          "attributes": {
            "name": "Map_1"
          },
          "children": [
            {
              "rtmapEntry": {
                "attributes": {
                  "action": "permit",
                  "loadShareV4": "enabled",
                  "order": "10"
                },
                "children": [
                  {
                    "rtmapSetNh": {
                      "attributes": {
                        "addr": "2.4.6.8"
}}}]}}]}}]}}

{
    "imdata": []
}

<System>
  <rpm-items>
    <rtmap-items>
      <Rule-list>
        <name>Map_1</name>
        <ent-items>
          <Entry-list>
            <order>10</order>
            <action>permit</action>
            <loadShareV4>enabled</loadShareV4>
            <nh-items>
              <SetNh-list>
                <addr>2.4.6.8</addr>
              </SetNh-list>
            </nh-items>
          </Entry-list>
        </ent-items>
      </Rule-list>
    </rtmap-items>
  </rpm-items>
</System>

CLI Commands

route-map Map_1
set ip next-hop 2.4.6.8 load-share

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/media/dme/index.html

Deleting Load Sharing Configuration

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtmapRule": {
          "attributes": {
            "name": "Map_1"
          },
          "children": [
            {
              "rtmapEntry": {
                "attributes": {
                  "action": "permit",
                  "loadShareV4": "disabled",
                  "order": "10"
                },
                "children": [
                  {
                    "rtmapSetNh": {
                      "attributes": {
                        "addr": "2.4.6.8",
                        "status": "deleted"
}}}]}}]}}]}}

{
    "imdata": []
}

<System>
  <rpm-items>
    <rtmap-items>
      <Rule-list>
        <name>Map_1</name>
        <ent-items>
          <Entry-list>
            <order>10</order>
            <action>permit</action>
            <loadShareV4>disabled</loadShareV4>
            <nh-items>
              <SetNh-list xc:operation="delete">
                <addr>2.4.6.8</addr>
              </SetNh-list>
            </nh-items>
          </Entry-list>
        </ent-items>
      </Rule-list>
    </rtmap-items>
  </rpm-items>
</System>

CLI Commands

route-map Map_1
no set ip next-hop 2.4.6.8 load-share

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/media/dme/index.html

Setting the Next-Hop Address to Unchanged for eBGP Sessions Only

Setting the Next-Hop Address to Unchanged for eBGP Sessions Only

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
"rpmEntity": {
  "children": [
{
  "rtmapRule": {
    "attributes": {
      "name": "map1"
},
"children": [
  {
    "rtmapEntry": {
      "attributes": {
        "action": "permit",
        "order": "10"
},
  "children": [
{
  "rtmapSetNhPeerAddr": {
    "attributes": {
      "v4Unchange": "enabled"
}}}]}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <rtmap-items>
      <Rule-list>
        <name>map1</name>
        <ent-items>
          <Entry-list>
            <order>10</order>
            <action>permit</action>
            <nhpa-items>
              <v4Unchange>enabled</v4Unchange>
            </nhpa-items>
          </Entry-list>
        </ent-items>
      </Rule-list>
    </rtmap-items>
  </rpm-items>
</System>

CLI Commands

route-map map1 permit 10
set ip next-hop unchanged

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/

Disabling the Next-Hop Address Set to Unchanged for eBGP Sessions Only

Disabling the Next-Hop Address Set to Unchanged for eBGP Sessions Only

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
"rpmEntity": {
  "children": [
    {
      "rtmapRule": {
        "attributes": {
          "name": "map1"
        },
        "children": [
          {
            "rtmapEntry": {
              "attributes": {
                "action": "permit",
                "order": "10"
              },
              "children": [
                {
                  "rtmapSetNhPeerAddr": {
                    "attributes": {
                      "v4Unchange": "disabled"
}}}]}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <rtmap-items>
      <Rule-list>
        <name>map1</name>
        <ent-items>
          <Entry-list>
            <order>10</order>
            <action>permit</action>
            <nhpa-items>
              <v4Unchange>disabled</v4Unchange>
            </nhpa-items>
          </Entry-list>
        </ent-items>
      </Rule-list>
    </rtmap-items>
  </rpm-items>
</System>

CLI Commands

route-map map1 permit 10
no set ip next-hop unchanged

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/

Configuring the Exact Prefix Length to be Matched (Permit)

Configuring the Exact Prefix Length to be Matched (Permit)

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtpfxRuleV4": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "action": "permit",
                  "criteria": "inexact",
                  "fromPfxLen": "25",
                  "mask": "2.4.6.8",
                  "order": "1243",
                  "pfx": "1.2.3.4/24",
                  "toPfxLen": "25"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv4-items>
      <RuleV4-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list>
            <order>1243</order>
            <action>permit</action>
            <criteria>inexact</criteria>
            <fromPfxLen>25</fromPfxLen>
            <mask>2.4.6.8</mask>
            <pfx>1.2.3.4/24</pfx>
            <toPfxLen>25</toPfxLen>
          </Entry-list>
        </ent-items>
      </RuleV4-list>
    </pfxlistv4-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

ip prefix-list List_1 seq 1243 permit 1.2.3.4/24 eq 25 mask 2.4.6.8

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

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)

Deleting the Exact Prefix Length to be Matched (Permit)

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtpfxRuleV4": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "order": "1243",
                  "status": "deleted"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv4-items>
      <RuleV4-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list xc:operation="delete">
            <order>1243</order>
          </Entry-list>
        </ent-items>
      </RuleV4-list>
    </pfxlistv4-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

no ip prefix-list List_1 seq 1243 permit 1.2.3.4/24 eq 25 mask 2.4.6.8

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the Exact Prefix Length to be Matched (Deny)

Configuring the Exact Prefix Length to be Matched (Deny)

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtpfxRuleV4": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "action": "deny",
                  "criteria": "inexact",
                  "fromPfxLen": "25",
                  "mask": "2.4.6.8",
                  "order": "1243",
                  "pfx": "1.2.3.4/24",
                  "toPfxLen": "25"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv4-items>
      <RuleV4-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list>
            <order>1243</order>
            <action>deny</action>
            <criteria>inexact</criteria>
            <fromPfxLen>25</fromPfxLen>
            <mask>2.4.6.8</mask>
            <pfx>1.2.3.4/24</pfx>
            <toPfxLen>25</toPfxLen>
          </Entry-list>
        </ent-items>
      </RuleV4-list>
    </pfxlistv4-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

ip prefix-list List_1 seq 1243 deny 1.2.3.4/24 eq 25 mask 2.4.6.8

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the Exact Prefix Length to be Matched (Deny)

Deleting the Exact Prefix Length to be Matched (Deny)

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtpfxRuleV4": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "order": "1243",
                  "status": "deleted"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv4-items>
      <RuleV4-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list xc:operation="delete">
            <order>1243</order>
          </Entry-list>
        </ent-items>
      </RuleV4-list>
    </pfxlistv4-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

no ip prefix-list List_1 seq 1243 deny 1.2.3.4/24 eq 25 mask 2.4.6.8

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the Minimum and Maximum Prefix Length to be Matched (Permit)

Configuring the Minimum and Maximum Prefix Length to be Matched (Permit)

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtpfxRuleV4": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "action": "permit",
                  "criteria": "inexact",
                  "fromPfxLen": "25",
                  "mask": "2.4.6.8",
                  "order": "1243",
                  "pfx": "1.2.3.4/24",
                  "toPfxLen": "25"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv4-items>
      <RuleV4-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list>
            <order>1243</order>
            <action>permit</action>
            <criteria>inexact</criteria>
            <fromPfxLen>25</fromPfxLen>
            <mask>2.4.6.8</mask>
            <pfx>1.2.3.4/24</pfx>
            <toPfxLen>25</toPfxLen>
          </Entry-list>
        </ent-items>
      </RuleV4-list>
    </pfxlistv4-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

ip prefix-list List_1 seq 1243 permit 1.2.3.4/24 ge 25 le 25 mask 2.4.6.8

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the Minimum and Maximum Prefix Length to be Matched (Permit)

Deleting the Minimum and Maximum Prefix Length to be Matched (Permit)

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtpfxRuleV4": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "order": "1243",
                  "status": "deleted"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv4-items>
      <RuleV4-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list xc:operation="delete">
            <order>1243</order>
          </Entry-list>
        </ent-items>
      </RuleV4-list>
    </pfxlistv4-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

no ip prefix-list List_1 seq 1243 permit 1.2.3.4/24 ge 25 le 25 mask 2.4.6.8

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the Minimum and Maximum Prefix Length to be Matched (Deny)

Configuring the Minimum and Maximum Prefix Length to be Matched (Deny)

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtpfxRuleV4": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "action": "deny",
                  "criteria": "inexact",
                  "fromPfxLen": "25",
                  "mask": "2.4.6.8",
                  "order": "1243",
                  "pfx": "1.2.3.4/24",
                  "toPfxLen": "25"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv4-items>
      <RuleV4-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list>
            <order>1243</order>
            <action>deny</action>
            <criteria>inexact</criteria>
            <fromPfxLen>25</fromPfxLen>
            <mask>2.4.6.8</mask>
            <pfx>1.2.3.4/24</pfx>
            <toPfxLen>25</toPfxLen>
          </Entry-list>
        </ent-items>
      </RuleV4-list>
    </pfxlistv4-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

ip prefix-list List_1 seq 1243 deny 1.2.3.4/24 ge 25 le 25 mask 2.4.6.8

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the Minimum and Maximum Prefix Length to be Matched (Deny)

Deleting the Minimum and Maximum Prefix Length to be Matched (Deny)

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtpfxRuleV4": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "order": "1243",
                  "status": "deleted"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv4-items>
      <RuleV4-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list xc:operation="delete">
            <order>1243</order>
          </Entry-list>
        </ent-items>
      </RuleV4-list>
    </pfxlistv4-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

no ip prefix-list List_1 seq 1243 deny 1.2.3.4/24 ge 25 le 25 mask 2.4.6.8

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the Explicity Match Mask (Permit)

Configuring the Explicity Match Mask (Permit)

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtpfxRuleV4": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "action": "permit",
                  "criteria": "exact",
                  "fromPfxLen": "25",
                  "mask": "2.4.6.8",
                  "order": "1243",
                  "pfx": "1.2.3.4/24",
                  "toPfxLen": "25"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv4-items>
      <RuleV4-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list>
            <order>1243</order>
            <action>permit</action>
            <criteria>exact</criteria>
            <fromPfxLen>25</fromPfxLen>
            <mask>2.4.6.8</mask>
            <pfx>1.2.3.4/24</pfx>
            <toPfxLen>25</toPfxLen>
          </Entry-list>
        </ent-items>
      </RuleV4-list>
    </pfxlistv4-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

ip prefix-list List_1 seq 1243 permit 1.2.3.4/24 mask 2.4.6.8

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the Explicity Match Mask (Permit)

Deleting the Explicity Match Mask (Permit)

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtpfxRuleV4": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "order": "1243",
                  "status": "deleted"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv4-items>
      <RuleV4-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list xc:operation="delete">
            <order>1243</order>
          </Entry-list>
        </ent-items>
      </RuleV4-list>
    </pfxlistv4-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

no ip prefix-list List_1 seq 1243 permit 1.2.3.4/24 mask 2.4.6.8

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the Explicity match mask (Deny)

Configuring the Explicity match mask (Deny)

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtpfxRuleV4": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "action": "deny",
                  "criteria": "exact",
                  "fromPfxLen": "25",
                  "mask": "2.4.6.8",
                  "order": "1243",
                  "pfx": "1.2.3.4/24",
                  "toPfxLen": "25"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv4-items>
      <RuleV4-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list>
            <order>1243</order>
            <action>deny</action>
            <criteria>exact</criteria>
            <fromPfxLen>25</fromPfxLen>
            <mask>2.4.6.8</mask>
            <pfx>1.2.3.4/24</pfx>
            <toPfxLen>25</toPfxLen>
          </Entry-list>
        </ent-items>
      </RuleV4-list>
    </pfxlistv4-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

ip prefix-list List_1 seq 1243 deny 1.2.3.4/24 mask 2.4.6.8

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the Explicity match mask (Deny)

Deleting the Explicity match mask (Deny)

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtpfxRuleV4": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "order": "1243",
                  "status": "deleted"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv4-items>
      <RuleV4-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list xc:operation="delete">
            <order>1243</order>
          </Entry-list>
        </ent-items>
      </RuleV4-list>
    </pfxlistv4-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

no ip prefix-list List_1 seq 1243 deny 1.2.3.4/24 mask 2.4.6.8

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the Minimum Prefix Length to be Matched (Permit)

Configuring the Minimum Prefix Length to be Matched (Permit)

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtpfxRuleV4": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "action": "permit",
                  "criteria": "inexact",
                  "fromPfxLen": "25",
                  "mask": "2.4.6.8",
                  "order": "1243",
                  "pfx": "1.2.3.4/24",
                  "toPfxLen": "25"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv4-items>
      <RuleV4-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list>
            <order>1243</order>
            <action>permit</action>
            <criteria>inexact</criteria>
            <fromPfxLen>25</fromPfxLen>
            <mask>2.4.6.8</mask>
            <pfx>1.2.3.4/24</pfx>
            <toPfxLen>25</toPfxLen>
          </Entry-list>
        </ent-items>
      </RuleV4-list>
    </pfxlistv4-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

ip prefix-list List_1 seq 1243 permit 1.2.3.4/24 ge 25 mask 2.4.6.8

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the Minimum Prefix Length to be Matched (Permit)

Deleting the Minimum Prefix Length to be Matched (Permit)

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtpfxRuleV4": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "order": "1243",
                  "status": "deleted"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv4-items>
      <RuleV4-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list xc:operation="delete">
            <order>1243</order>
          </Entry-list>
        </ent-items>
      </RuleV4-list>
    </pfxlistv4-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

no ip prefix-list List_1 seq 1243 permit 1.2.3.4/24 ge 25 mask 2.4.6.8

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the Minimum Prefix Length to be Matched (Deny)

Configuring the Minimum Prefix Length to be Matched (Deny)

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtpfxRuleV4": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "action": "deny",
                  "criteria": "inexact",
                  "fromPfxLen": "25",
                  "mask": "2.4.6.8",
                  "order": "1243",
                  "pfx": "1.2.3.4/24",
                  "toPfxLen": "25"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv4-items>
      <RuleV4-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list>
            <order>1243</order>
            <action>deny</action>
            <criteria>inexact</criteria>
            <fromPfxLen>3</fromPfxLen>
            <mask>2.4.6.8</mask>
            <pfx>1.2.3.4/24</pfx>
            <toPfxLen>25</toPfxLen>
          </Entry-list>
        </ent-items>
      </RuleV4-list>
    </pfxlistv4-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

ip prefix-list List_1 seq 1243 deny 1.2.3.4/24 ge 25 mask 2.4.6.8

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the Minimum Prefix Length to be Matched (Deny)

Deleting the Minimum Prefix Length to be Matched (Deny)

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtpfxRuleV4": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "order": "1243",
                  "status": "deleted"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv4-items>
      <RuleV4-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list xc:operation="delete">
            <order>1243</order>
          </Entry-list>
        </ent-items>
      </RuleV4-list>
    </pfxlistv4-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

no ip prefix-list List_1 seq 1243 deny 1.2.3.4/24ge 25 mask 2.4.6.8

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the Maximum Prefix Length to be Matched (Permit)

Configuring the Maximum Prefix Length to be Matched (Permit)

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtpfxRuleV4": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "action": "permit",
                  "criteria": "inexact",
                  "fromPfxLen": "25",
                  "mask": "2.4.6.8",
                  "order": "1243",
                  "pfx": "1.2.3.4/24",
                  "toPfxLen": "25"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv4-items>
      <RuleV4-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list>
            <order>1243</order>
            <action>permit</action>
            <criteria>inexact</criteria>
            <fromPfxLen>25</fromPfxLen>
            <mask>2.4.6.8</mask>
            <pfx>1.2.3.4/24</pfx>
            <toPfxLen>25</toPfxLen>
          </Entry-list>
        </ent-items>
      </RuleV4-list>
    </pfxlistv4-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

ip prefix-list List_1 seq 1243 permit 1.2.3.4/24 le 25 mask 2.4.6.8

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the Maximum Prefix Length to be Matched (Permit)

Deleting the Maximum Prefix Length to be Matched (Permit)

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtpfxRuleV4": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "order": "1243",
                  "status": "deleted"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv4-items>
      <RuleV4-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list xc:operation="delete">
            <order>1243</order>
          </Entry-list>
        </ent-items>
      </RuleV4-list>
    </pfxlistv4-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

no ip prefix-list List_1 seq 1243 permit 1.2.3.4/24 le 25 mask 2.4.6.8

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring the Maximum Prefix Length to be Matched (Deny)

Configuring the Maximum Prefix Length to be Matched (Deny)

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtpfxRuleV4": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "action": "deny",
                  "criteria": "inexact",
                  "fromPfxLen": "25",
                  "mask": "2.4.6.8",
                  "order": "1243",
                  "pfx": "1.2.3.4/24",
                  "toPfxLen": "25"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv4-items>
      <RuleV4-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list>
            <order>1243</order>
            <action>deny</action>
            <criteria>inexact</criteria>
            <fromPfxLen>25</fromPfxLen>
            <mask>2.4.6.8</mask>
            <pfx>1.2.3.4/24</pfx>
            <toPfxLen>25</toPfxLen>
          </Entry-list>
        </ent-items>
      </RuleV4-list>
    </pfxlistv4-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

ip prefix-list List_1 seq 1243 deny 1.2.3.4/24 le 25 mask 2.4.6.8

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting the Maximum Prefix Length to be Matched (Deny)

Deleting the Maximum Prefix Length to be Matched (Deny)

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtpfxRuleV4": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "order": "1243",
                  "status": "deleted"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv4-items>
      <RuleV4-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list xc:operation="delete">
            <order>1243</order>
          </Entry-list>
        </ent-items>
      </RuleV4-list>
    </pfxlistv4-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

no ip prefix-list List_1 seq 1243 deny 1.2.3.4/24 le 25 mask 2.4.6.8

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring Load Sharing

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtmapRule": {
          "attributes": {
            "name": "Map_1"
          },
          "children": [
            {
              "rtmapEntry": {
                "attributes": {
                  "action": "permit",
                  "loadShareV4": "enabled",
                  "order": "10"
                },
                "children": [
                  {
                    "rtmapSetNh": {
                      "attributes": {
                        "addr": "2.4.6.8"
}}}]}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <rtmap-items>
      <Rule-list>
        <name>Map_1</name>
        <ent-items>
          <Entry-list>
            <order>10</order>
            <action>permit</action>
            <loadShareV4>enabled</loadShareV4>
            <nh-items>
              <SetNh-list>
                <addr>2.4.6.8</addr>
              </SetNh-list>
            </nh-items>
          </Entry-list>
        </ent-items>
      </Rule-list>
    </rtmap-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

route-map Map_1
set ip next-hop 2.4.6.8 load-share

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting Load Sharing

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtmapRule": {
          "attributes": {
            "name": "Map_1"
          },
          "children": [
            {
              "rtmapEntry": {
                "attributes": {
                  "action": "permit",
                  "loadShareV4": "disabled",
                  "order": "10"
                },
                "children": [
                  {
                    "rtmapSetNh": {
                      "attributes": {
                        "addr": "2.4.6.8",
                        "status": "deleted"
}}}]}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <rtmap-items>
      <Rule-list>
        <name>Map_1</name>
        <ent-items>
          <Entry-list>
            <order>10</order>
            <action>permit</action>
            <loadShareV4>disabled</loadShareV4>
            <nh-items>
              <SetNh-list xc:operation="delete">
                <addr>2.4.6.8</addr>
              </SetNh-list>
            </nh-items>
          </Entry-list>
        </ent-items>
      </Rule-list>
    </rtmap-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

route-map Map_1
no set ip next-hop 2.4.6.8 load-share

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring Next Hop Order Configured per CLI

Configuring Next Hop Order Configured per CLI

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtmapRule": {
          "attributes": {
            "name": "Map_1"
          },
          "children": [
            {
              "rtmapEntry": {
                "attributes": {
                  "action": "permit",
                  "forceOrderV4": "enabled",
                  "order": "10"
                },
                "children": [
                  {
                    "rtmapSetNh": {
                      "attributes": {
                        "addr": "1.2.3.4"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <rpm-items>
    <rtmap-items>
      <Rule-list>
        <name>Map_1</name>
        <ent-items>
          <Entry-list>
            <order>10</order>
            <action>permit</action>
            <forceOrderV4>enabled</forceOrderV4>
            <nh-items>
              <SetNh-list>
                <addr>1.2.3.4</addr>
              </SetNh-list>
            </nh-items>
          </Entry-list>
        </ent-items>
      </Rule-list>
    </rtmap-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

route-map Map_1
set ip next-hop 1.2.3.4 force-order

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting Next Hop Order Configured per CLI

Deleting Next Hop Order Configured per CLI

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtmapRule": {
          "attributes": {
            "name": "Map_1"
          },
          "children": [
            {
              "rtmapEntry": {
                "attributes": {
                  "action": "permit",
                  "forceOrderV4": "disabled",
                  "order": "10"
                },
                "children": [
                  {
                    "rtmapSetNh": {
                      "attributes": {
                        "addr": "2.4.6.8",
                        "status": "deleted"
}}}]}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <rtmap-items>
      <Rule-list>
        <name>Map_1</name>
        <ent-items>
          <Entry-list>
            <order>10</order>
            <action>permit</action>
            <forceOrderV4>disabled</forceOrderV4>
            <nh-items>
              <SetNh-list xc:operation="delete">
                <addr>2.4.6.8</addr>
              </SetNh-list>
            </nh-items>
          </Entry-list>
        </ent-items>
      </Rule-list>
    </rtmap-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

route-map Map_1
no set ip next-hop 2.4.6.8 force-order

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Configuring Drop packets when Next Hop is Unreachable

Configuring Drop packets when Next Hop is Unreachable

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtmapRule": {
          "attributes": {
            "name": "Map_1"
          },
          "children": [
            {
              "rtmapEntry": {
                "attributes": {
                  "action": "permit",
                  "dropOnFailV4": "enabled",
                  "order": "10"
                },
                "children": [
                  {
                    "rtmapSetNh": {
                      "attributes": {
                        "addr": "2.4.6.8"
}}}]}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <rtmap-items>
      <Rule-list>
        <name>Map_1</name>
        <ent-items>
          <Entry-list>
            <order>10</order>
            <action>permit</action>
            <dropOnFailV4>enabled</dropOnFailV4>
            <nh-items>
              <SetNh-list>
                <addr>2.4.6.8</addr>
              </SetNh-list>
            </nh-items>
          </Entry-list>
        </ent-items>
      </Rule-list>
    </rtmap-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

route-map Map_1
set ip next-hop 2.4.6.8 drop-on-fail

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html

Deleting Drop packets when Next Hop is Unreachable

Deleting Drop packets when Next Hop is Unreachable

POST http://<mgmt0_IP>/api/mo/sys/rpm.json

{
  "rpmEntity": {
    "children": [
      {
        "rtmapRule": {
          "attributes": {
            "name": "Map_1"
          },
          "children": [
            {
              "rtmapEntry": {
                "attributes": {
                  "action": "permit",
                  "dropOnFailV4": "disabled",
                  "order": "10"
                },
                "children": [
                  {
                    "rtmapSetNh": {
                      "attributes": {
                        "addr": "2.4.6.8",
                        "status": "deleted"
}}}]}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <rtmap-items>
      <Rule-list>
        <name>Map_1</name>
        <ent-items>
          <Entry-list>
            <order>10</order>
            <action>permit</action>
            <dropOnFailV4>disabled</dropOnFailV4>
            <nh-items>
              <SetNh-list xc:operation="delete">
                <addr>2.4.6.8</addr>
              </SetNh-list>
            </nh-items>
          </Entry-list>
        </ent-items>
      </Rule-list>
    </rtmap-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.2(2).

CLI Commands

route-map Map_1
no set ip next-hop 2.4.6.8 drop-on-fail

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

For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference:
https://developer.cisco.com/media/dme/index.html