HP Matrix Operating Environment 7.3 and 7.3 Update 1 Infrastructure Orchestration User Guide

For large numbers of Software Automation (SA) or deployment images, the property is
timeout.get.images.
Other timeout properties available to configure are the following:
• timeout.get.storagepools
• timeout.generate.storage.entry
• timeout.get.vmtemplates
• timeout.get.deployment.services
For example, to increase fetch subnets timeout from the default value of 5 minutes to
15 minutes, modify the line: timeout.get.subnets = 5 to: timeout.get.subnets =
15.
Manual clean-up process (physical)
If an infrastructure orchestration physical server deployment or delete service request fails, perform
a manual clean-up process, which includes the following:
• Fully erase the operating system from the boot disks.
• Detach the blade from the storage.
• Return the blade to an infrastructure orchestration server pool for a future provisioning request.
This type of failure forces the server blade to move to the infrastructure orchestration Maintenance
pool and the Matrix OE logical server is renamed with the prefix “Clean-me-”.
The server profile and boot disk are preserved, enabling an administrator to determine the cause
of the failure and perform any required maintenance before returning the server blade to a user
pool. Manual clean-up of the failed server blade depends on the deployment server used to provision
it.
For Insight Control server provisioning:
1. Power on the server blade.
2. Press F9, and select Advanced Options, Erase Boot Disk.
3. Boot again, and press F9 again, and select the NIC as the first boot device.
4. Verify that the server blade is powered off after completing the above step. Manually power
off the blade server, if needed.
5. The server blade may exist in the Servers list, identified by its MAC address (switch to the
Hardware or Network view to see the MAC address). Manually delete the server blade from
the list.
For Insight Control server deployment:
1. Power on the server blade.
Cycle the power if the server blade is stuck.
2. Make sure that the attached boot LUN erases, by doing one of the following:
• Run the Erase ProLiant ML/DL/BL Array Configuration {LinuxPE} job
from the Insight Control server deployment console. This is the preferred option.
• Alternatively power on the server blade, then press F9, and select Advanced
Options→Erase Boot Disk.
3. Verify that the server blade is powered off after completing the preceding step. Manually
power off the server blade, if needed.
4. Manually delete the server blade from the Insight Control server deployment console.
234 Troubleshooting