system health autosupport trigger history show
- PDF of this doc site
Collection of separate PDF docs
Creating your file...
View system health alert history
Availability: This command is available to cluster administrators at the admin privilege level.
Description
The system health autosupport trigger history show
command displays all the alert triggers in the cluster that generated the AutoSupport messages. The following fields are displayed in the output:
-
Node name
-
Monitor name
-
Subsystem
-
Alert identifier
-
Alerting resource
-
Severity
-
If an AutoSupport has been sent due to this alert
Parameters
- {
[-fields <fieldname>,…]
-
Use this parameter to display only the fields you specify.
- |
[-instance ]
} -
Use this parameter to display additional information about all of the alerts that were generated.
[-node {<nodename>|local}]
- Node-
Use this parameter to display AutoSupport trigger history on the specified node.
[-monitor <hm_type>]
- Monitor-
Use this parameter to display AutoSupport trigger history with the specified monitor name.
[-alert-id <text>]
- Alert ID-
Use this parameter to display the AutoSupport message that was triggered by the specified alert ID.
[-alerting-resource <text>]
- Alerting Resource-
Use this parameter to display the AutoSupport message that was triggered by the specified alerting resource.
[-subsystem <hm_subsystem>]
- Subsystem-
Use this parameter to display the AutoSupport message that was triggered by the specified subsystem.
[-indication-time <Date>]
- Indication Time-
Use this parameter to display the AutoSupport message that was triggered at the indicated time.
[-perceived-severity <hm_perceived_sev>]
- Perceived Severity-
Use this parameter to display the AutoSupport message that was triggered by alerts with the specified perceived severity.
[-autosupport-triggered {true|false}]
- AutoSupport Triggered-
Use this parameter to display the alerts that generated AutoSupport messages.
[-probable-cause <hm_probable_cause>]
- Probable Cause-
Use this parameter to display the alerts that were generated with the specified probable cause.
[-corrective-actions <text>]
- Corrective Actions-
Use this parameter to display the AutoSupport alerts with the specified corrective actions.
[-asup-enable {true|false}]
- Enable Asup for This Alert-
Use this parameter to enable or disable an AutoSupport message for this alert.
[-alert-clear-time <Date>]
- Alert Clear Time-
Use this parameter to display the alerts that were cleared at a given time.
Examples
This example displays information about the AutoSupport trigger history
cluster1::> system health autosupport trigger history show Node Monitor Subsystem Alert ID ------------ ---------------------- ----------------- ---------------------- node1 node-connect SAS-connect DualPathToDiskShelf_ Alert Resource: 50:05:0c:c1:02:00:0f:02 Severity: Major AutoSupport sent: true
This example displays info about the autosupport trigger history in detail
cluster1::> system health autosupport trigger history show -instance Node: node1 Monitor: node-connect Alert ID: DualPathToDiskShelf_Alert Alerting Resource: 50:05:0c:c1:02:00:0f:02 Subsystem: SAS-connect Indication Time: Thu Mar 17 11:59:09 2011 Perceived Severity: Major AutoSupport Triggered: true Probable Cause: Connection_establishment_error Corrective Actions: 1. Halt controller node1 and all controllers attached to disk shelf 2. 2. Connect disk shelf 2 to controller node1 via two paths following the rules in the Universal SAS and ACP Cabling Guide. 3. Reboot the halted controllers. 4. Contact support personnel if the alert persists. Enable asup for this alert: true Alert Clear Time: Wed May 29 16:10:13 2013