Automatically scan IP ranges to discover all devices, services, and SNMP-enabled infrastructure on your network. Cloudmon supports ICMP, TCP, and SNMP discovery protocols, letting you move from scan to active monitoring in a single workflow.
Network Discovery in Cloudmon allows you to scan one or more IP ranges from a selected probe and discover all responsive devices, open ports, and SNMP-capable infrastructure. Rather than adding devices one by one, a single discovery scan returns a list of all found resources and lets you enable monitoring on any of them directly from the results.
Cloudmon supports three discovery protocols, each suited to a different monitoring goal. ICMP discovery pings each IP in the range and reports availability and reachability status, making it the fastest way to map which hosts are online. TCP discovery establishes connections to specific ports to identify which services are running on discovered hosts. SNMP discovery retrieves detailed information from SNMP-enabled devices including device type, configuration, and operational status, and is the correct protocol to use when you want to add routers, switches, firewalls, or other SNMP-capable devices to monitoring.
After a scan, Cloudmon marks devices already in monitoring as monitored and flags everything else as Not Monitored. You can then enable monitoring for any discovered resource directly from the results page without leaving the discovery view.
Navigate to Settings → Monitoring → Network Discovery and click the + button to add a new discovery rule. Fill in the fields as follows:
| Field | Description |
| Name | A descriptive name for this discovery rule, such as "Branch Office Scan" or "Data Centre SNMP Discovery". |
| Probe | The Cloudmon probe that will perform the scan. Choose a probe located in the same network segment as the IP range you want to scan for accurate results, particularly for SNMP discovery which requires network reachability. |
| IP Range | The IP range to scan, entered in CIDR notation or as a start-to-end range. For example, 192.168.1.0/24 to scan a full Class C subnet. |
| Type | Select Host to discover devices by availability and reachability, or Service to discover specific services running on ports. Host is the correct selection for general network device discovery. |
| Protocol | Choose the protocol used to scan the range. ICMP pings each IP for availability. TCP checks for open ports and running services. SNMP retrieves device details from SNMP-enabled devices and is the recommended protocol when adding network infrastructure such as routers, switches, and firewalls to monitoring. |
Click Save to create the discovery rule, then click Scan to run the discovery. Cloudmon will scan the defined IP range using the selected probe and protocol and return a list of all discovered resources.
Once the scan completes, results are displayed with a status for each discovered IP. Resources already being monitored in Cloudmon show their current monitoring status. Resources not yet monitored are marked as Not Monitored.
From the results, you can enable monitoring directly for any discovered resource. For SNMP devices, enabling monitoring adds them to Network → Network Devices where Cloudmon automatically assigns the appropriate template. For ICMP or TCP resources, enabling monitoring begins availability and reachability tracking for that host or service.
To use a discovered SNMP device as the seed for a Layer 2 Topology discovery, refer to the Layer 2 Topology and Topology Maps article.
| Issue | What to check |
| Scan returns no results for a known IP range | Confirm the selected probe is online and located in a network segment that can reach the target IP range. ICMP may be blocked by a firewall between the probe and the target range, so try TCP or SNMP if ICMP returns nothing. |
| SNMP discovery finds devices but shows no device details | Verify that the SNMP credentials configured for the probe match the community string or SNMPv3 credentials on the target devices. Also confirm that UDP port 161 is not blocked between the probe and the devices. |
| Devices appear as Not Monitored after enabling monitoring | Allow one full polling cycle after enabling monitoring. If the device still shows as Not Monitored, check that the correct probe is assigned and that the device is reachable from that probe at the time of polling. |