Configuring Event History Buffers for PIM

These examples demonstrate how to configure the size of the event history buffers. The options are small, medium, large, and disabled. The default is small.

Configuring Assert Event History Buffers For PIM

Configuring Assert Event History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "size": "medium",
                  "type": "assert"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list>
              <type>assert</type>
              <size>medium</size>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

ip pim event-history assert size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
sizepim:Size
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4]
DEFAULT: 3
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 Assert Event History Buffers For PIM

Deleting Assert Event History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "status": "deleted",
                  "type": "assert"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list xc:operation="delete">
              <type>assert</type>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no ip pim event-history assert size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 Bidir Event History Buffers For PIM

Configuring Bidir Event History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "size": "medium",
                  "type": "bidir"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list>
              <type>bidir</type>
              <size>medium</size>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

ip pim event-history bidir size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
sizepim:Size
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4]
DEFAULT: 3
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 Bidir Events History Buffers For PIM

Deleting Bidir Events History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "status": "deleted",
                  "type": "bidir"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list xc:operation="delete">
              <type>bidir</type>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no ip pim event-history bidir size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 CLI Event History Buffers For PIM

Configuring CLI Event History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "size": "medium",
                  "type": "cli"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list>
              <type>cli</type>
              <size>medium</size>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

ip pim event-history cli size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
sizepim:Size
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4]
DEFAULT: 3
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 CLI Events History Buffers For PIM

Deleting CLI Events History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "status": "deleted",
                  "type": "cli"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list xc:operation="delete">
              <type>cli</type>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no ip pim event-history cli size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 Data Register Received Event History Buffers For PIM

Configuring Data Register Received Event History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "size": "medium",
                  "type": "dataRegRecv"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list>
              <type>dataRegRecv</type>
              <size>medium</size>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

ip pim event-history data-register-receive size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
sizepim:Size
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4]
DEFAULT: 3
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 Data Register Received History Buffers For PIM

Deleting Data Register Received History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "status": "deleted",
                  "type": "dataRegRecv"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list xc:operation="delete">
              <type>dataRegRecv</type>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no ip pim event-history data-register-receive size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 Hello Received Event History Buffers For PIM

Configuring Hello Received Event History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "size": "medium",
                  "type": "hello"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list>
              <type>hello</type>
              <size>medium</size>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

ip pim event-history hello size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
sizepim:Size
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4]
DEFAULT: 3
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 Hello Received Event History Buffers For PIM

Deleting Hello Received Event History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "status": "deleted",
                  "type": "hello"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list xc:operation="delete">
              <type>hello</type>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no ip pim event-history hello size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 Event History Buffers For PIM

Configuring Join Prune Event History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "size": "medium",
                  "type": "joinPrune"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list>
              <type>joinPrune</type>
              <size>medium</size>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

ip pim event-history join-prune size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
sizepim:Size
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4]
DEFAULT: 3
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 Event History Buffers For PIM

Deleting Join Prune Event History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "status": "deleted",
                  "type": "joinPrune"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list xc:operation="delete">
              <type>joinPrune</type>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no ip pim event-history join-prune size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 MRIB Event History Buffers For PIM

Configuring MRIB Event History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "size": "medium",
                  "type": "mrib"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list>
              <type>mrib</type>
              <size>medium</size>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

ip pim event-history mrib size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
sizepim:Size
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4]
DEFAULT: 3
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 MRIB Event History Buffers For PIM

Deleting MRIB Event History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "status": "deleted",
                  "type": "mrib"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list xc:operation="delete">
              <type>mrib</type>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no ip pim event-history mrib size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 Null Register Event History Buffers For PIM

Configuring Null Register Event History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "size": "medium",
                  "type": "nullReg"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list>
              <type>nullReg</type>
              <size>medium</size>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

ip pim event-history null-register size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
sizepim:Size
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4]
DEFAULT: 3
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 Null Register Event History Buffers For PIM

Deleting Null Register Event History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "status": "deleted",
                  "type": "nullReg"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list xc:operation="delete">
              <type>nullReg</type>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no ip pim event-history null-register size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 Packet Event History Buffers For PIM

Configuring Packet Event History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "size": "medium",
                  "type": "packet"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list>
              <type>packet</type>
              <size>medium</size>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

ip pim event-history packet size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
sizepim:Size
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4]
DEFAULT: 3
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 Packet Event History Buffers For PIM

Deleting Packet Event History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "status": "deleted",
                  "type": "packet"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list xc:operation="delete">
              <type>packet</type>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no ip pim event-history packet size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 Internal Event History Buffers For PIM

Configuring Internal Event History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "size": "medium",
                  "type": "pimInternal"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list>
              <type>pimInternal</type>
              <size>medium</size>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

ip pim event-history pim-internal size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
sizepim:Size
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4]
DEFAULT: 3
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 Internal Event History Buffers For PIM

Deleting Internal Event History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "status": "deleted",
                  "type": "pimInternal"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list xc:operation="delete">
              <type>pimInternal</type>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no ip pim event-history pim-internal size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 PIM Library Event History Buffers

Configuring PIM Library Event History Buffers
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "size": "medium",
                  "type": "pimLib"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list>
              <type>pimLib</type>
              <size>medium</size>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

ip pim event-history pim-library size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
sizepim:Size
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4]
DEFAULT: 3
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 PIM Library Event History Buffers

Deleting PIM Library Event History Buffers
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "status": "deleted",
                  "type": "pimLib"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list xc:operation="delete">
              <type>pimLib</type>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no ip pim event-history pim-library size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 RP Event History Buffers For PIM

Configuring RP Event History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "size": "medium",
                  "type": "rp"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list>
              <type>rp</type>
              <size>medium</size>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

ip pim event-history rp size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
sizepim:Size
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4]
DEFAULT: 3
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 RP Event History Buffers For PIM

Deleting RP Event History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "status": "deleted",
                  "type": "rp"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list xc:operation="delete">
              <type>rp</type>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no ip pim event-history rp size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 Txlist Event History Buffers For PIM

Configuring Txlist Event History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "size": "medium",
                  "type": "txlist"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list>
              <type>txlist</type>
              <size>medium</size>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

ip pim event-history txlist size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
sizepim:Size
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4]
DEFAULT: 3
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 Txlist Event History Buffers For PIM

Deleting Txlist Event History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "status": "deleted",
                  "type": "txlist"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list xc:operation="delete">
              <type>txlist</type>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no ip pim event-history txlist size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 VPC Event History Buffers For PIM

Configuring VPC Event History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "size": "medium",
                  "type": "vpc"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list>
              <type>vpc</type>
              <size>medium</size>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

ip pim event-history vpc size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
sizepim:Size
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4]
DEFAULT: 3
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 VPC Event History Buffers For PIM

Deleting VPC Event History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "status": "deleted",
                  "type": "vpc"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list xc:operation="delete">
              <type>vpc</type>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no ip pim event-history vpc size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 VRF Event History Buffers For PIM

Configuring VRF Event History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "size": "medium",
                  "type": "vrf"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list>
              <type>vrf</type>
              <size>medium</size>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

ip pim event-history vrf size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
sizepim:Size
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4]
DEFAULT: 3
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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 VRF Event History Buffers For PIM

Deleting VRF Event History Buffers For PIM
POST http://<mgmt0_IP>/api/mo/sys/pim/inst.json
{
  "pimInst": {
    "children": [
      {
        "pimDom": {
          "attributes": {
            "name": "default"
          },
          "children": [
            {
              "pimEventHistory": {
                "attributes": {
                  "status": "deleted",
                  "type": "vrf"
}}}]}}]}}
{
    "imdata": []
}
<System>
  <pim-items>
    <inst-items>
      <dom-items>
        <Dom-list>
          <name>default</name>
          <eventHist-items>
            <EventHistory-list xc:operation="delete">
              <type>vrf</type>
            </EventHistory-list>
          </eventHist-items>
        </Dom-list>
      </dom-items>
    </inst-items>
  </pim-items>
</System>

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


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

no ip pim event-history vrf size medium

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
pimInst sys/pim/inst
pimDom sys/pim/inst/dom-{name}
pimEventHistory sys/pim/inst/dom-{name}/eventHist-{type}


pimDom Properties

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


pimEventHistory Properties

The following table contains information about the pimEventHistory 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
typepim:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - assert
1 - bidir
2 - cli
3 - dataRegRecv
4 - hello
5 - joinPrune
6 - mrib
7 - nullReg
8 - packet
9 - nbm
10 - pimInternal
11 - pimLib
12 - rp
13 - txlist
14 - vpc
15 - vrf
16 - jpSum
17 - jpTw


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