If you want redundancy for provisioning then configure a VRRP instance on the controllers and use that VIP as the provisioning target. If you are wanting redundancy post-provisioning then either use a cluster (which would require the addition of an MCR) or configure LMS/B-LMS in the AP system profile.
------------------------------
Carson Hulcher, ACEX#110
------------------------------
Original Message:
Sent: Jul 31, 2024 10:11 AM
From: Ronin101
Subject: Option 43 for controller discovery
In nutshell, without MM, is it possible to pass on 2 x IPs in option 43 to APs, so that if AP is not able to connect to one controller due to firmware mismatch, they should try and connect to second controller. Is it possible?
Original Message:
Sent: Jul 31, 2024 07:38 AM
From: Ronin101
Subject: Option 43 for controller discovery
Dear Experts,
Need your advice for below setup. Customer is running 2x7210 controller running version 8.7 without Mobility Master. They have 3 locations with 50 APs each that are terminated on these controllers. They want to replace location 1 APs with newer 6xx APs that support 8.11. So we have to break the redundancy (VRRP etc) between these controllers. Is there anyway to provide multiple controller ip through option 43 so that when the AP tries the first controller, there will be version mismatch so it will try the other controller?