cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
8790
Views
31
Helpful
6
Replies

AP 1562 Not Joining 5520 WLC

Mehmet Can
Level 1
Level 1

Hello Everyone,

 

I'm trying to include the AP-1562 Outdoor AP on 5520 WLC.
I upgraded the system twice. (first: 8.3.143 latter: 8.5.131 both version are suggested by cisco)

We have 165 pieces 2802 AP, all AP works fine.
What could be my problem?

 

(Cisco Controller) >show ap join stats summary all

Number of APs.............................................. 2

Base Mac AP EthernetMac AP Name IP Address Status
00:be:75:16:ee:c0 N A APA023.9FA9.F9C0 10.11.22.54 Not Joined
70:69:5a:01:03:20 N A AP380E.4DBF.8316 10.11.22.53 Not Joined

2 Accepted Solutions

Accepted Solutions

Hi

Outdoor APs need to be permitted via Mac address otherwise they won't join.

 

-If I helped you somehow, please, rate it as useful.-

View solution in original post

Yes, i found the way.

Security -> Ap policies -> Add -> Write Outdoor AP Mac Address -> Select "MIC" -> Enter Add

 

Thank you for reply.

View solution in original post

6 Replies 6

Hi

Outdoor APs need to be permitted via Mac address otherwise they won't join.

 

-If I helped you somehow, please, rate it as useful.-

Yes, i found the way.

Security -> Ap policies -> Add -> Write Outdoor AP Mac Address -> Select "MIC" -> Enter Add

 

Thank you for reply.

You got it!!

 

 

 

-If I helped you somehow, please, rate it as useful.-

Hi Flavio, Which of the 3 software should I have to be able to add an ap1562 to a WLC?
SWAP1560-MBEXP-K9, SWAP1560-LOCAL-K9 or SWAP1560-MBEXP-K9?

BenPluma
Level 1
Level 1

It was discovered that the 1562 is shipped in bridge mode. This is why it doesn't connect to the controller.

Run the command 'capwap ap mode local' to take it out of bridge mode. For some reason, we also had to set a static IP address to get it to work. Example: Use command 'capwap ap ip 192.168.0.10 255.255.255.0 192.168.0.1' where 192.168.0.10 is the AP's static IP address with subnet mask of 255.255.255.0 and where 192.168.0.1 is the default gateway.

After this it showed up on our controller and we were able to provision it. (Remember to change the IP address upon deployment)

This helped.

Thank you.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Review Cisco Networking products for a $25 gift card