You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My configuration:
route-map map1 permit 1
set metric 111
aggregate-address 66.0.0.0/16 as-set route-map map1
The metirc 111 is as expected
Network Next Hop Metric LocPrf Weight Path
*> 66.0.0.0/16 40.40.40.3 111 0 1111 10002 ?
*> 66.0.0.1/32 40.40.40.3 0 1111 10002 ?
But when I change map1 metric from 111 to 222, The metri of published routes is still 111!
sonic(config-router-af)# route-map map1 permit 1
sonic(config-route-map)# set metric 222
7.5 is a very old release, and lots have been fixed in terms of route-map/bgp. Please check with the latest versions (8.5, or 9.x).
Looking at the FRR 9.1 version code, I still haven't found a solution to this problem.
Do you agree that the above "set metric 222" should automatically trigger the re-publishing of the aggregate route with metric 222?
FRR 7.5
My configuration:
route-map map1 permit 1
set metric 111
aggregate-address 66.0.0.0/16 as-set route-map map1
The metirc 111 is as expected
Network Next Hop Metric LocPrf Weight Path
*> 66.0.0.0/16 40.40.40.3 111 0 1111 10002 ?
*> 66.0.0.1/32 40.40.40.3 0 1111 10002 ?
But when I change map1 metric from 111 to 222, The metri of published routes is still 111!
sonic(config-router-af)# route-map map1 permit 1
sonic(config-route-map)# set metric 222
route-map map1 permit 1
set metric 222
Network Next Hop Metric LocPrf Weight Path
*> 66.0.0.0/16 40.40.40.3 111 0 1111 10002 ?
*> 66.0.0.1/32 40.40.40.3 0 1111 10002 ?
The text was updated successfully, but these errors were encountered: