Setup cases

Depending on the system’s architecture some changes need to be made. If you are using a free version of PRTG, you are limited to 100 sensors, so you need to choose which sensors to keep in order to monitor the most important components of the system.

In this article you can see configurations for some architectures. Keep in mind that the large the environment, less sensors will be available per device, so there will be a need to prioritize the sensors in order to get the best coverage of your system.

 

 

Single Environment (with SQL Server on Another Server)

In this case we have two servers, one with all the OneContact’s components and another with the SQL server installed:

Server IP DNS Name
Server 1 10.10.0.10 Server1
Server 2 10.10.0.11 Server2

 

To monitor this environment, create two devices to monitor each server:

Server/Cluster Role Sensors
Server1 (10.10.0.10) Windows Server / OneContact
Server2 (10.10.0.11) Windows Server / SQL Server

 

 

 

Full-Clustered Environment (with SQL Server)

In this case we have two servers on a cluster with all the OneContact’s components and the SQL server installed:

47_cases.png

We have two servers:

Server IP DNS Name
Server 1 10.10.0.10 Server1
Server 2 10.10.0.11 Server2

 

The cluster groups will have the following services and IPs:

Group Components IP
B2B Group

OneContactCallControl

OneContactNotifier

OneContactTimer
10.10.0.1
Service Group

OneContactBaseService

OneContactService

OneContactScriptingService
10.10.0.2
Media Group

OneMedia

OneMediaCompressor

OnePark
10.10.0.3
Proxy Group OneProxy 10.10.0.4
Statistics Group

OneContactService (Statistics)

OneContactImporter
10.10.0.5
Web Group

OneContactWebServicesHost

OneAdmin

OneSupervisor

OneAgentWeb

OneContactOLAPHost

OneContactBaseServiceHost
10.10.0.6
SQL Server SQL Server 10.10.0.7

 

To monitor this environment, create two devices to monitor each server and seven devices to monitor each component on the cluster.
When creating the devices insert the IP or name of each server/cluster group and use the correct template when importing the template to that device (following the table bellow):

Server/Cluster Role Sensors
Server1 (10.10.0.10) Windows Server
Server2 (10.10.0.11) Windows Server
B2B Group OneContact
Service Group OneContact
Media Group OneContact
Proxy Group OneContact
Statistics Group OneContact
Web Group OneContact
SQL Server SQL Server

 

Note: After using the correct template there will be duplicated sensors on each device, so you will need to delete all of the sensors of services that aren’t on the clusters roles. For example, B2B Group should only have sensors for OneContactCallControl, OneContactTimer and OneContactNotifier.

 

 

 

Full-Clustered Environment (SQL Server in Different Cluster)

In this case we have two clusters, each with two servers, for all the OneContact’s components and the SQL server components:

48_cases.png


We have two servers:

Server IP DNS Name
Server 1 10.10.0.10 Server1
Server 2 10.10.0.11 Server2
Server 3 10.10.0.12 Server3
Server 4 10.10.0.13 Server4

 

The cluster groups will have the following services and IPs:

Group Components IP
B2B Group

OneContactCallControl

OneContactNotifier

OneContactTimer
10.10.0.1
Service Group

OneContactBaseService

OneContactService

OneContactScriptingService
10.10.0.2
Media Group

OneMedia

OneMediaCompressor

OnePark
10.10.0.3
Proxy Group OneProxy 10.10.0.4
Statistics Group

OneContactService (Statistics)

OneContactImporter
10.10.0.5
Web Group

OneContactWebServicesHost

OneAdmin

OneSupervisor

OneAgentWeb

OneContactOLAPHost

OneContactBaseServiceHost
10.10.0.6
SQL Server SQL Server 10.10.0.7

 

To monitor this environment create four devices to monitor each server and seven devices to monitor each component on the cluster.
When creating the devices insert the IP or name of each server/cluster group and use the correct template when importing the template to that device (following the table bellow):

Server/Cluster Role Sensors
Server1 (10.10.0.10) Windows Server
Server2 (10.10.0.11) Windows Server
Server3 (10.10.0.12) Windows Server
Server4 (10.10.0.13) Windows Server
B2B Group OneContact
Service Group OneContact
Media Group OneContact
Proxy Group OneContact
Statistics Group OneContact
Web Group OneContact
SQL Server SQL Server

 

Note: After using the correct template there will be duplicated sensors on each device, so you will need to delete all of the sensors of services that aren’t on the clusters roles. For example, B2B Group should only have sensors for OneContactCallControl, OneContactTimer and OneContactNotifier.

 

 

 

Clustered and Balanced Environment (SQL Server in Cluster)

In this case we have a cluster, with two servers, for some of the OneContact’s components and the SQL server components. There are also two servers for other balanced OneContact’s components:

49_cases.png 

We have two servers:

Server IP DNS Name
Server 1 10.10.0.10 Server1
Server 2 10.10.0.11 Server2
Server 3 10.10.0.12 Server3
Server 4 10.10.0.13 Server4

 

The cluster groups will have the following services and IPs:

Group Components IP
B2B Group

OneContactCallControl

OneContactNotifier

OneContactTimer
10.10.0.1
Proxy Group OneProxy 10.10.0.4
Statistics Group

OneContactService (Statistics)

OneContactImporter
10.10.0.5
SQL Server SQL Server 10.10.0.7

 

The remaining services will be balanced on server 3 and server 4 (OneContactBaseService, OneContactService, OneContactScriptingService, OneMedia, OneMediaCompressor, OnePark and Web Applications).
To monitor this environment create four devices to monitor each server and four devices to monitor each component on the cluster.
When creating the devices insert the IP or name of each server/cluster group and use the correct template when importing the template to that device (following the table bellow):

Server/Cluster Role Sensors
Server1 (10.10.0.10) Windows Server
Server2 (10.10.0.11) Windows Server
Server3 (10.10.0.12) Windows Server
Server4 (10.10.0.13) Windows Server
B2B Group OneContact
Proxy Group OneContact
Statistics Group OneContact
SQL Server SQL Server

 

Note: On the balanced devices (server 3 and server 4) you will need to use also the OneContact’s sensors, in order to monitor the OneContact components on those servers. Since they will be running in parallel the sensors are active on both devices.