Configuring MSDP Mesh Groups

You can use MSDP mesh groups to reduce the number of SA messages that are generated by peer-RPF flooding. By configuring a peering relationship between all the routers in a mesh and then configuring a mesh group of these routers, the SA messages that originate at a peer are sent by that peer to all other peers. SA messages received by peers in the mesh are not forwarded.

A router can participate in multiple mesh groups. By default, no mesh groups are configured.

For more information, see the Cisco Nexus 9000 Series NX-OS Multicast Routing Configuration Guide.

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

Configuring an MSDP Mesh Groups

Configuring an MSDP Mesh Groups

POST http://<IP_Address>/api/node/mo/sys/msdp/inst.json

{
  "msdpInst": {
    "children": [
      {
        "msdpDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "msdpPeer": {
                "attributes": {
                  "addr": "192.0.20.123"
                },
                "children": [
                  {
                    "msdpMeshGrp": {
                      "attributes": {
                        "grpName": "my_mesh_grp1"
}}}]}}]}}]}}

{
    "imdata": []
}

<System>
  <msdp-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <peer-items>
            <Peer-list>
              <addr>192.0.20.123</addr>
              <meshgrp-items>
                <grpName>my_mesh_grp1</grpName>
              </meshgrp-items>
            </Peer-list>
          </peer-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </msdp-items>
</System>

This example adds the peer to an MSDP mesh group.

CLI Command

The CLI command below is the equivalent to the payload example displayed in the pane on the right.

ip msdp mesh-group 192.0.20.123 my_mesh_grp1

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.

msdpDom Properties

The following table contains information about the msdpDom 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.

msdpPeer Properties

The following table contains information about the msdpPeer 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.

msdpMeshGrp Properties

The following table contains information about the msdpMeshGrp 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.

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