Re: loopback interface IP problem
Hi Mike thanks for your reply. My answers follow bellow right next to your questions. Tkx/Regards, PECastro So you do the ifconfig to lo after iscsi is setup and logged in right? Is the ip address different from what you originally logged into? I mean originally you did iscsiadm -m node -T some_tagret -p original_ip -l Initially I did iscsiadm -m discovery -t sendtargets -p 10.238.17.201 And I started the iscsi daemon, from there after it all just worked. then when you do the ifconfig it is a new_ip, but the iscsi tools think you want to still connect to original_ip so you get the connect failed errors and eventually the replacement/recovery timeout errors. But I do an ifconfig on the loopback interface adding a new IP on a virtual lo:0 I'm not messing with the original IP 10.238.17.201 which is still associated with eth0 What you would have to do is create a session to original_ip, then create a new session to new_ip, and if you do not want to see IO errors then you would use dm-multipath over both sessions and that would handle switching from the old path to the new path for you. Coul you explain me how I would be able to achieve that?! How do I create a session to the new IP? Perform a another discovery ? How can I use multipath between the two sessions?! Jan 28 19:00:34 vmbox kernel: connection1:0: iscsi: detected conn error (1011) Jan 28 19:00:34 vmbox iscsid: Kernel reported iSCSI connection 1:0 error (1011) state (3) Jan 28 19:00:37 vmbox iscsid: connect failed (111) Jan 28 19:01:08 vmbox last message repeated 8 times- Hide quoted text - - Show quoted text -- Hide quoted text - - Show quoted text - --~--~-~--~~~---~--~~ 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: loopback interface IP problem
Hi Ulrich, My response follows bellow On Jan 29, 7:11 am, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de wrote: On 28 Jan 2009 at 11:06, PECastro wrote: Hi there. I'm mounting a standard iscsi target. I've been doing a lot of interesting nice things, I can see the disk, I can play with it and everything is very wonderfull ! :) Long story short, the disk has been running fine as if it was really attached. The problem started when I had the need to configure a virtual IP on lo:0 . My client box IP is something like 10.238.17.221 and I was trying to configure a 10.238.17.220 IP on lo:0 with ifconfig lo:0 10.238.17.220 netmask 255.255.255.128 broadcast 10.238.17.255 up Hi! I'd suggest running netstat -rn, and I assume the kernel will route your net via lo now. I don't think I understand what you mean... This is my routing table whilst having iscsi working correctly and before I set up the virtual IP. Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 10.238.17.128 0.0.0.0 255.255.255.128 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 10.238.17.254 0.0.0.0 UG0 0 0 eth0 And this is after I create the virtual IP agains lo:0 [r...@vmbox1 ~]# ifconfig lo:0 10.238.17.220 netmask 255.255.255.128 broadcast 10.238.17.255 up [r...@vmbox1 ~]# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 10.238.17.128 0.0.0.0 255.255.255.128 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 10.238.17.254 0.0.0.0 UG0 0 0 eth0 Regards, Ulrich but the moment I do this I seem to lose connection to the disk whilst iscsi is throwing errors to the log. Jan 28 19:00:34 vmbox kernel: connection1:0: iscsi: detected conn error (1011) Jan 28 19:00:34 vmbox iscsid: Kernel reported iSCSI connection 1:0 error (1011) state (3) Jan 28 19:00:37 vmbox iscsid: connect failed (111) Jan 28 19:01:08 vmbox last message repeated 8 times Whilst trying to dd the disk I also got this Jan 28 19:02:34 vmbox last message repeated 6 times Jan 28 19:02:34 vmbox kernel: session1: iscsi: session recovery timed out after 120 secs Jan 28 19:02:34 vmbox kernel: iscsi: cmd 0x28 is not queued (8) Jan 28 19:02:34 vmbox kernel: sd 1:0:0:0: SCSI error: return code = 0x0001 Jan 28 19:02:34 vmbox kernel: end_request: I/O error, dev sdb, sector 0 Jan 28 19:02:34 vmbox kernel: Buffer I/O error on device sdb, logical block 0 Jan 28 19:02:34 vmbox kernel: Buffer I/O error on device sdb, logical block 1 Jan 28 19:02:34 vmbox kernel: Buffer I/O error on device sdb, logical block 2 Jan 28 19:02:34 vmbox kernel: Buffer I/O error on device sdb, logical block 3 Jan 28 19:02:34 vmbox kernel: iscsi: cmd 0x28 is not queued (8) Jan 28 19:02:34 vmbox kernel: sd 1:0:0:0: SCSI error: return code = 0x0001 Jan 28 19:02:34 vmbox kernel: end_request: I/O error, dev sdb, sector 0 Jan 28 19:02:34 vmbox kernel: Buffer I/O error on device sdb, logical block 0 Jan 28 19:02:37 vmbox iscsid: connect failed (111) Jan 28 19:03:11 vmbox last message repeated 9 times I hacked the init.d start file so that iscsid would start with the maximum verbosity of 8. The version I'm currently working with is from the RPM iscsi-initiator- utils-6.2.0.868-0.7.el5 bundled for CENTOS. Can any one reproduce this problem or even better can anyone explain why is this happening and if there's a way of getting away with this?!- Hide quoted text - - Show quoted text - --~--~-~--~~~---~--~~ 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: loopback interface IP problem
Hi! Your output (if complete) looks quite strange, because I see no routes to lo. Also If lines were not wrapped, it would be easier to read. Something I have here looks like this: # netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.1.1 132.199.176.253 255.255.255.255 UGH 0 0 0 bond0 192.53.103.104 132.199.176.253 255.255.255.255 UGH 0 0 0 bond0 195.135.220.3 132.199.176.253 255.255.255.255 UGH 0 0 0 bond0 63.76.115.39132.199.176.253 255.255.255.255 UGH 0 0 0 bond0 213.31.172.75 132.199.176.253 255.255.255.255 UGH 0 0 0 bond0 212.201.100.143 132.199.176.253 255.255.255.255 UGH 0 0 0 bond0 132.199.1.15132.199.176.253 255.255.255.255 UGH 0 0 0 bond0 195.135.220.8 132.199.176.253 255.255.255.255 UGH 0 0 0 bond0 132.199.1.17132.199.176.253 255.255.255.255 UGH 0 0 0 bond0 192.53.103.103 132.199.176.253 255.255.255.255 UGH 0 0 0 bond0 194.94.155.48 132.199.176.253 255.255.255.240 UG0 0 0 bond0 132.199.0.0 0.0.0.0 255.255.0.0 U 0 0 0 bond0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 132.199.207.6 0.0.0.0 UG0 0 0 bond0 (Note the route to lo). Regards, Ulrich On 29 Jan 2009 at 2:29, PECastro wrote: Hi Ulrich, My response follows bellow On Jan 29, 7:11 am, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de wrote: On 28 Jan 2009 at 11:06, PECastro wrote: Hi there. I'm mounting a standard iscsi target. I've been doing a lot of interesting nice things, I can see the disk, I can play with it and everything is very wonderfull ! :) Long story short, the disk has been running fine as if it was really attached. The problem started when I had the need to configure a virtual IP on lo:0 . My client box IP is something like 10.238.17.221 and I was trying to configure a 10.238.17.220 IP on lo:0 with ifconfig lo:0 10.238.17.220 netmask 255.255.255.128 broadcast 10.238.17.255 up Hi! I'd suggest running netstat -rn, and I assume the kernel will route your net via lo now. I don't think I understand what you mean... This is my routing table whilst having iscsi working correctly and before I set up the virtual IP. Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 10.238.17.128 0.0.0.0 255.255.255.128 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 10.238.17.254 0.0.0.0 UG0 0 0 eth0 And this is after I create the virtual IP agains lo:0 [r...@vmbox1 ~]# ifconfig lo:0 10.238.17.220 netmask 255.255.255.128 broadcast 10.238.17.255 up [r...@vmbox1 ~]# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 10.238.17.128 0.0.0.0 255.255.255.128 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 10.238.17.254 0.0.0.0 UG0 0 0 eth0 Regards, Ulrich but the moment I do this I seem to lose connection to the disk whilst iscsi is throwing errors to the log. Jan 28 19:00:34 vmbox kernel: connection1:0: iscsi: detected conn error (1011) Jan 28 19:00:34 vmbox iscsid: Kernel reported iSCSI connection 1:0 error (1011) state (3) Jan 28 19:00:37 vmbox iscsid: connect failed (111) Jan 28 19:01:08 vmbox last message repeated 8 times Whilst trying to dd the disk I also got this Jan 28 19:02:34 vmbox last message repeated 6 times Jan 28 19:02:34 vmbox kernel: session1: iscsi: session recovery timed out after 120 secs Jan 28 19:02:34 vmbox kernel: iscsi: cmd 0x28 is not queued (8) Jan 28 19:02:34 vmbox kernel: sd 1:0:0:0: SCSI error: return code = 0x0001 Jan 28 19:02:34 vmbox kernel: end_request: I/O error, dev sdb, sector 0 Jan 28 19:02:34 vmbox kernel: Buffer I/O error on device sdb, logical block 0 Jan 28 19:02:34 vmbox kernel: Buffer I/O error on device sdb, logical block 1 Jan 28 19:02:34 vmbox kernel: Buffer I/O error on device sdb, logical block 2 Jan 28 19:02:34 vmbox kernel: Buffer I/O error on device sdb, logical block 3 Jan 28 19:02:34 vmbox kernel: iscsi: cmd 0x28 is not queued (8) Jan 28 19:02:34 vmbox kernel: sd 1:0:0:0: SCSI error: return code = 0x0001 Jan 28 19:02:34 vmbox kernel: end_request: I/O error, dev sdb, sector 0 Jan 28 19:02:34 vmbox kernel: Buffer I/O error on device sdb, logical block 0 Jan 28 19:02:37 vmbox iscsid: connect failed (111) Jan 28 19:03:11 vmbox last message repeated 9 times I hacked the init.d start file so that iscsid would start
Re: loopback interface IP problem
PECastro wrote: Hi there. I'm mounting a standard iscsi target. I've been doing a lot of interesting nice things, I can see the disk, I can play with it and everything is very wonderfull ! :) Long story short, the disk has been running fine as if it was really attached. The problem started when I had the need to configure a virtual IP on lo:0 . My client box IP is something like 10.238.17.221 and I was trying to configure a 10.238.17.220 IP on lo:0 with ifconfig lo:0 10.238.17.220 netmask 255.255.255.128 broadcast 10.238.17.255 up but the moment I do this I seem to lose connection to the disk whilst iscsi is throwing errors to the log. So you do the ifconfig to lo after iscsi is setup and logged in right? Is the ip address different from what you originally logged into? I mean originally you did iscsiadm -m node -T some_tagret -p original_ip -l then when you do the ifconfig it is a new_ip, but the iscsi tools think you want to still connect to original_ip so you get the connect failed errors and eventually the replacement/recovery timeout errors. What you would have to do is create a session to original_ip, then create a new session to new_ip, and if you do not want to see IO errors then you would use dm-multipath over both sessions and that would handle switching from the old path to the new path for you. Jan 28 19:00:34 vmbox kernel: connection1:0: iscsi: detected conn error (1011) Jan 28 19:00:34 vmbox iscsid: Kernel reported iSCSI connection 1:0 error (1011) state (3) Jan 28 19:00:37 vmbox iscsid: connect failed (111) Jan 28 19:01:08 vmbox last message repeated 8 times --~--~-~--~~~---~--~~ 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: loopback interface IP problem
On 28 Jan 2009 at 11:06, PECastro wrote: Hi there. I'm mounting a standard iscsi target. I've been doing a lot of interesting nice things, I can see the disk, I can play with it and everything is very wonderfull ! :) Long story short, the disk has been running fine as if it was really attached. The problem started when I had the need to configure a virtual IP on lo:0 . My client box IP is something like 10.238.17.221 and I was trying to configure a 10.238.17.220 IP on lo:0 with ifconfig lo:0 10.238.17.220 netmask 255.255.255.128 broadcast 10.238.17.255 up Hi! I'd suggest running netstat -rn, and I assume the kernel will route your net via lo now. Regards, Ulrich but the moment I do this I seem to lose connection to the disk whilst iscsi is throwing errors to the log. Jan 28 19:00:34 vmbox kernel: connection1:0: iscsi: detected conn error (1011) Jan 28 19:00:34 vmbox iscsid: Kernel reported iSCSI connection 1:0 error (1011) state (3) Jan 28 19:00:37 vmbox iscsid: connect failed (111) Jan 28 19:01:08 vmbox last message repeated 8 times Whilst trying to dd the disk I also got this Jan 28 19:02:34 vmbox last message repeated 6 times Jan 28 19:02:34 vmbox kernel: session1: iscsi: session recovery timed out after 120 secs Jan 28 19:02:34 vmbox kernel: iscsi: cmd 0x28 is not queued (8) Jan 28 19:02:34 vmbox kernel: sd 1:0:0:0: SCSI error: return code = 0x0001 Jan 28 19:02:34 vmbox kernel: end_request: I/O error, dev sdb, sector 0 Jan 28 19:02:34 vmbox kernel: Buffer I/O error on device sdb, logical block 0 Jan 28 19:02:34 vmbox kernel: Buffer I/O error on device sdb, logical block 1 Jan 28 19:02:34 vmbox kernel: Buffer I/O error on device sdb, logical block 2 Jan 28 19:02:34 vmbox kernel: Buffer I/O error on device sdb, logical block 3 Jan 28 19:02:34 vmbox kernel: iscsi: cmd 0x28 is not queued (8) Jan 28 19:02:34 vmbox kernel: sd 1:0:0:0: SCSI error: return code = 0x0001 Jan 28 19:02:34 vmbox kernel: end_request: I/O error, dev sdb, sector 0 Jan 28 19:02:34 vmbox kernel: Buffer I/O error on device sdb, logical block 0 Jan 28 19:02:37 vmbox iscsid: connect failed (111) Jan 28 19:03:11 vmbox last message repeated 9 times I hacked the init.d start file so that iscsid would start with the maximum verbosity of 8. The version I'm currently working with is from the RPM iscsi-initiator- utils-6.2.0.868-0.7.el5 bundled for CENTOS. Can any one reproduce this problem or even better can anyone explain why is this happening and if there's a way of getting away with this?! --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
