Remote Client Communication to EID before Mobility Event
Below Figure shows the routing table on DC xTRs, on West DC there is no change in routing table, however in East Dc there is Null0 route for 10.11.11.0/24 routes installed. The reason is given below:
West Dc represents home site for 10.11.11.0/24 which is mobile subnet. And the only routes present in local xTR is /24 subnet, this can cause two immediate consequences:
XTR at local West DC will not dynamically discover workloads that are connected locally to West Site and source IP traffic in the northbound direction (as instead happens in extended subnet). But when the workload will be moved back to original site, then workload will be dynamically discovered and temporarily registered in local dynamic-eid table and with Map-Server.
Traffic when originated from remote site destined to network 10.11.11.0/24 will be sent to West DC by LISP, it will be decapsulated and routed directly to locally attached EID subnet. In this Host mobility across subnet implementation the basic principal is: communication to work load belonging to mobile subnet and connected to home site can be established even though EID prefix is not discovered dynamically