Radio down on AP1242AG during failover of controlers

Unanswered Question
Feb 12th, 2008

Hi,

I am setting up a 6509 with a WISM controller module.

When i "loose" one controller, the AP will failover to the second that is part of the mobility group. During that failover, the radios will go down disassociating any client connected...

Here are the messages that i get in the logs of the second controler:

Feb 11 17:27:40.979 apf_spam.c:934 APF-1-NOT_ADV_SSID_ON_AP: Not advertising SSID MNETG on AP 00:1e:13:ef:18:10 due to radio policy.

- Traceback: 1011a908 1011b084 100fd68c 1035ebec 10b76398 10d2804c

Feb 11 17:27:40.979 apf_spam.c:934 APF-1-NOT_ADV_SSID_ON_AP: Not advertising SSID MGUEST on AP 00:1e:13:ef:18:10 due to radio policy.

- Traceback: 1011a908 1011b084 100fd68c 1035ebec 10b76398 10d2804c

AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1e:13:ef:18:10 Cause=Admin Configured

Any ideas???

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
rob.huffman Tue, 02/12/2008 - 16:54

Hi Jean-Michel,

My understanding is that this is expected behaviour;

Q. I have two Wireless LAN Controllers (WLCs) named WLC1 and WLC2 configured within the same mobility group for failover. My Lightweight Access Point (LAP) is currently registered with WLC1. If WLC1 fails, does the AP registered to WLC1 reboot during its transition towards the surviving WLC (WLC2)? Also, during this failover, does the WLAN client lose WLAN connectivity with the LAP?

A. Yes, the LAP does de-register from WLC1, reboot, and then re-registers with WLC2, if WLC1 fails. Because the LAP reboots, the associated WLAN clients lose the connectivity to the rebooting LAP.

From this good doc;

http://www.cisco.com/en/US/products/hw/wireless/ps430/products_qanda_item09186a00808b4c61.shtml

Hope this helps!

Rob

Richard Atkin Sun, 03/02/2008 - 09:56

This is expected behaviour as the guys have already stated.

The new v5 code however offers a couple of ways of reducing the outage time by allowing you to adjust the heatbeat settings, thus discovering a failure sooner.

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