Cisco Wireless Guest user management

cisco-isewlc

I am in bad situation where I was allowed to build wireless network for my company, I did so using WLC-2504 with 7 APs registered, but I was not aware of the limitations of generating random username and password with in WLC, I worked alot for this with cisco and other but could not get(cisco has option to generate 1 username/password for guest single point of time).

please help me get any additional component/license/tool where I can intergrate with my wireless setup and can generate ramdom username & password for our guest internet users. I came to know ISE can be used for that but still do not have much idea over it.

thanks and regards

Best Answer

For Creating local Guest user account try below link:

https://youtu.be/UiPBI2jkaxM

try the below link to create guest account under lobby admin:

https://youtu.be/eJ4leeOaQKM

Related Solutions

Cisco – Identifying a Cisco access point post-install

Depending on the version of WLC code that you're running, you can either manually disable the status LED on the AP or flash it by logging into the WLC and issuing a command... Then just walk around with your laptop and turn off / flash LEDs until you find the right AP.

To disable the status LED, use this...

config ap led-state disable AP27

To flash the status LED on two second intervals, you can use this...

config ap led-state flash 2 AP27

Be sure to revert the AP LED back to the original state, otherwise it could cause confusion down the road. You can see the LED configuration of your APs with

show ap led-state

Cisco WLC Mobility Group between 7.0.x and 7.5.x

I've never had to do a migration from 7.0 to 7.5 code in my environments.

The 2600 series APs were first supported in 7.2.110. http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn7_2_115_2.html#wp976967

The 5508 can run also 7.2. If you could get the mobility group/anchor to work with 7.2, then why you could downgrade it to 7.2 during the transition process.

You should be able to change CISCO-CAPWAP-CONTROLLER to your new 5508 controller so the 2600 APs will establish a connection with the new controller out of the box.
All CAPWAP and LWAP APs should remember the previous controller that they connected to and will attempt to establish a connection to those controllers before trying to go for the DNS lookup. See the CAPWAP controller discovery process

Thus, if one of your 1230 APs were to reboot - even if it does a DNS lookup for CISCO-CAPWAP-CONTROLLER (which would then return the 5508 IP), it should still connect to the old controller.

I would also assume that your new 5508 has SMARTnet? Open a TAC case with Cisco and see what they say!

Best Answer

Related Solutions

Cisco – Identifying a Cisco access point post-install

Cisco WLC Mobility Group between 7.0.x and 7.5.x

Related Topic