Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

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

    Traffic and Congestion Summary Report

    The Traffic and Congestion Summary report is a standardized report generated in Network Director to show information about latency and port utilization on network devices. It provides detailed and trended information about latency and port utilization at the network, device and port level. This report supports any scope that includes devices that support high-frequency statistics.

    There are two portions of the report: a report header and the report body. The contents of the report header are described in Table 1.

    Table 1: Traffic and Congestion Summary Report Header

    Field

    Description

    NETWORK DIRECTOR REPORT:

    The type of report; in this case, the Traffic and Congestion Summary report.

    Generated On:

    The date and time the report ran. The date format is: [Day of the Month] [Month] [Year]. The time format follows the Coordinated Universal Time (UTC). For example: 07 December 2013 11:35 PM PST.

    Generated By:

    The username of the user that generated the report.

    Report Name

    The name of the report assigned when the report was created.

    Scope

    The report is generated from this view and node in the network.

    • Perspective—Can be a Logical View, Location View, or a Device View of the network.
    • Node—Represents the selected object on which the report is based.

    Report Filters

    Shows any filters that were applied to the report definition.

    The report body shows port utilization and latency information. If the report scope is My Network, the report contains sections that summarize port utilization and latency for all devices, then a section that shows more information about the top devices with the highest port utilization and latency. If the report scope is one device, the report shows more detailed information about that device, including port-level utilization and latency.

    Modified: 2016-09-29