I need assistance in aquiring documentation to setup N+1 redundancy & load balancing between two seperate guest anchor controllers installed in seperate data centers. Can you explaing how it should be setup or point me in the right direction for documentation? If you can't point me in the right direction to aquire documentation; can you answer the following questions?
1) How do I setup my mobility groups on my guest anchor controllers installed in the DMZ? Should both guest anchor's be in the same mobility group.
2) Do both guest anchors share the same virtual IP or do they need to be seperate (DMZ01 - 184.108.40.206 / DMZ02 - 220.127.116.11)? I think seperate!
3) Are there any configuration parameters on the guest anchors for load balancing?
4) Do either on of the guest anchors need to be setup as a master controller? I'm not sure?
5) Are there any configuration parameters on the foreign controllers for load balancing?
6) How do I setup my foreign controllers? Should both guest controllers be added to the mobility group on the foreigh controller? I would think both of them would be added to the foreign controller mobility group.
7) Should both guest anchors be added as an anchor on the WLAN? I would think both controllers would need to be added as anchors under the WLAN!
8) Am I missing anything here? This is how I think it should logically work?
Here is my $.02 on how it works
1) Typically, the Anchor WLC is in a different Mobility Group than the Foreign. I'd think that having both Anchors in the same mobility group (different than foreign) might be preferred. (I'd go with Example #1)
2) 18.104.22.168 should be sufficient across all controllers. If your DNS server limits what IP addresses you can actually define, then you'll have a problem. But generally speaking, the virtual interface should be something that does not exist in your network, and using the same IP/Name/Cert on multiple controllers should work fine.
5) No.... I believe load-balancing is round-robin, but I could be wrong.
6) Just make sure all controllers in defined in the mobility domain (different groups, but in the mobility management list on each WLC)
7) Yes... See #5
The above answers may not be factual. They are how I would set this up, and I'm fairly certain it would work.
The key point is that each controller needs to be mobility aware of the others.
Your foreign WLC should list both anchors as an auto-anchor (I think it round-robins the associations)
Each Anchor WLC should only list itself as the anchor (I assume).
I'd suggest opening a TAC case. However, you may want to get it all set up first. If it is configured but isn't working when you open the case, it is easier to troubleshoot what is broken. If you open a case now, you'll just have to configure it and see if it works before anyone can see what is wrong.