summaryrefslogtreecommitdiff
path: root/tests/topotests/bgp_oad/test_bgp_oad.py
diff options
context:
space:
mode:
authorDonald Sharp <sharpd@nvidia.com>2024-02-07 14:56:15 -0500
committerDonald Sharp <sharpd@nvidia.com>2024-07-03 09:34:55 -0400
commit266b0619942edd8d838235e14dc0cb71a772f585 (patch)
tree3bf209b3d69f255e371900de37271be9e62ab461 /tests/topotests/bgp_oad/test_bgp_oad.py
parentd4758b3ccc76c77d0b8ba255089f79e67379bb30 (diff)
zebra: Properly note that a nhg's nexthop has gone down
Current code when a link is set down is to just mark the nexthop group as not properly setup. Leaving situations where when an interface goes down and show output is entered we see incorrect state. This is true for anything that would be checking those flags at that point in time. Modify the interface down nexthop group code to notice the nexthops appropriately ( and I mean set the appropriate flags ) and to allow a `show ip route` command to actually display what is going on with the nexthops. eva# show ip route 1.0.0.0 Routing entry for 1.0.0.0/32 Known via "sharp", distance 150, metric 0, best Last update 00:00:06 ago * 192.168.44.33, via dummy1, weight 1 * 192.168.45.33, via dummy2, weight 1 sharpd@eva:~/frr1$ sudo ip link set dummy2 down eva# show ip route 1.0.0.0 Routing entry for 1.0.0.0/32 Known via "sharp", distance 150, metric 0, best Last update 00:00:12 ago * 192.168.44.33, via dummy1, weight 1 192.168.45.33, via dummy2 inactive, weight 1 Notice now that the 1.0.0.0/32 route now correctly displays the route for the nexthop group entry. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Diffstat (limited to 'tests/topotests/bgp_oad/test_bgp_oad.py')
0 files changed, 0 insertions, 0 deletions