ipMonitor's Network Scan allows you to control the discovery methods used to achieve monitoring coverage for your entire network. Options include DNS, ICMP/PING, SNMP, and TCP & UDP Port scanning. In order to actively use ICMP to detect devices on the network, you will have to use the ICMP Scan: PING each member of the subnets below section of the Network Scan feature to define the IP Addresses used by the scan.
To use ICMP when detecting devices on the network:
- Log in to the ipMonitor Administration interface and click the Monitors menu option, then select Network Scan.
- Enter the network prefix that identifies your gateway in the Found IP Addresses field, as well as the range of your search.
Note: The /bits parameter determines the range of your search. For example, /32 represents a single IP address, and /24 represents 256 addresses.
- Place a checkmark beside the Use ICMP/PING discovery option.
- In the ICMP Scan: PING each member of the subnets below section, click the Add Network to Scan... button and enter the same subnet as above. (In this example, 10.0.0.1 /24)
- Click the Next button to initiate the scan, and follow the Network Scan wizard.
The Found IP Addresses section of the Network Scan acts as a global container. It ensures that the scan does not exceed the defined boundaries. For example, should the SNMP scan method be selected, if it attempted to retrieve an IP Address from a machine's local connection table outside the initial Network Address Netmask field's range, ipMonitor would not be allowed to scan it.
The ICMP Scan: PING each member of the subnets below section is used to determine the IP addresses that will be processed by the ICMP scan.
The example shown in the image below illustrates this concept:
These settings would instruct the Network Scan to use the ICMP discovery method and scan the IP Addresses located between the two subnet ranges defined:
- 168.244.161.1
- 168.244.161.2
- 168.244.161.3
- 168.244.161.4
- 168.244.161.5
- 168.244.161.6
- 168.244.161.97
- 168.244.161.98
- 168.244.161.99
- 168.244.161.100
- 168.244.161.101
- 168.244.161.102
For information on other features and concepts related to those discussed in this article, refer to the following ipMonitor resources:
< Back
Last Updated: April 24, 2006 | What did you think of this topic?