Solaris tip of the week: Link Aggregation and Logical Interfaces
This tip describes two options for configuring network interfaces: 1) Link aggregation (IEEE 802.3ad), which uses Ethernet network cables/ports in parallel to increase the link speed above the limit of any single cable or port and increases redundancy for higher availability, and 2) Logical interfaces, which enable you to assign multiple IP addresses to a single physical interface and share the bandwidth of a single interface across multiple IP addresses.
Hi,
This is Solaris-10 x86 platform.
I am not able to ping gateway associated with aggr50001. I am not getting idea, where could be issue. Please advise.
# netstat -nr
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
--------------------... (10 Replies)
I am again rephrasing the issue that we are facing:
We are creating link aggregations with two interfaces named net0 & net5:
# dladm create-aggr -m dlmp -l net0 -l net5 -l net2 aggr1
Setting prob targets for aggr1:
# dladm set-linkprop -p probe-ip=+ aggr1
Setting failure detection... (3 Replies)
I have setup link aggregation with 3 interfaces on my solaris 10 system.
All looks good but my problem is that the traffic is only going out bge0 and not the other 2 links.
bash-4.3# dladm show-aggr -s
key:33 ipackets rbytes opackets obytes %ipkts %opkts
... (3 Replies)
AGR(4) BSD Kernel Interfaces Manual AGR(4)NAME
agr -- link aggregation pseudo network interface driver
SYNOPSIS
pseudo-device agr
DESCRIPTION
The agr driver provides link aggregation functionality (a.k.a. L2 trunking or bonding).
It supports the IEEE 802.3ad Link Aggregation Control Protocol (LACP) and the Marker Protocol.
The agr driver supports the following link specific flags for ifconfig(8):
link0 Use the round-robin distribution algorithm. Don't use it unless you're really sure, because it violates the frame ordering rule.
-link0 Use the default distribution algorithm, which is based on the hash of DA/SA, TCI, and, if available, some upper layer protocol infor-
mation like ip(4) DA/SA.
link1 Disable LACP. Prevents any LACP or Marker messaging which leaves the ports in the default static configuration. Set this prior to
adding ports.
EXAMPLES
Create an agr interface, agr0, and attach re0 and re1 to it. In other words, aggregate re0 and re1 so that they can be used as a single
interface, agr0. The physical interfaces which are attached to the agr interface must not have any IP addresses, neither IPv4 nor IPv6.
ifconfig re0 inet xxx.xxx.xxx.xxx delete
ifconfig re0 inet6 fe80::xxxx:xxxx:xxxx:xxxx delete
ifconfig re1 inet xxx.xxx.xxx.xxx delete
ifconfig re1 inet6 fe80::xxxx:xxxx:xxxx:xxxx delete
ifconfig agr0 create
ifconfig agr0 agrport re0
ifconfig agr0 agrport re1
Destroy an interface created in the above example.
ifconfig agr0 -agrport re0
ifconfig agr0 -agrport re1
ifconfig agr0 destroy
SEE ALSO ifconfig(8)STANDARDS
IEEE 802.3ad Aggregation of Multiple Link Segments
HISTORY
The agr driver first appeared in NetBSD 4.0.
AUTHORS
The agr driver was written by YAMAMOTO Takashi.
BUGS
There is no way to configure LACP administrative variables, including system and port priorities. The current implementation of the agr
driver always performs active-mode LACP and uses 0x8000 as system and port priorities.
The agr driver uses the MAC address of the first-added physical interface as the MAC address of the agr interface itself. Thus, removing the
physical interface and using it for another purpose can result in non-unique MAC addresses.
The current implementation of the agr driver doesn't prevent unsafe operations like some ioctls against underlying physical interfaces. Such
operations can result in unexpected behaviors, and are strongly discouraged.
There is no way to configure agr interfaces without attaching physical interfaces.
Physical interfaces being added to the agr interface shouldn't have any addresses except for link level address. Otherwise, the attempt will
fail with EBUSY. Note that it includes an automatically assigned IPv6 link-local address.
BSD February 23, 2010 BSD