Configuring IPv6 Next Hop

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

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

Note: The property information for this example was added in Release 9.3(3).

Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MO	DN
rpmEntity	sys/rpm
rtmapRule	sys/rpm/rtmap-{[name]}
rtmapEntry	sys/rpm/rtmap-{[name]}/ent-{order}
rtmapSetNh	sys/rpm/rtmap-{[name]}/ent-{order}/nh-{[addr]}

rtmapRule Properties

The following table contains information about the rtmapRule properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property Name	Data Type	Description	Values
name	pol:ObjName (naming:Name256)	Object name	RANGE: [0 , 63]

rtmapEntry Properties

The following table contains information about the rtmapEntry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property Name	Data Type	Description	Values
action	rtflt:Action (scalar:Enum8)	Action	SELECTION: 0 - deny 1 - permit DEFAULT: permit
loadShareV6	rtmap:AdminSt (scalar:Enum8)	Load Sharing V6	SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled
order	rtflt:Order (scalar:Uint32)	Order	RANGE: [0 , 65535]

rtmapSetNh Properties

The following table contains information about the rtmapSetNh properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property Name	Data Type	Description	Values
addr	address:Ip	The peer IP address.	Value must match ipv4 or ipv6 known format

Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

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

Note: The property information for this example was added in Release 9.3(3).

MO	DN
rpmEntity	sys/rpm
rtmapRule	sys/rpm/rtmap-{[name]}
rtmapEntry	sys/rpm/rtmap-{[name]}/ent-{order}
rtmapSetNh	sys/rpm/rtmap-{[name]}/ent-{order}/nh-{[addr]}

rtmapRule Properties

Property Name	Data Type	Description	Values
name	pol:ObjName (naming:Name256)	Object name	RANGE: [0 , 63]

rtmapEntry Properties

Property Name	Data Type	Description	Values
action	rtflt:Action (scalar:Enum8)	Action	SELECTION: 0 - deny 1 - permit DEFAULT: permit
loadShareV6	rtmap:AdminSt (scalar:Enum8)	Load Sharing V6	SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled
order	rtflt:Order (scalar:Uint32)	Order	RANGE: [0 , 65535]

rtmapSetNh Properties

Property Name	Data Type	Description	Values
addr	address:Ip	The peer IP address.	Value must match ipv4 or ipv6 known format
status	mo:ModificationStatus (scalar:Bitmask32)	The upgrade status. This property is for internal use only.	SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced

Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Next-Hop Order as Per CLI Configuration

Configuring 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": "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

Note: The property information for this example was added in Release 9.3(3).

MO	DN
rpmEntity	sys/rpm
rtmapRule	sys/rpm/rtmap-{[name]}
rtmapEntry	sys/rpm/rtmap-{[name]}/ent-{order}
rtmapSetNh	sys/rpm/rtmap-{[name]}/ent-{order}/nh-{[addr]}

rtmapRule Properties

Property Name	Data Type	Description	Values
name	pol:ObjName (naming:Name256)	Object name	RANGE: [0 , 63]

rtmapEntry Properties

Property Name	Data Type	Description	Values
action	rtflt:Action (scalar:Enum8)	Action	SELECTION: 0 - deny 1 - permit DEFAULT: permit
forceOrderV6	rtmap:AdminSt (scalar:Enum8)	Force Order V6	SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled
order	rtflt:Order (scalar:Uint32)	Order	RANGE: [0 , 65535]

rtmapSetNh Properties

Property Name	Data Type	Description	Values
addr	address:Ip	The peer IP address.	Value must match ipv4 or ipv6 known format

Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

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 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 9.2(2).

CLI Commands

route-map Map_1
no set ipv6 next-hop 1:2::3:4 force-order

Note: The property information for this example was added in Release 9.3(3).

MO	DN
rpmEntity	sys/rpm
rtmapRule	sys/rpm/rtmap-{[name]}
rtmapEntry	sys/rpm/rtmap-{[name]}/ent-{order}
rtmapSetNh	sys/rpm/rtmap-{[name]}/ent-{order}/nh-{[addr]}

rtmapRule Properties

Property Name	Data Type	Description	Values
name	pol:ObjName (naming:Name256)	Object name	RANGE: [0 , 63]

rtmapEntry Properties

Property Name	Data Type	Description	Values
action	rtflt:Action (scalar:Enum8)	Action	SELECTION: 0 - deny 1 - permit DEFAULT: permit
forceOrderV6	rtmap:AdminSt (scalar:Enum8)	Force Order V6	SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled
order	rtflt:Order (scalar:Uint32)	Order	RANGE: [0 , 65535]

rtmapSetNh Properties

Property Name	Data Type	Description	Values
addr	address:Ip	The peer IP address.	Value must match ipv4 or ipv6 known format
status	mo:ModificationStatus (scalar:Bitmask32)	The upgrade status. This property is for internal use only.	SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced

Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring 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

Note: The property information for this example was added in Release 9.3(3).

MO	DN
rpmEntity	sys/rpm
rtmapRule	sys/rpm/rtmap-{[name]}
rtmapEntry	sys/rpm/rtmap-{[name]}/ent-{order}
rtmapSetNh	sys/rpm/rtmap-{[name]}/ent-{order}/nh-{[addr]}

rtmapRule Properties

Property Name	Data Type	Description	Values
name	pol:ObjName (naming:Name256)	Object name	RANGE: [0 , 63]

rtmapEntry Properties

Property Name	Data Type	Description	Values
action	rtflt:Action (scalar:Enum8)	Action	SELECTION: 0 - deny 1 - permit DEFAULT: permit
dropOnFailV6	rtmap:AdminSt (scalar:Enum8)	Drop On Fail V6 for v6 nexthop	SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled
order	rtflt:Order (scalar:Uint32)	Order	RANGE: [0 , 65535]

rtmapSetNh Properties

Property Name	Data Type	Description	Values
addr	address:Ip	The peer IP address.	Value must match ipv4 or ipv6 known format

Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

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

Note: The property information for this example was added in Release 9.3(3).

MO	DN
rpmEntity	sys/rpm
rtmapRule	sys/rpm/rtmap-{[name]}
rtmapEntry	sys/rpm/rtmap-{[name]}/ent-{order}
rtmapSetNh	sys/rpm/rtmap-{[name]}/ent-{order}/nh-{[addr]}

rtmapRule Properties

Property Name	Data Type	Description	Values
name	pol:ObjName (naming:Name256)	Object name	RANGE: [0 , 63]

rtmapEntry Properties

Property Name	Data Type	Description	Values
action	rtflt:Action (scalar:Enum8)	Action	SELECTION: 0 - deny 1 - permit DEFAULT: permit
dropOnFailV6	rtmap:AdminSt (scalar:Enum8)	Drop On Fail V6 for v6 nexthop	SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled
order	rtflt:Order (scalar:Uint32)	Order	RANGE: [0 , 65535]

rtmapSetNh Properties

Property Name	Data Type	Description	Values
addr	address:Ip	The peer IP address.	Value must match ipv4 or ipv6 known format
status	mo:ModificationStatus (scalar:Bitmask32)	The upgrade status. This property is for internal use only.	SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced

Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring to Maintain Next-Hop Order as per CLI Config

Configuring to Maintain Next-Hop Order as per CLI Config

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",
                  "verifyAvailabilityV6": "enabled"
                },
                "children": [
                  {
                    "rtmapSetNh": {
                      "attributes": {
                        "addr": "1:2::3:4",
                        "trackId": "240"
}}}]}}]}}]}}

{
    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>
            <verifyAvailabilityV6>enabled</verifyAvailabilityV6>
            <nh-items>
              <SetNh-list>
                <addr>1:2::3:4</addr>
                <trackId>240</trackId>
              </SetNh-list>
            </nh-items>
          </Entry-list>
        </ent-items>
      </Rule-list>
    </rtmap-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.3(5).

CLI Commands

route-map Map_1
set ipv6 next-hop verify-availability 1:2::3:4 track 240 force-order

Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MO	DN
rpmEntity	sys/rpm
rtmapRule	sys/rpm/rtmap-[Map_1]
rtmapEntry	sys/rpm/rtmap-[Map_1]/ent-10
rtmapSetNh	sys/rpm/rtmap-[Map_1]/ent-10/nh-[1:2::3:4]

rtmapRule Properties

Property Name	Data Type	Description	Values
name	pol:ObjName (naming:Name256)	Object name	RANGE: [0 , 63]

rtmapEntry Properties

Property Name	Data Type	Description	Values
action	rtflt:Action (scalar:Enum8)	Action	SELECTION: 0 - deny 1 - permit DEFAULT: permit
forceOrderV6	rtmap:AdminSt (scalar:Enum8)	Force Order V6	SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled
order	rtflt:Order (scalar:Uint32)	Order	RANGE: [0 , 65535]
verifyAvailabilityV6	rtmap:AdminSt (scalar:Enum8)	Next Hop with V6 Verify Availability	SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled

rtmapSetNh Properties

Property Name	Data Type	Description	Values
addr	address:Ip	The peer IP address.	Value must match ipv4 or ipv6 known format
trackId	scalar:Uint32	Track id for Next Hop VA Address	RANGE: [1 , 512]

Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting the Config to Maintain Next-Hop Order as per CLI Config

Deleting the Config to Maintain Next-Hop Order as per CLI Config

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 nc: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.3(5).

CLI Commands

route-map Map_1
no set ipv6 next-hop verify-availability 1:2::3:4 track 240 force-order

Verifying a DME Configuration

MO	DN
rpmEntity	sys/rpm
rtmapRule	sys/rpm/rtmap-[Map_1]
rtmapEntry	sys/rpm/rtmap-[Map_1]/ent-10
rtmapSetNh	sys/rpm/rtmap-[Map_1]/ent-10/nh-[1:2::3:4]

rtmapRule Properties

Property Name	Data Type	Description	Values
name	pol:ObjName (naming:Name256)	Object name	RANGE: [0 , 63]

rtmapEntry Properties

Property Name	Data Type	Description	Values
action	rtflt:Action (scalar:Enum8)	Action	SELECTION: 0 - deny 1 - permit DEFAULT: permit
forceOrderV6	rtmap:AdminSt (scalar:Enum8)	Force Order V6	SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled
order	rtflt:Order (scalar:Uint32)	Order	RANGE: [0 , 65535]

rtmapSetNh Properties

Property Name	Data Type	Description	Values
addr	address:Ip	The peer IP address.	Value must match ipv4 or ipv6 known format
status	mo:ModificationStatus (scalar:Bitmask32)	The upgrade status. This property is for internal use only.	SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced

Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring to Drop Packets When Next-Hop is Unreachable

Configuring to 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",
                  "verifyAvailabilityV6": "enabled"
                },
                "children": [
                  {
                    "rtmapSetNh": {
                      "attributes": {
                        "addr": "1:2::3:4",
                        "trackId": "240"
}}}]}}]}}]}}

{
    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>
            <verifyAvailabilityV6>enabled</verifyAvailabilityV6>
            <nh-items>
              <SetNh-list>
                <addr>1:2::3:4</addr>
                <trackId>240</trackId>
              </SetNh-list>
            </nh-items>
          </Entry-list>
        </ent-items>
      </Rule-list>
    </rtmap-items>
  </rpm-items>
</System>

Note: This example was added in Release 9.3(5).

CLI Commands

route-map Map_1
set ipv6 next-hop verify-availability 1:2::3:4 track 240 drop-on-fail

Verifying a DME Configuration

MO	DN
rpmEntity	sys/rpm
rtmapRule	sys/rpm/rtmap-[Map_1]
rtmapEntry	sys/rpm/rtmap-[Map_1]/ent-10
rtmapSetNh	sys/rpm/rtmap-[Map_1]/ent-10/nh-[1:2::3:4]

rtmapRule Properties

Property Name	Data Type	Description	Values
name	pol:ObjName (naming:Name256)	Object name	RANGE: [0 , 63]

rtmapEntry Properties

Property Name	Data Type	Description	Values
action	rtflt:Action (scalar:Enum8)	Action	SELECTION: 0 - deny 1 - permit DEFAULT: permit
dropOnFailV6	rtmap:AdminSt (scalar:Enum8)	Drop On Fail V6 for v6 nexthop	SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled
order	rtflt:Order (scalar:Uint32)	Order	RANGE: [0 , 65535]
verifyAvailabilityV6	rtmap:AdminSt (scalar:Enum8)	Next Hop with V6 Verify Availability	SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled

rtmapSetNh Properties

Property Name	Data Type	Description	Values
addr	address:Ip	The peer IP address.	Value must match ipv4 or ipv6 known format
trackId	scalar:Uint32	Track id for Next Hop VA Address	RANGE: [1 , 512]

Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting the Config to Drop Packets When Next-Hop is Unreachable

Deleting the Config to 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 nc: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.3(5).

CLI Commands

route-map Map_1
no set ipv6 next-hop verify-availability 1:2::3:4 track 240 drop-on-fail

Verifying a DME Configuration

MO	DN
rpmEntity	sys/rpm
rtmapRule	sys/rpm/rtmap-[Map_1]
rtmapEntry	sys/rpm/rtmap-[Map_1]/ent-10
rtmapSetNh	sys/rpm/rtmap-[Map_1]/ent-10/nh-[1:2::3:4]

rtmapRule Properties

Property Name	Data Type	Description	Values
name	pol:ObjName (naming:Name256)	Object name	RANGE: [0 , 63]

rtmapEntry Properties

Property Name	Data Type	Description	Values
action	rtflt:Action (scalar:Enum8)	Action	SELECTION: 0 - deny 1 - permit DEFAULT: permit
dropOnFailV6	rtmap:AdminSt (scalar:Enum8)	Drop On Fail V6 for v6 nexthop	SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled
order	rtflt:Order (scalar:Uint32)	Order	RANGE: [0 , 65535]

rtmapSetNh Properties

Property Name	Data Type	Description	Values
addr	address:Ip	The peer IP address.	Value must match ipv4 or ipv6 known format
status	mo:ModificationStatus (scalar:Bitmask32)	The upgrade status. This property is for internal use only.	SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced

Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html