Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
  
[+] Expand All
[-] Collapse All

Related Documentation

    Scripts


    Exhaustive Single Element Failures


    The exhaustive single failure scripts fail all network elements of a given type, one at a time.

    Figure 99: Single Failure Simulation Window

    Single Failure Simulation Window
    • Exhaustive Node Failure: Exhaustively fails every single node in the network.
    • Exhaustive Link Failure: Exhaustively fails every single trunk in the network.
    • Exhaustive Site Failure: Exhaustively fails all sites in the network. A site file is required to define nodes within the same site. Nodes that are not grouped within a site are considered sites by themselves.
    • Exhaustive Slot Failure: Exhaustively fails all slots that are defined in the network (router networks only).
    • Exhaustive Card Failure: Exhaustively fails all cards that are defined in the network. For all ATM networks, cards can be specified in the definition of links. Go to the Links detail tab and select the Location tab. For certain router models, cards can be defined through the Equipment View feature. Select Inventory > Hardware Inventory, or right-click on a node and select View > Equipment View. Note that the Hardware Model feature requires a license.
    • Exhaustive SRLG/Facility Failure: Fails all facilities. A facility file is required to define node and trunk facility associations. Trunks that are not associated with a facility are considered to be facilities by themselves.
    • Exhaustive Parallel Links Failure: Exhaustively fails all trunks between all node pairs.
    • Exhaustive Voice Trunk Group Failure: (Requires a license for voice). Exhaustively fails all voice trunk groups defined in the network. Select Network > Voice > Trunk Group to examine the trunk groups in your network. Addition of trunk groups through the Java user interface is not supported at this time, although modification is supported. To define trunk groups, the trunk group file should be edited through a text editor.

    Reports


    • The Peak Link Utilization Report (Simulation Reports > Network Statistics > Peak Link Utilization) records the maximum trunk utilization for each trunk during the period of all the selected simulations and the element whose failure triggered this maximum utilization. Peak utilization is reset each time predefined scenarios are run. See Simulation Reports for details on this report. The resulting peak utilizations can also be viewed graphically on the Standard map by selecting Utilization Legends > Peak Util.
    • PeakSimLink: The PeakSimLink report contains detailed information on oversubscribed links after the exhaustive failure simulation.
    • PeakSimRoute:The PeakSimRoute report contains detailed information of failed demands or tunnels.
    • PeakSimReroute: The PeakSimReroute report contains detailed information for rerouted demands or tunnels. To generate this report, select Generate Detailed Reroute Report from the Options tab.
    • PeakSimSummary: The PeakSimSummary report contains a summary of all exhaustive failure simulations performed.

    Exhaustive Multiple Element Failures


    Figure 100: Multiple Failure Simulation Window

    Multiple Failure Simulation Window

    To run an exhaustive failure script for the simultaneous failure of 2 or 3 elements, select the Multiple Failure tab. Select the number of elements to be failed together (Double or Triple), select the Exhaustive radio button, and then select the element type to be failed (node, link, etc.) for the Failures Type. For example, selecting Double, Exhaustive Failure, for the Failure Types: Node and Link and then clicking the Run button will result in an exhaustive failure simulation of node & node, node & link, and link & link combinations.

    To randomly simulate a specified number of double or triple failures, rather than all possible failure combinations exhaustively, select “Cases to Simulate” instead of Exhaustive Failure, and enter the number of cases to simulate.

    Modified: 2017-04-04