Contents

1   Introduction

This instruction concerns alarm handling.

1.1   Alarm Description

The SW RAID Array Degradation alarm is issued by the Managed Object (MO) Host. The severity of the alarm is MAJOR.

The possible alarm causes and fault locations are explained in Table 1.

Table 1    Alarm Causes

Alarm Cause	Description	Fault Reason	Fault Location	Impact
Disk failure	One or more disks within the array are unavailable	HW fault SW fault	Compute host	Software RAID is degraded

The following is the consequence for the host if the alarm is not solved:

• System performance and reliability can be degraded.

The alarm attributes are listed in Table 2.

Table 2    Alarm Attributes

Attribute Name	Attribute Value
Major Type	193
Minor Type	2031817
Managed Object Class	Host
Managed Object Instance	Region=<region_name>, Equipment=1, Host=<hostname>
Specific Problem	SW RAID array degradation
Event Type	equipmentAlarm (5)
Probable Cause	diskFailure
Additional Text	SW RAID degraded as one or more disks within the array is unavailable; <hw_uuid>
Severity	MAJOR (4)

1.2   Prerequisites

This section provides information on the documents, tools, and conditions that apply to the procedure.

1.2.1   Documents

Not applicable.

1.2.2   Tools

No tools are required.

1.2.3   Conditions

No conditions.

2   Procedure

This section describes the procedure to follow when the alarm is received.

2.1   Actions

Perform the following:

1. Identify the affected compute server:
   1. Note down the HW UUID from the Additional Text field of the alarm.
   2. In case of an HDS system, match the HW UUID to the specific compute server with one of the following tools:
      • REST API

        For more information refer to the HDS topic List Computer Systems Assigned to a vPOD Using REST API, Reference [1].

      • HDS Command Center Manager (CCM) GUI

        For more information refer to the HDS topic List Computer Systems Assigned to a vPOD Using GUI, Reference [1].

2. Replace the affected compute server as described in the Server Replacement document.

   If the alarm remains, continue with Step 3.

3. Collect troubleshooting data as described in the Data Collection Guideline.
4. Contact the next level of maintenance support.

   Further actions are outside the scope of this instruction.

5. The job is completed.

Reference List

[1] Hyperscale Datacenter System 8000 Customer Documentation, 2/1551-LZN 901 5032