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.
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!