Introduction to Routed subnets
Thanks to Routed Subnet Scan, you can monitor Layer 3 / routed subnets (including VPN-connected networks).
With Routed Subnet Scan, you can discover and monitor, for example:
- Modems and routers located on different subnets
- Networks and devices that are reachable via routing (Layer 3) across subnets
- Multiple sites/buildings connected through a VPN (or other routed links)
How to Configure Routed Network Scan
In order to configure a routed network, once you access your Collector, please:
Secondly, use the “+” button toAdd a Routed Network:
At this point, for each subnet, you must specify the following:
Once you select “Advanced Scan via TCP“, Domotz will perform discovery scans on the specified subnet using both TCP port-based scanning and ICMP (ping). If this option is not selected, only the ICMP mechanism will be used on that subnet.
As a matter of fact, in some cases, devices cannot be identified (and monitored) via simple ping (ICMP mechanism). In those circumstances, it is recommended to use the Advanced Scan via TCP.
Device monitoring includes those services:
- Network Status
- TCP services available
- SNMP sensors
- Remote connection
How to Delete a Routed Subnet
This will open the edit panel, select Remote Routed Network, and the subnet will be removed from the Collector’s scanning settings.
Read some examples of configuration on the usage of Routed Subnets (Routed Networks) vs the usage of VLANs (Attached Networks). Read more on our Monitoring Networks with Subnets and VLANs blog post.
In conclusion, if you need to know more about Routed Networks, please refer to our Onboarding guide.