el 01-06-2025 01:49 PM
Hello: We have a Cisco ME-based deployment with several 1542i APs that are almost physically inaccessible. We have purchased several 9124AXi to expand this deployment and have connected them to a 9800-CL virtual controller. Now we want to move the old 1542is to this new controller since according to Cisco's wireless compatibility matrix it is possible, but we are having problems doing so. We have successfully configured option 43 pointing to the IP of the new controller (9800-CL) in the DHCP reservations of these machines, but after rebooting, the APs continue to join the ME controllers. We also tried deleting the AP's configuration from the ME controller before restarting the APs, but they keep joining the ME. We are sure that DHCP is working, because we are making the reservations with different IPs than the original ones, so the APs are reading the DHCP information, but for some reason they ignore the 43 info option.
What could be the problem? As I mentioned before, we have no way to easily access the devices or their console and it seems that for several versions Cisco has eliminated the possibility of connecting via ssh to the APs connected to ME controllers (very bad idea, friends!) . Can anyone help us? Thanks in advance.
Deployment data:
ME equipment: 1815i, 1542i and 9105i
MEs sw version: 8.10.96.0
ME controllers: three 1815i
WLC equipment: 9124AXi
WLC sw version: 17.12.4
WLC controller: 9800-CL (Hyper-V)
Option 43: F104C0A8013C (9800-CL IP: 192.168.1.60)
¡Resuelto! Ir a solución.
el 01-06-2025 02:05 PM
@Miguel Angel Alvarez Rodriguez
There is one config on the WLC that changes the priority for the AP when joining.
conf t
wireless priming-controller
end
On your case, the option 43 should work but as the AP has already joined to the ME before, they seems to prefer keep on the ME. When you setup priming, the AP should prefer the capwap offer from the WLC with priming enabled.
el 01-06-2025 05:24 PM
Since you ME chenge the primary WLC for your APs
You can do it by AP with this command:
config ap primary-base controller_name Cisco_AP [controller_ip_address]
If you want to do it for all APs you can use the next command:
config advanced backup-controller primary <backup_controller_name> <IP_Address>
If you want to do it by GUI then follow the next path: “Wireless -> All AP -> Global Configuration”
el 01-06-2025 02:05 PM
@Miguel Angel Alvarez Rodriguez
There is one config on the WLC that changes the priority for the AP when joining.
conf t
wireless priming-controller
end
On your case, the option 43 should work but as the AP has already joined to the ME before, they seems to prefer keep on the ME. When you setup priming, the AP should prefer the capwap offer from the WLC with priming enabled.
el 01-06-2025 05:24 PM
Since you ME chenge the primary WLC for your APs
You can do it by AP with this command:
config ap primary-base controller_name Cisco_AP [controller_ip_address]
If you want to do it for all APs you can use the next command:
config advanced backup-controller primary <backup_controller_name> <IP_Address>
If you want to do it by GUI then follow the next path: “Wireless -> All AP -> Global Configuration”
01-07-2025 10:15 AM - editado 01-07-2025 10:16 AM
Thank you Daniel and Flavio: with that comand from the ME controller I was able to force the controller asignament in the 1542is. Now they're all working in the C9800-CL with the new ones.
No DHCP 43 option required. This way of doing seems better.
Regards.
Descubra y salve sus notas favoritas. Vuelva a encontrar las respuestas de los expertos, guías paso a paso, temas recientes y mucho más.
¿Es nuevo por aquí? Empiece con estos tips. Cómo usar la comunidad Guía para nuevos miembros
Navegue y encuentre contenido personalizado de la comunidad