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

For Ignite-UX
1. Power on the server blade and allow it to boot the operating system.
2. From the CMS, run the mxtool Ignite Erase Disks by typing this command into a Windows
command prompt:
* mxexec –t “Ignite Erase Disks” –n <ip>
* where <ip> is the IP address of the Ignite server being cleaned
For HP Server Automation (SA):
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 device list in either the Unprovisioned Servers list or the
Unmanaged 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 either list.
After completing the previous steps based on the deployment server being used, do the following
to allow the storage pool entry to be selected in a future provisioning request:
1. Deactivate the associated Matrix OE logical server (if it is active) by using the Matrix OE
menu: Tools→Logical Servers→Deactivate.
2. After the associated logical server is inactive, delete the logical server using the Matrix OE
menu: Delete→Delete Logical Server.
In the Delete Logical Server screen, enter Yes for Type YES to proceed with this
operation: to confirm the operation.
NOTE: Do not select the Unmanage Logical Server option. Doing so will cause the logical
server storage pool entry to be modified to contain new WWNs without regard to presentation
or zoning. Follow the procedure in “Configuring storage pool entries, FC zones, and disk
array presentations” (page 236) to resolve this issue.
3. Verify that the VC profile associated with the failed server blade exists in Virtual Connect
Enterprise Manager. If the profile exists, unassign and delete the VC profile associated with
the failed server blade from Virtual Connect Enterprise Manager.
4. Move the server blade out of the infrastructure orchestration Maintenance pool.
a. In the infrastructure orchestration console (accessed from Systems Insight Manager), select
the original server blade pool and click Modify.
b. Move the failed server from the infrastructure orchestration Maintenance Pool back to the
server blade pool and then save the pool.
Manual clean-up process (virtual)
A Clean-me logical server appears for a virtual server when an infrastructure orchestration virtual
server deployment fails or infrastructure orchestration virtual server delete service request fails.
With these failures, the server blade is moved to the infrastructure orchestration maintenance pool,
and the Matrix OE logical server is renamed with the prefix Clean-me.
When infrastructure orchestration deploys a virtual machine, it creates a directory structure into
which the virtual machine is provisioned. The directory that is created follows the pattern: <VMFS
Volume>\<Service Name>\<VM Name>. This folder contains all the folders and files
corresponding to the virtual logical servers. Delete this folder and all its contents.
For ESX:
Corrective procedures 235