Networks & Sites
A collector only monitors the networks you assign to it. This keeps each collector focused on the equipment it can actually reach, and it’s the boundary that controls what a collector is allowed to scan and connect to.
Assign networks to a collector
Section titled “Assign networks to a collector”- Go to Configure → Sites & Networks.
- Pick (or create) the site, then add a network to it — an IP range in
CIDR form, such as
192.0.2.0/24or198.51.100.0/24. - Open that network and select Assign Collector, then pick the collector that should watch it.
You can see which networks are already assigned to a given collector on its Overview tab under Configure → Collectors.
Assigning a network sets the boundary, not the activity: reachability checks, metric polling, and discovery scans all stay inside the ranges you assigned, and never reach outside them.
What actually runs inside that boundary is up to the collector’s services, and on a newly enrolled collector every one of them starts switched off. Until you turn on Monitor, nothing is checked for reachability; until you turn on Poller, no metrics are collected; until you turn on Discovery, no scan runs. A collector with networks assigned and its services still off looks perfectly healthy and collects nothing. See Collector Services for what each one does and how to turn it on.
Organise by site
Section titled “Organise by site”When you monitor more than one location, give each site its own collector and assign that site’s networks to it. This keeps things tidy and ensures traffic stays local to each site.
| Site | Collector | Assigned networks (example) |
|---|---|---|
| Headquarters | hq-collector |
192.0.2.0/24 |
| Branch — Boston | bos-collector |
198.51.100.0/24 |
| Branch — Austin | aus-collector |
203.0.113.0/24 |
You can select the current site from the site picker at the top of GridNMS to focus dashboards, inventory, and events on one location.
Per-network settings
Section titled “Per-network settings”Opening a network gives you more than its collector assignment. Each network carries its own scanning and host-name settings, so you can be thorough on a server VLAN and leave a guest range alone.
Application Port Scanning
Section titled “Application Port Scanning”Enable port scanning on this network is the permission. Nothing scans the network until it is on — not a scheduled sweep, and not a whole-network discovery you start yourself.
Scheduled scans is the separate choice of whether to also scan the network automatically. Leave it off to keep the permission without a recurring sweep: nothing is scanned until you ask for it. Turning port scanning off turns the schedule off with it, so switching the permission back on later does not quietly restart recurring scans.
Scanning a whole network on demand needs the network’s collector on version 0.67 or later; scheduled sweeps and single-host scans work on any version. See Discovery.
With both on, two more settings apply:
- Scan interval — how often the sweep runs: every 5, 15 or 30 minutes, hourly (the default), every 6 hours, or every 24 hours. Pick the longest interval that still catches the changes you care about; a short interval on a large range is a lot of traffic for little extra news.
- Probe Profile — how deep each sweep goes, which ports it tries, and whether it reads service banners. Every network starts on Standard. See Probe Profiles for what each profile does.
What the scans find appears under Applications and Hosts.
Host names
Section titled “Host names”DNS lookups for hosts resolves the addresses found on this network into names, and works whether or not the network is scanned on a schedule. It is off until you turn it on, and you can optionally name a DNS server for the network’s collectors to ask instead of the one each collector’s own machine uses. See Hosts for the detail.
Replacing or deleting a collector
Section titled “Replacing or deleting a collector”A log forwarder’s credential belongs to the forwarder, not to the collector it enrolled through, so log forwarders keep working when you delete that collector and do not need to be re-enrolled. This is true even when you delete the last collector at a site: the forwarders’ credentials are kept, and a collector you add to the site later accepts them.
The forwarders do not move on their own, though. Each one still points at the collector you
deleted, so until you point it at the replacement they have nowhere to deliver their logs.
Add the replacement collector promptly, then on each affected host run
gridnms-forwarder update_config --collector-host=<new-host> (see
Pointing a forwarder at a different collector).
No new token is needed. Deleting a forwarder, by contrast, revokes its credential and locks
out the host it runs on until that host is enrolled again.
Which collector handles a device?
Section titled “Which collector handles a device?”GridNMS decides automatically, and in most cases you never have to think about it:
- A device whose IP falls inside a network with one assigned collector is polled by that collector.
- A device whose network has several assigned collectors is spread automatically across them, and re-balanced if one goes down.
- A device outside every assigned network has no active-polling collector — it’s passive-only: syslog and traps sent to any collector still arrive and are ingested, but nothing checks reachability or polls it for metrics.
If you need different behavior — always use one specific collector for a network or device, or add a dedicated standby collector for failover — that’s what a Collector Profile is for. Every account starts with a default policy that handles the common case above with no setup required.
- Overlapping ranges across collectors can make routing ambiguous — keep assignments distinct per site.
- Adding a new subnet later? Add it under Configure → Sites & Networks and assign it to the right collector — no reinstall needed.
Related
Section titled “Related”- What Is a Collector?
- Installing a Collector
- Collector Profiles — control which collector actively polls a device, and its failover behavior.
- Network Discovery
docs built 2026-11-12 · 945a2dec2