Pillar Axiom 300 Storage System
 
Pillar Axiom 600 Storage System
 
Pillar Axiom 500 Storage System
 

PLA-Support>Sun Systems>DISK>Axiom>SN-DK: Ax600
 

The purpose of this document is to outline code update procedures for Axiom Systems running in R4 and upgrading to R4

In this Document

Goal

Solution

PREREQUISITES:

UPGRADE INSTRUCTIONS:

VERIFYING UPGRADE:

COMPLETING THE UPGRADE

References

Applies to:

Goal

Pillar Axiom: Standard Ax600/500/300 Software Upgrade from R4.x to R4.x

This document outlines the steps to update an Axiom 600/500/300 from Release 4.x to Release 4.x.

These minor upgrades are Non-Disruptive Upgrades (NDU) they do not need to stop the hosts connected to the Axiom however it is recommended to choose a time when the IO load is reduced as Slammer Software and/or Brick Firmware may be upgraded resulting in possible reduced performances when these components are updated.

A minor release update typically lasts less than 30 min providing that the code has been staged prior to the upgrade (see below)

Solution

PREREQUISITES:

Axiom Software Release 04.00.02 or higher, a lower version would require a reboot of the Axiom and would therefore not be a NDU.

Download the upgrade package in the Patch and Update section of MOS. For an minor upgrade, the zip file 1 of 3 is the one you need.
Please refer to <Document: 1422199.1> Pillar Axiom: How to Find Pillar Axiom firmware and patches in MOS

If you are running a version 4.2.17 or lower and using MaxRep Replication for NAS. Please make sure that no Replication process is running as the target File System could become unusable. Please Refer to the MaxRep Replication for NAS User's Guide and Reference  for more details.
If you are using AxiomOne Replication for SAN please make sure that the pair are isolated before upgrading. Please refer to the AxiomONE Replication Guide for SAN for details on how to isolate and resume replication pairs.
Replication documentation is available in the Axiom user interface in the section Support --> Technical Documentation

UPGRADE INSTRUCTIONS:

1. This step is optional but it is recommended to deactivate the call-home function during the upgrade to avoid sending false alerts to us and avoid log transfer that may load the pilot and slow down the upgrade process.
   Go in System --> Networking, Modify Network setting in the drop box. In the Callhome Tab, uncheck enable callhome and save.
2. Select the correct package for your current installed release and Axiom platform.
   R4.x upgrades will use Ax500_FN_040xxxx-00xxxx.tgz for Ax500 and Ax600_FN_040xxxx-00xxxx.tgz for Ax600.
3. Login as Administrator into Axiom Storage Manager GUI.
4. Click the Support icon in the top context pane.
5. Click the Software Components link in the left navigation pane.
6. Choose Update Software from the Actions drop-down list.
7. 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.
8. After the Staging completes, all components that are affected should be automatically selected for the administrator account.
9. 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 they must correspond to the version described in the Release note available via the [Read Me] button where you downloaded the package.

COMPLETING THE UPGRADE

After the software upgrade has completed it is required to update the compatibility matrix.

1. Select the correct compatibility matrix for your current installed release and Axiom platform.
   R4.x upgrades will use Ax500_NP_040xxxx-00xxNP.tgz for Ax500 and Ax600_NP_040xxxx-00xxNP.tgz for Ax600.
2. Upload the compatibility matrix package as you did for the upgrade package.
3. After the Staging completes, the compatibility matrix will be up to date
4. If you have deactivated call home, reactivate the option.

References

This solution has no attachment