Merged
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.
By default, it is assumed that the SD-WAN is configured in the "root" VDOM. If this is not the case, it is now possible to specify the VDOM name, using
vdomparameter.This optional parameter can be set either globally (for the entire project):
...or per profile (this overrides the global value):
Note that we DO NOT support multiple SD-WAN VDOMs on the same device. For example, we generate several special interfaces with fixed names (such as "Lo", "Lo-HC"...), and this would cause conflicts if you tried to do it in multiple VDOMs.
That is why there must be only one SD-WAN VDOM on the device. It's just that it doesn't have to be the "root" VDOM.
The "root" VDOM is still the default choice, when the
vdomparameter is not set (neither in the profile nor globally).