Sun Microsystems, Inc.  Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1443817.1
Update Date:2012-08-27
Keywords:

Solution Type  Problem Resolution Sure

Solution  1443817.1 :   Pillar Axiom: Callhome event - Axiom Brick Firmware Update Failed  


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




In this Document
Symptoms
Cause
Solution


Created from <SR 3-5516378311>

Applies to:

Pillar Axiom 600 Storage System - Version Not Applicable and later
Information in this document applies to any platform.

Symptoms


A Callhome for a "Brick Firmware Update Failed" was received from this Axiom.

Cause

There are several factors that can trigger this Callhome, some of which are listed below, and all involve the ability of the target Brick's RAID Controllers to correctly negotiate the attempt to upgrade its on-board firmware version:
1) If the Brick's RAID Controller ran into a condition that triggers a fault or disconnect while attempting to download the newer firmware (via software, like an internal fault, or hardware, like a brief power loss)
2) If the new Brick's firmware is running at a higher revision level than the Axiom's current firmware levels (ie, the new brick is running R5 but the Axiom is still running R4)
3) The target Brick's RAID Controllers were not primed or faulty and does not know how to negotiate the retrieval of the firmware. This is a sign that the RAID Controller is inherently defective, especially with multiple attempts at the firmware update process.

Solution

1) Gather the information regarding the brick being added/updated, and any software versions (firmware, etc) that may exist for it, and the Axiom.
2) Look into possibly securing a brick Console cable to connect to the brick's RAID Controller(s) in case customer support requires it.
3) Take note if several re-attempts at adding the brick results in the same Callhome event.
4) Gather a logset if one hasn't been done yet and send that into Customer Support
5) Contact Customer Support for further assistance.


Attachments
This solution has no attachment
  Copyright © 2012 Sun Microsystems, Inc.  All rights reserved.
 Feedback