Re: isid persistence?
Hello, I don't believe that is required. In part because ISID is transport level, and SCSI3 PR is at the SCSI level. To be clear you are talking about a SCSI-3 Persistent Reservation correct? You are not talking about the older SCSI2 Exclusive Reservation. When I look at the PR table on my array it shows for each volume with a PR the volume ID, PR checksum and KEY along with the number of servers registered to that volume by iqn name of each initiator. Nothing about the ISID. The hosts uses the KEY and initiator name to maintain the reservation. Hosts can unregister an re-register if need be, done via SCSI commands not iSCSI transport. Ie. you remove a server from a cluster that PR entry will be removed from the table. I believe RedHat clustering uses SCSI3 PR with open-iSCSI without any issues? Regards, Don . On Sat, Jul 7, 2018 at 2:42 PM mayur kulkarni wrote: > for the SCSI PR to work, the same ISID should be given to the session, but > the open-iscsi is implemented such that it starts giving isids from 0 (not > considering the 3 byte prefix) and counts upwards. if an initiator logs out > and logs in again, for the same iqn port configuration (on both target and > initiator) the same isid should be allocated but that is not the case. > > hope, I was able to explain that. > > Thanks. > Mayur > > On Fri, Jul 6, 2018 at 4:30 AM Donald Williams > wrote: > >> Hello, >> >> It's an ID for that session what would be benefit of persistence? >> For my purposes the fact it's only for that session helps me when going >> through logs or traces. Makes it much easier to follow that session through >> the iSCSID logs and on the storage device as well. >> >>- SSID (Session ID): A session between an iSCSI initiator and an >> iSCSI target is defined by a session ID that is a tuple composed of >> an initiator part (ISID) and a target part (Target Portal Group >> Tag). *The ISID is explicitly specified by the initiator at session >> establishment. * The Target Portal Group Tag is implied by the >> initiator through the selection of the TCP endpoint at connection >> establishment. The TargetPortalGroupTag key must also be returned >> by the target as a confirmation during connection establishment >> when TargetName is given. >> >> Regards, >> Don >> >> >> On Thu, Jul 5, 2018 at 3:02 PM mayur kulkarni >> wrote: >> >>> did people move onto some other iscsi initiator that I don't know about >>> or my question is so stupid that no one cares to answer :( >>> >>> >>> On Wednesday, 27 June 2018 00:38:13 UTC+5:30, mayur kulkarni wrote: open-iscsi is not allocating same isid when logging in again, are there any plans to support it? if not then how to overcome this? am I missing anything? >>> -- >>> 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. >>> >> -- >> 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. >> > -- > 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. > -- 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.
Re: isid persistence?
for the SCSI PR to work, the same ISID should be given to the session, but the open-iscsi is implemented such that it starts giving isids from 0 (not considering the 3 byte prefix) and counts upwards. if an initiator logs out and logs in again, for the same iqn port configuration (on both target and initiator) the same isid should be allocated but that is not the case. hope, I was able to explain that. Thanks. Mayur On Fri, Jul 6, 2018 at 4:30 AM Donald Williams wrote: > Hello, > > It's an ID for that session what would be benefit of persistence?For > my purposes the fact it's only for that session helps me when going > through logs or traces. Makes it much easier to follow that session through > the iSCSID logs and on the storage device as well. > >- SSID (Session ID): A session between an iSCSI initiator and an > iSCSI target is defined by a session ID that is a tuple composed of > an initiator part (ISID) and a target part (Target Portal Group > Tag). *The ISID is explicitly specified by the initiator at session > establishment. * The Target Portal Group Tag is implied by the > initiator through the selection of the TCP endpoint at connection > establishment. The TargetPortalGroupTag key must also be returned > by the target as a confirmation during connection establishment > when TargetName is given. > > Regards, > Don > > > On Thu, Jul 5, 2018 at 3:02 PM mayur kulkarni > wrote: > >> did people move onto some other iscsi initiator that I don't know about >> or my question is so stupid that no one cares to answer :( >> >> >> On Wednesday, 27 June 2018 00:38:13 UTC+5:30, mayur kulkarni wrote: >>> >>> open-iscsi is not allocating same isid when logging in again, are there >>> any plans to support it? >>> >>> if not then how to overcome this? am I missing anything? >>> >> -- >> 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. >> > -- > 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. > -- 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.
Re: isid persistence?
Hello, It's an ID for that session what would be benefit of persistence?For my purposes the fact it's only for that session helps me when going through logs or traces. Makes it much easier to follow that session through the iSCSID logs and on the storage device as well. - SSID (Session ID): A session between an iSCSI initiator and an iSCSI target is defined by a session ID that is a tuple composed of an initiator part (ISID) and a target part (Target Portal Group Tag). *The ISID is explicitly specified by the initiator at session establishment. * The Target Portal Group Tag is implied by the initiator through the selection of the TCP endpoint at connection establishment. The TargetPortalGroupTag key must also be returned by the target as a confirmation during connection establishment when TargetName is given. Regards, Don On Thu, Jul 5, 2018 at 3:02 PM mayur kulkarni wrote: > did people move onto some other iscsi initiator that I don't know about or > my question is so stupid that no one cares to answer :( > > > On Wednesday, 27 June 2018 00:38:13 UTC+5:30, mayur kulkarni wrote: >> >> open-iscsi is not allocating same isid when logging in again, are there >> any plans to support it? >> >> if not then how to overcome this? am I missing anything? >> > -- > 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. > -- 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.
Re: isid persistence?
did people move onto some other iscsi initiator that I don't know about or my question is so stupid that no one cares to answer :( On Wednesday, 27 June 2018 00:38:13 UTC+5:30, mayur kulkarni wrote: > > open-iscsi is not allocating same isid when logging in again, are there > any plans to support it? > > if not then how to overcome this? am I missing anything? > -- 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.
isid persistence?
open-iscsi is not allocating same isid when logging in again, are there any plans to support it? if not then how to overcome this? am I missing anything? -- 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.