![]() From your PingPlotter machine, launch your web browser and access the agent at agent machine name):7465.To change the port, as well as other settings for the agent, double-click on the tray icon. ![]() Ensure your firewall(s) allow access to the agent on TCP port 7465, or change the server port for the agent.The agent will show up in the system tray. Browse to the directory where you extracted the agent and launch it.Extract the agent (PingPlotter_Remote_Agent.exe) to a working directory (e.g., c:\Program Files\PingPlotter Remote Agent).Download the Windows remote agent from the agent download page.Note: Presently the Windows agent does not come packaged with an installer or uninstaller. This agent can run as an application or as a service under Windows XP or newer. The PingPlotter remote agent for Windows is a self-contained executable that includes a small server and some portions of the PingPlotter core trace engine. Installation instructions Installing the Windows Agent A Windows XP or higher workstation (Windows agent), or a UNIX machine with Apache, perl, and appropriate permissions (UNIX agent).PingPlotter version 3.10.0p or higher, installed.Our summary screen in PingPlotter would look something like this: When using remote agents deployed on machines in both the Amsterdam and Tokyo office, we can now also measure the connection from both of those offices to both the business server, and VoIP server as well - all from the single instance of PingPlotter that's running back at our headquarters in Boise! We can also monitor our connection from the Boise office to our business and VoIP server. With a single instance of PingPlotter running at our Boise office, we already know that we can monitor the connection between us, and the other two offices. Lets say that we have three offices: a "main" office in Boise, a branch in Amsterdam, and one in Tokyo. You can even see the results from multiple remote sources/agents by defining and using Named Configurations. Essentially the only difference is that the trace isn't originating from the workstation running PingPlotter, but instead the agent is allowing you to source and see the traceroute from the vantage point of the machine running the remote agent. When using a remote agent, PingPlotter works and looks *exactly* the same as it does when you're using the local engine. The interval at which PingPlotter contacts the remote agent is controlled by the sampling parameters (trace interval) you've defined locally. ![]() When it receives a request, it does a single traceroute and returns the results back to PingPlotter, which then collects this data and displays it locally like any other trace data. The basic concept of the remote trace agent is that it resides on a remote machine listening for a request for data from your local PingPlotter instance. The Windows agent is fully self-contained (it has its own TCP server and GUI component) and does not require any additional software or server components. The UNIX agent requires perl, a web server, and the traceroute command. PingPlotter is able to initiate trace requests from a remote agent on both Windows and UNIX based machines. PingPlotter's software-based agents let you test hundreds of connections at once, saving you time and money. ![]() With PingPlotter Cloud, seeing a network from another computer's perspective is as simple as clicking a link. There's a better way to test remote networks. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |