Supported Platforms
Related Documentation
- J, SRX Series
- Verifying LACP on Standalone Devices
- Additional Information
- Junos OS Feature Support Reference for SRX Series and J Series Devices
- Junos OS CLI Reference
Example: Configuring LACP on Chassis Clusters
This example shows how to configure LACP on chassis clusters.
Requirements
Before you begin:
- Add the aggregated Ethernet interfaces using the device count. See Example: Configuring the Number of Aggregated Ethernet Interfaces on a Device.
- Associate physical interfaces with the aggregated Ethernet Interfaces. See Example: Associating Physical Interfaces with Aggregated Ethernet Interfaces.
- Configure the aggregated Ethernet link speed. See Example: Configuring Aggregated Ethernet Link Speed.
- Configure the aggregated Ethernet minimum links speed. See Example: Configuring Aggregated Ethernet Minimum Links.
- Configure the LACP on standalone devices. See Example: Configuring LACP on Standalone Devices.
Overview
In this example, you set LACP to passive mode for the reth0 interface. You set the LACP mode for the reth1 interface to active and set the link aggregation control PDU transmit interval to slow, which is every 30 seconds.
Configuration
Step-by-Step Procedure
The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration Mode in the Junos OS CLI User Guide .
To configure LACP on chassis clusters:
- Set the first LACP on primary node1.[edit interfaces]user@host# set reth0 redundant-ether-options lacp passive
- Set the second LACP.[edit interfaces]user@host# set reth1 redundant-ether-options lacp activeuser@host# set reth1 redundant-ether-options lacp periodic slow
- If you are done configuring the device, commit the configuration.[edit interfaces]user@host# commit
Verification
To confirm that the configuration is working properly, perform this task:
Verifying LACP on Redundant Ethernet Interfaces
Purpose
Display LACP status information for redundant Ethernet interfaces.
Action
From operational mode, enter the show lacp interfaces reth0 command.
user@host> show lacp interfaces reth0
Aggregated interface: reth0 LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity ge-11/0/0 Actor No No Yes Yes Yes Yes Fast Active ge-11/0/0 Partner No No Yes Yes Yes Yes Fast Active ge-11/0/1 Actor No No Yes Yes Yes Yes Fast Active ge-11/0/1 Partner No No Yes Yes Yes Yes Fast Active ge-11/0/2 Actor No No Yes Yes Yes Yes Fast Active ge-11/0/2 Partner No No Yes Yes Yes Yes Fast Active ge-11/0/3 Actor No No Yes Yes Yes Yes Fast Active ge-11/0/3 Partner No No Yes Yes Yes Yes Fast Active ge-3/0/0 Actor No No Yes Yes Yes Yes Fast Active ge-3/0/0 Partner No No Yes Yes Yes Yes Fast Active ge-3/0/1 Actor No No Yes Yes Yes Yes Fast Active ge-3/0/1 Partner No No Yes Yes Yes Yes Fast Active ge-3/0/2 Actor No No Yes Yes Yes Yes Fast Active ge-3/0/2 Partner No No Yes Yes Yes Yes Fast Active ge-3/0/3 Actor No No Yes Yes Yes Yes Fast Active ge-3/0/3 Partner No No Yes Yes Yes Yes Fast Active LACP protocol: Receive State Transmit State Mux State ge-11/0/0 Current Fast periodic Collecting distributing ge-11/0/1 Current Fast periodic Collecting distributing ge-11/0/2 Current Fast periodic Collecting distributing ge-11/0/3 Current Fast periodic Collecting distributing ge-3/0/0 Current Fast periodic Collecting distributing ge-3/0/1 Current Fast periodic Collecting distributing ge-3/0/2 Current Fast periodic Collecting distributing ge-3/0/3 Current Fast periodic Collecting distributing {primary:node1}
The output shows redundant Ethernet interface information, such as the following:
- The LACP state—Indicates whether the link in the bundle is an actor (local or near-end of the link) or a partner (remote or far-end of the link).
- The LACP mode—Indicates whether both ends of the aggregated Ethernet interface are enabled (active or passive)—at least one end of the bundle must be active.
- The periodic link aggregation control PDU transmit rate.
- The LACP protocol state—Indicates the link is up if it is collecting and distributing packets.
Related Documentation
- J, SRX Series
- Verifying LACP on Standalone Devices
- Additional Information
- Junos OS Feature Support Reference for SRX Series and J Series Devices
- Junos OS CLI Reference
Published: 2012-06-29
Supported Platforms
Related Documentation
- J, SRX Series
- Verifying LACP on Standalone Devices
- Additional Information
- Junos OS Feature Support Reference for SRX Series and J Series Devices
- Junos OS CLI Reference