HP Matrix Operating Environment 7.2 Update 1 Infrastructure Orchestration User Guide

Following are recommended minimums. Depending on the size of memory and number of HBA
cards on each server blade, the values may need to be greater than the minimums.
• Integrity BL860c and BL860c i2 blades:
◦ For infrastructure orchestration serverboot.physical.wait.seconds, use the default
minimum of 360 seconds.
◦ For LSM INTEGRITY_POWERON_WAITTIME, use the default minimum of 360000 milliseconds.
• BL870c and BL870c i2 blades:
For infrastructure orchestration serverboot.physical.wait.seconds, use the default
minimum of 540 seconds.
◦
◦ For LSM INTEGRITY_POWERON_WAITTIME, use the default minimum of 540000 milliseconds.
• BL890c and BL890c i2 blades:
◦ For infrastructure orchestration serverboot.physical.wait.seconds, use the default
minimum of 1080 seconds.
◦ For LSM INTEGRITY_POWERON_WAITTIME, use the default minimum of 1080000
milliseconds.
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 “Configuring storage pool
entries, FC zones, and disk array presentations” (page 211).
Action
178 Troubleshooting