Hi Bob,
The general recommendation is to use role as dual wherever possible.
Do you mean the AP never comes up if Local 1 is down & AP reboots as master keeps ignoring request from the AP ?
I am summarizing the issue as per my understanding. Please correct me in case I am incorrect at any point
1. Lets assume there is one Master & 2 locals
Master 10.1.1.1
Local 1: 10.1.1.2
Local 2: 10.1.1.3
HA profile Local 1:
10.1.1.2 role active
10.1.1.1 role standby
HA profile 2:
10.1.1.3 role active
10.1.1.1 role standby
AP system profile 1:
LMS: 10.1.1.2
Bkup LMS: 10.1.1.1
AP system profile 2:
LMS: 10.1.1.3
Bkup LMS: 10.1.1.1
If we consider ap's on Local 1 & following sequence of events occurs:
1. AP's are up on Local 1
Their standby tunnels are on Master.
2. Local 1 goes down.
AP's failover to Master controller.
3. Now one of these AP's (which got failed over successfully) reboots (L1 is still down), Master ignores the Hello received from the AP.
Please let me know if the issue is summarized correctly.
What is the master discovery method being used ?
Ideally master will ignore the request from AP in case the LMS IP in AP system profile is pointing to Master rather than local.
In that case master role is configured as standby & we are trying to terminate AP's on master. So, it will ignore the request from AP & legacy mechanism of lms/backup LMS will be initiated.