HP Virtual Connect Manager Command Line Interface Version 2.30 User Guide

Configuring the Virtual Connect domain using the CLI 89
Operation Examples
Display server profiles
Summary display
>show profile
Detailed display
>show profile *
Single profile display
>show profile MyProfile
Delete the domain configuration
>delete domain
Update interconnect module firmware
>update firmware
url=http://www.mywebserver.com/images/vc-
1.31.rom
Force a failover to the standby VC Manager
>reset vcm - failover
Power off server blades
>poweroff server enc0:2
>poweroff server 3
>poweroff server *
Power on server blades
>poweron server enc0:1
>poweron server 2
>poweron server *
Reset a server blade
>reboot server enc0:4
>reboot server 6
>reboot server *
Unassign a server profile from a device bay
>unassign profile MyProfile
Modify Ethernet network connection properties
>set enet-connection MyProfile 1
pxe=disabled
Modify FC fabric connections
>set fc-connection MyProfile 2 speed=auto
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 installed in I/O bays 1 and 2 of the enclosure, the user can manually change
which Virtual Connect Ethernet Module is hosting the Virtual Connect Manager through the use of this
feature. 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 module is available in the alternate I/O bay (I/O Bays 1 and 2 can host the Virtual Connect
Manager), the command line displays the 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 message: