--- title: "IT and OT sensor requirements | Lansweeper Platform" slug: "discovery-hub-and-sensor-requirements" description: "Review the requirements for the Lansweeper IT and OT sensor, including hub disk space, sensor hardware, and the firewall ports needed to scan assets." tags: ["Lansweeper Platform", "Discovery and scanning", "Network Discovery"] status: "update" updated: 2026-11-19T21:08:09Z published: 2026-11-19T21:08:09Z canonical: "docs.lansweeper.com/discovery-hub-and-sensor-requirements" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.lansweeper.com/llms.txt > Use this file to discover all available pages before exploring further. # IT and OT sensor requirements Before installing the hub or the IT and OT sensor, ensure your environment meets the following requirements. The hub has its own connection and hardware requirements, which are the same whichever sensor you install. See [Discovery hub requirements](/docs/discovery-hub-requirements). ## System requirements ### Hub disk space Disk space is the one hub requirement that depends on which sensors you connect. For a hub running IT and OT sensors only: | Resource | Minimum for up to 2 sensors | Recommended for up to 5 sensors | Recommended for up to 10 sensors | Recommended for up to 100 sensors | | --- | --- | --- | --- | --- | | Free disk space (SSD) | 1 GB | 10 GB | 50 GB | 500 GB | Traffic sensors need more hub disk space Traffic sensors upload capture files to the hub, so a hub running them needs 10 GB free as a minimum instead of 1 GB. If you plan to connect traffic sensors to the same hub, size the disk using [Traffic sensor requirements](/docs/traffic-sensor-requirements). ### Sensor requirements | Resource | Minimum | Recommended | | --- | --- | --- | | CPU | x64, 1 GHz single-core | x64, dual-core 2 GHz | | RAM | 1 GB | 4 GB | | Free disk space | 500 MB | 1 GB | | Network speed | 100 Mbps | 1 Gbps | ## Firewall and routing requirements | Protocol | Port(s) | Notes | | --- | --- | --- | | RPC endpoint mapper | TCP 135 | Initial WMI and DCOM connection to Windows assets | | SMB | TCP 445 | Windows scanning | | DCOM dynamic range | TCP 49152-65535 | Windows WMI data. Restrict the range via GPO or registry for tighter control | | WinRM | TCP 5985, 5986 | Windows, only for Hyper-V or cluster log collection | | SSH | TCP 22 | Linux, Unix, and macOS assets | | SNMP | UDP 161 | Network devices such as switches and printers | | HTTPS | TCP 443 | Web interfaces on network appliances | ICMP is recommended, not required The sensor uses ICMP (ping) to find active assets before scanning, so allowing ICMP from the sensor across your network makes discovery faster and more reliable. It isn't required: on networks that block ICMP, disable **Ping hosts before scanning** in the discovery action and the remaining checks still run. ## Next steps Now that you understand the requirements, you can install the hub and the IT and OT sensor on [Windows](/docs/install-network-discovery-windows), [Linux](/docs/install-network-discovery-linux), or [macOS](/docs/install-network-discovery-macos). The Network Discovery component that every sensor connects to. The hub holds the sensor configuration, collects the data the sensors gather, and syncs it to your Lansweeper Platform site.