After preparing your Network Protocol Manager deployment for discovery, you initiate an IP Availability Manager discovery for each IP Availability Manager application in the deployment. Then, you initiate a Network Protocol Manager discovery by:

  1. Starting Network Protocol Manager.

  2. Attaching a Global Console to Network Protocol Manager.

  3. Issuing the Add Source command to add IP Availability Manager as a topology source.

    Upon adding an IP Availability Manager as a source, Network Protocol Manager starts a probe that:

  4. Creates an InChargeDomain object that has the instance name of the IP Availability Manager application.

  5. Starts a synchronization program that probes the IP Availability Manager repository for relevant device topology and CLI device-access objects.

    Thereafter, at startup or whenever the connection to the IP Availability Manager is lost and then reestablished, Network Protocol Manager automatically runs this probe.

    Upon importing device topology from an IP Availability Manager, Network Protocol Manager initiates its own discovery by querying the imported devices to discover the protocol information that it needs to build the BGP, EIGRP, IS-IS, or OSPF topology.

    You use the Domain Manager Administration Console to add one or more IP Availability Managers as sources to Network Protocol Manager.


    If you plan to do CLI discovery and you make a change to CLI credentials, you must initiate both reconfigure and rediscovery of those devices affected by the change. Initiate the reconfigure and rediscovery processes in IP Availability Manager prior to running CLI discovery in any of the Network Protocol Manager servers. There may be an 8-minute delay before the credentials are synchronized between the IP and NPM servers. The completion of IP discovery automatically triggers NPM discovery for each device.