I am experiencing issues with clients not getting ip addresses when they connect to an access point in H-REAP mode. There are 2 WiSMs at our headquarters and various 1242's around the world that connect back to the WiSMs. The most common reoccurrence of this issue seems to occur at the Bogota, Colombia location. The access point will be operating normally and the clients pull addresses from their local subnet (the AP is in H-REAP mode); at some point in the day, the AP will not assign ip addresses anymore and clients just pull 0.0.0.0. I am not sure if the AP is just going into standalone mode and cannot authenticate new clients because it cannot build a successful tunnel to the controller. I enabled H-REAP Mode AP Fast Heartbeat Timer State and tweaked the timeout, but it does appear to have remedied this issue. Is there any limitation on how many H-REAP AP's can be connected to a controller?
The WiSMs are running version 126.96.36.199 code.
Did you ever find a resolution to this problem? I am noticing the same thing with my HREAP access points. It seems to me that this problem occurs when the primary WAN link loses connectivity. So an outage even a slight one lasting about 10-15 seconds begins this problem. In many cases a simple reboot of the AP gets the DHCP working again.
Any insight you can provide would be most appreciated.
When we lose the connectivity, that is.. when the client is getting 0.0.0.0 IP , at this time what is the VLAN mapping?? do we see the correct vlan mapped? or is it changed??
All the clients get their IP reservations from the router and that is on vlan 1. I do not have vlan support checked for the APs on the WLC. Could that be my issue?
If I understand the technology correctly since we are getting an IP addresss from the remote WAN router passed to the clients at the remote site we are using local switching.
run the debug "debug client
OK I went to a site that I saw the wireless client getting 0.0.0.0
It looks like I am having trouble passing machine authentication and not getting an IP address before a user signs in. Looking at my ACS logs I see this is only happening with APs in HREAP mode.
I am having the same problem that client show an 0.0.0.0 address but when i check the mac address in the router i can see that the mac address binds to an ip address and i can ping the client on this ip address. So for my issue the client has an ip address which works but it does not show in the controller. In this network we are also using static wep keys so it is not an issue that the client has to authenticate first. Another strange thing is that some of the clients show an ip address and some do not and this is on the same access point.