The Sochi Winter Olympics are officially underway, and as you may have seen, NBC will once again be providing viewers access to live streaming in a multitude of mediums. On the NBC Olympics page, computer users can enter their cable or digital television provider personal user name and password and watch live video of the events. Mobile viewers can also download the free NBC Live Extra App. The iPhone, Droid and iPad app will have live and recorded events, and on demand HD video. And for the first time, NBC Universal will stream video on Facebook as part of a partnership deal with the social media giant.
The games run until February 23, which includes 10 business days of events. Given the time difference, many of the events will air during normal working hours throughout the U.S. As NBC makes it easier and easier to bring the Olympics viewing experience to the office, are network operations staff prepared for the potential bandwidth onslaught? Employees don’t always realize the impact they can have on network performance and don’t understand how watching something as exciting as the cross country skiing finals could impact their entire company.
Streaming video can be an enormous bandwidth hog and can occupy much more network resources than almost any other application. At a remote office location, even one person watching live video coverage of the Olympics can bring an entire LAN to a standstill. And it doesn’t take more than a handful of viewers at large sites to slow the network to a point where customers have difficulty accessing the company’s Web site or the quality of Internet-based telecommunications tools (like Skype) degrades.
This problem has only been exacerbated by the influx of personal mobile devices into the enterprise, all of which are sucking up bandwidth from the corporate wireless network, which is generally more bandwidth constricted than the fixed-line Ethernet network.
The only way to analyze this traffic and be able to reroute it or add more capacity is to have full visibility into the network. There are a couple of “best practices” that make performance of this task more likely to result in a successful outcome. These include:
- Baseline your networks BEFORE you need to start “allocating” bandwidth. If you know what your normal network needs are, you are in a better position to set Quality of Service (QoS) policies to guarantee bandwidth for your mission-critical applications. Most importantly, don’t be satisfied with simply knowing the “average” bandwidth required – look across a several-day baseline to see usage by hour, and pay close attention to if/when you have microburst activity (applications causing his will most likely be the ones impacted first if your network becomes saturated).
- Since it is likely that most “non-business web browsing” will happen on Bring your Own Devices (BYODs), which are nearly universally wireless, think about isolating your wireless network from your mission- critical network, and consider putting limits on the outside bandwidth served to that network.
- Monitor your network closely, and look for signs of issues proactively. High-resolution network visibility tools are critical to ensuring you will see problems before they impact your enterprise.
- Assume you will run into issues, and plan what your options are when they occur. If your playbook has already thought-out and documented options to deal with issues, it is far more likely that you can mitigate issues quickly.
Learn more about our network visibility solutions here, and we, like many others around the world, look forward to watching the best of the best compete in Sochi for this year’s Winter Olympics!
** this blog was originally posted to APM Digest