Report Manager: Simulation Reports

Link Utilization Reports

The Link Utilization Report displays the link and bandwidth information under normal and peak conditions obtained from failure simulation runs. Thus, before opening this report, you must first run a failure simulation script (Simulation > Simulation Scenarios). The results depend on the settings of the failure simulation.

Figure 1: The Link Peak Utilization Report

Field	Description
Linkname	The name of the link.
Anode	The ID of the source node where the link originates.
Aloc	The name of the source node where the link originates.
ACountry	The country where the source node is located.
Znode	The ID of the destination node where the link terminates.
Zloc	The name of the destination node where the link terminates.
ZCountry	The country where the destination node is located.
Vdr	The vendor associated with this link. Possible values for vendors include those that are specific to a certain country or region, and are listed in the tariff database. If a vendor is not specified, this value is set to the default value DEF.
Type	The type of trunk being used. The trunk type is subsequently used in determining link pricing and bandwidth availability.
TotalBw	The total bandwidth of the link from node A to Z.
UsedBw	The amount of bandwidth used on this interface by the demand requirements from the demand file.
PeakBw	The peak (maximum) bandwidth used by the demand requirements between node A and Z during failure simulation.
UtilPct	The percentage of total bandwidth used by demands prior to the failure simulation.
PeakUtilPct	The peak percentage of total bandwidth used during failure simulation. This is calculated as PeakBW divided by TotalBW.
#Demand	The number of demands carried by the link in the normal mode
PeakCnt	The peak number of demands carried by the link during failure simulation.
#OverSubCnt	The number of failures that caused the used bandwidth to exceed (1-fatpct)*TotalBw.
LoadBW_n	The amount of bandwidth used on this interface by the demand requirements during period n of the trafficload file.
PeakLoadBw_n	The peak (maximum) bandwidth used during failure simulation for this period n of the trafficload file.
SimType / SimEvent	The type of simulation event (for example, NDFAIL stands for node failure) that triggered the worst traffic load on either end of the link, and the associated event detail (for example, name of failed network element).
Cnt_SimType / Cnt_SimEvent	The type of simulation event that triggered the worst demand count on the link (for example, NDFAIL stands for node failure), and the associated event detail (for example, name of failed network element).

Interactive Failure (SIMRPT) Reports

The Interactive Failure report is a trace file that records statistics during an interactive failure simulation. To create the report, you must enable the Trace option in the Failure Report tab of the Failure Simulation Options (Tools > Options > Failure Simulation). Then, perform an interactive failure sequence by failing nodes/links via the map right-click menus or via Simulation > Fail Link/Node/Facility. When you run or step through the simulation, results are appended onto the Interactive Failure report.

The Interactive Failure report is typically used for quick analysis. The report is usually used following another failure simulation. For example, you might first perform an Exhaustive Link Failure, during which a few problem links are identified. You may then want to analyze those link failures further by performing an interactive failure simulation in which just those links are brought down and up.

Note:

If you change any failure simulation options via Tools > Options > Failure Simulation and press “OK”, the SIMRPT is overwritten (that is, cleared). Note that for every network session (each time you open a network project or specification file), you will need to set the failure simulation options, as they are not saved.

Because this is a running trace file, you should not delete the SIMRPT file during a network session. The results of an interactive failure simulation may not be saved in this event.