When a discovery error occurs, follow these basic steps to resolve the error:
In a Domain Manager Administration Console attached to VoIP Availability Manager, click Topology > Show Discovery Progress to launch the Discovery Progress window.Note:
Instructions for opening the Domain Manager Administration Console are presented in “Procedure for opening the Domain Manager Administration Console” on page 40.
In the Discovery Progress window, 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 VoIP Availability Manager log file (for example, VoIP-AM_en_US_UTF-8.log) in the BASEDIR/smarts/local/logs directory in the VoIP Availability Manager 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 the BASEDIR/smarts/local/logs directory in the VoIP Availability Manager installation area.
When probing a Nortel Signaling Server or Call Server, and assuming that the TraceCLI or TraceDiscovery parameter in the voip.conf file 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.Note:
VoIP Availability Manager discovery errors do not appear as notifications in a Global Console attached to the Global Manager.