Aironet 340 Bridges with a Cisco 350 not associating

[admin_2]

The call came to me that the bridges were not talking anymore. I reload the configs but this didn't resolve the issue.

The 340s are running 8.80 and the one 350 is running 12.04. This setup has been working for several months. The two Aironet 340 Bridges are non-root to the root 350 bridge. The configuration on both 340 are identical with the obvious exceptions (IP address and Name).

I can not ping, telnet or http to the configs. The only access I have is the console serial interface.

1. BR500 - Non Root mode

| |

| Clients

|

2. BR350 - Root mode

|

|

|

3. BR500 - Non-root mode

|

Clients

Could it be a spanning tree problem? When I switch Site 1 to client_only from Bridge_Only, it re-associates with a message about spanning tree disabled but I still cannot ping, telnet or http to any of the three.

Coule it be encryption? When I disable encryption on one then I can ping it. If I disable all three encryptions I am back to no ping, telnet, or http.

I have taken all three back to default configs and applied settings one at a time. Exhausted. Any recommendations?

[ctripp]

Hi,

Could very well be a spanning-tree issue, see below.

http://www.cisco.com/en/US/partner/products/hw/wireless/ps458/prod_release_note09186a00801d572a.html

Cisco Aironet 350 Series Bridges Incompatible with 340 Series Bridges

Cisco Aironet 340 and 350 Series Bridges can be connected to the same LAN segments, but they cannot communicate wirelessly. Although you can disable STP on non-root 350 series bridges, 350 and 340 series bridges are not designed to interoperate. If you use both 340 and 350 series bridges on your network, make sure the 340 series bridges have radio bridge links only to other 340 series bridges, and that 350 series bridges have radio bridge links only to other 350 series bridges.

Regards,

Charlie.