{"push_id":2824414487,"size":1,"distinct_size":1,"ref":"refs/heads/ospf_vrf_dev","head":"96065dc3104a2f2dcfc2e7defd13a61662bd597e","before":"244d9f5a4d4fd646b978748ba59ab3522c087bf5","commits":[{"sha":"96065dc3104a2f2dcfc2e7defd13a61662bd597e","author":{"name":"Chirag Shah","email":"d6a45f5f463907f28ca87321deabd23203964ae0@cumulusnetworks.com"},"message":"ospfd: interface speed change during intf add\n\nThe problem is seen where speed mismatch caused ECMP route\nnot being reflected with correct number paths (NHs).\n\nDuring cold boot, some interface speed updated by zebra as\npart of one shot timer and triggers interface add to clients.\nIn this case, ospf already have created interface (bond interface),\nbut speed was not updated, trigger to do interface speed change\nas part of interface add, which will trigger all Router LSA to\nuse updated speed into cost calculation.\n\nTicket:CM-22170\nTesting Done:\nBring up CLOS config with Spine and leafs. Leaf have CLAG pair,\nwith same VRR ip address.\nAt spine one of the bond connecting to leaf node was having\nhigher speed than the paired device, With this fix, at spine (DUT)\nbond interface speed is equal from all peer nodes.\n\nSigned-off-by: Chirag Shah <chirag@cumulusnetworks.com>","distinct":true,"url":"https://api.github.com/repos/chiragshah6/frr/commits/96065dc3104a2f2dcfc2e7defd13a61662bd597e"}]}
{"actor":{"display_login":"chiragshah6"}}