AP1532 as WGB - no reassociation

[NotKnown12880]

Some times, these models running as WGB disassociate due to roaming and just stop trying to reconnect.  

Sep 18 11:33:49.958: %DOT11-4-UPLINK_DOWN: Interface Dot11Radio0, parent lost: Missed beacons
Sep 18 11:33:59.970: %DOT11-4-CANT_ASSOC: Interface Dot11Radio0, cannot associate: No Response
Sep 18 11:34:11.814: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
Sep 18 11:34:12.814: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
Sep 18 11:34:22.098: %DOT11-4-CANT_ASSOC: Interface Dot11Radio0, cannot associate: No Response

After the last log entry, the WGB just never tries to reconnect. resetting the interface or rebooting the WGB reconnects it.  Is there some code that could be added to try to reconnect at regular intervals or is this issue by design? 

antenna gain 4
station-role workgroup-bridge
mobile station minimum-rate 12.0
mobile station period 20 threshold 70
bridge-group 1
bridge-group 1 spanning-disabled

thx

[balaji.bandi]

What code running on the Device ?

try upgrade to new CODE and check ?

is this issue by design? 

we do not know how your design and installed AP here.

have you done any site survey and installed AP in right location ?

how kind of client base you have ? how many AP in the place ?

may be some tips to check :

https://community.cisco.com/t5/wireless-mobility-knowledge-base/wgb-roaming-internal-details-and-configuration/ta-p/3120936

[NotKnown12880]

Thanks for replying B. 

Yes, we have done a site survey and are on release 153-3.JK7. I can now see there JK11 is available, I will try an upgrade, but dont think this will make a differense. coverage is good, just a few clients. 

[balaji.bandi]

Try upgrade and see how that go, if not we still need to investigate any way for other elements which stopping for you to join.