Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Archived Reports

 

You can use the Archived Reports feature from the IP/MPLSView Web interface to display preprocessed traffic reports that you can view on a daily, weekly, monthly, or yearly basis. Because the reports are generated from preprocessed aggregated traffic data stored in the database on a daily, weekly, monthly, or yearly basis, you can perform report queries more quickly to retrieve the data.

The following archived reports are available:

Traffic reportsArchived Interface Traffic or Archived Tunnel Traffic.
Device performance reportsArchived System Uptime, Archived CPU Temperature, Archived CPU Usage, or Archived Memory Usage.
Network performance reportsArchived Ping, Archived Advanced Ping, Archived LSP Ping, Archived SLA, or Archived Link Latency.

The daily and weekly reports use hourly aggregated data. The monthly and yearly reports use daily aggregated data. You can specify display options for the average, maximum (max), or 80th, 90th, 95th, and 99th percentiles. IP/MPLSView prepares the data every day at 11:30 AM by running the /u/wandl/bin/genAggTrafDB.sh script.

To generate and display archived reports from the Web interface:

  1. (Optional) Configure the IP/MPLSView server to set the maximum number of days to store performance management data.

    By default, you can store data collected from live traffic, aggregated traffic, and archived traffic for a maximum of 35 days. In most cases, using the default value should be adequate for your data storage needs, However, you can increase or decrease this value according to the available storage space in your network and how long you need to retain the historical data.

    If necessary, you can set a nondefault value for the maximum data storage capacity in either of the following ways:

    • During the IP/MPLSView installation, change the default value (35) for Maximum Traffic Capacity in Days in the installation script.

    • After the IP/MPLSView installation, change the default value by running the /u/wandl/bin/changeconfig.sh script.

  2. Collect the data to be generated for the archived reports by running the appropriate collection task from Task Manager.

    Table 1 lists the collection tasks you need to run to provide data for the associated archived reports. For example, to generate data for the Archived Ping report, you must first schedule the Device Ping Collection task from the Task Manager to run on a recurring basis.

    Table 1: IP/MPLSView Collection Tasks and Associated Archived Reports

    Collection Task

    Associated Archived Reports

    Traffic Collection

    Archived Interface Traffic, Archived Tunnel Traffic

    Device SNMP Collection

    Archived System Uptime, Archived CPU Temperature, Archived CPU Usage, Archived Memory Usage

    Device Ping Collection

    Archived Ping

    Advanced Ping Collection

    Archived Advanced Ping

    LSP Ping Collection

    Archived LSP Ping

    SLA Collection

    Archived SLA

    Link Latency Collection

    Archived Link Latency

  3. Select Performance > Archived Reports from the main menu to access the Archived Reports.
    Figure 1: Example of Archived Reports
    Example of Archived Reports