I was looking at some different options for getting rid of the current layer 2 extension that exists today in a network, and two options I've been mulling over are redistribute neighbor and RoH. RoH is going to be a little challenging for us, since it's still a heavy Windows environment and Windows isn't supporting unnumbered presently (I think.)
The second option I was looking at was redistribute neighbor. This appeared to be a slightly more attractive environment with potentially more flexibility for the current situation of Windows hosts, but I had some specific questions around the implementation of it:
The discovery mechanism in LISP ESM is pretty close to redistribute neighbor. In my experience, ESM has typically struggled with discovery of things like load balancer VIPs, SQL cluster IPs, secondary IPs on servers that may not speak unless spoken to. Is there a way to work around this with the current iteration of redistribute neighbor? If not, any plans to do something like offer the ability to tether the address/MAC to a particular leaf and propagate that throughout the fabric? Just a spitball there, but I'm trying to get to the bottom of potential issues with discovery since I'm seriously considering the solution.