Cisco Blogs

Cisco Blog > Mobility

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 has achieved Maintenance Deployment (MD) status.

Release is the recommended MD release for all non-802.11ac deployments. For 802.11ac deployments, Release (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 CMX Analytics & Insights @ #MWC14

mwc3_1Today MWC 2014 came to a close in Barcelona having been another resoundingly successful event.

Mobile operators and Service Providers have displayed ever increasing interest in Monitization of their infrastructure especially via WiFi and Cisco’s CMX solution.

During the week I had many conversations with SP’s from across the world while very different geographies and facing different challenges, a common theme among the meetings was how can Cisco help us find ways to generate new revenue streams and new monetization models.

At MWC we showed various demos that show how this can be achieved and provide many interesting ideas to the customers to help them think about their own businesses and how they may be successfully applied.

One demo was how various components of Cisco’s SP Architecture can improve services and provide montitization opportunities to a fictitious hotel resort chain with wired and wireless small cells, SON &  Analytics all working together. Read More »

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

Cisco CMX & Monetization @ MWC 2014

mwc1_1Mobile World Congress 2014 continues this week in Barcelona with record attendances.

Many SP’s are exploring new ways to monetize their network investments, in an earlier posting some of these models were explored. Again this week these topics were again very much to the forefront with Service Providers actively discussing and exploring how to take the first steps to exploit this.


Hall 3 @ MWC Analytics:

The volume of traffic at the event was very large and as we can see in Hall 3 below, where Cisco along with a number of large companies are located, was very busy this morning.  Read More »

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

CMX, Analytics and Intelligence @ MWC 2014

Mobile World Congress 2014 is underway at Fira Gran Via in Barcelona, Spain.


As well as providing the WiFi network to the event, which has over 1200 access points covering the 2.6m sq feet  conference venues, Cisco had a number of exciting demos within the booth area in Hall 3.

Cisco’s theme is around utilizing your network infrastructure for business outcomes, being more intelligent, utilizing analytics and delivering capabilities and monetization opportunities.


Utilizing location based information along with various other network related information interesting dashboards and views of the event are possible. These screens show how using the Cisco open infrastructure various sources of data are combined in to a graphical view of the Fira conference venue during day 1 of MWC 2014. 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  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: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,