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 10.200.7.42 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 172.16.4.7 initiates traffic back to 192.168.1.12, the router 10.200.7.42 (the xTR serving 172.16.4.7) will send a solicit-map-request message to 10.10.1.1 (the xTR serving 192.168.1.12) telling it to send out a map-request message for 172.16.4.7, even thought it thinks it already has a valid RLOC for that address. 10.10.1.1 will send out a new map-request for 172.16.4.7 which results in 10.200.7.42 sending a map-reply back which then leads 10.10.1.1 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 172.16.4.7? Who’s now becoming a new gateway for that host? Do we need to configure /24 secondary address (172.16.4.1) on the router interface facing the 172.16.4.7?
2. What happens with 172.16.4.6 to 172.16.4.7 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
Moquery is the command line cousin of Vizore, it's very helpful and efficient sometimes during the troubleshooting. This article aims to provide moquery cheat sheet to the users for some most common seen scenarios.
Here is the checklist before customers/partners contact Cisco TAC:
Firmware Version of APIC and Switch
Download Switch and APIC techsupport logs
Problem description (Symptoms with details)
Business impact (eg, what kind of services...
moquery usageAPIC moquerySwitchmoquery
This document discuss a common issue observed during the VMM integration & VM workload migration to ACI fabric.
VMware Virtual machines are hosted in Cisco UCS-B seri...