The EVPN table holds VPN routes belonging to the L2VPN EVPN address-family. These routes may be received from an EVPN peer, originated locally, or exported from other VRFs for prefix routes.
EVPN route types 1 through 4 received from remote peers are imported only into the MAC-VRF table, except for MACIP host routes that may get converted to IPv4/v6 host routes and imported into the IP-VRF table. EVPN routes received from remote peers are validated against import rules and are added to the VPN table only if validation passes. The following table lists the import rules for peer types and route types.
| Received from peer type | Route type | Import rules |
|---|---|---|
| VXLAN peer | MAC/IP, Ethernet Tag | RTs in the route are looked up in the MAC-VRF table. A route is imported for the following conditions:
|
| IP Prefix | RTs in the route are looked up in IP-VRFs. For each IP-VRF matching the RT, route is imported into that IP-VRF. | |
| Ethernet Segment | Route is imported if the RT in the route matches the auto ES-RT of the locally configured MCT interface. | |
| Inclusive Multicast Routes |
The EVPN table can hold routes even if they are not imported into MAC-VRF or IP-VRF tables. This table is required at the spine or border-leaf nodes to reflect the routes to other leaf nodes or to other data centers, respectively. The retain route-target all command is used to configure this table.
The consolidation of the routes from different sources (RDs) occurs in the MAC-VRF table after the routes pass through route-target checking and import filtering. The following operations are performed exclusively in the MAC-VRF table:
The following table lists advertisement behavior by route type.
| Route type | Advertised to VXLAN peer? | Advertised to MPLS peer? |
|---|---|---|
| Autodiscovery | No | Yes |
| MAC | Yes (without ESI) | Yes |
| MACIP (ARP/ND) | Yes (without ESI) | Yes |
| Inclusive Multicast | Yes | Yes |
| Ethernet Segment (ES) | No | Yes |
| IP-Prefix (IPv4Prefix/IPv6Prefix) | Yes | Yes (without router MAC) |