What SP1 provides is redundancy and HA (e.g. multiple active SUPs per primary), 
and delayed failover (e.g. intelligence of SUP agent in ConfigMgr client, but 
only 2hrs 2 min after losing contact with current SUP).  The new capabilities 
of the SUP role does not provide load-balancing...only redundancy and HA of the 
role.

If you're looking for automatic failover (e.g. no delay) and load-balancing, 
your best best is to use SUP in an NLB cluster, or F5.

Just for clarity - when using NLB or F5 - all of the SUPs in the site share/use 
a single virtual name for the cluster/farm, so clients only use the one single 
virtual name of the SUP(s) to communicate with.  This is actually what provides 
the automatic failover mechanism...the NLB or F5 redirecting clients to the 
next available SUP in the cluster/farm when one or more SUPs become unavailable.

If the delayed failover is of concern and/or there is a compelling need for the 
SUP role to load-balanced, then go with the NLB cluster (e.g. Windows or F5).  
If not, then stick with the simpler native SP1 functionality.

Sent from my iPad

On Oct 4, 2013, at 7:59 PM, "Matt Tinney" 
<[email protected]<mailto:[email protected]>> wrote:



In SP1 of ConfigMgr2012, update point switching provides fault tolerance 
between multiple update points at a single site. I believe the biggest concern 
I have is the time it takes a client to go from its active SUP to another SUP 
in the event its not online/available?

How many of you are using this and allowing ConfigMgr 2012 to manage the load 
balancing and fault tolerance between multiple SUP's.

Originally, was looking at utilizing F5 to configure the SUP in an NLB Cluster 
but wanted to also explore the possibility of the native functionality.

Any experiences to share would be wonderful!


--
Matthew Tinney
(206) 778 4432
Windows Management Experts, Inc
www.windowsmanagementexperts.com<http://www.windowsmanagementexperts.com/>

________________________________


DISCLAIMER: This is a PRIVATE AND CONFIDENTIAL message for the ordinary user of 
this email address. If you are not the intended recipient, please delete 
without copying and kindly advise us by e-mail of the mistake in delivery. 
NOTE: Regardless of content, this e-mail shall not operate to bind 1E to any 
order or other contract unless pursuant to explicit written agreement or 
government initiative expressly permitting the use of e-mail for such purpose.



Reply via email to