HREAP AP not joining WLC

Alejandro Gonzalez · ‎03-12-2012

Hello everybody, Im consulting you because Im implementing a new AP outside my office.

The new AP is configured to use HREAP but it doesnt register with the centralized WLC.

ping connectivity is OK between each other.

This is the log on the AP:

*Mar 12 18:05:38.623: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.122.3.166 peer_port: 5246

*Mar 12 18:05:38.624: %CAPWAP-5-SENDJOIN: sending Join Request to 10.122.3.166

*Mar 12 18:05:38.624: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*Mar 12 18:05:39.180: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG

AP-Cican-1#p 10.122.3.166

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.122.3.166, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 6/12/19 ms

AP-Cican-1#sh capwap ip config

LWAPP Static IP Configuration

Default Gateway 10.122.19.250

Primary Controller 10.122.3.165

AP-Cican-1#

What´s is wrong??. Did I miss anything??

THANKS IN ADVANCE!!!!

daviwatk · ‎03-12-2012

What "is" wrong? This output shows we joined and were sent a config from the WLC. Is the AP falling off the WLC after some amount of time? Can you post the output of the entire boot-up/discovery/join process of this WLC? Is it joining a WLC other than the one you wanted? What's the problem here?

grabonlee · ‎03-12-2012

Hi

Could you please confirm what controller is using 10.122.3.166. This is because you mentioned that the AP can ping the controller but doesn't join it. From the AP config you have 10.122.3.165 as the primary controller, but you pinged 10.122.3.166, which is the controller

the AP has joined

Alejandro Gonzalez · ‎03-12-2012

The WLC has two management interfaces, .3.165 and .3.166

Ping to both addresses is OK.

The problem is that when I initialy config the AP, it doesnt join to the WLC, but after a normal reboot (reload now command), the AP did join the WLC.

After a few minutes, the AP where isolated again.

So, I reloaded again the AP and enter again into WLC operation.

This is the log:

Translating "CISCO-CAPWAP-CONTROLLER.sa.kof.ccf"...domain server (10.122.18.1)

., 2)12 18:40:19.995: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_ECHO_REQUEST

*Mar 12 18:40:19.995: %LWAPP-3-CLIENTEVENTLOG: Switching to Standalone mode

*Mar 12 18:40:20.021: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE

*Mar 12 18:40:20.021: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 10.122.3.166:5246

*Mar 12 18:40:20.086: %WIDS-6-DISABLED: IDS Signature is removed and disabled.

*Mar 12 18:40:20.087: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Mar 12 18:40:20.088: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP. (10.122.0.55)

*Mar 12 18:40:39.089: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER.sa.kof.ccfInterface does not have a DHCP originated address

Interface does not have a DHCP originated address

*Mar 12 18:42:49.115: %CAPWAP-5-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.

I should also say that this AP was used before on another LAN (the local LAN for the WLC).

grabonlee · ‎03-12-2012

Hi

Please do the following:

1. Do a Shut and no shut on the switch port the AP is connected to.

2. When AP is seen on the controller, quickly disable Admin status.

3. click clear all config and reset

When the AP has reloaded it will have no config except its DHCP assigned address. It will now send a broadcast to find a controller using DHCP option 43 since the controller isnt on the same LAN.

Just make sure the DHCP server is reachable and options 43 is configured with the controller ip

Leo Laohoo · ‎03-12-2012

Can you please post the following output:

1. AP: sh inventory

2. AP: sh version

3. WLC: sh sysinfo

Alejandro Gonzalez · ‎03-13-2012

Im performing in a few minutes the procedure before explained by Osita.

This is the output you requested.

THANKS IN ADVANCE!!

AP-Cican-1#sh version

Cisco IOS Software, C1240 Software (C1240-K9W8-M), Version 12.4(21a)JHB, RELEASE SOFTWARE (fc1)

Technical Support: http://www.cisco.com/techsupport

Compiled Tue 06-Jul-10 14:44 by prod_rel_team

ROM: Bootstrap program is C1240 boot loader

BOOTLDR: C1240 Boot Loader (C1240-BOOT-M) Version 12.4(13d)JA, RELEASE SOFTWARE (fc2)

AP-Cican-1 uptime is 23 hours, 53 minutes

System returned to ROM by power-on

System image file is "flash:/c1240-k9w8-mx.124-21a.JHB/c1240-k9w8-mx.124-21a.JHB"

This product contains cryptographic features and is subject to United

States and local country laws governing import, export, transfer and

use. Delivery of Cisco cryptographic products does not imply

third-party authority to import, export, distribute or use encryption.

Importers, exporters, distributors and users are responsible for

compliance with U.S. and local country laws. By using this product you

agree to comply with applicable laws and regulations. If you are unable

to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:

http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to

export@cisco.com.

cisco AIR-LAP1242G-A-K9 (PowerPCElvis) processor (revision A0) with 24566K/8192K bytes of memory.

Processor board ID FTX1239B6JR

PowerPCElvis CPU at 262Mhz, revision number 0x0950

Last reset from power-on

LWAPP image version 6.0.199.0

1 FastEthernet interface

1 802.11 Radio(s)

32K bytes of flash-simulated non-volatile configuration memory.

Base ethernet MAC Address: 00:1D:70:97:C3:28

Part Number : 73-11465-01

PCA Assembly Number : 800-30492-01

PCA Revision Number : A0

PCB Serial Number : FOC12365M9Z

Top Assembly Part Number : 800-29588-03

Top Assembly Serial Number : FTX1239B6JR

Top Revision Number : A0

Product/Model Number : AIR-LAP1242G-A-K9

Configuration register is 0xF

AP-Cican-1#

AP-Cican-1#sh inventory

NAME: "AP1240", DESCR: "Cisco Aironet 1240 Series (IEEE 802.11a/g) Access Point"

PID: AIR-LAP1242G-A-K9 , VID: V03, SN: FTX1239B6JR

(Cisco Controller) >show sysinfo

Manufacturer's Name.............................. Cisco Systems Inc.

Product Name..................................... Cisco Controller

Product Version.................................. 6.0.199.0

Bootloader Version............................... 1.0.1

Field Recovery Image Version..................... 6.0.182.0

Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27

Build Type....................................... DATA + WPS

System Name...................................... WLC-Alcorta

System Location.................................. UO_Alcorta-Femsa

System Contact................................... arnetworkdata@xxxxx

System ObjectID.................................. 1.3.6.1.4.1.9.1.1069

IP Address....................................... 10.122.3.165

Last Reset....................................... Software reset

System Up Time................................... 93 days 3 hrs 57 mins 11 secs

System Timezone Location......................... (GMT -3:00) Buenos Aires (Agentina)

Current Boot License Level....................... base

Current Boot License Type........................ Permanent

Next Boot License Level.......................... base

Next Boot License Type........................... Permanent

Configured Country............................... AR - Argentina

--More-- or (q)uit

Operating Environment............................ Commercial (0 to 40 C)

Internal Temp Alarm Limits....................... 0 to 65 C

Internal Temperature............................. +38 C

External Temperature............................. +24 C

Fan Status....................................... OK

State of 802.11b Network......................... Enabled

State of 802.11a Network......................... Disabled

Number of WLANs.................................. 5

3rd Party Access Point Support................... Disabled

Number of Active Clients......................... 52

Burned-in MAC Address............................ D0:D0:FD:1F:87:40

Power Supply 1................................... Present, OK

Power Supply 2................................... Absent

Maximum number of APs supported.................. 50

grabonlee · ‎03-13-2012

Alejandro,

Please remember not to enable the Admin status of the AP when you reconfigure back to HREAP. Only when you confirm that the AP does not disconnect from the controller that you can enable it.

Leo Laohoo · ‎03-13-2012

Can you try to upgrade your controller firmware code to 7.0.230.0 or 7.2.x?

Amjad Abdullah · ‎03-14-2012

Alejandro:

kindly noet that code version 6.0.199.0 is deprecated and no longer supported by Cisco. consider to upgrade at leaes to 6.0.220.0 (this is a maintenance release. I suggest you go for this one if you don't want -for whatever reason- to go to 7.x code version.

I had almost same problem like your's when local APs. I had a hard time with some newly installed APs. consoel output on AP was showing me something like your messages above with DHCP. My AP also was trying to go to DNS discovery method direclty and keeps trying indefinitely. I figured out this problem by configuring WLC IP address manually on the AP. my problem seemed to be with old image on the AP. I did not know the root cause though.

With your issue you may consider restting the config on the AP as per one of the suggestions above. But I wonder if it is going to work on this code versoin. I had worked with couple of weird AP joining problems on this version. I encourage you to upgrade.

BTW, what is your WLC model? and how you metion you have two management interfaces? a WLC can only have one management interface only. and how many APs are joining to the WLC?

Rating useful replies is more useful than saying "Thank you"