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.

MODN
lcmEntitysys/lcm
lcmSysModsys/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 NameData TypeDescriptionValues
moduleFailureActionlcm:ModuleFailureAction
(scalar:Enum8)
Configure module action on failureSELECTION:
0 - no
1 - shutdown
DEFAULT: no


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

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:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

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.

MODN
lcmEntitysys/lcm
lcmSysModsys/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 NameData TypeDescriptionValues
moduleFailureActionlcm:ModuleFailureAction
(scalar:Enum8)
Configure module action on failureSELECTION:
0 - no
1 - shutdown
DEFAULT: no


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

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:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

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.

MODN
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 NameData TypeDescriptionValues
moduleEmonEnhancedlcm:ModuleEmonEnhanced
(scalar:Enum8)
Configure module emon enhanced statusSELECTION:
0 - disable
1 - enable
DEFAULT: enable


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting 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.

MODN
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 NameData TypeDescriptionValues
moduleEmonEnhancedlcm:ModuleEmonEnhanced
(scalar:Enum8)
Configure module emon enhanced statusSELECTION:
0 - disable
1 - enable
DEFAULT: enable


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring 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.

MODN
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 NameData TypeDescriptionValues
moduleEmonEnhancedlcm:ModuleEmonEnhanced
(scalar:Enum8)
Configure module emon enhanced statusSELECTION:
0 - disable
1 - enable
DEFAULT: enable


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring 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.

MODN
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 NameData TypeDescriptionValues
idlcm: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 NameData TypeDescriptionValues
portRangelcm:PortRange
(string:Basic)
port range to config port typeA sequence of characters
DEFAULT: 1-54
portTypelcm: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:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting 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.

MODN
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 NameData TypeDescriptionValues
idlcm: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 NameData TypeDescriptionValues
portRangelcm:PortRange
(string:Basic)
port range to config port typeA sequence of characters
DEFAULT: 1-54
portTypelcm: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:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring 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.

MODN
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 NameData TypeDescriptionValues
idlcm: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 NameData TypeDescriptionValues
portRangelcm:PortRange
(string:Basic)
port range to config port typeA sequence of characters
DEFAULT: 1-54
portTypelcm: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:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting 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.

MODN
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 NameData TypeDescriptionValues
idlcm: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 NameData TypeDescriptionValues
portRangelcm:PortRange
(string:Basic)
port range to config port typeA sequence of characters
DEFAULT: 1-54
portTypelcm: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:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html