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
file system access to continue. This procedure cannot be used for major upgrades, but is appropriate
for minor and maintenance upgrades.
• Offline upgrades. This procedure requires that you first unmount file systems and stop services.
(Each file serving node may need to be rebooted if NFS or CIFS causes the unmount operation to
fail.) You can then perform the upgrade. Clients will experience a short interruption to file system
access while each file serving node is upgraded.
Standard upgrade for clusters with a dedicated Management Server machine
or blade
Use these procedures if your cluster has a dedicated Management Server machine or blade hosting
the management console software. The X9000 Software 5.4.x to 5.5 upgrade can be performed
either online or offline. Future releases may require offline upgrades.
NOTE:
Be sure to read all instructions before starting the upgrade procedure.
Standard online upgrade
The management console must be upgraded first. You can then upgrade file serving nodes and X9000
Clients in any order.
Upgrading the management console
Complete the following steps on the Management Server machine or blade:
1. Disable automated failover on all file serving nodes:
<ibrixhome>/bin/ibrix_server -m -U
2. Verify that automated failover is off:
<ibrixhome>/bin/ibrix_server -l
In the output, the HA column should display off.
3. Move the <installer_dir>/ibrix directory used in the previous release installation to ib-
rix.old. For example, if you expanded the tarball in /root during the previous X9000 install-
ation on this node, the installer is in /root/ibrix.
4. Expand the distribution tarball or mount the distribution DVD in a directory of your choice. Ex-
panding 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.
5. Change to the installer directory if necessary and run the upgrade:
./ibrixupgrade -f
6. Verify that the management console is operational:
/etc/init.d/ibrix_fusionmanager status
The status command should report that the correct services are running. The output is similar
to this:
Fusion Manager Daemon (pid 18748) running...
7. Check /usr/local/ibrix/log/fusionserver.log for errors.
X9300 Network Storage Gateway Administrator Guide 77