The system health alert definition show command displays information about the various alerts defined in the system health monitor policy file. Using -instance will display additional details.

Parameters

{ [-fields <fieldname>,…]

Selects the fields that you specify.

| [-instance ] }

Use this parameter to display additional information on each alert definition.

Node name
Monitor name
Subsystem identifier
Alert ID
Severity of the alert
Probable cause
Probable cause description
Possible effect due the error state
Recommended corrective actions to be followed
Any additional information
Additional alert tags

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

Selects the alert definitions for the specified node.

[-monitor <hm_type>] - Monitor

Selects the alert definitions with the specified monitor name.

[-alert-id <text>] - Class of Alert

Selects the alert definitions with the specified alert identifier.

[-perceived-severity <hm_perceived_sev>] - Severity of Alert

Selects the alert definitions with the specified perceived severity.

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

Selects the alert definitions with the specified probable cause of the alert.

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

Selects the alert definitions with the specified probable cause description.

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

Selects the alert definitions with the specified possible effect.

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

Selects the alert definitions with the specified corrective action.

[-subsystem <hm_subsystem>] - Subsystem Name

Selects the alert definitions with the specified subsystem.

[-additional-information <text>] - Additional Relevant Data

Selects the alert definitions with the specified additional information.

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

Selects the alert definitions with the specified keywords.

Examples

The example below displays information about all the definitions in the alert definition file:

cluster1::> system health alert definition show
Node          Monitor                Subsystem         Alert ID
------------- ---------------------- ----------------- -----------------------
node-01       system-connect         SAS-connect       DualControllerNonHa_
                                                       Alert
                  Severity: Major
            Probable Cause: Configuration_error
Probable Cause Description: Disk shelf $(sschm_shelf_info.id) is connected to
                            two controllers
                            ($(sschm_shelf_info.connected-nodes)) that are
                            not an HA pair.
           Possible Effect: Access to disk shelf $(sschm_shelf_info.id) may
                            be lost with a single controller failure.
        Corrective Actions: 1. Halt all controllers that are connected to disk shelf $(sschm_shelf_info.id).
                            2. Connect disk shelf $(sschm_shelf_info.id) to both HA controllers following the rules in the Universal SAS and ACP Cabling Guide.
                            3. Reboot the halted controllers.
                            4. Contact support personnel if the alert persists.
           Additional Info: -
                      Tags: quality_of_service, nondisruptive-upgrade

The example below displays detailed information about the definitions in the alert definition file:

cluster1::> system health alert definition show -instance
Node: krivC-01
                   Monitor: system-connect
            Class of Alert: DualControllerNonHa_Alert
         Severity of Alert: Major
            Probable Cause: Configuration_error
Probable Cause Description: Disk shelf $(sschm_shelf_info.id) is connected to two controllers ($(sschm_shelf_info.connected-nodes)) that are not an HA pair.
           Possible Effect: Access to disk shelf $(sschm_shelf_info.id) may be lost with a single controller failure.
        Corrective Actions: 1. Halt all controllers that are connected to disk shelf $(sschm_shelf_info.id).
        2. Connect disk shelf $(sschm_shelf_info.id) to both HA controllers following the rules in the Universal SAS and ACP Cabling Guide.
        3. Reboot the halted controllers.
        4. Contact support personnel if the alert persists.
            Subsystem Name: SAS-connect
  Additional Relevant Data: -
     Additional Alert Tags: quality_of_service, nondisruptive-upgrade