Automatically discover how your network devices are physically connected, and build custom topology maps to represent any view of your infrastructure.
Cloudmon provides two complementary topology tools. Layer 2 Topology automatically discovers the physical connectivity between network devices by using a seed device and crawling the network via CDP (Cisco Discovery Protocol) and LLDP (Link Layer Discovery Protocol). Topology Maps are custom, manually built maps that can represent any view of the environment, such as a site layout, a geographic view, a virtualisation environment, or a specific subset of devices.
Navigate to Network → Layer 2 Topology for automatic topology discovery, or to Network → Topology Maps for custom maps.
Layer 2 Topology discovery starts from a seed device and crawls outward through the network using CDP and LLDP, mapping device connections as it goes. For each discovered device, Cloudmon captures neighbour details via FDP (Foundry Discovery Protocol), IP-to-MAC mappings from the ARP table, and routing path information from the IP Route table. This produces a hierarchical diagram that shows how devices are physically connected across the segment.
Follow these steps to create your first topology discovery:
| Field | Description |
| Name | A name for this topology discovery, such as "Data Centre Core" or "Branch Office Network". |
| Probe | The Cloudmon probe that will run the discovery scan. Select the probe that is local to the network segment being scanned so it can reach all devices in the IP range. |
| Seed IP | The IP address of the starting device. The scan crawls outward from this device using CDP and LLDP. The seed device must have SNMP enabled and should be a well-connected device such as a core switch or router for the best discovery coverage. |
| SNMP Credentials | One or more SNMP credentials required to authenticate with the devices in the scan range. If devices in the range use different community strings or SNMPv3 credentials, add all applicable credentials here. |
| IP Range | The IP range within which the discovery should be conducted. Narrowing this to the relevant subnet limits the scan to the devices you want to map and reduces scan time. |
Once the scan completes, click the view icon in the topology discovery table to open the topology diagram. The diagram shows the network as a hierarchical tree with the seed device at the top and downstream neighbours connected below it. Devices already monitored in Cloudmon are colour-coded by status, with green for active and red for inactive. Devices not yet in monitoring are shown in grey and labelled as Not Monitored.
From within the topology diagram you can take the following actions:
Topology Maps are custom views built manually to represent any grouping of devices or locations that is meaningful to the team. A map can represent a physical site, a geographic view spanning multiple locations, a virtualisation environment, or a specific set of servers. Maps are listed by name and description, and can be created, edited, or removed at any time.
Custom topology maps are useful for teams that need a visual reference tied to a real-world layout, such as a floor plan showing which devices are in which room, or a regional map showing which offices have which infrastructure. They complement the auto-discovered Layer 2 topology by giving teams full control over how their environment is visualised.
Once saved, hovering over any resource in the map shows its name, state, type, and IP address. Hovering over a link shows the live interface or node status, IP address, and name. The map reflects real-time monitoring status as device states change.
To attach a custom topology map to a specific node in an auto-discovered Layer 2 topology, navigate to Network → Layer 2 Topology, open the discovered topology, click the node where the map should be linked, select Link Map, choose the map from the dropdown, and click Save.
To display a topology map on a custom dashboard, navigate to Dashboard → Create Dashboard, click Add Widget, select the Topology Maps widget, choose the desired map, and save the dashboard.
| Symptom | Likely Cause | Fix |
| Scan shows fewer devices than expected | Some devices do not support CDP or LLDP, or SNMP is not enabled on them | Confirm SNMP is enabled on all target devices, widen the IP range if needed, and manually add devices that do not support CDP or LLDP using the Link Map option |
| Scan not completing | The probe cannot reach the seed IP, or the SNMP credentials are incorrect | Verify the probe can reach the seed IP on UDP port 161 and that the SNMP credential is valid for the target devices |
| Seed device selected but topology shows only one node | CDP and LLDP are not enabled on the seed device or its neighbours, so crawling stops at the first hop | Enable CDP or LLDP on the seed device and its connected switches. For devices that cannot run CDP or LLDP, use Link Map to manually connect them to the topology. |
| Topology map links not showing live status | The link was created without selecting an interface or monitor group for status retrieval | Edit the link in the Topology Map and select the interface from the connected device, or select the Monitor group option to pull live status for the link. |