Prerequisites for installing the On-Premise Poller

To monitor your internal network and resources behind a firewall, you need to install the On-Premise Poller within your network. You can install the On-Premise Poller on physical or virtual machines. 

System requirements: 

The machine on which the On-Premise Poller will be installed should meet the below requirements: 

RAM	16GB (A minimum of 12GB of memory is required apart from the memory consumed by the OS and other processes)
Processor/ Virtual Processor	8 processors/ 16 Virtual Processors
Processor Speed	2.5GHz or above
Disk Space	100GB or higher
OS	Windows or Linux Note: Webpage Speed (Browser) monitoring is available only on Linux. To set it up, please refer to configuring the On-Premise Poller for synthetic (browser) monitors. The On-Premise Poller is currently incompatible with ARM-based machines.
OS Type	64-bit

Table 1: System requirements for installing the On-Premise Poller.

The On-Premise Poller needs to be started with root or Administrator privileges after installation, depending on whether the machine OS is Linux or Windows. 

If the On-Premise Poller is installed in a secure network, make sure you allow access to these domains and ports in your firewall to facilitate communication with the Site24x7 central server.

The requirements for an On-Premise Poller might differ slightly according to the specific type of monitoring you require. 

Additional requirements for network monitoring

Number of On-Premise Pollers required to monitor your network
We recommend using dedicated On-Premise Pollers to monitor your networks. 
The number of On-Premise Pollers required to monitor your networks might vary based on the number of resources to be monitored. Use this calculator to find out the number of On-Premise Pollers that you will require. 

1. Network monitoring capacity: One On-Premise Poller (with the specifications defined above) can support monitoring for up to 1,500 network devices, 10,000 interfaces, and 10,000 performance counters with a 15-minute polling interval.
   
2. Network traffic monitoring capacity: Flow rate: Supports 20K to 40K flows per second.

Ports to be allowlisted: 

The following ports need to be included in the allowlist for both the network's firewall (if applicable) and the firewall of the machine hosting the On-Premise Poller: 

Port	Protocol	Description	Inbound/ Outbound/Bidirectional	Used for
161	UDP	SNMP commands and messages	Bidirectional	SNMP-based monitoring
162	UDP	SNMP Trap Receiver port	Inbound	SNMP-based monitoring
9996	UDP	NetFlow Listener Port	Inbound	NetFlow Analyzer
22	SSH	SSHD port The default SSH service is used for remote login to the device on which the On-Premise Poller is installed.	Bidirectional	Network Configuration Manager (NCM)
23	Telnet	Telnet port The default Telnet service is used for remote login to the device on which the On-Premise Poller is installed.	Bidirectional	NCM
69	TFTP	TFTP port	Bidirectional	NCM
135	TCP	WMI	Outbound	WMI monitoring
1025 to 5000	TCP	WMI	Bidirectional	Windows 2000, Windows XP, and Windows Server 2003
49152 to 65535	TCP	WMI	Bidirectional	Windows Server 2008 and later versions, Windows Vista and later versions

Table 2: Additional ports to be allowlisted.

In addition, ports 8060 (Data collection) and 13306 (PostgreSQL Database Port) will also be used for network monitoring. If ports 8060, 9996, and 13306 are unavailable, subsequent ports that are free will be identified and used, like 8061, 9997, and 13307, respectively.

For Windows installations, ensure that the necessary folder permissions are granted for the Network Module to function correctly.

Additional requirements for Web Transaction (Browser) and Webpage Speed (Browser) monitoring

We recommend using dedicated On-Premise Pollers to monitor your Web Transaction (Browser) and Webpage Speed (Browser).

You can monitor up to 40 Web Transaction (Browser) monitors at a five-minute poll interval using one On-Premise Poller with the system requirements mentioned above.

Read on to learn more about additional prerequisites for installing the On-Premise Poller for Web Transaction (Browser) and Webpage Speed (Browser).

• Related Articles

• Synthetic browser module prerequisite and troubleshooting guide for On-Premise Pollers

  Introduction This document provides a structured troubleshooting guide for resolving issues encountered during the download process of On-Premise Poller for Synthetic (Browser) Module. It covers possible statuses, check-up steps, remedies, and ...

• Resolving huge disk space issues with the On-Premise Poller and Network Module

  Often huge disk space results from the heap dump files in the NetworkPlus/bin directory of the On-Premise Poller.  What are HPROF files? HPROF files are used to store Java virtual machine (JVM) memory dumps. When a JVM runs out of memory (OOM), it ...

• Exclude the selective SSH algorithms in On-Premise Poller during SFTP Transfer monitoring

  By excluding SSH algorithms, you can restrict Site24x7 SSH Client from using the excluded algorithm while connecting to the SSH server during SFTP Transfer monitoring. Follow the steps mentioned below for SSH algorithm exclusion in On-Premise Poller ...

• Monitors that require On-Premise Pollers in Site24x7

  Certain monitor types in Site24x7 require the use of On-Premise Pollers for data collection, especially when monitoring internal, firewall-restricted, or private resources. Depending on the type of monitoring, additional modules like the Network ...

• Troubleshoot the Unauthorized user (Error 401) when installing Tomcat plugins

  When installing Tomcat plugins, you may encounter the following error: Unauthorized user. Does not have permissions. HTTP Error 401: This error usually occurs when the user accessing the Tomcat Manager application does not have the necessary ...