Arista BGP default-originate route-map #3696
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the line:
neighbor 10.1.1.2 default-originate route-map ROUTE_MAP
Cisco uses
ROUTE_MAP
as a generation policy, but Arista instead applies it to the (unconditionally) exported default route (see Arista's documentation and notes from GNS3 for details). Currently Batfish always converts the route-map to a generation policy. This PR makes it add the route-map to the default route export policy instead if on an Arista device.The default route export policy can now vary per peer again, so we're back to creating one default route export policy per default-originating peer, except for NXOS, which still creates one default route export policy per config.