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-72-1577113.1
Update Date:2014-11-17
Keywords:

Solution Type  Problem Resolution Sure

Solution  1577113.1 :   Sun Storage 7000 Unified Storage System : 7420 Non M2 array with ILOM software 1.4 ILOM-3_0_16_13_a_r74558-Sun_Fire_X4470 7420 will not power up  


Related Items
  • Sun ZFS Storage 7420
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: 7xxx NAS
  •  




In this Document
Symptoms
Changes
Cause
Solution


Applies to:

Sun ZFS Storage 7420 - Version All Versions to All Versions [Release All Releases]
7000 Appliance OS (Fishworks)
This appears to be only seen when the array has this type of CPU as seen in the array hardware list:

cpu-000 CPU 0 ok Intel Intel(r) Xeon(r) CPU E7530 @ 1.87GHz unknown

and is listed as this type part number: 371-4721 1.86 GHz 6-Core Xeon E7530 CPU Module

Symptoms

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 ZFS Storage Appliance

On a 7420 Non M2 array after the upgrade to this ILOM 1.4 ILOM-3_0_16_13_a_r74558-Sun_Fire_X4470 version and after doing the start /SYS

at the ILOM prompt nothing is seen in the console and it appears that the node is not powered up.

Changes

 This occurs specifically after the upgrade of a 7420 Non M2 array to this specific ILOM 1.4 ILOM-3_0_16_13_a_r74558-Sun_Fire_X4470 code level.

Cause

This ILOM code version has a new CPU microcode and a certain small percentage of this specified type CPU will not function with this microcode.

Solution

The ILOM code can be reverted to the previous version and the array will again function.

 

Swapping out the CPUs will also correct this, although as of the original writing of the document it is not clear which versions of this CPU type has the problem.

So, there is a small chance of procuring a replacement CPU from spares/logistics, that then fails the microcode load.

 


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