IPv4/IPv6 initiator-target--automatic mapping of targets
Hello All, I have a case where both initiator and target are configured with IPv4 and IPv6 address. The target listens ob both sockets. When i login to the target without mentioning the portal , it logins and creates two sessions for the same target. Questions 1.How to force the initiator to login with a specific IP version ? It is configured for automatic login and both systems have to retain dual ip address version. 2.The session id always get incremented after each new login. Can this be changed to reset /start from least available after for each new session ? 3. How to persistently map iscsi target to fixed sd id ? for third Question, I came across couple of threads in forum and IET for similar issue. I am trying to configure the ScsiId in the ietd.conf and create the udev rule on the initiator. But no success. == Ietd.conf== Target iqn.2008-03.storageserver:storage.target1 Lun 1 Path=/dev/VolGroup00/target1,Type=blockio,ScsiId=1234567 Initiator Udev rule and ScsiId === [EMAIL PROTECTED] rules.d]$ sudo scsi_id -g -s /block/sdc 1494554003736353433323100 [EMAIL PROTECTED] rules.d]$ cat 20-names.rules KERNEL="sd*", BUS="scsi", PROGRAM="/sbin/scsi_id", RESULT="1234567", NAME="sdb%n" [EMAIL PROTECTED] rules.d]$ sudo iscsiadm --version iscsiadm version 2.0-865 === Once, I am successful with a single system,it has to be replicated on other systems. Is there feature in consideration on future initiator software releases to extract this info and provide a option to automate this event ? thanks in advance for your time and suggestions Regards Padmanabhan --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: IPv4/IPv6 initiator-target--automatic mapping of targets
Thanks for your replies. simple setup. Systems are Fedora Core 8 (kernel-2.6.23.15) with open- iscsi as initiator and IET as target.Both have single NIC card with IPv4/IPv6 address configuration. -- Yes the portal are discovered via send targets and configured for automatic logins. The problem here is, it opens two sessions to the same target via both IPv4/IPv6 portals. I am yet to look into iface readme file. --Yes, I need the volume exported by the target to be mapped to same sd say sdb. I looked in forums and tried to configure the udev rules and configure ietd.conf with ScsiId param. For example, my ietd.conf Target iqn.2008-03.storageserver:storage.target1 Lun 1 Path=/dev/VolGroup00/ target1,Type=blockio,ScsiId=1234567890123456 The value shown up at the initiator [EMAIL PROTECTED] rules.d]$ sudo scsi_id -g -s /block/sdc 1 49 45 54 00 00 00 00 00 31 32 33 34 35 36 37 38 39 30 31 32 33 34 35 36 It seems, id is shown up as ASCII values in Hex. to reflect this I changed again the udev rule, but not successful. I am not sure whether this is a good solution( since I need to create udev rule in each system for consistently mapping as a local drive) and if it is, I believe I do not have correct configurations. -- Konrad, Can I get some explanation on multipath suggestion. I am newbie to this field. How it will work for single NIC card configured with two versions of IP address ? Any links on this topic would be great. Regards Padmanabhan --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: IPv4/IPv6 initiator-target--automatic mapping of targets
Hello Mike,
Here again, let me try to explain the problem
Initiator Target
10.1.1.210.1.1.1
2001::2 2001::1
node.startup=automatic
When the system reboots, the initiator login twice (TWO TCP
connections) with target on both IPv4/IPv6 addresses
where only one is required. Is there a way to limit this session at
iSCSI level, preferably on initiator?
Output of fdisk -l on initiator, the same target volume is listed as
/dev/sdc
/dev/sdd
Yes, under /dev/disk the exported volume is updated in by-id,by-uuid..
directories.
Th by-id is same("scsi-" is prepended) as the ScsiId param which I
configure in ietd.conf
/dev/disk/by-id/
scsi-149455400313323334353637383930313233343536
I configured udev rule as per Redhat kbase
http://kbase.redhat.com/faq/FAQ_85_8082.shtm
KERNEL="sd*", BUS="scsi", PROGRAM="/sbin/scsi_id",
RESULT="149455400313323334353637383930313233343536",
NAME="sdb%n"
So the two issues,
--initiator should login only once ( i can set to either IPv4/IPv6)
--the exported volume should be listed as /dev/sdb on the initiator
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---
Re: IPv4/IPv6 initiator-target--automatic mapping of targets
Hello Mike, Let me explain the sequence of events -- The system reboots -- Open iscsi is enabled at start up Issue 1 ==>> From the database, the initiator logins twice to the same target via TWO TCP connections which are established on IPv4 and IPv6 sockets. Yes, if i disable automatic node startup, then it is fine, I can login to the target via specific portal by using iscsiadm comamands. But problem is when it configured for automatic login. As said earlier, I am looking for a solution at iSCSI layer. ==>> for the second issue, I searched further but still need your help . Yes, I find an entry under /dev/disk/by-id as say " scsi-149455400123456" ? Here is where I am not able to get you how to make it consistent. 1. mount /dev/disk/by-id/scsi-XXX /mnt/iscsi 2. output of mount /dev/sdd on /mnt/iscsi type ext3 (rw) 3. Created fstab entry /dev/sdd /mnt/iscsi auto _netdev 0 0 4. Reboot fstab retains the entry, but the mount output does not have it. When it logged in this time, it has different sd. I am not using udev rules. Once again, thanks for your time and suggestions. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: IPv4/IPv6 initiator-target--automatic mapping of targets
Hello > So if you do > iscsiadm -m node -T target -p ip:port -o update -n node.startup -v manual > > for just one portal, then restart the system that portal will not get auto > logged into. The other portal on that taget will still get auto logged > into. Does that make sense? Yes,, it made sense... now upon reboot only one iscsi session established over the preferred portal. > When you write the fstab entry use the /dev/disk/by-id/scsi-XXX value. Do > not use the /dev/sdX ones. I edited the fstab entry with /dev/disk/by-id/scsi- value. It is NOT mounted ti iscsi directory. /dev/disk/by-id/scsi-XXX /mnt/iscsi auto _netdev 0 0 Is there additional configuration that I am missing out ? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: IPv4/IPv6 initiator-target--automatic mapping of targets
> What distro are you using? I am using FC 8 // 2.6 kernel --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
upgrade from 2.0.865 to 2.0.869
Hello, I have already installed 2.0.865 and want to install the latest release 2.0.869. Which files should I remove from the previous installation ? Thanks in advance for your help --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: upgrade from 2.0.865 to 2.0.869
Thanks Mike --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
iSCSI performance guidelines
Hello All, I was looking for general guidelines to enhance software iSCSI performance by optimizing different parameters at these layers of network stack on a host. iSCSI FirstBurstLength MaxBurstLength MaxRecvDataSegmentLength InitialR2T -- No ImmediateData -- Yes TCP layer Receive/send Buffer size Disabling Nagle algorithm (on Targets) NIC card TCP segmentation offload Rx/Tx checksum offload Jumbo frames NAPI Questions 1. Does above mentioned iSCSI parameters are declared individually by initiator/target OR target influences these values ? 2. Is TCP tuning required in SAN networks which are Gigabit switched network? If yes, should target be tuned differently from initators as it may handle multiple connections? 3. what other parameters have to be considered when implementing software based initiators and targets ? Thanks for sharing your expertise and time Regards Padmanabhan --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: iSCSI performance guidelines
Thanks ... any recommendations or pointers on TCP window sizes ? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: iSCSI performance guidelines
Do iSCSI request initial TCP socket buffer size or is it left to TCP to determine size ? I did captures using wireshark, it shows always initiator/target opens TCP connection with a window size 56xx/58xx bytes.( small setup, initiator/target PCs with Gig NIC cards connected via Gig ethernet switch) Is there any guidelines on TCP socket buffer sizes for iSCSI ? thanks --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: dynamic behaviour of device name
Hello Vaibhav, I started a thread for similar issue http://groups.google.com/group/open-iscsi/browse_thread/thread/5e417afbddb5e271/6034c90dd5a4965b?lnk=gst&q=by-uuid+#6034c90dd5a4965b But i did not follow due to other issues...My distro is Fedora Core 8 with 2.6.23-15.137fc8 kernel If you come across solution.. please share the info Thanks Padmanabhan --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
General question about iSCSI/compression techniques
Hello All, This topic may not be related to open-iscsi initiator but i not able find any resources about header compression techniques for iSCSI or TCP/IP over ethernet links. Any suggestions or pointers to docs/resources would be great. Thanks & Regards Padmanabhan --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
