What must match in the EVPN and L2VPN configuration mode when configuring EVPN native in a router?

Question

Options

• Ainterface
• Baddress family
• Cbridge domain
• DEVI

• A
  4% (1)
• B
  8% (2)
• C
  16% (4)
• D
  72% (18)

Explanation

When configuring EVPN native, the EVI (EVPN Instance) number is the binding identifier that ties the evpn configuration block to the l2vpn configuration block - both must reference the same EVI number for the control plane and data plane to correctly associate and forward traffic. Without matching EVIs, the router cannot correlate the EVPN instance with its corresponding L2VPN bridge domain, breaking MAC/IP advertisement and BUM traffic handling.

Why the distractors are wrong:

• A (interface): Interfaces are bound to bridge domains in L2VPN config, not a cross-mode matching requirement between EVPN and L2VPN modes.
• B (address family): Address families matter under BGP for EVPN route distribution, but they don't need to "match" between EVPN and L2VPN configuration modes.
• C (bridge domain): Bridge domains live entirely within L2VPN config; they point to an EVI rather than being the matching element themselves.

Memory tip: Think of EVI as the "glue number" - it's the only element that appears in both config modes, so it's the only one that can match. If you remember that EVI = the unique identifier for an EVPN instance, it's logical that both sides must reference the same instance number to connect.

No community discussion yet for this question.