1 / 70

Lab 2. Traffic Generator

Lab 2. Traffic Generator. Chuan- Ching Sue DCNLAB, CSIE NCKU suecc@mail.ncku.edu.tw. Outline. Recall Long-Range Dependence Initialization Experiment Requirement Basic Procedure Advance Method Pool Type Simulation Conclusion. Recall Long-range Dependence . Long-Range Dependence .

sumana
Télécharger la présentation

Lab 2. Traffic Generator

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Lab 2. Traffic Generator Chuan-Ching Sue DCNLAB, CSIE NCKU suecc@mail.ncku.edu.tw

  2. Outline • Recall Long-Range Dependence • Initialization • Experiment Requirement • Basic Procedure • Advance Method • Pool Type • Simulation • Conclusion

  3. Recall Long-range Dependence

  4. Long-Range Dependence • This is self-similar and long-range dependent traffic. • non-negligible probability • extremely large bursts of data (packet trains) • extremely long periods of silence (inter-burst gaps) • This traffic has bursty behavior at several timescales and most closely models the empirical traffic profiles observed in LANs.

  5. initialization

  6. Experiment Requirement • PC client • Remote Desktop Connection • Simulation platform • OMNeT++ [3] • Xrdpserver • The installation of the simulation platform was introduced in the lab 1 slides.

  7. Traffic Generation Model • To simulate the real traffic in OMNeT++ simulator, the traffic generator will be introduced in the following slides.

  8. Traffic Generation Model • The network traffic is aggregated by a number of sources with Pareto distributed ON/ OFF periods. [1] Dispatcher Figure 1. traffic is aggregated by n sources

  9. Create Testbed • To simulate the interested traffic generation model, we create a testbed which is similar to the model. • Below figure is an example of the testbed.

  10. Submodules of Testbed • The Testbed for testing traffic should include • Source module • Dispatcher module • User module • Sink module • The following slides will introduce the procedure of creating the testbed.

  11. Create Testbed Project • Open OMNeT++ • File -> New-> OMNeT++ Project

  12. Testbed Project Name • Input project name, we take “Traffic_Generator” as example

  13. Initial Contexts • Select “Empty project with src and simulations folders” for clearness

  14. Finish Creating Empty Project • The initial contents should include • Includes • src folder • simulations folder • Makefile • Makefle.vc

  15. Create Source • Create source.ned in src folder

  16. Select Template • Select “NED file with one item”

  17. NED Component Type • Select “Simple module”

  18. Edit Source Code • Click “Source” to edit the empty Source module.

  19. Edit Source Code • Write the topology property of source. • For example • Loading • Output

  20. Create Dispatcher • Similarly, create a dispatcher module in src folder.

  21. Initial Contents: Select Template • Select the “NED file with one item”

  22. NED Component Type • Since that there will be no other modules inside dispatcher module, we select the “Simple module” type.

  23. Edit Source Code • Now, an empty Dispatcher module is done. • Click “Source” to edit its source code.

  24. Edit Source Code • Write the topology property of the dispatcher. • For example • Input from source • Output

  25. Create User Module • Create a user module in src folder.

  26. Initial Contents: Select Template • Select “NED file with item”

  27. NED Component Type • Select the “Compound module”, because the user module should include the source modules and dispatcher module.

  28. Edit the source code • Write the user topology in the source code. • For example: • Loading • Number of source • Connection between source and dispatcher

  29. The Sink • To verify the simulation result, here we use a Sink module to catch packets from the user module and pre-process data before analysis.

  30. Create Sink • As the procedure of creating the source module, we create the Sink module in src folder. • The Selection of initial contents is still “Simple module”.

  31. Edit Source Code • Since the Sink module has to catch packets from user, it should carry at least one input gate. • The desire time scale is also required.

  32. Create Network • Now, we have all required modules. It’s time to create the network • In OMNeT++, a simulation must contain one network. • The network file should be created in the “simulations” folder. • Our example network file is “test_traffic.ned”.

  33. Initial Contents • Select the “An empty network” template. • The empty network “Test_traffic” was created.

  34. Edit Network Source Code • In the Test_traffic network, there is a user which generate packet by its number of source and a sink which catch packets from user.

  35. Traffic Generator Implement • The connected configure setting in the testbedwas done. • Now we will begin the introduction of the generator implementation.

  36. ON / OFF Bursty Traffic Generator • There are two states in each source module • ON period state • OFF period state • There will be multiple packets generated in ON period, and the OFF period happened when the source is silence.

  37. ON / OFF Bursty Traffic Generator • When the packet is generated, it will be transmit to the dispatcher immediately. • A traffic generator can only transmit one packet at a time. • Thus, if there are two or more sources generate packets, those packets will be queued at the dispatcher.

  38. Traffic Generation Model: Example • Though orange packet generated by source 2 attime t1. The source 1 has generated its first red packet before t1. • Thus, The orange packet should wait for the transmission of the red packet.

  39. Traffic Generation Model: Example • Therefore, the aggregated traffic is still the bursty. • The dispatcher time line shows the aggregated traffic from three source.

  40. Length of ON/OFF Period • To represent the LRD of the real world traffic, the length of ON and OFF period should be generated by the Pareto distribution. • The generated number from Pareto distribution can be interpreted as the number of packets or the byte length in the ON period. • We call these two method • Packet number pool • Packet byte pool

  41. Packet Number Pool • At the end of every OFF period, the source uses a Pareto distribution to generate the number of packets in the new ON period. After that, the source use uniform(64, 1518) to generates the length for each packet, since the packet length of an Ethernet frame is between 64 and 1518 bytes. • The packet is generated in the period time of ON, and the period time of OFF is silence. It indicates that there is no packet generated.

  42. Packet Number Pool • For example, the length of first ON and OFF period in source are 2 and 1 which indicates there are two packets will be generated in the ON period time and wait for one packet length of OFF period time.

  43. Packet Byte Pool • At the end of every OFF period, the source uses a Pareto distribution to generate the byte length of ON and OFF. • After that, the source uses uniform(64, 1518) to decide the packet length. • When a source generates a packet, the remainder period length will be subtracted by the new packet length. • Therefore, when the remainder period length is not enough to create a single packet, the remainder period length will be reserved tothe next ON period. • If the remainder ON period length is ignored in every ON period, the real load will lower than the offered load.

  44. Packet Byte Pool • For example, the ON and OFF period length of source are 1100 and 600 at the first ON/OFF period. • The byte length of ON period is used to divide into packets.

  45. Initialization • The self-similar traffic is constructed by several Pareto distribution sources. They must not only be random each itself, but also be random to each other. • Initialization is to randomize sources at beginning.

  46. Three Initialization Methods • At the beginning of system, if the status of all sources is in the ON period, it could cause the high bursty and letting the simulation result is inaccurate. • There are three methods which distribute the ON period time of all source. • All sources are OFF at the beginning. • Some sources are initially in ON period, the percentage of ON sources is set according to the offered load. (Ex: 5% sources are ON initially at load 0.05) • Initially random the start of each source.[2]

  47. All Sources are OFF at The Beginning • All Pareto distribution sources are starting to generate packet after period time of OFF. Owing to period time of OFF in each sources are not equal, and each sources are not start in the same time.

  48. All Sources are OFF at The Beginning (cont’d) • A big bursty comes after a period of silence. • Those sources are starting in OFF period time, so it has a silence period in the beginning. • Because those period time of OFF is not variance to much, so packets may be generated in the same time.

  49. Part of Sources are Initially ON • Some sources are starting at ON period time. The ratio of ON and OFF is depending on the network’s load. • For example, If the ONU’s load is 0.05, there are 5% sources starting at ON period time.

  50. Part of Sources are Initially ON (cont’d) • Because part of sources are starting in ON period time. The big period of silence disappears, the burst is smaller than setting all source to be OFF status.

More Related