Search our Knowledge Base sites to find answers to your questions.
Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articlesResolution Guide - EX - Troubleshoot Aggregated Ethernet Interface (LAG)
Verify LAG (Link Aggregation Group) of EX switch is UP, and troubleshoot it if it is not.
To verify a Physical Interface (non-aggregated) or a VLAN interface, refer to KB22217 - Resolution Guides - EX - Troubleshoot/Verify Interface.
Goals:
root@KE-1-4200# run show interfaces terse | match ae0 ge-0/0/5.0 up up aenet --> ae0.0 <<<<< LAG Child Interface ge-0/0/6.0 up up aenet --> ae0.0 <<<<< LAG Child Interface ae0 up up <<<<< LAG Parent Interface ae0.0 up up eth-switch <<<<< LAG Logical Interface
- LAG parent interface (ae0) and LAG logical interface (ae0.0) are Administratively Up
- LAG parent interface (ae0) and LAG logical interface (ae0.0) are Link Up
- Child interfaces (ge-0/0/5.0 and ge-0/0/6.0) are Administratviely Up
- Child interfaces (ge-0/0/5.0 and ge-0/0/6.0) are Link Up
- Correct family is assigned to the LAG logical (ae0.0) interface
Perform the following steps:
Run the following command to view the status of the Aggregated Ethernet Interface:
show interfaces <ae interface> terse
Example:root@KE-1-4200#run show interfaces ae0 terse Interface Admin Link Proto Local Remote ae0 up down ae0.0 up down eth-switch
What is the 'Admin' status of the ae interface (i.e. ae0 in the example)?
root@KE-1-4200# run show interfaces ae0 terse
error: device ae0 not found
The ae interface is Administratively Down, which means the administrator of this switch disabled the interface.
This can be confirmed with the command:show configuration interfaces <aeX interface> | display set
Example:root@KE-1-4200# run show configuration interfaces ae0 | display set set interfaces ae0 disable set interfaces ae0 unit 0 family ethernet-switching
Bring the interface Administratively Up by enabling the interface with the command:
delete interfaces <ae interface> disable
Important Note: We strongly recommend that you check with the administrator before issuing this command, as it will alter the administrator's network topology.
Example:
root@KE-1-4200# delete interfaces ae0 disable
For more information, refer to the technical documentation on Disabling a Physical Interface
Continue with Step 3 (when the ae interface is Administratively Up).
Now observe the Aggregated Ethernet Interface Logical Interface line output (i.e. ae0.0).
Example:root@KE-1-4200#run show interfaces ae0 terse Interface Admin Link Proto Local Remote ae0 up down ae0.0 up <<<<< down eth-swith
What is the 'Admin' status of the LAG Logical interface (i.e. ae0.0 in the example)?
root@KE-1-4200# delete interfaces ae0 unit 0 disable
Important Note: We strongly recommend that you check with the administrator before issuing this command, as it will alter the administrator's network topology.
Continue with Step 4 (when the ae0.0 Logical interface is Administratively Up). Run the following command to view all the Child Interface members associated with the Aggregated Ethernet Interface bundle:
show int terse | match
<ae interface>
Note: This command is slightly different than the command used in the previous steps.
root@KE-1-4200# run show interfaces terse | match ae0 ge-0/0/5.0 up down aenet --> ae0.0 <<<<<LAG Child Interface ge-0/0/6.0 up up aenet --> ae0.0 <<<<<LAG Child Interface ae0 up up ae0.0 up up eth-switch
Are all the LAG Child Interface members of the Aggregated Ethernet Interface bundle listed?
Are the expected Child interfaces listed with the status of 'up up'? ('up up' means Administratively up and Link up)
root@KE-1-4200# run show interfaces terse | match ae0 ge-0/0/5.0 up up aenet --> ae0.0 <<<<<LAG Child Interface ge-0/0/6.0 up up aenet --> ae0.0 <<<<<LAG Child Interface ae0 up up ae0.0 up up eth-switch
For each Child Interface that is not 'up up', follow the steps in the Resolution Guide - EX - Verify/Troubleshoot Physical Interface to troubleshoot and correct it.
Run the following command again:
Is the correct Protocol family listed for the LAG Logical interface (i.e. ae0.0)? (It should be 'eth-switch' for Layer 2 or 'inet' for Layer 3.)show interfaces <ae interface> terse
Example:
root@KE-1-4200#run show interfaces ae0 terse Interface Admin Link Proto Local Remote ae0 up down ae0.0 up down
eth-switch<<<<<LAG Logical Interface
What is the 'Link' status of the ae interface (i.e. ae0)?
Example:
root@KE-1-4200#run show interfaces ae0 terse Interface Admin Link Proto Local Remote ae0 up down <<<<< ae0.0 up down eth-switch
root@KE-1-4200# run show interfaces terse | match ae0 ge-0/0/5.0 up up aenet --> ae0.0 <<<<< LAG Child Interface ge-0/0/6.0 up up aenet --> ae0.0 <<<<< LAG Child Interface ae0 up up <<<<< LAG Parent Interface ae0.0 up up eth-switch <<<<< LAG Logical Interface
- LAG parent interface (ae0) and LAG logical interface (ae0.0) are Administratively Up
- LAG parent interface (ae0) and LAG logical interface (ae0.0) are Link Up
- Child interfaces (ge-0/0/5.0 and ge-0/0/6.0) are Administratively Up
- Child interfaces (ge-0/0/5.0 and ge-0/0/6.0) are Link Up
- Correct family is assigned to the LAG logical (ae0.0) interface
If you are having a problem with traffic not passing, then jump to Step 13 for some pointers.
Is this LAG interface a LACP (Link Aggregation Control Protocol)?
Run the following command to verify the LACP configuration between peers:
show lacp interfaces
For an explanation of the fields below, refer to the documentation on show lacp interfaces.
Working Example:
root@KE-2-3200# run show lacp interfaces Aggregated interface: ae0 LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity ge-0/0/5 Actor No No Yes Yes Yes Yes Fast Passive ge-0/0/5 Partner No No Yes Yes Yes Yes Fast Active ge-0/0/6 Actor No No Yes Yes Yes Yes Fast Passive ge-0/0/6 Partner No No Yes Yes Yes Yes Fast Active LACP protocol: Receive State Transmit State Mux State ge-0/0/5 Current Fast periodic Collecting distributing ge-0/0/6 Current Fast periodic Collecting distributing
Non-working Example:
root@KE-1-4200# run show lacp interfaces Aggregated interface: ae0 LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity ge-0/0/5 Actor No No Yes Yes Yes Yes Fast Active ge-0/0/5 Partner No No Yes Yes Yes Yes Slow Passive ge-0/0/6 Actor No Yes No No No Yes Fast Active ge-0/0/6 Partner No Yes No No No Yes Fast Passive LACP protocol: Receive State Transmit State Mux State ge-0/0/5 Current Slow periodic Collecting distributing ge-0/0/6 Port disabled No periodic Detached
Is the Mux State for the all the physical child interfaces equal to 'Collecting distributing'? ('Collecting distributing' is the value you want to see.)
For the physical interface in question, is the LACP Activity state set to Passive for both the Actor and Partner?
Non-working Example:
root@KE-1-4200# run show lacp interfaces Aggregated interface: ae0 LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity ge-0/0/5 Actor No No Yes Yes Yes Yes Fast Active ge-0/0/5 Partner No No Yes Yes Yes Yes Slow Passive ge-0/0/6 Actor No Yes No No No Yes Fast Active ge-0/0/6 Partner No Yes No No No Yes Fast Passive LACP protocol: Receive State Transmit State Mux State ge-0/0/5 Current Slow periodic Collecting distributing ge-0/0/6 Port disabled No periodic Detached
For the physical interface in question, is the Periodic Interval the same for both the Actor and Partner?
Non-working Example:
root@KE-1-4200# run show lacp interfaces Aggregated interface: ae0 LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity ge-0/0/5 Actor No No Yes Yes Yes Yes Fast Active <<<<< ge-0/0/5 Partner No No Yes Yes Yes Yes Slow Passive <<<<< ge-0/0/6 Actor No No Yes Yes Yes Yes Fast Active ge-0/0/6 Partner No No Yes Yes Yes Yes Slow Passive LACP protocol: Receive State Transmit State Mux State ge-0/0/5 Current Slow periodic Collecting distributing ge-0/0/6 Current Slow periodic Collecting distributingIt is strongly recommended that both sides be configured with the same LACP Periodic interval Configuration. By default the LACP interfaces are set Fast-Periodic Intervals (LACPD will be sent every second). For more information on this parameter, refer to Understanding Periodic interval.
If all the physical interfaces are 'Collecting distributing' and you are experiencing issues with your Aggregated Ethernet Interface, also perform the following checks:
If the problem is that traffic is not passing, investigate the following areas:
Also, reference Troubleshooting Interface - Chapter 5, p.121 in the Junos for EX Series Ethernet Switches Technical Documentation.
If still not resolved, contact your technical support representative.
Related Links
Getting Up and Running with Junos
Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search