Cisco Blogs

Cisco Blog > Mobility

Five Reasons to Upgrade Cisco’s CMX to MSE 8.0 Today

The highly anticipated Wireless Release 8.0 came out last week, and among the feature updates is a key set of enhancements and new modules for Cisco’s CMX solution that come with MSE 8.0.  These updates were designed to build out the breadth of location services available to organizations, as well as improve the user experience for customers working with the CMX solution. These enhancements make five great reasons to upgrade to 8.0 today and test out these new tools and features in your Wi-Fi location deployment:

1. Presence Analytics

This new feature enables the use of a single access point (AP) to determine device presence and dwell time. It provides a simplified way to leverage Wi-Fi technology to Detect, Connect, and Engage your customers. Retail stores, hotels, conference facilities, shopping malls, schools, and even city centers can greatly benefit from Presence Analytics. Unleashing this tool can help customers understand the basic, yet powerful, knowledge of the number of visitors to their space, time spent by the visitors, and frequency of visits. It can even provide a more in-depth look into the movement patterns of their visitors, while within their space, giving an understanding of which areas are most attractive to their client base.

Presence Analytics is very simple to configure by naming the entry, selecting the access point, and setting threshold values. Best of all, the majority of CMX Analytics reports are available automatically. All this allows customers to start using CMX Analytics without having to make any changes to their existing network and get immediate value from it.


2. Enhancements to Guest Access
Those familiar with CMX Connect will know that there are two guest access solutions available to customers with Cisco CMX. The first, CMX Connect, provides organizations with a simple, secure way to provide guest Wi-Fi access. CMX Connect offers the option of custom splash pages using a zone-based captive portal.

In MSE 8.0, we have dramatically simplified how CMX Connect is configured. The administrator only needs to indicate information they’d like collected (such as, name and email), and the zones in which the template will be used. 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: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Announcing Cisco Wireless Release 7.5

With the prevalence of mobile devices connecting people and things today, we are seeing a base expectation for uncompromised wireless connectivity. There is no doubt that the trend for high performance, pervasive wireless is on the rise and will continue for the foreseeable future. We at Cisco strive to help organizations get ahead of these trends with solutions that can be deployed with confidence today.  That’s why I am proud to announce the latest Cisco Wireless Release 7.5, the third feature-rich release we’ve had in the last 12 months.

Release 7.5 enables mission critical wireless deployments with sub-second stateful failover for wireless clients, wire-like Gigabit performance with the 802.11ac Module, and a bevy of other features.

Key Features in 7.5:

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