I have been told by Juniper PS that when using VLAN Aware Bundle mode eVPN, a single VLAN must be assignd to a different unit. This sounds odd to me as looking at the configuration (below url), the interface mode is trunk and is configured with a vlan-id-list. This certainly infers that multiple VLANs can be assigned to a unit and dropped into a customer routing-instance. I applied configation using multiple VLANs and the syntax is accepted. We plan to test this to see if the config works but obviouly need Juniper ot underwrite/support what we intend to use.
Does anyone else use such configuration and can you point me to a Juniper URL detailing this config?
VLAN-aware bundle services supports the mapping of one or more routing instances of type Virtual Switch to many VLAN IDs (VIDs) and multiple bridge tables, with each bridge table corresponding to a different VLAN. To enable VLAN-aware bundle service, configure a Virtual Switch routing instance. For service provider-related applications, where the VLAN ID is local to the Layer 2 logic interface, enable theflexible-vlan-taggingstatement in your configuration. For enterprise-related applications, where the VLAN ID has global significance, enable thefamily ethernet-switchingstatement in your configuration. VLAN-aware bundle service supports up to 4000 VLANs per routing instance.
Let's not look at EVPN, because there's no difference in EVPN instance and Bridge Domain in terms of configs.
Your question should be an old topic, service-provider vs enterprise style of layer 2 interface configuration