In my scenario, I have an srv record setup with 4 ccm nodes, 1 and 2 are
equal weight and preferred, 3 and 4 have equal weights but are higher
weighted than the 1/2 pair. ccm1 and 2 are at a main data center, ccm 3
and 4 are at a remote DC. I want calls load balanced to 1 and 2, and in the
case
That may work fine based on how the SRV and options pings are configured...
but if you are counting on an SRV record to point to another CCM sub when
the primary is down (etc...), options pings will likely take the whole DP
down when a single host in the SRV goes unreachable.
On Wed, Jul 20, 2016
