Path trace troubleshooting table

Use this troubleshooting table to determine the type of error that you are encountering and to determine the possible reason for the error and actions to take that might resolve the error.

The following table provides possible reasons and corrective actions for each type of path trace error.

Table 1. Path trace troubleshooting table
Type of error	Possible reason	Possible corrective actions	Example of an error of this type
Internal Network Manager error	Internal database failure.	Switch on path trace debugging and review the logs.	Failed to create a path due to an internal database error. For more details check the log file $NMGUI_HOME/profile/logs/tnm/`ncp_topoviz.X.log`, where `X` is a number such as 1, or 2, and consult documentation on how to turn on further path tool logging.
Invalid input parameters	Input parameters specified in the Trace an IPv4 Path window are invalid. For example, the IP address is incorrectly formatted, or does not exist in the specified domain.	Correct the parameters specified in the Trace an IPv4 Path window and retrace the path.	The parameter is not a valid IPv4 address or IP forwarding has been disabled for the address. Cannot continue with the path trace.
Network devices not responding	An IP address in the path did not respond to ping verification. Note: This message is only generated if Ping-verify each hop is selected in the Trace IPv4 Network Path window.	Check whether the device is can be pinged. Configure the network or device as required.	`ip_address_or_device_name` address did not respond to ping verification. Cannot continue with trace.
Path trace error	Internal path trace error.	Switch on path trace debugging and review the logs.	An error occurred during the trace of this path. For more details check the log file $NMGUI_HOME/profile/logs/tnm/`ncp_topoviz.X.log`,, where `X` is a number such as 1, or 2, and consult documentation on how to turn on further path tool logging.
Path trace prerequisites not met	For one or more of the devices along the path, SNMP access or routing information has not been configured.	Check that there is SNMP access to devices along the path. If necessary, correct the SNMP community string settings for this device in the Discovery Configuration GUI. Check, and if necessary, correct the MIB settings for this device using the SNMP MIB Browser.	The path start point `ip_address_or_device_name`, does not satisfy prerequisites. Cannot continue the path trace. The ipCidrRouteNumber MIB variable is not retrievable from the device and therefore the path trace script itnm_pathTool.pl cannot determine an IP route.
Required Network Manager process not running	Some Network Manager processes are not running.	Check that all relevant Network Manager processes are running. In particular, check that the processes Topology manager, ncp_model, and WebTools, ncp_webtool, are running and that the NCIM topology database is accessible.	OQL WebTools request failed. Check that all ncp processes are running. For more details check the log file $NMGUI_HOME/profile/logs/tnm/`ncp_topoviz.X.log`,, where `X` is a number such as 1, or 2, and consult documentation on how to turn on further path tool logging.
Timeout error	Path trace timeouts are too short. For example, one of the devices along the path was unable to provide the necessary SNMP routing data within the specified timeout. For example, the device might be set to non-forwarding mode.	Increase the length of path trace timeouts by adjusting the relevant configuration file property.	A timeout occurred. The path trace is taking longer than the configured OQL timeout and might still be running. Increase the oql.response.poll.timeout in $NMGUI_HOME/profile/etc/tnm/`tnm.properties` to wait longer for the path trace result.