# SUSE HAE - standby node disconnect from network

**URL:** <https://forums.suse.com/t/suse-hae-standby-node-disconnect-from-network/23101>\
**Category:** SLES High Availability Extension\
**Created:** [September 17, 2012, 5:54am UTC](https://forums.suse.com/t/suse-hae-standby-node-disconnect-from-network/23101 "2012-09-17T05:54:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![supphakorn](https://avatars.discourse-cdn.com/v4/letter/s/f04885/32.png) [@supphakorn](https://forums.suse.com/u/supphakorn)\
**Post date:** [September 17, 2012, 5:54am UTC](https://forums.suse.com/t/suse-hae-standby-node-disconnect-from-network/23101/1 "2012-09-17T05:54:38Z")

</div>

My environment has 2 nodes. I run all resources at node 1. When I disconnect all network at node 2 (standby), it active resource at node 2 (standby) and node1 still active resource. when I plug network node 2 back to network, cluster status show multiple running and restart all resource.

Do you have solution for this environment

---

<div class="post-metadata">

**Author:** ![Jens-U](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jens-U](https://forums.suse.com/u/Jens-U)\
**Post date:** [September 17, 2012, 4:15pm UTC](https://forums.suse.com/t/suse-hae-standby-node-disconnect-from-network/23101/2 "2012-09-17T16:15:33Z")

</div>

Hi supphakorn,

I’m not sure I fully understand what you’re trying to achieve: When you disconnect all networking at node 2, it’s not in standby, but offline.

Independent of standby/offline, it’s a matter of resource stickiness to avoid redistribution of resources after bringing up a new active cluster node.

OTOH, you say that you see resources running multiple times after reconnecting the second node… are we maybe talking about a split-brain situation here?

- two nodes active, all resources active on node 1
- disconnect node 2 from networking _without putting node 2 into standby first_
- node 2 does no longer see node 1 (“split brain”) and so decides it must activate all resources on node 2. But on node 1, all these resources are active, too, at the same time.
- once you reconnect node 2 to the network, you can see that resources are active on node 2, too…

This is a typical problem with two-node clusters and needs to be circumvented. There are many ways to skin that cat, the proper search terms are “two-node clusters” and “split brain”…

Regards,  
Jens

---

<div class="post-metadata">

**Author:** ![LarsMB](https://avatars.discourse-cdn.com/v4/letter/l/bcef8e/32.png) [@LarsMB](https://forums.suse.com/u/LarsMB)\
**Post date:** [September 25, 2012, 11:53pm UTC](https://forums.suse.com/t/suse-hae-standby-node-disconnect-from-network/23101/3 "2012-09-25T23:53:12Z")

</div>

Hi there,

I think you have set no-quorum-policy=ignore (so that a two node cluster basically pretends to have quorum even with one node), but you have explicitly disabled IO fencing/STONITH. You need to re-enable and configure it properly for your environment to avoid the split brain and concurrency violation.

Best,  
Lars