It’s been a very big year for Nexus 1000V so far, with the introduction of Nexus 1000V InterCloud, and our reaching a key milestone of 7,000 virtual switch customers. The Nexus 1000V also continues to play an important role in our Cisco ONE portfolio for Software Defined Networking (SDN). Now, as we get closer to the GA of the Nexus 1000V virtual switch on Hyper-V, customers are looking for the detailed, hands-on information about integrating Cisco virtual networking into their Microsoft Windows Server infrastructures.
By integrating the Nexus 1000V virtual infrastructure into System Center, customers will be able to manage their virtual networks along with the rest of their cloud infrastructure, including compute and storage resources. SCVMM promises to help organizations build out and manage their private clouds, improve processes by automating workflows for standard tasks, and provide visibility to virtual applications across hybrid cloud locations.
Damian and the rest of the Nexus 1000V product management team will be providing more details on the benefits of Cisco virtual networking for Microsoft data center environments.
For the latest information on Cisco’s partnership with Microsoft and our virtual network infrastructure products for Windows 2012 and Hyper-V, you can go to http://cisco.com/go/microsoft
There’s been a great deal of excitement, interest and certainly follow-on questions after we announced our new hybrid cloud integration solution, Nexus 1000V InterCloud. My earlier three-part blog consisted of Part 1 on the architecture and features, Part 2 on the hybrid cloud management specifics, and Part 3 a recap of the frequently asked questions.
And now, we have the video demonstration. At Cisco live! last month in London, TechWise TV‘s Robb Boyd caught up with Prashant Gandhi, Sr. Director of Product Management in our Server Access and Virtualization Business Unit, before the trade show floor opened and recorded a demonstration of the new hybrid cloud infrastructure.
In this demo, Prashant quickly migrates a few virtual machines from our simulated private cloud to Amazon Web Services hosting servers. Part of the ease of use is through integration of Cisco’s Virtual Network Management Center (VNMC) InterCloud to Amazon cloud management tools, and the ability to view and manage virtual machines in both the private data center as well as those hosted in the cloud. The other important point about Nexus 1000V InterCloud is not only how it provides all the seamless layer 2 connectivity and security to connect the data center to public cloud resources quickly and easily, but security and application policies can be mirrored and migrated just as easily in the public cloud through the use and deployment of Cisco Cloud Network Services, such as our Virtual Security Gateway, the ASA 1000V Cloud Firewall or vWAAS. Take it away Robb and Prashant…
Cisco continues to roll out innovations that will enable the next generations of multi-cloud computing. I’m a product manager working on Cisco’s Cloud Management software, and we’re all about the high-level, self-service, automatic provisioning of services that the end-user cares about. The network just moves ones and zeros, and all protocols of interest (HTTP, SSH, RDP, SQL, etc.) work fine over TCP/IP. The hypervisor takes care of putting that pesky motherboard chipset and storage bus into a black box, right? The end-user doesn’t care about that stuff, or at least doesn’t want to have to care about it.
A common perspective, except among the engineers who manage the network, is that network infrastructure is a bunch of mysterious plumbing that “just works” and how it does what it does doesn’t matter. Indeed, many vendors in the “cloud” arena would like to perpetuate this perspective on the network. They would like you to believe a bunch of dumb pipes can carry traffic and that determination of the traffic (content, flow, etc.) is determined at higher levels in the stack.
In some cases, this is true, but operating this way doesn’t unlock anything new. The model they describe would be brilliant if all of your network requirements were defined in 1998. Few companies can afford to operate technology today like they did in 1998 and remain competitive.
Cisco is announcing a newNexus 1000V(N1KV), and this one changes the game.In brief, the Nexus 1000V is the foundation of the networking services that Cisco brings to virtual computing. The N1KV can be managed using the same NX-OS commands and practices used to manage the Nexus 5K and 7K switches, and extends network control down to the VM and virtual port into which a VM is “plugged in”, even across different vendors’ hypervisors.
The N1KV is also the platform for additional L2 and L3 network services such as those provided by the vASA Firewall, vNAM, and VSG. The new Nexus 1000V InterCloud extends this ability to cloud service providers, such as Amazon, but is “cross-provider” (in fact, it doesn’t even depend on the Cloud Service Provider). For me, in my role as a Cloud Product Manager, this is an important new addition to basic networking capabilities, and is exactly the kind of thing that Cisco can and should do in its role as “Networking Giant” to open up the promise of hybrid or multi-cloud.
I have a mental image of what this can do, and I tried to put this into images to the right. Animation would have been better, I just don’t have the Flash skills to put it together for a quick blog post. I envision a virtual machine as a ghostly “physical” server tower with network cables plugged into it. These network connections can come from end-users in a client-server model, or any of our web-and-mobile constructs. After all, we still are end-users connecting to machines. Of course, the “client” for a compute function could be another compute function, so there is a network cable coming from another nearby ghost server. These ghost servers can today float from blade to blade thanks to most mainstream virtual machine managers (VMM) and a virtual switch like the N1KV, and the cords stay connected throughout. With the new N1KV, that VM can float right out of that VMM and into another VMM (such as across VMware datacenters, or even from VMware to Hyper-V), or out to a public or hosted provider. The cord just magically uncoils to remain connected wherever that machine goes! I love magic.
The N1KV provides that cable that can float after its ethereal virtual machine. It also provides the platform to maintain monitoring by the vNAM, even as the machine moves. You simply can’t economically achieve this using basic dumb pipes. Add to this the new Virtual Network Management Console (VNMC) InterCloud management capabilities. In order for that cord to stay connected, there do have to be network switches or routers along the way that understand how to make that network cable follow the machine. VNMC InterCloud manages these devices, but adds another particularly important capability: actually moving the workload.
VNMC InterCloud adds the ability to discover virtual machines, and convert them to a cloud-provider’s instance format, move what could possibly be a fairly large set of files, and get that machine started back up in a far-away environment, with seamless network consistency. VNMC InterCloud is like a puff of wind that pushes the ghostly VM from my corporate VMWare-based cloud to float over to my hosted private cloud. Remember, ghosts can float through walls.
This is groundbreaking. Workload mobility is one of those hard-to-do core capabilities required for all of us to realize the promise of multi-cloud, and it requires a network that is both dynamic and very high performing. I’ve been looking forward to this from Cisco for some time now.
We had some sneak peeks at CiscoLive in London but as you probably know by now, this stuff was just formally announced last week. Several demos worth looking at give you the foundation for what is important. Shashi Kiran is leading this effort and you can always count on a good quote:
“Cisco takes Unified Fabric to the next level delivering compelling customer value in an evolutionary manner, we offer a switch with the industry’s highest 40GbE density per rack unit, the simplest solution for the hybrid cloud model, and the most extensible network controller.”
Interesting….tell us more…
Three areas of innovation: How we Scale (Nexus 6000), how we enable the Hybrid deployment model (Nexus 1000v InterCloud) and how we open it all up with Cisco ONE (Open Networking Environment)
Today we wrap up our three part introduction of Cisco’s new hybrid cloud infrastructure, Nexus 1000V InterCloud. In Part 1, we provided an overview of the architecture and the components that make up Nexus 1000V InterCloud. In Part 2, we looked a bit more closely into the single pane management of the cloud network and resources across the on-premises private cloud and the cloud service provider. In Part 3, we’ll answer some of the most frequently asked questions we’ve been getting from customers, analysts and the press in the early stages of this announcement.
Q: What is Nexus 1000V InterCloud? What part of the hybrid cloud infrastructure does it comprise? Is it software, hardware, some combination of both? Is it a switch, a server or an application?
A: Nexus 1000V InterCloud is a set of software components that run as virtual machines on a variety of servers. It forms the infrastructure that extendss your existing on-premises virtual network and virtual services to cloud providers in a seamless and secure manner. It provides all the infrastructure and protocols to support VM migration from the data center to the cloud provider. Effectively, Nexus 1000V InterCloud (with VNMC InterCloud management software) creates a secure, on-demand layer-2 virtual private cloud (VPC).