-
Notifications
You must be signed in to change notification settings - Fork 544
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
Warmboot Vlan neigh restore fix #1040
Conversation
retest this please |
2 similar comments
retest this please |
retest this please |
* Send arp request after first Vlan member port is added * Add wait logic after Vlan member add, nbrmgr to wait for restore complete * Address comment to pass db as a parameter and open only once
nbrmgrd waits restore neighbors for 120s in normal startup? isNeighRestoreDone true only if really do restore. I found VS tests about neighbor/nexthop (vrf new cases) failed because nbrmgrd cannot work. |
In normal startup, there is no wait as warmboot flag is disabled and the isNeighRestoreDone flag would be set without any wait. can you provide any logs that nbrmgrd is stuck in VS? |
nbrmgrd is stuck in VS because:
|
1. Setup pipeline without manual effort when checkout new release branch. 2. Use correct branch when downloading artifacts or checkout relative repos. 3. Clear downloaded artifacts to avoid using outdated dependencies. 4. Use commonlib pipeline to download libnl3 and libyang instead of vs image build, to increase success rate. 5. Add weekly build to keep artifacts remaining.
What I did
During Warmboot, the restore_neighbor script sends out ARP/NS for Vlan interfaces based on oper status. Since Vlan interface is bound to bridge, it is up by default. Modified to wait for Vlan members to be added.
Logger is changed to syslog for getting correct timestamps for events
Nbrmgrd push to kernel must happen only after warmboot neighbor restoration
Why I did it
To fix neigh restore issue for Vlans
How I verified it
Details if related