This is a page tracks issues that we run into while testing the Multi-Rail Feature
Problem List
with 17 interfaces trying to discover on the 17th interface returns an error "no route to host". This is an intermittent issue. Attempting to reproduce
With 17 interface discovered "show peer" hangs
looks like it's hanging in the ioctl call.
"lnetctl discover" command hangs with discovery off. This happened once, so an intermittent issue. Will try to reproduce.
"lnetctl discover" discovers the peer even with discovery off.
Doug: I configured a Parallels VM with 16 interfaces (won't let me do 17 as 16 is a limit). When I "lctl network configure" with no YAML or module parameters, I get this error from ksocklnd: "
Mar 7 14:01:16 centos-7 kernel: LNet: 5111:0:(socklnd.c:2652:ksocknal_enumerate_interfaces()) Ignoring interface virbr0 (too many interfaces)".