11 posts categorized "NetBeez" Feed

NetBeez Quickstart (by Tony Fortunato)

There is no shortage of utilities, applications and full blown network troubleshooting systems out there.  Some are free, and some cost a pretty penny.  Spoiler alert, they ALL have their place in the analysts’ toolbox.

When I present or work with a client, I explain the tools only accounts to 50% of the equation to successfully fixing a problem.  The other 50% is split between knowledge and practice. Think about it for a moment, anyone can buy a pocket knife, but only a few of us can carve something recognizable out of a block of wood.

NetBeez provides a very helpful free version of its product so you can get a feel of what it can do and where it might fit into your specific environment.  In the past I would have to figure out how to schedule, report results and then compile them for a report. Any one of those challenges would immediately turn off most analysts since we have plenty on our plates already.

Look at good old ping for a moment. Sure anyone can ping something

I tested the free virtual appliance, which you can find here https://netbeez.net/product/plans/netbeez-free. The free version supports; one agent, three targets, 1 user, Cloud server account, SMTP alerts, 1 and week data storage which is plenty for me and some of my clients who tried it.

Setup is pretty simple, go to NetBeez and create a cloud account and download their ova file. I used VMWARE workstation with no issues.

Some of the measurements that I tested are:

  • PING, Packet Loss, Round-Trip Time,
  • TCP-based PING test, Round-Trip Time, Packet Loss, Custom port numbers

Continue reading "NetBeez Quickstart (by Tony Fortunato)" »

LMTV LIVE | Distributed Network Monitoring with Raspberry Pi (with Panos Vouzis of NetBeez)

YouTube LIVE start time: Wednesday, August 9, 2017 - 9: 30 AM (PST)

Netbeez Single-board computers, like the Raspberry Pi or Odriod, are getting widespread adoption within the network engineering community thanks to their computational power (approximately 1 GHz) and low cost (less than $50 per unit). As a result, more and more companies are deploying these devices within their enterprise networks and using them as monitoring sensors to collect analytics on network performance, wireless networks, and cloud services.

Panos Vouzis is a cofounder of NetBeez which provides network performance monitoring designed for network managers primarily interested in early fault detection and quick troubleshooting of complex wide area networks.

Click to read other LMTV posts by contributors of LoveMyTool »

Distributed network monitoring with IP SLA (by Stefano Gridelli)

Distributed network monitoring with IP SLA!

The Cisco IP Service Level Agreement (IP SLA) technology is nothing new to network engineers. In its basic operations, IP SLA enables routers and switches to use a protocol like ICMP to check end-to-end response time between the device itself and a destination IP device.

Ip-sla-ciscoClick on images to enlarge!

As stated in the Cisco IP SLA configuration guide, “IP SLAs uses active traffic monitoring—the generation of traffic in a continuous, reliable, and predictable manner—for measuring network performance”.

One of the most common uses of IP SLA is configuring floating static routes to determine the preferred active link or, in HSRP, to assure that the router with the highest priority to take over that gateway function has access to the default route.

Continue reading "Distributed network monitoring with IP SLA (by Stefano Gridelli)" »

What to Look for in a Network Monitoring Tool (by Stefano Gridelli)


Before working on NetBeez with my team, I was a system administrator for many years and then a network engineer. In both positions, I had to select, configure, and maintain a variety of network monitoring tools for various purposes: server monitoring, network management and monitoring, and application troubleshooting. This experience gave me a clear understanding of how monitoring tools differ.

If you are in the market for a network monitoring tool, you will quickly notice that there are a lot of choices. Probably hundreds of them, and choosing the right one is not easy .. Following are some things to consider when selecting a network monitoring tool.

First, you must be aware that there are three major categories of network monitoring tools: SNMP-based, flow-based, and active/synthetic.

Continue reading "What to Look for in a Network Monitoring Tool (by Stefano Gridelli)" »

LMTV Interop | Mike Pennacchi (with Stefano Gridelli of Netbeez)

Please join us LIVE on Wednesday, April 27, 2016 at 9:30 AM PST

Interop2016B_170x400Mike-Headshot-20percent This Wednesday we will have a chat with +Mike Pennacchi who had taught at Interop for the last 19 years, a well-known author, trainer and industry network technical analyst.

Specifically, at next week's Interop Las Vegas, Mike will teach two classes, "Divide and Conquer: A Structured Approach to Network Troubleshooting" and "The Killer Toolset Every Network Engineer Needs".

Appearing on the show will be our special guest, +Stefano Gridelli, Co-founder & CEO of +NetBeez.

To help us build our community, please share this live event with your fellow professionals on LinkedIn. For more episodes of LMTV, please visit LoveMyTool.TV. In addition, for more LoveMyTool articles and videos related to Interop, please click here.

Distributed Command Line Interface for EASY Distributed Testing! (by Panos Vouzis)

Distributed Command Line Interface - Easy Distributed Testing!

In the best case scenario, you will need to troubleshoot a networking issue at the same location you are. This is rarely the case though. In most cases, you will receive a ticket about an issue affecting a user at a remote location. In these cases, the network engineer's best friends are command line utilities such as ping, traceroute, and iPerf.

Let’s take the scenario in which a user in Austin opens a ticket  about how he can’t access an application that runs at your data center in Scottsdale, which is where you are located. A ping and a traceroute from Scottsdale to Austin gets you started with troubleshooting, but what you really need is the ping and traceroute from Austin towards your data center in Scottsdale.

And if you are able to walk an employee in Austin through the steps to run a ping and a traceroute command on a console and send you the results, it would most likely take you 20 minutes. This is about 19 minutes longer than it would take for you to just run the tests yourself if you’d had access to the machine. Actually this is what many folks do. Today with low-cost platforms such as the Raspberry Pi, this is easier that it used to be.

Netbeez distributed

Deploying and managing dozens of these units can be a hassle. In addition, if you need to troubleshoot multiple locations at the same time, it is cumbersome to log in to one unit, run a ping and traceroute, and then repeat this several times.

Read more about easy Distributed Testing with NETBEEZ!


Continue reading "Distributed Command Line Interface for EASY Distributed Testing! (by Panos Vouzis)" »