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 configuration given below represents a standard setup for installing the On-Premise Poller. Actual system requirements may vary depending on the number of monitored devices and the monitoring load. For a more accurate estimate based on your environment, use the System Requirements Calculator.
The machine on which the On-Premise Poller will be installed should meet the following 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 core processors/ 16 Virtual Processors |
| Processor Speed | 2.5GHz or above |
| Disk Space | 100GB or higher |
| OS | Windows or Linux 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.
OS compatibility with certain monitors
Understanding the compatibility and scaling limitations of certain monitors within specific operating systems is essential for making informed decisions. Below is the list of monitors that are optimised for better scaling with specific operating systems:
Monitor type | Windows | Linux |
|---|---|---|
❌ | ✅ | |
❌ | ✅ | |
✅ | ❌ | |
✅ | ❌ |
All the other monitors that require an On-Premise Poller are compatible with both Windows and Linux-based operating systems.
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.
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.
- Network monitoring availability: When using the On-Premise Poller for network monitoring, especially for ICMP/ping-based availability checks, the Windows OS may offer better scalability and performance.
- 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.
- 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 | Connection | Purpose / Module | Source | Destination | Remarks |
|---|---|---|---|---|---|---|
8060 | TCP | Inbound to server | Data collection | Internal | Internal | Used for data collection. If port 8060 is unavailable, subsequent ports that are free will be identified and used, like 8061. |
13306 | TCP | Internal | PostgreSQL database | Internal | Internal | Used for internal database communication. External firewall opening is not needed. If port 13306 is unavailable, subsequent ports that are free will be identified and used, like 13307. |
135 | TCP | Outbound from On-Premise Poller | DCOM Communication (WMI) | On-Premise Poller | Monitored Windows Server | Required for the On-Premise Poller to establish the initial DCOM connection with remote Windows servers—a prerequisite for WMI monitoring. |
1025–5000 | TCP | Outbound from On-Premise Poller | WMI monitoring (dynamic–older Windows operating systems) | On-Premise Poller | Monitored device | Used to fetch monitoring data after a DCOM connection (via port 135) is established. Microsoft dynamically assigns ports within this range for WMI on Windows 2000, Windows XP, and Windows Server 2003. Learn more. |
49152–65535 | TCP | Outbound from server | WMI monitoring (dynamic – newer Windows operating systems) | On-Premise Poller | Monitored device | Used to fetch monitoring data after a DCOM connection (via port 135) is established. Microsoft dynamically assigns ports within this range for WMI on Windows Server 2008 and later, and Windows Vista and later. Learn more. |
161 | UDP | Outbound from server | SNMP monitoring | On-Premise Poller | Monitored device | Used by the On-Premise Poller to send SNMP requests to monitored devices. Site24x7 uses a dynamic listening port to receive SNMP responses; monitored devices must have port 161 open. |
162 | UDP | Inbound to server | SNMP traps | Monitored device | On-Premise Poller | Used by the On-Premise Poller to receive SNMP trap messages from monitored devices. |
23 | TCP | Outbound from server | Outbound from server | On-Premise Poller | Monitored device | The On-Premise Poller initiates Telnet sessions to remote servers for CLI monitoring. |
22 | TCP | Outbound from server | CLI monitoring (SSH) | On-Premise Poller | On-Premise Poller | The On-Premise Poller initiates SSH sessions to remote servers for secure CLI monitoring. |
514 | UDP | Inbound to server | Syslog messages | Monitored device | On-Premise Poller | Used to receive general Syslog messages from monitored devices. |
5985 | TCP | Outbound from server | WinRM | On-Premise Poller | DHCP server | Used by Microsoft IPAM to remotely connect to DHCP servers and collect DHCP scope, lease, and utilization information. It also enables IPAM to perform remote DHCP management and monitoring tasks. Required only if the IPAM module is used. |
5986 | TCP | Outbound from server | WinRM | On-Premise Poller | DHCP server | Used by Microsoft IPAM to securely communicate with DHCP servers for collecting DHCP scope, lease, and utilization data. It provides the same remote management capabilities as port 5985 but with TLS/SSL encryption for enhanced security. Required only if the IPAM module is used. |
69 | UDP | Inbound to server | Network Configuration (NCM)Module–TFTP server | Monitored device | On-Premise Poller | Used by the NCM module TFTP server to receive device configuration backups. Required only if the NCM module is configured to use TFTP. |
22 | TCP | Network Configuration Module (NCM)–SCP/SFTP server | Monitored device | On-Premise Poller | On-Premise Poller | Used by the NCM module to receive device configuration backups. Required only if either module is used for backups. |
9996 | UDP | Inbound to server | NetFlow Analyzer module | Devices (routers, switches, firewalls, NPS agents) | On-Premise Poller | Used by the NetFlow Analyzer module to receive network traffic flow data (NetFlow, sFlow, IPFIX, J-Flow, and others) from devices. If port 9996 is unavailable, subsequent ports that are free will be identified and used, like 9997. |
Table 2: Additional ports to be allowlisted.
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).
To set up the On-Premise Poller as a monitoring location for synthetic (browser) monitors, please refer to this guide.
Related article
Related Articles
Troubleshooting steps for On-Premise Poller
Prerequisites and basic details: Prerequisites for installing On-Premise Poller Necessary ports to allow access to the installed On-Premise Poller How secure is On-Premise Poller Amount of bandwidth consumed by the On-Premise Poller software Adding ...Set proxy for Linux On-Premise Poller during installation
There are 3 ways through which you can configure a proxy in an On-Premise Poller for a Linux server. During installation using the Installation Wizard Using the console During the silent installation of the On-Premise Poller Linux agent 1. During ...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 ...Silent installation and uninstallation of Windows On-Premise Poller
Silent installation of an On-Premise Poller on Windows Follow the steps below for the silent installation of an On-Premise Poller on a Windows server: Download the install.iss file. Open the install.iss file in an editor and navigate to line 20. ...How to configure maximum memory (heap size) of the On-Premise Poller
Configure the maximum memory (heap size) of the On-Premise Poller to control how much system memory the application can consume. This helps ensure stable performance and prevents resource exhaustion. Prerequisites Access to the On-Premise Poller ...