cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1415
Views
0
Helpful
8
Replies

WLC 2504 Keeps Dropping all AP'S

I'm having  a Cisco 2500 Series Wireless Controller and it keep dropping all the AP's, what could be the problem and i have attached pic of wlc.

Any assistance would be really appreciated.

2 Accepted Solutions

Accepted Solutions

Hello,

 

without knowing any details (what do your logs show ?), try and upgrade to release 8.0.152.0 MD...

View solution in original post

Hello,

 

I would suggest you to upgrade WLC software to some version 8.x. There are numerous bugs in the 7.x version.

 

Try to upgrade and let me know.

Cheers,

Milos

View solution in original post

8 Replies 8

Hello,

 

without knowing any details (what do your logs show ?), try and upgrade to release 8.0.152.0 MD...

Coverage hole pre alarm for client[1] a0:ed:cd:5b:af:18 on 802.11b/g interface of AP 1c:1d:86:52:52:f0 (APW21-W21-2F-STAIRS). Hist: 2 0 2 0 0 0 6 21 111 221 209 137 4 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

 

Rogue AP: 4c:5e:0c:28:cf:d7 detected on Base Radio MAC: d0:c7:89:33:ea:80 Interface no: 1(802.11a) Channel: 52 RSSI: -84 SNR: 8 Classification: unclassified, State: Alert, RuleClassified : N, Severity Score: 0, RuleName: N.A. ,Classified AP MAC: 00:00:00:00:00:00 ,Classified RSSI: 0

 

Rogue AP: 66:70:33:dd:ad:07 detected on Base Radio MAC: d0:c7:89:33:ea:80 Interface no: 0(802.11n(2.4 GHz)) Channel: 1 RSSI: -71 SNR: 16 Classification: unclassified, State: Alert, RuleClassified : N, Severity Score: 0, RuleName: N.A. ,Classified AP MAC: 00:00:00:00:00:00 ,Classified RSSI: 0

 

Coverage hole pre alarm for client[1] 8c:9f:3b:9e:16:9f on 802.11b/g interface of AP 1c:1d:86:52:52:f0 (APW21-W21-2F-STAIRS). Hist: 1 0 0 0 0 2 21 14 17 20 34 12 2 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Hello

How many APs are connected to the wlc?
Do they all drop at once of sporadically?
Are the Aps receiving the correct power from there POE switches?

sh msglog
sh eventlog
sh traplog


Note: if you upgrade the wlc then the APs will also get upgraded and reload so if you have alot of them you can cause some outage if you dont plan the upgrade.


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

How many APs are connected to the wlc? 

I have 14 Access point connected


Do they all drop at once of sporadically?

They all drop at once.


Are the Aps receiving the correct power from there POE switches?

I'm not really sure about the correct power but a month ago everything its been working just fine, all of a sudden the AP'S started dropping.

sh msglog

Message Log Severity Level ...................... ERROR
*apfOrphanSocketTask: Nov 14 16:12:29.376: #IPV6-3-INVALID_ADDR_ORPHAN: ipv6_net.c:715 Invalid ipv6 address ::, failed to do data gleaning.
*apfOrphanSocketTask: Nov 14 16:12:28.989: #IPV6-3-INVALID_ADDR_ORPHAN: ipv6_net.c:715 Invalid ipv6 address ::, failed to do data gleaning.
*apfOrphanSocketTask: Nov 14 16:12:19.525: #IPV6-3-INVALID_ADDR_ORPHAN: ipv6_net.c:715 Invalid ipv6 address ::, failed to do data gleaning.
*apfOrphanSocketTask: Nov 14 16:12:19.485: #IPV6-3-INVALID_ADDR_ORPHAN: ipv6_net.c:715 Invalid ipv6 address ::, failed to do data gleaning.
*apfOrphanSocketTask: Nov 14 16:11:51.845: #IPV6-3-INVALID_ADDR_ORPHAN: ipv6_net.c:715 Invalid ipv6 address ::, failed to do data gleaning.
*apfOrphanSocketTask: Nov 14 16:11:51.029: #IPV6-3-INVALID_ADDR_ORPHAN: ipv6_net.c:715 Invalid ipv6 address ::, failed to do data gleaning.
*apfOrphanSocketTask: Nov 14 16:11:28.381: #IPV6-3-INVALID_ADDR_ORPHAN: ipv6_net.c:715 Invalid ipv6 address ::, failed to do data gleaning.
*apfOrphanSocketTask: Nov 14 16:11:27.623: #IPV6-3-INVALID_ADDR_ORPHAN: ipv6_net.c:715 Invalid ipv6 address ::, failed to do data gleaning.
*apfOrphanSocketTask: Nov 14 16:11:24.826: #IPV6-3-INVALID_ADDR_ORPHAN: ipv6_net.c:715 Invalid ipv6 address ::, failed to do data gleaning.
*apfOrphanSocketTask: Nov 14 16:11:13.845: #IPV6-3-INVALID_ADDR_ORPHAN: ipv6_net.c:715 Invalid ipv6 address ::, failed to do data gleaning.
*apfOrphanSocketTask: Nov 14 16:11:05.610: #IPV6-3-INVALID_ADDR_ORPHAN: ipv6_net.c:715 Invalid ipv6 address ::, failed to do data gleaning.
*apfOrphanSocketTask: Nov 14 16:11:04.382: #IPV6-3-INVALID_ADDR_ORPHAN: ipv6_net.c:715 Invalid ipv6 address ::, failed to do data gleaning.

 


sh eventlog

(Cisco Controller) >show eventlog
Time
File Line TaskID Code d h m s
EVENT> bootos.c 1544 144A3750 AAAAAAAA 0 0 0 17
EVENT> bootos.c 1544 144A3750 AAAAAAAA 0 0 0 17
EVENT> bootos.c 1544 144A3750 AAAAAAAA 0 0 0 17
EVENT> bootos.c 1544 144A3750 AAAAAAAA 0 0 0 17
EVENT> bootos.c 1544 144A3750 AAAAAAAA 0 0 0 17
EVENT> bootos.c 1544 144A3750 AAAAAAAA 0 0 0 17
EVENT> bootos.c 1544 144A3750 AAAAAAAA 0 0 0 17
EVENT> bootos.c 1544 144A3750 AAAAAAAA 0 0 0 17
EVENT> bootos.c 1544 144A3750 AAAAAAAA 0 0 0 18
EVENT> bootos.c 1544 144A3750 AAAAAAAA 0 0 0 17
EVENT> bootos.c 1544 144A3750 AAAAAAAA 0 0 0 17
EVENT> bootos.c 1544 144A3750 AAAAAAAA 0 0 0 17
EVENT> bootos.c 1544 144A3750 AAAAAAAA 0 0 0 18
EVENT> bootos.c 1544 144A3750 AAAAAAAA 0 0 0 17
EVENT> bootos.c 1544 144A3750 AAAAAAAA 0 0 0 17

EVENT> bootos.c 1544 144A3750 AAAAAAAA 0 0 0 35
CORRUPT ENTRY >>>>>>>00000000 00000000 00000000 000004FA 00000081 00000000
CORRUPT ENTRY >>>>>>>00000000 00000000 00000000 00000000 00000000 00000000
CORRUPT ENTRY >>>>>>>00000000 00000000 00000000 00000000 00000000 00000000
CORRUPT ENTRY >>>>>>>00000000 00000000 00000000 00000000 00000000 00000000
CORRUPT ENTRY >>>>>>>00000000 00000000 00000000 00000000 00000000 00000000
CORRUPT ENTRY >>>>>>>00000000 00000000 00000000 00000000 00000000 00000000

 

File Line TaskID Code d h m s
CORRUPT ENTRY >>>>>>>00000000 00000000 00000000 00000000 00000000 00000000
CORRUPT ENTRY >>>>>>>00000000 00000000 00000000 00000000 00000000 00000000
CORRUPT ENTRY >>>>>>>00000000 00000000 00000000 00000000 00000000 00000000
CORRUPT ENTRY >>>>>>>00000000 00000000 00000000 2D2C29B0 00000000 00000000
CORRUPT ENTRY >>>>>>>00000000 2D2C2938 00000000 00000000 00000000 00000000

 


sh traplog

(Cisco Controller) >show traplog

Number of Traps Since Last Reset ............ 2687
Number of Traps Since Log Last Displayed .... 12

Log System Time Trap
--- ------------------------ -------------------------------------------------
0 Wed Nov 14 16:18:52 2018 Coverage hole pre alarm for client[1] ac:36:13:eb
:23:c4 on 802.11b/g interface of AP 1c:1d:86:52:5
2:f0 (APW21-W21-2F-STAIRS). Hist: 3 1 3 5 11 11 1
5 25 20 35 51 34 19 11 8 3 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0
1 Wed Nov 14 16:18:52 2018 Coverage hole pre alarm for client[1] 04:1b:ba:df
:39:b2 on 802.11b/g interface of AP 1c:1d:86:52:5
2:f0 (APW21-W21-2F-STAIRS). Hist: 1 0 1 1 0 1 2 1
0 11 17 9 7 1 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
2 Wed Nov 14 16:18:52 2018 Coverage hole pre alarm for client[1] a0:ed:cd:5b
:af:18 on 802.11b/g interface of AP 1c:1d:86:52:5
2:f0 (APW21-W21-2F-STAIRS). Hist: 0 0 2 1 1 1 0 1
8 144 87 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

 

Log System Time Trap
--- ------------------------ -------------------------------------------------16:20:13 2018 Rogue AP : f2:9f:c2:95:3a:ea removed from Base R
adio MAC : f8:4f:57:78:68:00 Interface no:0(802.1
1b/g)
16:20:13 2018 Rogue AP : 34:12:98:08:be:44 removed from Base R
adio MAC : c0:7b:bc:cf:15:a0 Interface no:0(802.1
1n(2.4 GHz))
16:20:13 2018 Rogue AP : 34:12:98:08:be:44 removed from Base R
adio MAC : 1c:1d:86:52:56:a0 Interface no:0(802.1
1n(2.4 GHz))
16:20:13 2018 Rogue AP : 34:12:98:08:be:44 removed from Base R
adio MAC : d0:c7:89:33:ea:80 Interface no:0(802.1
1n(2.4 GHz))
 16:20:13 2018 Rogue AP : 34:12:98:08:be:44 removed from Base R
adio MAC : f8:4f:57:78:68:00 Interface no:0(802.1
1n(2.4 GHz))

 

Hello,

 

how do you have rogue AP management configured ? Post the full config of the 2504...

Hello

what version code are you running?

 

would you know in that past month of any changes been made on your network?

 

is it possible you might have a duplicate ip conflict with the mgt wlc ip or a network issue that drops the connection towards the wlc?

 

Can you post if applicable the output of the following:

debug lwapp events enable

 

 


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

Hello,

 

I would suggest you to upgrade WLC software to some version 8.x. There are numerous bugs in the 7.x version.

 

Try to upgrade and let me know.

Cheers,

Milos

Leo Laohoo
Hall of Fame
Hall of Fame
What model of APs are these?
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Review Cisco Networking products for a $25 gift card