On Mon, Aug 20, 2007 at 08:23:09PM +0100, Wojciech Turek wrote: > eth0 Link encap:Ethernet HWaddr 00:13:72:FB:09:66 > inet addr:10.142.4.25 Bcast:10.142.4.255 Mask:255.255.255.0 > inet6 addr: fe80::213:72ff:fefb:966/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:429602 errors:0 dropped:0 overruns:0 frame:0 > TX packets:286189 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:42096900 (40.1 MiB) TX bytes:27083024 (25.8 MiB) > Interrupt:169 Memory:f8000000-f8011100 > > eth1 Link encap:Ethernet HWaddr 00:13:72:FB:09:68 > inet addr:10.143.4.25 Bcast:10.143.255.255 Mask:255.255.0.0 > inet6 addr: fe80::213:72ff:fefb:968/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:181050667 errors:0 dropped:0 overruns:0 frame:0 > TX packets:167463035 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:213247025573 (198.6 GiB) TX bytes:215923168460 > (201.0 GiB) > Interrupt:169 Memory:f4000000-f4011100
The traffic really went through eth1, as can be seen from "RX bytes" and "TX bytes" above. > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:240 errors:0 dropped:0 overruns:0 frame:0 > TX packets:240 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:20520 (20.0 KiB) TX bytes:20520 (20.0 KiB) > > >What does "dmesg | grep 'Added.LNI'" say after lnet module is loaded? > > dmesg | grep 'Added.LNI' > Lustre: Added LNI [EMAIL PROTECTED] [8/256] This looks weird. Can you please run "lctl --net tcp print_interfaces" and give me the outputs? Can you also unload all lustre/lnet modules, and load lnet separately by running "modprobe lnet networks='tcp(eth1)' config_on_load=1"? Does it change anything? Isaac _______________________________________________ Lustre-discuss mailing list [email protected] https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
