Cisco Blogs


Cisco Blog > The Platform

Executing on Virtualization

With all the talk around virtualization in our industry, it’s easy to get a bit confused.  Between our industry’s love of acronyms and passionate evangelism of technological specs, it can be far too difficult at times to determine what’s really important, what is real, and what is just talk.  Our announcement of the Cisco Evolved Services Platform today is meant to address these very points.  It represents the progress we’ve made on our provider virtualization strategy and, unlike many others in the industry, orients the talk of virtualization around real business benefits and customer deployments.

The Evolved Services Platform represents a fundamental shift in the way service provider networks will be built.  It not only has the industry’s broadest, most comprehensive range of virtualized functions, but it also orchestrates them to create, automate and provision services in real time, across compute, storage and network functions across the entire architecture.  As the middle layer of the Cisco ONE SP architecture which works in conjunction with the infrastructure layer – the Evolved Programmable Network which we announced in September – the ESP ensures the right type of experience for subscribers regardless of how or where they connect to the network.  And it does this while also delivering both significant operational cost savings and the ability to more easily and quickly pursue new revenue generating opportunities.  In essence, the ESP does the equivalent for a service provider business as a retail storefront, factory, and tool kit would do for a manufacturer. It allows them to “manufacture” network experiences quickly, efficiently, and in a customized manner.

Those experiences can be many and span the entire provider’s existing services portfolio, plus an ever increasing array of new services that are now or will be possible in Internet of Everything.  But to help keep the business orientation of this announcement, we’re announcing the first two service modules, complete with business models that can help quantify the benefits to the providers that are interested in or already deploying them: Read More »

Tags: , , , , , , , , ,

Introducing the Cisco Nexus 5600

What is the new Nexus 5600?

We at Cisco are really excited to introduce the new Cisco Nexus 5600 platform! It is the third generation of industry’s leading Data Center Server-Access Nexus 5000 series of switches. Cisco Nexus 5600 is the successor of industry’s most widely adopted Cisco Nexus 5500 series switches (with over 20,000 customers and 25 million ports shipped)  that maintain all the existing Nexus 5500 features such as LAN/SAN convergence, Fabric Extenders (FEX) and Fabric Path.

The new Nexus 5600 was unveiled at CiscoLive Milan in January 2014 with quite a bit of interest

:cvg3

Nuts and Bolts

We are introducing 2 models under the 5600 platform:

Cisco Nexus 5672UP – A 1 RU 10/40G Ethernet switch offering wire-speed performance for up to 48 10G Ethernet ports (16 of which are Unified Ports) and 6 true 40G ports.

Cisco Nexus 56128P – A 2 RU 10/40G Ethernet switch offering wire-speed performance for up to 96 10G Ethernet ports (48 of which are Unified Ports) and 8 true 40G ports..

In addition to the existing features of the Nexus 5000, 5600 platform brings new features such as True 40 GE support, VXLAN bridging and routing and Cisco Dynamic Fabric Automation (DFA) innovation. With a latency of about 1 µsec, the 5600 platform is ideal for applications which need low latency. For those of you who need network programmability, the Nexus 5600 supports Cisco OnePK and Openflow.

 Why these new features matter

 Extensibility with VXLAN support

The Cisco Nexus 5600 with its VXLAN support is very well suited for multi-tenant cloud deployments. In large scale, multi-tenant cloud deployments, there is a need for VMs to migrate across layer-3 boundaries. Traditional VLANs only support about 4000 VLANs which are insufficient in the deployments of thousands of VMs. With the migration need across layer-3 boundaries complexities of layer-3 routers are introduced. To solve the scalability as well as the migration issues VXLAN was developed. For more details on VXLAN, watch the video: http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9902/vidoe_fundamentals_vxlan.html

Ease of management with Cisco Dynamic Fabric Automation (DFA)

 Our customers are also faced with complex, manual network configurations and have a hard time keeping up with application requirements. To solve these challenges, Cisco has developed an architecture called Dynamic Fabric Automation (DFA) which simplifies management and automation – such as automatic device and fabric configuration, automatic VM deployment, migration and seamless integration of bare-metal and virtualized resources in the data center. The Cisco Nexus 5600 platform with DFA implemented in the hardware as well as software is ideal for the multi-tenant and mixed (physical and virtual) cloud infrastructure.

For more information on DFA, please visit: http://www.cisco.com/en/US/solutions/ns340/ns517/ns224/ns945/dynamic_fabric_automation.html

True 40G support

 The difference between a 40G and True 40G port is that you can push an entire 40G flow in the True 40G port and in the normal 40G port, the port really is divided into 4 10G ports via Etherchannels, Thus in the True 40G, you get full 40G bandwidth. The Cisco Nexus 5600 platform switches has True 40G ports, which help in servicing the full 40G flows.

The Big Picture

Cisco has one of the most comprehensive portfolios for the Data Center and Cloud Networking and this Nexus 5600 platform is but one of the pieces of this portfolio. You may want to read this excellent blog,   which explains Cisco’s Data Center and Cloud Networking portfolio.

Tags: , , , , , , , , , , , , ,

Marching towards Cloud CDN

Why should you put a virtualized content delivery network (CDN) in the cloud?

This is not just a theoretical question. It has come from our customers. At our recent Cisco Live event in Milan, we demonstrated how our continued CDN technical leadership can answer this question.

First, some history, as you can’t just begin with the cloud.

At Cisco, we’ve been working hard over the years to evolve our Videoscape Distribution Suite (VDS) platform. From its roots in hardware-based appliances, to software applications powered by our data center hardware, and more recently to virtual machine implementations which can be powered by our own or third party hardware. Each technological advance to our VDS platform has netted gains for our customers in their CDN deployments; whether through more flexible deployment from greater hardware independence, faster time-to-market implementing VDS software applications, or reduced total cost of ownership thanks to server-based virtualization that optimizes footprint and power/cooling requirements.

Nonetheless, requirements continue to evolve.

Consumers expect to Read More »

Tags: , , , , , , , , ,

…And The Momentum Continues! New Nexus Data Center Innovations AND Customer Deployments!

You probably have already heard that during CiscoLive Milan, we have unveiled the new additions to our Data Center and Cloud networking portfolio:

New Nexus Switches

  • New Nexus 7706 and a high density F3 Series 1/10G module for Nexus 7700 provide increased deployment options for data center interconnect, core or aggregation.
  • The next generation Nexus 5600 family offers VXLAN bridging and routing capability, line rate L2/L3, and 40G uplinks, to deliver high performance in a compact form factor for 10G Top of Rack, 1/10G FEX aggregation deployments.
  • New Nexus 6004 Unified Port LEM Module brings industry’s highest UP port density in a four RU form factor simplifying LAN and SAN convergence.
  • New Nexus 3172TQ top of rack 1 RU switch delivers industry-first 1/10G BaseT copper server access and superb performance combined with robust NX-OS features.
  • New Nexus 1000V on the Kernel-based Virtual Machine (KVM) hypervisor brings OpenStack cloud a fully integrated network virtualization solution that can be deployed consistently across VMware, Microsoft, and Linux based software platforms.

AND THERE HAS BEEN BROAD CUSTOMER ADOPTION ACROSS THE DATA CENTER! 

Data Center Nexus Networking Momentum

From Nexus 1000V to the Nexus 9000, Cisco’s holistic approach resonates with customers because it provides increased business agility, operational efficiency, and empowers IT to rapidly evolve as business requirements change.

Here are the latest examples of why our customers chose Nexus:

Read More »

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , ,

OpenDaylight Unleashes Hydrogen to the Masses

The OpenDaylight Project today announced that its first open source software release Hydrogen is now available for download. As the first simultaneous code release cross-community it has contributions across fifty organizations and includes over one million lines of code. Yes. ODL > 1MLOC. For those of you interested that’s approximately two hundred and thirty man-years of work completed in less than twelve months.

It was around this time last year that the media started to pick up on a few rumors that something may be in the works with software-defined networking and controllers. I remember our first meeting at Citrix where the community started to collaborate on The OpenDaylight Project and come to common ground on how to start something this large. We had multiple companies and academics in the room and many ideas of where we wanted this project to go but there was one thing we had in common: the belief and vision to drive networking software innovation to the Internet in a new way and accelerate SDN in the open; transparently and with diverse community support. Each of us had notions of what we could bring to the table, from controller offerings to virtualization solutions, SDN protocol plugins and apps to solve IT problems. Over two days at Citrix we looked at things from a customer perspective, a developer perspective and ultimately and arguably the most important, a community perspective. From there The OpenDaylight Project emerged under the Linux Foundation. As I look back I want to applaud and thank the companies, partners, developers, community members and the Linux Foundation for driving such a large vision from concept to reality in less than twelve months, which is an incredible feat in itself.

Hydrogen is truly a community release. Use cases span across enterprise, service provider, academia, data center, transport and NfV. There are multiple southbound protocols abstracted to a common northbound API for cross-vendor integration and interoperability and three editions have been created to ensure multi-domain support and application delivery as well as deployment modularity and flexibility for different domain-specific configurations. These packages have a consistent environment yet are tailored to domain and role-based needs of network engineers, developers and operators.

  • The Base Edition, which includes a scalable and multi-vendor SDN protocol based on OSGi, the latest (and backward compatible) OpenFlow 1.3 Plugin and Protocol Library, OVSDB, NetConf/Yang model driver SDN and Java-based YANG tooling for model-driven development.
  • The Virtualization Edition (which includes the Base Edition) and adds Affinity Metadata Service (essentially APIs to express workload relationships and service levels), Defense4All (DDoS detection & mitigation), Open DOVE, VTN, OpenStack Neutron NorthBound API support and a virtual tenant network offering.
  • The Service Provider Edition (again, including the Base Edition) that also offers the Metadata Services and Defense4All but includes BGP-LS and PCEP, LISP Flow Mapping and SNMP4SDN to manage routers, gateways switches.

More information can be found on the website with regards to the releases and projects themselves.

I want to stress the importance of how well the vision has been delivered to date. I’ve been involved in multiple standards-bodies and in open source discussions in the past but this is truly one of the largest undertakings I’ve seen come together in my entire career. OpenDaylight developers have been coding day and night to get this release out the door and it’s amazing to see the collaboration and coherency of the team as we unite to deliver on the industry’s first cross-vendor SDN and NfV Platform. In addition and frequently not mentioned is that many of the protocols listed in the Editions above are also standardized at organizations like the IETF during the same period. Code and specs at the same time. It’s been a long time since rough consensus and running code has been the norm.

Over here at Cisco we’re fully committed to OpenDaylight. We’re currently using it as a core component in our WAN Orchestration offering for service providers to allow intelligent network placement and automated capacity and workload planning. The ACI team (formerly Insieme) collaborated with IBM, Midokura and Plexxi to create a project in OpenDaylight that creates a northbound API that can set policy and be used across a wide range of network devices. And of course we’re bringing components of the OpenDaylight codebase into our own controllers and ensuring application portability for customers, partners and developers alike. From this I would expect to see more code donations going into the community moving forward as well. We made several announcements last week about our campus/branch controller that includes OpenDaylight technology.

At the end of the day an open source project is only as strong as its developers, its community and its code. As we as a community move forward with OpenDaylight I expect it to become stronger with more members joining with new project proposals as new code contributors coming onboard from different industries as well. As I look at our roadmap and upcoming release schedule I’m pumped for what’s next and so happy the community has catalyzed a developer community around networking.

Please do visit the site, download the code and take Hydrogen for a test-drive. We want to hear feedback on what we can make better, what features to add or how you’re going to utilize it. Moreover, we’d love you to participate. It’s a kick-ass community and I think you’ll have fun and the best part; you’ll see your hard work unleashed on the Internet and across multiple communities too.

Tags: , , , , , , , , , , , , , , , , , , ,