Model Features: ATM

This section provides a list of the main features available in the ATM model. ATM models are implemented based on information available from the sources listed in Reference Documents: ATM.

The ATM model supports the following connection types:

  • ATM PVCs and PVPs:
    • Soft—Fully dynamically routed, or with partially or fully pre-configured paths
    • Hard—Fully static paths
  • Flow Analysis models SVCs as SPVCs with configured tear-down times, while DES supports SVCs that are brought up on-demand when a call arrives from the application layer
  • Static stitching of hard and soft ATM PVCs
  • Static stitching of hard and soft ATM PVPs (Flow Analysis only)
  • (Flow Analysis only) Bandwidth allocations for hard PVCs, even when the circuit fails end-to-end
  • (Flow Analysis only) Tunneling of hard or soft PVCs through PVPs
  • Unidirectional/Bidirectional connections—Unidirectional connections can be modeled in DES and Flow Analysis as bidirectional connections with zero reservation in one of the two directions
  • Asymmetric connections (different traffic contracts in each direction)
  • (Flow Analysis only) Visualize traffic routes, bottlenecks, and routability of PVCs
  • Set up SVC connections on a per-demand basis
  • Accelerate capacity planning using the Call Only Mode feature on ATM uni-source nodes
  • Display VC routes using the Route Browser
  • (DES only) Signaling is provided for point-to-point, full-duplex SVCs, SPVCs, and SPVPs. SPVP/PVP modeling is limited to support for tunneling on-demand SVCs through an (S)PVP if an appropriate virtual path is configured to the destination. In this context, the PVPs should be represented in the model by the atm_spvx or atm_pvx connections with the connection type set to “PVP." Dynamic call setup and teardown procedures are supported.

For more information, see Types of Connections.

The ATM model supports the following routing and interworking protocols:

  • FRF.8:
    • Fully dynamic or fully static routing of Frame Relay or ATM/Frame Relay multi-domain circuits over ATM core using FRF.8 (Flow Analysis only)
    • Static configuration of FRF.8 stitching of Frame Relay and ATM circuits
  • FRF.6 (DES only):
    • Static configuration of FRF.6 tunneling of Frame Relay over ATM circuits
  • (Flow Analysis only) PNNI/VNN interworking and the ability to enable/disable dynamic routing over particular trunks:
    • Physical Trunks
    • Virtual/PVP Trunks
  • Distance Vector and PNNI dynamic routing protocols
  • IP routing protocols over ATM circuits

For more information, see Routing Protocol Attributes.

Note: IP traffic over ATM or Frame Relay circuits is not reflected in ATM web reports.

The ATM model supports traffic modeling as discussed in Traffic Modeling.

The ATM model supports the following ATM routing features:

  • Call Admission Control (CAC) algorithms
    • Lucent/Ascend (Flow Analysis only)
    • Custom—Support for user-supplied CAC function plug-ins written in Python (Flow Analysis only)
    • Guerin CAC (Flow Analysis only)
    • GCAC as specified by the ATM Forum standards

Note: The GCAC algorithm is used as ACAC by default by both DES and Flow Analysis.

  • (DES only) Traffic control support is as follows:
    • Support for both CAC and Usage Parameter Control (UPC)
    • Based on specific service category, traffic parameters (PCR, SCR, MCR, MBS), and QoS parameters (ppCDV, maxCTD, CLR)
    • Prevents all calls with unsupportable traffic requirements from establishing a connection, and prevents established calls from degrading network service below the specified QoS requirements
  • (DES only) Buffering
    • Output port buffering is modeled and supports the round-robin and weighted round-robin queueing schemes
    • Buffers can be configured at each switch for various QoS levels. A QoS level is made up of the QoS category (CBR, rt-VBR, nrt-VBR, ABR, UBR), the QoS parameters, (ppCDV, max CTD, CLR), and the traffic parameters
  • Supported Routing Constraints
    • Available bandwidth
    • Fixed or shared bandwidth pools (per-QoS class basis)
    • Oversubscription (per-QoS class basis)
    • Cell Transfer Delay (CTD)
    • Cell Delay Variation (CDV)
    • Cell Loss Ratio (CLR)

Note: For more information on routing constraints, see the Per-Port Configuration attributes in Route Selection Attributes.

  • Multiple levels of PNNI hierarchy
  • (Flow Analysis only) Dynamic peer group formation and partitioning
  • Trunk aggregation for non-virtual trunks
  • Crankbacks
  • IMA groups
  • (Flow Analysis only) Prune links from source route computation based on user-defined trunk/circuit affinity

The following PVC and ATM-level traffic imports can be configured to occur at simulation time:

  • (Flow Analysis only) Traffic/PVCs from XML files generated by the NavisCore import utilities
  • (Flow Analysis only) Traffic/PVCs from ATM text import (ATI) files
  • Import of traffic/PVCs from GDF files, compatible with DES

Note: In Flow Analysis, any PVCs or traffic imported from a file at simulation time are reflected in the ATM web reports. The Flow Analysis output tables will not reflect any of the ATM traffic imported in this manner and will not list the routes of individual circuits; however, they will reflect the correct link/buffer reservation statistics. In addition, Survivability Analysis will display full information in its output tables about the failure's impact on the ATM layer, including circuit re-routes, failures, and so on. Such PVCs/traffic are invisible to the IP layer. Only pure ATM simulations can be performed using this import method—not IP-over-ATM, IP-over-Frame Relay, or Capacity Planning. In DES, these restrictions do not apply; IP or application-layer traffic can be sent through these circuits.

Additional support:

  • Ability to use demand sequencing (e.g., order connections by QoS class, bandwidth, random, etc.)
  • Ability to set connection limits on a per-node, per-card (Flow Analysis only), or per-port basis
  • Ability to pre-configure baseline ATM buffer reservations without modeling PVCs explicitly
  • Ability to convert the results of ATM simulation to baseline reservations to speed up incremental routing studies

Additional DES support:

  • Configurable parameters for Service Specific Connection Oriented Protocol (SSCOP)
  • Simulation efficiency modes to reduce the duration of large simulations without sacrificing accuracy
  • An API package that applications can use to create, destroy, and send packets through an ATM Virtual Circuit
  • SPVC reroute capability to reroute SPVC connections on failure