Dr. Volker Jaenisch wrote: > Hi Mike! > > Thank you for the fast reply. > > Mike Christie schrieb: >> I am not sure if this is what you are looking for but you can control >> which sessions get made. > If I get you right your solution is not excactly what I want. >> Do you have multiple portals per target and so >> we can create a session through each portal to the same target? >> Something like this: >> >> # iscsiadm -m node >> 22.214.171.124:3260,1 iqn.2001-04.com.home:meanminna >> 126.96.36.199:3260,1 iqn.2001-04.com.home:meanminna >> >> And right now we create two sessions (one through each portal on the >> target)? If so you can run >> >> iscsiadm -m node -T target -p ip:port,tpgt -o update -n node.startup -v >> manual >> > This means I can set the initiator on one specific node not to start the > session automatically?
Yeah. > > It would be possible to use this approach, but it seems to me no robust > solution. The handling of the manual sessions Ok. > have to be driven by the HA-System (heartbeat). I case of split brain > this will give a session to both machines - and booom! > > I think the a robust solution have to be a session counting instance and > thus at best located > at the target side. > > Is there really no Target-side appoach? > Go with Tomo's suggestion. > Is it possible to limit the number of sessions via the authentification > of the session (e.g. a Radius service )? > > Best regards, > > Volker > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to firstname.lastname@example.org To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~----------~----~----~----~------~----~------~--~---