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

Bad ethernet network after LNet is loaded

Details

    • Bug
    • Resolution: Fixed
    • Major
    • Lustre 2.16.0, Lustre 2.17.0
    • Lustre 2.16.0
    • None
    • 3
    • 9223372036854775807

    Description

      In my test env (eth0 for ssh and eth1 for LNet), when LNet is loaded, replying to ping becomes impossible.

      After first analysis, ksocklnd-config seems to be the culprit (in commit v2_15_57-117-g7f60b2b558).

      Attachments

        Issue Links

          Activity

            [LU-18199] Bad ethernet network after LNet is loaded
            pjones Peter Jones made changes -
            Fix Version/s New: Lustre 2.17.0 [ 16192 ]
            ssmirnov Serguei Smirnov made changes -
            scherementsev Sergey Cheremencev made changes -
            scherementsev Sergey Cheremencev made changes -
            Attachment Original: ksocklnd-config-ignore_ipv6_link_local_addr_no_flush-1 [ 56618 ]
            scherementsev Sergey Cheremencev made changes -
            Attachment New: ksocklnd-config-ignore_ipv6_link_local_addr_no_flush-1 [ 56618 ]
            ssmirnov Serguei Smirnov made changes -
            scherementsev Sergey Cheremencev made changes -
            Attachment New: bash-xv-ksocklnd-config [ 56530 ]
            ssmirnov Serguei Smirnov made changes -
            pjones Peter Jones made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            pjones Peter Jones made changes -
            Labels Original: npy

            People

              ssmirnov Serguei Smirnov
              cbordage Cyril Bordage
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: