Description of problem: ACTIVE TIMEOUT is not mentioned in /etc/iscsi.conf file and man page for /etc/iscsi.conf. But is displayed with iscsi-ls -c. Version-Release number of selected component (if applicable): kernel-2.4.20-8 How reproducible: Always Steps to Reproduce: 1. Configure a target (JBOD) on MDS 9216 2. Configure the DiscoveryAddress on the linux host and start the driver 3. Execute iscsi-ls -c and details of ACTIVE TIMEOUT is shown. Actual results: Executing iscsi-ls -c shows details of ACTIVE TIMEOUT. man pages and /etc/iscsi.conf does not mention anything about Active Timeout. Expected results: Either man pages and /etc/iscsi.conf should mention details about Active timeout or if it is not being used, it should be removed from the code and should not be displayed in iscsi-ls -c Additional info: The output of iscsi-ls -c looks like follows: ******************************************************************************* [root@linux-2 root]# iscsi-ls -c ******************************************************************************* SFNet iSCSI Driver Version ... 3.6.2 (27-Sep-2004 ) ******************************************************************************* TARGET NAME : iqn.2004-04.com.cisco.cnitin-jbod-567c TARGET ALIAS : HOST NO : 2 BUS NO : 0 TARGET ID : 4 TARGET ADDRESS : 10.1.1.80:3260 SESSION STATUS : ESTABLISHED AT Thu Apr 28 19:45:32 2005 NO. OF PORTALS : 1 PORTAL ADDRESS 1 : 10.1.1.80:3260,12416 SESSION ID : ISID 00023d000001 TSID 3080 TARGET CONFIGURATION KEYS : ------------------------- INITIAL R2T : No IMMEDIATE DATA : Yes HEADERDIGEST : NONE DATA DIGEST : NONE FIRSTBURSTLENGTH : 65536 MAXBURSTLENGTH : 262144 MAXRECVDATASEGMENTLENGTH: initiator - 131072 target - 1344 LOGIN TIMEOUT : 10 AUTH TIMEOUT : 30 ACTIVE TIMEOUT : 5 IDLE TIMEOUT : 10 PING TIMEOUT : 3 *******************************************************************************
This bug has been filed on Sourceforge and has been closed there: [ 1110710 ] iscsi-ls -c shows Active Timeout without any mention in docs
Verified documentation change upstream
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2005-548.html