Question:
why do you define the bgp controller with "ebgp:1" , with your route-reflector as peer,
as you use the same 65001 asn on both node && route reflector ?
ebgp:1 add " neighbor BGP remote-as external", so the peer should have a different asn.
If you need to do a simple evpn route reflector with ibgp (same asn on each proxmox node), same as, you don't even need to define a bgp controller in the sdn.
Simply create the evpn controller, add add the route reflector as peer.
The bgp controller is mainly used for 2 things:
- If you want to use ebgp (different asn for each proxmox node) for the evpn.
- if you want add an external bgp peer to a specific node. (on an exit-node for example, to forward evpn routes to a classic bgp router)
why do you define the bgp controller with "ebgp:1" , with your route-reflector as peer,
as you use the same 65001 asn on both node && route reflector ?
ebgp:1 add " neighbor BGP remote-as external", so the peer should have a different asn.
If you need to do a simple evpn route reflector with ibgp (same asn on each proxmox node), same as, you don't even need to define a bgp controller in the sdn.
Simply create the evpn controller, add add the route reflector as peer.
The bgp controller is mainly used for 2 things:
- If you want to use ebgp (different asn for each proxmox node) for the evpn.
- if you want add an external bgp peer to a specific node. (on an exit-node for example, to forward evpn routes to a classic bgp router)
Last edited: