Fix for L3VNI W/O VLAN_ID generation #505 #508
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
2 participants
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.
<< Issue >>
#505
<< RCA >>
When a VRF (with L3VNI W/O enabled) is created using DCNM_VRF, vlan_id which is user specified or autogenerated from the module is sent to the NDFC in the payload. However, NDFC doesn't ignore it and it is set for the VRF.
Note: The vlan-id is not used when VRF configuration is pushed to the device, and is not allocated as a resource by the NDFC and can be still reused. Also, vlan autogeneration skips the ID and moves on to the next one, thinking it's allocated. This causes inconsistency.
<< Fix >>
Preventing autogeneration and transmitting of user-specified VLAN for a VRF with L3VNI W/O VLAN setting enabled.
Also, deriving the default setting value of L3VNI W/O VLAN at the VRF level from the Fabric level setting, instead of "False".