How does device discovery work?

Functional description

The NSP discovers devices using user-specified protocols and stores the device properties in the database. To discover one or more devices in your network, you create a discovery rule and then scan the network for devices according to the IP address ranges specified in the discovery rule.

A discovery rule contains lists of IP addresses or subnets are to be included in, or excluded from, the discovery process. For example, you can configure one subnet under included IP addresses for discovery, and another under excluded IP addresses. This allows you to provide a focused list of IP addresses for faster discovery scanning.

A discovery rule includes a network scan interval, for example, 60 min. This means that, if the discovery rule is active, NSP scans the network every 60 min to look for devices that match the information specified in the discovery rule and make them available for management by the NSP.

Discovery checks are also used to determine if an NE has been rebooted or if the software version has been upgraded. When a software upgrade is complete, the NE reboots and raises a reboot alarm. The reboot alarm triggers an NE-specific discovery scan. When the discovery scan detects a version change, the NE information is updated.

The management IP address is used to discover a device. The IP address provided for discovery must be reachable by the NSP.

Device discovery using IPv6

NSP supports the discovery of devices that use IPv6 IP addresses. In order for the NSP to discover and manage a device that uses IPv6, the device must have an IPv6 address on the management port, and the NSP cluster must be configured for IPv6 mediation; see “Multi-interface configuration” in the NSP Installation and Upgrade Guide.

Note: IPv4 and IPv6 addresses must be discovered using different discovery rules.

Synching from NFM-P

Discovery rules, policies, and managed devices are synched from NFM-P to NSP and available in the Device Discovery or Device Management views. Devices in an unmanaged state are not automatically synched.

Important! To use telemetry and reporting with a synched NE, the classic discovery rule used to discover the device must be stitched to a unified discovery rule with gRPC mediation configured. This is a one-time manual process; see How do I stitch a classic device to a unified discovery rule?.