HP Virtual Connect Enterprise Manager Software - Manual (Page 163)

3. Go to VCEM and re-add the VC Domain to the same VC Domain Group.
•
VCEM cannot create a VC Domain Group or add a VC Domain to a VC Domain Group when
a backup VC module is discovered or if a failover of a VC module occurred in a redundancy
environment. The following error message appears:
The VC Domain [] cannot be managed by VCEM. A
possible cause is that the current state of the VC Domain is unknown.
Verify HP Systems Insight Manager (HP SIM) is referencing the primary
VC Module. If not, run HP SIM discovery to update the reference.
To resolve this issue, perform a rediscovery on the Onboard Administrator IP address associated
with the VC Module and perform the VCEM operation again.
Jobs
System performance can slow down on the Jobs page when the number of jobs exceeds 20,000.
To maximize system performance, delete old jobs before the total number reaches this limit.
Server power management
VCEM might not correctly present the power state of a server when the server is powered off using
VCM.
Server profile operations
•
To create profiles for Integrity server blades that boot from SAN, you must manually configure
the SAN boot entries in the blade server EFI console.
•
If the server profile has Flex-10 connections enabled, and server blade NICs (onboard or
mezzanine card) are connected to HP 10/10 Gb-F Virtual Connect Ethernet Module, VC
requires you to power off the server blade to perform any server profile operation.
VC Profile Failover
•
When you initiate a VC Profile Failover operation, VCEM does not check the compatibility of
the physical connections of the target server. The VC Profile Failover operation automatically
selects an available spare server of the same type and assigns the profile, but assumes that
the correct physical connections are already in place.
•
When a Failover is executed, HP SIM may not update the servers information. To resolve this
issue, run a manual HP SIM discovery of the affected systems.
Profile operations fail, and the error message "An invalid boot LUN was
entered. Check the storage arrays for the proper LUN number" appears
VCEM requires the boot target LUN configuration and server profiles to be either a 3-digit decimal
between 0-255, or a 16-digit hexadecimal between 0 and FFFFFFFFFFFFFFFF.
This message appears whenever a profile move or failover operation is performed with a server
profile that has a boot LUN that fails to comply with the conditions stated here. This situation can
happen when you create a server profile in VCM, and then try to manage it with VCEM.
To resolve this issue:
1.
Select the VCEM Server Profiles tab.
2. Select the server profile that is presenting the problem.
3. Click Edit.
4. In the boot target configurations table, change all the target LUN fields to be within the allowed
ranges (either a 3-digit decimal between 0-255, or a 16-digit hexadecimal between 0 and
FFFFFFFFFFFFFFFF).
Jobs 163