Same name AP not joining controller
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2021 07:35 PM - edited 07-05-2021 01:18 PM
Hi,
We have Catalyst 9800-40 WLC , and we are facing the issue "Two Access Points with same name are not able to join controller "
I tried to add new access points . Initially APs joined controller and their MAC ID was shown in Access point list.
I went to Configuration ---> Access Points --> Clicked on AP --> changed its name
Unfortunately I gave few APs same name now they are not joining controller.... Is there any way APs join controller and we can change their name so there is no name conflict ?
- Labels:
-
Wireless LAN Controller
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2021 08:27 PM
sometimes unavoidable or accidental to have similar AP names for a few APs in new installation or migration.
I've seen APs 9120/9130 with the exact similar names were able to join fine on 17.4. and were able to manually change after joined.
in your case, check the AP drop reason/run capwap debugs on AP side and or try to change the existing AP name to something else.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2021 08:09 PM
All you gotta do is change the duplicate name of the AP that is currently on the controller. The AP that is not joined that had the same name will join. I just had this scenario and it worked. And of course the AP has to have the controller IP. Assuming it does in your case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2021 08:34 PM
Yes I did same as you suggested
Duplicate name APs are renamed to "-111" or like that and those APs have joined controller before that they were unable to join.
Thank you for the solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2021 08:32 PM
Yes As of now I did the same
I found out the list of APs that that have already joined controller to "-111" Duplication APs have joined the controller as the name conflict was removed
What do you suggest to go for 17.4 version or keep it same ? As of now my work is running smoothly without any issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2021 02:47 AM - edited 05-18-2021 02:47 AM
> What do you suggest to go for 17.4 version or keep it same ? As of now my work is running smoothly without any issue.
You did not say what version you're using?
Anyway you need to assess which release is correct for your environment. Read the release notes. In general, unless you need specific features in the short-lived releases, then you should stick with the long-lived extended support releases - currently 17.3.x next will be 17.6.x.
At the moment: TAC recommends 17.3.3 for all deployments
Please click Helpful if this post helped you and Select as Solution (drop down menu at top right of this reply) if this answered your query.
------------------------------
TAC recommended codes for AireOS WLC's and TAC recommended codes for 9800 WLC's
Best Practices for AireOS WLC's, Best Practices for 9800 WLC's and Cisco Wireless compatibility matrix
Check your 9800 WLC config with Wireless Config Analyzer using "show tech wireless" output or "config paging disable" then "show run-config" output on AireOS and use Wireless Debug Analyzer to analyze your WLC client debugs
Field Notice: FN63942 APs and WLCs Fail to Create CAPWAP Connections Due to Certificate Expiration
Field Notice: FN72424 Later Versions of WiFi 6 APs Fail to Join WLC - Software Upgrade Required
Field Notice: FN72524 IOS APs stuck in downloading state after 4 Dec 2022 due to Certificate Expired
- Fixed in 8.10.196.0, latest 9800 releases, 8.5.182.12 (8.5.182.13 for 3504) and 8.5.182.109 (IRCM, 8.5.182.111 for 3504)
Field Notice: FN70479 AP Fails to Join or Joins with 1 Radio due to Country Mismatch, RMA needed
How to avoid boot loop due to corrupted image on Wave 2 and Catalyst 11ax Access Points (CSCvx32806)
Field Notice: FN74035 - Wave2 APs DFS May Not Detect Radar After Channel Availability Check Time
Leo's list of bugs affecting 2800/3800/4800/1560 APs
Default AP console baud rate from 17.12.x is 115200 - introduced by CSCwe88390
