'Default Mobility Domain Name' for Anchor WLC needs to be mandatorily different from Foreign WLC?

[Muhammed Adnan]

Hello Experts,

It is understood that as per the design guide , security wise it is a best practice to have 'Default Mobility Domain Name' for Anchor and Foreign WLCs as separate. However functionality wise will it be an issue if it is chosen to have same 'Default Mobility Domain Name' on Anchor and Foreign WLCs.

[Rasika Nayanajith]

I think technically it will work. 

As pointed it is better to have separate mobility domain name in that way communication between two controllers limited as they belong to two different mobility domain

HTH

Rasika

*** Pls rate all useful responses ***

[Scott Fella]

I agree with Raskia.... it will work with the same MGN, but in actuality, you should keep it different. You don't want certain configurations to be shared to a guest anchor controller. Changing the anchor to just have _anchr at the end would differentiate the MGN. You would just need to update the mobility group members to reflect any changes.

[Muhammed Adnan]

Thank you Scott

[Muhammed Adnan]

Thank you Rasika