You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately I can't share full configs at this moment, but here are some snippets that will illustrate:
We have configuration similar to below where a static is created with a tag and a BGP policy that matches on protocol static and tag 80. This caused the route to be filtered in outbound BGP advertisements. If I removed the "from tag 80" term, the route is advertised as I would expect.
I checked the static route in Batfish and the tag seems to be applied correctly, just the policy component isnt working properly.
set routing-options static route 1.0.0.0/15 tag 80
set policy-options policy-statement OUT term ALLOW-OUT from protocol static
set policy-options policy-statement OUT term ALLOW-OUT from tag 80
set policy-options policy-statement OUT term ALLOW-OUT then accept
The text was updated successfully, but these errors were encountered:
Unfortunately I can't share full configs at this moment, but here are some snippets that will illustrate:
We have configuration similar to below where a static is created with a tag and a BGP policy that matches on protocol static and tag 80. This caused the route to be filtered in outbound BGP advertisements. If I removed the "from tag 80" term, the route is advertised as I would expect.
I checked the static route in Batfish and the tag seems to be applied correctly, just the policy component isnt working properly.
set routing-options static route 1.0.0.0/15 tag 80
set policy-options policy-statement OUT term ALLOW-OUT from protocol static
set policy-options policy-statement OUT term ALLOW-OUT from tag 80
set policy-options policy-statement OUT term ALLOW-OUT then accept
The text was updated successfully, but these errors were encountered: