5 Ways Enterprise IT Is Solving Public Cloud Access
by Andrew Sanders on

Public internet access has little appeal when it comes to mission-critical cloud connections. High latency, low bandwidth and patchy speeds depending on location are just a few hurdles that companies must endure. Here are a few ways you can troubleshoot your public cloud connections and improve cloud access for business applications:

1. Just Build a WAN!

Most enterprises don’t connect to cloud services using the public internet. They build some variation on a WAN to bridge together their various remote sites, and then connect to the cloud through the WAN. WAN connectivity has grown noticeably over recent years, driven mostly by cloud adoption.

All isn’t peachy with the WAN, however. A recent survey of global WAN traffic shows that some kinds of connections, such as TCP, result in lengthy application response times (up to 40 seconds) and up to a 200% variation. Even if you’re using SD-WAN, enterprises still have to watch out for latency and packet loss is the middle mile of a network.

2. Use a Protocol Analyzer

This is a tool that captures packets as they move between applications in your network and in the cloud. This should allow you to identify where problems are occurring and take action accordingly. The drawback of these devices is that they’re usually hardware-based. Users must either hook their laptop directly to a physical hardware switch or install dedicated appliances.

3. Become Expert in SNMP

Your network infrastructure is full of devices that should have a standard configuration—but don’t. When there’s a mismatch between them, problems erupt. The Simple Network Monitoring Protocol (SNMP) is designed to fix that. Several tools based on SNMP have been developed, which specifically monitor infrastructure and send notifications when equipment fails.

4. Check Your Firewall Rules

Sometimes, firewalls will block network traffic to servers in the cloud. There are a few ways to check this. First, ensure that the VM is reachable in any way by pinging it via a console command. If the ping works, then the firewall (probably) isn’t the problem. If it doesn’t, it means your firewall may be blocking ICMP traffic. You’ll also need to check whether the firewall is allowing TCP, which can be done using the telnet command.

5. Talk to Your ISP

Sometimes, the problem connecting to the cloud doesn’t live in your data center. While problems with your ISP may be transient, more endemic issues may require a different kind of connection. Fortunately, your ISP may be able to deliver some form of upgraded cloud connectivity. AT&T, Verizon and CenturyLink all offer services involve connecting an enterprise LAN directly to various cloud services.

Remove the Effort from Cloud Troubleshooting

Whether it’s a problem with your packets, your firewall, your WAN, or your ISP, these troubleshooting methods all have one thing in common—they take time. It takes time to hook physical appliances up to your network switches. It takes time to become expert in new troubleshooting applications. It takes time to wait and see whether an ISP outage is a one-time thing, or an endemic issue. This is all time that you don’t really have. They also require information that you may not be getting from current monitoring tools or network providers.

AppNeta takes the time and effort out of troubleshooting public cloud connectivity, with the patented ability to see into cloud provider networks. You’ll be able to instantly trace the source of an outage or an application slowdown to fix problems faster. See more on how modern monitoring works.

Filed Under: cloud computing, Networking Technology

Tags: cloud networking , ISP , network performance