Network monitoring (Pulse) 1 of 3

Pulse network monitoring and device discovery

What Pulse does today, how to turn on the Pulse Collector module on an agent, how discovery works, and how to adopt a discovered host.

Pulse is the network monitoring part of The One Stack. In the Hub it appears as the Network section inside RMM. Your TOS agent is the network collector: there is nothing separate to download, install or enroll. You switch on one agent module, tell it which subnets it may scan, and it reports what it finds.

If you do not see Network in RMM, your organization's plan does not include Pulse.

What works today#

Everything below runs through the TOS agent.

  • Device discovery on the subnets you choose.
  • SNMP monitoring with SNMP v2c and v3: CPU readings and SNMP Walk. A device that stops answering turns its monitors to fail and opens an alert. See Monitor network devices with SNMP.
  • Network alerts from alert rules, including SNMP-based rules.

Remote-access tunnels and Run CLI are not available. See Remote-access tunnels in Pulse.

The pages in the Network section#

PageWhat it is for
OverviewCounts of locations, online collectors, monitored devices and open alerts, plus a per-location table and recent open alerts.
DevicesNetwork devices you have adopted.
DiscoveredHosts a scan found that nobody owns yet.
MonitorsThe checks that run on your devices.
TopologyThe map of devices at the location.
Network Alerts and Network Alert RulesWhat fired, and the rules that decide what fires.
CollectorsThe agents acting as collectors, and their state.
LocationsOne entry per network. A location is created for you when a collector is turned on.

Network settings and Network Credentials are under the Settings gear in RMM, not in the Network section.

Turn on a collector#

  1. Open RMM, then All Devices, and choose a device on the network you want to scan. A server or an always-on desktop works best.
  2. Open the device's Agent Modules tab and turn on Pulse Collector.
  3. Confirm what it may scan. Enter the subnets, or choose Accept default subnet to use the device's own /24. Until you do, the device scans nothing and the field says Waiting for you to confirm what to scan.
  4. Wait for the device's next check-in. The default is every 10 minutes.

To turn the module on for many devices, use a module policy in RMM, then Policy Center.

What you can enter as a scan scope

The scope is a ceiling. The collector never touches an address outside it.

  • Private addresses only: 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16.
  • Each entry must be /22 or smaller (a /22 is the widest single subnet allowed).
  • Up to 32 entries.
  • An empty scope means the device scans nothing.

The server shows the reason for any entry it refuses.

How discovery works#

Each time the collector sweeps, it:

  1. Tries a short TCP connection to every address in your scope on ports 445, 22, 80, 443 and 3389. This needs no administrator rights and sends no ICMP pings.
  2. Adds hosts that appear in the device's own ARP table, which also supplies each host's MAC address.
  3. Looks up the vendor from the MAC address and sorts each host into a device class such as gateway, switch, access point, printer, server or endpoint.

The scan only reads. It does not log in to or change anything it finds. A host that blocks all five ports and does not appear in the ARP table is not found.

From Discovered to Devices#

Scanned hosts are listed under Network, then Discovered, as unowned sightings. They are not added to Devices on their own. You Adopt a host to assign it to a customer.

  • Adopt uses the client linked to the host's location. If the location is not linked to a client, link it on Locations first. There is no way to adopt without a client.
  • If an adopted host matches a device you already manage, it is linked to that device instead of creating a duplicate.
  • You need the Pulse device-management permission to adopt.

The sweep interval changes how often sightings are recorded. It does not change whether a sighting becomes a device.

Managed and Unmanaged#

An adopted device is Unmanaged unless you mark it Managed on the Devices page. Unmanaged devices are inventory. Marking a device Managed counts it against your plan's limit of managed devices per location (25, 100 or unlimited, depending on your Pulse plan size), and it is what makes the device eligible for device-down and SNMP alert rules.

Collector states#

  • Active: checking in and working.
  • Pending: set up but has not checked in yet.
  • Offline: has not checked in recently.
  • Deauthorized: switched off.

Last seen updates each time the collector checks in. To stop collecting, turn off Pulse Collector on the device's Agent Modules tab or remove the device from the module policy.

Troubleshooting#

The collector never appears. Confirm the device is online in RMM and that Pulse Collector is on, then wait for the next check-in.

Nothing shows up under Discovered. Check that you confirmed a scope. With no confirmed scope, nothing is scanned. Also check that the scope matches the device's own network, then look again after the next check-in.

Adopt is unavailable. The host's location is not linked to a client. Link it on Locations.