Software Owner's manual

This behavior is intermittent, but can occur in the following situations:
• When navigating through VCEM pages and requesting multiple operations at the same time
• When VC Domains that are being managed by VCEM are having a communication outage
To solve this issue, press Refresh to reload the VCEM page, and then perform the desired operation
again.
To prevent the issue from happening again, perform either of the following:
• Verify that the Central Management Server has the minimum hardware requirements to run
VCEM.
• Verify that all VC Domains are correctly communicating with the Central Management Server.
VC Domain not discovered by Systems Insight Manager
If SNMP protocol is not correctly configured, then Systems Insight Manager cannot correctly discover
the unconfigured VC Domains, and then you might not be able to see such VC Domains or the VC
Domains list.
To correct this issue, perform one of the following:
• Access the Systems Insight Manager menu, select Options→Discovery→Configure Global
Credentials, and verify the first SNMP read community string is public.
• Access the Systems Insight Manager menu, Select Options→Discovery→Configure Global
Protocol Settings, and verify that the Enable SNMP option is selected.
• Run Systems Insight Manager discovery on the Onboard Administrator IP address related to
the VC Domain by accessing the Systems Insight Manager menu and selecting Options→Identify
System or Options→Discovery.
Create VC Domain Group or Add VC Domain to VC Domain Group
operations fail and the 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 three-digit
decimal between 0–255, or a 16-digit hexadecimal value between 0 and FFFFFFFFFFFFFFFF.
This message appears whenever a Create VC Domain Group or an Add VC Domain to VC Domain
Group operation is performed and there is one or more server profiles inside the VC Domains that
have a boot LUN that does not comply with the required conditions.
To resolve this issue, use the Virtual Connect Manager to correct the Boot LUN value in the server
profiles. A valid value is either a three–digit decimal between 0–255 or a 16-digit hexadecimal
between 0 and FFFFFFFFFFFFFFFF. To determine the correct value, access the storage management
software or ask the storage administrator. After entering the correct value, try the operation again.
NOTE: VCEM validates the format of the target LUN but does not verify that it is actually bootable.
Profile move, assign, or failover operations fail and the 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 three-digit
decimal between 0–255, or a 16-digit hexadecimal value 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 a server profile is created in Virtual Connect Manager, and then you try to manage
it with VCEM.
VC Domain not discovered by Systems Insight Manager 139