04-06-2011 09:02 AM - edited 07-03-2021 08:03 PM
Hi,
I'm going to setup up an AP 1242 in a remote area to support b/g client via a 802.11a bridge link (all using AP 1242).
Before the deployment, I tested the configuration in a lab environment. However, I found the bridge link will come up a while and suddenly gone. Resetting the root AP or the non-root AP cannot bring the connection up again. Sometimes, when I shutdown the b/g radio (radio 0) of the remote AP, the bridge link will be established again. Following is the log from the root AP.
Thanks!
*Apr 4 12:24:05.013: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to r
eset
*Apr 4 12:24:05.054: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Apr 4 12:24:05.665: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthern
et0, changed state to down
*Apr 4 12:24:06.009: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio
1, changed state to up
*Apr 4 12:24:06.013: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio
0, changed state to down
*Apr 4 12:24:07.054: %LINK-3-UPDOWN: Interface BVI1, changed state to down
*Apr 4 12:24:16.091: %DOT11-4-CANT_ASSOC: Interface Dot11Radio0, cannot associa
te: No Response
*Apr 4 12:24:16.811: %LINK-3-UPDOWN: Interface BVI1, changed state to up
*Apr 4 12:24:17.811: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, chan
ged state to upInternal error: command failed <<<< Internal error: command failed ??????
<<<<don't know the meaning of this message
*Apr 4 12:27:22.206: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to r
eset
*Apr 4 12:27:22.233: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Apr 4 12:27:22.233: dot11_mgmt: bad cookie returned from driver for mac 003a.9 <<<<<003a.928.dad0 is radio 1 / non root bridge of remote AP
928.dad0(expected 0x00000000, got 0x010ADAB0) - force driver to delete client <<<<<don't know the meaning of this message
*Apr 4 12:27:22.235: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to r
eset
*Apr 4 12:27:22.262: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Apr 4 12:27:23.513: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthern
et0, changed state to up
*Apr 4 12:27:26.993: %DOT11-6-ASSOC: Interface Dot11Radio1, Station T9_QC168_Ca
ntil 003a.9928.dad0 Reassociated KEY_MGMT[NONE]
*Apr 4 12:27:28.465: %DOT11-4-MAXRETRIES: Packet to client 003a.9928.dad0 reach
ed max retries, removing the client
*Apr 4 12:27:28.465: %DOT11-6-DISASSOC: Interface Dot11Radio1, Deauthenticating
Station 003a.9928.dad0 Reason: Previous authentication no longer valid
*Apr 4 12:27:28.467: %DOT11-4-MAXRETRIES: Packet to client 003a.9928.dad0 reach
ed max retries, removing the client
*Apr 4 12:27:31.673: %DOT11-6-ASSOC: Interface Dot11Radio1, Station T9_QC168_Ca
ntil 003a.9928.dad0 Reassociated KEY_MGMT[NONE]
*Apr 4 12:27:32.687: %DOT11-6-ADD: Interface Dot11Radio1, Station 003a.9926.e76
0 Associated to Parent 003a.9928.dad0
*Apr 4 12:28:46.178: %DOT11-6-DISASSOC: Interface Dot11Radio1, Deauthenticating
Station 003a.9928.dad0 Reason: Sending station has left the BSS
*Apr 4 12:28:46.179: %DOT11-6-DISASSOC: Interface Dot11Radio1, Deauthenticating
Station 003a.9926.e760
*Apr 4 12:28:46.181: %DOT11-6-ASSOC: Interface Dot11Radio1, Station T9_QC168_Ca
ntil 003a.9928.dad0 Reassociated KEY_MGMT[NONE]
*Apr 4 12:28:47.196: %DOT11-6-ADD: Interface Dot11Radio1, Station 003a.9926.e76
0 Associated to Parent 003a.9928.dad0
*Apr 4 12:29:15.132: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthern
et0, changed state to down
*Apr 4 12:29:32.442: %DOT11-4-MAXRETRIES: Packet to client 003a.9928.dad0 reach
ed max retries, removing the client
*Apr 4 12:29:32.442: %DOT11-6-DISASSOC: Interface Dot11Radio1, Deauthenticating
Station 003a.9928.dad0 Reason: Previous authentication no longer valid
*Apr 4 12:29:32.443: %DOT11-6-DISASSOC: Interface Dot11Radio1, Deauthenticating
Station 003a.9926.e760
*Apr 4 12:29:32.444: %DOT11-4-MAXRETRIES: Packet to client 003a.9928.dad0 reach
ed max retries, removing the client
*Apr 4 12:31:10.285: %DOT11-4-CANT_ASSOC: Interface Dot11Radio0, cannot associa
te: Rcvd response from 003a.9928.2660 channel 6 2560
*Apr 4 12:31:18.286: %DOT11-4-CANT_ASSOC: Interface Dot11Radio0, cannot associa
te: AssociatingInternal error: command failed
*Apr 4 12:31:27.021: dot11_mgmt: bad cookie returned from driver for mac 003a.9
928.2660(expected 0x00000000, got 0x010ADAB0) - force driver to delete client
*Apr 4 12:31:29.107: %DOT11-4-UPLINK_ESTABLISHED: Interface Dot11Radio0, Associ
ated To AP T9_SML_LT2_AP2 003a.9928.2660 [None]
*Apr 4 12:31:29.108: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Apr 4 12:31:30.108: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio
0, changed state to up
Solved! Go to Solution.
04-06-2011 02:40 PM
I guess it should be better to ask the full show tech and show log from both units, how many antennas, and what antennas its using at each side, distance...
04-06-2011 09:33 AM
Please post the Root and the Non root config here..
Regards
Surendra
04-06-2011 02:40 PM
I guess it should be better to ask the full show tech and show log from both units, how many antennas, and what antennas its using at each side, distance...
04-07-2011 02:31 AM
Thanks dmantill for reminding me to revisit the antenna and related stuff.
As the setup is in a lab environment, the APs are put on a work bench next to each other, therefore, the radio output power was lowered.
After adjusting the output powers, it works as expected.
Thanks Surendra and dmantill.
04-07-2011 05:00 AM
Hey, thats nice to hear!! thanks for posting on CSC !!
04-07-2011 07:03 AM
GREAT! please rate the post and mark it as solved!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide