Table of Contents
Advertisement
In order to allow LACP to determine whether a set of links connect to the same device, and to
determine whether those links are compatible from the point of view of aggregation, it is
necessary to be able to establish
•
A globally unique identifier for each device that participates in link aggregation.
•
A means of identifying the set of capabilities associated with each port and with each
aggregator, as understood by a given device.
•
A means of identifying a LAG and its associated aggregator.
LACP Terminology
Table
5‐5 defines key terminology used in LACP configuration.
Table 5-5 LACP Terms and Definitions
Term
Aggregator
LAG
LACPDU
Actor and Partner
Admin Key
System Priority
SecureStack B3 Usage Considerations
In normal usage (and typical implementations) there is no need to modify any of the default
LACP parameters on the switch. The default values will result in the maximum number of
aggregations possible. If the switch is placed in a configuration with its peers not running the
Definition
Virtual port that controls link aggregation for underlying physical ports. Each
SecureStack B3 module provides 6 aggregator ports, which are designated in
the CLI as lag.0.1 through lag.0.6.
Link Aggregation Group. Once underlying physical ports (for example, ge.x.x)
are associated with an aggregator port, the resulting aggregation will be
represented as one LAG with a lag.x.x port designation.
SecureStack B3 LAGs can have up to associated physical ports.
Link Aggregation Control Protocol Data Unit. The protocol exchanges
aggregation state/mode information by way of a port's actor and partner
operational states. LACPDUs sent by the first party (the actor) convey to the
second party (the actor's protocol partner) what the actor knows, both about
its own state and that of its partner.
An actor is the local device sending LACPDUs. Its protocol partner is the
device on the other end of the link aggregation. Each maintains current status
of the other via LACPDUs containing information about their ports' LACP
status and operational state.
Value assigned to aggregator ports and physical ports that are candidates for
joining a LAG. The LACP implementation on SecureStack B3 devices will use
this value to form an oper key and will determine which underlying physical
ports are capable of aggregating by comparing oper keys. Aggregator ports
allow only underlying ports with oper keys matching theirs to join their LAG.
On SecureStack B3 devices, the default admin key value is 32768.
Value used to build a LAG ID, which determines aggregation precedence. If
there are two partner devices competing for the same aggregator, LACP
compares the LAG IDs for each grouping of ports. The LAG with the lower
LAG ID is given precedence and will be allowed to use the aggregator.
Note: Only one LACP system priority can be set on a
SecureStack B3 device, using either the set lacp asyspri
command
(page
(page
5-44).
Link Aggregation Control Protocol (LACP)
5-38), or the set port lacp command
SecureStack B3 Configuration Guide 5-35
Advertisement
Table of Contents
