Skip to content
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

Create a separate MLAG BGP peer group for overlay tenants #4825

Open
1 task done
ksantos01 opened this issue Dec 17, 2024 · 0 comments
Open
1 task done

Create a separate MLAG BGP peer group for overlay tenants #4825

ksantos01 opened this issue Dec 17, 2024 · 0 comments
Labels
type: enhancement New feature or request

Comments

@ksantos01
Copy link

Enhancement summary

Currently MLAG-IPv4-UNDERLAY-PEER peer group is used for the iBGP session between MLAG pair in the underlay and overlay. This approach can be misleading due to the use of UNDERLAY word in the peer group name

The following is an example of the MLAG-IPv4-UNDERLAY-PEER being used in an overlay tenant

router bgp xxxx
   neighbor MLAG-IPv4-UNDERLAY-PEER peer group
   neighbor MLAG-IPv4-UNDERLAY-PEER remote-as 65000.1
   neighbor MLAG-IPv4-UNDERLAY-PEER next-hop-self
   neighbor MLAG-IPv4-UNDERLAY-PEER description DC1-CL1
   neighbor MLAG-IPv4-UNDERLAY-PEER password 7 xxxx
   neighbor MLAG-IPv4-UNDERLAY-PEER send-community
   neighbor MLAG-IPv4-UNDERLAY-PEER maximum-routes 12000
   neighbor MLAG-IPv4-UNDERLAY-PEER route-map RM-MLAG-PEER-IN in

   address-family ipv4
      neighbor MLAG-IPv4-UNDERLAY-PEER activate

   vrf BLUE
      rd 192.168.100.1:1002
      route-target import evpn 1002:1002
      route-target export evpn 1002:1002
      router-id 192.168.100.1
      neighbor 172.16.1.1 peer group MLAG-IPv4-UNDERLAY-PEER
      redistribute connected

Which component of AVD is impacted

eos_designs

Use case example

please detail your use case

Describe the solution you would like

Overlay tenants should have its own dedicated MLAG peer group

router bgp xxx
   neighbor MLAG-IPv4-OVERLAY-PEER peer group
   neighbor MLAG-IPv4-OVERLAY-PEER remote-as 65000.1
   neighbor MLAG-IPv4-OVERLAY-PEER next-hop-self
   neighbor MLAG-IPv4-OVERLAY-PEER description DC1-CL1
   neighbor MLAG-IPv4-OVERLAY-PEER password 7 xxxx
   neighbor MLAG-IPv4-OVERLAY-PEER send-community
   neighbor MLAG-IPv4-OVERLAY-PEER maximum-routes 12000
   neighbor MLAG-IPv4-OVERLAY-PEER route-map RM-MLAG-PEER-IN in

   address-family ipv4
      neighbor MLAG-IPv4-OVERLAY-PEER activate

   vrf BLUE
      rd 192.168.100.1:1002
      route-target import evpn 1002:1002
      route-target export evpn 1002:1002
      router-id 192.168.100.1
      neighbor 172.16.1.1 peer group MLAG-IPv4-OVERLAY-PEER
      redistribute connected

Describe alternatives you have considered

No response

Additional context

No response

Contributing Guide

  • I agree to follow this project's Code of Conduct
@ksantos01 ksantos01 added the type: enhancement New feature or request label Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant