When a discovery error occurs, follow these basic steps to resolve the error:
In a Domain Manager Administration Console attached to Network Protocol Manager, click Topology > Show Discovery Progress to launch the Discovery Progress window.
Instructions for opening the Domain Manager Administration Console are presented in “Procedure for opening the Domain Manager Administration Console” on page 65.
In the Discovery Progress window in GUID-4B5EE9C9-0242-4CBB-B62E-1DE8F5A4E903.html#GUID-4B5EE9C9-0242-4CBB-B62E-1DE8F5A4E903___NPM_DISCO_RESOLVE_76054, check the messages on the Pending Elements list and in the Discovery Status section of the window.
Each entry on the Pending Elements list has an accompanying comment that describes the discovery error. And in some cases, just below the Discovery Status section in the Discovery Progress window, a message will appear that explains the discovery error.
Check the log file named <Network Protocol Manager name>_<locale>_<character encoding>.log (for example, INCHARGE-BGP_en_US_UTF-8.log) in the BASEDIR/smarts/local/logs directory in the Network Protocol Manager installation area.
The discovery process writes an error message to this log file when it encounters a discovery error. “Error message formatting” on page 75 explains how to read error messages.
Check the CLI log files in the BASEDIR/smarts/local/logs or BASEDIR/smarts/local/logs/dasl directory in the Network Protocol Manager installation area.
When probing an EIGRP- or IS-IS-enabled Cisco device, a CLI probe writes a record of the Telnet, SSH1, or SSH2 session with the device to a CLI log file. The CLI log file includes the CLI commands that are issued by the probe, and the responses that are returned by the device.
Creates CLI log files on page 22 identifies the CLI log files and describes how they are named.Note:
Network Protocol Manager does not notify discovery errors, which means that discovery errors do not appear in a Global Console attached to the Global Manager.