How to ANNOUNCE large scale BGP route with ExaBGP's API

[goodluck68]

How to ANNOUNCE large scale BGP route with ExaBGP's API

[thomas-mangin]

There is no HTTP API with ExaBGP so whatever you are using is not part of any code we support.

All annoucements are single line text based, so I have no idea how you get to use HTTP but it must pass the HTTP payload via the ExaAPI API which is two unix pipes connected to STDIN and STDOUT.

If you need to improve this code, please look for post using announce attribute ... ... ... nlri ... ... ... which allows to announce multiple NLRIs which share the same attributes.

[goodluck68]

There is no HTTP API with ExaBGP so whatever you are using is not part of any code we support.

All annoucements are single line text based, so I have no idea how you get to use HTTP but it must pass the HTTP payload via the ExaAPI API which is two unix pipes connected to STDIN and STDOUT.

If you need to improve this code, please look for post using announce attribute ... ... ... nlri ... ... ... which allows to announce multiple NLRIs which share the same attributes.

Thanks your suggestion! I have found an example ANNOUNCE attribute next-hop self nlri 10.0.1.0/24 10.0.1.1/24 10.0.1.2/24. I will base on this to update my case

Another question need your help. If I withdraw multiple BGP NLRI, does the command work? like this WITHDRAW attribute next-hop self nlri 10.0.1.0/24 10.0.1.1/24 10.0.1.2/24
In the BGP protocol, the UPDATE message does not require path attribute info when withdrawing a route, so I want to know whether the withdraw command is correct?

[thomas-mangin]

It is plural, but I just allowed singular on the main branch.

exabgp/src/exabgp/reactor/api/command/announce.py

Line 257 in c299fdb

@Command.register('text', 'withdraw attributes')

Unless you are using PATH_INFO or VPLS/MPLS, it may not require the attribute data. I would need to check the RFC and the code to be sure what the code does and if it is right ...