Troubleshooting

If the Task Manager does not open, go to /u/wandl/bin and run the command status_mplsview. Check that the Task Server and Web Server (JBoss) are both running. Depending upon your server performance, it may take a few seconds to a couple of minutes for the Web Server to finish deploying. Once it is finished starting up or being restarted, then close and reopen the IP/MPLSView client and reattempt to connect to the Task Manager.

If you see the error message “The client could not establish a connection to the Task Server. Please verify that the Task Server is running and fully initialized”, another place to check is the Java Control Panel settings. Select Control Panel > Java > General > Network Settings and select Direct connection. (The location of the Java Control Panel may vary depending upon which Windows operating system you use.)

If the tasks are not completing, check the file /u/wandl/bin/mplsenvsetup.sh and look for the MPLS_JBOSS_MEMORY setting. The Task Manager Memory setting is specified during the installation of the IP/MPLSView server and is defaulted to 256 MB. To change this setting to a higher number (512 or higher is recommended), modify the MPLS_TMNG_MEMORY line in /u/wandl/bin/mplsenvsetup.sh.

If there are abundant login problems when checking the Task Status tab, check the IP addresses that failed to be collected for. You may want to open a telnet/ssh window to the server and check whether you can ping those IP addresses. If not, check the routing table on your server (“netstat -rn”) and add any necessary routes (“route add”). Otherwise, you may want to check that the router profile login/password are configured correctly.

If the task fails, see Test Profile Connectivity to check for telnet, SSH, ping, and SNMP access.

Some routers cannot be reached directly due to a firewall, but can be reached by first logging in to another machine. To handle this, one method is to create the file /u/wandl/db/config/wtalk.agent with the IP addresses of the intermediate machines, one per line. This will be used for all routers and the default login and password to the intermediate machine is the same as for the routers. Another method is to enter in the intermediate server IP in the agent field of the router profile entry. Refer to Specifying Intermediary Servers on page 112 for more information. If a different login and password are needed for the intermediate machine(s), a router profile entry should be created for the intermediate machine(s), which should be added to the list of devices to be collected.

If the task completes without an error message but the Live Network fails to display on the topology map after the task is complete, check for the configuration files in /u/wandl/data/collection/.LiveNetwork/config directory. Check that the configuration files are present and contain the hostname of the router. In some cases, the router login provided in the router profile may not have full permission, and therefore certain commands in the /u/wandl/db/command file may be restricted. For more information, see Editing Show Commands for Data Collection.

To check for Task Manager errors, check /u/wandl/log/tmng.log.n for exceptions, and /u/wandl/log/tmng.msg for startup messages. To check for collection errors, check /u/wandl/log/wDriverTask.log , and /u/wandl/log/wtalklog.log (wtalklog is created if “Turn on Trace” option is selected).

If data (configuration files, interface files, etc.) cannot be completely collected within the timeout period, for example, as indicated by configuration files with partial data, increase the Timeout value in the Collection Options tab, Traffic Data Collector Parameters section. Partial collections can be identified in the config, interface, tunnel_path, etc. subdirectories of /u/wandl/data/collection/. LiveNetwork if there is the suffix ++ at the end of a file.