Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Starting the Traffic Data Collector(s)

 
  1. If your data collection has not been started, then at the command prompt on the machine on which you installed the traffic data collector (for example, /u/wandl/dcollect/dc.sh), type the following command shown after the “$” prompt:

    $ ./dc.sh start 1

    You should see start up messages indicating the process ID for the new traffic data collector.

    Trying to start using pid=8608
    Traffic Data Collector (pid=8608) Started.

    The last input parameter of the dc.sh command specifies the instance number of the collector that is being started. In the above example, the instance number is zero (1). There can be more than one instance of the traffic data collector running at once on the same server, so you may start another instance by selecting a different number.

  2. Multiple traffic data collector instances can be started in sequence by using comma. The example below starts instance 2, 3, 5, and 7.

    $ ./dc.sh start 2,3,5,7
    Multiple traffic data collector instances can be started as a range. The example below starts instance 0, 1, 2, 3, 4, and 5 inclusive.
    $ ./dc.sh start 0-5
  3. Execute the following command to see the status of the collectors running. In the following case, two traffic data collectors have been started.

    $ ./dc.sh status
    Found collector instance wandl_0 with pid=8608 (running)
    Found collector instance wandl_1 with pid=8628 (running)
  4. If SNMP traffic data collectors are to be connected to a different JMS host, then run:

    $ ./dc.sh start <instance#> -h <host_ip_address>

Note that SNMP traffic data collectors can be started with users other than “wandl” or the owner of the software installed.

To check that a distributed traffic data collector has been correctly registered on the Application server, check the /u/wandl/log/dgs.log.0 file on the application server for the line, “INFO: Collector registered”. Alternatively, check /u/wandl/dcollect/log/dcollect_wandl_<pid>.msg on the traffic data collector machine.

  1. In the IP/MPLSView client, open the live network. Select Performance > Traffic Collection Manager. If this is the first time, you will be prompted to enter in the client-server communication IP addresses and ports for traffic collection as shown in the figure below. Enter the IP address of your JMS server and Task Manager and the port numbers if you are not using the default ports. The JMS server and Task Manager is typically started on the Unix machine on which IP/MPLSView was installed.

    Note

    The Use HTTP Tunneling checkbox is used for JMS communications and normally should not be selected, except for scenarios with firewalls/NAT.

    Java Messaging Service (JMS) is a message middleware layer used to pass collected traffic statistics from the traffic data collector(s) to the IP/MPLSView server.

    Figure 1: Client-Server Communication Parameters
    Client-Server Communication Parameters
  2. Click OKand the Traffic Collection Manager window will appear as shown in Figure 117 in Setting the Collection Elements.

  3. If the Traffic Collection Manager does not appear and you have installed the IP/MPLSView client before, it could be due to incompatibility with previous installation. Try renaming the previous TrafficCollection.<server-IP-address>.xml file in your local user application data’s wandl directory. For example, “C:\Documents and Settings\<username>\Application Data\wandl” for Windows XP or “C:\Users\<username>\AppData\Roaming\wandl” for Windows Vista. Then reopen the Traffic Collection Manager. (Note that clearing out the old client side XML files was necessary in older versions, but may not be necessary anymore.)