-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Bgp evpn testing related to non default EVPN backbone #18358
base: master
Are you sure you want to change the base?
Conversation
ebeb641
to
8166406
Compare
ci:rerun |
|
||
tgen.gears["r2"].vtysh_cmd( | ||
""" | ||
configure terminal\n |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Drop \n chars from every line, it's not necessary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok
|
||
tgen.gears["r2"].vtysh_cmd( | ||
""" | ||
configure terminal\n |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ditto.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok
Change the test, and move the backbone evpn to a non default vrf. Signed-off-by: Philippe Guibert <[email protected]>
Add a BGP L3VPN setup with ability to import L3VPN prefixes, behind EVPN setup. Two BGP sessions are configured between R2 and R4, and are shutdown, then used at the end of the test; then filtering is applied. Signed-off-by: Philippe Guibert <[email protected]>
After creating a default BGP instance, the configuration of a VRF BGP instance used as EVPN backbone is not possible, the below error message appears: > %% Please unconfigure EVPN in default VRF Actually, at default BGP creation, the EVPN backbone is set, whereas this instance can be used for something else. Fix this by not setting too early the EVPN setup. Fixes: ("e2f3a930c54c") bgpd: Allow non-default instance to be EVPN one Signed-off-by: Philippe Guibert <[email protected]>
When setting up a RR EVPN setup on a non default BGP EVPN instance, the below error message is displayed for each received BGP update. > 2025/03/11 14:38:24.959177 BGP: [J51AF-GQ2HJ][EC 33554468] vrf import rt lookup - evpn instance not created yet > 2025/03/11 14:38:24.959188 BGP: [J51AF-GQ2HJ][EC 33554468] vrf import rt lookup - evpn instance not created yet The message is just here to inform that there is no BGP backbone defined, which is normal under a RR configuration. This message does not break anything functionally, and should be removed. Signed-off-by: Philippe Guibert <[email protected]>
48aba29
to
c5f826f
Compare
Add some more testing: