Configuring RPM for IPv6

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",
                        "forceOrderV6": "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>
            <forceOrderV6>enabled</forceOrderV6>
            <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>

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 Map_1
set ipv6 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

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",
                "forceOrderV6": "disabled",
                "order": "10"
              },
              "children": [
                {
                  "rtmapSetNh": {
                    "attributes": {
                      "addr": "1:2::3:4",
                      "status": "deleted"
}}}]}}]}}]}}

{
    "imdata": []
}

<System>
  <rpm-items>
    <rtmap-items>
      <Rule-list>
        <name>Map_1</name>
        <ent-items>
          <Entry-list>
            <order>10</order>
            <action>permit</action>
            <forceOrderV6>disabled</forceOrderV6>
            <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 Map_1
no set ipv6 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

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",
                  "loadShareV6": "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>
            <loadShareV6>enabled</loadShareV6>
            <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>

CLI Commands

route-map Map_1
set ipv6 next-hop 1:2::3:4 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",
                  "loadShareV6": "disabled",
                  "order": "10"
                },
                "children": [
                  {
                    "rtmapSetNh": {
                      "attributes": {
                        "addr": "1:2::3:4",
                        "status": "deleted"
}}}]}}]}}]}}

{
    "imdata": []
}

<System>
  <rpm-items>
    <rtmap-items>
      <Rule-list>
        <name>Map_1</name>
        <ent-items>
          <Entry-list>
            <order>10</order>
            <action>permit</action>
            <loadShareV6>disabled</loadShareV6>
            <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 Map_1
no set ipv6 next-hop 1:2::3:4 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

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": [
      {
        "rtpfxRuleV6": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "action": "permit",
                  "criteria": "inexact",
                  "fromPfxLen": "25",
                  "order": "1243",
                  "pfx": "1:2::3:4/24",
                  "toPfxLen": "25"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv6-items>
      <RuleV6-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list>
            <order>1243</order>
            <action>permit</action>
            <criteria>inexact</criteria>
            <fromPfxLen>25</fromPfxLen>
            <pfx>1:2::3:4/24</pfx>
            <toPfxLen>25</toPfxLen>
          </Entry-list>
        </ent-items>
      </RuleV6-list>
    </pfxlistv6-items>
  </rpm-items>
</System>

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

CLI Commands

ipv6 prefix-list List_1 seq 1243 permit 1:2::3:4/24 eq 25

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": [
      {
        "rtpfxRuleV6": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "order": "1243",
                  "status": "deleted"
}}}]}}]}}

{
    imdata:[]
}

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

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

CLI Commands

no ipv6 prefix-list List_1 seq 1243 permit 1:2::3:4/24 eq 25

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": [
      {
        "rtpfxRuleV6": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "action": "deny",
                  "criteria": "inexact",
                  "fromPfxLen": "25",
                  "order": "1243",
                  "pfx": "1:2::3:4/24",
                  "toPfxLen": "25"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv6-items>
      <RuleV6-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list>
            <order>1243</order>
            <action>deny</action>
            <criteria>inexact</criteria>
            <fromPfxLen>25</fromPfxLen>
            <pfx>1:2::3:4/24</pfx>
            <toPfxLen>25</toPfxLen>
          </Entry-list>
        </ent-items>
      </RuleV6-list>
    </pfxlistv6-items>
  </rpm-items>
</System>

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

CLI Commands

ipv6 prefix-list List_1 seq 1243 deny 1:2::3:4/24 eq 25

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": [
      {
        "rtpfxRuleV6": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "order": "1243",
                  "status": "deleted"
}}}]}}]}}

{
    imdata:[]
}

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

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

CLI Commands

no ipv6 prefix-list List_1 seq 1243 deny 1:2::3:4/24 eq 25

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": [
      {
        "rtpfxRuleV6": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "action": "permit",
                  "criteria": "inexact",
                  "fromPfxLen": "25",
                  "order": "1243",
                  "pfx": "1:2::3:4/24",
                  "toPfxLen": "25"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv6-items>
      <RuleV6-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list>
            <order>1243</order>
            <action>permit</action>
            <criteria>inexact</criteria>
            <fromPfxLen>25</fromPfxLen>
            <pfx>1:2::3:4/24</pfx>
            <toPfxLen>25</toPfxLen>
          </Entry-list>
        </ent-items>
      </RuleV6-list>
    </pfxlistv6-items>
  </rpm-items>
</System>

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

CLI Commands

ipv6 prefix-list List_1 seq 1243 permit 1:2::3:4/24 ge 25 le 25

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": [
      {
        "rtpfxRuleV6": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "order": "1243",
                  "status": "deleted"
}}}]}}]}}

{
    imdata:[]
}

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

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

CLI Commands

no ipv6 prefix-list List_1 seq 1243 permit 1:2::3:4/24 ge 25 le 25

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": [
      {
        "rtpfxRuleV6": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "action": "deny",
                  "criteria": "inexact",
                  "fromPfxLen": "25",
                  "order": "1243",
                  "pfx": "1:2::3:4/24",
                  "toPfxLen": "25"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv6-items>
      <RuleV6-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list>
            <order>1243</order>
            <action>deny</action>
            <criteria>inexact</criteria>
            <fromPfxLen>25</fromPfxLen>
            <pfx>1:2::3:4/24</pfx>
            <toPfxLen>25</toPfxLen>
          </Entry-list>
        </ent-items>
      </RuleV6-list>
    </pfxlistv6-items>
  </rpm-items>
</System>

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

CLI Commands

ipv6 prefix-list List_1 seq 1243 deny 1:2::3:4/24 ge 25 le 25

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": [
      {
        "rtpfxRuleV6": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "order": "1243",
                  "status": "deleted"
}}}]}}]}}

{
    imdata:[]
}

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

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

CLI Commands

no ipv6 prefix-list List_1 seq 1243 deny 1:2::3:4/24 ge 25 le 25

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": [
      {
        "rtpfxRuleV6": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "order": "1243",
                  "status": "deleted"
}}}]}}]}}

{
    imdata:[]
}

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

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

CLI Commands

no ipv6 prefix-list List_1 seq 1243 permit 1:2::3:4/24 ge 25

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": [
      {
        "rtpfxRuleV6": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "action": "deny",
                  "criteria": "inexact",
                  "fromPfxLen": "3",
                  "order": "1243",
                  "pfx": "1:2::3:4/24",
                  "toPfxLen": "25"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv6-items>
      <RuleV6-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list>
            <order>1243</order>
            <action>deny</action>
            <criteria>inexact</criteria>
            <fromPfxLen>3</fromPfxLen>
            <pfx>1:2::3:4/24</pfx>
            <toPfxLen>25</toPfxLen>
          </Entry-list>
        </ent-items>
      </RuleV6-list>
    </pfxlistv6-items>
  </rpm-items>
</System>

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

CLI Commands

ipv6 prefix-list List_1 seq 1243 deny 1:2::3:4/24ge 25

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": [
      {
        "rtpfxRuleV6": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "order": "1243",
                  "status": "deleted"
}}}]}}]}}

{
    imdata:[]
}

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

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

CLI Commands

no ipv6 prefix-list List_1 seq 1243 deny 1:2::3:4/24ge 25

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": [
      {
        "rtpfxRuleV6": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "action": "permit",
                  "criteria": "inexact",
                  "fromPfxLen": "25",
                  "order": "1243",
                  "pfx": "1:2::3:4/24",
                  "toPfxLen": "25"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv6-items>
      <RuleV6-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list>
            <order>1243</order>
            <action>permit</action>
            <criteria>inexact</criteria>
            <fromPfxLen>25</fromPfxLen>
            <pfx>1:2::3:4/24</pfx>
            <toPfxLen>25</toPfxLen>
          </Entry-list>
        </ent-items>
      </RuleV6-list>
    </pfxlistv6-items>
  </rpm-items>
</System>

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

CLI Commands

ipv6 prefix-list List_1 seq 1243 permit 1:2::3:4/24 le 25

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": [
      {
        "rtpfxRuleV6": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "order": "1243",
                  "status": "deleted"
}}}]}}]}}

{
    imdata:[]
}

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

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

CLI Commands

no ipv6 prefix-list List_1 seq 1243 permit 1:2::3:4/24 le 25

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": [
      {
        "rtpfxRuleV6": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "action": "deny",
                  "criteria": "inexact",
                  "fromPfxLen": "25",
                  "order": "1243",
                  "pfx": "1:2::3:4/24",
                  "toPfxLen": "25"
}}}]}}]}}

{
    imdata:[]
}

<System>
  <rpm-items>
    <pfxlistv6-items>
      <RuleV6-list>
        <name>List_1</name>
        <ent-items>
          <Entry-list>
            <order>1243</order>
            <action>deny</action>
            <criteria>inexact</criteria>
            <fromPfxLen>25</fromPfxLen>
            <pfx>1:2::3:4/24</pfx>
            <toPfxLen>25</toPfxLen>
          </Entry-list>
        </ent-items>
      </RuleV6-list>
    </pfxlistv6-items>
  </rpm-items>
</System>

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

CLI Commands

ipv6 prefix-list List_1 seq 1243 deny 1:2::3:4/24 le 25

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": [
      {
        "rtpfxRuleV6": {
          "attributes": {
            "name": "List_1"
          },
          "children": [
            {
              "rtpfxEntry": {
                "attributes": {
                  "order": "1243",
                  "status": "deleted"
}}}]}}]}}

{
    imdata:[]
}

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

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

CLI Commands

no ipv6 prefix-list List_1 seq 1243 deny 1:2::3:4/24 le 25

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",
                  "loadShareV6": "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>
            <loadShareV6>enabled</loadShareV6>
            <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 ipv6 next-hop 1:2::3:4 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",
                  "loadShareV6": "disabled",
                  "order": "10"
                },
                "children": [
                  {
                    "rtmapSetNh": {
                      "attributes": {
                        "addr": "1:2::3:4",
                        "status": "deleted"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <rpm-items>
    <rtmap-items>
      <Rule-list>
        <name>Map_1</name>
        <ent-items>
          <Entry-list>
            <order>10</order>
            <action>permit</action>
            <loadShareV6>disabled</loadShareV6>
            <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>

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

CLI Commands

route-map Map_1
no set ipv6 next-hop 1:2::3:4 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",
                  "forceOrderV6": "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>
            <forceOrderV6>enabled</forceOrderV6>
            <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 ipv6 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",
                  "forceOrderV6": "disabled",
                  "order": "10"
                },
                "children": [
                  {
                    "rtmapSetNh": {
                      "attributes": {
                        "addr": "1:2::3:4",
                        "status": "deleted"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <rpm-items>
    <rtmap-items>
      <Rule-list>
        <name>Map_1</name>
        <ent-items>
          <Entry-list>
            <order>10</order>
            <action>permit</action>
            <forceOrderV6>disabled</forceOrderV6>
            <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>

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

CLI Commands

route-map Map_1
no set ipv6 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

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",
                  "dropOnFailV6": "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>
            <dropOnFailV6>enabled</dropOnFailV6>
            <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 ipv6 next-hop 1:2::3:4 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",
                  "dropOnFailV6": "disabled",
                  "order": "10"
                },
                "children": [
                  {
                    "rtmapSetNh": {
                      "attributes": {
                        "addr": "1:2::3:4",
                        "status": "deleted"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}

{
    imdata:[]
}

<System>
  <rpm-items>
    <rtmap-items>
      <Rule-list>
        <name>Map_1</name>
        <ent-items>
          <Entry-list>
            <order>10</order>
            <action>permit</action>
            <dropOnFailV6>disabled</dropOnFailV6>
            <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>

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

CLI Commands

route-map Map_1
no set ipv6 next-hop 1:2::3:4 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