In network routing, the control plane is the part of the router architecture that is concerned with drawing the network topology, or the information in a routing table that defines what to do with incoming packets.
| Type | Description |
|---|---|
|
1 |
Ethernet Auto Discovery (AD) route |
|
2 |
MAC/IP advertisement route |
|
3 |
Inclusive Multicast Route |
|
4 |
Ethernet Segment Route |
|
5 |
IPv4/IPv6 Prefix Route |
|
7 |
IGMP Join Synch Route |
|
8 |
IGMP Leave Synch Route |
VxLAN data plane encapsulation is supported.
The BGP encapsulation extended-community attribute is carried with each route in the BGP control plane to signify the encapsulation to be used to reach the prefix. An EVPN route without an encapsulation extended-community attribute uses VxLAN encapsulation by default.
If an EVPN prefix is received from multiple sources with both VXLAN and MPLS encapsulations, the route source with VXLAN encapsulation is preferred within the data center.
The VLAN-based service-interface model described in RFC 7432 is supported. Each VLAN is mapped to a unique VNI label. Within the data center, each VNI maps to a unique EVI. This mapping is referred to as the "single subnet per EVI" option in "draft-ietf-bess-evpn-overlay." No VLAN translation service is supported. In the data center, VNI-to-VLAN mapping is local to each leaf, and the inner VxLAN frames may not carry an Ethernet tag. The administrator is responsible for keeping this mapping consistent in the data center.