Deleting a Vdisk or Global Disk

The Delete Vdisk capability forces a clearing of the identified Vdisk or Global Spare.

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_Vdisks_GlobalSpares.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. If the Vdisk to delete is associated with a Host Volume, you must turn off <CheckHealthStatus> as follows:
   <CheckHealthStatus>OFF</CheckHealthStatus>
   By default, PMAC includes storage health status checks in its error checking and will not proceed with the configuration if problems are found. In this case, you would not be allowed to delete a Vdisk that has an associated Host Volume.
4. Locate the <Controller> element and specify an IP address or hostname for the Controller. The configuration information for the Vdisk will be deleted from the specified Controller.
   The relevant section from the XML file is shown:

     <VdiskConfig>
       <Controllers>
         <!--
           Provide the IP addresses (or names that resolve to IP addresses)
           of one or more Controllers here.  The configuration in this file
           will be applied to each controller listed.
   
           At least one <Controller> must be provided, prior to the VDisks section.
   
           Specify only one Controller per Controller Enclosure.  Each
           Controller Enclosure has two Controllers, but they are a
           redundant pair.  Applying the same configuration to both would
           attempt to configure the Controller Enclosure twice.
         -->
         <Controller>10.240.6.150</Controller>

5. Locate the <Vdisk ConfigAction="Delete">element and under <Name> specify the Vdisk to delete. Perform this step for each Vdisk to delete.
   The relevant section from the XML file is shown:

   <Vdisk ConfigAction="Delete">
             <!--
             It is necessary to specify which Vdisk to delete.
             -->
             <Name>Vdisk1</Name>
           </Vdisk>
           <Vdisk ConfigAction="Delete">
             <Name>Vdisk2</Name>
           </Vdisk>

6. If necessary, upload the XML file(s) back to the PMAC server by using sftp. See Uploading files to PMAC via sftp if you need help uploading the file.
7. 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/

8. Log onto the PMAC GUI as the guiadmin or pmacop user.
9. Click Storage > Configure SAN Storage.
10. 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.
11. Click Task Monitoring to monitor progress as the background task executes.
12. 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 Vdisk configuration successfully deleted.. If the display indicates failure, make a note of the point at which the failure occurred and see Configure storage recovery.
13. After the operation executes, reboot the Host blade.

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