Problem in Solaris With Aggregation Where Each Interface Was Connected to a Separate Network Switch
(Doc ID 1382065.1)
Last updated on OCTOBER 12, 2019
Applies to:Solaris Operating System - Version 10 8/11 U10 and later
Information in this document applies to any platform.
On an 802.3ad link aggregation, high packet loss observed, the aggregation is not working properly when connecting each interface to a different switch
In general , if you want to configure an aggregation AND you want redundancy between 2-switches, then create separate 2-port aggregations to each switch, and create an IPMP group between the two aggregations. Or use a Solaris 11.1 (or higher) feature like Datalink Multipathing (DLMP) aggregations.
If a link aggregation spanning several switches is needed, switch vendors can implement such feature. This needs to be available and configured on switch side, so a single 802.3ad aggregation (port channel) is created.
For example Cisco has a LACP feature that will allow this type of config called " Cross-Stack Link Aggregation Control Protocol (LACP)". Without this special "Cross-Stack" feature, LACP for negotiated Cisco EtherChannel formation is supported only for ports on a single switch. Here is a link with some info: https://supportforums.cisco.com/docs/DOC-1901. Apparently it is only available on certain switch models and newer IOS software.
Similar features are called "Virtual Port Channel" (vpc on Cisco switches) or "Logical Link Aggregation" (on Oracle Ethernet switches).
The differences between "Trunked" 802.3ad aggregations and DLMP aggregations are noted here.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document