summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSander Klein <github@roedie.nl>2022-09-02 21:11:48 +0200
committerSander Klein <github@roedie.nl>2022-09-02 21:11:48 +0200
commit6a0d06565fc9af70b5d73326a200013e372a9f20 (patch)
tree50aea7ac82f6e87e48500172e1fe91b21da9d3ad
parent1e13aef910d4cd4a5936fe9d483182adddff0e67 (diff)
downloadvyos-documentation-6a0d06565fc9af70b5d73326a200013e372a9f20.tar.gz
vyos-documentation-6a0d06565fc9af70b5d73326a200013e372a9f20.zip
T4665: Keepalived: Docs for using the same VRID
Using the same VRID on the same interface is allowed when they are different address families.
-rw-r--r--docs/configuration/highavailability/index.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/configuration/highavailability/index.rst b/docs/configuration/highavailability/index.rst
index 4a279213..29bb97be 100644
--- a/docs/configuration/highavailability/index.rst
+++ b/docs/configuration/highavailability/index.rst
@@ -18,9 +18,9 @@ VRRP keepalive packets use multicast, and VRRP setups are limited to a single
datalink layer segment. You can setup multiple VRRP groups
(also called virtual routers). Virtual routers are identified by a
VRID (Virtual Router IDentifier). If you setup multiple groups on the same
-interface, their VRIDs must be unique, but it's possible (even if not
-recommended for readability reasons) to use duplicate VRIDs on different
-interfaces.
+interface, their VRIDs must be unique if they use the same address family,
+but it's possible (even if not recommended for readability reasons) to use
+duplicate VRIDs on different interfaces.
Basic setup
-----------