Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

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

    LSP Tunnel Traffic Collection (Juniper only)

    LSP Tunnel Traffic Collection task has been introduced to collect LSP Traffic statistics for Juniper routers every 15minutes or at an interval specified by the user. The task executes the following CLI command on all the Juniper routers that have been scheduled to collect LSP Traffic stats from:

    show mpls lsp ingress statistics logical-router all | no-more

    The command outputs cumulative traffic that have been originating at each tunnel on the local router.

    Note that this is an alternative method of LSP traffic collection using CLI, different from the Traffic Collection Manager, which uses SNMP to collect LSP traffic. This task allows handling of the case where different routers have different statistics intervals. See Scheduling Parameters for more information.

    To schedule the task, select Admin > Task Manager, click New Task, and then choose LSP Tunnel 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.

    Figure 1: LSP Tunnel Traffic Collection

    LSP Tunnel Traffic Collection

    Collection Parameters

    • Collection Directory: LSP 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 (Traffic 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). Decide whether or not to back up the raw traffic data
    • Data Collector (Traffic Data Collector) Parameters: The collection will collect the device’s Management IP first, and then the Device IP if the Management IP fails. For No. of Processes, you can increase this number to simultaneously collect a larger number of routers together. For more information, see the Traffic Data Collector Parameters on page 35.
    • Tunnel Traffic Options: Select the aggregation statistic (99th, 95th, 90th, 80th percentile, Max, or Average)

    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. The minimal period for this task is 15 minutes.

    Note that the default Juniper router setting is every 5 minutes. However, some routers may have a different interval configured under the hierarchy level: protocols mpls statistics interval <seconds>. In this case, make sure that your scheduled interval exceeds the router’s statistics interval. If different routers have different intervals at least 15 minutes, for example, one set of routers has 15 minute intervals and another set of routers has 30 minute intervals, then you can create two tasks, one for each set of routers, with a different scheduling parameter.

    Click Finish to submit the task.


    For troubleshooting purposes, the most recently collected output of the show command will be saved in a file:


    Furthermore, the log messages corresponding to the collection status will be generated in a log file: /u/wandl/data/LSPTraffic/<yymmdd>/log/LSPTraffic.log

    LSP Tunnel Traffic Outputs

    Parsed LSP tunnel traffic for the most recent 24 collection intervals will be saved to the file: /u/wandl/data/.network/LSPtunneltraffic.x. To view the recent LSP traffic on the client GUI, switch to offline mode and import LSPtunneltraffic.x file into the network (File > Load Network Files, t_trafficload). After importing the LSPtunneltraffic.x file, go to NetInfo > Tunnels, right click on a tunnel and hit Show Traffic Load.

    Parsed Tunnel traffic for the day will be aggregated every one hour and saved into a file, /u/wandl/data/LSPTraffic/tunneltraffic/tunneltraf.yymmdd at the end of each day. The aggregation method chosen in LSP Tunnel Traffic collection task will be used. To view any particular day’s aggregated LSP tunnel traffic on the client GUI, switch to offline mode and import tunneltraf.<yymmdd> file into the network (File > Load Network Files, t_trafficload). After importing the tunnel traffic file, go to NetInfo > Tunnels, right click on a tunnel and hit Show Traffic Load.

    Figure 2: LSP Tunnel Traffic Load

    LSP Tunnel Traffic Load

    LSP tunnel traffic that has been aggregated can also be viewed on the web in Live Network > Performance Management > View Historical Traffic Reports > LSP Tunnel Traffic Summary Report.

    Figure 3: LSP Tunnel Traffic Report

    LSP Tunnel Traffic Report

    Time-Based Invariant Aggregation

    To aggregate multiple days into one single file to determine hourly load, select Traffic > Traffic Load, and use Import Type: IP/MPLSView Traffic Data, as shown in the image below. Daily aggregated LSP tunnel Traffic is saved as an object file: /u/wandl/data/LSPTraffic/wandl_out/<mmmdd.yy>.

    The directory, wandl_out, containing these files is used as an input. The days to be aggregated together can be selected here.

    The resulting time-based variant aggregated file: /u/wandl/data/LSPTraffic/wandl_out/tunneltraf.x can be imported into the network (File > Load Network Files) for further analysis.

    Modified: 2016-11-08