AIR-CAP1702I-A-K9 and AIR-AP1832I-A-K9 does not join 2504 WLC

Ernesto0817 · ‎06-04-2021

We have a WLC2504 version 8.2.141.0 with 20 AIR-CAP1702I-A-K9 and AIR-AP1832I-A-K9, the Vlan is default in the network

For two years I worked well then, nest stopped being recognized little by little, now I don't see any of them, it's not a network problem.
We connect two APs in ports 3 and 4 of the WLC2504 the problem is the same, we load the software again in the WLC2504 the problem continues
In CDP Interface Neighbors we see the IPs of the two Access Points directly connected to the WLC with the status Not joined but in Wireless status the Number of APs is 0 zero or none.

The date, time and time zone is correct

The WLC reports:

Starting Portal Server Services: ok
Starting mDNS Services:
Failed to add service from xml to profile DB : 6 iTuneWirelessDeviceSharing 2 default-mdns-profileok
Starting Management Services:
Web Server: CLI: Secure Web: ok

Some additional information;

(Cisco Controller) >show interface detailed management

Interface Name................................... management
MAC Address...................................... 00:59:dc:b4:82:60
IP Address....................................... 10.30.106.131
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 10.30.106.1
External NAT IP State............................ Disabled
External NAT IP Address.......................... 0.0.0.0
Link Local IPv6 Address.......................... fe80::259:dcff:feb4:8260/64
STATE ........................................... REACHABLE
Primary IPv6 Address............................. ::/128
STATE ........................................... NONE
Primary IPv6 Gateway............................. ::
Primary IPv6 Gateway Mac Address................. 00:00:00:00:00:00
STATE ........................................... INCOMPLETE
VLAN............................................. untagged
Quarantine-vlan.................................. 0
Active Physical Port............................. 1
Primary Physical Port............................ 1
Backup Physical Port............................. Unconfigured
DHCP Proxy Mode.................................. Enabled
Primary DHCP Server.............................. 10.30.106.131

--More-- or (q)uit
Secondary DHCP Server............................ Unconfigured
DHCP Option 82................................... Disabled
DHCP Option 82 bridge mode insertion............. Disabled
IPv4 ACL......................................... Unconfigured
IPv6 ACL......................................... Unconfigured
mDNS Profile Name................................ Unconfigured
AP Manager....................................... Yes
Guest Interface.................................. No
L2 Multicast..................................... Enabled

(Cisco Controller) >

(Cisco Controller) >show sysinfo

Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 8.2.141.0
Bootloader Version............................... 1.0.20
Field Recovery Image Version..................... 7.6.101.1
Firmware Version................................. PIC 20.0

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

System Name...................................... Intra-V
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1279
IP Address....................................... 10.30.106.131
IPv6 Address..................................... ::
Last Reset....................................... Power on reset
System Up Time................................... 0 days 2 hrs 16 mins 7 secs
System Timezone Location......................... (GMT -5:00) Eastern Time (US and Canada)
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180

--More-- or (q)uit

Configured Country............................... US - United States
Operating Environment............................ Commercial (0 to 40 C)
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +31 C
External Temperature............................. +36 C
Fan Status....................................... 4200 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............................ 00:59:DC:B4:82:60
Maximum number of APs supported.................. 75
System Nas-Id.................................... Intra-V
WLC MIC Certificate Types........................ SHA1/SHA2

(Cisco Controller) >show time

Time............................................. Fri Jun 4 19:15:15 2021

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

NTP Servers
NTP Polling Interval......................... 3600

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

(Cisco Controller) >

Can you help me

Thank You

Leo Laohoo · ‎06-04-2021

"sh time" output shows no NTP configured.
If the WLC does not have the correct time and date the APs will not join.

Next, check the license of the WLC to make sure there are enough AP License support.

Finally, if the APs still won't join, console into the AP, reboot and then post the entire boot-up process.

Ernesto0817 · ‎06-04-2021

Hi

Refer your request:

I don't use NTP
The time and date is right
The license is correct, have 25 we are 0
The boot-up process we will send it soon

Aditional information we have other 5 WLC2504 with the same configuration and version working fine. the APs are the same style

Thank you

Scott Fella · ‎06-05-2021

Well since you have other controllers, have you tried to have those ap's join one of your other controllers just to see if the join works? Is you ap's on the same subnet as the wlc management interface? It should be just for testing, but the console output will tell you what is happening.

-Scott
*** Please rate helpful posts ***

Ernesto0817 · ‎06-06-2021

These APs work well in other controllers, for all cases we use a single Vlan

Below you can see some commands:

(Cisco Controller) >show cdp neigh

Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater,
M - Remotely Managed Device

Device ID Local Intrfce Holdtme Capability Platform Port ID
AP00B0.E1A2.5798 Gig 0/0/3 174 R T AIR-AP183 Gig 0
AP00B0.E1A2.58B8 Gig 0/0/4 165 R T AIR-AP183 Gig 0

(Cisco Controller) >

(Cisco Controller) >show ap join stats summary all

Number of APs.............................................. 2

Base Mac AP EthernetMac AP Name IP Address Status
00:b0:e1:a3:c4:e0 N A N A 10.30.106.115 Not Joined
00:b0:e1:a3:c9:60 N A N A 10.30.106.119 Not Joined

(Cisco Controller) >

Scott Fella · ‎06-06-2021

What I'm looking for is if those ap's that are having issues can join a different controller or not. If those two aps do work and can join another controller and is functioning, then you can isolate the issue with the controller that isn't working. If the ap's can't join one of the other controllers and stay connected, then the issue might be with the ap. The show ap join stats summary all doesn't really help as ap's can do the initial join and then never join back, so you would always see that. Im assuming since there was only two ap's joined to this controller, you have bounced the controller just to see?

-Scott
*** Please rate helpful posts ***

Ernesto0817 · ‎06-07-2021

The WLC2504 controller has been working fine with about 20 Access Points, little by little I stop seeing all the Access Points, now it doesn't see any APs
For that reason we disconnected two APs from the Network and we have connected it directly to ports 3 and 4 of the controller, in summary we see the same problem, the WLC does not see the APs connected to the Network and those connected directly to port 3 and 4
Later we load the image to the controller again, the problem is the same
We have several controllers in other clients working OK with the same styles of APs and software versions

Scott Fella · ‎06-07-2021

Keep in mind things can break, that is why there is a support you can get with devices. I would not connect ap's to the WLC ports as they were really never meant to be a switch and there is a special setup if you are doing that. All I can say is look at the output of the ap from the console when you reboot it and see what errors or what info that can help you understand why the ap is not joining.

What we are assuming is that no changes have been made and this was working fine for a while.

-Scott
*** Please rate helpful posts ***

Ernesto0817 · ‎06-07-2021

No changes have been made and this was working fine for a while and suddenly all of them have gone down with no discovery on controller, below errors are shown in CLI of the cisco AIR-AP1832I-A-K9, the CLI of the controller no report problem. Can anyone help?

[*03/31/2020 02:40:24.5723] waiting for WCP to initialize
[*03/31/2020 02:40:24.5723] waiting for WCP to initialize
[*03/31/2020 02:40:24.5723] waiting for WCP to initialize
[*03/31/2020 02:40:24.5723] waiting for WCP to initialize
[*03/31/2020 02:40:24.5723] Socket Invalid Element wcp/wcp_db Handler has_rlan Data 0 Length 10
[*03/31/2020 02:40:24.5723] CAPWAP State: Discovery
[*03/31/2020 02:40:24.5723] Discovery Request sent to 255.255.255.255 with discovery type set to CAPWAP_DISCOVERY_TYPE_UNKNOWN(0)
[*03/31/2020 02:40:24.5723] CAPWAP State: Init
[*03/31/2020 02:40:24.5723] CAPWAP State: Discovery
[*03/31/2020 02:40:25.5720] Discovery Response from 10.30.106.135
[*03/31/2020 02:40:25.5720]
[*03/31/2020 02:40:25.5720] This AP model is supported by controller version newer than 7.0.0.0!
[*03/31/2020 02:40:25.5720]
[*03/31/2020 02:40:25.5720] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*03/31/2020 02:40:25.5720] Failed to decode discovery response.
[*03/31/2020 02:40:25.5720] CAPWAP SM handler: Failed to process message type 2 state 2.
[*03/31/2020 02:40:25.5720] Failed to handle capwap control message from controller - status 4
[*03/31/2020 02:40:25.5720] Failed to process unencrypted capwap packet from 10.30.106.135
[*03/31/2020 02:40:25.5720] Failed to send capwap message 0 to the state machine. Packet already freed.
[*03/31/2020 02:40:25.5720] wtpProcessPacketFromSocket returned 4
[*03/31/2020 02:40:25.6220] device capwap0 entered promiscuous mode
[*03/31/2020 02:40:25.7020] device capwap1 entered promiscuous mode
[*03/31/2020 02:40:33.9494] CAPWAP State: Discovery
[*03/31/2020 02:40:33.9494] Discovery Request sent to 255.255.255.255 with discovery type set to CAPWAP_DISCOVERY_TYPE_UNKNOWN(0)
[*03/31/2020 02:40:33.9494] Discovery Response from 10.30.106.135
[*03/31/2020 02:40:33.9494]
[*03/31/2020 02:40:33.9494] This AP model is supported by controller version newer than 7.0.0.0!
[*03/31/2020 02:40:33.9494]
[*03/31/2020 02:40:33.9494] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*03/31/2020 02:40:33.9494] Failed to decode discovery response.
[*03/31/2020 02:40:33.9494] CAPWAP SM handler: Failed to process message type 2 state 2.
[*03/31/2020 02:40:33.9494] Failed to handle capwap control message from controller - status 4
[*03/31/2020 02:40:33.9494] Failed to process unencrypted capwap packet from 10.30.106.135
[*03/31/2020 02:40:33.9494] Failed to send capwap message 0 to the state machine. Packet already freed.
[*03/31/2020 02:40:33.9494] wtpProcessPacketFromSocket returned 4
[*03/31/2020 02:40:43.4564] CAPWAP State: Discovery
[*03/31/2020 02:40:43.4564] Discovery Request sent to 255.255.255.255 with discovery type set to CAPWAP_DISCOVERY_TYPE_UNKNOWN(0)
[*03/31/2020 02:40:43.4564] Discovery Response from 10.30.106.135
[*03/31/2020 02:40:43.4564]
[*03/31/2020 02:40:43.4564] This AP model is supported by controller version newer than 7.0.0.0!
[*03/31/2020 02:40:43.4564]

Leo Laohoo · ‎06-08-2021

@Ernesto0817 wrote:

[*03/31/2020 02:40:43.4564] This AP model is supported by controller version newer than 7.0.0.0!

Uhhhhh ... Why is the AP looking at a controller running 7.X.X.X?

Ernesto0817 · ‎06-08-2021

We have a WLC2504 version 8.2.141.0

Ernesto0817 · ‎06-06-2021

WLCNG Boot Loader Version 1.0.20 (Built on Jan 9 2014 at 19:02:44 by cisco)
Board Revision 0.0 (SN: PSZ20341JKL, Type: AIR-CT2504-K9) (P)

Verifying boot loader integrity... OK.

OCTEON CN5230C-SCP pass 2.0, Core clock: 750 MHz, DDR clock: 330 MHz (660 Mhz data rate)
CPU Cores: 4
DRAM: 1024 MB
Flash: 32 MB
Clearing DRAM........ done
Network: octeth0', octeth1, octeth2, octeth3
' - Active interface
E - Environment MAC address override
CF Bus 0 (IDE): OK
IDE device 0:
- Model: 1GB CompactFlash Card Firm: CF B61FK Ser#: A111100294A10q4GB16W
- Type: Hard Disk
- Capacity: 977.4 MB = 0.9 GB (2001888 x 512)

Press <ESC> now to access the Boot Menu...

Loading backup image (8.2.141.0)

0%

.....
99%

100%

36674963 bytes read
Launching...
Launching images...

init started: BusyBox v1.6.0 (2010-05-13 17:50:10 EDT) multi-call binary

starting pid 690, tty '': '/etc/init.d/rcS'
Decompressing... OK
Validating...... OK
Detecting Hardware ...
Installing ether-pow driver - 0x6008

starting pid 907, tty '/dev/ttyS0': '/usr/bin/gettyOrMwar'
Setting up ZVM
Exporting LD_LIBRARY_PATH

Cryptographic library self-test....
Testing SHA1 Short Message 1
Testing SHA256 Short Message 1
Testing SHA1 Short Message 1
SHA1 POST PASSED
passed!

XML config selected
Validating XML configuration
octeon_device_init: found 1 DPs
/dev/fpga: No such device or address
readCPUConfigData: cardid 0x6060001
Cisco is a trademark of Cisco Systems, Inc.
Software Copyright Cisco Systems, Inc. All rights reserved.

Cisco AireOS Version 8.2.141.0
Firmware Version PIC 20.0

Initializing OS Services: ok
Initializing Serial Services: ok
Initializing Network Services: ok
Initializing Licensing Services: ok

License daemon start initialization.....
Starting Statistics Service: ok

License daemon running.....
Starting Licensing Services: ok
Starting ARP Services: ok
Starting Trap Manager: ok
Starting Network Interface Management Services: ok
Starting System Services: ok
Starting FIPS Features: ok : Not enabled
Starting SNMP services: ok
Starting Fastpath Hardware Acceleration: ok
Starting Fastpath Console redirect : ok
Starting Fastpath DP Heartbeat : ok
Fastpath CPU0.00: Starting Fastpath Application. SDK-1.8.0, build 269. Flags-[DUTY CYCLE] : ok

Fastpath CPU0.00: Initializing last packet received queue. Num of cores(2)

Fastpath CPU0.00: Init MBUF size: 1856, Subsequent MBUF size: 2040

Fastpath CPU0.00: Core 0 Initialization: ok

Fastpath CPU0.00: Initializing Timer...

Fastpath CPU0.00: Initializing Timer...done.

Fastpath CPU0.00: Initializing Timer...

Fastpath CPU0.00: Initializing NBAR AGING Timer...done.

Fastpath CPU0.01: Core 1 Initialization: ok

Starting Switching Services: ok
Starting QoS Services: ok
Starting Policy Manager: ok
Starting Data Transport Link Layer: ok
Starting Access Control List Services: ok
Starting System Interfaces: ok
Starting Client Troubleshooting Service: ok
Starting Certificate Database: ok
Starting VPN Services: ok
Starting Management Frame Protection: ok
Starting DNS Services: ok
Starting Redundancy: ok

Start rmgrPingTaskok

Starting LWAPP: ok
Starting CAPWAP: ok
Starting LOCP: ok
Starting Security Services: ok
Starting Policy Manager: ok
Starting Authentication Engine: ok
Starting Mobility Management: ok
Starting Ethernet-over-IP: ok
Starting Capwap Ping Component: ok
Starting AVC Services: ok
Starting AVC Flex Services: ok

Starting Virtual AP Services: FP0.00:Max core is 2
ok
Starting AireWave Director: ok
Starting Network Time Services: ok
Starting Cisco Discovery Protocol: ok
Starting Broadcast Services: ok
Starting Logging Services: ok
Starting DHCP Server: ok
Starting IDS Signature Manager: ok
Starting RFID Tag Tracking: ok
Starting RF Profiles: ok
Starting Power Supply and Fan Status Monitoring Service: ok
Starting Mesh Services: ok
Starting TSM: ok
Starting CIDS Services: ok
Starting Ethernet-over-IP: ok
Starting DTLS server: enabled in CAPWAP
Starting CleanAir: ok
Starting WIPS: ok
Starting SSHPM LSC PROV LIST: ok
Starting RRC Services: ok
Starting SXP Services: ok
Starting Alarm Services: ok
Starting FMC HS: ok
Starting IPv6 Services: ok
Starting Config Sync Manager : ok
Starting Hotspot Services: ok
Starting Tunnel Services New: ok
Starting Portal Server Services: ok
Starting mDNS Services:
Failed to add service from xml to profile DB : 6 iTuneWirelessDeviceSharing 2 default-mdns-profileok
Starting Management Services:
Web Server: CLI: Secure Web: ok

(Cisco Controller)

Enter User Name (or 'Recover-Config' this one-time only to reset configuration to factory defaults)

(Cisco Controller) >show cdp neigh

Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater,
M - Remotely Managed Device

Device ID Local Intrfce Holdtme Capability Platform Port ID
AP00B0.E1A2.5798 Gig 0/0/3 157 R T AIR-AP183 Gig 0
AP00B0.E1A2.58B8 Gig 0/0/4 143 R T AIR-AP183 Gig 0

(Cisco Controller) >show ap join stats summary all

Number of APs.............................................. 2

Base Mac AP EthernetMac AP Name IP Address Status
00:b0:e1:a3:c4:e0 N A N A 10.30.106.115 Not Joined
00:b0:e1:a3:c9:60 N A N A 10.30.106.119 Not Joined

(Cisco Controller) >