Replies: 1 comment
-
All the evpn bundle logic is tied to the tenants (build for each tenant), so there is no simple fix for this. Please submit an enhancement request detailing the scenario you would like to use. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a setup where all VLANs for one VAB/Tenant are loaded from an IPAM.
for now, all my VRF's were also under the same tenant, but for flexibility, I want to split my VRF en VLANs in multiple tenants.
so I have tenant VAB, VRF1, VRF2; where tenant VAB contains all vlans used (also the SVI vlans).
In the VRF1, VRF2 tenant, I set the evpn_vlan_bundle on the SVI, so that we use the correct VLAN with the only_vlans_in_use knob.
What I now get is the error "Found duplicate objects with conflicting data while generating configuration for BGP VLAN-Aware Bundles defined under network services."
{'name': 'VAB', 'vlan': '1865'} conflicts with {'name': 'VAB', 'vlan': '1505,1515-1516,1572,1576,1581,1596,1865' }
The first one comes from my 'VRF' tenant, and the rest from the VLAN's imported from the IPAM.
I would have expected that vlans linked to the same VAB would have been merged in one list, and not create to different lists.
Is this something that could be addresses in the code, or are there better ways to do this.
Beta Was this translation helpful? Give feedback.
All reactions