bgp nlri mvpn

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

Multicast VPN (RFC 6513, RFC 6514) for IPv4 (AFI 1 / SAFI 5) and IPv6 (AFI 2 / SAFI 5). Decode-only: Ze parses received MVPN NLRI. Encoding is not implemented. Decoding runs through the plugin NLRI pipeline, not the legacy core path.

Category

Address families.

Configuration

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

bgp {
    peer upstream {
        family {
            ipv4/mvpn { prefix { maximum 10000; } }
            ipv6/mvpn { prefix { maximum 10000; } }
        }
    }
}

Behaviour

Decodes MVPN NLRIs for both address families, parsing the seven standard MVPN route types into structured JSON for the event stream. Encoding is not implemented.

If your deployment requires MVPN as a route originator, Ze is not the answer. If you need to consume MVPN routes for monitoring or analysis, the decode path is enough.

Plugin pipeline

The bgp-nlri-mvpn plugin registers the InProcessNLRIDecoder callback (and a config route parser for migration tooling), so MVPN NLRIs flow through the same plugin pipeline as the other families. Because the family is decode-only, no NLRI or route encoder is registered. The plugin also registers the PMSI Tunnel path attribute (type 22, RFC 6514) so received MVPN updates render correctly. JSON output is produced through the attribute JSON registry with ExaBGP-compatible key ordering.

Interactions

• Decode-only.
• bgp-rib stores parsed MVPN NLRI but does not run best-path on the family.

Source

main/internal/component/bgp/plugins/nlri/mvpn/

See also

• Address Families for the full family list.
• VPN NLRI for unicast L3VPN.
• Plugins for the plugin catalogue.

Adapted from the mvpn plugin source code (RFC 6513 / RFC 6514).