Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-13790

socklnd: NID to interface mapping issues

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • Lustre 2.14.0
    • None
    • None
    • 3
    • 9223372036854775807

    Description

      Testing showed that NID to interface mapping was still wrong after LU-13566 landed. The following procedure was used to reproduce:

      # lnetctl lnet configure
# lnetctl net add --net tcp --if eth0,eth1,eth2
# lnetctl discover <MR peer NID>
# lnetctl ping <MR peer NID>

      Discovery would succeed, but first ping would fail as a NID on an interface other than the first would be picked to send out the ping and the mapping for the NID was wrong.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. LU-13828 failed to ping 192.168.56.110@tcp: Input/output error

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. LU-13566 socklnd: wrong NID to interface mapping

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            People

              ssmirnov Serguei Smirnov
              ssmirnov Serguei Smirnov
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: