After upgrading to a newer Junos OS version, unconfigured AE interfaces may not be shown in the output of the show interfaces terse command.
show interfaces
terse
This article explains that such behavior is expected and provides a reason for the unconfigured AE interfaces to not be shown in the above command output.
When link aggregation group (LAG) devices count is set to 10, but only ae0 is configured, different Junos OS versions may show different results when the show interfaces terse command is executed.
show interfaces terse
Junos OS Release 14.1X53
user@router#set chassis aggregated-devices ethernet device-count 10 user@router#set interfaces ae0 aggregated-ether-options lacp active user@router# commit user@router> show interfaces terse | match ae >>> It shows from ae0 to ae9 because device-count set to 10. ae0 up down ae1 up down ae2 up down ae3 up down ae4 up down ae5 up down ae6 up down ae7 up down ae8 up down ae9 up down
Junos OS Release 15.1
user@router#set chassis aggregated-devices ethernet device-count 10 user@router#set interfaces ae0 aggregated-ether-options lacp active user@router#commit user@router> show interfaces terse | match ae >>> Here only ae0 is shown even if device-count is set to 10. ae0 up down
The behavior changed from Junos OS Release 14.2R1 wherein AE physical interfaces are not created only with set chassis aggregated-devices ethernet device-count <n> configuration. The set interfaces configuration must also be present for the particular AE interface in order to create it.
set chassis aggregated-devices ethernet device-count <n>
set interfaces
Without AE-specific configuration, the interface will not be shown in the show interfaces terse output.
This behavior is expected. To create the AE interface and to see its details in show interfaces terse output in devices that run Junos OS Release 14.2R1 and later, provide AE-specific details by using the set interfaces command.