Resource issues

When extending the lease period, the operation might fail without stating a specific reason or error message.  If you attempt to extend the lease period of an infrastructure beyond the period available to its resources (insufficient static IP addresses or insufficient capacity on a virtual machine host), the Insight Orchestration displays an error message, stating “ The informed lease period conflicts with another infrastructure service lease period and cannot be updated. ” Verify that there are sufficient and available:

Virtual Connect Domain Group status must display managed by VCEM for Insight Orchestration to correctly execute operations over its resources.  If you attempt to perform an operation on servers under a VCDG that presents a different status, might not complete the requested operation.

Entering a hostname in the network WINS setting causes a Windows customization to fail.  To resolve this issue, enter either an IP address or leave the network WINS setting blank.

Moving servers to the Maintenance pool, places the servers in Standby mode.  If you move a server in use by any infrastructure service to the Maintenance pool, that resource is placed into Standby, even if you select the No option on the Insight Orchestration confirmation screen.

If a physical server deployment fails, you must perform a manual cleanup process.  After a physical server blade provisioning fails, the server blade is moved to the Insight Orchestration Maintenance pool and the VSE logical server is renamed with the prefix “clean-me-”. The server profile and boot disk are preserved, enabling the administrator to determine the cause of the failure and perform any required maintenance before returning the server blade to a user pool.

For more details see the “Resources management” instructions in the “Troubleshooting” section of the HP Insight Orchestration User Guide.

I cannot add servers to an existing service using a Static IP address  When a service contains multiple servers and the network is configured with static IP addresses, you cannot add additional servers to the provisioned service, even though the Insight Orchestration interface enables you to create the request without a warning. When this type of request is processed, it fails.

Static IP allocation limitation.  You can provision a service from a template only once, if the template defines a server group with a statically defined IP addresses and an auto allocated network. Typically, static IP addresses are used together with an explicitly defined network in the template. However, you might want to create multiple infrastructures, each having the same private static IP addresses, with each infrastructure containing its own network and VLAN. Insight Orchestration does not support this configuration scenario. When static IP addresses are allocated to a network, they cannot be reallocated to a different network.

To workaround this issue, change static IP addresses in the template each time you use the template, or use automatic IP address allocation. Automatic allocation enables you to use the template multiple times for multiple infrastructures, each having a different set of IP addresses assigned to the service.

When restarting physical servers, the Resume operation might fail when selecting more than one server pool.  When using more than one server pool in a Resume operation, the reservation step of the Resume operation might fail displaying the message “ Unable to allocate servers and networks in the same Virtual Connect Domain group. ” This is an intermittent issue.

I can only assign a virtual IP address to the first network connected to the server group.  The Insight Orchestration Designer enables you to define virtual IP addresses for a server group. If multiple networks are connected to the group, Insight Orchestration only enables you to assign virtual IP addresses to the first network listed for the server group. Networks are listed in alphanumeric order.

You can only use the DHCP assignment type for a NIC connected to an IPV6 network.  The Automatic and Static assignment types are selectable in Designer when a network is specified as IPV6, however only DHCP works correctly for IPV6 with Insight Orchestration.

I cannot set the processor architecture to Unspecified using Insight Orchestration Designer.  When creating an infrastructure template, the Processor Architecture property must be set either to IA-32 or x86_64.

The memory resources allocated to a virtual machine host are not freed after I use the Standby operation.  When virtual infrastructures or individual servers are placed into Standby, Insight Orchestration does not recognize the memory previously allocated to the Logical servers as available to allocate to other virtual machines.