diff options
| author | b29332 <bao.zhen@h3c.com> | 2024-08-15 16:20:19 +0800 |
|---|---|---|
| committer | riw777 <355715+riw777@users.noreply.github.com> | 2025-02-04 11:33:02 +0000 |
| commit | 27413dd24a431ac1a67d3e790c3d0e67000fb47b (patch) | |
| tree | 76f8b68035341fd7a7798be388c5ebddff088fce /yang/frr-isisd.yang | |
| parent | 817c2c98230f3825df65283fc68f1b8f8a317d04 (diff) | |
isisd: 'tiebreaker' command line funtionality is inconsistent with its implementation
The command fast-reroute lfa tiebreaker [downstream | lowest-backup-metric | node-protecting] index (1-255) [level-1 | level-2] will overwrite configurations with the same index but different types. This is because the index is set as the key in frr-isisd.yang. However, the lfa_tiebreaker_cmp function uses a tuple (index, type) as the key. Therefore, the yang file should be modified to stay in sync with the business logic.
Test Scenario:
On RouterA, first configure fast-reroute lfa tiebreaker downstream index 100 level-1, then configure fast-reroute lfa tiebreaker lowest-backup-metric index 100 level-1, and check the configuration:
!
router isis 10
fast-reroute lfa tiebreaker lowest-backup-metric index 100 level-1
exit
!
Signed-off-by: baozhen-H3C <bao.zhen@h3c.com>
Diffstat (limited to 'yang/frr-isisd.yang')
| -rw-r--r-- | yang/frr-isisd.yang | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/yang/frr-isisd.yang b/yang/frr-isisd.yang index a3e073f626..228faa4f10 100644 --- a/yang/frr-isisd.yang +++ b/yang/frr-isisd.yang @@ -403,7 +403,7 @@ module frr-isisd { "Limit backup computation up to the prefix priority."; } list tiebreaker { - key "index"; + key "index type"; unique "type"; description "Configure tiebreaker for multiple backups."; |