On Mon, Sep 21, 2009 at 09:42:05AM +0200, Lars Ellenberg wrote:
> On Mon, Sep 21, 2009 at 11:44:50AM +1000, Oliver Hookins wrote:
> > Hi,
> >
> > Just wondering if it is possible to retrieve information somehow about the
> > status of the various communications links between nodes? For example, if
> > one node was unreachable via multicast on one interface, but still reachable
> > via multicast on a secondary interface would it be possible to retrieve this
> > information (aside from parsing the logs)?
>
> For the heartbeat comm layer:
>
> r...@barkeeper2-xen# cl_status
> Usage: cl_status <sub-command> [<options>] [<parameters>]
>
> Sub-commands:
> clientstatus <node-name> <client-id> [<timeout>]
> Show the status of heartbeat clients.
> hblinkstatus <node-name> <link-name>
> Show the status of a heartbeat link
> hbstatus
> Indicate if heartbeat is running on the local system.
> listhblinks <node-name>
> List the network interfaces used as hearbeat links.
> listnodes [<option>]
> List the nodes in the cluster.
> Options:
> -p list only 'ping' type nodes
> -n list only 'normal' type nodes
> nodestatus <node-name>
> List the node status.
> nodeweight <node-name>
> List the node weight.
> nodesite <node-name>
> List the node site.
> nodetype <node-name>
> List the nodes of a given type.
> rscstatus
> Show the status of cluster resources.
> hbparameter -p <parameter-name>
> Retrieve the value of a cluster parameter.
> As for the valid parameter names, please refer to the man page.
>
> r...@barkeeper2-xen:# cl_status hbstatus
> Heartbeat is running on this machine.
> r...@barkeeper2-xen:# cl_status listnodes
> barkeeper2-xen
> barkeeper1-xen
> r...@barkeeper2-xen:# cl_status listhblinks barkeeper1-xen
> br0
> eth3
> ethx
> r...@barkeeper2-xen:# cl_status hblinkstatus barkeeper1-xen br0
> up
> r...@barkeeper2-xen:# cl_status hblinkstatus barkeeper1-xen eth3
> up
> r...@barkeeper2-xen:# cl_status hblinkstatus barkeeper1-xen ethx
> up
> r...@barkeeper2-xen:# cl_status hblinkstatus barkeeper2-xen ethx
> up
>
> ...
>
> For OpenAIS / corosync: no idea,
> but I would expect there is something similar available.
> If there is not such thing yet,
> now is about time to make it available ;)
>
> Anyone?
Hm. apparently, openais-cfgtool.
who had guessed that! ;)
# openais-cfgtool -s
Printing ring status.
RING ID 0
id = 10.20.30.40
status = ring 0 active with no faults
RING ID 1
id = 10.234.0.1
status = ring 1 active with no faults
--
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com
DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
