Steffen Weiberle writes:
> Emmanuel Alao wrote:
> > Hi everyone
> >
> > I have got a box that has two network interfaces and what I am trying to do
> > is to bind both interfaces in to one single interface so I can make they
> > physical interface are both running and can share the network load
> >
> > similar to what is done here
> > http://www.cyberciti.biz/tips/linux-bond-or-team-multiple-network-interfaces-nic-into-single-interface.html
>
> Based on 6. in
> http://www.cyberciti.biz/howto/question/static/linux-ethernet-bonding-driver-howto.php
>
> similar features are IP Multipathing (active/passive) and link
> aggregation via dladm. The latter supports 802.3ad aggregation.
They're "similar" but not at all the same. Solaris doesn't have a
feature that's identical to Linux "bonding," nor does Linux have a
feature that's identical to IPMP.
Among the differences:
- Linux bonding doesn't appear to have a way to perform inbound load
spreading (or relies on peer configuration to do so). IPMP does,
but requires multiple IP addresses. 802.3ad does it automatically
with no extra addresses.
- Linux bonding requires specific configuration of probe targets, if
probing is used, and relies on ARP. IPMP does automatic target
selection based on the kernel forwarding (routing) table, and uses
ICMP Echo. 802.3ad uses LACP, which is quite different, and
doesn't test health through intermediate switches.
- Linux bonding (in round-robin mode) assumes trunk support on the
peer. IPMP keeps the interfaces separate, so special support
isn't needed, regardless of mode. 802.3ad generally needs peer
support.
- Linux bonding uses a single MAC address -- this is related to the
points above. IPMP uses _all_ of the addresses in the group.
802.3ad is also a single-MAC-address feature.
- Linux bonding exposes only a single interface to IP applications.
IPMP currently exposes all underlying interfaces as links to the
same subnet (this is mostly considered a defect and will change
with the IPMP refactoring done by Clearview). 802.3ad also
presents a single interface, at least in the dladm incarnation.
(The older Sun Trunking product had other usage models available.)
If you need to interoperate with Linux bonding, then I think you want
to set up an aggregation using dladm, but with "-l off" (LACP
disabled).
If you need to set up a system that's _similar_ in characteristics to
Linux bonding, then I'd suggest IPMP.
--
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]
