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
• Management console GUI. You will need to reconnect to the management console VIF after the
failover.
Failing over the management console manually
To fail over the active management console manually, place the console into maintenance mode.
Enter the following command on the node hosting the console:
ibrix_fm -m maintenance
The command takes effect immediately.
The failed-over management console remains in maintenance mode until it is moved to passive mode
using the following command:
ibrix_fm -m passive
A management console cannot be moved from maintenance mode to active mode.
Viewing information about management consoles
To view mode information, use the following command:
ibrix_fm –i
NOTE:
If the management console was not installed in an agile configuration, the output will report
FusionServer: fusion manager name not set! (active, quorum is not
configured).
When a management console is installed, it is registered in the management console configuration.
To view a list of all registered management consoles, use the following command:
ibrix_fm –f
Cluster high availability
X9000 Software High Availability keeps your data accessible at all times. Failover protection can be
configured for file serving nodes, network interfaces, individual segments, and HBAs. Through physical
and logical configuration policies, you can set up a flexible and scalable high availability solution.
X9000 clients experience no changes in service and are unaware of the failover events.
Failover modes
High Availability has two failover modes: the default manual failover and the optional automated
failover. A manual failover uses the ibrix_server command or the management console GUI to
fail over a file serving node to its standby. The server can be powered down or remain up during the
procedure. Manual failover also includes failover of any network interfaces having defined standbys.
You can perform a manual failover at any time, regardless of whether automated failover is in effect.
Automated failover allows the management console to initiate failover when it detects that
standby-protected components have failed. A basic automated failover setup protects all file serving
nodes. A comprehensive setup also includes network interface monitoring to protect user network
interfaces and HBA monitoring to protect access from file serving nodes to storage via an HBA.
Configuring failover26