Pillar Axiom 600 Storage System
 
Pillar Axiom 500 Storage System
 

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

In this Document

Goal

Solution

References

Created from <SR 3-5469430816>

Applies to:

Goal

The purpose of this document is to outline code upgrade procedures for Axiom Systems already running R5.x to a newer version of R5.x. This upgrade is an NDU (Non-Disruptive Upgrade) for configurations with 1 or 2 Slammers.  Axiom configurations with 3 or 4 Slammers may require an outage, see Prerequisites below.

Solution

Prerequisites/Planning for an R5.x to R5.x upgrade:

• • Axiom must already be running R5.
    
    

  • For upgrades that start at R5.3 or below, this is a disruptive upgrade for Axiom configurations with 3 or 4 Slammers. An outage is required (unpublished <Bug 14788300>).  Axioms already running R5.4 and upgrading to a higher release are unaffected and the upgrade is NDU.

  • R5.x does not support NAS protocols.

  • R5.2 implements no feature licenses. All features are licensed with the Axiom.

  • Upgrade from any R5.x release to any higher R5.x release are performed with a hardware independent single rpm package. There is no separate compatibility matrix package.

  • Axiom system must be functioning normally (Green) to be updated. If the Axiom shows a status of Warning (Yellow) or Critical (Red) you must take action to return the system to a healthy, normal status prior to attempting the Upgrade.

  • Any System Alerts should be resolved prior to attempting the Upgrade. 

Preliminary actions:

• • Verify the Installed Software version. Using the AxiomONE Storage Services Manager GUI, select the Support tab and then Software Modules in the navigation pane to view the installed version on the Axiom in the upper box of the main pane.

  • Compare to the latest version available. See <Document 1558848.1> ”Pillar Axiom: Current Recommended Software Versions” for details.
    
    

  • Review the Release Notes for the version you want to install (Release Notes are linked in a table in <Document 1558848.1> under Software Version).

Open a Service Request in MOS (My Oracle Support) for the upgrade. This is to done to track upgrades and to have an identified point of contact in case of any problems. Uploading a current log bundle is also part of this process. See <Document 1906876.1> “Pillar Axiom: How to Collect a System Information Log and Transfer it to Oracle” for details.

 Stage and Upgrade with the latest version:

• • Obtain the appropriate version for your needs. See <Document 1422199.1> “How to find Pillar Axiom firmware and patches in My Oracle Support”.

  • Disable Call Home. See <Document 1535352.1> “How to Disable Call Home to Prevent Automatic Service Request ASR Generation”.
    
    During the upgrade process components will be rebooted to enable the new versions of software/firmware being installed. These reboots may generate invalid Service Requests. Temporarily disabling Call-Home will prevent these from happening.

  • Stage the software onto the active Pilot.
    
    Once the appropriate software has been downloaded from MOS, you will need to stage (upload) it to the active Pilot. This is done from the AxiomONE Storage Services Manager GUI. After logging into the GUI, select the Support Tab and then Software Modules and then selecting the Upload Software Package button:
    
    
    
    When completed, the Staged Software area at the bottom will reflect the new Software version.
    
    

Upgrade the Software:

After the new software has been staged on the Pilot, you can now do the actual upgrade. Select Action from the menu bar and then Upgrade Software to get the following pop-up window:



If you want the upgrade to be NDU, confirm that the “Update software without restarting system” radio button is selected. Do NOT check any of the boxes in the “Software Update Options” pane unless specifically instructed to do so by Oracle Support.

 Monitor the Upgrade:

To verify that the update is occurring, click the “Communication Details” icon at the right of the Status bar. A list of recent and current requests received by the Axiom will be displayed. If the Axiom is processing a request called Perform Upgrade, then the upgrade is taking place. The System Status icon at the left of the Status bar provides an indication that an update is being performed. Place the mouse over the icon to view this message.

You can also click the Tasks button on the Status bar to display a window listing the background processes that are running or have recently completed. You should see an entry for the update process.

During an NDU the system IO will not be interrupted. After the software and firmware are updated, the Pilot shuts down and restarts. When the Pilot shuts down, the connection between the Axiom and the AxiomONE Storage Services Manager GUI will break. A message stating that the connection has been lost will be displayed, followed by the login panel from which you can log back in.

After you log back in, the update may still be in progress. Select the Monitor tab in the navigation pane and click Status Summary to view the status of the Pilot, Slammers and Bricks.

Verify the Upgrade:

To verify that the update was successful, view the Event Log. It should show each step of the update and its successful completion. In the Monitor tab, click Status Summary in the navigation pane and verify that the Pilot, Slammers and Bricks all report normal (Green) status.

Re-enable Call Home. See <Document 1535352.1> “How to Disable Call Home to Prevent Automatic Service Request ASR Generation”.

         Post Upgrade Actions:

         It will be required to now download and install a new Axiom Storage Services Manager application for your host to match the revision of software which was upgraded on the Axiom.

       To do this, open a browser and enter the Axiom IP address into the browswer address bar and hit enter.

       From the Pillar Axiom Software screen, select the Management Software section, and download and install one of the appropriate windows packages.

References

This solution has no attachment