beautypg.com

HP Matrix Operating Environment Software User Manual

Page 219

background image

The value of timeout.get.vmhost should always be less than the value of
timeout.get.serverpools

.

Hyper-V VM hosts sometimes disappear from the IO server pool in large scale
environments

Hyper-V VM hosts sometimes disappear from the IO server pool in large scale environments

Issue

An occasional communication issue between Windows server WMI data and Hyper-V VM hosts
can cause the VM hosts to disappear from the server resources pool on the IO Servers tab.

Possible cause

Update the WMI Mapper property:

Action

1. Change the value of the HyperVQueryTimeout property to HyperVQueryTimeout=300000 in

\bin\hpvmm.conf.

2. Restart the HP Insight Control virtual machine management service.
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

Console operations

219