HP Virtual Connect Enterprise Manager 6.2 Release Notes
Table Of Contents
- Table of Contents
- HP Virtual Connect Enterprise Manager Overview
- Supported VCEM components
- Minimum versions of supported platforms
- Enhancements
- Prerequisites
- Issues and workarounds
- Documentation change
- General
- Warning dialogs are not translated into Japanese
- VCEM performance
- Managing VC Domain firmware 3.10 after installing or upgrading to VCEM 6.2
- Resolving removal of the last VC Domain from a VC Domain Group
- Reinstalling Virtual Connect Enterprise Manager
- VC Domain Groups and VC Domain Management
- Jobs
- Server power management
- Server profile operations
- VC Profile Failover
- Profile operations fail, and the error message "An invalid boot LUN was entered. Check the storage arrays for the proper LUN number" appears
- Moving Ethernet networks (VLANs tagged) from one shared uplink to another
- Error popup appears when you select HP predefined ranges during remove VC Domain from Group or delete VC Domain Group operations
- For more information
- Software Availability in Native Languages
In addition, the screenshots accompanying this text were also updated since the publication
of the user guide. These changes will be reflected in future editions of the HP Virtual Connect
Enterprise Manager User Guide.
• If, after performing data migration, you are running Virtual Connect Manager and try to
access a VCEM-managed VC Domain, the following error message appears:
VC Domain locked by Virtual Connect Enterprise Manager <CMS IP
address>.
To resolve this issue:
1. Go to the CMS and invoke the MS-DOS command box.
2. Change the directory to the <DRIVE>\<VCEM INSTALLATION FOLDER>.
3. Run either of the following CLI commands:
— >vcem -updatevcmdesc
— >vcem -uvcm
To validate that the problem has been corrected, browse to the Virtual Connect Managers
that showed the incorrect message to ensure that the correct message is displayed.
• Using VCEM 1.40 or 6.0 to disable SNMP on Virtual Connect Manager 2.30 can result in
improper propagation of SNMP enablement to the VC Domain Group. This issue occurs if
you use either VCEM 1.40 or 6.0 to disable SNMP for VC Ethernet or Fibre Channel modules
and the following conditions exist:
— The VC Domain Group contains a combination of VC firmware version 2.30 and earlier
firmware such as 2.10 or 2.0x.
— You select a VC Domain running VC firmware 2.30, put it into VC Domain Maintenance,
and use the Virtual Connect Manager user interface to disable SNMP.
While a permanent fix will be provided in a future VC firmware release, you can resolve
this issue by performing these steps:
1. Select a non-version 2.30 firmware VC Domain in the VC Domain Group. For example,
select a VC Domain with a 2.0x or 2.10 firmware.
2. Put the VC Domain into VC Domain Maintenance.
3. In maintenance mode, use the Virtual Connect Manager user interface to disable SNMP.
4. Return to the VCEM user interface and accept the VC Domain maintenance changes.
This action causes VCEM to propagate a SNMP disabled status to all members in the
VC Domain Group.
• VCEM cannot manage a VC Domain that configures a Shared Uplink Set or Ethernet Network
with the following:
— Connection mode set to Failover
— More than one port with Port Role value set to Primary or no Port Role set to Primary
To resolve the issue, access Virtual Connect Manager and set one port to be the primary.
• VCEM cannot manage a VC Domain that configures an Ethernet Uplink Port with a
Speed/Duplex value as Disabled. VCEM always replicates the VC Domain configuration
with Speed/Duplex set to Auto.
However, VCEM does not prevent you from adding such VC Domain to a VC Domain
Group.
• VCEM fails to add a VC Domain that configures an Ethernet Uplink Port with a Speed/Duplex
value as Disabled to the same VC Domain Group to which it previously belonged.
To resolve the issue, perform the following steps after the Add to VC Domain Group job
failure:
1. Go to the Virtual Connect Manager user interface.
10