Support multi-regional deployment without LAN summaries#33
Merged
dmitryperets merged 3 commits intorelease/7.4from Nov 28, 2024
Merged
Support multi-regional deployment without LAN summaries#33dmitryperets merged 3 commits intorelease/7.4from
dmitryperets merged 3 commits intorelease/7.4from
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Normally we expect the LAN prefixes to be summaried on the regional boundaries (that is, on the Hub-to-Hub EBGP peering). However, this is not always possible: network addressing is not always under customer's tight control.
This enhancement makes the LAN summarization optional.
In fact, it was already optional within the region. Now it becomes optional also for a multi-regional deployment.
Below we summarize the routing behavior.
Within a region:
If the LAN summary is configured:
If the LAN summary is not configured:
In the offline mode, this is automatically done by the Jinja Orchestrator.
In FortiManager-based deployment, this must be done externally.
The Jinja Orchestrator does not handle this.
Between regions:
If the LAN summary is configured:
If the LAN summary is not configured:
The expectation is, again, that Spokes have a valid route (e.g. default route) to all the LAN destinations via the overlay tunnels.
The bottom line is: we recommend configuring LAN summaries whenever the network addressing permits that, to guarantee the most scalable routing design. At the same time, we support network environments where this summarization is not possible.