Escolar Documentos
Profissional Documentos
Cultura Documentos
1
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
What is Modeler?
An environment for building protocols and device models. An environment to plan changes by illustrating how the networked environment will perform. An environment that includes hundreds of pre-built models, used to study performance changes of your network: organizational scaling, technology changes, and application deployment.
2
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Goals
Learn what problems can be solved with Modeler Learn how to use the Modeler software in a hands-on environment Use Modeler to solve real problems
3
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Expectations
Prerequisites:
Ability to program in C or C++ or at least be comfortable in reading/understanding C or C++ code Basic understanding of networks For basic information, see http://compnetworking.about.com/library/glossary/blglossary.htm http://www.whatis.com
This class will move quickly Ask questions. It will enhance your learning experience, as well as the other students.
4
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Course Content
DAY 1: Introduction OPNET Technologies
History of OPNET OPNET Services and Support
DAY 2: Events and Event List Concepts Node Modeling Node Modeling {LAB} Process Modeling {LAB} Collecting Scalar Statistics
DAY 3: Modeling Large Networks Importing Topology and Traffic Wireless Modeling Wireless Modeling {LAB} OPNET Debugger {LABs} Publishing & Animation {Mini-labs} Overview of Modules {Demo} Summary & Questions
Building a First Network {LAB} Scalar Statistics {LAB} Modeling Framework Other Editors {Mini-labs} General Simulation Methodology
5
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Format
Purpose of the class: To give students a hands-on learning experience and introduce many of the features of Modeler. About half lecture, half lab More lecture at the beginning this will lay a strong foundation Lecture is interactive do not hesitate to ask questions Labs not completed in class may be completed on your own Note: In the interest of time, some labs contain unrealistically short simulation runs. Since the data may not have a chance to converge, your results may not match the results in the manual exactly.
6
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Format
During labs, raise your hand and an assistant will help you. Concepts will be taught during lecture, and you will apply them to labs. We encourage you to ask questions. Fill out the "sign-in" sheet and the "course evaluation" before you leave. Please provide constructive feedback for improvements to the OPNET software, user interface, documentation, and training session.
7
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
8
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
OPNET Technologies
Founded in 1986 Publicly Traded (NASDAQ: OPNT) 2500+ Customer Organizations Intelligent Network Management Solutions
Enterprises For Best E-Business Solution Service Providers At Supercomm Network Equipment Manufacturers Government Bethesda, MD (Headquarters) Santa Clara, CA Boston, MA Dallas, TX Cary, NC Paris, France Reading, UK Sydney, Australia Ghent, Belgium
Offices in
Introduction to Modeler
Enterprises
IBM Global Services Ingram Micro Intermedia Communications Kemper Insurance Mary Kay Microsoft National Semiconductor NCR Newport News Shipbuilding Northern Trust Company Oracle Pacificare Peoplesoft Petro-Canada Predictive Systems Prudential QuikTrip RadioShack RR Donnelley Safeway Schneider Electric Sears Seattle Times Seagate Technology Schlumberger Southern California Edison Spiegel State Street Sun Life Assurance Suntrust Bank Target Thomson Financial Trans Canada Pipelines TXU Unisys Visa International Vision Service Plan Wal-Mart Waste Management
Abbott Laboratories ABN AMRO Accenture Aerospatiale ATOFINA Petrochemicals American Water Works Aramco Ashland Inc. Avery Dennison Bank of Oklahoma Baptist Healthcare BB&T BEA Systems Becton Dickinson Blue Cross Blue Shield Booz Allen & Hamilton CACI Federal Cal Fed Capital One Charles Schwab & Co. Citicorp Compaq Global Services CP Ships CSC CSX Technology Cummins Engine Co. CVS Pharmacy DaimlerChrysler Dell Computers DHL DIRECTV Entergy Enterprise Rent-a-Car Ernst & Young FleetBoston Financial First American First Citizen First Union National Bank General Dynamics
Service Providers
Allegiance Telecom AT&T AT&T Wireless Belgacom BellSouth British Telecom Cable & Wireless Chunghwa Telecom Compuserve Deutsche Telekom Dolphin Telecom France Telecom Hungarian Telecom Hutchison 3G Italtel S.p.A. Indonesia Telecom Infonet Inmarsat Intelsat KDDI Korea Telecom LG TeleCom Network Access Slns Nextel NTT DoCoMo NTT Group Omnitel Orange PCS Orbital Sciences Polish Telecom PT Comunicacoes Rogers Communications Qwest SBC SK Telecom Sprint SWIFT Swisscom T-Mobile Telekom Austria Telecom Italia Telecom Italia Mobile Teledesic Telefonica Telenor TELUS Telstra TenFold UUNET Verizon Vodafone Williams Wind Telecomm. S.p.a. WorldCom
10
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Federal Customers
DoD
Army Research Laboratories (ARL) DARPA Defense Information Systems Agency (DISA) Joint Staff (J6) National Communication System National Ground Intelligence Center National Guard National Image Mapping Agency (NIMA) National Security Agency NATO Naval Information Warfare Center Naval Postgraduate School Naval Research Laboratories (NRL) Naval Surface Warfare Center (NSWC) Naval Underwater Warfare Center (NUSC) NRaD/NCCOSC SPAWAR East and West Tri-Service Information Management Program Office (TIMPO) US Army CECOM US Army Combined Arms Center US Army HQDA/DISC4 US Army Missile Command US Army Signal Center US Army Signal Command US Marine Corps US Military Academy US Air Force AFSOC US Air Force SSG US Air Force ESC US Air Force AFCA US Air Force HQ 38th EIW US Air Force Information Warfare Center US Air Force PAC US Air Force RADC
Civilian
Argonne National NASA- Ames Laboratory Research Center Bureau of Alcohol Tobacco NASA- Goddard Space & Firearms Flight Center Coast Guard NASA- Glenn Research CIA Center Department of Agriculture NASA- Marshall Space Department of Commerce Flight Center Department of State Oak Ridge National Labs FAA Sandia National Labs FBI Social Security Admin Federal Railroad Tennessee Valley Administration Authority Federal Reserve Bank US Agency for General Services Admin International Development IRS US Courts Idaho National US Census Bureau Engineering & US Senate Environmental Lab Veterans Administration Jet Propulsion Laboratory Lawrence Livermore National Laboratory
Contractors/Partners
Aerospace Corporation ARINC BAE Systems Bearing Point Booz Allen Hamilton BBN Boeing Computer Sciences Corp. Concurrent Technologies Corp. CACI Federal Systems CISCO Federal Cubic Defense Systems Draper Labs DynCorp Eagan, McAllister Associates Eagle Alliance Frontier Technology GEC Marconi General Dynamics GTE Georga Tech Research Institute Harris Honeywell Hughes IBM Global Services IITRI ITT Jaycor JHU APL Lockheed Martin L-3 Communications MIT Lincoln Labs MITRE Northrop Grumman Orincon Sygenex Optimization Technology, Inc. PEC Solutions Raytheon Rockwell Collins SAIC SeiCorp Sparta Scientific Research Corporate SRI International Syracuse Research Corporation Systems Planning and Analysis, Inc Titan Lincom/BTG Trident Systems TRW Veridian XPRT Solutions
11
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
12
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
13
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
14
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
15
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
CCNP: Cisco Certified Network Professional CISSP: Certified Information Systems Security Professional CCSE: Checkpoint Certified Systems Engineer CCNA: Cisco Certified Network Associate
OPNET subsidiary, OPNET Analysis Inc., holds a TS facility clearance Outstanding past performance Contacts: Ray Rafaels, VP Consulting Services (rrafaels@opnet.com) & Frank Longo, VP Business Development (flongo@opnet.com) http://www.opnet.com/services/consulting
16
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
OPNETWORK
OPNETWORK is the largest conference in the world on network and application modeling and simulation--offering a dynamic range of symposiums, case studies, and modeling sessions taught by OPNET experts. OPNETWORK (including course materials, models, nightly entertainment, all meals, and online proceedings) is free to all OPNET clients and client organizations. Those interested in attending who are not from a client organization will be considered on a case-by-case basis.
This years conference held at the Reagan Building in Washington, D.C. For Current Information: www.opnet.com
17
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Modeler Demo
Network Models
Represent data networks Run simulations on network
Node Models
Model devices in the network
Process Models
Represent communications protocols, CPUs, queuing schemes, etc.
18
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
19
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Overview
Project Editor:
Workflow More Details of the Project Workspace Map Backgrounds Zooming Threshold Value Annotation Palette Project Workspace {Lab} Models Deriving and Creating New Devices {Lab} Object Attributes Client-Server Configuration Example Statistics Product Documentation
20
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
21
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Duplicate scenario
Make changes Re-run simulation Compare results
Iterate
22
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Project Editor
Several tools are included in Modeler to intuitively map from network specifications to a modeled network.
Example network model:
Use the Startup Wizard to specify the initial environment of a scenario. Select objects from an Object Palette. Use Node and Link objects to represent actual topology. Use Rapid Configuration to quickly deploy common network topologies. Edit the Attributes of nodes and links to customize their behavior.
23
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Map Backgrounds
Modeler includes several maps that can be loaded as backgrounds for network models. Map backgrounds provide a physical context for model specification. Models are more easily interpreted when set in a proper geographical context. Distance between nodes can be a factor in affecting simulation results. Maps can be imported as well as shown below.
The format for an imported image is: .tiff, geotiff, MapInfo
24
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
25
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
27
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
28
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Annotation Palette
Add rectangles, circles, lines and text to models to enhance their appearance. This method is an effective way to graphically illustrate and document the changes made to a model. Does not affect simulations. Open by selecting Topology / Open Annotation Palette. Annotations have attributes that configure their appearance. Annotations can be hidden.
29
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Subnets
A subnetwork abstracts network components specified within it into a single object. Subnetworks:
Represent identical constructs in an actual Have no behavioral aspects, but simplify networks. May be stationary or mobile.
3 Subnet Types network. representation of large
30
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
31
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
32
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Object Hierarchy
Subnets represent various network components in a single object. This object could contain various LAN, node, and link models. LANs represent a local area network abstracted into a single node. Nodes represent servers, workstations, switches, gateways or any other physical devices associated with communication networks. Links represent the physical links between nodes.
33
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
34
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Model Library
The Model Library is an extensive library of standards-based and vendor models. Our Modeling Dept. is responsible for design, development, and ongoing evolution of the model library. Models are created using published protocol standards and other widely used vendor implementations.
IEEE Specifications (e.g., 802.1q, 802.3, 802.11, etc.) ANSI Standards (e.g., X3.139, T1.513, etc.) ATM Forum Specifications (e.g, UNI 3.1, TM 4.0, etc.) RFC Documents (e.g., RFC-793, RFC-1058, RFC-1771, etc.) Vendor Technologies (e.g., VLAN tagging, EIGRP, etc.)
35
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Traffic generators (workstations, servers, stations, etc.) Network devices (hubs, bridges, switches, routers, etc.) Links (SONET, PPP, FDDI, 10BaseT, ISDN, xDSL, etc.) Vendor device models (Cisco Systems, 3Com, Nortel, Lucent, HP, etc.)
These models are ready-to-use to create networks and predict performance behavior.
36
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Introduction to Modeler
Network Objects
Network models consist of nodes, links and subnets. Nodes represent network devices -- servers, workstations, routers, etc. Links represent point-to-point and bus links. Icons assist you in quickly locating the correct nodes and links. Vendor models are distinguished by a specific color and logo for each company.
Generic Devices
Vendor Devices
38
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
39
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Example: ethernet128_hub_adv
This model represents a hub with 128 ethernet interfaces. Since it is an advanced model, all the models attributes are visible and editable.
40
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Vendor Models
In addition to our standard models, OPNET contains vendor specific models. Vendors:
3Com Ascend Avici Bay Networks Cabletron Cisco Systems eXtreme Fore Systems Foundry Hewlett Packard Juniper Networks Lucent NEC Newbridge Nortel
41
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Example:
CS_4000_3s_e6_f_fr2_sl2
This model represents a Cisco Systems 4000 Router with 3 slots, 6 ethernet ports, 1 FDDI port, 2 frame relay ports, and 2 SL-IP ports. View description of the node by:
Right-clicking on the node in the object palette. Right-clicking on the node in the workspace and selecting View Node Description.
42
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Example:
10BaseT_adv
43
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
44
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Customizing Palettes
Keyword Model List Startup Wizard
45
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
LAB REFERENCE For a later lab we will use the model list method.
6
46
copyright 2004 OPNET Technologies, Inc.
4 3
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
47
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
48
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
3 2
6 4 5
49
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
50
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Device Creator
Device Creator
Provides the ability to automatically create a particular device with a specific configuration. Typical devices include routers, switches, hubs, bridges, vendor specific devices, and LAN models.
51
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
52
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Object Attributes
All Modeler objects have attributes Attributes define the object and control its behavior
Second attribute is model this is the filename of the object Attribute values may vary between objects of the same model Example: Two routers of the same model may have different routing parameters, two demands may represent different amounts of traffic Attributes may have sub-attributes
53
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
54
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Selecting Objects
Select objects to modify, cut, delete, move, or copy them Several methods to select multiple objects:
Shift-click or Control-click Right-click and choose Select Similar Nodes/Links/Demands Selects all objects with the same model name Edit / Select Objects Advanced object selection used to select objects with certain attribute values Excellent way to explore configuration of an existing network model Edit / Find Nodes Select objects based on object name Draw a selection box around a group of objects
55
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
56
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
57
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
58
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
59
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Purpose:
Play with features of the Project Editor Use the Device Creator and model derivation to create new node models Modify attributes values in order to model non-default behavior Search the product documentation
60
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
61
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Running Simulations
62
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
63
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Types of statistics:
Global: relate to network as a whole Node: collected on individual nodes Link: collected on individual links
Common statistics:
Global: application response times Node: delay, delay variation Link: utilization, throughput, queuing delay
64
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
65
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Descriptions of Statistics
To obtain complete definitions of statistics, right-click on the statistic in the Choose Results window and select Statistic Description.
66
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
67
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Understanding Statistics
To run simulations with useful results, it is essential to define the goals of the simulation and to understand the statistics that are needed to measure those goals. Browse available statistics and view their definitions. Understand the default collection mode to help interpret results.
68
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
69
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
70
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
71
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
72
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
73
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Simulation Mechanics
Run simulation
DES / Configure/Run Discrete Event Simulation Set simulation options Click Run
While simulation is running, view stats on events processed per second and amount of RAM used by simulation After simulation completes, check simulation log for errors
DES / Open DES Log
74
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
DES Log
Contains errors generated during simulation Contains information about special events during simulation Your code can write to DES log good way to output debugging information Always check DES log for errors before trusting results
75
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
76
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Left clicking on a specific message gives details on the symptoms, causes, and suggestions.
77
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Global attributes
Protocol specific Control behavior of every applicable object Sim efficiency modes: disable these for failure / recovery studies Tracer packet options: determine how quickly flows reroute in failure case
78
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
79
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Results Options
Stacked Statistics
Overlaid Statistics
80
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Results Options
Filters:
As is: every data point collected during sim Average: average of several data points together
81
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Click on a node and then click here to find the node within the topology
82
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Lab 2: Goals
Build your first network
Review for anyone who has gone through the tutorials or IT Guru Quickstart Teaches fundamentals of modeling workflow
83
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
84
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Summary
One project can contain many scenarios The Startup Wizard can be used to quickly and easily create new scenarios. The Project workflow consists of:
Creating a project Creating baseline scenario Choosing results to be collected Running simulation Viewing results Duplicating scenario Running simulation Comparing results
85
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
86
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Agenda
Conceptual Goals
Objects available in the modeling domains Data transfer between objects in a simulation Network, node, and process models Object attributes Object naming paradigm Role of packets in a simulation
87
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Node objects are represented by icons. Different icons may represent the same underlying object. Icons shown are the default icons. A fixed node remains stationary during a simulation. A mobile node changes position during a simulation, following an assigned trajectory or using vector based mobility (ground speed, bearing, and ascent rate). Trajectories can easily be created graphically in Modeler, or by ASCII text files. A satellite node changes position during a simulation, following an assigned orbit. Modeler has supporting tools to create and view orbits.
Mobile
Satellite
88
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Subnetwork
89
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
A bus link transfers data among many nodes and is a shared media.
A wireless link, established during a simulation, can be created between any radio transmitterreceiver channel pair. Satellite and mobile nodes must use wireless links. Fixed nodes may use wireless links. A wireless link is not drawn but is established if nodes contain radio transceivers.
Wireless link
90
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Queue
91
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
92
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Point-to-point transceivers
Bus transceivers
Antenna
Transmitter
Receiver
Transmitter
Receiver
Transmitter
Receiver
93
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Module Connections
Packet streams carry data packets from a source to a destination module. Statistic wires carry a single data value from a source to a destination module. In this case, hub_rx0 might report a packet reception to mac.
94
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
95
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Initial state
Forced state
Unforced state
red
green
red
96
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Condition statement
Transition executive
97
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Executive Blocks
Each state has two executive blocks
Enter executives are invoked on entering a state. Exit executives are invoked before exiting a state.
98
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
99
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Kernel Procedures
Sample of commonly used KPs
Packet Package: op_pk_create () op_pk_create_fmt () op_pk_copy () op_pk_get () op_pk_total_size_get () op_pk_nfd_set () op_pk_nfd_get () op_pk_send () op_pk_send_delayed () op_pk_destroy () Subq Package: op_subq_pk_insert () op_subq_pk_remove () Interrupt Package: op_intrpt_schedule_self () op_intrpt_type () op_intrpt_strm () op_intrpt_code () Stat Package: op_stat_reg () op_stat_write () op_stat_local_read () op_stat_scalar_write () Distribution Package: op_dist_load () op_dist_outcome () Simulation and Event Packages: op_ev_cancel () op_sim_time ()
ID, Topo and Internal Model Access Packages: op_id_self () op_topo_parent () op_topo_child () op_ima_obj_attr_get ()
Naming convention for Kernel Procedures op_<family name describing object >_<action> When using process model editor, press ctrl-H for list of commonly used KPs.
100
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
What is Proto-C ?
Proto-C consists of
State transition diagrams The complete C programming language The library of OPNET Kernel Procedures (KPs) State variables (private to each process) Temporary variables
101
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Object Attributes
Attributes are parameters of an object that can configure its behavior. Attributes are dynamically changeable during simulation. Processes have access to all object attributes. Different attribute values allow objects of the same type to behave differently.
102
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Object Attributes
Though you use the same process model, by changing the data rate for the channel attribute you alter the behavior of the node.
103
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
104
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
105
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
corporate
router.buf.priority:
high
mktg_lan
buf.priority:
promoted
router
priority:
promoted
buf
106
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Model Hierarchy
The internal structure and behavior of each node is dictated by the node model, specified in the model attribute. The node model is created in the Node Editor.
107
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Model Hierarchy
The internal structure and behavior of each processor and queue is dictated by the process model specified in the process model attribute. The process model is created in the Process Editor.
108
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Object Naming
Each object has a unique name that defines its place in the hierarchy. Format of name is:
network_type.subneta.subnetb...subnetz.node_name. object_name
109
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Object Naming
opnet
110
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
111
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Packets
Packets are
The information-carrying entity that circulates among system components. General data structures, organized into fields of information you define. Dynamic simulation entities that are created and destroyed as the simulation progresses.
A single system may rely on multiple types of packets with different formats.
112
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
113
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
114
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Summary
Network Objects: Nodes (fixed, mobile, satellite), Subnets, and Links (point-to-point, bus, wireless). Node Objects: Modules (Processors, Queues, Transmitters, Receivers, Antennas) and Connections (Packet Streams and Statistic Wires). Process Model Objects: States (initial, forced, unforced) and Transitions. Kernel Procedures: Pre-written functions that abstract communication modeling operations. Object Attributes: Dynamic parameters that can configure the behavior of an object. Packets : Basic units of information exchange in OPNET simulation.
115
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
116
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Agenda
Conceptual Goals
Modelers architecture and philosophy. Brief look at all other Editors Hierarchy of modeling
117
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Modeling Approach
Modeler provides a structured modeling approach
Hierarchical models parallel the layered structure of communications networks and distributed systems: State transition diagrams (STDs) model node element behavior.
118
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Modeler Editors
A variety of editors allow you to view and configure different layers of the network structure.
119
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
120
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
121
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Agenda
Topics
Understanding what you are modeling Granularity Defining Data Results
Conceptual Goals
Use basic methodology for developing a network simulation study. Plan simulation studies using a consistent method.
122
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Start
No No Specifying the system model Choosing input and running simulations System results accurate? Yes Results sufficiently detailed?
No
End
123
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
124
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
125
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
These objectives determine the granularity (level of detail) required in the model.
126
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
What is Granularity?
Granularity is the level of detail. Choose a granularity sufficient to answer all questions. You have:
Coarse granularity (minimum detail) allows faster execution and simpler development. Fine granularity (more detail) allows greater precision, but simulations run slower and may require more complex development.
127
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
128
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Granularity - Example 1
Model and calculate application end-to-end delay (ETE delay) for 10 workstations connected via an Ethernet hub. Compare the delay measurements with those obtained using an FDDI hub instead.
129
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
130
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Granularity - Example 2
Model the following scenario: 2,000 workstations in Chicago and another 4,000 in New York communicate via an OC12 link. How much will an OC48 link decrease response time?
131
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Conclusion: coarse granularity probably sufficient. Observation: modeling full detail might be prohibitively slow to develop and run.
132
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
133
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
134
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Introduction to Modeler
136
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
137
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
138
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
One technique: predict output first, then compare predicted to actual output.
139
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
140
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
141
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
142
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
143
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Summary
Understanding the system Understanding your goals for the simulation Choosing aspects to be modeled
Start
No No Specifying the system model Choosing input and running simulations System results accurate? Yes Results sufficiently detailed?
No
End
144
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
145
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Agenda
Conceptual Goals
Events Interrupts Event-driven simulation Event list and the simulation time clock Simulation Kernel Processes and interrupts
146
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Event-Driven Simulation
An event is a request for a particular activity to occur at a certain time. OPNET simulations are event-driven. Time, in the simulation, advances when an event occurs. A different method might be to sample at regular intervals. Disadvantages are as follows:
Accuracy of results is limited by the sampling resolution. Simulation is inefficient if nothing happens for long periods.
147
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Event Type
Initialize Initialize Timer expires Packet arrives
Module
src.gen src.rte src.gen src.rte
An event has data associated with it. When an event completes it is removed from the list.
148
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Interrupts
An event becomes an interrupt when it reaches the head of the event list and is delivered by the Simulation Kernel to the designated module. Data associated with the event can be obtained by the module when the interrupt occurs. Certain modules, processes, and queues can be selected to place initial interrupts on the event list.
149
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
150
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
New event reaches head of event list, which causes Simulation Kernel to deliver an interrupt to the appropriate module
Simulation Kernel deletes event from event list, allowing new event to reach head of list
151
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
0.01234 56789 11111 11 0.01234 56789 11111 22 0.01234 56789 11111 33 0.01234 56789 11111 44 0.01234 56789 11111 55 0.01234 56789 11111 66 0.01234 56789 11111 77
Suppose that this interrupt triggers an event to occur at 0.01234 56789 11111 75. The Simulation Kernel minimizes the time required to place this event at the correct place on the list.
152
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Simultaneous Events
What Happens When Two Events Are Scheduled for the Same Simulation Time? The events are actually simulated sequentially, though they appear to occur synchronously according to the time clock. The Simulation Kernel uses one of two methods to determine execution order:
Natural order method: The event that reaches the list first is executed first. Priority factor method: Modules and events are assigned priority factors. Events with a higher priority or originating from a higher priority module are executed before events with a lower priority or from a lower priority module.
153
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
An event list typically has a few events each event spawns another event or two that is placed on the list as the spawning event is deleted. The event list is always growing and shrinking. An event is pending until executed. A pending event can be cancelled.
154
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Delivery of Interrupts
When an interrupt is delivered to a module, control passes from the Simulation Kernel to the module. If the module is a queue or processor, the interrupt is delivered to the process running within the module.
155
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Forced States
Forced (green) and unforced (red) states differ significantly in execution timing. In a forced state, the process:
Invokes the enter executives Invokes the exit executives Evaluates all condition statements If exactly one condition statement evaluates to true, the transition is traversed to the next state.
Enter execs invoked No blocking or waiting Exit execs invoked Transition to next state
156
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Unforced States
In an unforced state, the process
Invokes the enter executives Places a marker at the middle of the state Releases control to the Simulation Kernel and becomes idle Resumes at the marker and processes the exit execs when next invoked
Start of invocation
End of invocation
157
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
158
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
No
Red state?
Yes
Receive interrupt
159
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
3. Transition occurs.
6. Transition occurs.
160
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
In control
SK pr1
Idle
All processes SK; other processes
pr2
SK ; other processes
161
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Node model
Node model
Network model
Network model
162
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
163
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
164
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Event Type
BEGSIM BEGSIM
Module
src.gen src.queue
Node model
165
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Event Type
BEGSIM BEGSIM
Module
src.gen src.queue
167
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Process model
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
169
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Process model
170
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Event Type
BEGSIM BEGSIM SELF
Module
src.gen src.queue src.gen
Marker
171
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Event Type
BEGSIM SELF
Module
src.queue src.gen
0.0 4.3
172
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Time
4.3
Event Type
SELF
Module
src.gen
173
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
174
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Time
4.3 4.3
Event Type
SELF STRM
Module
src.gen src.queue
175
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
176
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Simulation Termination
Simulations terminate in one of four ways
The event list is emptied. Simulation attribute duration expires. A process calls for termination, using the KP op_sim_end(). A fatal error occurs.
177
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
178
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Summary
Forced and unforced states differ in when they execute their instructions. Any processor or queue can have the attribute begsim intrpt enabled, scheduling an event for time 0.0. Control passes dynamically between the Simulation Kernel and individual processes.
179
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
180
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Agenda
Conceptual Goals
Creating and configuring nodes Configuring transceivers Configuring traffic generators Testing predicted behavior Deriving new models
Tools
Node Editor Probe Editor
181
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Sequence of Events
Follow these steps 1. Understand the problem:
Understand the network or system to be modeled. Understand the questions to be answered by the model.
2. Create models:
Create the node models first. Create the network model.
3. Set probes to collect statistics. 4. Configure simulation. 5. Determine expected output. 6. Run the simulation. 7. Analyze output. 8. Compare actual results to expected output. Explain any differences.
182
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
General Hints
Create descriptive names for nodes, modules, network models and node models. Create node models first, and only then the network model. To determine a particular buttons function, place the mouse on it and read the explanatory text in the display areas. Check link consistency before exiting the Network Editor. To avoid confusion, you may want to exit each editor as you finish using it.
183
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Node Editor
The Node Editor provides the resources necessary to model the internal functions of nodes. You have access to different modules which are used to model internal aspects of node behavior. Modules represent the internal capabilities of a node such as:
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Node Editor
Toolbar
Node Workspace
Create transceivers (tx/rx) point-to-point / bus / radio / antenna
Create processor
Create queue
Introduction to Modeler
Queue module. A module that provides a superset of the functionality of processor modules. Queue modules can execute an arbitrary process model that describes the behavior of a particular process or protocol, and can be connected via packet streams to other modules.
186
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Introduction to Modeler
Antenna: A module that is used to specify the antenna properties for radio transmitter or receiver modules.
Antenna
188
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Introduction to Modeler
Node Statistics allows you to select which statistics can be chosen for collection from within the Project Editor.
190
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
191
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Probe Editor
In previous chapters, statistics were selected and results collected in the project editor. The probe editor further expands your ability to configure where information is collected and what statistics are measured. You can save collections of probes to a file for use on different scenarios.
192
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Probe Editor
Toolbar
1 2 3 4 5 6 7 8 9 10
Probe Workspace
1. Global Statistic Probe 2. Node Statistic Probe 3. Link Statistic Probe 4. Path Statistic Probe 5. Demand Statistic Probe 6. Coupled Statistic Probe 7. Attribute Probe 8. Automatic Animation Probe 9. Statistic Animation Probe 10. Custom Animation Probe
193
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
LAB REFERENCE For a later lab we will use the model list method.
194
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
195
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
196
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
197
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
198
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
199
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Lab 4: Results
200
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Summary
The node editor gives you complete control over the design of a nodes architecture to reflect the behavior of a device based on specifications. The probe editor expands your capability to customize the selection of statistics.
201
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
202
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Agenda
Conceptual goals
Process models Custom statistics Kernel Procedures
Tools
Process Editor
203
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Process Models
A process in the context of computer systems and communications networks can be viewed as a series of logical operations performed on data, and the conditions that cause these operations. Processes may be implemented in terms of both hardware or software components. OPNET process models describe the logic of real-world processes, such as:
Communications protocols and algorithms Shared resource managers Queuing disciplines Specialized traffic generators Statistic collection mechanisms Operating systems
The Process Editor provides the necessary features for specifying process models, which consist of both graphical and textual components.
204
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Toolbar
1. Create state 2. Create transition 3. Set initial state 4. Edit state variable 5. Edit temporary variable 6. Edit header block 7. Edit function block 8. Edit diagnostic block 9. Edit termination block 10. Compile process model
205
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Process Editor Toolbar Create State: Creates a new state within the process model.
State: One of the components of a finite state machine. The behavior of a state is defined by its state executives, which are executed upon entry into and exit from the state.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Process Editor Toolbar State Variables Block: Defines variables that retain
their value from one process invocation to the next.
Introduction to Modeler
Process Editor Toolbar Diagnostic Block: Defines C/C++ statements that send
diagnostic information to the standard output device.
208
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
209
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
210
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Summary
Process modeling enable you to generate customized models and statistics. Built-in Kernel Procedures facilitate the coding of process models. In this Chapter, we learned how to create process model from scratch and incorporate it into existing node model.
211
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
212
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Agenda
Conceptual goals
Creation of an attribute of a process model Collect scalar statistics
Tool goals
View scalar analysis results
213
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
4 3
214
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Scalar Statistics
A scalar statistic is a single value representing a statistic computed over an interval, typically the entire simulation. A scalar statistic
Allows for parametric studies. Must be plotted versus another scalar. Shows the effect that making a change has on certain output parameters. Is usually a summary of some aspect of a networks behavior.
215
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
A vector statistic is a single output plotted versus simulation time. (Example: throughput as it evolves over time).
216
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Scalar Statistics
A scalar statistic is a single value representing a statistic computed over an interval, typically the entire simulation (example: average end-to-end delay for all received packets in a simulation). Scalar statistics:
Must be plotted versus another scalar statistic Allows for parametric studies Requires many simulation runs because each run produces only one data point Each simulation will add a new data point => The result file (.os extension) must be deleted when rerunning a set of simulations.
217
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
A statistic probe created in the Probe Editor (left) An attribute probe The KP op_stat_scalar_write (scstat_name, value)
3
218
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
219
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
220
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Introduction to Modeler
222
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
223
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Lab 6: Results
224
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
225
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Agenda
Conceptual goals
Importing network topologies Choosing aggregation levels Using LAN models Importing traffic Using routed background traffic Managing projects and scenarios Navigating Large Topologies Controlling Simulation Runtime Effectively Using Background Traffic
Software goals
Import topology Question and answer browser Import traffic Network browser Traffic browser Efficiency Modes Static Background Traffic Event Speed Parameter Specifying Traffic Growth Scheduling Automated Simulations Viewing and Editing Scheduled Simulations Log
226
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
227
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Common Pitfalls
OPNET is powerful software that tempts users with grand designs. Common Pitfall: I will model everything Developing models without clear direction and a solid understanding of the questions that need answering leads to inefficiency, and results that arent useful.
228
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
229
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
LAN Models
Single nodes may be used to model entire LANs.
230
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
231
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
232
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Modeling Techniques
Design Accurate, Efficient Models Two Techniques
Approximation Reduction
233
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Approximation
Tradeoff: Precision vs. Performance
Loss in precision means higher variance Overall results are still accurate
Approximation Approach
Apply a combination of analytically and explicitly modeled traffic Allows you to limit the number of variables, while retaining the proper traffic behavior for the model
234
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Traffic Types
Three different types of traffic
Loads Also called Device/Link Loads Represent percentage of capacity being used Can be imported or manually created Flows Visualized as demand objects Can be imported or manually created Packets Provide detailed performance statistics Delay, response time, jitter Represent different types of application traffic Can be imported from optional ACE module or manually created
Introduction to Modeler
236
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Link Loads
Represent utilization of individual links Values are represented in percentage utilization for each time period
Utilization A->B Utilization B->A
Introduction to Modeler
Flows
Represent flow of network traffic between sources and destinations in network Flows are represented in bits/sec and packets/sec Flow data can be imported from management platforms
Cisco NetFlow (AS Aggregation or No Aggregation) Cflowd NetScout NetScout Ngenius NAI Distributed Sniffer / Sniffer Pro Agilent NetMetrix Spreadsheet / text files
You can add new flows manually by choosing: Protocols / IP / Demands / Configure Traffic Demands Among Selected Nodes
238
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Flows
Flows are a type of traffic demand. Demands appear as dotted blue lines from source to destination. Right-click a traffic demand to edit its attributes or hide the demand Use View / Demand Objects to hide/show all demands Use Traffic / Open Flows Browser to quickly examine many flows
239
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Packets
Only used for discrete event simulation (DES) Represent individual packets in network
Application traffic LSAs
Application Configuration node used to globally define application traffic LSAs automatically sent by routers during simulation Capture the transient behavior of the network
Convergence Latency Queue depth Protocol effects
240
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Traffic Tradeoffs
Traffic Type Load Advantage Usually easiest data to obtain Visualize current load on network Simulations will route flow data over network according to routing protocol settings Good for failure studies Provides very detailed statistics: convergence time, packet loss, protocol interactions, delay, jitter Disadvantage Cant be rerouted in failure case Provides no detail about traffic ingress/egress points Sometimes difficult to obtain flow data for entire network
Flow
Packet
241
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
242
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Flows are best choice for failure studies Loads are often easiest to obtain and best for viewing utilization of current network Packets are only used in discrete event simulation. Packets give the most detailed results and are the best choice for QoS studies.
243
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Object Reduction
Each and every object in a model uses memory. Reducing the number of objects in a simulation allows for more efficient simulations, possibly allowing the workstation to overcome memory limitations (reduce swapping). Modeler provides LANs, clouds and devices with varying interfaces to allow you to keep the number of objects in the network model to a minimum without sacrificing precision.
244
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Object Reduction
LANs allow you to represent any number of workstations and a server as a single object. IP Clouds abstract numerous IP devices into a single cloud object. Each interface in a device requires memory. Creating devices that have the minimum amount of interfaces required for a model reduces memory needed to run simulation.
Example-- If all the hubs in a model will only have 8 connections, it is more efficient to use an ethernet8_hub than an ethernet64_hub. Even if this doesnt represent your actual hardware, it will not affect the precision of the simulation.
245
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Alternative Solutions
There are other solutions that do not involve model design. These alternative solutions can be characterized as brute force methods. The advantage to alternative solutions is that it gives you more latitude in your model designs. Increasing physical memory is always an effective way to increase workstation performance. Increasing the swap space is another effective method to get a better performance from a computer.
246
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
247
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
248
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
249
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Aliases
An alias is a name used to reference a particular node in OPNET. An alias may be an IP address, MAC address or a user friendly name. An object may have multiple aliases. These aliases are used as endpoints for imported traffic. LAN models retain the aliases for all nodes that are contained in the LAN. This makes it possible to address traffic to the appropriate LAN model.
250
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
251
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
252
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Network Browser
The Network Browser can be used to locate objects in your network. Choose View / Show Network Browser Type a search string into the Find box to show objects with that string in their names.
253
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Network Browser
To view an objects attributes, right-click the object in the workspace or the list and select Edit Attributes.
254
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Introduction to Modeler
Summary
Networks can be imported in a variety of manners. Modelers power as modeling software becomes evident with the analysis of large networks. As the size of the model increases so does the importance of efficient modeling. Avoiding common pitfalls and understanding the efficiency techniques inherent in Modeler leads to useful results and efficient models. By skillfully using the combination of the three types of traffic, you can achieve a comfortable balance of performance and precision.
256
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
257
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Agenda
Conceptual Goals
Introduction to wireless modeling Introduction to Transceiver Pipeline Stages Mobile/Satellite Nodes Custom Packets Custom Antennas Link Models Custom PDFs
Tool Goals
Define Trajectory Packet Format Editor Link Model Editor Antenna Pattern Editor PDF Editor
258
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Wireless Modeling
Modeler / Wireless allows models to utilize mobile nodes and mobile subnets using dynamic RF links. Node and subnet positions are updated (lazy evaluation) based on user specifications such as time step, altitude and a defined path that is anchored on absolute or relative coordinates. Wireless transceivers must be used that employ a 14 stage link budget model called the Transceiver Pipeline
259
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Wireless Modeling
Wireless is a broadcast technology and depends on dynamically changing parameters. The simulation must evaluate the possible connectivity between a transmitter channel and every receiver channel for each transmission. The network level characteristics factored into these calculations are the locations of the source and destination nodes, the distance between the nodes, and the direction the wireless signal travels from the source node to the destination node. If the nodes are mobile or satellite nodes, these position-related parameters may change during simulation.
260
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Wireless Links
A wireless link is not statically represented by an object, as are pointto-point and bus links. A wireless link can exist between any radio transmitterreceiver channel pair and is dynamically established during simulation. The possibility of a wireless link between a transmitter channel and a receiver channel depends on many physical characteristics of the components involved, as well as time-varying parameters, which are modeled in the Transceiver Pipeline Stages.
261
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Wireless Links
In OPNET simulations, parameters such as frequency band, modulation type, transmitter power, distance, and antenna directionality are common factors that determine whether a wireless link exists at a particular time or can ever exist
262
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Transceiver Pipeline
Models the transmission of packets across a communications channel (link) Implements the physical layer characteristics Divided into multiple stages, each modeling a particular aspect of the channel Determines whether or not a packet can be received at the links destination
S1
S2
S3
S4
Transmitter
Each stage models an aspect of the links behavior
Receiver
263
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Radio Transmitter
Receiver Group Transmission Delay Link Closure (LOS) Channel Match Tx Antenna Gain Propagation Delay
Radio Receiver
Rx Antenna Gain Received Power Background Noise Interference Noise Signal-to-Noise Ratio Bit Error Rate Error Allocation Error Correction 8 Stages (6-13) Associated with Radio Receiver
264
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
265
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
266
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Mobile Nodes
Mobile nodes model terrestrial network elements whose positions vary with time, such as automobiles, aircraft, and ships. Mobile nodes cannot be connected to point-to-point and bus links, because they move relative to the earth. Mobile nodes may change position during a simulation, either on an assigned trajectory or by direct changes to the nodes position attributes.
267
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
268
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Defining a Trajectory
1. Choose Define Trajectory from Topology pull down menu 2. Set the Trajectory attributes to the desired values. 5. Left-click in the work space to define intermediate positions for the mobile node.
Mobile nodes support an attribute called trajectory which specifies the name of an ASCII text file defining the path of the mobile node during the simulation.
269
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
8. Click on complete to finish the trajectory creation process. 9. Type in a trajectory name. Click OK to save the trajectory.
270
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Satellite Nodes
Satellite nodes model network elements in orbit around the earth, such as satellites and spacecraft. Like mobile nodes, satellite nodes cannot be connected by point-topoint and bus links because they change positions during a simulation. Satellite nodes change position based on an assigned orbit or by direct changes to the nodes position attributes.
271
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Orbits
Orbits can be imported from STK and viewed using op_vuorb (shown below)
272
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Wireless Features
TMM: (Terrain Modeling Module)
The Terrain Modeling Module allows you to take into account terrain when modeling wireless networks. With TMM, you can import elevation maps that contain terrain data. Supported map formats are DTED and DEM. TMM also allows you to select and compare signal loss from various propagation models.
Simulation Efficiencies
Dynamic Receiver Group Parallel Processing
273
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
274
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Lab 7: Overview
Parameters:
Telephones initiate pages addressed to a specific mobile pager. The pages are relayed through a central base station. A radio tower broadcasts the pages. If the appropriate mobile pager receives the page, an ack is transmitted back to the radio tower. The radio tower relays the ack back to the base station and a successful page statistic is recorded.
275
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Summary
Wireless models depend on dynamically changing parameters, which the simulation evaluates to determine the possible connectivity between all radio transmitters and receivers. Modeler simulate the movement of mobile nodes along trajectories and satellite nodes in orbit. The antenna, PDF, link and packet editors further expands your capability to define and customize parameters that affect the behavior of the model.
276
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
277
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Agenda
Conceptual Goals
Develop a sensible approach to debugging Examine ways to identify problems Introduce OPNET Debugger (ODB) Discuss the debugging process
278
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Debugging Techniques
Will not cover Using a C/C++ code debugger Segmentation violation Bus error Inconsistent problems These topics are covered in the Debugging Techniques (Advanced) chapter (part of the Modeler Advanced Training).
279
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
The Challenge
Debugging is like finding a needle in a haystack Systematic approach Looking for clues Narrow down the problem
Time (event number) Space (code segment)
280
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Types of Problems
Topology and attributes are not set up correctly Simulation fails to complete successfully Simulation completes successfully, but does not accurately represent the modelers intent
281
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Object Reference
Objects can be identified in two ways Object ID: Unique integer Hierarchical name of object
Format: <subnet name(s)>.<node name>.<module name> top.e_campus.bldg_10.router.in_queue
<subnet name(s)> top.e_campus.bldg_10 <node name> router <module name> in_queue
282
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
283
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
284
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Error Log
Contains errors from all OPNET applications New entries at the end of the file More details Locates error in space Locates error in time Should be cleared occasionally
285
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Problem that does not stop the simulation, but may cancel the current operation
Problem that is recoverable, but minor Only reported if the diag_enable preference is TRUE. Default value is FALSE.
286
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
|------------------------------------------------------------------------|
Type of error Match in Kernel Procedure documentation Simulation time of error Event ID of simulation event Name of module where error occurred Kernel Procedure that reported the problem
287
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
288
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
289
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
290
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Introduction to Modeler
When using FIN macro, replace return keyword with FRET (value) replaces return (value); FOUT replaces return; Using FIN without FOUT / FRET will result in a Standard Function Stack Imbalance
292
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Development Kernel
Same features as Optimized Kernel Plus diagnostic information automatically collected Slower
293
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
294
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Compiler Warnings
Results of compilation kept in: <home>/op_admin/tmp/cc_err Compiler warnings can identify: Uninitialized variables Non-prototyped functions
295
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
296
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
ODB Features
ODB provides commands that allow user to:
Execute single and multiple events Set breakpoints for specific events, times, modules, and processes Trace Kernel Procedures as they are being executed Print out information about the current status of simulation entities Print out statistics of memory usage Affect the course of the simulation by modifying object attributes
297
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
298
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
299
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
odb> help ________________ OPNET Debugger Help ________________ There are three levels of help: help -- displays summary of help categories. help <category> -- display help on specified category. help <command> -- display help on specified command. ____ Command Categories [builtin] ____ all basic action ...
300
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Simulation Entities
Each type of entity has a unique ID, starting with 0 Objects
Objects are created by the Simulation Kernel and may not be destroyed Nodes, links, subnets Processors, queues, transmitters, streams
Packets
Packets also have a tree ID, which marks copies of packets
ICIs Processes
Root processes are created by the Simulation Kernel and may not be destroyed Dynamic processes are created and destroyed at runtime
301
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Breakpoints
Interrupt simulation execution Allow you to issue commands at the odb> prompt Two methods of advancing simulation execution within ODB:
Single event execution Continuation of event execution until a breakpoint occurs
302
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
303
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
304
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
_________________________ (ODB 9.1.A: Event) ________________________ * Time : * Event : intrpt) * Source : transmitter) * Data : > Module : 11.11 sec, [00d 00h 00m 11s . 110ms 000us 000ns 000ps] execution ID (35), schedule ID (#38), type (self execution ID (24), top.pksw1.node_3.xmt (pt-pt code (0) top.pksw1.node_3.xmt (pt-pt transmitter)
Time Simulation time associated with the event Event Event ID associated with the event Type Type of interrupt that will be delivered Source Module generating the interrupt Data Other information associated with the event Module Simulation object where the event will occur
305
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Breakpoints: Reviewing
status command displays all pending breakpoints
Traces : None
306
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
307
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Traces
A list of KPs called by a process Used to print detailed information about event execution Kernel traces display details of Kernel Procedures
KP name Argument names Argument values Return value
Custom traces contain whatever you want! Contain information about the process being executed Once activated, a trace remains active until deactivated
308
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Traces: Interpretation
Process invocation State banner
* invoking process (pk_sink) __________state (st_0): exit executives__________ * op_intrpt_strm () active strm
(0)
KP invocations
* op_pk_get (instrm_index) strm. index (0) packet ID (1) * op_pk_destroy (pkptr) packet ID
(1)
309
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
mtrace
protrace
pktrace
pttrace
310
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Traces: Reviewing
status command displays all pending traces
odb> pktrace 5 odb> mtrace 11 odb> protrace 0 odb> status Breakpoints : None
Traces : 0) 1) 2) trace on packet with ID (5) (packet not in system) trace on module (top.pksw1.node_0.proc) trace on process (0)
311
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
If fulltrace is active, fulltrace again toggles to inactive Once activated, a trace remains active until deactivated
312
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
3. Turn on traces
fulltrace to turn on detailed trace next to view execution details of the event of interest
313
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
314
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Labels
Established by process model code Allow traces restricted to classes of activity
Print values of state, temporary variables Print results of statements
User-defined trace statements may be added to a process model Many OPNET standard models use labels
e.g. TCP, ATM
315
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
mltrace
Sets a trace for a specified module and label
proltrace
Sets a trace for a specified process model and label
316
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Output when running a simulation with the TCP trace turned on (ltrace tcp):
____________________________ (ODB 9.1.A: Event) ____________________________ * * * * > Time Event Source Data Module : : : : : 972.409334997 sec, [00d 00h 16m 12s . 409ms 334us 997ns 496ps] execution ID (15204), schedule ID (#15605), type (remote intrpt) execution ID (15203), top.Office network.DEVELOPMENT.tcp (processor) code (10) top.Office network.DEVELOPMENT.tcp (processor) | Removing connection (14) from TCB list.
317
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
318
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Maps
A list of simulation objects corresponding to some criteria
Provides object IDs and corresponding topological location
Objects are identified by name or object ID Inspect state of simulation objects and packets Typically:
Selection of a specific object (RIP process at Router_4) Selection of all objects of a specific type (map of all queue objects in the simulation, packets from the same packet tree)
319
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Unique integer identifying object Hierarchical name of object Description of class of object Object ID of parent object
320
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
promap
objid objassoc pkmap ptmap
321
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Entity Information
Commands can be applied to objects to display verbose information about the state of the object Examples:
Current state of a subqueue, including list of packets it contains Contents of packet fields
322
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
pkprint
attrget
attrset
attrprint
323
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
iciprint_ev
iciprint_pk
324
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
325
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Diagnostic Block
Process model code that can be invoked via an ODB command Statements that display state information of interest
Values of state variables Contents of key data structures (example TCP Transmission Control Block, routing tables)
Diagnostic block may be invoked from any breakpoint Created in Process Editor
Diagnostic block button
326
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
327
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
op_prg_odb_print_major ("TCB list:", OPC_NIL); list_size = op_prg_list_size (tcb_list); for (i = 0; i < list_size; i++) { tcb_ptr = (TcpT_Tcb *) op_prg_list_access (tcb_list, i); /* Print socket information. */ sprintf (msg0, "Connection (%d) information: state (%s)", tcb_ptr->conn_id, tcb_ptr->state_name); .... .... }
Text in ODB:
| | | | TCB list: Connection (1) information: state (LISTEN) Application objid (26034), Type of Service: As Requested by Client, traffic through stream (1)
328
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
3. Run the simulation in debug mode; stop it at some time 4. Print the information from the diagnostic block
Example: proldiag 0 rip_route_table
329
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
330
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Memory
Simulation Kernel tracks memory allocation, by category
Identify areas of memory buildup Example: Packets received but never destroyed
331
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
332
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
333
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Agenda
Conceptual Goals
Exporting Data Desktop Publishing Animation Preferences
Tool Goals
Print Reports Print Graphics Capture Screen Images op_vuanim Utility Editing Preferences
334
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Publishing Results
After building a model, running simulations, and analyzing results, you will often have to report the project to others. It is important to organize, document, and archive the evolution and results of a continually changing model. Modeler has several output options so you can create graphics, detailed reports, and output files.
335
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Exporting Data
Modeler allows you to export the network topology in a variety of different methods.
EMA Spreadsheet Visio XML
HTML Bitmap
336
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
User right clicks inside graph on desired panel. Selects Export Graph Data to Spreadsheet. Modeler launches the appropriate program with data.
337
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Desktop Publishing
There are four types of operations for publishing OPNET information:
Printing model graphics Capturing bitmap graphics Export to HTML Printing text files and contents of edit pads
338
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
339
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
341
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Exporting to HTML
Exporting to HTML will create screen captures of your network model and allow you to navigate the topology in a web browser. Under the Topology menu, select Export Topology, then choose To HTML. Save the HTML files to the desired location.
342
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Exporting to Spreadsheet
Exporting your network to a spreadsheet will provide a network summary that includes the type and number of links and nodes in your network model, and financial cost information. Under the Topology menu, select Export Topology, then choose To Spreadsheet. Your default spreadsheet program will be launched with network summary data.
343
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Examples:
Node description:
The information in these windows can be written to a user named text file or sent directly to a printer.
Statistic description:
344
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Animation
An animation can be viewed using the OPNET utility, op_vuanim. This capability is valuable in better understanding the behavior of the model and it is an excellent tool for debugging models. There are two types of animation in OPNET.
Automatic Statistic
345
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Animation - Automatic
Automatic animation displays node and packet movement. This is an effective way to graphically depict the movement of traffic throughout your network. To collect packet flow animation:
Open the desired project-scenario. Enter the desired subnet. Right-click on the project workspace and select Record Animation. Run the simulation.
346
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Animation - Statistic
Statistic animation allows you to view the statistics in a graph format as they are being collected. In Choose Statistics, right-click the Statistic and select Enable Animation.
347
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Animation
Open project, anim_lab. Right click the project workspace and select Record Animation. Configure the simulation for 50 seconds. Run a simulation From the Results pull-down menu, select Play Animation and wait for the Animation viewer to come up.
348
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Edit preferences
Instructor demo: Instructor will demonstrate the edit preferences utility in OPNET.
349
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Summary
Modeler provides you with various utilities for documenting and presenting the results of models. Animation allows you to see a dynamic representation of the behavior of a model and acts as a helpful tool in debugging simulations. Preferences allow you to customize OPNET to meet specific needs.
350
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
351
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Objectives
In this chapter you will learn
MVI Module : Import Topologies and Traffic from a Variety of Sources Wireless Module: Transceiver Pipeline Terrain Modeling Module: Contour Elevations Maps Selecting Propagation Models ACE Module
352
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
353
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Wireless Module
The Wireless Module is an add-on component for Modeler that allows you to build wireless network models. Additional node types included with the Wireless Module are mobile and satellite nodes.
Mobile nodes can be used to represent vehicles or people that move during the course of a simulation. You can assign a trajectory to a mobile node, or enter values for a bearing, ground speed, and ascent rate. Satellite nodes represent communications satellites that follow a specified orbit.
354
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Transceiver Pipeline
Wireless communications can have complex and dynamically changing parameters that can affect the transmission and reception of a packet. Dynamically changing parameters may include node location, interference, antenna power, etc. OPNET models the complexity of communication links as multiple computation stages, called the Transceiver Pipeline, that determine whether a transmitted packet will be received.
The Wireless Transceiver Pipeline consists of 14 stages, and each stage computes a specific element of the connection between a given transmitter and an eligible receiver. The various stages calculate such values as transmission delay, propagation delay, transmitter antenna gain, received power, interference, etc.
355
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
356
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
357
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Accelerate OPNET Modeler Projects with the OPNET Development Kit (ODK)
Key application areas:
Programmatically build network topologies Construct custom workflows to facilitate model configuration Customize network visualization Create custom workflows to selectively enable Modeler functionality
359
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
ODK Overview
C/C++ APIs Built-in application support packages
Network data import/export OPNET Advanced Graphical Interface ODK Information Modeling Intelligent hardware configuration Optimization engine Rules-based analysis Wizard-driven topology creation Report generation and export
360
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
ODK enables a user to develop custom mechanisms for importing topology, traffic and configuration data from text files, databases, spreadsheets, etc. Example uses of ODK in IT Guru, SP Guru, and Modeler products
Rapid Configuration Group Nodes into Subnets Import Topology from ATM Text Files
361
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
362
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
363
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
364
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
365
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Wrap-Up: Questions
We open up the class for questions and discussion on any items we discussed or issues that we did not discuss. If you think of any questions after the end of this class, check the documentation, the FAQs on our web site, or contact us via Technical Support (telephone (240-497-1200), fax (240-497-1064)), email (support@opnet.com)
366
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.
Introduction to Modeler
Wrap-Up
OPNET extends our thanks to all the students for their time and attention. This is a dynamic course in that we are constantly seeking to improve it to best present the material and to better instruct our students. You may download the course material (Powerpoint slides, lab manual, and model files) from:
ftp://opftp@ftp.opnet.com password: CaNeCo+ Go to pub/training/current folder
Please fill out the student evaluations in the beginning of this manual. Your constructive criticism and suggestions assist us in increasing the quality of this training and OPNET Modeler.
367
copyright 2004 OPNET Technologies, Inc.
Introduction to Modeler
Wrap-up OPNET appreciates your business and wishes you luck in your modeling endeavors!
368
copyright 2004 OPNET Technologies, Inc.
CONFIDENTIAL INFORMATION: DO NOT DISCLOSE, FORWARD, DISTRIBUTE, SHARE, OR MAKE COPIES OF THIS DOCUMENT IN WHOLE OR IN PART.