Configuring Hardware Ejector
Configuring the Card Functionality so that the Card Powers Down when Both Ejectors are Open
Configuring the Card Functionality so that the Card Powers Down when Both Ejectors are Open
POST http://<mgmt0_IP>/api/mo/sys/ops.json
{
"eqptEntity": {
"children": [
{
"eqptEjector": {
"attributes": {
"autoShutdown": "enabled"
}}}]}}
{
imdata:[]
}
<System>
<ops-items>
<ejector-items>
<autoShutdown>enabled</autoShutdown>
</ejector-items>
</ops-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.
hardware ejector enable
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 |
---|---|
eqptEntity | sys/ops |
eqptEjector | sys/ops/ejector |
eqptEjector Properties
The following table contains information about the eqptEjector properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
autoShutdown | eqpt:AutoShutdown (scalar:Enum8) | Auto Shutdown on Ejector Open | SELECTION: 0 - disabled 1 - enabled 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 Card Functionality so that the Card Powers Down when Both Ejectors are Open
Deleting the Card Functionality so that the Card Powers Down when Both Ejectors are Open
POST http://<mgmt0_IP>/api/mo/sys/ops.json
{
"eqptEntity": {
"children": [
{
"eqptEjector": {
"attributes": {
"autoShutdown": "disabled"
}}}]}}
{
imdata:[]
}
<System>
<ops-items>
<ejector-items>
<autoShutdown>disabled</autoShutdown>
</ejector-items>
</ops-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 hardware ejector enable
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 |
---|---|
eqptEntity | sys/ops |
eqptEjector | sys/ops/ejector |
eqptEjector Properties
The following table contains information about the eqptEjector properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
autoShutdown | eqpt:AutoShutdown (scalar:Enum8) | Auto Shutdown on Ejector Open | SELECTION: 0 - disabled 1 - enabled 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: