Completing the restore on the dedicated (non-agile) Management Server
1.
Ensure that you have root access to the management console. The restore process sets the root
password to
hpinvent
, the factory default.
2.
Run the
exds_stdiag
command from the just restored server. You should be able to see the
shared storage, just as you can from the other server blades in the chassis.
3.
Disable the
microcode_ctl
service:
chkconfig microcode_ctl off
4.
The QuickRestore DVD enables the
iptables
firewall. Either make the firewall configuration
match that of your other server blades to allow traffic on appropriate ports, or disable the
service entirely by running the
chkconfig iptables off
and
service iptables
stop
commands.
To allow traffic on appropriate ports, open the following ports:
•
80
•
443
•
1234
•
9000
•
9005
•
9008
•
9009
5.
Use the AutoPass GUI to reinstall your license. For more information, see the “Licensing”
chapter in the HP StorageWorks X9000 File Serving Software User Guide.
6.
Ensure that you have root access to the management console. The restore process sets the root
password to
hpinvent
, the factory default.
7.
Stop all X9000 Software services on the replacement management console machine:
# /etc/init.d/ibrix_fusionmanager stop
8.
Obtain the latest
fmbackup.zip
backup file. (See
“Backing up the management console
configuration” (page 42)
for more information.) Place the zip file in the
$IBRIXHOME/tmp
directory.
9.
Restart X9000 Software services to unzip the
fmbackup.zip
file and import the configuration:
# /etc/init.d/ibrix_fusionmanager start
10. If quotas were in effect before running the recovery process, restore them:
# <installdirectory>/bin/ibrix_edquota -r
11. Copy the
/etc/hosts
file from a working file serving node to the newly restored server.
12. Ensure that all servers have server hostname entries in
/etc/machines
on all nodes.
13. Run
ibrix_health -l
and verify that no errors are being reported.
Troubleshooting
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.
Troubleshooting
147
