Related Documentation
- J Series
- Example: Configuring Chassis Cluster Minimum Links
- Understanding Conditional Route Advertising in a Chassis Cluster
- Understanding Chassis Cluster Formation
- SRX Series
- Example: Configuring Chassis Cluster Minimum Links
- Understanding Conditional Route Advertising in a Chassis Cluster
- Understanding Chassis Cluster Formation
- Additional Information
- Junos OS Feature Support Reference for SRX Series and J Series Devices

Example: Configuring Chassis Cluster Redundant Ethernet Interface Link Aggregation Groups
This example shows how to configure a redundant Ethernet interface link aggregation group for a chassis cluster. Chassis cluster configuration supports more than one child interface per node in a redundant Ethernet interface. When at least two physical child interface links from each node are included in a redundant Ethernet interface configuration, the interfaces are combined within the redundant Ethernet interface to form a redundant Ethernet interface link aggregation group.
Requirements
Before you begin:
- Understand chassis cluster redundant Ethernet interfaces. See Understanding Chassis Cluster Redundant Ethernet Interfaces.
- Configure chassis cluster redundant interfaces. See Example: Configuring Chassis Cluster Redundant Ethernet Interfaces.
- Understand chassis cluster redundant Ethernet interface link aggregation groups. See Understanding Chassis Cluster Redundant Ethernet Interface Link Aggregation Groups.
Overview
![]() | Note: For aggregation to take place, the switch used to connect the nodes in the cluster must enable IEEE 802.3ad link aggregation for the redundant Ethernet interface physical child links on each node. Because most switches support IEEE 802.3ad and are also LACP capable, we recommend that you enable LACP on SRX Series devices. In cases where LACP is not available on the switch, you should not enable LACP on SRX Series devices. |
In this example, you assign six Ethernet interfaces to reth1 to form the Ethernet interface link aggregation group:
- ge-1/0/1—reth1
- ge-1/0/2—reth1
- ge-1/0/3—reth1
- ge-12/0/1—reth1
- ge-12/0/2—reth1
- ge-12/0/3—reth1
![]() | Note: A maximum of eight physical interfaces per node in a cluster, for a total of 16 child interfaces, can be assigned to a single redundant Ethernet interface when a redundant Ethernet interface LAG is being configured. |
Configuration
CLI Quick Configuration
To quickly configure a redundant Ethernet interface link aggregation group, copy the following commands and paste them into the CLI:
Step-by-Step Procedure
To configure a redundant Ethernet interface link aggregation group:
- Assign Ethernet interfaces to reth1.{primary:node0}[edit]user@host# set interfaces ge-1/0/1 gigether-options redundant-parent reth1user@host# set interfaces ge-1/0/2 gigether-options redundant-parent reth1user@host# set interfaces ge-1/0/3 gigether-options redundant-parent reth1user@host# set interfaces ge-12/0/1 gigether-options redundant-parent reth1user@host# set interfaces ge-12/0/2 gigether-options redundant-parent reth1 user@host# set interfaces ge-12/0/3 gigether-options redundant-parent reth1
Results
From configuration mode, confirm your configuration by entering the show interfaces reth1 command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.
For brevity, this show command output includes only the configuration that is relevant to this example. Any other configuration on the system has been replaced with ellipses (...).
If you are done configuring the device, enter commit from configuration mode.
Verification
To confirm that the configuration is working properly:
Verifying the Redundant Ethernet Interface LAG Configuration
Purpose
Verify the redundant Ethernet interface LAG configuration.
Action
From operational mode, enter the show interfaces terse | match reth command.
{primary:node0}user@host> show interfaces terse | match rethge-1/0/1.0 up down aenet --> reth1.0 ge-1/0/2.0 up down aenet --> reth1.0 ge-1/0/3.0 up down aenet --> reth1.0 ge-12/0/1.0 up down aenet --> reth1.0 ge-12/0/2.0 up down aenet --> reth1.0 ge-12/0/3.0 up down aenet --> reth1.0 reth0 up down reth0.0 up down inet 10.100.37.214/24 reth1 up down reth1.0 up down inet
Related Documentation
- J Series
- Example: Configuring Chassis Cluster Minimum Links
- Understanding Conditional Route Advertising in a Chassis Cluster
- Understanding Chassis Cluster Formation
- SRX Series
- Example: Configuring Chassis Cluster Minimum Links
- Understanding Conditional Route Advertising in a Chassis Cluster
- Understanding Chassis Cluster Formation
- Additional Information
- Junos OS Feature Support Reference for SRX Series and J Series Devices



