You can configure
multihoming in active-standby redundancy mode in an Ethernet VPN (EVPN) fabric with
MPLS.
This
mode enables the
device to autodiscover
Ethernet
segments,
construct
Ethernet segment
routes,
and assign
Ethernet segment identifier (ESI)
labels.
Note:
We support active-standby multihoming in EVPN fabrics only with MPLS.
QFX Series switches support EVPN-VXLAN with active-active multihoming; they don't
support EVPN with MPLS or multihoming in active-standby mode.
When configuring active-standby EVPN
multihoming on
supported devices, be aware of the following limitations:
-
An interface or ESI can be attached to more than one EVPN instance (EVI), with a
maximum limit of 200 EVIs per ESI.
-
For an EVPN routing instance, only one logical interface per physical interface
or ESI can be attached to an EVI.
-
For a virtual switch routing instance, only one logical interface per physical
interface or ESI can be configured under a bridge domain.
All the PE routers in the network topology that support this feature should be running
Junos OS Release 14.1 or later releases, which are based on EVPN
draft-ietf-l2vpn-evpn-03. Junos OS releases prior to 14.1 support the older version of
the EVPN draft, causing interoperability issues when Junos OS Release 14.1 and a
previous release are running.
Before you begin:
Configure the router interfaces.
Configure the router ID and autonomous system number for
the device.
Configure OSPF or any other IGP protocol.
Configure a BGP internal group.
Include the EVPN signaling network layer reachability
information (NLRI) to the internal BGP group.
Configure LDP.
Configure MPLS.
Configure RSVP MPLS LSP or GRE tunnels.
To configure the PE device:
- Enable EVPN active-standby multihoming on the multihomed
interfaces.
[edit interfaces]
user@PE1# set interface-name vlan-tagging
user@PE1# set interface-name encapsulation flexible-ethernet-services
user@PE1# set interface-name esi esi-value
user@PE1# set interface-name esi single-active
user@PE1# set interface-name unit 0 encapsulation vlan-bridge
user@PE1# set interface-name unit 0 vlan-id VLAN-ID
For example:
[edit interfaces]
user@PE1# set ge-0/0/4 vlan-tagging
user@PE1# set ge-0/0/4 encapsulation flexible-ethernet-services
user@PE1# set ge-0/0/4 esi 00:22:44:66:88:00:22:44:66:88
user@PE1# set ge-0/0/4 esi single-active
user@PE1# set ge-0/0/4 unit 0 encapsulation vlan-bridge
user@PE1# set ge-0/0/4 unit 0 vlan-id 300
- Configure the routing instance for the active-standby
mode of redundancy.
The active-standby multihoming can
be configured under any EVPN routing-instance. Both evpn and virtual-switch instance types are supported in active-standby
EVPN multihoming. The vrf routing-instance is configured
to illustrate the EVPN IRB functionality, in addition to multihoming,
and is not mandatory for the active-standby EVPN multihoming feature
to work. For example:
Virtual-switch Routing Instance
[edit routing-instances]
user@PE1# set virtual-switch-instance instance-type virtual-switch
user@PE1# set virtual-switch-instance protocols evpn extended-vlan-list VLAN-ID
user@PE1# set virtual-switch-instance bridge-domains bridge-domain-name domain-type bridge
user@PE1# set virtual-switch-instance bridge-domains bridge-domain-name vlan-id VLAN-ID
user@PE1# set virtual-switch-instance bridge-domains bridge-domain-name interface interface-name
user@PE1# set virtual-switch-instance bridge-domains bridge-domain-name routing-interface interface-name
user@PE1# set virtual-switch-instance route-distinguisher route-distinguisher-value
user@PE1# set virtual-switch-instance vrf-target vrf-target
OR
EVPN Routing Instance
[edit routing-instances]
user@PE1# set evpn-instance instance-type evpn
user@PE1# set evpn-instance vlan-id VLAN-ID
user@PE1# set evpn-instance interface interface-name
user@PE1# set evpn-instance routing-interface interface-name
user@PE1# set evpn-instance route-distinguisher route-distinguisher-value
user@PE1# set evpn-instance vrf-target vrf-target
OR
VRF Routing Instance
[edit routing-instances]
user@PE1# set vrf-instance instance-type vrf
user@PE1# set vrf-instance interface interface-name
user@PE1# set vrf-instance route-distinguisher route-distinguisher-value
user@PE1# set vrf-instance vrf-target vrf-target
- Verify and commit the configuration.
For example:
[edit routing-instances]
user@PE1# set ALPHA instance-type virtual-switch
user@PE1# set ALPHA route-distinguisher 10.255.0.1:100
user@PE1# set ALPHA vrf-target target:100:100
user@PE1# set ALPHA protocols evpn extended-vlan-list 100
user@PE1# set ALPHA bridge-domains ONE domain-type bridge
user@PE1# set ALPHA bridge-domains ONE vlan-id 100
user@PE1# set ALPHA bridge-domains ONE interface ae0.0
user@PE1# set ALPHA bridge-domains ONE interface ge-0/0/2.0
user@PE1# set ALPHA bridge-domains ONE routing-interface irb.0
user@PE1# set BETA instance-type evpn
user@PE1# set BETA vlan-id 300
user@PE1# set BETA interface ge-0/0/4.0
user@PE1# set BETA interface ae1.0
user@PE1# set BETA routing-interface irb.1
user@PE1# set BETA route-distinguisher 10.255.0.1:300
user@PE1# set BETA vrf-target target:300:300
user@PE1# set DELTA instance-type vrf
user@PE1# set DELTA interface irb.0
user@PE1# set DELTA interface irb.1
user@PE1# set DELTA route-distinguisher 10.255.0.1:200
user@PE1# set DELTA vrf-target target:200:200
user@PE1# set DELTA vrf-table-label
[edit]
user@PE1# commit
commit complete
