Re: iscsi login failure ubuntu 12.04

2014-02-13 Thread Mike Christie 
On 02/13/2014 12:53 PM, Anil Rana wrote:
 Hi Mike,
 
 Sorry about that. Actually I didn't connect second port cable but I just
 configured second port in the target that is why it comes up.  I will
 take care of it.
 But I have been playing around since morning. So As I said, I have
 array1 (10.10.10.1) and array2 (120.10.30.1). I can login on both
 successfully but first one was 10.10.10.1 which created dm-0 under /dev
 and a link in /dev/mapper with a long number. For the second array, I
 don't see anything like that. Do you think I can use default interface
 for both arrays? 
 

Yes. You can use the normal old default interface as long as you are not
trying to use multiple nics on the same subnet on the initiator box.

Also, here is a helpful command

iscsiadm -m session -P 3

That will show you the targets you are connected to and their devices.
It is possible for that second array we did not find a device. You can
also run

multipath -ll

and see the multipath devices and their paths. If iscsiadm -m session
shows you have a scsi disk for array2 but multipath does not show a
multipath device then make sure multipathd is running or run
/sbin/multipath to force creation. And you can run

multipath -v 3

which would print debugging info.


-- 
You received this message because you are subscribed to the Google Groups 
open-iscsi group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to open-iscsi+unsubscr...@googlegroups.com.
To post to this group, send email to open-iscsi@googlegroups.com.
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/groups/opt_out.

iscsi login failure ubuntu 12.04

2014-02-03 Thread ianil . irana 
Hi,

I have been trying for many days without luck. I am trying to access HP 
P2000 storage array. I did all the steps but just can't login. 
dmeg shows :

18080.926620] scsi1 : iSCSI Initiator over TCP/IP
[18081.190192] scsi 1:0:0:0: Enclosure HP   P2000 G3 iSCSI   
T250 PQ: 0 ANSI: 5
[18081.190536] scsi 1:0:0:0: Attached scsi generic sg2 type 13
[18081.209346] ses 1:0:0:0: Attached Enclosure device
[18223.951214] device-mapper: table: 252:0: multipath: error getting device
[18223.951224] device-mapper: ioctl: error adding target to table
[18223.952283] device-mapper: table: 252:0: multipath: error getting device
[18223.952290] device-mapper: ioctl: error adding target to table
[21286.562300] scsi2 : iSCSI Initiator over TCP/IP
[21286.823437] scsi 2:0:0:0: Enclosure HP   P2000 G3 iSCSI   
T250 PQ: 0 ANSI: 5
[21286.823538] ses 2:0:0:0: Attached Enclosure device
[21286.823692] ses 2:0:0:0: Attached scsi generic sg2 type 13
[33223.758638] type=1400 audit(1391045501.020:68): apparmor=DENIED 
operation=capable parent=1 profile=/usr/sbin/cupsd pid=1259 
comm=cupsd pid=1259 comm=cupsd capability=36  capname=block_suspend
[33419.599217] scsi3 : iSCSI Initiator over TCP/IP
[33419.861038] scsi 3:0:0:0: Enclosure HP   P2000 G3 iSCSI   
T250 PQ: 0 ANSI: 5
[33419.861140] ses 3:0:0:0: Attached Enclosure device
[33419.861360] ses 3:0:0:0: Attached scsi generic sg2 type 13
[35008.448431] Loading iSCSI transport class v2.0-870.
[35008.456760] iscsi: registered transport (tcp)
[35008.467082] iscsi: registered transport (iser)
[96727.828370] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
[96728.822652] IPv6: ADDRCONF(NETDEV_UP): eth5: link is not ready
[115366.435214] type=1400 audit(1391127820.590:69): apparmor=DENIED 
operation=capable parent=1 profile=/usr/sbin/cupsd pid=1259 
comm=cupsd pid=1259 comm=cupsd capability=36  capname=block_suspend
[118718.41] type=1400 audit(1391131180.374:70): apparmor=DENIED 
operation=capable parent=1 profile=/usr/sbin/cupsd pid=1259 
comm=cupsd pid=1259 comm=cupsd capability=36  capname=block_suspend
[119539.879930] type=1400 audit(1391132003.022:71): apparmor=DENIED 
operation=capable parent=19032 profile=/usr/sbin/tcpdump pid=19805 
comm=tcpdump pid=19805 comm=tcpdump capability=12  capname=net_admin
[119540.006854] type=1400 audit(1391132003.150:72): apparmor=DENIED 
operation=capable parent=19032 profile=/usr/sbin/tcpdump pid=19805 
comm=tcpdump pid=19805 comm=tcpdump capability=12  capname=net_admin
[119557.616364] type=1400 audit(1391132020.794:73): apparmor=DENIED 
operation=capable parent=1 profile=/usr/sbin/cupsd pid=1259 
comm=cupsd pid=1259 comm=cupsd capability=36  capname=block_suspend
[119566.872120] device eth4 entered promiscuous mode
[119781.598825] device eth4 left promiscuous mode



root@Blade15:~# iscsid -f -d 7 
iscsid: sysfs_init: sysfs_path='/sys'

iscsid: sysfs_attr_get_value: open '/module/scsi_transport_iscsi'/'version'

iscsid: sysfs_attr_get_value: new uncached attribute 
'/sys/module/scsi_transport_iscsi/version'

iscsid: sysfs_attr_get_value: add to cache 
'/sys/module/scsi_transport_iscsi/version'

iscsid: sysfs_attr_get_value: cache 
'/sys/module/scsi_transport_iscsi/version' with attribute value '2.0-870'

iscsid: transport class version 2.0-870. iscsid version 2.0-871
iscsid: Can not bind IPC socket


root@Blade15:~# iscsid -f -d 8
iscsid: sysfs_init: sysfs_path='/sys'

iscsid: sysfs_attr_get_value: open '/module/scsi_transport_iscsi'/'version'

iscsid: sysfs_attr_get_value: new uncached attribute 
'/sys/module/scsi_transport_iscsi/version'

iscsid: sysfs_attr_get_value: add to cache 
'/sys/module/scsi_transport_iscsi/version'

iscsid: sysfs_attr_get_value: cache 
'/sys/module/scsi_transport_iscsi/version' with attribute value '2.0-870'

iscsid: transport class version 2.0-870. iscsid version 2.0-871
iscsid: Can not bind IPC socket
iscsid: in ctldev_close



root@Blade15:~# iscsiadm -m node -T 
iqn.1986-03.com.hp:storage.p2000g3.13351a9162 -p 10.10.30.1:3260 --login
Logging in to [iface: iface2, target: 
iqn.1986-03.com.hp:storage.p2000g3.13351a9162, portal: 10.10.30.1,3260]
Logging in to [iface: iface4, target: 
iqn.1986-03.com.hp:storage.p2000g3.13351a9162, portal: 10.10.30.1,3260]
iscsiadm: Could not login to [iface: iface2, target: 
iqn.1986-03.com.hp:storage.p2000g3.13351a9162, portal: 10.10.30.1,3260]: 
iscsiadm: initiator reported error (5 - encountered iSCSI login failure)
iscsiadm: Could not login to [iface: iface4, target: 
iqn.1986-03.com.hp:storage.p2000g3.13351a9162, portal: 10.10.30.1,3260]: 
iscsiadm: initiator reported error (5 - encountered iSCSI login failure)



Could you please help me? I wanted to put storage online long time ago but 
iscsi always gives me problem so kept on giving up. I really need to figure 
this out.

Thanks,

Anil

-- 
You received this message because you are subscribed to the Google Groups 
open-iscsi group.
To unsubscribe from this group and stop receiving emails

Re: iscsi login failure ubuntu 12.04

2014-02-03 Thread Michael Christie 

On Jan 30, 2014, at 7:40 PM, ianil.ir...@gmail.com wrote:
 root@Blade15:~# iscsid -f -d 8
 iscsid: sysfs_init: sysfs_path='/sys'
 
 iscsid: sysfs_attr_get_value: open '/module/scsi_transport_iscsi'/'version'
 
 iscsid: sysfs_attr_get_value: new uncached attribute 
 '/sys/module/scsi_transport_iscsi/version'
 
 iscsid: sysfs_attr_get_value: add to cache 
 '/sys/module/scsi_transport_iscsi/version'
 
 iscsid: sysfs_attr_get_value: cache 
 '/sys/module/scsi_transport_iscsi/version' with attribute value '2.0-870'
 
 iscsid: transport class version 2.0-870. iscsid version 2.0-871
 iscsid: Can not bind IPC socket
 iscsid: in ctldev_close


You should kill all the iscsid instances then run that command. The above 
message means iscsid did not start.
Without iscsid nothing will work. It could be it was already started.


 
 
 
 root@Blade15:~# iscsiadm -m node -T 
 iqn.1986-03.com.hp:storage.p2000g3.13351a9162 -p 10.10.30.1:3260 --login
 Logging in to [iface: iface2, target: 
 iqn.1986-03.com.hp:storage.p2000g3.13351a9162, portal: 10.10.30.1,3260]
 Logging in to [iface: iface4, target: 
 iqn.1986-03.com.hp:storage.p2000g3.13351a9162, portal: 10.10.30.1,3260]
 iscsiadm: Could not login to [iface: iface2, target: 
 iqn.1986-03.com.hp:storage.p2000g3.13351a9162, portal: 10.10.30.1,3260]: 
 iscsiadm: initiator reported error (5 - encountered iSCSI login failure)
 iscsiadm: Could not login to [iface: iface4, target: 
 iqn.1986-03.com.hp:storage.p2000g3.13351a9162, portal: 10.10.30.1,3260]: 
 iscsiadm: initiator reported error (5 - encountered iSCSI login failure)
 


When you run that command send the /var/log/messages and also the iscsid output.

Also run iscsiadm with -d 8.

And does it work with just the defaults iface? Does it just not work when 
trying to setup your own faces?

-- 
You received this message because you are subscribed to the Google Groups 
open-iscsi group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to open-iscsi+unsubscr...@googlegroups.com.
To post to this group, send email to open-iscsi@googlegroups.com.
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/groups/opt_out.

Re: iscsi login failure ubuntu 12.04

2014-02-03 Thread parveen kumar 
Hello Anil Rana https://plus.google.com/u/0/112685628807227708129?prsrc=4
,

Try this,


Configuring iSCSI initiator

SCSI uses a client-server architecture. A client (ie: your system) is an
initiator, it initiates requests. A server (ie: your storage device) is a
target, it has something you want and answers requests from the
initiator(s). Initiators come in two varieties: software and hardware. A
software initiator is just a driver that handles all requests and pairs the
network interfaces driver and the SCSI drivers together to make it all
work. Using a software initiator any system with an ethernet card can act
as an iSCSI initiator. A hardware initiator is an iSCSI HBA, which is
basically just an ethernet card with a SCSI ASIC on-board to offload all
the work from the system CPU.

First, install the iscsi-initiator-utils package using:

# yum install iscsi-initiator-utils

Next, start the iscsid service and enable it to start when the system boots:

# service iscsid start
# chkconfig iscsid on

Then obtain a listing of available targets from a given host (please note
that ipaddress listed below must be replaced with the resolvable hostname
or ip address of the system providing the port if different than default):

# iscsiadm -m discovery -t sendtargets -p ipaddress
xxx.xxx.xxx.xxx:3260,1 iqn.2010-03.com.example:tgtd

Here the iqn.2010-03.com.example:tgtd is the target_iqn_name.

You can view the information of your target by:

# iscsiadm -m node -T -p ipaddress

Finally, use the following command to login to the available target (again,
replace target_iqn_name with one from the output of the previous command
and replace ipaddress below with that of the target system):

# iscsiadm -m node -T target_iqn_name -p ipaddress -l
Logging in to [iface: default, target: iqn.2010-03.com.example:tgtd,
portal: xxx.xxx.xxx.xxx,3260]
Login to [iface: default, target: iqn.2010-03.com.example:tgtd, portal:
xxx.xxx.xxx.xxx,3260]: successful

Note, you can log into all the LUNs exported on the target by running:

# iscsiadm -m discovery -t st -l

This will enable the target(or targets if you logged into all) to be
accessed upon reboots and it stores it in a node database found in
/var/lib/iscsi that is more thoroughly described in the
/usr/share/doc/iscsi-initiator-utils-VERSION/README file.

If you want to disable the target, you need log out by:

# iscsiadm -m node -T target_iqn_name -p ipaddress -u

Note, you can log out of all targets by running:

# iscsiadm -m node -U all

For a more verbose listing of possible options for the iscsiadm command in
Red Hat Enterprise Linux 5 refer to the manual page using:

# man iscsiadm


For a good overview of iSCSI in Red Hat Enterprise Linux 5 refer to the
documentation provided in
/usr/share/doc/iscsi-initiator-utils-VERSION/README.

try:)



On Tue, Feb 4, 2014 at 10:48 AM, Michael Christie micha...@cs.wisc.eduwrote:


 On Jan 30, 2014, at 7:40 PM, ianil.ir...@gmail.com wrote:
  root@Blade15:~# iscsid -f -d 8
  iscsid: sysfs_init: sysfs_path='/sys'
 
  iscsid: sysfs_attr_get_value: open
 '/module/scsi_transport_iscsi'/'version'
 
  iscsid: sysfs_attr_get_value: new uncached attribute
 '/sys/module/scsi_transport_iscsi/version'
 
  iscsid: sysfs_attr_get_value: add to cache
 '/sys/module/scsi_transport_iscsi/version'
 
  iscsid: sysfs_attr_get_value: cache
 '/sys/module/scsi_transport_iscsi/version' with attribute value '2.0-870'
 
  iscsid: transport class version 2.0-870. iscsid version 2.0-871
  iscsid: Can not bind IPC socket
  iscsid: in ctldev_close


 You should kill all the iscsid instances then run that command. The above
 message means iscsid did not start.
 Without iscsid nothing will work. It could be it was already started.


 
 
 
  root@Blade15:~# iscsiadm -m node -T
 iqn.1986-03.com.hp:storage.p2000g3.13351a9162 -p 10.10.30.1:3260 --login
  Logging in to [iface: iface2, target:
 iqn.1986-03.com.hp:storage.p2000g3.13351a9162, portal: 10.10.30.1,3260]
  Logging in to [iface: iface4, target:
 iqn.1986-03.com.hp:storage.p2000g3.13351a9162, portal: 10.10.30.1,3260]
  iscsiadm: Could not login to [iface: iface2, target:
 iqn.1986-03.com.hp:storage.p2000g3.13351a9162, portal: 10.10.30.1,3260]:
  iscsiadm: initiator reported error (5 - encountered iSCSI login failure)
  iscsiadm: Could not login to [iface: iface4, target:
 iqn.1986-03.com.hp:storage.p2000g3.13351a9162, portal: 10.10.30.1,3260]:
  iscsiadm: initiator reported error (5 - encountered iSCSI login failure)
 


 When you run that command send the /var/log/messages and also the iscsid
 output.

 Also run iscsiadm with -d 8.

 And does it work with just the defaults iface? Does it just not work when
 trying to setup your own faces?

 --
 You received this message because you are subscribed to the Google Groups
 open-iscsi group.
 To unsubscribe from this group

Re: Login error (5 - encountered iSCSI login failure)

2012-12-23 Thread Mike Christie 
On 12/20/2012 09:27 AM, Dongmin Kim wrote:
 Hello,
 
  
 
 While I was tying to use iscsiadm, I found out that iSCSI initiator
 couldn't connect to the iSCSI target.
 
 It looks strange because the output from some commands looks normal.
 
 Then, does anyone from the group help me to fix it?
 


Thank you for providing so much info. There is just one more piece of
info I need though. Could you send the /var/log/messages from when you
ran the iscsiadm command and it failed? It will have more info about
what failed.

-- 
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: iSCSI discovery error: Could not perform SendTargets discovery: encountered non-retryable iSCSI login failure

2012-07-09 Thread Mike Christie 
On 07/09/2012 07:02 AM, Wassim Zaarour wrote:
 Hi List,
 
 I have installed iSCSI on CentOS and it was working fine with the Seagte
 NAS until i had a power cut.
 After the server and the NAS restarted, i am getting errors when i try
 to discover or restart iSCSI
 
 root@insync ~]# iscsiadm -m discovery -t sendtargets -p 172.16.10.2
 iscsiadm: Login response timeout. Waited 30 seconds and did not get
 reponse PDU.
 
 iscsiadm: discovery login to 172.16.10.2 failed, giving up 2
 iscsiadm: Could not perform SendTargets discovery: encountered
 non-retryable iSCSI login failure

What was the extra error info in /var/log/messages?


 
 [root@insync ~]# service iscsi restart
 Stopping iscsi:[  OK  ]
 Starting iscsi: iscsiadm: Could not login to [iface: default, target:
 iqn.1992-09.com.seagate:remote, portal: 172.16.10.2,3260].
 iscsiadm: initiator reported error (8 - connection timed out)
 iscsiadm: Could not login to [iface: default, target:
 iqn.1992-09.com.seagate:beirutusers, portal: 172.16.10.2,3260].
 iscsiadm: initiator reported error (8 - connection timed out)
 iscsiadm: Could not log into all portals
[  OK  ]



Your target's login settings probably got reset. Make sure the
/etc/iscsi/initiatorname.iscsi is setup in the target ACLs, any CHAP
settings you setup on the initiator are still setup on the target, and
make sure the portals that were found before are up and active.

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

iSCSI login failure

2012-02-14 Thread 韩拓 
hi list,
when i use this command(on 10.0.0.106)
iscsiadm -m node -T iqn.2010-10.org.openstack:volume-0008 -p
10.0.0.105:3260 --login

i got the error message:
Logging in to [iface: default, target: iqn.
2010-10.org.openstack:volume-0008, portal: 10.0.0.105,3260]
iscsiadm: Could not login to [iface: default, target: iqn.
2010-10.org.openstack:volume-0008, portal: 10.0.0.105,3260]:
iscsiadm: initiator reported error (19 - encountered non-retryable
iSCSI login failure



===

the /etc/ietd.conf is empty,all is default.

here is the ietd log on target host(10.0.0.105):

Feb 13 17:29:21 qtest5 ietd: BHS: (0xd703a0)
Feb 13 17:29:21 qtest5 ietd:  43 87 00 00 | 00 00 01 c7 | 00 02 3d 03
| 00 00 00 00 | C =  |
Feb 13 17:29:21 qtest5 ietd:  00 00 00 00 | 00 00 00 00 | 00 00 00 00
| 00 00 00 00 |  |
Feb 13 17:29:21 qtest5 ietd:  00 00 00 00 | 00 00 00 00 | 00 00 00 00
| 00 00 00 00 |  |
Feb 13 17:29:21 qtest5 ietd: AHS: (0xd725d0)
Feb 13 17:29:21 qtest5 ietd: Data: (0xd725d0)
Feb 13 17:29:21 qtest5 ietd:  49 6e 69 74 | 69 61 74 6f | 72 4e 61 6d
| 65 3d 69 71 | InitiatorName=iq |
Feb 13 17:29:21 qtest5 ietd:  6e 2e 31 39 | 39 33 2d 30 | 38 2e 6f 72
| 67 2e 64 65 | n.1993-08.org.de |
Feb 13 17:29:21 qtest5 ietd:  62 69 61 6e | 3a 30 31 3a | 35 62 61 65
| 36 66 39 38 | bian:01:5bae6f98 |
Feb 13 17:29:21 qtest5 ietd:  31 00 49 6e | 69 74 69 61 | 74 6f 72 41
| 6c 69 61 73 | 1 InitiatorAlias |
Feb 13 17:29:21 qtest5 ietd:  3d 71 74 65 | 73 74 36 00 | 54 61 72 67
| 65 74 4e 61 | =qtest6 TargetNa |
Feb 13 17:29:21 qtest5 ietd:  6d 65 3d 69 | 71 6e 2e 32 | 30 31 30 2d
| 31 30 2e 6f | me=iqn.2010-10.o |
Feb 13 17:29:21 qtest5 ietd:  72 67 2e 6f | 70 65 6e 73 | 74 61 63 6b
| 3a 76 6f 6c | rg.openstack:vol |
Feb 13 17:29:21 qtest5 ietd:  75 6d 65 2d | 30 30 30 30 | 30 30 30 38
| 00 53 65 73 | ume-0008 Ses |
Feb 13 17:29:21 qtest5 ietd:  73 69 6f 6e | 54 79 70 65 | 3d 4e 6f 72
| 6d 61 6c 00 | sionType=Normal  |
Feb 13 17:29:21 qtest5 ietd:  48 65 61 64 | 65 72 44 69 | 67 65 73 74
| 3d 4e 6f 6e | HeaderDigest=Non |
Feb 13 17:29:21 qtest5 ietd:  65 00 44 61 | 74 61 44 69 | 67 65 73 74
| 3d 4e 6f 6e | e DataDigest=Non |
Feb 13 17:29:21 qtest5 ietd:  65 00 44 65 | 66 61 75 6c | 74 54 69 6d
| 65 32 57 61 | e DefaultTime2Wa |
Feb 13 17:29:21 qtest5 ietd:  69 74 3d 32 | 00 44 65 66 | 61 75 6c 74
| 54 69 6d 65 | it=2 DefaultTime |
Feb 13 17:29:21 qtest5 ietd:  32 52 65 74 | 61 69 6e 3d | 30 00 49 46
| 4d 61 72 6b | 2Retain=0 IFMark |
Feb 13 17:29:21 qtest5 ietd:  65 72 3d 4e | 6f 00 4f 46 | 4d 61 72 6b
| 65 72 3d 4e | er=No OFMarker=N |
Feb 13 17:29:21 qtest5 ietd:  6f 00 45 72 | 72 6f 72 52 | 65 63 6f 76
| 65 72 79 4c | o ErrorRecoveryL |
Feb 13 17:29:21 qtest5 ietd:  65 76 65 6c | 3d 30 00 49 | 6e 69 74 69
| 61 6c 52 32 | evel=0 InitialR2 |
Feb 13 17:29:21 qtest5 ietd:  54 3d 4e 6f | 00 49 6d 6d | 65 64 69 61
| 74 65 44 61 | T=No ImmediateDa |
Feb 13 17:29:21 qtest5 ietd:  74 61 3d 59 | 65 73 00 4d | 61 78 42 75
| 72 73 74 4c | ta=Yes MaxBurstL |
Feb 13 17:29:21 qtest5 ietd:  65 6e 67 74 | 68 3d 31 36 | 37 37 36 31
| 39 32 00 46 | ength=16776192 F |
Feb 13 17:29:21 qtest5 ietd:  69 72 73 74 | 42 75 72 73 | 74 4c 65 6e
| 67 74 68 3d | irstBurstLength= |
Feb 13 17:29:21 qtest5 ietd:  32 36 32 31 | 34 34 00 4d | 61 78 4f 75
| 74 73 74 61 | 262144 MaxOutsta |
Feb 13 17:29:21 qtest5 ietd:  6e 64 69 6e | 67 52 32 54 | 3d 31 00 4d
| 61 78 43 6f | ndingR2T=1 MaxCo |
Feb 13 17:29:21 qtest5 ietd:  6e 6e 65 63 | 74 69 6f 6e | 73 3d 31 00
| 44 61 74 61 | nnections=1 Data |
Feb 13 17:29:21 qtest5 ietd:  50 44 55 49 | 6e 4f 72 64 | 65 72 3d 59
| 65 73 00 44 | PDUInOrder=Yes D |
Feb 13 17:29:21 qtest5 ietd:  61 74 61 53 | 65 71 75 65 | 6e 63 65 49
| 6e 4f 72 64 | ataSequenceInOrd |
Feb 13 17:29:21 qtest5 ietd:  65 72 3d 59 | 65 73 00 4d | 61 78 52 65
| 63 76 44 61 | er=Yes MaxRecvDa |
Feb 13 17:29:21 qtest5 ietd:  74 61 53 65 | 67 6d 65 6e | 74 4c 65 6e
| 67 74 68 3d | taSegmentLength= |
Feb 13 17:29:21 qtest5 ietd:  32 36 32 31 | 34 34 00|
| | 262144   |
Feb 13 17:29:21 qtest5 ietd: Login request (operational negotiation):
0
Feb 13 17:29:21 qtest5 ietd: Can't get session param 6 22
Feb 13 17:29:21 qtest5 ietd: exp_cmd_sn: 0,0
Feb 13 17:29:21 qtest5 ietd: alloc'ed new buf_segment
Feb 13 17:29:21 qtest5 ietd: wrote: TargetPortalGroupTag
Feb 13 17:29:21 qtest5 ietd: wrote: =
Feb 13 17:29:21 qtest5 ietd: wrote: 1
Feb 13 17:29:21 qtest5 ietd: wrote:
Feb 13 17:29:21 qtest5 ietd: BHS: (0xd703f8)
Feb 13 17:29:21 qtest5 ietd:  23 04 00 00 | 00 00 00 00 | 00 00 00 00
| 00 00 00 00 | #|
Feb 13 17:29:21 qtest5 ietd:  00 00 00 00 | 00 00 00 00 | 00 00 00 00
| 00 00 00 00 |  |
Feb 13 17:29:21 qtest5 ietd:  00 00 00 00 | 02 01 00 00 | 00 00 00 00
| 00 00 00 00 |  |
Feb 13 17:29:21 qtest5 ietd: AHS: ((nil))
Feb 13 17:29:21 qtest5 ietd: Data: ((nil))
Feb 13 17:29:21 qtest5 ietd

Re: iSCSI login failure

2012-02-14 Thread Mike Christie 
On 02/13/2012 03:38 AM, 韩拓 wrote:
 hi list,
 when i use this command(on 10.0.0.106)
 iscsiadm -m node -T iqn.2010-10.org.openstack:volume-0008 -p
 10.0.0.105:3260 --login
 
 i got the error message:
 Logging in to [iface: default, target: iqn.
 2010-10.org.openstack:volume-0008, portal: 10.0.0.105,3260]
 iscsiadm: Could not login to [iface: default, target: iqn.
 2010-10.org.openstack:volume-0008, portal: 10.0.0.105,3260]:
 iscsiadm: initiator reported error (19 - encountered non-retryable
 iSCSI login failure
 
 

Could you send the /var/log/messages for the system the initiator is on?

-- 
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: iSCSI login failure

2009-09-16 Thread Mike Christie 

Jesse Butler wrote:
 
 I am attempting to login to a Solaris iSER target w/ a Linux machine,  
 and am seeing this error:
 
 #   iscsiadm -m node -T iqn.1986-03.com.sun:02:d8e2ebc9-6886-46dd-91f6- 
 e80b7400948d -p 10.0.0.2:3260,1 -l
 Logging in to [iface: default, target: iqn.1986-03.com.sun: 
 02:d8e2ebc9-6886-46dd-91f6-e80b7400948d, portal: 10.0.0.2,3260]
 iscsiadm: Could not login to [iface: default, target: iqn. 
 1986-03.com.sun:02:d8e2ebc9-6886-46dd-91f6-e80b7400948d, portal:  
 10.0.0.2,3260]:
 iscsiadm: initiator reported error (5 - encountered iSCSI login failure)
 #
 
 I think I have everything configured properly (see below), so I'm just  
 wondering what that 5 means so I can try to troubleshoot this.  I  

5 actually just means the error encountered iSCSI login failure. It is 
just a generic error value to cover all login problems.

There is normally more error info in /var/log/messages like if it was a 
chap error or a login pdu error and what the status/class values were or 
if it was just a connection problem. Look for something from iscsiadm or 
iscsid in there.


 looked at the code, but it's a bit difficult to track all the way into  
 the specific error codes.
 
 My Linux Kung Fu is weak, so if version/rev info is needed, please let  
 me know what and how to retrieve it.
 

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

Re: iSCSI login failure

2009-09-16 Thread Mike Christie 

Mike Berg wrote:
 I see:
 
 iscsid: Login negotiation failed, couldn't recognize text 
 MaxOutstandingUnexpectedPDUs=0
 
 in /var/log/messages.
 
 Is the initiator getting MaxOutstandingUnexpectedPDUs=0 from the target?

Yeah, the target is sending the initaitor that string during login 
negotiation. We have no idea what it is (is it a iser value?) and do not 
know how to handle it so we fail the login process.

 
 
 On Sep 16, 2009, at 11:02 AM, Mike Christie wrote:
 
 Jesse Butler wrote:
 I am attempting to login to a Solaris iSER target w/ a Linux 
 machine,  and am seeing this error:
 #   iscsiadm -m node -T 
 iqn.1986-03.com.sun:02:d8e2ebc9-6886-46dd-91f6- e80b7400948d -p 
 10.0.0.2:3260,1 -l
 Logging in to [iface: default, target: iqn.1986-03.com.sun: 
 02:d8e2ebc9-6886-46dd-91f6-e80b7400948d, portal: 10.0.0.2,3260]
 iscsiadm: Could not login to [iface: default, target: iqn. 
 1986-03.com.sun:02:d8e2ebc9-6886-46dd-91f6-e80b7400948d, portal:  
 10.0.0.2,3260]:
 iscsiadm: initiator reported error (5 - encountered iSCSI login failure)
 #
 I think I have everything configured properly (see below), so I'm 
 just  wondering what that 5 means so I can try to troubleshoot 
 this.  I

 5 actually just means the error encountered iSCSI login failure. It 
 is just a generic error value to cover all login problems.

 There is normally more error info in /var/log/messages like if it was 
 a chap error or a login pdu error and what the status/class values 
 were or if it was just a connection problem. Look for something from 
 iscsiadm or iscsid in there.


 looked at the code, but it's a bit difficult to track all the way 
 into  the specific error codes.
 My Linux Kung Fu is weak, so if version/rev info is needed, please 
 let  me know what and how to retrieve it.
 


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

Re: iSCSI login failure

2009-09-16 Thread Mike Berg 

I see:

iscsid: Login negotiation failed, couldn't recognize text  
MaxOutstandingUnexpectedPDUs=0

in /var/log/messages.

Is the initiator getting MaxOutstandingUnexpectedPDUs=0 from the target?


On Sep 16, 2009, at 11:02 AM, Mike Christie wrote:

 Jesse Butler wrote:
 I am attempting to login to a Solaris iSER target w/ a Linux  
 machine,  and am seeing this error:
 #   iscsiadm -m node -T iqn.1986-03.com.sun: 
 02:d8e2ebc9-6886-46dd-91f6- e80b7400948d -p 10.0.0.2:3260,1 -l
 Logging in to [iface: default, target: iqn.1986-03.com.sun:  
 02:d8e2ebc9-6886-46dd-91f6-e80b7400948d, portal: 10.0.0.2,3260]
 iscsiadm: Could not login to [iface: default, target: iqn.  
 1986-03.com.sun:02:d8e2ebc9-6886-46dd-91f6-e80b7400948d, portal:   
 10.0.0.2,3260]:
 iscsiadm: initiator reported error (5 - encountered iSCSI login  
 failure)
 #
 I think I have everything configured properly (see below), so I'm  
 just  wondering what that 5 means so I can try to troubleshoot  
 this.  I

 5 actually just means the error encountered iSCSI login failure.  
 It is just a generic error value to cover all login problems.

 There is normally more error info in /var/log/messages like if it  
 was a chap error or a login pdu error and what the status/class  
 values were or if it was just a connection problem. Look for  
 something from iscsiadm or iscsid in there.


 looked at the code, but it's a bit difficult to track all the way  
 into  the specific error codes.
 My Linux Kung Fu is weak, so if version/rev info is needed, please  
 let  me know what and how to retrieve it.


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

Re: iSCSI login failure

2009-09-16 Thread Mike Christie 

Jesse Butler wrote:
 No, that was an old copy of the RFC. Current valid values are
 
   MaxOutstandingUnexpectedPDUs=numerical-value-from-2-to-(2**32-1) | 0
 
 which means we're just fine replying w/ 0.
 
 Is this a bug on the OpeniSCSI side, where you're intercepting an iSER  
 key-value and failing since you don't recognize it, rather than  
 passing it down?

This is a bug on the initiator side. Open-iscsi just has no code to 
handle this key. I guess the iser guys just never implemented it (ccing Or).


 
 Let me know what you think, thanks.
 
 
 On Sep 16, 2009, at 11:51 AM, Mike Christie wrote:
 
 Mike Berg wrote:
 I see:

 iscsid: Login negotiation failed, couldn't recognize text
 MaxOutstandingUnexpectedPDUs=0

 in /var/log/messages.

 Is the initiator getting MaxOutstandingUnexpectedPDUs=0 from the  
 target?
 Yeah, the target is sending the initaitor that string during login
 negotiation. We have no idea what it is (is it a iser value?) and do  
 not
 know how to handle it so we fail the login process.


 On Sep 16, 2009, at 11:02 AM, Mike Christie wrote:

 Jesse Butler wrote:
 I am attempting to login to a Solaris iSER target w/ a Linux
 machine,  and am seeing this error:
 #   iscsiadm -m node -T
 iqn.1986-03.com.sun:02:d8e2ebc9-6886-46dd-91f6- e80b7400948d -p
 10.0.0.2:3260,1 -l
 Logging in to [iface: default, target: iqn.1986-03.com.sun:
 02:d8e2ebc9-6886-46dd-91f6-e80b7400948d, portal: 10.0.0.2,3260]
 iscsiadm: Could not login to [iface: default, target: iqn.
 1986-03.com.sun:02:d8e2ebc9-6886-46dd-91f6-e80b7400948d, portal:
 10.0.0.2,3260]:
 iscsiadm: initiator reported error (5 - encountered iSCSI login  
 failure)
 #
 I think I have everything configured properly (see below), so I'm
 just  wondering what that 5 means so I can try to troubleshoot
 this.  I
 5 actually just means the error encountered iSCSI login failure.  
 It
 is just a generic error value to cover all login problems.

 There is normally more error info in /var/log/messages like if it  
 was
 a chap error or a login pdu error and what the status/class values
 were or if it was just a connection problem. Look for something from
 iscsiadm or iscsid in there.


 looked at the code, but it's a bit difficult to track all the way
 into  the specific error codes.
 My Linux Kung Fu is weak, so if version/rev info is needed, please
 let  me know what and how to retrieve it.

 
 
  


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

Re: iSCSI login failure

2009-09-16 Thread Mike Christie 
Mike Christie wrote:
 Jesse Butler wrote:
 No, that was an old copy of the RFC. Current valid values are

  MaxOutstandingUnexpectedPDUs=numerical-value-from-2-to-(2**32-1) | 0

 which means we're just fine replying w/ 0.

 Is this a bug on the OpeniSCSI side, where you're intercepting an iSER  
 key-value and failing since you don't recognize it, rather than  
 passing it down?
 
 This is a bug on the initiator side. Open-iscsi just has no code to 
 handle this key. I guess the iser guys just never implemented it (ccing Or).
 

Hey, so MaxOutstandingUnexpectedPDU is for iser only right and 0 means 
there is no limit? If so, I think this patch will work for the default case.

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

diff --git a/usr/login.c b/usr/login.c
index 0235870..74813a9 100644
--- a/usr/login.c
+++ b/usr/login.c
@@ -544,6 +544,21 @@ get_op_params_text_keys(iscsi_session_t *session, int cid,
 			return LOGIN_NEGOTIATION_FAILED;
 		}
 		text = value_end;
+	} else if (iscsi_find_key_value(MaxOutstandingUnexpectedPDU, text,
+	 end, value, value_end)) {
+		if (!session-t-template-rdma) {
+			log_error(Login negotiation failed. Can't accept 
+  MaxOutstandingUnexpectedPDU for non 
+  RDMA connections.);
+			return LOGIN_NEGOTIATION_FAILED;
+		}
+
+		if (strcmp(value, 0)) {
+			log_error(Login negotiation failed. iSER initiator 
+  only supports MaxOutstandingUnexpectedPDU 
+  of 0.\n);
+			return LOGIN_NEGOTIATION_FAILED;
+		}
 	} else if (iscsi_find_key_value(RDMAExtensions, text, end,
 	value, value_end)) {
 		if (session-t-template-rdma

Re: iSCSI login failure

2009-09-16 Thread Mike Berg 


On Sep 16, 2009, at 11:51 AM, Mike Christie wrote:

 Mike Berg wrote:
 I see:
 iscsid: Login negotiation failed, couldn't recognize text  
 MaxOutstandingUnexpectedPDUs=0
 in /var/log/messages.
 Is the initiator getting MaxOutstandingUnexpectedPDUs=0 from the  
 target?

 Yeah, the target is sending the initaitor that string during login  
 negotiation. We have no idea what it is (is it a iser value?) and do  
 not know how to handle it so we fail the login process.

We are trying to establish an iser connection. I'll have to  
investigate more as I am using newer software releases on everything  
and I do not recall this problem before.

thanks.


 On Sep 16, 2009, at 11:02 AM, Mike Christie wrote:
 Jesse Butler wrote:
 I am attempting to login to a Solaris iSER target w/ a Linux  
 machine,  and am seeing this error:
 #   iscsiadm -m node -T iqn.1986-03.com.sun: 
 02:d8e2ebc9-6886-46dd-91f6- e80b7400948d -p 10.0.0.2:3260,1 -l
 Logging in to [iface: default, target: iqn.1986-03.com.sun:  
 02:d8e2ebc9-6886-46dd-91f6-e80b7400948d, portal: 10.0.0.2,3260]
 iscsiadm: Could not login to [iface: default, target: iqn.  
 1986-03.com.sun:02:d8e2ebc9-6886-46dd-91f6-e80b7400948d, portal:   
 10.0.0.2,3260]:
 iscsiadm: initiator reported error (5 - encountered iSCSI login  
 failure)
 #
 I think I have everything configured properly (see below), so I'm  
 just  wondering what that 5 means so I can try to troubleshoot  
 this.  I

 5 actually just means the error encountered iSCSI login failure.  
 It is just a generic error value to cover all login problems.

 There is normally more error info in /var/log/messages like if it  
 was a chap error or a login pdu error and what the status/class  
 values were or if it was just a connection problem. Look for  
 something from iscsiadm or iscsid in there.


 looked at the code, but it's a bit difficult to track all the way  
 into  the specific error codes.
 My Linux Kung Fu is weak, so if version/rev info is needed,  
 please let  me know what and how to retrieve it.



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

Re: iSCSI login failure

2009-09-16 Thread Jesse Butler 


On Sep 16, 2009, at 4:06 PM, Mike Christie wrote:

 Mike Christie wrote:
 Jesse Butler wrote:
 No, that was an old copy of the RFC. Current valid values are

 MaxOutstandingUnexpectedPDUs=numerical-value-from-2-to-(2**32-1)  
 | 0

 which means we're just fine replying w/ 0.

 Is this a bug on the OpeniSCSI side, where you're intercepting an  
 iSER
 key-value and failing since you don't recognize it, rather than
 passing it down?

 This is a bug on the initiator side. Open-iscsi just has no code to
 handle this key. I guess the iser guys just never implemented it  
 (ccing Or).


 Hey, so MaxOutstandingUnexpectedPDU is for iser only right and 0 means
 there is no limit?

Yes exactly.

 If so, I think this patch will work for the default case.

Ok, I will pass this off to Or and to Mike Berg, I think.  Let me know  
if I can do anything to assist further!

Thanks for your rapid response, Mike (Christie).

/jb



 
 diff --git a/usr/login.c b/usr/login.c
 index 0235870..74813a9 100644
 --- a/usr/login.c
 +++ b/usr/login.c
 @@ -544,6 +544,21 @@ get_op_params_text_keys(iscsi_session_t  
 *session, int cid,
   return LOGIN_NEGOTIATION_FAILED;
   }
   text = value_end;
 + } else if (iscsi_find_key_value(MaxOutstandingUnexpectedPDU, text,
 +  end, value, value_end)) {
 + if (!session-t-template-rdma) {
 + log_error(Login negotiation failed. Can't accept 
 +   MaxOutstandingUnexpectedPDU for non 
 +   RDMA connections.);
 + return LOGIN_NEGOTIATION_FAILED;
 + }
 +
 + if (strcmp(value, 0)) {
 + log_error(Login negotiation failed. iSER initiator 
 +   only supports MaxOutstandingUnexpectedPDU 
 +   of 0.\n);
 + return LOGIN_NEGOTIATION_FAILED;
 + }
   } else if (iscsi_find_key_value(RDMAExtensions, text, end,
   value, value_end)) {
   if (session-t-template-rdma 


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

Re: login failure-iscsi: received itt 4000000

2009-04-28 Thread Ulrich Windl 

On 27 Apr 2009 at 10:46, Mike Christie wrote:

[...]
  Apr 24 12:40:33 localhost iscsid: conn 0 login rejected: initiator
  error - target not found (02/03)
 
 
 It might be related to this. It just means that we tried to log into a 
 target, but it did not exist on the other box.
[...]

Hi!

Is there any documentation (other than the sources) where those numeric codes 
like 
(02/03) are explained?

Regards,
Ulrich



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

Re: login failure-iscsi: received itt 4000000

2009-04-28 Thread Mike Christie 

Ulrich Windl wrote:
 On 27 Apr 2009 at 10:46, Mike Christie wrote:
 
 [...]
 Apr 24 12:40:33 localhost iscsid: conn 0 login rejected: initiator
 error - target not found (02/03)

 It might be related to this. It just means that we tried to log into a 
 target, but it did not exist on the other box.
 [...]
 
 Hi!
 
 Is there any documentation (other than the sources) where those numeric codes 
 like 
 (02/03) are explained?
 

That is a iscsi SPEC error value. http://www.ietf.org/rfc/rfc3720.txt 
Page 161.

If you are going to ask, yes, I am planning on converting those to a the 
strings in there. I got to finish up work stuff (bnx2i addition) first.

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

Re: was [Re: Login failure]: iSer login failure

2008-12-16 Thread Or Gerlitz 

Mike Christie wrote:
 Login session [iiser: iser_connect:connecting to: 10.8.0.112, port  
 0xbc0c
 face: default, target: iqn.1986-iser: iser_cma_handler:event 0 conn  
 81022847ce80 id 81023eb82a00
 03.com.sun:02:91iser: iser_cma_handler:event 2 conn 81022847ce80  
 id 81023eb82a00
 7071dc-db02-ebf0-9508-d11df2889cda, portal: 10.8.0.112,3260]
 iser: iser_create_ib_conn_res:setting conn 81022847ce80 cma_id  
 81023eb82a00: fmr_pool 81043edf8d40 qp 810247154200
 iser: iser_cma_handler:event 9 conn 81022847ce80 id 81023eb82a00
 iser: iscsi_iser_ep_poll:ib conn 81022847ce80 rc = 1
 iser: iscsi_iser_conn_bind:binding iscsi conn 810228385290 to  
 iser_conn 81022847ce80
 iser: iser_cma_handler:event 10 conn 81022847ce80 id  
 81023eb82a00
 iser: iscsi_iser_ep_disconnect:ib conn 81022847ce80 state 4
 iser: iser_free_ib_conn_res:freeing conn 81022847ce80 cma_id  
 81023eb82a00 fmr pool 81043edf8d40 qp 810247154200
 iser: iser_device_try_release:device 81043fee4d40 refcount 1
 [ snip ]
 iscsiadm: initiator reported error (5 - encountered iSCSI login failure)
 iscsiadm: Could not execute operation on all records. Err 107.

 Any way to get some more robust information regarding iSCSI login  
 failure?

 What are you talking about. You do not have the iser_cmd_handler event 
 numbers memorized yet :) Me neither :( It looks like the target 
 disconnected and there was some sort of iser connection error because 
 the ib_conn state is ISER_CONN_DOWN. The iser guys can diagnose it 
 better for whatever kernel you are using.
What you have here is connection established (event 9) and then 
disconnection (event 10). I suggest that you use logging with the iscsid 
user space daemon to realize better what went wrong. The way I do this 
is: start the service, then logout, then kill the daemon, run it again 
with logging/debug prints open and login manually.

run$ iscsid -d 8 -f  /tmp/iscsid.log 21 
login$ iscsiadm -m node -T $target -l
logout$ iscsiadm -m node -T $target -u


As for the iser event numbers... it not iser but rather the RDMA CM 
events, they are present in include/rdma/rdma_cm.h at the kernel source 
tree.

Or.


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

Login failure

2008-12-10 Thread Jesse Butler 

Not sure what we changed, but we're having failures logging into our  
iSER target now with RHEL 5.2 / OFED 1.3 initiator which has been  
working.

Login session [iiser: iser_connect:connecting to: 10.8.0.112, port  
0xbc0c
face: default, target: iqn.1986-iser: iser_cma_handler:event 0 conn  
81022847ce80 id 81023eb82a00
03.com.sun:02:91iser: iser_cma_handler:event 2 conn 81022847ce80  
id 81023eb82a00
7071dc-db02-ebf0-9508-d11df2889cda, portal: 10.8.0.112,3260]
iser: iser_create_ib_conn_res:setting conn 81022847ce80 cma_id  
81023eb82a00: fmr_pool 81043edf8d40 qp 810247154200
iser: iser_cma_handler:event 9 conn 81022847ce80 id 81023eb82a00
iser: iscsi_iser_ep_poll:ib conn 81022847ce80 rc = 1
iser: iscsi_iser_conn_bind:binding iscsi conn 810228385290 to  
iser_conn 81022847ce80
iser: iser_cma_handler:event 10 conn 81022847ce80 id  
81023eb82a00
iser: iscsi_iser_ep_disconnect:ib conn 81022847ce80 state 4
iser: iser_free_ib_conn_res:freeing conn 81022847ce80 cma_id  
81023eb82a00 fmr pool 81043edf8d40 qp 810247154200
iser: iser_device_try_release:device 81043fee4d40 refcount 1
[ snip ]
iscsiadm: initiator reported error (5 - encountered iSCSI login failure)
iscsiadm: Could not execute operation on all records. Err 107.

Any way to get some more robust information regarding iSCSI login  
failure?

Thanks
/jb

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

was [Re: Login failure]: iSer login failure

2008-12-10 Thread Mike Christie 

For iser questions you should stick something about iser in the subject, 
because I do not think the iser guys read every email on the list. I 
added Eli and Or.


Jesse Butler wrote:
 Not sure what we changed, but we're having failures logging into our  
 iSER target now with RHEL 5.2 / OFED 1.3 initiator which has been  
 working.
 

Is this using the iscsi tools that come with RHEL 5.2 or with OFED 1.3? 
Also does OFED use its own kernel or is this with the RHEL 5.2 kernel?


Is this related to the other issue you posted about on Monday? I did not 
see a reply. I was asking the same thing about OFED. I forgot to ask 
about the kernel.


 Login session [iiser: iser_connect:connecting to: 10.8.0.112, port  
 0xbc0c
 face: default, target: iqn.1986-iser: iser_cma_handler:event 0 conn  
 81022847ce80 id 81023eb82a00
 03.com.sun:02:91iser: iser_cma_handler:event 2 conn 81022847ce80  
 id 81023eb82a00
 7071dc-db02-ebf0-9508-d11df2889cda, portal: 10.8.0.112,3260]
 iser: iser_create_ib_conn_res:setting conn 81022847ce80 cma_id  
 81023eb82a00: fmr_pool 81043edf8d40 qp 810247154200
 iser: iser_cma_handler:event 9 conn 81022847ce80 id 81023eb82a00
 iser: iscsi_iser_ep_poll:ib conn 81022847ce80 rc = 1
 iser: iscsi_iser_conn_bind:binding iscsi conn 810228385290 to  
 iser_conn 81022847ce80
 iser: iser_cma_handler:event 10 conn 81022847ce80 id  
 81023eb82a00
 iser: iscsi_iser_ep_disconnect:ib conn 81022847ce80 state 4
 iser: iser_free_ib_conn_res:freeing conn 81022847ce80 cma_id  
 81023eb82a00 fmr pool 81043edf8d40 qp 810247154200
 iser: iser_device_try_release:device 81043fee4d40 refcount 1
 [ snip ]
 iscsiadm: initiator reported error (5 - encountered iSCSI login failure)
 iscsiadm: Could not execute operation on all records. Err 107.
 
 Any way to get some more robust information regarding iSCSI login  
 failure?

What are you talking about. You do not have the iser_cmd_handler event 
numbers memorized yet :) Me neither :( It looks like the target 
disconnected and there was some sort of iser connection error because 
the ib_conn state is ISER_CONN_DOWN. The iser guys can diagnose it 
better for whatever kernel you are using.


 
 Thanks
 /jb
 
  


--~--~-~--~~~---~--~~
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: was [Re: Login failure]: iSer login failure

2008-12-10 Thread Jesse Butler 


On Dec 10, 2008, at 11:47 AM, Mike Christie wrote:


 For iser questions you should stick something about iser in the  
 subject,
 because I do not think the iser guys read every email on the list. I
 added Eli and Or.


Ah, OK.  Thanks!


 Jesse Butler wrote:
 Not sure what we changed, but we're having failures logging into our
 iSER target now with RHEL 5.2 / OFED 1.3 initiator which has been
 working.


 Is this using the iscsi tools that come with RHEL 5.2 or with OFED  
 1.3?
 Also does OFED use its own kernel or is this with the RHEL 5.2 kernel?


Same that I've been running all along...  This is RHEL 5.2 w/ OFED 1.3  
built on top of it.  I know it comes bundled, but it did not work.  I  
am using whichever Open iSCSI comes bundled w/ OFED 1.3.   Also, I  
remember I had to update the tcl pkg for some reason?  Other than  
that, stock kernel and libraries.


 Is this related to the other issue you posted about on Monday? I did  
 not
 see a reply. I was asking the same thing about OFED. I forgot to ask
 about the kernel.

No, I don't think related to that.




 Login session [iiser: iser_connect:connecting to: 10.8.0.112, port
 0xbc0c
 face: default, target: iqn.1986-iser: iser_cma_handler:event 0 conn
 81022847ce80 id 81023eb82a00
 03.com.sun:02:91iser: iser_cma_handler:event 2 conn 81022847ce80
 id 81023eb82a00
 7071dc-db02-ebf0-9508-d11df2889cda, portal: 10.8.0.112,3260]
 iser: iser_create_ib_conn_res:setting conn 81022847ce80 cma_id
 81023eb82a00: fmr_pool 81043edf8d40 qp 810247154200
 iser: iser_cma_handler:event 9 conn 81022847ce80 id  
 81023eb82a00
 iser: iscsi_iser_ep_poll:ib conn 81022847ce80 rc = 1
 iser: iscsi_iser_conn_bind:binding iscsi conn 810228385290 to
 iser_conn 81022847ce80
 iser: iser_cma_handler:event 10 conn 81022847ce80 id
 81023eb82a00
 iser: iscsi_iser_ep_disconnect:ib conn 81022847ce80 state 4
 iser: iser_free_ib_conn_res:freeing conn 81022847ce80 cma_id
 81023eb82a00 fmr pool 81043edf8d40 qp 810247154200
 iser: iser_device_try_release:device 81043fee4d40 refcount 1
 [ snip ]
 iscsiadm: initiator reported error (5 - encountered iSCSI login  
 failure)
 iscsiadm: Could not execute operation on all records. Err 107.

 Any way to get some more robust information regarding iSCSI login
 failure?

 What are you talking about. You do not have the iser_cmd_handler event
 numbers memorized yet :) Me neither :( It looks like the target
 disconnected and there was some sort of iser connection error because
 the ib_conn state is ISER_CONN_DOWN. The iser guys can diagnose it
 better for whatever kernel you are using.


Oh, OK.  This is very helpful.  I'll explore from this side (I was  
thinking it had to do w/ some iSCSI parameter, but maybe I'm just  
blowing up the RC channel for no good reason).

Thanks
/jb



 Thanks
 /jb




 


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