HP Virtual Connect 8Gb 24-port Fibre Channel Module for c-Class BladeSystem - Manual (Page 149)

Configuring the Virtual Connect domain using the CLI 149
• Administratively Disabled—The port has been disabled by an administrative action, such as setting the
uplink port speed to ‘disabled.’
• Unpopulated—The port does not have an SFP module connected.
• Unrecognized—The SFP module connected to the port cannot be identified.
• Failed Validation—The SFP module connected to the port failed HPID validation.
• Smart Link—The Smart Link feature is enabled.
• Not Linked/Loop Protected—VCM is intercepting BPDU packets on the server downlink ports and has
disabled the server downlink port to prevent a loop condition.
• Linked/Uncertified—The port is linked to another port, but the connected SFP module is not certified by
HP to be fully compatible. In this case, the SFP module might not work properly. Use certified modules
to ensure server traffic.
Resetting the Virtual Connect Manager
To reset the Virtual Connect Manager, use the reset vcm command:
>reset vcm
>reset vcm [-failover]
Administrator privileges are required for this operation.
If VC Ethernet modules are configured for redundancy using a primary and backup Ethernet module, you can
use this feature to manually change which Virtual Connect Ethernet module hosts the Virtual Connect
Manager. You can also force the Virtual Connect Manager to restart without switching to the alternate Virtual
Connect Ethernet module. This feature can be useful when troubleshooting the Virtual Connect Manager. The
network and FC processing of the Virtual Connect subsystem is not disturbed during the restart or failover of
the Virtual Connect Manager.
If the command line option -failover is included in the reset vcm command and a backup Virtual
Connect Ethernet module is available, the command line displays the following message:
SUCCESS: The Virtual Connect Manager is being reset. Please wait...
You are logged out of the session after approximately 1 minute. An attempted login to the same Virtual
Connect Ethernet module is rejected with the following message:
Virtual Connect Manager not found at this IP address.
If you attempt to log in to the backup module, you might receive the following error message:
Unable to communicate with the Virtual Connect Manager. Please retry again
later.
The login should succeed after the Virtual Connect Manager restarts on the backup Virtual Connect Ethernet
module. Allow up to 5 minutes, depending on the enclosure configuration.
If the command line option -failover is not included in the reset vcm command or a backup Virtual
Connect Ethernet module is not available, the command line displays the following message:
SUCCESS: The Virtual Connect Manager is being reset. Please wait...
You are logged out of the session after approximately 1 minute. If you attempt to log in to the module again,
you might receive the following error message:
Unable to communicate with the Virtual Connect Manager. Please retry again
later.