HP StoreAll Series Installation Manual page 118

-----------
r3r10-s1
r3r10-s2
r3r10-s5
r3r10-s6
Example of output after registration has stabilized.
[root@r3r10-s1 ~]# ibrix_server -l
SERVER_NAME
-----------
r3r10-s1
r3r10-s2
r3r10-s5
d. Compare the list of servers with errors from
ibrix_server
4. To recover a server that has failed to register:
a. Log in to the server, and enter the following command:
/usr/local/ibrix/bin/register_server
H /usr/local/ibrix
In this command, <SERVERHOSTNAME> is the host name of the server that failed to
register. For this example, the <SERVERHOSTNAME> is r3r10-s6.
<VIFIPADDRESS> is the cluster virtual management IP address that was entered in the
Management IP field of the Cluster Settings screen. For this example, the
<VIFIPADDRESS> is 10.103.10.201 in
<VIFIPADDRESS> can be accessed from Cluster Settings on the Getting Started screen.
The following example shows the command and its output with these entries:
[root@r3r10-s6 ~]# /usr/local/ibrix/bin/register_server -p 10.103.10.201 -c bond0 -H /usr/local/ibrix
-a none -n r3r10-s6
iadconf.xml does not exist...creating new config.
Registering Segment Server r3r10-s6 with cluster r3r10_s1s2s5s6
wrote /etc/ibrix/iadconf.xml
command successful
b. Confirm that the server successfully registered by locating the iadconf.xml file in the
/etc/ibrix directory.
The following example shows the output with the iadconf.xml file listed in the /etc/
ibrix directory directory.
[root@r3r10-s6 ~]# cd /etc/ibrix
[root@r3r10-s6 ibrix]# ll
total 40
drwxr-xr-x 2 root root 4096 Jan 14 20:40 appliance
drwxr-xr-x 2 root root 4096 Jan 14 20:43 engine
-rw-r--r-- 1 root root 4274 Jan 14 21:36 fminstance.xml
drwxr-xr-x 2 root root 4096 Jan 14 23:24 fusion
-rw-r--r-- 1 root root 8482 Jan 14 23:24 fusion.xml
-rw-r--r-- 1 root root 2196 Jan 14 23:23 iadconf.xml
-rw-r--r-- 1 root root
1 18 Configuring clusters remotely with the Getting Started Wizard
----------
Up
Up
Up
Registered
STATE
----------
Up
Up
Up
l command. Do one of the following:
If the server with the error is not in the ibrix_server
register. It may be possible to recover from this condition by re-registering the servers.
To do so, select Next from the File Servers screen. If the retry does not register all of
the servers, use the procedure in
If the server with the error is in the ibrix_server
partial registration error. Use the procedure in
------ ------------
3 0.00
1 0.00
1 0.00
N/A N/A
CPU(%) NET_IO(MB/s)
------ ------------
3 0.00
1 0.00
1 0.00
Step 3.c
Step 4 to recover from the error.
a none n <SERVERHOSTNAME>
Figure 44 (page
121 Jan 14 20:48 launcher.properties
------------- ------
0.00
0.00
0.00
N/A
DISK_IO(MB/s) BACKUP
------------- ------
0.00
0.00
0.00
against the output from the
l list, the server failed to
l list, the server failed with a
Step 5 to recover from the error.
p <VIFIPADDRESS> -c bond0
117).
--
off
off
off
off
HA
--
off
off
off