Configure an External Routed Subnet Scan (Routed Network)

2 min

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

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.

Note: If you perform an Advanced Scan via TCP and disable this option, devices that do not “reply” to ICMP messages will be marked offline. You should remove them manually.

Note: ‘The Advanced Scan via TCP’ is an additional feature that can be used in many case scenarios but can not work as expected in some of them (and this is why it is not enabled by default).

You can experience some unexpected behavior for example if you have a Firewall which is interpreting the Domotz scans as suspicious and act as a honeypot and replying with fake ip addresses.

If this has happened to you please:
– remove all the routed networks you have added to Domotz
– delete all the devices found on those routed networks
– add the routed networks again without enabling the Advanced TCP Scan

In general the standard Routed Network Scan is enough for you to monitor external subnets.

Device monitoring includes those services:

  • Network Status
  • TCP services available
  • SNMP sensors
  • Remote connection

Note: MAC addresses are not propagated on top of Layer 3. Due to this limitation of Layer 3 information, static IPs are recommended to monitor devices through this feature.

How to Delete a Routed Subnet

To remove a routed subnet from scanning, navigate to the Devices menu and click on the “+” icon next to the Routed Networks section. Then, click on the edit (pen) icon next to the routed subnet you wish to remove.

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.

Share via Social Networks

You might also like…

Read more top posts in this category

Ready to Get Started?

  • Uncover Network Blind Spots
  • Resolve Issues Faster and Easier
  • Exceed Service Delivery Expectations