This Kb explains that lacp will be down and all child links will be in admin down state if aeX speed wrongly set
LACP child links are admin down
From below configuration we can see that ae1 is configured with wrong speed. Its child interfaces are of 100g each while ae1 is configured with 10g. This affected all other ae interfaces on the devices as all interfaces are down and their child interfaces shows as “admin down” :
root@Juniper> show configuration interfaces ae0 | display set
Nov 18 04:49:10
set interfaces ae0 aggregated-ether-options lacp active
set interfaces ae0 unit 0 family inet address 192.168.1.1/24
root@Juniper> show configuration interfaces ae1 | display set
Nov 18 04:49:22
set interfaces ae1 description "nlrtm1-rt001i {t=agg;if=ae1;}"
set interfaces ae1 per-unit-scheduler
set interfaces ae1 vlan-tagging
set interfaces ae1 mtu 9216
set interfaces ae1 aggregated-ether-options minimum-links 1
set interfaces ae1 aggregated-ether-options link-speed 10g ----- wrong speed set on ae1
set interfaces ae1 aggregated-ether-options lacp active
set interfaces ae1 unit 1519 description "nlrtm1-rt001i {t=bbl;if=ae1.1519;}"
set interfaces ae1 unit 1519 vlan-id 1519
set interfaces ae1 unit 1519 family inet policer arp arp-limit-5000pps
set interfaces ae1 unit 1519 family inet address 109.200.218.89/31
root@Juniper> show configuration interfaces et-0/0/0 | display set
Nov 18 04:51:57
set interfaces et-0/0/0 gigether-options 802.3ad ae0
root@Juniper> show configuration interfaces et-0/0/1 | display set
Nov 18 04:52:07
set interfaces et-0/0/1 gigether-options 802.3ad ae0
root@Juniper> show configuration interfaces et-1/0/1 | display set
Nov 18 04:52:19
set interfaces et-1/0/1 description "nlrtm1-ag044i {t=phys;if=et-0/0/31;xcid=4030;}"
set interfaces et-1/0/1 gigether-options 802.3ad ae1
root@Juniper> show configuration interfaces et-1/0/0 | display set
Nov 18 04:52:27
set interfaces et-1/0/0 description "lumen {t=phys;as=3356;cid=442325571;ven=lumen;xcid=3760;}"
set interfaces et-1/0/0 gigether-options 802.3ad ae1
We can see here that complete LACP is down:
root@Juniper> show lacp statistics interfaces ae0
Nov 18 04:50:11
root@Juniper>
Nov 18 04:50:19
root@Juniper> show lacp statistics interfaces ae1
Nov 18 04:50:30
Also, ae interface speed shows as unspecified :
root@Juniper> show interfaces ae0 extensive
Nov 18 04:45:46
Physical interface: ae0, Enabled, Physical link is Down
Interface index: 128, SNMP ifIndex: 1964, Generation: 131
Link-level type: Ethernet, MTU: 1514, Speed: Unspecified, BPDU Error: None,
MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled,
Flow control: Disabled
Pad to minimum frame size: Disabled
Minimum links needed: 1, Minimum bandwidth needed: 1bps
Device flags : Present Running
Interface flags: Hardware-Down Internal: 0x4000
Current address: cc:e1:94:77:b1:8b, Hardware address: cc:e1:94:77:b1:8b
Last flapped : 2024-11-18 04:37:10 PST (00:08:36 ago)
root@Juniper> show interfaces ae1 extensive
Nov 18 04:46:08
Physical interface: ae1, Enabled, Physical link is Down
Interface index: 129, SNMP ifIndex: 606, Generation: 132
Description: nlrtm1-rt001i {t=agg;if=ae1;}
while lacp process is running :
root@Juniper> show system processes extensive | match lacp
Nov 18 04:51:22
17867 root 20 0 726M 18M select 7 0:00 0.00% lacpd
root@blackfire-re0>
Tried restart lacp process but did not help :
root@Juniper> restart lacp
Nov 18 05:07:16
Link Aggregation Control Protocol process started, pid 20355
Nov 18 05:07:29
20355 root 21 0 726M 18M select 2 0:00 0.00% lacpd
Child links are showing admin down, while it is not disabled :
root@Juniper> show interfaces et-0/0/0 extensive
Nov 18 05:08:32
Physical interface: et-0/0/0, Administratively down, Physical link is Down
Interface index: 243, SNMP ifIndex: 501, Generation: 246
Link-level type: Ethernet, MTU: 1514, MRU: 0, Speed: 100Gbps,
root@Juniper> show interfaces et-0/0/1 extensive
Nov 18 05:08:59
Physical interface: et-0/0/1, Administratively down, Physical link is Down
Interface index: 244, SNMP ifIndex: 504, Generation: 247
Removed wrong configuration, still interfaces were in admin down state so we need to restart lacp to bring the lacp in UP state:
[edit]
root@Juniper# show | compare
Nov 18 05:10:10
[edit interfaces ae1 aggregated-ether-options]
- link-speed 10g;
root@Juniper# commit check
Nov 18 05:10:15
configuration check succeeds
root@Juniper# commit
Nov 18 05:10:23
commit complete
root@Juniper#
Nov 18 05:11:38
Link Aggregation Control Protocol process started, pid 20898
Nov 18 05:11:48
Physical interface: et-0/0/0, Enabled, Physical link is Up
Link-level type: Ethernet, MTU: 1514, MRU: 1522, Speed: 100Gbps,
BPDU Error: None, Loop Detect PDU Error: None, Loopback: Disabled,
root@Juniper> show interfaces et-1/0/0 extensive
Nov 18 05:12:23
Physical interface: et-1/0/0, Enabled, Physical link is Up
Interface index: 219, SNMP ifIndex: 775, Generation: 222
Description: lumen {t=phys;as=3356;cid=442325571;ven=lumen;xcid=3760;}
Link-level type: Ethernet, MTU: 9216, MRU: 9224, Speed: 100Gbps,
root@Juniper> show interfaces et-1/0/1 extensive
Nov 18 05:12:53
Physical interface: et-1/0/1, Enabled, Physical link is Up
Interface index: 220, SNMP ifIndex: 778, Generation: 223
Description: nlrtm1-ag044i {t=phys;if=et-0/0/31;xcid=4030;}
root@Juniper> show lacp interfaces ae0
Nov 18 05:13:41
Aggregated interface: ae0
LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity
et-0/0/0 Actor No No Yes Yes Yes Yes Fast Active
et-0/0/0 Partner No No Yes Yes Yes Yes Fast Active
et-0/0/1 Actor No No Yes Yes Yes Yes Fast Active
et-0/0/1 Partner No No Yes Yes Yes Yes Fast Active
LACP protocol: Receive State Transmit State Mux State
et-0/0/0 Current Fast periodic Collecting distributing
et-0/0/1 Current Fast periodic Collecting distributing
root@Juniper> show lacp interfaces ae1
Nov 18 05:13:49
Aggregated interface: ae1
et-1/0/0 Actor No No Yes Yes Yes Yes Fast Active
et-1/0/0 Partner No No Yes Yes Yes Yes Fast Active
et-1/0/1 Actor No No Yes Yes Yes Yes Fast Active
et-1/0/1 Partner No No Yes Yes Yes Yes Fast Active
et-1/2/0 Actor No Yes No No No Yes Fast Active
et-1/2/0 Partner No Yes No No No Yes Fast Passive
et-1/5/0 Actor No Yes No No No Yes Fast Active
et-1/5/0 Partner No Yes No No No Yes Fast Passive
et-0/4/1 Actor No Yes No No No Yes Fast Active
et-0/4/1 Partner No Yes No No No Yes Fast Passive
et-0/5/0 Actor No Yes No No No Yes Fast Active
et-0/5/0 Partner No Yes No No No Yes Fast Passive
et-1/0/0 Current Fast periodic Collecting distributing
et-1/0/1 Current Fast periodic Collecting distributing
et-1/2/0 Port disabled No periodic Detached
et-1/5/0 Port disabled No periodic Detached
et-0/4/1 Port disabled No periodic Detached
et-0/5/0 Port disabled No periodic Detached
The reason for all the child links affected on the lacp bundle is due to below reason: >>>
DCD process stared after the upgrade while wrong configuration was in place:
Nov 19 06:28:07.890 Juniper jlaunchd[16662]: interface-control (PID 16923) started >>>> DCD process started
Nov 19 06:28:13.545 Juniper jlaunchd[16662]: interface-control (PID 16923) terminate signal 15 sent >>>> jlaunchd sending dcd terminate due to config error
####### 1st occurrence of dcd exiting on it's own and restarted #####
Nov 19 06:28:17.044 Juniper dcd[17804]: UI_CONFIGURATION_ERROR: Process: dcd, path: <none>, statement: <none>, Interface ae1 with child links of mixed speed but link-speed mixed is not configured
Nov 19 06:28:17.053 Juniper jlaunchd[16662]: interface-control (PID 17804) exited with status=0 Normal Exit
####### 2nd occurrence of dcd exiting on it's own and restarted #####
Nov 19 06:28:23.142 Juniper dcd[17993]: UI_CONFIGURATION_ERROR: Process: dcd, path: <none>, statement: <none>, Interface ae1 with child links of mixed speed but link-speed mixed is not configured
Nov 19 06:28:23.149 Juniper jlaunchd[16662]: interface-control (PID 17993) exited with status=0 Normal Exit
#######dcd exit 3rd occurrence and not restarted and marked by jlaunchd as thrashing
Nov 19 06:28:29.552 Juniper dcd[18017]: UI_CONFIGURATION_ERROR: Process: dcd, path: <none>, statement: <none>, Interface ae1 with child links of mixed speed but link-speed mixed is not configured
Nov 19 06:28:29.559 Juniper jlaunchd[16662]: interface-control (PID 18017) exited with status=0 Normal Exit
Nov 19 06:28:29.560 Juniper jlaunchd[16662]: interface-control is thrashing, not restarted
Nov 19 06:35:46.499 Juniper chassisd[16925]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for et-1/0/0 >>>>> IFD's are getting created
Nov 19 06:35:46.500 Juniper chassisd[16925]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for et-1/0/1
Logs during setup recovery:
Nov 19 22:38:00.990 Juniper mgd[18178]: UI_COMMIT: User 'root' requested 'commit' operation (comment: none) >>>>> invalid config is getting removed and commited
Nov 19 22:38:03.745 Juniper mgd[18178]: UI_COMMIT_COMPLETED: : commit complete
Nov 19 22:40:15.351 Juniper mgd[18178]: UI_RESTART_EVENT: User 'root' restarting daemon 'Link Aggregation Control Protocol process' >>>>> LACPD restart requested
Nov 19 22:40:15.355 Juniper jlaunchd[16662]: lacp (PID 17802) exited with status=0 Normal Exit
Nov 19 22:40:15.613 Juniper jlaunchd[16662]: Registered PID 89883(interface-control): exec_command >>>>>> DCD is started
Nov 19 22:40:15.614 Juniper jlaunchd[16662]: Registered PID 89884((null)): exec_command
Nov 19 22:40:15.614 Juniper jlaunchd[16662]: Alarm clear command: /usr/sbin/cli (PID 89884) started
Nov 19 22:40:15.614 Juniper jlaunchd[16662]: interface-control (PID 89883) started
Nov 19 22:40:15.614 Juniper jlaunchd[16662]: Registered PID 89883(interface-control): new process
This issue is seen for all releases which are having fix for below PR:
https://prsearch.juniper.net/problemreport/PR1725168
Solution:
Please remove wrong configuration.