Like Farid said,
The EVI is the Route Instance, and you will set the instance-type to "virtual-switch" for using only one EVI for multiple bridge-domains (aka, vlans/broadcast domains)
EVI Type – EVPN – vlan-based requires a different EVI for each Broadcast Domain
EVI Type – Virtual Switch – vlan-aware requires 1 EVI for all Broadcast Domains
That's how I built me data centers... evpn-mpls using evpn evi virtual switch, and then i transport multiple vlans using one single route-instance (evi - virtual switch)
...here's how i expanded for each additional vlan within that one evi inside that virtual-switch
set routing-instances my-evpn-01 protocols evpn extended-vlan-list 10-14
set routing-instances my-evpn-01 protocols evpn extended-vlan-list 17
set routing-instances my-evpn-01 protocols evpn extended-vlan-list 101
set routing-instances my-evpn-01 protocols evpn extended-vlan-list 201-202
set routing-instances my-evpn-01 protocols evpn extended-vlan-list 204
set routing-instances my-evpn-01 protocols evpn extended-vlan-list 210
set routing-instances my-evpn-01 protocols evpn extended-vlan-list 1006
set routing-instances my-evpn-01 protocols evpn extended-vlan-list 1103
set routing-instances my-evpn-01 protocols evpn extended-vlan-list 2202
me@mx960# set routing-instances my-evpn-01 instance-type ?
Possible completions:
evpn EVPN routing instance
evpn-vpws EVPN VPWS routing instance
forwarding Forwarding instance
l2backhaul-vpn L2Backhaul/L2Wholesale routing instance
l2vpn Layer 2 VPN routing instance
layer2-control Layer 2 control protocols
mac-vrf MAC-VRF routing instance
mpls-forwarding Routing instance provides a MPLS forwarding-context
mpls-internet-multicast Internet Multicast over MPLS routing instance
no-forwarding Nonforwarding instance
virtual-router Virtual routing instance
virtual-switch Virtual switch routing instance
vpls VPLS routing instance
vrf Virtual routing forwarding instance
btw, I am curious about what this mac-vrf and its various options are for.
I have read this change brings Junos into alignment with RFC 7432 - BGP MPLS-Based Ethernet VPN, but I'm not sure I understand what that means.
I wonder if they now relocated the vlan-based and vlan-aware settings here for what we knew about the previous evi types... and then added this vlan-bundle type... I don't know.
me@mx960# set routing-instances my-evpn-01 instance-type mac-vrf service-type ?
Possible completions:
vlan-aware Instance service type vlan-aware
vlan-based Instance service type vlan-based
vlan-bundle Instance service type vlan-bundle
me@mx960> show system information
Model: mx960
Family: junos
Junos: 22.2R3-S2.8
Hostname: mx960
------------------------------
- Aaron
------------------------------
Original Message:
Sent: 01-29-2024 12:50
From: kronicklez
Subject: instance-type virtual-switch vs instance-type evpn in EVPN-MPLS?
Hi,
My objective is not to create two routing-instance. I'm try to do like instance-type virtual-switch that can bring multiple vlan in one routing-instance. I think it's limitation when to choose instance-type evpn right because it just can do vlan-based not vlan-bundle like instance-type virtual-switch? Please correct me if i wrong.
Thanks
Original Message:
Sent: 01-29-2024 10:43
From: WalkerSteve
Subject: instance-type virtual-switch vs instance-type evpn in EVPN-MPLS?
check out this link: https://www.juniper.net/documentation/us/en/software/junos/evpn-vxlan/topics/example/example-etree-service-evpn-configuring.html
you'll need to make some modifications your AE0 interface config under the unit as well as the R-I evpn. may have to create 2 separate R-I's for each vlan unless it allows you to set the type to vlan-bundle.
Original Message:
Sent: 01-28-2024 21:34
From: kronicklez
Subject: instance-type virtual-switch vs instance-type evpn in EVPN-MPLS?
Hi all,
Is it possible when we use instance-type evpn we can do like below config? When i change to instance-type evpn then it cannot work. Appreciate someone feedback
root@AGG-SNTL01# run show configuration interfaces ae0
description "Cust: TRUNK to CE1-EVPN01 (ae0)";
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
esi {
00:11:22:33:44:55:66:77:88:99;
all-active;
}
aggregated-ether-options {
lacp {
active;
system-id 00:01:02:03:04:05;
}
}
unit 1 {
description CE2-EVPN01-ETREE-HUB;
family bridge {
interface-mode trunk;
vlan-id-list 26-27;
}
etree-ac-role root;
}
[edit]
root@AGG# ...routing-instances CE2-EVPN01-ETREE-HUB
instance-type virtual-switch;
protocols {
evpn {
extended-vlan-list 26-27;
evpn-etree;
}
}
bridge-domains {
v26 {
domain-type bridge;
vlan-id 26;
}
v27 {
domain-type bridge;
vlan-id 27;
}
}
interface ae0.1;
route-distinguisher 172.16.200.21:201;
vrf-target target:65001:201;
Thanks