ifaces and assigning portals
I have a dell md3000i with only a single controller in it, but it has two iscsi ports. Each one of my servers has two iscsi nics as well. I setup two ifaces per server and have iface0 and iface1 setup to each use their own switch. Each switch is connected to an individual iscsi port on the md3000i controller. Each network is on its own subnet. I am trying for the life of me to connect a single iface to a single portal, but I keep getting errors that no records are found. When I try to do any type of discovery methods, it keeps adding both interfaces to both ifaces, also seems to throw in ipv6 even though Im not using it on my network and don't want to (how can disable ipv6). When I run iscsiadm -m discovery -t sendtargets -p 10.0.0.1, I get the following: [EMAIL PROTECTED] iscsi]# iscsiadm -m discovery -t sendtargets -p 10.0.0.1 10.0.0.1:3260,1 iqn.1984-05.com.dell:powervault.6001e4f0003b58f84833b5b4 10.0.0.1:3260,1 iqn.1984-05.com.dell:powervault.6001e4f0003b58f84833b5b4 10.0.1.1:3260,1 iqn.1984-05.com.dell:powervault.6001e4f0003b58f84833b5b4 10.0.1.1:3260,1 iqn.1984-05.com.dell:powervault.6001e4f0003b58f84833b5b4 [fe80::::021e:4fff:fe3b:58fa]:3260,1 iqn.1984-05.com.dell:powervault.6001e4f0003b58f84833b5b4 [fe80::::021e:4fff:fe3b:58fa]:3260,1 iqn.1984-05.com.dell:powervault.6001e4f0003b58f84833b5b4 [fe80::::021e:4fff:fe3b:58fc]:3260,1 iqn.1984-05.com.dell:powervault.6001e4f0003b58f84833b5b4 [fe80::::021e:4fff:fe3b:58fc]:3260,1 iqn.1984-05.com.dell:powervault.6001e4f0003b58f84833b5b4 ### Even though I should only be getting 1 portal for each iface and definitely no ipv6. What should I be doing to accomplish the task of assigning only one portal to one iface and no ipv6 results showing in discoveries? Looking for final results of two ifaces, 1 portal each, 1 active session each. Thanks, Mark --~--~-~--~~~---~--~~ 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: ipv6 and discovery
On Thursday 16 October 2008 21:58:06 Mark Chaney wrote: > Yep, already have that. CentOS is definitely setup not to use ipv6. No diff > =/ This may help: echo > /etc/modprobe.d/ipv6 blacklist ipv6 echo >> /etc/modprobe.d/ipv6 install ipv6 /bin/true &:-) > > -Original Message- > From: open-iscsi@googlegroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of George Liu > Sent: Thursday, October 16, 2008 2:45 PM > To: open-iscsi@googlegroups.com > Subject: Re: ipv6 and discovery > > > Add the line below in /etc/sysconfig/network file. > NETWORKING_IPV6=no > > --George > > Mark Chaney wrote: > > How do I disable ipv6 from showing up in discoveries? I am not using ipv6 > > on > > > my network and do not want any ipv6 results showing up. Its just giving > > me clutter in my records. > > > > Thanks, > > Mark > > --~--~-~--~~~---~--~~ 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: ipv6 and discovery
Eh, if figured it out. I had to disable it on each interface as well. /etc/syconfig/network-scripts/ifcfg-eth*, then added IPV6INIT=no. Sad I had to add it there when I had the module disabled. Eh, its working right now though, so Im happy. =) -Original Message- From: open-iscsi@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Mark Chaney Sent: Thursday, October 16, 2008 2:58 PM To: open-iscsi@googlegroups.com Subject: RE: ipv6 and discovery Yep, already have that. CentOS is definitely setup not to use ipv6. No diff =/ -Original Message- From: open-iscsi@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of George Liu Sent: Thursday, October 16, 2008 2:45 PM To: open-iscsi@googlegroups.com Subject: Re: ipv6 and discovery Add the line below in /etc/sysconfig/network file. NETWORKING_IPV6=no --George Mark Chaney wrote: > How do I disable ipv6 from showing up in discoveries? I am not using ipv6 on > my network and do not want any ipv6 results showing up. Its just giving me > clutter in my records. > > Thanks, > Mark > > > > > > > --~--~-~--~~~---~--~~ 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: ipv6 and discovery
Yep, already have that. CentOS is definitely setup not to use ipv6. No diff =/ -Original Message- From: open-iscsi@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of George Liu Sent: Thursday, October 16, 2008 2:45 PM To: open-iscsi@googlegroups.com Subject: Re: ipv6 and discovery Add the line below in /etc/sysconfig/network file. NETWORKING_IPV6=no --George Mark Chaney wrote: > How do I disable ipv6 from showing up in discoveries? I am not using ipv6 on > my network and do not want any ipv6 results showing up. Its just giving me > clutter in my records. > > Thanks, > Mark > > > > > > > --~--~-~--~~~---~--~~ 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: ipv6 and discovery
Add the line below in /etc/sysconfig/network file. NETWORKING_IPV6=no --George Mark Chaney wrote: > How do I disable ipv6 from showing up in discoveries? I am not using ipv6 on > my network and do not want any ipv6 results showing up. Its just giving me > clutter in my records. > > Thanks, > Mark > > > > > > > --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
ipv6 and discovery
How do I disable ipv6 from showing up in discoveries? I am not using ipv6 on my network and do not want any ipv6 results showing up. Its just giving me clutter in my records. Thanks, Mark --~--~-~--~~~---~--~~ 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: Issues connecting to LUN on MD3000i
On Thu, 2008-10-16 at 11:49 -0700, Ray Van Dolson wrote: > On Thu, Oct 16, 2008 at 11:40:44AM -0700, Chandra Seetharaman wrote: > > > > > > On Thu, 2008-10-16 at 11:28 -0700, Ray Van Dolson wrote: > > > Thanks to both of you guys. Established a network access to the other > > > controller and all is well. > > > > Are you now using the multipath as suggested by Hasse ? > > Not yet -- but we'll aim to get that configured (gotta read up on Oh ok. > multipath first). For the time being I'm able to connect to the LUN at > least however. When you use multipath, if you have any problems (not that you will have any :), feel free to post questions to the dm-devel mailing list. > > > which version of kernel are you using ? 2.6.27 has scsi hardware handler > > which gets rid of boot/probe time slowness and the error messages (for > > rdac). > > > > This is the stock (latest) RHEL5 kernel (CentOS actually). I doubt > this fix has been backported yet. :-) I see. > > Ray > > > --~--~-~--~~~---~--~~ 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: Issues connecting to LUN on MD3000i
On Thu, Oct 16, 2008 at 11:40:44AM -0700, Chandra Seetharaman wrote: > > > On Thu, 2008-10-16 at 11:28 -0700, Ray Van Dolson wrote: > > Thanks to both of you guys. Established a network access to the other > > controller and all is well. > > Are you now using the multipath as suggested by Hasse ? Not yet -- but we'll aim to get that configured (gotta read up on multipath first). For the time being I'm able to connect to the LUN at least however. > which version of kernel are you using ? 2.6.27 has scsi hardware handler > which gets rid of boot/probe time slowness and the error messages (for > rdac). > This is the stock (latest) RHEL5 kernel (CentOS actually). I doubt this fix has been backported yet. :-) Ray --~--~-~--~~~---~--~~ 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: Issues connecting to LUN on MD3000i
On Thu, 2008-10-16 at 11:28 -0700, Ray Van Dolson wrote: > Thanks to both of you guys. Established a network access to the other > controller and all is well. Are you now using the multipath as suggested by Hasse ? which version of kernel are you using ? 2.6.27 has scsi hardware handler which gets rid of boot/probe time slowness and the error messages (for rdac). > > Ray > > > --~--~-~--~~~---~--~~ 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: Issues connecting to LUN on MD3000i
Thanks to both of you guys. Established a network access to the other controller and all is well. Ray --~--~-~--~~~---~--~~ 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: Limiting the number of ISCSI-Sessions per target
Dr. Volker Jaenisch wrote: > Hi open-iscsi-List! > > I have a HA XEN-setup based on ISCSI devices [tgtd (target) and > open-iscsi (initiator)] > as physical devices for the XEN DomUs. > > In case of a split-Brain in the HA-System more than one machine may > fetch a iSCSI-Session > and may try to bring up a XEN-VM on it. This will seriously damage the > filesystem. > > Therefore I like to prevent iSCSI to make more than one simultanous > session per target. > > Is there a way to limit the number of ISCSI-Sessions per Target-ID. > I found the MaxConnection-Parameter but it limits only the number of > connections within a single iSCSI-Session. > Is there something alike - say a MaxSession-Parameter? > I am not sure if this is what you are looking for but you can control which sessions get made. Do you have multiple portals per target and so we can create a session through each portal to the same target? Something like this: # iscsiadm -m node 20.15.0.12:3260,1 iqn.2001-04.com.home:meanminna 20.15.0.100:3260,1 iqn.2001-04.com.home:meanminna And right now we create two sessions (one through each portal on the target)? If so you can run iscsiadm -m node -T target -p ip:port,tpgt -o update -n node.startup -v manual so that one of the portals does not get a session. Note that the "node" in the node.startup name does not mean the node as in the target and will not disable all sessions to the target. It only affects the record you are passing to iscsiadm so it only affects the session through that specific portal on that target. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Limiting the number of ISCSI-Sessions per target
Hi open-iscsi-List! I have a HA XEN-setup based on ISCSI devices [tgtd (target) and open-iscsi (initiator)] as physical devices for the XEN DomUs. In case of a split-Brain in the HA-System more than one machine may fetch a iSCSI-Session and may try to bring up a XEN-VM on it. This will seriously damage the filesystem. Therefore I like to prevent iSCSI to make more than one simultanous session per target. Is there a way to limit the number of ISCSI-Sessions per Target-ID. I found the MaxConnection-Parameter but it limits only the number of connections within a single iSCSI-Session. Is there something alike - say a MaxSession-Parameter? Thanks in advance. Best Regards, Volker -- inqbus it-consulting +49 ( 341 ) 5643800 Dr. Volker Jaenisch http://www.inqbus.de Herloßsohnstr.12 0 4 1 5 5Leipzig N O T - F Ä L L E +49 ( 170 ) 3113748 --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
