> On Jan 29, 2016, at 4:50 PM, Chris Leech <[email protected]> wrote: > > On Thu, Jan 28, 2016 at 06:11:28PM -0800, shiva krishna merla wrote: >> Thanks Mike, Yes, we have one LUN per target and testing with large >> number of LUN's. 100 - 1024. With this each LUN will have a volume >> level target. I think the reason other vendors have not seen this >> issue till now may be because they use single target multiple luns >> model and will have least number of sessions per target. > > I've sent a patch that should increase the used ISID space from 8 to 24 > bits. I'll continue to get additional testing on it. > > But, I was also reading through the RFC 7143 about ISID use and from > what I can tell isn't an Initiator Name + ISID pair only required to be > unique within a single target portal group? If you have many targets, > or many portal groups, reuse of the same ISID should not be an error.
You are correct for non multipath use. We should never hit the problem. For multiparth use we create N sessions to the same target port group. If the user does not specify a different initiator name (this is common when the user was just binding a session to a nic port), then we need your patch because the isid has to be unique. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
