Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Troubleshooting Performance and Diagnostics

    If ping and traceroute are not working from the graphical interface, try to login to the IP/MPLSView server using a telnet or ssh window. As root user, try to ping and traceroute the relevant routers. If this does not work, check the Getting Started Guide for IP/MPLSView, System Administration chapter section on setting up routes to the router network and troubleshooting ping/traceroute issues.

    For problems accessing devices to execute show commands, check the file /u/wandl/data/.TaskManager/tmp/.diag to see what IP address is being used. Additionally, check that the show command is properly set to use the right program, telnet or ssh, in the diagnostics configuration settings described in Diagnostics Configuration Settings. To customize diagnostics settings, log into the Web Portal as the admin user and select Admin > Change Diag Settings.

    If you cannot connect to the router, run ping, traceroute, or CPU Utilization, from the application, try scheduling a live network to populate the /u/wandl/data/.TaskManager/tmp/.diag. If that does not help, copy a router profile from /u/wandl/data/.TaskManager/profile to /u/wandl/data/.TaskManager/tmp/.diag and restart the server using ./stop_mplsview and ./startup_mplsview commands in /u/wandl/bin.

    If you have TACACS, make sure to select that under Diagnostic Login Type in the diagnostics configuration settings described in Diagnostics Configuration Settings.

    Modified: 2016-11-08