Hi.
I have an EVPN VXLAN VTEP that is advertising the following Type 1 EVPN route even though it is not a multihoming VTEP.
{master:0}[edit]
jcluser@DC2-Leaf1# run show route advertising-protocol bgp 10.255.1.1 table bgp match-prefix 1* detail
bgp.evpn.0: 7 destinations, 8 routes (7 active, 0 holddown, 0 hidden)
* 1:10.255.1.3:0::050000fc4d00003a9800::FFFF:FFFF/192 AD/ESI (1 entry, 1 announced)
BGP group OVERLAY type Internal
Route Distinguisher: 10.255.1.3:0
Route Label: 1
Nexthop: Self
Localpref: 100
AS path: [64589] I
Communities: target:64589:1111 encapsulation:vxlan(0x8) esi-label:0x0:all-active (label 0)
This is being advertised because of a local IRB interface. I know this because this route is withdrawn when I delete the IRB interface.
Below is relevant configuration. Can someone please let me know why this non-multihoming PE is advertising a Type 1 EVPN route, when only multihoming VTEPs are supposed to advertise them. Also, how is the ESI of this route computed to be 050000fc4d00003a9800?
Thanks.
{master:0}[edit]
jcluser@DC2-Leaf1# show interfaces irb
unit 150 {
proxy-macip-advertisement;
virtual-gateway-accept-data;
family inet {
address 192.168.150.1/24 {
preferred;
virtual-gateway-address 192.168.150.254;
{master:0}[edit]
jcluser@DC2-Leaf1# show switch-options
vtep-source-interface lo0.0;
route-distinguisher 10.255.1.3:1;
vrf-target {
target:64589:1111;
auto;
}
{master:0}[edit]
jcluser@DC2-Leaf1# show vlans
VNI_15000 {
vlan-id 150;
l3-interface irb.150;
vxlan {
vni 15000;
}
}
default {
vlan-id 1;
}
{master:0}[edit]
jcluser@DC2-Leaf1# show protocols evpn
encapsulation vxlan;
default-gateway no-gateway-community;
extended-vni-list all;