Specifications

Link Aggregation Control Protocol (LACP)
SecureStack B2 Usage Considerations
SecureStack B2 Configuration Guide 3-35
3.5.3 SecureStack B2 Usage Considerations
In normal usage (and typical implementations) there is no need to modify any of the default LACP
parameters on the SecureStack B2 device. The default values will result in the maximum number
LACPDU 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.
Actor and 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.
Admin Key Value assigned to aggregator ports and physical ports that are
candidates for joining a LAG. The LACP implementation on
SecureStack B2 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.
System Priority 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 B2 device, using either the set lacp asyspri
command (Section 3.5.4.3), or the set port lacp command
(Section 3.5.4.9).
Table 3-3 LACP Terms and Definitions (Continued)
Term Definition