1300 Wbridge, point-to-point setup

[thisisshanky]

I have done several of these installs in the past, trying to get a new setup for one of my customers. I usually configure them before taking them to the site, even test them to see if they are associating before hand. So I started with two 1300 bridges, only using wep keys, one ssid, channel 1, two 13.5 db yagi antennas. The two wont associate when I test it. The Nonroot keeps giving me the following error

Mar 1 01:05:26.449: %DOT11-4-CANT_ASSOC: Interface Dot11Radio0, cannot associate: Reason 40.

I have changed antennas, with no change. I tried with two other bridges and they work without any issues.

The IOS on these were 12.3.2JA when I tested this setup.Then I upgraded to 12.3.4JA to check if that helps, but same error, Downgraded to 12.2.15JA and that did not help either. Have not tried 12.2.15XR yet.

Seems to me like a bad hardware. The funny part is, I get a similar but not same error, when I swap the roles of the root and non root bridges

*Mar 1 01:15:14.152: %DOT11-4-CANT_ASSOC: Interface Dot11Radio0, cannot associate: Associated

Any body have encountered something similar ?

[thisisshanky]

Some new messages..

Mar 1 00:49:03.137: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to do

wn

*Mar 1 00:49:03.138: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to r

eset

*Mar 1 00:49:13.666: %DOT11-4-CANT_ASSOC: Interface Dot11Radio0, cannot associa

te: No Response

*Mar 1 00:49:18.921: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to do

wn

*Mar 1 00:49:29.666: %DOT11-4-CANT_ASSOC: Interface Dot11Radio0, cannot associa

te: No Response

*Mar 1 01:05:33.730: %DOT11-4-CANT_ASSOC: Interface Dot11Radio0, cannot associa

te: Rcvd response from 0013.1985.9bf0 channel 9 250975

*Mar 1 01:05:34.729: %DOT11-4-CANT_ASSOC: Interface Dot11Radio0, cannot associa

te: Authenticating

[thisisshanky]

Never mind, one of the bridges were faulty

[ashish_gupta]

hi

was the non-root one faulty or was it root. also do you have any idea where can we get those reasons and their explanation like ur log showed reason 40 .

regards

ashish gupta

[thisisshanky]

If i remember right, the non-root was faulty. I could not get answers to the explanation of the messages, even though I could use error message decoder to decode it. Does not yield any useful output.As usual it says "Copy the message and give it to TAC".

The best way to test in such situations, is to configure the bridge as an AP and try to associate a wireless client to it. This will tell you if the bridge is faulty or not.