Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Every discovery range you create must be associated with a network view. If no network views are specifically defined in your deployment, your discovery ranges will automatically be assigned to the automatically created network view Network 1. For the first discovery of the network, this network view is automatically assigned to the SCAN1 port when you set up the appliance using the  configure   server command.

If more than one network view exists, you can choose the network view with which the discovery range will be associated, by clicking the Network View drop-down menu. If only one network exists in NetMRI, this setting does not appear. The chosen network view must also be associated with a scan interface. Otherwise, discovery does not take place. Unassigned network views that do not have an assigned scan interface or virtual scan interface appear with theicon in discovery ranges configuration. For more details, see Configuring Network Views.

Network views can contain multiple discovery ranges. So when you create other ranges, you can assign the same network view to each. However, you can assign each discovery range to only one network view. Also, ensure that the ranges you assign to each network view make sense. Selecting the network view in an Operations Center environment also involves other details. For more information, see Defining   Discovery   Ranges   on   Operations   Center   Collectors.

You can define discovery ranges that will be excluded from management. This is useful for devices you may not want to manage, but want to know about for inventory purposes. End Host network segments are a good example.

...

Note
titleNote

An advanced setting, Discovery Status Precedence (Settings icon > General Settings > Advanced Settings > Discovery group > Discovery Status Precedence), governs the global setting for exclusion ranges. Changing this Advanced setting to Longest Prefix Match enables an exclusion range to contain smaller IP ranges that can be matched against to allow discovery — for example, you can exclude a /23 network, but Include a /24 prefix within the EXCLUDE range, because the /24 is a longer prefix.

56. To use a discovery ping sweep for discovery on IPv4

Anchor
bookmark117
bookmark117
 networks, select the Enable Discovery Ping Sweep checkbox. This implies a probe that uses a range of packet types to detect the presence of a system on each IP in the specified range, with ICMP Echo, ICMP Timestamp, TCP SYN to port 80, and TCP SYN to ports 161, 162, 22, and 23 (for the SNMP, SNMPTRAP, SSH, and TELNET services correspondingly). A ping sweep is not available for IPv6 network values. For more information on ping sweeps, see Defining Group Data Collection Settings.

Note
titleNote

The discovery ping sweep feature differs from the Smart Subnet ping sweep in the following ways: the discovery ping sweep will run only against the specified range, the sweep will run regardless of the range size, and the sweep will run regardless of the number of discovered devices within the specified range.

67. Select the Enable Discovery Blackout checkbox and click its Scheduling icon.

78. Define your schedule as follows:

...

Note
titleNote

For more information about discovery blackouts and change blackouts, see Defining Blackout Periods.

89. Select the Enable Change Blackout checkbox and click its Scheduling icon. Follow the instructions for the Enable Discovery Blackout setting in the previous step.

910. Click Add to place the new discovery range into the Range table.