-
Notifications
You must be signed in to change notification settings - Fork 2
bgp nlri vpls
Thomas Mangin edited this page May 30, 2026
·
4 revisions
Pre-Alpha. This page describes behavior that may change.
L2VPN VPLS (AFI 25 / SAFI 65). The older L2VPN family, largely superseded by EVPN for new deployments.
Address families.
plugin {
internal nlri-vpls { use bgp-nlri-vpls }
}
bgp {
peer upstream {
family {
l2vpn/vpls { prefix { maximum 10000; } }
}
}
}
Encode and decode VPLS NLRIs. Routes carry a Route Distinguisher, a Virtual Edge (VE) ID, and the label block information that makes up the VPLS control plane.
VPLS is a legacy family. For new deployments, prefer bgp-nlri-evpn. The plugin exists for interoperability with networks that still run VPLS.
- Supports both encode and decode.
- Does not interact with
bgp-nlri-evpndirectly; the two families are orthogonal.
main/internal/component/bgp/plugins/nlri/vpls/
Unreviewed draft. This wiki was authored in bulk and has not been reviewed. File corrections on the issue tracker.
- Overview
- YANG Model
- Editor Workflow
- Archive and Rollback
- System
- Interfaces
- VRRP
- BFD
- FIB
- OSPF
- IS-IS
- MPLS / LDP / RSVP-TE
- RSVP-TE
- SRv6
- Static Routes
- Policy Routing
- Firewall
- Traffic Control
- Class of Service
- L2TP/PPP
- PPPoE
- VPP Data Plane
- RPKI
- IPsec VPN
- TACACS+ AAA
- RADIUS AAA
- AS112 DNS
- Authorization
- Fleet
- BGP
- Starting and Stopping
- Show Commands
- Monitoring
- Flow Export
- DDoS Mitigation
- Anomaly Detection
- Health Checks
- Audit Trail
- Production Diagnostics
- Logging
- Operational Reports
- Healthcheck
- Self-Update
- Zero-Touch Provisioning
- MRT Analysis
- Upgrade and Restart
- Storage
- Policy
- Core
- Resilience
- Validation
- Capabilities
- Address Families
- Protocol
- Subsystems
- Infrastructure
- Route Server at an IXP
- Transit Edge with RPKI
- Public Looking Glass
- ExaBGP Migration Walkthrough
- FlowSpec Injection
- Chaos-Tested Peering
- AS Path Topology