-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[fast-reboot] FDB entries are not restored on fast-reboot #5216
[fast-reboot] FDB entries are not restored on fast-reboot #5216
Comments
@stepanblyschak Thanks for reporting this issue. can you please post the content of arp.json? |
The script filter FDB entries based on the contents of arp.json file and not based on |
@tahmed-dev Sending the repro also with arp.json content:
The issue #5217 is different. As you can see arp.json has the necessary entry, but after reboot in #5217 those entry are not configured on HW before ports become operationally up. |
Thanks @stepanblyschak can you please link those files to the issue:
|
@tahmed-dev Done |
sonic_dump_arc-switch1004_20201013_124814.tar.gz Reopening as the issue reproduced. Attached new system dump. |
I see in the log file the following signature:
which seem related to issue:5580 |
Opened wrong issue by a mistake, The comments is related to #5217 |
Description
FDB entries are not restored on fast-reboot. This issues causes traffic to flood for a long period of time till all FDB entries are re-learned. The original fast-reboot design is to save FDB entries to a file and add them on HW in fast-boot ASAP, instead of waiting for learning.
Steps to reproduce the issue:
Describe the results you received:
Flooding for a long period of time after fast-reboot when data plane comes back.
Describe the results you expected:
There should be no flooding when switch is fast-rebooted, FDB entries known prior to reboot have to be restored in the HW ASAP instead of waiting for learning to happen.
Additional information you deem important (e.g. issue happens only occasionally):
The issue is most probably caused by filter_fdb_entries.py added in sonic-net/sonic-utilities#890, a simple reproduction without running full fast-reboot flow:
arp.json.txt
fdb.json.txt
config_db.json.txt
The text was updated successfully, but these errors were encountered: