There should not be much of a difference in troubleshooting LAG on EX and QFX devices. Are you seeing any command or step that does not work on QFX? If so, please let us know. We can find an alternate command for you that is specific to QFX.
The below document specific to QFX should help you with verification of LAG status :
If I am getting your question correctly, you want to check how many interfaces are configured under LAG on the peer end device. Correct?
Firstly, a LAG needs to have a minimum number of links up in order for it to function correctly. Considering your LAG on one end had 2 interfaces configured. You will need 2 other interfaces on the other end. Only then it forms 2 links ( child interfaces) on each end. Ideally, in a simple LAG, both the devices will have the same number of interfaces.
For the LAG to operate correctly, it is necessary to coordinate the two end systems connected by the LAG, either manually or automatically.
From the same guide, you are referring to, I am pasting the below:
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
You can verify what interfaces are a part of your local device by running the above command. For ae0 aggregated interface, ge-0/0/5.0 and ge-0/0/6.0 are child interfaces.
To find child interfaces that are part of a LAG bundle: ( you can check the show interfaces extensive output )
The ae interface will show "down". By default, the minimum links (child interfaces) that are supposed to be up for an ae interface to remain up is 1. This is changeable. Considering your device is running on default behavior, if the other end child interfaces show "down", then the aggregate interface also shows down. And the Child Interface will show "Detached" in its MUX State for LACP protocol output.
If you have 2 child interfaces in your ae bundle and one interface goes down and your minimum links are running as per default value(1), then your ae bundle will still remain up but the link will show down.
Example: (Here, only ge-0/0/6 is LACP down and ge-0/0/5 is up )
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
Let me know if you have more queries.
Please mark "Accepted Solution" if this helps you solve your queries.
Please mark "Accepted Solution" for posts that solve your query so that it helps others as well.
Kudos are always appreciated!
For Junos OS, when a new interface is added as a member to the aggregated Ethernet bundle, a link flap event is generated. When you add an interface to the bundle, the physical interface is deleted as of a regular interface and then added back as a member. During this time, the details of the physical interface are lost.