HP Virtual Connect Enterprise Manager 7.2 Release Notes

Suggested action

1. Navigate to the folder where HPSIM is installed.

2. Navigate to the lib subfolder and delete the vcem.bat file found there.

3. Re-execute the vcem.bat CLI or mxreconfig commands.

Performing a VC Domain Maintenance operation on an uplink port that is configured

for port monitoring

An uplink port that is configured for port monitoring can unintentionally be associated to an Ethernet

network or Shared Uplink Set when performing a VC Domain Maintenance operation. The double

association will also occur on the other VC Domains in the VC Domain Group after maintenance

is completed. This situation may cause conflicting data streams over the uplink port.

Suggested action

Perform a VC Domain Maintenance operation again to remove the conflict by editing the Ethernet

network or Shared Uplink Set to not use the conflicting uplink port.

Adding VC Domains with configured network access groups

Adding VC Domains with network access groups configured and with server profiles using any

network access group other than the default group can cause the operation to fail with an error

message similar to the following:

Error during Add VC Domain [ch00087vc] to VC Domain Group. Details: The

operation cannot be performed because it refers to a network in the

profile that does not belong to the NAG associated with the profile.

Suggested action

1. Take note of each server profile network access group configuration.

2. Access VCM and update each server profile network access group configuration from

“user-defined” to “default”.

3. Add the VC Domain to the target VC Domain Group.

4. Update the server profile’s network access group configuration with the original configuration.

NOTE: It will be necessary to repeat steps 1 (one) and 3 (three) for each server profile that

is using the user-defined network access groups.

NOTE: All networks in use by the server profile must be part of default network access group

configuration.

Migrating from Systems Insight Manager with VCEM 6.3.x or 7.0.x

If you are migrating from a source CMS configured with Systems Insight Manager and VCEM

6.3.x or 7.0.x to a target CMS which will have Systems Insight Manager and VCEM 7.2, you

must remove the target CMS VC Domain Groups from VCEM (if any) before starting the import

operation in the target CMS.

Updating VC firmware versions in a VC Domain to be compatible with VC 3.70 and

VC 4.01 or later

With release 7.1.1 or later, VC firmware versions 3.70, 4.01 and later are not compatible with

VC firmware versions prior to 3.3x.

Suggested actions

Virtual Connect firmware compatibility mode allows administrators to update each VC Domain in

a VC Domain Group incrementally, rather than requiring that all VC Domains be updated at the

same time. VC Domain Group firmware mode is the firmware level in which a VC Domain Group

operates.