Discovery error resolutions
When a discovery error occurs, follow these basic steps to resolve the error:
- In aDomain Manager Administration Consoleattached to , clickTopology > Show Discovery Progressto launch theDiscovery Progresswindow.Instructions for opening the Domain Manager Administration Console are presented in “Procedure for opening the Domain Manager Administration Console” on page 40.
- In theDiscovery Progresswindow, check the messages on thePending Elementslist and in the Discovery Status section of the window.Each entry on thePending Elementslist has an accompanying comment that describes the discovery error. And in some cases, just below theDiscovery Statussection in theDiscovery Progresswindow, a message will appear that explains the discovery error.
- Check the log file (for example, VoIP-AM_en_US_UTF-8.log) in the BASEDIR/smarts/local/logs directory in the installation area.The discovery process writes an error message to this log file when it encounters a discovery error. “VoIP Availability Manager log files” on page 48 explains how to read error messages.
- Check the CLI log files in theBASEDIR/smarts/local/logsdirectory in the installation area.When probing a Nortel Signaling Server or Call Server, and assuming that theTraceCLIorTraceDiscoveryparameter in thevoip.conffile is set to TRUE, a CLI probe writes a record of the Telnet session with the server to a CLI log file. The CLI log file includes the CLI commands issued by the probe and the responses returned by the server.Examples of error messages in CLI log files on page 49 presents examples of messages printed to CLI log files for various CLI discovery problems.discovery errors do not appear as notifications in aGlobal Consoleattached to theGlobal Manager.