ScanopyScanopy
Networking & Deployment

Deploy Daemons Across Several Sites

Place daemons for locations joined by a WAN, SD-WAN or VPN, either one per site or scanning remote sites from a central host.

Each location gets its own site, with its own hosts, subnets and map. See Planning Sites. A daemon belongs to one site, chosen when you create it in Discovery > Daemons, and can't move to another site afterwards. It scans subnets on its own site only. Create the site in Inventory > Sites before you create its daemon.

Cover a remote site with a daemon at the site, or with a daemon on a central host at the main site.

Daemon at each siteCentral host scanning remote sites
Where the daemon runsA host at each siteA host at the main site, with a route to each remote site
Remote subnets scanned atLayer 2Layer 3
MAC addresses at remote sitesCollectedOnly from the ARP tables of SNMP devices at the site
Hosts that answer ARP and nothing elseFoundNot found
Hardware needed at the remote siteOne host that can run the daemonNone

See Interfaced and routed subnets for what a routed scan records. You can mix the two, with a daemon at the larger sites and the central host covering the rest.

Run a daemon at each site

  1. Create a site for each location in Inventory > Sites.
  2. In Discovery > Daemons, create a daemon for each site and pick that site on the Setup step.
  3. Run each daemon's install artifact on a host at its site. See Installing Daemons for supported hosts and sizing.
  4. If a site has VLANs the daemon's host has no interface on, either add them to its scan as routed subnets (Managing Scan Targets) or run one daemon per VLAN on a host trunked to them (Scanning Isolated Networks from One Host).

With DaemonPoll, the default, each daemon opens its own connection to the server, so remote sites need outbound access to the server and no inbound rules. See Choosing a polling mode.

To create sites and daemons for many locations through the API, see Automate a Site Rollout.

Scan remote sites from a central host

A daemon scans subnets on its own site, so a remote site needs its own daemon even when that daemon runs at the main site. Run one daemon per remote site on the central host:

  1. Create the remote site in Inventory > Sites.
  2. In Discovery > Daemons, create a daemon on the remote site. Set its Interfaces to the loopback interface (lo on Linux). Without it, the daemon reports the central host's own subnets as part of the remote site. Loopback subnets are never scanned. See Daemon Configuration.
  3. Install the daemon on the central host. Several daemons can run on one host, and Scanning Isolated Networks from One Host covers slots and ports.
  4. In Inventory > Subnets, create each of the remote site's subnets and assign it to the remote site.
  5. Add those subnets to the daemon's scan in Discovery > Scans. A scan covers exactly the subnets in its list.

The central host needs a route to every remote subnet, and the path needs to allow ping and the TCP ports the scan probes.

Collect MAC addresses at remote sites

A routed scan collects no MAC addresses. Add an SNMP credential for the router or Layer 3 switch at each remote site. The daemon reads the device's ARP table and records the hosts and MAC addresses on its subnets, and reads LLDP and CDP neighbors for the Layer 2 topology. The device needs to accept SNMP from the central host's address on UDP 161.

Sites that reuse address ranges

Within a site, the same CIDR is the same subnet. Keep each location on its own site, as above, and two branches that both use 192.168.1.0/24 stay separate. A central host has one route per address range, so it reaches only one of two branches that both use 192.168.1.0/24. Run a daemon at each of those sites instead.

On this page