Sangeeta Misra writes:
> Can you kindly explain what specific problem you want to solve by
> running VRRP on Solaris? Assuming that you want it for high availibility
> of server-type application, why would you choose VRRP over Solaris'
> Clustering solution?
If it's for application support rather than for routing, it's worth
noting that VRRP doesn't actually solve that problem.
If you obey RFC 3768 correctly, when a new master is promoted, it must
*NOT* respond to any packets directed to the Virtual IP Address nor
use the address for the source of packets it sends, because it is not
the configured IP address owner. This makes VRRP useless for
applications, and useful only for forwarding. (And really only for
certain classes of manually-configured routes at that.)
Section 6.4.3:
- MUST NOT accept packets addressed to the IP address(es) associated
with the virtual router if it is not the IP address owner.
The fact that "VRRP" appears to solve this problem on Linux is more of
a bug than a feature, I think.
I agree that getting good information about the intended application
would help greatly here.
--
James Carlson, KISS Network <[EMAIL PROTECTED]>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
_______________________________________________
networking-discuss mailing list
[email protected]
