Configuring PIM6 on a VRF

Configuring an RP in an Anycast-RP Set (Using PIM6)

Configuring an RP in an Anycast-RP Set (Using PIM6) 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6AcastRpFuncP": {
                            "children": [
                              {
                                "pim6AcastRpPeer": {
                                  "attributes": {
                                    "addr": "1:2::3:4/128",
                                    "rpSetAddr": "4:3::2:1/128"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <acastrpfunc-items>
            <peer-items>
              <AcastRpPeer-list>
                <addr>1:2::3:4/128</addr>
                <rpSetAddr>4:3::2:1/128</rpSetAddr>
              </AcastRpPeer-list>
            </peer-items>
          </acastrpfunc-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 ipv6 pim anycast-rp 1:2::3:4 4:3::2:1

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6AcastRpFuncP sys/pim6/inst/dom-{name}/acastrpfunc
pim6AcastRpPeer sys/pim6/inst/dom-{name}/acastrpfunc/peer-{[addr]}-peer-{[rpSetAddr]}


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6AcastRpPeer Properties

The following table contains information about the pim6AcastRpPeer 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 NameData TypeDescriptionValues
addraddress:Ip
AddressValue must match ipv4 or ipv6 known format
rpSetAddraddress:Ip
IP Address of node performing the functionValue 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 an RP in an Anycast-RP Set (Using PIM6)

Deleting an RP in an Anycast-RP Set (Using PIM6) 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6AcastRpFuncP": {
                            "children": [
                              {
                                "pim6AcastRpPeer": {
                                  "attributes": {
                                    "addr": "1:2::3:4/128",
                                    "rpSetAddr": "4:3::2:1/128",
                                    "status": "deleted"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <acastrpfunc-items>
            <peer-items>
              <AcastRpPeer-list xc:operation="delete">
                <addr>1:2::3:4/128</addr>
                <rpSetAddr>4:3::2:1/128</rpSetAddr>
              </AcastRpPeer-list>
            </peer-items>
          </acastrpfunc-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim anycast-rp 1:2::3:4 4:3::2:1

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6AcastRpFuncP sys/pim6/inst/dom-{name}/acastrpfunc
pim6AcastRpPeer sys/pim6/inst/dom-{name}/acastrpfunc/peer-{[addr]}-peer-{[rpSetAddr]}


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6AcastRpPeer Properties

The following table contains information about the pim6AcastRpPeer 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 NameData TypeDescriptionValues
addraddress:Ip
AddressValue must match ipv4 or ipv6 known format
rpSetAddraddress:Ip
IP Address of node performing the functionValue must match ipv4 or ipv6 known format
statusmo: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 Remove Routes When Restarting PIM6

Configuring Remove Routes When Restarting PIM6 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "flushRoutes": "yes",
                        "name": "VRF_1"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <flushRoutes>true</flushRoutes>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 ipv6 pim flush-routes

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
flushRoutesscalar:Bool
Flush RoutesSELECTION: true or false
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


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 Remove Routes When Restarting PIM6

Deleting Remove Routes When Restarting PIM6 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "flushRoutes": "no",
                        "name": "VRF_1"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <flushRoutes>false</flushRoutes>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim flush-routes

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
flushRoutesscalar:Bool
Flush RoutesSELECTION: true or false
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


Related Documentation

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

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

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

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

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

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

Configuring the Log Up/Down PIM6 Neighbor Transitions

Configuring the Log Up/Down PIM6 Neighbor Transitions 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "logNbhChng": "yes",
                        "name": "VRF_1"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <logNbhChng>true</logNbhChng>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 ipv6 pim log-neighbor-changes

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
logNbhChngscalar:Bool
Log Neighbhor changesSELECTION: true or false
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


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 Log Up/Down PIM6 Neighbor Transitions

Deleting the Log Up/Down PIM6 Neighbor Transitions 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "logNbhChng": "no",
                        "name": "VRF_1"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <logNbhChng>false</logNbhChng>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim log-neighbor-changes

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
logNbhChngscalar:Bool
Log Neighbhor changesSELECTION: true or false
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


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

Creating a Configuration to Listen to Bootstrap Messages

Creating a Configuration to Listen to Bootstrap Messages 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6BsrP": {
                            "attributes": {
                              "ctrl": "listen"
                            }
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <bsr-items>
            <ctrl>listen</ctrl>
          </bsr-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 ipv6 pim bsr listen

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6BsrP sys/pim6/inst/dom-{name}/bsr


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6BsrP Properties

The following table contains information about the pim6BsrP 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 NameData TypeDescriptionValues
ctrlrtdmc:BSRCtrl
(scalar:Bitmask8)
ControlSELECTION:
1 - listen
2 - forward


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 to Listen to Bootstrap Messages

Deleting to Listen to Bootstrap Messages 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6BsrP": {
                            "attributes": {
                              "ctrl": ""
                            }
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <bsr-items>
            <ctrl></ctrl>
          </bsr-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim bsr listen

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6BsrP sys/pim6/inst/dom-{name}/bsr


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6BsrP Properties

The following table contains information about the pim6BsrP 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 NameData TypeDescriptionValues
ctrlrtdmc:BSRCtrl
(scalar:Bitmask8)
ControlSELECTION:
1 - listen
2 - forward


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

Creating a Configuration to Forward Bootstrap Messages

Creating a Configuration to Forward Bootstrap Messages 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6BsrP": {
                            "attributes": {
                              "ctrl": "forward"
                            }
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <bsr-items>
            <ctrl>forward</ctrl>
          </bsr-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 ipv6 pim bsr forward

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6BsrP sys/pim6/inst/dom-{name}/bsr


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6BsrP Properties

The following table contains information about the pim6BsrP 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 NameData TypeDescriptionValues
ctrlrtdmc:BSRCtrl
(scalar:Bitmask8)
ControlSELECTION:
1 - listen
2 - forward


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 Configuration to Forward Bootstrap Messages

Deleting the Configuration to Forward Bootstrap Messages 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6BsrP": {
                            "attributes": {
                              "ctrl": ""
                            }
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <bsr-items>
            <ctrl></ctrl>
          </bsr-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim bsr forward

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6BsrP sys/pim6/inst/dom-{name}/bsr


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6BsrP Properties

The following table contains information about the pim6BsrP 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 NameData TypeDescriptionValues
ctrlrtdmc:BSRCtrl
(scalar:Bitmask8)
ControlSELECTION:
1 - listen
2 - forward


Related Documentation

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

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

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

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

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

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

Configuring the Group Rangs Through Policy

Configuring the Group Rangs Through Policy 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6AsmPatP": {
                            "children": [
                              {
                                "pim6SharedRangeP": {
                                  "attributes": {
                                    "pfxList": "",
                                    "rtMap": "RT_Map1",
                                    "useSPTCommand": "no"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <asm-items>
            <shared-items>
              <pfxList></pfxList>
              <rtMap>RT_Map1</rtMap>
              <useSPTCommand>false</useSPTCommand>
            </shared-items>
          </asm-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 ipv6 pim use-shared-tree-only group-list RT_Map1

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6AsmPatP sys/pim6/inst/dom-{name}/asm
pim6SharedRangeP sys/pim6/inst/dom-{name}/asm/shared


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6SharedRangeP Properties

The following table contains information about the pim6SharedRangeP 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 NameData TypeDescriptionValues
pfxListstring:Basic
Prefix ListA sequence of characters
rtMapstring:Basic
Route MapA sequence of characters
useSPTCommandscalar:Bool
Flag to use spt-threashold commandSELECTION: true or false


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 Group Rangs Through Policy

Deleting the Group Rangs Through Policy 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6AsmPatP": {
                            "children": [
                              {
                                "pim6SharedRangeP": {
                                  "attributes": {
                                    "status": "deleted"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <asm-items>
            <shared-items xc:operation="delete">
            </shared-items>
          </asm-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim use-shared-tree-only group-list RT_Map1

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6AsmPatP sys/pim6/inst/dom-{name}/asm
pim6SharedRangeP sys/pim6/inst/dom-{name}/asm/shared


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6SharedRangeP Properties

The following table contains information about the pim6SharedRangeP 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 NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
The upgrade status. This property is for internal use only.SELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


Related Documentation

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

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

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

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

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

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

Configuring the Source-Tree Switching Threshold to Never Switch to Source Tree for a Group List

Configuring the Source-Tree Switching Threshold to Never Switch to Source Tree for a Group List 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6AsmPatP": {
                            "children": [
                              {
                                "pim6SharedRangeP": {
                                  "attributes": {
                                    "pfxList": "",
                                    "rtMap": "RtMap_1",
                                    "useSPTCommand": "yes"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <asm-items>
            <shared-items>
              <pfxList></pfxList>
              <rtMap>RtMap_1</rtMap>
              <useSPTCommand>true</useSPTCommand>
            </shared-items>
          </asm-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 ipv6 pim spt-threshold infinity group-list RtMap_1

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6AsmPatP sys/pim6/inst/dom-{name}/asm
pim6SharedRangeP sys/pim6/inst/dom-{name}/asm/shared


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6SharedRangeP Properties

The following table contains information about the pim6SharedRangeP 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 NameData TypeDescriptionValues
pfxListstring:Basic
Prefix ListA sequence of characters
rtMapstring:Basic
Route MapA sequence of characters
useSPTCommandscalar:Bool
Flag to use spt-threashold commandSELECTION: true or false


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 Source-Tree Switching Threshold to Never Switch to Source Tree for a Group List

Deleting the Source-Tree Switching Threshold to Never Switch to Source Tree for a Group List 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6AsmPatP": {
                            "children": [
                              {
                                "pim6SharedRangeP": {
                                  "attributes": {
                                    "status": "deleted"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <asm-items>
            <shared-items xc:operation="delete">
            </shared-items>
          </asm-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim spt-threshold infinity group-list RtMap_1

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6AsmPatP sys/pim6/inst/dom-{name}/asm
pim6SharedRangeP sys/pim6/inst/dom-{name}/asm/shared


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6SharedRangeP Properties

The following table contains information about the pim6SharedRangeP 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 NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
The upgrade status. This property is for internal use only.SELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


Related Documentation

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

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

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

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

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

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

Configuring the Bootstrap Protocol RP-Distribution Priority

Configuring the Bootstrap Protocol RP-Distribution Priority 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6BsrP": {
                            "children": [
                              {
                                "pim6BsrFuncP": {
                                  "attributes": {
                                    "hashLen": "10",
                                    "interval": "60",
                                    "prio": "123",
                                    "srcIf": "eth1/1"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <bsr-items>
            <bsrfunc-items>
              <hashLen>10</hashLen>
              <interval>60</interval>
              <prio>123</prio>
              <srcIf>eth1/1</srcIf>
            </bsrfunc-items>
          </bsr-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 ipv6 pim bsr bsr-candidate ethernet 1/1 hash-len 10 priority 123

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6BsrP sys/pim6/inst/dom-{name}/bsr
pim6BsrFuncP sys/pim6/inst/dom-{name}/bsr/bsrfunc


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6BsrFuncP Properties

The following table contains information about the pim6BsrFuncP 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 NameData TypeDescriptionValues
hashLenrtdmc:BSRHashLen
(scalar:Uint16)
Hash Mask LenRANGE: [0, 65535]
intervalrtdmc:BSRInterval
(scalar:Uint16)
Interval
RANGE: [1 , 65535]
DEFAULT: 60
priortdmc:BSRPrio
(scalar:Uint16)
Priority
RANGE: [1 , 255]
DEFAULT: 64
srcIfnw:IfId
(base:IfIndex)
Source InterfaceMust match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100


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 Bootstrap Protocol RP-Distribution Priority

Deleting the Bootstrap Protocol RP-Distribution Priority 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6BsrP": {
                            "children": [
                              {
                                "pim6BsrFuncP": {
                                  "attributes": {
                                    "status": "deleted"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <bsr-items>
            <bsrfunc-items xc:operation="delete">
            </bsrfunc-items>
          </bsr-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim bsr bsr-candidate ethernet 1/1 hash-len 10 priority 123

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6BsrP sys/pim6/inst/dom-{name}/bsr
pim6BsrFuncP sys/pim6/inst/dom-{name}/bsr/bsrfunc


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6BsrFuncP Properties

The following table contains information about the pim6BsrFuncP 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 NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
The upgrade status. This property is for internal use only.SELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


Related Documentation

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

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

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

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

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

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

Configuring the Priority and Interval for a Policy That Filters RP-Candidate Messages

Configuring the Priority and Interval for a Policy That Filters RP-Candidate Messages 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6BsrP": {
                            "children": [
                              {
                                "pim6RpFuncP": {
                                  "attributes": {
                                    "interval": "12",
                                    "prio": "123",
                                    "srcIf": "eth1/1"
                                  },
                                  "children": [
                                    {
                                      "pim6RpGrpRange": {
                                        "attributes": {
                                          "bidir": "no",
                                          "grpList": "ff02::1:ff00:0/1",
                                          "pfxList": "",
                                          "rtMap": ""
                                        }
                                      }
                                    }
                                  ]
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <bsr-items>
            <rpfunc-items>
              <interval>12</interval>
              <prio>123</prio>
              <srcIf>eth1/1</srcIf>
              <range-items>
                <RpGrpRange-list>
                  <bidir>false</bidir>
                  <grpList>ff02::1:ff00:0/1</grpList>
                  <pfxList></pfxList>
                  <rtMap></rtMap>
                </RpGrpRange-list>
              </range-items>
            </rpfunc-items>
          </bsr-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 ipv6 pim bsr rp-candidate ethernet 1/1 group-list FF02:0:0:0:0:1:FF00:0000/1 priority 123 interval 12

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6BsrP sys/pim6/inst/dom-{name}/bsr
pim6RpFuncP sys/pim6/inst/dom-{name}/bsr/rpfunc
pim6RpGrpRange sys/pim6/inst/dom-{name}/staticrp/rp-{[addr]}/range-{bidir}


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6RpFuncP Properties

The following table contains information about the pim6RpFuncP 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 NameData TypeDescriptionValues
intervalrtdmc:BSRInterval
(scalar:Uint16)
Interval
RANGE: [1 , 65535]
DEFAULT: 60
priortdmc:BSRPrio
(scalar:Uint16)
Priority
RANGE: [1 , 255]
DEFAULT: 64
srcIfnw:IfId
(base:IfIndex)
Source InterfaceMust match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100


pim6RpGrpRange Properties

The following table contains information about the pim6RpGrpRange 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 NameData TypeDescriptionValues
bidirscalar:Bool
BiDir GroupsSELECTION: true or false
grpListaddress:Ip
Group ListValue must match ipv4 or ipv6 known format
pfxListstring:Basic
Prefix ListA sequence of characters
rtMapstring:Basic
Route MapA sequence of characters


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 Priority and Interval for a Policy That Filters RP-Candidate Messages

Deleting the Priority and Interval for a Policy That Filters RP-Candidate Messages 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6BsrP": {
                            "children": [
                              {
                                "pim6RpFuncP": {
                                  "attributes": {
                                    "status": "deleted"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <bsr-items>
            <rpfunc-items xc:operation="delete">
            </rpfunc-items>
          </bsr-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim bsr rp-candidate ethernet 1/1 group-list FF02:0:0:0:0:1:FF00:0000/1 priority 123 interval 12

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6BsrP sys/pim6/inst/dom-{name}/bsr
pim6RpFuncP sys/pim6/inst/dom-{name}/bsr/rpfunc


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6RpFuncP Properties

The following table contains information about the pim6RpFuncP 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 NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
The upgrade status. This property is for internal use only.SELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


Related Documentation

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

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

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

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

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

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

Configuring the Policy for Filtering RP Candidate Messages with the Specified Route Map, Interval, and Prioriy Level

Configuring the Policy for Filtering RP Candidate Messages with the Specified Route Map, Interval, and Prioriy Level 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6BsrP": {
                            "children": [
                              {
                                "pim6RpFuncP": {
                                  "attributes": {
                                    "interval": "12",
                                    "prio": "123",
                                    "srcIf": "eth1/1"
                                  },
                                  "children": [
                                    {
                                      "pim6RpGrpRange": {
                                        "attributes": {
                                          "bidir": "no",
                                          "grpList": "::",
                                          "pfxList": "",
                                          "rtMap": "RtMap_1"
                                        }
                                      }
                                    }
                                  ]
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <bsr-items>
            <rpfunc-items>
              <interval>12</interval>
              <prio>123</prio>
              <srcIf>eth1/1</srcIf>
              <range-items>
                <RpGrpRange-list>
                  <bidir>false</bidir>
                  <grpList>::</grpList>
                  <pfxList></pfxList>
                  <rtMap>RtMap_1</rtMap>
                </RpGrpRange-list>
              </range-items>
            </rpfunc-items>
          </bsr-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 ipv6 pim bsr rp-candidate ethernet 1/1 route-map RtMap_1 priority 123 interval 12

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6BsrP sys/pim6/inst/dom-{name}/bsr
pim6RpFuncP sys/pim6/inst/dom-{name}/bsr/rpfunc
pim6RpGrpRange sys/pim6/inst/dom-{name}/staticrp/rp-{[addr]}/range-{bidir}


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6RpFuncP Properties

The following table contains information about the pim6RpFuncP 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 NameData TypeDescriptionValues
intervalrtdmc:BSRInterval
(scalar:Uint16)
Interval
RANGE: [1 , 65535]
DEFAULT: 60
priortdmc:BSRPrio
(scalar:Uint16)
Priority
RANGE: [1 , 255]
DEFAULT: 64
srcIfnw:IfId
(base:IfIndex)
Source InterfaceMust match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100


pim6RpGrpRange Properties

The following table contains information about the pim6RpGrpRange 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 NameData TypeDescriptionValues
bidirscalar:Bool
BiDir GroupsSELECTION: true or false
grpListaddress:Ip
Group ListValue must match ipv4 or ipv6 known format
pfxListstring:Basic
Prefix ListA sequence of characters
rtMapstring:Basic
Route MapA sequence of characters


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 Policy for Filtering RP Candidate Messages with the Specified Route Map, Interval, and Prioriy Level

Deleting the Policy for Filtering RP Candidate Messages with the Specified Route Map, Interval, and Prioriy Level 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6BsrP": {
                            "children": [
                              {
                                "pim6RpFuncP": {
                                  "attributes": {
                                    "status": "deleted"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <bsr-items>
            <rpfunc-items xc:operation="delete">
            </rpfunc-items>
          </bsr-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim bsr rp-candidate ethernet 1/1 route-map RtMap_1 priority 123 interval 12

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6BsrP sys/pim6/inst/dom-{name}/bsr
pim6RpFuncP sys/pim6/inst/dom-{name}/bsr/rpfunc


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6RpFuncP Properties

The following table contains information about the pim6RpFuncP 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 NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
The upgrade status. This property is for internal use only.SELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


Related Documentation

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

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

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

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

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

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

Configuring the Static RP for a Group Range

Configuring the Static RP for a Group Range 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6StaticRPP": {
                            "children": [
                              {
                                "pim6StaticRP": {
                                  "attributes": {
                                    "addr": "1:2::3:4/128"
                                  },
                                  "children": [
                                    {
                                      "pim6RpGrpRange": {
                                        "attributes": {
                                          "bidir": "no",
                                          "override": "no",
                                          "pfxList": "",
                                          "rtMap": "RtMap_1"
                                        }
                                      }
                                    }
                                  ]
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <staticrp-items>
            <rp-items>
              <StaticRP-list>
                <addr>1:2::3:4/128</addr>
                <range-items>
                  <RpGrpRange-list>
                    <bidir>false</bidir>
                    <override>false</override>
                    <pfxList></pfxList>
                    <rtMap>RtMap_1</rtMap>
                  </RpGrpRange-list>
                </range-items>
              </StaticRP-list>
            </rp-items>
          </staticrp-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 ipv6 pim rp-address 1:2::3:4 route-map RtMap_1

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6StaticRPP sys/pim6/inst/dom-{name}/staticrp
pim6StaticRP sys/pim6/inst/dom-{name}/staticrp/rp-{[addr]}
pim6RpGrpRange sys/pim6/inst/dom-{name}/staticrp/rp-{[addr]}/range-{bidir}


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6StaticRP Properties

The following table contains information about the pim6StaticRP 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 NameData TypeDescriptionValues
addraddress:Ip
AddressValue must match ipv4 or ipv6 known format


pim6RpGrpRange Properties

The following table contains information about the pim6RpGrpRange 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 NameData TypeDescriptionValues
bidirscalar:Bool
BiDir GroupsSELECTION: true or false
overridescalar:Bool
Flag to override RP preference to choose static RPSELECTION: true or false
pfxListstring:Basic
Prefix ListA sequence of characters
rtMapstring:Basic
Route MapA sequence of characters


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 Static RP for a Group Range

Deleting the Static RP for a Group Range 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6StaticRPP": {
                            "children": [
                              {
                                "pim6StaticRP": {
                                  "attributes": {
                                    "addr": "1:2::3:4/128",
                                    "status": "deleted"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <staticrp-items>
            <rp-items>
              <StaticRP-list xc:operation="delete">
                <addr>1:2::3:4/128</addr>
              </StaticRP-list>
            </rp-items>
          </staticrp-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim rp-address 1:2::3:4 route-map RtMap_1

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6StaticRPP sys/pim6/inst/dom-{name}/staticrp
pim6StaticRP sys/pim6/inst/dom-{name}/staticrp/rp-{[addr]}


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6StaticRP Properties

The following table contains information about the pim6StaticRP 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 NameData TypeDescriptionValues
addraddress:Ip
AddressValue must match ipv4 or ipv6 known format
statusmo:ModificationStatus
(scalar:Bitmask32)
The upgrade status. This property is for internal use only.SELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


Related Documentation

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

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

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

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

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

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

Configuring the Override and Prefix List Policy for a Static RP

Configuring the Override and Prefix List Policy for a Static RP 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6StaticRPP": {
                            "children": [
                              {
                                "pim6StaticRP": {
                                  "attributes": {
                                    "addr": "1:2::3:4/128"
                                  },
                                  "children": [
                                    {
                                      "pim6RpGrpRange": {
                                        "attributes": {
                                          "bidir": "yes",
                                          "override": "yes"
                                        }
                                      }
                                    },
                                    {
                                      "pim6RpGrpRange": {
                                        "attributes": {
                                          "bidir": "no",
                                          "pfxList": "List_1",
                                          "rtMap": ""
                                        }
                                      }
                                    }
                                  ]
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <staticrp-items>
            <rp-items>
              <StaticRP-list>
                <addr>1:2::3:4/128</addr>
                <range-items>
                  <RpGrpRange-list>
                    <bidir>true</bidir>
                    <override>true</override>
                  </RpGrpRange-list>
                  <RpGrpRange-list>
                    <bidir>false</bidir>
                    <pfxList>List_1</pfxList>
                    <rtMap></rtMap>
                  </RpGrpRange-list>
                </range-items>
              </StaticRP-list>
            </rp-items>
          </staticrp-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 ipv6 pim rp-address 1:2::3:4 prefix-list List_1 override

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6StaticRPP sys/pim6/inst/dom-{name}/staticrp
pim6StaticRP sys/pim6/inst/dom-{name}/staticrp/rp-{[addr]}
pim6RpGrpRange sys/pim6/inst/dom-{name}/staticrp/rp-{[addr]}/range-{bidir}


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6StaticRP Properties

The following table contains information about the pim6StaticRP 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 NameData TypeDescriptionValues
addraddress:Ip
AddressValue must match ipv4 or ipv6 known format


pim6RpGrpRange Properties

The following table contains information about the pim6RpGrpRange 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 NameData TypeDescriptionValues
bidirscalar:Bool
BiDir GroupsSELECTION: true or false
overridescalar:Bool
Flag to override RP preference to choose static RPSELECTION: true or false


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 Override and Prefix List Policy for a Static RP

Deleting the Override and Prefix List Policy for a Static RP 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6StaticRPP": {
                            "children": [
                              {
                                "pim6StaticRP": {
                                  "attributes": {
                                    "addr": "1:2::3:4/128",
                                    "status": "deleted"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <staticrp-items>
            <rp-items>
              <StaticRP-list xc:operation="delete">
                <addr>1:2::3:4/128</addr>
              </StaticRP-list>
            </rp-items>
          </staticrp-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim rp-address 1:2::3:4 prefix-list List_1 override

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6StaticRPP sys/pim6/inst/dom-{name}/staticrp
pim6StaticRP sys/pim6/inst/dom-{name}/staticrp/rp-{[addr]}


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6StaticRP Properties

The following table contains information about the pim6StaticRP 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 NameData TypeDescriptionValues
addraddress:Ip
AddressValue must match ipv4 or ipv6 known format
statusmo:ModificationStatus
(scalar:Bitmask32)
The upgrade status. This property is for internal use only.SELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


Related Documentation

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

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

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

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

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

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

Configuring the State Limit

Configuring the State Limit 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6ResP": {
                            "attributes": {
                              "max": "1234",
                              "rsvd": "123",
                              "rtMap": "RtMap_1"
                            }
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <limit-items>
            <max>1234</max>
            <rsvd>123</rsvd>
            <rtMap>RtMap_1</rtMap>
          </limit-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 ipv6 pim state-limit 1234 reserved RtMap_1 123

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6ResP sys/pim6/inst/dom-{name}/limit


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6ResP Properties

The following table contains information about the pim6ResP 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 NameData TypeDescriptionValues
maxmcast:NumEntries
(scalar:Uint32)
Maximum Multicast Entries
RANGE: [0 , 4294967295]
DEFAULT: 0
rsvdmcast:NumEntries
(scalar:Uint32)
Reserved Multicast Entries
RANGE: [0 , 4294967295]
DEFAULT: 0
rtMapstring:Basic
Reserved Entries Route MapA sequence of characters


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

Deleting the State Limit 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6ResP": {
                            "attributes": {
                              "status": "deleted"
                            }
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <limit-items xc:operation="delete">
          </limit-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim state-limit 1234 reserved RtMap_1 123

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6ResP sys/pim6/inst/dom-{name}/limit


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6ResP Properties

The following table contains information about the pim6ResP 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 NameData TypeDescriptionValues
statusmo: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

Deleting the router configuration to send Auto-RP Announce messages

Deleting the router configuration to send Auto-RP Announce messages
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6AutoRPP": {
                            "children": [
                              {
                                "pim6RpFuncP": {
                                  "attributes": {
                                    "status": "deleted"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <autorp-items>
            <rpfunc-items xc:operation="delete">
            </rpfunc-items>
          </autorp-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim send-rp-announce ethernet 1/1 interval 12

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6RpFuncP sys/pim6/inst/dom-{name}/bsr/rpfunc


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6RpFuncP Properties

The following table contains information about the pim6RpFuncP 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 NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
The upgrade status. This property is for internal use only.SELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


Related Documentation

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

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

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

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

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

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

Configuring the Policy for Filtering Mapping Agent Messages with a Route Map

Configuring the Policy for Filtering Mapping Agent Messages with a Route Map 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6AutoRPP": {
                            "children": [
                              {
                                "pim6MaFilterP": {
                                  "attributes": {
                                    "rtMap": "RtMap_1"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <autorp-items>
            <mafilter-items>
              <rtMap>RtMap_1</rtMap>
            </mafilter-items>
          </autorp-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 ipv6 pim auto-rp mapping-agent-policy RtMap_1

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


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 Policy for Filtering Mapping Agent Messages with a Route Map

Deleting the Policy for Filtering Mapping Agent Messages with a Route Map 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6AutoRPP": {
                            "children": [
                              {
                                "pim6MaFilterP": {
                                  "attributes": {
                                    "status": "deleted"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <autorp-items>
            <mafilter-items xc:operation="delete">
            </mafilter-items>
          </autorp-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim auto-rp mapping-agent-policy RtMap_1

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


Related Documentation

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

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

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

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

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

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

Configuring the Policy for Filtering Mapping Agent Messages with a Route Policy

Configuring the Policy for Filtering Mapping Agent Messages with a Route Policy 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6AutoRPP": {
                            "children": [
                              {
                                "pim6MaFilterP": {
                                  "attributes": {
                                    "rtMap": "RT_POL"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <autorp-items>
            <mafilter-items>
              <rtMap>RT_POL</rtMap>
            </mafilter-items>
          </autorp-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 ipv6 pim auto-rp mapping-agent-policy RT_POL

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


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 Policy for Filtering Mapping Agent Messages with a Route Policy

Deleting the Policy for Filtering Mapping Agent Messages with a Route Policy 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6AutoRPP": {
                            "children": [
                              {
                                "pim6MaFilterP": {
                                  "attributes": {
                                    "status": "deleted"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <autorp-items>
            <mafilter-items xc:operation="delete">
            </mafilter-items>
          </autorp-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim auto-rp mapping-agent-policy RT_POL

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


Related Documentation

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

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

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

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

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

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

Configuring the Auto-RP Protocol RP-Distribution Configuration Policy for Filtering RP Candidate Messages with a Route Map

Configuring the Auto-RP Protocol RP-Distribution Configuration Policy for Filtering RP Candidate Messages with a Route Map 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6AutoRPP": {
                            "children": [
                              {
                                "pim6RpFilterP": {
                                  "attributes": {
                                    "rtMap": "RtMap_1"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <autorp-items>
            <rpfilter-items>
              <rtMap>RtMap_1</rtMap>
            </rpfilter-items>
          </autorp-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 ipv6 pim auto-rp rp-candidate-policy RtMap_1

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6RpFilterP sys/pim6/inst/dom-{name}/bsr/rpfilter


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6RpFilterP Properties

The following table contains information about the pim6RpFilterP 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 NameData TypeDescriptionValues
rtMapstring:Basic
Route MapA sequence of characters


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 Auto-RP Protocol RP-Distribution Configuration Policy for Filtering RP Candidate Messages with a Route Map

Deleting the Auto-RP Protocol RP-Distribution Configuration Policy for Filtering RP Candidate Messages with a Route Map 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6AutoRPP": {
                            "children": [
                              {
                                "pim6RpFilterP": {
                                  "attributes": {
                                    "status": "deleted"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <autorp-items>
            <rpfilter-items xc:operation="delete">
            </rpfilter-items>
          </autorp-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim auto-rp rp-candidate-policy RtMap_1

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6RpFilterP sys/pim6/inst/dom-{name}/bsr/rpfilter


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6RpFilterP Properties

The following table contains information about the pim6RpFilterP 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 NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
The upgrade status. This property is for internal use only.SELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


Related Documentation

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

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

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

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

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

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

Configuring the Auto-RP Protocol RP-Distribution Configuration Policy for Filtering RP Candidate Messages with a Route Policy

Configuring the Auto-RP Protocol RP-Distribution Configuration Policy for Filtering RP Candidate Messages with a Route Policy 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6AutoRPP": {
                            "children": [
                              {
                                "pim6RpFilterP": {
                                  "attributes": {
                                    "rtMap": "RT_POL"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <autorp-items>
            <rpfilter-items>
              <rtMap>RT_POL</rtMap>
            </rpfilter-items>
          </autorp-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 ipv6 pim auto-rp rp-candidate-policy RT_POL

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6RpFilterP sys/pim6/inst/dom-{name}/bsr/rpfilter


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6RpFilterP Properties

The following table contains information about the pim6RpFilterP 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 NameData TypeDescriptionValues
rtMapstring:Basic
Route MapA sequence of characters


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 Auto-RP Protocol RP-Distribution Configuration Policy for Filtering RP Candidate Messages with a Route Policy

Deleting the Auto-RP Protocol RP-Distribution Configuration Policy for Filtering RP Candidate Messages with a Route Policy 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6AutoRPP": {
                            "children": [
                              {
                                "pim6RpFilterP": {
                                  "attributes": {
                                    "status": "deleted"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <autorp-items>
            <rpfilter-items xc:operation="delete">
            </rpfilter-items>
          </autorp-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim auto-rp rp-candidate-policy RT_POL

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6RpFilterP sys/pim6/inst/dom-{name}/bsr/rpfilter


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6RpFilterP Properties

The following table contains information about the pim6RpFilterP 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 NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
The upgrade status. This property is for internal use only.SELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


Related Documentation

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

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

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

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

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

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

Configuring the Policy for Filtering BSR Messages with a Route Map

Configuring the Policy for Filtering BSR Messages with a Route Map 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6BsrP": {
                            "children": [
                              {
                                "pim6BsrFilterP": {
                                  "attributes": {
                                    "rtMap": "RtMap_1"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <bsr-items>
            <bsrfilter-items>
              <rtMap>RtMap_1</rtMap>
            </bsrfilter-items>
          </bsr-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 ipv6 pim bsr bsr-policy RtMap_1

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6BsrP sys/pim6/inst/dom-{name}/bsr
pim6BsrFilterP sys/pim6/inst/dom-{name}/bsr/bsrfilter


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6BsrFilterP Properties

The following table contains information about the pim6BsrFilterP 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 NameData TypeDescriptionValues
rtMapstring:Basic
Route MapA sequence of characters


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 Policy for Filtering BSR Messages with a Route Map

Deleting the Policy for Filtering BSR Messages with a Route Map 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6BsrP": {
                            "children": [
                              {
                                "pim6BsrFilterP": {
                                  "attributes": {
                                    "status": "deleted"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <bsr-items>
            <bsrfilter-items xc:operation="delete">
            </bsrfilter-items>
          </bsr-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim bsr bsr-policy RtMap_1

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6BsrP sys/pim6/inst/dom-{name}/bsr
pim6BsrFilterP sys/pim6/inst/dom-{name}/bsr/bsrfilter


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6BsrFilterP Properties

The following table contains information about the pim6BsrFilterP 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 NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
The upgrade status. This property is for internal use only.SELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


Related Documentation

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

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

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

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

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

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

Configuring the Policy for Filtering BSR Messages with a Route Policy

Configuring the Policy for Filtering BSR Messages with a Route Policy 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6BsrP": {
                            "children": [
                              {
                                "pim6BsrFilterP": {
                                  "attributes": {
                                    "rtMap": "RT_POL"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <bsr-items>
            <bsrfilter-items>
              <rtMap>RT_POL</rtMap>
            </bsrfilter-items>
          </bsr-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 ipv6 pim bsr bsr-policy RT_POL

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6BsrP sys/pim6/inst/dom-{name}/bsr
pim6BsrFilterP sys/pim6/inst/dom-{name}/bsr/bsrfilter


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6BsrFilterP Properties

The following table contains information about the pim6BsrFilterP 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 NameData TypeDescriptionValues
rtMapstring:Basic
Route MapA sequence of characters


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 Policy for Filtering BSR Messages with a Route Policy

Deleting the Policy for Filtering BSR Messages with a Route Policy 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6BsrP": {
                            "children": [
                              {
                                "pim6BsrFilterP": {
                                  "attributes": {
                                    "status": "deleted"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <bsr-items>
            <bsrfilter-items xc:operation="delete">
            </bsrfilter-items>
          </bsr-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim bsr bsr-policy RT_POL

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6BsrP sys/pim6/inst/dom-{name}/bsr
pim6BsrFilterP sys/pim6/inst/dom-{name}/bsr/bsrfilter


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6BsrFilterP Properties

The following table contains information about the pim6BsrFilterP 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 NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
The upgrade status. This property is for internal use only.SELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


Related Documentation

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

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

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

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

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

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

Configuring the Bootstrap Protocol RP-Distribution Configuration Policy for Filtering RP Candidate Messages with a Route Map

Configuring the Bootstrap Protocol RP-Distribution Configuration Policy for Filtering RP Candidate Messages with a Route Map 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6BsrP": {
                            "children": [
                              {
                                "pim6RpFilterP": {
                                  "attributes": {
                                    "rtMap": "RtMap_1"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <bsr-items>
            <rpfilter-items>
              <rtMap>RtMap_1</rtMap>
            </rpfilter-items>
          </bsr-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 ipv6 pim bsr rp-candidate-policy RtMap_1

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6BsrP sys/pim6/inst/dom-{name}/bsr
pim6RpFilterP sys/pim6/inst/dom-{name}/bsr/rpfilter


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6RpFilterP Properties

The following table contains information about the pim6RpFilterP 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 NameData TypeDescriptionValues
rtMapstring:Basic
Route MapA sequence of characters


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 Bootstrap Protocol RP-Distribution Configuration Policy for Filtering RP Candidate Messages with a Route Map

Deleting the Bootstrap Protocol RP-Distribution Configuration Policy for Filtering RP Candidate Messages with a Route Map 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6BsrP": {
                            "children": [
                              {
                                "pim6RpFilterP": {
                                  "attributes": {
                                    "status": "deleted"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <bsr-items>
            <rpfilter-items xc:operation="delete">
            </rpfilter-items>
          </bsr-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim bsr rp-candidate-policy RtMap_1

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6BsrP sys/pim6/inst/dom-{name}/bsr
pim6RpFilterP sys/pim6/inst/dom-{name}/bsr/rpfilter


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6RpFilterP Properties

The following table contains information about the pim6RpFilterP 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 NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
The upgrade status. This property is for internal use only.SELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


Related Documentation

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

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

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

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

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

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

Configuring the Bootstrap Protocol RP-Distribution Configuration Policy for Filtering RP Candidate Messages with a Route Policy

Configuring the Bootstrap Protocol RP-Distribution Configuration Policy for Filtering RP Candidate Messages with a Route Policy 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6BsrP": {
                            "children": [
                              {
                                "pim6RpFilterP": {
                                  "attributes": {
                                    "rtMap": "RT_POL"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <bsr-items>
            <rpfilter-items>
              <rtMap>RT_POL</rtMap>
            </rpfilter-items>
          </bsr-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 ipv6 pim bsr rp-candidate-policy RT_POL

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6BsrP sys/pim6/inst/dom-{name}/bsr
pim6RpFilterP sys/pim6/inst/dom-{name}/bsr/rpfilter


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6RpFilterP Properties

The following table contains information about the pim6RpFilterP 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 NameData TypeDescriptionValues
rtMapstring:Basic
Route MapA sequence of characters


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 Bootstrap Protocol RP-Distribution Configuration Policy for Filtering RP Candidate Messages with a Route Policy

Deleting the Bootstrap Protocol RP-Distribution Configuration Policy for Filtering RP Candidate Messages with a Route Policy 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6BsrP": {
                            "children": [
                              {
                                "pim6RpFilterP": {
                                  "attributes": {
                                    "status": "deleted"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <bsr-items>
            <rpfilter-items xc:operation="delete">
            </rpfilter-items>
          </bsr-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim bsr rp-candidate-policy RT_POL

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6BsrP sys/pim6/inst/dom-{name}/bsr
pim6RpFilterP sys/pim6/inst/dom-{name}/bsr/rpfilter


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6RpFilterP Properties

The following table contains information about the pim6RpFilterP 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 NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
The upgrade status. This property is for internal use only.SELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


Related Documentation

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

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

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

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

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

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

Configuring the Enable Listening or Forwarding of Auto-RP Messages

Configuring the Enable Listening or Forwarding of Auto-RP Messages 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6AutoRPP": {
                            "attributes": {
                              "ctrl": "listen"
                            }
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <autorp-items>
            <ctrl>listen</ctrl>
          </autorp-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 ipv6 pim auto-rp listen

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


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 Enable Listening or Forwarding of Auto-RP Messages

Deleting the Enable Listening or Forwarding of Auto-RP Messages 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6AutoRPP": {
                            "attributes": {
                              "ctrl": ""
                            }
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <autorp-items>
            <ctrl></ctrl>
          </autorp-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim auto-rp listen

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


Related Documentation

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

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

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

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

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

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

Configuring the Enabling Forwading of Auto-RP Messages

Configuring the Enabling Forwading of Auto-RP Messages 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6AutoRPP": {
                            "attributes": {
                              "ctrl": "forward"
                            }
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <autorp-items>
            <ctrl>forward</ctrl>
          </autorp-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 ipv6 pim auto-rp forward

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


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 Enabling Forwading of Auto-RP Messages

Deleting the Enabling Forwading of Auto-RP Messages 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6AutoRPP": {
                            "attributes": {
                              "ctrl": ""
                            }
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <autorp-items>
            <ctrl></ctrl>
          </autorp-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim auto-rp forward

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


Related Documentation

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

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

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

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

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

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

Configuring the Policy for Receiving Register Messages with a Route Map

Configuring the Policy for Receiving Register Messages with a Route Map 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6AsmPatP": {
                            "children": [
                              {
                                "pim6RegTrP": {
                                  "attributes": {
                                    "pfxList": "",
                                    "rtMap": "RtMap_1"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <asm-items>
            <reg-items>
              <pfxList></pfxList>
              <rtMap>RtMap_1</rtMap>
            </reg-items>
          </asm-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 ipv6 pim register-policy RtMap_1

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6AsmPatP sys/pim6/inst/dom-{name}/asm
pim6RegTrP sys/pim6/inst/dom-{name}/asm/reg


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6RegTrP Properties

The following table contains information about the pim6RegTrP 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 NameData TypeDescriptionValues
pfxListstring:Basic
Register Message Prefix ListA sequence of characters
rtMapstring:Basic
Register Message Route MapA sequence of characters


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 Policy for Receiving Register Messages with a Route Map

Deleting the Policy for Receiving Register Messages with a Route Map 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6AsmPatP": {
                            "children": [
                              {
                                "pim6RegTrP": {
                                  "attributes": {
                                    "pfxList": "",
                                    "rtMap": ""
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <asm-items>
            <reg-items>
              <pfxList></pfxList>
              <rtMap></rtMap>
            </reg-items>
          </asm-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim register-policy RtMap_1

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6AsmPatP sys/pim6/inst/dom-{name}/asm
pim6RegTrP sys/pim6/inst/dom-{name}/asm/reg


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6RegTrP Properties

The following table contains information about the pim6RegTrP 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 NameData TypeDescriptionValues
pfxListstring:Basic
Register Message Prefix ListA sequence of characters
rtMapstring:Basic
Register Message Route MapA sequence of characters


Related Documentation

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

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

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

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

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

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

Configuring the Policy for Receiving Register Messages with a Route Policy

Configuring the Policy for Receiving Register Messages with a Route Policy 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6AsmPatP": {
                            "children": [
                              {
                                "pim6RegTrP": {
                                  "attributes": {
                                    "pfxList": "",
                                    "rtMap": "RT_POL"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <asm-items>
            <reg-items>
              <pfxList></pfxList>
              <rtMap>RT_POL</rtMap>
            </reg-items>
          </asm-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 ipv6 pim register-policy RT_POL

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6AsmPatP sys/pim6/inst/dom-{name}/asm
pim6RegTrP sys/pim6/inst/dom-{name}/asm/reg


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6RegTrP Properties

The following table contains information about the pim6RegTrP 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 NameData TypeDescriptionValues
pfxListstring:Basic
Register Message Prefix ListA sequence of characters
rtMapstring:Basic
Register Message Route MapA sequence of characters


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 Policy for Receiving Register Messages with a Route Policy

Deleting the Policy for Receiving Register Messages with a Route Policy 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "pim6AsmPatP": {
                            "children": [
                              {
                                "pim6RegTrP": {
                                  "attributes": {
                                    "pfxList": "",
                                    "rtMap": ""
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <asm-items>
            <reg-items>
              <pfxList></pfxList>
              <rtMap></rtMap>
            </reg-items>
          </asm-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
</System>

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


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.

vrf context VRF_1
 no ipv6 pim register-policy RT_POL

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}
pim6AsmPatP sys/pim6/inst/dom-{name}/asm
pim6RegTrP sys/pim6/inst/dom-{name}/asm/reg


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


pim6RegTrP Properties

The following table contains information about the pim6RegTrP 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 NameData TypeDescriptionValues
pfxListstring:Basic
Register Message Prefix ListA sequence of characters
rtMapstring:Basic
Register Message Route MapA sequence of characters


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 Join-Prune Messages to Inter-Packet Delay

Configuring Join-Prune Messages to Inter-Packet Delay
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "jpDelay": "123",
                        "name": "VRF_1"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <jpDelay>123</jpDelay>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-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.

vrf context VRF_1
 ipv6 pim jp-delay 123

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
jpDelayrtdmc:JpDelayRange
(scalar:Uint32)
Join-Prune message inter-packet delay
RANGE: [1 , 4294967295]
DEFAULT: 100
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


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 Join-Prune Messages to Inter-Packet Delay

Deleting Join-Prune Messages to Inter-Packet Delay 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "jpDelay": "100",
                        "name": "VRF_1"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <jpDelay>100</jpDelay>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-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.

vrf context VRF_1
 no ipv6 pim jp-delay 123

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
jpDelayrtdmc:JpDelayRange
(scalar:Uint32)
Join-Prune message inter-packet delay
RANGE: [1 , 4294967295]
DEFAULT: 100
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


Related Documentation

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

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

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

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

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

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

Configuring the Rate Limit for PIM Data Registers

Configuring the Rate Limit for PIM Data Registers
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      },
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "name": "VRF_1",
                        "regRateLmt": "123"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <regRateLmt>123</regRateLmt>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-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.

vrf context VRF_1
 ipv6 pim register-rate-limit 123

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.

MODN
topSystem sys
l3Inst sys/inst-{name}
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-{name}


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63
regRateLmtrtdmc:RegRateRange
(scalar:Uint32)
Register rate limit for data packets per second
RANGE: [0 , 65535]
DEFAULT: 0


Related Documentation

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

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

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

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

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

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

Configuring Disabling ECMP Multicast Load Splitting

Configuring Disabling ECMP Multicast Load Splitting
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "m6ribEntity": {
          "children": [
            {
              "m6ribInst": {
                "children": [
                  {
                    "m6ribDom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "m6ribConfig": {
                            "attributes": {
                              "mode": "none",
                                                          }
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      },
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <m6rib-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <config-items>
            <mode>none</mode>
          </config-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </m6rib-items>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
</System>

Note: This example was added in Release 9.3(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.

vrf context VRF_1
  ipv6 multicast multipath none


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.

MODN
topSystem sys
m6ribEntity sys/m6rib
m6ribInst sys/m6rib/inst
m6ribDom sys/m6rib/inst/dom-VRF_1
m6ribConfig sys/m6rib/inst/dom-VRF_1/config
l3Inst sys/inst-VRF_1


m6ribDom Properties

The following table contains information about the m6ribDom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


m6ribConfig Properties

The following table contains information about the m6ribConfig 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 NameData TypeDescriptionValues
modem6rib:MultipathMode
(scalar:Enum8)
M6RIB ECMP Multicast load splittingSELECTION:
1 - none
2 - s-g-hash
DEFAULT: s-g-hash


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


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 Disabling ECMP Multicast Load Splitting

Deleting Disabling ECMP Multicast Load Splitting
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "m6ribEntity": {
          "children": [
            {
              "m6ribInst": {
                "children": [
                  {
                    "m6ribDom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "m6ribConfig": {
                            "attributes": {
                              "mode": "none",
                                                          }
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      },
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <m6rib-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <config-items>
            <mode>none</mode>
          </config-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </m6rib-items>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
</System>

Note: This example was added in Release 9.3(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.

vrf context VRF_1
  no ipv6 multicast multipath none


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.

MODN
topSystem sys
m6ribEntity sys/m6rib
m6ribInst sys/m6rib/inst
m6ribDom sys/m6rib/inst/dom-VRF_1
m6ribConfig sys/m6rib/inst/dom-VRF_1/config
l3Inst sys/inst-VRF_1


m6ribDom Properties

The following table contains information about the m6ribDom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


m6ribConfig Properties

The following table contains information about the m6ribConfig 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 NameData TypeDescriptionValues
modem6rib:MultipathMode
(scalar:Enum8)
M6RIB ECMP Multicast load splittingSELECTION:
1 - none
2 - s-g-hash
DEFAULT: s-g-hash


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


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 a Resilient RPF Interface

Configuring a Resilient RPF Interface
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "m6ribEntity": {
          "children": [
            {
              "m6ribInst": {
                "children": [
                  {
                    "m6ribDom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "m6ribConfig": {
                            "attributes": {
                              "modeResilient": "yes"
                            }
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      },
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <m6rib-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <config-items>
            <modeResilient>true</modeResilient>
          </config-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </m6rib-items>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
</System>

Note: This example was added in Release 9.3(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.

vrf context VRF_1
  ipv6 multicast multipath resilient


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.

MODN
topSystem sys
m6ribEntity sys/m6rib
m6ribInst sys/m6rib/inst
m6ribDom sys/m6rib/inst/dom-VRF_1
m6ribConfig sys/m6rib/inst/dom-VRF_1/config
l3Inst sys/inst-VRF_1


m6ribDom Properties

The following table contains information about the m6ribDom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


m6ribConfig Properties

The following table contains information about the m6ribConfig 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 NameData TypeDescriptionValues
modeResilientm6rib:ResilientType
(scalar:Bool)
Multipath Resilient RPF interface modeSELECTION: true or false
DEFAULT: false


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


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 a Resilient RPF Interface

Deleting a Resilient RPF Interface
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "m6ribEntity": {
          "children": [
            {
              "m6ribInst": {
                "children": [
                  {
                    "m6ribDom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "m6ribConfig": {
                            "attributes": {
                              "modeResilient": "no"
                            }
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      },
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <m6rib-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <config-items>
            <modeResilient>false</modeResilient>
          </config-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </m6rib-items>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
</System>

Note: This example was added in Release 9.3(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.

vrf context VRF_1
  no ipv6 multicast multipath resilient


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.

MODN
topSystem sys
m6ribEntity sys/m6rib
m6ribInst sys/m6rib/inst
m6ribDom sys/m6rib/inst/dom-VRF_1
m6ribConfig sys/m6rib/inst/dom-VRF_1/config
l3Inst sys/inst-VRF_1


m6ribDom Properties

The following table contains information about the m6ribDom 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


m6ribConfig Properties

The following table contains information about the m6ribConfig 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 NameData TypeDescriptionValues
modeResilientm6rib:ResilientType
(scalar:Bool)
Multipath Resilient RPF interface modeSELECTION: true or false
DEFAULT: false


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


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

Removing Routes when Restarting PIM6

Removing Routes when Restarting PIM6
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "flushRoutes": "yes",
                        "name": "VRF_1"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      },
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <flushRoutes>true</flushRoutes>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
</System>

Note: This example was added in Release 9.3(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.

vrf context VRF_1
  ipv6 pim flush-routes


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.

MODN
topSystem sys
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-VRF_1
l3Inst sys/inst-VRF_1


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
flushRoutesscalar:Bool
Flush RoutesSELECTION: true or false
DEFAULT: false
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


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 for Removing Routes when Restarting PIM6

Deleting the Config for Removing Routes when Restarting PIM6
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "pim6Entity": {
          "children": [
            {
              "pim6Inst": {
                "children": [
                  {
                    "pim6Dom": {
                      "attributes": {
                        "flushRoutes": "no",
                        "name": "VRF_1"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      },
      {
        "l3Inst": {
          "attributes": {
            "name": "VRF_1"
          }
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <pim6-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>VRF_1</name>
          <flushRoutes>false</flushRoutes>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim6-items>
  <inst-items>
    <Inst-list>
      <name>VRF_1</name>
    </Inst-list>
  </inst-items>
</System>

Note: This example was added in Release 9.3(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.

vrf context VRF_1
  no ipv6 pim flush-routes


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.

MODN
topSystem sys
pim6Entity sys/pim6
pim6Inst sys/pim6/inst
pim6Dom sys/pim6/inst/dom-VRF_1
l3Inst sys/inst-VRF_1


pim6Dom Properties

The following table contains information about the pim6Dom 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 NameData TypeDescriptionValues
flushRoutesscalar:Bool
Flush RoutesSELECTION: true or false
DEFAULT: false
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 63


l3Inst Properties

The following table contains information about the l3Inst 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 NameData TypeDescriptionValues
namenaming:Name256
(string:Basic)
The name of the object.
MAX SIZE: 128


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