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-2226665.1
Update Date:2018-03-06
Keywords:

Solution Type  Problem Resolution Sure

Solution  2226665.1 :   FS System: Identification of an FS1-2 Pilot Model  


Related Items
  • Oracle FS1-2 Flash Storage System
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Flash Storage>SN-EStor: FSx
  •  




In this Document
Symptoms
Changes
Cause
Solution
References


Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Repair details
Created from <SR 3-14004204309>

Applies to:

Oracle FS1-2 Flash Storage System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

 Depending on the Oracle FS System Manager GUI and CLI version, the specific model type of the Pilot can be incorrectly displayed.

Changes

 The FS1-2 supports several Oracle Server models as Pilots:

  • Oracle Server X3-2 (mostly internal systems)
  • Oracle Server X4-2
  • Oracle Server X5-2
  • Oracle Server X6-2 (support added in R6.2.9)

Each one has its own unique set of part numbers and none of them are interchangeable with the other models.

 

Cause

 The underlying server hardware on which the Pilots are based is typically updated every 12-18 months.  As the support life for the FS1-2 has been longer, newer versions of the Pilot hardware are added to compensate for these updates.  This in turn has led to confusion as to how to determine which Pilot is being used.

Solution

Since both Pilots must be the same model type, gathering this information from a working Pilot will suffice if the other Pilot is down.  The most reliable way to determine the model of a Pilot is using the Oracle Server Assembly Part Number.  Depending on the data being examined, this data point has different labels.

Note: Do NOT rely on the Pilot information in the SystemConfiguration.txt from a log bundle.  It is not a reliable source, particularly in earlier versions of code.

 

From a log bundle, to obtain the Oracle Server Assembly Part Number, grep for the EnclosureAssemblyNumber in the Call Home Session Header (*.chsh.xml) file:

% grep EnclosureAssemblyNumber *.chsh.xml
      <EnclosureAssemblyNumber>7095032</EnclosureAssemblyNumber>
      <EnclosureAssemblyNumber>7095032</EnclosureAssemblyNumber>

 

From a live Pilot, the Oracle Server Assembly Part Number can be found using ipmitool and grepping for part_number:

[root@pilot1 ~]# ipmitool -H 169.254.2.5 -U root -P changeme sunoem cli "show /System" -I lanplus | grep part_number
        part_number = 7095032
[root@pilot1 ~]#

 

With the Oracle Server Assembly Part Number, the Pilot Model can be confirmed:

  • 7056044 = Oracle Server X3-2
  • 7078340 = Oracle Server X4-2
  • 7095032 = Oracle Server X5-2

    Note: Information for the Oracle Server X6-2 Pilot is not currently available as that change has not been made in manufacturing.

And with the proper Pilot Model identified, the proper parts can be ordered.

 

References

<BUG:24611447> - X5-2 PILOTS ARE REPORTED AS X4-2 IN SYSTEMCONFIGURATION.TXT

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