Can't advertise static route over ebgp

[Mushussu]

Hi all,

i'm not having much joy getting this working.

I have created a static route for a subnet which I am trying to advertise to an eBGP peer.

I then created a redistribution profile with only static enabled

I then added that profile under bgp Redist Rules.

The BGP peering is definitely established and I am able to redistribute a Connected route no problem.

I tried it with and without export rules and that made no difference.

I tried all the steps in this page https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PNt2CAG

I've been beating away at it all day and have ran out of ideas. Any thoughts on what I might be missing?

[rmfalconer · Accepted solution]

As a test, did you try without a redistribution profile? In redist rules, you can just free type the prefix you're trying to redistribute, x.x.x.x/m, and click enable. 

[aleksandar.astardzhiev · Accepted solution]

Hi @Mushussu 

- Are you trying to redistribute default route or specific route? If it is default, don't forget to enable  default route redistribution

- Do you see the static route in the local rib?

> show routing protocol bgp loc-rib

- Stupid question, but actually a common mistake - When you created the redistribution profile, did you set the action to "redistribute", because the default is "no redist"

- BGP Redistribution Rules allows you to redistribute prefix, without needing to create Redist. Profile. The catch is that FW will create "dummy" router for that prefix and use it for redistribution. Main purpose of this approach is if you want to redistribute prefix that is not actually in FW routing table (for example additional public range used for NAT). It is not recommended to use it for static or directly connected routes - with redist profile, BGP will stop advertising the prefix if route is removed from routing table (without redist profile, the dummy route will always be there).  However just for the test you can try what @rmfalconer suggested and put the prefix directly in the bgp redist rule.

[Mushussu]

Thanks @rmfalconer that seems to have done the trick.

@aleksandar.astardzhiev advertising a public NAT range is exactly what I'm trying to do and many thanks for the explanation as to why it needs to be done this way for such cases.