EC436 Lab 2 Fall, 2013

Introduction to the OPNET Modeler Suite

Objective: To familiarize you with OPNET and to learn how OPNET Modeler can be used to
model and evaluate the performance of a small internetwork. Along the way, you will learn to
Build a network quickly
Collect statistics about network performance
Analyze these results

Pre-lab: OPNET Configuration:

To establish a OPNET working directory within your own My Documents directory, please
complete the following steps before starting the OPNET tutorial. These steps are workstationunique and should be repeated if you move to a new computer in the lab.
1. Open OPNET Modeler 17.5
"Select Product Modules" window will open (Wireless will be checked)
2. Click "OK"
"Notification" window may be open
"The primary model directory (C:\Users\Administrator\op_models) ....
.... will fail until this problem is corrected"
3. Click "OK"
"Restricted Use Agreement" is open
4. Click "I Accept"
At the OPNET Modeler window click the following:
5. File>Manage Model Files>Add Model Directory
6. Browse to Libraries\Documents\My Documents
7. Click "Make New Folder" and name it OPNET
8. Click "OK"
9. Check "Include all subdirectories"
10. Check "Make this the default directory"
Now you are ready to proceed with the lab and associated tutorial.

Part 1 Review OPNET Modeler Introduction (OPNET Tutorial #1)

Please review the introduction to OPNET Modeler. This will begin to familiarize you with the
OPNET Modeler environment.

Part 2 Complete OPNET Modeler tutorial Small Internetworks (OPNET

Tutorial #2)
Please complete the OPNET Modeler tutorial Small Internetworks.

Part 3 Extend the work of the Small Internetworks tutorial

Create an additional scenario that extends the results of the tutorial of Part 2 by adding a network
on the third floor of the office building. This network will mirror the second floor expansion in
the tutorial but will be comprised of 20 workstations. This third floor network should connect to
the existing internetwork through the second floor network.
Determine whether or not this additional network overloads the existing server. In other words,
will the network remain stable? Justify your findings by including and commenting on
performance plots that compare Server load vs. time and Ethernet delay vs. time for all three
scenarios.

Part 4 Lab Submission Requirements

Lab report due date: Thursday, 12 Sep 2013
A full lab report is not required, but please summarize your work, results, and lessons learned in
a 2-3 page document. This write-up should include figures of all networks and relevant
performance plots. The results presented in all plots should be fully discussed in the text. The
lessons learned discussion should include the objectives identified above as well as all
introduced OPNET components.
A note to help with documenting work in OPNET
I have found that network diagrams and plots in OPNET can be easily transferred to
Microsoft Word using the ALT-PRINT SCREEN command.

EC436 Lab 3 Basic Processes (OPNET)

Fall, 2013
Objective: To continue to familiarize you with the modeling capabilities of OPNET. Specifically, you will
learn to work with both node and process models as well as the associated variables, macros, and transitions.

Part 1 Complete OPNET Modeler tutorial Basic Processes

Please complete the OPNET Modeler tutorial Basic Processes.
Additional notes:
1. In your lab write-up, include both the picture and code associated with all models generated during the
lab. Model code can be generated in text format by using the Generate Text Report command under the
File menu.
2. The Network Simulation Repositories preference can be found under the Discrete Event Simulation tab.

Part 2 Lab Submission Requirements

Lab report due date: Thursday, 19 September 2013
A full lab report is not required, but please summarize your work, results, and lessons learned in a 2-3 page
document. This write-up should include figures of all networks and relevant performance plots. The results
presented in all plots should be fully discussed in the text. The lessons learned discussion should include
the objectives identified above as well as all introduced OPNET components.
A note to help with documenting work in OPNET
I have found that network diagrams and plots in OPNET can be easily transferred to Microsoft
Word using the ALT-PRINT SCREEN command.

EC436 Lab 4 Packet Switching (OPNET)

Fall, 2013
Objective: To explore the performance of a packet switching network and to continue to familiarize you
with the modeling capabilities of OPNET. Specifically, you will learn to work with both packet and link
editors as well as continue to build your skills in developing process, node, and network models.

Part 1 Complete OPNET Modeler tutorial: Packet Switching I

Please complete the accompanying OPNET Modeler tutorial Packet Switching I.
Additional notes and tasks:
1. The order in which you create the packet stream and links is important. OPNET will automatically
assign input and output streams at a node in order.
2. Plot average and time average end-to-end delay results in addition to the plots specified in the tutorial.
Use the distance between nodes (this can be measured in your network model) to validate the steady
state value that the plots approach for end-to-end delay. Discuss any other delays (in addition to
propagation delay) that might be encountered and, for each run, estimate their mean value based on your
results.
3. Be sure to include in your lab report a discussion of the meaning of the utilization results you have
plotted.

Part 2 Complete OPNET Modeler tutorial: Packet Switching II

Please complete the accompanying OPNET Modeler tutorial Packet Switching II.
Additional notes and tasks:
1. Plot average and time average end-to-end delay results in addition to the plots specified in the tutorial.
Use the distance between nodes (this can be measured in your network model) to validate the steady
state value that the plots approach for end-to-end delay. Discuss any other delays (in addition to
propagation delay) that might be encountered and, for each run, estimate their mean value based on your
results. Include a discussion of how these results compare to those of Part 1.

Part 3 Lab Submission Requirements

Lab report due date: Thursday, 10 October 2013
A full lab report is not required, but please summarize your work, results, and lessons learned in a 2-3 page
document. This write-up should include figures of all networks and relevant performance plots. The results
presented in all plots should be fully discussed in the text. The lessons learned discussion should include
the objectives identified above as well as all introduced OPNET components.
A note to help with documenting work in OPNETI have found that network diagrams and plots in
OPNET can be easily transferred to Microsoft Word using the ALT-PRINT SCREEN command.

EC436 Lab 5 M/M/1 Queue (OPNET)

Fall, 2013
Objective: To explore the performance of an M/M/1 queuing system and to continue to familiarize you
with the modeling capabilities of OPNET. Specifically, you will learn to work with both node and process
models as well as the associated variables, macros, and transitions.

Part 1 Complete OPNET Modeler tutorial M/M/1 Queue

1. Please complete the OPNET Modeler tutorial M/M/1 Queue.
Additional notes:
Repeat the steps on pages 18-21 for the queuing delay. Note and discuss these results for both
queuing delay and queue size.
Mathematically verify your results for both average queuing delay and average queue size using the
M/M/1 queuing analysis we discussed in lecture. Check your results against predicted values for
both waiting time and total time in the system as well as both mean queue size and mean total
number of packets in the system. Which do your results more closely approximate?

Part 2 Validate the M/M/1 performance analysis discussed in lecture using your
findings
1. Plot your observed queue size results against predicted mean queue size and mean total number of
packets in residence as a function of packet arrival rate.
2. Plot your observed delay results against predicted mean delay in the queue and mean total delay in the
system as a function of packet arrival rate.
3. What are your conclusions?
Additional notes:
This will take multiple simulation runs to build the plots. Each plot should contain two curves and a
set of data points curves for the predicted behavior from our queuing equations for both packets in
residence and packets in the queue only and data points for your observed behavior from the
OPNET simulations.
Data from OPNET plots may be exported into Excel by right-clicking on the plot and selecting the
appropriate menu item. Once in Excel, they may be fed into MATLAB if you prefer to use that for
plotting your results.

Part 3 Lab Submission Requirements

Lab report due date: Thursday, 17 October 2013
A full lab report is not required, but please summarize your work, results, and lessons learned in a 2-3 page
document. This write-up should address all assignments in the lab as well as include figures of all networks
and relevant performance plots. The results presented in all plots should be fully discussed in the text. The
lessons learned discussion should include the objectives identified above as well as all introduced OPNET
components.
A note to help with documenting work in OPNET
I have found that network diagrams and plots in OPNET can be easily transferred to Microsoft
Word using the ALT-PRINT SCREEN command.

EC436 Lab 6 Aloha, CSMA, CSMA/CD

Fall, 2013
Objective: To explore the performance of a contention-based medium access schemes and to
continue to familiarize you with the modeling capabilities of OPNET. Specifically, you will
develop models for the ALOHA and CSMA medium access protocols and will explore the
CSMA/CD medium access scheme that forms the foundation for Ethernet. During this OPNET
lab, you will also learn to construct more advanced protocols, design a simple channel interface
and execute parametric simulations.

Part 1 Complete OPNET Modeler tutorial

Please complete the OPNET Modeler tutorial CSMA/CD.

Part 2 Lab Submission Requirements

Lab report due date: Wednesday, 13 November 2013
A full lab report is not required, but please summarize your work, results and lessons learned in a
1-2 page document. Your report should include all relevant plots accompanied by a brief
discussion of each. A couple of notes to help with documenting work in OPNET
I have found that network diagrams and plots in OPNET can be easily transferred to
Microsoft Word using the ALT-PRINT SCREEN command.
Model code can be generated in text format by using the Generate Text Report
command under the File menu.