bgp nlri evpn

Pre-Alpha. This page describes behavior that may change.

L2VPN EVPN (AFI 25 / SAFI 70), per RFC 7432. Encodes and decodes all five EVPN route types.

Category

Address families.

Configuration

plugin {
    internal nlri-evpn { use bgp-nlri-evpn }
}

bgp {
    peer upstream {
        family {
            l2vpn/evpn { prefix { maximum 10000; } }
        }
    }
}

Behaviour

The plugin handles all five EVPN route types: Ethernet Auto-Discovery, MAC/IP Advertisement, Inclusive Multicast Ethernet Tag, Ethernet Segment, and IP Prefix. Routes are parsed into their structured form for event subscribers and re-encoded for forwarding.

EVPN is what you use for L2VPN services over a BGP control plane. Pair with the VXLAN or MPLS-based dataplane of your choice.

Ze is a control-plane relay, not a PE. There is no MAC-VRF or EVI, no bridge or MAC learning, no ARP/ND cache, and no EVPN forwarding plane. Ze parses, stores, and re-advertises EVPN routes; it does not terminate the service.

RFC 7432 is enrolled in the requirement gate with 82 gated MUST-level obligations: 3 proven by tagged tests, 13 recorded as gaps, and 66 not applicable because they bind PE roles Ze does not play. The RFC status ledger names each one.

On decode, the MAC/IP Advertisement and Ethernet Segment route types reject a malformed IP Address Length rather than accepting it. Only 0, 32, and 128 are valid; anything else is an error, not a value to work around.

Interactions

• Works alongside bgp-nlri-vpn when you mix L2 and L3 VPN services.
• Supports both encode and decode.

Source

main/internal/component/bgp/plugins/nlri/evpn/