Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-2244434.1
Update Date:2017-06-22
Keywords:

Solution Type  Technical Instruction Sure

Solution  2244434.1 :   Pillar Axiom: Howto Configure CallHome For a Brick Fan Failure Event  


Related Items
  • Pillar Axiom 600 Storage System
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Axiom>SN-DK: Ax600
  •  




In this Document
Goal
Solution


Created from <SR 3-14258347457>

Applies to:

Pillar Axiom 600 Storage System - Version All Versions to All Versions [Release All Releases]
Axiom System Operating Software

Goal

 

This problem is fixed in 5.4.24 so you only need to implement this workaround if the system version is on 5.4.23 or lower.

 

How to upload a new callhome matrix to trigger a callhome for a Brick Fan Failure event.

Current situation:
In certain Brick Fan failure conditions, a corresponding callhome BRICK_SENSOR_STATE_CHANGE is not created so there is no service request created for the event.

The LED on the PSU/fan module might change to amber and the fan is not spinning but there is no callhome generated. If there are other follow-on events, these may trigger a callhome which in turn may generate a service request.


A manual way to check for PSU/Fan failing is to periodically do a wet finger check on each of the three fans in each supply on every brick. However, if you have a several systems and bricks then you want to implement the fix offered in this document.


The following modification will allow the BRICK_SENSOR_STATE_CHANGE callhome to be performed. If Automated Service Request (ASR) is enabled,  a corresponding ASR will thus be generated for a Brick FAN failure.

Solution

 Upload a new CallHomeMatrix.xml (link to the CallHomeMatrix.xml) with the added trigger value to the Networking screen.

 The following is a section of the callhome matrix indicating the change (do not install just this section..)

The CallHomeMatrix.xml with the change is as follows:
<Event>
@ <Name>BRICK_SENSOR_STATE_CHANGE</Name>
@ <ExpectedEventParameter>
@ <KeyValuePair>
@
@ <ParameterKey>BrickSensorStateEvent.BrickSensorState.sensorDetectedState</Para
@ meterKey>
@ <TriggerValue>SEN_STATE_LOWCRIT</TriggerValue>
@ <TriggerValue>SEN_STATE_LOWWARN</TriggerValue>
@ <TriggerValue>SEN_STATE_HIWARN</TriggerValue>
@ <TriggerValue>SEN_STATE_HICRIT</TriggerValue>
@ <TriggerValue>SEN_STATE_FAIL</TriggerValue>
@ </KeyValuePair>
@ <KeyValuePair>
@
@ <ParameterKey>BrickSensorStateEvent.BrickSensorState.sensorType</ParameterKey>
@ .
@ <TriggerValue>SEN_TYPE_TEMP</TriggerValue>
@ <TriggerValue>SEN_TYPE_ACMON</TriggerValue>
@ <TriggerValue>SEN_TYPE_FAN</TriggerValue> this line is added to trigger the event
@ </KeyValuePair>
@ </ExpectedEventParameter>
@ <Flags>
@ <InitiateCallHome/>
@ <SessionHeader/>
@ <EventLogEntries>
@ <Period>ONE_DAY</Period>
@ </EventLogEntries>
@ </Flags>
@ </Event>

 Steps to add the CallHomeMatrix.xml file to the Axiom system:


1) Download the attached CallHomeMatrix.xml


2) Login to the Axiom GUI with user Pillar


3) Go to Configure then click on Networking


4) From the Networking screen, right click and select Upload Call-Home Matrix.
Go to the CallHomeMatrix.xml file location and select the file.
Click OK.

 

uplaod_call-home_matrix

 

The file CallHomeMatrix.xml will replace the same file currently saved in /var/PillarCallHome. It will tell PacMan to synchronize it to the other pilot and re-read it.


PillarCallHome

If a Brick Fan fails, it will create a service request (if enabled) with the event BRICK_SENSOR_STATE_CHANGE

Example of the event parameters:
@ Event Properties
@ .
@ Event: Brick Sensor State Change
@ Category: System
@ Time Occurred: Fri Feb 17 11:30:17 PST 2017
@ User: (system)
@ Affected Item: /Brick001
@ .
@ Description:
@ .
@ Brick Sensor state change.
@ .
@ BrickSensorStateEvent.BrickSensorState.sensorId: 1
@ BrickSensorStateEvent.BrickEventHeader.info: BV_FAULT
@ BrickSensorStateEvent.BrickEventHeader.wwn: 200C000B083A5436
@ BrickSensorStateEvent.BrickEventHeader.reserved: 0
@ BrickSensorStateEvent.BrickSensorState.cruId: CRU_PSU0
@ BrickSensorStateEvent.BrickEventHeader.reserved1: 0
@ BrickSensorStateEvent.BrickEventHeader.length: 52
@ BrickSensorStateEvent.BrickEventHeader.controllerId: 0
@ BrickSensorStateEvent.BrickSensorState.sensorValue: 0
@ BrickSensorStateEvent.BrickSensorState.sensorDetectedState: SEN_STATE_FAIL
@ BrickSensorStateEvent.BrickSensorState.sensorType: SEN_TYPE_FAN
@ BrickSensorStateEvent.BrickEventHeader.raidControllerFirmwareVersion: 072334
@ BrickSensorStateEvent.BrickEventHeader.id: BRIX_SENSOR_STATE
@ BrickSensorStateEvent.BrickEventHeader.time: 365856541

 

 -END-


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback