Radio0-802.11B Settings

Unanswered Question
Jul 10th, 2007
User Badges:

I have four 1200 AP series installed and i found that their radio setting are set to 'disable' but weird things is, the software and hardware status is still up and i don't have any problem in the connectivity.

I have a backup unit and i checked the status of the radio settings, it is set to 'enable' when i tried to disable it, eventually my radio interface went down as expected. Please advise. i have attached the screenshot of one of the APs that i am talking to.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
vassiliev Wed, 07/11/2007 - 21:42
User Badges:

Excuse me,can you use CLI to shutdown the radio interface?!

vlad110226 Wed, 07/18/2007 - 16:58
User Badges:

yes i can use CLI to shutdown the radio interface and then when i viewed the radio interface via web access, it shows that it is disabled but when i activate it again using CLI, web access viewed for radio interface is UP but the "Disabled" button is is still ticked. Weird isnt it?

bcolvin Thu, 07/19/2007 - 12:33
User Badges:
  • Bronze, 100 points or more

FYI: I have had similar experiences with the GUI, it seems to be related to Windows or somethig caching the WEB pages, you are viewing a cached page not the current status. Usually exiting the prowser and reconnecting to the AP will cause the page to display corectly. A pain but it works.


vlad110226 Thu, 07/19/2007 - 18:19
User Badges:

Hi Bill..first of all thank you for sharing..i did reconnect to my AP again and again but still the i mentioned using CLI when i shutdown the radio interface, in web access it indeed shows that my radio is disabled..weird things is when i enable again using CLI, in web browser view it is now activated but the "Disable" button is still ticked.. hmmmnn anyway, there is no current issue on my AP, just curious..thanks again..

cobbc Tue, 07/24/2007 - 06:01
User Badges:

I think you need to refresh the web page, not just exit out of it and if it still shows incorrectly, you need to call Cisco and create a bug for it.


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