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

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

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

Naughty or Nice: Cisco Wireless Rewards Release 7.6 Innovations to All

Deloitte’s 2013 Annual Holiday survey came out with some staggering statistics:

  • Nearly 7 in 10 shoppers will use their smartphones and tablets to shop this holiday season.
  • Nearly half of all shoppers will use social media to assist in shopping.
  • 73% of shoppers will be influenced by coupons and promotional offers.

Retailers both online and in-store can no longer ignore the power of mobile technology and social media influence with shoppers. Shoppers using mobile devices inside stores are actually more likely to make a purchase when being presented with the right information. In fact, this isn’t only true for retailers, but across all industries. Whether it’s guests, visitors, patients or passengers, there’s a real opportunity for businesses to make an impression via the mobile device.

Today I am happy to announce our latest Cisco Wireless Software Release 7.6. As you may recall from Sujai Hajela’s State of Cisco WLAN blog earlier this week, Cisco’s Wireless group has been ahead of the competition with our dedication to delivering cutting edge, high performing technology to our customers.

Many features in Release 7.6 were designed specifically to enable our customers to take advantage of the latest mobile trends. Here are some of the highlights:

Connected Mobile Experiences (CMX)

CMX for Facebook Wi-Fi is a joint Cisco — Facebook solution for guest Wi-Fi. Read More »

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

Wireless Controller Redundancy with No Client Reauthentication Needed

July 12, 2013 at 5:00 am PST

Last fall, I blogged about No SSID Outage or Access Point Stateful Switchover introduced with the AireOS 7.3 release whereby if your wireless LAN Controller fails due to some hardware failure, thousands of Access Points fail over sub-second to the standby controller! This is possible due to continuous synchronization of CAPWAP states, Configuration Changes, Radio Channel and Power, Roaming Keys and Access Point licenses between the two Controllers. This means even if the administrator changes the configuration, channel plans or the clients roam and the primary controller fails; the Access Points will simply fail over in a stateful fashion to the secondary. In this blog, I will share details on the upcoming enhancements to High Availabilty with the 7.5 release.

In the upcoming AireOS 7.5 release, we take High Availability to the next level with two critical enhancements.

1. Today, after Access Points fail over from the primary to the standby controller, each client tries to re-authenticate and the standby controller then checks against its CCKM database whether the client has already authenticated. At the rate of several tens of authentications per second, it can take anywhere from zero to a few hundred seconds for the tens of thousands of clients that are connected to a controller to re-authenticate. The client stateful essentially eliminates this downtime with sub-second failover. Thus the total downtime that any user running a voice-call or Citrix session experiences is 2-3 seconds that the application requires to reconnect.

sso1 Read More »

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