Repository navigation
Command Reference
A-Z alphabetical reference for all ExaBGP commands (API and configuration)
Complete command reference covering API commands, configuration directives, and operational commands.
- Overview
- API Commands
- Configuration Directives
- CLI Commands
- Alphabetical Quick Reference
- Command Categories
ExaBGP has three types of commands:
| Type | Where Used | Purpose | Example |
|---|---|---|---|
| API Commands | Process STDOUT → ExaBGP STDIN | Dynamic route control | announce route 10.0.0.0/24 next-hop self |
| Configuration Directives | Config file | Static configuration | neighbor 192.168.1.1 { } |
| CLI Commands | Terminal/shell | ExaBGP operation | exabgp configuration validate /etc/exabgp/exabgp.conf |
All API commands are sent via STDOUT from your process to ExaBGP.
import sys
# Send command
sys.stdout.write("announce route 10.0.0.0/24 next-hop self\n")
sys.stdout.flush() # CRITICAL: Always flush!Rules:
- ✅ Always end commands with
\n - ✅ Always call
sys.stdout.flush()after writing - ✅ Commands are case-sensitive
- ✅ ExaBGP answers every command with
doneorerroron the program's STDIN, which the program has to read, see Reading the answers - ℹ️ ACK can be disabled:
- Environment variable:
exabgp.api.ack=false(4.x, 5.x and 6.0) - Runtime commands:
disable-ackorsilence-ackin 5.x,session ack disableorsession ack silencein 6.0
- Environment variable:
Announce IPv4/IPv6 unicast route
Syntax:
announce route <prefix> next-hop <ip> [attributes]
Examples:
# Basic IPv4
announce route 10.0.0.0/24 next-hop self
announce route 10.0.0.0/24 next-hop 192.168.1.1
# Basic IPv6
announce route 2001:db8::/64 next-hop 2001:db8::1
announce route 2001:db8::/64 next-hop self
# With attributes
announce route 10.0.0.0/24 next-hop self community [65001:100]
announce route 10.0.0.0/24 next-hop self as-path [65001 65002]
announce route 10.0.0.0/24 next-hop self local-preference 200
announce route 10.0.0.0/24 next-hop self med 50
announce route 10.0.0.0/24 next-hop self origin igp
# Combined attributes
announce route 10.0.0.0/24 next-hop self local-preference 200 community [65001:100] as-path [65001]Attributes:
-
next-hop self- Use local router IP -
next-hop <ip>- Explicit next-hop -
community [<asn>:<value>]- BGP communities -
large-community [<asn>:<v1>:<v2>]- Large communities (RFC 8092) -
as-path [<asn> ...]- AS path -
local-preference <n>- Local preference (higher = preferred) -
med <n>- Multi-Exit Discriminator (lower = preferred) -
origin igp|egp|incomplete- Origin attribute
See also: Text API Reference, Attribute Reference
Announce FlowSpec rule
Syntax:
announce flow route { match { <conditions> } then { <actions> } }
Examples:
# Block TCP port 80 from 10.0.0.0/8
announce flow route { match { source 10.0.0.0/8; destination-port =80; protocol =tcp; } then { discard; } }
# Rate limit UDP traffic to 1 Mbps
announce flow route { match { destination 192.168.1.0/24; protocol =udp; } then { rate-limit 1000000; } }
# Redirect traffic to VRF
announce flow route { match { source 10.0.0.0/8; } then { redirect 65001:100; } }
# Mark DSCP
announce flow route { match { source 10.0.0.0/8; } then { mark 10; } }
# Complex rule with multiple conditions
announce flow route { match { source 10.0.0.0/8; destination 192.168.0.0/16; destination-port [ =80 =443 ]; protocol =tcp; } then { discard; community [65001:666]; } }ADD-PATH (6.0.0+): a flow route takes path-information <id> (written 0.0.0.2 or 2), sent in front of the NLRI when ADD-PATH is negotiated for the flow family. It works in the block form and in the flat form:
announce flow route { path-information 2; match { destination 10.0.0.0/24; } then { discard; } }
announce flow route path-information 2 destination 10.0.0.0/24 discardMatch Conditions:
-
source <prefix>- Source IP prefix -
destination <prefix>- Destination IP prefix -
port [=<port>]- Any port (source or destination) -
source-port [=<port>]- Source port -
destination-port [=<port>]- Destination port -
protocol [=<proto>]- Protocol (tcp, udp, icmp, or number) -
packet-length [>N&<M]- Packet length range -
tcp-flags [SYN ACK]- TCP flags -
fragment [first-fragment]- Fragment type
Actions:
-
discard- Drop traffic -
rate-limit <value>- Rate limit in bytes/second (per RFC 5575) -
redirect <asn>:<value>- Redirect to VRF -
redirect <ip>- Redirect to IP -
mark <dscp>- Mark DSCP value -
community [<asn>:<value>]- Add community -
action sample|terminal- FlowSpec action flags
See also: FlowSpec Overview, Match Conditions, Actions Reference
Announce a VPNv4 or VPNv6 (L3VPN) route
A route with a route distinguisher and a label is an L3VPN route. There is no vpnv4 or
vpnv6 command.
Syntax:
announce route <prefix> rd <rd> label <label> next-hop <ip> [attributes]
Examples:
# VPNv4
announce route 10.0.0.0/24 rd 65001:100 label 100 next-hop 192.168.1.1 extended-community [target:65001:100]
# Multiple Route Targets
announce route 10.0.0.0/24 rd 65001:100 label 100 next-hop 192.168.1.1 extended-community [target:65001:100 target:65001:200]
# VPNv6
announce route 2001:db8::/64 rd 65001:100 label 100 next-hop 2001:db8::1 extended-community [target:65001:100]A route with an rd and no label is refused.
Route Distinguisher formats:
-
<asn>:<value>- 2-byte ASN format (e.g.,65001:100) -
<ip>:<value>- IPv4 format (e.g.,192.168.1.1:100) -
<4byte-asn>:<value>- 4-byte ASN format (e.g.,4200000000:100)
See also: L3VPN Overview
Announce VPLS (L2VPN) route
Syntax:
announce vpls endpoint <n> base <n> offset <n> size <n> rd <rd> next-hop <ip> [attributes]
Examples:
announce vpls endpoint 10 base 10000 offset 10 size 8 rd 65001:100 next-hop 192.0.2.1 extended-community [target:65001:100]See also: VPLS Configuration
Withdraw IPv4/IPv6 unicast route
Syntax:
withdraw route <prefix> [next-hop <ip>]
Examples:
# Withdraw IPv4
withdraw route 10.0.0.0/24
withdraw route 10.0.0.0/24 next-hop 192.168.1.1
# Withdraw IPv6
withdraw route 2001:db8::/64
withdraw route 2001:db8::/64 next-hop 2001:db8::1Note: If multiple routes with different next-hops exist for the same prefix, you must specify the next-hop to withdraw a specific one.
See also: Text API Reference
Withdraw FlowSpec rule
Syntax:
withdraw flow route { match { <conditions> } }
Examples:
# Withdraw by exact match
withdraw flow route { match { source 10.0.0.0/8; destination-port =80; protocol =tcp; } }
# The match conditions must EXACTLY match the announced ruleImportant: You must specify the exact same match conditions used in the original announcement.
See also: FlowSpec Overview
Withdraw a VPNv4 or VPNv6 route
Syntax:
withdraw route <prefix> rd <rd> [label <label>] [next-hop <ip>]
Examples:
withdraw route 10.0.0.0/24 rd 65001:100
withdraw route 10.0.0.0/24 rd 65001:100 next-hop 192.168.1.1 label 100
withdraw route 2001:db8::/64 rd 65001:100Stop ExaBGP
Syntax:
shutdown # v4
daemon shutdown # v6
Examples:
# Stop the daemon: every session is closed and the process exits
shutdownBehavior:
- Answers
shutdown in progress(or{"status": "shutdown in progress"}with the JSON encoder) - Stops listening, closes every BGP session, terminates the API processes, removes the PID file and exits
- It is not a way to close one session: use
teardownfor that, ordisableto keep a neighbor down
See also: Debugging Guide
Close a neighbor session with a NOTIFICATION
Syntax:
neighbor <selector> teardown # Cease / Administrative Shutdown (6,2), 6.0.0+
neighbor <selector> teardown <subcode> [<text>] # Cease / <subcode>
neighbor <selector> teardown <code> <subcode> [<text>] # any code and subcode, 6.0.0+
peer <selector> teardown ... # 6.0.0 format, same arguments
Examples:
neighbor 192.168.1.1 teardown # 6/2
neighbor 10.0.0.1 teardown 4 # 6/4 Administrative Reset
neighbor 10.0.0.1 teardown 6 2 "[TICKET-1] upgrade, back in 2h"
neighbor 10.0.0.1 teardown 4 "12 monkeys" # quoted: starts with a digit
neighbor 10.0.0.1 teardown 3 1 testing # UPDATE / Malformed Attribute List
peer * teardown # 6.0.0 formatArguments:
- One number is a Cease subcode, not an error code:
teardown 6is Cease / Other Configuration Change (6/6). This is what the command has always done, whatever older documentation said. - Two numbers (6.0.0+) are the code and the subcode, any value from 0 to 255. A value IANA does not assign is logged as a warning, a value over 255 is answered with an error.
- Text (6.0.0+): for (6,2) and (6,4) it is the RFC 9003 Shutdown Communication (UTF-8, cut to 128 octets), otherwise the NOTIFICATION Data field. Quote it if it starts with a digit.
Behavior: only established sessions are closed, and the neighbor connects again. Use disable to keep it down.
Shut a neighbor down until it is enabled again
Syntax:
neighbor <selector> disable [<text>]
neighbor <selector> enable
peer <selector> disable [<text>] # 6.0.0 format
peer <selector> enable # 6.0.0 format
Examples:
neighbor 10.0.0.1 disable "[TICKET-1] upgrade, back in 2h"
neighbor 10.0.0.1 enable
peer * disableBehavior:
-
disablecloses an established session with Cease / Administrative Shutdown (6,2), the text being the RFC 9003 Shutdown Communication. A neighbor which is not established is disabled too. - While disabled, ExaBGP does not connect to the neighbor, refuses its connections with Cease / Connection Rejected (6,5), and
show neighborreports its state as disabled - The neighbor keeps its routes: what the API announces while it is disabled is sent once it is enabled, followed by End-of-RIB
-
enabletakes no argument and connects straight away -
shutdown true;in a neighbor starts it disabled, see Neighbor Configuration. A reload only acts onshutdownwhen its value changed in the file.
Send End-of-RIB (EoR) marker
Syntax:
announce eor [<afi> <safi>]
Examples:
# Signal end of initial route announcements
announce eor
announce eor ipv6 unicastThe command is answered with error when no session is established.
Purpose: Signals to BGP peer that initial route convergence is complete.
Automatic EoR: ExaBGP normally sends EoR automatically. Use manual EoR when you need fine-grained control (e.g., staggered announcements).
See also: Configuration Example, Manual EOR Example
ExaBGP 6.0.0 introduces a new "target-first" command format. Each program is held to the format of its first command which tells, so 5.x programs keep working; exabgp.api.version set to 4 or 6 holds every program to one format instead.
Announce or withdraw to ALL neighbors (6.0.0+ recommended)
Syntax:
peer * announce route <prefix> next-hop <ip> [attributes]
peer * withdraw route <prefix>
Examples:
# 6.0.0 format (recommended)
peer * announce route 10.0.0.0/24 next-hop self
peer * withdraw route 10.0.0.0/24
# 5.x format (a program written for 5.x)
announce route 10.0.0.0/24 next-hop selfAnnounce or withdraw to specific neighbor (6.0.0+ recommended)
Syntax:
peer <ip> announce route <prefix> next-hop <ip> [attributes]
peer <ip> withdraw route <prefix>
Examples:
# 6.0.0 format (recommended)
peer 192.0.2.1 announce route 10.0.0.0/24 next-hop self
peer 192.0.2.1 withdraw route 10.0.0.0/24
# 5.x format (a program written for 5.x)
neighbor 192.0.2.1 announce route 10.0.0.0/24 next-hop selfShow neighbor status (6.0.0)
Syntax:
peer show
Examples:
# 6.0.0 format
peer show
# 5.x format (a program written for 5.x)
show neighborShow RIB contents (6.0.0)
Syntax:
rib show in
rib show out
Examples:
# 6.0.0 format
rib show in
rib show out
# 5.x format (a program written for 5.x)
show adj-rib in
show adj-rib outDaemon control commands (6.0.0)
Syntax:
daemon shutdown
daemon status
Examples:
# 6.0.0 format
daemon shutdown
daemon status
# 5.x format (a program written for 5.x)
shutdown
statusHealth check ping command (6.0.0)
Syntax:
session ping
Examples:
# Health check ping - responds with pong + daemon UUID
session ping
# Response: {"pong": "abc123-uuid", "active": true}
# With "session ping text": pong abc123-uuid active=trueAvailability: ExaBGP 6.0.0+ only
Note: Use daemon status for full daemon information (version, uptime, peers).
ACK control commands (6.0.0 format)
Syntax:
session ack enable
session ack disable
session ack silence
Examples:
# 6.0.0 format
session ack enable
session ack disable
session ack silence
# 5.x format
enable-ack
disable-ack
silence-ackdisable answers with a last done before the answers stop; silence sends no answer from this command on, and silences error answers as well.
| 5.x Command | 6.0.0 Command | Notes |
|---|---|---|
announce route ... |
peer * announce route ... |
All neighbors |
neighbor <ip> announce ... |
peer <ip> announce ... |
Specific neighbor |
shutdown |
daemon shutdown |
Daemon control |
status |
daemon status |
Daemon status |
enable-ack |
session ack enable |
ACK control |
disable-ack |
session ack disable |
ACK control |
silence-ack |
session ack silence |
ACK control |
show neighbor |
peer show |
Peer status |
show adj-rib in |
rib show in |
RIB view |
show adj-rib out |
rib show out |
RIB view |
ping |
session ping |
Health check |
neighbor <ip> teardown ... |
peer <ip> teardown ... |
Close a session |
neighbor <ip> disable / enable
|
peer <ip> disable / enable
|
Both forms new in 6.0.0 |
Note: A program uses one format: its first command which tells decides which, and a command in the other format is answered error. 5.x scripts run unchanged; env exabgp_api_version=4 holds every program to the 5.x format.
Configuration file directives for static configuration.
These sections belong to the environment file (exabgp.env, see
Environment Variables), not to the configuration
file, which refuses them. Each setting can also be given as an environment variable, such as
exabgp.api.ack=false. A comment has to be on a line of its own: text after a value is read
as part of the value.
API configuration section
Syntax:
[exabgp.api]
ack = true|false
encoder = text|jsonExamples:
[exabgp.api]
# Command acknowledgment (done/error answers), on by default
ack = true
# Default encoder: text or json
encoder = textSee also: Environment Variables
Daemon mode configuration
Syntax:
[exabgp.daemon]
daemonize = true|false
pid = <path>
user = <username>Examples:
[exabgp.daemon]
daemonize = true
pid = /var/run/exabgp.pid
user = exabgpLogging configuration
Syntax:
[exabgp.log]
destination = stdout|syslog|<file-path>
level = DEBUG|INFO|WARNING|ERROR|CRITICAL
all = true|false
configuration = true|false
reactor = true|false
processes = true|false
network = true|false
packets = true|false
message = true|false
rib = true|falseExamples:
[exabgp.log]
destination = /var/log/exabgp.log
level = INFO
packets = true
message = true
network = trueSee also: Debugging Guide
Define BGP neighbor
Syntax:
neighbor <ip> {
<neighbor-directives>
}Examples:
neighbor 192.168.1.1 {
description "Primary BGP peer";
router-id 192.168.1.2;
local-address 192.168.1.2;
local-as 65001;
peer-as 65000;
}See also: Configuration Syntax
BGP router identifier
Syntax:
router-id <ipv4-address>Examples:
router-id 192.168.1.2;
router-id 10.0.0.1;Note: Must be a valid IPv4 address (even for IPv6-only sessions).
Local IP address to bind
Syntax:
local-address <ip>Examples:
local-address 192.168.1.2;
local-address 2001:db8::1;Local Autonomous System Number
Syntax:
local-as <asn>Examples:
local-as 65001;
local-as 4200000000; # 4-byte ASNPeer Autonomous System Number
Syntax:
peer-as <asn>Examples:
peer-as 65000;
peer-as 4200000000; # 4-byte ASNBGP hold time (seconds)
Syntax:
hold-time <seconds>Examples:
hold-time 180; # 3 minutes (common)
hold-time 90; # 1.5 minutes
hold-time 240; # 4 minutesDefault: 180 seconds
Keepalive: Automatically set to 1/3 of hold-time, jittered by a random factor between 0.75 and 1
TCP MD5 authentication
Syntax:
md5-password <password>Examples:
md5-password "MySecretPassword123";See also: Security Best Practices, Example
TTL security (Generalized TTL Security Mechanism)
Syntax:
incoming-ttl <hops>Examples:
incoming-ttl 255; # Only a directly connected peer is accepted (GTSM)
incoming-ttl 254; # A peer one router away is accepted tooSee also: Security Best Practices, Example
Address family configuration
Syntax:
family {
<afi> <safi>;
}Examples:
family {
ipv4 unicast;
ipv4 multicast;
ipv4 flow;
ipv4 flow-vpn;
ipv4 nlri-mpls;
ipv6 unicast;
ipv6 flow;
ipv4 mpls-vpn;
ipv6 mpls-vpn;
l2vpn vpls;
l2vpn evpn;
bgp-ls bgp-ls;
}Common AFI/SAFI combinations:
-
ipv4 unicast- IPv4 routing -
ipv6 unicast- IPv6 routing -
ipv4 flow- FlowSpec IPv4 -
ipv6 flow- FlowSpec IPv6 -
ipv4 mpls-vpn- VPNv4 (MPLS L3VPN) -
ipv6 mpls-vpn- VPNv6 -
l2vpn vpls- VPLS -
l2vpn evpn- EVPN -
bgp-ls bgp-ls- BGP-LS
See also: Address Families, Configuration Reference
Define API process
Syntax:
process <name> {
run <command>;
encoder text|json;
}Examples:
process announce-routes {
run /etc/exabgp/api/announce.py;
encoder text;
}
process healthcheck {
run python3 -m exabgp healthcheck --cmd "curl http://localhost";
encoder text;
}See also: Process Configuration, API Overview
Process command to execute
Syntax:
run <command> [arguments];Examples:
run /etc/exabgp/api/announce.py;
run python3 /etc/exabgp/api/healthcheck.py --interval 5;
run python3 -m exabgp healthcheck --cmd "curl http://localhost";Process encoder (text or json)
Syntax:
encoder text|json;Examples:
encoder text; # Use text API format
encoder json; # Use JSON API formatDefault: text
See also: Text API Reference, JSON API Reference
Static route block
Syntax:
static {
route <prefix> {
<attributes>
}
}Examples:
static {
route 10.0.0.0/24 {
next-hop 192.168.1.1;
community [65001:100];
}
route 10.0.1.0/24 next-hop 192.168.1.1; # Compact syntax
}FlowSpec block
Syntax:
flow {
route <name> {
path-information <id>; # optional, 6.0.0+, sent when ADD-PATH is negotiated
match { <conditions> }
then { <actions> }
}
}Examples:
flow {
route block-attack {
match {
source 10.0.0.0/8;
destination-port =80;
protocol tcp;
}
then {
discard;
community [65001:666];
}
}
}See also: FlowSpec Overview, Configuration Example
Commands for running and managing ExaBGP from the terminal.
Run ExaBGP with configuration file
Syntax:
exabgp [options] <config-file>Examples:
# Run with configuration
exabgp /etc/exabgp/exabgp.conf
# Run with every log category on (-d also starts the Python debugger on errors)
exabgp server -v /etc/exabgp/exabgp.conf
# Validate configuration (6.0; 5.x: exabgp validate)
exabgp configuration validate /etc/exabgp/exabgp.conf
# Run with specific environment file
exabgp --env-file /etc/exabgp/exabgp.env server /etc/exabgp/exabgp.confMain Subcommands (ExaBGP 5.x):
-
validate- Validate configuration and exit -
server- Run ExaBGP server (default if config file provided) -
version- Show version information -
cli- ExaBGP CLI for controlling running instance -
healthcheck- Health check mode -
env- Show environment configuration -
decode- Decode BGP packets
Note: In ExaBGP 4.x, use --test flag. In ExaBGP 5.x, use validate subcommand.
See also: Installation Guide, Quick Start
ExaBGP command-line interface
Syntax:
exabgpcli [command]Examples:
# Show version
exabgpcli version
# Show neighbors
exabgpcli show neighbor summary
# Show the routes sent
exabgpcli show adj-rib outNote: Requires ExaBGP to be running.
See also: ExaBGP CLI Documentation
Complete A-Z listing of all commands and directives.
| Command/Directive | Type | Purpose |
|---|---|---|
announce flow |
API | Announce FlowSpec rule |
announce route |
API | Announce IPv4/IPv6 unicast route |
announce eor |
API | Send End-of-RIB marker |
announce vpls |
API | Announce VPLS route |
as-path |
Attribute | AS path attribute |
community |
Attribute | BGP community attribute |
description |
Config | Neighbor description |
disable |
API | Shut a neighbor down until enabled (6.0.0+) |
enable |
API | Let a disabled neighbor connect again (6.0.0+) |
encoder |
Config | Process encoder (text/json) |
[exabgp.api] |
Environment file | API configuration section |
[exabgp.daemon] |
Environment file | Daemon configuration |
[exabgp.log] |
Environment file | Logging configuration |
exabgp |
CLI | Run ExaBGP |
exabgpcli |
CLI | ExaBGP CLI tool |
extended-community |
Attribute | Extended community attribute |
family |
Config | Address family configuration |
flow |
Config | FlowSpec static configuration |
hold-time |
Config | BGP hold time |
large-community |
Attribute | Large community attribute |
local-address |
Config | Local IP address |
local-as |
Config | Local AS number |
local-preference |
Attribute | Local preference attribute |
md5-password |
Config | MD5 authentication |
med |
Attribute | Multi-Exit Discriminator |
neighbor |
Config | BGP neighbor definition |
next-hop |
Attribute | Next-hop attribute |
origin |
Attribute | Origin attribute (igp/egp/incomplete) |
peer-as |
Config | Peer AS number |
process |
Config | API process definition |
router-id |
Config | BGP router ID |
run |
Config | Process command to execute |
shutdown |
API | Stop ExaBGP (v6: daemon shutdown) |
static |
Config | Static route block |
incoming-ttl |
Config | TTL security (GTSM) |
teardown |
API | Close a neighbor session with a NOTIFICATION |
withdraw flow |
API | Withdraw FlowSpec rule |
withdraw route |
API | Withdraw IPv4/IPv6 route |
withdraw vpls |
API | Withdraw VPLS route |
-
announce route- Announce unicast route -
announce flow- Announce FlowSpec rule -
announce route ... rd ... label ...- Announce VPN routes -
announce vpls- Announce VPLS route -
withdraw route- Withdraw unicast route -
withdraw flow- Withdraw FlowSpec rule -
withdraw route ... rd ...- Withdraw VPN routes
-
shutdown- Stop ExaBGP, closing every session (v6:daemon shutdown) -
teardown- Close a neighbor session with a NOTIFICATION -
disable/enable- Shut a neighbor down and bring it back (6.0.0+) -
announce eor- Send End-of-RIB marker
-
neighbor- Define BGP neighbor -
family- Configure address families -
process- Define API process -
static- Static routes -
flow- FlowSpec rules
-
next-hop- Next-hop configuration -
as-path- AS path manipulation -
community- Standard communities -
large-community- Large communities -
extended-community- Extended communities -
local-preference- Local preference -
med- Multi-Exit Discriminator -
origin- Origin attribute
All basic commands supported:
-
announce route,withdraw route -
announce flow,withdraw flow -
announce vpnv4,withdraw vpnv4 shutdownannounce eor
Not supported in 4.x:
-
enable-ack,disable-ack,silence-ack(5.x only; in 4.xexabgp.api.ack=falseis the only way to turn the answers off)
- ACK control commands (
enable-ack,disable-ack,silence-ack) - Enhanced JSON API format
See also: Migration from 4.x to 5.x
- API Overview - API architecture and concepts
- Text API Reference - Complete text API
- JSON API Reference - Complete JSON API
- Configuration Syntax - Configuration file syntax
- Directives Reference - All configuration directives
- Attribute Reference - All BGP attributes
- IPv4/IPv6 Unicast - Basic routing
- FlowSpec - DDoS mitigation
- L3VPN - MPLS VPNs
- EVPN - Data center fabrics
- Debugging Guide - Troubleshooting
- Monitoring Guide - Production monitoring
- Examples Index - Browse the configuration examples
- API Examples - API examples
- Configuration Examples - Static config examples
Getting Started
Configuration
- Configuration Syntax
- Neighbor Configuration
- Directives A-Z
- Syntax Reference
- Templates
- Environment Variables
- Process Configuration
API
- API Overview
- Text API Reference
- JSON API Reference
- API Commands
- Writing API Programs
- Error Handling
- Production Best Practices
Address Families
- Overview
- IPv4 Unicast
- IPv6 Unicast
- FlowSpec
- EVPN
- L3VPN
- BGP-LS
- VPLS
- SRv6 / MUP
- Multicast
- RT Constraint
Features
Use Cases
Tools
Operations
Reference
- Architecture
- Design
- Attribute Reference
- Command Reference
- BGP State Machine
- Capabilities
- Communities
- Examples Index
- Glossary
- RFC Support
Integration
Migration
Community
External