Equipment Diagnostics
Diagnostic Actions
Diagnostic Actions
POST http://<mgmt0_IP>/api/mo/sys/action.json
{
"actionLSubj": {
"attributes": {
"dn": "sys/action/lsubj-[sys/diag/rule-[type]-trig-[trig]/subj-[oDn]]"
}
"children" : [{
"eqptdiagSubjTestLTask" : {
"attributes" : {
"adminSt" : "start",
"dn" : "sys/action/lsubj-[sys/diag/rule-[type]-trig-[trig]/subj-[oDn]]/eqptdiagSubjTestLTask",
"freq": "one-shot"
}
}
}]
}
}
{
"imdata": []
}
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. The command options include the following:
diagnostic ?
clear Erase Diagnostic Test Results/Stats
ondemand On demand diagnostic setting
start Starting on demand diagnostic
stop Stopping diagnostic
test Diagnostic test selection
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
actionLSubj | sys/action/lsubj-{[oDn]} |
actionLSubj Properties
The following table contains information about the actionLSubj properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
dn | reference:BinRef | A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module. |
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:
Managing the Equipment
Locating the Chassis
Locating the Chassis
POST http://<mgmt0_IP>/api/mo/sys/action.json
{
"actionLSubj": {
"attributes": {
"dn": "sys/action/lsubj-[sys/ch]"
}
"children" : [{
"eqptChLocateLTask" : {
"attributes" : {
"adminSt" : "start",
"dn" : "sys/action/lsubj-[sys/ch]/eqptChLocateLTask",
"freq": "one-shot"
}
}
}]
}
}
{
"imdata": []
}
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
locator-led module <mod-num>
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
actionLSubj | sys/action/lsubj-{[oDn]} |
actionLSubj Properties
The following table contains information about the actionLSubj properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
dn | reference:BinRef | A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module. |
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:
Locating the Fan Tray
Locating the Fan Tray
POST http://<mgmt0_IP>/api/mo/sys/action.json
{
"actionLSubj": {
"attributes": {
"dn": "sys/action/lsubj-[sys/ch/ftslot-1/ft]"
}
"children" : [{
"eqptFtLocateLTask" : {
"attributes" : {
"adminSt" : "start",
"dn" : "sys/action/lsubj-[sys/ch/ftslot-1/ft]/eqptFtLocateLTask",
"freq": "one-shot"
}
}
}]
}
}
{
"imdata": []
}
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
locator-led fan 1
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
actionLSubj | sys/action/lsubj-{[oDn]} |
actionLSubj Properties
The following table contains information about the actionLSubj properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
dn | reference:BinRef | A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module. |
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:
Locating the Linecard
Locating the Linecard
POST http://<mgmt0_IP>/api/mo/sys/action.json
{
"actionLSubj": {
"attributes": {
"dn": "sys/action/lsubj-[sys/ch/lcslot-1/lc]"
}
"children" : [{
"eqptLCLocateLTask" : {
"attributes" : {
"adminSt" : "start",
"dn" : "sys/action/lsubj-[sys/ch/lcslot-1/lc]/eqptLCLocateLTask",
"freq": "one-shot"
}
}
}]
}
}
{
"imdata": []
}
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
locator-led module 1
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
actionLSubj | sys/action/lsubj-{[oDn]} |
actionLSubj Properties
The following table contains information about the actionLSubj properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
dn | reference:BinRef | A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module. |
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:
Locating the System Controller
Locating the System Controller
POST http://<mgmt0_IP>/api/mo/sys/action.json
{
"actionLSubj": {
"attributes": {
"dn": "sys/action/lsubj-[sys/ch/scslot-1/sc]"
}
"children" : [{
"eqptSysCLocateLTask" : {
"attributes" : {
"adminSt" : "start",
"dn" : "sys/action/lsubj-[sys/ch/scslot-1/sc]/eqptSysCLocateLTask",
"freq": "one-shot"
}
}
}]
}
}
{
"imdata": []
}
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
locator-led module 1
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
actionLSubj | sys/action/lsubj-{[oDn]} |
actionLSubj Properties
The following table contains information about the actionLSubj properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
dn | reference:BinRef | A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module. |
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:
Locating the Extended Chassis
Locating the Extended Chassis
POST http://<mgmt0_IP>/api/mo/sys/action.json
{
"actionLSubj": {
"attributes": {
"dn": "sys/action/lsubj-[sys/extch-101]"
}
"children" : [{
"eqptExtChLocateLTask" : {
"attributes" : {
"adminSt" : "start",
"dn" : "sys/action/lsubj-[sys/extch-101]/eqptExtChLocateLTask",
"freq": "one-shot"
}
}
}]
}
}
{
"imdata": []
}
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
locator-led fex 101
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
actionLSubj | sys/action/lsubj-{[oDn]} |
actionLSubj Properties
The following table contains information about the actionLSubj properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
dn | reference:BinRef | A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module. |
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:
Locating the FC
Locating the FC
POST http://<mgmt0_IP>/api/mo/sys/action.json
{
"actionLSubj": {
"attributes": {
"dn": "sys/action/lsubj-[sys/ch/fcslot-1/fc]"
}
"children" : [{
"eqptFCLocateLTask" : {
"attributes" : {
"adminSt" : "start",
"dn" : "sys/action/lsubj-[sys/ch/fcslot-1/fc]/eqptFCLocateLTask",
"freq": "one-shot"
}
}
}]
}
}
{
"imdata": []
}
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
locator-led module 1
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
actionLSubj | sys/action/lsubj-{[oDn]} |
actionLSubj Properties
The following table contains information about the actionLSubj properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
dn | reference:BinRef | A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module. |
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:
Locating the Supervisor Card
Locating the Supervisor Card
POST http://<mgmt0_IP>/api/mo/sys/action.json
{
"actionLSubj": {
"attributes": {
"dn": "sys/action/lsubj-[sys/ch/supslot-1/sup]"
}
"children" : [{
"eqptSupCLocateLTask" : {
"attributes" : {
"adminSt" : "start",
"dn" : "sys/action/lsubj-[sys/ch/supslot-1/sup]/eqptSupCLocateLTask",
"freq": "one-shot"
}
}
}]
}
}
{
"imdata": []
}
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
locator-led module 1
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
actionLSubj | sys/action/lsubj-{[oDn]} |
actionLSubj Properties
The following table contains information about the actionLSubj properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
dn | reference:BinRef | A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module. |
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:
Reloading the Linecard
Reloading the Linecard
POST http://<mgmt0_IP>/api/mo/sys/action.json
{
"actionLSubj": {
"attributes": {
"dn": "sys/action/lsubj-[sys/ch/lcslot-1/lc]"
}
"children" : [{
"eqptLCReloadLTask" : {
"attributes" : {
"adminSt" : "start",
"dn" : "sys/action/lsubj-[sys/ch/lcslot-1/lc]/eqptLCReloadLTask",
"freq": "one-shot"
}
}
}]
}
}
{
"imdata": []
}
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
reload module <mod>
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
actionLSubj | sys/action/lsubj-{[oDn]} |
actionLSubj Properties
The following table contains information about the actionLSubj properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
dn | reference:BinRef | A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module. |
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:
Reloading the FC
Reloading the FC
POST http://<mgmt0_IP>/api/mo/sys/action.json
{
"actionLSubj": {
"attributes": {
"dn": "sys/action/lsubj-[sys/ch/fcslot-1/fc]"
}
"children" : [{
"eqptFCReloadLTask" : {
"attributes" : {
"adminSt" : "start",
"dn" : "sys/action/lsubj-[sys/ch/fcslot-1/fc]/eqptFCReloadLTask",
"freq": "one-shot"
}
}
}]
}
}
{
"imdata": []
}
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
reload module <mod>
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
actionLSubj | sys/action/lsubj-{[oDn]} |
actionLSubj Properties
The following table contains information about the actionLSubj properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
dn | reference:BinRef | A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module. |
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:
Reloading the System Controller
Reloading the System Controller
POST http://<mgmt0_IP>/api/mo/sys/action.json
{
"actionLSubj": {
"attributes": {
"dn": "sys/action/lsubj-[sys/ch/scslot-1/sc]"
}
"children" : [{
"eqptSysCReloadLTask" : {
"attributes" : {
"adminSt" : "start",
"dn" : "sys/action/lsubj-[sys/ch/scslot-1/sc]/eqptSysCReloadLTask",
"freq": "one-shot"
}
}
}]
}
}
{
"imdata": []
}
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
reload module <mod>
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
actionLSubj | sys/action/lsubj-{[oDn]} |
actionLSubj Properties
The following table contains information about the actionLSubj properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
dn | reference:BinRef | A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module. |
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:
Reloading the Chassis
Reloading the Chassis
POST http://<mgmt0_IP>/api/mo/sys/action.json
{
"actionLSubj": {
"attributes": {
"dn": "sys/action/lsubj-[sys/ch]"
}
"children" : [{
"eqptChReloadLTask" : {
"attributes" : {
"adminSt" : "start",
"dn" : "sys/action/lsubj-[sys/ch]/eqptChReloadLTask",
"freq": "one-shot"
}
}
}]
}
}
{
"imdata": []
}
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
reload module <mod>
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
actionLSubj | sys/action/lsubj-{[oDn]} |
actionLSubj Properties
The following table contains information about the actionLSubj properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
dn | reference:BinRef | A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module. |
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:
Reloading the Supervisor Card
Reloading the Supervisor Card
POST http://<mgmt0_IP>/api/mo/sys/action.json
{
"actionLSubj": {
"attributes": {
"dn": "sys/action/lsubj-[sys/ch/supslot-1/sup]"
}
"children" : [{
"eqptSupCReloadLTask" : {
"attributes" : {
"adminSt" : "start",
"dn" : "sys/action/lsubj-[sys/ch/supslot-1/sup]/eqptSupCReloadLTask",
"freq": "one-shot"
}
}
}]
}
}
{
"imdata": []
}
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
reload module <mod>
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
actionLSubj | sys/action/lsubj-{[oDn]} |
actionLSubj Properties
The following table contains information about the actionLSubj properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
dn | reference:BinRef | A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module. |
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:
Reloading the Extended Chassis
Reloading the Extended Chassis
POST http://<mgmt0_IP>/api/mo/sys/action.json
{
"actionLSubj": {
"attributes": {
"dn": "sys/action/lsubj-[sys/extch-101]"
}
"children" : [{
"eqptExtChReloadLTask" : {
"attributes" : {
"adminSt" : "start",
"dn" : "sys/action/lsubj-[sys/extch-101]/eqptExtChReloadLTask",
"freq": "one-shot"
}
}
}]
}
}
{
"imdata": []
}
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
reload fex 101
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
actionLSubj | sys/action/lsubj-{[oDn]} |
actionLSubj Properties
The following table contains information about the actionLSubj properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
dn | reference:BinRef | A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module. |
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: