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).
Q: How is Nexus 1000V InterCloud different from the Nexus 1000V virtual switch?
A: Nexus 1000V is a virtual switch deployed to achieve physical Nexus switching and operational consistency for virtualized environments. Nexus 1000V InterCloud extends that virtual network infrastructure to cloud providers in a seamless and secure way, even allowing for VM and policy migration across the resulting hybrid cloud. As virtual machines are instantiated in the VPC, the operational model is exactly the same.
So, you do not need to replace, upgrade, augment or otherwise mess with your existing Nexus 1000V virtual switches that are happily supporting your data center today. In fact, Nexus 1000V InterCloud, despite the name, will support most virtual networking infrastructures, even if there are no Nexus 1000V virtual switches present. You may be using VMware’s vSwitch (and Microsoft’s Hyper-V switch in future). You can still extend that virtual network to the cloud through Nexus 1000V InterCloud.
Q: What components are included in Nexus 1000V InterCloud?
A: Two of the major components are: 1) the secure, encrypted communications channel that creates the InterCloud Link from the enterprise to the cloud provider, plus an overlay InterCloud Switch in the VPC (provider cloud), and 2) the new VNMC InterCloud management platform that provides a single view of the enterprise and cloud resources and provisions network services consistently across sites. While not formally part of Nexus 1000V InterCloud product bundle, the whole resulting hybrid cloud environment will also support virtual services in a phased manner, like Virtual Security Gateway (VSG), ASA 1000V Cloud Firewall, virtual Prime NAM, virtual WAAS, as well as ecosystem services. All of the familiar features of Nexus 1000V switches are available in the InterCloud Switch – VLANs, security ACL’s, QoS, as well as the vPath service insertion and chaining architecture integrated with VSG, ASA 1000V and vWAAS.
Q: How complex is it to manage the integrated hybrid cloud environment and what tools does Cisco provide or include with Nexus 1000V InterCloud?
A: One of the strengths of this new hybrid cloud solution is the ability to get a single view of the multiple hybrid cloud sites and manage VM mobility and cloud network service policies as easily as has been done within a single enterprise data center or private cloud. The management platform, Cisco Virtual Network Management Center (VNMC) InterCloud offers new capabilities including:
- A single management console for network services across both private and public domains.
- The ability to manage virtual machine lifecycle and mobility along with service assurance for awareness of problems before they affect access to your data.
- A northbound API for integration with management systems including Cisco Intelligent Automation for Cloud.
VNMC InterCloud accomplishes this by integrating into enterprise VM management tools (e.g. VMware vCenter and, in the future, Microsoft SCVMM), and cloud provider APIs (e.g., Amazon AWS APIs, and in the future APIs of other cloud providers).
Q: How is the Nexus 1000V InterCloud unique of different from existing hybrid cloud solutions?
A: The following aspects of Nexus 1000V InterCloud give it unique advantages compared to other hybrid cloud solutions:
- Security: It provides enterprise-grade encryption across the private and provider clouds, as well as within cloud providers (within a tenant’s VPC). It also supports VM-to-VM firewalling for VMs across the hybrid cloud as well as within the VPC.
- Simplicity: By creating a Layer-2 VPC network, Nexus 1000V InterCloud enables applications to migrate transparently – without changing their network properties such as IP addresses, VLANs/subnets, ACLs, etc. Also, with VNMC InterCloud, there is no need to jump between multiple management consoles to manage the hybrid cloud.
- Flexibility: The solution is architected to support multiple cloud providers, and is designed to work with hypervisors and virtual switches from multiple vendors across the enterprise and provider clouds.
- Consistency: For customers using Cisco networking infrastructure, Nexus 1000V InterCloud preserves the customers’ networking environment in the hybrid cloud, for example: Nexus switching, IOS routing (via CSR 1000V), VSG/ASA firewalling, WAAS-based WAN optimization, NAM-based monitoring. Customers can apply policies consistently regardless of the location of the workload.
Thus Nexus 1000V InterCloud truly creates a virtual data center in provider cloud having characteristics and posture very similar to those established for enterprise cloud workloads. Having such extensive consistency also helps reduce operational cost, as no new training and knowledge is required for operations teams.
Q: Nexus 1000V InterCloud includes Layer-2 network extension capability, much like Cisco’s Overlay Transport Virtualization (OTV) technology? Are they functionally the same, or are both needed?
A: There are a lot of similarities and, yes, both solve the problem of layer 2 extension over a multi-site cloud network. However, OTV is suitable for extending data center networks while InterCloud is suitable for hybrid clouds (including where administrative domains are different). OTV supports both physical and virtual applications, whereas InterCloud is primarily for virtual workloads. InterCloud also has additional features in support of hybrid clouds, such as a fully encrypted connection and is managed through VNMC InterCloud, which integrates with VM management tools and cloud orchestration applications.
Q: Does my cloud provider have to do something in order for me to use the Nexus 1000V InterCloud?
A: If Nexus 1000V InterCloud already integrates with your cloud service provider, then there is not much you need to do. You will be able to instantiate hybrid clouds and VPC’s yourself, or subscribe to the managed hybrid cloud service offered by your service provider(s). We are working with multiple service providers so please stay tuned for future announcements.
Q: How is the Nexus 1000V InterCloud licensed and deployed?
A: Nexus 1000V components are software deployed as virtual machines. It is architected to provide complete deployment flexibility. Enterprise customers can purchase it as a product and deploy it on their own. Service provider customers can offer this as a service in a variety of ways: a new service for their managed/hosted customers, as well as a managed hybrid cloud services (i.e., managed VPC services) to any customer.
Q: What’s the capital of Mongolia?
A: Ulan Bator (you almost had me that one!)
So, we hope that clarifies a majority of the outstanding questions that this week’s Nexus 1000V InterCloud generated. We are getting a lot of positive feedback from folks interested in hybrid cloud and the promise that this seamless and automatic degree of integration holds for customers. If you have any more questions, we’d be happy to hear them. You can always send questions (via email) to email@example.com, via twitter to @Official_1000V, or just drop us a comment in the form below.
I just tried to email firstname.lastname@example.org and it bounced back…
I do still have a couple questions after reading through the 3 blog posts.
1. I think I’ve been able to deduce that currently the 1000v InterCloud works with VMware vCenter, Nexus 1000v, VMware vSwitch and Amazon EC2. As far as I could tell anything else is a future consideration, is that correct? (e.g. Terremark cloud services).
2. I’m still struggling to grasp which components are necessary to install into an environment to make this work. When I try to navigate Cisco downloads I end up staring at the Nexus1000v.4.2.1.SV2.1.1a.zip which doesn’t seem like the right software since you say that the Nexus 1000v is not a required component of the Nexus 1000v InterCloud.
-Is the software available to download at this point?
-Is it just a licensed feature of the existing Nexus 1000v?
3. Same thing for VNMC-InterCloud software, I can’t find it.
Thanks in advance for your help!
Sorry about the trouble with the email address, but I just checked it and it appears to be working fine…
Bear in mind that Nexus 1000V InterCloud is not shipping just yet, but will next quarter. So this should clear up your confusion about not figuring out how to download it just yet (same with VNMC). Stay tuned for more details.
You are basically correct in #1, but by the time we FCS the product, we will be able to support more cloud service providers, although I can’t enumerate them at this time. But Terremark is an excellent example of the type of cloud provider we hope to support soon.
Thanks for the follow up Gary. I’ll be sure to keep my eyes open for the software release and any further information on the product. In the mean time, if there is any futher recommended reading, I’d love to see it.
FYI, I just tried the email address agian and got this response immediately:
The following organization rejected your message: rcdn-inbound-a.cisco.com.
Comments are closed.