Wireless Access

In supporting organizations that are deploying IoT and compute resources to the edge of their networks as a way to provide real-time data collection, analysis and action, it’s becoming very important that our customers’ networks, whether they be on a campus, in a data center or in a remote office, provide continuous service 7/24/365, perform at the highest levels, and help provide security. Cloud-managed networking is emerging to help deal with these challenges because of its ability to provide visibility and control regardless of location or type of networking device. But is that enough for your organizations to succeed or do you need more?

We’re doing a study into common challenges you all are dealing with and the potential impact cloud-managed networking could have. The results from this study will help us shape our product direction. Also, to put a bit of a fun spin on it, the top 3 kudo’d replies will receive an IAP303H and a one-year license for Central to manage your new IAP. Winners will be announced in 3 weeks!

So... now to the first pain point we keep running into.

We are at a time where the popularity of branch offices is growing faster than we can keep up and also at the same time also witnessing a transition to a SaaS structure for most daily client applications. Both of these are not a bad thing with proper resources and planning, but what happens when you don’t have access to the proper resources? For this pain point, let’s say that resource is your WAN connection (or the multiple connections you manage). Whether you are having issues with consistency or your pipe simply can’t scale according, how are you addressing this problem? What is your ideal magic button to lessen the impact your network feels from WAN connection limitations?

A pain point is a specific problem that prospective customers of your business are experiencing. In other words, you can think of pain points as problems, plain and simple Upsers. Like any problem, customer pain points are as diverse and varied as your prospective customers themselves.

whoops it was an old post I replied so edited.

Continuing on with the conversation the next pain point is:

Disjointed, disparate tool sets for provisioning, monitoring, troubleshooting and reporting. There are so many options to help you maintain, monitor, and troubleshoot your network how do you, or do you maintain a central point of monitoring and reporting with all of the options? From your perspective, what from would best address this problem?

Tell us about it!

Not every situation is the same, and sometimes we are frustrated at the road blocks. When it comes to Independent management for wired, wireless and SD-WAN, what do you do to advert these challenges?

Give us the scoop!