Commands for managing a node remotely
You can manage a node remotely by accessing its SP and running SP CLI commands to perform node-management tasks. For several commonly performed remote node-management tasks, you can also use ONTAP commands from another node in the cluster. Some SP commands are platform-specific and might not be available on your platform.
If you want to… | Use this SP command… | Use this BMC command… | Or this ONTAP command … | |
---|---|---|---|---|
Display available SP commands or subcommands of a specified SP command |
|
|||
Display the current privilege level for the SP CLI |
|
|||
Set the privilege level to access the specified mode for the SP CLI |
|
|||
Display system date and time |
|
|
||
Display events that are logged by the SP |
|
|||
Display SP status and network configuration information |
The |
The |
|
|
Display the length of time the SP has been up and the average number of jobs in the run queue over the last 1, 5, and 15 minutes |
|
|
||
Display system console logs |
|
|||
Display the SP log archives or the files in an archive |
|
|
||
Display the power status for the controller of a node |
|
|
||
Display battery information |
|
|||
Display ACP information or the status for expander sensors |
|
|||
List all system FRUs and their IDs |
|
|||
Display product information for the specified FRU |
|
|||
Display the FRU data history log |
|
|||
Display the status for the environmental sensors, including their states and current values |
|
|
||
Display the status and details for the specified sensor |
You can obtain |
|||
Display the SP firmware version information |
|
|
||
Display the SP command history |
|
|
||
Display the SP debug information |
|
|
||
Display the SP messages file |
|
|
||
Display the settings for collecting system forensics on a watchdog reset event, display system forensics information collected during a watchdog reset event, or clear the collected system forensics information |
|
|||
Log in to the system console |
|
|
||
You should press Ctrl-D to exit the system console session. |
||||
Turn the node on or off, or perform a power-cycle (turning the power off and then back on) |
|
|
||
|
||||
|
||||
The standby power stays on to keep the SP running without interruption. During the power-cycle, a brief pause occurs before power is turned back on.
|
||||
Create a core dump and reset the node |
The |
(advanced privilege level) |
||
These commands have the same effect as pressing the Non-maskable Interrupt (NMI) button on a node, causing a dirty shutdown of the node and forcing a dump of the core files when halting the node. These commands are helpful when ONTAP on the node is hung or does not respond to commands such as |
||||
Reboot the node with an optionally specified BIOS firmware image (primary, backup, or current) to recover from issues such as a corrupted image of the node's boot device |
|
|
||
If no BIOS firmware image is specified, the current image is used for the reboot. The SP stays operational as long as the input power to the node is not interrupted. |
||||
Display the status of battery firmware automatic update, or enable or disable battery firmware automatic update upon next SP boot |
(advanced privilege level) |
|||
Compare the current battery firmware image against a specified firmware image |
(advanced privilege level) If |
|||
Update the battery firmware from the image at the specified location |
(advanced privilege level) You use this command if the automatic battery firmware upgrade process has failed for some reason. |
|||
Update the SP firmware by using the image at the specified location |
|
|
|
|
Reboot the SP |
|
|
||
Erase the NVRAM flash content |
This command cannot be initiated when the controller power is off ( |
|||
Exit the SP CLI |
|