ottomeister wrote:
On 9/5/07, Quayle, Bill (ETS) <[EMAIL PROTECTED]> wrote:
As it turns out, the root of the problem was caused by one of the Cisco
dudes fat-fingering a config on an uplink. All six servers in two
datacenters are quite happily awaiting our DTU deployment! We utilize
multicast quite substantially in our production applications, so it
surprised me that this wasn't working out of the gate.
This being an "unsupported configuration" begs the question, though...
Is there a better way to do this? In order to support my SLA on the
DTU's, I need to share my group across datacenters. We don't route
VLANs across datacenters, which only leaves multicast routing. It seems
like a very elegant solution, so I'm just curious... What does Sun do?
Sun, at least among the major SF Bay Area campuses, uses
multicast across subnets. The IT guys know that if multicast
stops working then the Sun Ray service across these
campuses will be disrupted, but they're confident that it
works and will continue to work.
This isn't a fair comparison, Otto, because each campus
has a separate FoG. So, we're not connecting our FoGs
via multicast, which I think is the issue at hand.
We don't do failover between campuses, at least via
FoGs.
-Bob
An alternative would have been to create a VLAN segment
in common across all of the servers, which means that they
could fall back to using broadcasts if multicast failed. They
could still do that if multicast suffered a meltdown but
apparently it's been pretty solid so far.
OttoM.
__
ottomeister
Disclaimer: These are my opinions. I do not speak for my employer.
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
