We can configure ALE server IP per AP group LEVEL in controller , I havent tried it before but worth trying this option and check the status.
NOTE: Please note that the views, opinions, and statements expressed are solely my own and are provided in my personal capacity. They do not represent, reflect, or bind the company in any manner.
------------------------------
Original Message:
Sent: Dec 19, 2025 05:47 AM
From: ssmith764
Subject: ALE server configured with one controller listing AP's not on the source controller
Hi, did you ever find an answer to this? I have a similar problem with a 4 controller cluster and 3800AP's. I only need the data from around 2000 of them so could configure RTLS settings in the system profiles of the ones I want but can only configure one AMON feed so will end up getting AMON data for all of the AP's in ALE. From the design guide - If the RTLS feed is enabled on the deployment, RSSI data is retrieved from the RTLS feed instead of AMON. Other context information is sourced from AMON
------------------------------
--------------------
Stewart Smith
ACMX, ACDX, ACCP, ACSA
--------------------
Original Message:
Sent: May 22, 2025 08:55 AM
From: D_Graham
Subject: ALE server configured with one controller listing AP's not on the source controller
Hi,
I'm rebuilding our ALE environment as it is way overloaded - 1 ALE server and ~ 7500 WAPS
The Plan is 1 ALE server for every 2 controllers but the issue is that the first server built, which is pointing at only 1 controller with ~800 APs, is pulling in info for ~ 3300 APs. There doesn't appear to be any logic to which APs, they aren't even all from the same cluster that the controller belongs to.
What we have is:
1 Mobility Conductor consisting of 2 servers ( DC1-WMM-01 and DC2-WMM-01)
All running 8.10.0.14 LSR
8 Mobility controllers configured in two clusters, 1 per data centre (DC1 + DC2)
DC1 datacentre (DC1-WMC-01, 02, 03, 04)
DC2 datacentre (DC2-WMC-01, 02, 03, 04)
All running 8.10.0.14 LSR
4 ALE servers, 2 per datacentre
DC1 datacentre (DC1-ALE-01 + 02)
DC2 datacentre (DC2-ALE-01 + 02)
All running version 3.2.0.0(4)
7540 WAPs
Currently DC2-ALE-01 is the original ALE server and has ALL the WAPs linked to it.
My plan was to configure 1 ALE server for every 2 Mobility Controllers.
I have configured one of the new ALE servers, DC1-ALE-02 with DC1-WMC-04 (controller) as it's source and enabled RTLS. I have also added DC1-ALE-02 to the MC under Configuration -> System -> More -> General -> MON Receiver
This all seems to work except rather than pull in the expected ~ 800 WAPs that are associated with APT-WMC-04, it has pulled in information for 3322 WAPs which from my checks are WAPs from all over the estate and not specific to any of the DC2 infrastructure.
The main goal is to apply the licenses to the controllers so that we can start using the Publisher/subscriber model but until i can sort the AP numbers in ALE that's impossible.
Follow on pop question:
WAPs move between controllers regularly to load balance - that's ok as numbers are generally small. BUT, in the event of a controller , or worse still datacentre failure, then the AP count on the remaining DC controllers will effectively double which will then mean the ALE server will see double the number of AP's compared to the license it holds.
Has anyone cracked this challenge (TAC suggested buying 2x the licenses but clearly that isn't a solution)