Loading...
Loading...
Attempting to remove an initiator fails. Error 0x6000116 returned. The Ignore option under Edit Initiator may not resolve the issue. Error Text: Failed: The system could not delete the initiator because there are storage resources associated with the host that the initiator is registered to (Error Code:0x6000116 ) Figure 1. System could not delete the initiator message
The initiator is associated with a host that still has one or more storage resources (LUNs, consistency groups, VMFS datastores, and so on) assigned.
Scenario 1: Host No Longer Requires Storage Access Remove all storage resource assignments from the host. Navigate to: Access > Initiators Select the initiator. Click the Delete (trash can) icon. Scenario 2: Initiator Must Be Removed Without Removing Host Storage Access For example: ESXi path changes HBA replacement Host remediation No downtime desired Create a temporary host object with no storage resources assigned. Edit the initiator. Change the host association to the temporary host. Delete the initiator from the temporary host object. Remove the temporary host object if no longer needed. Additional Notes The Ignore setting does not bypass storage resource association checks. Initiators cannot be removed while they remain associated with a host that has active storage resources assigned. Error 0x6000116 is expected behavior and prevents accidental host access loss. Create a New ESXi host with no access to any LUNs (Test Host). Open the ESXi host that has the initiators > under Initiators tab > Click Edit Figure 2. Open ESXi host that has the initiators Change the Host under Edit Initiator to the new host (Test Host). From the new host, delete the initiators. Figure 3. Delete Initiators from the new Host
Click on a version to see all relevant bugs