-
Notifications
You must be signed in to change notification settings - Fork 439
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
Parsing some l2vpn-evpn messages causes session flap #1195
Comments
Please provide enough information for me to help. Output of the full log using exabgp -d. |
The full log file would be quite large since there are over 100k evpn routes being received. Would it help to capture the single raw message that causes this issue? Also, the full log file would expose sensitive information about the production network |
When using -d the logs contain the exchanged open messages and shared updates. The lines with the opens and way down the update before the crash is what I would need. |
Also please check with the main branch as this is where I will fix it. |
Thanks. Perhaps this log has this information. At least there is one working decode before the crash. |
Any change getting this fix merged on 4.2 release? |
@ottorei I could backport but no one confirmed that the change worked as expected. |
I'll patch my local instance and try it later this week. |
With version 4.2.21 peering with Juniper MX router as a route reflector client with family l2vpn-evpn, the BGP-session seems to constantly flap. Attachment contains the last errors being logged on ExaBGP side.
[exa-errors.txt]
The text was updated successfully, but these errors were encountered: