08-20-2013 09:08 AM - edited 07-04-2021 12:41 AM
I am bring up a new wireless network (complete with new controller and AP's) in a environment with existing temporay AP's. The tempory AP's will be replaced with the new wireless network once testing has been completed. Other than disabling the ssid is there anything else I can do to prevent the new wireless network from interfering with the temporary one. Is there any other parameter I can disable on the new controller? Maybe a way to turn off the radios?
Thanks for any sugguestions
Solved! Go to Solution.
08-21-2013 05:07 AM
nh6we,
Like some of the others that posted correctly, there are a few choices. The reason I mentioned to disable the admin status as opposed to using the AP Groups is that when you move an AP to a different group, the AP needs to reboot. It really comes down to your cutover. I script a lot of things and I would run two wireless environments in parallel but have the new APs admin down. This way when my customer is ready to cutover, he brings down the old wireless and I paste the commands to admin up all the AP's. takes less than a minute to do 500. This way I also don't have to worry about AP's not coming up just in case. So that's why I do it that way.
Sent from Cisco Technical Support iPhone App
08-20-2013 09:12 AM
I typically adim down the status of the AP until I'm ready to cutover. This way the AP is up and joined to the WLC, but the radios are disabled.
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"
08-20-2013 09:14 AM
Scott, within NCS or WCS where do I go to do this
Thanks
08-20-2013 10:01 AM
I usually script it an run it from the wlc cli. You should be able to create a template on wcs or ncs to disable the access point.
Sent from Cisco Technical Support iPhone App
08-20-2013 12:12 PM
Hello,
As per your query i can suggest you the following solution -
Disabling the Reset Button on Access Points Converted to Lightweight Mode
You can disable the reset button on access points converted to lightweight mode. The reset button is labeled MODE on the outside of the access point.
Use this command to disable or enable the reset button on one or all converted access points associated to a controller:
config ap reset-button {enable | disable} {ap-name | all}
The reset button on converted access points is enabled by default.
Hope this will help you
Hello,
As per your query i can suggest you the following solution -
Disabling the Reset Button on Access Points Converted to Lightweight Mode
You can disable the reset button on access points converted to lightweight mode. The reset button is labeled MODE on the outside of the access point.
Use this command to disable or enable the reset button on one or all converted access points associated to a controller:
config ap reset-button {enable | disable} {ap-name | all}
The reset button on converted access points is enabled by default.
Hope this will help you.
08-20-2013 04:03 PM
Other than disabling the ssid is there anything else I can do to prevent the new wireless network from interfering with the temporary one.
Put the new APs in a new AP Group and the old APs in the "default" AP group. Or the other way around ...
08-20-2013 08:38 PM
It's unfortunate others don't read the actual question before cutting and pasting comments that don't apply ..
Sent from Cisco Technical Support iPhone App
08-20-2013 09:08 PM
Hey,
Guess we have a new feature whcih is "out of the box AP" which will not broadcast any SSIDs till you uncheck that box..
Regards
Surendra
08-20-2013 09:18 PM
08-21-2013 05:02 AM
Abhishek,
If you read the subject of this post it say's, "Is there a way to DISABLE the RADIOS in a lightweight environment?". Not, "disable the reset button".
May I suggest that you take time to read the subject line and the posters question before suggesting something that doesn't make any sense at all. This will only make it confusing for others, especially the original poster.
Thanks!
Sent from Cisco Technical Support iPhone App
08-21-2013 05:07 AM
nh6we,
Like some of the others that posted correctly, there are a few choices. The reason I mentioned to disable the admin status as opposed to using the AP Groups is that when you move an AP to a different group, the AP needs to reboot. It really comes down to your cutover. I script a lot of things and I would run two wireless environments in parallel but have the new APs admin down. This way when my customer is ready to cutover, he brings down the old wireless and I paste the commands to admin up all the AP's. takes less than a minute to do 500. This way I also don't have to worry about AP's not coming up just in case. So that's why I do it that way.
Sent from Cisco Technical Support iPhone App
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: