01-28-2025 02:27 PM
Hi Team,
I'm facing a problem the AP not joined the WLC, please find the logs below.
[*01/27/2025 12:49:29.9297] CAPWAP State: DTLS Teardown
[*01/27/2025 12:49:30.9777] OOBImageDnld: Do common error handler for OOB image download..
[*01/27/2025 12:49:31.0199] CAPWAP detected next hop MAC changed from 0000.5E00.01C8 to E81C.BACC.70EC
[*01/27/2025 12:49:31.0200]
[*01/27/2025 12:49:31.0859] status 'upgrade.sh: Script called with args:[CANCEL]'
[*01/27/2025 12:49:31.1645] do CANCEL, part1 is active part
[*01/27/2025 12:49:31.1826] status 'upgrade.sh: Cleanup tmp files ...'
[*01/27/2025 12:49:35.6031] OOBImageDnld: Do common error handler for OOB image download..
[*01/27/2025 12:49:35.6257] No more AP manager addresses remain..
[*01/27/2025 12:49:35.6257] No valid AP manager found for controller 'WLC-SCR' (ip: 192.11.5.10)
[*01/27/2025 12:49:35.6257] Failed to join controller WLC-SCR.
[*01/27/2025 12:49:35.6257] Failed to join controller.
[*01/27/2025 12:49:36.6261] ipv6 gw config loop in discovery timer expiry
Your Support please.
01-28-2025 02:32 PM
Please add more detail. What controller, what code, the actual model of the AP. Do you have any ap's connected and just having issue with this one? Some info on your setup and the console output from the ap when you boot it up.
01-28-2025 02:45 PM
WLC 9800 in HA mode, all the model of APs 2802 wé have 33 APs but now just 17 joint the WLC.
After disconnecting the AP from the network and reconnecting the AP, do not rejoin the WLC.
01-28-2025 02:35 PM
192.11.5.10 <<- this IP of wlc WMI?
MHM
01-28-2025 02:42 PM
yes this IP of the WLC
01-28-2025 02:45 PM
01-28-2025 02:44 PM
" No valid AP manager found for controller 'WLC-SCR' (ip: 192.11.5.10)"
There is a Bug related to this log
"Cisco Wave 2 APs are unable to establish DTLS connection with the controller until it is rebooted"
"Symptom: COS APs are intermittently entering a state in which they are unable to join WLC. AP logging indicates that there are simply no AP manager interfaces available."
Workaround: Rebooting the AP when in this state will resolve the issue
01-28-2025 02:50 PM
i will rebooting AP but the problem persists
01-28-2025 03:01 PM
Console into the AP and enter the command "capwap ap erase all".
01-30-2025 08:24 AM
You did not answer the earlier question: what software version are you using? (the exact version of software)
Hint: refer to the TAC recommended link below for what you should be using.
01-31-2025 03:35 AM
Hi friend
Please share this from wlc
Wlc >monitoring > witeless > AP
Select AP mac and share output of both
General and statistics
Waiting your reply
MHM
03-18-2025 08:34 AM
@soufiane.belahsen you never answered the question about what version of software you're using.
There's a well known bug which can cause the error your log is reporting (CAPWAP detected next hop MAC changed) - https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwb52379
Also (but unlikely since I don't think you're using IPv6) https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwc71198
Either way, as I said before, you should upgrade software as per the TAC recommended link below to resolve these bugs.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide