[LU-12729] lnet_selftest not work in multi-net and multi-rail client Created: 05/Sep/19  Updated: 16/Oct/20  Resolved: 12/Feb/20

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.12.2
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Mahmoud Hanafi Assignee: Serguei Smirnov
Resolution: Fixed Votes: 0
Labels: None

Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

A multi-rail client can't setup lnet selftest to a router with multiple interface like this:

# lctl list_nids 10.151.26.148@o2ib 10.151.25.170@o2ib 10.141.26.148@o2ib417 10.141.25.170@o2ib417 

Here is what peer show looks like

    - primary nid: 10.151.26.148@o2ib
      Multi-Rail: True
      peer ni:
        - nid: 10.141.26.148@o2ib417
          state: up
        - nid: 10.141.25.170@o2ib417
          state: NA
        - nid: 10.151.26.148@o2ib
          state: NA
        - nid: 10.151.25.170@o2ib
          state: NA
~ # modprobe lnet_selftest
~ # export LST_SESSION=99
~ # lst new_session test
SESSION: test FEATURES: 1 TIMEOUT: 300 FORCE: No
nbp16-srv1 ~ # lst add_group servers 10.151.26.148@o2ib                                        
create session RPC failed on 12345-10.151.26.148@o2ib: Unknown error -110
No nodes added successfully, deleting group servers
Group is deleted


 Comments   
Comment by Amir Shehata (Inactive) [ 06/Sep/19 ]

Try running a discovery before running the test.

lnetctl discover <nid> 

Run the command from one of the nodes you're running the test on to the other nodes.

This is a known limitation of selftest at the moment.

Comment by Mahmoud Hanafi [ 10/Oct/19 ]

Please close

Comment by Peter Jones [ 10/Oct/19 ]

ok - thanks

Comment by Mahmoud Hanafi [ 21/Nov/19 ]

Running lnetctl discover <nid> doesn't help. It still doesn't work.

Comment by Mahmoud Hanafi [ 12/Feb/20 ]

please close.

Comment by Peter Jones [ 12/Feb/20 ]

ok - thanks

Generated at Sat Feb 10 02:55:08 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.