HP Matrix Operating Environment 7.2 Update 1 Infrastructure Orchestration User Guide

3. Rediscover Hyper-V VM hosts in Systems Insight Manager.
4. Check the device subtype of the VM hosts. If the subtype does not display “Microsoft Hyper-V
Virtual Host”, restart the WMI Mapper service and rediscover the VM host.
Server blades that are not in use are shown in infrastructure orchestration server pools
but are not allocated for provisioning
Server blades that are not in use are shown in IO server pools, but IO does not allocate the blades
for provisioning.
Issue
The server blade is not a valid target for provisioning.Possible cause
Run the command sbapi GetServerPools and check the isValidTarget value for the blade.Action
If IsValidTarget=true, refresh the Servers view and try again.
If IsValidTarget=false, the blade cannot be used for provisioning. Possible causes:
1. The blade has a hardware problem
2. The blade enclosure is in maintenance mode (verify via VCEM)
3. The blade is no longer in its enclosure (verify via OA)
4. The VC domain group is deleted (verify via VCEM)
If a blade is not expected to ever be available again for provisioning, it can be moved to another
server pool created especially for unavailable servers (IO contains the built-in Maintenance pool).
Moving servers to the Maintenance pool always deactivates the servers
Moving servers to the Maintenance pool always deactivates the servers.Issue
When a server is moved to the Maintenance pool, that resource is deactivated. A warning displays
stating that services reserving the server for future use will be canceled, and current logical servers
using the resource will be deactivated.
Possible cause
When moving a server to the Maintenance pool, attach a note to the server that indicates why the
server was moved to maintenance.
Action
Memory resources allocated to a virtual machine host are not available after using
the Deactivate servers operation
The memory resources allocated to a virtual machine host are not available after using the Deactivate
servers operation.
Issue
When virtual infrastructures or individual servers are deactivated, infrastructure orchestration does
not recognize the memory previously allocated to the logical servers as available to allocate to
other virtual machines.
Possible cause
Action
Step in the Request Details fails
A step in the Request Details is shown as having failed.Issue
When executing a request, infrastructure orchestration might report the failure of one or more steps
on the Request Details page. After such an error occurs, infrastructure orchestration attempts to
Possible cause
recover by retrying the tasks or re-allocating the resources. During a recovery allocation process,
infrastructure orchestration uses the server pools selected in the initial request. If a step fails too
many times, the whole request fails.
Configure the number of retries in the ..\Program Files\HP\Matrix infrastructure
orchestration\conf\hpio.properties file.
Action
198 Troubleshooting