[lustre-discuss] Issue with lnet showing network down lustre 2.5.3

[Ben Evans]

Trying the obvious, did you run lustre_rmmod before doing the upgrade?

Did you happen to have a shell running that was in the /proc/sys/lnet directory when the modules unloaded?  (that's a fun one to encounter)

Check /etc/modprobe.d for your "options lnet" line and make sure it's correct.

Are the lnet modules actually loaded?

-Ben Evans

-----Original Message-----
From: lustre-discuss [mailto:lustre-discuss-bounces at lists.lustre.org] On Behalf Of Kurt Strosahl
Sent: Thursday, May 28, 2015 9:27 AM
To: lustre-discuss at lists.lustre.org
Subject: [lustre-discuss] Issue with lnet showing network down lustre 2.5.3

Good Morning,

   I've encountered an unusual issue when upgrading a lustre client from 1.8.7 to 2.5.3.  The client installed, but when I start the lnet service it does not come up (all the modules load).  When I run a service lnet status it shows the following error:

sudo service lnet status
cat: /proc/sys/lnet/routes: No such file or directory loaded

The box has a qdr ib card and a 10 gig ethernet card.  It is running centos 6.2 with the lustre client compiled on the box.

~> rpm -qa | grep lustre
lustre-iokit-2.5.3-2.6.32_220.7.1.el6.x86_64.x86_64
lustre-client-2.5.3-2.6.32_220.7.1.el6.x86_64.x86_64
lustre-client-tests-2.5.3-2.6.32_220.7.1.el6.x86_64.x86_64
lustre-client-modules-2.5.3-2.6.32_220.7.1.el6.x86_64.x86_64
lustre-client-source-2.5.3-2.6.32_220.7.1.el6.x86_64.x86_64
~> uname -r
2.6.32-220.7.1.el6.x86_64

w/r,
Kurt
_______________________________________________
lustre-discuss mailing list
lustre-discuss at lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org