displayed. This situation could be caused by network inconsistencies or an outage. Usually a
network outage lasts only a few minutes. Try relaunching the wizard and revisiting this page.
If the operation continues to fail, use the text-based installation method to form the cluster.
Server registration fails with “Error: Registering server” or “Error: Passive FM”
Probable cause:
•
The operation failed when checking and configuring network details for a passive server.
•
The hostname is not valid and cannot be reached.
•
The operation failed when registering the server with the active Fusion Manager.
•
The operation failed when setting passive mode on the server.
•
The operation failed when setting nofailover mode on the server.
•
The operation failed when restarting the Fusion Manager.
•
The operation failed because of a timeout or other condition.
Troubleshooting steps:
1.
Try to ping the server. If the server cannot be reached, the network settings on that server may
have failed. This can be due to temporary connectivity conditions. Try using the iLO to assign
network details such as the IP address and hostname and then launch the wizard again. If
connectivity is restored, the server will be discovered as already configured, and it can be
used to form the cluster.
2.
Check the status of the Fusion Manager registration on the primary server:
ibrix_fm –i
If the output is
FusionServer: fusion manager name not set! (active, quorum
is not configured)
and the output of
ibrix_fm –l
is empty, use the following command
to perform the Fusion Manager registration:
ibrix_fm -R hostname -I ipaddress
3.
Run the
ibrix_server –l
command. If there is no output, use the following command to
register the segment server:
/usr/local/ibrix/bin/register_server -p -c bond0 -n <hostname> -a
none -H /usr/local/ibrix <VIF IP address>
4.
Restart the server:
/usr/local/ibrix/bin/init/ibrix_server start
Alternatively, you can use the text-based installation method to perform the registration, but you
will need to enable the HA configuration after the registration is complete.
If the registration continues to fail, there may be a network inconsistency or outage. A network
outage usually lasts only a few minutes. If the operation continues to fail, contact your network
administrator.
An HA pair cannot be configured
Probable cause:
•
Network configuration failed on the server.
•
The command timed out.
Troubleshooting steps:
•
Try to ping the server. If you cannot reach the server, the network settings on the server may
have failed. This can be due to temporary connectivity conditions. Use the iLO to assign
Troubleshooting the Getting Started Wizard
39
