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

Bad ethernet network after LNet is loaded

XMLWordPrintable

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

      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).

        1. bash-xv-ksocklnd-config
          35 kB
        2. bash-xv-ksocklnd-config-ignore_ipv6_link_local_addr_no_flush
          23 kB
        3. ksocklnd-config
          12 kB
        4. ksocklnd-config-1
          13 kB
        5. ksocklnd-config-ignore_ipv6_link_local_addr
          13 kB
        6. ksocklnd-config-ignore_ipv6_link_local_addr_no_flush
          13 kB
        7. ksocklnd-config-ignore_ipv6_link_local_addr_no_flush_local_route
          14 kB

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

              Created:
              Updated:
              Resolved: