Pillar Axiom: Troubleshooting ES module failures (ESM)

Asset ID:	1-75-1518365.1
Update Date:	2016-01-26
Keywords:

Solution Type Troubleshooting Sure

Solution 1518365.1 : Pillar Axiom: Troubleshooting ES module failures (ESM)

Applies to:

Pillar Axiom 600 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Pillar Axiom 500 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Pillar Axiom 300 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.

Purpose

The purpose of this document is to describe how to troubleshoot ES module failures

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community - Disk Storage Pillar Axiom System

Troubleshooting Steps

Symptoms

Amber LED on the Brick ESM, no alerts from Pillar Axiom Storage Services Manager

Enclosure Services (ES) module location

Legend:

Pull tab
Screw
LEDs
Brick back
Dial settings
Digital push button

Troubleshooting and possible solutions

1. Double check if the amber LED is located on the Brick ESM

2. Confirm ESM status in the axiom log : SystemConfiguration.txt

Example :

Brick007.ESModule.Model = PCA-00023-12-E
Brick007.ESModule.SerialNumber = SGSCI00074ULM00C
Brick007.ESModule.Status = Normal

3. If the status of the Brick ESM is "Normal" please Disable CallHome by following KM 1535352.1 and reseat the ESM by following the procedure from pages 171 to 177 on the Pillar Axiom Service Guide.

That part of the document applies to all types of bricks for all types of Axioms (Axiom 300, 500 and 600).

Guided Maintenance details:
R4: go to the Support tab, click on Bricks (left menu), click on the Brick to reseat/remove the ES module, click on "ES Module" and follow the wizard.

R5: go to the Monitor tab, click on Bricks, double click on the Brick to reseat/remove the ES module, select "ES Module", click on "Replace Component" and follow the wizard.

The ES Module can be responsible for Brick Power Supplies to report a fault LED and a Warning status on the Axiom GUI. That lead can be verified if the power supply is replaced and the fault is still there.
Also, from Bug 17372842, the ES module can be responsible for back-end problems with the Raid Controllers (by Brick RC back-end, we mean connections between the RAID controller and the midplane).

Re-enable CallHome by following the last steps from Doc ID 1535352.1.

4. If the problem still exists or if the status of the ESM is different than "Normal" please contact with Customer Support Center and log a Service Request.

Note: Please check the Axiom software version as prior to 04.02.00 you could have the brick monitoring crashing and then errors not appearing in the GUI. On R5, ensure that Bricks are sending Events to the Pilot: check the event logs for recent brick events or remove a brick bezel and check the events. Steps to recover from not getting Brick Events are explained at the end of unpublished KM Doc 1560210.1.

For R3 and R4, please note that there is a known Bug 13754501 where Brick Monitoring stops working. The fixes were introduced on code branches 03.05.03, 04.01.05, 04.02.00 and onwards.

For R5, the Bug (Closed as unresolved) tracking the "NO BRICK HW EVENT RECEIVED BY PACMAN" issue is 17305123.

References

<NOTE:1436782.1> - Pillar Axiom: How to add a new Brick to an existing configuration
<NOTE:1535352.1> - Pillar Axiom: How to Disable Call Home to Prevent Automatic Service Request ASR Generation
<BUG:17305123> - **FORKED** NO BRICK OR SLAMMER EVENTS FROM MASTER NODE
<BUG:13754501> - [59472]SR26124 - BRICK MONITORING HAS DIED | PIERRE & VACANCES
<NOTE:1560210.1> - Pillar Axiom: Alternative Non Disruptive Upgrade to avoid upgrade failing during Brick Firmware phase

Attachments

This solution has no attachment