I am implementing this currently. The foreign controller should be reachable by the anchor controller on which interface? the management interface ? Please specify that
What a detailed description on creating guest WLAN on cisco WLC. The teaching and explaining style is fantastic. Appreciate you for making such worthy content. Thank you so much for sharing your valuable knowledge and experience. This video helped me alot .
Thanks for sharing the knowledge. I have one question what is the difference between mobility anchor and auto mobility anchor. Or better if you can explain what is auto anchoring in Layman so that I can understand the article on auto anchoring. Thanks in Advance.
The mobility anchor concept is for supporting the mobility of the Wireless Clients mainly the client roaming. For example, If we have more than one WLC on the same campus then there are chances that clients Roam from one AP that connects to WLC1 to another AP that connects to WLC2. In this case, the Global Mobility members will be able to accept that the client and give a seamless experience to the end-user. The other use case is the APs can use the mobility member information from connected/joined WLC and fallback to those Mobility members in-case of connected WLC failure. This is not based on the HA/Priming configuration of the AP, this is part of the CAPWAP discovery algorithm on Cisco WLC. But the functionality of the auto anchor is to control the Data Plane of the WLAN/SSID. When you configure the auto anchor under a WLAN, the foreign WLC will tunnel the entire Data to Anchor WLC using an EOIP/CAPWAP tunnel based on the mobility model(Old/New Mobility) configured. In this scenario Foreign will be responsible for Control Plane and Anchor will be responsible for Data Plane. This is mainly used on Guest Access to isolate the Guest Traffic from Corporate Traffic and terminate in DMZ. But some companies use this for other types of SSIDs based on their use cases that need complete traffic Isolation. I will not be able to put the entire theory here in this reply :), hope this explanation clears some of the basic doubts. You try to get your hands dirty by going through these scenarios in the LAB to get a better understanding.
@@CiscoNetworking Thanks Jaison, network isolation(or guest -tunneling) is what we use guest anchor controller for(this is what I understood). Now only question left is what is special in Auto-Anchor Mobility compare to what we can get through a guest anchor controller setup. Or the word auto is nothing here it's just like normal guest anchor controller setup. Please help.
Excellent video very descriptive. What if we need to change the SSID name from Guest-WLAN to let's say Visitors-WLAN. Do we have to create new pair of WLANs at both ends or this can be renamed at both WLCs ?
Hi Jason Thank you for the wonderful video it's really good Can you please update video of configuring guest Wlan without anchor controller? That means can we configure guest Wlan with existing WLC? Thank you
If you dont want to use Anchor WLC and your company IT security policy allows then you can always use Local WLC for guest access. Using Local WLC for Guest access is not recommended as the Guest IP packets are going to get exposed to the Corporate infrastructure if we use the Local WLC. Creating Guest SSID is similar to any other SSID that meets the requirements of a Guest Access.
I am implementing this currently. The foreign controller should be reachable by the anchor controller on which interface? the management interface ? Please specify that
IP that displayed on your Mobility page of each WLCs should be reachable in both directions
@@CiscoNetworking Thanks jaison
What a detailed description on creating guest WLAN on cisco WLC. The teaching and explaining style is fantastic. Appreciate you for making such worthy content. Thank you so much for sharing your valuable knowledge and experience. This video helped me alot .
Yes, really helpful. Thanks Jaison
Keep up the good work Jaison !!!
Thanks for sharing the knowledge. I have one question what is the difference between mobility anchor and auto mobility anchor. Or better if you can explain what is auto anchoring in Layman so that I can understand the article on auto anchoring. Thanks in Advance.
The mobility anchor concept is for supporting the mobility of the Wireless Clients mainly the client roaming. For example, If we have more than one WLC on the same campus then there are chances that clients Roam from one AP that connects to WLC1 to another AP that connects to WLC2. In this case, the Global Mobility members will be able to accept that the client and give a seamless experience to the end-user.
The other use case is the APs can use the mobility member information from connected/joined WLC and fallback to those Mobility members in-case of connected WLC failure. This is not based on the HA/Priming configuration of the AP, this is part of the CAPWAP discovery algorithm on Cisco WLC.
But the functionality of the auto anchor is to control the Data Plane of the WLAN/SSID. When you configure the auto anchor under a WLAN, the foreign WLC will tunnel the entire Data to Anchor WLC using an EOIP/CAPWAP tunnel based on the mobility model(Old/New Mobility) configured. In this scenario Foreign will be responsible for Control Plane and Anchor will be responsible for Data Plane. This is mainly used on Guest Access to isolate the Guest Traffic from Corporate Traffic and terminate in DMZ. But some companies use this for other types of SSIDs based on their use cases that need complete traffic Isolation.
I will not be able to put the entire theory here in this reply :), hope this explanation clears some of the basic doubts. You try to get your hands dirty by going through these scenarios in the LAB to get a better understanding.
@@CiscoNetworking Thanks Jaison, network isolation(or guest -tunneling) is what we use guest anchor controller for(this is what I understood). Now only question left is what is special in Auto-Anchor Mobility compare to what we can get through a guest anchor controller setup. Or the word auto is nothing here it's just like normal guest anchor controller setup. Please help.
Excellent video very descriptive. What if we need to change the SSID name from Guest-WLAN to let's say Visitors-WLAN. Do we have to create new pair of WLANs at both ends or this can be renamed at both WLCs ?
Once a WLAN is created changing SSID is not an option, you can create a new one. If you have Anchor then you have to create WLAN both sides
Thanks
Hi Jason
Thank you for the wonderful video it's really good
Can you please update video of configuring guest Wlan without anchor controller?
That means can we configure guest Wlan with existing WLC?
Thank you
If you dont want to use Anchor WLC and your company IT security policy allows then you can always use Local WLC for guest access. Using Local WLC for Guest access is not recommended as the Guest IP packets are going to get exposed to the Corporate infrastructure if we use the Local WLC. Creating Guest SSID is similar to any other SSID that meets the requirements of a Guest Access.
thx very informative
How we create by mobile
Didn't got what you want to configure using mobile
Thanks