正文文本
2016/5/3 https://updates.oracle.com/Orion/Services/download?type=readme&aru=19539809
ORACLE PILLAR AXIOM SOFTWARE PATCH RELEASE NOTES
PATCH RELEASE: 05.04.18
AVAILABILITY : LIMITED
MAJOR RELEASE: 05.04.00
APPLIES TO : Axiom 500/600
RELEASE DATE : 02/10/2015
DESCRIPTION:
This is a patch for the release 5 version of the Oracle Pillar Axiom storage system.
CONTENTS:
Package Description
1 of 3 Install RPM packages (These are the standard packages used for most upgrades)
2 of 3 Install FN packages (Used in conjunction with upgrades from releases prior to Release 5)
3 of 3 Drive Firmware packages (If applicable. Used for disk drive firmware updates by Support)
NOTABLE CHANGES OR ADDITIONS:
None
DEFECTS FIXED IN THIS PATCH:
Applies
Release Defect To Description
05.04.18 20380232 All The periodic statistics information push from the Slammers
may cause the Pilot to hang, followed by Core Dump Found
events.
20359750 All A defective replacement drive may result in repeated RAID
Controller faults, which may result in an entire FC Brick
going offline.
20354129 All If a drive is in a proactive CopyAway process and the drive
faults during the CopyAway, the CopyAway may hang
instead of transitioning to a Rebuild operation. The RAID
controllers may experience Stuck Busy faults and remain in
a Booting status.
19402261 All RAID Controllers may experience Stuck Busy software faults
due to a deadlock condition if a read and a write are
attempting to access the same RAID stripe and the read
request encounters a media error and attempts to call a
https://updates.oracle.com/Orion/Services/download?type=readme&aru=19539809 1/3
2016/5/3 https://updates.oracle.com/Orion/Services/download?type=readme&aru=19539809
sector repair operation.
19202009 All During a proactive CopyAway operation, if other drives in
the RAID array generate a large number of read errors
leading to unrecoverable sector repair operations, the RAID
controllers may experience repeated software faults.
19131890 All If a RAID rebuild operation is in progress, and a second
drive in the same array attempts to fault, user volumes on
that Brick may go offline due to one RAID CU remaining in
the bootblock and the other experiencing repeated Stuck
Busy software faults.
18263053 All An internal Slammer software request for private network
statistics may occasionally return more information than will
fit in the allocated buffers, resulting in a Slammer CU
software warm start.
17235421 All An FC drive that has experienced an internal firmware fault
may be allowed back online without re-seating that drive ,
resulting in repeated RAID CU software faults.
KNOWN PROBLEMS AND WORKAROUNDS:
See full 5.4 Release Notes
PREREQUISITES:
Please Refer to the Upgrade Instructions and Release Notes.
Ax600: Axiom Software Release 04.05.00 or higher
The Axiom 500 is no longer supported. For information on upgrading Axiom 500 systems, please refer
to MOS Support document 1472278.1 (Pillar Axiom: Software/Firmware upgrade procedure R4.x to
R5.x)
UPGRADE INSTRUCTIONS:
Select the correct package for your current installed release and Axiom hardware platform.
Package zip file 1 of 3 contains the RPM format package for upgrading an Axiom Ax600 from any
R5.x release.
Package zip file 2 of 3 contains the FN tgz packages for upgrading from Release 4.x.
Ax600_FN_NNNNNN-NNNNNN.tgz packages must be used for Ax600.
Package zip file 3 of 3 contains the Drive Firmware upgrade packages in RPM format.
1. Select the correct package for your current installed release and Axiom platform.
https://updates.oracle.com/Orion/Services/download?type=readme&aru=19539809 2/3
2016/5/3 https://updates.oracle.com/Orion/Services/download?type=readme&aru=19539809
Download the patch package and save it into a local directory and extract the contents of the zip
file. R5.x to R5.x upgrades will use AxiomONE-SW-050418-014900.i386.rpm. R4.x upgrades will
use Ax600_FN_050418-014900.tgz for Ax600.
2. Login as Administrator into Axiom Storage Manager GUI.
3. Click the Support icon in the top context pane.
4. Click the Software Components link in the left navigation pane.
5. Choose Update Software from the Actions drop-down list.
6. To upload an update package to the Pilot:
1. Click the Upload Package button.
2. Browse to the patch package, and click the OK button.
7. After the Staging completes, all components that are affected should be automatically selected for
the administrator account.
8. Select Perform Update Now or Schedule Update.
VERIFYING UPGRADE:
1. Click the Support icon in the top context pane.
2. Click the Software Components link in the left navigation pane.
3. Review the displayed information to ensure that the versions are as shown below:
Software Module Installed Version
--------------- -----------------
Pilot OS 050414-013000
Pilot Software 050418-014900
Slammer PROM 050000-040000
Slammer Software 050418-014900
Brick Firmware 012334-012334/002334-002334/022334-022334/072334-072334
MINIMUM RELEASES
For current recommended software versions, refer to Document ID 1558848.1.
If you have any questions or problems, please visit the My Oracle Support site at:
http://support.oracle.com.
Other information regarding support for the Pillar Axiom products can be found at:
http://www.oracle.com/us/corporate/acquisitions/pillardata/support-459782.html
https://updates.oracle.com/Orion/Services/download?type=readme&aru=19539809 3/3