Configuring Ethernet Link Aggregation
On Fast Ethernet, Tri-Rate Ethernet copper, Gigabit Ethernet, and 10-Gigabit Ethernet interfaces on M-series and T-series routing platforms, you can associate a physical interface with an aggregated Ethernet interface. To enable the aggregated link, include the 802.3ad statement at the [edit interfaces interface-name fastether-options] or [edit interfaces interface-name gigether-options] hierarchy level:
- [edit interfaces interface-name (fastether-options
| gigether-options)]
- 802.3ad aex;
You specify the interface instance number x to complete the link association; x can be from 0 through 127, for a total of 128 aggregated interfaces. You must also include a statement defining aex at the [edit interfaces] hierarchy level. You can optionally specify other physical properties that apply specifically to the aggregated Ethernet interfaces; for details, see , and for a sample configuration, see .
![]() |
Note: In general, aggregated Ethernet bundles support the features available on all supported interfaces that can become a member link within the bundle. As an exception, Gigabit Ethernet IQ features and some newer Gigabit Ethernet features are not supported in aggregated Ethernet bundles. Gigabit Ethernet IQ and SFP interfaces can be member links, but IQ- and SFP-specific features are not supported on the aggregated Ethernet bundle even if all the member links individually support those features. |
To delete an aggregated Ethernet interface from the configuration, issue the delete interfaces aex command at the [edit] hierarchy level in configuration mode:
If you delete an aggregated Ethernet interface from the configuration, the JUNOS software removes the configuration statements related to aex and sets this interface to down state. However, the aggregated Ethernet interface is not deleted until you delete the chassis aggregated-devices ethernet device-count configuration statement.

