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>
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.
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
).
5.
If you created the interface
bond1:0
in step 3, now set up the user network VIF, specifying
the user VIF IP address and VIF device used in step 3.
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
6.
Register the agile management console (also known as agile FM) to the cluster:
ibrix_fm –R <FM hostname> -I <local_cluster_ipaddr>
7.
From the agile management console, verify that the definition was set up correctly:
grep –i vif /etc/ibrix/fusion.xml
The output should be similar to the following:
<property name="fusionManagerVifCheckInterval" value="60"></property>
<property name="vifDevice" value="bond0:0"></property>
<property name="vifNetMask" value="255.255.254.0"></property>
NOTE:
If the output is empty, restart the fusionmanager services as in step 8 and then recheck.
8.
Restart the fusionmanager services:
/etc/init.d/ibrix_fusionmanager restart
NOTE:
It takes approximately 90 seconds for the agile management console to return to
optimal with the
agile_cluster_vif
device appearing in
ifconfig
output. Verify that
this device is present in the output.
9.
Install the file serving node software on the agile management console node:
ibrix/ibrixinit -ts -C <cluster_interface> -i <agile_cluster_VIF_IP_Addr>
For example:
ibrix/ibrixinit -ts -C eth4 -i 172.16.3.100
10.
Verify that the agile management console is active:
ibrix_fm –i
For example:
Performing the migration
65
Содержание StorageWorks X9320
Страница 97: ...13 When the Configure Network dialog box reappears select bond0 Configuring a file serving node manually 97 ...
Страница 108: ...Cabling diagrams Cluster network cabling diagram 108 System component and cabling diagrams ...
Страница 109: ...SATA option cabling Description Line SAS I O pathController A SAS I O pathController B Cabling diagrams 109 ...
Страница 144: ...English notice Estonian notice Finnish notice French notice 144 Regulatory compliance and safety ...
Страница 145: ...German notice Greek notice Hungarian notice Italian notice Waste Electrical and Electronic Equipment directive 145 ...
Страница 146: ...Latvian notice Lithuanian notice Polish notice Portuguese notice 146 Regulatory compliance and safety ...
Страница 147: ...Slovakian notice Slovenian notice Spanish notice Swedish notice Waste Electrical and Electronic Equipment directive 147 ...
