10 Migrating to an agile management console configuration
The agile management console configuration provides one active management console and one
passive management console installed on different file serving nodes in the cluster. The migration
procedure configures the current Management Server blade as a host for an agile management
console and installs another instance of the agile management console on a file serving node.
After completing the migration to the agile management console configuration, you can use the
original Management Server blade as follows:
•
Use the blade only as a host for the agile management console.
•
Convert the blade to a file serving node (to support high availability, the cluster must have an
even number of file serving nodes). The blade can continue to host the agile management
console.
To perform the migration, the X9000 installation code must be available. As delivered, this code
is provided in
/tmp/X9720/ibrix
. If this directory no longer exists, download the installation
code from the HP support website for your storage system.
IMPORTANT:
The migration procedure can be used only on clusters running HP X9000 File
Serving Software 5.4 or later.
Backing up the configuration
Before starting the migration to the agile management console configuration, make a manual
backup of the management console configuration:
ibrix_fm -B
The resulting backup archive is located at
/usr/local/ibrix/tmp/fmbackup.zip
. Save a
copy of this archive in a safe, remote location, in case recovery is needed.
Performing the migration
Complete the following steps on the blade currently hosting the management console:
1.
The agile management console uses a virtual interface (VIF) IP address to enable failover and
prevent any interruptions to file serving nodes and X9000 clients. The existing cluster NIC IP
address becomes the permanent VIF IP address. Identify an unused IP address to use as the
Cluster NIC IP address for the currently running management console.
2.
Disable high availability on the server:
ibrix_server –m -U
3.
Using
ssh
, connect to the management console on the user network if possible.
•
Edit the
/etc/sysconfig/network-scripts/ifcfg-bond0
file. Change the IP
address to the new, unused IP address and also ensure that
ONBOOT=Yes
.
•
If you have preferred X9000 clients over the user
bond1
network, edit the
/etc/
sysconfig/network-scripts/ifcfg-bond1
file. Change the IP address to another
unused, reserved IP address.
Run one of the following commands:
/etc/init.d/network restart
service network restart
Verify that you can ping the new local IP address.
4.
Configure the agile management console:
ibrix_fm -c <cluster_VIF_addr> -d <cluster_VIF_device> –n <cluster_VIF_netmask> -v cluster -I
<local_cluster_IP_addr>
Backing up the configuration
67
Содержание StorageWorks X9720
Страница 137: ...13 When the Configure Network dialog box reappears select bond0 Configuring a file serving node 137 ...
Страница 178: ...English notice Estonian notice Finnish notice French notice 178 Regulatory compliance and safety ...
Страница 179: ...German notice Greek notice Hungarian notice Italian notice Waste Electrical and Electronic Equipment directive 179 ...
Страница 180: ...Latvian notice Lithuanian notice Polish notice Portuguese notice 180 Regulatory compliance and safety ...
Страница 181: ...Slovakian notice Slovenian notice Spanish notice Swedish notice Waste Electrical and Electronic Equipment directive 181 ...