<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: Failover Cluster Step by Step

This section guides you through the step-by-step process to set up a failover cluster. Follow these instructions carefully to successfully integrate two or more PRTG core servers into one failover cluster.

i_round_redBefore you start, make sure that you consider the information in section Failover Cluster Configuration.

i_podThis feature is not available in PRTG Hosted Monitor.

In this section:

Step 1: Install the PRTG Core Servers

First, you need two separate PRTG core server installations. Use the same license key for both PRTG core server installations.

If you already have a PRTG core server, this is your future master node. In this case, set up an additional PRTG core server installation.

Before you set up a cluster, make sure that all (future) cluster nodes run the exact same PRTG version (build number). Install updates if necessary.

i_round_blueOnce you establish the cluster, any updates that you install on a cluster node are automatically deployed to all other cluster nodes.

i_square_cyanFor details about the installation process, see section Install a PRTG Core Server.

Step 2: Configure the Master Node

Decide which of your PRTG core server installations is your future master node. If you have an installation of PRTG in your network that has been running for some time, this should be your master node so that you keep your monitoring configuration.

On the master node, from the Windows Start menu, open the PRTG Administration Tool. On the Cluster tab, click the following button:

Create a Cluster

  • Click Create a Cluster to create a cluster. The current PRTG core server is then the master node of the cluster.
  • Click Yes to convert this installation to a master node.
Converting an Installation to a Master Node

Converting an Installation to a Master Node

  • A dialog box appears.
Creating a Master Node

Creating a Master Node

  • Enter a Cluster Port. This is the port on which PRTG sends the internal communication between the cluster nodes. Make sure that connections between the cluster nodes are possible on the port that you select.
  • Enter or paste a Cluster Access Key. This is a unique access key. All cluster nodes must use the same cluster access key to join the cluster. Connection attempts with a different access key are not possible.
    i_round_blueWe recommend that you use the default value.
  • Save the Cluster Access Key so that you have it at hand when you configure the failover nodes.
  • After confirming your settings, you are asked to restart Windows services. Click OK to restart the Windows services so that your changes take effect.
Restart Services to Apply Changes

Restart Services to Apply Changes

Step 3: Configure the Failover Node

On the failover node, open the PRTG Administration Tool. On the Cluster tab, click the following button:

Join a Cluster

  • Click Join a Cluster to add this installation to a cluster that already has a master node. The current PRTG core server is then a failover node.
  • This button is also available if the PRTG core server is in Cluster Mode: Master Node. This option then changes the master node to a failover node.
  • Click Yes to convert this installation into a failover node.
Converting an Installation to a Failover Node

Converting an Installation to a Failover Node

  • A dialog box appears.
Cluster Connection Setup

Cluster Connection Setup

  • Enter a Master Node (IP address/DNS name) for the cluster. It must be reachable from the machine that runs the failover node.
  • Enter the other settings as defined in the settings of the master node. Make sure that you use the same settings on all cluster nodes.
  • Enter a Cluster Port. This is the port on which PRTG sends the internal communication between the cluster nodes. Make sure that connections between the cluster nodes are possible on the port that you select.
  • Enter or paste a Cluster Access Key. This is a unique access key. All cluster nodes must use the same cluster access key to join the cluster. Connection attempts with a different access key are not possible.
    i_round_blueWe recommend that you use the default value.
  • After confirming your settings, you are asked to restart Windows services. Click OK to restart the Windows services so that your changes take effect.
Restart Services to Apply Changes

Restart Services to Apply Changes

Step 4: Confirm the Failover Node

Now you need to confirm the new failover node by setting it to Active in the master node's settings.

In a browser window, log in to the PRTG web interface of the master node.

In the cluster settings, you see your master node in the first line of the cluster list and your failover node in the second line.

i_round_redIf you use remote probes outside of your local network, for each PRTG core server in the cluster, use a Domain Name System (DNS) name or IP address that the remote probes can reach from the outside. Enter the entries in the Cluster Node Setup table accordingly. The addresses must be valid for both cluster nodes to reach each other and for remote probes to individually reach all cluster nodes. Remote probes outside your LAN cannot reach private IP addresses or DNS names.

System Administration: Cluster Node Setup

System Administration: Cluster Node Setup

For the failover node, set the Node State to Active and Save the changes. The cluster nodes now connect and exchange configuration data. This might take a few minutes.

Step 5: Check the Cluster Connection

In two browser windows, log in to the PRTG web interface of both of your PRTG core servers. Open the Cluster Status tab in both windows. You should see the cluster status with the two cluster nodes in a Connected state after a few minutes.

Cluster Status

Cluster Status

Step 6: Troubleshooting

If the cluster nodes cannot connect, see

  • the cluster log entries on the Cluster Status tab in the PRTG web interface.
  • the PRTG core server log file, a text file in the \Logs subfolder of the PRTG data directory.

In the latest entries of these logs, you can see messages about any errors that might have occurred. These give you hints on where to find a solution.

If you have connection issues with the two cluster nodes, make sure that no software or hardware firewall is blocking communication on the cluster port that you defined during the cluster setup. Communication between the cluster nodes must be possible in both directions for the cluster to work properly.

Step 7: Move Sensors to the Cluster Probe Now

You have successfully set up your failover cluster. All devices that you create or move under the cluster probe are monitored by both cluster nodes.

i_round_redTo monitor your configuration via all cluster nodes, on your master node, move your groups, devices, and sensors from the local probe to the cluster probe. Objects, including their settings, are then automatically transferred to all cluster nodes.

Step 8: Move Custom Content to the Failover Nodes

On startup of the master node, maps and custom lookups are automatically transmitted to the failover nodes. While PRTG automatically synchronizes changes to maps, you must manually (re)load lookups on all cluster nodes. You must also manually copy other custom content from the according subfolders of the PRTG program directory on the master node to the same folders on the failover nodes.

Custom Content

Subfolder of the PRTG Program Directory

Device templates

\devicetemplates

Custom sensors

\Custom Sensors

MIB files

\MIB

SNMP libraries

\snmplibs

Notifications

\notifications

Step 9: Add More Failover Nodes (optional)

If you want to add an additional failover node to your cluster, you need an additional license key to run two and three failover nodes, and two additional license keys to run four failover nodes.

i_round_blueIn a cluster, only PRTG core servers that have the same license type can be combined. To add an additional failover node to the cluster, set up a new PRTG core server on a new machine and use an additional license key. Then proceed with step 3 and following. Use a second license key to set up both the second failover node and third failover node. Use a third license key to set up the fourth failover node. Each failover cluster is technically limited to five cluster nodes: as a maximum, you can have one master node and four failover nodes in one cluster.

i_round_redStay below 2,500 sensors for best performance in a cluster. Clusters with more than 5,000 sensors are not supported. For each additional failover node, divide the number of sensors by two.

More

i_square_blueKnowledge Base

My cluster is messed up. How can I start over?

 

i_square_bluePAESSLER WEBSITE

How to connect PRTG through a firewall in 4 steps