Dear All, We are using RHEL 6.6 and iscsi-initiator-utils-6.2.0.873-13 in our test environment and have modified following timeout and retry values in iscsi.conf file:
node.session.timeo.replacement_timeout = 30(previously 180 by default) node.session.initial_login_retry_max = 1(previously 8 by default) node.session.err_timeo.abort_timeout = 5(previously 15 by default) node.session.err_timeo.lu_reset_timeout = 10(previously 30 by default) node.session.err_timeo.tgt_reset_timeout = 10(previously 30 by default) As per our understanding these changes would be effective in iscsiadm commands after restarting iscsi daemon, when we restart iscsi daemon above changes are not effective. But, when we explicitly execute the discovery command (iscsiadm -m discovery --type sendtargets -p X.X.X.X), these setting become effective. Following are my queries regarding executing discovery command after changing values in iscsi.conf file: 1> As iscsi database(/var/lib/iscsi/nodes) is maintained at initiator side, only restarting daemon should reflect the changes in iscsi database file(/var/lib/iscsi/nodes). Is this understanding correct? If not, do we always need to execute discovery command after changing the value in iscsi.conf file and why [after restarting iscsi daemon] ? 2> Can't we avoid executing discovery command for making the iscsi.conf changes effective [Is there some other possible way] ? Thanks, Manish Singh -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
