Symptom
On Nexus switch, host reach-ability is affected over routed network when there is VMotion of the host, i.e. host moves from one location to other.
Example:
Host 1 was behind Leaf 1 in native VRF X. VRF X has HMM entry for host route (/32) for host 1.
VRF X Exports (attached-export) host routes to VRF Y (import)
Host 1 now moves to Leaf 5. HMM entry is deleted from Leaf 1 and now Leaf 5 has HMM entry locally.
Attached-export happens correctly on Leaf 5 from VRF X to VRF Y.
However, Leaf 1 still has the attached-export in VRF Y pointing locally to VRF X with AD (administrative distance) 190, as well as evpn export in default VRF with AD 200.
Route table keeps AD 190 preferred breaking the communication.
Broken view from Leaf 1:
# show ip route vrf vrf-Y 192.168.10.20/32
IP Route Table for VRF "vrf-Y"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%' in via output denotes VRF
192.168.10.20/32, ubest/mbest: 1/0, attached
*via 192.168.10.20%vrf-X, Vlan10, [190/0], 00:43:09, attached-export >>>>>>>> This entry should not exit on Leaf 1, rather Leaf 5.
via 10.20.1.20%default, [200/0], 00:02:04, bgp-, internal, tag (evpn) segid: tunnelid: encap: VXLAN
Conditions
VXLAN/EVPN setup with Inter-VRF routing leaking (attached-export)
Workaround
Remove/Re-add import commands from VRF Y with route-target from VRF X.
