Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 
Community Member

Calling LISP fans... if the're any :-)

Hello guys!
I was wondering is this the right place to ask my questions, but thought should be fine.

As I am a newbie to the LISP world, I’ve been reading a lot about it recently, but really got stuck on some fundamental bits & pieces.

Being reading this article I got really confused about this part:

“Once notices it has a new server to take care of, it installs a specific /32 address in its routing table and registers the /32 address with a map-register message with the map server. Now if initiates traffic back to, the router (the xTR serving will send a solicit-map-request message to (the xTR serving telling it to send out a map-request message for, even thought it thinks it already has a valid RLOC for that address. will send out a new map-request for which results in sending a map-reply back which then leads to install the /32 EID/RLOC info in its map cache..”

My questions here:

1. What happens with traditional/fundamental rules of IP routing when we move Who’s now becoming a new gateway for that host? Do we need to configure /24 secondary address ( on the router interface facing the

2. What happens with to communication here? If we are stretching VLANs using OTC/MPLS/Pure Ethernet – that should be fine (but this is not the LISP case), but if don’t do that? Do we use some kind of proxy-arp mechanism to forward communication between EIDs?

3. In LISP world – how do we authenticate ITR mappings? I mean, how are we authorize router X to be ETR for specific prefix? With traditional IP routing that’s achieved using RIPE database and route objects (bind to AS).

I have quite a few more questions, but these should be good start! Thank you so much in advance and sorry if those sound too lame

Everyone's tags (1)
Community Member

Calling LISP fans... if the're any :-)


1. The feature is called "VM Mobility with an extended Subnet". For your first question - the answer is:  (Chapter 4 in this document)

2. The feature is called "VM Mobility accross subnets" (Same paper, Chapter 5).

3. Check this video. You'll find your answer at 46:30



CreatePlease to create content