Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Overview
OPNET work flow OPNET Basics and Structure Network Model Editor Node Model Editor Process Model Editor Other OPNET Editors
CEG 4286
After creating the network, you should choose network statistics that you want to work on or observe as you change the simulation parameters. For instance, for WLANs, these statistics could be communication delay, system throughput, packet error rate etc. You can choose wanted statistics by right clicking the on the network model window and choosing Choose individual statistics option as illustrated below in figure 2.
Running the simulation would be the next step after choosing statistics to analyze. Running the simulation can be accomplished by calling Configure Discrete Event Simulation option from the Simulation tab in the Network model window.
CEG 4286
The last step in simulating a network is analyzing the results of the network. Analyzing results means observing the change of selected network statistics relative to different simulation parameters. For a WLAN example this could be the change of network throughput relative to time as the load of the network changes, as illustrated in the figure below. Simulation results can be observed by right clicking the network window and choosing view results option from the drop down menu. The variation of the chosen statistics relative to time is shown in a graph.
CEG 4286
Project editor is the first interface that you come across with, when you start OPNET. You can specify network topology, choose statistics to analyze, run simulations and view results by this editor. Node editor specifies the internal structure of the components in project model. (e.g. router or hub) Process editor implements the algorithm in node models. (e.g. ARQ algorithms)
CEG 4286
Links enable the connection between nodes, e.g. An Ethernet link connecting multiple computers.
CEG 4286
Process model determines the behavior of the nodes by state transition diagrams, C-modules and built-in functions (i.e. Kernel procedures) Process model consists of Finite state machine or state transition diagrams Chunks of C-codes called C modules State/Temporary variables Every action taken by process model is called process In finite state machine, every state has enter executives (top half) and exit executives (bottom half) The states can be forced (green) and unforced (red). Unforced state waits for an interrupt to continue execution of exit executives. Example for green (forced) state: When first entered it performs enter execs in the first state Without any wait, it executes the exit execs (i.e. The reason it is called forced). (That is the only difference between the unforced state. Unforced [Red] state passes the control to kernel after enter execs and waits for a signal [interrupt] in order to continue with exit execs.) Evaluates the condition for transition. If the conditions are true it continues with the second state
CEG 4286
CEG 4286
The packet format editor lets you define the fields and the length of fields of a packet. For example IEEE 802.11 wireless channel simulations requires two types of packet formats, namely control packet format and information packet format. Different fields are color coded for illustration and the length of fields are proportional to the number of bits each field contains.
CEG 4286
The probe editor lets you choose the statistics to be collected during the simulation. With probe editor you can specify, save and load the statistics to be collected for any simulation.
CEG 4286