Help with Cisco 1142N not discovering 2504 WLC

[Clay Plaga]

I have a wireless test network that I am using for my certification. I am very new to this. I have a Cisco 1142N access point trying to connect to a Cisco 2504 WLC. I am using DHCP from my domain controller. I converted the access point from autonomous to lightweight. The access point is running k9w8. The DHCP server says it's issuing an IP address(192.168.20.11), but I can not PING the access point ip address from the WLC. The AP console output is saying it cannot discover the WLC. If you look at the output text from the AP, it says the bvi1 address is 192.168.5.200. I used that address for the conversion to lightweight. Is the bvi1 address causing the problem? Do I need to remove the bvi1 ip address 192.168.5.200?  I have 3 other 1142N's, and they are joining the controller correctly.

Below are sections of the AP console output.

Access point console output

Not in Bound state.
*Mar 1 09:32:22.929: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*Mar 1 09:32:26.055: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 192.168.20.11, mask 255.255.255.0, hostname AP4055.39ca.8052

Translating "CISCO-CAPWAP-CONTROLLER.photonics.org"...domain server (192.168.5.7)

AP4055.39ca.8052#show ip interface brief
Interface IP-Address OK? Method Status Protocol
BVI1 192.168.5.200 YES TFTP up up
Dot11Radio0 unassigned NO unset up up
Dot11Radio1 unassigned NO unset up up
GigabitEthernet0 unassigned NO unset up up
AP4055.39ca.8052#

BVI1 is up, line protocol is up
Internet address is 192.168.20.11/24
Broadcast address is 255.255.255.255
Address determined by DHCP
MTU is 1500 bytes
Helper address is not set
Directed broadcast forwarding is disabled
Multicast reserved groups joined:
Outgoing access list is not set
Inbound access list is not set
Proxy ARP is enabled
Local Proxy ARP is disabled
Security level is default
Split horizon is enabled
ICMP redirects are always sent
I▒
using eeprom values

Any help will appreciated. Thank you.

[Leo Laohoo]

Post the complete output to the following commands: 

1. WLC:  sh sysinfo
2. WLC:  sh time
3. AP:  sh version
4. AP:  sh ip interface brief
5. AP:  sh capwap client rcb

[Clay Plaga]

Thank you for helping me. I am very new to this. When I type:

SHOW SYSINFO

SHOW TIME

The CLI output on the WLC 2504 says:

incorrect usage

What is the exact command to show sysinfo and show time on the WLC CLI? From the 2504 GUI, I can see that the time is correct.

CORRECTION. I AM NOT ABLE TO PING 192.168.20.11 FROM WLC.

This is a screenshot from 2504 CLI:

This is the console output from the 1142 access point:

sh version
Cisco IOS Software, C1140 Software (C1140-RCVK9W8-M), Version 15.3(3)JD, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2016 by Cisco Systems, Inc.
Compiled Fri 29-Jul-16 05:19 by prod_rel_team

ROM: Bootstrap program is C1140 boot loader
BOOTLDR: C1140 Boot Loader (C1140-BOOT-M) Version 12.4(23c)JA, RELEASE SOFTWARE (fc3)

AP4055.39ca.8052 uptime is 45 minutes
System returned to ROM by power-on
System image file is "flash:/c1140-rcvk9w8-mx/c1140-rcvk9w8-xx"
Last reload reason:

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
--More--
Translating "CISCO-CAPWAP-CONTROLLER.photonics.org"...domain server (192.168.5.7

SHOW IP INT BRIEF

AP4055.39ca.8052#show ip int brief
Interface IP-Address OK? Method Status Protocol
BVI1 unassigned YES DHCP up up
GigabitEthernet0 unassigned NO unset up up
AP4055.39ca.8052#
*Mar 1 00:46:52.030: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*Mar 1 00:46:55.156: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 192.168.20.11, mask 255.255.255.0, hostname AP4055.39ca.8052

Translating "CISCO-CAPWAP-CONTROLLER.photonics.org"...domain server (192.168.5.7)

SHOW CAPWAP CLIENT RCB

AP4055.39ca.8052#SH CAPWAP CLIENT
AP4055.39ca.8052#SH CAPWAP CLIENT RCB
AdminState : ADMIN_ENABLED
SwVer : 8.3.102.0
NumFilledSlots : 0
Name : AP4055.39ca.8052
Location : default location
MwarName :
MwarMacAddr : ff01.0000.0000
MwarHwVer : 0.0.0.0
ApMode : Local
ApSubMode : Not Configured
OperationState : DISCOVERY
CAPWAP Path MTU : 148
Not in Bound state.5
Link-Encryption (AP) : Disabled
Link-Encryption (MWAR) : Disabled
Prefer-mode : Un-configured
LinkAuditing : disabled
AP Rogue Detection Mode : Enabled
AP Tcp MSS Adjust : Disabled
Predownload Status : None
Auto Immune Status : Disabled
RA Guard Status : Disabled
Efficient Upgrade State : Disabled
Efficient Upgrade Role : None
TFTP Server : Disabled
Antenna Band Mode : Unknown
Universal AP Priming mode : Unprimed

Thank you.

[marce1000]

 - What software version is the WLC running ? Is there anything in the WLC-logs when the AP tries to join ?

 M.

[Clay Plaga]

WLC 2504 software version is:

8.3.143.0

This is CLI debug log from WLC when AP attempts to join WLC:

(Cisco Controller) >debug capwap events enable

(Cisco Controller) >*spamApTask3: Oct 28 09:26:43.995: 58:bc:27:5d:12:c0 Primary Discovery Request from 192.168.20.12:18133

*spamApTask3: Oct 28 09:26:43.995: 58:bc:27:5d:12:c0 apType = 15 apModel: AIR-LAP1142N-A-K9

*spamApTask3: Oct 28 09:26:43.995: 58:bc:27:5d:12:c0 apType: Oxf bundleApImageVer: 8.3.143.0
*spamApTask3: Oct 28 09:26:43.995: 58:bc:27:5d:12:c0 version:8 release:3 maint:143 build:0
*spamApTask3: Oct 28 09:26:43.995: 58:bc:27:5d:12:c0 Primary Discovery Response sent to 192.168.20.12:18133

*spamApTask3: Oct 28 09:26:45.161: 58:bc:27:5d:12:c0 WTP Event Request from 192.168.20.12:18133 epoch 1635427605

*spamApTask3: Oct 28 09:26:45.161: 58:bc:27:5d:12:c0 WTP Event Response sent to 192.168.20.12:18133

*spamApTask3: Oct 28 09:26:45.165: 58:bc:27:5d:12:c0 WTP Event Request from 192.168.20.12:18133 epoch 1635427605

*spamApTask3: Oct 28 09:26:45.165: 58:bc:27:5d:12:c0 WTP Event Response sent to 192.168.20.12:18133

*spamApTask3: Oct 28 09:26:45.168: 58:bc:27:5d:12:c0 WTP Event Request from 192.168.20.12:18133 epoch 1635427605

*spamApTask3: Oct 28 09:26:45.168: 58:bc:27:5d:12:c0 WTP Event Response sent to 192.168.20.12:18133

*spamApTask3: Oct 28 09:26:45.213: 58:bc:27:5d:12:c0 WTP Event Request from 192.168.20.12:18133 epoch 1635427605

*spamApTask3: Oct 28 09:26:45.214: 58:bc:27:5d:12:c0 WTP Event Response sent to 192.168.20.12:18133

*spamApTask3: Oct 28 09:26:45.247: 58:bc:27:5d:12:c0 WTP Event Request from 192.168.20.12:18133 epoch 1635427605

*spamApTask3: Oct 28 09:26:45.248: 58:bc:27:5d:12:c0 WTP Event Response sent to 192.168.20.12:18133

*spamApTask3: Oct 28 09:26:45.969: 58:bc:27:5d:12:c0 WTP Event Request from 192.168.20.12:18133 epoch 1635427605

*spamApTask3: Oct 28 09:26:45.969: 58:bc:27:5d:12:c0 WTP Event Response sent to 192.168.20.12:18133

*spamApTask3: Oct 28 09:26:45.971: 58:bc:27:5d:12:c0 WTP Event Request from 192.168.20.12:18133 epoch 1635427605

*spamApTask3: Oct 28 09:26:45.971: 58:bc:27:5d:12:c0 WTP Event Response sent to 192.168.20.12:18133

*spamApTask3: Oct 28 09:26:45.973: 58:bc:27:5d:12:c0 WTP Event Request from 192.168.20.12:18133 epoch 1635427605

*spamApTask3: Oct 28 09:26:45.973: 58:bc:27:5d:12:c0 WTP Event Response sent to 192.168.20.12:18133

*spamApTask3: Oct 28 09:26:50.765: 58:bc:27:5d:12:c0 WTP Event Request from 192.168.20.12:18133 epoch 1635427610

*spamApTask3: Oct 28 09:26:50.766: 58:bc:27:5d:12:c0 WTP Event Response sent to 192.168.20.12:18133

*spamApTask3: Oct 28 09:26:50.768: 58:bc:27:5d:12:c0 WTP Event Request from 192.168.20.12:18133 epoch 1635427610

*spamApTask3: Oct 28 09:26:50.768: 58:bc:27:5d:12:c0 WTP Event Response sent to 192.168.20.12:18133

*spamApTask3: Oct 28 09:26:50.770: 58:bc:27:5d:12:c0 WTP Event Request from 192.168.20.12:18133 epoch 1635427610

*spamApTask3: Oct 28 09:26:50.770: 58:bc:27:5d:12:c0 WTP Event Response sent to 192.168.20.12:18133

*spamApTask3: Oct 28 09:27:20.768: 58:bc:27:5d:12:c0 Echo Request from 192.168.20.12:18133

(Cisco Controller) >debug dis*spamApTask3: Oct 28 09:27:20.768: 58:bc:27:5d:12:c0 Echo Response sent to 192.168.20.12:18133

*spamApTask3: Oct 28 09:27:45.208: 58:bc:27:5d:12:c0 WTP Event Request from 192.168.20.12:18133 epoch 1635427665

*spamApTask3: Oct 28 09:27:45.208: 58:bc:27:5d:12:c0 WTP Event Response sent to 192.168.20.12:18133

*spamApTask3: Oct 28 09:27:45.242: 58:bc:27:5d:12:c0 WTP Event Request from 192.168.20.12:18133 epoch 1635427665

able-all*spamApTask3: Oct 28 09:27:45.242: 58:bc:27:5d:12:c0 WTP Event Response sent to 192.168.20.12:18133

*spamApTask6: Oct 28 09:27:49.588: 00:27:0d:99:80:f0 Capwap State Change Event (Down) from capwap_ac_sm.c 7747

*apfReceiveTask: Oct 28 09:27:49.589: 00:27:0d:99:80:f0 Received LWAPP Down event for AP 00:27:0d:99:80:f0 slot 0!
*spamApTask6: Oct 28 09:27:49.589: 00:27:0d:99:80:f0 apfSpamProcessStateChangeInSpamContext: Down LWAPP event for AP 00:27:0d:99:80:f0 slot 0
*spamApTask6: Oct 28 09:27:49.590: 00:27:0d:99:80:f0 Capwap State Change Event (Down) from capwap_ac_sm.c 7747

*apfReceiveTask: Oct 28 09:27:49.590: 00:27:0d:99:80:f0 Received LWAPP Down event for AP 00:27:0d:99:80:f0 slot 1!
*spamApTask6: Oct 28 09:27:49.591: 00:27:0d:99:80:f0 apfSpamProcessStateChangeInSpamContext: Down LWAPP event for AP 00:27:0d:99:80:f0 slot 1
*spamApTask6: Oct 28 09:27:49.592: 00:27:0d:99:80:f0 Finding DTLS connection to delete for AP (192:168:20:13/29977)
*spamApTask6: Oct 28 09:27:49.593: 00:27:0d:99:80:f0 Disconnecting DTLS Capwap-Ctrl session 0x19c794b8 for AP (192:168:20:13/29977). Notify(true)
*spamApTask6: Oct 28 09:27:49.593: 00:27:0d:99:80:f0 CAPWAP State: Dtls tear down

*spamApTask6: Oct 28 09:27:49.594: 00:27:0d:99:80:f0 acDtlsPlumbControlPlaneKeys: lrad:192.168.20.13(29977) mwar:192.168.5.4(5246)

*spamApTask6: Oct 28 09:27:49.594: 00:27:0d:99:80:f0 DTLS keys for Control Plane deleted successfully for AP 192.168.20.13

*spamApTask5: Oct 28 09:27:49.595: 00:27:0d:99:80:f0 DTLS connection closed event receivedserver (192.168.5.4/5246) client (192.168.20.13/29977)
*spamApTask5: Oct 28 09:27:49.595: 00:27:0d:99:80:f0 Entry exists for AP (192.168.20.13/29977)
*spamApTask5: Oct 28 09:27:49.597: 00:27:0d:99:80:f0 Capwap State Change Event (DeReg) from capwap_ac_sm.c 1746

*spamApTask5: Oct 28 09:27:49.597: 00:27:0d:99:80:f0 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 00:27:0d:99:80:f0 slot 0
*spamApTask5: Oct 28 09:27:49.597: 00:27:0d:99:80:f0 Capwap State Change Event (DeReg) from capwap_ac_sm.c 1746

*spamApTask5: Oct 28 09:27:49.597: 00:27:0d:99:80:f0 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 00:27:0d:99:80:f0 slot 1
*spamApTask5: Oct 28 09:27:49.597: 00:27:0d:99:80:f0 AP Delete request
*apfReceiveTask: Oct 28 09:27:49.599: 00:27:0d:99:80:f0 Deregister LWAPP event for AP 00:27:0d:99:80:f0 slot 0
*apfReceiveTask: Oct 28 09:27:49.600: 00:27:0d:99:80:f0 Deregister LWAPP event for AP 00:27:0d:99:80:f0 slot 1
*spamApTask5: Oct 28 09:27:49.600: 00:27:0d:99:80:f0 No AP entry exist in temporary database for 192.168.20.13:29977

Thank you.

[marce1000 · Accepted solution]

 - Check working NTP settings on the controller and have a look into this thread  , it may be useful :

            https://community.cisco.com/t5/wireless/ap-failed-to-join-the-mobility-express-controller/m-p/4460382

 M.

[Clay Plaga]

Yes, the time is correct. NTP is configured on WLC.  The WLC is getting time from my domain controller. NTP master is on domain controller.

 I will  read document. Any other ideas?

Thanks.

[Clay Plaga]

Just one last question. Is it possible that the access point is broken? I have 4 other 1142N's, and they all connect to the WLC. I just wanted to try and fix the AP to improve my troubleshooting skills.

Thank you,

[marce1000]

   - You could try to factory reset it and try again , 

 M.

[Leo Laohoo · Accepted solution]

---

@Clay Plaga wrote:

NTP is configured on WLC.  The WLC is getting time from my domain controller. NTP master is on domain controller.

---

If this NTP Master is a MS-based OS then it will not work.  Microsoft's implementation of NTP/SNTP is not the standard. 

---

@Clay Plaga wrote:

The CLI output on the WLC 2504 says:

incorrect usage

---

After entering the command "sh time", press the <TAB> before CR.

[Clay Plaga]

I know you are correct. What I don't understand is, from what I can see, the WLC is getting the exact time as the domain controller. NTP is configured on the DC. How is the WLC getting it's time? Also, I have 4 other 1142N's, and they are joining the WLC and working. Clients can access and connect to the AP. I have also reset the AP that's not joining the 2504 WLC.  Any ideas on anything else I can check?

The CLI command I found for the WLC is:

show run-config

That command showed me all the info I needed. What do you mean by:

press the <TAB> before CR

Thank you very much.

[Leo Laohoo]

---

@Clay Plaga wrote:

 Also, I have 4 other 1142N's, and they are joining the WLC and working.

---

I believe there is only one culprit left:  FN - 63942 - Wireless Lightweight Access Points and WLAN Controllers Fail to Create CAPWAP/LWAPP Connections Due to Certificate Expiration