cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3259
Views
0
Helpful
34
Replies

controller failover for different controllers

ejlbarcelon
Level 1
Level 1

Hi,

I have 3 existing controller with different model, capacity, version and configurations. I have purchased new controller that supports 100 APs.

Let's say WLC_A has a capacity of 25 APs and caters 20 APs, WLC_B has a capacity of 12 APs and caters 12APs, WLC_C has a capcity of 50 and caters 30APs. the NEW WLC, WLC_NEW has a capacity of 100 and will only have 18 APs registered to it.

What will be the requirement for me to have WLC_A, WLC_B, WLC_C failover to WLC_NEW, given that all OLD WLCs have different version and configurations? We are trying to make this as HA as possible.

34 Replies 34

Try to map the SSID to a wired vlan that is working and see if that works.

Sent from my iPhone

-Scott
*** Please rate helpful posts ***

Hi Scott,

Already done that also. in my wired connection to the same VLAN i can get an IP. when "local switching" is NOT enabled and AP is in H-REAP mode, i can obtain IP address. it is when the time when i put a check on "local switching" that my IP is lost. i litteraly see it suddenly disapear on my iPhone's WLAN setting and also when i check on my Laptop's ipconfig.

Well when local switching is not used, then traffic is tunneled back I the wlc. So that isn't going to prove anything. In your remote site, do you have a dhcp scope on the subnet the h-reap ap is in? I not, can you create one? I would then map your SSID to that vlan and test. Let me know if it works.

Sent from my iPhone

-Scott
*** Please rate helpful posts ***

Can you enable telnet/ssh in your AP, and try to ping your local DHCP server from the AP

Thanks

NikhiL

since client getting an ip on disabling local switching on wlan. either there is no working dhcp server at the site or wlan is not mapped to the right vlan(where dhcp server is hosted) under hreap tab.

from hreap, it may not ping the dhcp server ip, if it is on different vlan than native or no routing to dhcp server vlan from native vlan.

be sure to map wlan with native vlan id or appropriate vlan id for remote client under AP's hreap tab>> vlan support. if nothing is mapped here then the client would place the dhcp request on native vlan.

be sure to have reachable & working dhcp server on appropriate vlan where client can get ip.

otherwise try assign static ip address on client.

Review Cisco Networking for a $25 gift card