Configuring PIM Flooding Mechanism with Source Discovery (PFM-SD)

Configuring PFM-SD

Configuring PFM-SD
POST http://<mgmt_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "pimEntity": {
          "children": [
            {
              "pimInst": {
                "children": [
                  {
                    "pimDom": {
                      "attributes": {
                        "name": "default"
                      },
                      "children": [
                        {
                          "pimPfmsd": {
                            "attributes": {
                              "announcementInterval": "100",
                              "announcementRate": "10",
                              "announcementgapInterval": "1200",
                              "grpRange": "225.0.0.0/24",
                              "originator": "lo0",
                              "pfxList": "",
                              "rtMap": "",
                              "sourceHoldTime": "60"
                            }
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}   
{
    imdata:[]
}
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
  <System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
        <pim-items>
          <inst-items>
            <dom-items>
              <Dom-list>
                <name>default</name>
                <pfmsd-items>
                  <grpRange>225.0.0.0/24</grpRange>
                  <originator>lo0</originator>
                  <announcementInterval>100</announcementInterval>
                  <announcementgapInterval>1200</announcementgapInterval>
                  <announcementRate>10</announcementRate>
                  <sourceHoldTime>60</sourceHoldTime>
                </pfmsd-items>
              </Dom-list>
            </dom-items>
          </inst-items>
        </pim-items>


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.

  1. [no] ip pim pfm-sd range {prefix | { route-map route-map-name } | { prefix-list prefix-list-name }}
  2. [no] ip pim pfm-sd originator-id {interface}
  3. [no] ip pim pfm-sd announcement interval { interval }
  4. [no] ip pim pfm-sd announcement gap { interval }
  5. [no] ip pim pfm-sd announcement rate { rate }
  6. [no] ip pim pfm-sd gsh holdtime { holdtime }

Note: The property information for this example was added in release 10.3(2)F.


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
pimPfmsd sys/pim/inst/dom-default/pfmsd


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 PFM-SD Boundary

Configuring PFM-SD Boundary
POST http://<mgmt_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "pimEntity": {
          "children": [
            {
              "pimInst": {
                "children": [
                  {
                    "pimDom": {
                      "attributes": {
                        "name": "default"
                      },
                      "children": [
                        {
                          "pimIf": {
                            "attributes": {
                              "id": "eth1/1",
                              "pfmSdBoundary": "in"
                            }
                          }
                        }
                      ]
                    }
                  }
                ]
              }
            }
          ]
        }
      },
      {
        "interfaceEntity": {
          "children": [
            {
              "l1PhysIf": {
                "attributes": {
                  "id": "eth1/1"
                }
              }
            }
          ]
        }
      }
    ]
  }
}   
{
    imdata:[]
}
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
<System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
        <pim-items>
          <inst-items>
            <dom-items>
              <Dom-list>
                <name>default</name>
                <if-items>
                  <If-list>
                    <id>eth1/1</id>
                    <pfmSdBoundary/>
                  </If-list>
                </if-items>
              </Dom-list>
            </dom-items>
          </inst-items>
        </pim-items>


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.

[no] ip pim pfm-sd {boundary [direction]}

Note: The property information for this example was added in release 10.3(2)F.


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
pimIf sys/pim/inst/dom-default/if-[interface_name]


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