On Thu, Mar 17, 2022 at 4:16 PM Ulrich Windl <
ulrich.wi...@rz.uni-regensburg.de> wrote:
> Hi!
>
> I had the idea to display the status of a cluster node on the 14-character
> LCD display of a Dell PowerEdge server; preferably displaying the hostname
> at least partially, too ;-)
>
> Now, what
Thank you for the idea about a bug in resource script.
...
NETWORK=`$IP2UTIL route list dev $INTERFACE scope link $PROTO match
$ipaddress|grep -m 1 -o '^[^ ]*'`
...
$NETWORK was surprisingly empty when a bug occurs, something wrong was with
$PROTO variable. Command above returns the correct
Hi!
I had the idea to display the status of a cluster node on the 14-character LCD
display of a Dell PowerEdge server; preferably displaying the hostname at least
partially, too ;-)
Now, what would you display, and how would you display it?
(Actually I already have something (e.g.
On 17.03.2022 14:14, ZZ Wave wrote:
>> Define "network connectivity to node2".
>
> pacemaker instances can reach each other, I think.
This is called split brain, the only way to resolve it is fencing.
> In case of connectivity
> loss (turn off network interface manually, disconnect eth cable
> Define "network connectivity to node2".
pacemaker instances can reach each other, I think. In case of connectivity
loss (turn off network interface manually, disconnect eth cable etc), it
should turn off virtsrc and then virtip on active node, turn virtip on and
then virtsrc on second node, and
>>> ZZ Wave schrieb am 16.03.2022 um 10:24 in Nachricht
:
> Hello. I'm trying to implement floating IP with pacemaker but I can't
> get IPsrcaddr to work correctly. I want a following thing - floating
> IP and its route SRC is started on node1. If node1 loses network
> connectivity to node2,
