13 troubleshooting vcem, Using expanded vlan capacity – HP Virtual Connect Enterprise Manager Software User Manual
Page 156
13 Troubleshooting VCEM
When you are upgrading to a new and different CMS, or are moving to a 64-bit CMS, you might
need to migrate your data by using the Systems Insight Manager data migration tool. If you are
upgrading to a new version of VCEM on the same CMS, data migration with the Systems Insight
Manager data migration tool is not necessary. For more information, see the Data Migration of
an Existing Microsoft Windows CMS to a new Insight Management 7.2 system white paper on
the Systems Insight Manager Information Library at
Deleting a large number of assigned profiles results in a timeout
If you are trying to delete 1000 or more assigned profiles, the deletion can either take a long time
to complete or can result in a timeout. HP recommends that you only delete less than 1000 assigned
profiles at a time.
Managing VC domains with Expanded VLAN capacity enabled
VCEM 7.1.1 or later is able to manage VC domains with Expanded VLAN capacity enabled.
CAUTION:
Virtual Connect Manager 3.30 or later does not allow you to easily revert back from
Expanded VLAN capacity mode to Legacy capacity mode. To revert back to Legacy capacity
mode, you must delete the VC domain in Virtual Connect Manager and then recreate it.
Using Expanded VLAN capacity
Virtual Connect Manager 3.7x or later has Expanded VLAN capacity mode enabled by default.
To add a VC Domain with VC FW 3.7x to a VC Domain Group prior to VC firmware 3.7x, the
VC Domain Group must have Expanded VLAN Capacity enabled.
NOTE:
If the VC Domain Group was created with all VC Domains in Legacy VLAN Capacity
and the VC firmware is prior to 3.7x (3.30/3.51/3.60), when you update the VC firmware to
3.7x (3.70/3.75) or later, all VC Domains will continue in Legacy VLAN capacity.
Adding a VC 3.70 or later Domain with IGMP No Flood enabled into a VC Domain
Group with group firmware mode 3.3x or 3.5x
IMPORTANT:
IGMP behavior is configured by using Advanced Settings in the VCM GUI. VCM
3.70 allows administrators to select whether IGMP Snooping is enabled and whether to prevent
flooding of unregistered multicast traffic. These settings can be viewed in the Ethernet Common
Settings section of the VC Domain Group Properties or the VC Domain Properties displayed in
VCEM.
VCEM is unable to communicate to a VC Domain running VC firmware 3.70 after VCEM attempts
to configure the VC Domain using Prevent flooding of unregistered multicast traffic with a VC
Domain Group that disables the IGMP Snooping feature.
NOTE:
This does not impact server blade I/O connectivity in the managed enclosures.
After the situation occurs, the VCEM job reports the failure immediately following the entry “Validated
VC Domain.” It contains the following message:
Error during Add VC Domain [xxxxx_vc_domain] to VC Domain Group.
Details: Virtual Connect is not responding. To resolve this issue:
1. Verify if the IP address is active (try to log to the Virtual Connect Manager via Onboard Administrator).
2. Verify that there are no network related issues between Virtual Connect Manager and VCEM (try to ping from
the command line of the Virtual Connect Enterprise Manager server to the Virtual Connect Manager. 3. Verify if
Virtual Connect is in the process of updating firmware. If so, wait for a few minutes and try again. 4. Verify
if Virtual Connect is in the process of failover. If so, wait for a few minutes and try again. 5. Check if the
156
Troubleshooting VCEM