The evolution of the applications environment is creating new demands on IT and in the data center. Broad adoption of scale-out application architectures (i.e. big data), workload virtualization and cloud deployments are demanding greater scalability across the fabric. The increase in east/west (i.e. server-to-server) traffic along with the higher adoption of 10GbE in the server access layer is driving higher bandwidth requirements in the upstream links.
Following up on the introduction of 40GE/100GE on the Nexus 7000 Series, today we unveil the new Nexus 6000 Series, expanding Cisco’s Unified Fabric data center switching portfolio in order to provide greater deployment flexibility through higher density and scalability in an energy efficient form factor.
The Cisco Nexus 6000 Series is industry’s highest density full-featured Layer 2 / Layer 3 40 Gigabit data center fixed switch with Ethernet and Fiber Channel over Ethernet (FCoE) – an industry first!In addition to high scalability, Nexus 6000 Series offers operational efficiency, superior visibility and agility.
Some say “Nexus 6000 Series is a red carpet platform that will turn heads”. We agree! It’s because of …
Previously I talked about the growing demands and how the role of IT has to change from a cost center to a business strategic partner. And we also looked at the journey you need to take to deliver IT as a Service. Cloud computing is part of this journey and it is happening – and I mean all types of Clouds – Private, Public and Hybrid. In other words, we are entering the World of Many Clouds. Forrester Research recently published a report that concluded, “Cloud computing is ready for the enterprise… but many enterprises aren’t ready for the cloud.”1 Yet cloud deployments are happening, driven by workload virtualization and changes in application architecture and usage.
Take a look at this short video with Paul Perez (VP/GM of Unified Computing System and CTO of Data Center Group) and me. Paul shares his insights on the trends of how Cloud is changing the way of the IT and the challenges you will be facing.
Guess what? Once again Cisco is here to help you on your journey to the World of Many Clouds. How you ask?
Previously I talked about the growing demands and how the role of IT has to change from a cost center to a business strategic partner. It’s important to acknowledge that getting an organization to the point where it can implement IT as a Service isn’t easy, nor does it take place all at once. Every customer has their own journey and different customers will take different journeys. For some, it’s all about doing what they do now, only more efficiently or perhaps adding new capabilities. For others, it’s about making that full-blown transformation to service-driven IT.
So how do you get there? Each phase expands into a series of key initiatives…
It all starts with moving into more of a unified architecture of network fabric and corresponding operations.
The TechWiseTV Fundamentals series continues to enjoy a great run -- this concept of character animation and tight scripting we started with back in the early TrustSec and EnergyWise days, is still a complete joy to work on. We have learned a ton about getting the scripts tighter, writing to support visuals, how to stay technical and not try to say too much AND all the work that goes into storyboarding the visuals, working with artists and motion graphic experts. There was an element, however, we had never considered before -- in my mind perhaps because I thought it was furthest from our capability.
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: