VXLAN Mastery · Lesson 03

The EVPN control plane: BGP tells the fabric where everything is

You know how VXLAN moves packets and how BUM traffic is replicated. Now meet the brain: MP-BGP EVPN. See how sessions form, what RDs and RTs really do, how each route type (1 to 5, plus 6 to 11) looks on the wire, and how hosts move.

📘 Builds on Lessons 1–2B⏱ ~55 minutes🖱 Live animated walkthrough🧠 Quiz and checklist
Progress is saved in this browser
1Starter⏱ 5 min

From “flood and learn” to “tell and learn”

Lessons 1 and 2 showed VXLAN as a data plane: how frames are wrapped and carried. Flood-and-learn discovers MACs by flooding. EVPN adds a control plane: leaves tell each other which MACs, IPs and subnets live behind them, using BGP. When the applicable MAC/IP route has been advertised and imported, a leaf can use its forwarding table rather than flooding for an unknown location.

🗣️ Flood and learn

“Who has this MAC?” goes to everyone. The owner’s reply teaches the others. Works, but every unknown destination causes a flood, and nothing stops a mistake from spreading.

📣 EVPN (tell and learn)

When Leaf 1 is configured to advertise its locally learned MAC, it announces “MAC 00:AA…:01 is behind me (10.0.0.1)” in a BGP message. Other leaves can learn the location before they need to forward traffic to that host.

Flood and learnEVPN
How MACs are foundFlooding + data-plane learningBGP route advertisements
Unknown-unicast floodingCommonRare (most MACs known in advance)
ARP broadcastsFlooded to all VTEPsMay be answered locally when ARP suppression is enabled and a valid MAC/IP binding exists; otherwise may be flooded
Routing between subnetsNeeds an external gatewayDistributed anycast gateway and symmetric IRB; Type 2 host routes and optional Type 5 IP prefixes support different routing cases
Host movesWait for aging or a new floodMAC mobility sequence number
Multi-vendor standardBasic VXLAN onlyRFC 7432, RFC 8365, RFC 9136
Important: EVPN does not replace VXLAN. VXLAN still carries the packets. EVPN is the BGP address family that fills in the forwarding tables. BUM replication (Lessons 2A and 2B) is still needed for the few frames that must be flooded.
2Starter⏱ 6 min

MP-BGP: BGP that carries more than IPv4

Plain BGP carries IPv4 routes. Multiprotocol BGP (MP-BGP) adds address families so one session can carry other kinds of information. EVPN is the L2VPN EVPN address family: AFI 25 (L2VPN), SAFI 70 (EVPN).

1. The underlay gets VTEPs reachable

First, an IGP or eBGP underlay makes every leaf loopback (10.0.0.1 … 10.0.0.4) reachable. This is the transport for VXLAN packets and for the BGP sessions.

2. The overlay BGP session

Leaves peer with the spine (route reflector) between loopbacks. The EVPN address family is activated on those sessions, and extended communities must be sent, because route targets travel as extended communities.

3. Next hop = VTEP loopback

Every EVPN route says “reach this MAC via next hop 10.0.0.x”. That next hop is the VTEP IP that becomes the outer destination IP of the VXLAN packet. Spines must not change it.

Two common session designs

Pick one
A BGP EVPN update carries three things: (1) the route (type and key fields such as MAC or IP), (2) attributes such as the next hop, and (3) extended communities such as the route target and the encapsulation (VXLAN). The next chapters decode each one.
3Intermediate⏱ 9 min

Route Distinguisher (RD) and Route Target (RT)

These two names confuse almost everyone. Remember them with one sentence each:

🏷️ RD = “make it unique”

An RD is glued in front of a route so that identical-looking routes from different places stay separate entries in BGP. It is a label for uniqueness, not for filtering. Format: IP:number or ASN:number.

🎯 RT = “who wants it”

An RT is a tag (an extended community) that says which tenants/VNIs a route belongs to. A device exports routes with its RT and imports only routes whose RT it is configured to accept. It is a filter.

RT import filter

Change the tags

Leaf 1 advertises a MAC in VNI 10100 and attaches an export RT. Each other leaf imports the route only if the RT matches one of its import RTs.

Why unique RDs matter

Leaf 1 and Leaf 3 both advertise the same MAC

Example: a MAC reachable behind two leaves (dual-homed host, or an anycast gateway MAC). What does the route reflector keep?

Auto-derived RD and RT (NX-OS style)

Type your values
Typical mistake: two leaves in the same VNI with different RTs. Routes still arrive (RD is fine) but are not imported, so hosts behind that leaf are unreachable.
4Intermediate⏱ 10 min

Live walkthrough: sessions, Type 3, Type 2, ARP suppression, traffic

One complete EVPN lifecycle, seven steps. Purple chips are BGP messages. Press Next step, and watch the tables under the diagram fill in.

Watch EVPN build its tables, step by step

BGP / EVPN control messageEthernet frame on a host linkVXLAN data packet
EVPN control plane (MP-BGP, AS 65000) Spine = Route ReflectoriBGP · L2VPN EVPN Leaf 1VTEP 10.0.0.1Leaf 2VTEP 10.0.0.2Leaf 3VTEP 10.0.0.3Leaf 4VTEP 10.0.0.4Host A00:AA…:01Host B00:BB…:02Host C00:CC…:03Host D00:DD…:04

Packets in this step

Notice: the spine is a route reflector. Leaves peer only with it, and it reflects each route to the others, so no full mesh of sessions is needed. Data traffic (the last step) bypasses BGP entirely.
5Intermediate⏱ 12 min

Every EVPN route type, with a live-style example

EVPN defines several route types, each answering a different question. Pick a type to see what it is for, its fields, and what it looks like in show bgp l2vpn evpn on a leaf. Values use our lab: Host A is 00:AA:AA:AA:AA:01 / 192.168.100.11, VNI 10100.

    Illustrative output: the bracketed format follows common NX-OS style, but exact prefix lengths and columns differ by vendor and version.
    TypeNameQuestion it answersUsed for
    1Ethernet Auto-DiscoveryWhich ESIs are alive? Who else serves this segment?Multihoming: fast convergence, aliasing
    2MAC/IP AdvertisementWhere is this MAC (and IP)?Host reachability, ARP suppression, mobility
    3Inclusive Multicast Ethernet TagWhich VTEPs are in this VNI, and how do I flood to them?BUM flood list
    4Ethernet SegmentWho shares this Ethernet segment?Multihoming: DF election
    5IP PrefixWhere is this subnet or prefix?Inter-subnet / external routing
    6–11Specialized multicast membership, synchronization and PMSI/leaf discovery routesWhich receivers need multicast, and how is multicast delivery coordinated?Selective multicast, membership synchronization, regional transport and explicit receiver tracking (feature-dependent)
    6Mastery⏱ 8 min

    Type 2 deep dive: fields, MAC-only vs MAC+IP, and host mobility

    Type 2 is the workhorse. Here is one announcement for Host A, field by field.

    FieldExampleMeaning
    Route Distinguisher10.0.0.1:32867Keeps the route unique per leaf and VLAN
    ESI0 (single-homed)Non-zero when the host is multihomed
    Ethernet tag0Usually 0 with VLAN-based service
    MAC address00:AA:AA:AA:AA:01The host MAC
    IP address (optional)192.168.100.11Present in MAC+IP routes; can support enabled ARP suppression with valid bindings
    Label 1 (L2 VNI)10100VNI to put in the VXLAN header for bridging
    Label 2 (L3 VNI)50001VNI of the tenant VRF, for routing (symmetric IRB)
    Next hop10.0.0.1Outer destination IP for VXLAN
    Route target65000:10100 (and 65000:50001)Which VNI/VRF imports it
    EncapsulationVXLANTunnel type extended community
    Router MAC0C:01:01:01:01:01Inner destination MAC for routed traffic

    MAC-only route

    Sent when the leaf has learned a MAC but no IP yet. Lets others bridge to it if imported and programmed.

    MAC+IP route

    Sent when the leaf also knows the IP (from ARP/GARP). Can support local proxy ARP (when enabled and the binding is valid) and host routing as configured.

    Host mobility with the sequence number

    Move Host A between leaves

    For a single-homed host moving between leaves, the new leaf normally advertises the MAC with an increased MAC-mobility sequence number. Route preference and withdrawal follow EVPN mobility rules; multihoming and duplicate-MAC handling introduce additional conditions.

    Move Host A to:
    7Mastery⏱ 7 min

    Choose the event: which EVPN route type solves it?

    These are not trivia questions; they reflect operational symptoms. Select a scenario and predict which control-plane advertisement matters. The answer includes the expected forwarding state.

    Choose a scenario and route type, then check your answer.
    8Mastery⏱ 6 min

    Configuration across vendors

    Every vendor needs the same four ideas: (1) BGP session with the EVPN family on, (2) extended communities sent, (3) an RD and RT per VNI, (4) the VNI mapped to a VLAN or bridge.

      Illustrative only: these snippets show the EVPN-specific lines, not a complete working configuration (underlay, interfaces and NVE/VXLAN interface settings are omitted). Syntax varies by software version, so check your vendor’s documentation.
      9Mastery⏱ 6 min

      Troubleshooting EVPN

      Work from the bottom up: underlay → BGP session → routes received → routes imported → forwarding table.

      LayerQuestionTypical check
      1. UnderlayCan VTEP loopbacks reach each other (with the right MTU)?ping from loopback to loopback, with DF bit and large size
      2. BGPIs the L2VPN EVPN session established?show bgp l2vpn evpn summary
      3. ReceivedDid the route arrive with the right next hop and RT?show bgp l2vpn evpn route-type 2
      4. ImportedDoes the VNI import that RT?compare RT export and import on both leaves
      5. ForwardingIs the MAC or IP in the table with the right VTEP?show l2route evpn mac all / show mac address-table

      What’s wrong? Pick a symptom

      Troubleshooting helper
      Click a symptom to see the most likely cause.
      ✓Check yourself⏱ 6 min

      Test what you learned

      Ten questions, each with an explanation.

      Mastery checklist

      Tick each one when you can explain it in your own words.

      Cheat sheet

      • EVPN = BGP address family 25/70 that distributes MACs, IPs, prefixes
      • RD makes routes unique; RT decides who imports
      • Type 1 A-D · 2 MAC/IP · 3 IMET · 4 ES · 5 IP prefix
      • Next hop = VTEP loopback = VXLAN outer destination
      • Higher MAC-mobility sequence wins after a host move
      • Send extended communities, or RTs never arrive

      What’s next

      Separate deep-dive lessons will cover routing with Type 5 and symmetric IRB and multihoming with Types 1 and 4.