Controlling ExaBGP : interacting from the API

There are several commands in order to interact with ExaBGP from the API. Here some of the possibilities are listed.

Please notice that you can check all of the possible options in the schedule function within the reactor

---

###API to handle ExaBGP

• shutdown Terminates ExaBGP. > shutdown in progress
• reload Reload ExaBGP's configuration > reload in progress
• restart Reloads ExaBGP from scracth > restart in progress
• version Answers in the shape: > 'exabgp %s' % version
• show neighbors
• show routes
• show routes extensive
• announce watchdog
• withdraw watchdog

---

###API to handle neighbors

• 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
• flush route ...
• withdraw route ...
• announce attribute ...
• withdraw attribute ...
• announce flow ...
• withdraw flow ...
• teardown ... See notes below for more information.
• announce route-refresh ...
• operational ...

---

BGP Cease Status Codes for Teardown:

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