Using Ping Options More Effectively

By | Network Engineering, Resources | No Comments

I feel sorry for ping.  Ping has been beaten up, abused, misunderstood, banned and even tossed aside.

Ping was originally used to check if a device was up or down, period.  Back in the day, equipment failure was very common. I chuckle thinking back at those sales people that used Mean Time Between Failure to sell their equipment. As network analysts, we needed a way to see if our hardware or equipment failed and ping did the trick.

Over the years, SNMP was introduced to aid in network visibility, but we still used ping for simple up and down checks. In the 90s, bandwidth limits were becoming an issue, so we used ping response time results to determine if a device or link was slowing us down.
Read More

Meetups for Network Engineers

By | Network Engineering, Resources | No Comments

Meetups for network engineersUnless you’ve lived in a cave for the past ten years (and if you have, I totally respect that), you are most likely familiar with meetups. Meetups are planned events where members regularly get together to network and talk about a particular topic that they are interested in. It could be a sport, a language, a discipline, etc. Currently, there are more than 270,000 meetups in 182 countries, for a total number of 30+ million of members. That’s pretty significant.

If you’re interested in meeting with other network engineers, then you should know that there are several meetup groups around the country that are focused on network engineering. All you have to do is go on, search for a topic of interest in your area, and then follow the group guidelines on how to become a member. Some groups are open, while others may require permission or vetting from the organizer. If you don’t know where to start, here is a list of the most prominent meetups that may appeal to network engineers:
Read More

HTTP transaction timing breakdown with curl

By | Network Engineering, Network Monitoring, Resources | 3 Comments

curl is one of the most used commands for HTTP transactions. It’s a Swiss army knife for network and application engineers when they want to quickly test whether a server application is responsive, and it also has a myriad of options to configure proxy servers, username-password pairs, encryption protocols, redirections, and much more. Our purpose here is to give a quick overview of how you can use curl to break down the timing of an HTTP transaction from namelookup to the completion of the HTTP request. Read More

3 Ways to Bridge the Gap Between Network and Application Groups and the Help Desk with Distributed Network Monitoring

By | Distributed network monitoring, Network Monitoring, Resources | No Comments

A_Part_of_Pittsburgh_by_titaniaThe internal help desk of an enterprise is the end-user’s single point of contact for ticket submission and troubleshooting. Unsurprisingly, the help desk receives tickets that range across the board from keyboard and mouse issues to application and network problems. A company may have one, two, or more levels of help desk support depending on its size, allowing ticket escalation to more specialized staff as needed.  Read More

Troubleshooting Networks with NetBeez

By | Network Monitoring, Product, Resources, Troubleshooting | No Comments

One of the best ways to show how NetBeez enables network engineers to improve their operations is through the lenses of our customers. For that purpose, we have just published Troubleshooting with NetBeez, which describes the following three use cases:

  • Troubleshooting web application performance problems
  • Determining the root cause of intermittent connection issues at retail stores
  • Verifying web content filtering

We compiled them from a number of use cases our customers have shared with us. It has been a really rewarding experience to get the feedback from network engineers on how they use our product. With NetBeez, our customers have reduced dispatches by being able to know exactly what’s going on at every remote site of their network, decreased troubleshooting time thanks to the fault-isolation data displayed on the dashboard, and proactively detected and repaired network issues at remote locations even before their users got impacted and opened tickets.

Read More