HP 1.10GB Virtual Connect Ethernet Module for c-Class BladeSystem - Manual (Page 217)

Maintenance and troubleshooting 217
• Directory listings
• Boot Loader environment variables
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 VCM 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.
Server profile troubleshooting
In some cases, server profiles can be assigned to server blades when certain mismatches exist between the
server profile definition and the server blade. The following list summarizes Virtual Connect behavior under
these circumstances:
• If the number of network connections in the profile is more than the number of physical Ethernet ports,
the profile is assigned.
• If a switch other than a Virtual Connect Ethernet switch is connected to any port in the profile, the profile
is assigned, but the MAC address is not changed on the NIC. The connections display a status of “Not
mapped” when viewing the profile.
• If the number of Fibre Channel connections in the profile is more than the number of physical Fibre
Channel HBA ports, the profile is assigned, but the connections display a status of “Not mapped” when
viewing the profile.