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 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!
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: Cisco, Cisco DFA, Cisco Dynamic Fabric Automation, cloud, Cloud Computing, data center, DCNM, F3 Modules, FabricPath, KVM, LISP, nexus, Nexus 1000v, Nexus 3000, Nexus 3100, Nexus 5000, Nexus 5600, Nexus 6000, Nexus 7000, Nexus 7700, NX-OS, OTV, private cloud, switch, Unified Fabric, Unified Ports, virtualization, VXLAN
As Cisco Live Europe 2014 draws to a close I wanted to reflect on what has (for me) been a personal campaign to raise the visibility of IPv6 in the World of Solutions / WoS (the demonstration / show floor of the event)
Last year at Cisco Live London I heard some comments that there was not enough IPv6 in the WoS. I decided to see if I could encourage Cisco Business Units and Partners to enable demonstrations for Dual Stack operation and highlight that fact. I wrote previously we would be “awarding” an “IPv6 Enabled Logo” to all Cisco and Partner demonstrations that took the step of enabling Dual Stack and highlighting the same fact.
How did we fare ? Cisco Live 2014 Milano showcased over 15 IPv6 enabled demonstrations including two which were enabled as “IPv6 only”. These were spread between Cisco and Partner booths and were mainly marked with the newly created green “IPv6 Enabled Logo”.
I personally visited a number:
Read More »
Tags: autonomic networking, Cisco, cisco live, first hop security, IPv6, LISP
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: academia, Cisco, community, controller, data center, developers, Enterprise, LISP, netconf, Neutron, NFV, open source, opendaylight, OpenStack, Overlay, ovsdb, SDN, Service Provider, virtualization, yang
Hey Bro, Do you even LISP?
So in the last article, we discussed a bit of why a solution like LISP ( Locator/Identifier Separation Protocol) is required. To summarize, there aren’t enough IPv4 addresses to go around and there are too many IPv6 addresses to let them ‘roam’ using traditional routing methods. Available in IOS (15.1X+) and NX-OS with standards currently being developed within the IETF LISP Working Group, LISP provides a promising solution to mapping IP nodes to locations on the Internet.
If you read the last article, by now some of you are saying, “John, the devices that roam, such as mobile phones, can simply acquire new addresses on the most local network. Why do we need LISP?” It is true this is how we do it now, and it works reasonably well for most users and applications. While it would be nice to seamlessly stream as we move from one network to another, that is more of a luxury feature than a necessity.
The Case for LISP
Let’s forget about mobile devices for just a moment and consider virtual machines and cloud computing. Virtual machines (VM) themselves are increasingly mobile. If I want to do maintenance on some bare metal, I can migrate that VM to another node but if my IP address is going to change, this adds a series of complications in updating services and applications such as DNS (Domain Name Service), to point at the correct address. These name to address mappings can be cached causing significant delays between a desired move and an actualized result when the cache finally expires. Read More »
Tags: EID, ETR, guest blogger, ITR, LISP, RLOC, vm mobility
Your Location Has Changed, Carry On!
Solving the Network Location Problem with LISP (Locator/Identifier Separation Protocol)
The first thing that comes to mind when someone mentions location is our GPS location. Our ability to roam around the earth with our mobile devices is something many of us take for granted. However, at the packet level on the Internet of Everything (IOE), trying to map the network location of a trillion new things may require some new thinking.
Read More »
Tags: getting started, IoE, LISP, location, networking