CASMNET-2260 Mountain HMN and HMN should use ospf area 2 #555
Conversation
This file contains 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
Mountain HMN and NMN are now in custom VRF, this change implies using ospf area 2
rustydb
changed the title
trad511
approved these changes
Nov 25, 2024
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.
Mountain HMN and NMN are now in custom VRF, this change implies using ospf area 2
Summary and Scope
Canu version 1.8 change Management Networks VRF from default to CSM, ospf area are also changed, this change hasn't been
applied to all NMN/HMN Vlans resulting in Mountain HMN/HMN still being in ospf area 1
the result is one ospf in area 1 for default vrf and two ospf areas (1 and 2) in CSM vrf, this patch fixes the discrepancy
Issues and Related PRs
addresses CASMNET-2260
Testing
Tested by applying the config to Hill CDU switches