summaryrefslogtreecommitdiff
path: root/tests/topotests/zebra_multiple_connected/test_zebra_multiple_connected.py
diff options
context:
space:
mode:
authorYash Ranjan <ranjany@vmware.com>2022-03-21 04:30:22 -0700
committerYash Ranjan <ranjany@vmware.com>2022-04-17 21:55:22 -0700
commitec58bf6f244ea7c23bc33693f036249113fe8de7 (patch)
treeb3f73c064ac373c34e33bf6bb02326b07c36234d /tests/topotests/zebra_multiple_connected/test_zebra_multiple_connected.py
parenteb3bd824516e52823ef15bf77002a02ccd263738 (diff)
ospf6d: Check for MinLSInterval timer when adding to LSUpdate list
A router has some static routes and redistributes turned on. "clear ipv6 ospf process" command is applied. Then static routes are deleted. In 1 in 5 runs, AS-External LSAs are not getting removed from the neighbors even though it gets removed from its own LSDB. Because of the clear process command, MAX_AGE LSAs are advertised and fresh LSAs are installed in the LSDB. When the MAX_LSAs are advertised back to the same router as part of the flooding process, it gets added to the LSUpdate list even though it comes inside the MinLSArrival time. When the static routes get deleted, it removed the LSA from the LSRetrans list but not from LSUpdate list. The LSAs present in the LSUpdate list gets advertised when sending LS Updates. When an old copy of an LSA is more recent than the new LSA, check if it has come inside the MinLSArrival time before adding to the LSUpdate list. Signed-off-by: Yash Ranjan <ranjany@vmware.com>
Diffstat (limited to 'tests/topotests/zebra_multiple_connected/test_zebra_multiple_connected.py')
0 files changed, 0 insertions, 0 deletions