Filter
Top Products
Troubleshooting Link Aggregation Troubleshooting a Link Aggregation Failure
OmniSwitch Troubleshooting Guide September 2005 page 7-5
Source Learning
When one of the primary links go down, the filtering database is purged and the process of learning the
source addresses is started again. The next available port is chosen to be the primary port. If the port that
goes down happens to be a secondary port, the MAC addresses learned on that particular port are re-
assigned to other ports evenly.
Link Aggregation Affecting Other Traffic
Note that depending on what software and hardware is being used, enabling link aggregation on a port
could affect other traffic on the same NI. Please call Customer Support if you suspect this to be the case.
Problems Creating a Group
Note that if there are problems creating a linkagg group or adding ports to an existing group the below
should be considered:
• Ports involved in a link aggregate need to all be of the same line speed.
• Mobile ports can not be a part of a link aggregate.
• There are a maximum of 32 aggregate groups allowed on an OmniSwitch 7700/7800/8800switch, 30
on a stack of OmniSwitch 6624/6648 switches, and 8 on a single OmniSwitch 6624/6648 switch. The
number goes down on OmniSwitch 7700/7800/8800 switches depending on the size of the aggregate,
see below.
Problems Deleting a Group
To delete a static link aggregate, the attached ports must first be deleted with the no static agg CLI
command. To delete a dynamic (802.3AD) aggregate, use the no lacp linkagg CLI command.