ssid creation for anchor mobility

[suthomas1]

Hi,

We have been tasked to do anchor mobility for one of our subsidaries.

I have two questions for this;

1. what is the actual use of mobility anchoring, isn't it better to just configure the WLC to provide normal connectivity instead of tunnelling the traffic to main controllers?

2. If we are creating an ssid "TEST"(Vlan 21) on the remote foreign controller, do we need this ssid interface( Vlan 21) to be created on the main controllers interface & the remote foreign controller also ?

Thanks for all inputs in advance.

[Scott Fella · Accepted solution]

Let me try to answer your question:

1. what is the actual use of mobility anchoring, isn't it better to just configure the WLC to provide normal connectivity instead of tunnelling the traffic to main controllers?

Anchoring an ssid is helpful when you have guest. Here is an example, if you have internal egress out of the HQ, you would have an anchor WLC at the HQ to terminate the guest ssid. This allows you not to have to create acl's at all your other sites, because then you would have to have a subnet at each location for guest.

2. If we are creating an ssid "TEST"(Vlan 21) on the remote foreign controller, do we need this ssid interface( Vlan 21) to be created on the main controllers interface & the remote foreign controller also ?

The TEST ssid needs to be created on both the foreign and the anchor WLC. The ssid has to match exactly except for the interface. You don't need to have a dynamic interface created in the foreign, just the anchor. The foreign WLC will tunnel traffic to the anchor using the management interface. The anchor WLC will receive the traffic from the tunnel in its management interface. The anchor will then have a dynamic interface in echo you want to place the traffic on.

Hope this helps you understand.

Sent from Cisco Technical Support iPhone App