NOTE: Network scanning is disabled on trial accounts. Please contact support if you want to evaluate this feature during your trial.

You can configure LogicMonitor to have collectors scan an IP range periodically and add discovered hosts into the system automatically.

Automated discovery of devices on your network involves 3 steps:

1. Creating a netscan policy (NSP)
2. Executing that policy on a particular collector
3. Optionally, scheduling the policy to periodically execute on a collector or collectors.

Network Scan Policies are configured under the Settings tab, by clicking Datasources, eventsources, batchjobs, and netscans.

Netscan Policies are contained in their own node at the bottom of the navigation tree:

Netscan Policies can be created by by clicking the New button in the top right and selecting Netscan Policy, while existing policies can be edited simply by selecting them. Policies can be deleted by right clicking the policy in the tree and selecting Delete.

Creating Netscan Policies

 

Name - a unique name for human-readable identification.

Scan Method- Supported scanning methods are:

• Ping scan will scan all IPs in the given IP ranges for ping response.
• Amazon EC2 scanning which will use Amazon credentials to list all active machine instances.
• Script will use the output of an arbitrary script to discover hosts - this can be used to pull hosts from a configuration database, or other repository.

Folder an arbitrary folder name for grouping NSPs

For Ping Scan policies, you must specify an IP range or ranges to scan. An IP range could be:

• A single IP address such as 192.168.1.1.
• A network address such as 192.168.1.0/24. In this case, LogicMonitor will check IPs from 192.168.1.0 to 192.168.1.255.
• A hyphenated range such as 192.168.1.200 - 192.168.1.255.
• any of the above separated by commas such as 192.168.1.1; 192.168.1.200 - 192.168.1.255, 10.0.0.0/24.

For Amazon EC2 policies, the parameters to specify are:

• Access Key ID - amazon access key
• Secret Access Key - Key required to use the Amazon API.

For Script policies, you must specify the path to the script to be used for Linux &/or Windows collectors, and any parameters needed by those scripts.

The script can be passed a combination of postional arguments and named options. If both are used,  options should be passed in first, then the arguments: e.g. opt1=xxx opt2=yyy argument1 argument2

Within a groovy script, you can access arguments via:
args[0] == "test argument"

and options via:
option foo=="bar"

The script output should the list of discovered hosts in this format, one line per host:

IP##Hostname##[prop=value##]*[suggest_group]

Only the IP and Hostname are required. The script can optionally report a set of properties and their values for each host, and optionally suggest a group to place the discovered host into. The group field, if present, must be the last field. Thus a script with the following output:
168.1.1.1##host1.somewhere.com##snmp.community=public##jmx.port=9099##testgroup
would result in the discovered host having the following attributes
IP: 168.1.1.1
Hostname: host1.somewhere.com
properties: snmp.community=public,jmx.port=9099
group: testgroup

Executing Network Scan Policies

Once you submit an NSP, it will be available for execution - either immediate or scheduled.

To execute immediately, click the Execute Now button - a form will pop up so you can select the collector that will run the scan policy, and the group to add newly discovered hosts into.

To schedule recurring scans, click the Add button next to Recurring Executions:

and complete the form:

• Collector - the collector to run the scan policy on. (Note that more than one collector can be scheduled to run the same policy.)
• Schedule - How often this scan should be executed.
• Add Discovered Hosts to the Group - If a group is selected, then newly discovered hosts will be placed in that group, and be monitored automatically. If "Add to the @Uncovered group" is selected, then newly discovered hosts are placed in the @Uncovered hosts table on the Hosts tab, and can be manually added to the appropriate groups.

Adding Discovered Hosts to Monitoring

If hosts have been discovered by an NSP, and not automatically added to monitoring (i.e. no group was specified to add the hosts to), then they will appear in the @Uncovered group:

When selected, this will show a list of discovered hosts:

Any hosts you wish to monitor can be selected, and then either deleted or added to monitoring, by use of the More button in the top right: