Prameet Chhabra writes: > " Today on Linux we use a bond network interface to enable > active/standby Ethernet links to insure network connectivity. This > works very well with our virtual IP address mechanism.
Solaris doesn't have anything that's directly equivalent to "bonding" in Linux. However, we do support 802.3ad Link Aggregation, which presents a single interface to applications, and which (unlike Linux bonding) uses standards-compliant mechanism to spread load, detect link failure, and recover. > However, based on what I know about SUN Multipathing, this will not > work with our virtual IP address mechanism. The issue is that our > Virtual IP address homes itself on a single logical interface (in > Linux it is a "bond" interface), where-as multipathing exposes two > interfaces to the application. For IPMP, the application doesn't "see" those interfaces and doesn't need to. Instead, an IP address is configured on one interface in the system. If that interface fails, then the system automatically removes that address and places it on another address in the same IPMP group. The application isn't involved in moving the address around or dealing with interface failure in any way. Yet another option is to use layer three (routing) mechanisms. The Solaris 'vni' interface provides a way to set up an IP address that doesn't move at all when physical interfaces fail, and the ifconfig "usesrc" keyword allows you to configure the system so that applications see that 'vni' address as being the preferred source address when sending packets. Routing is then used to switch among viable paths for data. -- James Carlson, Solaris Networking <[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]
