These are chat archives for Exa-Networks/exabgp

21st
Oct 2018
Stacey Sheldon
@solidgoldbomb
Oct 21 2018 16:58
Could someone help me adapt a 3.x API command to the equivalent in 4.x?
Stacey Sheldon
@solidgoldbomb
Oct 21 2018 16:59
In 3.x: announce attribute next-hop ${myip} community [ 65142:666 no-export ] nlri cidr cidr cidr ...
ahh, thanks. will take a look.
Thomas Mangin
@thomas-mangin
Oct 21 2018 17:00
This is the only doc I have and I could not tell you without doing the work myself neither !
That announce command should still work on 4.0
Please look at the /etc folder within the github repository to find examples of working configurations
Stacey Sheldon
@solidgoldbomb
Oct 21 2018 17:02
i looked through there quite a bit but didn't see any examples of announce attribute being sent via the API. maybe i missed it.
Thomas Mangin
@thomas-mangin
Oct 21 2018 17:02
the announce API should work as was ..
But it has been a few years and my memory may let me down
Stacey Sheldon
@solidgoldbomb
Oct 21 2018 17:04
I'm running 4.0.8 from pip
I get this: "api | command from process not understood : announce attribute next-hop 127.0.1.1 community [ 65142:666 no-export ] nlri 198.51.100.0/24"
I can try to dig further to identify the issue but thought I'd ask here first in case this had been dropped from the api.
any useful debug I can turn on to dump more detail of why the api is unhappy with this?
Thomas Mangin
@thomas-mangin
Oct 21 2018 17:08
I am surprised !
that should help
Stacey Sheldon
@solidgoldbomb
Oct 21 2018 17:14
ok, will try that right after my current test against 3.4.26. It's possible that this project has only previously been tested against exabgp 3.4.18.
Stacey Sheldon
@solidgoldbomb
Oct 21 2018 17:20
Looks like it works in 3.4.26
Sun, 21 Oct 2018 13:19:26 | INFO | 12290 | processes | Command from process bhr-dynamic : announce attribute next-hop 127.0.1.1 community [ 65142:666 no-export ] nlri 2001:db8:abcd:ef01::/64
Sun, 21 Oct 2018 13:19:26 | INFO | 12290 | reactor | Route added to neighbor 192.168.2.201 local-ip 127.0.1.1 local-as 64512 peer-as 65000 router-id 127.0.1.1 family-allowed in-open : 2001:db8:abcd:ef01::/64 next-hop 127.0.1.1 community [ 65142:666 no-export ]
Also works for the same IPv4 subnet from my previous example
processes | Command from process bhr-dynamic : announce attribute next-hop 127.0.1.1 community [ 65142:666 no-export ] nlri 198.51.100.0/24
So 3.4.26 == success. Will flip back to 4.0.8 and try with more debugging enabled as suggested.
Thomas Mangin
@thomas-mangin
Oct 21 2018 17:24
ok - if I can keep backward compatibility easily I will look into it
when I can …..
Stacey Sheldon
@solidgoldbomb
Oct 21 2018 17:26
if not able to be backwards compatible, is there another form of that announcement that i can use that will work in 4.x?
Thomas Mangin
@thomas-mangin
Oct 21 2018 17:26
It should work - it may be an issue.
I can not look atm but I may be later on this week ..
Stacey Sheldon
@solidgoldbomb
Oct 21 2018 17:36
I ran exabgp 4.0.8 with: env exabgp_debug_configuration=1 exabgp_debug_all=1 exabgp --debug <conf>
Shows the failure with a bit of new context but not much
13:30:27 | 12697 | process | command from process bhr-dynamic : announce attribute next-hop 127.0.1.1 community [ 65142:666 no-export ] nlri 198.51.100.0/24
13:30:27 | 12697 | process | responding to bhr-dynamic : error
13:30:27 | 12697 | api | command from process not understood : announce attribute next-hop 127.0.1.1 community [ 65142:666 no-export ] nlri 198.51.100.0/24
Thanks for offering to look into it thomas-mangin.
For now, I'll back off to 3.4.26. If you want me to test any fixes, I should be able to help out.
Stacey Sheldon
@solidgoldbomb
Oct 21 2018 18:01
thomas-mangin: ^^ let me know if you need any other information beyond what's in the issue