James Carlson wrote:
[EMAIL PROTECTED] writes:
That aside, what I think is quite possible is for us to help people port
freevrrpd, ucarp, etc, to Solaris and for these to be made available
via websites such as blastwave. Is there being any risk for Sun in
that approach?
Actually, yes, and there's also substantial risk in discussing such
things on a mailing list. Unless the discussion is about how we're
going to _comply_ with the known IPR issues, I'd strongly discourage
anyone from trying to provide direct advice about those issues or
finding ways "around" them.
We can't take responsibility for what some third party does, but we
also can't ask them to do something like that _for_ us.
We are looking into the legal aspect of VRRP implementation. But in the
meantime it looks like there is a need for a HA solution for *both*
forwarder and server-type application that is cheaper,easier to maintain
and administer than Clustering.
As Jim pointed out in a earlier email, VRRP *as defined* by RFC 3768
only provides HA for forwarder- it would not work for server-type
application. CARP may be different ( not sure yet) . Another issue is
that CARP seems to reuse VRRP's IP protocol number( 112). THis might
affect CARP's deployment in a datacenter scenario where provider's gear
is running VRRP.
_______________________________________________
networking-discuss mailing list
[email protected]
