A unified discovery rule can be used to discover model-driven and classic devices in specified IP address ranges, so that you can manage them in NSP.

The discovery rule provides the protocols and policies required to discover model-driven devices.

To use the unified discovery rule to discover classic devices, you must associate a classic discovery rule. The classic discovery rule contains the mediation and reachability policy information required to discover and manage the classic devices in the specified IP address ranges.

When the unified discovery rule scans the network, it performs discovery using both MDM and classic:

• For host addresses (/32), NSP first tries to discover the devices in the IP address ranges using MDM. If MDM discovery fails, the IP addresses are pushed to NFM-P for classic discovery.

• For subnet discovery, the subnet IP address will be sent to both NFM-P and NSP MDM for NE discovery at the same time.

Note: NSP does not support IP address overlap in discovery rules: an IP address cannot be included in more than one discovery rule.

Select a discovery rule in the Device Discovery, Unified Discovery Rules view to see rule components, discovered NEs and any errors that occurred during discovery.

Note: Nokia AIM devices serve as controllers for MAG-c a2 appliances. You can discover an AIM using a unified discovery rule.

Specifying IP addresses for discovery

You can use an IP prefix to identify a range of IP addresses when you create a discovery rule. NSP discovery scans the range, with the exception of IP addresses typically reserved for the network address or broadcast address of a subnet.

For example, for the included IP address 10.0.1.0/25 NSP will scan the following range to discover devices: 10.0.1.1 – 10.0.1.126.

To avoid this issue, specify specific (/32) IP addresses to include in the discovery rule for each expected IP address of an device that you want to discover.