1 Migrating To An Agile Fusion Manager Configuration; Backing Up The Configuration; Performing The Migration - HP IBRIX X9720 System Administrator Manual

1 1 Migrating to an agile Fusion Manager configuration

The agile Fusion Manager configuration provides one active Fusion Manager and one passive
Fusion Manager installed on different file serving nodes in the cluster. The migration procedure
configures the current Management Server blade as a host for an agile Fusion Manager and installs
another instance of the agile Fusion Manager on a file serving node. After completing the migration
to the agile Fusion Manager configuration, you can use the original Management Server blade
as follows:
Use the blade only as a host for the agile Fusion Manager.
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 Fusion Manager.
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:
Serving Software 5.4 or later.

Backing up the configuration

Before starting the migration to the agile Fusion Manager configuration, make a manual backup
of the Fusion Manager 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 Fusion Manager:
1. The agile Fusion Manager 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 Fusion Manager:
ibrix_fm -c <cluster_VIF_addr> -d <cluster_VIF_device> –n <cluster_VIF_netmask> -v cluster -I
<local_cluster_IP_addr>
In the command, <cluster_VIF_addr> is the old cluster IP address for the original
management console and <local_cluster_IP_addr> is the new IP address you acquired.
The migration procedure can be used only on clusters running HP X9000 File
Backing up the configuration 91