forked from sonic-net/sonic-mgmt
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Clean up the fdb on the sonic fanout in fdb test (sonic-net#15878)
Fanout switch should not learn any FDB entries at all, but it learns tens of thousands of them. FDB table for fanout is much bigger than FDB table for DUT. Replace 'show mac' with 'fdbshow' to improve the efficiency In this case, when do shutdown of the port from DUT, the port on the fanout will also go down. FDB flush also executed on this port on fanout, if there is too many fdb entries on the port, then during flushing following event occurred on fanout: INFO database#supervisord: redis 40:M 24 Oct 2024 15:23:08.510 #Lua slow script detected: still in execution after 6524 milliseconds. You can try killing the script using the SCRIPT KILL command. Script SHA1 is: 7acccfabe7fbd17d9a74e91c34de49c51d70749b ERR pmon#psud: :- checkReplyType: Expected to get redis type 3 got type 6, err: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE. Script fdb_flush.lua takes a long time to execute because it goes through all FDB entries in redis (This problem already described in community bug [warm-reboot] apps crash due to redis is busy running 'table_dump.lua' during warm-start sonic-net#3008. It is generic problem for any type of entries, no only FDB ) Finally on fanout will have following err: INFO swss#supervisord 2024-10-24 15:23:10,233 INFO exited: orchagent (terminated by SIGABRT (core dumped); not expected) It will cause Dockers go to restart and on dut ports will also go to DOWN state for a few seconds. In the fdb test case, we have the logic to cleanup the fdb entry on the dut, at the same time we also need to clean the fdb on fanout to avoid issue happen. Update mac move test to make it stable at dualtor aa setup 1.Replace 'show mac' with 'fdbshow' to improve the efficiency 2.Increase the fdb check interval to make it more stable at dualtor aa setup Change-Id: I5f9e15c69fb3eb4353fca0d504c5e14961e1f675
- Loading branch information
Showing
4 changed files
with
24 additions
and
16 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters