A client with a central office would like to monitor 125 stores. Those stores are network isolates from central office (a simple ADSL) and barely have 3-4 simple devices each. Our idea is use a probe by store with less than 10 sensors by probe.

Paessler documentation reads: Our general recommendation is to stay below 30 remote probes on one PRTG core server.PRTG still scales well up to 60 probes as long as you have less than 100 sensors per probe.

Our question is: would a single core of PRTG be valid or will they have to buy 2 PRTG?

Thanks for your time

Omar.

Article Comments

With that amount of sensors, the amount of remote probes should be no problem.

Kind regards,
Stephan Linke, Tech Support Team


Aug, 2018 - Permalink

Do you recomend all 125 probes in a single core or better split the load in two cores ?

thanks :)


Aug, 2018 - Permalink

It should work with one server. If you want to be on the safe side, use two :)

Kind regards,
Stephan Linke, Tech Support Team


Aug, 2018 - Permalink

Perfect.

Thanks for your time :)

Omar.


Aug, 2018 - Permalink

You're most welcome! :)

Kind regards,
Stephan Linke, Tech Support Team


Aug, 2018 - Permalink

Felix, the number of stores has raised, now we have over 300 so the multicore option is mandatory.

Obviusly, we must dristribute the probes as even as possible betwen the cores but we have just one public static IP where the cores will be deployed, i thought using NAT to assing each core to a unique Public IP:Port but is not totally clear to me if this will work because in the PRTG Network Monitor - PRTG Administration Tool u can specify a Server IP or DNS but if a IP:Port combinations is specified the systems just delete the port and keeps the IP.

So, the main question: it is possible to configure probes to conect a core server using Socket (IP:Port) ?


Sep, 2018 - Permalink

No, but you should be able to do this entirely via Destination NAT, somewhat like this:

[ PROBE SIDE ]
+-----------------+----------------+
| Source          | Target         |
+-----------------+----------------+
| 170.0.0.1:23560 | 171.4.2.1:1100 |
+-----------------+----------------+
                  |
             { internet }
[ CORE SIDE ]     |
+-----------------+----------------+
| Source          | Target         |
+-----------------+----------------+
| 170.0.0.1:1100  | 171.4.2.1:23560|
| 170.0.0.2:1101  | 171.4.2.2:23560|
+-----------------+----------------+

This took longer than I'd like to admit, hope it's useful :)

PRTG Scheduler | PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team


Sep, 2018 - Permalink

Was useful.

Thans for your time Stephan.

Omar.


Sep, 2018 - Permalink