Skip to content
Start free

Find every device and see how it connects

Collectors sweep the address ranges you choose for SNMP devices, hold each new one for your review, and draw the map from the LLDP neighbors your switches, routers and firewalls report, with the evidence behind every link.

Start freeBook a demoRead the discovery docs
  • CIDR range sweeps
  • SNMP v2c · v3
  • Links from LLDP

How it works

From an address range to a map you can check

Discovery runs on the collectors inside your network. Nothing joins your inventory or the map until a device answers and you confirm it.

  1. 01ScopeAdd CIDR ranges and a site to the SNMP card in a collector policy, with the v2c community or SNMPv3 user your devices accept.
  2. 02SweepThe collector probes every address on a schedule, every 15 minutes by default, and skips devices it already manages.
  3. 03IdentifyEach device that answers is fingerprinted by sysObjectID, sysName and sysDescr and matched to a profile.
  4. 04ReviewNew devices wait in Discovery Candidates until you confirm them, unless the range auto-accepts.
  5. 05MapLLDP neighbor reports become links, and each device takes a tier by its role within the site.

Discovery

Sweep the ranges you choose, on your schedule

Give the SNMP card a list of CIDR ranges and the site they belong to. A /32 adds one device; wider ranges are swept, and every device that answers SNMP becomes a candidate.

  • Only devices that answer SNMP are kept, so a sweep never fills the list with empty addresses
  • Probe with a v2c community or an SNMPv3 user; an address that refuses the v3 credentials is backed off, so retries don't lock out the account
  • The site you set groups the device list and the topology map

Topology

Every link shows the reports behind it

Switches, routers and firewalls report their LLDP neighbors port by port. Tracix turns each report into evidence, and draws a link with a confidence that rises when both ends agree and falls as the reports age.

  • Seen from both ends

    A link both neighbors report scores higher than one only one side sees.

  • Tiers by role

    Firewalls and routers on top, then core, distribution and access. Pin a role to override.

  • Stale, not hidden

    A device that has not reported for 30 minutes is marked stale on the map.

  • Gaps you can see

    A neighbor Tracix does not poll appears as a stub, so discovery gaps show.

Review

New devices wait for you, not the other way round

Discovery Candidates lists what each sweep found with its make, model, software version and identity, so you can confirm the devices you expect and reject the rest, one at a time or in bulk.

  • Turn on auto-accept for a range you trust; it is off by default
  • When no built-in profile matches a make and model, Brain writes one from a single sample walk, if your organization has connected an AI model
  • Each candidate shows how it was identified: an SNMPv3 engine ID, a serial number, or only its address

Better together

The map is the start of the network story

The devices you confirm are polled, backed up and alerted on by the same collectors, in the same workspace as your applications.

FAQ

Questions network teams ask about the map

Ask a network engineer
Which protocols draw the links?
LLDP, today. Links come from the LLDP neighbors your devices report, so a device that does not run LLDP appears on the map without links. Cisco Discovery Protocol, MAC and ARP tables and routing tables are not used for links yet; a switch's MAC, ARP and routing tables appear on its device page.
Does discovery find hosts that do not run SNMP?
Not as devices. Only devices that answer SNMP become candidates and appear on the map. An optional port scan card scans ranges for open ports and starts a matching receiver for the MySQL, PostgreSQL, Redis, MongoDB, Elasticsearch, NGINX and Apache servers it recognizes, but those hosts are not drawn on the map.
Can the map trace a path or show link utilization?
Not yet. The map shows devices and the links between them, with the evidence and confidence for each link. It does not trace a route between two devices, and traffic and errors per port are on each device's page.
What if the map puts a device in the wrong tier?
Pin its role from the side panel: firewall, router, core, distribution or access switch, switch, wireless controller or load balancer. A pinned role overrides what Tracix infers from the device and its links.

Point a collector at your first address range

Add a CIDR range and a site to the SNMP card, then confirm the devices it finds in Discovery Candidates.

Start freeRead the guide