Configuring IGMP Global Parameters
This section contains payload examples and CLIs to demonstrate how to use the NX-API REST API to configure IGMP globally on Cisco Nexus 3000 and 9000 Series switches and to show how the REST APIs correspond to the CLI commands.
For more information about configuring IGMP, see the Cisco Nexus 9000 Series NX-OS Multicast Routing Configuration Guide.
Allowing Any Destination-IP for General Queries
Allowing Any Destination-IP for General Queries
POST http://<mgmt0_IP>/api/mo/sys/igmp.json
{
"igmpEntity": {
"children": [
{
"igmpInst": {
"attributes": {
"anyQueryDest": "yes"
}}}]}}
{
imdata:[]
}
<System>
<igmp-items>
<inst-items>
<anyQueryDest>true</anyQueryDest>
</inst-items>
</igmp-items>
</System>
Note: This example was added in Release Cisco NX-OS Release 7.0(3)I7(2).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
ip igmp any-query-destination
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 |
---|---|
igmpEntity | sys/igmp |
igmpInst | sys/igmp/inst |
igmpInst Properties
The following table contains information about the igmpInst properties in the DME 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 |
---|---|---|---|
anyQueryDest | scalar:Bool | Allow any destination-IP for General Queries | SELECTION: true or false |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the Allowance of Any Destination-IP for General Queries
Deleting the Allowance of Any Destination-IP for General Queries
POST http://<mgmt0_IP>/api/mo/sys/igmp.json
{
"igmpEntity": {
"children": [
{
"igmpInst": {
"attributes": {
"anyQueryDest": "no"
}}}]}}
{
imdata:[]
}
<System>
<igmp-items>
<inst-items>
<anyQueryDest>false</anyQueryDest>
</inst-items>
</igmp-items>
</System>
Note: This example was added in Release Cisco NX-OS Release 7.0(3)I7(2).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
no ip igmp any-query-destination
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 |
---|---|
igmpEntity | sys/igmp |
igmpInst | sys/igmp/inst |
igmpInst Properties
The following table contains information about the igmpInst properties in the DME 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 |
---|---|---|---|
anyQueryDest | scalar:Bool | Allow any destination-IP for General Queries | SELECTION: true or false |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Enforcing Router Alert Option Check for IGMPv2 and IGMPv3 Packets
Enforcing Router Alert Option Check for IGMPv2 and IGMPv3 Packets
POST http://<mgmt0_IP>/api/mo/sys/igmp.json
{
"igmpEntity": {
"children": [
{
"igmpInst": {
"attributes": {
"rtrAlert": "yes"
}}}]}}
{
imdata:[]
}
<System>
<igmp-items>
<inst-items>
<rtrAlert>true</rtrAlert>
</inst-items>
</igmp-items>
</System>
Note: This example was added in Release Cisco NX-OS Release 7.0(3)I7(2).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
ip igmp enforce-router-alert
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 |
---|---|
igmpEntity | sys/igmp |
igmpInst | sys/igmp/inst |
igmpInst Properties
The following table contains information about the igmpInst properties in the DME 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 |
---|---|---|---|
rtrAlert | scalar:Bool | Enforce Router Alert | SELECTION: true or false |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Removing the Enforcement of a Router Alert Option Check for IGMPv2 and IGMPv3 Packets
Removing the Enforcement of a Router Alert Option Check for IGMPv2 and IGMPv3 Packets
POST http://<mgmt0_IP>/api/mo/sys/igmp.json
{
"igmpEntity": {
"children": [
{
"igmpInst": {
"attributes": {
"rtrAlert": "no"
}}}]}}
{
imdata:[]
}
<System>
<igmp-items>
<inst-items>
<rtrAlert>false</rtrAlert>
</inst-items>
</igmp-items>
</System>
Note: This example was added in Release Cisco NX-OS Release 7.0(3)I7(2).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
no ip igmp enforce-router-alert
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 |
---|---|
igmpEntity | sys/igmp |
igmpInst | sys/igmp/inst |
igmpInst Properties
The following table contains information about the igmpInst properties in the DME 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 |
---|---|---|---|
rtrAlert | scalar:Bool | Enforce Router Alert | SELECTION: true or false |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Removing Routes When Restarting IGMP
Removing Routes When Restarting IGMP
POST http://<mgmt0_IP>/api/mo/sys/igmp.json
{
"igmpEntity": {
"children": [
{
"igmpInst": {
"attributes": {
"flushRoute": "yes"
}}}]}}
{
imdata:[]
}
<System>
<igmp-items>
<inst-items>
<flushRoute>true</flushRoute>
</inst-items>
</igmp-items>
</System>
Note: This example was added in Release Cisco NX-OS Release 7.0(3)I7(2).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
ip igmp flush-routes
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
igmpEntity | sys/igmp |
igmpInst | sys/igmp/inst |
igmpInst Properties
The following table contains information about the igmpInst properties in the DME 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 |
---|---|---|---|
flushRoute | scalar:Bool | Flush Routes on Restart | SELECTION: true or false |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Permitting Routes When Restarting IGMP
Permitting Routes When Restarting IGMP
POST http://<mgmt0_IP>/api/mo/sys/igmp.json
{
"igmpEntity": {
"children": [
{
"igmpInst": {
"attributes": {
"flushRoute": "no"
}}}]}}
{
imdata:[]
}
<System>
<igmp-items>
<inst-items>
<flushRoute>false</flushRoute>
</inst-items>
</igmp-items>
</System>
Note: This example was added in Release Cisco NX-OS Release 7.0(3)I7(2).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
no ip igmp flush-routes
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
igmpEntity | sys/igmp |
igmpInst | sys/igmp/inst |
igmpInst Properties
The following table contains information about the igmpInst properties in the DME 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 |
---|---|---|---|
flushRoute | scalar:Bool | Flush Routes on Restart | SELECTION: true or false |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Enabling High Availability for IGMP
Enabling High Availability for IGMP
POST http://<mgmt0_IP>/api/mo/sys/igmp.json
{
"igmpEntity": {
"children": [
{
"igmpInst": {
"attributes": {
"ctrl": "stateful-ha"
}}}]}}
{
imdata:[]
}
<System>
<igmp-items>
<inst-items>
<ctrl>stateful-ha</ctrl>
</inst-items>
</igmp-items>
</System>
Note: This example was added in Release Cisco NX-OS Release 7.0(3)I7(2).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
ip igmp ha-stateful
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 |
---|---|
igmpEntity | sys/igmp |
igmpInst | sys/igmp/inst |
igmpInst Properties
The following table contains information about the igmpInst properties in the DME 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 |
---|---|---|---|
ctrl | nw:InstCtrl (scalar:Bitmask64) | The control state. | SELECTION: 1 - stateful-ha |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Disabling High Availability for IGMP
Disabling High Availability for IGMP
POST http://<mgmt0_IP>/api/mo/sys/igmp.json
{
"igmpEntity": {
"children": [
{
"igmpInst": {
"attributes": {
"ctrl": ""
}}}]}}
{
imdata:[]
}
<System>
<igmp-items>
<inst-items>
<ctrl></ctrl>
</inst-items>
</igmp-items>
</System>
Note: This example was added in Release Cisco NX-OS Release 7.0(3)I7(2).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
no ip igmp ha-stateful
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 |
---|---|
igmpEntity | sys/igmp |
igmpInst | sys/igmp/inst |
igmpInst Properties
The following table contains information about the igmpInst properties in the DME 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 |
---|---|---|---|
ctrl | nw:InstCtrl (scalar:Bitmask64) | The control state. | SELECTION: 1 - stateful-ha |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Translating IGMPv1/v2 Reports to (S,G) Route Entries
Translating IGMPv1/v2 Reports to (S,G) Route Entries
POST http://<mgmt0_IP>/api/mo/sys/igmp/inst.json
{
"igmpInst": {
"children": [
{
"igmpDom": {
"attributes": {
"name": "default"
},
"children": [
{
"igmpSSMXlate": {
"attributes": {
"grpPfx": "232.0.0.0/8",
"srcAddr": "10.1.1.1/32"
}}}]}}]}}
{
imdata:[]
}
<System>
<igmp-items>
<inst-items>
<dom-items>
<Dom-list>
<name>default</name>
<ssmxlate-items>
<SSMXlate-list>
<srcAddr>10.1.1.1/32</srcAddr>
<grpPfx>232.0.0.0/8</grpPfx>
</SSMXlate-list>
</ssmxlate-items>
</Dom-list>
</dom-items>
</inst-items>
</igmp-items>
</System>
Note: This example was added in Release Cisco NX-OS Release 7.0(3)I7(2).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
ip igmp ssm-translate 232.0.0.0/8 10.1.1.1
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
igmpInst | sys/igmp/inst |
igmpDom | sys/igmp/inst/dom-{name} |
igmpSSMXlate | sys/igmp/inst/dom-{name}/ssmxlate-src-{[srcAddr]}-grp-{[grpPfx]} |
igmpDom Properties
The following table contains information about the igmpDom properties in the DME 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 |
igmpSSMXlate Properties
The following table contains information about the igmpSSMXlate properties in the DME 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 |
---|---|---|---|
grpPfx | mcast:GrpIp (address:Ip) | Address | Value must match ipv4 or ipv6 known format |
srcAddr | address:Ip | Address | Value must match ipv4 or ipv6 known format |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Disabling the Translation of IGMPv1/v2 Reports to (S,G) Route Entries
Disabling the Translation of IGMPv1/v2 Reports to (S,G) Route Entries
POST http://<mgmt0_IP>/api/mo/sys/igmp/inst.json
{
"igmpInst": {
"children": [
{
"igmpDom": {
"attributes": {
"name": "default"
},
"children": [
{
"igmpSSMXlate": {
"attributes": {
"grpPfx": "232.0.0.0/8",
"srcAddr": "10.1.1.1/32",
"status": "deleted"
}}}]}}]}}
{
imdata:[]
}
<System>
<igmp-items>
<inst-items>
<dom-items>
<Dom-list>
<name>default</name>
<ssmxlate-items>
<SSMXlate-list xc:operation="delete">
<srcAddr>10.1.1.1/32</srcAddr>
<grpPfx>232.0.0.0/8</grpPfx>
</SSMXlate-list>
</ssmxlate-items>
</Dom-list>
</dom-items>
</inst-items>
</igmp-items>
</System>
Note: This example was added in Release Cisco NX-OS Release 7.0(3)I7(2).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
no ip igmp ssm-translate 232.0.0.0/8 10.1.1.1
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
igmpInst | sys/igmp/inst |
igmpDom | sys/igmp/inst/dom-{name} |
igmpSSMXlate | sys/igmp/inst/dom-{name}/ssmxlate-src-{[srcAddr]}-grp-{[grpPfx]} |
igmpDom Properties
The following table contains information about the igmpDom properties in the DME 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 |
igmpSSMXlate Properties
The following table contains information about the igmpSSMXlate properties in the DME 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 |
---|---|---|---|
grpPfx | mcast:GrpIp (address:Ip) | Address | Value must match ipv4 or ipv6 known format |
srcAddr | address:Ip | Address | Value must match ipv4 or ipv6 known format |
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring MAC-Based Multicast Lookup Mode
Configuring MAC-Based Multicast Lookup Mode
POST http://<mgmt0_IP>/api/mo/sys/igmpsnoop/inst/dom/gl.json
{
"igmpsnoopGl": {
"children": [
{
"igmpsnoopIgmpsnBase": {
"attributes": {
"lookupMac": "yes"
}}}]}}
{
imdata:[]
}
<System>
<igmpsnoop-items>
<inst-items>
<dom-items>
<gl-items>
<igmpsnbase-items>
<lookupMac>true</lookupMac>
</igmpsnbase-items>
</gl-items>
</dom-items>
</inst-items>
</igmpsnoop-items>
</System>
Note: This example was added in Release 9.2(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
layer-2 multicast lookup mac
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 |
---|---|
igmpsnoopGl | sys/igmpsnoop/inst/dom/gl |
igmpsnoopIgmpsnBase | sys/igmpsnoop/inst/dom/gl/igmpsnbase |
igmpsnoopIgmpsnBase Properties
The following table contains information about the igmpsnoopIgmpsnBase properties in the DME 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 |
---|---|---|---|
lookupMac | scalar:Bool | Indicates if Layer-2 Multicast Lookup Mac is Enabled | SELECTION: true or false |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting MAC-Based Multicast Lookup Mode
Deleting MAC-Based Multicast Lookup Mode
POST http://<mgmt0_IP>/api/mo/sys/igmpsnoop/inst/dom/gl.json
{
"igmpsnoopGl": {
"children": [
{
"igmpsnoopIgmpsnBase": {
"attributes": {
"lookupMac": "no"
}}}]}}
{
imdata:[]
}
<System>
<igmpsnoop-items>
<inst-items>
<dom-items>
<gl-items>
<igmpsnbase-items>
<lookupMac>false</lookupMac>
</igmpsnbase-items>
</gl-items>
</dom-items>
</inst-items>
</igmpsnoop-items>
</System>
Note: This example was added in Release 9.2(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
no layer-2 multicast lookup mac
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 |
---|---|
igmpsnoopGl | sys/igmpsnoop/inst/dom/gl |
igmpsnoopIgmpsnBase | sys/igmpsnoop/inst/dom/gl/igmpsnbase |
igmpsnoopIgmpsnBase Properties
The following table contains information about the igmpsnoopIgmpsnBase properties in the DME 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 |
---|---|---|---|
lookupMac | scalar:Bool | Indicates if Layer-2 Multicast Lookup Mac is Enabled | SELECTION: true or false |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring Subnet Check for Layer 3 IGMP Querier Election
Configuring Subnet Check for Layer 3 IGMP Querier Election
POST http://<mgmt0_IP>/api/mo/sys/igmp.json
{
"igmpEntity": {
"children": [
{
"igmpInst": {
"attributes": {
"strictQuerElect": "yes"
}}}]}}
{
imdata:[]
}
<System>
<igmp-items>
<inst-items>
<strictQuerElect>true</strictQuerElect>
</inst-items>
</igmp-items>
</System>
Note: This example was added in Release 9.3(5).
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 igmp querier-elect strict
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 |
---|---|
igmpEntity | sys/igmp |
igmpInst | sys/igmp/inst |
igmpInst Properties
The following table contains information about the igmpInst properties in the DME 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 |
---|---|---|---|
strictQuerElect | scalar:Bool | Consider subnet check for L3 igmp querier election | SELECTION: true or false |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting Subnet Check for Layer 3 IGMP Querier Election
Deleting Subnet Check for Layer 3 IGMP Querier Election
POST http://<mgmt0_IP>/api/mo/sys/igmp.json
{
"igmpEntity": {
"children": [
{
"igmpInst": {
"attributes": {
"strictQuerElect": "no"
}}}]}}
{
imdata:[]
}
<System>
<igmp-items>
<inst-items>
<strictQuerElect>false</strictQuerElect>
</inst-items>
</igmp-items>
</System>
Note: This example was added in Release 9.3(5).
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 igmp querier-elect strict
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 |
---|---|
igmpEntity | sys/igmp |
igmpInst | sys/igmp/inst |
igmpInst Properties
The following table contains information about the igmpInst properties in the DME 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 |
---|---|---|---|
strictQuerElect | scalar:Bool | Consider subnet check for L3 igmp querier election | SELECTION: true or false |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring a VLAN List to Drop Unknown Multicast Traffic
Configuring a VLAN List to Drop Unknown Multicast Traffic
POST http://<mgmt0_IP>/api/mo/sys/igmpsnoop/inst/dom/gl.json
{
"igmpsnoopGl": {
"children": [
{
"igmpsnoopGVlan": {
"attributes": {
"vxlanUmcDropVlan": "3943"
}}}]}}
{
imdata:[]
}
<System>
<igmpsnoop-items>
<inst-items>
<dom-items>
<gl-items>
<gvlan-items>
<vxlanUmcDropVlan>3943</vxlanUmcDropVlan>
</gvlan-items>
</gl-items>
</dom-items>
</inst-items>
</igmpsnoop-items>
</System>
Note: This example was added in Release 9.3(5).
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 igmp snooping vxlan-umc drop vlan 3943
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 |
---|---|
igmpsnoopGl | sys/igmpsnoop/inst/dom/gl |
igmpsnoopGVlan | sys/igmpsnoop/inst/dom/gl/gvlan |
igmpsnoopGVlan Properties
The following table contains information about the igmpsnoopGVlan properties in the DME 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 |
---|---|---|---|
vxlanUmcDropVlan | ipmcsnoop:VxlanVlanRange (l2:VlanBitmap) | Drop Unknown Multicast Traffic on Vlan(s) | Range: 1-3967 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting a VLAN List to Drop Unknown Multicast Traffic
Deleting a VLAN List to Drop Unknown Multicast Traffic
POST http://<mgmt0_IP>/api/mo/sys/igmpsnoop/inst/dom/gl.json
{
"igmpsnoopGl": {
"children": [
{
"igmpsnoopGVlan": {
"attributes": {
"vxlanUmcDropVlan": "0"
}}}]}}
{
imdata:[]
}
<System>
<igmpsnoop-items>
<inst-items>
<dom-items>
<gl-items>
<gvlan-items>
<vxlanUmcDropVlan>0</vxlanUmcDropVlan>
</gvlan-items>
</gl-items>
</dom-items>
</inst-items>
</igmpsnoop-items>
</System>
Note: This example was added in Release 9.3(5).
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 igmp snooping vxlan-umc drop vlan 3943
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 |
---|---|
igmpsnoopGl | sys/igmpsnoop/inst/dom/gl |
igmpsnoopGVlan | sys/igmpsnoop/inst/dom/gl/gvlan |
igmpsnoopGVlan Properties
The following table contains information about the igmpsnoopGVlan properties in the DME 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 |
---|---|---|---|
vxlanUmcDropVlan | ipmcsnoop:VxlanVlanRange (l2:VlanBitmap) | Drop Unknown Multicast Traffic on Vlan(s) | Range: 1-3967 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring Spoof Check for IGMP
Configuring Spoof Check for IGMP
POST http://<mgmt0_IP>/api/mo/sys/igmp.json
{
"igmpEntity": {
"children": [
{
"igmpInst": {
"attributes": {
"spoofCheck": "yes"
}}}]}}
{
imdata:[]
}
<System>
<igmp-items>
<inst-items>
<spoofCheck>true</spoofCheck>
</inst-items>
</igmp-items>
</System>
Note: This example was added in Release 9.3(5).
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 igmp spoof-check
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 |
---|---|
igmpEntity | sys/igmp |
igmpInst | sys/igmp/inst |
igmpInst Properties
The following table contains information about the igmpInst properties in the DME 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 |
---|---|---|---|
spoofCheck | scalar:Bool | Enable spoof check for IGMP | SELECTION: true or false |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting Spoof Check for IGMP
Deleting Spoof Check for IGMP
POST http://<mgmt0_IP>/api/mo/sys/igmp.json
{
"igmpEntity": {
"children": [
{
"igmpInst": {
"attributes": {
"spoofCheck": "no"
}}}]}}
{
imdata:[]
}
<System>
<igmp-items>
<inst-items>
<spoofCheck>false</spoofCheck>
</inst-items>
</igmp-items>
</System>
Note: This example was added in Release 9.3(5).
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 igmp spoof-check
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 |
---|---|
igmpEntity | sys/igmp |
igmpInst | sys/igmp/inst |
igmpInst Properties
The following table contains information about the igmpInst properties in the DME 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 |
---|---|---|---|
spoofCheck | scalar:Bool | Enable spoof check for IGMP | SELECTION: true or false |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring CLI Events for MLD
Configuring CLI Events for MLD
POST http://<mgmt0_IP>/api/mo/sys/mld/inst.json
{
"mldInst": {
"children": [
{
"mldEventHistory": {
"attributes": {
"size": "medium",
"type": "cli"
}}}]}}
{
imdata:[]
}
<System>
<mld-items>
<inst-items>
<eventhist-items>
<EventHistory-list>
<type>cli</type>
<size>3</size>
</EventHistory-list>
</eventhist-items>
</inst-items>
</mld-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ipv6 [icmp] mld internal event-history cli size medium
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 |
---|---|
mldInst | sys/mld/inst |
mldEventHistory | sys/mld/inst/eventhist-cli |
mldEventHistory Properties
The following table contains information about the mldEventHistory properties in the DME 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 | mld:Size (scalar:Uint32) | Configures buffer size in text per kb | RANGE: [0 , 4] DEFAULT: 2 |
type | mld:EhType (scalar:Enum16) | Configures type of event history | SELECTION: 0 - cli 2 - ha 4 - vrf 5 - group-debugs 6 - group-events 7 - interface-debugs 8 - interface-events 9 - policy 10 - mld-internal |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting CLI Events for MLD
Deleting CLI Events for MLD
POST http://<mgmt0_IP>/api/mo/sys/mld/inst.json
{
"mldInst": {
"children": [
{
"mldEventHistory": {
"attributes": {
"size": "small",
"type": "cli"
}}}]}}
{
imdata:[]
}
<System>
<mld-items>
<inst-items>
<eventhist-items>
<EventHistory-list>
<type>cli</type>
<size>2</size>
</EventHistory-list>
</eventhist-items>
</inst-items>
</mld-items>
</System>
Note: This example was added in Release 9.3(5).
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 ipv6 [icmp] mld internal event-history cli size medium
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 |
---|---|
mldInst | sys/mld/inst |
mldEventHistory | sys/mld/inst/eventhist-cli |
mldEventHistory Properties
The following table contains information about the mldEventHistory properties in the DME 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 | mld:Size (scalar:Uint32) | Configures buffer size in text per kb | RANGE: [0 , 4] DEFAULT: 2 |
type | mld:EhType (scalar:Enum16) | Configures type of event history | SELECTION: 0 - cli 2 - ha 4 - vrf 5 - group-debugs 6 - group-events 7 - interface-debugs 8 - interface-events 9 - policy 10 - mld-internal |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring Group Events for MLD
Configuring Group Events for MLD
POST http://<mgmt0_IP>/api/mo/sys/mld/inst.json
{
"mldInst": {
"children": [
{
"mldEventHistory": {
"attributes": {
"size": "medium",
"type": "group-events"
}}}]}}
{
imdata:[]
}
<System>
<mld-items>
<inst-items>
<eventhist-items>
<EventHistory-list>
<type>group-events</type>
<size>3</size>
</EventHistory-list>
</eventhist-items>
</inst-items>
</mld-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ipv6 [icmp] mld internal event-history group-events size medium
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 |
---|---|
mldInst | sys/mld/inst |
mldEventHistory | sys/mld/inst/eventhist-group-events |
mldEventHistory Properties
The following table contains information about the mldEventHistory properties in the DME 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 | mld:Size (scalar:Uint32) | Configures buffer size in text per kb | RANGE: [0 , 4] DEFAULT: 2 |
type | mld:EhType (scalar:Enum16) | Configures type of event history | SELECTION: 0 - cli 2 - ha 4 - vrf 5 - group-debugs 6 - group-events 7 - interface-debugs 8 - interface-events 9 - policy 10 - mld-internal |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting Group Events for MLD
Deleting Group Events for MLD
POST http://<mgmt0_IP>/api/mo/sys/mld/inst.json
{
"mldInst": {
"children": [
{
"mldEventHistory": {
"attributes": {
"size": "small",
"type": "group-events"
}}}]}}
{
imdata:[]
}
<System>
<mld-items>
<inst-items>
<eventhist-items>
<EventHistory-list>
<type>group-events</type>
<size>2</size>
</EventHistory-list>
</eventhist-items>
</inst-items>
</mld-items>
</System>
Note: This example was added in Release 9.3(5).
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 ipv6 [icmp] mld internal event-history group-events size medium
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 |
---|---|
mldInst | sys/mld/inst |
mldEventHistory | sys/mld/inst/eventhist-group-events |
mldEventHistory Properties
The following table contains information about the mldEventHistory properties in the DME 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 | mld:Size (scalar:Uint32) | Configures buffer size in text per kb | RANGE: [0 , 4] DEFAULT: 2 |
type | mld:EhType (scalar:Enum16) | Configures type of event history | SELECTION: 0 - cli 2 - ha 4 - vrf 5 - group-debugs 6 - group-events 7 - interface-debugs 8 - interface-events 9 - policy 10 - mld-internal |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring HA Events for MLD
Configuring HA Events for MLD
POST http://<mgmt0_IP>/api/mo/sys/mld/inst.json
{
"mldInst": {
"children": [
{
"mldEventHistory": {
"attributes": {
"size": "medium",
"type": "ha"
}}}]}}
{
imdata:[]
}
<System>
<mld-items>
<inst-items>
<eventhist-items>
<EventHistory-list>
<type>ha</type>
<size>3</size>
</EventHistory-list>
</eventhist-items>
</inst-items>
</mld-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ipv6 [icmp] mld internal event-history ha size medium
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 |
---|---|
mldInst | sys/mld/inst |
mldEventHistory | sys/mld/inst/eventhist-ha |
mldEventHistory Properties
The following table contains information about the mldEventHistory properties in the DME 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 | mld:Size (scalar:Uint32) | Configures buffer size in text per kb | RANGE: [0 , 4] DEFAULT: 2 |
type | mld:EhType (scalar:Enum16) | Configures type of event history | SELECTION: 0 - cli 2 - ha 4 - vrf 5 - group-debugs 6 - group-events 7 - interface-debugs 8 - interface-events 9 - policy 10 - mld-internal |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting HA Events for MLD
Deleting HA Events for MLD
POST http://<mgmt0_IP>/api/mo/sys/mld/inst.json
{
"mldInst": {
"children": [
{
"mldEventHistory": {
"attributes": {
"size": "small",
"type": "ha"
}}}]}}
{
imdata:[]
}
<System>
<mld-items>
<inst-items>
<eventhist-items>
<EventHistory-list>
<type>ha</type>
<size>2</size>
</EventHistory-list>
</eventhist-items>
</inst-items>
</mld-items>
</System>
Note: This example was added in Release 9.3(5).
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 ipv6 [icmp] mld internal event-history ha size medium
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 |
---|---|
mldInst | sys/mld/inst |
mldEventHistory | sys/mld/inst/eventhist-ha |
mldEventHistory Properties
The following table contains information about the mldEventHistory properties in the DME 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 | mld:Size (scalar:Uint32) | Configures buffer size in text per kb | RANGE: [0 , 4] DEFAULT: 2 |
type | mld:EhType (scalar:Enum16) | Configures type of event history | SELECTION: 0 - cli 2 - ha 4 - vrf 5 - group-debugs 6 - group-events 7 - interface-debugs 8 - interface-events 9 - policy 10 - mld-internal |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring Interface Events for MLD
Configuring Interface Events for MLD
POST http://<mgmt0_IP>/api/mo/sys/mld/inst.json
{
"mldInst": {
"children": [
{
"mldEventHistory": {
"attributes": {
"size": "medium",
"type": "interface-events"
}}}]}}
{
imdata:[]
}
<System>
<mld-items>
<inst-items>
<eventhist-items>
<EventHistory-list>
<type>interface-events</type>
<size>3</size>
</EventHistory-list>
</eventhist-items>
</inst-items>
</mld-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ipv6 [icmp] mld internal event-history interface-events size medium
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 |
---|---|
mldInst | sys/mld/inst |
mldEventHistory | sys/mld/inst/eventhist-interface-events |
mldEventHistory Properties
The following table contains information about the mldEventHistory properties in the DME 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 | mld:Size (scalar:Uint32) | Configures buffer size in text per kb | RANGE: [0 , 4] DEFAULT: 2 |
type | mld:EhType (scalar:Enum16) | Configures type of event history | SELECTION: 0 - cli 2 - ha 4 - vrf 5 - group-debugs 6 - group-events 7 - interface-debugs 8 - interface-events 9 - policy 10 - mld-internal |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting Interface Events for MLD
Deleting Interface Events for MLD
POST http://<mgmt0_IP>/api/mo/sys/mld/inst.json
{
"mldInst": {
"children": [
{
"mldEventHistory": {
"attributes": {
"size": "small",
"type": "interface-events"
}}}]}}
{
imdata:[]
}
<System>
<mld-items>
<inst-items>
<eventhist-items>
<EventHistory-list>
<type>interface-events</type>
<size>2</size>
</EventHistory-list>
</eventhist-items>
</inst-items>
</mld-items>
</System>
Note: This example was added in Release 9.3(5).
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 ipv6 [icmp] mld internal event-history interface-events size medium
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 |
---|---|
mldInst | sys/mld/inst |
mldEventHistory | sys/mld/inst/eventhist-interface-events |
mldEventHistory Properties
The following table contains information about the mldEventHistory properties in the DME 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 | mld:Size (scalar:Uint32) | Configures buffer size in text per kb | RANGE: [0 , 4] DEFAULT: 2 |
type | mld:EhType (scalar:Enum16) | Configures type of event history | SELECTION: 0 - cli 2 - ha 4 - vrf 5 - group-debugs 6 - group-events 7 - interface-debugs 8 - interface-events 9 - policy 10 - mld-internal |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring Internal Events for MLD
Configuring Internal Events for MLD
POST http://<mgmt0_IP>/api/mo/sys/mld/inst.json
{
"mldInst": {
"children": [
{
"mldEventHistory": {
"attributes": {
"size": "medium",
"type": "mld-internal"
}}}]}}
{
imdata:[]
}
<System>
<mld-items>
<inst-items>
<eventhist-items>
<EventHistory-list>
<type>mld-internal</type>
<size>3</size>
</EventHistory-list>
</eventhist-items>
</inst-items>
</mld-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ipv6 [icmp] mld internal event-history mld-internal size medium
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 |
---|---|
mldInst | sys/mld/inst |
mldEventHistory | sys/mld/inst/eventhist-mld-internal |
mldEventHistory Properties
The following table contains information about the mldEventHistory properties in the DME 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 | mld:Size (scalar:Uint32) | Configures buffer size in text per kb | RANGE: [0 , 4] DEFAULT: 2 |
type | mld:EhType (scalar:Enum16) | Configures type of event history | SELECTION: 0 - cli 2 - ha 4 - vrf 5 - group-debugs 6 - group-events 7 - interface-debugs 8 - interface-events 9 - policy 10 - mld-internal |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting Internal Events for MLD
Deleting Internal Events for MLD
POST http://<mgmt0_IP>/api/mo/sys/mld/inst.json
{
"mldInst": {
"children": [
{
"mldEventHistory": {
"attributes": {
"size": "small",
"type": "mld-internal"
}}}]}}
{
imdata:[]
}
<System>
<mld-items>
<inst-items>
<eventhist-items>
<EventHistory-list>
<type>mld-internal</type>
<size>2</size>
</EventHistory-list>
</eventhist-items>
</inst-items>
</mld-items>
</System>
Note: This example was added in Release 9.3(5).
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 ipv6 [icmp] mld internal event-history mld-internal size medium
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 |
---|---|
mldInst | sys/mld/inst |
mldEventHistory | sys/mld/inst/eventhist-mld-internal |
mldEventHistory Properties
The following table contains information about the mldEventHistory properties in the DME 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 | mld:Size (scalar:Uint32) | Configures buffer size in text per kb | RANGE: [0 , 4] DEFAULT: 2 |
type | mld:EhType (scalar:Enum16) | Configures type of event history | SELECTION: 0 - cli 2 - ha 4 - vrf 5 - group-debugs 6 - group-events 7 - interface-debugs 8 - interface-events 9 - policy 10 - mld-internal |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring Policy Events for MLD
Configuring Policy Events for MLD
POST http://<mgmt0_IP>/api/mo/sys/mld/inst.json
{
"mldInst": {
"children": [
{
"mldEventHistory": {
"attributes": {
"size": "medium",
"type": "policy"
}}}]}}
{
imdata:[]
}
<System>
<mld-items>
<inst-items>
<eventhist-items>
<EventHistory-list>
<type>policy</type>
<size>3</size>
</EventHistory-list>
</eventhist-items>
</inst-items>
</mld-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ipv6 [icmp] mld internal event-history policy size medium
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 |
---|---|
mldInst | sys/mld/inst |
mldEventHistory | sys/mld/inst/eventhist-policy |
mldEventHistory Properties
The following table contains information about the mldEventHistory properties in the DME 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 | mld:Size (scalar:Uint32) | Configures buffer size in text per kb | RANGE: [0 , 4] DEFAULT: 2 |
type | mld:EhType (scalar:Enum16) | Configures type of event history | SELECTION: 0 - cli 2 - ha 4 - vrf 5 - group-debugs 6 - group-events 7 - interface-debugs 8 - interface-events 9 - policy 10 - mld-internal |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting Policy Events for MLD
Deleting Policy Events for MLD
POST http://<mgmt0_IP>/api/mo/sys/mld/inst.json
{
"mldInst": {
"children": [
{
"mldEventHistory": {
"attributes": {
"size": "small",
"type": "policy"
}}}]}}
{
imdata:[]
}
<System>
<mld-items>
<inst-items>
<eventhist-items>
<EventHistory-list>
<type>policy</type>
<size>2</size>
</EventHistory-list>
</eventhist-items>
</inst-items>
</mld-items>
</System>
Note: This example was added in Release 9.3(5).
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 ipv6 [icmp] mld internal event-history policy size medium
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 |
---|---|
mldInst | sys/mld/inst |
mldEventHistory | sys/mld/inst/eventhist-policy |
mldEventHistory Properties
The following table contains information about the mldEventHistory properties in the DME 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 | mld:Size (scalar:Uint32) | Configures buffer size in text per kb | RANGE: [0 , 4] DEFAULT: 2 |
type | mld:EhType (scalar:Enum16) | Configures type of event history | SELECTION: 0 - cli 2 - ha 4 - vrf 5 - group-debugs 6 - group-events 7 - interface-debugs 8 - interface-events 9 - policy 10 - mld-internal |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring VRF Events for MLD
Configuring VRF Events for MLD
POST http://<mgmt0_IP>/api/mo/sys/mld/inst.json
{
"mldInst": {
"children": [
{
"mldEventHistory": {
"attributes": {
"size": "medium",
"type": "vrf"
}}}]}}
{
imdata:[]
}
<System>
<mld-items>
<inst-items>
<eventhist-items>
<EventHistory-list>
<type>vrf</type>
<size>3</size>
</EventHistory-list>
</eventhist-items>
</inst-items>
</mld-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ipv6 [icmp] mld internal event-history vrf size medium
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 |
---|---|
mldInst | sys/mld/inst |
mldEventHistory | sys/mld/inst/eventhist-vrf |
mldEventHistory Properties
The following table contains information about the mldEventHistory properties in the DME 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 | mld:Size (scalar:Uint32) | Configures buffer size in text per kb | RANGE: [0 , 4] DEFAULT: 2 |
type | mld:EhType (scalar:Enum16) | Configures type of event history | SELECTION: 0 - cli 2 - ha 4 - vrf 5 - group-debugs 6 - group-events 7 - interface-debugs 8 - interface-events 9 - policy 10 - mld-internal |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting VRF Events for MLD
Deleting VRF Events for MLD
POST http://<mgmt0_IP>/api/mo/sys/mld/inst.json
{
"mldInst": {
"children": [
{
"mldEventHistory": {
"attributes": {
"size": "small",
"type": "vrf"
}}}]}}
{
imdata:[]
}
<System>
<mld-items>
<inst-items>
<eventhist-items>
<EventHistory-list>
<type>vrf</type>
<size>2</size>
</EventHistory-list>
</eventhist-items>
</inst-items>
</mld-items>
</System>
Note: This example was added in Release 9.3(5).
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 ipv6 [icmp] mld internal event-history vrf size medium
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 |
---|---|
mldInst | sys/mld/inst |
mldEventHistory | sys/mld/inst/eventhist-vrf |
mldEventHistory Properties
The following table contains information about the mldEventHistory properties in the DME 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 | mld:Size (scalar:Uint32) | Configures buffer size in text per kb | RANGE: [0 , 4] DEFAULT: 2 |
type | mld:EhType (scalar:Enum16) | Configures type of event history | SELECTION: 0 - cli 2 - ha 4 - vrf 5 - group-debugs 6 - group-events 7 - interface-debugs 8 - interface-events 9 - policy 10 - mld-internal |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring Interface-Debug Events for MLD
Configuring Interface-Debug Events for MLD
POST http://<mgmt0_IP>/api/mo/sys/mld/inst.json
{
"mldInst": {
"children": [
{
"mldEventHistory": {
"attributes": {
"size": "medium",
"type": "interface-debugs"
}}}]}}
{
imdata:[]
}
<System>
<mld-items>
<inst-items>
<eventhist-items>
<EventHistory-list>
<type>interface-debugs</type>
<size>3</size>
</EventHistory-list>
</eventhist-items>
</inst-items>
</mld-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ipv6 mld internal event-history interface-debugs size medium
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 |
---|---|
mldInst | sys/mld/inst |
mldEventHistory | sys/mld/inst/eventhist-interface-debugs |
mldEventHistory Properties
The following table contains information about the mldEventHistory properties in the DME 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 | mld:Size (scalar:Uint32) | Configures buffer size in text per kb | RANGE: [0 , 4] DEFAULT: 2 |
type | mld:EhType (scalar:Enum16) | Configures type of event history | SELECTION: 0 - cli 2 - ha 4 - vrf 5 - group-debugs 6 - group-events 7 - interface-debugs 8 - interface-events 9 - policy 10 - mld-internal |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting Interface-Debug Events for MLD
Deleting Interface-Debug Events for MLD
POST http://<mgmt0_IP>/api/mo/sys/mld/inst.json
{
"mldInst": {
"children": [
{
"mldEventHistory": {
"attributes": {
"size": "small",
"type": "interface-debugs"
}}}]}}
{
imdata:[]
}
<System>
<mld-items>
<inst-items>
<eventhist-items>
<EventHistory-list>
<type>interface-debugs</type>
<size>2</size>
</EventHistory-list>
</eventhist-items>
</inst-items>
</mld-items>
</System>
Note: This example was added in Release 9.3(5).
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 ipv6 mld internal event-history interface-debugs size medium
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 |
---|---|
mldInst | sys/mld/inst |
mldEventHistory | sys/mld/inst/eventhist-interface-debugs |
mldEventHistory Properties
The following table contains information about the mldEventHistory properties in the DME 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 | mld:Size (scalar:Uint32) | Configures buffer size in text per kb | RANGE: [0 , 4] DEFAULT: 2 |
type | mld:EhType (scalar:Enum16) | Configures type of event history | SELECTION: 0 - cli 2 - ha 4 - vrf 5 - group-debugs 6 - group-events 7 - interface-debugs 8 - interface-events 9 - policy 10 - mld-internal |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring Group-Debug Events for MLD
Configuring Group-Debug Events for MLD
POST http://<mgmt0_IP>/api/mo/sys/mld/inst.json
{
"mldInst": {
"children": [
{
"mldEventHistory": {
"attributes": {
"size": "medium",
"type": "group-debugs"
}}}]}}
{
imdata:[]
}
<System>
<mld-items>
<inst-items>
<eventhist-items>
<EventHistory-list>
<type>group-debugs</type>
<size>3</size>
</EventHistory-list>
</eventhist-items>
</inst-items>
</mld-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ipv6 mld internal event-history group-debugs size medium
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 |
---|---|
mldInst | sys/mld/inst |
mldEventHistory | sys/mld/inst/eventhist-group-debugs |
mldEventHistory Properties
The following table contains information about the mldEventHistory properties in the DME 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 | mld:Size (scalar:Uint32) | Configures buffer size in text per kb | RANGE: [0 , 4] DEFAULT: 2 |
type | mld:EhType (scalar:Enum16) | Configures type of event history | SELECTION: 0 - cli 2 - ha 4 - vrf 5 - group-debugs 6 - group-events 7 - interface-debugs 8 - interface-events 9 - policy 10 - mld-internal |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting Group-Debug Events for MLD
Deleting Group-Debug Events for MLD
POST http://<mgmt0_IP>/api/mo/sys/mld/inst.json
{
"mldInst": {
"children": [
{
"mldEventHistory": {
"attributes": {
"size": "small",
"type": "group-debugs"
}}}]}}
{
imdata:[]
}
<System>
<mld-items>
<inst-items>
<eventhist-items>
<EventHistory-list>
<type>group-debugs</type>
<size>2</size>
</EventHistory-list>
</eventhist-items>
</inst-items>
</mld-items>
</System>
Note: This example was added in Release 9.3(5).
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 ipv6 mld internal event-history group-debugs size medium
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 |
---|---|
mldInst | sys/mld/inst |
mldEventHistory | sys/mld/inst/eventhist-group-debugs |
mldEventHistory Properties
The following table contains information about the mldEventHistory properties in the DME 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 | mld:Size (scalar:Uint32) | Configures buffer size in text per kb | RANGE: [0 , 4] DEFAULT: 2 |
type | mld:EhType (scalar:Enum16) | Configures type of event history | SELECTION: 0 - cli 2 - ha 4 - vrf 5 - group-debugs 6 - group-events 7 - interface-debugs 8 - interface-events 9 - policy 10 - mld-internal |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring the IP IGMP Logging Level
Configuring the IP IGMP Logging Level
POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
{
"loggingLogLevel": {
"children": [
{
"loggingFacility": {
"attributes": {
"facilityName": "igmp",
"severityLevel": "warnings"
}}}]}}
{
imdata:[]
}
<System>
<logging-items>
<loglevel-items>
<facility-items>
<Facility-list>
<facilityName>igmp</facilityName>
<severityLevel>warnings</severityLevel>
</Facility-list>
</facility-items>
</loglevel-items>
</logging-items>
</System>
Note: This example was added in Release 9.3(5).
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.
logging level ip igmp 4
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 |
---|---|
loggingLogLevel | sys/logging/loglevel |
loggingFacility | sys/logging/loglevel/facility-[igmp] |
loggingFacility Properties
The following table contains information about the loggingFacility properties in the DME 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 |
---|---|---|---|
facilityName | comp:DelimitedString (string:Basic) | Facility Name of individual processes subscribed for logging level | A sequence of characters |
severityLevel | syslog:Severity (scalar:Enum8) | Logging severity level for individual facility name | SELECTION: 0 - emergencies 1 - alerts 2 - critical 3 - errors 4 - warnings 5 - notifications 6 - information 7 - debugging DEFAULT: notifications |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the IP IGMP Logging Level
Deleting the IP IGMP Logging Level
POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
{
"loggingLogLevel": {
"children": [
{
"loggingFacility": {
"attributes": {
"facilityName": "igmp",
"severityLevel": "notifications"
}}}]}}
{
imdata:[]
}
<System>
<logging-items>
<loglevel-items>
<facility-items>
<Facility-list>
<facilityName>igmp</facilityName>
<severityLevel>notifications</severityLevel>
</Facility-list>
</facility-items>
</loglevel-items>
</logging-items>
</System>
Note: This example was added in Release 9.3(5).
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 logging level ip igmp 4
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 |
---|---|
loggingLogLevel | sys/logging/loglevel |
loggingFacility | sys/logging/loglevel/facility-[igmp] |
loggingFacility Properties
The following table contains information about the loggingFacility properties in the DME 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 |
---|---|---|---|
facilityName | comp:DelimitedString (string:Basic) | Facility Name of individual processes subscribed for logging level | A sequence of characters |
severityLevel | syslog:Severity (scalar:Enum8) | Logging severity level for individual facility name | SELECTION: 0 - emergencies 1 - alerts 2 - critical 3 - errors 4 - warnings 5 - notifications 6 - information 7 - debugging DEFAULT: notifications |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring Router Guard for Multicast Packet Processing
Configuring Router Guard for Multicast Packet Processing
POST http://<mgmt0_IP>/api/mo/sys/igmpsnoop/inst/dom/gl.json
{
"igmpsnoopGl": {
"children": [
{
"igmpsnoopRtrGrd": {
"attributes": {
"state": "yes"
}}}]}}
{
imdata:[]
}
<System>
<igmpsnoop-items>
<inst-items>
<dom-items>
<gl-items>
<rtrgrd-items>
<state>true</state>
</rtrgrd-items>
</gl-items>
</dom-items>
</inst-items>
</igmpsnoop-items>
</System>
Note: This example was added in Release 9.3(5).
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.
router-guard ip multicast switchports
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 |
---|---|
igmpsnoopGl | sys/igmpsnoop/inst/dom/gl |
igmpsnoopRtrGrd | sys/igmpsnoop/inst/dom/gl/rtrgrd |
igmpsnoopRtrGrd Properties
The following table contains information about the igmpsnoopRtrGrd properties in the DME 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 |
---|---|---|---|
state | scalar:Bool | Configures Router Guard for Multicast packets on all switchports | SELECTION: true or false |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting Router Guard for Multicast Packet Processing
Deleting Router Guard for Multicast Packet Processing
POST http://<mgmt0_IP>/api/mo/sys/igmpsnoop/inst/dom/gl.json
{
"igmpsnoopGl": {
"children": [
{
"igmpsnoopRtrGrd": {
"attributes": {
"status": "deleted"
}}}]}}
{
imdata:[]
}
<System>
<igmpsnoop-items>
<inst-items>
<dom-items>
<gl-items>
<rtrgrd-items nc:operation="delete">
</rtrgrd-items>
</gl-items>
</dom-items>
</inst-items>
</igmpsnoop-items>
</System>
Note: This example was added in Release 9.3(5).
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 router-guard ip multicast switchports
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 |
---|---|
igmpsnoopGl | sys/igmpsnoop/inst/dom/gl |
igmpsnoopRtrGrd | sys/igmpsnoop/inst/dom/gl/rtrgrd |
igmpsnoopRtrGrd Properties
The following table contains information about the igmpsnoopRtrGrd properties in the DME 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 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring Router Guard for Multicast Packet Proccesing
Configuring Router Guard for Multicast Packet Proccesing
POST http://<mgmt0_IP>/api/mo/sys/mldsnoop/inst/dom/gl.json
{
"mldsnoopGl": {
"children": [
{
"mldsnoopRtrGrd": {
"attributes": {
"state": "yes"
}}}]}}
{
imdata:[]
}
<System>
<mldsnoop-items>
<inst-items>
<dom-items>
<gl-items>
<rtrgrd-items>
<state>true</state>
</rtrgrd-items>
</gl-items>
</dom-items>
</inst-items>
</mldsnoop-items>
</System>
Note: This example was added in Release 9.3(5).
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.
router-guard ipv6 multicast switchports
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 |
---|---|
mldsnoopGl | sys/mldsnoop/inst/dom/gl |
mldsnoopRtrGrd | sys/mldsnoop/inst/dom/gl/rtrgrd |
mldsnoopRtrGrd Properties
The following table contains information about the mldsnoopRtrGrd properties in the DME 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 |
---|---|---|---|
state | scalar:Bool | Configures Router Guard for Multicast packets on all switchports | SELECTION: true or false |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting Router Guard for Multicast Packet Proccesing
Deleting Router Guard for Multicast Packet Proccesing
POST http://<mgmt0_IP>/api/mo/sys/mldsnoop/inst/dom/gl.json
{
"mldsnoopGl": {
"children": [
{
"mldsnoopRtrGrd": {
"attributes": {
"status": "deleted"
}}}]}}
{
imdata:[]
}
<System>
<mldsnoop-items>
<inst-items>
<dom-items>
<gl-items>
<rtrgrd-items nc:operation="delete">
</rtrgrd-items>
</gl-items>
</dom-items>
</inst-items>
</mldsnoop-items>
</System>
Note: This example was added in Release 9.3(5).
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 router-guard ipv6 multicast switchports
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 |
---|---|
mldsnoopGl | sys/mldsnoop/inst/dom/gl |
mldsnoopRtrGrd | sys/mldsnoop/inst/dom/gl/rtrgrd |
mldsnoopRtrGrd Properties
The following table contains information about the mldsnoopRtrGrd properties in the DME 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 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring an IGMP Table Syslog Threshold
Configuring an IGMP Table Syslog Threshold
POST http://<mgmt0_IP>/api/mo/sys/igmp.json
{
"igmpEntity": {
"children": [
{
"igmpInst": {
"attributes": {
"syslogThreshold": "73"
}}}]}}
{
imdata:[]
}
<System>
<igmp-items>
<inst-items>
<syslogThreshold>73</syslogThreshold>
</inst-items>
</igmp-items>
</System>
Note: This example was added in Release 9.3(5).
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 igmp syslog-threshold 73
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 |
---|---|
igmpEntity | sys/igmp |
igmpInst | sys/igmp/inst |
igmpInst Properties
The following table contains information about the igmpInst properties in the DME 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 |
---|---|---|---|
syslogThreshold | ipmc:SyslogThresT (scalar:Uint16) | IGMP table syslog threshold percentage | RANGE: [1 , 100] DEFAULT: 90 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting an IGMP Table Syslog Threshold
Deleting an IGMP Table Syslog Threshold
POST http://<mgmt0_IP>/api/mo/sys/igmp.json
{
"igmpEntity": {
"children": [
{
"igmpInst": {
"attributes": {
"syslogThreshold": "90"
}}}]}}
{
imdata:[]
}
<System>
<igmp-items>
<inst-items>
<syslogThreshold>90</syslogThreshold>
</inst-items>
</igmp-items>
</System>
Note: This example was added in Release 9.3(5).
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 igmp syslog-threshold 73
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 |
---|---|
igmpEntity | sys/igmp |
igmpInst | sys/igmp/inst |
igmpInst Properties
The following table contains information about the igmpInst properties in the DME 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 |
---|---|---|---|
syslogThreshold | ipmc:SyslogThresT (scalar:Uint16) | IGMP table syslog threshold percentage | RANGE: [1 , 100] DEFAULT: 90 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring the MLD Table Syslog Threshold
Configuring the MLD Table Syslog Threshold
POST http://<mgmt0_IP>/api/mo/sys/mld.json
{
"mldEntity": {
"children": [
{
"mldInst": {
"attributes": {
"syslogThreshold": "100"
}}}]}}
{
imdata:[]
}
<System>
<mld-items>
<inst-items>
<syslogThreshold>100</syslogThreshold>
</inst-items>
</mld-items>
</System>
Note: This example was added in Release 9.3(5).
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.
ipv6 mld syslog-threshold 100
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 |
---|---|
mldEntity | sys/mld |
mldInst | sys/mld/inst |
mldInst Properties
The following table contains information about the mldInst properties in the DME 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 |
---|---|---|---|
syslogThreshold | ipmc:SyslogThresT (scalar:Uint16) | IGMP table syslog threshold percentage | RANGE: [1 , 100] DEFAULT: 90 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Deleting the MLD Table Syslog Threshold
Deleting the MLD Table Syslog Threshold
POST http://<mgmt0_IP>/api/mo/sys/mld.json
{
"mldEntity": {
"children": [
{
"mldInst": {
"attributes": {
"syslogThreshold": "90"
}}}]}}
{
imdata:[]
}
<System>
<mld-items>
<inst-items>
<syslogThreshold>90</syslogThreshold>
</inst-items>
</mld-items>
</System>
Note: This example was added in Release 9.3(5).
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 ipv6 mld syslog-threshold 100
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 |
---|---|
mldEntity | sys/mld |
mldInst | sys/mld/inst |
mldInst Properties
The following table contains information about the mldInst properties in the DME 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 |
---|---|---|---|
syslogThreshold | ipmc:SyslogThresT (scalar:Uint16) | IGMP table syslog threshold percentage | RANGE: [1 , 100] DEFAULT: 90 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring Multicast Telemetry notification for IGMP
Configuring Multicast Telemetry notification for IGMP
<model>
<package name="igmp">
<objects>
<!-- This objects hold per igmp domain (vrf) information -->
<mo name="IgmpVrf"
access="admin,tenant-ext-protocol-l3"
concrete="yes"
configure="no"
label="This Objects holds per IGMP Virtual Routing and Forwarding (VRF) Information"
>
<!-- Vrf name-->
<property name="name"
type="l3:VrfName"
owner="management"
mod="explicit"
label="Virtual Routing and Forwarding Name"
/>
</mo>
<rn mo="IgmpVrf">
<item prefix="igmpvrf" property="name"/>
</rn>
<contains parent="HostTrack"
child="IgmpVrf"
/>
<chunk target="IgmpVrf"
owner="igmp"
type="primary"
>
<prop target="name" />
</chunk>
<!-- This object holds igmp route group information -->
<mo name="Host"
access="admin,tenant-ext-protocol-l3"
concrete="yes"
configure="no"
label="This Object holds IGMP host Information"
>
<!-- Reporter Address -->
<property name="rprtAddr"
type="string:Basic"
owner="management"
mod="implicit"
label="IGMP host-reporter IP Address"
/>
</mo>
<rn mo="Host">
<item prefix="host" property="rprtAddr"/>
</rn>
<contains parent="IgmpVrf"
child="Host"
/>
<chunk target="Host"
owner="igmp"
type="primary"
>
<prop target="rprtAddr" />
</chunk>
<!-- This object holds igmp route group information -->
<mo name="RouteGrp"
access="admin,tenant-ext-protocol-l3"
concrete="yes"
configure="no"
label="This Object holds IGMP Route Group Information"
>
<!-- Group Address -->
<property name="grpAddrs"
type="address:Ip"
owner="management"
mod="implicit"
label="Multicast Group IP Address"
/>
</mo>
<rn mo="RouteGrp">
<item prefix="rtgrp" property="grpAddrs"/>
</rn>
<contains parent="Host"
child="RouteGrp"
/>
<chunk target="RouteGrp"
owner="igmp"
type="primary"
>
<prop target="grpAddrs" />
</chunk>
<!-- This object holds igmp route source information -->
<mo name="RouteSrc"
access="admin,tenant-ext-protocol-l3"
concrete="yes"
configure="no"
label="This Object holds IGMP Route Source Information"
>
<!-- Source Address -->
<property name="srcAddrs"
type="address:Ip"
owner="management"
mod="implicit"
label="IGMP Route Source IP Address"
/>
</mo>
<rn mo="RouteSrc">
<item prefix="rtsrc" property="srcAddrs"/>
</rn>
<contains parent="RouteGrp"
child="RouteSrc"
/>
<chunk target="RouteSrc"
owner="igmp"
type="primary"
>
<prop target="srcAddrs" />
</chunk>
<!-- IGMP Route Oif MOs. We create one object per interface in the oif list -->
<mo name="RouteInfo"
access="admin,fabric-protocol-l3,tenant-ext-protocol-l3"
concrete="yes"
configure="no"
label="Holds Route Outgoing Interface(OIF) Details"
>
<!-- Is Local -->
<property name="isJoin"
type="scalar:Bool"
owner="oper"
mod="implicit"
label="Indicates if the Route is Local"
/>
<!-- Is Static -->
<property name="isStatic"
type="scalar:Bool"
owner="oper"
mod="implicit"
label="Indicates if the Route is Static"
/>
<!-- Is Host Proxy -->
<property name="isHostProxy"
type="scalar:Bool"
owner="oper"
mod="implicit"
label="Indicates if Host is Proxy"
/>
<!-- Is Host Proxy -->
<property name="isLocal"
type="scalar:Bool"
owner="oper"
mod="implicit"
label="Indicates if the Route is Local"
/>
<!-- Expiry time -->
<property name="expiration"
type="string:Basic"
owner="oper"
mod="implicit"
label="Route OIF Expiry Timestamp"
/>
<!-- -->interface
<property name="interface"
type="IfId""
owner="oper"
mod="implicit"
label="Indicates interface on which IGMP Join is received"
/>
<!-- Is ssm Translate -->
<property name="ssm_translate"
type="scalar:Bool"
owner="oper"
mod="implicit"
label="Indicates if its SSM translated route”
/>
</mo>
<contains parent="RouteSrc"
child="RouteInfo"
/>
<rn mo="RouteInfo">
<item prefix="rtinfo"/>
</rn>
<chunk target="RouteInfo"
owner="igmp"
type="primary"
>
<prop target="isJoin" />
<prop target="isStatic" />
<prop target="isHostProxy" />
<prop target="expiration" />
</chunk>
</objects>
</package>
</model>
Note: This example was added in Release 10.4(1). This feature sends the telemetry notification with maximum scale of 8000 IGMP groups only.
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.
show ip igmp groups
Verifying IGMP Routes in DME DN
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 |
---|---|
igmp | sys/igmp/inst/hostTrack/igmpvrf-[%s]/ host- |
igmpRouteInfo Properties
The following table contains information about the igmpsnoopRtrGrd properties in the DME 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 |
---|
expiration |
isJoin |
isLocal |
isStatic |
isHostProxy |
interface |
ssmTranslate |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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:
Configuring Multicast Telemetry notification for IGMPSNOOP
Configuring Multicast Telemetry notification for IGMPSNOOP
<model>
<package name="igmpsnoop">
<objects>
<!-- This object holds igmp route group information -->
<mo name="Host"
access="admin,access-protocol-l2"
concrete="yes"
configure="no"
label="This Object holds IGMP host Information"
>
<property name="rprtAddr"
type="address:Ip"
owner="management"
mod="implicit"
label="IGMP snoop Report IP Address"
/>
</mo>
<rn mo="Host">
<item prefix="host" property="rprtAddr"/>
</rn>
<contains parent="HostTrack"
child="Host"
/>
<chunk target="Host"
owner="igmpsnoop"
type="primary"
>
<prop target="rprtAddr" />
</chunk>
<!-- Explicit Tracking record -->
<mo name="ExpHostTrackRec"
super="ipmcsnoop:AExpTrackRec"
access="admin,access-protocol-l2"
concrete="yes"
pers="no"
label="Holds IGMP Snooping Explicit Host Tracking Record"
>
<property name="isJoin"
type="scalar:Bool"
owner="oper"
mod="implicit"
label="Indicates if the Route is join or leave"
/>
</mo>
<rn mo="ExpHostTrackRec">
<item prefix="exphostTrack" property="vlanid"/>
<item prefix="grp" property="grpAddr"/>
<item prefix="src" property="srcAddr"/>
<item prefix="intf" property="intf"/>
</rn>
<contains parent="Host"
child="ExpHostTrackRec"
/>
<chunk target="ExpHostTrackRec"
owner="igmpsnoop"
type="primary"
>
<prop target="isJoin" />
</chunk>
</objects>
</package>
</model>
Note: This example was added in Release 10.3(3).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
show ip igmp snooping explicit-tracking
sh system internal dme running-config all dn sys/igmpsnoop/inst/dom/hostTrack
Verifying IGMP Routes in DME DN
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 |
---|---|
igmpsnoop | sys/igmpsnoop/inst/dom/hostTrack/host-[rprtAddr]/expTrack-[vlanid]-grp-[grpAddr]-src-[srcAddr]-intf-[intf] |
igmpsnoopExpTrackRecInfo Properties
The following table contains information about the igmpsnoopRtrGrd properties in the DME 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 |
---|
vlanid |
uptime |
expiresTime |
interface |
version |
numReports |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
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: