Hello Manish, No restarting the iSCSI daemon does not update the node files. There are iscsiadm commands that will do so on the fly.
This is taken from the Dell Tech Report TR1062. Configuring iSCSI and MPIO for RHEL v5.x. Which is 99% the same for RHEL v6.x. A search for Dell TR1062 will give you a link to the PDF. For example: This creates the interface file for Ethernet port2. # iscsiadm --mode iface --interface eth2 -o update --name iface.net_ifacename -–value=eth2 #iscsiadm --mode iface --interface eth2 -o update --name iface.net_ifacename -–value=eth2 This updates the option in the interface file for Ethernet2 so that MPIO will work properly The way you found, editing the /etc/iscsi/iscsid.conf then re-running discovery will push out the changes to all the node files at once. So both techniques have their value. Regards, Don On Tue, Aug 18, 2015 at 8:10 AM, Manish Singh <[email protected]> wrote: > Dear All, > > We are using RHEL 6.6 and iscsi-initiator-utils-6.2.0.873-13 in our test > environment. > > we have modified following iscsi timeout and retry values in iscsi.conf, > > node.session.timeo.replacement_timeout = 30 (previously 180) > > 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, the above changes should get effective for > iscsiadm commands just after restarting iscsi daemon. > > But, these are not getting effective until we execute the discovery > command( iscsiadm -m discovery --type sendtargets -p x.x.x.x) after > restarting iscsi daemon. > > > Can someone please respond to my following queries: > > 1> As iscsi database(/var/lib/iscsi/nodes) resides at initiator side, > restarting iscsi daemon should update the database(/var/lib/iscsi/nodes). > > Is the above understanding correct? > > If not, is it always required to explicitly execute discovery command to > make changes in iscsi.conf become effective ? > > 2> Is it possible to achieve the same without executing discovery command > [Is there any other possible way] ? > > > > > > -- > 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. > -- 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.
