Hey folks--this is the second of three posts looking a little more closely at VXLAN. If you missed the first post, you can find it here. In this installment we are going to look at the some of the other options out there. Two of the most common questions we see are “why do I need yet another protocol?” and “can I now get rid of X?” This should help you answer these questions.So, let’s dig in… Read More »
Today’s IT organizations face a broad set of challenges today.
- How to deal with the proliferation of end-user devices? (smartphones, tablets, etc.)
- How to deal with the proliferation of virtualization and it’s new operational model?
- How to adapt to requirement for new application traffic patterns (east-west, VM mobility)?
- How to manage the edges of their networks as work/life locations blur?
- When do they decide to deliver a business need via internal resources vs. external resources?
- With all this technology change happening so rapidly, how do they align their teams?
What if your mobile device allowed you the freedom to seamlessly roam across any network in the world, regardless of location or operator and with all the attributes you would expect, security or privacy… With LISPmob, we may have gotten a giant step closer as we open sourced a network stack for network mobility on Linux platforms, an implementation of basic LISP mobile node functionalities.
This is the Locator Identifier Separation Protocol, which supports the separation of the IPv4 and IPv6 address space following a network-based map-and-encapsulate scheme based on an IETF open standard.
We hope this will be a project and a community many will find not just interesting and vibrant, but necessary and fun to engage, collaborate and contribute.
How will this help your plans to deal with all these amazing possibilities of mobile access to an ever-growing Internet?
With the opening of the new Cisco Datacenter in RTP, I thought it would be cool to reach out to a few of the guys responsible for the design and ask them a few questions. So, I got together with Jag Kahlon (Cisco IT Architect) and John Banner (Cisco IT Network Engineer) for a quick chat.
Me: What were the primary objectives for the new datacenter?
So, the recent VXLAN announcement we made with some of our partners (including VMware, Citrix, and RedHat) certainly generated a lot of questions.
So let me cover some of the most common ones I have heard.
Why do we need a new protocol? We already have VLANs, MPLS, OTV, LISP and a whole host of other acronyms to contend with!