Updating persistent iSCSI target IQN bindings and CHAP secrets via iscsicli after SAN controller replacement

Hello,

You don’t need to remove and recreate the persistent targets entirely, but you do need to update the stored authentication parameters because Windows iSCSI initiator caches the IQN and CHAP secrets in its persistent binding. When the SAN controller was replaced, its target IQN or CHAP configuration likely changed, and the initiator is still trying to use the old binding.

The most direct way is to use iscsicli to update the existing persistent target entry. Run iscsicli ListPersistentTargets first to confirm the IQN and portal address currently stored. Then use iscsicli QLoginTarget <TargetIQN> to verify the initiator is attempting the connection. If the CHAP secret has changed, you can update it with iscsicli AddTarget <TargetIQN> <PortalAddress> <PortNumber> <Username> <Password>. This overwrites the authentication parameters without requiring you to delete the entry. If the target IQN itself has changed because the new controller presents a different identifier, then you must remove the old binding with iscsicli RemovePersistentTarget <TargetIQN> and add the new one with the correct IQN and CHAP credentials. Windows will not automatically remap an IQN mismatch.

In short: if only the CHAP secret changed, update the existing binding with AddTarget. If the IQN changed, you must remove and recreate the persistent target entry. After updating, restart the Microsoft iSCSI service (iscsicli RefreshTargetPortal <PortalAddress>) or reboot to ensure the initiator picks up the new credentials.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

Domic Vo.