HP Virtual Connect for c-Class BladeSystem Setup and Install Guide Version 3.70 and 3.75

HP Virtual Connect Manager 54
• The attempted IP sign-in address is not valid for the specified account.
• The attempted IP sign-in address is for a VC-Enet module not running the primary VCM.
• The browser settings are incorrect. See "Configuring browser support (on page 50)."
• You have entered an invalid role or authentication service name.
• Authentication service is disabled, is not correctly configured, or is not up in the server.
About HP Virtual Connect Manager
To view detailed product information, select About HP Virtual Connect Manager from the Help pull-down
menu.
Reset Virtual Connect Manager
You must have domain privileges to reset VCM. In a multi-enclosure environment, the VC-Enet modules in
bays 1 and 2 of the local enclosure host VCM. With VC 3.10 and higher, the primary modules can be in
bays other than 1 and 2.
To reset VCM running on the primary VC-Enet module, select Reset Virtual Connect Manager from the Tools
pull-down menu. The Reset Virtual Connect Manager screen appears.
• If the Force Failover checkbox is selected and a VC-Enet module is available in the alternate
interconnect bay, the GUI is redirected to the alternate VC-Enet module for log on after the VCM has
restarted. Reset times depend on the size and complexity of the VC domain configuration.
• If the Force Failover checkbox is not selected or a VC-Enet module is not available in the alternate
interconnect bay, the VCM restarts on the current VC-Enet module, and you are presented the logon
screen for the current VC-Enet module after VCM restarts. Reset times depend on the size and
complexity of the VC domain configuration.
When resetting the VC-Enet module, VCM is temporarily unavailable. If failover is specified and a backup
VC-Enet module is available, you are logged off and redirected to the backup VC-Enet module IP address.
Recovering remote enclosures
The credentials of the remote enclosure must be restored in the following situations:
• A previously saved configuration file is restored
• The Onboard Administrator is reset to factory defaults
• The Onboard Administrator associated with the remote enclosure is replaced
If the IP link between the local enclosure Onboard Administrator and the remote enclosure Onboard
Administrator is lost, the remote enclosure is also marked as NO-COMM. If IP connectivity is lost, credential
recovery is not required. The enclosure automatically recovers after connectivity is returned.