BGP EVPN type 2 routes advertise MAC addresses of clients connected to VNIs on this VTEP. Other VTEPs use this information to populate the MAC address tables for the VLAN associated with the VNI…

Question

Options

• AThe forwarding interface for the MAC address is the local interfaces
• BThe forwarding interface for the MAC address is the tunnel to the next hop VTEP

• A
  28% (14)
• B
  72% (36)

Explanation

When a remote VTEP receives a BGP EVPN Type 2 route, the advertised MAC belongs to a host attached to a different VTEP - meaning traffic must traverse the VXLAN tunnel to reach it. The MAC address table entry is therefore programmed with the NVE (tunnel) interface pointing toward the next-hop VTEP as the forwarding interface, not any local port.

Option A is wrong because local interfaces only forward traffic to MAC addresses of hosts directly attached to that VTEP. A Type 2 route received via BGP EVPN describes a MAC on a remote VTEP - it cannot be reachable through a local interface.

The phrase "VXLAN does not rely on MAC forwarding to establish connectivity" is a distractor hinting that the underlay IP reachability (not Layer 2 flooding) carries the traffic, but the MAC table still gets populated - just with tunnel interfaces as the egress rather than physical ports.

Memory tip: BGP EVPN Type 2 is essentially a remote VTEP announcing "this MAC lives behind me." If the MAC is behind another VTEP, you must go through the tunnel to that VTEP - tunnel = remote, local interface = local. Never mix the two.

No community discussion yet for this question.