[Lustre-discuss] lctl ping of Pacemaker IP

Ms. Megan Larko dobsonunit at gmail.com
Sun Nov 4 21:48:38 PST 2012


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 know how to make the corosync alias IP accessible to
LNET for a successful lctl ping required for Lustre OSS nodes to
properly communicate with the MGS/MDS, I chose to point to the real
InfiniBand ib0 IP and coorsync align  that network address with the
system servinig the fibre channel multipath mgs/mdt disk.   In this
way the ost disks have one and only one mgsnode (no failover because
the IB0 address fails over).

This has been successful in my TCP test (an LSB-compliant service for
eth1).   I plan on implementing this week when the IB hardware comes

Thanks for your help.  I appreciate it.


More information about the lustre-discuss mailing list