HP StorageWorks 9100 Extreme Data Storage System administration guide V1.0.2 (AN540-96018, February 2010)

Removing server blades
CAUTION:
Do not remove a server blade from the blade enclosure without first powering it off and waiting for
two minutes. If you remove a live server blade, the Matrix could lock up because it cannot fence
the removed server blade. If you inadvertently lock up the Matrix this way, you can recover by using
the mx server markdown command. Only use this command when you are certain that the server
blade is powered down or removed.
To remove a server blade:
1. Ensure that all other server blades are running. Use the exdsmgr show server command and
examine the Matrix State (see Viewing server information on page 43). If any server (other than
the server you plan to remove) is not in the joined state, you cannot proceed with this process.
If a server is down, boot the server and wait until its Matrix State is joined.
2. If you use the exsd_exgp_default export group, you can delete the surplus virtual host with the
exdsmgr modify vnfs command and the removeserver action. You should only do this
when you know that clients no longer use the virtual host IP address.
3. If you use the vhttpd Apache service, you can delete the surplus virtual host by deleting and re-
creating the vhttpd configuration (exdsmgr delete/create vhttpd). You should only do
this when you know that clients no longer use the virtual host IP address.
4. Run the delete server command:
# exdsmgr delete server 8
where 8 is the server blade number.
5. Physically remove the blade from the blade chassis. For more information, see HP ProLiant BL460c
Server Blade User Guide.
6. Use mxconsole or mx(8) to validate that server is no longer a member of the Matrix cluster.
If it is, contact HP technical support for help (or see Troubleshooting).
Removing storage blocks
You cannot remove a storage block (array) if that array is being used to host a LUN on which the
utility filesystem or a membership partition is based. Use the exdsmgr show lun command to
determine which arrays host which LUNs. See the concept, LUNs, for more information.
To delete an array:
1. Validate that the array does not contain any LUNs whose role is adm or mp.
2. Delete any filesystems that use the array.
3. Delete LUNs on the array as shown in the following example:
# exdsmgr unconfigure array 4
4. Physically disconnect the SAS cables connecting both array controllers to the SAS switches.
5. Remove the array from system as shown in the following example:
# exdsmgr delete array 4
The exdsmgr delete array command only works if there are no LUNs on the array. If you delete
an array before disconnecting the array and a server reboots or you run the exdsmgr discover
Upgrading the HP ExDS910098