Introduction

OPNET MODELER is used to design and study communication networks, devices, protocols and applications. It provides a graphical editor interface to build models for various network entities from physical layer modulator to application processes [12].

OPNET MODELER Tools

OPNET supports model specification with a number of tools, called editors. These editors handle the required modeling information in a manner that is similar to the structure of real network systems. Therefore, the model-specification editors are organized hierarchically. Model specifications performed in the Project Editor rely on elements specified in the Node Editor. The rest of the editors are used to define various data models, new links and nodes, etc. This organization is described below [1, 13, 7, 11]: Project Editor Project Editor is used to develop network models. Network models are made up of subnets and node models. This editor also includes basic simulation and analysis capabilities. The Project Editor is the main staging area for creating a network simulation. From this editor, you can build a network model using models from the standard library, choose statistics about the network, run a simulation and view the results. It is also possible to create node and process models, build packet formats, and create filters and parameters, using specialized editors that you can access from the Project Editor. In Figure 3.1 an example of the project editor view of a Wireless Network is shown. Node Editor Node Editor is used to develop node models. Node models are objects in a network model. They are made up of modules with process models. The Node Editor lets you define the behavior of each network object. Behavior is defined using different modules, each of which models some internal aspect of node behavior such as data creation, data storage, etc. A network object is typically made up of multiple modules that define its behavior. In the Figure 3.2, there are some parts of a routers internal structure, such as a TCP module, an UDP module and an IP module. Process Editor Process Editor is used to develop process models. Process models control module behavior and may reference parameter models. This editor lets you create process models, which control the underlying functionality of the node models created in the Node Editor [8]. Process models are represented by finite state machines (FSMs), and are created with icons that represent states and lines that represent transitions between states. Operations performed in each state or for a transition are described in embedded C or C++ code blocks. External System Editor External System Editor is used to develop external system definitions. External system definitions are necessary for simulation. Link Model Editor Link Model Editor creates new types of link objects. Each new type of link can have different attribute interfaces and representation. It is also possible to edit and view link models already created.

Packet Format Editor Develop packet formats models are created by using Packet Format Editor. This editor defines the internal structure of a packet as a set of fields. A packet format contains one or more fields, represented in the editor as colored rectangular boxes. The size of the box is proportional to the number of bits specified as the fields size. ICI Editor ICI Editor is used to Create, edit, and view interface control information (ICI) formats. ICIs are used to communicate control information between processes. PDF Editor The PDF (Probability Density Function) Editor describes the spread of probability over a range of possible outcomes. A PDF can model the likelihoods associated with packet interarrival times, or it can model the probability of transmission errors. This editor allows creating, editing, and viewing probability density functions (PDFs). Path Editor The Path Editor defines path models; each path object's underlying model determines its attribute interfaces, presentation, and behavior. Demand Editor The Demand Editor defines demand models; each demand object's underlying model determines its attribute interfaces, presentation, and behavior. Link Editor The Link Editor supports the definition of reusable link models that are used to create link objects in the Project Editor. Each link object's attribute interfaces, presentation, and behavior, are determined by the link model that it relies upon. Once all the different interfaces are shown, it is necessary to describe the different steps to build a network model and to simulate it. For the purposes of this thesis work, its only necessary to work with the project.

The Modeler Workflow

This section outlines the workflow when using OPNET. Create Network Model The first step is to create the networks models. It is necessary to generate the network to simulate in any of the following three ways: Placing individual nodes from the object palette into the workspace. Using the rapid configuration tool. And/or importing the network from an external data. Furthermore, you have to introduce the traffic you want to run through the network. There is two main ways of putting traffic in the model: a) Importing b) Manually specifying Choose Statistics Afterwards and before running a simulation, it is necessary to choose the statistics we want to collect. OPNET does not automatically collect all statistics in the system because there are so many available that you may not have enough disk space to store them. Specifying statistics is a straightforward task which is performed through the GUI.

Run Simulation The third thing to set is configuring the parameters of the simulation and running them. Running simulations is typically thought of as the next-to-last step in the simulation and modeling process, the last step being results analysis. However, simulation is typically done many times in the modeling process to check the rightness of the generated network. There are different kinds of analysis that can be done in OPNET MODELER. 1. Discrete Event Simulation 2. Flow Analysis 3. Failure Impact Analysis 4. NetDoctor Validation Discrete event simulation provides the most detailed results but has the longest running times. This is because it does a more thorough analysis than the others, handling explicit traffic, conversation pair traffic, and link loads. The other types answer specific types of questions and generate results much faster than a discrete event simulation. A flow analysis, for example, handles only conversation pair traffic (flows) and a NetDoctor validation does not consider traffic at all. Licenses for generating Discrete Event Simulations (DES) are available for this studies and analysis. View and Analyze Results It is the last step of simulation. The results can be watched from the Project Editor or from the Analysis Tool. The Analysis Tool provides the capability to extract data from simulation output files, and to manipulate and display it according to various plotting methods. Data can be manipulated through built-in operations in a different way to get wanted information. Hence, the final workflow of a project could be as follows: Create project Create baseline scenario - Import or create topology - Import or create traffic - Choose results and reports to be collected - View results and analyze them Iterate by duplicating the scenario and changing parameters OPNET uses a project and scenario approach to model networks. Project is a collection of related network scenarios in which each explores a different aspect of network design. A project contains at least one scenario and a scenario is a single instance of a network containing all the information. It is possible to run all the scenarios of the network at the same time and compare the results of each one. This allows the scenarios to check if a server will support and increment of the traffic, the effect of the increment of the traffic in a link in the response of a service, etc [14

Overview
The OPNET is a very powerful network simulator. Main purposes are to optimize cost, performance and availability. The goal of this laboratory is to learn the basics of how to use Modeler interface, as well as some basic modeling theory. The following tasks are considered: Build and analyze models. Configure the object palette with the needed models. Set up application and profile configurations. Model a LAN as a single node. Specify background utilization that changes over a time on a link. Simulate multiple scenarios simultaneously. Apply filter to graphs of results and analyze the results. Before starting working on the Exercise part of this laboratory, one has to read the Preparations part.

Preparations
To build a network model the workflow centers on the Project Editor. This is used to create network models, collect statistics directly from each network object or from the network as a hole, execute a simulation and view results. See Fig.1.

Project Editor
The main staging area for creating a network simulation is the Project Editor. This is used to create a network model using models from the standard library, collect statistics about the network, run the simulation and view the results. Using specialized editors accessible from the Project Editor via File New one can create node and process models, build packet formats and create filters and parameters.
Figure 2 - A network model built in the Project Editor

Depending on the type of network being modeled, a network model may consist of subnetworks and nodes connected by point-to-point, bus, or radio links. Subnetworks, nodes, and links can be placed within subnetworks, which can then be treated as single objects in the network model. This is useful for separating the network diagram into manageable pieces and provides a quick way of duplicating groups of nodes and links.

The Node Editor

The Node Editor is used to create models of nodes. The node models are then used to create node instances within networks in the Project Editor. Internally, OPNET node models have a modular structure. You define a node by connecting various modules with packet streams and statistic wires. The connections between modules allow packets and status information to be exchanged between modules. Each module placed in a node serves a specific purpose, such as generating packets, queuing packets, processing packets, or transmitting and receiving packets.

The Process Model Editor

To create process models which control the underlying functionality of the node models created in the Node Editor one can use the Process Editor. Process models are represented by finite state machines (FSMs) and are created with icons that represent states and lines that represent transitions between states. Operations performed in each state or for a transition are described in embedded C or C++ code blocks.

The Link Model Editor

This editor enables for the possibility to create new types of link objects. Each new type of link can have different attribute interfaces and representation. Specific comments and keywords for easy recognition are also possible.

The Path Editor

The Path Editor is used to create new path objects that define a traffic route. Any protocol model that uses logical connections or virtual circuits such as MPLS, ATM, Frame Relay, etc can use paths to route traffic.

The Packet Format Editor

By making use of this editor it is possible to define the internal structure of a packet as a set of fields. A packet format contains one or more fields, represented in the editor as colored rectangular boxes. The size of the box is proportional to the number of bits specified as the fields size.

The Probe Editor

This editor is used to specify the statistics to be collected. By using different probes there are several different types of statistics that can be collected, including global statistics, link statistics, node statistics, attribute statistics, and several types of animation statistics. It is mentioned that similar possibilities for collecting statistics are also available under the Project Editor. These are however not as powerful as the Probe Editor.

Sequence Editor
In the Simulation Sequence Editor additional simulation constrains can be specified. Simulation sequences are represented by simulation icons, which contain a set of attributes that control the simulations run-time characteristics.

The Analysis Tool

The Analysis Tool has several useful additional features like for instance one can create scalar graphics for parametric studies, define templates for statistical data, create analysis configurations to save and view later, etc.

The Project Editor Workspace

There are several areas in the Project Editor window (a.k.a. workspace) that are important for building an executing a model. See Figure 11 as an example.

The Menu bar

Each editor has its own menu bar. The menu bar shown below appears in the project editor.

Buttons
Several of the more commonly used menu bar can also be activated through buttons. Each editor has its own set of buttons. The buttons shown below appear in the Project Editor. 1. Open object palette 2. Check link consistency 3. Fail selected objects

4. Recover selected object 5. Return to parent subnet 6. Zoom in 7. Zoom out 8. Configure discrete event simulation 9. View simulation results 10. View web-based reports 11. Hide or show all graphs

The message area

The message area is located at the bottom of the Modeler window. It provides information about the status of the tool. Occasionally, the messages Modeler generates may be larger than the message area. You can left-click on the icon next to the message area to open the message buffer, where the entire message displays.

Tool tips
If you place your cursor over a button or a menu selection, a help balloon soon appears.
Figure 15 - Tool tips

Online Documentation. Select Help => Online Documentation