Remove initiators from igroups force_remove: true impact analysis

[strong shore]

Dear Team,

I am currently working on a task to eliminate stale initiators from multiple igroups using Ansible. I have found a module, “netapp.ontap.na_ontap_igroup_initiator”, which seems to be capable of performing this task.

However, I have encountered an issue when there are LUNs associated with the igroups in our production environment, causing the operation to fail. To circumvent this, I have incorporated the “force_remove: true” parameter.

Our storage architect has raised a concern regarding this approach. Specifically, we would like to understand the potential impact on connectivity when using the “force_remove” option. Is there a possibility that this could cause any disconnections to the existing LUNs within the igroup?

I hope my query is clear. If you need any further clarification, please do not hesitate to ask.

Best Regards,
Abhi

[minor finch]

If you remove (by accident, or intentionally) an initiator from the igroup that has an active connection to a LUN, then yes, that server (initiator) will immediately lose access to its LUN.
If you are 100% certain that the initiator you are removing is not connected, then there will be no impact to anything else

note that just because an initiator is not currently connected at a specific point in time does not mean that it is a stale entry. The server could just be rebooting for example

[strong shore]

thanks @minor finch the idea here is to remove the entry once VMware team (in this case) informes for some reason the initiator does not exist (example replaced HBA).