Greetings,
My present solution for my corosync/pacemaker control of my Lustre
filesystem availability was to make a Linux Standards Base (LSB) Sys V
init script for my IB0 service and then I could use the corosync
primitive to control the IB network (and therefore the MGS). Being
that I did not
On Fri, Nov 02, 2012 at 12:04:02AM -0400, Ms. Megan Larko wrote:
..
What steps should I take to generate a successful lctl ping a.b.c.d?
There must be a LNet instance running over SOCKLND on a.b.c.d.
- Isaac
___
Lustre-discuss mailing list
Greetings!
I am working with Lustre-2.1.2 on RHEL 6.2. First I configured it
using the standard defaults over TCP/IP. Everything worked very
nicely usnig a real, static --mgsnode=a.b.c.x value which was the
actual IP of the MGS/MDS system1 node.
I am now trying to integrate it with
Megan,
lnet pings aren't the same as tcpip/udp pings. An lnet ping 'lctl ping' would
need to touch an active lnet instance on the target address. I don't think you
can bind lnet to a pacemaker virtual IP but I'll let someone smarter than me on
this list confirm or correct me.
In any event an
