EVPN · Topic 1 of 3

EVPN Concepts and Route Types

JN0-650 study page on EVPN: MAC learning in the control plane, address family, route types 1 to 5, and the commands to read EVPN routing tables on Junos.

  • 5 min
In a nutshell
  • EVPN (RFC 7432) uses MP-BGP to advertise MACs and IPs; address family l2vpn evpn, family evpn signaling, table bgp.evpn.0.
  • Route types: 1 Ethernet auto-discovery, 2 MAC/IP, 3 inclusive multicast, 4 Ethernet segment, 5 IP prefix.
  • Type 2 gives MAC learning and ARP suppression information; type 3 builds the BUM flood list.

What it is

Ethernet VPN (EVPN, RFC 7432) is a standards based control plane that uses multiprotocol BGP to advertise MAC addresses, IP addresses and other Layer 2 and Layer 3 reachability. It replaces flood-and-learn, where switches learn MAC addresses only when frames arrive and flood unknown traffic.

With EVPN, a switch learns a MAC address locally, then tells all other EVPN switches about it in a BGP route. The others install it without learning from data traffic.

Leaf 1Learns MAC locallyBGP EVPN routeRoute reflector or spineBGP EVPN routeLeaf 2Installs MAC and next hop

How it works

Why EVPN

Flood and learnEVPN
MACs learned from data trafficMACs advertised in BGP
Unknown unicast flooded everywhereFewer floods; known MACs are forwarded directly
No standard multihomingActive-active multihoming with Ethernet segments
Layer 2 onlyLayer 2 and Layer 3 information, including ARP and IP prefixes
Hard to scaleScales with BGP

EVPN can run over different data planes: MPLS, and VXLAN (RFC 8365). Most data center designs on QFX switches use EVPN with VXLAN.

Terms

TermMeaning
EVIEVPN instance, the EVPN service itself
MAC-VRFThe MAC table for an EVI on a device
Route distinguisher (RD)Makes routes unique across instances
Route target (RT)Controls which instances import a route
ESIEthernet segment identifier, 10 bytes, identifies a multihomed link
VTEPVXLAN tunnel endpoint, the device that encapsulates and decapsulates

The address family is l2vpn evpn, and in Junos it is configured as family evpn signaling on the BGP session. The routes are stored in the bgp.evpn.0 table.

set protocols bgp group OVERLAY type internal
set protocols bgp group OVERLAY local-address 10.255.0.1
set protocols bgp group OVERLAY family evpn signaling
set protocols bgp group OVERLAY neighbor 10.255.0.11

The five route types

TypeNameCarriesMain use
1Ethernet auto-discoveryESI and Ethernet tagMultihoming: aliasing and fast withdrawal
2MAC/IP advertisementMAC address, optionally the IP, and the VNI or labelLearned MAC and ARP information
3Inclusive multicast Ethernet tagThe originating VTEP addressBuilds the flood list for broadcast, unknown unicast and multicast (BUM) traffic
4Ethernet segmentESI and originating routerDesignated forwarder election among the PEs of a segment
5IP prefixAn IP prefix and its next hopLayer 3 routing between subnets and external networks
Type 2MAC and IPused forUnicast forwardingType 3VTEP flood listused forBUM trafficType 1 and 4ESIused forMultihomingType 5IP prefixused forInter subnet routing

A type 2 route tells everyone where a MAC address lives, and the IP attached to it lets leaves answer ARP requests locally (ARP suppression), which cuts flooding. When a MAC moves, the new location advertises it with a higher sequence number in the MAC mobility extended community, and the old location withdraws it.

A type 3 route is sent by every VTEP for each VLAN. It also announces how the device wants to receive BUM traffic. The result is the flood list: every VTEP knows who else has the VLAN.

Exam tip

Memorize the pairs: type 2 is MAC learning, type 3 is BUM flooding, types 1 and 4 are Ethernet segments, and type 5 is IP prefixes.

Configuring EVPN with VXLAN on a leaf

set protocols evpn encapsulation vxlan
set protocols evpn extended-vni-list all
set protocols evpn multicast-mode ingress-replication
set switch-options vtep-source-interface lo0.0
set switch-options route-distinguisher 10.255.0.1:1
set switch-options vrf-target target:65000:1
set vlans V100 vlan-id 100
set vlans V100 vxlan vni 10100

The VTEP source is a loopback. The vrf-target is the route target that all leaves import and export, so they see each other's routes.

Reading the routes

show route table bgp.evpn.0
show route table bgp.evpn.0 match-prefix "2:*"
show evpn database
show ethernet-switching table

The first digit of the prefix in bgp.evpn.0 is the route type, so you can filter by type. show evpn database lists the MAC addresses and IP addresses known to the instance, local and remote.

Common mistakes

Forgetting family evpn signaling. The BGP session comes up but exchanges no EVPN routes.

Mismatched route targets. Routes arrive but are not imported.

Mixing up types 2 and 3. Type 2 is a MAC; type 3 builds the BUM flood list.

Assuming EVPN removes all flooding. BUM traffic still exists, and type 3 routes control it.

Expecting type 5 to carry MAC addresses. It carries IP prefixes.

What to remember for the exam

  • EVPN (RFC 7432) uses MP-BGP to advertise MACs and IPs; address family l2vpn evpn, family evpn signaling, table bgp.evpn.0.
  • Route types: 1 Ethernet auto-discovery, 2 MAC/IP, 3 inclusive multicast, 4 Ethernet segment, 5 IP prefix.
  • Type 2 gives MAC learning and ARP suppression information; type 3 builds the BUM flood list.
  • Types 1 and 4 support multihoming; type 5 supports routing between subnets.
  • RD makes routes unique, RT controls import, ESI identifies a multihomed segment.
  • Data planes include MPLS and VXLAN.

Check yourself

  • Which route type advertises a MAC address?

    Type 2, the MAC/IP advertisement route.

  • Which route type builds the flood list for BUM traffic?

    Type 3, the inclusive multicast Ethernet tag route.

  • Which BGP address family and Junos statement carry EVPN routes?

    Family l2vpn evpn, configured as family evpn signaling.

Topic 1 of 3 in EVPN

Test yourself on EVPN

The full Juniper JNCIP-ENT JN0-650 question bank has 858 questions, with timed practice exams and an explanation for every answer.

This study guide is independent and is not affiliated with, endorsed by, or sponsored by Juniper. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.