Table of Contents

Pollers: Overview, Deployment Strategy & Setup

Jennifer Trower Updated by Jennifer Trower

Read Time: 7 mins

A poller is a server that sits inside your network. It monitors the equipment deployed on your accounts and network sites, and it sends that data back to your Sonar instance. Pollers collect data with SNMP and ICMP. They also work out which subscriber equipment is connected to which network site equipment, and Sonar uses that to draw your Pulse maps.

This article covers what a poller needs, where to deploy it, and how to set it up. Setup happens in two places: your Sonar instance and the poller's own web interface.

Prerequisites

Before you set up a poller, you'll need:

  • A server or virtual machine running Ubuntu 24.04 Server Edition that meets the hardware requirements below.
  • Network access from the poller to the devices you want to monitor, and outbound HTTPS access from the poller to your Sonar instance.
  • Subnets configured in Sonar's IPAM. Pollers are assigned to subnets, not to individual devices. To learn more, see the IPAM: Overview article.
  • Monitoring templates for the inventory models you intend to monitor. To learn more, see the Building a Monitoring Template article.
Pollers don't return any data while your instance is in test mode. You can tell your instance is in test mode when an orange banner is pinned to the top of the window.

Permissions

Before getting started with the feature, your user roles will need to be adjusted to account for the permissions required to use the Pollers feature.

If you're a Super Admin, you already have full access and no changes are needed. To learn more, see the User Role Creation & Best Practices article.
Entity
Permission
Reason
Poller
View all pollers
View your pollers, their last poll times, and each poller's API key.
Poller
Create a poller
Create a new poller in your Sonar instance.
Poller
Update a poller
Change a poller's name, assigned subnets, or subnet priorities.
Misc
Update poller configuration settings
Set the account and infrastructure polling intervals in Poller Settings.

What is a Poller?

A poller is a dedicated server that collects monitoring data from your network and delivers it to Sonar. Sonar tells the poller which devices to monitor and what to collect from each one, based on the subnets assigned to the poller and your monitoring templates. The poller then checks each device using:

  • ICMP (ping): whether the device responds, plus its latency and packet loss.
  • SNMP: device details, interface statistics, and connection data. Sonar uses the connection data to link subscriber equipment to network site equipment in Pulse.

Hardware requirements

Component
Recommended minimum
Operating system
Ubuntu 24.04 Server Edition, on bare metal or a virtual machine
CPU
2 cores (dual-core CPU released 2011 or newer)
Memory
4 GB RAM
Storage
20 GB

How many devices can one poller handle?

A single poller with adequate resources can typically monitor 1,000 to 2,000 devices. Real-world performance depends on your network layout and the equipment you have deployed, so some networks will see less.

If your network has 3,000 or more devices, we recommend running two or three pollers rather than one larger server.

Deployment Strategy

Host your pollers inside your own network, as close as possible to the devices they monitor. You can host a poller with a cloud provider such as AWS, Azure, or DigitalOcean, but we don't recommend it for two reasons:

  • Faster, more accurate results: devices respond more quickly to a nearby poller, which gives you more accurate monitoring data.
  • Better security: keeping polling traffic on your own network avoids exposing SNMP and device access to the internet.

If your network covers a large area, deploy several pollers and place each one near the devices it monitors. Assign each poller only the subnets in its area.

Instructions on how to install the Poller on a Virtual Machine can be found on our GitHub here.

Setting up a poller

Setup has four parts: create the poller in Sonar, install it on your server, connect it to Sonar, and set your polling intervals.

Step 1: Create the poller in Sonar

To create a poller in Sonar, go to

The Pollers page in Sonar Settings. Callouts show the Settings gear in the sidebar (1), Monitoring expanded in the settings menu (a), Pollers selected under Monitoring (b), and the Create Poller button at the top right (2). The pollers table shows columns for ID, Name, Enabled, API Key, Results Last Received, SNMP Time Taken, Last Account Poll, Last Infrastructure Poll, and Version.
  1. Navigate to Settings > Monitoring > Pollers.
  2. Click Create Poller.
  3. Enter a Name. A good rule of thumb is to name the poller after its location or the subnets it polls.
    The Create Poller window with the Enabled checkbox selected and the Name field set to "Poller 1 Demo." Below is a Subnets list grouped by parent subnet, each group with All / None buttons. One subnet in the Infrastructure group and one in the Public Subnet #1 group are selected, each with a priority dropdown set to 5. Cancel and Create buttons are at the bottom.
  4. Select the subnets this poller should monitor. To select or clear every subnet at once, use the All / None buttons.
  5. Set a priority for each selected subnet (see Subnet priority below).
  6. Save the poller.

If you already have other pollers, the Create Poller window shows “Currently Used By” under any subnet; another poller is already monitoring, along with that poller's name.

Subnet list in the Create Poller window under Public Subnet #1 (107.152.0.0/16), with All / None buttons. The A-001 DATA (107.152.82.0/25) subnet shows a highlighted label reading "Currently Used By: Poller 1 Demo." Each subnet has a checkbox and a priority dropdown set to 5.

By checking off additional boxes, you can add more subnets to be polled by that poller.

After you click Create, you return to the Pollers list. Copy the poller's API key from this list, because you'll need it in Step 3. The status columns stay blank until the poller connects in Step 3.

The Pollers list showing one poller, Poller 1 Demo, with Enabled set to Yes. Its API key is highlighted in the API Key column. The Results Last Received, SNMP Time Taken, Last Account Poll, Last Infrastructure Poll, and Version columns are empty because the poller hasn't connected yet. An Edit button is on the right of the row.
Treat the poller API key like a password. Anyone who has it can send monitoring data to your instance as that poller.

Subnet priority

Sonar monitors only one IP address per inventory item. When an item has more than one IP address assigned, Sonar picks one to send to the poller as the polling target, and all monitoring for that item runs through that address.

Multiple IP addresses in the same subnet

If an item has more than one IP address in the same subnet, the most recently created IP assignment becomes the polling target. Subnet priority doesn’t apply in this case.

Adding another IP address to an item that’s already being monitored changes which interface Sonar polls. If the new address doesn’t respond to the poller the same way the original one did, the item reports as Down.
If you need to monitor more than one interface on the same device, create a separate inventory item for each interface, and assign each item its own IP address.

Multiple IP addresses in different subnets

If an item’s IP addresses are in different subnets and the poller monitors more than one of them, subnet priority decides which address is used. Each subnet on a poller has a priority from 1 (highest) to 10 (lowest), and the poller uses the address from the subnet with the highest priority, meaning the lowest number.

For example, a device might have one address in a management subnet set to priority 1 and another in a subscriber subnet set to priority 5. The poller monitors that device through its management address.

Step 2: Install the poller

On your Ubuntu 24.04 server, run the following commands:

wget https://raw.githubusercontent.com/SonarSoftwareInc/poller/master/setup.sh
chmod +x setup.sh
sudo ./setup.sh

The poller installs and starts automatically. For full installation details, see the Sonar Poller repository on GitHub.

Step 3: Connect the poller to Sonar
  1. In a browser, go to https://SERVER_IP, where SERVER_IP is the IP address of your poller server.
  2. Log in with your instance name and your Sonar username and password.
    Poller login page with fields for the instance name, username, and password, and a Sign in button.
  3. Open the Settings tab.
    Poller 3.0.1 Home page with an arrow pointing to the Settings tab.
  4. In Sonar Instance URL, enter only your instance name. The field already includes https:// and .sonar.software. For example, if your instance is https://example.sonar.software, enter example.
  5. In Poller API Key, paste the API key you copied in Step 1.
  6. Click Update..
    Poller Settings tab showing the Sonar Instance URL field, a blurred Poller API Key, the Log all errors option, and the Update button.
The Log all errors option on the Settings tab is for troubleshooting only. Logging every error reduces poller performance, so turn it off when you’re done.

About 5 minutes after you click Update, go to Settings > Monitoring > Pollers in Sonar. Check that Results Last Received, Last Account Poll, and Last Infrastructure Poll show a recent date and time. If they’re still blank, log in to the poller server and restart the poller:

supervisorctl restart sonar_poller
Step 4: Set your polling intervals

Polling intervals apply to all of your pollers. To set them, navigate to Settings > Monitoring > Poller Settings.

  • Account Polling: how often equipment deployed on accounts is polled. Don't set this lower than 5 minutes unless your network is very small.
  • Infrastructure Polling: how often equipment on network sites is polled. We generally recommend 2 to 5 minutes.

Providing Device Credentials in the Poller GUI

By default, the poller collects data over SNMP using the SNMP settings from your monitoring templates. You don’t need to enter SNMP communities in the poller, because Sonar sends them to the poller automatically. For certain device types, you can add login credentials in the poller. The poller then connects to those devices directly, pulls more detailed connection data, and produces more accurate Pulse maps. This step is optional.

  1. In the poller web interface, open the Device Credentials tab.
  2. Click Create.
    Poller Device Credentials tab with callouts on the Device Credentials tab and the Create button.
  3. Choose a Credential Type from the table below.
  4. Enter the Username of an account that already exists on the device.
  5. Enter the Password, then enter it again in Repeat Password.
  6. Enter the Port the poller should use to connect to the device.
  7. Click Save.
    Create Device Credentials window with numbered callouts on the Credential Type, Username, Password and Repeat Password, and Port fields.
Credential Type
Used for
MikroTik API (SSL)
MikroTik devices, using the API over SSL
Netonix SSH
Netonix switches, over SSH
Ubiquiti Toughswitch SSH
Ubiquiti Toughswitch devices, over SSH
Ubiquiti UFiber OLT HTTPS
Ubiquiti UFiber OLTs, over HTTPS
Calix AXOS SSH
Calix AXOS devices, over SSH
Create Device Credentials window with the Credential Type dropdown open, listing MikroTik API (SSL), Netonix SSH, Ubiquiti Toughswitch SSH, Ubiquiti UFiber OLT HTTPS, and Calix AXOS SSH.
You can add one credential per credential type. The poller uses that credential for every matching device it monitors, so the same username, password, and port must work on all of them. Each device must also be reachable from the poller on that port.

Poller Troubleshooting

If your poller isn’t returning data, or devices aren’t appearing in Pulse, see these articles:

Need a hand?

Our Support Team is here to help

How did we do?

Poller Troubleshooting

Troubleshooting Poller and Monitoring Issues