His answer was from 2019, things have possibly changed since then.
For instance, the AP discovery flow was changed with 8.4 and then tuned again in 8.5.
Original Message:
Sent: Oct 23, 2024 04:20 AM
From: Mosher
Subject: DHCP option 43
Hi
Did a test in my lab and added a few LMS IP's to the AP system profile.
Bootet the AP and stopped it at boot, and voila,
previous_lms=10.11.157.27
cfg_lms=10.11.157.27
num_total_bootstrap=8
cfg_blms=10.11.157.254
Looks like Colin was wrong on this one :D
Roar
------------------------------
------------------------------
| ACMP | ACSP | ACCP | ACEP | ACNT |
-Just your regular airhead-
------------------------------
Original Message:
Sent: Oct 22, 2024 09:56 AM
From: Mosher
Subject: DHCP option 43
Hi
Customer has one WLC in each of their datacenters.
To maximize bandwidth and have some redundancy, half of the AP's are connected to DC1, the other half to DC2, with LMS failover.
As they are using DHCP options for AP's to discover the WLC, option 43, this discovery will point to WLC1 at the moment. As i understand, LMS is not stored in the AP config, thus the AP's will not be able to find any WLC if WLC1 is down and boots.
Meaning if the AP's failover (apmove) to WLC2, and is booted, they will be down.
Looks like the Windows dhcp server can push several IP's under option 43, but will the Aruba AP understand this?
The 2 WLC's do not have any connection between each other, no HA etc. They just connect to a Mobility Master/Conducter in a different place for config etc.
Any clever way to get around this?
Roar
------------------------------
------------------------------
| ACMP | ACSP | ACCP | ACEP | ACNT |
-Just your regular airhead-
------------------------------
------------------------------