Cisco Blogs


Cisco Blog > Mobility

Bring Out Yer Dead: 5 Steps to Eliminate 802.11b From Your Networks

Now that US tax day is over, we in the wireless field can get back to focusing on P1: optimizing and maintaining network performance. Keeping your network in good shape is like gardening: if you don’t pull out the weeds, it’ll never look as good as it could. My friend Jim Florwick detailed the gory bits of the 802.11b penalty with its awful lag in efficiency and absolute waste of spectrum. I write today to help give you the steps to act on Jim’s order to stop the madness.

I liken this process to a memorable scene from Monty Python: You must “Bring out yer dead.” However much the first standard insists it’s still alive, let’s all be honest with ourselves: 802.11b is dead.

In memoriam of the first amendment to the IEEE 802.11 wireless networking standard hailing all the way since 1999, 802.11b was superseded by 802.11a and g in 2003 which are much more efficient.  802.11n was available in draft form in 2007 and was ratified in 2009 while 802.11ac was ratified last September. A few years from now we should be planning the wake for 802.11a and 802.11g as well.

Now is the right time to bury 802.11b and reduce the drag on your network. Let’s be real: there is a reason cyclists are not allowed on the freeway, and an 802.11b device will slow everyone down. Here are 5 easy steps for eradicating your network of 802.11b and getting on your way towards higher speed wireless:

STEP    1.         Identify any 802.11b devices on your network

All of the latest Wi-Fi connecting devices are 802.11a/b/g/n capable. So how do you hunt down the 802.11b-only devices? You’ll be looking for older laptop and mobile clients (mostly before the year 2005).

Cisco Prime Infrastructure makes this easy for you with a report on clients by protocol. It will look like this:

prime1 Read More »

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

Non-Stop Wireless Network at John Muir Health

April 15, 2014 at 8:12 am PST

Previously I have blogged about No SSID Outage and No Client Reauthentication whereby even if your Cisco Wireless Controllers were to fail due to any reason, the clients will NOT experience any downtime due to Stateful Failover functionality to a Standby Controller. What could be better than that? Controllers that never go down! 

muir1

A picture is worth a thousand words! As you can see the above the WEBGUI on a 5508 series wireless controller shows that, it is running 7.0 code which was an MD release, has been operational for over a thousand days or over three years! Read More »

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

Top 10 Reasons to Upgrade to the 7.4 MD Software Release

As the famous saying goes, “Good things come to those who wait”. Delayed gratification -- person’s ability to forgo a smaller reward now for a larger reward in the future -- has been linked to better life outcomes as demonstrated by the often cited Stanford Marshmallow experiment and others. In most cases though, it requires a degree of self-control not easily achievable in today’s fast paced, ever-changing world with new mobile devices, protocols and technologies.

If you are one of the Cisco Wireless customers currently deploying Release 7.0 MD and waiting for the next Cisco Wireless Software Maintenance Deployment Release, the wait is over!

Release 7.4.121.0 has achieved Maintenance Deployment (MD) status.

Release 7.4.121.0 is the recommended MD release for all non-802.11ac deployments. For 802.11ac deployments, Release 7.6.110.0 (Release 7.6 Maintenance release 1) is the recommended release.

For additional details on Software Release Recommendations and Guidelines, see Guidelines for Cisco Wireless Software Release Migration

Below are top 10 reasons (in no particular order) to upgrade from the current 7.0 MD release to the latest 7.4MD Release.

10. FlexConnect (improved and rebranded H-REAP) with efficient AP upgrade across WAN, BYOD policies support, Flex ACLs and split tunneling. Read More »

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

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