The L3 redundancy described pertains only to Mobility Conductor (formerly known as Mobility Master).
The remainder of the question likely pertains to MD(controller) redundancy, which is a strategic/design question.
One could have a single MD in each location, if L2 clustering can be used, or simple VRRP. If L2 is not available, static methods could be used to direct APs to either location (again, dependent on the underlying network design)
The Design guidelines and AOS User guides provide documentation and examples.
Hope this is helpful.
------------------------------
Shawn Adams
------------------------------
Original Message:
Sent: Sep 11, 2024 03:47 AM
From: mohamed
Subject: setup VRRP between 2 conductors exist at different Branches
Thanks for you're support.
Layer-3 Redundancy must have a mobility master to be configured?
Original Message:
Sent: Sep 11, 2024 03:31 AM
From: sadams
Subject: setup VRRP between 2 conductors exist at different Branches
If the 2 Mobility Conductors share a L2 network, one could use one VRRP instance shared, with MDs connecting to that VRRP address.
If there is no L2 between the sites, an MC at each site could use L3 redundancy as described in the AOS User Guide 8.2 and above.
Refer to the AOS User Guide "Configuring Secondary Mobility Conductor Using Layer-3 Redundancy".
also see:
https://community.arubanetworks.com/community-home/digestviewer/viewthread?MID=17533
https://higherlogicdownload.s3.amazonaws.com/HPE/MigratedAttachments/89358BF8-F155-4B2E-859A-A7537A25C8FE-1-Campus%20WLAN%20Redundancy%20VRD.pdf
------------------------------
Shawn Adams
Original Message:
Sent: Sep 10, 2024 07:50 AM
From: mohamed
Subject: setup VRRP between 2 conductors exist at different Branches
Hi All
I hope a goodday for all
I have 2 branches connected to each other using ISP (MPLS) and every branch have a mobility conductor.
is it available to create VRRP between the 2 conductros to work as Active/Standby?