Apologies!!!
Hi, Very sorry for the previous mail which was actually intended for a few people but somehow, by mistake got to all of the contacts and other mailing lists I had ever sent a mail to. I will take care that such a human error won't repeat again. Apologies again!! Thanks and Regards, Nikhil --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
8 monkeys
(This is reportedly based on an actual experiment conducted in the U.K.) * * *Put eight monkeys in a room. In the middle of the room is a ladder, leading to a bunch of bananas hanging from a hook on the ceiling.* * * * * *Each time a monkey tries to climb the ladder, all the monkeys are sprayed with ice water, which makes them miserable. Soon enough, whenever a monkey attempts to climb the ladder, all of the other monkeys, not wanting to be sprayed, set upon him and beat him up. Soon, none of the eight monkeys ever attempts to climb the ladder.* * * * * *One of the original monkeys is then removed, and a new monkey is put in the room. Seeing the bananas and the ladder, he wonders why none of the other monkeys are doing the obvious. But undaunted, he immediately begins to climb the ladder.* * * * * *All the other monkeys fall upon him and beat him silly. He has no idea why. * * * *However, he no longer attempts to climb the ladder.* * * * * *A second original monkey is removed and replaced. The newcomer again attempts to climb the ladder, but all the other monkeys hammer the crap out of him.* * * *This includes the previous new monkey, who, grateful that he's not on the receiving end this time, participates in the beating because all the other monkeys are doing it. However, he has no idea why he's attacking the new monkey.* * * * * *One by one, all the original monkeys are replaced. Eight new monkeys are now in the room. None of them have ever been sprayed by ice water. None of them attempt to climb the ladder. All of them will enthusiastically beat up any new monkey who tries, without having any idea why.* * * * * *And that is how most companies' policies get established.* -- If you fool me once shame on you. If you fool me twice shame on me. \|||/ (o o) ooO-(_)-Ooo Nikhil Talpallikar --talli ;) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
which isns server would be the best
hi all, Which iSNS server would you recommend with regards to QoS and ease of usability. cheers, Nikhil \|||/ (o o) ooO-(_)-Ooo Nikhil Talpallikar --talli ;) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: iSNS discovery error (login)
hi, On Tue, Jan 20, 2009 at 12:03 AM, Mike Christie wrote: > > Nikhil Talpallikar wrote: > > Hi, > > I cannot login to a target if I do a discovery via iSNS server, but if I > do > > Are you doing > > iscsiadm -m discovery -t isns > yes > > > > discovery using SendTarget method I can login > > I could figure out something.but i am not able to resolve it. > > > > When I do discovery via ST the req->flags (Login PDU flags) are set > > to ISCSI_FLG_CSG_SECURITY, which calls CHAP authentication method. > > > > But when I do a discovery via iSNS server req->flags are set > > to ISCSI_FLG_CSG_LOGIN due to which it does not use CHAP authentication. > > > > It might be a bug in the open-iscsi setup code. > > Do you have the CHAP settings in /etc/iscsi/iscsid.conf > > ? yes > > > Then when you do > > iscsiadm -m discovery -t isns > > > for the targets found if you do > > iscsiadm -m node -T your_target -p ip:port > > > When it spits out the node info do you see the CHAP settings that should > get used? > > yes > > What version of the open-iscsi tools are using? Are then from > open-iscsi.org or from a distro? > > Its from a distro. RPM is open-iscsi-2.0.707-0.19.i586.rpm. > > > Why is this so? Does the iSNS server interfere with the login PDU??? > > > It can be a bug as you say. But where does the iSNS play a role in this bug. What I want to know is whether the initiator keeps some kind of mapping or a flag for targets discovered via iSNS which later interferes with the login PDU's CSG and NSG flags??? cheers, Nikhil -- If you fool me once shame on you. If you fool me twice shame on me. \|||/ (o o) ooO-(_)-Ooo Nikhil Talpallikar --talli ;) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: iSNS discovery error (login)
hi, On Tue, Jan 20, 2009 at 12:03 AM, Mike Christie wrote: > > Nikhil Talpallikar wrote: > > Hi, > > I cannot login to a target if I do a discovery via iSNS server, but if I > do > > Are you doing > > iscsiadm -m discovery -t isns > yes > > > > discovery using SendTarget method I can login > > I could figure out something.but i am not able to resolve it. > > > > When I do discovery via ST the req->flags (Login PDU flags) are set > > to ISCSI_FLG_CSG_SECURITY, which calls CHAP authentication method. > > > > But when I do a discovery via iSNS server req->flags are set > > to ISCSI_FLG_CSG_LOGIN due to which it does not use CHAP authentication. > > > > It might be a bug in the open-iscsi setup code. > > Do you have the CHAP settings in /etc/iscsi/iscsid.conf > > ? yes > > > Then when you do > > iscsiadm -m discovery -t isns > > > for the targets found if you do > > iscsiadm -m node -T your_target -p ip:port > > > When it spits out the node info do you see the CHAP settings that should > get used? > > yes > > What version of the open-iscsi tools are using? Are then from > open-iscsi.org or from a distro? > > Its from a distro. RPM is open-iscsi-2.0.707-0.19.i586.rpm. > > > Why is this so? Does the iSNS server interfere with the login PDU??? > > > > > > > > > > > It can be a bug as you say. But where does the iSNS play a role in this bug. What I want to know is whether the initiator keeps some kind of mapping or a flag for targets discovered via iSNS??? -- If you fool me once shame on you. If you fool me twice shame on me. \|||/ (o o) ooO-(_)-Ooo Nikhil Talpallikar --talli ;) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: iSNS discovery error (login)
I agree .. that is why I am having trouble (unable to connect the dots) .. and need some explanation if anyone has come across this kind of situation and solved it. Afterall what effect can iSNS discovery have on Login PDU ?? Just unable to connect and reason what I have observed. On Mon, Jan 19, 2009 at 3:23 PM, Dheeraj Sangamkar wrote: > As far as I know, your transactions/sessions with the iSNS server and those > with the iSCSI target should be independent. > The iSNS can give you target information and you can use it to connect to > target and login. > Targets themselves are iSNS clients like your initiator. They register the > information with the iSNS server that you as an iSNS client can use to > connect to the target. If there is a descrepency, your login can fail. > > However, once way chap authentication is a minimum according to the > standard and if your initiator offer this and the target mandates this, then > there could be trouble during login. > > Dheeraj > > > > On Mon, Jan 19, 2009 at 2:57 PM, Nikhil Talpallikar < > nikhil.talpalli...@gmail.com> wrote: > >> Hi, >> I cannot login to a target if I do a discovery via iSNS server, but if I >> do discovery using SendTarget method I can login >> I could figure out something.but i am not able to resolve it. >> >> When I do discovery via ST the req->flags (Login PDU flags) are set >> to ISCSI_FLG_CSG_SECURITY, which calls CHAP authentication method. >> >> But when I do a discovery via iSNS server req->flags are set >> to ISCSI_FLG_CSG_LOGIN due to which it does not use CHAP authentication. >> >> Why is this so? Does the iSNS server interfere with the login PDU??? >> >> >> >> -- >> If you fool me once shame on you. If you fool me twice shame on me. >> >> \|||/ >> (o o) >> ooO-(_)-Ooo >> >> Nikhil Talpallikar >> --talli ;) >> >> >> > > > -- > Simplicity of character is the natural result of profound thought. > > > > -- If you fool me once shame on you. If you fool me twice shame on me. \|||/ (o o) ooO-(_)-Ooo Nikhil Talpallikar --talli ;) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
iSNS discovery error (login)
Hi, I cannot login to a target if I do a discovery via iSNS server, but if I do discovery using SendTarget method I can login I could figure out something.but i am not able to resolve it. When I do discovery via ST the req->flags (Login PDU flags) are set to ISCSI_FLG_CSG_SECURITY, which calls CHAP authentication method. But when I do a discovery via iSNS server req->flags are set to ISCSI_FLG_CSG_LOGIN due to which it does not use CHAP authentication. Why is this so? Does the iSNS server interfere with the login PDU??? -- If you fool me once shame on you. If you fool me twice shame on me. \|||/ (o o) ooO-(_)-Ooo Nikhil Talpallikar --talli ;) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Is machine name allowed for login?
AFAIK, This might be because u might have multiple interfaces up with different ip address. Now a target can provide for a login event only via the specified ip:port as the target is mapped to that interface. On Thu, Jan 15, 2009 at 10:26 PM, Mike Christie wrote: > > HIMANSHU wrote: > > Hi all, > > > > I am asking very basic,simple question here.I am using "iscsi- > > initiator-utils-6.2.0.865-0.2.fc7". > > > > iscsiadm -m discovery -t sendtargets -p ip:port > > > > It says that "ip:port" should be specified.It worked with 'machine > > name' stead of 'ip' also. > > > > This works in discovery, but > > > iscsiadm -m node -T targetname -p ip:port --login > > > > But login command didn't work with replacing 'ip' by 'machine name'. > > > > does not work here because it is not implemented yet. You have to > actually pass the login command whatever the target gave us in > sendtargets discovery. So if it gave us a machine name you can use it. > If it gave us a ip then you have to use it. > > Do not ask when it will be fixed. It is on the TODO, but I do not have > much time right now. > > > > What should I do? is it way to login by 'machine name'.otherwise I > > will have to disallow discovery using 'machine name'. > > > > > > > > -- If you fool me once shame on you. If you fool me twice shame on me. \|||/ (o o) ooO-(_)-Ooo Nikhil Talpallikar --talli ;) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: open-iscsi isns registration fails using Solaris isns server
Hi, The iSNS server refuses connection to a network entity (eid) if there exists an object already registered with the same network entity id but different iSCSI node type(i.e. one initator and other target or vice versa). But if the iSCSI node type is same (in case of two targets on same network entity) iSNS server accepts the connection. Conclusion: If we use iSNS discovery method, we cannot have initiator and target on the same m/c with the same DNS name. cheers,nikhil On Wed, Jan 14, 2009 at 3:26 PM, Nikhil Talpallikar < nikhil.talpalli...@gmail.com> wrote: > ok it worked after a reboot.but dropping eid does not make sense to > me. What might be the exact cause of this eid being the FQDN not to be > authorised??? > > On Tue, Jan 13, 2009 at 11:27 PM, Nikhil wrote: > >> >> Hi, >> >> It does not work for me :( >> I used target name instead of eid . but the same err HELP! >> >> cheers, >> nikhil >> >> On Jan 5, 2:21 am, Albert Pauw wrote: >> > For the watchfull observant,the patch is shown in reverse, >> > it should read: >> > >> > --- usr/isns.c 2009-01-04 12:11:27.0 +0100 >> > +++ usr/isns.c.new 2009-01-04 11:17:43.0 +0100 >> > @@ -162,10 +162,10 @@ >> > >> > length += isns_tlv_set(&tlv, ISNS_ATTR_ISCSI_NAME, strlen >> > (name), name); >> > length += isns_tlv_set(&tlv, ISNS_ATTR_ENTITY_IDENTIFIER, >> > - strlen(eid), eid); >> > + strlen(name), name); >> > length += isns_tlv_set(&tlv, 0, 0, 0); >> > length += isns_tlv_set(&tlv, ISNS_ATTR_ENTITY_IDENTIFIER, >> > - strlen(eid), eid); >> > + strlen(name), name);; >> > >> > length += isns_tlv_set(&tlv, ISNS_ATTR_ENTITY_PROTOCOL, >> >sizeof(type), &type); >> >> >> > > > -- > If you fool me once shame on you. If you fool me twice shame on me. > > \|||/ > (o o) > ooO-(_)-Ooo > > Nikhil Talpallikar > --talli ;) > -- If you fool me once shame on you. If you fool me twice shame on me. \|||/ (o o) ooO-(_)-Ooo Nikhil Talpallikar --talli ;) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: open-iscsi isns registration fails using Solaris isns server
ok it worked after a reboot.but dropping eid does not make sense to me. What might be the exact cause of this eid being the FQDN not to be authorised??? On Tue, Jan 13, 2009 at 11:27 PM, Nikhil wrote: > > Hi, > > It does not work for me :( > I used target name instead of eid . but the same err HELP! > > cheers, > nikhil > > On Jan 5, 2:21 am, Albert Pauw wrote: > > For the watchfull observant,the patch is shown in reverse, > > it should read: > > > > --- usr/isns.c 2009-01-04 12:11:27.0 +0100 > > +++ usr/isns.c.new 2009-01-04 11:17:43.0 +0100 > > @@ -162,10 +162,10 @@ > > > > length += isns_tlv_set(&tlv, ISNS_ATTR_ISCSI_NAME, strlen > > (name), name); > > length += isns_tlv_set(&tlv, ISNS_ATTR_ENTITY_IDENTIFIER, > > - strlen(eid), eid); > > + strlen(name), name); > > length += isns_tlv_set(&tlv, 0, 0, 0); > > length += isns_tlv_set(&tlv, ISNS_ATTR_ENTITY_IDENTIFIER, > > - strlen(eid), eid); > > + strlen(name), name);; > > > > length += isns_tlv_set(&tlv, ISNS_ATTR_ENTITY_PROTOCOL, > > sizeof(type), &type); > > > -- If you fool me once shame on you. If you fool me twice shame on me. \|||/ (o o) ooO-(_)-Ooo Nikhil Talpallikar --talli ;) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Need help
Hi Prachi, If you need help asap u can share what specifically you want to do. cheers, nikhil On Tue, Jan 6, 2009 at 3:59 AM, Konrad Rzeszutek wrote: > > On Mon, Jan 05, 2009 at 12:15:11AM -0800, Prachi Bodke wrote: > > > > Hi all, > > I am new to this iSCSI.. > > I want to study the iSCSI interface with Linux. > > Take a look at RFC 3720, then at RFC 3720. > > It might also be useful to get acquainted with the SCSI specs hosted > by the T10 consortium (http://www.t10.org/scsi-3.htm) > > > Can any1 help me out in this..?? > > >From where to start?? using that interface, i want to develop one > > small application.. > > It might be also useful for you to take a look at iSCSI Target product > and their source code. That should give you some ideas on how > to implement an iSCSI target (if that is also what you are looking for). > > > > -- If you fool me once shame on you. If you fool me twice shame on me. \|||/ (o o) ooO-(_)-Ooo Nikhil Talpallikar --talli ;) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
