APs not joining controller errors

I keep getting errors on different APs not joining controllers:
Jan 5 15:54:40.097: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Jan 5 15:54:40.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.x.x.x peer_port: 5246
*Jan 5 15:54:40.001: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Jan 5 15:54:41.778: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.x.x.x peer_port: 5246
*Jan 5 15:54:41.780: %CAPWAP-5-SENDJOIN: sending Join Request to 10.x.x.x
*Jan 5 15:54:41.780: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Jan 5 15:54:41.787: %DTLS-5-ALERT: Received WARNING : Close notify alert from 10.x.x.x
*Jan 5 15:54:41.788: %DTLS-5-PEER_DISCONNECT: Peer 10.x.x.x has closed connection.
*Jan 5 15:54:41.788: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 10.x.x.x :5246.
Any ideas? I'm not sure why the peer is disconnecting the connection. The controller that is linked to It happens on 1242 and 1231 APs mostly. I've had it happen on a 1142 and 1252 once, but after a reboot it joined fine.
I'm running 6.0.188.0 on 6 WISMs. The ap-manager that these APs keep trying to join only has 5 APs on it.

Can you get a sniffer trace of the port-channel to one of the WiSM, and if possible, the console of the AP? Also, check the MAC address of the AP(s) that are not joining to see if they start with something other than 00:, you may also want to check the MAC of the gw for those AP for the same thing.
The defect I'm thinking of is CSCte01087

Similar Messages

3502i APs not joining controller

So basically my infrastructure consists of four 4402 WLCs running on 7.0.235.3. I'm trying to get new access points to join to the environment, but I am having difficulty doing so. All currently joined APs work fine and are operating well. I'm getting a red, green, off blink code which means it's trying to join, but never does. The other one I get a constantly blinking green but it never joins either. I've setup option 43 in DHCP, added cisco-capwap-controller entries in DNS thinking it was because those are missing, and still cannot get these two access points to join. Can anyone think why it would not be joining?
The access points and WLC are all on the Same VLAN by the way.

Hello,
In a Cisco Unified Wireless network, the LAPs must first discover and       join a WLC before they can service wireless clients.
Originally, the controllers only operated in Layer 2 mode. In Layer 2       mode, the LAPs are required to be on the same subnet as the management       interface and the Layer 3 mode AP-manager interface is not present on the       controller. The LAPs communicate with the controller using Layer 2       encapsulation only (ethernet encapsulation) and do not Dynamic Host       Configuration Protocol (DHCP) an IP address.
When Layer 3 mode on the controller was developed, a new Layer 3       interface called AP-manager was introduced. In Layer 3 mode, the LAPs would       DHCP an IP address first and then send their discovery request to the       management interface using IP addresses (Layer 3). This allowed the LAPs to be       on a different subnet than the management interface of the controller. Layer 3       mode is the dominate mode today. Some controllers and LAPs can only perform       Layer 3 mode.
However, this presented a new problem: how did the LAPs find the       management IP address of the controller when it was on a different subnet?
In Layer 2 mode, they were required to be on the same subnet. In Layer       3 mode, the controller and LAP are essentially playing hide and seek in the       network. If you do not tell the LAP where the controller is via DHCP option 43,       DNS resolution of "Cisco-lwapp-controller@local_domain", or statically       configure it, the LAP does not know where in the network to find the management       interface of the controller.
In addition to these methods, the LAP does automatically look on the       local subnet for controllers with a 255.255.255.255 local broadcast. Also, the       LAP remembers the management IP address of any controller it joins across       reboots. Therefore, if you put the LAP first on the local subnet of the       management interface, it will find the controller's management interface and       remember the address. This is called priming. This does not help find the       controller if you replace a LAP later on. Therefore, Cisco recommends using the       DHCP option 43 or DNS methods.
When the LAPs discover the controller, they do not know if the       controller is in Layer 2 mode or Layer 3 mode. Therefore, the LAPs always       connect to the management interface address of the controller first with a       discovery request. The controller then tells the LAP which mode it is in the       discovery reply. If the controller is in Layer 3 mode, the discovery reply       contains the Layer 3 AP-manager IP address so the LAP can send a join request       to the AP-manager interface next.
Note: By default both management and AP-manager interfaces are left           untagged on their VLAN during configuration. In case these are tagged, make           sure they are tagged to the same VLAN in order to properly receive discovery           and join response from the WLC.
The LWAPP AP goes through this process on startup for Layer 3       mode:
The LAP boots and DHCPs an IP address if it was not previously           assigned a static IP address.
The LAP sends discovery requests to controllers through the various           discovery algorithms and builds a controller list. Essentially, the LAP learns           as many management interface addresses for the controller list as possible via:
DHCP option 43 (good for global companies where offices and             controllers are on different continents)
DNS entry for             cisco-capwap-controller (good for local             businesses - can also be used to find where brand new APs join)
Note: If you use CAPWAP, make sure that there is a DNS entry for                 cisco-capwap-controller.
Management IP addresses of controllers the LAP remembers             previously
A Layer 3 broadcast on the subnet
Over the air provisioning
Statically configured information
From this list, the easiest method to use for deployment is to have           the LAPs on the same subnet as the management interface of the controller and           allow the LAP’s Layer 3 broadcast to find the controller. This method should be           used for companies that have a small network and do not own a local DNS           server.
The next easiest method of deployment is to use a DNS entry with           DHCP. You can have multiple entries of the same DNS name. This allows the LAP           to discover multiple controllers. This method should be used by companies that           have all of their controllers in a single location and own a local DNS server.           Or, if the company has multiple DNS suffixes and the controllers are segregated           by suffix.
DHCP option 43 is used by large companies to localize the information           via the DHCP. This method is used by large enterprises that have a single DNS           suffix. For example, Cisco owns buildings in Europe, Australia, and the United           States. In order to ensure that the LAPs only join controllers locally, Cisco           cannot use a DNS entry and must use DHCP option 43 information to tell the LAPs           what the management IP address of their local controller is.
Finally, static configuration is used for a network that does not           have a DHCP server.You can statically configure the information necessary to           join a controller via the console port and the AP’s CLI. For information on how           to statically configure controller information using the AP CLI, refer to           Manually           Configuring Controller Information Using the Access Point CLI.
For a detailed explanation on the different discovery algorithms that           LAPs use to find controllers, refer to           LAP           Registration with WLC.
For information on configuring DHCP option 43 on a DHCP server, refer           to           DHCP           OPTION 43 for Lightweight Cisco Aironet Access Points Configuration           Example.
Send a discovery request to every controller on the list and wait for           the controller's discovery reply which contains the system name, AP-manager IP           addresses, the number of APs already attached to each AP-manager interface, and           overall excess capacity for the controller.
Look at the controller list and send a join request to a controller           in this order (only if the AP received a discovery reply from it):
Primary Controller system name (previously configured on             LAP)
Secondary Controller system name (previously configured on             LAP)
Tertiary Controller system name (previously configured on             LAP)
Master controller (if the LAP has not been previously configured             with any Primary, Secondary, or Tertiary controller names. Used to always know             which controller brand new LAPs join)
If none of the above are seen, load balance across controllers             using the excess capacity value in the discovery response.
If two controllers have the same excess capacity, then send the             join request to the first controller that responded to the discovery request             with a discovery response. If a single controller has multiple AP-managers on             multiple interfaces, choose the AP-manager interface with the least number of             APs.
The controller will respond to all discovery requests without             checking certificates or AP credentials. However, join requests must have a             valid certificate in order to get a join response from the controller. If the             LAP does not receive a join response from its choice, the LAP will try the next             controller in the list unless the controller is a configured controller             (Primary/Secondary/Tertiary).
When it receives the join reply, the AP checks to make sure it has           the same image as that of the controller. If not, the AP downloads the image           from the controller and reboots to load the new image and starts the process           all over again from step 1.
If it has the same software image, it asks for the configuration from           the controller and moves into the registered state on the controller.
After you download the configuration, the AP might reload again to           apply the new configuration. Therefore, an extra reload can occur and is a           normal behavior.

APs not joining controller

I upgraded a controller yesterday 5508 it went from a low code version 6.x to 6.0.196.0 then to 7.0.116.0. However although all the access points joined code 6.0.196.0 they refused to join 7.0.116.0. The aps are all 1242s.
The country codes etc were all fine so I do not understand what was going on.
Any ideas?
*spamApTask0: Jun 26 16:07:44.734: 00:3a:99:db:f3:20 Discovery Request from 10.0.0.183:55065
*spamApTask0: Jun 26 16:07:44.734: 00:3a:99:db:f3:20 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask0: Jun 26 16:07:44.735: 00:3a:99:db:f3:20 Discovery Response sent to 10.0.0.183:55065
*spamApTask0: Jun 26 16:07:44.735: 00:3a:99:db:f3:20 Received LWAPP DISCOVERY REQUEST to e8:b7:48:9b:86:4f on port '13'
*spamApTask0: Jun 26 16:07:44.735: 00:3a:99:db:f3:20 Discarding discovery request in LWAPP from AP supporting CAPWAP
*spamApTask0: Jun 26 16:07:44.735: 00:3a:99:db:f3:20 Discovery Request from 10.0.0.183:55065
*spamApTask0: Jun 26 16:07:44.735: 00:3a:99:db:f3:20 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask0: Jun 26 16:07:44.735: 00:3a:99:db:f3:20 Discovery Response sent to 10.0.0.183:55065
*spamApTask7: Jun 26 16:07:45.308: 00:3a:99:db:fa:20 Discovery Request from 10.0.0.95:55080
*spamApTask7: Jun 26 16:07:45.308: 00:3a:99:db:fa:20 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask0: Jun 26 16:07:45.308: 00:3a:99:db:fa:20 Received LWAPP DISCOVERY REQUEST to e8:b7:48:9b:86:4f on port '13'
*spamApTask0: Jun 26 16:07:45.308: 00:3a:99:db:fa:20 Discarding discovery request in LWAPP from AP supporting CAPWAP
*spamApTask7: Jun 26 16:07:45.308: 00:3a:99:db:fa:20 Discovery Response sent to 10.0.0.95:55080
*spamApTask7: Jun 26 16:07:45.309: 00:3a:99:db:fa:20 Discovery Request from 10.0.0.95:55080
*spamApTask7: Jun 26 16:07:45.309: 00:3a:99:db:fa:20 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask7: Jun 26 16:07:45.309: 00:3a:99:db:fa:20 Discovery Response sent to 10.0.0.95:55080
*spamApTask7: Jun 26 16:07:45.511: 00:13:c3:e1:4c:e0 Discovery Request from 10.0.1.232:20023
*spamApTask7: Jun 26 16:07:45.511: 00:13:c3:e1:4c:e0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask7: Jun 26 16:07:45.511: 00:13:c3:e1:4c:e0 Discovery Response sent to 10.0.1.232:20023
*spamApTask0: Jun 26 16:07:45.511: 00:13:c3:e1:4c:e0 Received LWAPP DISCOVERY REQUEST to e8:b7:48:9b:86:4f on port '13'
*spamApTask0: Jun 26 16:07:45.511: 00:13:c3:e1:4c:e0 Discarding discovery request in LWAPP from AP supporting CAPWAP
*spamApTask7: Jun 26 16:07:45.512: 00:13:c3:e1:4c:e0 Discovery Request from 10.0.1.232:20023
*spamApTask7: Jun 26 16:07:45.512: 00:13:c3:e1:4c:e0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask7: Jun 26 16:07:45.512: 00:13:c3:e1:4c:e0 Discovery Response sent to 10.0.1.232:20023
*spamApTask4: Jun 26 16:07:46.516: 00:3a:99:db:fa:10 DTLS connection not found, creating new connection for 10:0:0:101 (55079) 10:0:1:45 (5246)
*spamApTask4: Jun 26 16:07:46.708: 00:3a:99:db:fa:10 DTLS connection closed event receivedserver (10:0:1:45/5246) client (10:0:0:101/55079)
*spamApTask4: Jun 26 16:07:46.708: 00:3a:99:db:fa:10 No entry exists for AP (10:0:0:101/55079)
*spamApTask4: Jun 26 16:07:46.708: 00:3a:99:db:fa:10 No entry exists in database
*spamApTask4: Jun 26 16:07:47.759: 00:3a:99:db:fa:a0 Discovery Request from 10.0.0.184:55084
*spamApTask4: Jun 26 16:07:47.759: 00:3a:99:db:fa:a0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask0: Jun 26 16:07:47.760: 00:3a:99:db:fa:a0 Received LWAPP DISCOVERY REQUEST to e8:b7:48:9b:86:4f on port '13'
*spamApTask0: Jun 26 16:07:47.760: 00:3a:99:db:fa:a0 Discarding discovery request in LWAPP from AP supporting CAPWAP
*spamApTask4: Jun 26 16:07:47.760: 00:3a:99:db:fa:a0 Discovery Response sent to 10.0.0.184:55084
*spamApTask4: Jun 26 16:07:47.760: 00:3a:99:db:fa:a0 Discovery Request from 10.0.0.184:55084
*spamApTask4: Jun 26 16:07:47.760: 00:3a:99:db:fa:a0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask4: Jun 26 16:07:47.760: 00:3a:99:db:fa:a0 Discovery Response sent to 10.0.0.184:55084
*spamApTask7: Jun 26 16:07:49.471: 00:13:c3:e1:4d:c0 Discovery Request from 10.0.1.239:20032
*spamApTask7: Jun 26 16:07:49.471: 00:13:c3:e1:4d:c0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask7: Jun 26 16:07:49.471: 00:13:c3:e1:4d:c0 Discovery Response sent to 10.0.1.239:20032
*spamApTask0: Jun 26 16:07:49.471: 00:13:c3:e1:4d:c0 Received LWAPP DISCOVERY REQUEST to e8:b7:48:9b:86:4f on port '13'
*spamApTask0: Jun 26 16:07:49.471: 00:13:c3:e1:4d:c0 Discarding discovery request in LWAPP from AP supporting CAPWAP
*spamApTask7: Jun 26 16:07:49.472: 00:13:c3:e1:4d:c0 Discovery Request from 10.0.1.239:20032
*spamApTask7: Jun 26 16:07:49.472: 00:13:c3:e1:4d:c0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask7: Jun 26 16:07:49.472: 00:13:c3:e1:4d:c0 Discovery Response sent to 10.0.1.239:20032
*spamApTask1: Jun 26 16:07:52.222: 00:13:c3:e1:4d:80 Discovery Request from 10.0.1.230:20027
*spamApTask1: Jun 26 16:07:52.222: 00:13:c3:e1:4d:80 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask1: Jun 26 16:07:52.223: 00:13:c3:e1:4d:80 Discovery Response sent to 10.0.1.230:20027
*spamApTask0: Jun 26 16:07:52.223: 00:13:c3:e1:4d:80 Received LWAPP DISCOVERY REQUEST to e8:b7:48:9b:86:4f on port '13'
*spamApTask0: Jun 26 16:07:52.223: 00:13:c3:e1:4d:80 Discarding discovery request in LWAPP from AP supporting CAPWAP
*spamApTask1: Jun 26 16:07:52.223: 00:13:c3:e1:4d:80 Discovery Request from 10.0.1.230:20027
*spamApTask1: Jun 26 16:07:52.223: 00:13:c3:e1:4d:80 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask1: Jun 26 16:07:52.224: 00:13:c3:e1:4d:80 Discovery Response sent to 10.0.1.230:20027
*spamApTask5: Jun 26 16:07:52.267: 00:3a:99:da:c7:70 DTLS connection not found, creating new connection for 10:0:0:181 (34152) 10:0:1:45 (5246)
*spamApTask1: Jun 26 16:07:52.274: 00:3a:99:db:ff:20 Discovery Request from 10.0.0.182:55099
*spamApTask1: Jun 26 16:07:52.274: 00:3a:99:db:ff:20 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask0: Jun 26 16:07:52.274: 00:3a:99:db:ff:20 Received LWAPP DISCOVERY REQUEST to e8:b7:48:9b:86:4f on port '13'
*spamApTask1: Jun 26 16:07:52.274: 00:3a:99:db:ff:20 Discovery Response sent to 10.0.0.182:55099
*spamApTask0: Jun 26 16:07:52.274: 00:3a:99:db:ff:20 Discarding discovery request in LWAPP from AP supporting CAPWAP
*spamApTask1: Jun 26 16:07:52.275: 00:3a:99:db:ff:20 Discovery Request from 10.0.0.182:55099
*spamApTask1: Jun 26 16:07:52.275: 00:3a:99:db:ff:20 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask1: Jun 26 16:07:52.275: 00:3a:99:db:ff:20 Discovery Response sent to 10.0.0.182:55099
*spamApTask1: Jun 26 16:07:52.306: 00:3a:99:db:f2:40 DTLS connection not found, creating new connection for 10:0:0:100 (55069) 10:0:1:45 (5246)
*spamApTask5: Jun 26 16:07:52.463: 00:3a:99:da:c7:70 DTLS connection closed event receivedserver (10:0:1:45/5246) client (10:0:0:181/34152)
*spamApTask5: Jun 26 16:07:52.463: 00:3a:99:da:c7:70 No entry exists for AP (10:0:0:181/34152)
*spamApTask5: Jun 26 16:07:52.463: 00:3a:99:da:c7:70 No entry exists in database
*spamApTask1: Jun 26 16:07:52.501: 00:3a:99:db:f2:40 DTLS connection closed event receivedserver (10:0:1:45/5246) client (10:0:0:100/55069)
*spamApTask1: Jun 26 16:07:52.502: 00:3a:99:db:f2:40 No entry exists for AP (10:0:0:100/55069)
*spamApTask1: Jun 26 16:07:52.502: 00:3a:99:db:f2:40 No entry exists in database

Something "weird" is on the newest 7.0.X. Here's my situation:
1. It doesn't happen to all new APs. When I mean "new", I mean out from a box including APs from RMA.
2. I've seen this in 1240, 1250, 1140. Haven't seen it on a 3500.
3. Here's how it goes ... When the AP, fresh from a box, connects to the networks, sees the WLC/WiSM and downloads the full IOS (OK so far). After the reboot the AP in question loads the new IOS and shows up in the WLC/WiSM. When I check CDP neighbors, NOTHING. What the ... ?
4. Go to the switch and do command "sh cdp neighbor" and what do I get? NOTHING.
5. Check PoE and show that it's IEEE.
For unknown reason, APs in this "trance" shuts off the CDP. I currently have a Cisco TAC Case trying to iron out this "feature". Doesn't appear on the 7.0.96.0 but happens to the newer one.

1242 is not joining controller

hello friends,
i have 1240 series access points which is not joining controller 5500 series..
here is logs at joining time below
AP503d.e56e.e7be#Xmodem file system is available.
flashfs[0]: 7 files, 2 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
flashfs[0]: Total bytes: 15998976
flashfs[0]: Bytes used: 2649600
flashfs[0]: Bytes available: 13349376
flashfs[0]: flashfs fsck took 25 seconds.
Base ethernet MAC Address: 50:3d:e5:6e:e7:be
Initializing ethernet port 0...
Reset ethernet port 0...
Reset done!
ethernet link up, 100 mbps, full-duplex
Ethernet port 0 initialized: link is up
button is pressed, wait for button to be released...
button pressed for 37 seconds
process_config_recovery: set IP address and config to default 10.0.0.1
process_config_recovery: image recovery
image_recovery: Download default IOS tar image tftp://255.255.255.255/c1240-k9w7-tar.default
examining image...
%Error opening (connection timed out)Loading "flash:/c1240-rcvk9w8-mx/c1240-rcvk9w8-mx"...#############################################################################################################################################
File "flash:/c1240-rcvk9w8-mx/c1240-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, C1240 Software (C1240-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 18:40 by prod_rel_team
Proceeding with system init
Proceeding to unmask interrupts
Initializing flashfs...
flashfs[1]: 6 files, 2 directories
flashfs[1]: 0 orphaned files, 0 orphaned directories
flashfs[1]: Total bytes: 15998976
flashfs[1]: Bytes used: 2632192
flashfs[1]: Bytes available: 13366784
flashfs[1]: flashfs fsck took 4 seconds.
flashfs[1]: Initialization complete....done Initializing flashfs.
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
[email protected].
cisco AIR-LAP1242AG-E-K9   (PowerPCElvis) processor (revision A0) with 24566K/8192K bytes of memory.
Processor board ID FCZ150482DL
PowerPCElvis CPU at 262Mhz, revision number 0x0950
Last reset from power-on
LWAPP image version 3.0.51.0
1 FastEthernet interface
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 50:3D:E5:6E:E7:BE
Part Number                          : 73-10256-07
PCA Assembly Number                  : 800-26918-06
PCA Revision Number                  : A0
PCB Serial Number                    : FOC150158MH
Top Assembly Part Number             : 800-29152-03
Top Assembly Serial Number           : FCZ150482DL
Top Revision Number                  : A0
Product/Model Number                 : AIR-LAP1242AG-E-K9
% Please define a domain-name first.
Press RETURN to get started!
*Mar 1 00:00:05.426: %LWAPP-3-CLIENTEVENTLOG: Read and initialized AP event log (contains, 34 messages)
*Mar 1 00:00:07.500: %LINK-3-UPDOWN: Interface FastEthernet0, changed state to up
*Mar 1 00:00:07.526: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C1240 Software (C1240-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 18:40 by prod_rel_team
*Mar 1 00:00:07.601: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Mar 1 00:00:08.500: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to down
*Mar 1 00:00:12.979: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to up
AP503d.e56e.e7be#
*Mar 1 00:00:46.445: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!
AP503d.e56e.e7be#
AP503d.e56e.e7be#
AP503d.e56e.e7be#sh ver
Cisco IOS Software, C1240 Software (C1240-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 18:40 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)
AP503d.e56e.e7be uptime is 0 minutes
System returned to ROM by power-on
System image file is "flash:/c1240-rcvk9w8-mx/c1240-rcvk9w8-mx"
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
[email protected].
cisco AIR-LAP1242AG-E-K9   (PowerPCElvis) processor (revision A0) with 24566K/8192K bytes of memory.
Processor board ID FCZ150482DL
PowerPCElvis CPU at 262Mhz, revision number 0x0950
Last reset from power-on
LWAPP image version 3.0.51.0
1 FastEthernet interface
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 50:3D:E5:6E:E7:BE
Part Number                          : 73-10256-07
PCA Assembly Number                  : 800-26918-06
PCA Revision Number                  : A0
PCB Serial Number                    : FOC150158MH
Top Assembly Part Number             : 800-29152-03
Top Assembly Serial Number           : FCZ150482DL
--More--
*Mar 1 00:00:56.445: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not haveTop Revision Number                  : A0
Product/Model Number                 : AIR-LAP1242AG-E-K9
Configuration register is 0xF
AP503d.e56e.e7be#
*Mar 1 00:01:06.445: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!
any advice please??
thanks

It sounds like you are still working out IP connectivity, but I also noticed your AP is not for US regulatory domain.
Can you confirm that your WLC is ready to accept an AP with country code -E?
Your AP model: AIR-LAP1242AG-E-K9
From the WLC CLI
>show country
If you are in US, you should only have -A available. If this AP is intended to be used the US, then you will need to acquire an AP with the correct country code, as -E would not be supported in the US -A regulatory domain and should not be used. Perhaps this is for another location, so you may need to add the applicable regulatory domain support.
This link provides the list of the respective country codes and compatbility/etc.
http://www.cisco.com/en/US/prod/collateral/wireless/ps5679/ps5861/product_data_sheet0900aecd80537b6a_ps6087_Products_Data_Sheet.html

APs not joining 5508 on dynamic ports created manualy

Hey all,
i have a problem with our new 5508 wireless controller (7.0.116.0).
Port 1 is the system default "management" (Port 2 is backup). Dynamic AP Management is disabled.
Port 3 is a new dynamic interface "ap-manager 2" with Dynamic AP Management enabled and has a ip in a seperated VLAN which is not routed.
When i am connecting the AP (1260 series) to the "ap-manager 2" interface, then it will not join and i get an error message on the WLC:
*spamApTask1: Mar 05 14:52:12.783: %CAPWAP-3-DISC_INTF_ERR1:
capwap_ac_sm.c:1453 Ignoring discovery request received on non-management
interface (3) from AP
When i am connecting the AP to the "management2 interface, then it is working fine. But i don't want the APs in the Management LAN. I want them in the separated no routed LAN explicit for the APs.
What do i miss here.
Thanks a lot.
Regards
Matthew

Hmmm...but i found follwoing in the documentation:
The AP-manager interface's IP address must be different from the management interface's IP address and may or may not be on the same subnet as the management interface. However, we recommend that both interfaces be on the same subnet for optimum access point association.
I want the APs in a separated non routed LAN because of security reasons. Why set APs into the management LAN when they only need to communicate with the controller?
But if there is no way to do that, then i need to redesign the plans for the WLAN structure.
Thanks
Matthew

Cisco APs not joining WLC

Hi guys,
I am in the process of configuring a WLC and got stuck due to APs are not joining the WLC.
I have configure DHCP server on the Gateway router and the WLC management interface is pointing to the Gateway as DHCP Server.
I have multiple Dynamic interfaces configured on the WLC and Interface group has been configured and mapped to Management Interface.
For each WLAN, a separate DHCP pool has been created on the router.
LAG has been configured and working fine. Connectivity works fine in the network and I can ping all devices and vlans from WLC.
Now, the APs are not joining the WLC. The error I am getting
" 44:03:a7:f1:b4:40 Received a Discovery Request from 44:03:A7:F1:B4:40 via IP broadcast address but the source IP address (10.xx.xx.xx) is not in any of the configured subnets. Dropping it "
Some one help me troubleshooting this issue with DHCP IP Assignment.
Thanks,
CJ

If you are using Broadcast method to discover WLC to AP then you need to ensure following is correctly configured.
1. Unders the switch SVI defined for AP-management (10.38.11.x) you have to configure "ip helper-address "
2. In switch global config "ip forward-protocol udp 5246"
Refer this for more detail
http://mrncciew.com/2013/05/04/wlc-discovery-via-broadcast/
There are other methods available as well (static, DNS, DHCP option 43) for the WLC discovery purpose. To verify there is no configuration issues at WLC end, you can simply configure the WLC details on AP statically & check wether AP get register to WLC. To do this you can enter following CLI commands on AP console priviledge mode.
debug capwap console cli
capwap ap ip address 10.38.11.x 255.255.255.x
capwap ap ip default-gateway 10.38.11.y
capwap ap controller ip address
In this way your AP should get registered to WLC (if no config issue at WLC end). Refer this for more detail
http://mrncciew.com/2013/03/17/ap-registration/
If you have so many APs, then as Steve pointed configuring DHCP-Option 43 would be a good option
Regards
Rasika
**** Pls rate all useful responses ****

Wireless AP not joining Controller

Hi,
I am facing an issue with my AP not joining the controller.
Following is the error log
Mar 1 00:01:11.923: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Mar 1 00:01:21.923: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Apr 3 08:10:04.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.146.47.150 peer_port: 5246
*Apr 3 08:10:26.775: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
*Apr 3 08:10:33.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2051 Max retransmission count reached!
*Apr 3 08:11:03.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.146.47.150:5246
*Apr 3 08:11:03.999: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Apr 3 08:10:04.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.146.47.150 peer_port: 5246

Hi Guys,
Thanks for your inputs.
I investigated the issue suspecting a problem with the communication between the WLC and the APs. Actually the WLC is connected to 2 6506 chassis with the 1st chassis as the root.
I discovered a minor error on the module in the 1st chassis. When i connected to the 2nd chassis. The AP was able to join the controller. Outputs for the faulty module as below:
Looks like I will need to RMA the module.
Router#sh module
Mod Ports Card Type Model Serial No.
1 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX SAL1743F20V
2 16 CEF720 16 port 10GE WS-X6716-10GE SAL1746G9RS
3 16 CEF720 16 port 10GE WS-X6716-10GE SAL1746G9QR
5 5 Supervisor Engine 720 10GE (Active) VS-S720-10G SAL1746GC1G
Mod MAC addresses Hw Fw Sw Status
1 7c69.f690.8908 to 7c69.f690.8937 4.3 12.2(18r)S1 12.2(33)SXJ6 Ok
2 7c69.f690.badc to 7c69.f690.baeb 2.1 12.2(18r)S1 12.2(33)SXJ6 Ok
3 e4d3.f1a4.39f8 to e4d3.f1a4.3a07 2.1 12.2(18r)S1 12.2(33)SXJ6 Ok
5 5057.a8e3.394a to 5057.a8e3.3951 4.1 8.5(4) 12.2(33)SXJ6 Ok
Mod Sub-Module Model Serial Hw Status
1 Centralized Forwarding Card WS-F6700-CFC SAL1746GAAX 4.1 Ok
2 Distributed Forwarding Card WS-F6700-DFC3C SAL1746G6T1 1.6 Ok
3 Distributed Forwarding Card WS-F6700-DFC3C SAL1746G844 1.6 Ok
5 Policy Feature Card 3 VS-F6K-PFC3C SAL1746GBJK 1.2 Ok
5 MSFC3 Daughterboard VS-F6K-MSFC3 SAL1746GAGT 5.1 Ok
Mod Online Diag Status
1 Minor Error
2 Pass
3 Pass
5 Pass
Router#sh diagnostic result module 1
Current bootup diagnostic level: minimal
Module 1: CEF720 48 port 10/100/1000mb Ethernet SerialNo : SAL1743F20V
Overall Diagnostic Result for Module 1 : MINOR ERROR
Diagnostic level at card bootup: minimal
Test results: (. = Pass, F = Fail, U = Untested)
1) TestLoopback:
Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
Port 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
2) TestTxPathMonitoring ------------> .
3) TestSynchedFabChannel -----------> .
4) TestL3VlanMet -------------------> F
5) TestIngressSpan -----------------> .
6) TestEgressSpan ------------------> .
7) TestAsicMemory ------------------> U
8) TestEobcStressPing --------------> U
9) TestFirmwareDiagStatus ----------> .
10) TestAsicSync --------------------> .
11) TestUnusedPortLoopback:
Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
U U U U U U U U U U U . U U U U U U U U U U U .
Port 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
U U U U U U U U U U U . U U U U U U U U U U U .
12) TestOBFL ------------------------> .
13) TestErrorCounterMonitor ---------> .
14) TestPortTxMonitoring:
Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
U U U U U U U U U U U U U U U U U U U U U U U U
Port 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
U U U U U U U U U U U U U U U U U U U U U U U U
15) TestLtlFpoeMemoryConsistency ----> .
16) TestRwEngineOverSubscription ----> U
Router#sh diagnostic result module 1 detail
Current bootup diagnostic level: minimal
Module 1: CEF720 48 port 10/100/1000mb Ethernet SerialNo : SAL1743F20V
Overall Diagnostic Result for Module 1 : MINOR ERROR
Diagnostic level at card bootup: minimal
Test results: (. = Pass, F = Fail, U = Untested)
1) TestLoopback:
Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
Port 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> Apr 01 2014 10:55:39
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Apr 01 2014 10:55:39
Total failure count ---------> 0
Consecutive failure count ---> 0
2) TestTxPathMonitoring ------------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 40
Last test testing type ------> Health Monitoring
Last test execution time ----> Apr 01 2014 10:57:30
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Apr 01 2014 10:57:30
Total failure count ---------> 0
Consecutive failure count ---> 0
3) TestSynchedFabChannel -----------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 39
Last test testing type ------> Health Monitoring
Last test execution time ----> Apr 01 2014 10:57:30
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Apr 01 2014 10:57:30
Total failure count ---------> 0
Consecutive failure count ---> 0
4) TestL3VlanMet -------------------> F
Error code ------------------> 54 (DIAG_CHECK_UDP_PAK_ERROR)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> Apr 01 2014 10:55:53
First test failure time -----> Apr 01 2014 10:55:53
Last test failure time ------> Apr 01 2014 10:55:53
Last test pass time ---------> n/a
Total failure count ---------> 1
Consecutive failure count ---> 1
5) TestIngressSpan -----------------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> Apr 01 2014 10:56:05
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Apr 01 2014 10:56:05
Total failure count ---------> 0
Consecutive failure count ---> 0
6) TestEgressSpan ------------------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> Apr 01 2014 10:56:05
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Apr 01 2014 10:56:05
Total failure count ---------> 0
Consecutive failure count ---> 0
7) TestAsicMemory ------------------> U
Error code ------------------> 3 (DIAG_SKIPPED)
Total run count -------------> 0
Last test testing type ------> n/a
Last test execution time ----> n/a
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> n/a
Total failure count ---------> 0
Consecutive failure count ---> 0
8) TestEobcStressPing --------------> U
Error code ------------------> 3 (DIAG_SKIPPED)
Total run count -------------> 0
Last test testing type ------> n/a
Last test execution time ----> n/a
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> n/a
Total failure count ---------> 0
Consecutive failure count ---> 0
9) TestFirmwareDiagStatus ----------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> Apr 01 2014 10:56:05
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Apr 01 2014 10:56:05
Total failure count ---------> 0
Consecutive failure count ---> 0
10) TestAsicSync --------------------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 5
Last test testing type ------> Health Monitoring
Last test execution time ----> Apr 01 2014 10:57:21
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Apr 01 2014 10:57:21
Total failure count ---------> 0
Consecutive failure count ---> 0
11) TestUnusedPortLoopback:
Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
U U U U U U U U U U U . U U U U U U U U U U U .
Port 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
U U U U U U U U U U U . U U U U U U U U U U U .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Health Monitoring
Last test execution time ----> Apr 01 2014 10:57:06
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Apr 01 2014 10:57:06
Total failure count ---------> 0
Consecutive failure count ---> 0
12) TestOBFL ------------------------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> Apr 01 2014 10:56:05
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Apr 01 2014 10:56:05
Total failure count ---------> 0
Consecutive failure count ---> 0
13) TestErrorCounterMonitor ---------> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 2
Last test testing type ------> Health Monitoring
Last test execution time ----> Apr 01 2014 10:57:06
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Apr 01 2014 10:57:06
Total failure count ---------> 0
Consecutive failure count ---> 0
Error Records ---------------> n/a
14) TestPortTxMonitoring:
Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
U U U U U U U U U U U U U U U U U U U U U U U U
Port 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
U U U U U U U U U U U U U U U U U U U U U U U U
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Health Monitoring
Last test execution time ----> Apr 01 2014 10:57:21
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Apr 01 2014 10:57:21
Total failure count ---------> 0
Consecutive failure count ---> 0
15) TestLtlFpoeMemoryConsistency ----> .
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 5
Last test testing type ------> Health Monitoring
Last test execution time ----> Apr 01 2014 10:57:21
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> Apr 01 2014 10:57:21
Total failure count ---------> 0
Consecutive failure count ---> 0
16) TestRwEngineOverSubscription ----> U
Error code ------------------> 3 (DIAG_SKIPPED)
Total run count -------------> 0
Last test testing type ------> n/a
Last test execution time ----> n/a
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> n/a
Total failure count ---------> 0
Consecutive failure count ---> 0
Router#sh diagnostic result module 1 failure
Current bootup diagnostic level: minimal
Module 1: CEF720 48 port 10/100/1000mb Ethernet SerialNo : SAL1743F20V
Overall Diagnostic Result for Module 1 : MINOR ERROR
Diagnostic level at card bootup: minimal
Test results: (. = Pass, F = Fail, U = Untested)
4) TestL3VlanMet -------------------> F

1140 AP not joining controller

I have 3 AP's setup on my network and each port is configured the same exact way on the switches. One AP joined the controller fine but the other two are not joning it. They get the IP address but that is about it. When I go and check for the statistics on the WLC it tells me that they are not joined. Here is what the DEBUG shows:
*spamApTask5: Apr 18 18:13:01.198: c4:71:fe:8f:da:dc CAPWAP Control Msg Received from 10.230.129.113:60844
*spamApTask5: Apr 18 18:13:01.198: c4:71:fe:8f:da:dc packet received of length 97 from 10.230.129.113:60844
*spamApTask5: Apr 18 18:13:01.198: c4:71:fe:8f:da:dc Msg Type = 1 Capwap state = 0
*spamApTask5: Apr 18 18:13:01.198: c4:71:fe:8f:da:dc Discovery Request from 10.230.129.113:60844
*spamApTask5: Apr 18 18:13:01.198: c4:71:fe:8f:da:dc msgEleLength = 1 msgEleType = 20
*spamApTask5: Apr 18 18:13:01.198: c4:71:fe:8f:da:dc Total msgEleLen = 68
*spamApTask5: Apr 18 18:13:01.198: c4:71:fe:8f:da:dc msgEleLength = 40 msgEleType = 39
*spamApTask5: Apr 18 18:13:01.198: c4:71:fe:8f:da:dc Total msgEleLen = 24
*spamApTask5: Apr 18 18:13:01.198: c4:71:fe:8f:da:dc msgEleLength = 1 msgEleType = 41
*spamApTask5: Apr 18 18:13:01.198: c4:71:fe:8f:da:dc Total msgEleLen = 19
*spamApTask5: Apr 18 18:13:01.198: c4:71:fe:8f:da:dc msgEleLength = 1 msgEleType = 44
*spamApTask5: Apr 18 18:13:01.198: c4:71:fe:8f:da:dc Total msgEleLen = 14
*spamApTask5: Apr 18 18:13:01.199: c4:71:fe:8f:da:dc msgEleLength = 10 msgEleType = 37
*spamApTask5: Apr 18 18:13:01.199: c4:71:fe:8f:da:dc Vendor specific payload from AP C4:71:FE:8F:DA:DC validated
*spamApTask5: Apr 18 18:13:01.199: c4:71:fe:8f:da:dc Total msgEleLen = 0
*spamApTask5: Apr 18 18:13:01.199: c4:71:fe:8f:da:dc Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 12, joined Aps =1
*spamApTask5: Apr 18 18:13:01.199: c4:71:fe:8f:da:dc 1. 1 0
*spamApTask5: Apr 18 18:13:01.199: c4:71:fe:8f:da:dc 2. 232 3
*spamApTask5: Apr 18 18:13:01.199: c4:71:fe:8f:da:dc 3. 1 0
*spamApTask5: Apr 18 18:13:01.199: c4:71:fe:8f:da:dc 4. 12 0
*spamApTask5: Apr 18 18:13:01.199: c4:71:fe:8f:da:dc Discovery resp: AC Descriptor message element len = 40
*spamApTask5: Apr 18 18:13:01.199: c4:71:fe:8f:da:dc acName = WLCNAME
*spamApTask5: Apr 18 18:13:01.199: c4:71:fe:8f:da:dc Discovery resp:AC Name message element length = 56
*spamApTask5: Apr 18 18:13:01.199: c4:71:fe:8f:da:dc Discovery resp: WTP Radio Information msg length = 65
*spamApTask5: Apr 18 18:13:01.199: c4:71:fe:8f:da:dc Discovery resp: CAPWAP Control IPV4 Address len = 85
*spamApTask5: Apr 18 18:13:01.199: c4:71:fe:8f:da:dc Discovery resp: CAPWAP Control IPV6 Address len = 107
*spamApTask5: Apr 18 18:13:01.199: c4:71:fe:8f:da:dc Discovery resp: Mwar type payload len = 118
*spamApTask5: Apr 18 18:13:01.199: c4:71:fe:8f:da:dc Discovery resp: Time sync payload len = 133
*spamApTask5: Apr 18 18:13:01.199: c4:71:fe:8f:da:dc Discovery Response sent to 10.230.129.113:60844
*spamApTask5: Apr 18 18:13:01.199: c4:71:fe:8f:da:dc WTP already released
Note: I have one "management interface" configured on 10.230.129.xxx network" Then I created two "AP Manager interfaces on the 10.230.129.xxx network and enabled dynamic AP Management on them".

Ok, right, thats because whenever you type ANY number it TAGs the packets with that vlan id. 0 leaves the traffic untagged.
So even if it that IP belongs to vlan 10, if the port is as native (untagged) then on the WLC side should be 0
Thats how it was designed.

Flexconnect AP not joining Controller

Hi Community ,
I have some flexconnect APs in remote side . But they are not able to join controller 5508 (7.6) and flexconnect is also showing down in PI.
Any reason ??

Hi Adam ,
Thanks for your reply .
Scenario is that we have 2 controllers in HQ . Controllers running IOS code 7.6 . APs are 1242 LAP . They were working fine just one week ago . But now I can see them they are not in the controller , though up . When I checked in PI , Flexconnect status showing down . Hope this will help .

LWAP not joining controller, but has downloaded software

Hi All,
I have four APs that when I powered on individually, they went into the downloading state and rebooted, now have the mac address APxxxx.xxxx.xxxx.cisco.com and can see this on my switch and cdp is working, but has not joined the controller?
I know that DHCP is set correctly as I have another AP on the switch/VLAN that is working?
Any ideas?
Many thx indeed,
Ken

To answer your specific question, there's no need to clear anything on the WLC. The access points should simply connect.
Did you upgrade these access points, and could this be a certificate issue? If they are upgraded 1100s or 1200s, you may need to add the SSCs generated during the upgrade process into the controller. This can be done under the Security tab.
If that's not the issue, I would try to connect the access points more directly by placing them on the management subnet. This will hopefully tell you whether there's a problem with your discovery method.
Have you looked at the access points to see their status according to their LEDs? Are they still seeking a controller? Is it possible that they've found a different controller somewhere else on the network?

Mesh AP 1524SB Not Joining Controller

Hello,
I'm just getting started here and have run into some problems.
I have a WLC 5508 running 7.0.116.0 and 1524SB access points.
I have a 3750 switch sitting between them hosting the DHCP.
The switch is using VLAN 1 and the management interface of the WLC is untagged.
The problem is that my APs will not join the controller. I don't even think they are getting an IP address.
When I console into the AP it seems to me that the boot process is interupted and the AP reboots.
I get this message:
*Mar 1 00:00:34.375: %SYS-5-RELOAD: Reload requested by Adj Process. Reload Reason: Mesh Reboots AP ....
*Mar 1 00:00:34.375: %LWAPP-5-CHANGED: CAPWAP changed state to DOWNWriting out the event log to nvram...
And then it reboots. I have attached the entire boot sequence.
Could someone help me out please?
Thanks,
Justin
PS if needed here is the dhcp config:
ip dhcp pool dhcp
   network 10.0.0.0 255.255.255.0
   default-router 10.0.0.254
   option 60 ascii "Cisco AP c1520"
   option 43 ip 10.0.0.1
where 10.0.0.1 is the ip of the management interface.

Assuming 10.0.0.1 is the controller's management IP address. For 1524SB Mesh AP, you can't use format of "option 43 ip 10.0.0.1", change it to "option 43 hex f1040a000001" on the 3750 switch and try again.

Ap not joining controller

i am trying to troubleshoot a 2125 WLC alongside a 1252 access point. The access point is not joining and the y both
have the same software image. See logs below:
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 5.2.193.0
RTOS Version..................................... 5.2.193.0
Bootloader Version............................... 4.0.191.0
Emergency Image Version.......................... 6.0.199.4
Build Type....................................... DATA + WPS
System Name...................................... Cisco_f4:f7:c0
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.828
IP Address....................................... 192.168.1.5
System Up Time................................... 6 days 2 hrs 42 mins 39 secs
System Timezone Location.........................
Current Boot License Level.......................
Next Boot License Level..........................
Configured Country............................... SI - Slovenia
Operating Environment............................ Commercial (0 to 40 C)
Internal Temp Alarm Limits....................... 0 to 65 C
--More-- or (q)uit
Internal Temperature............................. +49 C
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 3
3rd Party Access Point Support................... Disabled
Number of Active Clients......................... 0
Burned-in MAC Address............................ C8:4C:75:F4:F7:C0
(Cisco Controller) >show network summary
RF-Network Name............................. law school
Web Mode.................................... Disable
Secure Web Mode............................. Enable
Secure Web Mode Cipher-Option High.......... Disable
Secure Web Mode Cipher-Option SSLv2......... Enable
Secure Shell (ssh).......................... Enable
Telnet...................................... Disable
Ethernet Multicast Mode..................... Disable
Ethernet Broadcast Mode..................... Disable
AP Multicast Mode........................... Multicast Address : 0.0.0.0
IGMP snooping............................... Disabled
IGMP timeout................................ 60 seconds
User Idle Timeout........................... 300 seconds
ARP Idle Timeout............................ 300 seconds
Cisco AP Default Master..................... Disable
AP Join Priority............................ Disable
Mgmt Via Wireless Interface................. Enable
Mgmt Via Dynamic Interface.................. Enable
Bridge MAC filter Config.................... Enable
Bridge Security Mode........................ EAP
Mesh Full Sector DFS........................ Enable
Kindly advice what is missing?
many thanks

Console into the AP and post the output to the following commands:
1. sh version;
2. sh ip interface brief

APs not joining WLC

Hello community,
I hope you can help me with my problem.
I have a vWLC Firmware version: 7.4.121.0, I have also Aironet 1700Aps
I have successfully configured wlc with service and management interface. In the management network I can ping the vWLC managenemt interface as well the APs in this network. The firewall is also the DHCP Server for the management network. (It is working because APs get an IP address) The problem is the APs are not joining the vWLC. This is my first time I use WLC and APs. So they are completely new and not used before.
Here is the debug output of vWLC:
ApTask4: Feb 11 16:31:07.997: 84:80:2d:bd:fa:10 Finding DTLS connection to delete for AP (192:168:200:10/57250)
*spamApTask4: Feb 11 16:31:07.997: 84:80:2d:bd:fa:10 Disconnecting DTLS Capwap-Ctrl session 0x8faa580 for AP (192:168:200:10/57250)
*spamApTask4: Feb 11 16:31:07.997: 84:80:2d:bd:fa:10 CAPWAP State: Dtls tear down
*spamApTask4: Feb 11 16:31:07.998: 84:80:2d:bd:fa:10 DTLS connection closed event receivedserver (192:168:200:3/5246) client (192:168:200:10/57250)
*spamApTask4: Feb 11 16:31:07.998: 84:80:2d:bd:fa:10 Entry exists for AP (192:168:200:10/57250)
*spamApTask4: Feb 11 16:31:07.998: 84:80:2d:bd:fa:10 No AP entry exist in temporary database for 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.004: 84:80:2d:bd:fa:1e DTLS connection not found, creating new connection for 192:168:200:10 (57250) 192:168:200:3 (5246)
*spamApTask4: Feb 11 16:31:08.472: 84:80:2d:bd:fa:1e DTLS Session established server (192.168.200.3:5246), client (192.168.200.10:57250)
*spamApTask4: Feb 11 16:31:08.472: 84:80:2d:bd:fa:1e Starting wait join timer for AP: 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.477: 84:80:2d:bd:fa:10 Join Request from 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.477: 84:80:2d:bd:fa:1e Deleting AP entry 192.168.200.10:57250 from temporary database.
*spamApTask4: Feb 11 16:31:08.477: 84:80:2d:bd:fa:10 Finding DTLS connection to delete for AP (192:168:200:10/57250)
*spamApTask4: Feb 11 16:31:08.477: 84:80:2d:bd:fa:10 Disconnecting DTLS Capwap-Ctrl session 0x8faa720 for AP (192:168:200:10/57250)
*spamApTask4: Feb 11 16:31:08.477: 84:80:2d:bd:fa:10 CAPWAP State: Dtls tear down
*spamApTask4: Feb 11 16:31:08.479: 84:80:2d:bd:fa:10 DTLS connection closed event receivedserver (192:168:200:3/5246) client (192:168:200:10/57250)
*spamApTask4: Feb 11 16:31:08.479: 84:80:2d:bd:fa:10 Entry exists for AP (192:168:200:10/57250)
*spamApTask4: Feb 11 16:31:08.479: 84:80:2d:bd:fa:10 No AP entry exist in temporary database for 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.515: 84:80:2d:bd:fa:10 Discovery Request from 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.515: 84:80:2d:bd:fa:10 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 200, joined Aps =0
*spamApTask4: Feb 11 16:31:08.515: 84:80:2d:bd:fa:10 Discovery Response sent to 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.515: 84:80:2d:bd:fa:10 Discovery Response sent to 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.516: 84:80:2d:bd:fa:10 Discovery Request from 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.516: 84:80:2d:bd:fa:10 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 200, joined Aps =0
*spamApTask4: Feb 11 16:31:08.516: 84:80:2d:bd:fa:10 Discovery Response sent to 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.516: 84:80:2d:bd:fa:10 Discovery Response sent to 192.168.200.10:57250
*spamApTask0: Feb 11 16:31:08.516: 84:80:2d:bd:fa:1e Received LWAPP DISCOVERY REQUEST to 40:4a:03:79:d7:20 on port '1'
*spamApTask0: Feb 11 16:31:08.516: 84:80:2d:bd:fa:1e Discarding discovery request in LWAPP from AP supporting CAPWAP
Sadly I don`t have a debuging cable for the APs. Therefore I have no debuging output of the APs. (It is ordered ;-) )
But I hope the output of the APs is right now not important to solve this problem.
Thank you
//EDIT
On the firewall are no ports blocked

Okay I upgraded the vWLC to 8.0.110.0.
I looked in the event log of the vWLC. It was successfully discovered and also the new image version was send to the AP.
Sadly the Ap does not join to the vWLC.
*apfReceiveTask: Feb 12 09:53:35.640: WARP IEs: (12)
*apfReceiveTask: Feb 12 09:53:35.640: [0000] dd 0a 00 c0 b9 01 00 00 00 08 01 01
*apfReceiveTask: Feb 12 09:53:35.640: Wlan Feature status 0 for AP:84:80:2d:45:75:e0 (slotID 1)
*apfReceiveTask: Feb 12 09:53:35.640: Split tunnel status (Disabled) encoded in the vap payload for WLAN(1), AP:84:80:2d:45:75:e0 (slotID 1)
*spamApTask5: Feb 12 09:53:35.789: 84:80:2d:45:75:e0 Configuration Status from 192.168.200.10:57251
*spamApTask5: Feb 12 09:53:35.789: 84:80:2d:45:75:e0 CAPWAP State: Configure
*spamApTask5: Feb 12 09:53:35.789: 84:80:2d:45:75:e0 Updating IP info for AP 84:80:2d:45:75:e0 -- static 0, 192.168.200.10/255.255.255.0, gtw 192.168.200.3
*spamApTask5: Feb 12 09:53:35.789: 84:80:2d:45:75:e0 Updating IP 192.168.200.10 ===> 192.168.200.10 for AP 84:80:2d:45:75:e0
*spamApTask5: Feb 12 09:53:35.789: 84:80:2d:45:75:e0 Invalid length (9) countedlen 6 sizeUserPayload 277 for vendor-specific element 0x00409600-unknown (185) from AP 84:80:2D:45:75:E0
*spamApTask5: Feb 12 09:53:35.790: 84:80:2d:45:75:e0 Setting MTU to 1485
*spamApTask5: Feb 12 09:53:35.790: 84:80:2d:45:75:e0 Finding DTLS connection to delete for AP (192:168:200:10/57251)
*spamApTask5: Feb 12 09:53:35.790: 84:80:2d:45:75:e0 Disconnecting DTLS Capwap-Ctrl session 0xb947000 for AP (192:168:200:10/57251)
*spamApTask5: Feb 12 09:53:35.790: 84:80:2d:45:75:e0 CAPWAP State: Dtls tear down
*spamApTask5: Feb 12 09:53:35.791: 84:80:2d:45:75:e0 DTLS connection closed event receivedserver (192.168.200.3/5246) client (192.168.200.10/57251)
*spamApTask5: Feb 12 09:53:35.791: 84:80:2d:45:75:e0 Entry exists for AP (192.168.200.10/57251)
*spamApTask5: Feb 12 09:53:35.791: 84:80:2d:45:75:e0 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 84:80:2d:45:75:e0 slot 0
*spamApTask5: Feb 12 09:53:35.791: 84:80:2d:45:75:e0 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 84:80:2d:45:75:e0 slot 1
*spamApTask5: Feb 12 09:53:35.791: update ap status:84:80:2d:45:75:e0 ,index:60
*spamApTask5: Feb 12 09:53:35.791: 84:80:2d:45:75:e0 No AP entry exist in temporary database for 192.168.200.10:57251
*apfReceiveTask: Feb 12 09:53:35.792: 84:80:2d:45:75:e0 Deregister LWAPP event for AP 84:80:2d:45:75:e0 slot 0
*apfReceiveTask: Feb 12 09:53:35.792: 84:80:2d:45:75:e0 Deregister LWAPP event for AP 84:80:2d:45:75:e0 slot 1
*spamApTask4: Feb 12 09:53:35.918: 84:80:2d:45:75:e0 Discovery Request from 192.168.200.10:57250
*spamApTask4: Feb 12 09:53:35.918: 84:80:2d:45:75:e0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 200, joined Aps =0
*spamApTask4: Feb 12 09:53:35.918: apModel: AIR-CAP702I-C-K9
*spamApTask4: Feb 12 09:53:35.918: apType = 45 apModel: AIR-CAP702I-C-K9
*spamApTask4: Feb 12 09:53:35.918: 84:80:2d:45:75:e0 Discovery Response sent to 192.168.200.10 port 57250
*spamApTask4: Feb 12 09:53:35.918: 84:80:2d:45:75:e0 Discovery Response sent to 192.168.200.10:57250
*spamApTask4: Feb 12 09:53:35.919: 84:80:2d:45:75:e0 Discovery Request from 192.168.200.10:57250
*spamApTask4: Feb 12 09:53:35.919: 84:80:2d:45:75:e0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 200, joined Aps =0
*spamApTask4: Feb 12 09:53:35.919: apModel: AIR-CAP702I-C-K9
*spamApTask4: Feb 12 09:53:35.919: apType = 45 apModel: AIR-CAP702I-C-K9
*spamApTask4: Feb 12 09:53:35.919: 84:80:2d:45:75:e0 Discovery Response sent to 192.168.200.10 port 57250
*spamApTask4: Feb 12 09:53:35.919: 84:80:2d:45:75:e0 Discovery Response sent to 192.168.200.10:57250
Sadly I don`t understand what this debugging log says :-(
Maybe you can help me again
Thank you
//SOLUTION -----------------------------------------------------------------------------------------------------------------------------------------------------------
I found something on the internet, but for all people having also this problem here is the solution:
Change the country of your vWLC. Right now I am in China, so I changed it and then it was working flawlessly :-)
Step 1
Disable the 802.11 networks as follows:
Choose Wireless > 802.11a/n > Network.
Unselect the 802.11a Network Status check box.
Click Apply.
Choose Wireless > 802.11a/n > Network.
Unselect the 802.11b/g Network Status check box.
Click Apply.
Step 2
Choose Wireless > Country to open the Country page.
Thank you all for your help :-)
Paul

2602E not joining controller

hi All,
I have a scenario where my 2602E is not joining a controller in US. AP is in Netherlands.
AP: AIR-CAP2602E-E-K9
Logs on WLC 5508:
*spamApTask4: Jan 29 10:26:37.398: 18:9c:5d:9b:4d:00 Bridge AP can not join MultiCountry Controller: Bridge mode AP 10.130.90.11:63313 cannot be supported on Multi Country Controll
*spamApTask4: Jan 29 10:26:37.406: 18:9c:5d:9b:4d:00 State machine handler: Failed to process msg type = 3 state = 0 from 10.130.90.11:63313
is there a way i can change the bridge mode from this AP to normal or Local so that it can be useD?
Any help will be great.
thanks
Royce

check the following.

Reset 1510 AP not joining controller

Hi
I have a 3750 Controller with 1510 access points. I have 1 access point that will not join. I think it was configured as a remote with a fixed IP address but I don't know what that address is, and I think that it is not the right subnet. I think I need to re-prime the AP with new settings.
Unfortunately I suspect that it because it has a set IP address it will now not try to get a DHCP address and thus I cannot prime it using that method. Is there another way to reset the IP address on these units?
Many Thanks
LP

Hi Laurie,
We do not run 1510's so I can't verify this, but I did come across this info;
Misconfigured Access Point IP address
IP address misconfiguration can occur when you are re-addressing a segment of your mesh network and you start at the mesh access point connected to the wired network (RAP). To avoid this problem, always start the IP addressing changes from the farthest access point and work your way back to the root access point. This problem might also happen if you move equipment such as uninstalling an mesh access point and then redeploying with a different IP subnet in another physical location on the mesh network.
Another option to fix this misconfigured IP address is to physically take a controller in Layer 2 mode with a root access point to the location of the misconfigured mesh access point. Set the bridge group name for the root access point to match the misconfigured access point. Add the access point's MAC address to the controller's filter list and enable Zero Touch Configuration. When the misconfigured access point appears in the controller's Summary page, configure the access point with an IP address.
From this doc;
http://www.cisco.com/en/US/products/ps6548/products_quick_start09186a00806b5d00.html#wp39368
Hope this helps!
Rob

APs not joining controller errors

Similar Messages

Maybe you are looking for