Now that we covered how LISP Routing works in Part 1 and Part 2 of this series, let dig into some of the things you can do with it. I would suggest you go back and read the first two posts if you are new to LISP since I am not going to cover that material again. So, lets look at three of the most popular use cases: 1) VM mobility, 2) IPv6 migration, and 3) smarter multi-homing. I am going to cover the generic use cases, then wrap with some real-world customer use cases.
Since it seems to be the hottest topic, let start with the mobility solution. From a networking perspective, there are a couple of things that are important with a live migration (ex. VMotion): we want to try and preserve TCP sessions (note: this does not mean “packets don’t get dropped”) and we want to maintain optimal routing (note to server folks: you too care about these things). We would also like global mobility—basically the server admin should be able to move her VM wherever she want and not be constrained by IP addressing considerations.
Let’s build on the scenario we have been using in the prior posts, where we have a host 192.168.1.12 is chatting with a VM 172.16.4.7. Assume that we have gone through the whole map-request/map-reply process, so we have something that looks like this:
Is your network ready to help you transform and be the strategic partner that you can be? Let’s face it… Today’s data centers are challenged with siloed resources and facilities… Limited scalability… Poor resource utilization… Growing complexity…Perhaps the biggest challenge is time. When 80% of your resources are dedicated to “keeping the lights on” and managing all what you have, there is very little time left for innovation that benefits the business.
And the reality is that the role of IT has to change – from a cost center to a business strategic partner! Why? Because there are increasing demands on IT to help your business differentiate in order to survive and grow in these rough economic conditions. And let’s not forget that the increasing cost pressures, technology changes, and the advent of game-changers like cloud are forcing IT executives to look at how to deliver IT differently.
These growing demands put even more pressure on the shoulders of IT especially given the current state of your Data Centers. The data center network sits at the core of IT and is key to how IT can deliver services and provide value back to the business.
So what do you do? The good news is that …
Tags: ASA, Cisco, cloud, Cloud Computing, Consolidation, convergence, data center, DCNM, Fabric Path, FCoE, fex, Fibre Channel, it-as-a-service, LISP, MDS, nexus, Nexus 1000v, Nexus1010, NX-OS, OTV, switch, Unified Fabric, virtualization
In this week’s episode of Engineers Unplugged, storage industry luminaries Chad Sakac (@sakacc) of EMC and Vaughn Stewart (@vstewed) of NetApp discuss the concept of Stretch Clustering, a topic they’ve been covering at tech events for awhile now. Check out their discussion here:
Welcome to Engineers Unplugged, where technologists talk to each other the way they know best, with a whiteboard. The rules are simple:
For more information on stretch clustering and all storage topics, be sure to check out Chad’s blog and Vaughn’s blog. Questions, comments, thoughts? Post them here or join the conversation with @CiscoDC on Twitter!
So, lets dig into LISP Routing a little more. If you have not done so, I would recommend you read my first post, since I am not going to review the concepts here. In this post, I am going to break things down into three steps: 1) how packets are forwarded (i.e. the data plane operation), 2) how mapping information is propagated (i.e. control plane operation), and 3) how we internetwork with non-LISP locations.
For starters, lets head into the weeds and take a look at the LISP header format. In the last post, I mentioned there is some flexibility in how handles IP addressing. The two examples below show a couple of scenarios: pure IPv4 and a IPv4/IPv6 hybrid: