Cisco Blogs


Cisco Blog > Mobility

Cisco Bonjour helps make beautiful music at University of Nevada, Las Vegas

February 28, 2014 at 4:36 pm PST

The University of Nevada, Las Vegas (UNLV), founded in 1957, is located in the heart of showbiz industry in Las Vegas. The school offers higher education programs ranging from business, engineering, fine arts and music, and science, and professional schools such as dental medicine and law.

The school’s mascot, Hey Reb, was recently featured on Hulu’s “Behind the Mask,” and you may recognize the Southern Gym during the dance scene between Elvis Presley and Ann-Margret Olsson in the movie Viva Las Vegas.

With over 24,000 unique WLAN users per day, 1.1 gigabytes of throughput per second, and more than 50 wireless access locations across campus providing WLAN coverage, this educational institute demands a massive Wi-Fi network.

In the previous blog, we highlighted some of the Bonjour enhancements of the 7.5 software release and the deployment of Bonjour at St. Margaret’s Episcopal School, a K-12 school. In this blog, we will describe details about UNLVs WLAN deployment, how they use Bonjour services, and give you an insight into rapid pace of innovation necessary to support this technology in the education arena. 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: , , , , , , , , , , , , , , , , , , ,

Is Your WLAN Ready for Unified Communications & Collaboration?

January 31, 2014 at 5:00 am PST

As Wi-Fi continues to be the primary mode of access, enterprise Unified Communication(UC) applications usage is increasing with smartphones, tablets and laptops.

Customers are asking, is there anything I can do to prioritize Jabber or Lync traffic over others or even identify how much of the traffic is really collaboration traffic vs. other types of media. The recently introduced Wireless Release 7.6 enhances the ability to classify Microsoft Lync 2013 and Jabber with Cisco WLAN Infrastructure.

In the first blog about Application Visibility and Control over Cisco WLAN, I captured what is AVC and the capabilities included in the release 7.4. In a subsequent blog, I had captured a success story about a customer who benefited from the reliability by deprioritizing scavenger level applications as well as captured highlights of the enhancements in release 7.5. This blog captures how the release 7.6 allows popular collaboration applications to be accurately classified and prioritized as well as provides a teaser to some of the innovations that can be expected in the future.

What exact capabilities AireOS 7.6 provide ?

The protocol pack 6.3 introduced in AireOS 7.6 allows you to identify and prioritize not just Jabber but also sub-classify Cisco Jabber Audio, Cisco Jabber IM and Cisco Jabber Video. Customers may want to prioritize the Cisco Jabber Audio as the highest priority while the others may be lower priority. Similarly you can classify not just Microsoft Lync but also Microsoft Lync Audio, rtcp and Microsoft Lync Video and thereby prioritize them separately. Read More »

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

CMX Analytics: An Inside Scoop on CiscoLive! Milan #CLEUR

cmxclmilan1

Today is the final day of a very busy and successful Cisco Live Milan 2014. Read my initial observations from the event earlier this week.

As the event draws to a close, lets look at some of the location analytics available via Cisco’s Connected Mobile Experiences solution (CMX) and perhaps try to answer some of the following questions about the event.

For this I will just focus on the World of Solutions Show floor -- approximately 800,000 sq feet in size, and containing all the Cisco Booths and the partner displays.

  1. How many people actually visited the world of solutions?
  2. How many people did  the different Cisco Booths attract?
  3. Where was the busiest part of the show floor?

These and other insights can be derived from looking at the business intelligence that emerges from CMX. Read More »

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

My App anywhere: On devices, on controller, on both!

January 29, 2014 at 12:41 am PST

Current differences in app development on devices and controllers disappear. Devices and controllers will share a common programming environment – offering a unified development and deployment experience.

While SDN is moving from concept to reality, we notice that many deployments which focus on creating new network features interpret the role of the “controller” very pragmatically. In these deployments, the controller is not used as an independent layer of software which abstracts the entire underlying infrastructure as in the traditional view of SDN (see for example ONF’s SDN Definition). The pragmatic approach to network programming simply extends the distributed development environment of the network devices using a set of qualities offered by the controller.  Developers move those components of their distributed apps to the controller that benefit from the logical centralization or the enhanced resources (CPU, memory) that a controller typically offers while keeping other components on the network devices. Example use cases fall into the categories of distributed network analytics, DDoS thread mitigation, or routing optimization based on performance measurements. What does this mean for our development environment?

Read More »

Tags: , , ,