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

    • “Could not initialize JMS communications. Please check the JMS server” - This is often due to a firewall blocking traffic to the JMS server. Check that the appropriate ports are open between the client and the server as described in the Getting Started Guide for IP/MPLSView, Port Requirements. In some cases, the port value needs to be changed from the default. The user is prompted for the port value the first time the Traffic Collection Manager is opened. Once the settings are saved, the user is not prompted for them anymore. To get the prompt for these options again, delete the file: C:\Documents and Settings\<user_name>\Application Data\wandl\TrafficCollection.<server_ip>.xml (Windows XP) or C:\Users\<user_name>\AppData\Roaming\wandl\TrafficCollection.<server_ip>.xml and then run Traffic Collection again.
    • If the traffic data collector does not appear in the Traffic Collection Manager check the status using the “./dc.sh status” command. In some cases, you may need to check the /u/wandl/tmp/.pids file to check that a non-existent process (labelled as DGS) is cleared from the .pids file. If the traffic data collector is on a different machine than the application server, check /u/wandl/log/dgs.log.0on the application server to see if the collector has been registered or not (“INFO: Collector registered”). Check /u/wandl/dcollect/log/dcollect_wandl_<pid>.msg on the traffic data collector machine.
    • If the Traffic Collection Manager cannot be started, try renaming the TrafficCollection.<server-ip-address>.xml file as described in step 3 on page 156 and reopening the Traffic Collection Manager. Select the option for HTTP tunneling. If that does not work, check if there is a firewall between the IP/MPLSView client and server machines, and make sure the port 4458 is open. Refer to the Getting Started Guide for IP/MPLSView for a list of ports used between the server and client.
    • If there is still a problem with the Traffic Collection Manager, 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), stop the IP/MPLSView server (/u/wandl/bin/stop_mplsview), run the following commands, and then startup the IP/MPLSView server (/u/wandl/bin/startup_mplsview):

      cd /u/wandl/bin; ./changeconfig.sh

      Select 7.) Task Manager Memory, and change it to a large number ,for example, 768

      Select 24.) JBoss Web Memory, and change it to a larger number, for example, 512

    • If the Traffic Collection Manager’s status tab shows the error that data was collected before scheduling a traffic collection (“the network is not currently collecting, yet data has arrived”, or if traffic is being collected at an interval different than the saved setting in the Traffic Collection Manager, then there may be a traffic data collector still running from a previous installation. In that case, go to the directory of the previous installation and run “dc.sh stop all”.
    • If the Traffic Collection Manager’s status tab indicates a warning or error that traffic collection is being queued “Task already queued or running, skipping <ip address>”, this means that the task was not completed by the time of the next collection interval, and the interval may be skipped. In that case, it may be helpful to increase the collection interval. Click on the Global Network in the Collection Elements tab, and then edit the Traffic collection interval in the right pane to increase its value
    • If there is a major error that says,Cannot find module xxxxx messages, this can be fixed by copying over some updated mibs to /u/wandl/dcollect/snmp/mibs and then deleting .index so that the index can be rebuilt. For example, the routers may be using a newer version of SNMP Mibs
    • If not all the traffic data can be collected within the current timeout value (default 3s), open the Traffic Collection Manager, use <Ctrl> or <Shift> to select the routers whose SNMP timeout value needs to be increased and then increase the value in the right pane. When doing so, it may be desirable to also increase the collection interval.
    • For some routers, there may be errors of severity MAJOR indicating no response within the timeout. In this case, check first for connectivity from the IP/MPLSView server to the router. Basic reachability can be checked from Tools > Diagnostics > Diagnostics Manager. If the reachability fails, check that the necessary routes are added on the IP/MPLSView server to the router network. If the problem is still not solved, SNMP connectivity can also be checked from either the MIB Browser* (Tools > MIB Browser) or the Host Discovery task in the Task Manager. If the SNMP connection fails, check the router configuration and the router profile settings (for example, community string).
    • If the Traffic Collection Manager still has problems, stop the IP/MPLSView server (/u/wandl/bin/stop_mplsview), run the following commands to clear out temporary files that may be in a bad state, and then startup the IP/MPLSView server (/u/wandl/bin/startup_mplsview).
      rm /u/wandl/data/mysql/data/jms/*
      rm /u/wandl/data/mysql/ib*
      cd /u/wandl/app/jboss/server/wandl
      rm -rf data tmp work
      cd /u/wandl/app/jboss/server/web
      rm -rf data tmp work

    Modified: 2016-11-08