Description

On EX4400 series switch, warning message below might be seen when exceeded 1025 vlans on trunk LAG interface.

warning: Too many VLAN-IDs on untagged interface

This is a software bug as EX4400 has supported more than 1025 vlans on the same trunk LAG interface.

Symptoms

EX4400 would generate warning message below when configured more than 1025 vlans on trunk LAG interface. 
user@Switch# commit
warning: Too many VLAN-IDs on untagged interface
fpc0:
configuration check succeeds
fpc1:
warning: Too many VLAN-IDs on untagged interface
commit complete
fpc0:
commit complete
But if they used vlan numbers with range string, the message is not seen even if exceeded 1025. And the issue is seen with LAG interface only, not seen with normal interface.
Here is the sample config to see the issue. 
user@Switch# show interfaces ae0 | display set
set interfaces ae0 aggregated-ether-options lacp active
set interfaces ae0 aggregated-ether-options lacp periodic slow
set interfaces ae0 unit 0 family ethernet-switching interface-mode trunk
set interfaces ae0 unit 0 family ethernet-switching vlan members vlan1
set interfaces ae0 unit 0 family ethernet-switching vlan members vlan2
set interfaces ae0 unit 0 family ethernet-switching vlan members vlan3
set interfaces ae0 unit 0 family ethernet-switching vlan members vlan4
set interfaces ae0 unit 0 family ethernet-switching vlan members vlan5
set interfaces ae0 unit 0 family ethernet-switching vlan members vlan6
~snip~
set interfaces ae0 unit 0 family ethernet-switching vlan members vlan1019
set interfaces ae0 unit 0 family ethernet-switching vlan members vlan1020
set interfaces ae0 unit 0 family ethernet-switching vlan members vlan1021
set interfaces ae0 unit 0 family ethernet-switching vlan members vlan1022
set interfaces ae0 unit 0 family ethernet-switching vlan members vlan1023
set interfaces ae0 unit 0 family ethernet-switching vlan members vlan1024
set interfaces ae0 unit 0 family ethernet-switching vlan members vlan1025

{master:0}[edit]
user@Switch# show interfaces ae0 | display set | match members | count
Count: 1025 lines

Solution

This is a software bug which reported by PR1791053. This is a warning message and there is no functional impact.
https://prsearch.juniper.net/problemreport/PR1791053
 

Modification History

2024-04-05 : Article Created