Add ISIS single-topology metric leaf under interface level config #1206
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.
Change Scope
Add ISIS single-topology metric leaf under interface/level:
Resolves #1093
Rationale
Currently, the ISIS metric can only be defined per Address Family under isis interface/level. This is not a problem for ISIS multi-topology but becomes an issue when an ISIS single-topology is used and an interface has only IPv6 AF configured. In most implementations today the IPv6 ISIS metric is ignored in ISIS single-topology mode. Instead, one has to configure IPv4 AF metric even for interfaces without IPV4 AF configured/enabled.
This change is backwards compatible
Platform Implementations
From Juniper ISIS metric reference and Juniper ISIS multi-topology reference
From Arista ISIS config guide