Add eos_vrf_global model
#277
Open
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
5 tasks
|
@KB-perByte can you please merge this PR as the module is merged now? I dont have the permissions to merge this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I was reviewing the configuration options for the
eos_vrf_globalmodel on the EOS device and noticed that the available options are quite limited—mainly justdescriptionandrd. Additionally, I found that there is no address family support in EOS appliance under vrf section. I have attached a image of the options below for reference here.Given this, I’m wondering if we actually need a dedicated vrf_global module for EOS, as it doesn't seem to provide much beyond these basic options.
Would love to hear your thoughts on this :)