---
title: Preseem Poller Hardware Requirements
description: Help Center
---

[Skip to content](https://docs.preseem.com/hardware/poller-hardware-requirements#main-content)

English

Show submenu for translations

[![Preseem Logo Classic](https://docs.preseem.com/hs-fs/hubfs/Preseem%20Logo%20Classic.png?width=150&height=38&name=Preseem%20Logo%20Classic.png)](https://app.preseem.com)

- [Aterlo Blog](https://preseem-467307.hs-sites.com/blog)

Open main navigation

Close main navigation

- [Aterlo Blog](https://preseem-467307.hs-sites.com/blog)
- English
  
  Show submenu for translations
- Contact us

 Contact us

 Hi There! How Can We Help You?

- There are no suggestions because the search field is empty.

1. [Help Center](https://docs.preseem.com/?hsLang=en)
2. [Preseem Hardware](https://docs.preseem.com/preseem-hardware?hsLang=en)

# Preseem Poller Hardware Requirements

The Network Poller collects inventory and performance data from your network elements, such as APs, CPEs, routers, and OLTs. It's separate from the inline appliance, which measures and shapes live subscriber traffic.

Where the poller runs depends on your Preseem version:

- **Preseem 2.x:** The poller must run on a dedicated VM or host, separate from the inline appliance. Running the poller on the inline node isn't supported, because the two compete for CPU, memory, and interface resources. If you're upgrading from Preseem 1.x, your previous Preseem node can serve as the poller until a dedicated VM is ready.
- **Preseem 1.x:** The poller can run on the inline appliance, but it shares that system's resources and may affect performance. On busier or larger networks, a dedicated poller is recommended.

**Prerequisites for a Dedicated Poller**

- Virtualization platform: VMware, Hyper-V, VirtualBox, or any other standard hypervisor is supported.
- A minimum of 5 Mbps of available upload bandwidth to send metrics data to Preseem Cloud (varies with element count and polling mix).
- Layer 3 reachability from the poller to every device it will poll (APs, CPE, routers, OLTs, and related infrastructure), from a central point in the network with reliable access to each device's management plane.
- Remote management access (a reachable IP plus login credentials) so Preseem support can perform initial setup and configuration.

**Poller Hardware Sizing**

The following are starting-point guidelines based on element count. Exact requirements vary with polling mix, vendor types, enabled features, and network complexity.

| **Estimated Element Count** | **CPU** | **RAM** | **Disk** |
| --- | --- | --- | --- |
| Up to ~1,500 | 8 cores | 8 GB | 64 GB |
| ~1,500 to 10,000 | 8–12 cores | 16 GB | 64–128 GB |
| ~10,000 to 60,000 | 16 cores | 16–32 GB | 128 GB |
| ~60,000 to 300,000 | 16–32 cores | 32 GB | 128–256 GB |
| 300,000+ | 32 cores | 32+ GB | 256 GB |

If your polling mix is heavier than average, size toward the upper end of each range. For deployments over 300,000 elements, size conservatively.

**Setup and SNMP Support**

Once you provide access to the VM, Preseem Support installs and configures the poller software. Some vendor integrations also need an additional agent, which Support installs where required.

If you're moving from an existing poller, Support copies its configuration to the new poller, including SNMP communities and element credentials. Before switching over, Support also confirms the new poller collects the same data as the old one.

SNMPv3 is supported on a limited, case-by-case basis. If your deployment requires it, contact Preseem Support.

- [Preseem Overview](https://docs.preseem.com/preseem-overview?hsLang=en)
- [Getting Started with Preseem](https://docs.preseem.com/getting-started-with-preseem?hsLang=en#main-content)

    - [Deploying Preseem](https://docs.preseem.com/getting-started-with-preseem?hsLang=en#deploying-preseem)
    - [Mapping the Network Topology](https://docs.preseem.com/getting-started-with-preseem?hsLang=en#mapping-the-network-topology)
    - [Enforcing Plan Speeds](https://docs.preseem.com/getting-started-with-preseem?hsLang=en#enforcing-plan-speeds)
- [Using Preseem](https://docs.preseem.com/using-preseem?hsLang=en#main-content)

    - [How to Use Preseem to Troubleshoot Subscriber Issues](https://docs.preseem.com/using-preseem?hsLang=en#how-to-use-preseem-to-troubleshoot-subscriber-issues)
    - [Operations](https://docs.preseem.com/using-preseem?hsLang=en#operations)
    - [How to Use Preseem to Optimize QoE](https://docs.preseem.com/using-preseem?hsLang=en#how-to-use-preseem-to-optimize-qoe)
    - [Preseem's RF Scoring and Metrics](https://docs.preseem.com/using-preseem?hsLang=en#preseems-rf-scoring-and-metrics)
- [Preseem Hardware](https://docs.preseem.com/preseem-hardware?hsLang=en#main-content)

    - [Legacy Hardware](https://docs.preseem.com/preseem-hardware?hsLang=en#legacy-hardware)
- [Administering Preseem](https://docs.preseem.com/administering-preseem?hsLang=en#main-content)

    - [Upgrades](https://docs.preseem.com/administering-preseem?hsLang=en#upgrades)
    - [Planning and Configuration](https://docs.preseem.com/administering-preseem?hsLang=en#planning-and-configuration)
    - [Troubleshooting](https://docs.preseem.com/administering-preseem?hsLang=en#troubleshooting)
    - [User Management](https://docs.preseem.com/administering-preseem?hsLang=en#user-management)
- [Integrations](https://docs.preseem.com/integrations?hsLang=en)
- [Release Notes](https://docs.preseem.com/release-notes?hsLang=en#main-content)

    - [Archived Release Notes](https://docs.preseem.com/release-notes?hsLang=en#archived-release-notes)
- [FAQs and Other Explanations](https://docs.preseem.com/faqs-and-other-explanations?hsLang=en)
- [Amplify AI - Support Assistant](https://docs.preseem.com/amplify-ai-support-assistant?hsLang=en)

- [Aterlo Blog](https://preseem-467307.hs-sites.com/blog)

[![Chill listening crop-3](https://docs.preseem.com/hs-fs/hubfs/Preseem_logo_large.png?width=80&height=30&name=Preseem_logo_large.png "Chill listening crop-3")](https://preseem.com/)

Copyright © 2026, Preseem (Aterlo Networks)