APs (1242 & 1230) disassociate from WLC4404 every hour

[moises.rodriguez]

My APs disassociate from WLC every hour, so I completly lose the connection.

0 Fri Sep 8 17:29:09 2006 AP Disassociated. Base Radio MAC:00:17:0f:da:f2:60

1 Fri Sep 8 17:29:09 2006 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:17:0f:da:f2:60 Cause=Unknown

2 Fri Sep 8 17:29:09 2006 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:17:0f:da:f2:60 Cause=Unknown

3 Fri Sep 8 17:29:09 2006 AP Disassociated. Base Radio MAC:00:11:21:7d:71:c0

4 Fri Sep 8 17:29:09 2006 AP's Interface:1(unknown type) Operation State Down: Base Radio MAC:00:11:21:7d:71:c0 Cause=Unknown

5 Fri Sep 8 17:29:09 2006 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:11:21:7d:71:c0 Cause=Unknown

6 Fri Sep 8 17:21:38 2006 Rogue : 00:16:46:2b:aa:10 removed from Base Radio MAC : 00:17:0f:da:f2:60 Interface no:0(802.11b/g)

somebody can help me?

[b.hsu]

Ensure that there are no duplicate IP address, conflicting with APs

[ethiel]

What version of code do you have? 4.0.155.0 had a known AP reboot bug. Each AP reboots every 40 hours d\by default.

More info here:

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCse64027

[joelkeranen]

I am running 4.0.179.8 and my APs do this too. I am running 1030 APs. They don't do it every hour but it is probably at least once every day or two.

When this happens I get a message for every AP Operation State Down: ... Cause = Unknown and shortly after that Operation State Up: ... Cause = Unknown.

If it was due to IP conflicts would only the APs with conflicts have problems? I am sure that there is no way that I have conflicting devices for every AP.

We are running Meditech client software on wireless laptops and every time this happens we end up with lost work and hung Meditech sessions.

I really need to get this fixed. I am beginning to regret going from Cisco 1100s to this new system.

I also get this message now and then:

AP's Interface:1(802.11b) Operation State Down: Base Radio MAC:00:0b:85:74:e9:90 Cause=Max Retrasmission

Does anyone know how to disable AP shutdown due to "Retrasmission"?

[4t-baron]

Hi,

I had the same problem for the last month, fixed two days ago. I have a Cisco 4400 controller with ver 4.0.155.5, with 1242 ap's, I am evaluating the Cisco 4400 vs the Aruba 6000. Anyway the short quick fix was either too put the AP's on the same vlan as the AP Manager (which worked for those AP's that I could put on the same VLAN) or put in a static ARP of the AP Manager on the router that it is attached too. The problem is the AP Manager is not updating the ARP table on the router, so depending on when the routers ARP cache clears, (every 4 hours for us), the AP Manager loses its connection to the AP's and they reboot. Since adding the static ARP to the router 48 hours ago, no AP's have rebooted, they were rebooting every 4 hours. This is a bug and is suppose to be fixed in the Nov/Dec time frame.

Hope this helps, it worked for me.

Terry

[aramos17428]

Can you post the router part where you configured the static arp to match the controller?

Thanks

Armando

[jdclingan]

I ping'd the ap-manager interfaces on the controllers and then did a 'show arp | inc "IP of interface' then I used the MAC it found for my static arp entry which was 'arp IP MAC arpa'

This helped somewhat but we ended up putting all of the AP's into their own AP specific vlan (not the same vlan as the controller interface). Hope that helps.