How Do I Load Lagg Driver?: A Note About Custom Freebsd Kernels
How Do I Load Lagg Driver?: A Note About Custom Freebsd Kernels
biz/faq -
I've two Intel gigabit network card installed in HP server. I know how to setup bounding under CentOS
Linux, but I'd like to do same under FreeBSD. How do I setup link aggregation of multiple network
interfaces as one virtual trunk interface for the purpose of providing fault-tolerance and high-speed
links under FreeBSD 7.x server?
FreeBSD has lagg - link aggregation and link failover interface. The lagg interface allows aggregation
of multiple network interfaces as one virtual lagg interface for the purpose of providing fault-tolerance
and high-speed links.
Aggregation
Description
Protocols
Sends and receives traffic only through the master port. If the master port
failover becomes unavailable, the next active port is used. The first interface added is
the master port; any interfaces added after that are used as failover devices.
Supports Cisco EtherChannel. This is a static setup and does not negotiate
fec
aggregation with the peer or exchange frames to monitor the link.
Supports the IEEE 802.3ad Link Aggregation Control Protocol (LACP) and the
Marker Protocol. LACP will negotiate a set of aggregable links with the peer in
to one or more Link Aggregated Groups. Each LAG is composed of ports of
lacp the same speed, set to full-duplex operation. The traffic will be balanced across
the ports in the LAG with the greatest total speed, in most cases there will only
be one LAG which contains all ports. In the event of changes in physical
connectivity, Link Aggregation will quickly converge to a new configuration.
Balances outgoing traffic across the active ports based on hashed protocol
header information and accepts incoming traffic from any active port. This is a
static setup and does not negotiate aggregation with the peer or exchange
loadbalance
frames to monitor the link. The hash includes the Ethernet source and
destination address, and, if available, the VLAN tag, and the IP source and
destination address.
Distributes outgoing traffic using a round-robin scheduler through all active
roundrobin
ports and accepts incoming traffic from any active port.
This protocol is intended to do nothing: it disables any traffic without disabling
none
the lagg interface itself.
References:
The research for this FAQ is based upon the following man pages:
Article printed from Frequently Asked Questions About Linux / UNIX: http://www.cyberciti.biz/faq