Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

**HELP** Avaya wireless clients roaming Cisco AP350s - Slow / inconsistent

We have a number of wireless clients (running WINNT 4.0) all with Avaya PCMCIA cards connecting to a pure Cisco environment:

8 x Catalyst 3550-24 switches with 1000BaseSX uplinks connecting each throughout a warehouse environment. (Spanning tree is disabled on all ethernet ports but is enabled on the uplinks for the fibre ring topology).

Ther are 3 x AP350 (2.2dBi) all connected into the switches around the network. The access points are connected at 10Mb/half duplex. All APs have a common SSID which the clients are configured with. The environment is a flat subnet with no VLANs and no WEP or similar additional security.

All APs are configured as root APs.

The APs are configured for non-aironet clients and teh aironet extensions are off. CDP is running OK throughout the warehouse and all seems to be OK.

When an Avaya client roams from one AP domain to anotherthe AP denies initial association stating it must authenticate before associating, then a second later the client associates correctly. Once the client has associated and authenticated to all APs it appears to function OK, but the associations list clears out after a period of 30 minutes by default, causing the client to reestablish itself. During the authentication time the delay is long enough to time the client application out and cause interruption.


1) Do the access points (via the ethernet) pass any client associate information to allow better roaming.

2) Whare are the optimum settings when using non-aironet clients.

3) Are there any known issues with the use of third party cards such as Avaya.

Any suggestions - help is greatly appreciated.

New Member

Re: **HELP** Avaya wireless clients roaming Cisco AP350s - Slow

I remember that in the early days of 802.11, there was an issue with the AVAYA products , formerly Lucent, against former Aironet / CISCO AP's. The solution was to change the Fragment treshold value. I can't remember what value.


CreatePlease login to create content