1.49k likes | 1.77k Views
Modeler Day 3. Course Content. DAY 4: Process Modeling Methodology Accelerating Wireless Simulations {LABs} Custom Wireless Effect {LABs} Debugging Simulation Models{LABs}. DAY 3: Configuring Standard Applications {LABs} Traffic Modeling Techniques {LABs} Modeling Large Networks
E N D
Course Content DAY 4: • Process Modeling Methodology • Accelerating Wireless Simulations{LABs} • Custom Wireless Effect {LABs} • Debugging Simulation Models{LABs} DAY 3: • Configuring Standard Applications {LABs} • Traffic Modeling Techniques {LABs} • Modeling Large Networks • Importing Topology and Traffic
Agenda • Application basics • Network traffic (users, devices, networks, etc.) • Modeling traffic in OPNET • Application modeling techniques • OPNET application architecture • Configuring applications workflow • Configure applications • Define profiles • Configure server/peer • Deploy profiles • Lab 1: OPNK2003 cyber café • Configuring analytical traffic on client-client applications • Concepts and attributes • Lab 2: VoIP configuration • Easy configuration of application traffic • Concepts and attributes • Lab 3: application demands • Troubleshooting • Lab 4: troubleshooting (bonus)
Take-Away Points • Standard applications available • Application configuration • Defining user profile • Client & server setup for standard applications • Application demands • Application modeling techniques • Application troubleshooting
Agenda • Application basics • Network traffic (users, devices, networks, etc.) • Modeling traffic in OPNET • Application modeling techniques • OPNET application architecture • Configuring applications workflow • Configure applications • Define profiles • Configure server/peer • Deploy profiles • Lab 1: OPNK2003 cyber café • Configuring analytical traffic on client-client applications • Concepts and attributes • Lab 2: VoIP configuration • Easy configuration of application traffic • Concepts and attributes • Lab 3: application demands • Troubleshooting • Lab 4: troubleshooting (bonus)
How Do We Define Network Traffic? • Source (user, group of users) • Destination (user, server) • Traffic patterns
Client-server applications Examples: HTTP, FTP Peer-peer applications Examples: voice, video Multi-tier applications Examples: web-based applications, e-commerce, home-grown applications REQUEST RESPONSE REQUEST REQUEST RESPONSE RESPONSE 3 4 RESPONSE RESPONSE 2 1 REQUEST REQUEST Applications
Application Modeling Techniques • Explicit • Simulate all packets in detail • Very high fidelity results • Potentially longer run times • Analytical • Simulate majority of traffic using mathematical representation • Faster simulation run times • Hybrid • Combination of both explicit and analytical modeling techniques
OPNET Application Architecture Custom application
Profile and Applications: Example Profiles Apps
Configuring Application Models: Workflow Configure applications Define profiles Configure servers/peers Deploy profiles
Agenda • Application basics • Network traffic (users, devices, networks, etc.) • Modeling traffic in OPNET • Application modeling techniques • OPNET application architecture • Configuring applications workflow • Configure applications • Define profiles • Configure server/peer • Deploy profiles • Lab 1: OPNK2003 cyber café • Configuring analytical traffic on client-client applications • Concepts and attributes • Lab 2: VoIP configuration • Easy configuration of application traffic • Concepts and attributes • Lab 3: AppDemands • Troubleshooting • Lab 4: troubleshooting (bonus)
Configuring Applications Configure applications Define profiles Configure servers/peers Deploy profiles
Applications: Built-in Common Applications Name Description Custom Application Generic/customizable application Database Data entry/query application E-mail E-mail application FTP File transfer protocol application Web-browsing application HTTP Standard applications Print job Print Telnet application application Remote Login Client-to-client video application Video Conferencing Client-to-client voice application Voice
Applications • Session of specific request/response patterns • Commonly used applications: email, http, ftp… • Common settings to all applications • Type of service • Symbolic server name • RSVP parameters • Specific settings to each application • HTTP page configurations • FTP file sizes • Database query ratio
Application Definition Utility • Contains all application definitions • Reusability • Across clients • Across scenarios • Easier deployment • Easier change “FTP (Light)” Application Definition I I’m running “FTP (Light)” I I’m running “FTP (Light)” I I’m running “FTP (Light)” I I’m running “FTP (Light)” I I I’m running “FTP (Light)” I’m running “FTP (Light)”
Symbolic Server Name Application has a symbolic server name, e.g. “FTP (Light)” Actual server name is specified in server, e.g. WashingtonDC_Server Mapping between symbolic server name and actual server name
Example: File Transfer Protocol • Upload or download of files: • Using file size distribution • Using Inter-request time distribution FTP (Application) GET PUT PUT PUT time Inter-Request Time Inter-Request Time Inter-Request Time Specific FTP settings Common settings
Example: Hypertext Transfer Protocol (HTTP) • Download of a web page: • Using distribution for number of objects in page and sizes • Using page interarrival time distribution HTTP (Application) Web page download Web page download Web page download time Page Inter arrival Time Page Inter arrival Time Specific HTTP settings Common settings
Profiles Configure applications Define profiles Configure servers/peers Deploy profiles
Profiles • Profile = Reusable collection of applications • Describes activity patterns of: • an individual user • a group of users Engineer Engineer Marketing department Engineer Help desk CFO CEO
Profile Configuration Object Engineer Profile Definition • Contains all profile definitions • Reusability • Across clients • Across scenarios • Easier deployment • Easier change I I’m an engineer I’m an engineer I I I’m an engineer I I’m an engineer I I I’m an engineer I’m an engineer
Profile Properties Repeatability Profile Name Operation Mode Duration Applications Start Time
Profile Name, Start Time, and Duration • Example: • “Engineer” profile • Starting at 9:00am • Lasting 8 hours Duration Engineer 9:00am 12:00pm 5:00pm Start Time
Profile Repeatability • Serial mode Engineer Engineer Engineer Engineer Inter-repetition time Inter-repetition time Inter-repetition time • Concurrent mode Engineer Engineer Inter-repetition time Engineer Inter-repetition time Engineer Inter-repetition time
Applications in Profile • I have the definitions of the following applications: • Database Access (Light) • Email (Light) • Web Browsing (Light) • FTP
Application Scheduling • Multiple applications per profile “Engineer” profile Database Web Browsing Web Browsing Web Browsing Email FTP FTP FTP FTP FTP 9:00am 12:00pm 17:00pm
Operation Mode • Simultaneous Database Web Browsing Email FTP 9:00am 12:00pm 17:00pm • Serial (ordered/random) Database Web Browsing Email FTP 9:00am 12:00pm 17:00pm
Applications in Profile Repeatability Name Start Time Offset Duration
Name, Start Time Offset, and Duration • Example: • “FTP” application • Starting 2 hours after profile “Engineer” starts • Lasting 4 hours Engineer (Profile) FTP (Application) GET PUT PUT PUT Start time offset Duration 9:00am 11:00am 3:00pm 5:00pm Note: an application will not last longer than the profile
Application Repeatability • Serial mode FTP FTP FTP FTP Inter-repetition time Inter-repetition time Inter-repetition time • Concurrent mode FTP FTP Inter-repetition time FTP Inter-repetition time FTP Inter-repetition time Note: an application will not repeat and last longer than the profile
Configure Servers/Peers Configure applications Define profiles Configure servers/peers Deploy profiles
Server Address • Uniquely identifies server • Server address to be mapped to the symbolic server name
Deploy Profiles Configure applications Define profiles Configure servers/peers Deploy profiles
Destination Preferences • No destination preference => Randomly select among destinations supporting service • Selection weight set on destinations My weight is 10 Choose me! Server2 is 5X more likely to be chosen Server1 ? Client My weight is 50 Choose me! Server2 • Explicitly configure destination(s) => Randomly select among destinations specified on client • Weight set on client I have to choose between: - Server1: weight 20 - Server2: weight 10 Server1 Server1 is 2X more likely to be chosen ? Client Server2
Configuring Destination Preferences Application refers to a symbolic server name, e.g. web_browsing_server Actual server name is specified in server, e.g. WashingtonDC_Server Mapping between symbolic server name and actual server name
Application Statistics • Local and global statistics • Client/Server statistics or calling/called party statistics • Specific to each application • Local statistic results will be grouped per profile/application
Lab 1: OPNK2003 Cyber Cafe • Objective • Apply workflow to configure application traffic • Application configuration • User behavior profiles • Configure servers to support applications • Deploy user profiles • Refer to lab handout “Lab1: HTTP Application Configuration Lab” on page 1 Configure applications Define profiles Configure servers/peers Deploy profiles
Agenda • Application basics • Network traffic (users, devices, networks, etc.) • Modeling traffic in OPNET • Application modeling techniques • OPNET application architecture • Configuring applications workflow • Configure applications • Define profiles • Configure server/peer • Deploy profiles • Lab 1: OPNK2003 cyber café • Configuring analytical traffic on client-client applications • Concepts and attributes • Lab 2: VoIP configuration • Easy configuration of application traffic • Concepts and attributes • Lab 3: AppDemands • Troubleshooting • Lab 4: troubleshooting