Ulrich Windl wrote:
> Well, I knew, but...where is the connection number there (SLES10 SP2)?:
> 


Ah yeah, I guess I never printed it out since it was always 0.

> Target: 
> iqn.1986-03.com.hp:fcgw.mpx100:rkdvmis1.0.50001fe1500c1f60.50001fe1500c1f6c
>         Current Portal: 172.20.76.1:3260,0
>         Persistent Portal: 172.20.76.1:3260,0
>                 **********
>                 Interface:
>                 **********
>                 Iface Name: default
>                 Iface Transport: tcp
>                 Iface Initiatorname: 
> iqn.1992-04.de.uni-regensburg.klinik:testhost
>                 Iface IPaddress: 172.20.76.13
>                 Iface HWaddress: default
>                 Iface Netdev: default
>                 SID: 32

This is the session id.

I will print out the connection id here too. For what you want to do it 
is not important though.

>                 iSCSI Connection State: LOGGED IN
>                 iSCSI Session State: Unknown
>                 Internal iscsid Session State: NO CHANGE
>                 ************************
>                 Negotiated iSCSI params:
>                 ************************
>                 HeaderDigest: None
>                 DataDigest: None
>                 MaxRecvDataSegmentLength: 65536
>                 MaxXmitDataSegmentLength: 65536
>                 FirstBurstLength: 65536
>                 MaxBurstLength: 262144
>                 ImmediateData: Yes
>                 InitialR2T: Yes
>                 MaxOutstandingR2T: 1
>                 ************************
>                 Attached SCSI devices:
>                 ************************
>                 Host Number: 34 State: running
>                 scsi34 Channel 00 Id 0 Lun: 0
> 
>> In older tools there was a debug option
>> iscsiadm -m session -i
> 
> On a multiple-CPU machine with multiple iSCSI portals an storage systems 
> behind, 
> event ordering can be quite confusing, so that's why I'm asking. Again, when 
> seeing:
> 
> kernel: ping timeout of 15 secs expired, last rx 4748275159, last ping 
> 4748277659, 
> now 4748281409
> kernel:  connection12:0: iscsi: detected conn error (1011)
> 
> How can I find out which connection (i.e. which SCSI target) is actually 
> affected?
> 

The connection value is always zero. You want to match the session 
number which is the 12 in connection12:0. For the iscsiadm ... -P 3 
print out above that SID value is the session id and is what you want to 
match against. For the iscsiadm -m session the SID is the number in 
brackets.


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

Reply via email to