Deleting a Host Volume

The Delete Host Volume capability deletes the Host Volume configuration on the specified server blade and deletes the corresponding configuration on the Controller.

Caution:

The order in which Vdisks, Host Volumes, Global Spares are created or deleted is important. The procedures in this section do not state or imply the order to use. The operator with site-specific knowledge has the responsibility to configure the Vdisks, Host Volumes, and Global Spares in the proper order.

1. Log into the PMAC server as admusr.
2. Copy the file example_SharedStorageConfig_Delete_HostVolume.xml to a location where you can edit it from the following directory location on the PMAC server: /usr/share/doc/TKLCsmac-config-<release_number>/examples/.
3. Locate the <HostVolume ConfigAction="Delete"> tag.
   The relevant section from the XML file is shown:

   <HostVolume ConfigAction="Delete">
       <!--
           A Host may be specified by its IP address or a name that
           resolves to its IP address.
       -->
       <Host>10.2.3.1</Host>
       <Controller>10.2.3.4</Controller>
       <VolumeName>FirstVolume</VolumeName>
   </HostVolume>

4. Fill in the necessary site-specific information such as the IP addresses and Volume Names. You can have multiple <HostVolume> elements in one file.
5. If necessary, upload the XML file back to the PMAC server by using sftp. See Uploading files to PMAC via sftp if you need help uploading the file.
6. On the PMAC server, copy the XML file to /usr/TKLC/smac/etc/storage/.

   For instance,

   sudo /bin/cp /var/TKLC/smac/image/isoimages/home/smacftpusr/<filename> /usr/TKLC/smac/etc/storage/

7. Log into the PMAC GUI as the guiadmin or pmacop user.
8. Click Storage > Configure SAN Storage.
9. In the Configure Storage list, select the XML file and then click Configure Storage.
   The Configure Storage background task is launched. An ID for the background task is provided.
10. Click Task Monitoring to monitor progress as the background task executes.
11. Use the Refresh link to monitor the background task until you have verified that the background task completes successfully. If the background task completes successfully, the last step in the Background Task Monitoring display reads Host Volume successfully deleted. If the display indicates failure, make a note of the point at which the failure occurred and see Configure storage recovery.

The Host Volume configuration has now been deleted on the specified server blade. The corresponding configuration on the Controller has also been deleted.