Reset virtual connect manager, Recovering remote enclosures – HP Integrity BL860c i2 Server-Blade User Manual
Page 21
HP Virtual Connect Manager 21
Reset Virtual Connect Manager
Users must have Administrative privileges to reset the Virtual Connect Manager. In a multi-enclosure
environment, the Ethernet modules in bays 1 and 2 of the primary enclosure host the Virtual Connect
Manager.
To reset the Virtual Connect Manager application running on the primary Virtual Connect Ethernet
module, select Reset Virtual Connect Manager from the Tools pull-down menu. The Reset Virtual Connect
Manager screen is displayed.
•
If the Force Failover checkbox is selected and a Virtual Connect Ethernet module is available in the
alternate interconnect bay (interconnect Bays 1 and 2 can host the Virtual Connect Manager), the
GUI counts down from 90 seconds. Then the GUI is redirected to the alternate Virtual Connect
Ethernet module for logon after the Virtual Connect Manager has restarted.
•
If the Force Failover checkbox is not selected or a Virtual Connect Ethernet module is not available in
the alternate interconnect bay, the GUI counts down from 90 seconds, the Virtual Connect Manager
restarts on the current Virtual Connect Ethernet Module, and the user is presented the logon screen
for the current Virtual Connect Ethernet module after the Virtual Connect Manager has restarted.
When resetting the Virtual Connect Ethernet module, Virtual Connect Manager is temporarily unavailable
to the user. If failover is specified and a standby Virtual Connect Ethernet module is available, users are
logged off and must reconnect using the standby Virtual Connect Ethernet module IP address.
Recovering remote enclosures
If a previously saved configuration file is restored, the OA is reset to factory defaults, or the OA
associated with the remote enclosure is replaced, then the credentials of the remote enclosure must be
restored. If the IP link between the primary enclosure OA and the remote enclosure OA is lost, the remote
enclosure is also marked as NO-COMM. Ensure network connectivity before attempting credentials
recovery.