Uploaded image for project: 'Product Technical Learning'
  1. Product Technical Learning
  2. PTL-8052

RH436-9: iscsi timeouts - please expand

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Can't Do
    • Icon: Minor Minor
    • RH436 - RHEL 6 NEXT
    • RH436 - RHEL 6.2 2
    • RH436
    • None
    • 4

      URL:
      Reporter RHNID:
      Section: -
      Language:
      Workaround:

      Description: Please expand content discussing iscsi timeout parameters in the iscid.conf file.

      There is a reference to the file and such settings in the Unit 2 iscsi initiator content. It is just a short list of titles, not any description of when such timeouts should be modified.
      Later in the Unit 4, Configuring Multipath performance checklist we change ALL timeouts to 2 seconds. Do we really need to be changing ALL timeouts? Is there a more appropriate subset of timeouts to lower? Which are lower for production multipath, which are being lowered for classroom testing?

      As an IG note, point out that changing the timeouts requires that the client not only logout of the iscsi session but also delete and then discover again since these settings are inherited at discovery. When students miss the step and go back later to change the timeouts, they do not pick up the subtle parenthesis about "(the ones that will be propagated to newly discovered targets)"

              wboessen Wander Boessenkool (Inactive)
              lauber Susan Lauber
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: