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
[root@x109s3 ibrix]# ibrix_fm -i
FusionServer: x109s3 (passive, quorum is running)
=============================
Command succeeded
Removing the dedicated Management Server
This procedure removes the dedicated Management Server machine from the cluster and installs
another instance of the agile management console on a second file serving node.
Complete the following steps:
1. On the Management Server machine, place the agile management console into maintenance
mode:
ibrix_fm -m maintenance
2. Verify that the management console is in maintenance mode:
ibrix_fm –i
For example:
[root@x109s1 ibrix]# ibrix_fm -i
FusionServer: x109s1 (maintenance, quorum not started)
==================================
Command succeeded!
Verify that the passive management console has become the active management console. Run
the ibrix_fm -i command on the file serving node hosting the passive management console
(x109s3 in this example). It may take up to two minutes for the passive management console to
become active.
For example:
[root@x109s3 ibrix]# ibrix_fm -i
FusionServer: x109s3 (active, quorum is running)
=============================
Command succeeded!
At this point, the ibrix_fm -f command reports two agile management consoles, the passive
console on the Management Server (x109s1) and the active console on the file serving node
(x109s3).
[root@x109s3 ibrix]# ibrix_fm -f
NAME IP ADDRESS
------ ----------
x109s1 172.16.3.100
x109s3 172.16.3.3
Command succeeded!
3. Uninstall the management console from the Management Server machine:
/ibrix/ibrixinit -tm -U
4. Verify that the uninstalled management console is no longer registered. Run the following command
from the file serving node hosting the newly active management console:
ibrix_fm -f
The command should now report only the agile management console on the file serving node.
[root@x109s3 ibrix]# ibrix_fm -f
NAME IP ADDRESS
------ ----------
Migrating to an agile managment console configuration72