Configure Aggregated Ethernet Interfaces
Learn how to configure Aggregated Ethernet (AE) interfaces on security devices. Also, learn about configuration details of AE interfaces, physical interfaces, AE interface link speed, and VLAN tagging.
Aggregated Ethernet Interfaces Overview
Link aggregation of Ethernet interfaces is defined in the IEEE 802.3ad standard. Junos OS implementation of 802.3ad balances traffic across the member links within an aggregated Ethernet bundle based on the following:
-
Session ID data (The session ID data has higher precedence than the L3 or L4 information)
-
L3 information carried in the packet
-
L4 information carried in the packet
-
Or both of the above
This implementation uses the same load-balancing algorithm used for per-packet load balancing.
Aggregated Ethernet (AE) interfaces are primarily used with Chassis Cluster. With the transition to MNHA, you can configure AE interfaces on a per-device basis between two or more local interfaces. The AE interfaces are not used across MNHA devices, as the concept of MNHA no longer includes such configurations.
Aggregate interfaces can be L3 interfaces (VLAN-tagged or untagged) and L2 interfaces.
Aggregated Ethernet Interfaces
To configure an aex:
- Set the number of aex on the device. See Example: Configuring the Number of Aggregated Ethernet Interfaces on a Device.
- Associate a physical interface with the aex. See Example: Associate Physical Interfaces with Aggregated Ethernet Interfaces.
- (Optional) Set the required link speed for all the interfaces included in the bundle. See Example: Configure Aggregated Ethernet Link Speed.
- (Optional) Configure the minimum number of links required for the bundle to be labeled as up. See Example: Configure Aggregated Ethernet Minimum Links.
- (Optional) Enable or disable VLAN tagging. See Understanding VLAN Tagging for Aggregated Ethernet Interfaces.
- (Optional) Enable promiscuous mode. See Understanding Promiscuous Mode for Aggregated Ethernet Interfaces.
See Also
Example: Delete Aggregated Ethernet Interfaces
This example shows:
-
How to delete an aggregated Ethernet interface (aex) from the interface configuration. You can Junos OS removes the configuration statements related to
aexand sets this interface to thedownstate. The deleted aggregated Ethernet interface still exists, but it becomes an empty interface. This example shows how to delete aggregated Ethernet interfaces using the device count. -
How to delete the contents of an aggregated Ethernet interface (aex)
Requirements
-
Set the number of aggregated Ethernet interfaces on the device. See Example: Configuring the Number of Aggregated Ethernet Interfaces on a Device.
-
Associate a physical interface with the aggregated Ethernet interface. See Example: Associate Physical Interfaces with Aggregated Ethernet Interfaces.
-
Set the required link speed for all the interfaces included in the bundle. See Example: Configure Aggregated Ethernet Link Speed.
-
Configure the minimum number of links that must be up for the bundle as a whole to be labeled as up. See Example: Configure Aggregated Ethernet Minimum Links.
Overview
This example shows:
-
How to clean up unused aggregated Ethernet interfaces (aex). In this example, you reduce the number of interfaces from 10 to 6, thereby removing the last 4 interfaces from the interface object list.
-
You delete the contents of the ae4 aggregated Ethernet interface, which sets it to the down state.
Configuration
Procedure
Step-by-Step Procedure
To delete an interface:
Set the number of aggregated Ethernet interfaces.
[edit] user@host# delete chassis aggregated-devices ethernet device-count 6
To delete the contents of an aggregated Ethernet interface:
[edit] user@host# delete interfaces ae4
If you are done configuring the device, commit the configuration.
[edit] user@host# commit
Verification
To verify the configuration is working properly, enter the show chassis
aggregated-devices and the show interfaces commands.
VLAN Tagging for Aggregated Ethernet Interfaces
Aggregated Ethernet interfaces can be either VLAN-tagged or untagged, with LACP enabled or disabled.
Use 802.1Q VLAN tagging to confirm platform and release support.
inner-tag-protocol-idinner-vlan-idpop-poppop-swappush-pushswap-pushswap-swap
Promiscuous Mode for Aggregated Ethernet Interfaces
You can enable promiscuous mode on aex. When you enable promiscuous mode on an L3 Ethernet interface, the interface forwards all received packets to the central point or Services Processing Unit (SPU). This forwarding applies regardless of the packet’s destination MAC address. If you enable promiscuous mode on an aex, promiscuous mode is then enabled on all member interfaces.
Verify Aggregated Ethernet Interfaces
Verify Aggregated Ethernet Interfaces (terse)
Purpose
Display status information in terse (concise) format for aggregated Ethernet interfaces.
Action
From operational mode, enter the show interfaces
ae0 terse command.
user@host> show interfaces ae0 terse
ge-2/0/0.0 up up aenet --> ae0.0
ge-2/0/0.32767 up up aenet --> ae0.32767
ge-2/0/1.0 up up aenet --> ae0.0
ge-2/0/1.32767 up up aenet --> ae0.32767
ae0 up up
ae0.0 up up bridge
ae0.32767 up up multiserviceThe output shows the bundle relationship for the aggregated Ethernet interface and the overall status of the interface, including the following information:
The link aggregation control PDUs run on the .0 child logical interfaces for the untagged aggregated Ethernet interface.
The link aggregation control PDUs run on the .32767 child logical interfaces for the VLAN-tagged aggregated Ethernet interface.
The .32767 logical interface is created for the parent link and all child links.
Verify Aggregated Ethernet Interfaces (extensive)
Purpose
Display status information and statistics in extensive (detailed) format for aggregated Ethernet interfaces.
Action
From operational mode, enter the show interfaces
ae0 extensive command.
user@host> show interfaces ae0 extensive
Physical interface: ae0, Enabled, Physical link is Up
...
Logical interface ae0.0 (Index 67) (SNMP ifIndex 628) (Generation 134)
...
LACP info: Role System System Port Port Port
priority identifier priority number key
ge-5/0/0.0 Actor 127 00:1f:12:8c:af:c0 127 832 1
ge-5/0/0.0 Partner 127 00:1f:12:8f:d7:c0 127 640 1
ge-5/0/1.0 Actor 127 00:1f:12:8c:af:c0 127 833 1
ge-5/0/1.0 Partner 127 00:1f:12:8f:d7:c0 127 641 1
LACP Statistics: LACP Rx LACP Tx Unknown Rx Illegal Rx
ge-5/0/0.0 12830 7090 0 0
ge-5/0/1.0 10304 4786 0 0
...
Logical interface ae0.32767 (Index 70) (SNMP ifIndex 630) (Generation 135)
...
LACP info: Role System System Port Port Port
priority identifier priority number key
ge-5/0/0.32767 Actor 127 00:1f:12:8c:af:c0 127 832 1
ge-5/0/0.32767 Partner 127 00:1f:12:8f:d7:c0 127 640 1
ge-5/0/1.32767 Actor 127 00:1f:12:8c:af:c0 127 833 1
ge-5/0/1.32767 Partner 127 00:1f:12:8f:d7:c0 127 641 1
LACP Statistics: LACP Rx LACP Tx Unknown Rx Illegal Rx
ge-5/0/0.32767 12830 7090 0 0
ge-5/0/1.32767 10304 4786 0 0
...
The output shows detailed aggregated Ethernet interface information. This portion of the output shows LACP information and LACP statistics for each logical aggregated Ethernet interface.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.