Types of Traffic

You can model the following types of traffic:

Explicit Traffic

“Explicit traffic” is packet-by-packet traffic, in which the simulation models each packet-related event (packet created, packet queued, packet transmitted, etc.) that occurs during the simulation. Explicit traffic modeling provides the most accurate results because it models all protocol effects. However, this also results in longer simulations and higher memory usage (because the simulation allocates memory for each individual packet).

There are three general methods for explicitly modeling traffic:

  • Packet generation – You can configure certain node objects to generate streams of generic packets. This is a basic method of adding traffic to a network topology.
  • application demands – You can create application demands to represent the traffic flowing between two nodes. The traffic generated by application demands can be purely discrete (explicit), purely analytic (background), or a combination of these two (hybrid).
  • Application traffic models – You can include a set of models for generating traffic based on standard applications such as FTP, HTTP, voice, and e-mail. You can also use the generic “custom application” model to represent a broad range of applications (such as multi-tier ERP transactions) that do not correspond to the traffic patterns of standard network applications.

Background Traffic

“Background traffic” is analytically modeled traffic that affects the performance of explicit traffic by introducing additional delays. Unlike explicit traffic, background traffic can affect not only discrete event simulations, but also flow analyses. Discrete event simulations that include background traffic use the hybrid simulation model. This model includes the effects of background traffic to calculate queue build-ups on intermediate devices and delays based on the queue length, at any time during in the simulation. Because each packet that produces traffic on the network is not explicitly modeled, using background traffic can speed up simulations considerably.

Background traffic takes three forms:

  • Traffic Flows – A traffic flow describes an end-to-end flow of traffic from a source to one or more destination nodes. You can create traffic flows manually, using traffic flow objects (covered later in this chapter). You can also import traffic flows from text files and spreadsheets. If you have a license for the XDI (eXpress Data Import) module, you can also import traffic from programs like Netflow Collector and NetScout nGenius.
  • Baseline Loads – This type of traffic (also called “static background utilization”) represents traffic as a background load on a link, node, connection, or LSP. Unlike a traffic flow, which can span multiple links and nodes, a traffic load is “static” and applies to one object. You can convert existing link loads to traffic flows, which allows flow analyses to account for these loads. You can import baselines from external ASCII files; if you have a license for the XDI (eXpress Data Vendor Import) module, you can also import data from programs like CA eHealth–Network, MRTG and InfoVista.
  • Application demands – You can use application demands to represent background traffic flowing between two nodes. Besides background traffic, you can also configure application demands to be purely discrete (explicit) traffic, or a combination of these two (hybrid).

Traffic References

The following table lists references to information on creating, importing, and working with network traffic.

Table 1: Network Traffic: References

Topic Reference
Background Traffic
(overview and detailed discussion)
“Analyzing Background Traffic“
“Background Traffic and Statistics“
“Limitations of the Background Traffic System“
Generated Traffic Generated Traffic
“RPG“
Application Traffic Models “Applications“
Application Demands Application Demands
Traffic Flows Traffic Flows
Baseline Loads Baseline Loads
“Converting Link Loads to Traffic Flows“
Paths Using Paths to Represent Virtual Circuits

Generated Traffic

The model library includes traffic source/sink node models, which generally have names that end with “_station” or “_uni_src”. These models contain a compound attribute called “Traffic Generation Parameters” that lets you generate streams of “generic” packets (that is, packets that contain no protocol data above layer 2). This method of traffic is mainly useful for studying layer-2 technologies such as Ethernet, Frame Relay and ATM.

The model library also includes a Raw Packet Generator (RPG) model for modeling self-similar traffic. For more information, see “RPG“.

Application Traffic

The model library includes a large set of models that allow you to create explicit traffic based on applications such as FTP, HTTP, voice, video conferencing, etc. You can also use the Custom Application model to generate traffic based on other types of applications (such as multi-tier ERP exchanges.

For information about creating application traffic, see “Applications“.

Application Demands

When your simulation study is not focused on the behavior of the applications that generate traffic in the network, application demands are a simple way to represent that traffic in your network model. These demands characterize traffic in terms of the size and rate of the requests and responses going back and forth between two nodes.

Configuring application demands is simpler than configuring the application traffic models because all of the configuration occurs on the demand itself—no additional configuration is needed on the source or destination nodes to support the applications. The application traffic models, however, offer a more detailed characterization of the different types of applications (FTP, E-mail, HTTP, …). The models are the preferred way of representing network traffic when your simulation study is focused on the behavior of one or more applications.

As with the application traffic models, the traffic from application demands flows as a series of requests and responses between the application layers of the end nodes. The source node of the application demand sends requests to the destination node, which returns responses to the source. For a client-server architecture, configure the demand so that the client is the source node and the server is the destination node.

Table 2: Feature Comparison of Application Demands and Application Models

Feature Application Demands Application Models
Models individual requests and responses sent by the application yes yes
Traffic Mix attribute to model traffic as analytic, discrete, or hybrid traffic yes yes – voice and video conferencing
no – all others
Detailed configuration for application-specific parameters no yes
Global statistics for response time, traffic sent, and traffic received no yes
Object statistics for response time, traffic sent, and traffic received yes yes

本站文档由 北京智网畅联科技有限公司 整理、翻译并提供 · Documentation compiled and provided by Beijing ZNetLink Technology Co., Ltd.

交流群 · QQ Group:OPNET/智网妙算网络仿真交流群(群号 486383494)

原文档 © 2017 Riverbed Technology · 本站为公益翻译,由 AI 辅助完成,请仔细甄别

Original documentation © 2017 Riverbed Technology. Community translation, AI-assisted. Contact: jiazequn@znetlink.com