HP Virtual Connect Manager Command Line Interface Version 3.00 User for Integrity BL8x0c i2 Server Blades Guide

Configuring the Virtual Connect domain using the CLI 112
>reset vcm
>reset vcm [-failover]
Administrator privileges are required for this operation.
If VC Ethernet Modules are configured for redundancy using a primary and secondary Ethernet module,
the user can use this feature to manually change which Virtual Connect Ethernet Module hosts the Virtual
Connect Manager. The feature 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 Virtual Connect
Ethernet secondary module is available, the command line displays the following message:
SUCCESS: The Virtual Connect Manager is being reset. Please wait...
The user is 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 the user attempts to log in to the secondary I/O bay, they might receive the following error message
during the attempted login:
Unable to communicate with the Virtual Connect Manager. Please retry
again later.
The login should succeed after the Virtual Connect Manager has restarted on this secondary 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 Virtual Connect
Ethernet module is not available in the alternate I/O bay, the command line displays the following
message:
SUCCESS: The Virtual Connect Manager is being reset. Please wait...
The user is logged out of the session after approximately 1 minute. If the user attempts to re-login, they
might receive the following error message during the attempted login:
Unable to communicate with the Virtual Connect Manager. Please retry
again later.
The login should succeed after the Virtual Connect Manager has restarted. Allow up to 5 minutes,
depending on the enclosure configuration.