After upgrading the software on the EX4100 (or similar platforms) switch to 22.4R3-S2 /S3 or any of the new versions, we wont be able to use the "vlan member all" statment while assigning the vlans to the interface.
 
> This is an expected behaviour in the newer releases. Changes were made of the software due to the following limitations. 
> Broadcom-based platforms like the QFX5K and EX4400 inherently have an implicit default VLAN that exists without configuration due to product limitations. This is documented in the following links -

https://www.juniper.net/documentation/us/en/software/junos/multicast-l2/topics/topic-map/bridging-and-vlans.html
https://www.juniper.net/documentation/us/en/software/junos/cli-reference/topics/ref/statement/vlan-id-edit-vlans-qfx-series.html

> Considering the above,

  - The command “vlan members all” had to be removed due to potential traffic drops when an interface is part of both vxlan-vlan and vlan.
  - The sequence of events received by the PFE from the control plane can lead to incorrect programming, as the same table index is utilized for both vlan ifbd and vxlan ifbd. Subsequent programming can overwrite earlier configurations.
  - Typically, vxlan configuration is received after the default vlan configuration, which does not affect vxlan traffic. However, if the vxlan configuration precedes the vlan configuration, traffic loss can occur.
  - The sequence of these events is unpredictable.

> Additionally, these platforms cannot support VXLAN and non-VXLAN logical interfaces simultaneously on the same physical interface with enterprise-style configurations. This limitation is noted in the JUNOS documentation.
 https://www.juniper.net/documentation/us/en/software/junos/ovsdb-vxlan-qfx/evpn-vxlan/topics/concept/vxlan-constraints-qfx-series.html

The following error is seen while trying to commit a configuration when "vlan member all" is used on the trunk interface

 error: In routing-instance dc interface ae8.0 has vlan and vxlan mixed which is not supported 
 error: configuration check-out failed    
 

This is an expected behaviour in the newer software releases on broadcom based platforms.