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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
size | pim:Size (scalar:Uint32) | configures buffer size in text/kb | RANGE: [0 , 4] DEFAULT: 3 |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
size | pim:Size (scalar:Uint32) | configures buffer size in text/kb | RANGE: [0 , 4] DEFAULT: 3 |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
size | pim:Size (scalar:Uint32) | configures buffer size in text/kb | RANGE: [0 , 4] DEFAULT: 3 |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
size | pim:Size (scalar:Uint32) | configures buffer size in text/kb | RANGE: [0 , 4] DEFAULT: 3 |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
size | pim:Size (scalar:Uint32) | configures buffer size in text/kb | RANGE: [0 , 4] DEFAULT: 3 |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
size | pim:Size (scalar:Uint32) | configures buffer size in text/kb | RANGE: [0 , 4] DEFAULT: 3 |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
size | pim:Size (scalar:Uint32) | configures buffer size in text/kb | RANGE: [0 , 4] DEFAULT: 3 |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
size | pim:Size (scalar:Uint32) | configures buffer size in text/kb | RANGE: [0 , 4] DEFAULT: 3 |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
size | pim:Size (scalar:Uint32) | configures buffer size in text/kb | RANGE: [0 , 4] DEFAULT: 3 |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
size | pim:Size (scalar:Uint32) | configures buffer size in text/kb | RANGE: [0 , 4] DEFAULT: 3 |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
size | pim:Size (scalar:Uint32) | configures buffer size in text/kb | RANGE: [0 , 4] DEFAULT: 3 |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
size | pim:Size (scalar:Uint32) | configures buffer size in text/kb | RANGE: [0 , 4] DEFAULT: 3 |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
size | pim:Size (scalar:Uint32) | configures buffer size in text/kb | RANGE: [0 , 4] DEFAULT: 3 |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
size | pim:Size (scalar:Uint32) | configures buffer size in text/kb | RANGE: [0 , 4] DEFAULT: 3 |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
size | pim:Size (scalar:Uint32) | configures buffer size in text/kb | RANGE: [0 , 4] DEFAULT: 3 |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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
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.
MO | DN |
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 Name | Data Type | Description | Values |
name | naming: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 Name | Data Type | Description | Values |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
type | pim:EhType (scalar:Enum32) | configures type of event history | SELECTION: 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