Initiating
discovery
After preparing your deployment
for discovery, you initiate an
IP Availability Manager
discovery for each IP Availability Manager
application
in the deployment. Then, you initiate a discovery
by:- Starting .
- Attaching aGlobal Consoleto .
- Issuing the Add Source command to addIP Availability Manageras a topology source.Upon adding anIP Availability Manageras a source, starts a probe that:
- Creates an InChargeDomain object that has the instance name of theIP Availability Managerapplication.
- Starts a synchronization program that probes theIP Availability Managerrepository for relevant device topology and CLI device-access objects.Thereafter, at startup or whenever the connection to theIP Availability Manageris lost and then reestablished, automatically runs this probe.Upon importing device topology from anIP Availability 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 moreIP Availability Managers as sources to .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 inIP Availability Managerprior to running CLI discovery in any of the 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.