| Asset ID: |
1-79-2047203.1 |
| Update Date: | 2018-01-08 |
| Keywords: | |
Solution Type
Predictive Self-Healing Sure
Solution
2047203.1
:
Pillar Axiom: Compare the Installed vs Staged Release Before Replacing a Pilot on release R5
| Related Items |
- Pillar Axiom 600 Storage System
- Pillar Axiom 500 Storage System
|
| Related Categories |
- PLA-Support>Sun Systems>DISK>Axiom>SN-DK: Ax600
|
In this Document
Oracle Confidential PARTNER - Available to partners (SUN).
Reason: The check in scope of this document have to be performed by the TSC engineers before ordering a replacement pilot.
Applies to:
Pillar Axiom 600 Storage System - Version All Versions and later
Pillar Axiom 500 Storage System - Version All Versions and later
Information in this document applies to any platform.
Purpose
This article describes what steps to perform in order to check the versions before replacing a Pilot. This article applies to Pillar Axiom Release R5 only.
IMPORTANT: If this check is not performed before replacing an Axiom Pilot in R5, the replacement pilot will have the issue described in the document <Document 1952478.1> Pillar Axiom: Pilot Control Unit Replacement Fails if Staged Software Version is Higher than Installed Software Version.
Details
- Log into the Axiom Storage Manager GUI (Graphical User Interface).
- Navigate to "Support" tab, and from the left menu click "Software Modules".
- In the main page check the "Installed Software" and make sure its the same as the "Staged Software".
- Pilot replacement:
- If both versions are identical, please stop here and proceed with the pilot replacement.
- If there is a difference, stage the same version as the running version before proceeding with the pilot replacement. See the steps below.
- Download the patch corresponding to the release currently running on the Pillar Axiom. Refer to the <Document 1422199.1> Pillar Axiom: How to Find Pillar Axiom Software/Firmware and Patches in My Oracle Support (MOS).
Example: If the running version is 050417-014600 and the staged version is 050418-014900, download in this case the patch 20372809 for 050417-014600.
- Unzip the downloaded file and upload the package "AxiomONE-SW-<release>.i386.rpm" to the Axiom in order to stage it without performing the upgrade.
- Proceed with the pilot replacement once the staged and running versions are identical.
The following procedure to compare the installed release vs the staged release can be carried out by Oracle support engineers by using an existing log bundle:
- Execute "scanlog" against the manual log bundle.
- Compare the running version (aka PacmanVersion) with the staged version (aka CompatibilityMatrixVersion) in the file chsh.xml:
# egrep "PacmanVersion|CompatibilityMatrixVersion" chsh.xml
Example:
# egrep "PacmanVersion|CompatibilityMatrixVersion" chsh.xml
<PacmanVersion>2073-00001-050403-008300</PacmanVersion>
<
PacmanVersion>2073-00001-
050403-008300</PacmanVersion>
<
CompatibilityMatrixVersion>2090-00001-
050403-008300</CompatibilityMatrixVersion>
#
Note: In the above example we have 050403-008300 installed for the running and staged versions.
References
<NOTE:1906876.1> - Pillar Axiom: How to Collect a System Information Log and Transfer it to Oracle
Attachments
This solution has no attachment
