Cisco Blogs


Cisco Blog > Internet of Everything

School Days 2.0: Connected, Borderless, and Highly Inclusive

Up in the mornin’ and out to school
The teacher is teachin’ the Golden Rule
American history and practical math
You study’ em hard and hopin’ to pass

Chuck Berry’s old hit “School Days” sums up an educational model that has persisted since the 1800s — if not since Aristotle. Students and their classmates sit within the same walls and absorb rote knowledge from one teacher at a time. And woe to those who fail to show up for the morning bell or to follow the lesson plan!

But if you think your own school days are a model for the future, get ready for a whole new lesson plan. Just as the Internet of Everything (IoE) is disrupting so many other areas of our lives (not to mention business models), its ever-expanding wave of network connectivity promises to upend education as well.

After all, when people, process, data, and things are linked in startling new ways, radical transformation follows. Within the context of learning, the very definition of schools, students, teachers, and classrooms is being challenged. Now, your classroom is wherever you happen to be, and your lessons take place when you want them — all thanks to a convergence of IoE cornerstones such as mobility, media-rich collaboration tools, cloud, and analytics.

Cisco predicts that the IoE Value at Stake will be $4.6 trillion for the public sector worldwide over the next decade. Of that total, $258 billion in value will come from Connected Education.

 

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: , , , , , , , , , , , , , , , , , , ,

Cisco Live Milan 2014 & CMX

cmxclmilan1

Cisco Live Milan 2014 kicked off this morning with an opening keynote by Rob Lloyd. During the session Rob shared Cisco’s  vision of the Internet of Everything, and explored the industry trends and technologies that are making that vision a reality. One of these areas is enabled by Cisco’s CMX solutions and our growing ecosystem of partners.

To illustrate how this vision is becoming a reality, a CMX demo was shown on stage. The demo related to a wine producer ( we are in Italy by the way..) who was able to engage with their customers via their mobile app. Enabling the customer find the particular wines they are interested in, interact with the wine maker, get location specific promotions and really deliver a highly personalized and location specific service.

cmxclmilan2

CMX at Cisco Live Day 1:

The whole venue has been designed and setup for WiFi location based services and CMX is running across the complete conference. Read More »

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

What Next for BYOD?

One of the interesting and challenging aspects of working in the Mobility space is the sheer pace at which the industry is moving.  I’m fortunate to work with many Customers in EMEA to help support and shape their strategy towards Mobile technology.  A great example of this has been the reaction to BYOD.

The influx of personal devices into the Enterprise caused by the BYOD trend poses numerous challenges to IT Departments.  Understandably, initial reaction was to focus on network and device level Security.

Cisco responded by introducing a BYOD Solution to remove some of the burden from IT Departments and provide them with a central point for managing many aspects of the BYOD lifecycle: onboarding, device profiling, authentication, authorization, offboarding and self-service management.

Almost at the same time, a new industry segment was created: Mobile Device Management. The intent of MDM systems is Read More »

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

HDX Blog Series #2: Scaling with Turbo Performance

Editor’s Note: This is the second of a four-part deep dive series into High Density Experience (HDX), Cisco’s latest solution suite designed for high density environments and next-generation wireless technologies. For more on Cisco HDX, visit www.cisco.com/go/80211ac.  Read part 1 here

With any new technology comes a new set of obstacles to overcome.  802.11ac is no exception.  Last week we talked about CleanAir for 802.11ac and why spectrum intelligence still matters. Another challenge is scalability. In this post I will give you some details on new HDX feature, Turbo Performance, which allows the AP 3700 overcome common scaling issues to scale amazingly well.

What’s Different with 802.11ac?

802.11ac means higher data rates, which means more packets per second (PPS).  There are three reasons for more PPS with 11ac: wider channels, increased modulation and increased aggregation.  Channel width doubled to 80 MHz, modulation increased from 64 QAM to 256 QAM, and aggregation increased from 64k to 1MB!

With 802.11n, an AP might have had to push 30,000 1500 byte packets per second through the APs data plane. Today with 802.11ac that could now be 75,000+ PPS.  More PPS means more load on the APs CPU, so to really keep up with the demands of 802.11ac, we needed to go back to the drawing board.   Read More »

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