Re: need help before I kill myself
On Monday, April 8, 2013 12:57:36 PM UTC-4, Eddie Wai wrote: On Mon, 2013-04-08 at 04:25 -0700, lian...@gmail.com javascript: wrote: I finally got this to work but I have some questions about the card and its setup. Some specifics: Server with 4 onboard NICS (eth0, eth1, eth4, eth5), eth0 connected to array via 174.x.x.x (this port will be closed once setup complete, used for testing remotely atm) BC 5709 dual port (eth2, eth3), eth2 connected to array via 192.x.x.x Created and iface config with the following: # BEGIN RECORD 6.2.0-873.2.el6 ace.iscsi_ifacename = eth2 iface.transport_name = bnx2i iface.hwaddress = 00:10:18:F3:43:00 iface.ipaddress = 192.x.x.x iface.bootproto = static iface.subnet_mask = 255.255.255.0 iface.vlan_id = 0 iface.vlan_priority = 0 iface.iface_num = 0 iface.mtu = 9000 iface.port = 0 # END RECORD I read that ToE cards and other accelerator cards have a separate MAC for the accelerator engines. Is this true? So my dual port BC 5709 would have 4 mac addresses? If so I take the proper Mac to place in the iface config would be that of the accelerator? This is true. You should have 2 MACs and 2 SAN MACs. The SAN MACs are the ones you need to specify in the iface config file if you choose to specify the iface.hwaddress explicity. You should be able to find the corresponding SAN MACs under /sys/class/iscsi_host. # iscsiadm -m session -o show tcp: [1] 192.x.x.x:3260,0 iqn.2000-01.com.synology:san.quincy Is the 'tcp' telling me it is not properly setup? should it be bnx2i at the beginning of the above result? Yes, the bnx2i transport name would be indicated upon a successful offload connection. I was also under the impression that when I created an iface config file it would act as the default and only connection. I say this because the connection with the server's nic is still appearing when I reboot. How do I stop this from happening and force the 5709 to be the only interface? Right now I just firewalled the 174.x.x.x network from the array but that causes a long delay as it times out at boot time, not a very elegant fix. I did delete all traces of earlier discovered targets with the 174.x.x.x IP. If the node created already contains the correct transport_name, then perhaps the MAC address specified was not the SAN MAC. This would lead to a fallback to use software iSCSI for your connection. On Thursday, April 4, 2013 2:46:12 PM UTC-4, gee...@gmail.com wrote: Hello, I have been trying to setup an iSCSI storage array for several weeks now. I have some things working but others are not. I am running out of time and am willing to to hire someone with the skill and experience to help me out. If this kind of request is not accepted on this list I apologize and will stop posting at the first notice I receive. If it's ok then please respond. Here is what I have and need help with. I have purchased a Synology DS1812+, running the latest DSM management software and configured with 14 TB of storage. I want to use the array for my /home and /backup partitions on my web hosting servers. There will be about 3-4 servers using it for this purpose. The individiual servers will be running CentOS, various versions, and open-iscsi as the initiator. I have purchaes a few ToE cards (the broadcom 5709) for the physical connections. I am currently working on a new server (centos 6.4) and testing the concept out. I have been able to connect using the server's onboard NIC but not the ToE card. I have played with the iface config but it refuses to connect. I am not going to post the details as I am hoping to have someone help me out with this. I am not a very experienced Linux administrator but I can manage with proper instruction. Thanks for reading jservices -- 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+...@googlegroups.com javascript:. To post to this group, send email to open-...@googlegroups.comjavascript:. Visit this group at http://groups.google.com/group/open-iscsi?hl=en. For more options, visit https://groups.google.com/groups/opt_out. You should be able to find the corresponding SAN MACs under /sys/class/iscsi_host. I have looked in this location but found an empty folder. Can someone provide a way to obtain the actual SAN mac address form a broadcom 5709 ToE card? Without it I can't seem to move forward. Thanks! -- You received
Re: need help before I kill myself
On 04/04/2013 01:46 PM, geeo...@gmail.com wrote: Hello, I have been trying to setup an iSCSI storage array for several weeks now. I have some things working but others are not. I am running out of time and am willing to to hire someone with the skill and experience to help me out. If this kind of request is not accepted on this list I apologize and will stop posting at the first notice I receive. If it's ok then please respond. Here is what I have and need help with. I have purchased a Synology DS1812+, running the latest DSM management software and configured with 14 TB of storage. I want to use the array for my /home and /backup partitions on my web hosting servers. There will be about 3-4 servers using it for this purpose. The individiual servers will be running CentOS, various versions, and open-iscsi as the initiator. I have purchaes a few ToE cards (the broadcom 5709) for the physical connections. I am currently working on a new server (centos 6.4) and testing the concept out. I have been able to connect using the server's onboard NIC but not the ToE card. I have played with the iface config but it refuses to connect. For Centos 6.4 you should be able to use the default bnx2i ifaces. I am not going to post the details as I am hoping to have someone help me out with this. I am not sure what that means. We need some details :) Could you post the error message you get when you try to login with iscsiadm -m node -l and also post the /var/log/messages for when you try to login. -- 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 http://groups.google.com/group/open-iscsi?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: need help before I kill myself
On 08.04.2013 08:00, Mike Christie wrote: On 04/04/2013 01:46 PM, geeo...@gmail.com wrote: Hello, I have been trying to setup an iSCSI storage array for several weeks now. I have some things working but others are not. I am running out of time and am willing to to hire someone with the skill and experience to help me out. If this kind of request is not accepted on this list I apologize and will stop posting at the first notice I receive. If it's ok then please respond. Here is what I have and need help with. I have purchased a Synology DS1812+, running the latest DSM management software and configured with 14 TB of storage. I want to use the array for my /home and /backup partitions on my web hosting servers. There will be about 3-4 servers using it for this purpose. The individiual servers will be running CentOS, various versions, and open-iscsi as the initiator. I have purchaes a few ToE cards (the broadcom 5709) for the physical connections. I am currently working on a new server (centos 6.4) and testing the concept out. I have been able to connect using the server's onboard NIC but not the ToE card. I have played with the iface config but it refuses to connect. For Centos 6.4 you should be able to use the default bnx2i ifaces. These also require special free and nonfree firmware. Check your kernel config! Check your firmware-nonfree package! Look at: CONFIG_BNX2 CONFIG_SCSI_BNX2_ISCSI Kernel: $ ls firmware/bnx2 bnx2-mips-06-6.2.1.fwbnx2-rv2p-06-6.0.15.fw.ihex bnx2-mips-06-6.2.1.fw.ihex bnx2-rv2p-09-6.0.17.fw bnx2-mips-09-6.2.1a.fw bnx2-rv2p-09-6.0.17.fw.ihex bnx2-mips-09-6.2.1a.fw.ihex bnx2-rv2p-09ax-6.0.17.fw bnx2-rv2p-06-6.0.15.fw bnx2-rv2p-09ax-6.0.17.fw.ihex If compiled manually: $ make install modules_install firmware_install firmware-nonfree: $ ls bnx2/bnx2 bnx2-mips-06-5.0.0.j3.fw bnx2-rv2p-06-5.0.0.j3.fw bnx2-mips-06-6.2.1.fw bnx2-rv2p-06-6.0.15.fw bnx2-mips-06-6.2.3.fw bnx2-rv2p-09-5.0.0.j3.fw bnx2-mips-09-5.0.0.j3.fw bnx2-rv2p-09-6.0.17.fw bnx2-mips-09-6.2.1a.fwbnx2-rv2p-09ax-5.0.0.j3.fw bnx2-mips-09-6.2.1b.fwbnx2-rv2p-09ax-6.0.17.fw Cheers, Sebastian -- 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 http://groups.google.com/group/open-iscsi?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: need help before I kill myself
On 04/08/2013 11:16 AM, Sebastian Riemer wrote: For Centos 6.4 you should be able to use the default bnx2i ifaces. These also require special free and nonfree firmware. Check your kernel config! Check your firmware-nonfree package! Look at: CONFIG_BNX2 CONFIG_SCSI_BNX2_ISCSI Maybe not your exactly your situation but keep in mind that that at least the on-board Broadcoms in Dell servers need a special license key in order for the firmware to function with TOE! Without that everything looks OK, you see TOE all over the place (BIOS screens, driver loading etc) but it just won't work; In Dell boxes the license key looks like a really small USB token to be inserted directly into the motherboard. Can only hope that your interfaces came with the said license embedded or that they don't need it. -- 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 http://groups.google.com/group/open-iscsi?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: need help before I kill myself
I finally got this to work but I have some questions about the card and its setup. Some specifics: Server with 4 onboard NICS (eth0, eth1, eth4, eth5), eth0 connected to array via 174.x.x.x (this port will be closed once setup complete, used for testing remotely atm) BC 5709 dual port (eth2, eth3), eth2 connected to array via 192.x.x.x Created and iface config with the following: # BEGIN RECORD 6.2.0-873.2.el6 ace.iscsi_ifacename = eth2 iface.transport_name = bnx2i iface.hwaddress = 00:10:18:F3:43:00 iface.ipaddress = 192.x.x.x iface.bootproto = static iface.subnet_mask = 255.255.255.0 iface.vlan_id = 0 iface.vlan_priority = 0 iface.iface_num = 0 iface.mtu = 9000 iface.port = 0 # END RECORD I read that ToE cards and other accelerator cards have a separate MAC for the accelerator engines. Is this true? So my dual port BC 5709 would have 4 mac addresses? If so I take the proper Mac to place in the iface config would be that of the accelerator? # iscsiadm -m session -o show tcp: [1] 192.x.x.x:3260,0 iqn.2000-01.com.synology:san.quincy Is the 'tcp' telling me it is not properly setup? should it be bnx2i at the beginning of the above result? I was also under the impression that when I created an iface config file it would act as the default and only connection. I say this because the connection with the server's nic is still appearing when I reboot. How do I stop this from happening and force the 5709 to be the only interface? Right now I just firewalled the 174.x.x.x network from the array but that causes a long delay as it times out at boot time, not a very elegant fix. I did delete all traces of earlier discovered targets with the 174.x.x.x IP. On Thursday, April 4, 2013 2:46:12 PM UTC-4, gee...@gmail.com wrote: Hello, I have been trying to setup an iSCSI storage array for several weeks now. I have some things working but others are not. I am running out of time and am willing to to hire someone with the skill and experience to help me out. If this kind of request is not accepted on this list I apologize and will stop posting at the first notice I receive. If it's ok then please respond. Here is what I have and need help with. I have purchased a Synology DS1812+, running the latest DSM management software and configured with 14 TB of storage. I want to use the array for my /home and /backup partitions on my web hosting servers. There will be about 3-4 servers using it for this purpose. The individiual servers will be running CentOS, various versions, and open-iscsi as the initiator. I have purchaes a few ToE cards (the broadcom 5709) for the physical connections. I am currently working on a new server (centos 6.4) and testing the concept out. I have been able to connect using the server's onboard NIC but not the ToE card. I have played with the iface config but it refuses to connect. I am not going to post the details as I am hoping to have someone help me out with this. I am not a very experienced Linux administrator but I can manage with proper instruction. Thanks for reading jservices -- 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 http://groups.google.com/group/open-iscsi?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: need help before I kill myself
On 08.04.2013 13:25, liano...@gmail.com wrote: Created and iface config with the following: # BEGIN RECORD 6.2.0-873.2.el6 ace.iscsi_ifacename = eth2 iface.transport_name = bnx2i iface.hwaddress = 00:10:18:F3:43:00 iface.ipaddress = 192.x.x.x iface.bootproto = static iface.subnet_mask = 255.255.255.0 iface.vlan_id = 0 iface.vlan_priority = 0 iface.iface_num = 0 iface.mtu = 9000 iface.port = 0 # END RECORD [...] # iscsiadm -m session -o show tcp: [1] 192.x.x.x:3260,0 iqn.2000-01.com.synology:san.quincy Is the 'tcp' telling me it is not properly setup? should it be bnx2i at the beginning of the above result? Yes, that's wrong. It has been discovered with the default transport name. So you have to tell open-iscsi which interface to use (e.g. by editing the discovered data base entry in /etc/iscsi/nodes). You can also use iscsiadm. Change this line: iface.transport_name = tcp Into: iface.transport_name = bnx2i We already had this situation with iSER. There it is the same. Cheers, Sebastian -- 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 http://groups.google.com/group/open-iscsi?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: need help before I kill myself
On Mon, 2013-04-08 at 04:25 -0700, liano...@gmail.com wrote: I finally got this to work but I have some questions about the card and its setup. Some specifics: Server with 4 onboard NICS (eth0, eth1, eth4, eth5), eth0 connected to array via 174.x.x.x (this port will be closed once setup complete, used for testing remotely atm) BC 5709 dual port (eth2, eth3), eth2 connected to array via 192.x.x.x Created and iface config with the following: # BEGIN RECORD 6.2.0-873.2.el6 ace.iscsi_ifacename = eth2 iface.transport_name = bnx2i iface.hwaddress = 00:10:18:F3:43:00 iface.ipaddress = 192.x.x.x iface.bootproto = static iface.subnet_mask = 255.255.255.0 iface.vlan_id = 0 iface.vlan_priority = 0 iface.iface_num = 0 iface.mtu = 9000 iface.port = 0 # END RECORD I read that ToE cards and other accelerator cards have a separate MAC for the accelerator engines. Is this true? So my dual port BC 5709 would have 4 mac addresses? If so I take the proper Mac to place in the iface config would be that of the accelerator? This is true. You should have 2 MACs and 2 SAN MACs. The SAN MACs are the ones you need to specify in the iface config file if you choose to specify the iface.hwaddress explicity. You should be able to find the corresponding SAN MACs under /sys/class/iscsi_host. # iscsiadm -m session -o show tcp: [1] 192.x.x.x:3260,0 iqn.2000-01.com.synology:san.quincy Is the 'tcp' telling me it is not properly setup? should it be bnx2i at the beginning of the above result? Yes, the bnx2i transport name would be indicated upon a successful offload connection. I was also under the impression that when I created an iface config file it would act as the default and only connection. I say this because the connection with the server's nic is still appearing when I reboot. How do I stop this from happening and force the 5709 to be the only interface? Right now I just firewalled the 174.x.x.x network from the array but that causes a long delay as it times out at boot time, not a very elegant fix. I did delete all traces of earlier discovered targets with the 174.x.x.x IP. If the node created already contains the correct transport_name, then perhaps the MAC address specified was not the SAN MAC. This would lead to a fallback to use software iSCSI for your connection. On Thursday, April 4, 2013 2:46:12 PM UTC-4, gee...@gmail.com wrote: Hello, I have been trying to setup an iSCSI storage array for several weeks now. I have some things working but others are not. I am running out of time and am willing to to hire someone with the skill and experience to help me out. If this kind of request is not accepted on this list I apologize and will stop posting at the first notice I receive. If it's ok then please respond. Here is what I have and need help with. I have purchased a Synology DS1812+, running the latest DSM management software and configured with 14 TB of storage. I want to use the array for my /home and /backup partitions on my web hosting servers. There will be about 3-4 servers using it for this purpose. The individiual servers will be running CentOS, various versions, and open-iscsi as the initiator. I have purchaes a few ToE cards (the broadcom 5709) for the physical connections. I am currently working on a new server (centos 6.4) and testing the concept out. I have been able to connect using the server's onboard NIC but not the ToE card. I have played with the iface config but it refuses to connect. I am not going to post the details as I am hoping to have someone help me out with this. I am not a very experienced Linux administrator but I can manage with proper instruction. Thanks for reading jservices -- 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 http://groups.google.com/group/open-iscsi?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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 http://groups.google.com/group/open-iscsi?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
need help before I kill myself
Hello, I have been trying to setup an iSCSI storage array for several weeks now. I have some things working but others are not. I am running out of time and am willing to to hire someone with the skill and experience to help me out. If this kind of request is not accepted on this list I apologize and will stop posting at the first notice I receive. If it's ok then please respond. Here is what I have and need help with. I have purchased a Synology DS1812+, running the latest DSM management software and configured with 14 TB of storage. I want to use the array for my /home and /backup partitions on my web hosting servers. There will be about 3-4 servers using it for this purpose. The individiual servers will be running CentOS, various versions, and open-iscsi as the initiator. I have purchaes a few ToE cards (the broadcom 5709) for the physical connections. I am currently working on a new server (centos 6.4) and testing the concept out. I have been able to connect using the server's onboard NIC but not the ToE card. I have played with the iface config but it refuses to connect. I am not going to post the details as I am hoping to have someone help me out with this. I am not a very experienced Linux administrator but I can manage with proper instruction. Thanks for reading jservices -- 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 http://groups.google.com/group/open-iscsi?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Need help debugging 1011 connection errors
I seem to be getting this over and over again in the logs: Jun 12 09:13:40 example-server kernel: connection0:0: iscsi: detected conn error (1011) Jun 12 09:13:40 example-server iscsid: Kernel reported iSCSI connection 0:0 error (1011) state (3) Jun 12 09:13:43 example-server iscsid: connection0:0 is operational after recovery (1 attempts) Jun 12 09:14:06 example-server iscsid: Got nop in, but kernel supports nop handling. I'm not really sure what the 1011 error indicates. Also the bit about the Got nop in, but kernel supports nop handling. message is confusing as well. It is the first time I have ever seen it and I'm wondering if it is indicating a problem. The kernel on the machine is quite old and could be the culprit either because drivers or whatever else. Currently the kernel is: 2.6.18-8.1.14.el5 Hopefully, going to update it shortly to see if it fixes any of the issues but thought I would post here to see if anyone had any input. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To view this discussion on the web visit https://groups.google.com/d/msg/open-iscsi/-/AyeuqA44Gj0J. 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?hl=en.
Re: Need help debugging 1011 connection errors
On 06/12/2012 11:18 AM, awiddersh...@hotmail.com wrote: I seem to be getting this over and over again in the logs: Jun 12 09:13:40 example-server kernel: connection0:0: iscsi: detected conn error (1011) 1011 is just a generic error code meaning there was a connection problem. We do not know what caused it. It could have been the target died or someone pulled a cable or a bug. We do not have enough info. Jun 12 09:13:40 example-server iscsid: Kernel reported iSCSI connection 0:0 error (1011) state (3) Jun 12 09:13:43 example-server iscsid: connection0:0 is operational after recovery (1 attempts) Jun 12 09:14:06 example-server iscsid: Got nop in, but kernel supports nop handling. This indicates something went screwy. The kernel has that el5 string, so are you using Centos or RHEL? If so what is the iscsi tools version rpm -q iscsi-initiator-utils Is there anything else in the log before or after that? Something about a nop or ping timing out? What type of target is this with? We used to send the nops as pings from userspace, but later moved it to the kernel. The userspace tools support both (if the kernel does not support it then we drop down and send from userspace). The message above indicates that the kernel supports nops, but for some reason the kernel sent it to userspace to handle. This should never happen. It could happen if the target is not setting something on the iscsi packet correctly. To detect this we could take a wireshark/tcpdump trace and see the packet causing the problem. -- 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?hl=en.
Re: Need help debugging 1011 connection errors
This indicates something went screwy. The kernel has that el5 string, so are you using Centos or RHEL? If so what is the iscsi tools version It is RHEL5 and the tools are as follows: iscsi-initiator-utils-6.2.0.872-13.el5 Is there anything else in the log before or after that? Something about a nop or ping timing out? No, it is just went I sent you repeated over and over again. What type of target is this with? SUN COMSTAR It could happen if the target is not setting something on the iscsi packet correctly. To detect this we could take a wireshark/tcpdump trace and see the packet causing the problem. I doubt this. We have about 300 other hosts connected to this without an issue. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To view this discussion on the web visit https://groups.google.com/d/msg/open-iscsi/-/Zl8RzmwW7uoJ. 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?hl=en.
Re: Need help debugging 1011 connection errors
On 06/12/2012 11:33 AM, awiddersh...@hotmail.com wrote: This indicates something went screwy. The kernel has that el5 string, so are you using Centos or RHEL? If so what is the iscsi tools version It is RHEL5 and the tools are as follows: iscsi-initiator-utils-6.2.0.872-13.el5 Is there anything else in the log before or after that? Something about a nop or ping timing out? No, it is just went I sent you repeated over and over again. What type of target is this with? SUN COMSTAR It could happen if the target is not setting something on the iscsi packet correctly. To detect this we could take a wireshark/tcpdump trace and see the packet causing the problem. I doubt this. We have about 300 other hosts connected to this without an issue. Are those other hosts running the same kernel version and tools as the machine you hit this issue with? -- 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?hl=en.
Re: Need help debugging 1011 connection errors
On 06/12/2012 11:41 AM, Mike Christie wrote: On 06/12/2012 11:33 AM, awiddersh...@hotmail.com wrote: This indicates something went screwy. The kernel has that el5 string, so are you using Centos or RHEL? If so what is the iscsi tools version It is RHEL5 and the tools are as follows: iscsi-initiator-utils-6.2.0.872-13.el5 Is there anything else in the log before or after that? Something about a nop or ping timing out? No, it is just went I sent you repeated over and over again. What type of target is this with? SUN COMSTAR It could happen if the target is not setting something on the iscsi packet correctly. To detect this we could take a wireshark/tcpdump trace and see the packet causing the problem. I doubt this. We have about 300 other hosts connected to this without an issue. Are those other hosts running the same kernel version and tools as the machine you hit this issue with? If it is easy to replicate, could you send a trace? -- 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?hl=en.
Re: Need help debugging 1011 connection errors
On 06/12/2012 11:45 AM, Mike Christie wrote: On 06/12/2012 11:41 AM, Mike Christie wrote: On 06/12/2012 11:33 AM, awiddersh...@hotmail.com wrote: This indicates something went screwy. The kernel has that el5 string, so are you using Centos or RHEL? If so what is the iscsi tools version It is RHEL5 and the tools are as follows: iscsi-initiator-utils-6.2.0.872-13.el5 Is there anything else in the log before or after that? Something about a nop or ping timing out? No, it is just went I sent you repeated over and over again. What type of target is this with? SUN COMSTAR It could happen if the target is not setting something on the iscsi packet correctly. To detect this we could take a wireshark/tcpdump trace and see the packet causing the problem. I doubt this. We have about 300 other hosts connected to this without an issue. Are those other hosts running the same kernel version and tools as the machine you hit this issue with? If it is easy to replicate, could you send a trace? Actually. Do not waste your time. Just update your kernel. There is a bug, because that kernel you are using does not support kernel nops as pings and is returning a different error code than what userspace is expecting when checking if the kernel supports it. -- 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?hl=en.
Re: Need help debugging 1011 connection errors
Awesome. I'll do that and hopefully everything is happy afterward including these random connection issues. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To view this discussion on the web visit https://groups.google.com/d/msg/open-iscsi/-/grCIZutEzE4J. 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?hl=en.
Re: Need help debugging 1011 connection errors
On 06/12/2012 11:55 AM, Mike Christie wrote: On 06/12/2012 11:45 AM, Mike Christie wrote: On 06/12/2012 11:41 AM, Mike Christie wrote: On 06/12/2012 11:33 AM, awiddersh...@hotmail.com wrote: This indicates something went screwy. The kernel has that el5 string, so are you using Centos or RHEL? If so what is the iscsi tools version It is RHEL5 and the tools are as follows: iscsi-initiator-utils-6.2.0.872-13.el5 Is there anything else in the log before or after that? Something about a nop or ping timing out? No, it is just went I sent you repeated over and over again. What type of target is this with? SUN COMSTAR It could happen if the target is not setting something on the iscsi packet correctly. To detect this we could take a wireshark/tcpdump trace and see the packet causing the problem. I doubt this. We have about 300 other hosts connected to this without an issue. Are those other hosts running the same kernel version and tools as the machine you hit this issue with? If it is easy to replicate, could you send a trace? Actually. Do not waste your time. Just update your kernel. On second or third thought could you send a trace? With the bug below it means that we are not sending nops at all, so it must be coming from the target or the kernel code is really messing up or there is corruption somewhere because we are misreading packet headers. There is a bug, because that kernel you are using does not support kernel nops as pings and is returning a different error code than what userspace is expecting when checking if the kernel supports it. -- 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?hl=en.
Re: Need help debugging 1011 connection errors
On 06/12/2012 12:09 PM, Mike Christie wrote: On 06/12/2012 11:55 AM, Mike Christie wrote: On 06/12/2012 11:45 AM, Mike Christie wrote: On 06/12/2012 11:41 AM, Mike Christie wrote: On 06/12/2012 11:33 AM, awiddersh...@hotmail.com wrote: This indicates something went screwy. The kernel has that el5 string, so are you using Centos or RHEL? If so what is the iscsi tools version It is RHEL5 and the tools are as follows: iscsi-initiator-utils-6.2.0.872-13.el5 Is there anything else in the log before or after that? Something about a nop or ping timing out? No, it is just went I sent you repeated over and over again. What type of target is this with? SUN COMSTAR It could happen if the target is not setting something on the iscsi packet correctly. To detect this we could take a wireshark/tcpdump trace and see the packet causing the problem. I doubt this. We have about 300 other hosts connected to this without an issue. Are those other hosts running the same kernel version and tools as the machine you hit this issue with? If it is easy to replicate, could you send a trace? Actually. Do not waste your time. Just update your kernel. On second or third thought could you send a trace? With the bug below it means that we are not sending nops at all, so it must be coming from the target or the kernel code is really messing up or there is corruption somewhere because we are misreading packet headers. Sorry. Ignore that. I was right the first time. It is such old code. I have not looked at it for a long time, so my eyes got cross eyed looking at different versions :) It looks like target could send a nop as a ping. We do not reply, because of the bug I mentioned, then target drops connection. This will happen over an over. So please just upgrade. Do not waste your time getting me traces. Sorry for the confusion. -- 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?hl=en.
RE: Need help debugging 1011 connection errors
Understood. -- 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?hl=en.
Re: Need help debugging detected conn error (1010) problem
Thanks for the help Mike. I was able to get a wireshark trace of this problem and found that the target was misbehaving by returning out-of-order DataIn PDUs even though open-iscsi initiator had negotiated DataPDUInOrder=Yes. Turns out there was a firmware update available that fixed this problem in the iSCSI target. On Fri, Mar 30, 2012 at 9:42 PM, Mike Christie micha...@cs.wisc.edu wrote: On 03/30/2012 03:36 PM, iscsi developer man wrote: I'm trying to debug the following open-iscsi initiator errors that are reported in /var/log/messages: Is there something before this in the logs? It is rare to see this error value. I have only have seen this when the scsi eh runs and we are sending aborts and resets and the target and initiator get out of sync and we end up seeing a task response for a task we thought was aborted or cleaned up from a abort. Trying doing echo 1 /sys/modules/libiscsi/parameters/debug_libiscsi_eh Then rerun your targets. Do you see something about aborts and resets getting sent before the 1010 error, Mar 30 14:19:31 R415-08 kernel: [56802.859946] connection194:0: detected conn error (1010) Mar 30 14:19:34 R415-08 kernel: [56805.373323] connection194:0: detected conn error (1020) Mar 30 14:21:58 R415-08 kernel: [56949.620808] connection117:0: detected conn error (1010) Mar 30 14:22:01 R415-08 kernel: [56952.634359] connection117:0: detected conn error (1020) From the investigation I've done so far, the 1010 error means ISCSI_ERR_BAD_ITT, which I assume means that the initiator received an iSCSI PDU that contained an ITT that was unexpected. The 1020 error always follows the 1010 error and it apparently means the initiator closed the connection, is that correct? You normally see it when the target closes the connection on us, but with some targets you can see it if we send a logout. The target might send the logout response and close the connection really quickly and before we completely handle the logout response we see the connection closed event notification. Is there a way to get the unexpected ITT so I can compare it to the iSCSI target debug logs and a wireshark network trace? Not really. It is normally a bad target type of issue, or a race/code bug. Would setting the iscsid debug level to a non-zero value help? If so, No. -- 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?hl=en.
Re: Need help debugging detected conn error (1010) problem
On 03/30/2012 03:36 PM, iscsi developer man wrote: I'm trying to debug the following open-iscsi initiator errors that are reported in /var/log/messages: Is there something before this in the logs? It is rare to see this error value. I have only have seen this when the scsi eh runs and we are sending aborts and resets and the target and initiator get out of sync and we end up seeing a task response for a task we thought was aborted or cleaned up from a abort. Trying doing echo 1 /sys/modules/libiscsi/parameters/debug_libiscsi_eh Then rerun your targets. Do you see something about aborts and resets getting sent before the 1010 error, Mar 30 14:19:31 R415-08 kernel: [56802.859946] connection194:0: detected conn error (1010) Mar 30 14:19:34 R415-08 kernel: [56805.373323] connection194:0: detected conn error (1020) Mar 30 14:21:58 R415-08 kernel: [56949.620808] connection117:0: detected conn error (1010) Mar 30 14:22:01 R415-08 kernel: [56952.634359] connection117:0: detected conn error (1020) From the investigation I've done so far, the 1010 error means ISCSI_ERR_BAD_ITT, which I assume means that the initiator received an iSCSI PDU that contained an ITT that was unexpected. The 1020 error always follows the 1010 error and it apparently means the initiator closed the connection, is that correct? You normally see it when the target closes the connection on us, but with some targets you can see it if we send a logout. The target might send the logout response and close the connection really quickly and before we completely handle the logout response we see the connection closed event notification. Is there a way to get the unexpected ITT so I can compare it to the iSCSI target debug logs and a wireshark network trace? Not really. It is normally a bad target type of issue, or a race/code bug. Would setting the iscsid debug level to a non-zero value help? If so, No. -- 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?hl=en.
Re: Need help with multipath and iscsi in CentOS 5.4
Using a single path (without MPIO) as a baseline: With bonding I saw, on average 99-100% of the speed (worst case 78%) of a single path. With MPIO (2 nics) I saw, on average 82% of the speed (worst case 66%) of the single path. With MPIO with one nic (ifconfig downed the second), I saw, on average 86% of the speed (worst case 66%) of the single path. There were situations where bonding and MPIO both scored slightly higher than the single path, but that is most likely due to differences on the array, since the tests weren't run back to back. --Kyle On 1/6/10, Mike Christie micha...@cs.wisc.edu wrote: On 12/30/2009 11:48 AM, Kyle Schmitt wrote: On Wed, Dec 9, 2009 at 8:52 PM, Mike Christiemicha...@cs.wisc.edu wrote: So far single connections work: If I setup the box to use one NIC, I get one connection and can use it just fine. Could you send the /var/log/messages for when you run the login command so I can see the disk info? Sorry for the delay. In the meanwhile I tore down the server and re-configured it using ethernet bonding. It worked, according to iozone, provided moderately better throughput than the single connection I got before. Moderately. Measurably. Not significantly. I tore it down after that and reconfigured again using MPIO, and funny enough, this time it worked. I can access the lun now using two devices (sdb and sdd), and both ethernet devices that connect to iscsi show traffic. The weird thing is that aside from writing bonding was measurably faster than MPIO. Does that seem right? With MPIO are you seeing the same throughput you would see if you only used one path at a time? -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@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?hl=en.
Re: Need help with multipath and iscsi in CentOS 5.4
On 12/30/2009 11:48 AM, Kyle Schmitt wrote: On Wed, Dec 9, 2009 at 8:52 PM, Mike Christiemicha...@cs.wisc.edu wrote: So far single connections work: If I setup the box to use one NIC, I get one connection and can use it just fine. Could you send the /var/log/messages for when you run the login command so I can see the disk info? Sorry for the delay. In the meanwhile I tore down the server and re-configured it using ethernet bonding. It worked, according to iozone, provided moderately better throughput than the single connection I got before. Moderately. Measurably. Not significantly. I tore it down after that and reconfigured again using MPIO, and funny enough, this time it worked. I can access the lun now using two devices (sdb and sdd), and both ethernet devices that connect to iscsi show traffic. The weird thing is that aside from writing bonding was measurably faster than MPIO. Does that seem right? With MPIO are you seeing the same throughput you would see if you only used one path at a time? -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@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?hl=en.
Re: Need help with multipath and iscsi in CentOS 5.4
On Wed, Dec 30, 2009 at 11:48:31AM -0600, Kyle Schmitt wrote: On Wed, Dec 9, 2009 at 8:52 PM, Mike Christie micha...@cs.wisc.edu wrote: So far single connections work: If I setup the box to use one NIC, I get one connection and can use it just fine. Could you send the /var/log/messages for when you run the login command so I can see the disk info? Sorry for the delay. In the meanwhile I tore down the server and re-configured it using ethernet bonding. It worked, according to iozone, provided moderately better throughput than the single connection I got before. Moderately. Measurably. Not significantly. If you have just a single iscsi connection/login from the initiator to the target, then you'll have only one tcp connection, and that means bonding won't help you at all - you'll be only able to utilize one link of the bond. bonding needs multiple tcp/ip connections for being able to give more bandwidth. I tore it down after that and reconfigured again using MPIO, and funny enough, this time it worked. I can access the lun now using two devices (sdb and sdd), and both ethernet devices that connect to iscsi show traffic. The weird thing is that aside from writing bonding was measurably faster than MPIO. Does that seem right? That seems a bit weird. How did you configure multipath? Please paste your multipath settings. -- Pasi Here's the dmesg, if that lends any clues. Thanks for any input! --Kyle 156 lines of dmesg follows cxgb3i: tag itt 0x1fff, 13 bits, age 0xf, 4 bits. iscsi: registered transport (cxgb3i) device-mapper: table: 253:6: multipath: error getting device device-mapper: ioctl: error adding target to table device-mapper: table: 253:6: multipath: error getting device device-mapper: ioctl: error adding target to table Broadcom NetXtreme II CNIC Driver cnic v2.0.0 (March 21, 2009) cnic: Added CNIC device: eth0 cnic: Added CNIC device: eth1 cnic: Added CNIC device: eth2 cnic: Added CNIC device: eth3 Broadcom NetXtreme II iSCSI Driver bnx2i v2.0.1e (June 22, 2009) iscsi: registered transport (bnx2i) scsi3 : Broadcom Offload iSCSI Initiator scsi4 : Broadcom Offload iSCSI Initiator scsi5 : Broadcom Offload iSCSI Initiator scsi6 : Broadcom Offload iSCSI Initiator iscsi: registered transport (tcp) iscsi: registered transport (iser) bnx2: eth0: using MSIX ADDRCONF(NETDEV_UP): eth0: link is not ready bnx2i: iSCSI not supported, dev=eth0 bnx2i: iSCSI not supported, dev=eth0 bnx2: eth0 NIC Copper Link is Up, 1000 Mbps full duplex, receive transmit flow control ON ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready bnx2: eth2: using MSIX ADDRCONF(NETDEV_UP): eth2: link is not ready bnx2i: iSCSI not supported, dev=eth2 bnx2i: iSCSI not supported, dev=eth2 bnx2: eth2 NIC Copper Link is Up, 1000 Mbps full duplex ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready bnx2: eth3: using MSIX ADDRCONF(NETDEV_UP): eth3: link is not ready bnx2i: iSCSI not supported, dev=eth3 bnx2i: iSCSI not supported, dev=eth3 bnx2: eth3 NIC Copper Link is Up, 1000 Mbps full duplex ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready eth0: no IPv6 routers present eth2: no IPv6 routers present scsi7 : iSCSI Initiator over TCP/IP scsi8 : iSCSI Initiator over TCP/IP scsi9 : iSCSI Initiator over TCP/IP scsi10 : iSCSI Initiator over TCP/IP Vendor: DGC Model: RAID 5Rev: 0429 Type: Direct-Access ANSI SCSI revision: 04 sdb : very big device. try to use READ CAPACITY(16). SCSI device sdb: 7693604864 512-byte hdwr sectors (3939126 MB) sdb: Write Protect is off sdb: Mode Sense: 7d 00 00 08 SCSI device sdb: drive cache: write through sdb : very big device. try to use READ CAPACITY(16). SCSI device sdb: 7693604864 512-byte hdwr sectors (3939126 MB) sdb: Write Protect is off sdb: Mode Sense: 7d 00 00 08 SCSI device sdb: drive cache: write through sdb:5 Vendor: DGC Model: RAID 5Rev: 0429 Type: Direct-Access ANSI SCSI revision: 04 Vendor: DGC Model: RAID 5Rev: 0429 Type: Direct-Access ANSI SCSI revision: 04 sdc : very big device. try to use READ CAPACITY(16). SCSI device sdc: 7693604864 512-byte hdwr sectors (3939126 MB) sdc: test WP failed, assume Write Enabled sdc: asking for cache data failed sdc: assuming drive cache: write through Vendor: DGC Model: RAID 5Rev: 0429 Type: Direct-Access ANSI SCSI revision: 04 sdc : very big device. try to use READ CAPACITY(16). SCSI device sdc: 7693604864 512-byte hdwr sectors (3939126 MB) sdc: test WP failed, assume Write Enabled sde : very big device. try to use READ CAPACITY(16). sdc: asking for cache data failed sdc: assuming drive cache: write through sdc:5SCSI device sde: 7693604864 512-byte hdwr sectors (3939126 MB) sd 8:0:0:0: Device not ready: 6: Current: sense key: Not Ready Add. Sense: Logical
Re: Need help with multipath and iscsi in CentOS 5.4
On Thu, Dec 31, 2009 at 8:23 AM, Pasi Kärkkäinen pa...@iki.fi wrote:
If you have just a single iscsi connection/login from the initiator to the
target, then you'll have only one tcp connection, and that means bonding
won't help you at all - you'll be only able to utilize one link of the
bond.
bonding needs multiple tcp/ip connections for being able to give more
bandwidth.
That's what I thought, but I figured it was one of the following three
possibilities:
MPIO was (mis)configured and using more overhead than bonding
OR the initiator was firing multiple concurrent requests (which you
say it doesn't, I'll believe you)
OR the san was under massively different load between the test runs
(not too likely, but possible. Only one other lun is in use).
That seems a bit weird.
That's what I thought, otherwise I would have just gone with it.
How did you configure multipath? Please paste your multipath settings.
-- Pasi
Here's the /etc/multipath.conf. Where there other config options that
you'd need to see?
devnode_blacklist {
devnode ^sda[0-9]*
devnode ^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*
devnode ^hd[a-z][[0-9]*]
devnode ^cciss!c[0-9]d[0-9]*[p[0-9]*]
}
devices {
device {
vendor EMC
product SYMMETRIX
path_grouping_policy multibus
getuid_callout /sbin/scsi_id -g -u -s /block/%n
path_selector round-robin 0
features 0
hardware_handler 0
failback immediate
}
device {
vendor DGC
product *
path_grouping_policy group_by_prio
getuid_callout /sbin/scsi_id -g -u -s /block/%n
prio_callout /sbin/mpath_prio_emc /dev/%n
hardware_handler 1 emc
features 1 queue_if_no_path
no_path_retry 300
path_checker emc_clariion
failback immediate
}
}
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To post to this group, send email to open-is...@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?hl=en.
Re: Need help with multipath and iscsi in CentOS 5.4
Note, the EMC specific bits of that multipath.conf were just copied from boxes that use FC to the SAN, and use MPIO successfully. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@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?hl=en.
Re: Need help with multipath and iscsi in CentOS 5.4
On Wed, Dec 9, 2009 at 8:52 PM, Mike Christie micha...@cs.wisc.edu wrote: So far single connections work: If I setup the box to use one NIC, I get one connection and can use it just fine. Could you send the /var/log/messages for when you run the login command so I can see the disk info? Sorry for the delay. In the meanwhile I tore down the server and re-configured it using ethernet bonding. It worked, according to iozone, provided moderately better throughput than the single connection I got before. Moderately. Measurably. Not significantly. I tore it down after that and reconfigured again using MPIO, and funny enough, this time it worked. I can access the lun now using two devices (sdb and sdd), and both ethernet devices that connect to iscsi show traffic. The weird thing is that aside from writing bonding was measurably faster than MPIO. Does that seem right? Here's the dmesg, if that lends any clues. Thanks for any input! --Kyle 156 lines of dmesg follows cxgb3i: tag itt 0x1fff, 13 bits, age 0xf, 4 bits. iscsi: registered transport (cxgb3i) device-mapper: table: 253:6: multipath: error getting device device-mapper: ioctl: error adding target to table device-mapper: table: 253:6: multipath: error getting device device-mapper: ioctl: error adding target to table Broadcom NetXtreme II CNIC Driver cnic v2.0.0 (March 21, 2009) cnic: Added CNIC device: eth0 cnic: Added CNIC device: eth1 cnic: Added CNIC device: eth2 cnic: Added CNIC device: eth3 Broadcom NetXtreme II iSCSI Driver bnx2i v2.0.1e (June 22, 2009) iscsi: registered transport (bnx2i) scsi3 : Broadcom Offload iSCSI Initiator scsi4 : Broadcom Offload iSCSI Initiator scsi5 : Broadcom Offload iSCSI Initiator scsi6 : Broadcom Offload iSCSI Initiator iscsi: registered transport (tcp) iscsi: registered transport (iser) bnx2: eth0: using MSIX ADDRCONF(NETDEV_UP): eth0: link is not ready bnx2i: iSCSI not supported, dev=eth0 bnx2i: iSCSI not supported, dev=eth0 bnx2: eth0 NIC Copper Link is Up, 1000 Mbps full duplex, receive transmit flow control ON ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready bnx2: eth2: using MSIX ADDRCONF(NETDEV_UP): eth2: link is not ready bnx2i: iSCSI not supported, dev=eth2 bnx2i: iSCSI not supported, dev=eth2 bnx2: eth2 NIC Copper Link is Up, 1000 Mbps full duplex ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready bnx2: eth3: using MSIX ADDRCONF(NETDEV_UP): eth3: link is not ready bnx2i: iSCSI not supported, dev=eth3 bnx2i: iSCSI not supported, dev=eth3 bnx2: eth3 NIC Copper Link is Up, 1000 Mbps full duplex ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready eth0: no IPv6 routers present eth2: no IPv6 routers present scsi7 : iSCSI Initiator over TCP/IP scsi8 : iSCSI Initiator over TCP/IP scsi9 : iSCSI Initiator over TCP/IP scsi10 : iSCSI Initiator over TCP/IP Vendor: DGC Model: RAID 5Rev: 0429 Type: Direct-Access ANSI SCSI revision: 04 sdb : very big device. try to use READ CAPACITY(16). SCSI device sdb: 7693604864 512-byte hdwr sectors (3939126 MB) sdb: Write Protect is off sdb: Mode Sense: 7d 00 00 08 SCSI device sdb: drive cache: write through sdb : very big device. try to use READ CAPACITY(16). SCSI device sdb: 7693604864 512-byte hdwr sectors (3939126 MB) sdb: Write Protect is off sdb: Mode Sense: 7d 00 00 08 SCSI device sdb: drive cache: write through sdb:5 Vendor: DGC Model: RAID 5Rev: 0429 Type: Direct-Access ANSI SCSI revision: 04 Vendor: DGC Model: RAID 5Rev: 0429 Type: Direct-Access ANSI SCSI revision: 04 sdc : very big device. try to use READ CAPACITY(16). SCSI device sdc: 7693604864 512-byte hdwr sectors (3939126 MB) sdc: test WP failed, assume Write Enabled sdc: asking for cache data failed sdc: assuming drive cache: write through Vendor: DGC Model: RAID 5Rev: 0429 Type: Direct-Access ANSI SCSI revision: 04 sdc : very big device. try to use READ CAPACITY(16). SCSI device sdc: 7693604864 512-byte hdwr sectors (3939126 MB) sdc: test WP failed, assume Write Enabled sde : very big device. try to use READ CAPACITY(16). sdc: asking for cache data failed sdc: assuming drive cache: write through sdc:5SCSI device sde: 7693604864 512-byte hdwr sectors (3939126 MB) sd 8:0:0:0: Device not ready: 6: Current: sense key: Not Ready Add. Sense: Logical unit not ready, manual intervention required end_request: I/O error, dev sdc, sector 0 Buffer I/O error on device sdc, logical block 0 sd 8:0:0:0: Device not ready: 6: Current: sense key: Not Ready Add. Sense: Logical unit not ready, manual intervention required end_request: I/O error, dev sdc, sector 0 ... that repeats a bunch of times Buffer I/O error on device sdc, logical block 0 unable to read partition table sdd : very big device. try to use READ CAPACITY(16). sd 8:0:0:0: Attached scsi disk sdc SCSI device sdd: 7693604864 512-byte hdwr sectors (3939126
RE: Need help with multipath and iscsi in CentOS 5.4
Hi Kyle. For your configuration do you have a LUN in the storage group assigned to your server? If so, the LUN is presented to both SPs (service processors) but only owned by one. If your storage group for the server has been configured for the default mode the LUN is presented in PNR mode; therefore, only one SP owns it and can be used for the IO. In order to use the LUN thru the other SP the LUN needs to be trespassed to that SP. If the storage group for the server is configured for ALUA mode then you can read and write thru both SPs without a trespass command. If there are no LUNs assigned in a storage group for your server, then the LUN that is presented to the server is a LUNZ and you will not be able to access it. You indicate below that you are able to fdisk one of the SCSI devices but not all four. If you are configured in the manner you described you should be able to access it thru the two NICs that attached to the SP that owns the LUN. Regards, Wayne. EMC Corp -Original Message- From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com] On Behalf Of Mike Christie Sent: Wednesday, December 09, 2009 9:52 PM To: open-iscsi@googlegroups.com Subject: Re: Need help with multipath and iscsi in CentOS 5.4 Kyle Schmitt wrote: I'm cross-posting here from linux-iscsi-users since I've seen no linux-scsi-users would be for centos 4. Centos 5 uses a different initiator, but you are the right place finally :) traffic in the weeks since I posted this. Hi, I needed a little help or advice with my setup. I'm trying to configure multipathed iscsi on a CentOS 5.4 (RHEL 5.4 clone) box. Very short version: One server with two NICs for iSCSI sees storage on EMC. Storage shows up as four discs, but only one works. So far single connections work: If I setup the box to use one NIC, I get one connection and can use it just fine. When I setup multiple connections I have problems... I created two interfaces, and assigned each one to a NIC iscsiadm -m iface -I iface0 --op=new iscsiadm -m iface -I iface0 --op=update -n iface.net_ifacename -v eth2 iscsiadm -m iface -I iface1 --op=new iscsiadm -m iface -I iface1 --op=update -n iface.net_ifacename -v eth3 Each interface saw two paths to their storage, four total, so far so good. I logged all four of them them in with: iscsiadm -m node -T long ugly string here -l I could see I was connected to all four via iscsiadm-m session At this point, I thought I was set, I had four new devices /dev/sdb /dev/sdc /dev/sdd /dev/sde Ignoring multipath at this point for now, here's where the problem started. I have all four devices, but I can only communicate through one of them: /dev/sdc. As a quick test I tried to fdisk all four partitions, to see if I saw the same thing in each place, and only /dev/sdc works. What do you mean by works? Can you dd it, or fdisk it? Turning on multipath, I got a multipathed device consisting of sdb sdc sdd and sde, but sdb sdd and sde are failed with a message of checker msg is emc_clariion_checker: Logical Unit is unbound or LUNZ Have you created a lun that is accessible to the initiator defined in /etc/iscsi/initiatorname.iscsi? Could you send the /var/log/messages for when you run the login command so I can see the disk info? -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@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?hl=en. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@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?hl=en.
Re: Need help with multipath and iscsi in CentOS 5.4
On Wed, Dec 9, 2009 at 8:52 PM, Mike Christie micha...@cs.wisc.edu wrote: Kyle Schmitt wrote: What do you mean by works? Can you dd it, or fdisk it? it works by most any measure sdc: I can dd it, fdisk it, mkfs.ext3 it, run iozone, etc. In contrast sdb sdd and sde cant be fdisked, dded, or even less -fed. Have you created a lun that is accessible to the initiator defined in /etc/iscsi/initiatorname.iscsi? Yup, I've got a lun, and can read/write to it. Could you send the /var/log/messages for when you run the login command so I can see the disk info? Sure, let me dig it out... it'll be a few minutes. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@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?hl=en.
Re: Need help with multipath and iscsi in CentOS 5.4
Kyle Schmitt wrote: I'm cross-posting here from linux-iscsi-users since I've seen no linux-scsi-users would be for centos 4. Centos 5 uses a different initiator, but you are the right place finally :) traffic in the weeks since I posted this. Hi, I needed a little help or advice with my setup. I'm trying to configure multipathed iscsi on a CentOS 5.4 (RHEL 5.4 clone) box. Very short version: One server with two NICs for iSCSI sees storage on EMC. Storage shows up as four discs, but only one works. So far single connections work: If I setup the box to use one NIC, I get one connection and can use it just fine. When I setup multiple connections I have problems... I created two interfaces, and assigned each one to a NIC iscsiadm -m iface -I iface0 --op=new iscsiadm -m iface -I iface0 --op=update -n iface.net_ifacename -v eth2 iscsiadm -m iface -I iface1 --op=new iscsiadm -m iface -I iface1 --op=update -n iface.net_ifacename -v eth3 Each interface saw two paths to their storage, four total, so far so good. I logged all four of them them in with: iscsiadm -m node -T long ugly string here -l I could see I was connected to all four via iscsiadm-m session At this point, I thought I was set, I had four new devices /dev/sdb /dev/sdc /dev/sdd /dev/sde Ignoring multipath at this point for now, here's where the problem started. I have all four devices, but I can only communicate through one of them: /dev/sdc. As a quick test I tried to fdisk all four partitions, to see if I saw the same thing in each place, and only /dev/sdc works. What do you mean by works? Can you dd it, or fdisk it? Turning on multipath, I got a multipathed device consisting of sdb sdc sdd and sde, but sdb sdd and sde are failed with a message of checker msg is emc_clariion_checker: Logical Unit is unbound or LUNZ Have you created a lun that is accessible to the initiator defined in /etc/iscsi/initiatorname.iscsi? Could you send the /var/log/messages for when you run the login command so I can see the disk info? -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@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?hl=en.
Need help with multipath and iscsi in CentOS 5.4
I'm cross-posting here from linux-iscsi-users since I've seen no traffic in the weeks since I posted this. Hi, I needed a little help or advice with my setup. I'm trying to configure multipathed iscsi on a CentOS 5.4 (RHEL 5.4 clone) box. Very short version: One server with two NICs for iSCSI sees storage on EMC. Storage shows up as four discs, but only one works. So far single connections work: If I setup the box to use one NIC, I get one connection and can use it just fine. When I setup multiple connections I have problems... I created two interfaces, and assigned each one to a NIC iscsiadm -m iface -I iface0 --op=new iscsiadm -m iface -I iface0 --op=update -n iface.net_ifacename -v eth2 iscsiadm -m iface -I iface1 --op=new iscsiadm -m iface -I iface1 --op=update -n iface.net_ifacename -v eth3 Each interface saw two paths to their storage, four total, so far so good. I logged all four of them them in with: iscsiadm -m node -T long ugly string here -l I could see I was connected to all four via iscsiadm-m session At this point, I thought I was set, I had four new devices /dev/sdb /dev/sdc /dev/sdd /dev/sde Ignoring multipath at this point for now, here's where the problem started. I have all four devices, but I can only communicate through one of them: /dev/sdc. As a quick test I tried to fdisk all four partitions, to see if I saw the same thing in each place, and only /dev/sdc works. Turning on multipath, I got a multipathed device consisting of sdb sdc sdd and sde, but sdb sdd and sde are failed with a message of checker msg is emc_clariion_checker: Logical Unit is unbound or LUNZ I'm in the dark here. Is this right? Obviously wrong? Thanks --Kyle -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@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?hl=en.
Re: Need help in compiling open-iscsi-2.0-870.2 for kernel 2.6.28
Mike Christie wrote: Jeronimo de A. Barros wrote: Hello, Any help or hint to compile open-iscsi-2.0-870.2 for kernel 2.6.28 ? I'm trying on a Bluewhite64 12.2 running kernel 2.6.28.2: r...@test:/usr/local/src/open-iscsi-2.0-870.2# uname -a Linux test 2.6.28.2 #1 SMP Sun Feb 1 09:32:16 BRST 2009 x86_64 Intel(R) Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux r...@test:/usr/local/src/open-iscsi-2.0-870.2# gcc -v Reading specs from /usr/lib/gcc/x86_64-pc-linux/4.2.4/specs Target: x86_64-pc-linux Configured with: ../gcc-4.2.4/configure --prefix=/usr --enable-shared --enable-languages=ada,c,c++,fortran,java,objc --disable-multilib --enable-threads=posix --enable-__cxa_atexit --disable-checking --with-gnu-ld --verbose --build=x86_64-pc-linux --target=x86_64-pc-linux --host=x86_64-pc-linux Thread model: posix gcc version 4.2.4 I have inserted the line linux_2_6_28: $(unpatch_code) but still getting errors: Yeah, that is not going to work, because the 2.6.28 kernel changed some kernel APIs. The kernel modules need to be updated for the new APIs. I have done this to the code in git: git clone git://git.kernel.org/pub/scm/linux/kernel/git/mnc/open-iscsi.git I am preparing to do a new release when I finish up integrating some patches from Fedora, converting code to use strlcat and strlcpy, and fix some bugs in the iface printing code. I was planning on having this done by 2.6.29 (so the new release will have 2.6.28 and .29 support). I know this does not help you much. But the upstream 2.6.28.2 kernel is up to date with 870.1 (.2 just has one fix that 2.6.28 does not for memory leak), so you could just use those kernel modules and then use the userspace tools from open-iscsi-2.0-870.2 and you would probably be fine. Hi mike, if we are already at the subject. Something I wanted for a while. It is expected for out-of-tree Kernel modules to constantly break at the development edge. What happens today is that I can't finish compiling and installing user-mode tools, if Kernel does not compile. I want to submit a patch that will not force Kernel module compilation by default, but only if say we do make kernel. Since for me 99% of the time I just want to update on the user-mode, and I'm using the Kernel modules that come from the Kernel I'm using. Is that OK? Boaz --~--~-~--~~~---~--~~ 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 in compiling open-iscsi-2.0-870.2 for kernel 2.6.28
Mike, 2009/2/1 Mike Christie micha...@cs.wisc.edu Yeah, that is not going to work, because the 2.6.28 kernel changed some kernel APIs. The kernel modules need to be updated for the new APIs. I have done this to the code in git: git clone git://git.kernel.org/pub/scm/linux/kernel/git/mnc/open-iscsi.git I am preparing to do a new release when I finish up integrating some patches from Fedora, converting code to use strlcat and strlcpy, and fix some bugs in the iface printing code. I was planning on having this done by 2.6.29 (so the new release will have 2.6.28 and .29 support). I know this does not help you much. Actually your info helps a lot. I'll try the git code in the enviroment test. Thank you !!! []s, Jero --~--~-~--~~~---~--~~ 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 in compiling open-iscsi-2.0-870.2 for kernel 2.6.28
Boaz Harrosh wrote: Hi mike, if we are already at the subject. Something I wanted for a while. It is expected for out-of-tree Kernel modules to constantly break at the development edge. What happens today is that I can't finish compiling and installing user-mode tools, if Kernel does not compile. I want to submit a patch that will not force Kernel module compilation by default, but only if say we do make kernel. Since for me 99% of the time I just want to update on the user-mode, and I'm using the Kernel modules that come from the Kernel I'm using. Is that OK? I added a make user make user install to git the other day because I hit the same problem. I did not make it the default, because I was thinking most users are using older kernels and if they are grabbing the tarballs on open-iscsi.prg want the updated kernel modules built. Is this ok? What about splitting up the kernel from the userspace parts in different tarballs/trees? --~--~-~--~~~---~--~~ 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 in compiling open-iscsi-2.0-870.2 for kernel 2.6.28
Jeronimo de A. Barros wrote: Hello, Any help or hint to compile open-iscsi-2.0-870.2 for kernel 2.6.28 ? I'm trying on a Bluewhite64 12.2 running kernel 2.6.28.2: r...@test:/usr/local/src/open-iscsi-2.0-870.2# uname -a Linux test 2.6.28.2 #1 SMP Sun Feb 1 09:32:16 BRST 2009 x86_64 Intel(R) Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux r...@test:/usr/local/src/open-iscsi-2.0-870.2# gcc -v Reading specs from /usr/lib/gcc/x86_64-pc-linux/4.2.4/specs Target: x86_64-pc-linux Configured with: ../gcc-4.2.4/configure --prefix=/usr --enable-shared --enable-languages=ada,c,c++,fortran,java,objc --disable-multilib --enable-threads=posix --enable-__cxa_atexit --disable-checking --with-gnu-ld --verbose --build=x86_64-pc-linux --target=x86_64-pc-linux --host=x86_64-pc-linux Thread model: posix gcc version 4.2.4 I have inserted the line linux_2_6_28: $(unpatch_code) but still getting errors: Yeah, that is not going to work, because the 2.6.28 kernel changed some kernel APIs. The kernel modules need to be updated for the new APIs. I have done this to the code in git: git clone git://git.kernel.org/pub/scm/linux/kernel/git/mnc/open-iscsi.git I am preparing to do a new release when I finish up integrating some patches from Fedora, converting code to use strlcat and strlcpy, and fix some bugs in the iface printing code. I was planning on having this done by 2.6.29 (so the new release will have 2.6.28 and .29 support). I know this does not help you much. But the upstream 2.6.28.2 kernel is up to date with 870.1 (.2 just has one fix that 2.6.28 does not for memory leak), so you could just use those kernel modules and then use the userspace tools from open-iscsi-2.0-870.2 and you would probably be fine. --~--~-~--~~~---~--~~ 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
On Wed, 2009-01-07 at 12:06 +0100, Ulrich Windl wrote: On 5 Jan 2009 at 14:02, prachi bodke wrote: Thnks...but plz help me out as soon as possible.. Did you read the iSCSI RFC? If you don't understand what's written there, you'll have some trouble when programming iSCSI. Maybe be concrete with your questions. http://www.ietf.org/rfc/rfc3720.txt http://en.wikipedia.org/wiki/ISCSI j Regards, Ulrich On Mon, Jan 5, 2009 at 2:00 PM, Yuri yuri.li...@gmail.com wrote: welcome new friend. On Mon, Jan 5, 2009 at 4:15 PM, Prachi Bodke prachibo...@gmail.comwrote: Hi all, I am new to this iSCSI.. I want to study the iSCSI interface with Linux. Can any1 help me out in this..?? From where to start?? using that interface, i want to develop one small application.. Please help me out..as soon as possible. Thanks in advance Regards, Prachi -- Thanks regards,|73 Yuri Huang -- Regards, Prachi S. Bodke --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Need help
Hi all, I am new to this iSCSI.. I want to study the iSCSI interface with Linux. Can any1 help me out in this..?? From where to start?? using that interface, i want to develop one small application.. Please help me out..as soon as possible. Thanks in advance Regards, Prachi --~--~-~--~~~---~--~~ 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
welcome new friend. On Mon, Jan 5, 2009 at 4:15 PM, Prachi Bodke prachibo...@gmail.com wrote: Hi all, I am new to this iSCSI.. I want to study the iSCSI interface with Linux. Can any1 help me out in this..?? From where to start?? using that interface, i want to develop one small application.. Please help me out..as soon as possible. Thanks in advance Regards, Prachi -- Thanks regards,|73 Yuri Huang --~--~-~--~~~---~--~~ 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
Thnks...but plz help me out as soon as possible.. On Mon, Jan 5, 2009 at 2:00 PM, Yuri yuri.li...@gmail.com wrote: welcome new friend. On Mon, Jan 5, 2009 at 4:15 PM, Prachi Bodke prachibo...@gmail.comwrote: Hi all, I am new to this iSCSI.. I want to study the iSCSI interface with Linux. Can any1 help me out in this..?? From where to start?? using that interface, i want to develop one small application.. Please help me out..as soon as possible. Thanks in advance Regards, Prachi -- Thanks regards,|73 Yuri Huang -- Regards, Prachi S. Bodke --~--~-~--~~~---~--~~ 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
On Mon, Jan 5, 2009 at 2:02 PM, prachi bodke prachibo...@gmail.com wrote: Thnks...but plz help me out as soon as possible.. On Mon, Jan 5, 2009 at 2:00 PM, Yuri yuri.li...@gmail.com wrote: welcome new friend. On Mon, Jan 5, 2009 at 4:15 PM, Prachi Bodke prachibo...@gmail.comwrote: Hi all, I am new to this iSCSI.. I want to study the iSCSI interface with Linux. Can any1 help me out in this..?? From where to start?? using that interface, i want to develop one small application.. Please help me out..as soon as possible. Thanks in advance Regards, Prachi -- Thanks regards,|73 Yuri Huang -- Regards, Prachi S. Bodke Hi, you can check this two links. http://www.howtoforge.com/iscsi_on_linux http://en.wikipedia.org/wiki/ISCSI Thanks and regards, Vaibhav Pol National PARAM Supercomputing Facility Centre for Development of Advanced Computing Ganeshkhind Road Pune University Campus PUNE-Maharastra Phone +91-20-25704176 ext: 176 Cell Phone : +919850466409 --~--~-~--~~~---~--~~ 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
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). --~--~-~--~~~---~--~~ 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 kon...@virtualiron.comwrote: 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 -~--~~~~--~~--~--~---
