| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
> I'm getting this error in my event logs almost precisely every 30
> seconds. The iscsi connection fails to the discovery address, and then
> is immediately made again.
>
> Dec 14 15:48:52 chlorine iscsid[19813]: Connection to Discovery Address
> 192.168.15.2 failed
> Dec 14 15:48:52 chlorine iscsid[19815]: Connection to Discovery Address
> 192.168.15.3 failed
> Dec 14 15:48:52 chlorine iscsid[19813]: Connected to Discovery Address
> 192.168.15.2
> Dec 14 15:48:52 chlorine iscsid[19815]: Connected to Discovery Address
> 192.168.15.3
>
> Does anyone have any ideas what I can do to remedy this? All RHEL4U4
> hosts that connect to this target exhibit this behavior, while the
> windows hosts do not.
Hello Matthew!
Just wondering if you have found a solution ?
I'm having the exact same problem on a debian sarge box (kernel
2.6.8-3-686-smp, SFNet iSCSI Driver Version ... 4:0.1.10, Dell/EMC
AX150SCi):
Jan 3 00:22:14 rocksteady iscsid[2408]: Connection to Discovery Address
10.10.1.10 failed
Jan 3 00:22:14 rocksteady iscsid[2408]: Connected to Discovery Address
10.10.1.10
Jan 3 00:22:45 rocksteady iscsid[2408]: Connection to Discovery Address
10.10.1.10 failed
Jan 3 00:22:45 rocksteady iscsid[2408]: Connected to Discovery Address
10.10.1.10
I have tried the Continuous=no/yes option and setting the global idle
timeout to something below 30 (20):
iscsi-ls -c:
*******************************************************************************
SFNet iSCSI Driver Version ... 4:0.1.10 ( 8-Oct-2004)
*******************************************************************************
TARGET NAME : iqn.1992-04.com.emc:ax.fcnpr062301759.a0
TARGET ALIAS :
HOST NO : 3
TARGET ADDRESS : 10.10.1.10:3260
SESSION STATUS : CONNECTION ON 10.10.1.10:3260
ESTABLISHED AT Tue Jan 2 23:20:45 2007
NO. OF PORTALS : 1
PORTAL ADDRESS 1 : 10.10.1.10:3260,1
SESSION ID : ISID 00023d000001 TSIH a197
TARGET CONFIGURATION KEYS :
-------------------------
INITIAL R2T : Yes
IMMEDIATE DATA : No
HEADERDIGEST : NONE
DATA DIGEST : NONE
FIRSTBURSTLENGTH : 0
MAXBURSTLENGTH : 262144
MAXRECVDATASEGMENTLENGTH: initiator - 131072
target - 65536
LOGIN TIMEOUT : 15
AUTH TIMEOUT : 45
ACTIVE TIMEOUT : 5
IDLE TIMEOUT : 60
PING TIMEOUT : 5
*******************************************************************************
TARGET NAME : iqn.1992-04.com.emc:ax.fcnpr062301759.a1
TARGET ALIAS :
HOST NO : 4
TARGET ADDRESS : 10.10.2.10:3260
SESSION STATUS : CONNECTION ON 10.10.2.10:3260
ESTABLISHED AT Tue Jan 2 23:20:45 2007
NO. OF PORTALS : 1
PORTAL ADDRESS 1 : 10.10.2.10:3260,2
SESSION ID : ISID 00023d000001 TSIH a198
TARGET CONFIGURATION KEYS :
-------------------------
INITIAL R2T : Yes
IMMEDIATE DATA : No
HEADERDIGEST : NONE
DATA DIGEST : NONE
FIRSTBURSTLENGTH : 0
MAXBURSTLENGTH : 262144
MAXRECVDATASEGMENTLENGTH: initiator - 131072
target - 65536
LOGIN TIMEOUT : 15
AUTH TIMEOUT : 45
ACTIVE TIMEOUT : 5
IDLE TIMEOUT : 20
PING TIMEOUT : 5
*******************************************************************************
I think it's a bit strange that the first target
(iqn.1992-04.com.emc:ax.fcnpr062301759.a0) seems to ignore the idle
timeout setting.
Anyway, I can access data on the SAN without any problems, it's just
annoying with failed/connected messages filling up the log ;-)
Best regards
Søren
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
linux-iscsi-users mailing list
linux-iscsi-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/linux-iscsi-users
[IP Storage] [IETF] [Linux SCSI] [iSCSI Book] [Linux Resources] [Yosemite News] [Photo] [Home] [IETF Announcements] [IETF Discussion] [SCSI Hardware]