Dear list,
There are two Ethernet Cards on our login node, one outside
connection(202.122.*.*), one for inside connection to other servers. The
problem is Lustre sometimes confuse with configuration.
[root at lxslc09 ~]# netstat -an | grep 988
tcp 0 0 0.0.0.0:988 0.0.0.0:*
LISTEN
tcp 0 0 202.122.**.**:1022 192.168.50.32:988
ESTABLISHED
tcp 0 0 202.122.**.**:1023 192.168.50.32:988
ESTABLISHED
tcp 0 0 202.122.**.**:1021 192.168.50.32:988
ESTABLISHED
tcp 0 1 192.168.51.131:1023 192.168.50.34:988
SYN_SENT
tcp 0 1 192.168.51.131:1023 192.168.50.40:988
SYN_SENT
tcp 0 0 192.168.51.131:1023 192.168.50.33:988
ESTABLISHED
tcp 0 0 192.168.51.131:1022 192.168.50.33:988
ESTABLISHED
tcp 0 0 192.168.51.131:1021 192.168.50.33:988
ESTABLISHED
It connect mds with outside NIC, while oss with inside NIC. How to bind Lustre
on NIC(192.168.51.131),which is eth2 on this manchine. I have tried to add
options lnet network=tcp(eth2) to /etc/modprobe.conf
however, it doesn''t work.
--------------
Lu Wang
2008-12-15
On Mon, Dec 15, 2008 at 10:01:08AM +0800, Lu Wang wrote:> Dear list, > There are two Ethernet Cards on our login node, one outside connection(202.122.*.*), one for inside connection to other servers. The problem is Lustre sometimes confuse with configuration. > [root at lxslc09 ~]# netstat -an | grep 988 > tcp 0 0 0.0.0.0:988 0.0.0.0:* LISTEN > tcp 0 0 202.122.**.**:1022 192.168.50.32:988 ESTABLISHED > tcp 0 0 202.122.**.**:1023 192.168.50.32:988 ESTABLISHED > tcp 0 0 202.122.**.**:1021 192.168.50.32:988 ESTABLISHED > tcp 0 1 192.168.51.131:1023 192.168.50.34:988 SYN_SENT > tcp 0 1 192.168.51.131:1023 192.168.50.40:988 SYN_SENT > tcp 0 0 192.168.51.131:1023 192.168.50.33:988 ESTABLISHED > tcp 0 0 192.168.51.131:1022 192.168.50.33:988 ESTABLISHED > tcp 0 0 192.168.51.131:1021 192.168.50.33:988 ESTABLISHED > It connect mds with outside NIC, while oss with inside NIC. How to bind Lustre on NIC(192.168.51.131),which is eth2 on this manchine. I have tried to add > options lnet network=tcp(eth2) to /etc/modprobe.conf > however, it doesn''t work.It''s your routing table which ultimately decides the outgoing interface to use. If a routing entry says to reach your MDS IP your "outside" NIC must be used, Lustre can''t do anything about it. Thanks, Isaac