Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[WANDL] Example - Start Data Collectors and Live Traffic Collection with the WANDL server

0

0

Article ID: KB33582 KB Last Updated: 30 Dec 2018Version: 1.0
Summary:

This article summarizes the steps and tasks needed to start live traffic collection on the WANDL server.

Symptoms:

Initial setup of WANDL server and pre-production stages.

Solution:

Follow the steps below:

Prerequisite: Router must be configured with SNMP. 

Example of SNMP configuration on vMX router:

root@vmx101> show configuration | display set | match snmp
set groups global system login class wheel permissions snmp
set groups global system processes snmp enable
set groups global snmp location "Systest lab"
set groups global snmp contact "Jay Lloyd"
set groups global snmp community public authorization read-only
set groups global snmp community private authorization read-write
set snmp community public authorization read-only
set snmp trap-group space targets 10.85.234.84

1) Check if data collectors have been started using the CLI command in the directory '/u/wandl/dcollect':

[root@localhost ~]# cd /u/wandl/dcollect/
[root@localhost dcollect]# ./dc.sh status
No Data Collectors have been started

2) If no data collectors have been started, start the collectors with the CLI command './dc.sh status':

[root@localhost dcollect]# ./dc.sh status
No Data Collectors have been started

Note: Data collectors can only be started as a WANDL user:

[root@localhost dcollect]# su wandl
$ bash
[wandl@localhost dcollect]$ ./dc.sh start 0

Note: There can be more than one instance of the Traffic Data Collector running at once on the same server or on other servers, and it is recommended one collector per 100-150 devices. If the Traffic Data Collector is on a different machine than the main IP/MPLSView application server, specify the IP address using the '-h' option as the example below:

./dch.sh start instance# -h host_ip_address

[wandl@localhost dcollect]$ ./dc.sh --help
Invalid operation value: must be start/stop/status [value: --help]
Usage:
1.) dc.sh start [-h <appl server ip address>] <instance #|range_values>
2.) dc.sh stop [-f] <instance #|all|range_values>
3.) dc.sh status
4.) dc.sh -H (prints this help message)

-f: attempts to terminate normally, then issues kill -9 if the instance is still running
range_value formats:
        1)  0-10             starts/stops instances 0 through 10, inclusive
        2)  0,10,20,30   starts/stops instances 0, 10, 20, 30 ...
        *** no spaces allowed in range values


When the Traffic Data Collector(s) have started, the following messages are reported:

[wandl@localhost dcollect]$ ./dc.sh start 0
 
Trying to start instance 0, using pid=11415
Data Collector instance 0 (pid=11415) Started.

3) Configure/add devices (if none have been added) under the Tools > Device Profile Tab.

 

Fill out the device parameters:  'Device IP' and 'SNMP Get' fields. The other fields are optional. See Device Profiles for a description of the fields.


 

4) Verify connectivity with the device to ensure ping/SSH/SNMP is working, as SNMP is required for live traffic collection:


5) Add the devices to the Traffic Collection Manager. Select the Performance > Traffic Collection Manager. Add the device and information and select the data collector(s) it will be using.


Note: The important information needed is Device IP and SNMP GET community string ('public' is the string).

In the screenshot below, 'Router Groupd Validation Failed' means no collector has been selected. Right click over the new RouterGroup select 'Set Collector'. Once this is done, push the 'Play' button in the top left corner to start live traffic collection.


 

6) Verify that live traffic collection has been started in the 'Collection Status' tab.


 

7) Display the Live Traffic (Performance > Live Traffic). Review 'Traffic Type' and interface traffic to verify that traffic is currently being captured.


Once this has all been done, follow the same steps again for other routers/devices added to the WANDL server.


 

Related Links

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search