what does /routing bgp advertisements printI've having a little trouble getting bgp to advertise my route. I'm not entirely sure whether the issue is on my end or if my provider is filtering me incorrectly. Before I call them, I wanted to make sure that I have things set up properly.
I have a single /22 that I'm trying to advertise to my upstream provider (Qwest). I'm using version 2.9.42. Here's my configuration:
/ routing filter
add chain=bgp_out prefix=184.108.40.206/22 invert-match=yes action=discard comment="" \
/ routing bgp instance
set default name="default" as=32808 router-id=220.127.116.11 redistribute-connected=yes \
redistribute-static=yes redistribute-rip=no redistribute-ospf=no \
redistribute-other-bgp=no out-filter=bgp_out client-to-client-reflection=yes \
ignore-as-path-len=no comment="" disabled=no
/ routing bgp peer
add name="qwest" instance=default remote-address=18.104.22.168 remote-as=209 \
tcp-md5-key="" nexthop-choice=default multihop=no route-reflect=no hold-time=3m \
ttl=1 in-filter="" out-filter=bgp_out comment="" disabled=no
Should this occomplish my goal of advertising 22.214.171.124/22 to Qwest? Does anyone see anything wrong with this set up? (BTW, I am connected to the remote end and I am receiving routes from them.) Thanks in advance.
Because the announcement is either generated by a static route or a connected route, not by a "network" announcement, and it's not IGP or EGP.Why would it say that the origin is "incomplete".
No.. once the bgp session is up and you can see you route in the announced prefixes, 99% you have everything set up fine, and there is still work to do in the upstream filters (or the upstream upstreams filter).Would this have anything to do with the fact that when I look it up in the looking glass, it says "Not advertised to any peer"? Thanks for the help so far!