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

    Viewing the Results


    Trafficload


    If the period “All” was designed for, then not only will the demands be updated, but also the trafficload file which includes the designed bandwidth of the demand for multiple periods. The T-Solve window will only display the results for the final period. However, the per-period results can be viewed per link after the design by right-clicking the link on the map and selecting Traffic Load > Interface vs Demand. Select Bar/Line to view the chart as a line chart. This chart will show how well the utilization based on the designed trafficload bandwidth matches with the actual interface load.

    Figure 1: Trafficload Window

    Trafficload Window

    Save the network to a new directory using File > Save Network... Navigate to this directory in the File Manager and open the designed trafficload file to see the bandwidths designed for each period.


    Console


    Intermediate results will be displayed in the console. In each successive iteration, the program attempts to minimize the cost function, which is based on the linkDiff + shape weight * shapeDiff, where the linkDiff is a function of the sum of the differences between measured interface traffic and an interface’s total demand bandwidth over the sum of the link bandwidths.

    The following information is also indicated to provide warnings regarding incomplete data. The links indicated below will not be considered into the cost function. These should be checked to see if that is the desired behavior or not, or if additional information can be supplied.

    • #link_interface without traffic and demands=n : Indicates number of links with no seed demands nor measured interface traffic.
    • #link_interface without traffic=n : Indicates number of links with seed demands routed over it, but no measured interface traffic.
    • #link_interface without demands=n : Indicates number of links with measured interface traffic, but without seed demands routed over it. If these are links that are important, then it may be a good idea to add the appropriate flow(s) that goes through this link into the demand file. In some cases, however, you may not worry about the link, in which case it can be ignored. For example, this might be the case if you are only concerned about running designs and simulations for Area 0 traffic and link loading, but this is a link in a different area.

    Reports


    After the iterations are completed, the following output files will be saved to the server:

    • TMLINK.runcode : The Tomogravity Link Traffic Comparison Report provides information (per link) regarding differences between measured interface traffic and the interface’s total demand load (see Links Tab)
    • TMShape.runcode : The Tomgravity Demand Traffic Shape Report provides information regarding the shape matrix and the traffic matrix.
    • TMPATH.runcode : Provides Path Placement and bandwidth Information
    • TMLOAD.runcode : The T-solve Demand Bandwidth vs Demand Load Comparison Report provides information (per flow) about the difference between model demand bandwidth and measured demand bandwidth from the trafficload file

    Once complete, select Network > Elements > Demands to view the changed demand bandwidths assigned by the Traffic Matrix Solver.


    Summary Tab


    Click the Summary tab to see a summary of the statistics from the links tab.

    • overallFit : Sum of the absolute differences between the measured interface traffic and interface’s total demand load divided by the sum of the measured traffic plus geometric mean of the measured and modeled traffic. Note that the results are independent of the link bandwidth.
    • formula : overallFit = |measured traffic - demand| / [measured traffic + SQRT (measured traffic * modeled traffic)]
    • For example, a 10G link between two nodes with measured interface traffic 5G for both interfaces on that link and 8G bidirectional demand over the link. In this example the absolute difference is |5G - 8G| = 3G. The geometric mean is SQRT(5*8) = 6.325. Thus the overallFit = absolute difference / (measured traffic + geometric mean) = 3/(5 + 6.325) = 0.2649 = 26.49%.
    • ShapeError : The shaping error is based on a comparison the shaping matrix derived from normalizing the seed demands’ bandwidth matrix, against the shaping matrix derived from normalizing the demands’ new bandwidth matrix.
    • WorstLinkDiff : Indicates the largest difference between the measured and model utilization percentage, i.e., the highest value for Abs Diff Util % in the Links tab.

    When evaluating the fit of the new traffic matrix to the interface traffic file, the linkDiff provides an averaged difference, and the worst link diff provides the worst case difference for a particular link. Ideally, these two numbers should be as close to zero as possible.


    Links Tab


    Select the Links tab of the T-Solve window.

    Figure 2: Links Tab

    Links Tab

    Here, you can view statistics comparing the original measured interface traffic file (Measured Traffic and Measured Util %) with the traffic load and utilizations computed based on the set of end-to-end demands (Model Traffic and Model Util %).

    • Name : Link’s name
    • Direction : A2Z or Z2A direction of the link
    • Node,Interface : The node and interface corresponding to the given direction on the link
    • Remote Node : The other end node of the link
    • Type : The link’s Trunk Type
    • Known Model Traffic : Traffic load on the link based on measured flow bandwidth (based on the trafficload file)
    • Measured Traffic : Traffic load on the link according to measured interface traffic file (based on the egress/ingress files)
    • Diff Traffic : The difference between Model Traffic and Measured Interface Traffic. Note that the values -1, -2, -3, and -4 have special meanings here: “-4” means that there is measured interface traffic, but model traffic is 0, “-3” means that there is model traffic, but measured interface traffic is 0, “-2” means that there is model traffic but measured traffic is missing, and “-1” means the model traffic is 0, but measured interface traffic is missing.
    • Measured Util % : Percentage Utilization of the link according to measured interface traffic file (based on the egress/ingress files)
    • Model Util % : Percentage Utilization of the link according to the sum of bandwidth of demands over the link (based on the demand file0
    • Diff Util % : Model Util % - Measured Util %
    • Abs Diff Util % : The absolute value of Diff Util % (This number will always be positive)

    Modified: 2016-11-08