Professional Documents
Culture Documents
Lab Manual - OPNET Labs - EC354 PDF
Lab Manual - OPNET Labs - EC354 PDF
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
2. Click "OK"
3. Click "OK"
Now you are ready to proceed with the lab and associated tutorial.
1
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.
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.
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.
2
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.
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.
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.
1
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.
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.
1
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.
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.
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.
1
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.
2
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.
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.