updating iSNS registration for portal IP address change

I am trying to determine the proper way to update an iSNS server when
the IP address of an iSCSI target port changes.  In my case, I have a
multi-ported iSCSI target that registers a single Storage Node object
and multiple Portal and Portal Group objects.

One method is to re-register the entire Network Entity using DevAttrReg
with the replace flag set.  This method seems rather disruptive as SCNs
will be generated for the de-registered objects and additional SCNs are
generated for registration of the new objects.  I assume this means that
iSCSI initiators in the target's Discovery Domain might logout all
sessions with the target's portals only to re-login a short time later.
Is this true?  I'd like to avoid causing logouts on any portals that
retain their original IP address.

Alternately, I can de-register the Portal object for the old IP address
of the target port using DevDereg and then register a new Portal object
for the new IP address using DevAttrReg.  However, I don't believe it's
possible to de-register the old Portal Group objects without
de-registering the Storage Node object.  In my case, I believe that
de-registering the Storage Node object would be as disruptive as doing a
replacement registration of the entity, since the target has only one
Storage Node object associated with all of its portal groups.

Thanks for any help on this.

Paul

_______________________________________________
Ips mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/ips