Re: b2iscsi and LeftHand P4500
On 10/11/2011 08:24 PM, Colin Coe wrote: >> >> Do you actually have a LUN with that value 4194304? >> >> Maybe the LeftHand target needs some blacklist entry in the scsi mid >> layer to scan for devices properly. >> > > No, this LUN was the first one created. I don't know where the > 4194304 came from. > Could you take a wireshark/tcpdump trace and send it to me? -- 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: b2iscsi and LeftHand P4500
On Wed, Oct 12, 2011 at 5:05 AM, Mike Christie wrote: > On 09/22/2011 12:02 AM, coec wrote: >> Hi all >> >> I'm using RHEL 6.1 (fully patched, 2.6.32-131.12.1.el6.x86_64 with >> iscsi-initiator-utils-6.2.0.872-21.el6.x86_64) on HP BL460c G7 blades >> talking to a P4500 14.4TB Virt SAN (two clustered P4500 boxes). >> >> As the blade has two FlexHBA (iSCSI) interfaces I want to do >> multipathing. Is the following valid? (Spefically, should both ifaces >> have the same iqn?) >> --- >> iscsiadm -m iface >> default tcp >> iser iser >> be2iscsi.00:17:a4:77:10:01 be2iscsi, >> 00:17:a4:77:10:01,,,iqn.2011-08.scada.benvir2p >> be2iscsi.00:17:a4:77:10:00 be2iscsi, >> 00:17:a4:77:10:00,,,iqn.2011-08.scada.benvir2p >> --- >> >> In this setup, I can only login to the LUN on iface be2iscsi. >> 00:17:a4:77:10:01. When I attempt to login with the other iface I get >> 'iscsiadm: No records found'. > > It sounds like you did not bind that iface. Does: > > iscsiadm -m node -P 1 > > show records for both ifaces? > > > You should have done something like > > iscsiadm -m discovery -t st -p ip -I be2iscsi.00:17:a4:77:10:01 -I > be2iscsi.00:17:a4:77:10:00 > > or > iscsiadm -m discovery -t st -p ip -I be2iscsi.00:17:a4:77:10:01 > iscsiadm -m discovery -t st -p ip -I be2iscsi.00:17:a4:77:10:00 -o new > > > >> >> I have other servers where I'm only using a single FlexHBA (be2iscsi) >> and they are having their own troubles. For example, dmesg is >> reporting lots of: >> --- >> scsi: host 0 channel 0 id 0 lun4194304 has a LUN larger than allowed > > > Do you actually have a LUN with that value 4194304? > > Maybe the LeftHand target needs some blacklist entry in the scsi mid > layer to scan for devices properly. > No, this LUN was the first one created. I don't know where the 4194304 came from. CC -- RHCE#805007969328369 -- 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: b2iscsi and LeftHand P4500
On 09/22/2011 12:02 AM, coec wrote: > Hi all > > I'm using RHEL 6.1 (fully patched, 2.6.32-131.12.1.el6.x86_64 with > iscsi-initiator-utils-6.2.0.872-21.el6.x86_64) on HP BL460c G7 blades > talking to a P4500 14.4TB Virt SAN (two clustered P4500 boxes). > > As the blade has two FlexHBA (iSCSI) interfaces I want to do > multipathing. Is the following valid? (Spefically, should both ifaces > have the same iqn?) > --- > iscsiadm -m iface > default tcp > iser iser > be2iscsi.00:17:a4:77:10:01 be2iscsi, > 00:17:a4:77:10:01,,,iqn.2011-08.scada.benvir2p > be2iscsi.00:17:a4:77:10:00 be2iscsi, > 00:17:a4:77:10:00,,,iqn.2011-08.scada.benvir2p > --- > > In this setup, I can only login to the LUN on iface be2iscsi. > 00:17:a4:77:10:01. When I attempt to login with the other iface I get > 'iscsiadm: No records found'. It sounds like you did not bind that iface. Does: iscsiadm -m node -P 1 show records for both ifaces? You should have done something like iscsiadm -m discovery -t st -p ip -I be2iscsi.00:17:a4:77:10:01 -I be2iscsi.00:17:a4:77:10:00 or iscsiadm -m discovery -t st -p ip -I be2iscsi.00:17:a4:77:10:01 iscsiadm -m discovery -t st -p ip -I be2iscsi.00:17:a4:77:10:00 -o new > > I have other servers where I'm only using a single FlexHBA (be2iscsi) > and they are having their own troubles. For example, dmesg is > reporting lots of: > --- > scsi: host 0 channel 0 id 0 lun4194304 has a LUN larger than allowed Do you actually have a LUN with that value 4194304? Maybe the LeftHand target needs some blacklist entry in the scsi mid layer to scan for devices properly. -- 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: TODO list- userspace2.
Hi Mike/all,
I am working on a part of user space 1 of TODO list, which precisely says-
the functions that were run (FUNCTION)
the iSCSI packets that were sent/receieved (PDUS)
print out extended iscsi login error information (LOGIN_ERRS)
i) I have written log_debug to retrieve all functions names and print PDUS
sent/recieved.
but in case of FUNCTION for retrieving description I got two ways-
(Please suggest which one is better approach)
(all pls note that description always has to be in format just above
function definition starts-
/**
* function name - function description
)
1st approach-
For getting description I will call a function,
func_descrip(descrip, __FILE__ , __FUNCTION__, __LINE__);
by this function I will fopen the file and then search for the
desired function name whos one line back i will find /*,
so that I will be sure this is the description of the desired function :) .
2nd approach is-
I can create a global structure which will carry the function and
its description, I mean something like:-
struct func_name_descip{
char func_name[20];
char func_descrip[256];
};
and while executing discovery a function which will parse all .c files
under "usr" directory and fill up this structure,
while calling log_debug for FUNCTION, I will retrieve all values from the
global object of this structure.
disadvantage of 1st approach is- "its very time consuming task for
iscsiadm"
every time log_debug() is encountered then whole file is parsed for
retrieving description which has been already parsed for other functions.
Whereas disadv of 2nd one is - creating a global variable, also triggering
it during discovery might slow up discovery too (but we can
trigger it only when user specifies -d FUNCTION).
I think second one is better. Please let me know anyone has a better idea,
also share your views on these two.
ii) Regarding LOGIN_ERRS,
after reading __check_iscsi_status_class(), I thought maybe it should come
in debug with iscsid, I mean
iscsid -f -d LOGIN_ERR
and NOT iscsiadm -m node -T iqn.iet.target -p 102.2.2.2 -d LOGIN_ERR
In TODO, do you also mean't to say same as above I have written.
well I can try to do it for any/both :) , let me know which one is
desired/better.
Thanks,
Rahul.
On Mon, Aug 8, 2011 at 9:49 PM, Mike Christie wrote:
> On 08/03/2011 12:24 PM, rahul gupta wrote:
> > For integers, like timeout:-
> > while fetching from sysfs_get_str(), I am setting timeouts to -1 for
> > indicating error and also in qla card's case where chap is not supported
> in
> > /sys,
> > and then while printing, checking same value by taking its complement.
> >
> > I found in iscsid.conf file setting timeout value to -1 to huge -ve value
> is
> > valid (as after setting that can restart iscsid successfully) but not
> really
> > sure does user uses it.
> > I assume user never uses -1 for timeout in iscsid.conf file, so I have
> used
> > it in following code for error purpose:-
> >
> > Signed-off-by: Rahul Gupta
> >
> > iSCSI user space TODO item-2 : Displaying timeout and CHAP.
> >
> > Date: Wed Aug 3 22:35:30 2011 IST.
> >
>
> Thank you for your work on this. Merged in commit
> 42a5950919038cac331c7fa69304478bd62bec15. It should show up on
> kernel.org in a couple hours.
>
--
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: [PATCH] Do not run configure for open-isns on every build
On 10/11/2011 05:05 AM, Mike Christie wrote: On 10/07/2011 09:09 AM, Hannes Reinecke wrote: We only need to run configure in open-isns if either the configure script or Makefile.in has changed. Otherwise it's perfectly okay just to call a plain 'make' here. Signed-off-by: Hannes Reinecke diff --git a/Makefile b/Makefile index 8dd64c7..de7ef65 100644 --- a/Makefile +++ b/Makefile @@ -29,8 +29,8 @@ OPTFLAGS ?= -O2 -g all: user -user: ; - cd utils/open-isns; ./configure CFLAGS="$(OPTFLAGS)" --with-security=no; $(MAKE) I did not have the optflags patch so we just had: -user: ; - cd utils/open-isns; ./configure --with-security=no; $(MAKE) Let me know if you have sent a optflags patch and I have missed it. Thanks. Ah, no. OPTFLAGS is for our build system (which insists on passing in it's own set of flags). I'll be pushing out a patch here. Cheers, Hannes -- Dr. Hannes Reinecke zSeries & Storage h...@suse.de +49 911 74053 688 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg) -- 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: b2iscsi and LeftHand P4500
oh and IIRC the P4000 series (former LeftHand Networks boxes) have 'odd' behaviour with multipathing On 11 October 2011 08:36, Seth Tunstall wrote: > Hi, > > I'm running a similar configuration (HP/Serverengines UNAs) and ran > into similar problems. The only configuration I could get to work even > sometimes was using mainline kernel 3.0.0 and compiled iscsi userland, > whatever the latest version was ~3 months ago. > > HP have told me that you're not supposed to be able to connect a > HP/Serverengines NIC to an iscsi target unless you have: > > - A FlexFabric Switch > - The appropriate FlexFabric license > > Which sounds to me like filthy lies, since iSCSI is just plain tcp. > There could be some autodetection faff that the NICs do, but I doubt > it. > > I ended up using the tcp transport, as the performance impact for what > i'm running didn't seem to be too noticeable (Xen VMs, NFS roots) > > Seth > > On 22 September 2011 06:02, coec wrote: >> Hi all >> >> I'm using RHEL 6.1 (fully patched, 2.6.32-131.12.1.el6.x86_64 with >> iscsi-initiator-utils-6.2.0.872-21.el6.x86_64) on HP BL460c G7 blades >> talking to a P4500 14.4TB Virt SAN (two clustered P4500 boxes). >> >> As the blade has two FlexHBA (iSCSI) interfaces I want to do >> multipathing. Is the following valid? (Spefically, should both ifaces >> have the same iqn?) >> --- >> iscsiadm -m iface >> default tcp >> iser iser >> be2iscsi.00:17:a4:77:10:01 be2iscsi, >> 00:17:a4:77:10:01,,,iqn.2011-08.scada.benvir2p >> be2iscsi.00:17:a4:77:10:00 be2iscsi, >> 00:17:a4:77:10:00,,,iqn.2011-08.scada.benvir2p >> --- >> >> In this setup, I can only login to the LUN on iface be2iscsi. >> 00:17:a4:77:10:01. When I attempt to login with the other iface I get >> 'iscsiadm: No records found'. >> >> I have other servers where I'm only using a single FlexHBA (be2iscsi) >> and they are having their own troubles. For example, dmesg is >> reporting lots of: >> --- >> scsi: host 0 channel 0 id 0 lun4194304 has a LUN larger than allowed >> by the host adapter >> device-mapper: table: 253:7: multipath: error getting device >> device-mapper: ioctl: error adding target to table >> device-mapper: table: 253:7: multipath: error getting device >> device-mapper: ioctl: error adding target to table >> scsi: host 0 channel 0 id 0 lun4194304 has a LUN larger than allowed >> by the host adapter >> device-mapper: table: 253:7: multipath: error getting device >> device-mapper: ioctl: error adding target to table >> device-mapper: table: 253:7: multipath: error getting device >> device-mapper: ioctl: error adding target to table >> --- >> >> cat /proc/scsi/scsi >> Attached devices: >> Host: scsi0 Channel: 00 Id: 00 Lun: 00 >> Vendor: HP Model: P410i Rev: 3.66 >> Type: RAID ANSI SCSI revision: 05 >> Host: scsi0 Channel: 00 Id: 00 Lun: 01 >> Vendor: HP Model: LOGICAL VOLUME Rev: 3.66 >> Type: Direct-Access ANSI SCSI revision: 05 >> Host: scsi1 Channel: 00 Id: 00 Lun: 00 >> Vendor: LEFTHAND Model: iSCSIDisk Rev: 9000 >> Type: Direct-Access ANSI SCSI revision: 05 >> >> cat /proc/partitions >> major minor #blocks name >> >> 8 0 586029016 sda >> 8 1 512000 sda1 >> 8 2 585515008 sda2 >> 253 0 2097152 dm-0 >> 253 1 50331648 dm-1 >> 253 2 4194304 dm-2 >> 253 3 4194304 dm-3 >> 253 4 4194304 dm-4 >> 253 5 4194304 dm-5 >> 8 16 1073741824 sdb >> 253 6 1073741824 dm-6 >> >> This is all standard data iSCSI, I'm not attempting to do iSCSI >> booting at all. >> >> I've been trying to make this work for a while now and I'm wondering >> if I should just use software iSCSI? >> >> Thanks >> >> CC >> >> -- >> 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. >> >> > -- 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: b2iscsi and LeftHand P4500
Hi, I'm running a similar configuration (HP/Serverengines UNAs) and ran into similar problems. The only configuration I could get to work even sometimes was using mainline kernel 3.0.0 and compiled iscsi userland, whatever the latest version was ~3 months ago. HP have told me that you're not supposed to be able to connect a HP/Serverengines NIC to an iscsi target unless you have: - A FlexFabric Switch - The appropriate FlexFabric license Which sounds to me like filthy lies, since iSCSI is just plain tcp. There could be some autodetection faff that the NICs do, but I doubt it. I ended up using the tcp transport, as the performance impact for what i'm running didn't seem to be too noticeable (Xen VMs, NFS roots) Seth On 22 September 2011 06:02, coec wrote: > Hi all > > I'm using RHEL 6.1 (fully patched, 2.6.32-131.12.1.el6.x86_64 with > iscsi-initiator-utils-6.2.0.872-21.el6.x86_64) on HP BL460c G7 blades > talking to a P4500 14.4TB Virt SAN (two clustered P4500 boxes). > > As the blade has two FlexHBA (iSCSI) interfaces I want to do > multipathing. Is the following valid? (Spefically, should both ifaces > have the same iqn?) > --- > iscsiadm -m iface > default tcp > iser iser > be2iscsi.00:17:a4:77:10:01 be2iscsi, > 00:17:a4:77:10:01,,,iqn.2011-08.scada.benvir2p > be2iscsi.00:17:a4:77:10:00 be2iscsi, > 00:17:a4:77:10:00,,,iqn.2011-08.scada.benvir2p > --- > > In this setup, I can only login to the LUN on iface be2iscsi. > 00:17:a4:77:10:01. When I attempt to login with the other iface I get > 'iscsiadm: No records found'. > > I have other servers where I'm only using a single FlexHBA (be2iscsi) > and they are having their own troubles. For example, dmesg is > reporting lots of: > --- > scsi: host 0 channel 0 id 0 lun4194304 has a LUN larger than allowed > by the host adapter > device-mapper: table: 253:7: multipath: error getting device > device-mapper: ioctl: error adding target to table > device-mapper: table: 253:7: multipath: error getting device > device-mapper: ioctl: error adding target to table > scsi: host 0 channel 0 id 0 lun4194304 has a LUN larger than allowed > by the host adapter > device-mapper: table: 253:7: multipath: error getting device > device-mapper: ioctl: error adding target to table > device-mapper: table: 253:7: multipath: error getting device > device-mapper: ioctl: error adding target to table > --- > > cat /proc/scsi/scsi > Attached devices: > Host: scsi0 Channel: 00 Id: 00 Lun: 00 > Vendor: HP Model: P410i Rev: 3.66 > Type: RAID ANSI SCSI revision: 05 > Host: scsi0 Channel: 00 Id: 00 Lun: 01 > Vendor: HP Model: LOGICAL VOLUME Rev: 3.66 > Type: Direct-Access ANSI SCSI revision: 05 > Host: scsi1 Channel: 00 Id: 00 Lun: 00 > Vendor: LEFTHAND Model: iSCSIDisk Rev: 9000 > Type: Direct-Access ANSI SCSI revision: 05 > > cat /proc/partitions > major minor #blocks name > > 8 0 586029016 sda > 8 1 512000 sda1 > 8 2 585515008 sda2 > 253 0 2097152 dm-0 > 253 1 50331648 dm-1 > 253 2 4194304 dm-2 > 253 3 4194304 dm-3 > 253 4 4194304 dm-4 > 253 5 4194304 dm-5 > 8 16 1073741824 sdb > 253 6 1073741824 dm-6 > > This is all standard data iSCSI, I'm not attempting to do iSCSI > booting at all. > > I've been trying to make this work for a while now and I'm wondering > if I should just use software iSCSI? > > Thanks > > CC > > -- > 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. > > -- 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.
