How to configure IPNetwork in case of high latency when connecting target network?
Q: We have a problem: high latency issues between our two buildings connected by wireless. We are getting incorrect results, because of ping times becoming so long sometimes the system rightfully flags the associated systems as being down. Can I set up a second IPNetwork system in the second building and just have it report back to the main IPNetwork server with the information from the second building?
A: Solution is to use Remote Network Agent. This piece of software resides inside network, the device(s) of which you need to monitor, and communicates with primary installation of IPNetwork Monitor to send monitoring data.
Install RNA on a suitable server or a workstation in the second building. Set up monitoring as specified in the manual – How to configure distributed monitoring with Remote Network Agents.
RNA will perform the monitoring of selected devices and transfer the results to the main IPNetwork (to the first building). This will allow avoiding delays in the wireless connection during monitoring.
Related topics
Do I have to install Remote Network Agent on every server to monitor all our branches?
Check out our Knowledge Base where we answer questions regarding various topics. The agent runs inside the remote network and performs local polling there, then sends results back to the main IPNetwork installation. Install it on a suitable server or workstation inside the second building so monitoring traffic stays local to that network. No. The agent collects monitoring results in the remote network and reports them to the primary IPNetwork Monitor installation.
Frequently Asked Questions
How does a Remote Network Agent help with high latency links?
Where should the Remote Network Agent be installed for a second building?
Does the Remote Network Agent replace the main IPNetwork server?