-
Notifications
You must be signed in to change notification settings - Fork 2
bgp nlri mup
Thomas Mangin edited this page May 30, 2026
·
4 revisions
Pre-Alpha. This page describes behavior that may change.
Mobile User Plane SAFI for IPv4 (AFI 1 / SAFI 85) and IPv6 (AFI 2 / SAFI 85).
Address families.
plugin {
internal nlri-mup { use bgp-nlri-mup }
}
bgp {
peer upstream {
family {
ipv4/mup { prefix { maximum 10000; } }
ipv6/mup { prefix { maximum 10000; } }
}
}
}
MUP is the control plane for 5G Mobile User Plane integration with BGP. The plugin encodes and decodes MUP NLRIs for both address families. Routes carry user plane information that routers in the path use to direct mobile traffic.
MUP is a specialised family. Most deployments do not need it. Enable it when you are integrating Ze into a 5G mobile user plane setup.
- Supports both encode and decode.
- Independent of the other address family plugins.
main/internal/component/bgp/plugins/nlri/mup/
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