There’s been a lot of news and momentum surrounding VXLAN technology in the last several months, and there is no doubt that VXLAN is becoming a more strategic and pervasive technology across cloud networks as a result. When we rolled out VXLAN about two years ago with the first commercial implementation as part of our Nexus 1000V virtual switch, VXLAN was solely a virtual networking construct and had real constraints in how it could be extended to physical networks and devices. It was also restricted to overlay networks using our Nexus 1000V switch (or other virtual switches supporting the VXLAN overlay protocol).
Now, however, VXLAN is being supported broadly across Cisco networking platforms and devices, across multiple Cisco fabric architectures, and we are even seeing broader support from other vendor ecosystems and non-Cisco switching platforms. Cisco is continuing to expand its support for VXLAN onto the new Nexus 5600 Series switches, as well as Nexus 7700 Series using the F3 line card.
For those of you not fully up to speed on VXLAN, VXLAN stands for Virtual eXtensible Local Area Network, and started out as vastly more scalable Layer 2 LAN and tenant isolation construct for data center and cloud networks. Where cloud networks were running out of only 4000+ VLAN IDs to segment application networks, VXLAN gave them over 16 Million logical network segments.
The Cisco Prime Network Services Controller team is pleased to announce the availability of 3.2 release. This release incorporates a number of new features and functionalities to build virtual data centers (VDCs) with various network topologies. Follow this link to download the software and documentation.
Designed for multi-tenant cloud deployments, Cisco Prime Network Services Controller offers scalable, and automation-centric management for virtualized data center and cloud environments. The Cisco Prime Network Services Controller is a virtual appliance that provides centralized device and policy management of virtual networking services. It provides a unified northbound API (XML payload over HTTPS) to allow the creation of dynamic data center that includes switching, routing, fire-walling and load-balancing functions.
Cisco Prime Network Services Controller is built on an information-model architecture in which each managed device is represented by its subcomponents (or objects), which are parametrically defined. It also uses Services profiles for model-based configuration of virtual devices policies. A service profile is a collection of device policies and configuration templates that can be predefined and applied on demand at the time of virtual appliance instantiation or later. Cisco Prime Network Services Controller enables
Flexible and simple mechanism to managing virtualized infrastructure using Cisco VSG, Cisco ASA 1000V, Cisco CSR 1000V virtual services as well as Citrix’s NetScaler virtual load balancers (NetScaler VPX and NetScaler 1000V)
Cisco InterCloud for virtual machine (VM) workload management and migration between the enterprise data center (private cloud) and public clouds
Cisco VSG, Cisco ASA 1000V, Cisco CSR 1000V, NetScaler VPX and NetScaler 1000V services in Dynamic Fabric Automation (DFA) solution
The Microsoft ecosystem continues to be an important area of focus with our Cisco Datacenter product and solution teams. UCS, Nexus, UCS Management, and ACI teams have continued to innovate and launch new offerings during the past few months. Let’s take a look at our recent happenings and launches that can help enable your organization to deliver an optimal datacenter environment for your Microsoft platforms:
1. PASS, Microsoft SQL Server, and Cisco’s Unified Datacenter…
We’ve ramped up our focus on Microsoft’s SQL Server platform! Investments in PASS (Professional Association of SQL Server), Pass Summit 2013, and the PASS Virtualization Chapter afford us the opportunity to educate this world-wide BI and Data Management audience on UCS, Nexus, FlexPod, and VSPEX. Stay tuned for more from us, too as Microsoft gets closer to shipping their SQL Server 2014 platform.
2. Cisco and the Microsoft Cloud OS Launch…
Occurring around the world during the November 2013 to January 2014 timeframe is Microsoft’s Cloud OS launch – the coming out party for Windows Server 2012 R2 as well as System Center 2012 R2. Cisco will be a local sponsor at many of these events – in fact as of this writing we have wrapped up our participation at multiple events in Canada, Germany, and South Africa. Please stop by your local Microsoft Cloud OS event and visit the Cisco booth to learn more as well as listen to Cisco’s Chief Technology & Strategy Officer Padmasree Warrior on our Microsoft alliance and datacenter solutions.
3. Cisco, Microsoft, and the Application Centric Infrastructure (ACI)…
Microsoft was a key strategic partner at our recent New York City ACI launch with strong support from key Microsoft leaders such as Satya Nadella, Executive Vice President of their Cloud and Enterprise business unit. Satya shared the stage with Cisco CEO John Chambers in announcing ACI to the public. In addition, Microsoft’s Brad Anderson, Corporate Vice President, System Center blogged on the event and created a video on his ACI thoughts. Microsoft -- with their key platforms of Exchange, SQL Server, and SharePoint – sees ACI as a way to deliver ‘…datacenter without boundaries for our customers…’
Following our launch of the Cisco Application Centric Infrastructure (ACI), we continue with our series exploring in more detail key aspects of the ACI policy model and partner ecosystem. In Part 1 of my series on ACI, we looked at why application policies were an ideal model to build infrastructure automation around, and how application policies are better suited to mirror business objectives and requirements than traditional IT infrastructure policies. The key benefits for customers end up being vastly greater degrees of automation, process improvement and business agility.
In Part 2, we looked into one example of the difficulty in deploying and managing applications and the level of complexity that must be overcome to truly automate application-oriented tasks: application-specific network services and security policies (as well as a separate post on the partner ecosystem for application services and security solutions that support the ACI model).
What ACI has done is backed off from all the network complexity in trying to build more and more intelligence directly in the fabric. Building the network to be externally automated can centralize the intelligence and control, while simplifying the design and operations of the fabric greatly (also a goal of SDN, by the way). But what’s really new about ACI is that the programmability and orchestration of the infrastructure (how it takes the orders) is now done in a business-relevant policy language/model.
In a pre-launch post, I looked at why application policies were an ideal model to build infrastructure automation around, and how application policies are better suited to mirror business objectives and requirements than traditional IT infrastructure policies. The fact is that applications are the brains of the business and best reflect the activity and dynamic requirements of the business. Application policies are inherently business-relevant. The key benefits for customers end up being vastly greater degrees of automation, process improvement and business agility. [Note: It will be left as an exercise for the reader to prove that OpenFlow, e.g., is not a business-oriented policy language.]