Troubleshooting a node by using the SP
When you encounter a problem with a node, you can use the SP to display information about the problem, create a core dump, and reboot the node, even if the node's firmware is corrupted.
The following table describes the common SP commands that you can use at the SP prompt to troubleshoot a node:
| If this condition occurs... | And you want to... | Enter this command at the SP CLI prompt... |
|---|---|---|
| An environmental sensor has reached an abnormal condition. | Display the status for all environmental sensors, their states, and the current values. | system sensors show |
| Display the status and details for a specific sensor. | system sensors get sensor_name | |
| The node is not responding properly. | Access the system console from the SP. | system console |
| Create a core dump and reboot the node. | system core | |
| Power-cycle the node. | system power cycle | |
| You receive an AutoSupport message indicating an event such as a panic or hardware component failure. | Display what has occurred at the system console. | system log |
| Display all events. | events all | |
| Display a specific number of recent events. | events newest number | |
| Search for specific events regarding keyword. | events search keyword | |
| The node firmware is corrupted. | Boot the node by using the backup image of the firmware. | system reset backup |
| A FRU is malfunctioning. | Display the FRU's product information. | system fru list to list all FRU IDs |
| system fru show fru_id to display product information for a specific FRU |