topic Re: Access Point not registering with 5508 controller running 7.0.220.0 code in Wireless

Access Point not registering with 5508 controller running 7.0.220.0 code

bdobruna09 — Mon, 05 Jul 2021 17:13:58 GMT

I am having issues adding additional AP's currently i have 15 aps no problem but trying to add 2 more and no luck , they do show under statistics ap join with ip addresses assigned but status not joined.

also found this:

Reason For Last Unsuccessful Attempt

Layer 3 discovery request not received on management VLAN

Re: Access Point not registering with 5508 controller running 7.0.220.0 code

Sathiyanarayanan Ravindran — Tue, 09 Apr 2019 19:01:38 GMT

Hi,

Check whether the WLC is reachable from the AP. Also please share the Model of AP which you are trying to join.

Re: Access Point not registering with 5508 controller running 7.0.220.0 code

Sathiyanarayanan Ravindran — Tue, 09 Apr 2019 19:04:35 GMT

Hi,

Check whether the WLC is reachable from the AP. Also please share the Model of AP which you are trying to join.

Re: Access Point not registering with 5508 controller running 7.0.220.0 code

balaji.bandi — Tue, 09 Apr 2019 19:11:30 GMT

Is this new AP connected to Same Access Switch , same IP addres Range ?

how is the IP address allocated to these AP ? from DHCP ?

what is the AP working IP range, what is new AP IP range ?

Re: Access Point not registering with 5508 controller running 7.0.220.0 code

bdobruna09 — Tue, 09 Apr 2019 19:36:23 GMT

Model of the AP is AIR-CAP3502E-A-K9 and you mean connect console to the ap and try to ping the WLC ?

Re: Access Point not registering with 5508 controller running 7.0.220.0 code

Sathiyanarayanan Ravindran — Tue, 09 Apr 2019 19:40:12 GMT

Yes, Try to ping the WLC from the AP. Also check whether you are getting any error message on the console. If possible post those error logs.

Re: Access Point not registering with 5508 controller running 7.0.220.0 code

bdobruna09 — Tue, 09 Apr 2019 19:46:55 GMT

@balaji yes AP is on same switch and same range , the switch port is trunk and i see it under the ap not associated to the controller.Yes its from dhcp and then i will assign static.

Re: Access Point not registering with 5508 controller running 7.0.220.0 code

RaffyLindogan — Wed, 10 Apr 2019 04:55:15 GMT

This error "Layer 3 discovery request not received on management VLAN" could mean:

1. WLC is not added on DHCP option

2. Vlan may not be allowed all the way to the respective trunk links

Can you send the logs when you console to the AP.

Cheers

Re: Access Point not registering with 5508 controller running 7.0.220.0 code

Leo Laohoo — Wed, 10 Apr 2019 07:02:50 GMT

Post the complete output to the following commands:
1. WLC: sh sysinfo;
2. WLC: sh time; and
3. AP: sh version

Re: Access Point not registering with 5508 controller running 7.0.220.0 code

bdobruna09 — Wed, 10 Apr 2019 14:30:13 GMT

@leo
(Cisco Controller) >show sysinfo

Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.0.220.0
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS

System Name...................................... USTHOWC02
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
IP Address....................................... 10.2.24.12
Last Reset....................................... Power on reset
System Up Time................................... 244 days 18 hrs 43 mins 48 secs
System Timezone Location......................... (GMT -5:00) Eastern Time (US and Canada)
Current Boot License Level....................... base
Current Boot License Type........................ Permanent
Next Boot License Level.......................... base
Next Boot License Type........................... Permanent

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

--More-- or (q)uit
Operating Environment............................ Commercial (0 to 40 C)
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +33 C
External Temperature............................. +19 C
Fan Status....................................... OK

State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 7
Number of Active Clients......................... 76

Burned-in MAC Address............................ 6C:20:56:64:B8:00
Power Supply 1................................... Present, OK
Power Supply 2................................... Absent
Maximum number of APs supported.................. 25

(Cisco Controller) >show time

Time............................................. Wed Apr 10 07:37:33 2019

Timezone delta................................... 0:0
Timezone location................................ (GMT -5:00) Eastern Time (US and Canada)

NTP Servers
NTP Polling Interval......................... 86400

Index NTP Key Index NTP Server NTP Msg Auth Status
------- ---------------------------------------------------------------

AP VERSION

AP1cdf.0f95.255e>sho version
Cisco IOS Software, C3500 Software (AP3G1-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 14:59 by prod_rel_team

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

AP1cdf.0f95.255e uptime is 8 minutes
System returned to ROM by power-on
System image file is "flash:/ap3g1-k9w8-mx.124-23c.JA3/ap3g1-k9w8-mx.124-23c.JA3
"

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to
export@cisco.com.

cisco AIR-CAP3502E-A-K9 (PowerPC460exr) processor (revision A0) with 81910K/4
9152K bytes of memory.
Processor board ID FGL1502S03B
PowerPC460exr CPU at 666Mhz, revision number 0x18A8
Last reset from power-on
LWAPP image version 7.0.220.0
1 Gigabit Ethernet interface
2 802.11 Radio(s)

32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 1C:DF:0F:95:25:5E
Part Number : 73-12175-03
PCA Assembly Number : 800-32268-03
PCA Revision Number : A0
PCB Serial Number : FOC14464CAL
Top Assembly Part Number : 800-32904-01
Top Assembly Serial Number : FGL1502S03B
Top Assembly Serial Number : FGL1502S03B
Product/Model Number : AIR-CAP3502E-A-K9

Configuration register is 0xF

Re: Access Point not registering with 5508 controller running 7.0.220.0 code

RaffyLindogan — Thu, 11 Apr 2019 06:11:24 GMT

Hi mate,

Can you enable the debug on WLC.

Reload the AP once debugs are enabled.

And please post the results here.

Thanks.

WLC:

debug mac add <ap mac>

debug client <ap mac>

debug capwap events events enable

debug capwap errors enable

AP:

show log

Re: Access Point not registering with 5508 controller running 7.0.220.0 code

Leo Laohoo — Thu, 11 Apr 2019 06:38:47 GMT

What happens if you configure NTP on the controller?

Re: Access Point not registering with 5508 controller running 7.0.220.0 code

bdobruna09 — Thu, 11 Apr 2019 11:59:26 GMT

I figured out as it sounds very strange, i changed the port where the AP was connected not to be Trunk and i was able to join the WLC then changed it back to trunk and good to go.

thank you all