RE: iscsiadm login fails when hostname is specified instead of IP address

2008-10-21 Thread Mark Chaney

Maybe im missing something, but where does it say that hostnames are
supported?

-Original Message-
From: open-iscsi@googlegroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Ashutosh Naik
Sent: Tuesday, October 21, 2008 12:44 PM
To: open-iscsi@googlegroups.com
Cc: Mike Christie
Subject: iscsiadm login fails when hostname is specified instead of IP
address


Hi,

I am logging to the iSCSI Enterprise target and observe the following
behaviour. I am using open-iscsi version 2.0-869.2

The discovery session seems to resolve the hostname to an IP address well.

[EMAIL PROTECTED] ~]# iscsiadm --mode discovery --type sendtargets --portal
sw01
10.192.166.103:3260,1 iqn.2004-05.com.faker.sw01

But while logging in, this resolution fails

[EMAIL PROTECTED] ~]# iscsiadm -m node --portal sw01 --login
iscsiadm: no records found!

It works fine after I use the IP address instead of the hostname

[EMAIL PROTECTED] ~]# iscsiadm -m node --portal 10.192.166.103 --login
Logging in to [iface: default, target: iqn.2004-05.com.faker.sw01,
portal: 10.192.166.103,3260]
Login to [iface: default, target: iqn.2004-05.com.faker.sw01, portal:
10.192.166.103,3260]: successful

It's easily reproducible

Thanks
Ashutosh



--~--~-~--~~~---~--~~
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: ifaces and assigning portals

2008-10-17 Thread Mark Chaney

Mike,

Thanks, that helped a lot. I ended up find a cli command to disable ipv6 on
my targets as well. Im still getting some errors when I start the iscsi
service though. Here are my results:

#

[EMAIL PROTECTED] iscsi]# iscsiadm -m node
10.0.1.1:3260,1
iqn.1984-05.com.dell:powervault.6001e4f0003b58f84833b5b4
10.0.0.1:3260,1
iqn.1984-05.com.dell:powervault.6001e4f0003b58f84833b5b4
[EMAIL PROTECTED] iscsi]# nano /etc/iscsi/iscsid.conf
[EMAIL PROTECTED] iscsi]# iscsiadm -m discovery -t sendtargets -p 10.0.1.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
[EMAIL PROTECTED] iscsi]# iscsiadm -m node -I iface0 -p 10.0.1.1:3260,1 -o
delete
[EMAIL PROTECTED] iscsi]# iscsiadm -m node -I iface1 -p 10.0.0.1:3260,1 -o
delete
[EMAIL PROTECTED] iscsi]# service iscsi stop
Logging out of session [sid: 3, target:
iqn.1984-05.com.dell:powervault.6001e4f0003b58f84833b5b4, portal:
10.0.1.1,3260]
Logging out of session [sid: 4, target:
iqn.1984-05.com.dell:powervault.6001e4f0003b58f84833b5b4, portal:
10.0.0.1,3260]
Logout of [sid: 3, target:
iqn.1984-05.com.dell:powervault.6001e4f0003b58f84833b5b4, portal:
10.0.1.1,3260]: successful
iscsiadm: got read error (0/2), daemon died?
iscsiadm: Could not logout of [sid: 4, target:
iqn.1984-05.com.dell:powervault.6001e4f0003b58f84833b5b4, portal:
10.0.0.1,3260]:
iscsiadm: initiator reported error (18 - could not communicate to iscsid)
Stopping iSCSI daemon: /etc/init.d/iscsi: line 33: 22495 Killed
/etc/init.d/iscsid stop
[EMAIL PROTECTED] iscsi]# service iscsi start  [  OK  ]
iscsid dead but pid file exists
Turning off network shutdown. Starting iSCSI daemon:   [  OK  ]
   [  OK  ]
Setting up iSCSI targets: Logging in to [iface: iface1, target:
iqn.1984-05.com.dell:powervault.6001e4f0003b58f84833b5b4, portal:
10.0.1.1,3260]
Logging in to [iface: iface0, target:
iqn.1984-05.com.dell:powervault.6001e4f0003b58f84833b5b4, portal:
10.0.0.1,3260]
Login to [iface: iface1, target:
iqn.1984-05.com.dell:powervault.6001e4f0003b58f84833b5b4, portal:
10.0.1.1,3260]: successful
iscsiadm: Could not login to [iface: iface0, target:
iqn.1984-05.com.dell:powervault.6001e4f0003b58f84833b5b4, portal:
10.0.0.1,3260]:
iscsiadm: initiator reported error (15 - already exists)
iscsiadm: Could not log into all portals. Err 15.
   [  OK  ]
[EMAIL PROTECTED] iscsi]#

#

I don't see any reason why it would be trying to logging in twice. 

Thanks,
Mark

-Original Message-
From: open-iscsi@googlegroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Mike Christie
Sent: Friday, October 17, 2008 12:12 PM
To: open-iscsi@googlegroups.com
Subject: Re: ifaces and assigning portals


Mark Chaney wrote:
> 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:

RE: ifaces and assigning portals

2008-10-17 Thread Mark Chaney

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
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
-~--~~~~--~~--~--~---



ifaces and assigning portals

2008-10-16 Thread Mark Chaney

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

2008-10-16 Thread Mark Chaney

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

2008-10-16 Thread Mark Chaney

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
-~--~~~~--~~--~--~---



ipv6 and discovery

2008-10-16 Thread Mark Chaney

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
-~--~~~~--~~--~--~---