Sites are how Ntrospect organizes everything by location — device inventory, flow attribution, alert scoping, and the incident blast-radius views all key off them.

Create your sites

Under Settings → Sites, add a site per physical location. Sites can nest (e.g. a campus with buildings). For each site set:

  • Site name
  • Subnets to scan — one CIDR or single IP per line. This drives both discovery and "which site does this traffic belong to."
  • Fallback gateway — used only if no gateway has direct access to the subnet.
  • Description — free text.

Each subnet row also offers copyable flow-export snippets for common vendors (Extreme EXOS/VOSS, Cisco, Juniper, and generic hosts) pointing at the right gateway — handy when you get to flow configuration.

Run discovery

Discovery runs from a gateway, so it sees the network the way the site does. On the gateway's Discovery tab:

  1. Choose Subnet (CIDR) or IP range (Start IP / End IP).
  2. Attach SNMP credentials — v2c community, or v3 username with auth password (SHA) and privacy password (AES). Devices discovered with working SNMP creds come up polled, not just pinged.
  3. Optionally attach SSH credentials (username/password, device family Auto / EXOS / VOSS / IOS) so switches and routers are enrolled in Config Backup at the same time.
  4. Scan. Review discovered resources, promote what you want monitored, or Add Device Manually for anything the scan can't reach.

After discovery

Promoted devices appear in Infrastructure → Inventory (filterable by site, type, and vendor) and, for network gear, under Network → Devices and SNMP Devices. From a device you can Deploy Agent over SSH/WinRM if the host should run one.

Re-run discovery whenever a site's addressing changes; existing devices are recognized, not duplicated.