Guide
BGP
Ze includes a native BGP engine for external and internal peering, route-server work, policy-driven imports and exports, graceful operation, and programmable route injection.
Use this page as the BGP entry point. It links the operational guides and the generated feature pages instead of making the homepage choose one narrow BGP topic.
Start here
- BGP peering covers peers, groups, dynamic peer groups, address families, prefix limits, attached programs, ADD-PATH, BGP Role, and session verification.
- BGP policy covers import filters, export filters, redistribution, and route checks.
- BGP resilience covers route refresh, graceful restart, RIB persistence, and route reflection.
- BGP Role covers RFC 9234 role negotiation and OTC route-leak prevention.
- BGP healthcheck covers service checks that control BGP announcements.
- Graceful Restart covers RFC 4724 restart behavior in detail.
Feature references
- Native BGP engine documents the protocol implementation, negotiated capabilities, path handling, capture, replay, and wire-level behavior.
- BGP configuration documents the BGP configuration surface and points to the generated configuration reference.
- Programmable APIs documents REST, gRPC, and gNMI access to the same command and API engine.
- MCP integration documents AI-facing tools generated from the same command registry.
Labs and use cases
- BGP interop lab runs Ze against FRR, BIRD, and GoBGP.
- Route server at an IXP shows Ze as an RFC 7947 route server.
- Transit edge with RPKI shows a two-transit edge with origin validation.
- FlowSpec injection shows controlled BGP FlowSpec announcements.
- BGP performance testing shows repeatable route-server measurement.
When to use the feature page directly
Use Native BGP engine when you need protocol internals, RFC behavior, or proof links. Use BGP peering when you need to configure or operate a session.