This fall your wireless networks will experience many devices upgrading to the new Android 5.0(L-release) and Apple iOS 8 releases (cue: IT managers groan). There have now been many blogs attempting to capture the enhancements expected with these releases. Today I am going to focus on describing how Android L and iOS 8 may affect customers deploying Cisco enterprise grade Wi-Fi networks based upon our research and testing of the Apple seed. Our verdict: Carry on with business as usual.
Here are four features we predict will have the most impact your networks:
1. Chromecast and Google Cast Enhancements (Android L)
Rishi Chandra, the Director of Chromecast Product Management announced that, starting with the Android L release, users have the ability to cast to your neighboring devices such as a TV without having to connect to your Wi-Fi network. In the demo, a phone used the cellular connection to connect to chromecast through the cloud. A variety of techniques are used to authenticate the users in the same room OR use a pin-code as an alternative. Users can Google Cast an ecosystem of applications or even their own applications over any Android or iOS device as well as Cloud based apps on Chrome.
Predicted Impact: Given that this feature works transparently to the Wi-Fi, it is expected that there is no impact on the WLAN in your classrooms or dorm rooms or auditoriums where this will most likely be used.
2. Peer-to-peer AirPlay discovery and playback (iOS 8)
Starting with the iOS 7.1 release, AirPlay devices will discover an AppleTV via the bluetooth network. Users could also secure their AppleTV via a 4 digit pin-code. With the iOS 8 release, Airplay devices can also mirror their content via Airdrop. This feature offers an alternative method for customers to discover and mirroring of Bonjour traffic without accessing the corporate Wi-Fi network.
Predicted Impact: Again this feature operates transparent to the Wi-Fi and therefore customers using this feature should not see any impact on the WLAN. Cisco wireless customers also have the ability to use the Service Discovery Gateway on Cisco IOS based switches, routers or wireless LAN controllers or the Bonjour Services Directory on AireOS controllers. Read More »
This week we finished our biggest product announcement in recent memory.The various teams worked hard to bring out to our partners and customers products that delivered maximum quality, flexibility and value.
One of the products included was the new Cisco Small Business WAP371 Wireless Access Point. This Access Point is the first 802.11ac model in the portfolio representing a paradigm shift in the way you as a business owner can improve wireless performance for your business. This new model has a dual radio, includes a Gigabit Ethernet (GbE) Power-Over-Ethernet (PoE) LAN port and has the ever-popular Single Point Set-up capability. The WAP371 also features Captive Portal for guests, and like the rest of the wireless portfolio, offers simple set-up and deployment with an intuitive user interface and set-up wizards.
But this release raises the question regarding exactly why you should think about upgrading your small business wireless network.
Nasser Tarazi, Product Manager for the Cisco Small Business Wireless Access Points, talks about reasons why to take a look at the all-new WAP371.
“Right now is a good time for Small Businesses to consider upgrading their wireless networks from older 802.11 technologies to 802.11ac. First-off, 802.11ac is three times faster than it’s predecessor, 802.11n. The use of Multiple-Antenna, Multiple-in, Multiple-out technology (MIMO) reliably delivers this boost in performance providing for a much better user experience.”
Nasser goes on, “We expect over 70% of mobile devices will be 11ac-enabled by 2016. Like mentioned before, 11ac is three times faster than 11n, so from business-critical to social media applications, improved wireless high-speed performance will ensure your applications will run smoothly, reliably. Also, range is better, even for 11n enabled devices.”
“Security is on every business owner’s mind. 802.11ac is more secure than 11n. And in fact, 11ac is also more power efficient, which can result in a 30% improvement in battery life for your wireless devices such as mobile phones and tablets. Finally, 11ac provides for greatly improved client density, so high-client use cases such as schools, churches, and other organizations will greatly benefit from the upgrade to 11ac.”
Check out our FAQ and the WAP371 product page for more information.
What do WebEx QoS and Phone Troubleshooting have in Common?
If you read my previous blog then you’ll already know that the answer is Medianet. In Part 1 of this 2 Part blog series I discussed the new reverse Metadata capability, provided by a Cisco network, that allows an Enterprise to enable granular QoS marking for all the different media streams that make up a WebEx meeting. In this 2nd instalment, we’re going to take a look at how we can extend Medianet’s Mediatrace capability to Cisco’s 79XX, 89XX and 99XX IP Phone portfolio.
The other recent innovation for Medianet is Prime Collaboration’s ability to now invoke a Mediatrace for a number of IP Phones models that don’t support the MSI (Media Services Interface). As these devices cannot originate Metadata, it has been previously impossible start a Mediatrace through end point selection for telephones in Prime Collaboration. It is now possible, reactively and proactively, to troubleshoot voice quality issues on 79XX, 89XX and 99XX devices, using the same combination of Medianet and Prime Collaboration tools that have previously only been applicable to personal and room based video systems. Take a look at one of my previous blogs, “Medianet in Action”, for some additional background material on video troubleshooting. The demonstration below shows how to start a Mediatrace for a pair of phones.
What do WebEx QoS and Phone Troubleshooting have in Common?
The answer is Medianet, which in conjunction with a Cisco network can provide an innovative solution for two very different real life problems. In Part 1 of this 2 Part blog we’re going to discuss how customers can use Medianet Metadata to provide a robust QoS mechanism for the WebEx cloud service within their Enterprise Networks. Keep an eye out for Part 2 where we’re going to take a look at how we can extend Medianet’s Mediatrace capability to Cisco’s 79XX, 89XX and 99XX IP Phone portfolio. I’ll also point out the benefits for each of these completely different Medianet use cases.
WebEx is a SaaS Conferencing service providing web based data, audio and video conferencing for millions of users. As it’s a cloud service, it’s inherently secure and in a lot of use cases it will tunnel all its media streams within HTTPS. That’s great for secure transport, but it’s resultantly challenging to map the constituent parts of the WebEx application into a granular Enterprise QoS policy. Why would we want to do that anyway? Isn’t it good enough to mark all the WebEx traffic the same? As the saying goes, there is a method to our madness.The tunnelled WebEx traffic contains control packets, data-sharing traffic and possibly VoIP, which are relatively low bandwidth media streams. On the flip side any tunnelled video traffic will likely be bandwidth hungry by nature. The challenge we want to circumvent is how to ensure the WebEx video traffic does not “swamp” the other types of meeting traffic. Ultimately, we want to allow end users to enable the video service they have paid for, without the risk of video having a negative impact on the overall quality of the online conference. We do everything with the end user in mind to make sure you have the best possible experience.
For those of you that don’t know, a WebEx client can generate Medianet Metadata. In simple terms, Metadata is a way for a Cisco application to announce itself to a Cisco network. In the case of WebEx, different Metadata packets are transmitted onto the network, uniquely identifying all the component media streams (including video) that comprise a WebEx conference. This allows a Cisco network to useWebEx Metadata to differentiate between any WebEx traffic types, even when securely tunnelled over a HTTPS connection. The figure below provides an illustration of the different Metadata packets that will be generated for different types of WebEx traffic.
Figure 1 – Identifying Different Flows using Metadata
Imagine that you have several branch offices that are using WAN demanding applications like Salesforce.com, Office 365, Virtual Desktops, Video Teleconferencing and more. You are using those expensive MPLS/VPN WAN connections as you don’t want to risk it and probably because when you started to work there it was already there and … why mess around with something that is working, right? Normally I would agree with that but when IT budgets are shrinking and the network needs to step up and support those business critical apps, there is no other way but to innovate.
At any given time your network carries information from LAN to WAN and vice versa, some is important and some is less important. In many cases as a network admin you don’t have the visibility to distinguish between them, so what do you do when those critical apps are starting to act up? Usually the answer will be to buy more WAN bandwidth and that will give the apps and the user experience behind them some breathing space. But all you’re doing is buying time. Buying time never solves the problem because you will need to treat the symptoms again in a few weeks or months.