10. Restart the Fusion Manager services by entering the following command:
[root@X9720 ~]#service ibrix_fusionmanager restart
Stopping Fusion Manager Daemon [ OK ]
Starting Fusion Manager Daemon [ OK ]
11. Run the following command, which ensures the node does not enter configuration mode upon
the next login:
rm -rf .run_wizard
12. Complete the following verifications:
a.
Verify that the server is added to the cluster on the Fusion Manager node by entering the
following command:
[root@r150s16 ~]#ibrix_server -l
The command displays the servers on the cluster.
SERVER_NAME STATE CPU(%) NET_IO(MB/s) DISK_IO(MB/s) BACKUP HA
----------- ----- ------ ------------ ------------- ------ --
r150b15 Up 0.01 0.00 off
r150s16 Up 1 0.01 0.00 off
b.
Verify that the network devices are up.
[root@r150s16 ~]#ibrix_nic -l
The following output is displayed:
iLO remote console does not respond to keystrokes
You need to use a local terminal when performing a recovery because networking has not yet
been set up. Occasionally when using the iLO integrated remote console, the console will not
respond to keystrokes.
To correct this situation, remove and reseat the blade. The iLO remote console will then respond
properly. Alternatively, you can use a local KVM to perform the recovery.
The ibrix_auth command fails after a restore
If the
ibrix_auth
command fails after a QR restore of a server in a cluster with a message similar
to the following:
ibrix_auth -n IBRQA1.HP.COM -A [email protected] -P password
-h hostnameX
nl
Iad error on host hostnameX failed command (<HIDDEN_COMMAND>) status
(1) output: (Joining to AD Domain:IBRQA1.HP.COM With Computer DNS Name:
hostsnameX.ibrqa1.hp.com )
Verify that the content of the
/etc/resolve.conf
file is not empty. If the content is empty, copy
the contents of the
/etc/resolve.conf
file on another server to the empty
resolve.conf
file.
Troubleshooting
169