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>

Note: This example was added in Release 7.0(3)I7(3).


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>

Note: This example was added in Release 7.0(3)I7(3).


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
 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

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 7.0(3)I7(3).


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 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

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>

Note: This example was added in Release 7.0(3)I7(3).


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
 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