Perform ONTAP FLI ESXi post-migration host remediation
Suggest changes
PDFs
After migration, ESXi hosts require remediation steps to ensure the newly imported LUNs are properly recognized and functional.
Post migration - Offline FLI
For Offline FLI, bring the LUN online after deleting the lun import and confirming host initiators are connected.
| VMs/VMDK | RDM | WFSC | VMSC |
|---|---|---|---|
Step 1: Rescan storage on all mapped ESXi hosts. |
Step 1: Rescan storage on all mapped ESXi hosts. |
Step 1: Rescan storage on all mapped ESXi hosts. |
Step 1: Rescan storage on all mapped ESXi hosts. |
Step 2: List volume/device details to confirm filesystem details on the LUN. |
Step 2: Identify new NAA IDs and add RDMs back to the respective VMs. |
Step 2: List volume/device details to confirm filesystem details on the LUN. |
Step 2: List volume/device details to confirm filesystem details on the LUN. |
Step 3: Identify datastore details and mount datastores back to ESXi. |
Step 3: Power on guest VMs and start applications. |
Step 3: Identify datastore details and mount datastores back to ESXi. |
Step 3: Identify datastore details and mount datastores back to ESXi. |
Step 4: Identify datastore details and mount datastores back to ESXi. |
Step 4: Identify datastore details and mount datastores back to ESXi. |
Step 4: Power on guest VMs and start applications. |
|
Step 5: identify the RDM disks used by the cluster and remap them to the WFSC cluster nodes using the same controller IDs and unit numbers (for example, SCSI1:0) to maintain consistency with the previous configuration. |
Step 5: Power on guest VMs and start applications |
||
Step 6: Power on guest VMs and start the cluster application. |
|
Refer to OS Vendor Documentation for Latest and updated command list. |
- Rescan after detaching to confirm clean state
esxcli storage core adapter rescan --all- Exit maintenance mode after completion
esxcli system maintenanceMode set --enable false- Rescan storage on all ESXi hosts mapped to the LUN
esxcli storage core adapter rescan --all- List devices and filesystems to confirm LUN / filesystem details
esxcli storage core device list
esxcli storage filesystem list- Identify new NAA IDs if they changed post-migration
esxcli storage core device list | grep -i naa- Mount VMFS datastore(s) back to ESXi
esxcli storage filesystem mount -l <DATASTORE_NAME>- Verify datastore mount
esxcli storage filesystem list- Add RDM back to VM (done via vSphere UI)
-
CLI is typically not used; verify backend device visibility instead.
esxcli storage core device list -d <naa.ID> - Exit maintenance mode (if applicable)
esxcli system maintenanceMode set --enable false- Power on guest VMs
-
(VM power operations are typically done via vCenter, but verification can be done on the ESXi host)
vim-cmd vmsvc/getallvms vim-cmd vmsvc/power.on <VMID>
Post migration - Online FLI
After deleting the import relationship, confirm the new LUN operates independently with CAW/UNMAP/XCOPY/WRITESAME enabled.
Revert VMFS locking mode to ATS-only by unmounting the datastore, setting ATS-only, then remounting. After deleting the LUN import, check if the LUN is set with -space-reserve disabled and -space-allocation enabled. If not, modify it accordingly.
| VMs/VMDK | RDM | VMSC |
|---|---|---|
Step 1: Rescan storage on all mapped ESXi hosts. |
Step 1: Rescan storage on all mapped ESXi hosts. |
Step 1: Rescan storage on all mapped ESXi hosts. |
Step 2: Shut down guest VMs gracefully. |
Step 2: Shut down guest VMs gracefully. |
|
Step 3: Unmount datastores planned for migration; if shared, unmount from all hosts. |
Step 3: Unmount datastores planned for migration; if shared, unmount from all hosts. |
|
Step 4: Check VMFS locking mode (ATS-only vs ATS+SCSI). If ATS-SCSI, change to ATS-Only |
Step 4: Check VMFS locking mode (ATS-only vs ATS+SCSI). If ATS-SCSI, change to ATS-Only |
|
Step 5: Identify datastore details and mount datastores back to ESXi. |
Step 5: Enable VM-HA / DRS and configure the required heartbeat disks if required. |
|
Step 6: Power on guest VMs and start applications. |
Step 6: Power on guest VMs and start applications |
|
Step 7: Validate datastore locking mode and VM/application health |
Step 7: Validate datastore locking mode and VM/application health |
- Rescan after detaching to confirm clean state
esxcli storage core adapter rescan --all- Exit maintenance mode after completion
esxcli system maintenanceMode set --enable false- Rescan storage on all ESXi hosts mapped to the LUN
esxcli storage core adapter rescan --all- List devices and filesystems to confirm LUN / filesystem details
esxcli storage core device list
esxcli storage filesystem list- Identify new NAA IDs if they changed post-migration
esxcli storage core device list | grep -i naa- Mount VMFS datastore(s) back to ESXi
esxcli storage filesystem mount -l <DATASTORE_NAME>- Verify datastore mount
esxcli storage filesystem list- Add RDM back to VM (done via vSphere UI)
-
CLI is typically not used; verify backend device visibility instead.
esxcli storage core device list -d <naa.ID> - Exit maintenance mode (if applicable)
esxcli system maintenanceMode set --enable false- Power on guest VMs
-
(VM power operations are typically done via vCenter, # but verification can be done on the ESXi host)
vim-cmd vmsvc/getallvms vim-cmd vmsvc/power.on <VMID> - If ATS+SCSI is detected, convert to ATS-only
vmkfstools --configATSOnly 1 /vmfs/volumes/<DATASTORE_NAME>