HP Insight Orchestration 6.3 User Guide

A provisioning request remains paused during a manual storage allocation (approximately 5%),
and a storage pool entry cannot be created in Insight Dynamics because the VC Domain Group is
not listed on the Storage Pools screen.
Issue
VCDG is using factory default MAC/WWN settings. HP Insight Dynamics and Insight Orchestration
do not support a VCDG with factory default MAC/WWN settings. Logical servers require portable
WWNs and MAC addresses that can be moved from blade server to blade server.
Possible cause
When creating a VCDG in Virtual Connect Enterprise Manager, select the HP Pre-Defined option
to enable portable WWNs and MAC Addresses. (For more information, see the Virtual Connect
Enterprise Manager documentation at HP Insight Dynamics Information Library.)
Action
• To avoid this issue, make sure the servers from a VCDG not configured for portable addresses
are not included in Insight Orchestration server pools.
• To resolve an existing issue, cancel the request and resubmit the request using a target Insight
Orchestration Pool that contains servers from a VCDG with portable addresses.
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 114).
Action
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 Insight Orchestration, click on 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 Virtualization Manager.
a. Browse to Tools→Virtualization Manager.
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 navigating 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. Navigate to Tools→Insight Orchestration, then select the Servers tab.
b. Select the server pool to which the servers from the maintenance pool will be moved.
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 fails when a physical template with Windows Server OS is selected. Insight
Management WBEM provider installation on the target server hangs.
Issue
An Insight Orchestration timeout waiting for Insight Control server deployment to complete installation
of Insight Management Agents.
Possible cause
When a request fails, Insight Orchestration automatically retries the request and a new server is
provisioned with the requested service. The original server is moved to the maintenance pool and
Action
can be cleaned and moved back to a valid server pool. If the failure is observed frequently, the
Working with services 89