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 18.104.22.168 code.