Re: iSCSI- duplicate initiator name
William Studenmund <[email protected]>
| Newsgroups | gmane.ietf.ips |
|---|---|
| Message-ID | <[email protected]> |
On Mar 22, 2006, at 7:34 AM, Inbal Zilbershmidt wrote: > Is it possible to have 2 leading connections from the same > initiator? Isn't a session implies an IT nexus? > As I understood, it is possible to have multiple connections in a > single session. > My question was regarding to a 2nd leading connection from a > certain initiator name. I caused such situation by giving two > different initiators the same name. > I wanted to know how should I deal with such case. If something is logging in with the same initiator name and ISID as an existing session, and it further passes the security phase (either you are configured for no security or the new initiator successfully authenticated), then IT IS THE SAME INITIATOR. You are supposed to follow the session reinstatement operations described in RFC 3720. Doing anything else would have a number of other, severe, consequences. We (Wasabi) have had customers end up with end-systems that all had the same initiator name and ISID. Since we have to do session reinstatement, we ended up having systems keep logging each other out. Our solution was to add the IP address of a logging-in initiator to our log messages. Thus if you see 192.168.1.2 and 192.168.1.3 both using the same name over & over, you know what the problem is. Take care, Bill _______________________________________________ Ips mailing list [email protected] https://www1.ietf.org/mailman/listinfo/ips
PGP.sig
(application/pgp-signature, 186 B) - not displayed