On Fri, Oct 17, 2008 at 04:53:11AM -0500, Mark Chaney wrote:
> 
> Id really appreciate it if someone could help me out with the above issue.
> Its driving me crazy and I have been spending hours trying to resolve the
> issue. Cant seem to find anything in the documentation that actually works
> to resolve it.
> 
> Thanks,
> Mark
> 
> -----Original Message-----
> From: open-iscsi@googlegroups.com [mailto:[EMAIL PROTECTED] On
> Behalf Of Mark Chaney
> Sent: Thursday, October 16, 2008 4:17 PM
> To: open-iscsi@googlegroups.com
> Subject: 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

I've had the same issue. The issue was that the OS routing would thwart my 
attempt
and connect to the other target over the ifaces.

> 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). 

The IPv6 is from the MD3000i. You need to go to iSCSI Port settings and
uncheck the IPv6 button.

> 
> 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.6001e4f0003b58f8000000004833b5b4
> 10.0.0.1:3260,1
> iqn.1984-05.com.dell:powervault.6001e4f0003b58f8000000004833b5b4
> 10.0.1.1:3260,1
> iqn.1984-05.com.dell:powervault.6001e4f0003b58f8000000004833b5b4
> 10.0.1.1:3260,1
> iqn.1984-05.com.dell:powervault.6001e4f0003b58f8000000004833b5b4
> [fe80:0000:0000:0000:021e:4fff:fe3b:58fa]:3260,1
> iqn.1984-05.com.dell:powervault.6001e4f0003b58f8000000004833b5b4
> [fe80:0000:0000:0000:021e:4fff:fe3b:58fa]:3260,1
> iqn.1984-05.com.dell:powervault.6001e4f0003b58f8000000004833b5b4
> [fe80:0000:0000:0000:021e:4fff:fe3b:58fc]:3260,1
> iqn.1984-05.com.dell:powervault.6001e4f0003b58f8000000004833b5b4
> [fe80:0000:0000:0000:021e:4fff:fe3b:58fc]:3260,1
> iqn.1984-05.com.dell:powervault.6001e4f0003b58f8000000004833b5b4
> 
> ###########################################################
> 
> 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?

The IPV6 is easy. Turn it off in your storage.

For the one portal per one iface  do this

route add -host 10.0.1.1 dev <iface0>
route add -host 10.0.0.1 dev <iface1>

And so on. You can also make each of the target portals have its unique IP.
So instead of two 10.0.1.1 you can do 10.0.1.1 and 10.0.1.2 and be
more selective with the network routing.

> 
> Looking for final results of two ifaces, 1 portal each, 1 active session
> each.

For that wouldn't you need four NICs? Since you have four IPv4 portals?
> 
> 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to