From 6fb97f06b9645e4a7f16566d11a1b92da5428e8f Mon Sep 17 00:00:00 2001
From: James Holgate <130981049+JamesHazelcast@users.noreply.github.com>
Date: Thu, 27 Jun 2024 12:20:18 +0100
Subject: [PATCH] Add note to adv network configuration docs w.r.t endpoint
 overlaps (#1147)

This addition is made following an incident that raised the topic for
discussion.

See: https://hazelcast.atlassian.net/browse/SUP-432

---------

Co-authored-by: rebekah-lawrence <142301480+rebekah-lawrence@users.noreply.github.com>
---
 docs/modules/clusters/pages/network-configuration.adoc | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/docs/modules/clusters/pages/network-configuration.adoc b/docs/modules/clusters/pages/network-configuration.adoc
index 793f85854..3b3443509 100644
--- a/docs/modules/clusters/pages/network-configuration.adoc
+++ b/docs/modules/clusters/pages/network-configuration.adoc
@@ -827,6 +827,12 @@ settings of outgoing connections (from the members of a source cluster to the ta
 WAN cluster members) or to establish server sockets on which a target WAN member can
 listen for the incoming connections from the source cluster.
 
+NOTE: When using the advanced network configuration and defining separate endpoints for
+`WAN` and `MEMBER` protocols, you must ensure that endpoint ranges do not overlap.
+Each protocol must be configured with unique endpoints that are not used in other protocols,
+otherwise WAN replication can cause the cluster to
+become unstable if IPs are reused.
+
 === Server Socket Endpoint Configuration
 
 The server socket endpoint configuration is common for all protocols. The elements