![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Solution Type Predictive Self-Healing Sure Solution 1577565.1 : Pillar Axiom: Axiom 300, 500, 600 Pilot CU Substitution Matrix
This document lists all of the Pilot CUs for the Ax600, Ax500, and Ax300 Axiom Systems In this Document
Oracle Confidential PARTNER - Available to partners (SUN). Applies to:Pillar Axiom 300 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 600 Storage System - Version Not Applicable to Not Applicable [Release N/A] Information in this document applies to any platform. PurposeThis document contains all the Pilot Control Units (CUs) that are or were supported in Axiom Systems, and lists these items:
Please refer to the following in the Oracle System Handbook:
For the steps to replace a Pilot CU, please refer to Document 1539019.1, Pillar Axiom: How to Replace a Pilot Control Unit.
ScopeThis document is intended for TSC and FE personnel. This document details all of the Pilot CU hardware that has ever been used on Axiom systems and the various substitutions that will work. DetailsAxiom Pilot CU Substitution InformationThe following table contains the current actively supported part numbers.
The following table is for historical reference only:
1The "Software on Pilot FRU" is the lowest revision of Axiom software that will support this Pilot model, except as noted in the notes column. 2Although you may encounter older Pilot CUs on a system, one of the following four should always be used as a replacement:
3In the unlikelihood that an R4.0 or R4.1 Axiom with a Pilot issue is encountered, 1450-00179-3x is the recommended replacement part. 4The MSI Pilot CUs are imaged to R 1.7.6 and are the only Pilot CUs that may be used to replace a Pilot CU on a system below R2.4.2. The MSI should never be used to replace a Pilot CU on any R5.x system--it will very likely crash the system. The MSI may also be used to replace a Pilot CU on any release up to R4.x, but only if no other Pilot CU is available. The Axiom 1.x release used separate IP networks for the PMI. The 172.30.81.xx network was used for the Pilot to Pilot ethernet. The 172.30.80.xx network is used for Pilot to Slammer and Slammer to Slammer communications. Release 2.4.2 binds the two Pilot ethernets together and uses Spanning Tree to avoid ethernet frames from repeating until the Pilot or Slammer crashes. All Axiom releases up to and including R4.x are able to detect the older network and temporarily bring up a 172.30.81.xx network to image the new Pilot CU. R5.x does not have this capability, so any new MSI placed in an R5.x system will become pilot1 and will assume it is the active pilot, with potentially disastrous results. 5Some models of the MSI Pilot were shipped with only 512 Mbyte memory. These all should have been upgraded to 2 Gb memory as part of the R1.x to R2.x upgrade, however the part number may not have been updated as the memory was upgraded. If you encounter one of the MSI Pilot CUs that does not have 2 Gb memory, contact a product expert and Engineering for assistance. Axiom systems with older Pilot CUs, including the old DC, Intel, and MSI can be upgraded to R5.x without first replacing the Pilot CUs as long as all software prerequisites are met. The older Pilot CUs may fail on the upgrade, typically because the grub loader is not updated, and it cannot boot the Oracle Linux kernel properly. This is not recoverable in the field--just replace the Pilot CU with one that is supported on the R5 software.
References<NOTE:1539019.1> - Pillar Axiom: How to Replace a Pilot Control Unit:ATR:1539019.1:2Attachments This solution has no attachment |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|