Configuring Embedded Event Manager
EEM monitors events that occur on your device and takes action to recover or troubleshoot these events, based on your configuration. EEM consists of three major components:
- Event statements—Events to monitor from another Cisco NX-OS component that may require some action, workaround, or notification.
- Action statements—An action that EEM can take, such as executing CLI commands, sending an email through the use of Smart Call Home feature, and disabling an interface to recover from an event.
- Policies—An event that is paired with one or more actions to troubleshoot or recover from the event.
For more information, see the Cisco Nexus 9000 Series NX-OS System Management Configuration Guide:
Configuring an Event Manager Policy Applet
Configuring an Event Manager Policy Applet
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
}}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
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 Event Manager Policy Applet
Deleting an Event Manager Policy Applet
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1",
"status": "deleted"
}}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list nc:operation="delete">
<appletName>App_1</appletName>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
no event manager applet App_1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
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:
Note: EEM applet configuration is available in Netconf under subtree "/System/evtmgr-items/inst-items/applet-items." There is no support to delete leaf nodes which holds mandatory fields for the applet config. Deleting such leaf nodes from Netconf will be blocked resutling in an error message.
Configuring a Counter Event (Tagged)
Configuring a Counter Event (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventCounter": {
"attributes": {
"counterName": "SampleString_123",
"entryOp": "le",
"entryValue": "1",
"eventTag": "SampleString_123",
"exitOp": "le",
"exitValue": "1"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<countertag-items>
<EventCounter-list>
<eventTag>SampleString_123</eventTag>
<counterName>SampleString_123</counterName>
<entryOp>le</entryOp>
<entryValue>1</entryValue>
<exitOp>le</exitOp>
<exitValue>1</exitValue>
</EventCounter-list>
</countertag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event counter tag SampleString_123 name SampleString_123 entry-val 1 entry-op le exit-val 1 exit-op le
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventCounter | sys/evtmgr/inst/applet-App_1/events/countertag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventCounter Properties
The following table contains information about the evmsEventCounter 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 |
---|---|---|---|
counterName | string:Basic | Name of the counter | RANGE: [0 , 28] |
entryOp | evms:CounterEntryExitOpType (scalar:Enum8) | Specify the comparison operator | SELECTION: 5 - gt 6 - ge 7 - eq 8 - ne 9 - lt 10 - le DEFAULT: |
entryValue | scalar:Uint32 | Specify the value for comparison with the counter Value | RANGE: [0 , 2147483647] |
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
exitOp | evms:CounterEntryExitOpType (scalar:Enum8) | Specify the comparison operator | SELECTION: 5 - gt 6 - ge 7 - eq 8 - ne 9 - lt 10 - le DEFAULT: |
exitValue | scalar:Uint32 | Specify the value for comparison with the counter Value | RANGE: [0 , 2147483647] |
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 Counter Event (Tagged)
Deleting a Counter Event (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventCounter": {
"attributes": {
"eventTag": "SampleString_123",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<countertag-items>
<EventCounter-list nc:operation="delete">
<eventTag>SampleString_123</eventTag>
</EventCounter-list>
</countertag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event counter tag SampleString_123 name SampleString_123 entry-val 1 entry-op le exit-val 1 exit-op le
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventCounter | sys/evtmgr/inst/applet-App_1/events/countertag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventCounter Properties
The following table contains information about the evmsEventCounter 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 a Counter Event (Untagged)
Configuring a Counter Event (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventCounterUnTagged": {
"attributes": {
"counterName": "SampleString_123",
"entryOp": "le",
"entryValue": "1",
"exitOp": "le",
"exitValue": "1"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<counter-items>
<counterName>SampleString_123</counterName>
<entryOp>le</entryOp>
<entryValue>1</entryValue>
<exitOp>le</exitOp>
<exitValue>1</exitValue>
</counter-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event counter name SampleString_123 entry-val 1 entry-op le exit-val 1 exit-op le
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventCounterUnTagged | sys/evtmgr/inst/applet-App_1/events/counter |
evmsEventCounterUnTagged Properties
The following table contains information about the evmsEventCounterUnTagged 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 |
---|---|---|---|
counterName | string:Basic | Name of the counter | RANGE: [0 , 28] |
entryOp | evms:CounterEntryExitOpType (scalar:Enum8) | Specify the comparison operator | SELECTION: 5 - gt 6 - ge 7 - eq 8 - ne 9 - lt 10 - le DEFAULT: |
entryValue | scalar:Uint32 | Specify the value for comparison with the counter Value | RANGE: [0 , 2147483647] |
exitOp | evms:CounterEntryExitOpType (scalar:Enum8) | Specify the comparison operator | SELECTION: 5 - gt 6 - ge 7 - eq 8 - ne 9 - lt 10 - le DEFAULT: |
exitValue | scalar:Uint32 | Specify the value for comparison with the counter Value | RANGE: [0 , 2147483647] |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
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 Counter Event (Untagged)
Deleting a Counter Event (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventCounterUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<counter-items nc:operation="delete">
</counter-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event counter name SampleString_123 entry-val 1 entry-op le exit-val 1 exit-op le
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventCounterUnTagged | sys/evtmgr/inst/applet-App_1/events/counter |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventCounterUnTagged Properties
The following table contains information about the evmsEventCounterUnTagged 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:
ps://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:
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 Time Interval for a System-Policy Event
Configuring the Time Interval for a System-Policy Event
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1",
"appletOverride": "__bootflash"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventPolicyDefault": {
"attributes": {
"occurences": "2455",
"timeInterval": "19860"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<appletOverride>__bootflash</appletOverride>
<events-items>
<policydefault-items>
<occurences>2455</occurences>
<timeInterval>19860</timeInterval>
</policydefault-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1 override __bootflash
event policy-default count 2455 time 19860
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventPolicyDefault | sys/evtmgr/inst/applet-App_1/events/policydefault |
evmsEventPolicyDefault Properties
The following table contains information about the evmsEventPolicyDefault 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 |
---|---|---|---|
occurences | scalar:Uint16 | Number of occurances | RANGE: [1 , 65000] DEFAULT: 1 |
timeInterval | scalar:Uint32 | Time interval in seconds | RANGE: [0 , 32768] |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
appletOverride | evms:AppletOverrideType (string:Basic) | Name of the system policy to override | MAX SIZE: 29 DEFAULT: |
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 Time Interval for a System-Policy Event
Deleting the Time Interval for a System-Policy Event
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1",
"appletOverride": "__bootflash"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventPolicyDefault": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<appletOverride>__bootflash</appletOverride>
<events-items>
<policydefault-items nc:operation="delete">
</policydefault-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1 override __bootflash
no event policy-default count 2455 time 19860
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventPolicyDefault | sys/evtmgr/inst/applet-App_1/events/policydefault |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
appletOverride | evms:AppletOverrideType (string:Basic) | Name of the system policy to override | MAX SIZE: 29 DEFAULT: |
evmsEventPolicyDefault Properties
The following table contains information about the evmsEventPolicyDefault 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 Shutdown of the Specified LCs Due to Power Over Budget
Configuring Shutdown of the Specified LCs Due to Power Over Budget
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsAction": {
"attributes": {
"actionLabel": "1"
},
"children": [
{
"evmsActionOverBudgetShut": {
"attributes": {
"moduleNumber": "all"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<action-items>
<Action-list>
<actionLabel>1</actionLabel>
<overbudgetshut-items>
<moduleNumber>all</moduleNumber>
</overbudgetshut-items>
</Action-list>
</action-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
action 1 overbudgetshut
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsAction | sys/evtmgr/inst/applet-App_1/action-1 |
evmsActionOverBudgetShut | sys/evtmgr/inst/applet-App_1/action-1/overbudgetshut |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsAction Properties
The following table contains information about the evmsAction 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 |
---|---|---|---|
actionLabel | evms:ActionLabelType (string:Basic) | Specify action label | A sequence of characters |
evmsActionOverBudgetShut Properties
The following table contains information about the evmsActionOverBudgetShut 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 |
---|---|---|---|
moduleNumber | string:Basic | Specify module number: all, interger module number or a $predefine environment name | RANGE: [1 , 30] DEFAULT: all |
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 Shutdown of the Specified LCs Due to Power Over Budget
Deleting Shutdown of the Specified LCs Due to Power Over Budget
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsAction": {
"attributes": {
"actionLabel": "1"
},
"children": [
{
"evmsActionOverBudgetShut": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<action-items>
<Action-list>
<actionLabel>1</actionLabel>
<overbudgetshut-items nc:operation="delete">
</overbudgetshut-items>
</Action-list>
</action-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no action 1 overbudgetshut
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsAction | sys/evtmgr/inst/applet-App_1/action-1 |
evmsActionOverBudgetShut | sys/evtmgr/inst/applet-App_1/action-1/overbudgetshut |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsAction Properties
The following table contains information about the evmsAction 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 |
---|---|---|---|
actionLabel | evms:ActionLabelType (string:Basic) | Specify action label | A sequence of characters |
evmsActionOverBudgetShut Properties
The following table contains information about the evmsActionOverBudgetShut 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 Reload for the System or a Specific Module
Configuring Reload for the System or a Specific Module
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsAction": {
"attributes": {
"actionLabel": "1"
},
"children": [
{
"evmsActionReload": {
"attributes": {
"moduleNumber": "all"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<action-items>
<Action-list>
<actionLabel>1</actionLabel>
<reload-items>
<moduleNumber>all</moduleNumber>
</reload-items>
</Action-list>
</action-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
action 1 reload
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsAction | sys/evtmgr/inst/applet-App_1/action-1 |
evmsActionReload | sys/evtmgr/inst/applet-App_1/action-1/reload |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsAction Properties
The following table contains information about the evmsAction 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 |
---|---|---|---|
actionLabel | evms:ActionLabelType (string:Basic) | Specify action label | A sequence of characters |
evmsActionReload Properties
The following table contains information about the evmsActionReload 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 |
---|---|---|---|
moduleNumber | string:Basic | Specify module number: all, interger module number or a $predefine environment name | RANGE: [1 , 30] DEFAULT: all |
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 Reload for the System or a Specific Module
Deleting Reload for the System or a Specific Module
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsAction": {
"attributes": {
"actionLabel": "1"
},
"children": [
{
"evmsActionReload": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<action-items>
<Action-list>
<actionLabel>1</actionLabel>
<reload-items nc:operation="delete">
</reload-items>
</Action-list>
</action-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no action 1 reload
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsAction | sys/evtmgr/inst/applet-App_1/action-1 |
evmsActionReload | sys/evtmgr/inst/applet-App_1/action-1/reload |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsAction Properties
The following table contains information about the evmsAction 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 |
---|---|---|---|
actionLabel | evms:ActionLabelType (string:Basic) | Specify action label | A sequence of characters |
evmsActionReload Properties
The following table contains information about the evmsActionReload 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 the Default Action for an Event
Configuring the Default Action for an Event
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsAction": {
"attributes": {
"actionLabel": "1"
},
"children": [
{
"evmsActionEventDefault": {
"attributes": {
"actioneventdefaultstatus": "yes"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<action-items>
<Action-list>
<actionLabel>1</actionLabel>
<eventdefault-items>
<actioneventdefaultstatus>true</actioneventdefaultstatus>
</eventdefault-items>
</Action-list>
</action-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
action 1 event-default
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsAction | sys/evtmgr/inst/applet-App_1/action-1 |
evmsActionEventDefault | sys/evtmgr/inst/applet-App_1/action-1/eventdefault |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsAction Properties
The following table contains information about the evmsAction 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 |
---|---|---|---|
actionLabel | evms:ActionLabelType (string:Basic) | Specify action label | A sequence of characters |
evmsActionEventDefault Properties
The following table contains information about the evmsActionEventDefault 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 |
---|---|---|---|
actioneventdefaultstatus | scalar:Bool | SELECTION: true or false DEFAULT: yes |
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 Default Action for an Event
Deleting the Default Action for an Event
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsAction": {
"attributes": {
"actionLabel": "1",
"status": "deleted"
}}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<action-items>
<Action-list nc:operation="delete">
<actionLabel>1</actionLabel>
</Action-list>
</action-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no action 1 event-default
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsAction | sys/evtmgr/inst/applet-App_1/action-1 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsAction Properties
The following table contains information about the evmsAction 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 |
---|---|---|---|
actionLabel | evms:ActionLabelType (string:Basic) | Specify action label | A sequence of characters |
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 the Default Action of the Policy Being Overridden
Configuring the Default Action of the Policy Being Overridden
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1",
"appletOverride": "__bootflash"
},
"children": [
{
"evmsAction": {
"attributes": {
"actionLabel": "1"
},
"children": [
{
"evmsActionPolicyDefault": {
"attributes": {
"actionpolicydefaultstatus": "yes"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<appletOverride>__bootflash</appletOverride>
<action-items>
<Action-list>
<actionLabel>1</actionLabel>
<policydefault-items>
<actionpolicydefaultstatus>true</actionpolicydefaultstatus>
</policydefault-items>
</Action-list>
</action-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1 override __bootflash
action 1 policy-default
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsAction | sys/evtmgr/inst/applet-App_1/action-1 |
evmsActionPolicyDefault | sys/evtmgr/inst/applet-App_1/action-1/policydefault |
evmsAction Properties
The following table contains information about the evmsAction 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 |
---|---|---|---|
actionLabel | evms:ActionLabelType (string:Basic) | Specify action label | A sequence of characters |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
appletOverride | evms:AppletOverrideType (string:Basic) | Name of the system policy to override | MAX SIZE: 29 DEFAULT: |
evmsActionPolicyDefault Properties
The following table contains information about the evmsActionPolicyDefault 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 |
---|---|---|---|
actionpolicydefaultstatus | scalar:Bool | SELECTION: true or false DEFAULT: yes |
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 Default Action of the Policy Being Overridden
Deleting the Default Action of the Policy Being Overridden
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1",
"appletOverride": "__bootflash"
},
"children": [
{
"evmsAction": {
"attributes": {
"actionLabel": "1",
"status": "deleted"
}}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<appletOverride>__bootflash</appletOverride>
<action-items>
<Action-list nc:operation="delete">
<actionLabel>1</actionLabel>
</Action-list>
</action-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1 override __bootflash
no action 1 policy-default
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsAction | sys/evtmgr/inst/applet-App_1/action-1 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
appletOverride | evms:AppletOverrideType (string:Basic) | Name of the system policy to override | MAX SIZE: 29 DEFAULT: |
evmsAction Properties
The following table contains information about the evmsAction 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 |
---|---|---|---|
actionLabel | evms:ActionLabelType (string:Basic) | Specify action label | A sequence of characters |
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 the Send out of an SNMP Trap
Configuring the Send out of an SNMP Trap
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsAction": {
"attributes": {
"actionLabel": "1"
},
"children": [
{
"evmsActionSnmpTrap": {
"attributes": {
"trapstatus": "yes"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<action-items>
<Action-list>
<actionLabel>1</actionLabel>
<snmptrap-items>
<trapstatus>true</trapstatus>
</snmptrap-items>
</Action-list>
</action-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
action 1 snmp-trap
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsAction | sys/evtmgr/inst/applet-App_1/action-1 |
evmsActionSnmpTrap | sys/evtmgr/inst/applet-App_1/action-1/snmptrap |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsAction Properties
The following table contains information about the evmsAction 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 |
---|---|---|---|
actionLabel | evms:ActionLabelType (string:Basic) | Specify action label | A sequence of characters |
evmsActionSnmpTrap Properties
The following table contains information about the evmsActionSnmpTrap 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 |
---|---|---|---|
trapstatus | scalar:Bool | Enable or Disable snmp trap | SELECTION: true or false DEFAULT: yes |
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 Send out of an SNMP Trap
Deleting the Send out of an SNMP Trap
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsAction": {
"attributes": {
"actionLabel": "1",
"status": "deleted"
}}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<action-items>
<Action-list nc:operation="delete">
<actionLabel>1</actionLabel>
</Action-list>
</action-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no action 1 snmp-trap
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsAction | sys/evtmgr/inst/applet-App_1/action-1 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsAction Properties
The following table contains information about the evmsAction 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 |
---|---|---|---|
actionLabel | evms:ActionLabelType (string:Basic) | Specify action label | A sequence of characters |
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:
Deleting an Action
Deleting an Action
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsAction": {
"attributes": {
"actionLabel": "1",
"status": "deleted"
}}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<action-items>
<Action-list nc:operation="delete">
<actionLabel>1</actionLabel>
</Action-list>
</action-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no action 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsAction | sys/evtmgr/inst/applet-App_1/action-1 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsAction Properties
The following table contains information about the evmsAction 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 |
---|---|---|---|
actionLabel | evms:ActionLabelType (string:Basic) | Specify action label | A sequence of characters |
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 Route Extra in FIB for an Adjacency Related Event
Configuring Route Extra in FIB for an Adjacency Related Event
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventUfdm": {
"attributes": {
"eventFib": "adjacency"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<ufdm-items>
<eventFib>adjacency</eventFib>
</ufdm-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event fib adjacency extra
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventUfdm | sys/evtmgr/inst/applet-App_1/events/ufdm |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventUfdm Properties
The following table contains information about the evmsEventUfdm 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 |
---|---|---|---|
eventFib | evms:EventFibType (scalar:Enum8) | Event-manager Applet Event Fib type | SELECTION: 0 - undefined 1 - inconsistent 2 - missing 3 - extra 4 - adjacency 5 - tcam-resource |
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 Route Extra in FIB for an Adjacency Related Event
Deleting Route Extra in FIB for an Adjacency Related Event
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventUfdm": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<ufdm-items nc:operation="delete">
</ufdm-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event fib adjacency extra
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventUfdm | sys/evtmgr/inst/applet-App_1/events/ufdm |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventUfdm Properties
The following table contains information about the evmsEventUfdm 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:
Specifying a TCAM Usage Related Event
Specifying a TCAM Usage Related Event
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventUfdm": {
"attributes": {
"eventFib": "tcam-resource"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<ufdm-items>
<eventFib>tcam-resource</eventFib>
</ufdm-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event fib resource tcam usage
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventUfdm | sys/evtmgr/inst/applet-App_1/events/ufdm |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventUfdm Properties
The following table contains information about the evmsEventUfdm 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 |
---|---|---|---|
eventFib | evms:EventFibType (scalar:Enum8) | Event-manager Applet Event Fib type | SELECTION: 0 - undefined 1 - inconsistent 2 - missing 3 - extra 4 - adjacency 5 - tcam-resource |
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 TCAM Usage Related Event
Deleting a TCAM Usage Related Event
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventUfdm": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<ufdm-items nc:operation="delete">
</ufdm-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event fib resource tcam usage
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventUfdm | sys/evtmgr/inst/applet-App_1/events/ufdm |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventUfdm Properties
The following table contains information about the evmsEventUfdm 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 Route Extra in FIB
Configuring Route Extra in FIB
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventUfdm": {
"attributes": {
"eventFib": "extra"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<ufdm-items>
<eventFib>extra</eventFib>
</ufdm-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event fib route extra
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventUfdm | sys/evtmgr/inst/applet-App_1/events/ufdm |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventUfdm Properties
The following table contains information about the evmsEventUfdm 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 |
---|---|---|---|
eventFib | evms:EventFibType (scalar:Enum8) | Event-manager Applet Event Fib type | SELECTION: 0 - undefined 1 - inconsistent 2 - missing 3 - extra 4 - adjacency 5 - tcam-resource |
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 Route Extra in FIB
Deleting Route Extra in FIB
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventUfdm": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<ufdm-items nc:operation="delete">
</ufdm-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event fib route extra
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventUfdm | sys/evtmgr/inst/applet-App_1/events/ufdm |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventUfdm Properties
The following table contains information about the evmsEventUfdm 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 Inconsistent Route in FIB
Configuring an Inconsistent Route in FIB
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventUfdm": {
"attributes": {
"eventFib": "inconsistent"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<ufdm-items>
<eventFib>inconsistent</eventFib>
</ufdm-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event fib route inconsistent
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventUfdm | sys/evtmgr/inst/applet-App_1/events/ufdm |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventUfdm Properties
The following table contains information about the evmsEventUfdm 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 |
---|---|---|---|
eventFib | evms:EventFibType (scalar:Enum8) | Event-manager Applet Event Fib type | SELECTION: 0 - undefined 1 - inconsistent 2 - missing 3 - extra 4 - adjacency 5 - tcam-resource |
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 Inconsistent Route in FIB
Deleting an Inconsistent Route in FIB
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventUfdm": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<ufdm-items nc:operation="delete">
</ufdm-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event fib route inconsistent
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventUfdm | sys/evtmgr/inst/applet-App_1/events/ufdm |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventUfdm Properties
The following table contains information about the evmsEventUfdm 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 a Missing Route in FIB
Configuring a Missing Route in FIB
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventUfdm": {
"attributes": {
"eventFib": "missing"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<ufdm-items>
<eventFib>missing</eventFib>
</ufdm-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event fib route missing
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventUfdm | sys/evtmgr/inst/applet-App_1/events/ufdm |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventUfdm Properties
The following table contains information about the evmsEventUfdm 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 |
---|---|---|---|
eventFib | evms:EventFibType (scalar:Enum8) | Event-manager Applet Event Fib type | SELECTION: 0 - undefined 1 - inconsistent 2 - missing 3 - extra 4 - adjacency 5 - tcam-resource |
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 Missing Route in FIB
Deleting a Missing Route in FIB
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventUfdm": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<ufdm-items nc:operation="delete">
</ufdm-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event fib route missing
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventUfdm | sys/evtmgr/inst/applet-App_1/events/ufdm |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventUfdm Properties
The following table contains information about the evmsEventUfdm 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 Online or Offline Status (Tagged)
Configuring Online or Offline Status (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventModule": {
"attributes": {
"eventTag": "SampleString_123",
"moduleNumber": "1",
"moduleStatus": "any"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<moduletag-items>
<EventModule-list>
<eventTag>SampleString_123</eventTag>
<moduleNumber>1</moduleNumber>
<moduleStatus>any</moduleStatus>
</EventModule-list>
</moduletag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event module tag SampleString_123 status any module 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventModule | sys/evtmgr/inst/applet-App_1/events/moduletag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventModule Properties
The following table contains information about the evmsEventModule 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
moduleNumber | evms:ModuleNumber (string:Basic) | Module number for event module | A sequence of characters DEFAULT: all |
moduleStatus | evms:ModuleStatus (scalar:Enum8) | Module status for event module | SELECTION: 5 - online 6 - offline 7 - any DEFAULT: any |
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 Online or Offline Status (Tagged)
Deleting Online or Offline Status (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventModule": {
"attributes": {
"eventTag": "SampleString_123",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<moduletag-items>
<EventModule-list nc:operation="delete">
<eventTag>SampleString_123</eventTag>
</EventModule-list>
</moduletag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event module tag SampleString_123 status any module 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventModule | sys/evtmgr/inst/applet-App_1/events/moduletag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventModule Properties
The following table contains information about the evmsEventModule 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 Online or Offline Status (Untagged)
Configuring Online or Offline Status (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventModuleUnTagged": {
"attributes": {
"moduleNumber": "1",
"moduleStatus": "any"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<module-items>
<moduleNumber>1</moduleNumber>
<moduleStatus>any</moduleStatus>
</module-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event module status any module 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventModuleUnTagged | sys/evtmgr/inst/applet-App_1/events/module |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventModuleUnTagged Properties
The following table contains information about the evmsEventModuleUnTagged 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 |
---|---|---|---|
moduleNumber | evms:ModuleNumber (scalar:Uint16) | Module number for event module | RANGE: [0 , 32] DEFAULT: all |
moduleStatus | evms:ModuleStatus (scalar:Enum8) | Module status for event module | SELECTION: 5 - online 6 - offline 7 - any DEFAULT: any |
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 Online or Offline Status (Untagged)
Deleting Online or Offline Status (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventModuleUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<module-items nc:operation="delete">
</module-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event module status any module 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventModuleUnTagged | sys/evtmgr/inst/applet-App_1/events/module |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventModuleUnTagged Properties
The following table contains information about the evmsEventModuleUnTagged 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 Offline Status (Tagged)
Configuring Offline Status (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventModule": {
"attributes": {
"eventTag": "SampleString_123",
"moduleNumber": "1",
"moduleStatus": "offline"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<moduletag-items>
<EventModule-list>
<eventTag>SampleString_123</eventTag>
<moduleNumber>1</moduleNumber>
<moduleStatus>offline</moduleStatus>
</EventModule-list>
</moduletag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event module tag SampleString_123 status offline module 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventModule | sys/evtmgr/inst/applet-App_1/events/moduletag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventModule Properties
The following table contains information about the evmsEventModule 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
moduleNumber | evms:ModuleNumber (string:Basic) | Module number for event module | A sequence of characters DEFAULT: all |
moduleStatus | evms:ModuleStatus (scalar:Enum8) | Module status for event module | SELECTION: 5 - online 6 - offline 7 - any DEFAULT: any |
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 Offline Status (Tagged)
Deleting Offline Status (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventModule": {
"attributes": {
"eventTag": "SampleString_123",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<moduletag-items>
<EventModule-list nc:operation="delete">
<eventTag>SampleString_123</eventTag>
</EventModule-list>
</moduletag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event module tag SampleString_123 status offline module 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventModule | sys/evtmgr/inst/applet-App_1/events/moduletag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventModule Properties
The following table contains information about the evmsEventModule 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 Offline Status (Untagged)
Configuring Offline Status (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventModuleUnTagged": {
"attributes": {
"moduleNumber": "1",
"moduleStatus": "offline"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<module-items>
<moduleNumber>1</moduleNumber>
<moduleStatus>offline</moduleStatus>
</module-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event module status offline module 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventModuleUnTagged | sys/evtmgr/inst/applet-App_1/events/module |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventModuleUnTagged Properties
The following table contains information about the evmsEventModuleUnTagged 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 |
---|---|---|---|
moduleNumber | evms:ModuleNumber (scalar:Uint16) | Module number for event module | RANGE: [0 , 32] DEFAULT: all |
moduleStatus | evms:ModuleStatus (scalar:Enum8) | Module status for event module | SELECTION: 5 - online 6 - offline 7 - any DEFAULT: any |
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 Offline Status (Untagged)
Deleting Offline Status (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventModuleUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<module-items nc:operation="delete">
</module-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event module status offline module 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventModuleUnTagged | sys/evtmgr/inst/applet-App_1/events/module |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventModuleUnTagged Properties
The following table contains information about the evmsEventModuleUnTagged 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 the Offline Status for All Modules (Tagged)
Configuring the Offline Status for All Modules (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventModule": {
"attributes": {
"eventTag": "SampleString_123",
"moduleNumber": "all",
"moduleStatus": "offline"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<moduletag-items>
<EventModule-list>
<eventTag>SampleString_123</eventTag>
<moduleNumber>0</moduleNumber>
<moduleStatus>offline</moduleStatus>
</EventModule-list>
</moduletag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event module tag SampleString_123 status offline module all
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventModule | sys/evtmgr/inst/applet-App_1/events/moduletag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventModule Properties
The following table contains information about the evmsEventModule 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
moduleNumber | evms:ModuleNumber (string:Basic) | Module number for event module | A sequence of characters DEFAULT: all |
moduleStatus | evms:ModuleStatus (scalar:Enum8) | Module status for event module | SELECTION: 5 - online 6 - offline 7 - any DEFAULT: any |
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 Offline Status for All Modules (Tagged)
Deleting the Offline Status for All Modules (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventModule": {
"attributes": {
"eventTag": "SampleString_123",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<moduletag-items>
<EventModule-list nc:operation="delete">
<eventTag>SampleString_123</eventTag>
</EventModule-list>
</moduletag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event module tag SampleString_123 status offline module all
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventModule | sys/evtmgr/inst/applet-App_1/events/moduletag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventModule Properties
The following table contains information about the evmsEventModule 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 the Offline Status for All Modules (Untagged)
Configuring the Offline Status for All Modules (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventModuleUnTagged": {
"attributes": {
"moduleNumber": "all",
"moduleStatus": "offline"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<module-items>
<moduleNumber>all</moduleNumber>
<moduleStatus>offline</moduleStatus>
</module-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event module status offline module all
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventModuleUnTagged | sys/evtmgr/inst/applet-App_1/events/module |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventModuleUnTagged Properties
The following table contains information about the evmsEventModuleUnTagged 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 |
---|---|---|---|
moduleNumber | evms:ModuleNumber (scalar:Uint16) | Module number for event module | RANGE: [0 , 32] DEFAULT: all |
moduleStatus | evms:ModuleStatus (scalar:Enum8) | Module status for event module | SELECTION: 5 - online 6 - offline 7 - any DEFAULT: any |
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 Offline Status for All Modules (Untagged)
Deleting the Offline Status for All Modules (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventModuleUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<module-items nc:operation="delete">
</module-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event module status offline module all
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventModuleUnTagged | sys/evtmgr/inst/applet-App_1/events/module |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventModuleUnTagged Properties
The following table contains information about the evmsEventModuleUnTagged 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 Online Status (Tagged)
Configuring Online Status (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventModule": {
"attributes": {
"eventTag": "SampleString_123",
"moduleNumber": "1",
"moduleStatus": "online"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<moduletag-items>
<EventModule-list>
<eventTag>SampleString_123</eventTag>
<moduleNumber>1</moduleNumber>
<moduleStatus>online</moduleStatus>
</EventModule-list>
</moduletag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event module tag SampleString_123 status online module 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventModule | sys/evtmgr/inst/applet-App_1/events/moduletag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventModule Properties
The following table contains information about the evmsEventModule 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
moduleNumber | evms:ModuleNumber (string:Basic) | Module number for event module | A sequence of characters DEFAULT: all |
moduleStatus | evms:ModuleStatus (scalar:Enum8) | Module status for event module | SELECTION: 5 - online 6 - offline 7 - any DEFAULT: any |
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 Online Status (Tagged)
Deleting Online Status (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventModule": {
"attributes": {
"eventTag": "SampleString_123",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<moduletag-items>
<EventModule-list nc:operation="delete">
<eventTag>SampleString_123</eventTag>
</EventModule-list>
</moduletag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event module tag SampleString_123 status online module 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventModule | sys/evtmgr/inst/applet-App_1/events/moduletag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventModule Properties
The following table contains information about the evmsEventModule 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 Online Status (Untagged)
Configuring Online Status (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventModuleUnTagged": {
"attributes": {
"moduleNumber": "1",
"moduleStatus": "online"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<module-items>
<moduleNumber>1</moduleNumber>
<moduleStatus>online</moduleStatus>
</module-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event module status online module 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventModuleUnTagged | sys/evtmgr/inst/applet-App_1/events/module |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventModuleUnTagged Properties
The following table contains information about the evmsEventModuleUnTagged 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 |
---|---|---|---|
moduleNumber | evms:ModuleNumber (scalar:Uint16) | Module number for event module | RANGE: [0 , 32] DEFAULT: all |
moduleStatus | evms:ModuleStatus (scalar:Enum8) | Module status for event module | SELECTION: 5 - online 6 - offline 7 - any DEFAULT: any |
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 Online Status (Tagged)
Deleting Online Status (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventModuleUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<module-items nc:operation="delete">
</module-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event module status online module 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventModuleUnTagged | sys/evtmgr/inst/applet-App_1/events/module |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventModuleUnTagged Properties
The following table contains information about the evmsEventModuleUnTagged 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 the Registration Failure After Hitless Upgrade (Tagged)
Configuring the Registration Failure After Hitless Upgrade (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventModuleFailure": {
"attributes": {
"count": "1",
"errType": "hitless-upgrade-reg-failure",
"eventTag": "SampleString_123",
"moduleNumber": "1",
"time": "none"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<modulefailuretag-items>
<EventModuleFailure-list>
<eventTag>SampleString_123</eventTag>
<count>1</count>
<errType>hitless-upgrade-reg-failure</errType>
<moduleNumber>1</moduleNumber>
<time>-1</time>
</EventModuleFailure-list>
</modulefailuretag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event module-failure tag SampleString_123 type hitless-upgrade-reg-failure module 1 count 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventModuleFailure | sys/evtmgr/inst/applet-App_1/events/modulefailuretag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventModuleFailure Properties
The following table contains information about the evmsEventModuleFailure 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 |
---|---|---|---|
count | scalar:Uint32 | Integer number to be used as count | RANGE: [0 , 65000] DEFAULT: 0 |
errType | evms:ErrorType (scalar:Enum32) | Error type for event module-failure | SELECTION: 21 - unexpected-registration 22 - registration-failure 23 - registration-timeout 25 - runtime-diag-failure 26 - runtime-diag-timeout 30 - lc-ready-timeout 38 - lc-failed 69 - lc-not-responding 91 - lc-sw-failure 119 - image-upgrade-failed 212 - sequence-timeout 226 - hitless-upgrade-reg-failure 227 - hitless-upgrade-diag-failure 228 - hitless-upgrade-procmgr-notif 231 - hitless-upgrade-seq-timeout 238 - upgrade-srg-not-compatible 239 - hitless-upgrade-failure 258 - srg-info-resp-timeout 276 - image-download-failed 400 - insertion-seq-failure 406 - addon-sequence-failure 65535 - any DEFAULT: any |
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
moduleNumber | evms:ModuleNumber (string:Basic) | Module number for event module-failure | A sequence of characters DEFAULT: all |
time | evms:timeInterval (scalar:Sint32) | Time interval within which the events need to happen | RANGE: [-1 , 10000000] DEFAULT: none |
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 Registration Failure After Hitless Upgrade (Tagged)
Deleting the Registration Failure After Hitless Upgrade (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventModuleFailure": {
"attributes": {
"eventTag": "SampleString_123",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<modulefailuretag-items>
<EventModuleFailure-list nc:operation="delete">
<eventTag>SampleString_123</eventTag>
</EventModuleFailure-list>
</modulefailuretag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event module-failure tag SampleString_123 type hitless-upgrade-reg-failure module 1 count 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventModuleFailure | sys/evtmgr/inst/applet-App_1/events/modulefailuretag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventModuleFailure Properties
The following table contains information about the evmsEventModuleFailure 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 the Registration Failure After Hitless Upgrade (Untagged)
Configuring the Registration Failure After Hitless Upgrade (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventModuleFailureUnTagged": {
"attributes": {
"count": "1",
"errType": "hitless-upgrade-reg-failure",
"moduleNumber": "1",
"time": "none"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<modulefailure-items>
<count>1</count>
<errType>hitless-upgrade-reg-failure</errType>
<moduleNumber>1</moduleNumber>
<time>-1</time>
</modulefailure-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event module-failure type hitless-upgrade-reg-failure module 1 count 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventModuleFailureUnTagged | sys/evtmgr/inst/applet-App_1/events/modulefailure |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventModuleFailureUnTagged Properties
The following table contains information about the evmsEventModuleFailureUnTagged 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 |
---|---|---|---|
count | scalar:Uint32 | Integer number to be used as count | RANGE: [0 , 65000] DEFAULT: 0 |
errType | evms:ErrorType (scalar:Enum32) | Error type for event module-failure | SELECTION: 21 - unexpected-registration 22 - registration-failure 23 - registration-timeout 25 - runtime-diag-failure 26 - runtime-diag-timeout 30 - lc-ready-timeout 38 - lc-failed 69 - lc-not-responding 91 - lc-sw-failure 119 - image-upgrade-failed 212 - sequence-timeout 226 - hitless-upgrade-reg-failure 227 - hitless-upgrade-diag-failure 228 - hitless-upgrade-procmgr-notif 231 - hitless-upgrade-seq-timeout 238 - upgrade-srg-not-compatible 239 - hitless-upgrade-failure 258 - srg-info-resp-timeout 276 - image-download-failed 400 - insertion-seq-failure 406 - addon-sequence-failure 65535 - any DEFAULT: any |
moduleNumber | evms:ModuleNumber (scalar:Uint16) | Module number for event module-failure | RANGE: [0 , 32] DEFAULT: all |
time | evms:timeInterval (scalar:Sint32) | Time interval within which the events need to happen | RANGE: [-1 , 10000000] DEFAULT: none |
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 Registration Failure After Hitless Upgrade (Untagged)
Deleting the Registration Failure After Hitless Upgrade (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventModuleFailureUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<modulefailure-items nc:operation="delete">
</modulefailure-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event module-failure type hitless-upgrade-reg-failure module 1 count 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventModuleFailureUnTagged | sys/evtmgr/inst/applet-App_1/events/modulefailure |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventModuleFailureUnTagged Properties
The following table contains information about the evmsEventModuleFailureUnTagged 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 the Registration Failure After Hitless Upgrade for All Modules (Tagged)
Configuring the Registration Failure After Hitless Upgrade for All Modules (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventModuleFailure": {
"attributes": {
"count": "1",
"errType": "hitless-upgrade-reg-failure",
"eventTag": "SampleString_123",
"moduleNumber": "all",
"time": "none"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<modulefailuretag-items>
<EventModuleFailure-list>
<eventTag>SampleString_123</eventTag>
<count>1</count>
<errType>hitless-upgrade-reg-failure</errType>
<moduleNumber>0</moduleNumber>
<time>-1</time>
</EventModuleFailure-list>
</modulefailuretag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event module-failure tag SampleString_123 type hitless-upgrade-reg-failure module all count 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventModuleFailure | sys/evtmgr/inst/applet-App_1/events/modulefailuretag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventModuleFailure Properties
The following table contains information about the evmsEventModuleFailure 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 |
---|---|---|---|
count | scalar:Uint32 | Integer number to be used as count | RANGE: [0 , 65000] DEFAULT: 0 |
errType | evms:ErrorType (scalar:Enum32) | Error type for event module-failure | SELECTION: 21 - unexpected-registration 22 - registration-failure 23 - registration-timeout 25 - runtime-diag-failure 26 - runtime-diag-timeout 30 - lc-ready-timeout 38 - lc-failed 69 - lc-not-responding 91 - lc-sw-failure 119 - image-upgrade-failed 212 - sequence-timeout 226 - hitless-upgrade-reg-failure 227 - hitless-upgrade-diag-failure 228 - hitless-upgrade-procmgr-notif 231 - hitless-upgrade-seq-timeout 238 - upgrade-srg-not-compatible 239 - hitless-upgrade-failure 258 - srg-info-resp-timeout 276 - image-download-failed 400 - insertion-seq-failure 406 - addon-sequence-failure 65535 - any DEFAULT: any |
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
moduleNumber | evms:ModuleNumber (string:Basic) | Module number for event module-failure | A sequence of characters DEFAULT: all |
time | evms:timeInterval (scalar:Sint32) | Time interval within which the events need to happen | RANGE: [-1 , 10000000] DEFAULT: none |
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 Registration Failure After Hitless Upgrade for All Modules (Tagged)
Deleting the Registration Failure After Hitless Upgrade for All Modules (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventModuleFailure": {
"attributes": {
"eventTag": "SampleString_123",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<modulefailuretag-items>
<EventModuleFailure-list nc:operation="delete">
<eventTag>SampleString_123</eventTag>
</EventModuleFailure-list>
</modulefailuretag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event module-failure tag SampleString_123 type hitless-upgrade-reg-failure module all count 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventModuleFailure | sys/evtmgr/inst/applet-App_1/events/modulefailuretag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventModuleFailure Properties
The following table contains information about the evmsEventModuleFailure 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 the Registration Failure After Hitless Upgrade for All Modules (Untagged)
Configuring the Registration Failure After Hitless Upgrade for All Modules (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventModuleFailureUnTagged": {
"attributes": {
"count": "1",
"errType": "hitless-upgrade-reg-failure",
"moduleNumber": "all",
"time": "none"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<modulefailure-items>
<count>1</count>
<errType>hitless-upgrade-reg-failure</errType>
<moduleNumber>all</moduleNumber>
<time>-1</time>
</modulefailure-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event module-failure type hitless-upgrade-reg-failure module all count 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventModuleFailureUnTagged | sys/evtmgr/inst/applet-App_1/events/modulefailure |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventModuleFailureUnTagged Properties
The following table contains information about the evmsEventModuleFailureUnTagged 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 |
---|---|---|---|
count | scalar:Uint32 | Integer number to be used as count | RANGE: [0 , 65000] DEFAULT: 0 |
errType | evms:ErrorType (scalar:Enum32) | Error type for event module-failure | SELECTION: 21 - unexpected-registration 22 - registration-failure 23 - registration-timeout 25 - runtime-diag-failure 26 - runtime-diag-timeout 30 - lc-ready-timeout 38 - lc-failed 69 - lc-not-responding 91 - lc-sw-failure 119 - image-upgrade-failed 212 - sequence-timeout 226 - hitless-upgrade-reg-failure 227 - hitless-upgrade-diag-failure 228 - hitless-upgrade-procmgr-notif 231 - hitless-upgrade-seq-timeout 238 - upgrade-srg-not-compatible 239 - hitless-upgrade-failure 258 - srg-info-resp-timeout 276 - image-download-failed 400 - insertion-seq-failure 406 - addon-sequence-failure 65535 - any DEFAULT: any |
moduleNumber | evms:ModuleNumber (scalar:Uint16) | Module number for event module-failure | RANGE: [0 , 32] DEFAULT: all |
time | evms:timeInterval (scalar:Sint32) | Time interval within which the events need to happen | RANGE: [-1 , 10000000] DEFAULT: none |
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 Registration Failure After Hitless Upgrade for All Modules (Untagged)
Deleting the Registration Failure After Hitless Upgrade for All Modules (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventModuleFailureUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<modulefailure-items nc:operation="delete">
</modulefailure-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event module-failure type hitless-upgrade-reg-failure module all count 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventModuleFailureUnTagged | sys/evtmgr/inst/applet-App_1/events/modulefailure |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventModuleFailureUnTagged Properties
The following table contains information about the evmsEventModuleFailureUnTagged 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 Any OIR (Fan; Tagged)
Configuring Any OIR (Fan; Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOir": {
"attributes": {
"deviceNumber": "5",
"deviceType": "fan",
"eventTag": "SampleString_123",
"oirType": "anyoir"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oirtag-items>
<EventOir-list>
<eventTag>SampleString_123</eventTag>
<deviceNumber>5</deviceNumber>
<deviceType>fan</deviceType>
<oirType>anyoir</oirType>
</EventOir-list>
</oirtag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event oir tag SampleString_123 fan anyoir 5
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOir | sys/evtmgr/inst/applet-App_1/events/oirtag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOir Properties
The following table contains information about the evmsEventOir 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 |
---|---|---|---|
deviceNumber | evms:DeviceNumber (scalar:Uint16) | Device number matching with device type | RANGE: [0 , 32] DEFAULT: all |
deviceType | evms:DeviceType (scalar:Enum8) | Device type for event oir | SELECTION: 1 - fan 2 - module 3 - powersupply DEFAULT: module |
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
oirType | evms:OirType (scalar:Enum8) | Oir type for event oir | SELECTION: 5 - insert 6 - remove 8 - anyoir DEFAULT: anyoir |
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 Any OIR (Fan; Tagged)
Deleting Any OIR (Fan; Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOir": {
"attributes": {
"eventTag": "SampleString_123",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oirtag-items>
<EventOir-list nc:operation="delete">
<eventTag>SampleString_123</eventTag>
</EventOir-list>
</oirtag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event oir tag SampleString_123 fan anyoir 5
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOir | sys/evtmgr/inst/applet-App_1/events/oirtag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOir Properties
The following table contains information about the evmsEventOir 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 Any OIR (Fan; Untagged)
Configuring Any OIR (Fan; Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOirUnTagged": {
"attributes": {
"deviceNumber": "5",
"deviceType": "fan",
"oirType": "anyoir"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oir-items>
<deviceNumber>5</deviceNumber>
<deviceType>fan</deviceType>
<oirType>anyoir</oirType>
</oir-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event oir fan anyoir 5
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOirUnTagged | sys/evtmgr/inst/applet-App_1/events/oir |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOirUnTagged Properties
The following table contains information about the evmsEventOirUnTagged 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 |
---|---|---|---|
deviceNumber | evms:DeviceNumber (scalar:Uint16) | Device number matching with device type | RANGE: [0 , 32] DEFAULT: all |
deviceType | evms:DeviceType (scalar:Enum8) | Device type for event oir | SELECTION: 1 - fan 2 - module 3 - powersupply DEFAULT: module |
oirType | evms:OirType (scalar:Enum8) | Oir type for event oir | SELECTION: 5 - insert 6 - remove 8 - anyoir DEFAULT: anyoir |
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 Any OIR (Fan; Untagged)
Deleting Any OIR (Fan; Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOirUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oir-items nc:operation="delete">
</oir-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event oir fan anyoir 5
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOirUnTagged | sys/evtmgr/inst/applet-App_1/events/oir |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOirUnTagged Properties
The following table contains information about the evmsEventOirUnTagged 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 OIR Insert (Fan; Tagged)
Configuring OIR Insert (Fan; Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOir": {
"attributes": {
"deviceNumber": "5",
"deviceType": "fan",
"eventTag": "SampleString_123",
"oirType": "insert"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oirtag-items>
<EventOir-list>
<eventTag>SampleString_123</eventTag>
<deviceNumber>5</deviceNumber>
<deviceType>fan</deviceType>
<oirType>insert</oirType>
</EventOir-list>
</oirtag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event oir tag SampleString_123 fan insert 5
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOir | sys/evtmgr/inst/applet-App_1/events/oirtag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOir Properties
The following table contains information about the evmsEventOir 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 |
---|---|---|---|
deviceNumber | evms:DeviceNumber (scalar:Uint16) | Device number matching with device type | RANGE: [0 , 32] DEFAULT: all |
deviceType | evms:DeviceType (scalar:Enum8) | Device type for event oir | SELECTION: 1 - fan 2 - module 3 - powersupply DEFAULT: module |
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
oirType | evms:OirType (scalar:Enum8) | Oir type for event oir | SELECTION: 5 - insert 6 - remove 8 - anyoir DEFAULT: anyoir |
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 OIR Insert (Fan; Tagged)
Deleting OIR Insert (Fan; Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOir": {
"attributes": {
"eventTag": "SampleString_123",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oirtag-items>
<EventOir-list nc:operation="delete">
<eventTag>SampleString_123</eventTag>
</EventOir-list>
</oirtag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event oir tag SampleString_123 fan insert 5
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOir | sys/evtmgr/inst/applet-App_1/events/oirtag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOir Properties
The following table contains information about the evmsEventOir 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 OIR Insert (Fan; Untagged)
Configuring OIR Insert (Fan; Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOirUnTagged": {
"attributes": {
"deviceNumber": "5",
"deviceType": "fan",
"oirType": "insert"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oir-items>
<deviceNumber>5</deviceNumber>
<deviceType>fan</deviceType>
<oirType>insert</oirType>
</oir-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event oir fan insert 5
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOirUnTagged | sys/evtmgr/inst/applet-App_1/events/oir |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOirUnTagged Properties
The following table contains information about the evmsEventOirUnTagged 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 |
---|---|---|---|
deviceNumber | evms:DeviceNumber (scalar:Uint16) | Device number matching with device type | RANGE: [0 , 32] DEFAULT: all |
deviceType | evms:DeviceType (scalar:Enum8) | Device type for event oir | SELECTION: 1 - fan 2 - module 3 - powersupply DEFAULT: module |
oirType | evms:OirType (scalar:Enum8) | Oir type for event oir | SELECTION: 5 - insert 6 - remove 8 - anyoir DEFAULT: anyoir |
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 OIR Insert (Fan; Untagged)
Deleting OIR Insert (Fan; Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOirUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oir-items nc:operation="delete">
</oir-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event oir fan insert 5
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOirUnTagged | sys/evtmgr/inst/applet-App_1/events/oir |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOirUnTagged Properties
The following table contains information about the evmsEventOirUnTagged 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 OIR Remove (Fan; Tagged)
Configuring OIR Remove (Fan; Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOir": {
"attributes": {
"deviceNumber": "5",
"deviceType": "fan",
"eventTag": "SampleString_123",
"oirType": "remove"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oirtag-items>
<EventOir-list>
<eventTag>SampleString_123</eventTag>
<deviceNumber>5</deviceNumber>
<deviceType>fan</deviceType>
<oirType>remove</oirType>
</EventOir-list>
</oirtag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event oir tag SampleString_123 fan remove 5
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOir | sys/evtmgr/inst/applet-App_1/events/oirtag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOir Properties
The following table contains information about the evmsEventOir 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 |
---|---|---|---|
deviceNumber | evms:DeviceNumber (scalar:Uint16) | Device number matching with device type | RANGE: [0 , 32] DEFAULT: all |
deviceType | evms:DeviceType (scalar:Enum8) | Device type for event oir | SELECTION: 1 - fan 2 - module 3 - powersupply DEFAULT: module |
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
oirType | evms:OirType (scalar:Enum8) | Oir type for event oir | SELECTION: 5 - insert 6 - remove 8 - anyoir DEFAULT: anyoir |
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 OIR Remove (Fan; Tagged)
Deleting OIR Remove (Fan; Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOir": {
"attributes": {
"eventTag": "SampleString_123",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oirtag-items>
<EventOir-list nc:operation="delete">
<eventTag>SampleString_123</eventTag>
</EventOir-list>
</oirtag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event oir tag SampleString_123 fan remove 5
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOir | sys/evtmgr/inst/applet-App_1/events/oirtag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOir Properties
The following table contains information about the evmsEventOir 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 OIR Remove (Fan; Untagged)
Configuring OIR Remove (Fan; Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOirUnTagged": {
"attributes": {
"deviceNumber": "5",
"deviceType": "fan",
"oirType": "remove"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oir-items>
<deviceNumber>5</deviceNumber>
<deviceType>fan</deviceType>
<oirType>remove</oirType>
</oir-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event oir fan remove 5
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOirUnTagged | sys/evtmgr/inst/applet-App_1/events/oir |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOirUnTagged Properties
The following table contains information about the evmsEventOirUnTagged 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 |
---|---|---|---|
deviceNumber | evms:DeviceNumber (scalar:Uint16) | Device number matching with device type | RANGE: [0 , 32] DEFAULT: all |
deviceType | evms:DeviceType (scalar:Enum8) | Device type for event oir | SELECTION: 1 - fan 2 - module 3 - powersupply DEFAULT: module |
oirType | evms:OirType (scalar:Enum8) | Oir type for event oir | SELECTION: 5 - insert 6 - remove 8 - anyoir DEFAULT: anyoir |
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 OIR Remove (Fan; Untagged)
Deleting OIR Remove (Fan; Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOirUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oir-items nc:operation="delete">
</oir-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event oir fan remove 5
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOirUnTagged | sys/evtmgr/inst/applet-App_1/events/oir |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOirUnTagged Properties
The following table contains information about the evmsEventOirUnTagged 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 Any OIR (Module; Tagged)
Configuring Any OIR (Module; Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOir": {
"attributes": {
"deviceNumber": "1",
"deviceType": "module",
"eventTag": "SampleString_123",
"oirType": "anyoir"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oirtag-items>
<EventOir-list>
<eventTag>SampleString_123</eventTag>
<deviceNumber>1</deviceNumber>
<deviceType>module</deviceType>
<oirType>anyoir</oirType>
</EventOir-list>
</oirtag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event oir tag SampleString_123 module anyoir 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOir | sys/evtmgr/inst/applet-App_1/events/oirtag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOir Properties
The following table contains information about the evmsEventOir 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 |
---|---|---|---|
deviceNumber | evms:DeviceNumber (scalar:Uint16) | Device number matching with device type | RANGE: [0 , 32] DEFAULT: all |
deviceType | evms:DeviceType (scalar:Enum8) | Device type for event oir | SELECTION: 1 - fan 2 - module 3 - powersupply DEFAULT: module |
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
oirType | evms:OirType (scalar:Enum8) | Oir type for event oir | SELECTION: 5 - insert 6 - remove 8 - anyoir DEFAULT: anyoir |
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 Any OIR (Module; Tagged)
Deleting Any OIR (Module; Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOir": {
"attributes": {
"eventTag": "SampleString_123",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oirtag-items>
<EventOir-list nc:operation="delete">
<eventTag>SampleString_123</eventTag>
</EventOir-list>
</oirtag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event oir tag SampleString_123 module anyoir 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOir | sys/evtmgr/inst/applet-App_1/events/oirtag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOir Properties
The following table contains information about the evmsEventOir 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 Any OIR (Module; Untagged)
Configuring Any OIR (Module; Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOirUnTagged": {
"attributes": {
"deviceNumber": "1",
"deviceType": "module",
"oirType": "anyoir"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oir-items>
<deviceNumber>1</deviceNumber>
<deviceType>module</deviceType>
<oirType>anyoir</oirType>
</oir-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event oir module anyoir 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOirUnTagged | sys/evtmgr/inst/applet-App_1/events/oir |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOirUnTagged Properties
The following table contains information about the evmsEventOirUnTagged 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 |
---|---|---|---|
deviceNumber | evms:DeviceNumber (scalar:Uint16) | Device number matching with device type | RANGE: [0 , 32] DEFAULT: all |
deviceType | evms:DeviceType (scalar:Enum8) | Device type for event oir | SELECTION: 1 - fan 2 - module 3 - powersupply DEFAULT: module |
oirType | evms:OirType (scalar:Enum8) | Oir type for event oir | SELECTION: 5 - insert 6 - remove 8 - anyoir DEFAULT: anyoir |
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 Any OIR (Module; Untagged)
Deleting Any OIR (Module; Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOirUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oir-items nc:operation="delete">
</oir-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event oir module anyoir 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOirUnTagged | sys/evtmgr/inst/applet-App_1/events/oir |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOirUnTagged Properties
The following table contains information about the evmsEventOirUnTagged 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 OIR Insert (Module; Tagged)
Configuring OIR Insert (Module; Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOir": {
"attributes": {
"deviceNumber": "1",
"deviceType": "module",
"eventTag": "SampleString_123",
"oirType": "insert"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oirtag-items>
<EventOir-list>
<eventTag>SampleString_123</eventTag>
<deviceNumber>1</deviceNumber>
<deviceType>module</deviceType>
<oirType>insert</oirType>
</EventOir-list>
</oirtag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event oir tag SampleString_123 module insert 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOir | sys/evtmgr/inst/applet-App_1/events/oirtag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOir Properties
The following table contains information about the evmsEventOir 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 |
---|---|---|---|
deviceNumber | evms:DeviceNumber (scalar:Uint16) | Device number matching with device type | RANGE: [0 , 32] DEFAULT: all |
deviceType | evms:DeviceType (scalar:Enum8) | Device type for event oir | SELECTION: 1 - fan 2 - module 3 - powersupply DEFAULT: module |
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
oirType | evms:OirType (scalar:Enum8) | Oir type for event oir | SELECTION: 5 - insert 6 - remove 8 - anyoir DEFAULT: anyoir |
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 OIR Insert (Module; Tagged)
Deleting OIR Insert (Module; Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOir": {
"attributes": {
"eventTag": "SampleString_123",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oirtag-items>
<EventOir-list nc:operation="delete">
<eventTag>SampleString_123</eventTag>
</EventOir-list>
</oirtag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event oir tag SampleString_123 module insert 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOir | sys/evtmgr/inst/applet-App_1/events/oirtag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOir Properties
The following table contains information about the evmsEventOir 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 OIR Insert (Module; Untagged)
Configuring OIR Insert (Module; Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOirUnTagged": {
"attributes": {
"deviceNumber": "1",
"deviceType": "module",
"oirType": "insert"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oir-items>
<deviceNumber>1</deviceNumber>
<deviceType>module</deviceType>
<oirType>insert</oirType>
</oir-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event oir module insert 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOirUnTagged | sys/evtmgr/inst/applet-App_1/events/oir |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOirUnTagged Properties
The following table contains information about the evmsEventOirUnTagged 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 |
---|---|---|---|
deviceNumber | evms:DeviceNumber (scalar:Uint16) | Device number matching with device type | RANGE: [0 , 32] DEFAULT: all |
deviceType | evms:DeviceType (scalar:Enum8) | Device type for event oir | SELECTION: 1 - fan 2 - module 3 - powersupply DEFAULT: module |
oirType | evms:OirType (scalar:Enum8) | Oir type for event oir | SELECTION: 5 - insert 6 - remove 8 - anyoir DEFAULT: anyoir |
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 OIR Insert (Module; Untagged)
Deleting OIR Insert (Module; Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOirUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oir-items nc:operation="delete">
</oir-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event oir module insert 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOirUnTagged | sys/evtmgr/inst/applet-App_1/events/oir |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOirUnTagged Properties
The following table contains information about the evmsEventOirUnTagged 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 OIR Remove (Module; Tagged)
Configuring OIR Remove (Module; Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOir": {
"attributes": {
"deviceNumber": "1",
"deviceType": "module",
"eventTag": "SampleString_123",
"oirType": "remove"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oirtag-items>
<EventOir-list>
<eventTag>SampleString_123</eventTag>
<deviceNumber>1</deviceNumber>
<deviceType>module</deviceType>
<oirType>remove</oirType>
</EventOir-list>
</oirtag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event oir tag SampleString_123 module remove 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOir | sys/evtmgr/inst/applet-App_1/events/oirtag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOir Properties
The following table contains information about the evmsEventOir 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 |
---|---|---|---|
deviceNumber | evms:DeviceNumber (scalar:Uint16) | Device number matching with device type | RANGE: [0 , 32] DEFAULT: all |
deviceType | evms:DeviceType (scalar:Enum8) | Device type for event oir | SELECTION: 1 - fan 2 - module 3 - powersupply DEFAULT: module |
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
oirType | evms:OirType (scalar:Enum8) | Oir type for event oir | SELECTION: 5 - insert 6 - remove 8 - anyoir DEFAULT: anyoir |
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 OIR Remove (Module; Tagged)
Deleting OIR Remove (Module; Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOir": {
"attributes": {
"eventTag": "SampleString_123",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oirtag-items>
<EventOir-list nc:operation="delete">
<eventTag>SampleString_123</eventTag>
</EventOir-list>
</oirtag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event oir tag SampleString_123 module remove 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOir | sys/evtmgr/inst/applet-App_1/events/oirtag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOir Properties
The following table contains information about the evmsEventOir 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 OIR Remove (Module; Untagged)
Configuring OIR Remove (Module; Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOirUnTagged": {
"attributes": {
"deviceNumber": "1",
"deviceType": "module",
"oirType": "remove"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oir-items>
<deviceNumber>1</deviceNumber>
<deviceType>module</deviceType>
<oirType>remove</oirType>
</oir-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event oir module remove 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOirUnTagged | sys/evtmgr/inst/applet-App_1/events/oir |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOirUnTagged Properties
The following table contains information about the evmsEventOirUnTagged 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 |
---|---|---|---|
deviceNumber | evms:DeviceNumber (scalar:Uint16) | Device number matching with device type | RANGE: [0 , 32] DEFAULT: all |
deviceType | evms:DeviceType (scalar:Enum8) | Device type for event oir | SELECTION: 1 - fan 2 - module 3 - powersupply DEFAULT: module |
oirType | evms:OirType (scalar:Enum8) | Oir type for event oir | SELECTION: 5 - insert 6 - remove 8 - anyoir DEFAULT: anyoir |
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 OIR Remove (Module; Untagged)
Deleting OIR Remove (Module; Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOirUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oir-items nc:operation="delete">
</oir-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event oir module remove 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOirUnTagged | sys/evtmgr/inst/applet-App_1/events/oir |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOirUnTagged Properties
The following table contains information about the evmsEventOirUnTagged 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 Any OIR (Powersupply; Tagged)
Configuring Any OIR (Powersupply; Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOir": {
"attributes": {
"deviceNumber": "4",
"deviceType": "powersupply",
"eventTag": "SampleString_123",
"oirType": "anyoir"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oirtag-items>
<EventOir-list>
<eventTag>SampleString_123</eventTag>
<deviceNumber>4</deviceNumber>
<deviceType>powersupply</deviceType>
<oirType>anyoir</oirType>
</EventOir-list>
</oirtag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event oir tag SampleString_123 powersupply anyoir 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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOir | sys/evtmgr/inst/applet-App_1/events/oirtag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOir Properties
The following table contains information about the evmsEventOir 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 |
---|---|---|---|
deviceNumber | evms:DeviceNumber (scalar:Uint16) | Device number matching with device type | RANGE: [0 , 32] DEFAULT: all |
deviceType | evms:DeviceType (scalar:Enum8) | Device type for event oir | SELECTION: 1 - fan 2 - module 3 - powersupply DEFAULT: module |
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
oirType | evms:OirType (scalar:Enum8) | Oir type for event oir | SELECTION: 5 - insert 6 - remove 8 - anyoir DEFAULT: anyoir |
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 Any OIR (Powersupply; Tagged)
Deleting Any OIR (Powersupply; Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOir": {
"attributes": {
"eventTag": "SampleString_123",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oirtag-items>
<EventOir-list nc:operation="delete">
<eventTag>SampleString_123</eventTag>
</EventOir-list>
</oirtag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event oir tag SampleString_123 powersupply anyoir 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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOir | sys/evtmgr/inst/applet-App_1/events/oirtag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOir Properties
The following table contains information about the evmsEventOir 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 Any OIR (Powersupply; Untagged)
Configuring Any OIR (Powersupply; Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOirUnTagged": {
"attributes": {
"deviceNumber": "4",
"deviceType": "powersupply",
"oirType": "anyoir"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oir-items>
<deviceNumber>4</deviceNumber>
<deviceType>powersupply</deviceType>
<oirType>anyoir</oirType>
</oir-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event oir powersupply anyoir 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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOirUnTagged | sys/evtmgr/inst/applet-App_1/events/oir |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOirUnTagged Properties
The following table contains information about the evmsEventOirUnTagged 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 |
---|---|---|---|
deviceNumber | evms:DeviceNumber (scalar:Uint16) | Device number matching with device type | RANGE: [0 , 32] DEFAULT: all |
deviceType | evms:DeviceType (scalar:Enum8) | Device type for event oir | SELECTION: 1 - fan 2 - module 3 - powersupply DEFAULT: module |
oirType | evms:OirType (scalar:Enum8) | Oir type for event oir | SELECTION: 5 - insert 6 - remove 8 - anyoir DEFAULT: anyoir |
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 Any OIR (Powersupply; Untagged)
Deleting Any OIR (Powersupply; Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOirUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oir-items nc:operation="delete">
</oir-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event oir powersupply anyoir 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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOirUnTagged | sys/evtmgr/inst/applet-App_1/events/oir |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOirUnTagged Properties
The following table contains information about the evmsEventOirUnTagged 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 OIR Insert (Powersupply; Tagged)
Configuring OIR Insert (Powersupply; Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOir": {
"attributes": {
"deviceNumber": "4",
"deviceType": "powersupply",
"eventTag": "SampleString_123",
"oirType": "insert"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oirtag-items>
<EventOir-list>
<eventTag>SampleString_123</eventTag>
<deviceNumber>4</deviceNumber>
<deviceType>powersupply</deviceType>
<oirType>insert</oirType>
</EventOir-list>
</oirtag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event oir tag SampleString_123 powersupply insert 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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOir | sys/evtmgr/inst/applet-App_1/events/oirtag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOir Properties
The following table contains information about the evmsEventOir 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 |
---|---|---|---|
deviceNumber | evms:DeviceNumber (scalar:Uint16) | Device number matching with device type | RANGE: [0 , 32] DEFAULT: all |
deviceType | evms:DeviceType (scalar:Enum8) | Device type for event oir | SELECTION: 1 - fan 2 - module 3 - powersupply DEFAULT: module |
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
oirType | evms:OirType (scalar:Enum8) | Oir type for event oir | SELECTION: 5 - insert 6 - remove 8 - anyoir DEFAULT: anyoir |
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 OIR Insert (Powersupply; Tagged)
Deleting OIR Insert (Powersupply; Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOir": {
"attributes": {
"eventTag": "SampleString_123",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oirtag-items>
<EventOir-list nc:operation="delete">
<eventTag>SampleString_123</eventTag>
</EventOir-list>
</oirtag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event oir tag SampleString_123 powersupply insert 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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOir | sys/evtmgr/inst/applet-App_1/events/oirtag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOir Properties
The following table contains information about the evmsEventOir 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 OIR Insert (Powersupply; Untagged)
Configuring OIR Insert (Powersupply; Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOirUnTagged": {
"attributes": {
"deviceNumber": "4",
"deviceType": "powersupply",
"oirType": "insert"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oir-items>
<deviceNumber>4</deviceNumber>
<deviceType>powersupply</deviceType>
<oirType>insert</oirType>
</oir-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event oir powersupply insert 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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOirUnTagged | sys/evtmgr/inst/applet-App_1/events/oir |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOirUnTagged Properties
The following table contains information about the evmsEventOirUnTagged 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 |
---|---|---|---|
deviceNumber | evms:DeviceNumber (scalar:Uint16) | Device number matching with device type | RANGE: [0 , 32] DEFAULT: all |
deviceType | evms:DeviceType (scalar:Enum8) | Device type for event oir | SELECTION: 1 - fan 2 - module 3 - powersupply DEFAULT: module |
oirType | evms:OirType (scalar:Enum8) | Oir type for event oir | SELECTION: 5 - insert 6 - remove 8 - anyoir DEFAULT: anyoir |
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 OIR Insert (Powersupply; Untagged)
Deleting OIR Insert (Powersupply; Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOirUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oir-items nc:operation="delete">
</oir-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event oir powersupply insert 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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOirUnTagged | sys/evtmgr/inst/applet-App_1/events/oir |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOirUnTagged Properties
The following table contains information about the evmsEventOirUnTagged 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 OIR Remove (Powersupply; Tagged)
Configuring OIR Remove (Powersupply; Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOir": {
"attributes": {
"deviceNumber": "4",
"deviceType": "powersupply",
"eventTag": "SampleString_123",
"oirType": "remove"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oirtag-items>
<EventOir-list>
<eventTag>SampleString_123</eventTag>
<deviceNumber>4</deviceNumber>
<deviceType>powersupply</deviceType>
<oirType>remove</oirType>
</EventOir-list>
</oirtag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event oir tag SampleString_123 powersupply remove 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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOir | sys/evtmgr/inst/applet-App_1/events/oirtag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOir Properties
The following table contains information about the evmsEventOir 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 |
---|---|---|---|
deviceNumber | evms:DeviceNumber (scalar:Uint16) | Device number matching with device type | RANGE: [0 , 32] DEFAULT: all |
deviceType | evms:DeviceType (scalar:Enum8) | Device type for event oir | SELECTION: 1 - fan 2 - module 3 - powersupply DEFAULT: module |
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
oirType | evms:OirType (scalar:Enum8) | Oir type for event oir | SELECTION: 5 - insert 6 - remove 8 - anyoir DEFAULT: anyoir |
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 OIR Remove (Powersupply; Tagged) `
Deleting OIR Remove (Powersupply; Tagged) `
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOir": {
"attributes": {
"eventTag": "SampleString_123",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oirtag-items>
<EventOir-list nc:operation="delete">
<eventTag>SampleString_123</eventTag>
</EventOir-list>
</oirtag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event oir tag SampleString_123 powersupply remove 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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOir | sys/evtmgr/inst/applet-App_1/events/oirtag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOir Properties
The following table contains information about the evmsEventOir 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 OIR Remove (Powersupply; Untagged)
Configuring OIR Remove (Powersupply; Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOirUnTagged": {
"attributes": {
"deviceNumber": "4",
"deviceType": "powersupply",
"oirType": "remove"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oir-items>
<deviceNumber>4</deviceNumber>
<deviceType>powersupply</deviceType>
<oirType>remove</oirType>
</oir-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event oir powersupply remove 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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOirUnTagged | sys/evtmgr/inst/applet-App_1/events/oir |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOirUnTagged Properties
The following table contains information about the evmsEventOirUnTagged 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 |
---|---|---|---|
deviceNumber | evms:DeviceNumber (scalar:Uint16) | Device number matching with device type | RANGE: [0 , 32] DEFAULT: all |
deviceType | evms:DeviceType (scalar:Enum8) | Device type for event oir | SELECTION: 1 - fan 2 - module 3 - powersupply DEFAULT: module |
oirType | evms:OirType (scalar:Enum8) | Oir type for event oir | SELECTION: 5 - insert 6 - remove 8 - anyoir DEFAULT: anyoir |
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 OIR Remove (Powersupply; Untagged) `
Deleting OIR Remove (Powersupply; Untagged) `
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventOirUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<oir-items nc:operation="delete">
</oir-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event oir powersupply remove 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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventOirUnTagged | sys/evtmgr/inst/applet-App_1/events/oir |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventOirUnTagged Properties
The following table contains information about the evmsEventOirUnTagged 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 a Storm Control Event Specification
Configuring a Storm Control Event Specification
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventEthpm": {
"attributes": {
"eventStrmCtrl": "yes"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<ethpm-items>
<eventStrmCtrl>true</eventStrmCtrl>
</ethpm-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event storm-control
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventEthpm | sys/evtmgr/inst/applet-App_1/events/ethpm |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventEthpm Properties
The following table contains information about the evmsEventEthpm 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 |
---|---|---|---|
eventStrmCtrl | scalar:Bool | 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 a Storm Control Event Specification
Deleting a Storm Control Event Specification
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventEthpm": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<ethpm-items nc:operation="delete">
</ethpm-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event storm-control
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventEthpm | sys/evtmgr/inst/applet-App_1/events/ethpm |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventEthpm Properties
The following table contains information about the evmsEventEthpm 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 the State of the Tracking Object as Any (Tagged)
Configuring the State of the Tracking Object as Any (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventTrack": {
"attributes": {
"eventTag": "SampleString_123",
"trackId": "84",
"trackStateOp": "any"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<tracktag-items>
<EventTrack-list>
<eventTag>SampleString_123</eventTag>
<trackId>84</trackId>
<trackStateOp>any</trackStateOp>
</EventTrack-list>
</tracktag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event track tag SampleString_123 84 state any
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventTrack | sys/evtmgr/inst/applet-App_1/events/tracktag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventTrack Properties
The following table contains information about the evmsEventTrack 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
trackId | scalar:Uint32 | Track object ID Number | RANGE: [0 , 512] |
trackStateOp | evms:TrackStateOp (scalar:Enum8) | track event specification | SELECTION: 0 - down 1 - up 2 - any DEFAULT: any |
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 State of the Tracking Object Configured as Any (Tagged)
Deleting the State of the Tracking Object Configured as Any (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventTrack": {
"attributes": {
"eventTag": "SampleString_123",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<tracktag-items>
<EventTrack-list nc:operation="delete">
<eventTag>SampleString_123</eventTag>
</EventTrack-list>
</tracktag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event track tag SampleString_123 84 state any
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventTrack | sys/evtmgr/inst/applet-App_1/events/tracktag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventTrack Properties
The following table contains information about the evmsEventTrack 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 the State of the Tracking Object as Any (Untagged)
Configuring the State of the Tracking Object as Any (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventTrackUnTagged": {
"attributes": {
"trackId": "84",
"trackStateOp": "any"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<track-items>
<trackId>84</trackId>
<trackStateOp>any</trackStateOp>
</track-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event track 84 state any
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventTrackUnTagged | sys/evtmgr/inst/applet-App_1/events/track |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventTrackUnTagged Properties
The following table contains information about the evmsEventTrackUnTagged 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 |
---|---|---|---|
trackId | scalar:Uint32 | Track object ID Number | RANGE: [0 , 512] |
trackStateOp | evms:TrackStateOp (scalar:Enum8) | track event specification | SELECTION: 0 - any 1 - up 2 - down DEFAULT: any |
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 State of the Tracking Object Configured as Any (Untagged)
Deleting the State of the Tracking Object Configured as Any (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventTrackUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<track-items nc:operation="delete">
</track-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event track 84 state any
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventTrackUnTagged | sys/evtmgr/inst/applet-App_1/events/track |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventTrackUnTagged Properties
The following table contains information about the evmsEventTrackUnTagged 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 the State of the Tracking Object as Down (Tagged)
Configuring the State of the Tracking Object as Down (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventTrack": {
"attributes": {
"eventTag": "SampleString_123",
"trackId": "84",
"trackStateOp": "down"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<tracktag-items>
<EventTrack-list>
<eventTag>SampleString_123</eventTag>
<trackId>84</trackId>
<trackStateOp>down</trackStateOp>
</EventTrack-list>
</tracktag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event track tag SampleString_123 84 state down
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventTrack | sys/evtmgr/inst/applet-App_1/events/tracktag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventTrack Properties
The following table contains information about the evmsEventTrack 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
trackId | scalar:Uint32 | Track object ID Number | RANGE: [0 , 512] |
trackStateOp | evms:TrackStateOp (scalar:Enum8) | track event specification | SELECTION: 0 - down 1 - up 2 - any DEFAULT: any |
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 State of the Tracking Object Configured as Down (Tagged)
Deleting the State of the Tracking Object Configured as Down (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventTrack": {
"attributes": {
"eventTag": "SampleString_123",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<tracktag-items>
<EventTrack-list nc:operation="delete">
<eventTag>SampleString_123</eventTag>
</EventTrack-list>
</tracktag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event track tag SampleString_123 84 state down
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventTrack | sys/evtmgr/inst/applet-App_1/events/tracktag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventTrack Properties
The following table contains information about the evmsEventTrack 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 the State of the Tracking Object as Down (Untagged)
Configuring the State of the Tracking Object as Down (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventTrackUnTagged": {
"attributes": {
"trackId": "84",
"trackStateOp": "down"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<track-items>
<trackId>84</trackId>
<trackStateOp>down</trackStateOp>
</track-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event track 84 state down
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventTrackUnTagged | sys/evtmgr/inst/applet-App_1/events/track |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventTrackUnTagged Properties
The following table contains information about the evmsEventTrackUnTagged 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 |
---|---|---|---|
trackId | scalar:Uint32 | Track object ID Number | RANGE: [0 , 512] |
trackStateOp | evms:TrackStateOp (scalar:Enum8) | track event specification | SELECTION: 0 - any 1 - up 2 - down DEFAULT: any |
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 State of the Tracking Object Configured as Down (Untagged)
Deleting the State of the Tracking Object Configured as Down (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventTrackUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<track-items nc:operation="delete">
</track-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event track 84 state down
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventTrackUnTagged | sys/evtmgr/inst/applet-App_1/events/track |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventTrackUnTagged Properties
The following table contains information about the evmsEventTrackUnTagged 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 the State of the Tracking Object as Up (Tagged)
Configuring the State of the Tracking Object as Up (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventTrack": {
"attributes": {
"eventTag": "SampleString_123",
"trackId": "84",
"trackStateOp": "up"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<tracktag-items>
<EventTrack-list>
<eventTag>SampleString_123</eventTag>
<trackId>84</trackId>
<trackStateOp>up</trackStateOp>
</EventTrack-list>
</tracktag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event track tag SampleString_123 84 state up
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventTrack | sys/evtmgr/inst/applet-App_1/events/tracktag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventTrack Properties
The following table contains information about the evmsEventTrack 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
trackId | scalar:Uint32 | Track object ID Number | RANGE: [0 , 512] |
trackStateOp | evms:TrackStateOp (scalar:Enum8) | track event specification | SELECTION: 0 - down 1 - up 2 - any DEFAULT: any |
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 State of the Tracking Object as Up (Tagged)
Deleting the State of the Tracking Object as Up (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventTrack": {
"attributes": {
"eventTag": "SampleString_123",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<tracktag-items>
<EventTrack-list nc:operation="delete">
<eventTag>SampleString_123</eventTag>
</EventTrack-list>
</tracktag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event track tag SampleString_123 84 state up
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventTrack | sys/evtmgr/inst/applet-App_1/events/tracktag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventTrack Properties
The following table contains information about the evmsEventTrack 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 the State of the Tracking Object as Up (Tagged)
Configuring the State of the Tracking Object as Up (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventTrackUnTagged": {
"attributes": {
"trackId": "84",
"trackStateOp": "up"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<track-items>
<trackId>84</trackId>
<trackStateOp>up</trackStateOp>
</track-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event track 84 state up
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventTrackUnTagged | sys/evtmgr/inst/applet-App_1/events/track |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventTrackUnTagged Properties
The following table contains information about the evmsEventTrackUnTagged 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 |
---|---|---|---|
trackId | scalar:Uint32 | Track object ID Number | RANGE: [0 , 512] |
trackStateOp | evms:TrackStateOp (scalar:Enum8) | track event specification | SELECTION: 0 - any 1 - up 2 - down DEFAULT: any |
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 State of the Tracking Object as Up (Untagged)
Deleting the State of the Tracking Object as Up (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventTrackUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<track-items nc:operation="delete">
</track-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event track 84 state up
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventTrackUnTagged | sys/evtmgr/inst/applet-App_1/events/track |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventTrackUnTagged Properties
The following table contains information about the evmsEventTrackUnTagged 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 the Fanabsent Event Timer
Configuring the Fanabsent Event Timer
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventFanAbsentUnTagged": {
"attributes": {
"fanNumber": "7",
"time": "14615"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<fanabsent-items>
<fanNumber>7</fanNumber>
<time>14615</time>
</fanabsent-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event fanabsent fan 7 time 14615
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventFanAbsentUnTagged | sys/evtmgr/inst/applet-App_1/events/fanabsent |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventFanAbsentUnTagged Properties
The following table contains information about the evmsEventFanAbsentUnTagged 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 |
---|---|---|---|
fanNumber | evms:IntegerRange (string:Basic) | Specify fan number, 0\ | all for all fan or interger range |
time | evms:FanInterval (scalar:Uint16) | Time in seconds fan can stay absent | RANGE: [10 , 64000] DEFAULT: 10 |
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 Fanabsent Event Timer
Deleting the Fanabsent Event Timer
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventFanAbsentUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<fanabsent-items nc:operation="delete">
</fanabsent-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event fanabsent fan 7 time 14615
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventFanAbsentUnTagged | sys/evtmgr/inst/applet-App_1/events/fanabsent |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventFanAbsentUnTagged Properties
The following table contains information about the evmsEventFanAbsentUnTagged 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 the Fanbad Event Time
Configuring the Fanbad Event Time
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventFanBadUnTagged": {
"attributes": {
"fanNumber": "7",
"time": "36888"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<fanbad-items>
<fanNumber>7</fanNumber>
<time>36888</time>
</fanbad-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event fanbad fan 7 time 36888
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventFanBadUnTagged | sys/evtmgr/inst/applet-App_1/events/fanbad |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventFanBadUnTagged Properties
The following table contains information about the evmsEventFanBadUnTagged 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 |
---|---|---|---|
fanNumber | evms:IntegerRange (string:Basic) | Specify fan number, 0\ | all for all fan or interger range |
time | evms:FanInterval (scalar:Uint16) | Time in seconds fan can stay absent | RANGE: [10 , 64000] DEFAULT: 10 |
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 Fanbad Event Time
Deleting the Fanbad Event Time
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventFanBadUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<fanbad-items nc:operation="delete">
</fanbad-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event fanbad fan 7 time 36888
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventFanBadUnTagged | sys/evtmgr/inst/applet-App_1/events/fanbad |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventFanBadUnTagged Properties
The following table contains information about the evmsEventFanBadUnTagged 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 a Poweroverbudget Event
Configuring a Poweroverbudget Event
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventPowerOverBudgetUnTagged": {
"attributes": {
"eventpoweroverbudgetstatus": "yes"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<poweroverbudget-items>
<eventpoweroverbudgetstatus>true</eventpoweroverbudgetstatus>
</poweroverbudget-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event poweroverbudget
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventPowerOverBudgetUnTagged | sys/evtmgr/inst/applet-App_1/events/poweroverbudget |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventPowerOverBudgetUnTagged Properties
The following table contains information about the evmsEventPowerOverBudgetUnTagged 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 |
---|---|---|---|
eventpoweroverbudgetstatus | scalar:Bool | SELECTION: true or false DEFAULT: yes |
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 Poweroverbudget Event
Deleting a Poweroverbudget Event
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventPowerOverBudgetUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<poweroverbudget-items nc:operation="delete">
</poweroverbudget-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event poweroverbudget
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventPowerOverBudgetUnTagged | sys/evtmgr/inst/applet-App_1/events/poweroverbudget |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventPowerOverBudgetUnTagged Properties
The following table contains information about the evmsEventPowerOverBudgetUnTagged 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 the Number of Occurrences before Raising the Event
Configuring the Number of Occurrences before Raising the Event
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsTag": {
"attributes": {
"correlateTag1": "andnot",
"correlateTag2": "andnot",
"correlateTag3": "andnot",
"eventTag1": "SampleString_123",
"eventTag2": "SampleString_123",
"eventTag3": "SampleString_123",
"eventTag4": "SampleString_123",
"occurences": "1",
"timeInterval": "1"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<tag-items>
<correlateTag1>andnot</correlateTag1>
<correlateTag2>andnot</correlateTag2>
<correlateTag3>andnot</correlateTag3>
<eventTag1>SampleString_123</eventTag1>
<eventTag2>SampleString_123</eventTag2>
<eventTag3>SampleString_123</eventTag3>
<eventTag4>SampleString_123</eventTag4>
<occurences>1</occurences>
<timeInterval>1</timeInterval>
</tag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
tag SampleString_123 andnot SampleString_123 andnot SampleString_123 andnot SampleString_123 happens 1 in 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsTag | correlateTag1:andnot |
correlateTag2:andnot | correlateTag3:andnot |
sys/evtmgr/inst/applet-App_1/events/tag |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsTag Properties
The following table contains information about the evmsTag 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 |
---|---|---|---|
correlateTag1 | evms:CorrelateTagType (scalar:Enum8) | Correlate-1 operator | SELECTION: 0 - none 1 - and 2 - andnot 3 - or DEFAULT: none |
correlateTag2 | evms:CorrelateTagType (scalar:Enum8) | Correlate-2 operator | SELECTION: 0 - none 1 - and 2 - andnot 3 - or DEFAULT: none |
correlateTag3 | evms:CorrelateTagType (scalar:Enum8) | Correlate-3 operator | SELECTION: 0 - none 1 - and 2 - andnot 3 - or DEFAULT: none |
eventTag1 | evms:EventTagType (string:Basic) | Tag-1 to correlate | MAX SIZE: 29 DEFAULT: |
eventTag2 | evms:EventTagType (string:Basic) | Tag-2 to correlate | MAX SIZE: 29 DEFAULT: |
eventTag3 | evms:EventTagType (string:Basic) | Tag-3 to correlate | MAX SIZE: 29 DEFAULT: |
eventTag4 | evms:EventTagType (string:Basic) | Tag-4 to correlate | MAX SIZE: 29 DEFAULT: |
occurences | scalar:Uint32 | Number of occurences | RANGE: [1 , 4294967295] DEFAULT: 1 |
timeInterval | scalar:Uint32 | Time interval | RANGE: [0 , 4294967295] |
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 Number of Occurrences before Raising the Event
Deleting the Number of Occurrences before Raising the Event
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsTag": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<tag-items nc:operation="delete">
</tag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no tag SampleString_123 andnot SampleString_123 andnot SampleString_123 andnot SampleString_123 happens 1 in 1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsTag | sys/evtmgr/inst/applet-App_1/events/tag |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsTag Properties
The following table contains information about the evmsTag 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 a Counter
Configuring a Counter
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsAction": {
"attributes": {
"actionLabel": "1.0"
},
"children": [
{
"evmsActionCounter": {
"attributes": {
"counterName": "action1.0",
"counterOp": "inc",
"counterValue": "1.0"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<action-items>
<Action-list>
<actionLabel>1.0</actionLabel>
<counter-items>
<counterName>action1.0</counterName>
<counterOp>inc</counterOp>
<counterValue>1.0</counterValue>
</counter-items>
</Action-list>
</action-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
action 1.0 counter name action1.0 value 1.0 op inc
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsAction | sys/evtmgr/inst/applet-App_1/action-1.0 |
evmsActionCounter | sys/evtmgr/inst/applet-App_1/action-1.0/counter |
evmsAction Properties
The following table contains information about the evmsAction 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 |
---|---|---|---|
actionLabel | evms:ActionLabelType (string:Basic) | Specify action label | A sequence of characters |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsActionCounter Properties
The following table contains information about the evmsActionCounter 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 |
---|---|---|---|
counterName | string:Basic | Name of the action counter | RANGE: [0 , 29] |
counterOp | evms:CounterOpType (scalar:Enum8) | Specify the operator to be applied | SELECTION: 1 - nop 2 - set 3 - inc 4 - dec DEFAULT: |
counterValue | string:Basic | Specify the value to be applied to the counter | A sequence of characters |
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 Counter
Deleting a Counter
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsAction": {
"attributes": {
"actionLabel": "1.0",
"status": "deleted"
}}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<action-items>
<Action-list nc:operation="delete">
<actionLabel>1.0</actionLabel>
</Action-list>
</action-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no action 1.0 counter name action1.0 value 1.0 op inc
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsAction | sys/evtmgr/inst/applet-App_1/action-1.0 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsAction Properties
The following table contains information about the evmsAction 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 |
---|---|---|---|
actionLabel | evms:ActionLabelType (string:Basic) | Specify action label | A sequence of characters |
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 a VSH CLI Action
Configuring a VSH CLI Action
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsAction": {
"attributes": {
"actionLabel": "1.0"
},
"children": [
{
"evmsActionCLI": {
"attributes": {
"cliCommand": "vsh_cmd",
"execModule": "yes"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<action-items>
<Action-list>
<actionLabel>1.0</actionLabel>
<cli-items>
<cliCommand>vsh_cmd</cliCommand>
<execModule>true</execModule>
</cli-items>
</Action-list>
</action-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
action 1.0 cli local vsh_cmd
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsAction | sys/evtmgr/inst/applet-App_1/action-1.0 |
evmsActionCLI | sys/evtmgr/inst/applet-App_1/action-1.0/cli |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsAction Properties
The following table contains information about the evmsAction 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 |
---|---|---|---|
actionLabel | evms:ActionLabelType (string:Basic) | Specify action label | A sequence of characters |
evmsActionCLI Properties
The following table contains information about the evmsActionCLI 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 |
---|---|---|---|
cliCommand | string:Basic | Enter the VSH command | RANGE: [0 , 1023] DEFAULT: |
execModule | scalar:Bool | Execute the action on the module where event happens | SELECTION: true or false DEFAULT: no |
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 VSH CLI Action
Deleting a VSH CLI Action
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsAction": {
"attributes": {
"actionLabel": "1.0",
"status": "deleted"
}}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<action-items>
<Action-list nc:operation="delete">
<actionLabel>1.0</actionLabel>
</Action-list>
</action-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no action 1.0 cli local vsh_cmd
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsAction | sys/evtmgr/inst/applet-App_1/action-1.0 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsAction Properties
The following table contains information about the evmsAction 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 |
---|---|---|---|
actionLabel | evms:ActionLabelType (string:Basic) | Specify action label | A sequence of characters |
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 a Cron Entry String
Configuring a Cron Entry String
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventTimer": {
"attributes": {
"absoluteTime": "",
"countdownTime": "",
"cronTime": "33 19 02 12 tuesday",
"eventTag": "TAG1",
"name": "Timer_12",
"watchdogTime": ""
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<timertag-items>
<EventTimer-list>
<eventTag>TAG1</eventTag>
<absoluteTime></absoluteTime>
<countdownTime></countdownTime>
<cronTime>33 19 02 12 tuesday</cronTime>
<name>Timer_12</name>
<watchdogTime></watchdogTime>
</EventTimer-list>
</timertag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event timer tag TAG1 cron cron-entry "33 19 02 12 tuesday" name Timer_12
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventTimer | sys/evtmgr/inst/applet-App_1/events/timertag-TAG1 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventTimer Properties
The following table contains information about the evmsEventTimer 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 |
---|---|---|---|
absoluteTime | string:Basic | Event absolute time in seconds | A sequence of characters |
countdownTime | string:Basic | Event countdown time in seconds | A sequence of characters |
cronTime | string:Basic | Event cron time in [min hour dom month dow\] format | RANGE: [0 , 100] |
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
name | string:Basic | Name of the timer | RANGE: [0 , 29] |
watchdogTime | string:Basic | Event watchdog time in seconds | A sequence of characters |
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 Cron Entry String
Deleting a Cron Entry String
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventTimer": {
"attributes": {
"eventTag": "TAG1",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<timertag-items>
<EventTimer-list nc:operation="delete">
<eventTag>TAG1</eventTag>
</EventTimer-list>
</timertag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event timer tag TAG1 cron cron-entry "12" name Timer_12
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventTimer | sys/evtmgr/inst/applet-App_1/events/timertag-TAG1 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventTimer Properties
The following table contains information about the evmsEventTimer 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 Event Tag Id
Configuring an Event Tag Id
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventNone": {
"attributes": {
"eventTag": "TAG1",
"eventnonestatus": "yes"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<nonetag-items>
<EventNone-list>
<eventTag>TAG1</eventTag>
<eventnonestatus>true</eventnonestatus>
</EventNone-list>
</nonetag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event none tag TAG1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventNone | sys/evtmgr/inst/applet-App_1/events/nonetag-TAG1 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventNone Properties
The following table contains information about the evmsEventNone 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
eventnonestatus | scalar:Bool | SELECTION: true or false DEFAULT: yes |
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 Event Tag Id
Deleting an Event Tag Id
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventNone": {
"attributes": {
"eventTag": "TAG1",
"eventnonestatus": "no"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<nonetag-items>
<EventNone-list>
<eventTag>TAG1</eventTag>
<eventnonestatus>false</eventnonestatus>
</EventNone-list>
</nonetag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event none tag TAG1
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventNone | sys/evtmgr/inst/applet-App_1/events/nonetag-TAG1 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventNone Properties
The following table contains information about the evmsEventNone 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
eventnonestatus | scalar:Bool | SELECTION: true or false DEFAULT: yes |
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 CLI Event Specification
Configuring a CLI Event Specification
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventCli": {
"attributes": {
"eventTag": "SampleString_123",
"match": "SampleString_123",
"occurrences": "39618",
"timeInterval": "568290"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<clitag-items>
<EventCli-list>
<eventTag>SampleString_123</eventTag>
<match>SampleString_123</match>
<occurrences>39618</occurrences>
<timeInterval>568290</timeInterval>
</EventCli-list>
</clitag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event cli tag SampleString_123 match "SampleString_123" count 39618 time 568290
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventCli | sys/evtmgr/inst/applet-App_1/events/clitag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventCli Properties
The following table contains information about the evmsEventCli 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
match | string:Basic | CLI regular expression to be used for matching | RANGE: [0 , 128] |
occurrences | scalar:Uint32 | Enter an integer to be used as count | RANGE: [1 , 65000] |
timeInterval | scalar:Uint32 | Time interval in seconds | RANGE: [0 , 10000000] |
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 CLI Event Specification
Deleting a CLI Event Specification
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventCli": {
"attributes": {
"eventTag": "SampleString_123",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<clitag-items>
<EventCli-list nc:operation="delete">
<eventTag>SampleString_123</eventTag>
</EventCli-list>
</clitag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event cli tag SampleString_123 match "SampleString_123" count 39618 time 568290
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventCli | sys/evtmgr/inst/applet-App_1/events/clitag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventCli Properties
The following table contains information about the evmsEventCli 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 SNMP Event Specification
Configuring an SNMP Event Specification
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventSnmp": {
"attributes": {
"entryOp": "ne",
"entryVal": "1000",
"eventTag": "TagName",
"exitComb": "or",
"exitOp": "gt",
"exitOp1": "none",
"exitTimeMax": "4000",
"exitTimeMin": "3000",
"exitVal": "2000",
"exitVal1": "0",
"getType": "exact",
"oid": "SNMPGetOper",
"pollIntervalMax": "123",
"pollIntervalMin": "123"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<snmptag-items>
<EventSnmp-list>
<eventTag>TagName</eventTag>
<entryOp>ne</entryOp>
<entryVal>1000</entryVal>
<exitComb>or</exitComb>
<exitOp>gt</exitOp>
<exitOp1>none</exitOp1>
<exitTimeMax>4000</exitTimeMax>
<exitTimeMin>3000</exitTimeMin>
<exitVal>2000</exitVal>
<exitVal1>0</exitVal1>
<getType>exact</getType>
<oid>SNMPGetOper</oid>
<pollIntervalMax>123</pollIntervalMax>
<pollIntervalMin>123</pollIntervalMin>
</EventSnmp-list>
</snmptag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event snmp tag TagName oid SNMPGetOper get-type exact entry-op ne entry-val 1000 exit-comb or exit-op gt exit-val 2000 exit-time 3000 - 4000 poll-interval 123
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventSnmp | sys/evtmgr/inst/applet-App_1/events/snmptag-TagName |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventSnmp Properties
The following table contains information about the evmsEventSnmp 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 |
---|---|---|---|
entryOp | evms:EntryExitOpType (scalar:Enum8) | Entry comparison operator | SELECTION: 0 - none 1 - gt 2 - ge 3 - eq 4 - ne 5 - lt 6 - le DEFAULT: none |
entryVal | scalar:Uint64 | Value to compare with the current polled value | RANGE: [0, 18446744073709551615] |
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
exitComb | evms:ExitCombType (scalar:Enum8) | Exit criterion combination | SELECTION: 0 - none 1 - or 2 - and DEFAULT: none |
exitOp | evms:EntryExitOpType (scalar:Enum8) | Exit comparison operator | SELECTION: 0 - none 1 - gt 2 - ge 3 - eq 4 - ne 5 - lt 6 - le DEFAULT: none |
exitOp1 | evms:EntryExitOpType (scalar:Enum8) | Exit comparison operator | SELECTION: 0 - none 1 - gt 2 - ge 3 - eq 4 - ne 5 - lt 6 - le DEFAULT: none |
exitTimeMax | scalar:Uint32 | Max Exit time value required | RANGE: [0, 4294967295] |
exitTimeMin | scalar:Uint32 | Min Exit time value required | RANGE: [0, 4294967295] |
exitVal | scalar:Uint64 | Value to compare with the current polled value | RANGE: [0, 18446744073709551615] |
exitVal1 | scalar:Uint64 | Value to compare with the current polled value | RANGE: [0, 18446744073709551615] |
getType | evms:GetTypeType (scalar:Enum8) | The type of SNMP get operation | SELECTION: 0 - none 1 - exact 2 - next DEFAULT: none |
oid | string:Basic | Oid of data element in dot notation | RANGE: [0 , 128] |
pollIntervalMax | scalar:Uint32 | Max Polling time interval | RANGE: [1 , 2147483647] |
pollIntervalMin | scalar:Uint32 | Min Polling time interval | RANGE: [1 , 2147483647] |
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 SNMP Event Specification
Deleting an SNMP Event Specification
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventSnmp": {
"attributes": {
"eventTag": "TagName",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<snmptag-items>
<EventSnmp-list nc:operation="delete">
<eventTag>TagName</eventTag>
</EventSnmp-list>
</snmptag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event snmp tag TagName oid SNMPGetOper get-type exact entry-op ne entry-val 1000 exit-comb or exit-op gt exit-val 2000 exit-time 3000 - 4000 poll-interval 123
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventSnmp | sys/evtmgr/inst/applet-App_1/events/snmptag-TagName |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventSnmp Properties
The following table contains information about the evmsEventSnmp 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 SNMP Event Specification
Configuring an SNMP Event Specification
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventSyslog": {
"attributes": {
"eventTag": "SampleString_123",
"occurences": "61077",
"pattern": "SampleString_123",
"priority": "1",
"timeInterval": "1"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<syslogtag-items>
<EventSyslog-list>
<eventTag>SampleString_123</eventTag>
<occurences>61077</occurences>
<pattern>SampleString_123</pattern>
<priority>1</priority>
<timeInterval>1</timeInterval>
</EventSyslog-list>
</syslogtag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event syslog tag SampleString_123 occurs 61077 period 1 priority 1 pattern "SampleString_123"
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventSyslog | sys/evtmgr/inst/applet-App_1/events/syslogtag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventSyslog Properties
The following table contains information about the evmsEventSyslog 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
occurences | scalar:Uint16 | Number of occurances | RANGE: [1 , 65000] |
pattern | string:Basic | Syslog pattern text of the syslog message | RANGE: [0 , 256] |
priority | evms:PriorityType (scalar:Enum8) | Priority of the syslog message | SELECTION: 0 - 0 1 - 1 2 - 2 3 - 3 4 - 4 5 - 5 6 - 6 7 - 7 8 - alerts 9 - critical 10 - debugging 11 - emergencies 12 - errors 13 - informational 14 - notifications 15 - warnings 16 - none DEFAULT: 7 |
timeInterval | scalar:Uint32 | Time interval in seconds | RANGE: [0 , 4294967295] |
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 SNMP Event Specification
Deleting an SNMP Event Specification
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventSyslog": {
"attributes": {
"eventTag": "SampleString_123",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<syslogtag-items>
<EventSyslog-list nc:operation="delete">
<eventTag>SampleString_123</eventTag>
</EventSyslog-list>
</syslogtag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event syslog tag SampleString_123 occurs 61077 period 1 priority 1 pattern "SampleString_123"
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventSyslog | sys/evtmgr/inst/applet-App_1/events/syslogtag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventSyslog Properties
The following table contains information about the evmsEventSyslog 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 a Syslog Event Specification
Configuring a Syslog Event Specification
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsAction": {
"attributes": {
"actionLabel": "1"
},
"children": [
{
"evmsActionSyslog": {
"attributes": {
"message": "Message_Text",
"priority": "emergencies"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<action-items>
<Action-list>
<actionLabel>1</actionLabel>
<syslog-items>
<message>Message_Text</message>
<priority>emergencies</priority>
</syslog-items>
</Action-list>
</action-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
action 1 syslog priority emergencies msg Message_Text
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsAction | sys/evtmgr/inst/applet-App_1/action-1 |
evmsActionSyslog | sys/evtmgr/inst/applet-App_1/action-1/syslog |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsAction Properties
The following table contains information about the evmsAction 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 |
---|---|---|---|
actionLabel | evms:ActionLabelType (string:Basic) | Specify action label | A sequence of characters |
evmsActionSyslog Properties
The following table contains information about the evmsActionSyslog 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 |
---|---|---|---|
message | string:Basic | Syslog message text | RANGE: [0 , 256] |
priority | string:Basic | Priority of the syslog message | RANGE: [0 , 29] |
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 Syslog Event Specification
Deleting a Syslog Event Specification
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsAction": {
"attributes": {
"actionLabel": "1",
"status": "deleted"
}}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<action-items>
<Action-list nc:operation="delete">
<actionLabel>1</actionLabel>
</Action-list>
</action-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no action 1 syslog priority emergencies msg Message_Text
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsAction | sys/evtmgr/inst/applet-App_1/action-1 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsAction Properties
The following table contains information about the evmsAction 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 |
---|---|---|---|
actionLabel | evms:ActionLabelType (string:Basic) | Specify action label | A sequence of characters |
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 a New CDP Cache Entry Addition (Tagged)
Configuring a New CDP Cache Entry Addition (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventCdp": {
"attributes": {
"cacheEntryOp": "add",
"eventTag": "SampleString_123",
"intf": "eth1/2"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<cdptag-items>
<EventCdp-list>
<eventTag>SampleString_123</eventTag>
<cacheEntryOp>add</cacheEntryOp>
<intf>eth1/2</intf>
</EventCdp-list>
</cdptag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event tag SampleString_123 neighbor-discovery interface ethernet 1/2 cdp add
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventCdp | sys/evtmgr/inst/applet-App_1/events/cdptag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventCdp Properties
The following table contains information about the evmsEventCdp 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 |
---|---|---|---|
cacheEntryOp | evms:CacheEntryOp (scalar:Enum8) | cdp event specification | SELECTION: 1 - all 2 - add 3 - update 4 - delete DEFAULT: all |
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
intf | nw:IfId (base:IfIndex) | interface | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 New CDP Cache Entry Addition (Tagged)
Deleting a New CDP Cache Entry Addition (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventCdp": {
"attributes": {
"eventTag": "SampleString_123",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<cdptag-items>
<EventCdp-list nc:operation="delete">
<eventTag>SampleString_123</eventTag>
</EventCdp-list>
</cdptag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event tag SampleString_123 neighbor-discovery interface ethernet 1/2 cdp add
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventCdp | sys/evtmgr/inst/applet-App_1/events/cdptag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventCdp Properties
The following table contains information about the evmsEventCdp 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 a New CDP Cache Entry Addition (Untagged)
Configuring a New CDP Cache Entry Addition (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventCdpUnTagged": {
"attributes": {
"cacheEntryOp": "add",
"intf": "eth1/2"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<cdp-items>
<cacheEntryOp>add</cacheEntryOp>
<intf>eth1/2</intf>
</cdp-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event neighbor-discovery interface ethernet 1/2 cdp add
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventCdpUnTagged | sys/evtmgr/inst/applet-App_1/events/cdp |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventCdpUnTagged Properties
The following table contains information about the evmsEventCdpUnTagged 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 |
---|---|---|---|
cacheEntryOp | evms:CacheEntryOp (scalar:Enum8) | cdp event specification | SELECTION: 1 - all 2 - add 3 - update 4 - delete DEFAULT: all |
intf | nw:IfId (base:IfIndex) | interface | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 New CDP Cache Entry Addition (Untagged)
Deleting a New CDP Cache Entry Addition (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventCdpUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<cdp-items nc:operation="delete">
</cdp-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event neighbor-discovery interface ethernet 1/2 cdp add
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventCdpUnTagged | sys/evtmgr/inst/applet-App_1/events/cdp |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventCdpUnTagged Properties
The following table contains information about the evmsEventCdpUnTagged 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 CDP Cache Entry Addition, Deletion, or Update (Tagged)
Configuring CDP Cache Entry Addition, Deletion, or Update (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventCdp": {
"attributes": {
"cacheEntryOp": "all",
"eventTag": "SampleString_123",
"intf": "eth1/2"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<cdptag-items>
<EventCdp-list>
<eventTag>SampleString_123</eventTag>
<cacheEntryOp>all</cacheEntryOp>
<intf>eth1/2</intf>
</EventCdp-list>
</cdptag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event tag SampleString_123 neighbor-discovery interface ethernet 1/2 cdp all
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventCdp | sys/evtmgr/inst/applet-App_1/events/cdptag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventCdp Properties
The following table contains information about the evmsEventCdp 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 |
---|---|---|---|
cacheEntryOp | evms:CacheEntryOp (scalar:Enum8) | cdp event specification | SELECTION: 1 - all 2 - add 3 - update 4 - delete DEFAULT: all |
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
intf | nw:IfId (base:IfIndex) | interface | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 CDP Cache Entry Addition, Deletion, or Update (Tagged)
Deleting CDP Cache Entry Addition, Deletion, or Update (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventCdp": {
"attributes": {
"eventTag": "SampleString_123",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<cdptag-items>
<EventCdp-list nc:operation="delete">
<eventTag>SampleString_123</eventTag>
</EventCdp-list>
</cdptag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event tag SampleString_123 neighbor-discovery interface ethernet 1/2 cdp all
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventCdp | sys/evtmgr/inst/applet-App_1/events/cdptag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventCdp Properties
The following table contains information about the evmsEventCdp 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 CDP Cache Entry Addition, Deletion, or Update (Untagged)
Configuring CDP Cache Entry Addition, Deletion, or Update (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventCdpUnTagged": {
"attributes": {
"cacheEntryOp": "all",
"intf": "eth1/2"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<cdp-items>
<cacheEntryOp>all</cacheEntryOp>
<intf>eth1/2</intf>
</cdp-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event neighbor-discovery interface ethernet 1/2 cdp all
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventCdpUnTagged | sys/evtmgr/inst/applet-App_1/events/cdp |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventCdpUnTagged Properties
The following table contains information about the evmsEventCdpUnTagged 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 |
---|---|---|---|
cacheEntryOp | evms:CacheEntryOp (scalar:Enum8) | cdp event specification | SELECTION: 1 - all 2 - add 3 - update 4 - delete DEFAULT: all |
intf | nw:IfId (base:IfIndex) | interface | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 CDP Cache Entry Addition, Deletion, or Update (Untagged)
Deleting CDP Cache Entry Addition, Deletion, or Update (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventCdpUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<cdp-items nc:operation="delete">
</cdp-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event neighbor-discovery interface ethernet 1/2 cdp all
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventCdpUnTagged | sys/evtmgr/inst/applet-App_1/events/cdp |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventCdpUnTagged Properties
The following table contains information about the evmsEventCdpUnTagged 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:
Deleting Existing CDP Cache Entry (Tagged)
Deleting Existing CDP Cache Entry (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventCdp": {
"attributes": {
"cacheEntryOp": "delete",
"eventTag": "SampleString_123",
"intf": "eth1/2"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<cdptag-items>
<EventCdp-list>
<eventTag>SampleString_123</eventTag>
<cacheEntryOp>delete</cacheEntryOp>
<intf>eth1/2</intf>
</EventCdp-list>
</cdptag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event tag SampleString_123 neighbor-discovery interface ethernet 1/2 cdp delete
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventCdp | sys/evtmgr/inst/applet-App_1/events/cdptag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventCdp Properties
The following table contains information about the evmsEventCdp 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 |
---|---|---|---|
cacheEntryOp | evms:CacheEntryOp (scalar:Enum8) | cdp event specification | SELECTION: 1 - all 2 - add 3 - update 4 - delete DEFAULT: all |
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
intf | nw:IfId (base:IfIndex) | interface | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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:
Unconfiguring the Existing CDP Cache Entry Deletion (Tagged)
Unconfiguring the Existing CDP Cache Entry Deletion (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventCdp": {
"attributes": {
"eventTag": "SampleString_123",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<cdptag-items>
<EventCdp-list nc:operation="delete">
<eventTag>SampleString_123</eventTag>
</EventCdp-list>
</cdptag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event tag SampleString_123 neighbor-discovery interface ethernet 1/2 cdp delete
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventCdp | sys/evtmgr/inst/applet-App_1/events/cdptag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventCdp Properties
The following table contains information about the evmsEventCdp 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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:
Deleting Existing CDP Cache Entry (Untagged)
Deleting Existing CDP Cache Entry (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventCdpUnTagged": {
"attributes": {
"cacheEntryOp": "delete",
"intf": "eth1/2"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<cdp-items>
<cacheEntryOp>delete</cacheEntryOp>
<intf>eth1/2</intf>
</cdp-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event neighbor-discovery interface ethernet 1/2 cdp delete
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventCdpUnTagged | sys/evtmgr/inst/applet-App_1/events/cdp |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventCdpUnTagged Properties
The following table contains information about the evmsEventCdpUnTagged 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 |
---|---|---|---|
cacheEntryOp | evms:CacheEntryOp (scalar:Enum8) | cdp event specification | SELECTION: 1 - all 2 - add 3 - update 4 - delete DEFAULT: all |
intf | nw:IfId (base:IfIndex) | interface | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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:
Unconfiguring the Existing CDP Cache Entry Deletion (Untagged)
Unconfiguring the Existing CDP Cache Entry Deletion (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventCdpUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<cdp-items nc:operation="delete">
</cdp-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event neighbor-discovery interface ethernet 1/2 cdp delete
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventCdpUnTagged | sys/evtmgr/inst/applet-App_1/events/cdp |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventCdpUnTagged Properties
The following table contains information about the evmsEventCdpUnTagged 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 a CDP Cache Entry Update (Tagged)
Configuring a CDP Cache Entry Update (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventCdp": {
"attributes": {
"cacheEntryOp": "update",
"eventTag": "SampleString_123",
"intf": "eth1/2"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<cdptag-items>
<EventCdp-list>
<eventTag>SampleString_123</eventTag>
<cacheEntryOp>update</cacheEntryOp>
<intf>eth1/2</intf>
</EventCdp-list>
</cdptag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event tag SampleString_123 neighbor-discovery interface ethernet 1/2 cdp update
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventCdp | sys/evtmgr/inst/applet-App_1/events/cdptag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventCdp Properties
The following table contains information about the evmsEventCdp 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 |
---|---|---|---|
cacheEntryOp | evms:CacheEntryOp (scalar:Enum8) | cdp event specification | SELECTION: 1 - all 2 - add 3 - update 4 - delete DEFAULT: all |
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
intf | nw:IfId (base:IfIndex) | interface | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 CDP Cache Entry Update (Tagged)
Deleting a CDP Cache Entry Update (Tagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventCdp": {
"attributes": {
"eventTag": "SampleString_123",
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<cdptag-items>
<EventCdp-list nc:operation="delete">
<eventTag>SampleString_123</eventTag>
</EventCdp-list>
</cdptag-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event tag SampleString_123 neighbor-discovery interface ethernet 1/2 cdp update
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventCdp | sys/evtmgr/inst/applet-App_1/events/cdptag-SampleString_123 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventCdp Properties
The following table contains information about the evmsEventCdp 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 |
---|---|---|---|
eventTag | evms:EventTagType (string:Basic) | Event tag specifier, uniquely defines an event. | MAX SIZE: 29 DEFAULT: |
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 a CDP Cache Entry Update (Untagged)
Configuring a CDP Cache Entry Update (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventCdpUnTagged": {
"attributes": {
"cacheEntryOp": "update",
"intf": "eth1/2"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<cdp-items>
<cacheEntryOp>update</cacheEntryOp>
<intf>eth1/2</intf>
</cdp-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
event neighbor-discovery interface ethernet 1/2 cdp update
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventCdpUnTagged | sys/evtmgr/inst/applet-App_1/events/cdp |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventCdpUnTagged Properties
The following table contains information about the evmsEventCdpUnTagged 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 |
---|---|---|---|
cacheEntryOp | evms:CacheEntryOp (scalar:Enum8) | cdp event specification | SELECTION: 1 - all 2 - add 3 - update 4 - delete DEFAULT: all |
intf | nw:IfId (base:IfIndex) | interface | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
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 CDP Cache Entry Update (Untagged)
Deleting a CDP Cache Entry Update (Untagged)
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsEvents": {
"children": [
{
"evmsEventCdpUnTagged": {
"attributes": {
"status": "deleted"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<events-items>
<cdp-items nc:operation="delete">
</cdp-items>
</events-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no event neighbor-discovery interface ethernet 1/2 cdp update
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsEvents | sys/evtmgr/inst/applet-App_1/events |
evmsEventCdpUnTagged | sys/evtmgr/inst/applet-App_1/events/cdp |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsEventCdpUnTagged Properties
The following table contains information about the evmsEventCdpUnTagged 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 Debugging Collection Using a YAML File
Configuring Debugging Collection Using a YAML File
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsAction": {
"attributes": {
"actionLabel": "1.0"
},
"children": [
{
"evmsActionCollect": {
"attributes": {
"componentName": "$_syslog_msg",
"purgeTime": "1",
"rateLimit": "1",
"yamlFile": "Sample.yaml",
"yamlStatus": "enabled"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<action-items>
<Action-list>
<actionLabel>1.0</actionLabel>
<collect-items>
<componentName>$_syslog_msg</componentName>
<purgeTime>0</purgeTime>
<rateLimit>1</rateLimit>
<yamlFile>Sample.yaml</yamlFile>
<yamlStatus>enabled</yamlStatus>
</collect-items>
</Action-list>
</action-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
action 1.0 collect Sample.yaml rate-limit 1 $_syslog_msg
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsAction | sys/evtmgr/inst/applet-App_1/action-1.0 |
evmsActionCollect | sys/evtmgr/inst/applet-App_1/action-1.0/collect |
evmsAction Properties
The following table contains information about the evmsAction 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 |
---|---|---|---|
actionLabel | evms:ActionLabelType (string:Basic) | Specify action label | A sequence of characters |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsActionCollect Properties
The following table contains information about the evmsActionCollect 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 |
---|---|---|---|
componentName | string:Basic | Enter the component for tech-support collection | RANGE: [0 , 1023] |
purgeTime | scalar:Uint16 | Change the time period for which older files are purged | RANGE: [1 , 65000] |
rateLimit | scalar:Uint16 | Limit trigger based collection for a period of time | RANGE: [1 , 65000] |
yamlFile | string:Basic | Enter the YAML input file | RANGE: [0 , 1023] |
yamlStatus | nw:AdminSt (scalar:Enum8) | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
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 Debugging Collection Using a YAML File
Deleting Debugging Collection Using a YAML File
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsAction": {
"attributes": {
"actionLabel": "1.0",
"status": "deleted"
}}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<action-items>
<Action-list nc:operation="delete">
<actionLabel>1.0</actionLabel>
</Action-list>
</action-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no action 1.0 collect Sample.yaml rate-limit 1 $_syslog_msg
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsAction | sys/evtmgr/inst/applet-App_1/action-1.0 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsAction Properties
The following table contains information about the evmsAction 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 |
---|---|---|---|
actionLabel | evms:ActionLabelType (string:Basic) | Specify action label | A sequence of characters |
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 the Timer Period for which Older Files are Purged
Configuring the Timer Period for which Older Files are Purged
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsAction": {
"attributes": {
"actionLabel": "1.0"
},
"children": [
{
"evmsActionCollect": {
"attributes": {
"componentName": "$_syslog_msg",
"purgeTime": "1",
"rateLimit": "1",
"yamlFile": "Sample.yaml",
"yamlStatus": "enabled"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<action-items>
<Action-list>
<actionLabel>1.0</actionLabel>
<collect-items>
<componentName>$_syslog_msg</componentName>
<purgeTime>1</purgeTime>
<rateLimit>0</rateLimit>
<yamlFile>Sample.yaml</yamlFile>
<yamlStatus>enabled</yamlStatus>
</collect-items>
</Action-list>
</action-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note:
- Purge time is in minutes.
- This example was added in Release 9.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.
event manager applet App_1
action 1.0 collect Sample.yaml purge-time 1 $_syslog_msg
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsAction | sys/evtmgr/inst/applet-App_1/action-1.0 |
evmsActionCollect | sys/evtmgr/inst/applet-App_1/action-1.0/collect |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsAction Properties
The following table contains information about the evmsAction 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 |
---|---|---|---|
actionLabel | evms:ActionLabelType (string:Basic) | Specify action label | A sequence of characters |
evmsActionCollect Properties
The following table contains information about the evmsActionCollect 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 |
---|---|---|---|
componentName | string:Basic | Enter the component for tech-support collection | RANGE: [0 , 1023] |
purgeTime | scalar:Uint16 | Change the time period for which older files are purged | RANGE: [1 , 65000] |
rateLimit | scalar:Uint16 | Limit trigger based collection for a period of time | RANGE: [1 , 65000] |
yamlFile | string:Basic | Enter the YAML input file | RANGE: [0 , 1023] |
yamlStatus | nw:AdminSt (scalar:Enum8) | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
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 Timer Period for which Older Files are Purged
Deleting the Timer Period for which Older Files are Purged
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsAction": {
"attributes": {
"actionLabel": "1.0",
"status": "deleted"
}}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<action-items>
<Action-list nc:operation="delete">
<actionLabel>1.0</actionLabel>
</Action-list>
</action-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no action 1.0 collect Sample.yaml purge-time 1 $_syslog_msg
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsAction | sys/evtmgr/inst/applet-App_1/action-1.0 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsAction Properties
The following table contains information about the evmsAction 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 |
---|---|---|---|
actionLabel | evms:ActionLabelType (string:Basic) | Specify action label | A sequence of characters |
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:
Disabling the Trigger-Based Collection
Disabling the Trigger-Based Collection
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsAction": {
"attributes": {
"actionLabel": "1.0"
},
"children": [
{
"evmsActionCollect": {
"attributes": {
"componentName": "",
"purgeTime": "1",
"rateLimit": "1",
"yamlFile": "",
"yamlStatus": "disabled"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<action-items>
<Action-list>
<actionLabel>1.0</actionLabel>
<collect-items>
<componentName></componentName>
<purgeTime>0</purgeTime>
<rateLimit>0</rateLimit>
<yamlFile></yamlFile>
<yamlStatus>disabled</yamlStatus>
</collect-items>
</Action-list>
</action-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
action 1.0 collect disable
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsAction | sys/evtmgr/inst/applet-App_1/action-1.0 |
evmsActionCollect | sys/evtmgr/inst/applet-App_1/action-1.0/collect |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsAction Properties
The following table contains information about the evmsAction 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 |
---|---|---|---|
actionLabel | evms:ActionLabelType (string:Basic) | Specify action label | A sequence of characters |
evmsActionCollect Properties
The following table contains information about the evmsActionCollect 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 |
---|---|---|---|
componentName | string:Basic | Enter the component for tech-support collection | RANGE: [0 , 1023] |
purgeTime | scalar:Uint16 | Change the time period for which older files are purged | RANGE: [1 , 65000] |
rateLimit | scalar:Uint16 | Limit trigger based collection for a period of time | RANGE: [1 , 65000] |
yamlFile | string:Basic | Enter the YAML input file | RANGE: [0 , 1023] |
yamlStatus | nw:AdminSt (scalar:Enum8) | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
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:
Unconfiguring the Disabled Trigger-Based Collection
Unconfiguring the Disabled Trigger-Based Collection
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsAction": {
"attributes": {
"actionLabel": "1.0",
"status": "deleted"
}}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<action-items>
<Action-list nc:operation="delete">
<actionLabel>1.0</actionLabel>
</Action-list>
</action-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no action 1.0 collect disable
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsAction | sys/evtmgr/inst/applet-App_1/action-1.0 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsAction Properties
The following table contains information about the evmsAction 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 |
---|---|---|---|
actionLabel | evms:ActionLabelType (string:Basic) | Specify action label | A sequence of characters |
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 Debugging Collection Using a YAML File and the Timer Period for which Older Files are Purged
Configuring Debugging Collection Using a YAML File and the Timer Period for which Older Files are Purged
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsAction": {
"attributes": {
"actionLabel": "1.0"
},
"children": [
{
"evmsActionCollect": {
"attributes": {
"componentName": "$_syslog_msg",
"purgeTime": "1",
"rateLimit": "1",
"yamlFile": "sample.yaml",
"yamlStatus": "enabled"
}}}]}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<action-items>
<Action-list>
<actionLabel>1.0</actionLabel>
<collect-items>
<componentName>$_syslog_msg</componentName>
<purgeTime>1</purgeTime>
<rateLimit>1</rateLimit>
<yamlFile>sample.yaml</yamlFile>
<yamlStatus>enabled</yamlStatus>
</collect-items>
</Action-list>
</action-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
action 1.0 collect sample.yaml rate-limit 1 purge-time 1 $_syslog_msg
WARNING: Yaml file not found in bootflash:scripts directory
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsAction | sys/evtmgr/inst/applet-App_1/action-1.0 |
evmsActionCollect | sys/evtmgr/inst/applet-App_1/action-1.0/collect |
evmsAction Properties
The following table contains information about the evmsAction 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 |
---|---|---|---|
actionLabel | evms:ActionLabelType (string:Basic) | Specify action label | A sequence of characters |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsActionCollect Properties
The following table contains information about the evmsActionCollect 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 |
---|---|---|---|
componentName | string:Basic | Enter the component for tech-support collection | RANGE: [0 , 1023] |
purgeTime | scalar:Uint16 | Change the time period for which older files are purged | RANGE: [1 , 65000] |
rateLimit | scalar:Uint16 | Limit trigger based collection for a period of time | RANGE: [1 , 65000] |
yamlFile | string:Basic | Enter the YAML input file | RANGE: [0 , 1023] |
yamlStatus | nw:AdminSt (scalar:Enum8) | SELECTION: 1 - enabled 2 - disabled DEFAULT: enabled |
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 Debugging Collection Using a YAML File and the Timer Period for which Older Files are Purged
Configuring Debugging Collection Using a YAML File and the Timer Period for which Older Files are Purged
POST http://<mgmt0_IP>/api/mo/sys/evtmgr/inst.json
{
"evmsInst": {
"children": [
{
"evmsApplet": {
"attributes": {
"appletName": "App_1"
},
"children": [
{
"evmsAction": {
"attributes": {
"actionLabel": "1.0",
"status": "deleted"
}}}]}}]}}
{
imdata:[]
}
<System>
<evtmgr-items>
<inst-items>
<applet-items>
<Applet-list>
<appletName>App_1</appletName>
<action-items>
<Action-list nc:operation="delete">
<actionLabel>1.0</actionLabel>
</Action-list>
</action-items>
</Applet-list>
</applet-items>
</inst-items>
</evtmgr-items>
</System>
Note: This example was added in Release 9.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.
event manager applet App_1
no action 1.0 collect sample.yaml rate-limit 1 purge-time 1 $_syslog_msg
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 |
---|---|
evmsInst | sys/evtmgr/inst |
evmsApplet | sys/evtmgr/inst/applet-App_1 |
evmsAction | sys/evtmgr/inst/applet-App_1/action-1.0 |
evmsApplet Properties
The following table contains information about the evmsApplet 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 |
---|---|---|---|
appletName | string:Basic | Name of the policy | RANGE: [1 , 29] |
evmsAction Properties
The following table contains information about the evmsAction 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 |
---|---|---|---|
actionLabel | evms:ActionLabelType (string:Basic) | Specify action label | A sequence of characters |
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: