Bug 690065

Summary: Insufficient explanation of how to configure iSCSI target (replacement_timeout, etc.)
Product: Red Hat Enterprise Linux 5 Reporter: Satoru SATOH <ssato>
Component: Online_Storage_Reconfiguration_GuideAssignee: Jacquelynn East <jeast>
Status: CLOSED CURRENTRELEASE QA Contact: ecs-bugs
Severity: high Docs Contact:
Priority: unspecified    
Version: 5.8CC: mchristi, rlandman
Target Milestone: rcKeywords: Documentation
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-29 13:36:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Deadline: 2011-10-24   

Description Satoru SATOH 2011-03-23 08:59:06 UTC 
Description of problem: AFAIK, to change the configuration as instructed at "16.2.1. NOP-Out Interval/Timeout" and "16.2.2. replacement_timeout" are not 
effective for iSCSI targets already logged in or discovered at initiator side.

The file /etc/iscsi/iscsid.conf just provides an initial default configurations
for new iSCSI targets and to modify /etc/iscsi/iscsid.conf does not work 
for iSCSI targets already logged in or discovered once, I guess.

I'm not sure but I guess that correct way to change configurations are a or b
(b looks better):

a. modify saved configs under /var/lib/iscsi/send_targets and/or (?)
   /var/lib/iscsi/nodes and restart iscsi service

b. run iscsiadm to update configuration values explicitly such like:

   iscsiadm -m node -T $target_name -p $target_ip:$port -o update -n \
   node.session.timeo.replacement_timeout -v $timeout_value


Also it might be better that there is a note explains how to get the currenct configuration of iSCSI targets with using iscsiadm, I think.


Version-Release number of selected component (if applicable): The latest?
Comment 8 Mike Christie 2011-10-27 03:48:50 UTC 
This:

iscsiadm -m node -T $target_name -p $target_ip:$port  -o show -n \
node.session.timeo.replacement_timeout -v $timeout_value

should be:

iscsiadm -m node -T $target_name -p $target_ip:$port  -o update -n \
node.session.timeo.replacement_timeout -v $timeout_value

so update instead of show.

I would write something like

The iSCSI tools do not use the iscsid.conf settings for portals that have already been discovered and logged into. If you want to modify the settings of portal that you have already discovered and setup run:

iscsiadm -m node -T $target_name -p $target_ip:$port  -o update -n \
node.session.timeo.replacement_timeout -v $timeout_value

That will modify the portal's record so next time the iscsi tools login that value will be used.

You cannot modify the value on a running session. For the value to be used you must run the iscsiadm logout command on that session then log back in or restart the iscsi service.

If you would like the value to be the new default for all newly discovered portals then set the value in iscsid.conf. Next time the iscsiadm discovery command is run and portals are found the new value will be used.