On 01/28/2016 02:19 PM, shiva krishna merla wrote: > Hi All, > > We are seeing an issue with Redhat 6.7 where ISID's are repeated for > different sessions to same target (volume level target). Our array > target has to close the existing sessions with same ISID before > accepting new connections. This causes repeated login retry attempts by > iscsid and overall system discovery process is too slow. From the code i > see that ISID is determined as below. With this many sessions above 256 > can have repeated ISID. Is this a design flaw?. Can this be avoided?. > > /* OUI and uniqifying number */ > session->isid[0] = DRIVER_ISID_0; > session->isid[1] = DRIVER_ISID_1; > session->isid[2] = DRIVER_ISID_2; > session->isid[3] = 0; > session->isid[4] = 0; > session->isid[5] = 0; >
Very nice debugging. Thanks. We have not seen setups with that many sessions, so we just did not support it. It sounds like the Red Hat iSCSI engineer, Chris Leech, is working on a patch, so it should get fixed quickly. Just curious. Are you doing a LUN per target and have lots of LUNs? Or do you have lots of targets or target portals for some other reason? How many? -- 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 open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at https://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
