The <stat> variable can be any of the following: rx_errs, rx_dropped, rx_fifo, rx_frame,
tx_errs, tx_dropped, tx_fifo.
This message is usually caused by customer network issues, but might be caused by conflicting or
mismatching network settings between the Service Processor (SP), customer switch(es), and the storage
system. Check the SP network interface settings using the SPMAINT interface or SPOCC. Check the
storage system settings using commands such as shownet and shownet -d .
task
Displays failed tasks. Checks for any tasks that have failed within the past 24 hours. This is the default
time frame for the showtask -failed all command.
Format of Possible task Exception Messages
Task Task:<Taskid> "Failed Task"
task Example
Component --Identifier--- -------Detailed Description--------
Task Task:6313 Failed Task
In this example, checkhealth also showed an Alert. The task failed, because the command was
entered with a syntax error:
Component -Identifier- --------Detailed Description------------------------
Alert sw_task:6313 Task 6313 (type 'background_command', name
'upgradecage -a -f') has failed (Task Failed). Please see task status for
details.
task
Suggested Action
The CLI command showtask -d <Task_id> will display detailed information about the task. To clean
up the Alerts and the Alert-reporting of checkhealth, you can delete the failed-task alerts if they are of
no further use. They will not be auto-resolved and they will remain until they are manually removed with
the SSMC (GUI) or CLI with removealert or setalert ack . To display system-initiated tasks, use
showtask -all .
cli%
showtask -d 6313
Id Type Name Status Phase Step
6313 background_command upgradecage -a -f failed --- ---
Detailed status is as follows:
task 93
To Next Page
Loading...
