Command -add profile error messages, Additional troubleshooting information and tools – HP Insight Management-Software User Manual
Page 91
following error message appears whenever an -add profile or -set profile 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.
An invalid boot LUN was entered. Check the storage arrays for the proper LUN number
Correct the Boot LUN value in the server profiles to resolve the issue. 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, retry the operation.
Command -add profile error messages
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. The
following error is reported whenever a -set profile operation is performed with a server
profile that has a boot LUN that fails to comply with the conditions stated here.
An invalid boot LUN was entered. Check the Storage arrays for the proper LUN number
This situation can happen when a server profile is created in Virtual Connect Manager, and then
you try to manage it with VCEM. To resolve this issue change all the target LUN fields to be within
the allowed ranges (either a three-digit decimal between 0–255, or a 16-digit hexadecimal between
0 and FFFFFFFFFFFFFFFF). After the operation completes, you can perform migrate, assign, and
failover operations on the server profile.
Additional Troubleshooting Information and tools
The following troubleshooting tools are available to you:
•
Systems Insight Manager audit log—Review the Systems Insight Manager audit log from
theTasks & Logs
→View HP Systems Insight Manager Audit Log…menu in the Systems Insight
Manager web UI. The audit log records logons by VCEMCLI along with the IP address where
VCEMCLI is running.
•
VCEM events—Review VCEM events in the VCEM web UI to check for details around success
or failure of jobs. This information is available using VCEMCLI but you can use the VCEM UI
for checks when needed.
•
NT event log—Review the NT event log on the CMS host for errors pertaining to connectivity
or user logons to the system.
•
Documentation—See
“Support and other resources” (page 92)
for documentation information.
Command -add profile error messages
91