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
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. Then reconfigure the cluster and
user networks:
• 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 are using 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
If you are not at the local terminal you might have to reconnect using the new IP address. The
following example shows the syntax for creating the agile management console cluster VIF
(bond0:1) and, if using X9000 clients, the agile management console user VIF (bond1:0).
ifconfig bond0:1 172.16.3.1
ifconfig bond1:0 10.30.83.1
2. Configure the agile management console:
ibrix_fm -c <cluster_IP_addr> -d <cluster_VIF_device> –n
<cluster_VIF_netmask> -v cluster -I <local_IP_addr>
For example:
[root@x109s1 ~]# ibrix_fm -c 172.16.3.1 -d bond0:1 -n 255.255.248.0 -v cluster
-I 172.16.3.100
Command succeeded!
The original cluster IP address is now configured to the newly created cluster VIF device (bond0:1).
3. If you are using X9000 clients and you created the interface bond1:0 in step 1, now set up the
user network VIF, specifying the user VIF IP address and VIF device used in step 1.
NOTE:
This step does not apply to CIFS/NFS clients. If you are not using X9000 clients, you can skip
this step.
Set up the user network VIF:
ibrix_fm -c <user_VIF_IP> -d <user_VIF_device> -n <user_VIF_netmask>
-v user
For example:
[root@x109s1 ~]# ibrix_fm -c 10.30.83.1 -d bond1:0 -n 255.255.0.0 -v user
Command succeeded
4. Restart the Fusionmanager services:
/etc/init.d/ibrix_fusionmanager restart
5. If the Management Server is currently running X9000 Software 5.4 or 5.4.1, skip this step. If the
Management Server is currently running X9000 Software 5.5, install the file serving node software
on the management server:
./ibrixinit -ts -C <local_cluster_Iface_device> -I
<cluster_VIF_IP_Addr> -F
Migrating to an agile managment console configuration70