Max retries removing client

[sarnot]

I have 3 1300 bridges. One is configured as root with an external omni directional antenna. The other 2 are both non-roots with the internal antenna. Both remote sites have clear line of site and are less than 500m. Site (a) works fine, site (b) works fine sometimes and other times runs extremely slowly giving the following errors in the log.

1 Apr 27 16:00:45.254 K Error Interface Virtual-Dot11Radio1, changed state to up

2 Apr 27 16:00:45.253 K Information Interface Dot11Radio0, Station RecreationCentre 0011.21b9.1d70 Reassociated KEY_MGMT[NONE]

3 Apr 27 16:00:44.823 K Error Interface Virtual-Dot11Radio1, changed state to down

4 Apr 27 16:00:44.823 K Information Interface Dot11Radio0, Deauthenticating Station 0011.21b9.1d70 Reason: Previous authentication no longer valid

5 Apr 27 16:00:44.822 K Warning Packet to client 0011.21b9.1d70 reached max retries, removing the client

I have swapped the bridges and the problem has stayed with the site. I have relocated the bridge at site (b), changed cable and power injector. As previously stated when it is running it works well. Any ideas please?

[mchin345]

Use the mobile station configuration interface command to configure a 1300 series bridge as a mobile device. When you enable this setting on a bridge in non-root or workgroup bridge mode, the bridge scans for a new parent association when it encounters a poor Received Signal Strength Indicator (RSSI), excessive radio interference, or a high frame-loss percentage. Using these criteria, a bridge configured as a mobile station searches for a new parent association and roams to a new parent before it loses its current association. When the mobile station setting is disabled (the default setting) the bridge does not search for a new association until it loses its current association.

This command is supported only on 1300 series bridges.

http://www.cisco.com/en/US/products/hw/wireless/ps4570/products_command_reference_chapter09186a0080207efe.html#wp2593116

[sarnot]

Problem solved by manually selecting another channel. It was set to auto select the least conjested channel but for some reason it was getting interference from someone elses equipement. I ran the carrier busy test and chose what to me looked like a less conjected channel and it hasn't given an error since.