I know a lot of documentation says the virtual ip should be 184.108.40.206 and that's what I've used previously. But I recall a friend of mine saying the 220.127.116.11 had been allocated and would actually be used on the internet hence that's a bad address to use now. I know cisco recommended another one (which also is public but would never be used). I've totally forgotten what the new recommended IP address should be, could someone help me out here?
Solved! Go to Solution.
1. How come primary and secondary wlc has same Management IP?
If you doing HA, then both unit will share same management IP address. They have unique IP on "redundancy management" interface in order you to manage them individually.
2. Virtual IP: is this something I have to initialise locally to the controller or it should be advertised to the network (APs
No, this is not a routable within your network. Just define it on your WLCs which need to be in same mobility cluster.(ie same virtual IP address in all your WLCs as long as they establish mobility peering)
*** Pls rate all useful responses ***
Virtual IP is used for three things:
* DHCP proxying (WLC hides the real DHCP server identity to the clients and shows this instead)
The Virtual IP address does not really matter here.
* Guest login splash page redirection. If WLC is to present the guest login screen it uses the
Virtual IP. Should be a non-existing, non-routable address.
* Mobility tunnel creation to other WLC´s. All WLCs must share the same Virtual IP address
to form a group besides the group/domain configuration as well as same SW version
(well, its recommended but there are exceptions where different versions work)
Some cloud proxies have started to use 18.104.22.168 for their proxy, and this breaks the guest login
splash page presentation if used. If virtual IP is changed the mobility tunnels might break, so this
should be changed for all WLCs in the same Mobility Domain in same service window.
We are facing the same issue. We have over 40 WLC 5508 all with same virtual 22.214.171.124
Any recommendations on how to maybe leave 126.96.36.199 in place with a DNS type work around? Or suggest easy way to change all? Big issue is when you change virtual 188.8.131.52 address you have to reboot (x40) the WLCs for it to take affect...!!
Thanks in advance
Thanks for your input
When guest try to connect---they have to click refresh or launch new browsers several times.... in order to get web auth sign on screen to pop up....some never get it (I am told)
If we change the anchor to 192.x.x.x we will break all remote WLCs being able to access guest... we will not be able to change address and reboot all 40+ in one weekend...to much down time and possible issues...