Cisco Blogs


Cisco Blog > SP360: Service Provider

Introduction of Big Thinkers in Small Cells

Over the past five years, the adoption of small cells has increased dramatically. At Mobile World Congress (MWC) this year the Small Cell Forum announced that we have now crossed the threshold where there are more small cells deployed than macro cells in the world. Clearly, small cells are playing, and will continue to play a critical role in the global mobile infrastructure.

Over the last 18 months Cisco has doubled-down on its investments in small cells, from dramatic growth and scaling of our Service Provider Wi-Fi solution to our recently announced intent to acquire licensed small cell leader Ubiquisys.  With this opportunity, Cisco has a responsibility to address the challenges we face in small cell deployments. How do we help mobile and cable operators around the world address the issue of cost effective coverage and capacity using small cells?  How do we work with the small cell ecosystem, including mobile partners and thought leaders in this industry, to create successful, and profitable, deployments of small cells by operators around the world? How do we work with enterprise organizations to deploy small cells? Read More »

Tags: , , , , , , , , , ,

Why You’ll Want LISP Routing – Part 3

November 19, 2012 at 12:03 am PST

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.

VM Mobility

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:

Read More »

Tags: , , , , , ,