What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Configure probe with multiple core server IPs

Votes:

0

Our PRTG Core is behind a firewall with multiple WAN links. Port-forwarding is configured on the firewall for remote probes to connect in to the core - and this is possible on any of the WAN IP addresses.

However, the probe can only be configured to connect to one of these addresses, from what I can tell.

What I'd like to be able to do is have multiple core server IPs configured in the probe and the probe would cycle through them in case one is down. It would always be connecting to the same core, just via a different path.

Is this possible?

core-probe-connection probe probe-conf

Created on Apr 3, 2017 1:57:18 PM



5 Replies

Votes:

0

Hello alexism,
thank you for your KB-Post.

A Remote Probe can only have a single destination Core Server IP or DNS Address, there's no way to configure multiple Addresses for the probe to connect.

Best Regards,
Luciano Lingnau [Paessler Support]

Created on Apr 5, 2017 1:19:32 PM by Luciano Lingnau [Paessler]



Votes:

0

Ok, thanks - can we raise this as a feature request?

In the meantime we're looking at workarounds, such as using bouncer as an intermediary to round-robin the connections (https://github.com/ggrandes/bouncer).

Created on Apr 5, 2017 1:25:26 PM



Votes:

0

I've talked to the responsible developers, this is not on our roadmap I'm afraid. The number of customers looking for this kind of capability is very low and we would have to make fundamental changes in PRTG to implement this, so we don't see this implementation coming anytime soon. You can read more about how we handle feature requests here:

As for the intermediate round-robin bouncer: We strongly advice against this, this could cause unforeseen consequences to the Core/Probe connection. If this is vital to your business, you could try:

  1. Use a scheduled task to confirm that the Core Server is continuously accessible.
  2. If the used IP becomes unavailable:
    1. Stop the Probe Service
    2. Change the core server address in the registry
    3. Start the Probe Service again

Best Regards,
Luciano Lingnau [Paessler Support]

Created on Apr 6, 2017 1:55:40 PM by Luciano Lingnau [Paessler]

Last change on Apr 6, 2017 2:00:42 PM by Luciano Lingnau [Paessler]



Votes:

0

Thanks for the suggestion, we'll set up a powershell script to do that. Can you point me to the registry key we'd need to change for this?

Created on Apr 6, 2017 2:01:51 PM



Votes:

0

Sure thing!

This is the path:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Paessler\PRTG Network Monitor\Probe

The relevant keys used to define the address of the core server are:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Paessler\PRTG Network Monitor\Probe]
"Server"="server.domain.tld"
"ServerPort"="23560"

Also, you will see some keys like:

"Server1"=""
"ServerPort1"=""
"Server2"=""
"ServerPort2"=""
"Server3"=""
"ServerPort3"=""
"Server4"=""
"ServerPort4"=""
"Server5"=""
"ServerPort5"=""

You may feel tempted to use these. DON'T. There are only for PRTG Clusters, just "leave them be" (unset).

Created on Apr 7, 2017 12:21:52 PM by Luciano Lingnau [Paessler]




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.