A Solution for 2504 WLC Configuration to Different Regions of APs

Preface: Cisco 2500 Series Wireless Controller support a maximum of 50 lightweight APs in increments of 5 APs with a minimum of 5 APs, making it a cost-effective solution for retail and small and medium-sized businesses. The Cisco 2500 Series Wireless Controller offers robust coverage with 802.11a/b/g or delivers unprecedented reliability using 802.11n and Cisco Next-Generation Wireless Solutions and Cisco Enterprise Wireless Mesh.

 2500-deploy-guide-01

2500-deploy-guide-02

Here I would like to share my experience of WLC Configuration to Different Aps Regions.

I have a Cisco 2504 WLC running Software Version 7.4.110.0 and I have 3 AIR-CAP1602I-C-K9s setup on it. Here I also checked the AP image to WLC 2504 and have log as follows:

Primary AP     Image Size

—————-             —-

ap1g2                   9568

ap3g1                   11288

ap3g2                   11196

ap801                   7164

ap802                   8568

c1130                   5072

c1140                   9416

c1250                   6944

c1520                   8044

c602i                   3736

 Secondary AP     ImageSize

——————            —-

ap3g1                   5792

ap801                   5192

ap802                   5232

c1100                   3084

c1130                   4964

c1140                   4992

c1200                   3364

c1240                   4812

c1250                   5504

c1310                   3136

c1520                   6404

c3201                   4324

c602i                   3716

I got that the c602i is the AP image I need for my APs. But the problem is the WLC cannot find the APs, so I read Log from AP details below:

13 12:44:26.607: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(UNKNOWN_MESSAGE_TYPE (5)

*Nov 13 12:44:26.607: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE

*Nov 13 12:44:26.607: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.1.30:5246

*Nov 13 12:44:26.651: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Nov 13 12:44:26.671: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

*Nov 13 12:44:26.671: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down

*Nov 13 12:44:26.687: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Nov 13 12:44:26.719: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up

*Nov 13 12:44:27.667: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Nov 13 12:44:27.719: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down

*Nov 13 12:44:27.727: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset

*Nov 13 12:44:28.711: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Nov 13 12:44:28.719: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down

*Nov 13 12:44:28.763: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up

*Nov 13 12:44:28.771: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Nov 13 12:44:28.779: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Nov 13 12:44:29.763: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up

*Nov 13 12:44:29.771: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Nov 13 12:44:29.807: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Nov 13 12:44:30.807: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Nov 13 12:44:42.719: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Nov 13 12:44:42.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.1.30 peer_port: 5246

*Nov 13 12:44:42.507: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.1.30 peer_port: 5246

*Nov 13 12:44:42.507: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.30

*Nov 13 12:44:42.511: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.

*Nov 13 12:44:42.511: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.

*Nov 13 12:44:42.511: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Nov 13 12:44:42.511: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 192.168.1.30

In fact, it took me much time to solve this problem, I finally realized that Cisco has configured a country code ensures that each radio’s broadcast frequency bands, interfaces, channels and transmit power levels are compliant with country-specific regulations. Well, I changed the country code of my WLC and last it worked.

How to change the country code of a WLC? Before you can change the country code of a WLC, you must disable the 802.11a and 802.11b network:

>config 802.11a disable network

>config 802.11b disable network

Now you can change the country code of the controller. For example, we change it from US to CN (CHINA)

>config country CN

After changing the country, enable the 802.11 interfaces.

>config 802.11a enable network

>config 802.11b enable network

Change the Timezone if necessary on WLC:

(Cisco Controller) >config time timezone 2 0

And now we’ve got the right time :

(Cisco Controller) >show time

Time……………………………………… Thu Nov 17 16:50:17 2013

Change time on AP:

clock set hh:mm:ssday month year

More Cisco Networking Guide and Tips:

How to Use IP SLA to Change Routing?

How to Connect Cisco Wireless Access Point?

Steps to Configure Static NAT with Route-maps

Share This Post

Post Comment