Deploying the Mobility Services Engine

December 15, 2011 - 0 Comments

CleanAir continues to provide significant differentiation for Cisco Wireless as well it should. What many don’t realize, is how much of the attractive visualization and control is not from CleanAir itself, but CleanAir plus the Mobility Services Engine. I would go as far as to say there are several very important distinctions for why the MSE should be considered a mandatory element within any Cisco Wireless Design.

1. Event Correlation – this gets really attractive when you are dealing with multiple controllers. The increased speed for troubleshooting and making sure you are only chasing real problems, not ghost redundancies is fantastic.

2. Historical Replay – interference issues are intermittent.  CleanAir can give you a look at the spectrum that y0u may never have considered…but when you are trying to back trace an issue you will appreciate this more than ever.

3. API – this pretty much ensures that the sky is the limit. For example – I have been really intrigued with the possibilities for what is happening with indoor wireless.  Check out Spotlight Mobile or SITA Lab and Copenhagen airport.  Using our Smart Phones for personal navigation could have profound implications as well – Cisco’s Unified Wireless along with the MSE and the multiple triangulation methods available form the base for all this innovation. The API makes it easily available for smart developers like this to take it all to another level.

What are you doing with all that rich metadata?

Check out Fundamentals of MSE for good baseline.

The team we have been working with on this product have been incredible.  If you are running wireless without this you are NOT maximizing your investment.  Check out their stuff at



In an effort to keep conversations fresh, Cisco Blogs closes comments after 60 days. Please visit the Cisco Blogs hub page for the latest content.