Summary
Overview: Perform the following steps to delete a single LUN. Repeat the procedure to delete multiple LUNs.
Symptoms
After you perform an Agentless VMware Instant Restore of VMDK, you must manually delete LUNs on both the ESX server and NetApp storage.
Resolution
DPX 4.0.2 or later, use the following steps:
To find the FlexClone volume name:
- Log in to the DPX master server and navigate to the Job Monitor.
- Record the FlexClone volume from job log, for example: temp_lun_clone_APEXVOL_S_1340981207401.
The following is the format of the FlexClone volume:
APEXVOL_S - second qualifier represent name of the NetApp volume
1340981207401 - third qualifier represents timestamp of the volume creation
192.168.xxx.xxx Fri 6/29/2012 10:46:44 am sssvh SNBSVH_230J ----- Task 1 of job 1340981155 (node: DPX vSphere 4.1 Cluster/VAP CLUSTER/VAP NFS/RHEL6.1X6 (BASIC DISK), disk: Hard disk 1 (RHEL6.1X6-000001.vmdk)) starts -----
192.168.xxx.xxx Fri 6/29/2012 10:46:47 am ssrmi SNBVRE_096J Creating FlexClone volume (temp_lun_clone_APEXVOL_S_1340981207401)
192.168.xxx.xxx Fri 6/29/2012 10:47:13 am ssrmi SNBVTE_008J Creating Initiator Group (DPX_VMRST_76B1CF79_1340981155)
192.168.xxx.xxx Fri 6/29/2012 10:47:15 am ssrmi SNBVRE_081J Creating Datastore (tempds_1340981155)
192.168.xxx.xxx Fri 6/29/2012 10:47:16 am ssrmi SNBVRE_016J Creating lun (/vol/temp_lun_clone_APEXVOL_S_1340981207401/[NFS-rh61]DPXvcenter@76B1CF79/tempds_1340981155.LUN) backed by (tempds_1340981155)
192.168.xxx.xxx Fri 6/29/2012 10:50:48 am ssrmi SNBVRE_016J Creating lun (/vol/temp_lun_clone_APEXVOL_S_1340981207401/[NFS-rh61]DPXvcenter@76B1CF79/rst_6000C299-9787-fa8b-0afa-711a3d9fba7e_1340981155.LUN) backed by (/vol/temp_lun_clone_APEXVOL_S_1340981207401/.snapshot/DPXvcenter_NFS-rh61.1338497179/[NFS-rh61]DPXvcenter@76B1CF79/6000C299-9787-fa8b-0afa-711a3d9fba7e.RAW)
192.168.xxx.xxx Fri 6/29/2012 10:52:11 am ssrmi SNBVRE_034J Attaching the RDM disk (/vmfs/devices/disks/naa.60a98000486e58334a5a6b7471487734) to the VM (DPX vSphere 4.1 Cluster/VAP CLUSTER/VAP NFS/RHEL6.1X6 (BASIC DISK))...
192.168.xxx.xxx Fri 6/29/2012 10:53:33 am sssvh SNBSVH_231J ----- Task 1 of job 1340981155 ends -----
192.168.xxx.xxx Fri 6/29/2012 10:53:33 am sssvh SNBSVH_232J Task 1: Completion status 0; Run time 0:06:49; Data volume 15 GB; Throughput 37.6 MB/s
192.168.xxx.xxx Fri 6/29/2012 10:53:37 am sssvh SNBSVH_221J ===== Job 1340981155 ends =====
To delete the LUNs on vCenter/ESX server:
- Log in to the vCenter/ESX server.
- Navigate to the VM that has the VMDK attached.
- Power off the VM if powered on (suggested, not required).
- Navigate to the VM > Summary > Datastore. Verify that the tempds_1340981155 Datastore Mapping File is created.
- Right-click the VM and select Edit Settings.
- Select the VMDK (Mapped Raw LUN) to delete.
- Click Remove and select the Remove from virtual machine and delete files from disk removal option. Click OK.
- See the following related VMWare articles:
- An ESX/ESXi host with one or more LUNs in an All-Paths-Down (APD) condition may become unmanageable in vCenter Server - kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1030980
- Removing a LUN containing a datastore from VMware ESXi/ESX 4.x - kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1029786&sliceId=1&docTypeID=DT_KB_1_1&dialogID=383784454&stateId=1%200%20383796457
- Unpresenting a LUN in ESXi 5.x - kb.vmware.com/selfservice/documentLinkInt.do?micrositeID=&popup=true&languageId=&externalID=2004605
- Log in to the NetApp OnCommand System Manager and navigate to Storage > Volumes.
- Right-click the FlexClone volume temp_lun_clone_APEXVOL_S_1340981207401. Select Status > Offline, then Delete.
- Verify deleting temp_lun_clone_APEXVOL_S_1340981207401 removes the corresponding LUNs, for example:
(1) tempds_1340981155.LUN
(2) rst_6000C299-9787-fa8b-0afa-711a3d9fba7e_1340981155.LUN
- Navigate to vCenter/ESX server > Configuration > Storage Adapters tab.
- Right-click iSCSI Software Adapter and Rescan HBA.
- Navigate to VM > Summary > Datastore. Verify that the tempds Datastore Mapping File is removed.
DPX 4.0.0 and earlier, use the following steps:
To find the iGroup name:
- Log in to the master server and navigate to the DPX logs directory.
- Use the newest rmiserver***.txt file. Use the ls -lt command to find this file.
Refer to the output of the following Linux grep command on this file for the string igroup.
[root@apex04 logs]# grep igroup rmiserver955367289149698673.txt
Tue Mar 06 15:49:23 2012; TGID(1331066881), TID(1); Creating igroup[name(DPX_VMRST_E596BF75_1331066881), type(iscsi), osType(vmware)] on filer(10.1.101.165)
Tue Mar 06 15:49:24 2012; TGID(1331066881), TID(1); Adding initiator(iqn.1998-01.com.vmware:vi3-1a3629d2) to igroup(DPX_VMRST_E596BF75_1331066881)
Tue Mar 06 15:49:27 2012; TGID(1331066881), TID(1); Mapping LUN(/vol/volume/[WIN-IA-NONDUP]DPXVCENTER@E596BF75/tempds_1331066881.LUN) to igroup(DPX_VMRST_E596BF75_1331066881)
Tue Mar 06 15:49:27 2012; TGID(1331066881), TID(1); LUN(/vol/volume/[WIN-IA-NONDUP]DPXVCENTER@E596BF75/tempds_1331066881.LUN) was mapped to igroup(DPX_VMRST_E596BF75_1331066881) with LUNID(0)
Tue Mar 06 15:52:36 2012; TGID(1331066881), TID(1); Mapping LUN(/vol/volume/[WIN-IA-NONDUP]DPXVCENTER@E596BF75/rst_6000C294-1ea3-52a9-d8dc-694e5cba78e0_1331066881.LUN) to igroup(DPX_VMRST_E596BF75_1331066881)
Tue Mar 06 15:52:36 2012; TGID(1331066881), TID(1); LUN(/vol/volume/[WIN-IA-NONDUP]DPXVCENTER@E596BF75/rst_6000C294-1ea3-52a9-d8dc-694e5cba78e0_1331066881.LUN) was mapped to igroup(DPX_VMRST_E596BF75_1331066881) with LUNID(3)
- The last line of the above output contains the iGroup name created by DPX, DPX_VMRST_E596BF75_1331066881.
Record the iGroup name. The job id of the DPX Instant Restore of VMDK's is the numeric substring after the last '_' character, e.g., 1331066881, in the iGroup name.
- Log in to the vCenter/ESX server.
- Go to the VM that has the VMDK attached.
- Power off the VM if powered on.
- Navigate to the VM > Summary > Datastore. Verify that the tempds_1331131746317 Datastore Mapping File is created.
- Right-click the VM and select Edit Settings.
- Select the VMDK (Mapped Raw LUN) to delete.
- Click Remove and select the Remove from virtual machine and delete files from disk removal option. Click OK.
- Log in to the NetApp console using ssh and show the LUNs that are mapped to the iGroup. Use the following command:
LUN path Mapped to LUN ID Protocol
-----------------------------------------------------------------------
/vol/volume/[WIN-IA-NONDUP]DPXVCENTER@E596BF75/tempds_1331066881.LUN DPX_VMRST_E596BF75_1331066881 0 iSCSI
/vol/volume/[WIN-IA-NONDUP]DPXVCENTER@E596BF75/rst_6000C294-1ea3-52a9-d8dc-694e5cba78e0_1331066881.LUN DPX_VMRST_E596BF75_1331066881 3 iSCSI
- Delete the LUNs that are mapped to the iGroup:
Tue Mar 6 16:57:38 EST [lun.destroy:info]: LUN /vol/volume/[WIN-IA-NONDUP]DPXVCENTER@E596BF75/tempds_1331066881.LUN destroyed
fas2020> lun destroy -f /vol/volume/[WIN-IA-NONDUP]DPXVCENTER@E596BF75/rst_6000C294-1ea3-52a9-d8dc-694e5cba78e0_1331066881.LUN
Tue Mar 6 17:00:31 EST [lun.destroy:info]: LUN /vol/volume/[WIN-IA-NONDUP]DPXVCENTER@E596BF75/rst_6000C294-1ea3-52a9-d8dc-694e5cba78e0_1331066881.LUN destroyed
- Verify the LUNs that are mapped to the iGroup and no LUNs should return:
- Navigate to vCenter/ESX server > Configuration > Storage Adapters tab.
- Right-click iSCSI Software Adapter and Rescan HBA twice.
- Navigate to VM > Summary > Datastore. Verify that the tempds Datastore Mapping File is removed.