HP Matrix Operating Environment Software User Manual
Page 208

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.
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
* where
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 209)
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.
208 Troubleshooting