Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
ContentIndex
  
[+] Expand All
[-] Collapse All

No index entries found.

Related Documentation

    LDP Traffic Collection (Juniper only)

    Note: This feature requires a license. Please contact your Juniper representative for more details on this feature.

    The LDP Traffic Collection is designed to collect LDP statistics from Juniper routers. Juniper LDP traffic statistics gives you the volume of traffic that has passed through a particular forwarding equivalence class on a Juniper router. The LDP traffic statistics data can be collected and converted into IP/MPLSView demand and trafficload data. The resultant LDP traffic statistics demand and trafficload files, which can represent the various VPN traffic carried by LDP on the network, is then used for capacity planning and failure simulation studies. The LDP demand and trafficload files can also be specified as the known traffic while running the T-Solve traffic demand matrix solver. See the Router Guide for more information.

    There are two methods to collect Juniper LDP traffic statistics data.

    • One method is to configure the router to automatically gather the LDP traffic statistics and periodically write the statistics to a file. Please refer to the Juniper LDP Statistics Import section of “The Traffic Menu chapter” of the General Reference Guide for details of this method and on how to import the collected Juniper LDP statistics data files using the Import Traffic Wizard.
    • The other method to collect Juniper LDP traffic statistics data is via the following CLI show command: “show ldp traffic-statistics”. The LDP Traffic Collection Task uses this method and allows the user to collect Juniper LDP traffic statistics at regular scheduled intervals for selected devices.

    To schedule the task, select Admin > Task Manager, click New Task, and then choose LDP Traffic Collection from the available tasks. You may specify a name and comment for the task as desired. Click Next to continue. Then fill out the following collection parameters.


    Collection Parameters


    • Collection Directory: LDP traffic information will be saved to this directory.
    • Select the device(s) to be collected: Select the appropriate router profile. Then add Juniper routers from the “Select device(s) from” list to the “Devices to be collected” list. Alternatively, use Use Profile directly to use all of the routers in the selected router profile. This option has the advantage that it will automatically pick up updates made to the selected router profile. Selecting “Use Master Profile” will allow the user to choose from devices that were previously collected, using the last successful credentials.
    • Data Collector Instruction: For the Access Method, select whether to use SSH, Telnet, SSH- or Telnet as alternate, Telnet- or SSH as alternate, or Use Profile setting (the SSH/Telnet setting in the router profile).
    • Data Collector Parameters: For No. of Processes, you can increase this number to simultaneously collect a larger number of routers together. For more information, refer to Data Collector Parameters on page 35.
    • Demand/trafficload options: Upon collection of LDP traffic, a demand and trafficload file will be created in /u/wandl/data/.network/LDPdemand.x and /u/wandl/data/.network/LDPtrafficload.x based on the following parameters:
    • Max BW (bps) per demand: Generated demands will not exceed this value
    • Min BW (bps): Generated demands will be at least this value.
    • Range: This option indicates which period to use to generate the demand file. Options include Peak Period, 24 Period, and Period n, where 1<=n<=24
    • ECMP: Used to created ECMP demands as appropriate.
    • Aggregation statistic: This is the computation methods used to calculate traffic. Options include 99th, 95th, 90th, and 80th percentiles, average, and max.
    • Use destination node IP: If this option is selected the loopback address will be used instead of the node name in the LDPdemand file.

    Figure 36: LDP Traffic Collection

    LDP Traffic Collection

    Scheduling Parameters


    After filling out the collection parameters, click Next. In the Schedule Task pane, schedule an interval of traffic collection, for example, every 15 minutes. Click Finish to submit the task.


    Collection Results


    After the data collection has been performed, the collected LDP traffic statistics data will be stored under /u/wandl/data/LDPTraffic/YYMMDD/nodename.LDPTraffic.

    Subsequently, the LDP traffic is processed and aggregated on a daily basis to generate the demand and trafficload files and stored under /u/wandl/data/LDPTraffic/demandtrafficload.

    The following demand and trafficload files are automatically generated based on the last 24 collections:

    /u/wandl/data/.network/LDPdemand.x

    /u/wandl/data/.network/LDPTrafficload.x

    These files can subsequently be loaded via the Read Files menu (via File > Load Network Files) as demand and trafficload files for capacity planning and simulation studies.

    The results can be viewed from the IP/MPLSView Web Interface (File > Launch Web). After logging into the web, select Live Network > Performance Management > View Historical Traf Reports. Find the bullet which contains the LDP Traffic Directory. Check that this is the same as the Collection Directory specified when scheduling the task (default is /u/wandl. Otherwise, click Browse to browse for the collection directory. Next, click the LDP Traffic Summary Report link to view the collected data in a table format with the LDP traffic statistics (default in bits per second). The report options allow you to pick the date range to report on as well as the aggregation interval (for example, hourly), aggregation method (for example, maximum or average), and units (for example, Mbps).

    Modified: 2015-12-29