12.4(10b) on 1310G bridges

Unanswered Question
Sep 4th, 2008

Anyone run into any problems running 12.4(10b) on 1310G radios running as P-t-P bridges? I tried 12.4(10b)JA3 and got a really strange asymmetrical association rate; 1Mbps on one side and 54Mbps reported on the other. It ran extremely slow so I downgraded to 12.4(10b)JA and then the radio's kept hanging with a "%DOT11-2-RADIO_FAILED: Interface Dot11Radio0, failed - cmd busy -Traceback=" error which would eventually coredump. At my wits end, I installed 12.3(11)JA4 and everything worked like a champ. The radios were at 12.3(7)JA1 before I tried any of this, and I was simply looking to update the code.

Very strange, especially with the asymmetrical data-rate.

Anyone seen anything similar?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
didyap Wed, 09/10/2008 - 14:00

When all wireless LANS are defined on 1130AG and 1240AG access points converted to lightweight mode, and the radio environment is very busy, access point transmission attempts can be delayed. The 802.11g radios sometimes report this error:

%DOT11-2-RADIO_FAILED: Interface Dot11Radio0, failed - Radio command failed, cmd 121

(FF80,0,0) status 7F21 (5,0,0)

When the failure occurs, the radio restarts, all clients are disassociated, the failure is logged, and normal operation resumes.To resolve this issue Reduce the number of wireless LANs in use.

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode