HP BladeSystem c-Class Virtual Connect Support Utility Version 1.7.0 Release Notes

Important notes and recommendations 4
Important notes and recommendations
• IMPORTANT: If you have FCoE connections configured through a mezzanine card, please read the
"Known issues" section for an important workaround required to avoid a temporary FCoE outage
during firmware update.
• For upgrading to VC 3.00 or later, the embedded Virtual Connect GUI and CLI FW update options
have been removed. VCSU is the only stand alone method of FW update.
• HP strongly recommends running the healthcheck option on an enclosure before performing any
management tasks. These tasks include, but are not limited to, the following:
o Onboard Administrator firmware upgrade
o Virtual Connect firmware upgrade
o Onboard Administrator planned failover
o Virtual Connect planned failover
• When entering an OA user name from a Linux command shell with the domain\username format, use
quotation marks around the username so it is not expanded by the Linux shell.
Example:
vcsu -a collect -i 128.88.142.141 -u "dvt\ldapuser" -p hp123
• When entering an OA user password interactively with password masking from a Linux command shell,
use quotation marks around the asterisk so it is not expanded by the Linux shell.
Example:
vcsu -a version -i 192.168.1.100 -u Administrator -p "*"
OA Password :***********
Manual activation
Use the following steps for manual activation of VC firmware:
1. Determine which module is the Primary and which is Standby using the VCM CLI show
interconnect command or by executing VCSU with the -healthcheck option.
2. In the base enclosure (ENC0), reset the module identified as the Standby module.
3. Wait for the checkpoint to complete. You can view this within VCM or you can run VCSU with the
-healthcheck option to see that the Domain configuration is "In Sync" on all the modules.
4. Force a failover of VCM from the Primary to the Standby module by selecting Reset VCM from the Tools
pull-down menu and then selecting the checkbox to Force failover.
5. Wait for the Standby module to become Primary and for the checkpoint to complete. (See step 3
above).
6. In the base enclosure (ENC0), reset the module that was the original Primary module, but currently is the
Standby module.
7. Wait for checkpoint to complete. You can view this within VCM or you can run VCSU with the
-healthcheck option to see that the Domain configuration is "In Sync" on all the modules.