A junos lacp interface down state almost always traces back to one of five things: minimum-links not satisfied, both ends set to LACP passive, a speed or duplex mismatch on a member link, the AE or its member interfaces still administratively disabled, or a periodic-interval mismatch between the two sides. This is one of the most repeated threads on r/Juniper -- engineers bundling two or more links into an ae interface, committing cleanly, and watching the bundle sit in down/down or up/down while the member ports look fine in isolation.
This guide is written against Junos OS 21.4R3 on EX and MX platforms. The LACP state machine itself has not changed meaningfully across recent trains, but default minimum-links behavior and ELS versus non-ELS CLI syntax differ by platform family, and that is called out below where it matters.
What "AE Interface Down" Actually Means in Junos
An aggregated Ethernet bundle has three layers that each report status independently: the AE parent interface (ae0), the AE logical unit (ae0.0), and the physical member links (ge-0/0/5, ge-0/0/6, and so on). A bundle can show the parent as administratively up while the logical unit is down, or show every member physically up while LACP itself refuses to converge. Treating "ae0 is down" as one symptom instead of three is the most common reason troubleshooting goes in circles.
On r/Juniper, one recurring thread describes exactly this: an EX4300 and an SRX300 connected via LACP where the bundle simply would not come online, with no obvious error in the config. The fix in that case turned out to be a passive/passive LACP mismatch, not a cabling or hardware problem -- which is why the diagnostic order below starts with the cheapest check and ends with packet-level verification.
Diagnostic Order: Cheapest Check First
Run these in sequence. Each step either resolves the issue or narrows the next one.
show interfaces ae0 terse
This single command tells you whether the parent, the logical unit, and each member are administratively up, link up, and assigned to the right family. If the AE interface is not listed at all, the aggregated-devices ethernet device-count statement is missing or too low for the number of AE interfaces you have configured.
show lacp interfaces
This is the command that separates a physical-layer problem from an LACP negotiation problem. Look at the Mux State column. A healthy member interface reads Collecting distributing. Anything else -- Detached, Waiting, Attached -- means LACP itself has not converged even though the link light is on.
show interfaces ae0 extensive
Use this when the bundle is up but traffic is not passing correctly, or when you need to confirm the partner's MAC address to rule out a cabling mix-up between two chassis.
Root Cause 1: Minimum-Links Not Satisfied
By default, Junos only requires one member link to be up for the AE bundle itself to report up. If someone has explicitly configured minimum-links higher than the number of currently active members, the bundle will sit down even with healthy physical links. In our experience this is the single most common cause on freshly built EX and QFX leaf switches where a template config sets minimum-links to match the intended final member count before all the cabling is actually in place.
set interfaces ae0 aggregated-ether-options minimum-links 1
Verify the configured value against what is actually physically connected with show interfaces ae0 | display set before changing it -- lowering minimum-links on a production bundle without checking why it was set that way can mask a real capacity problem.
Root Cause 2: Both Ends Configured LACP Passive
LACP has two negotiation roles, active and passive. A passive interface will not initiate the protocol on its own; it only responds once it receives an LACP PDU from a peer that is active. If both switches in the bundle are left on the Junos default of passive, neither side ever sends the first packet and the Mux State never leaves Detached.
set interfaces ae0 aggregated-ether-options lacp active
Only one side needs to be active for negotiation to start; both sides can be active, but both cannot be passive.
Root Cause 3: Speed or Duplex Mismatch on a Member Link
A member interface can show link up while still being commercially useless to LACP if it auto-negotiated a different speed than its bundle peers or the far end. One widely referenced r/Juniper thread on an EX/SRX pairing found that once a link was aggregated, it appeared to lose auto-negotiation entirely, requiring both the member port and the AE bundle itself to be hard-set to the same link speed.
set interfaces ge-0/0/5 speed 1g
set interfaces ge-0/0/5 link-mode full-duplex
Check this with show interfaces ge-0/0/5 extensive | match Speed on both ends of the link, not just one.
Root Cause 4: Interface or Logical Unit Still Administratively Disabled
This sounds obvious but is easy to miss after a copy-paste config load: either the ae0 parent or ae0.0 logical unit can carry a leftover disable statement from a template or a previous maintenance window.
delete interfaces ae0 disable
delete interfaces ae0 unit 0 disable
Confirm which one is disabled first with show interfaces ae0 | display set rather than blindly running both deletes -- on a shared switch, removing a disable statement someone else set deliberately is a good way to create an unplanned outage.
Root Cause 5: Periodic Interval Mismatch (Fast vs. Slow)
Junos defaults to fast periodic LACP (one PDU per second). If one side is set to slow and the other to fast, the bundle can appear to partially negotiate and then flap, since the two state machines expect PDUs at different rates.
set interfaces ae0 aggregated-ether-options lacp periodic fast
Set this identically on both ends of the bundle. A mismatch here is less common than the first three causes but shows up often enough on multi-vendor LACP pairs to be worth checking.
Quick Reference: Symptom, Cause, Fix
| Symptom in show lacp interfaces | Likely Cause | Fix |
|---|---|---|
| AE not listed in show interfaces terse | device-count too low | Raise aggregated-devices ethernet device-count |
| Mux State: Detached on all members | Both ends passive | Set lacp active on at least one side |
| ae0 admin up, link down, min-links unmet | minimum-links set too high | Lower minimum-links or add members |
| Member link up but excluded from bundle | Speed/duplex mismatch | Hard-set matching speed/duplex both ends |
| Bundle flaps every few seconds | Periodic interval mismatch | Match lacp periodic fast/slow on both sides |
Verification: What Healthy Output Looks Like
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
LACP protocol: Receive State Transmit State Mux State
ge-0/0/5 Current Fast periodic Collecting distributing
Compare that against a broken state where the Mux State reads Detached and transmit state reads No periodic -- that combination means the local side has nothing to negotiate with and points straight back at Root Cause 2.
Per RFC 2378 and the IEEE 802.3ad specification that Junos implements LACP against, the protocol requires at least one side to actively solicit the exchange; this is not a Junos quirk, it is how the standard itself is designed to avoid two switches each silently waiting for the other to speak first. RFC 2378 covers the underlying VRRP-adjacent addressing context referenced in Juniper's own LACP and VRRP documentation.
Frequently Asked Questions
Why does my ae0 interface show up but no traffic passes?
Check the logical unit family assignment first with show interfaces ae0 terse -- it needs either eth-switch for Layer 2 or inet for Layer 3. If the family is correct, check MTU and spanning-tree state on the logical unit next, since those block traffic even on a link-up bundle.
Do both sides of an LACP bundle need to be set to active?
No. Only one side needs lacp active for negotiation to begin, though both sides can be active safely. Both sides cannot be passive, or neither will ever transmit the first LACP PDU.
What is the default minimum-links value in Junos?
By default only one physical member link needs to be up for the AE bundle to report up, unless minimum-links has been explicitly configured higher. Check the current value with show interfaces ae0 | display set before changing it.
Why did my LACP bundle break after upgrading Junos?
Juniper has documented cases where unconfigured AE interfaces do not appear in show interfaces terse output after certain upgrades, and separately where LAG interfaces can land in admin-down state if the AE speed statement is misconfigured relative to the member links. Check both the KB article for your specific upgrade path and the AE speed configuration after any Junos version change.
How do I check which MAC address my LACP partner is presenting?
Run show interfaces ae0 extensive and look for the learned Partner System ID field. Cross-reference the OUI against the IEEE public OUI lookup tool to confirm you are actually connected to the chassis you expect.
Related guides: see our troubleshooting category hub for more interface-level failure guides, our walkthrough on SRX chassis cluster failover not working for HA-specific interface monitoring, and our guide to Junos BGP prefix limit exceeded if the interface itself is fine but a neighboring protocol is not converging.
Juniper, Junos, MX, SRX, EX and QFX are trademarks of Juniper Networks, Inc. juniperclient.com is independent and unaffiliated.
Discussion (0)