5.5 HP StorageWorks X9300 Network Storage Gateway Administrator Guide (AW539-96007, March 2011)
Table Of Contents
- X9300 Network Storage Gateway Administrator Guide
- Contents
- 1 Product description
- 2 Getting started
- 3 Configuring virtual interfaces for client access
- 4 Configuring failover
- 5 Configuring cluster event notification
- 6 Configuring system backups
- 7 Creating hostgroups for X9000 clients
- 8 Monitoring cluster operations
- 9 Maintaining the system
- Shutting down the system
- Starting the system
- Powering file serving nodes on or off
- Starting and stopping processes
- Tuning file serving nodes and X9000 clients
- Migrating segments
- Removing storage from the cluster
- Maintaining networks
- Viewing network interface information
- 10 Migrating to an agile managment console configuration
- 11 Upgrading the X9000 Software
- 12 Licensing
- 13 Upgrading firmware
- 14 Troubleshooting
- 15 Replacing components
- 16 Recovering a file serving node
- 17 Support and other resources
- A Component and cabling diagrams
- B Spare parts list
- C Warnings and precautions
- D Regulatory compliance and safety
- Glossary
- Index
2. On the current active management console, move the <installer_dir>/ibrix directory
used in the previous release installation to ibrix.old. For example, if you expanded the tarball
in /root during the previous X9000 installation on this node, the installer is in /root/ibrix.
3. On the current active management console, expand the distribution tarball or mount the distribution
DVD in a directory of your choice. Expanding the tarball creates a subdirectory named ibrix
that contains the installer program. For example, if you expand the tarball in /root, the installer
is in /root/ibrix.
4. Change to the installer directory on the active management console, if necessary. Run the following
command:
./auto_ibrixupgrade
The upgrade script performs all necessary upgrade steps on every server in the cluster and logs
progress in the upgrade.log file. The log file is located in the installer directory.
5. Upgrade X9000 clients. See Upgrading Linux X9000 clients, page 88 and Upgrading Windows
X9000 clients, page 89.
6. If you received a new license from HP, install it as described in the “Licensing” chapter in this
guide.
Manual upgrades
Upgrade paths
There are two manual upgrade paths: a standard upgrade and an agile upgrade.
• The standard upgrade is used on clusters having a dedicated Management Server machine or
blade running the management console software.
• The agile upgrade is used on clusters having an agile management console configuration, where
the management console software is installed in an active/passive configuration on two cluster
nodes.
To determine whether you have an agile management console configuration, run the ibrix_fm -i
command. If the output reports the status as quorum is not configured, your cluster does not
have an agile configuration.
Be sure to use the upgrade procedure corresponding to your management console configuration:
• For standard upgrades, use Standard upgrade for clusters with a dedicated Management Server
machine or blade, page 77.
• For agile upgrades, use Agile upgrade for clusters with an agile management console configura-
tion, page 81.
NOTE:
If you are using a dedicated Management Server and want to convert to an agile management console
configuration, see Chapter 10. Complete the migration first, and then perform the upgrade using the
agile upgrade procedure.
Online and offline upgrades
Online and offline upgrade procedures are available for both the standard and agile upgrades:
• Online upgrades. This procedure upgrades the software while file systems remain mounted. Before
upgrading a file serving node, you will need to fail the node over to its backup node, allowing
Upgrading the X9000 Software76