Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

AP 1552E NOT JOINING WLC 2504

Hello,

I am currently having issue relating to my AP not joining the WLC. Have made the WLC the internal DHCP server and the AP has picked an IP Address but the below is what i get from the AP:

*Feb 14 22:48:56.707: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Feb 14 22:48:56.759: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Feb 14 22:48:56.783:  status of voice_diag_test from WLC is false

*Feb 14 22:49:12.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.1.2 peer_port: 5246

*Feb 14 22:49:12.000: %CAPWAP-5-CHANGED: CAPWAP changed state to

*Feb 14 22:49:12.663: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.1.2 peer_port: 5246

*Feb 14 22:49:12.663: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.2

*Feb 14 22:49:12.663: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*Feb 14 22:49:17.663: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.2

*Feb 14 22:49:17.663: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.1.2

*Feb 14 22:49:17.663: %DTLS-5-PEER_DISCONNECT: Peer 192.168.1.2 has closed connection.

*Feb 14 22:49:17.663: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.1.2:5246

*Feb 14 22:49:12.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.1.2 peer_port: 5246

*Feb 14 22:49:12.000: %CAPWAP-5-CHANGED: CAPWAP changed state to

*Feb 14 22:49:12.663: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.1.2 peer_port: 5246

*Feb 14 22:49:12.663: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.2

*Feb 14 22:49:12.663: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

% CDP is not supported on this interface, or for this encapsulation

*Feb 14 22:49:17.663: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.2

*Feb 14 22:49:17.663: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.1.2

*Feb 14 22:49:17.663: %DTLS-5-PEER_DISCONNECT: Peer 192.168.1.2 has closed connection.

*Feb 14 22:49:17.663: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.1.2:5246

*Feb 14 22:49:17.707: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Feb 14 22:49:17.707: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Feb 14 22:49:17.759: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Feb 14 22:49:17.783:  status of voice_diag_test from WLC is false

*Feb 14 22:49:34.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.1.2 peer_port: 5246

*Feb 14 22:49:34.000: %CAPWAP-5-CHANGED: CAPWAP changed state to

*Feb 14 22:49:34.663: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.1.2 peer_port: 5246

*Feb 14 22:49:34.663: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.2

*Feb 14 22:49:34.663: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*Feb 14 22:49:39.663: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.2

*Feb 14 22:49:39.663: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.1.2

*Feb 14 22:49:39.663: %DTLS-5-PEER_DISCONNECT: Peer 192.168.1.2 has closed connection.

*Feb 14 22:49:39.663: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.1.2:5246

*Feb 14 22:49:34.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.1.2 peer_port: 5246

*Feb 14 22:49:34.000: %CAPWAP-5-CHANGED: CAPWAP changed state to

*Feb 14 22:49:34.663: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.1.2 peer_port: 5246

*Feb 14 22:49:34.663: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.2

*Feb 14 22:49:34.663: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*Feb 14 22:49:38.591: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired

*Feb 14 22:49:38.591: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired

*Feb 14 22:49:38.591: %MESH-6-LINK_UPDOWN: Mesh station f029.29c2.effc link Down

*Feb 14 22:49:39.663: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.2

25 REPLIES
VIP Purple

AP 1552E NOT JOINING WLC 2504

Hi

*Feb 14 22:49:38.591: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired

*Feb 14 22:49:38.591: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired

*Feb 14 22:49:38.591: %MESH-6-LINK_UPDOWN: Mesh station f029.29c2.effc link Down

Your AP has come with MESH image. So you have to add your AP ethernet MAC address to WLC MAC Filter (SECURITY -> MAC Filtering in WLC GUI) & then it should register. Once register, you can change AP mode to Local mode (from Mesh mode)

HTH

Rasika

*** Pls rate all useful responses ****

New Member

AP 1552E NOT JOINING WLC 2504

Thanks for the response but i have don't that already. Please the image below.

Two challenges am facing is (1) that i can't seem to be able to access the CLI of my AP because I don't have the login credential (2) Even though i have created the MAC Auth-list on the WLC i am not still able to have the AP join the WLC.

AP.JPG

VIP Purple

Re: AP 1552E NOT JOINING WLC 2504

Can you also check the "Accept Manu.. Installed certificate box" and then try again.

If still not works then paste the output of these command:

from WLC: sh sysinfo

From AP: sh version

also paste the entire bootup process from AP console.

Regards

Dont forget to rate helpful posts

New Member

Hi Sandeep. It seems you are

Hi Sandeep. It seems you are experienced on this. So i will ask you and i hope you will help me. 

I have AIR-CT2504-k9 WLC and new 1702i-E-k9 APs. But APs cant join to the controller.

I have upgraded WLC software to the 8.2.111, but no sense. 

Hall of Fame Super Silver

You need to make sure you

You need to make sure you have the following:

  • NTP or time set correctly on the controller
  • Country code for -E defined on the controller
  • AP is obtaining a valid up address

Place the AP on the same subnet as the WLC to see if the AP joins.

You also need to console into the AP to really determine what is happening. For example, you can have an issue if the AP is booting in autonomous mode or the AP is setup as a mesh AP.  Console into the AP and attached a text file with the output while booting up the AP.

-Scott

*** Please rate helpful posts ***

-Scott
*** Please rate helpful posts ***
Hall of Fame Super Silver

Take a look at this guide

Take a look at this guide also:

http://www.cisco.com/c/en/us/support/docs/wireless/5500-series-wireless-controllers/119286-lap-notjoin-wlc-tshoot.html

-Scott 

*** Please rate helpful posts ***

-Scott
*** Please rate helpful posts ***
Hall of Fame Super Silver

Re: AP 1552E NOT JOINING WLC 2504

Just to add... Here is an older document in regards to MESH troubleshooting. I would look this over also.

http://www.cisco.com/c/en/us/td/docs/wireless/access_point/1500/troubleshooting/guide/TrbleshtMesh.html

Having more info also helps. Do you have any other MESH AP's up? Do you have any AP's up on the WLC? What code are you running on the WLC?

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***
New Member

Re: AP 1552E NOT JOINING WLC 2504

Platform: AIR-CT2504-K9, Version :

Manufacturer's Name: Cisco Systems Inc.  Product Name: Cisco Controller  Product Version: 7.0.220.0  RTOS Version: Erro  Bootloader Version: 1.0.18  Build Type: DATA + WPS

Platform: cisco AIR-CAP1552E-E-K9  Version :

Cisco IOS Software, C1550 Software (C1520-K9W8-M), Version 12.4(23c)JA3, RELEASE SOFTWARE (fc1)

Proceeding with system init

Proceeding to unmask interrupts

Initializing flashfs...

flashfs[1]: 22 files, 3 directories

flashfs[1]: 0 orphaned files, 0 orphaned directories

flashfs[1]: Total bytes: 31610880

flashfs[1]: Bytes used: 6631936

flashfs[1]: Bytes available: 24978944

flashfs[1]: flashfs fsck took 5 seconds.

flashfs[1]: Initialization complete.

flashfs[2]: 0 files, 1 directories

flashfs[2]: 0 orphaned files, 0 orphaned directories

flashfs[2]: Total bytes: 5806080

flashfs[2]: Bytes used: 1024

flashfs[2]: Bytes available: 5805056

flashfs[2]: flashfs fsck took 1 seconds.

flashfs[2]: Initialization complete....done Initializing flashfs.

Warning:  the compile-time code checksum does not appear to be present.

Radio0  present 8364B 8000 A8020000 0 A8030000 30

Radio1  present 8364B 8000 B8020000 0 B8030000 13

Radio2 not present 0 0 0 0 0 11

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:/c1520-rcvk9w8-mx/info (No such file or directory)cisco AIR-CAP1552E-E-K9    (PowerPC 8349) processor (revision A0) with 49142K/16384K bytes of memory.

Processor board ID FCZ1718H01Y

PowerPC 8349 CPU at 533Mhz, revision number 0x0031

Last reset from power loss

LWAPP image version 7.0.220.0

4 Gigabit Ethernet interfaces

2 802.11 Radio(s)

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

Base ethernet MAC Address: F0:29:29:C2:EF:E0

Part Number                          : 73-13538-02

PCA Assembly Number                  : 800-31224-01

PCA Revision Number                  : 03

PCB Serial Number                    : FOC1705241P

Top Assembly Part Number             : 800-34853-05

Top Assembly Serial Number           : FCZ1718H01Y

Top Revision Number                  : A0

Product/Model Number                 : AIR-CAP1552E-E-K9

% Please define a domain-name first.

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

Press RETURN to get started!

*Mar  1 00:00:07.307: %SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: IOS crypto FIPS self test passed

*Mar  1 00:00:07.723: m8349_ether_enable: MACCFG1 sync timeout

*Mar  1 00:00:09.819: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 0

*Mar  1 00:00:09.819: %LINK-3-UPDOWN: Interface Ethernet4, changed state to up

*Mar  1 00:00:09.819: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state to up

*Mar  1 00:00:09.819: %LINK-3-UPDOWN: Interface GigabitEthernet1, changed state to up

*Mar  1 00:00:09.819: %LINK-3-UPDOWN: Interface GigabitEthernet2, changed state to up

*Mar  1 00:00:09.819: %LINK-3-UPDOWN: Interface GigabitEthernet3, changed state to up

*Mar  1 00:00:11.375: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to down

*Mar  1 00:00:11.375: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1, changed state to down

*Mar  1 00:00:11.375: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2, changed state to down

*Mar  1 00:00:11.375: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3, changed state to down

*Mar  1 00:00:11.963: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 1

*Mar  1 00:00:12.039: %LWAPP-3-CLIENTEVENTLOG: Read and initialized AP event log (contains, 1024 messages)

*Mar  1 00:00:12.051: AP identified to be in Fenway/Huck Jr/1240/1130 configuration

*Mar  1 00:00:12.055:  status of voice_diag_test from WLC is false

*Mar  1 00:00:14.079: %SYS-5-RESTART: System restarted --

Cisco IOS Software, C1550 Software (C1520-K9W8-M), Version 12.4(23c)JA3, RELEASE SOFTWARE (fc1)

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

Copyright (c) 1986-2011 by Cisco Systems, Inc.

Compiled Tue 18-Oct-11 15:13 by prod_rel_team

*Mar  1 00:00:14.079: %SNMP-5-COLDSTART: SNMP agent on host APf029.29c2.efe0 is undergoing a cold start

*Mar  1 00:00:14.143: %MESH-6-BVI_CREATED: Mesh BVI1 interface created

*Mar  1 00:00:14.163: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset

*Mar  1 00:00:14.163: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Mar  1 00:00:15.163: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down

*Mar  1 00:00:15.163: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Mar  1 00:00:16.143: %LINK-3-UPDOWN: Interface BVI1, changed state to down

*Mar  1 00:00:17.139: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitE

Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)thernet0, changed state to down

*Mar  1 00:00:17.143: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1, changed state to down

*Mar  1 00:00:17.143: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2, changed state to down

*Mar  1 00:00:17.143: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3, changed state to down

*Mar  1 00:00:18.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet4, changed state to up

*Mar  1 00:00:20.723: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up

*Mar  1 00:00:32.743: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Mar  1 00:00:32.795: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Mar  1 00:00:32.959: %SSH-5-ENABLED: SSH 2.0 has been enabled

*Mar  1 00:00:33.107: Logging LWAPP message to 255.255.255.255.

*Mar  1 00:00:33.307: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 255.255.255.255 started - CLI initiated

*Mar  1 00:00:46.383: %CDP_PD-2-POWER_LOW: All radios disabled - NEGOTIATED WS-C2960-24PC-S (189c.5d95.2d18)

Username:

*Mar  1 00:01:27.119: %MESH-6-ADJACENCY_STATE_MACHINE_STARTED: Mesh adjacency state machine started

Username:

*Mar  1 00:01:32.163: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started

*Mar  1 00:01:34.119: %LINK-3-UPDOWN: Interface BVI1, changed state to up

*Mar  1 00:01:35.119: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up

*Mar  1 00:01:37.207: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

% CDP is not supported on this interface, or for this encapsulation

*Mar  1 00:01:40.887: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Mar  1 00:01:40.907:  status of voice_diag_test from WLC is false

*Mar  1 00:01:46.387: %CDP_PD-2-POWER_LOW: All radios disabled - NEGOTIATED WS-C2960-24PC-S (189c.5d95.2d18)

Regards,

Obinna Samuel

VIP Purple

Re: AP 1552E NOT JOINING WLC 2504

paste the output of this command:

sh sysinfo from wlc.

Regards

Hall of Fame Super Silver

Re: AP 1552E NOT JOINING WLC 2504

*Mar 1 00:01:46.387: %CDP_PD-2-POWER_LOW: All radios disabled - NEGOTIATED WS-C2960-24PC-S (189c.5d95.2d18)

You need to have the correct power injector, AC adapter or hard wired power source to bring up the radios. So don't think this will bring up your MAP. Do you have any other mesh AP's or AP's up in this WLC?

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***
New Member

Re: AP 1552E NOT JOINING WLC 2504

(Cisco Controller) >show sysinfo

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

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

Product Version.................................. 7.0.220.0

Bootloader Version............................... 1.0.18

Field Recovery Image Version..................... 1.0.0

Firmware Version................................. PIC 16.0

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

System Name...................................... Cisco_43:db:24

System Location..................................

System Contact...................................

System ObjectID.................................. 1.3.6.1.4.1.9.1.1279

IP Address....................................... 192.168.1.2

Last Reset....................................... Power on reset

System Up Time................................... 0 days 3 hrs 43 mins 56 secs

System Timezone Location.........................

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

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

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

--More-- or (q)uit

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

Configured Country............................... US  - United States

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

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

Internal Temperature............................. +29 C

External Temperature............................. +31 C

Fan Status....................................... 3800 rpm

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

State of 802.11a Network......................... Enabled

Number of WLANs.................................. 1

Number of Active Clients......................... 0

Burned-in MAC Address............................ 24:E9:B3:43:DB:20

Maximum number of APs supported.................. 5

VIP Purple

Re: AP 1552E NOT JOINING WLC 2504

Configured Country............................... US  - United States

so here is the problem:

you have access point: Product/Model Number                 : AIR-CAP1552E-E-K9

which is for europe regulatery domain and your WLC is configured as USA.

Which country r u in???

Regards

dont forget to rate helpful posts

New Member

Re: AP 1552E NOT JOINING WLC 2504

Nigeria which isn't on the country code list.

Does that me i should change the Configured country to an european country since Nigeria isn't on the list?

VIP Purple

Re: AP 1552E NOT JOINING WLC 2504

If you have diff country then USA then please change it.

How to change country code on WLC:

Step 1  Disable the 802.11 networks as follows:
  1. Choose Wireless > 802.11a/n > Network.
  2. Unselect the 802.11a Network Status check box.
  3. Click Apply.
  4. Choose Wireless > 802.11a/n > Network.
  5. Unselect the 802.11b/g Network Status check box.
  6. Click Apply.
Step 2 

Choose Wireless > Country to open the Country page and select the correct country code.

Regards

Dont forget to rate helpful posts

New Member

Re: AP 1552E NOT JOINING WLC 2504

Yes I do have other MAP but not been deployed. trying to see how it works in a lab environment before i go live.

Please tell me if a 2960 PoE switch cannot power the MAP or i need to get a thicker STP Cable?

Thanks,

Obinna Samuel

VIP Purple

Re: AP 1552E NOT JOINING WLC 2504

Yes you can try that.

Regards

VIP Purple

Re: AP 1552E NOT JOINING WLC 2504

Hi,

With the -E there are many profiles that can be selected, as most are very close to the same restrictions.

However you should contact to your local regulatory domain group and ask them which country is the same as Nigeria. Explain what you are doing and have them tell you, and get it in writing.  that way you are covered on your choice.

Regards

Dont forget to rate helpful posts

New Member

Re: AP 1552E NOT JOINING WLC 2504

Could it be that power is the only reason why this AP is flapping (joining and unjoining) or something else as i have changed the country to GB as advised:

% CDP is not supported on this interface, or for this encapsulation

*Feb 15 03:29:46.663: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.2

*Feb 15 03:29:46.663: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.1.2

*Feb 15 03:29:46.663: %DTLS-5-PEER_DISCONNECT: Peer 192.168.1.2 has closed connection.

*Feb 15 03:29:46.663: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.1.2:5246

*Feb 15 03:29:46.707: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Feb 15 03:29:46.707: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Feb 15 03:29:46.763: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Feb 15 03:29:46.783:  status of voice_diag_test from WLC is false

*Feb 15 03:30:02.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.1.2 peer_port: 5246

*Feb 15 03:30:02.000: %CAPWAP-5-CHANGED: CAPWAP changed state to

*Feb 15 03:30:02.663: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.1.2 peer_port: 5246

*Feb 15 03:30:02.663: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.2

*Feb 15 03:30:02.663: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*Feb 15 03:30:07.663: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.2

*Feb 15 03:30:07.663: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.1.2

*Feb 15 03:30:07.663: %DTLS-5-PEER_DISCONNECT: Peer 192.168.1.2 has closed connection.

*Feb 15 03:30:07.663: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.1.2:5246

*Feb 15 03:30:02.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.1.2 peer_port: 5246

*Feb 15 03:30:02.000: %CAPWAP-5-CHANGED: CAPWAP changed state to

*Feb 15 03:30:02.663: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.1.2 peer_port: 5246

*Feb 15 03:30:02.663: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.2

*Feb 15 03:30:02.663: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

% CDP is not supported on this interface, or for this encapsulation

*Feb 15 03:30:07.663: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.2

*Feb 15 03:30:07.663: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.1.2

*Feb 15 03:30:07.663: %DTLS-5-PEER_DISCONNECT: Peer 192.168.1.2 has closed connection.

*Feb 15 03:30:07.663: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.1.2:5246

*Feb 15 03:30:07.707: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Feb 15 03:30:07.707: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Feb 15 03:30:07.763: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Feb 15 03:30:07.783:  status of voice_diag_test from WLC is false

*Feb 15 03:30:24.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.1.2 peer_port: 5246

*Feb 15 03:30:24.000: %CAPWAP-5-CHANGED: CAPWAP changed state to

*Feb 15 03:30:24.659: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.1.2 peer_port: 5246

*Feb 15 03:30:24.659: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.2

*Feb 15 03:30:24.659: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

VIP Purple

Re: AP 1552E NOT JOINING WLC 2504

did you check the box for "Accept Manufactured Installed certificate box" ?

AP.JPG

If not then check it. otherwise AP will not join.

Regards

Dont forget to rate helpful posts

New Member

Re: AP 1552E NOT JOINING WLC 2504

Guys, i have noticed that unlike before the AP has joined and remind join for atleast 5mins sine i checked the box

Accept Manufactured Installed certificate box.

AP2.JPG

The below is what i get now after i issue the below command:

(Cisco Controller) >show ap join stats detailed f029.29c2.efe0

Discovery phase statistics

- Discovery requests received.............................. 102

- Successful discovery responses sent...................... 90

- Unsuccessful discovery request processing................ 12

- Reason for last unsuccessful discovery attempt........... Discovery request decoding with subnet broadcast and wrong AP IP address

- Time at last successful discovery attempt................ Feb 15 03:38:44.958

- Time at last unsuccessful discovery attempt.............. Feb 15 03:15:53.737

Join phase statistics

- Join requests received................................... 147

- Successful join responses sent........................... 5

- Unsuccessful join request processing..................... 74

- Reason for last unsuccessful join attempt................ RADIUS authorization is pending for the AP

- Time at last successful join attempt..................... Feb 15 03:38:55.632

- Time at last unsuccessful join attempt................... Feb 15 03:38:55.634

Configuration phase statistics

- Configuration requests received.......................... 11

- Successful configuration responses sent.................. 1

- Unsuccessful configuration request processing............ 4

- Reason for last unsuccessful configuration attempt....... Regulatory domain check has failed for the AP

--More-- or (q)uit

- Time at last successful configuration attempt............ Feb 15 03:38:55.819

- Time at last unsuccessful configuration attempt.......... Feb 15 03:20:12.564

Last AP message decryption failure details

- Reason for last message decryption failure............... Not applicable

Last AP disconnect details

- Reason for last AP connection failure.................... Not applicable

- Last AP disconnect reason................................ AP's capwap state machine restarted

Last join error summary

- Type of error that occurred last......................... Lwapp join request rejected

- Reason for error that occurred last...................... RADIUS authorization is pending for the AP

- Time at which the last join error occurred............... Feb 15 03:38:55.634

AP disconnect details

- Reason for last AP connection failure.................... Not applicable

Ethernet Mac : f0:29:29:c2:ef:e0  Ip Address : 192.168.1.8

(Cisco Controller) >

Hall of Fame Super Silver

Re: AP 1552E NOT JOINING WLC 2504

That is the default setting on the WLC and shouldn't of been removed. Well at least you have it joined.

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***
VIP Purple

Re: AP 1552E NOT JOINING WLC 2504

Hi,

Glad that finally you got it. but just for info fro mesh AP.

There are only few things you must check.

1. MIC box is checked.

2. Mac address should be there in AP Policy.

3. Country code should be matched with your AP.(as per your info......it should be europe)

Regards

Dont forget to rate helpful posts

Hall of Fame Super Silver

Re: AP 1552E NOT JOINING WLC 2504

If you look at the data sheet for the 1550, that will list the power source that will be able to power up these MESH AP's

http://www.cisco.com/c/en/us/products/collateral/wireless/aironet-1550-series/data_sheet_c78-641373.html

If you have this in a lab, you can keep the 1550 connected to that switch, but you will not be able to test associations since the radios will be in a down state. Like Sandeep mentioned, make sure the country codes are correct. I would verify that the WLC time is correct and I would place the AP on the same subnet as the WLC for lab purposes. That is how I stage MESH AP's. If you still can't get the AP to join the WLC, then I would verify that the MAC address is correct, remove it and add it back.

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***
New Member

Re: AP 1552E NOT JOINING WLC 2504

Guys,

Thanks for the assistance so far. I might have to wait till Monday (17/02/14) when i get the PoE power injector and power up the radios to know for sure if all we have done works correct and currently the AP is joined to the WLC.

Thanks once again.

Regards,

Obinna Samuel

VIP Purple

Re: AP 1552E NOT JOINING WLC 2504

Glad that works, yes power injector are always prefrred.

did you enabled :

Enable the 802.11 networks as follows:

  1. #Choose Wireless > 802.11a/n > Network.
  2. #select the 802.11a Network Status check box.
  3. #Click Apply.
  4. #Choose Wireless > 802.11a/n > Network.
  5. #select the 802.11b/g Network Status check box.
  6. #Click Apply.

Regards

Dont forget to rate helpful posts and mark this as answered, it may help others.

1103
Views
0
Helpful
25
Replies