Configuring a System Module Action
Configuring Shutdown as the Module Action on Failure
Configuring Shutdown as the Module Action on Failure
POST http://<mgmt0_IP>/api/mo/sys/lcm.json
{
"lcmEntity": {
"children": [
{
"lcmSysMod": {
"attributes": {
"moduleFailureAction": "shutdown"
}}}]}}
```0
```[DME]json-Response
{
imdata:[]
}
<System>
<lcm-items>
<sysmod-items>
<moduleFailureAction>shutdown</moduleFailureAction>
</sysmod-items>
</lcm-items>
</System>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
system module failure-action shutdown
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue 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 |
---|---|
lcmEntity | sys/lcm |
lcmSysMod | sys/lcm/sysmod |
lcmSysMod Properties
The following table contains information about the lcmSysMod properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
moduleFailureAction | lcm:ModuleFailureAction (scalar:Enum8) | Configure module action on failure | SELECTION: 0 - no 1 - shutdown DEFAULT: no |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting Shutdown as the Module Action on Failure
Deleting Shutdown as the Module Action on Failure
POST http://<mgmt0_IP>/api/mo/sys/lcm.json
{
"lcmEntity": {
"children": [
{
"lcmSysMod": {
"attributes": {
"moduleFailureAction": "no"
}}}]}}
{
imdata:[]
}
<System>
<lcm-items>
<sysmod-items>
<moduleFailureAction>no</moduleFailureAction>
</sysmod-items>
</lcm-items>
</System>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
no system module failure-action shutdown
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue 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 |
---|---|
lcmEntity | sys/lcm |
lcmSysMod | sys/lcm/sysmod |
lcmSysMod Properties
The following table contains information about the lcmSysMod properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
moduleFailureAction | lcm:ModuleFailureAction (scalar:Enum8) | Configure module action on failure | SELECTION: 0 - no 1 - shutdown DEFAULT: no |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring Emon Enhanced Support
Configuring Emon Enhanced Support
POST http://<mgmt0_IP>/api/mo/sys/lcm.json
{
"lcmEntity": {
"children": [
{
"lcmSysMod": {
"attributes": {
"moduleEmonEnhanced": "enable"
}}}]}}
{
imdata:[]
}
<System>
<lcm-items>
<sysmod-items>
<moduleEmonEnhanced>enable</moduleEmonEnhanced>
</sysmod-items>
</lcm-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.
system module emon-enhanced
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue 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 |
---|---|
lcmEntity | sys/lcm |
lcmSysMod | sys/lcm/sysmod |
lcmSysMod Properties
The following table contains information about the lcmSysMod properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
moduleEmonEnhanced | lcm:ModuleEmonEnhanced (scalar:Enum8) | Configure module emon enhanced status | SELECTION: 0 - disable 1 - enable DEFAULT: enable |
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 Emon Enhanced Support
Deleting Emon Enhanced Support
POST http://<mgmt0_IP>/api/mo/sys/lcm.json
{
"lcmEntity": {
"children": [
{
"lcmSysMod": {
"attributes": {
"moduleEmonEnhanced": "disable"
}}}]}}
{
imdata:[]
}
<System>
<lcm-items>
<sysmod-items>
<moduleEmonEnhanced>disable</moduleEmonEnhanced>
</sysmod-items>
</lcm-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 system module emon-enhanced
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue 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 |
---|---|
lcmEntity | sys/lcm |
lcmSysMod | sys/lcm/sysmod |
lcmSysMod Properties
The following table contains information about the lcmSysMod properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
moduleEmonEnhanced | lcm:ModuleEmonEnhanced (scalar:Enum8) | Configure module emon enhanced status | SELECTION: 0 - disable 1 - enable DEFAULT: enable |
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 Emon Enhanced Slow Timeout
Configuring Emon Enhanced Slow Timeout
POST http://<mgmt0_IP>/api/mo/sys/lcm.json
{
"topSystem": {
"children": [
{
"lcmEntity": {
"children": [
{
"lcmSysMod": {
"attributes": {
"moduleEmonEnhancedSlowTimeout": "enable"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<lcm-items>
<sysmod-items>
<moduleEmonEnhancedSlowTimeout>enable</moduleEmonEnhancedSlowTimeout>
</sysmod-items>
</lcm-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.
system module emon-enhanced slow-timeout
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue 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 |
---|---|
lcmEntity | sys/lcm |
lcmSysMod | sys/lcm/sysmod |
lcmSysMod Properties
The following table contains information about the lcmSysMod properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
moduleEmonEnhanced | lcm:ModuleEmonEnhanced (scalar:Enum8) | Configure module emon enhanced status | SELECTION: 0 - disable 1 - enable DEFAULT: enable |
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 Ethernet Port
Configuring an Ethernet Port
POST http://<mgmt0_IP>/api/mo/sys/lcm/slotcfg.json
{
"lcmSlotCfgEntity": {
"children": [
{
"lcmSlotInst": {
"attributes": {
"id": "1"
},
"children": [
{
"lcmPortCfg": {
"attributes": {
"portRange": "61",
"portType": "ethernet"
}}}]}}]}}
{
imdata:[]
}
<System>
<lcm-items>
<slotcfg-items>
<slot-items>
<SlotInst-list>
<id>1</id>
<portcfg-items>
<portRange>61</portRange>
<portType>ethernet</portType>
</portcfg-items>
</SlotInst-list>
</slot-items>
</slotcfg-items>
</lcm-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.
slot 1
port 61 type ethernet
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue 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 |
---|---|
lcmSlotCfgEntity | sys/lcm/slotcfg |
lcmSlotInst | sys/lcm/slotcfg/slot-1 |
lcmPortCfg | sys/lcm/slotcfg/slot-1/portcfg |
lcmSlotInst Properties
The following table contains information about the lcmSlotInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | lcm:moduleNumber (scalar:Uint16) | Module identifier for Slot property | RANGE: [1 , 32] DEFAULT: 1 |
lcmPortCfg Properties
The following table contains information about the lcmPortCfg properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
portRange | lcm:PortRange (string:Basic) | port range to config port type | A sequence of characters DEFAULT: 1-54 |
portType | lcm:PortType (scalar:Enum8) | port type to config [ethernet/fc\] | SELECTION: 1 - fc 2 - ethernet DEFAULT: ethernet |
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 Ethernet Port
Deleting an Ethernet Port
POST http://<mgmt0_IP>/api/mo/sys/lcm/slotcfg.json
{
"lcmSlotCfgEntity": {
"children": [
{
"lcmSlotInst": {
"attributes": {
"id": "1"
},
"children": [
{
"lcmPortCfg": {
"attributes": {
"portRange": "61",
"portType": "fc"
}}}]}}]}}
{
imdata:[]
}
<System>
<lcm-items>
<slotcfg-items>
<slot-items>
<SlotInst-list>
<id>1</id>
<portcfg-items>
<portRange>61</portRange>
<portType>fc</portType>
</portcfg-items>
</SlotInst-list>
</slot-items>
</slotcfg-items>
</lcm-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.
slot 1
no port 61 type ethernet
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue 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 |
---|---|
lcmSlotCfgEntity | sys/lcm/slotcfg |
lcmSlotInst | sys/lcm/slotcfg/slot-1 |
lcmPortCfg | sys/lcm/slotcfg/slot-1/portcfg |
lcmSlotInst Properties
The following table contains information about the lcmSlotInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | lcm:moduleNumber (scalar:Uint16) | Module identifier for Slot property | RANGE: [1 , 32] DEFAULT: 1 |
lcmPortCfg Properties
The following table contains information about the lcmPortCfg properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
portRange | lcm:PortRange (string:Basic) | port range to config port type | A sequence of characters DEFAULT: 1-54 |
portType | lcm:PortType (scalar:Enum8) | port type to config [ethernet/fc\] | SELECTION: 1 - fc 2 - ethernet DEFAULT: ethernet |
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 FC Port
Configuring an FC Port
POST http://<mgmt0_IP>/api/mo/sys/lcm/slotcfg.json
{
"lcmSlotCfgEntity": {
"children": [
{
"lcmSlotInst": {
"attributes": {
"id": "1"
},
"children": [
{
"lcmPortCfg": {
"attributes": {
"portRange": "61",
"portType": "fc"
}}}]}}]}}
{
imdata:[]
}
<System>
<lcm-items>
<slotcfg-items>
<slot-items>
<SlotInst-list>
<id>1</id>
<portcfg-items>
<portRange>61</portRange>
<portType>fc</portType>
</portcfg-items>
</SlotInst-list>
</slot-items>
</slotcfg-items>
</lcm-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.
slot 1
port 61 type fc
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue 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 |
---|---|
lcmSlotCfgEntity | sys/lcm/slotcfg |
lcmSlotInst | sys/lcm/slotcfg/slot-1 |
lcmPortCfg | sys/lcm/slotcfg/slot-1/portcfg |
lcmSlotInst Properties
The following table contains information about the lcmSlotInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | lcm:moduleNumber (scalar:Uint16) | Module identifier for Slot property | RANGE: [1 , 32] DEFAULT: 1 |
lcmPortCfg Properties
The following table contains information about the lcmPortCfg properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
portRange | lcm:PortRange (string:Basic) | port range to config port type | A sequence of characters DEFAULT: 1-54 |
portType | lcm:PortType (scalar:Enum8) | port type to config [ethernet/fc\] | SELECTION: 1 - fc 2 - ethernet DEFAULT: ethernet |
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 and FC Port
Deleting and FC Port
POST http://<mgmt0_IP>/api/mo/sys/lcm/slotcfg.json
{
"lcmSlotCfgEntity": {
"children": [
{
"lcmSlotInst": {
"attributes": {
"id": "1"
},
"children": [
{
"lcmPortCfg": {
"attributes": {
"portRange": "61",
"portType": "ethernet"
}}}]}}]}}
{
imdata:[]
}
<System>
<lcm-items>
<slotcfg-items>
<slot-items>
<SlotInst-list>
<id>1</id>
<portcfg-items>
<portRange>61</portRange>
<portType>ethernet</portType>
</portcfg-items>
</SlotInst-list>
</slot-items>
</slotcfg-items>
</lcm-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.
slot 1
no port 61 type fc
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue 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 |
---|---|
lcmSlotCfgEntity | sys/lcm/slotcfg |
lcmSlotInst | sys/lcm/slotcfg/slot-1 |
lcmPortCfg | sys/lcm/slotcfg/slot-1/portcfg |
lcmSlotInst Properties
The following table contains information about the lcmSlotInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | lcm:moduleNumber (scalar:Uint16) | Module identifier for Slot property | RANGE: [1 , 32] DEFAULT: 1 |
lcmPortCfg Properties
The following table contains information about the lcmPortCfg properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
portRange | lcm:PortRange (string:Basic) | port range to config port type | A sequence of characters DEFAULT: 1-54 |
portType | lcm:PortType (scalar:Enum8) | port type to config [ethernet/fc\] | SELECTION: 1 - fc 2 - ethernet DEFAULT: ethernet |
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: