Re: LAP 1250 can't join the controller

Jaaazman777 · ‎04-01-2011

Good day!

Briefly about the problem:

I have upgraded one of our autonomus AP to lightweight AP
At first everything went ok - the LAP dowloaded the image from the WLC and then I was able to successfuly manage it though the controller.
After that the LAP was switched off and waited for her destiny for several months
During the installation we noticed that in several minutes all the indicators stopped blinking. The issue was not about power, because in the CLI we saw it actively functioning. But it couldn't assotiate with the controller
Debug

%CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.
%CAPWAP-3-ERRORLOG: Failed to handle timer message.
%CAPWAP-3-ERRORLOG: Failed to process timer message.
%CAPWAP-3-ERRORLOG: Discovery interval timer expiry handler failed.

I downgraded the LAP to AP, then returned it again to LAP

After that the indicators bwgan to blink in normal mode, but still no assosoation with the WLC

Surendra BG · ‎04-01-2011

Hi,

What does the Console logs from the AP say??

Regards

Surendra

Regards
Surendra BG

Surendra BG · ‎04-01-2011

please make sure we have the DNS entry CISCO-CAPWAP-CONTROLLER or CISCO-LWAPP-CONTROLLER , if we are using the DNS to resolve..

Wats the WLC software version we are running??

Regards

Surendra

Regards
Surendra BG

Jaaazman777 · ‎04-01-2011

Surendra BG, thank you for your answer!

As far as I know, LAP can find the controller without dns entries CISCO-CAPWAP-CONTROLLER and CISCO-LWAPP-CONTROLLER, because we can clearly indicate the ap-manager interface by using

lwapp ap controller ip address *wls_ap-manager_ip* / capwap ap controller ip address *wls_ap-manager_ip*

besides, I can ping the ap_manager interface from the LAP

From the practic experience (almost 10 LAPs) I managed LAPs with the following configuration:

lwapp/capwap ap ip address *ap_ip* *mask*
lwapp/capwap ap controller ip address *wls_ap-manager_ip*

and everything was ok, inspite of there are no dns CONTROLLER entries

Here is the full debug:

Translating "CISCO-LWAPP-CONTROLLER"...domain server (255.255.255.255)

Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)

%CAPWAP-3-ERRORLOG: Could not discover configured MWAR (Lab).

%CAPWAP-3-ERRORLOG: Could Not resolve CISCO-LWAPP-CONTROLLER

%CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER

%CAPWAP-3-ERRORLOG: Failed to join controller.

%CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.

%CAPWAP-3-ERRORLOG: Failed to handle timer message.

%CAPWAP-3-ERRORLOG: Failed to process timer message.

%CAPWAP-3-ERRORLOG: Discovery interval timer expiry handler failed.

p.s. WLC version is 7.0.98.0

dmantill · ‎04-01-2011

Is WLC in a different subnet as the AP?

Did you setup the gateway on each AP? capwap ap ip default-gateway x.x.x.x

Jaaazman777 · ‎04-01-2011

Yes, I have provided it with default-gateway

the WLC is on different subnet with the LAP,

dmantill · ‎04-01-2011

So so go ahead and use this command:

test capwap controller ip x.x.x.x

Where x.x.x.x is the managment IP address of the WLC.

Remember that you MUST have IP connectivity to both, management and ap-manager interface.

Leo Laohoo · ‎04-01-2011

I don't know with the rest but the informations you've provided isn't enough.

1. Console to into the AP.

2. Power down the AP.

3. Power up the AP.

4. Post the entire output from the console. I would like to see the bootup process all the way down to the discovery process. This is very, very imformative process and it's never failed me.

justin_barnes · ‎04-06-2011

what version of code is on the controller? 1250 series wont join to anything above 4.2.176

dmantill · ‎04-06-2011

Justin, according to the logs, its sasys capwap, therefore it shouldnt be using 4.2 code or below since 4.2 is LWAPP

Jaaazman777 · ‎04-06-2011

Dear, all! thank you very much for your advices!

I've provided you the wrong information about LAP - it is 1252AG, not just 1250

leolaohoo , here is the bootup process

IOS Bootloader - Starting system.
Xmodem file system is available.
flashfs[0]: 159 files, 8 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
flashfs[0]: Total bytes: 31868928
flashfs[0]: Bytes used: 23429120
flashfs[0]: Bytes available: 8439808
flashfs[0]: flashfs fsck took 38 seconds.
Reading cookie from flash parameter block...done.
Base Ethernet MAC address: 00:22:90:0b:bf:0a
Loading "flash:/c1250-rcvk9w8-mx"...#############################################################################################################

File "flash:/c1250-rcvk9w8-mx" uncompressed and installed, entry point: 0x3000
executing...

Restricted Rights Legend

Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.

           cisco Systems, Inc.
           170 West Tasman Drive
           San Jose, California 95134-1706

Cisco IOS Software, C1250 Software (C1250-RCVK9W8-M), Version 12.4(21a)JA2, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Mon 02-Nov-09 19:03 by prod_rel_team

Proceeding with system init

Proceeding to unmask interrupts
Initializing flashfs...

flashfs[1]: 159 files, 8 directories
flashfs[1]: 0 orphaned files, 0 orphaned directories
flashfs[1]: Total bytes: 31868928
flashfs[1]: Bytes used: 23429120
flashfs[1]: Bytes available: 8439808
flashfs[1]: flashfs fsck took 8 seconds.
flashfs[1]: Initialization complete....done Initializing flashfs.

%Error opening flash:/info (No such file or directory)
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.

%Error opening flash:/info (No such file or directory)
%Error opening flash:/c1250-rcvk9w8-mx/info (No such file or directory)cisco AIR-AP1252AG-A-K9 (PowerPC 8349) processor (revision A0) with 49142K/16384K bytes of memory.
Processor board ID FCW1230Z00M
PowerPC 8349 CPU at 533Mhz, revision number 0x0031
Last reset from power-on
LWAPP image version 3.0.51.0
1 Gigabit Ethernet interface

32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 00:22:90:0B:BF:0A
Part Number                          : 73-10425-05
PCA Assembly Number                  : 800-27630-05
PCA Revision Number                  : A0
PCB Serial Number                    : FOC12285R9Q
Top Assembly Part Number             : 800-29039-02
Top Assembly Serial Number           : FCW1230Z00M
Top Revision Number                  : A0
Product/Model Number                 : AIR-AP1252AG-A-K9

hostname
% Incomplete command.
% Please define a domain-name first.

Press RETURN to get started!

Translating "CISCO-LWAPP-CONTROLLER"...domain server (255.255.255.255)

Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)

*Mar 1 00:00:09.979: %LWAPP-3-CLIENTEVENTLOG: Read and initialized AP event log (contains, 1024 messages)
capwap_read_version_info: Info file flash:/info not find
*Mar 1 00:00:12.055: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state to up
*Mar 1 00:00:12.079: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C1250 Software (C1250-RCVK9W8-M), Version 12.4(21a)JA2, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Mon 02-Nov-09 19:03 by prod_rel_team
*Apr 22 06:28:05.035: %CDP_PD-2-POWER_LOW: All radios disabled - AC_ADAPTOR (0000.0000.0000)
*Apr 22 06:28:05.975: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up
*Apr 22 06:28:06.019: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-LWAPP-CONTROLLER
*Apr 22 06:28:06.019: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Apr 22 06:28:06.023: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
Translating "CISCO-LWAPP-CONTROLLER"...domain server (255.255.255.255)

Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)

*Apr 22 06:28:33.899: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-LWAPP-CONTROLLER
*Apr 22 06:28:33.899: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
Translating "CISCO-LWAPP-CONTROLLER"...domain server (255.255.255.255)

Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)

*Apr 22 06:28:43.903: %CAPWAP-3-ERRORLOG: Could not discover configured MWAR (Lab).
*Apr 22 06:28:43.903: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-LWAPP-CONTROLLER
*Apr 22 06:28:43.903: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Apr 22 06:28:43.907: %CAPWAP-3-ERRORLOG: Failed to join controller.
*Apr 22 06:28:43.907: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.
*Apr 22 06:28:43.907: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
*Apr 22 06:28:43.907: %CAPWAP-3-ERRORLOG: Failed to process timer message.
*Apr 22 06:28:43.907: %CAPWAP-3-ERRORLOG: Discovery interval timer expiry handler failed.
Translating "CISCO-LWAPP-CONTROLLER"...domain server (255.255.255.255)

Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)

*Apr 22 06:28:53.907: %CAPWAP-3-ERRORLOG: Could not discover configured MWAR (Lab).
*Apr 22 06:28:53.907: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-LWAPP-CONTROLLER
*Apr 22 06:28:53.907: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Apr 22 06:28:53.911: %CAPWAP-3-ERRORLOG: Failed to join controller.
*Apr 22 06:28:53.911: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.
*Apr 22 06:28:53.911: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
*Apr 22 06:28:53.911: %CAPWAP-3-ERRORLOG: Failed to process timer message.
*Apr 22 06:28:53.911: %CAPWAP-3-ERRORLOG: Discovery interval timer expiry handler failed.
Translating "CISCO-LWAPP-CONTROLLER"...domain server (255.255.255.255)

Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)

about resolving the controller name - I saw these failed translations before, but the whole looking-up process was OK, the LAP was able to joib the wlc

- the WLC ver is 7.0.98.0

- the WLC and LAP are in different L3 networks

I typed in the following commands (the same with lwapp):

capwap ap ip address *ap_ip* *mask*
capwap ap controller ip address *wls_ap-manager_ip*
capwap ap ip default-gateway *gw*

Leo Laohoo · ‎04-06-2011

Pretty!

Now where's the IP address? You got static?

Can you ping the WLC management IP address?

Jaaazman777 · ‎04-07-2011

The ip address is static

LAP doesn't try to get it by dhcp - it is strange

yes, I'm able to ping boyh WLC interfaces: managment, ap-manager

dmantill · ‎04-07-2011

Did you already try using this command:

test capwap controller ip x.x.x.x

x.x.x.x is the Management IP of the WLC.

Jaaazman777 · ‎04-07-2011

I tried this command, but didn't see any results

debug messages are still the same

*Apr 22 06:37:14.071: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-LWAPP-CONTROLLER
*Apr 22 06:37:14.071: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Apr 22 06:37:14.075: %CAPWAP-3-ERRORLOG: Failed to join controller.
*Apr 22 06:37:14.075: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.
*Apr 22 06:37:14.075: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
*Apr 22 06:37:14.075: %CAPWAP-3-ERRORLOG: Failed to process timer message.
*Apr 22 06:37:14.075: %CAPWAP-3-ERRORLOG: Discovery interval timer expiry handler failed.