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... Or this ONTAP command ...
Display available SP commands or subcommands of a specified SP command help [command]  
Display the current privilege level for the SP CLI priv show  
Set the privilege level to access the specified mode for the SP CLI priv set {admin | advanced | diag}  
Display system date and time date date
Display events that are logged by the SP events {all | info | newest number | oldest number | search keyword}  
Display SP status and network configuration information sp status [-v | -d]

The -v option displays SP statistics in verbose form. The -d option adds the SP debug log to the display.

system service-processor show
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 sp uptime  
Display system console logs system log  
Display the SP log archives or the files in an archive sp log history show [-archive {latest | all | archive-name}] [-dump {all | file-name}]  
Display the power status for the controller of a node system power status system node power show
Display battery information system battery show  
Display ACP information or the status for expander sensors system acp [show | sensors show]  
List all system FRUs and their IDs system fru list  
Display product information for the specified FRU system fru show fru_id  
Display the FRU data history log system fru log show

(advanced privilege level)

Display the status for the environmental sensors, including their states and current values system sensors or system sensors show system node environment sensors show
Display the status and details for the specified sensor system sensors get sensor_name

You can obtain sensor_name by using the system sensors or the system sensors show command.

Display the SP firmware version information version system service-processor image show
Display the SP command history sp log audit

(advanced privilege level)

Display the SP debug information sp log debug

(advanced privilege level)

Display the SP messages file sp log messages

(advanced privilege level)

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 system forensics [show | log dump | log clear]  
Log in to the system console system console system node run-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) system power on system node power on

(advanced privilege level)

system power off  
system power cycle  

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.

Attention: Using these commands to turn off or power-cycle the node might cause an improper shutdown of the node (also called a dirty shutdown) and is not a substitute for a graceful shutdown using the ONTAP system node halt command.
Create a core dump and reset the node system core [-f]

The -f option forces the creation of a core dump and the reset of the node.

system node coredump trigger

(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 system node shutdown. The generated core dump files are displayed in the output of the system node coredump show command. The SP stays operational as long as the input power to the node is not interrupted.

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 system reset {primary | backup | current} system node reset with the -firmware {primary | backup | current} parameter

(advanced privilege level)

system node reset

Attention: This operation causes a dirty shutdown of the node.

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 system battery auto_update [status | enable | disable]

(advanced privilege level)

Compare the current battery firmware image against a specified firmware image system battery verify [image_URL]

(advanced privilege level)

If image_URL is not specified, the default battery firmware image is used for comparison.

Update the battery firmware from the image at the specified location system battery flash image_URL

(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 sp update image_URL

image_URL must not exceed 200 characters.

system service-processor image update
Reboot the SP sp reboot system service-processor reboot-sp
Attention: You should avoid booting the SP from the backup image. Booting from the backup image is reserved for troubleshooting and recovery purposes only. It might require that the SP automatic firmware update be disabled, which is not a recommended setting. You should contact technical support before attempting to boot the SP from the backup image.
Erase the NVRAM flash content system nvram flash clear

(advanced privilege level)

This command cannot be initiated when the controller power is off (system power off).

Exit the SP CLI exit