H-Reap Issue

[Suresh Varghese]

I currently have a WLC 2125 located at my HQ and 4 LWAP-1131G AP's configured in H-reap modes in 4 respective branch offices connected to my HQ controller.

The issue is all 4 branch office AP's need to be restarted everyday in the morning for the clients to connect to the wireless SSID.

Currently it has been configured for WPA2 (8021.X + CCKM)

Can anyone let e know why this is happeneing and what needs to be done for resolving this issue.

Thanks

SureshV

[Roman Rodichev]

are you running latest software on the controller?

[Suresh Varghese]

My current software in the controller is 6.0.199.4, i am not sure if there is a later version than this

Software Version

6.0.199.4

[weterry]

what code version?

what exactly is not working?

Is the client not even seeing the ssid?

Not successfully associating to it?

Not passing 802.1x?

Not getting a DHCP?

Not passing traffic once they have a DHCP?

I know of some issues in earlier 6.0 or 7.0.98.0 where it is possible the client is associated and authenticated but can't get an IP address..... so if you think that is your problem and you aren't already on 6.0.202.0 or at least 7.0.98.218, you might want to consider that.

[Suresh Varghese]

my code version is 6.0.199.4

the issue is that all 4 branch office AP at a point of time in a day stops broadcasting the SSID's and the clients get disconnected.

After restarting the AP once it starts working again.

These branch office AP's are currently configured in H-Reap mode and connected to the HQ controller.

rest everything else works fine just that it gets disconnected every now and then.

[Roman Rodichev]

I see several resolved H-REAP caveats in 6.0.202

http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn6_0_202_0.html#wp746609

[weterry]

Ok, so the SSIDs just flat out stop working (as in clients can't even "associate").

Nothing specifically comes to mind, but you should probably try 6.0.202.0 to rule out any wasted troubleshooting efforts

Other than that,  I suggest a "show controller do0"  from when the AP is broken, and then when the AP is working (after reboot).

And then I'd get from the wlc: "show ap eventlog "    

[Suresh Varghese]

Thanks weterry,

I will check the same and get back.

rega