Client Load Balancing - 3 Unique Pairs of CS
Here is a rough topology of the servers in our system:
Redundant DCI for 800xA Connectivity Servers (First 1/2 the DCI I/O)
Redundant DCI for 800xA Connectivity Servers (Second 1/2 the DCI 1/O)
Redundant AC800M Connectivity Servers
My Concern is I noticed that CS3 and CS4 had their affinity set to (1)CS1 (2)CS2 (3)All Nodes. I would expect not to see any affinity references to (CS1, CS2, CS5, and CS6) for CS3 and CS4. (i.e. The redundant CS pairs should only have affinity to themselves.) Is this a correct assumption?
With 3 unique CS pairs should I have 3 affinity objects defined in the Admin Structure, (1 affinity object for each redundant pair)?
I read a post by Stefan related to load balancing and he recommended adding the "All Nodes" group as the last affinity item for each client. Why is this? For Example if I have an Operator Client (OC) who has affinity to (1)CS5 (2)CS6 for AC800M connectivity there are no other CS nodes in the system that would provide additional AC800M connectivity. Adding "All Nodes" seems counter intuitive. What am I missing.
Thanks for the advice.
2. you can configure all your redundant pairs in 1 CS affinity object itself. no need for separate.
3. "All nodes" are need to be selected at end for each clients during affinity allocation.