Skip to main content

system health alert show

Contributors
Suggest changes

View system health alerts

Availability: This command is available to cluster administrators at the admin privilege level.

Description

The system health alert show command displays information about all the alerts generated on the system. Using -instance will add detailed information.

Parameters

{ [-fields <fieldname>,…​]

Selects the fields that you specify.

| [-instance ] }

Displays the following additional information about each alert:

  • Node name

  • Resource name

  • Severity of the alert

  • Time of alert generation

  • Suppress state of the alert

  • Acknowledge state of the alert

  • Probable cause for the alert

  • Possible effect due to the alert

  • Recommended corrective actions to follow

[-node {<nodename>|local}] - Node

Selects the alerts generated for the specified node.

[-monitor <hm_type>] - Monitor

Selects the alerts with the specified monitor name.

[-alert-id <text>] - Alert ID

Selects the alerts with the specified alert ID.

[-alerting-resource <text>] - Alerting Resource

Selects the alerts with the specified alerting resource name.

[-subsystem <hm_subsystem>] - Subsystem

Selects the alerts generated on the monitoring subsystem.

[-indication-time <Date>] - Indication Time

Selects the alerts with the specified indicated time.

[-perceived-severity <hm_perceived_sev>] - Perceived Severity

Selects the alerts with the perceived severity level.

[-probable-cause <hm_probable_cause>] - Probable Cause

Selects the alerts that contain the specified probable cause.

[-probable-cause-description <text>] - Description

Selects the alerts containing the specified probable cause description.

[-corrective-actions <text>] - Corrective Actions

Selects the alerts with the specified recommended corrective action.

[-possible-effect <text>] - Possible Effect

Selects the alerts with the specified possible effect.

[-acknowledge {true|false}] - Acknowledge

Selects the alerts with the specified acknowledgement status.

[-suppress {true|false}] - Suppress

Selects the alerts with the specified suppressor field status of true or false.

[-policy <text>] - Policy

Selects the alerts with the specified policy name.

[-acknowledger <text>] - Acknowledger

Selects the alerts with the specified acknowledger field.

[-suppressor <text>] - Suppressor

Selects the alerts with the specified suppressor field.

[-additional-info <text>,…​] - Additional Information

Selects the alerts with the specified additional information.

[-alerting-resource-name <text>] - Alerting Resource Name

Selects the alerts with the specified alerting resource name.

[-tags <hm_alert_type>,…​] - Additional Alert Tags

Selects the alerts with the specified keywords.

Examples

The example below displays information about all the alerts generated in the cluster:

cluster1::> system health alert show
Node: node1
           Alert ID: DualPathToDiskShelf_Alert
           Resource: Shelf ID 2
           Severity: Major
     Suppress: false
  Acknowledge: false
         Tags: quality-of-service, nondisruptive-upgrade
     Probable Cause: Disk shelf 2 does not have two paths to controller
                     node1.
    Possible Effect: Access to disk shelf 2 via controller node1 will be
                     lost with a single hardware component failure (e.g.
                     cable, HBA, or IOM failure).
 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.

The example below displays additional information about a specific alert generated in the cluster:

cluster1::> system health alert show -monitor node-connect -alert-id DualPathToDiskShelf_Alert -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: Mon Mar 21 10:26:38 2011
    Perceived Severity: Major
        Probable Cause: Connection_establishment_error
           Description: Disk shelf 2 does not have two paths to controller node1.
    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.
       Possible Effect: Access to disk shelf 2 via controller node1 will be lost with a single hardware component failure (e.g. cable, HBA, or IOM failure).
           Acknowledge: false
              Suppress: false
                Policy: DualPathToDiskShelf_Policy
          Acknowledger: -
            Suppressor: -
Additional Information: Shelf uuid: 50:05:0c:c1:02:00:0f:02
                        Shelf id: 2
                        Shelf Name: 4d.shelf2
                        Number of Paths: 1
                        Number of Disks: 6
                        Adapter connected to IOMA:
                        Adapter connected to IOMB: 4d
Alerting Resource Name: Shelf ID 2
 Additional Alert Tags: quality-of-service, nondisruptive-upgrade