Re: iSCSI Conformance Test Tool: iSCT
On 01/04/10 03:46, lancests wrote: We are currently developing iSCT, a tool which does iSCSI conformance test for the target. It's written in Python and can be driven by user- defined test scripts. Using iSCT, it is easy to identify target protocol conformance problems in user space during Open-iSCSI development. iSCT can be found on our website www.storagetest.com. We are proud if iSCT can be of any help to Open-iSCSI. Hello Lance, Are you aware that an open-source iSCSI conformance test tool already exists ? See also Ronnie Sahlberg, SCSI testing/USB devices are amazing, linux-scsi mailing list, April 2013 (http://thread.gmane.org/gmane.linux.scsi/81622/). Bart. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: iscsistart VLAN ID ??
Thanks but vconfig doesn't apply here this is an iscsi hba so it's not using the network stack at all ... besides that it's too early in the boot process still running on initramfs ... On Monday, September 15, 2014 8:14:01 AM UTC, Cip wrote: How about using vconfig to create a VLAN interface? Tagging then becomes a kernel problem and thus no longer relevant to iscsi. On 09/11/2014 05:43 PM, Rob Roschewsk wrote: Hi all ... I've searched but have found no answers maybe my google-juice is low ... I need to be able to pass a VLAN ID and enable VLAN TAGGING in iscsistart I'm using an EMULEX 10G NETWORK / ISCSI HBA and our iscsi traffic is on a specific vlan Emulex Corporation OneConnect 10Gb NIC (be3) (rev 01) I am able to connect to the device from the command line using iscsiadm but during the boot process I want to mount the iscsi lun as root. I see nothing in the scripts / configs / man pages about VLAN support FYI ... trying to do this on Ubunti Server 14.04.1 Thanks ... -- Rob -- 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.com javascript:. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
Re: SHA-1 hashing Algorithm for CHAP
I have never seen a spec for CHAP with any other hash algorithms. No spec, so no implementations. paul On Sep 11, 2014, at 6:22 AM, Tejas vaykole tejas.vaykol...@gmail.com wrote: Hello, I am trying out with the open-iscsi initiator.I see that the initiator uses MD5 algorithm for CHAP. I need help in configuring the initiator to use SHA-1 hashing Algorithm for CHAP. Thanks. Tejas -- 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. For more options, visit https://groups.google.com/d/optout.
iscsistart Ubuntu server 14.01.1 LTS / HP proliant DL380p GEN 8
OK ... so I've made a lot of progress since my last post about VLAN id discovered I should be using ISCSI_AUTO and ibft However ... I'm still getting grief from the init script local-top/iscsi, iscsistart -b is *failing* with the message: *Could not get boot entry.* I have hacked at the iscsi script and pared it down to the bare essentials: echo loading ibft module modprobe iscsi_ibft echo load ibft module echo sleep 5 sleep 5 echo wake up echo running iscsistart /sbin/iscsistart -b echo ended iscsistart echo running udevadm settle udevadm settle echo ended udevadm settle echo ended iscsi script no joy but here is the kicker when the initscript fails to find root and drops me to the initramfs shell I run iscsistart -b at the command line it all works fine! configures the hba and connects to the lun on both interfaces .. exit out of the shell ... root gets mounted and all is well. The box is using emulex lan/iscsi adapters: 03:00.2 Mass storage controller: Emulex Corporation OneConnect 10Gb iSCSI Initiator (be3) (rev 01) 03:00.3 Mass storage controller: Emulex Corporation OneConnect 10Gb iSCSI Initiator (be3) (rev 01) I'm stumped ... is it a timing thing??? Any and all help appreciated !!! Thanks! -- Rob -- 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. For more options, visit https://groups.google.com/d/optout.
Re: iscsistart Ubuntu server 14.01.1 LTS / HP proliant DL380p GEN 8
OK I might be onto something even though ibft_iscsi loads ... it seems the /sys/ entries the iscsistart needs aren't ready after modprobe returns . adding a sleep 60 allowed iscsistart to connect to the luns without dropping to a shell On Monday, September 15, 2014 3:06:40 PM UTC, Rob Roschewsk wrote: OK ... so I've made a lot of progress since my last post about VLAN id discovered I should be using ISCSI_AUTO and ibft However ... I'm still getting grief from the init script local-top/iscsi, iscsistart -b is *failing* with the message: *Could not get boot entry.* I have hacked at the iscsi script and pared it down to the bare essentials: echo loading ibft module modprobe iscsi_ibft echo load ibft module echo sleep 5 sleep 5 echo wake up echo running iscsistart /sbin/iscsistart -b echo ended iscsistart echo running udevadm settle udevadm settle echo ended udevadm settle echo ended iscsi script no joy but here is the kicker when the initscript fails to find root and drops me to the initramfs shell I run iscsistart -b at the command line it all works fine! configures the hba and connects to the lun on both interfaces .. exit out of the shell ... root gets mounted and all is well. The box is using emulex lan/iscsi adapters: 03:00.2 Mass storage controller: Emulex Corporation OneConnect 10Gb iSCSI Initiator (be3) (rev 01) 03:00.3 Mass storage controller: Emulex Corporation OneConnect 10Gb iSCSI Initiator (be3) (rev 01) I'm stumped ... is it a timing thing??? Any and all help appreciated !!! Thanks! -- Rob -- 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. For more options, visit https://groups.google.com/d/optout.
Re: iscsistart VLAN ID ??
On 09/11/2014 10:43 AM, Rob Roschewsk wrote: Hi all ... I've searched but have found no answers maybe my google-juice is low ... I need to be able to pass a VLAN ID and enable VLAN TAGGING in iscsistart I'm using an EMULEX 10G NETWORK / ISCSI HBA and our iscsi traffic is on a specific vlan Emulex Corporation OneConnect 10Gb NIC (be3) (rev 01) Are you using the Emulex iscsi offload driver (be2iscsi) or using software iscsi (iscsi_tcp) over the Emulex network driver (be2net)? -- 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. For more options, visit https://groups.google.com/d/optout.
Re: iscsistart VLAN ID ??
be2iscsi but I've made more progress since this post ... see: https://groups.google.com/d/msg/open-iscsi/JZVK8BBImg0/QS08QsAwX_wJ The configuration of the VLAN still seems to be automagic but it's working On Monday, September 15, 2014 5:23:25 PM UTC, Mike Christie wrote: On 09/11/2014 10:43 AM, Rob Roschewsk wrote: Hi all ... I've searched but have found no answers maybe my google-juice is low ... I need to be able to pass a VLAN ID and enable VLAN TAGGING in iscsistart I'm using an EMULEX 10G NETWORK / ISCSI HBA and our iscsi traffic is on a specific vlan Emulex Corporation OneConnect 10Gb NIC (be3) (rev 01) Are you using the Emulex iscsi offload driver (be2iscsi) or using software iscsi (iscsi_tcp) over the Emulex network driver (be2net)? -- 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. For more options, visit https://groups.google.com/d/optout.
Re: iscsistart VLAN ID ??
If you are using be2iscsi, then you would not use ibft. If you are using a custom boot script then you need be2iscsi and iscsi_boot_sysfs only. If you are using a distro boot script then it might be more general and loading ibft (loading ibft loads iscsi_boot_sysfs) because other drivers need it. I think for be2iscsi boot, there is no code to get the vlan id and then pass that down to the driver. However, I think be2iscsi might store the vlan info in firmware like it does with the other net info. So as long as the vlan id did not change then you are ok. Jay, is that correct? On 09/15/2014 12:34 PM, Rob Roschewsk wrote: be2iscsi but I've made more progress since this post ... see: https://groups.google.com/d/msg/open-iscsi/JZVK8BBImg0/QS08QsAwX_wJ The configuration of the VLAN still seems to be automagic but it's working On Monday, September 15, 2014 5:23:25 PM UTC, Mike Christie wrote: On 09/11/2014 10:43 AM, Rob Roschewsk wrote: Hi all ... I've searched but have found no answers maybe my google-juice is low ... I need to be able to pass a VLAN ID and enable VLAN TAGGING in iscsistart I'm using an EMULEX 10G NETWORK / ISCSI HBA and our iscsi traffic is on a specific vlan Emulex Corporation OneConnect 10Gb NIC (be3) (rev 01) Are you using the Emulex iscsi offload driver (be2iscsi) or using software iscsi (iscsi_tcp) over the Emulex network driver (be2net)? -- 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 mailto:open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com mailto:open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
Re: SHA-1 hashing Algorithm for CHAP
On Sep 15, 2014, at 1:19 PM, Mike Christie micha...@cs.wisc.edu wrote: On 09/11/2014 05:22 AM, Tejas vaykole wrote: Hello, I am trying out with the open-iscsi initiator.I see that the initiator uses MD5 algorithm for CHAP. I need help in configuring the initiator to use SHA-1 hashing Algorithm for CHAP. We only support MD5. The API use is hard coded, so there is no simple config step. You would have to write the code. What target are you using? I don't think it matters; there is no CHAP other than MD5 CHAP in the iSCSI standard. See RFC 7143, page 228. So there are *no* conforming implementations of CHAP for any other hash. paul -- 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. For more options, visit https://groups.google.com/d/optout.
