Operating Environment Software Instruction Manual

Check the hpio-controller.log file for warning messages of the form: ”Unable to get all VM
Host data in the allotted time. The data from some hosts will not be returned.” and ”Unable to get
VM Host data in the allotted time for host : <hostname>.”
Fix the environmental issues or increase the following timeout property settings. If a blade is not
expected to ever be available again for provisioning (especially under actions 3 and 4, above), it
can be moved to another server pool created especially for unavailable servers.
Action
1. Edit the ..\Program Files\HP\Matrix infrastructure orchestration\conf\
hpio.properties file.
2. Set timeout.get.serverpools to a longer interval. (For example, for a 20 minute interval,
set timeout.get.serverpools=20).
3. Set timeout.get.vmhost to a longer interval, but less than timeout.get.serverpools.
The default value of timeout.get.vmhost is 10. (If you change this value, the value is reset
to the default after an upgrade of infrastructure orchestration.)
The value of timeout.get.vmhost should always be less than the value of
timeout.get.serverpools.
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
Console operations 185