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:
2010-10-22 10:35:36 PDT Created task.
2010-10-22 10:35:36 PDT Updated Executing "upgradecage -a -f" as 0:12109
2010-10-22 10:35:36 PDT Errored upgradecage: Invalid option: -f
vlun
• Displays inactive Virtual LUNs (VLUNs) and those which have not been reported by the host agent.
• Reports VLUNs that have been configured but are not currently being exported to hosts or host-ports.
• Displays when too many VLUNs have been created.
Format of possible
vlun
exception messages
vlun vlun:(<vvID>, <lunID>, <hostname>)"Path to <wwn> is not is not seen by host" vlun
vlun:(<vvID>, <lunID>, <hostname>) "Path to <wwn> is failed"
vlun host:<hostname> "Host <ident>(<type>):<connection> is not connected to a port"
vlun -- "<count> active VLUNs exceeds the supported limit of <max count>"
vlun
example
Component ---------Summary Description--------- Qty
vlun Hosts not connected to a port 1
Component -----Identifier----- ---------Detailed Description--------
Troubleshooting
163