Troubleshooting

This appendix contains several troubleshooting tools to use in case you encounter a problem while setting up or running AtmDirector.

Problem Solving

Table A-1 lists some problems that you might encounter while using the AtmDirector application and provides some possible causes and solutions.

Table  A-1: Troubleshooting Problems

Problem	Probable Cause	Possible Solution
Unable to discover an end host	ILMI is not enabled.	Enable ILMI on the affected end host.
	No SNMP connection to the end host.	Set up the SNMP connection to the end host. Make sure all device requirements are met. See "Device RequirementsATM Discovery" in Chapter 3 "Generating the ATM Fabric Topology Map."
The Sybase database server is unable to start. The AtmDirector database is marked suspect.	The AtmDirector database is in an inconsistent state.	Reinitialize the database using the atmd_setupdb command. Recover the database from a backup using the atmd_recover command.

Logging Trace Messages

In some cases, you might be asked to turn on the topology and discovery debug options. These options enable the system to log verbose trace messages in the logfile file at the following location: $CWSIROOT/log/atmd.

To enable these debug options, follow these steps:

Step 1 Select Preferences>Options from the AtmDirector main window (Figure 1-1).

The Global Preferences window opens.

Step 2 Select the miscellaneous index tab.

The Miscellaneous window opens (Figure A-1).

Figure A-1: Miscellaneous Window

Step 3 In the Debug box, configure the settings, as follows:

• Topology--Click On to enable verbose message logging for topology.

• Discovery--Click On to enable verbose message logging for the discovery process. If the discovery process is polling, messages are logged after Discovery has completed polling.

Step 4 Click OK.

The AtmDirector window reopens (Figure 1-1).