B Radios Seem to Reset

Unanswered Question
Mar 19th, 2009

I see the the following log entries quite regularly in the logs of all of my controllers. I am running 4.2 and 5.2 code. Does any one know why this is happening??

Thu Mar 19 05:27:32 2009 AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:14:6a:73:83:d0 Cause=Admin Configured

2 Thu Mar 19 05:27:32 2009 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:14:6a:73:83:d0 Cause=Admin Configured

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Leo Laohoo Thu, 03/19/2009 - 19:20

From the WLC, if you do the CLI command "sh ap eventlog ", do you see a line that goes like "%LWAPP-5-RLDP: RLDP stopped on slot 0." and then your radios go down/up?

If so, you need to set the AP's to detect whether you are operating in PoE or Injector. Go to Monitors -> All APs -> Choose the AP -> Advanced Tab and under Power Over Ethernet Settings choose Pre-Standard State if you are not using an Injector. If you are, choose Power Injector State -> Installed.

d-berlinski Fri, 03/20/2009 - 05:39

This is what I get from the CLI when this happens...

*Mar 20 07:18:59.994: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Mar 20 07:19:00.003: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

The PoE is also checked as appropriate. If it was a PoE negotiation issue, wouldn't the 'A' radios reset also? This only happend for the 'B' radios.

dennischolmes Sat, 03/21/2009 - 13:21

Not always. Usually it's the other way around though. A radios usually drop first.

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode