-
Notifications
You must be signed in to change notification settings - Fork 447
Controlling ExaBGP : interacting from the API
chantra edited this page May 2, 2018
·
18 revisions
There are several commands in order to interact with ExaBGP from the API. Here some of the possibilities are listed.
- shutdown Terminates ExaBGP. > shutdown in progress
- reload Reload ExaBGP's configuration > reload in progress
- restart Reloads ExaBGP from scratch > restart in progress
- reset Reset clears the queue of pending command not yet completed
- version Show exabgp's version
- show neighbor [optional neighbor ip] summary
- show neighbor [optional neighbor ip] extensive
- show neighbor [optional neighbor ip] configuration
- show ajd-rib in [extensive] (will be integrated in neighbor)
- show ajd-rib out [extensive] (will be integrated in neighbor)
- announce watchdog
-
announce route (will be deprecated when
announce <afi> <safi>
is introduced) - announce eor
- announce flow
- announce operational
- announce vpls
- announce route-refresh
- teardown
every announce
command has it withdraw
equivalent.
Answers in the shape: exabgp <version>
where version can be in the form of the release 3.4.20
or the git version like exabgp master-2583e388ee833897b15cb6a653d255b718c183fc
-
announce route ...
neighbor 10.0.0.1 , neighbor 10.0.0.2 announce route 1.0.0.0/16 next-hop 101.1.101.1 split /16
The ExaBGP "teardown" feature requires the correct/specific status code to notify the "other end" the reason for the teardown. For example, syntax to notify the remote end of a max prefix trip
neighbor 10.0.0.1 teardown 1
See list below:
1 Maximum Number of Prefixes Reached
2 Administrative Shutdown
3 Peer De-configured
4 Administrative Reset
5 Connection Rejected
6 Other Configuration Change
7 Connection Collision Resolution
8 Out of Resources
Get Started
Misc
Self-Promotion