Link Aggregation; Link Aggregation Overview; Lag Formation Rules - Dell PowerConnect B-RX Configuration Manual

Bigiron rx series supporting multi-service ironware v02.7.03
Hide thumbs Also See for PowerConnect B-RX:
Table of Contents

Advertisement

Link Aggregation

Link aggregation overview

This chapter describes how to configure Link Aggregation Groups (LAG). Beginning with release
02.6.00 of the Multi-Service IronWare software, you can use a single interface to configure any of
the following LAG types:
The new LAG configuration procedures supersede the previous configurations procedures for
Trunks and Dynamic Link Aggregation. When a BigIron RX switch is upgraded to release 02.6.00,
any configurations for Trunks or Dynamic Link Aggregation defined in Multi-Service IronWare
versions prior to 02.6.00 will be converted to a 02.6.00 (and later) compatible LAG configuration.
Details about how this conversion is performed are described in
trunk or LACP configuration"
configuration pre-02.6.00 and post-02.6.00 release:
NOTE
Refer to the Dynamic Link Aggregation chapter in the BigIron RX Series Configuration Guide -
Versions 02.5.00 and earlier for information on how to configure LACP in previous version of the
Multi-Service IronWare software.

LAG formation rules

Given below are the LAG formation rules:
BigIron RX Series Configuration Guide
53-1001986-01
Static LAGs – These trunk groups are manually-configured aggregate links containing multiple
ports.
Dynamic LAGs – This LAG type uses the Link Aggregation Control Protocol (LACP), to maintain
aggregate links over multiple port. LACP PDUs are exchanged between ports on each
switchswitch to determine if the connection is still active. The LAG then shuts down ports
whose connection is no longer active.
Keep Alive LAGs – In a Keep Alive LAG a single connection between a single port on 2 BigIron
RX switches is established. In a keep alive LAG, LACP PDUs are exchanged between the 2 ports
to determine if the connection between the switches is still active. If it is determined that the
connection is no longer active, the ports are blocked.
NOTE
No trunk is created for "Keep Alive" LAGs
on page 239 . The following are the major differences between in LAG
Beginning with release 02.6.00, a trunk is not created until a LAG is deployed using the deploy
command.
Beginning with release 02.6.00, LACP is not started until a dynamic LAG is deployed.
You cannot configure a port concurrently as a member of a static, dynamic, or keep-alive LAG
"Migration from a pre-02.6.00
Chapter
8
235

Advertisement

Table of Contents
loading

This manual is also suitable for:

Bigiron rx series

Table of Contents