Find out what is actually on the network, then keep finding out
Every inherited network comes with a spreadsheet, and the spreadsheet is wrong. Discovery is how you stop arguing with it.
Key points
- You run the first sweep from the dashboard with live progress; from then on active scans and passive LLDP/CDP capture run continuously as a service, whether or not anyone is logged in.
- New devices land in a "Discovered" filter with a nudge on the dashboard, so onboarding is a click, not an audit.
- Smart groups with membership rules (subnet ranges, device types, discovering probe, manual pins) file a new branch switch into the branch group on their own.
- The topology map comes from LLDP/CDP on the wire, and the same dependencies let the alerting roll forty downstream hosts under the one switch that failed.
- Twelve identical switches are discovered as twelve devices, and a renamed host keeps the name your team chose.
On this page: The first sweep Discovery as a service Smart groups The map Details that matter Inventory
A one-time scan tool answers the question once. The answer is stale by the next quarter, when someone adds an access point in a cupboard and a vendor appliance appears on a VLAN nobody documented. SysPeep's discovery is part of the monitoring service, so the answer keeps updating, and the devices it finds are one click from being monitored at full depth.
The first sweep is yours to start
On a new install, discovery waits for you to run the first sweep from the dashboard, with live progress, so a fresh installation never fills with devices before anyone has chosen what to scan. Point it at a subnet, watch it work, and the first devices are on the map while you are still reading the release notes. Before every scan a card names the credential that will be used, with its non-secret details, so a device that answers to the branch community and not the global one is found on the right credential rather than missed.
Discovery that runs whether or not you are logged in
From the first sweep on, active discovery scans and passive LLDP/CDP capture run continuously as a service. New devices appear in a "Discovered" filter with a nudge on the dashboard; retired hardware leaves the working views but keeps its history for reports; test boxes and mistakes are deleted cleanly if they were never monitored. Discovery and housekeeping run off the poll thread, so a long sweep never costs the monitored devices a sample.
Every sensor is offered on every discovered device, and the ones discovery did not detect are marked with what was recorded and when, so a protocol the sweep missed is still one click away. Flow exporters that are sending records but are not yet monitored are listed with an Enable button and a daily reminder, not silently dropped.
What discovery does for you
- Finds devices and interfaces on its own
- Files them into groups by subnet, type or probe
- Lists unmonitored flow exporters with an Enable button
- Offers every sensor on every device, marking the ones it could not detect
- Keeps history when hardware is retired
Groups that maintain themselves
Smart groups have membership rules: subnet ranges, device types, the probe that discovered the device, manual pins, with subgroups and first-match precedence, editable in place. A new switch discovered in the branch subnet joins the branch group and shows up in the right place without anyone filing it. The practical result is a tree that grows with the estate instead of needing to be re-organised every time the estate changes.
A map that reflects the cabling, not someone's memory of it
The device workspace shows the tree and the topology map in one place. Groups visibly contain their devices; dependency parents and children are stepped and connected; a Show filter, search and per-device tabs get you to the device you need in seconds, and the page remembers your view, filters and open tabs so you land back where you left off. Passive LLDP/CDP capture needs Npcap on the server; the neighbours it hears become the links on the map with no polling.
The map is also the alert model. Because the dependencies come from LLDP/CDP on the wire, the alerting engine uses the same relationships: a dead core switch raises one incident, and the forty hosts behind it are listed under it as consequences rather than paging you forty times.
Two details that matter on a real estate
Twelve switches, twelve devices
Every discovered device gets its own random key, never the model's SNMP object identifier or the address, so twelve identical switches are discovered as twelve devices rather than as the first of each model. A re-addressed device stays the same device.
Names that survive a rename
A discovered name follows the host when it is renamed, while the names your team chose are kept, with "Discovered as" shown beside them. The label on the map is the one the on-call person recognises, and the hostname the device reports is one glance away.
From discovery to inventory
What discovery finds feeds the inventory report, one of the reports SysPeep produces beside the scorecard, health, SLA, alerts, capacity and traffic reports, exportable as CSV in every edition and as PDF in the paid editions, where it can also be scheduled and delivered by email. The library's discovery and inventory guides cover how to keep an inventory honest, and the network diagrams guide covers what a drawn map should and should not try to show.
Questions administrators ask about discovery and mapping
Is it an advanced network scanner and IP scanner for Windows, and is there a download?
Discovery scans the address ranges you give it, identifies what answers and how (SNMP, WMI, SSH, ICMP, open ports), and listens for LLDP and CDP, which is what an advanced network scanner or IP scanner for Windows does, with one difference: every device it finds is one click from being monitored at full depth. The download is the SysPeep installer; there is no separate network discovery tool download for Windows 10 or Windows 11.
Does it draw the network diagram automatically, or is it a network diagram builder I draw in?
Automatically. The topology map is drawn from LLDP and CDP neighbour announcements on the wire and kept current as cables move; it is not a network diagram creator or design tool with a palette of icons. For the logical layer and the WAN, which no wire can announce, you still draw a simple network diagram by hand, and the network diagrams guide covers what belongs on it.
Does discovery work over IPv6, and what is the IPv6 network discovery protocol?
IPv6 Neighbor Discovery (NDP) is the protocol IPv6 hosts use to find each other on a link; it replaces ARP. SysPeep's discovery works from the address ranges you configure and from LLDP and CDP, which are independent of the IP version, and monitors dual-stack devices by whichever address you choose.
Is there an advanced port scanner in it?
Discovery checks the ports that identify a device's collection methods, and a TCP port sensor watches any port on any monitored device continuously. It is not a general-purpose port scanner for auditing the internet-facing surface; the attack surface monitoring series covers that job and the tools that do it.
Can it find duplicate IP addresses, and does it do DNS, DHCP and IP address management?
Discovery records which address each device key answered on, so a device that moves or an address that answers twice shows up with its history rather than as a new device. DNS and DHCP servers are monitored as services and through their counters over WMI; full IP address management, with subnets, ranges and assignments, is a separate category that the IPAM and subnet monitoring series covers.
Is it a total network inventory tool?
The inventory report lists every discovered and monitored device with what was recorded about it, exportable as CSV in every edition and as PDF in the paid editions, kept current by discovery rather than by hand. Retired hardware leaves the working views but keeps its history for the report.
Can it map a network across several sites?
Yes. In the paid editions a remote probe in each branch discovers and maps from the inside and reports back over mutual TLS, and smart groups file each branch's devices by the probe that found them, so a new switch in a branch subnet joins the branch group on its own.
Can I see a sample network map before I install it?
The console screenshot on the home page shows the dashboard; the map itself is best seen on your own network, and the Free edition draws it for up to 5 devices for nothing. One sweep against one subnet is usually enough to judge.
Does it discover Linux hosts and Macs, or only Windows?
Anything that answers: Linux hosts over SSH or SNMP, Macs and printers over SNMP, switches and routers over SNMP and through their LLDP and CDP announcements, Windows over WMI. The device's own collection methods are detected during the sweep.
Is there an online network diagram tool, or does it run on my server?
On your server. SysPeep is on-premises software; the map, the inventory and everything discovery learns about your network stay in your own database. There is no online mapping service and nothing is uploaded.
Can it export the map as a diagram?
The map is a live console view rather than a drawing file; the inventory and the device list export as CSV, and the reports as PDF in the paid editions. For a static diagram to put in a document, the hand-drawn logical map remains the right tool.
Does it discover HP, Dell, Cisco and other vendors' devices?
Vendor-neutrally. Discovery uses SNMP, LLDP, CDP, WMI, SSH and ICMP, not vendor tools, and the compiled MIB set names the counters of Cisco, Juniper, Arista, Fortinet, Palo Alto, HPE, Dell, APC, MikroTik and Synology devices as they are found.
Is it a network map creator, a network diagram creator or a network diagram design tool?
It creates the map from the wire, so for the physical layer it is the map creator; it is not a drawing or design tool with a palette, and a simple network diagram of the logical layer is still drawn by hand. Professional network mapping across sites is what the probes are for in the paid editions.
Passive network discovery and the network discovery settings: what has to be on?
Passive discovery needs Npcap on the SysPeep server so it can hear LLDP and CDP; active discovery needs the address ranges and the credentials for SNMP, WMI and SSH. Both run continuously after the first sweep, and the settings page shows which probe is scanning which ranges.
Is there a best network mapper for a local network, and does it map Ubiquiti and other vendors' devices?
For a local network the best mapper is the one that keeps running after the first scan, because the map is out of date the day someone adds a switch. Devices from Ubiquiti and every other vendor are found the same way, by what they answer and what they announce, with the compiled MIB set naming the ones it knows.
Can SysPeep draw a simple network diagram, a personal network map or a professional network map, and is it software to create a network diagram?
It generates the map rather than letting you draw one: discovery finds the devices and LLDP and CDP tell it which port connects to which, so the diagram is the network as it is, redrawn as devices come and go. For a simple diagram of a personal network that is usually all you want. A professional network map drawn by hand for a design document is a diagramming tool's job; SysPeep's map is the operational one, the one that is still right next month.
Run one sweep and see what the spreadsheet missed
Download SysPeep, point discovery at one subnet, and compare the result with the documentation. Up to 5 devices are free at full depth for as long as you like; the 30-day trial unlocks every feature except clustering.
Download Free TrialThe console, day to day