HREAP on LAP reboot

Unanswered Question
Jul 29th, 2009

Hi,

I've got HREAP working well, in that when an AP loses conenctivity with the WLC the AP continues to push out a LAN over radio and clients are authenticated back onto a radius server that the AP can see when disconnected.

I have one burning question: When an AP in HREAP power-cycles (and still cannot see the WLC), does it lose its HREAP config? I'll be really, really annoyed if it does.

This is what I'm seeing at the moment. A newly rebooted LAP just seems to spend its time saying

*Mar 1 00:22:39.872: capwapHandleDiscoveryTimer Expired

and not doing anything remotely HREAP.

Anyone had any issues with this?

Thanks,

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
LCC-IT Wed, 07/29/2009 - 07:30

is there a really obvious, basic setting that will force the AP to retain the HREAP config. I'm using 1131AG access points?

LCC-IT Wed, 07/29/2009 - 08:00

Our contact at cisco UK has told us that this is a feature to prevent config info being available if the LAP is stolen.

That means I've got one Cisco guy saying it should work and one saying that (by design) it won't. Which is which?

LCC-IT Wed, 07/29/2009 - 08:36

I still think this should work even though Cisco UK have said that it will not. My LAP that has been restarted has a few files in flash. they are as follows:

2 -rwx 40572 Jul 29 2009 15:25:17 +00:00 lwapp_reap.cfg

3 -rwx 0 Mar 1 2002 00:16:57 +00:00 validate.txt

154 drwx 128 Mar 16 2009 11:17:19 +00:00 c1130-rcvk9w8-mx

4 -rwx 296 Jul 29 2009 15:25:13 +00:00 env_vars

5 -rwx 29298 Jul 29 2009 13:42:29 +00:00 event.log

6 -rwx 5 Mar 16 2009 11:17:45 +00:00 private-config

9 drwx 256 Jul 29 2009 12:10:47 +00:00 c1130-k9w8-mx.124-18a.JA1

7 -rwx 7192 Mar 1 2002 00:00:31 +00:00 private-multiple-fs

The top one is a reap.cfg file, which when I do a 'more' command contain some basic information about the WLAN that is supposed to be being pushed out by the radio, but for some reason the LAP is ignoring this and spending time trying to get to a WLC that it can never reach - as i've created a fake WAN failure between the LAP and WLC.

Any ideas?

dancampb Wed, 07/29/2009 - 09:19

I have tested this in my lab and was able to reconnect and pull an IP after a AP in H-REAP standalone mode after a reboot of the AP. It will take a few minutes after the AP reboots before it will kick over to standalone mode. It will try to join a controller first. After it fails it will revert back to standalone mode and the WLAN will be available.

LCC-IT Wed, 07/29/2009 - 10:58

thanks for taking the time to test this for me. I'm currently running 5.2(?) on the WLC 4404-100. could you list what kit you have used and what version sw on each?

I've left the APs for about 20 minutes, with no failover to standalone, but at least I know that if someone can do it, then I can.

Thanks again

dancampb Wed, 07/29/2009 - 11:02

I ran the test with 6.0.182.0 running on the controller and a 1242 AP.

LCC-IT Thu, 07/30/2009 - 02:46

thanks for the help. I update the WLC software and the backup image on the WLC. I think the latter is what made the difference but thanks again.

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