topic Re: Delete iSCSI Initiator in ONTAP Discussions

Delete iSCSI Initiator

NEO-BAHAMUT — Tue, 18 Mar 2025 11:31:17 GMT

Hi All,

Is there a way to delete unwanted iscsi initiators. If you go to System Manager > Storage VMs > Select an svm with iscsi protocol enabled > iSCSI > Initiator Security

I have a list of initiators (VMs) that have all been decommed and can be removed from this list. If I select one of them there is no way to just "delete" that initiator through System Manager. I've also had a look at doing it via command line but again cant seem to spot the command to do it.

The only way I have managed to delete them is if they were already in an igroup I can remove them from the igroup which also deleted them from Initiator Security. If they arent in an igroup then I cant find a way at the moment to delete them.

ONTAP version is 9.11.1P10

Thanks

Re: Delete iSCSI Initiator

wareer — Wed, 19 Mar 2025 03:07:43 GMT

You can take this command to see first：

cluster1::*> storage iscsi-initiator show

Then delete：

cluster1::*> storage iscsi-initiator remove-target -node node1
             -label target1

Here are the relevant links：https://docs.netapp.com/us-en/ontap-cli-9111/storage-iscsi-initiator-remove-target.html

Re: Delete iSCSI Initiator

NEO-BAHAMUT — Wed, 19 Mar 2025 09:58:40 GMT

Hi Warer, this isn't the case in our environment. I wouldnt have thought it would be targeting a specific node as its "cluster wide".

I've been looking around and I don't seem to be able to remove it still. The closest I can get is changing the security type from Chap enabled to None. Still it keeps the decommed VM in the list. Would like to find a way to do this though. Perhaps this is something not available in our version of ONTAP

Re: Delete iSCSI Initiator

NEO-BAHAMUT — Thu, 20 Mar 2025 08:49:10 GMT

I managed to work around this. It was simple but took a bit of time to work out.

1. If an initiator was in an igroup, I had to remove the initiator from the igroup, then change the security settings on the initiator from CHAP (which we use) to default. This then automatically removed the initiator.

2. If the initiator wasn't in an igroup it was simply change the security to default which would automatically remove it.

Simple fix, but wasnt straight forward to see. Hopefully in a later release it is.