Just to close the loop on this issue, discussions with Redhat have
confirmed that this behavior is as designed, that all membership
changes must first be realized by the Corosync layer. So the full
trajectory of a STONITH action in response to, for example, a failed
stop operation looks like:
crm
FYI, I stumbled across a report of a suspected kernel issue breaking
iptables clusterip inside containers:
https://github.com/lxc/lxd/issues/2773
ocf:heartbeat:IPaddr2 uses clusterip when cloned. I'm guessing no one's
tried something like that yet, but this is a note of caution to anyone
thin
On 04/26/2017 02:45 AM, Bratislav Petkovic wrote:
> Tahank you,
>
>
>
> We use the Cisco Nexus 7000 switches, they support Multicast MAC.
>
> It is possible that something is not configured correctly.
>
> In this environment working IBM PowerHA SystemMirror 7.1 (use Multicast)
> without prob
Tahank you,
We use the Cisco Nexus 7000 switches, they support Multicast MAC.
It is possible that something is not configured correctly.
In this environment working IBM PowerHA SystemMirror 7.1 (use Multicast)
without problems.
Regards,
Bratislav
ODRICANJE OD ODGOVORNOSTI
Informacija u ovom
