Check for F0467 bgpProt-policy-already-existing#373
Open
dhaselva wants to merge 1 commit intodatacenter:masterfrom
Open
Check for F0467 bgpProt-policy-already-existing#373dhaselva wants to merge 1 commit intodatacenter:masterfrom
dhaselva wants to merge 1 commit intodatacenter:masterfrom
Conversation
| [Fabric Port Status][f19] | F1394: ethpm-if-port-down-fabric | :white_check_mark: | :no_entry_sign: | ||
| [Equipment Disk Limits][f20] | F1820: 80% -minor<br>F1821: -major<br>F1822: -critical | :white_check_mark: | :no_entry_sign: | ||
| [VMM Inventory Partially Synced][f21] | F0132: comp-ctrlr-operational-issues | :white_check_mark: | :no_entry_sign: | ||
| [BGP Policy Already Existing][f22] | F0467: bgpProt-policy-already-existing | :white_check_mark: | :no_entry_sign: |
There was a problem hiding this comment.
bgpProto timer policy already existing
| ### BGP Policy Already Existing | ||
|
|
||
| This check validates `F0467` faults where `changeSet` contains `bgpProt-policy-already-existing`. | ||
| The fault indicates conflicting BGP protocol policy configuration under an L3Out deployment path. |
There was a problem hiding this comment.
The fault indicates conflicting BGP protocol timer policy configuration under an L3Outs deployed under vrf in same node.
| This check validates `F0467` faults where `changeSet` contains `bgpProt-policy-already-existing`. | ||
| The fault indicates conflicting BGP protocol policy configuration under an L3Out deployment path. | ||
|
|
||
| Resolve these faults before upgrade by reviewing the affected L3Out BGP policy and removing duplicate or inconsistent configuration. |
There was a problem hiding this comment.
Resolve these faults before upgrade by reviewing the affected L3Out BGP proto timer policy.
| data = [] | ||
| unformatted_headers = ['Fault', 'Affected', 'changeSet'] | ||
| unformatted_data = [] | ||
| recommended_action = 'Resolve duplicate BGP policy configuration on the affected L3Out.' |
There was a problem hiding this comment.
Remove the fault by keeping Single bgp policy per vrf for different l3out.
lovkeshsharma702
left a comment
lovkeshsharma702
left a comment
There was a problem hiding this comment.
can we add this check closer to other check for fault 4067
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.
F0467_bgpProt-policy-already-existing.txt
Attached the local run log.
Issue