Symptom
Sometimes EVPN Route-type 2 with MAC+IP with two labels is not accepted and IP Address not imported to IP VPN VRF.
Conditions
The IP Address is not imported to L3 VRF even though NLRI has RT EXTCOMM matching L3 VRF import RT and the NLRI has two labels.
- BGP Update message has both EVPN Route-type 2 with MAC only and MAC+IP NLRI's.
- The first NLRI in the Update message is a EVPN Route-type 2 with MAC only (without IP Address) and it is not imported to L2 VRF (bridge-domain) either because L2VRF is not configured or import of L2 VRF does not match the RT EXTCOMM of EVPN Route-type 2.
- And EVPN Route-type 2 with MAC+IP is present in the same BGP Update message.
Workaround
Have different BGP attributes for EVPN Route-type 2 with MAC and MAC+IP NLRIs, so that MAC routes and MAC+IP routes are sent in the different BGP Update message.
On Both VTSRs
prefix-set default-route-prefix-set
0.0.0.0/0 le 32
end-set
!
prefix-set default-route-v6-prefix-set
::/0 le 128
end-set
route-policy set_community_xrvr_out
set extcommunity soo vts additive
if evpn-route-type is 2 and destination in default-route-prefix-set or destination in default-route-v6-prefix-set then
pass
elseif evpn-route-type is 2 then
set community (100:9600) additive
pass
else
pass
endif
end-policy
And apply this policy to all VTSR neighbors in outbound direction:
Sample is below:
router bgp 100
neighbor 80.70.10.1
remote-as 100
update-source Loopback0
address-family l2vpn evpn
route-policy recvrt_filter_comm_xrvr_in in
encapsulation-type vxlan
route-policy set_community_xrvr_out out ===> apply policy in out direction
advertise vpnv4 unicast re-originated
advertise vpnv6 unicast re-originated
Further Problem Description
