Cisco Blogs


Cisco Blog > Mobility

The Network After 25 Years of Cisco Live!

#clus1A lot can change in 25 years. At the first Cisco Live (then known as Networkers conferences) in 1989, 200 geeks gathered for the inaugural event. Fast forward to three weeks ago, when we welcomed a whopping 25,000 attendees into the arms of our namesake, beautiful San Francisco.

We heard there was some interest in how the network performed at the show, so I wanted to share some of the interesting statistics about the network at Cisco Live! I shudder at the thought of the ancient network from 25 years ago. So here we go:

Wi-Fi Client Devices

This year we saw 30,705 unique devices, with 7000 in the theater for John Chambers’ keynote.

# of Unique Clients

# of Sessions

# of Unique Users

# of Unique APs

Avg Users per AP

30705

1396239

30705

859

33.64

Max. Concurrent Connected Wi-Fi Devices

There was a peak of 14216 concurrently connected device at SF this year.

clients2 Read More »

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

TU Darmstadt Rolls Out Cisco Unified Access to Prepare for 802.11ac

May 27, 2014 at 11:31 am PST

Technische Universität Darmstadt, usually known as TU Darmstadt is a research university based in Germany. It was founded in 1877 and over the last 137 years has grown to be among the largest and most prestigious public universities in Germany serving over 25,000 students per year. It is the alma-mater to many world-wide leaders from Nobel prize winners, a CEO of a fortune 500 company, a president of a country and multiple World Robocup champions.

tud1

No wonder, they have a reference from Albert Einstein!

tud2

In 2009 TU Darmstadt embraced BYOD with the 5508 Series Controller managing the 1140 802.11n Access Points. Recently we talked to Thomas Vogel, the Head of Network Group and Andreas Liebe, the Network Services Manager who have over 15 years of experience managing WLAN environments. In this blog, we will describe some of the details of WLAN deployments using the 3850 Series Switch and the 5760 Series Wireless LAN Controller to address the new requirements in the school environment. Read More »

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

Increasing Demand for Higher Location Data Resolution

Cisco has been playing a critical part for retail, healthcare, hospitality and transportation organizations to gain an understanding of how end-users move throughout an organization’s physical location. This is done through our Cisco Connected Mobile Experiences (CMX) solution.

With all the valuable information CMX provides, the demand for even more accurate data has been growing. Location accuracy has been a hot developing field and, as I mentioned in announcing our Best of Interop Finalist status in the wireless category last week, Cisco’s taken the lead in redefining how this location-based data is acquired.

In the past many solutions have relied on the probing performed by the mobile device to acquire location-based data.  In recent months this approach has shown diminishing returns. The underlying issue is that this data is reliant on how frequently the mobile device probes an access point. A couple issues that arise include:

-       Mobile device manufacturers are reducing the frequency of device probing to conserve battery. This reduces the number of data points collected and impacts the accuracy of the data

-       Different manufacturers probe the access point with varying frequency so some devices deliver more accurate information than others skewing the location analytics data.

At Cisco’s annual Partner Summit event we are revealing some key areas of focus for the upcoming Cisco v8.0 release. Although the list is not inclusive of all new functionality, I would like to highlight some steps we are taking to bring CMX to meet the ever-evolving demand for location-based data.

Step 1: Increasing Data Resolution 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: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

HDX Blog Series #4: Optimized Roaming

Editor’s Note: This is the last 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. Read part 2 here. Read part 3 here.

If you’ve been a long time user of Wi-Fi, at some point you have either observed someone encounter (or have personally suffered from) so called “sticky client syndrome”. In this circumstance, a client device tenaciously, doggedly, persistently, and stubbornly stays connected to an AP that it connected to earlier even though the client has physically moved closer to another AP.

Surprisingly, the reason for this is not entirely…errr…ummm…unreasonable. After all, if you are at home, you don’t want to be accidentally connecting to your neighbor’s AP just because the Wi-Fi device you’re using happens to be closer to your neighbor’s AP than to your own.

However, this behavior is completely unacceptable in an enterprise or public Wi-Fi environment where multiple APs are used in support of a wireless LAN and where portability, nomadicity, or mobility is the norm. In this case, the client should typically be regularly attempting to seek the best possible Wi-Fi connection.

Some may argue that regularly scanning for a better Wi-Fi connection unnecessarily consumes battery life for the client device and will interrupt ongoing connectivity. Therefore the “cure is worse than the disease”. But this is true only if the client is very aggressively scanning and actually creates the complete opposite of being “sticky”.

The fundamental issue with “stickiness” is that many client devices simply wait too long to initiate scanning and therefore seeking a better connection. These devices simply insist on maintaining an existing Wi-Fi connection even though that connection may be virtually unusable for anything but the most basic functionality. Read More »

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