HP Matrix Operating Environment Software User Manual
Page 177
Cannot deploy Integrity VM guests when gWLM is controlling the host
If IO chooses a host controlled by gWLM for deploying an Integrity VM guest service template, the
guest cannot start and the following messages appear in the /var/opt/hpvm/common/
command.log
:
Issue
05/31/12 11:43:45|ERROR|Guest_number|root|Guest Guest_number has been
marked as not startable.
05/31/12 11:43:45|ERROR|Guest_number|root|An external manager (gWLM) is
managing VMs on this Host. This manager is located on location and can
be accessed via http://location. Add the VM to the manager to make it
available for starting.
Integrity VM guests cannot be deployed when gWLM is controlling the VM host.
Possible cause
Exclude any Integrity VM hosts and VSPs under the control of gWLM from the IO server pools.
Action
OS deployment through Insight Control server deployment fails when deploying to a SAN booted
physical server
The operating system deployment process through Insight Control server deployment fails when
deploying to a SAN booted physical server.
Issue
If the target server is sharing FC zones with other servers in the environment, changes in the SAN,
like an RSCN (Registered State Change Notification) event may lead to operating system deployment
or SAN boot failures.
Possible cause
Use initiator WWN zones to isolate each of the servers within the fabric. This is a typical best-practice
in SANs where servers are booted from a disk within the SAN. See
entries, FC zones, and disk array presentations” (page 209)
.
Action
Service creation fails in the in the target reconfiguration phase
Service creation fails in the target reconfiguration phase.
Service creation intermittently fails when a service is created with RedHat Enterprise Linux 6 OS.
Failure message
The target server fails to shut down due to an issue with the HP Health Agents versions 8.70 and
older.
Possible cause
Action
1.
Identify the failed target servers in the Maintenance server pool.
a. In infrastructure orchestration, select the Servers tab.
b. Expand the Maintenance server pool.
c. Note the names of servers in this server pool as they are the serial numbers of the servers.
2.
Delete the logical servers from Matrix OE visualization.
a. In Systems Insight Manager, select Tools
→Matrix OE visualization.
b. Select Logical Server from the Perspective drop-down box.
c. Identify the logical server entries where the name starts with “Clean-me” and contains the
previously noted serial number.
d. Select these logical servers and delete them by selecting to Delete
→Delete Logical Server.
3.
After the logical servers are successfully deleted, move the servers from the Maintenance pool
to an appropriate server pool.
a. Select Tools
→Infrastructure orchestration, then select the Servers tab.
b. Select the server pool to which to move the servers from the maintenance pool.
c. Click the Modify Pool button.
d. Select Maintenance from the drop-down list.
e. Select the server that needs to be moved from the list displayed and click the >> button.
f. Save the server pool.
Service creation 177