Project LAB 3: Network Design Fall Semester 2018 Objective The objective of this lab is to determine the basics of desinging a network using Reverbed Modeler Academic Edition 17.5, taking into consideration the users, services and locations of the hosts. Overview In this lab you will design a network for a company that has four departments: Research, Engineering, E-Commerce, and Sales. You will utilize a LAN model that allows you to simulate multiple clients and servers in one simulation object. This model dramatically reduces both the amount of configuration work you need to perform and the amount of memory needed to execute the simulation. You will be able to define a profile that specifies the pattern of applications employed by the users of each department in the company. By the end of this lab, you will be able to study how different design decisions can affect the performance of the network. Lab Instructions Step 0: Project Folder setting-up 1. Create a new folder “itm332_P3” to the desktop. 2. Learn/know how to select all the files of a folder and compress them into a zip file. At the end of each lab class, you have to compress all the files of the folder “itm332_P3” to a zip file and save/store the file by your way (Email, Blabkboard, Google Docs, etc…). Next time in order to continue your project 3, you need to create a new folder “itm332_P3” to the desktop , unzip the zipped file and copy all the files to the “itm332_P3” folder. Step 1: Network design Follow the instruction below to create a new project. 1. Click Start → All Programs →Reverbed Modeler Academic Edition 17.5 → Reverbed Modeler Academic Edition 17.5 NOTE: it will take some time to load. DO NOT PRESS IT AGAIN 2. You will see the license agreement – Accept it 3. You will now see the modeller. 4. Click File → Manage Model Files → Add Model Directory. 5. Select the folder itm332_P3 on the desktop at the Browser For Folder window, and click OK. 6. In the Confirm Model Directory window select both options: Include all subdirectories & Make this the default directory. Repeat Step 4-6 every time you begin to use Reverbed Modeler for your project. 7. To create a new project click on File → New. 8. Select Project and Click ok. 1 9. You project editor workspace will open now. Enter project name as YourLastName_FirstInitial, such as “Smith_J”, and change scenario name to “network_1”. Make sure the box “Use Startup Wizard creating new scenarios” be selected, next Click ok. 10. From the next dialog box, select “Create empty scenario” and press Next 11. From the next dialog box, select “Campus” and press Next 12. Don’t change the size, just press Next. 13. Don’t select any technology, just press Next. 14. The setup is complete. Press Finish 15. You will now be able to see the object palette and the Project workspace as the following image. You can move and change the size of them. Now you will learn to create, initialise and configure the network Step 2: Network Initilisation and Service configuration 1. The Object Palette dialog box should be now on the top of your project space. Make sure that the internet_toolbox is selected from the pull-down menu on the object palette. 2. Add to the project workspace the following objects from the palette: Application Config, Profile Config, and a Subnet, (Subnet icon is red and located on the lower right corner). 3. To add an object from a palette, click its icon in the object palette → Move your mouse to the workspace → Leftclick to place the object. Right-click when finished. 4. The workspace should contain the following three objects as showing at the following left-side image. 2 5. Right-click on the Application definition node → Edit Attributes → Change the name attribute to Application → Change the Application Definitions attribute to Default → Click OK (as showing at above image). 6. Same as step 5, Right-click on the Profile definition node → Edit Attributes → Change the name attribute to Profiles → Change the Profile Configuration attribute to Sample Profiles → Click OK. Sample Profiles provides patterns of applications employed by users such as engineers, researchers, salespeople, and multimedia users. Configure a Subnet: 7. Right-click on the subnet node → Edit Attributes → Change the name attributes to Engineering and click OK. 8. Double-click on the Engineering node. You get an empty workspace, indicating that the subnet contains no objects. 9. Open the object palette and make sure it is still set to internet_toolbox. 10. Add the following items to the subnet workspace: 10BaseT LAN, ethernet16_switch, and a 10BaseT link to connect the LAN with the Switch. 11. Right-click on the 10BaseT LAN node → Edit Attributes → Change the name attribute to LAN. 12. Under the LAN tab, observe that the Number of Workstations attribute has a value of 10. 3 13. Expand the Applications tab (as showing above between the rows IP Multicasting and H323), Click in the Value column for the Application: Supported Profiles attribute, and select Edit. You should get a table in which you should do the following: a. Set the number of rows to 1. b. Set the Profile Name to Engineer. Note: Engineer is one of the “sample” profiles provided within the Profile definition object. c. Click OK twice. The object we just created is equivalent to a 10-workstation star topology LAN. The traffic generated from the users of this LAN resembles that generated by “engineers.” 4 14. Rename the ethernet16 switch to Switch. 15. The subnet should look like the shown below 16. Save your project. Configure All Departments: 17. Now you have completed the configuration of the Engineering department subnet. 18. To go back to the main project space, click the Go to the higher level button. 19. The subnets of the other departments should be similar to the engineering one, except for the supported profiles. 20. Make three(3) copies of the Engineering subnet we just created: Click on the Engineering node → From the Edit menu, select Copy → From the Edit menu, select Paste three times, placing the subnet in the workspace after each, to create the new subnets. 21. Rename (right-click on the subnet and select Set Name) the 3 pasted subnets to “E-Commerce”, “Research”, and “Sales”, and arrange the subnets as shown below: 22. Double-click the Research node → (You get-in the Research Subnet workspace), Edit the attributes of its LAN → Edit the value of the Application: Supported Profiles attribute → Change the value of the Profile Name from Engineer to Researcher → Click OK twice → Go to the higher level by clicking the button 5 . 23. Repeat step 22 with the Sales node and assign to its Profile Name the profile Sales Person. 24. Repeat step 22 with the E-Commerce node and assign to its Profile Name the profile E-commerce Customer. Configure the Servers: Now we need to implement a subnet that contains the servers. The servers have to support the applications defined in the profiles we deployed. You can double-check those applications by editing the attributes of our Profile node. Inspect each row under the Applications hierarchy, which in turn, is under the Profile Configuration hierarchy. You will see that we need servers that support the following applications: Web browsing, Email, Telnet, File Transfer, Database, and File Print. 25. Open the Object Palette by clicking the icon “Open Object Palette“ (which is located on the right side of Print icon), and add a new subnet → Rename the new subnet to Servers. 26. Double-click the Servers node to enter its workspace. 27. From the Object Palette, add three (3) ethernet_servers, one ethernet16_switch, and three 10BaseT links to connect the servers with the switch. 28. Close the Object Palette. 6 29. Rename the servers and the switch as follows: 30. Right-click on each one of the above servers and Edit the value of the Application: Supported Services attribute. a. For the Web Server add four (4) rows to support the following services: Web Browsing (Light HTTP1.1), Web Browsing (Heavy HTTP1.1), Email (Light), and Telnet Session (Light). b. For the File Server add two (2) rows to support the following services: File Transfer (Light) and File Print (Light). c. For the Database Server add one row to support the following service: Database Access (Light). 31. Go back to the project space by clicking the Go to the higher level button. Connect the Subnets: Now all subnets are ready to be connected together. 32. Open the Object Palette and add four 100BaseT links to connect the subnets of the departments to the Servers subnet. 33. As you create each link, a Select Nodes window will pop out. Make sure to connect the “switches” in both the Department and the Server. 34. Do this by choosing them from the drop-down menus as following image. 7 Choose the Statistics To test the performance of our network we will collect one of the many available statistics as follows: 35. Right-click anywhere in the project workspace and select Choose Individual DES Statistics from the pop-up menu. 36. In the Choose Results dialog box, choose Global statistics : HTTP, Ftp, DB entry and DB query 37. Click OK and SAVE your project. Configure the Simulation Here we need to configure the duration of the simulation: 38. Click on the Run Simulation button. 8 39. Set the duration to be 1 hour. 40. Press Run. Lab Questions: Question Lab 3-1: Compare the average HTTP Object Response Time and HTTP Page Response Time. Explain your results. Question Lab 3-2: Compare the average FTP download Response Time and FTP upload Response Time. Explain your results. The results graphs and explanations for these questions need to be submitted in the lab report. Step 3: Modified links 1. Now create a new duplicate scenario of the network desinged in the previous step. Name it network_2. 2. Now change the LANs in the four (4) departments to 100BaseT LANs (Click “Yes” for the Warning Message”). Change all the links within the 4 subnets and the links inside the Servers (links between Server Switch to each Server) from 10baseT to 100baseT. 9 3. Run the simulation and compare the results with the previous scenarios. Lab Questions: Question Lab 3-3: Compare the average HTTP Object Response Time and HTTP Page Response Time for the two scenarios (Click menu DES → Results → Compare Results..). Explain your results. Question Lab 3-4: Compare the average DB query response time and DB entry response time for the two scenarios. Explain your results. 10 The results graphs and explanations for these questions need to be submitted in the lab report. Step 4: Multimedia department Switch back to scenario “Network_1”. Create a duplicate scenario for Network_1 and name it network_1_multimedia. Same steps to create a duplicate scenario for network_2 and name it network_2_multimedia. For this lab you need to add a new subnet for the multimedia department. This needs to be added to both the scenarios network_1_multimedia and network_2_multimedia. 11 Follow the steps above to add the new subnet. The multimedia subnet is similar to the engineering subnet configured before containing a LAN and a switch. The profile name Application: Supported Profiles attribute for the LAN in this multimedia subnet needs to be configured to a Multimedia user. You will also need to add a new server, Multimedia, on the server subnet. 12 You will need to add video conferencing [heavy], add video conferencing [light], and Voice over IP Call [PCM Quality] in the Application: Supported Services attribute for this Multimedia server. This also needs to be added to both the scenarios network_1_multimedia and network_2_multimedia. For both network_1_multimedia and network_2_multimedia scenarios, Choose the Statistics as following: 1. Right-click anywhere in the project workspace and select Choose Individual DES Statistics from the pop-up menu. 2. In the Choose Results dialog box, choose Node statistics, 3. Scroll down to click Video Conferencing and select video packet end-to-end delay and packet delay variation. 4. Click Voice applications and select voice packet end-to-end delay and voice jitter. 5. Click OK. Run the simulation for 10 minutes for the four (4) scenarios, and compare the results for the four scenarios. Lab Questions: Question Lab 3-5: Compare the average voice packet end-to-end delay and voice jitter for the two new scenarios. Explain your results. Question Lab 3-6: Compare the average video packet end-to-end delay and packet delay variation for the two new scenarios. Explain your results. The results graphs and explanations for these questions need to be submitted in the lab report. LAB SUBMISSION: 1. Double check your Lab 3 report. Make sure each question from 3-1 to 3-6 is clearly labelled and answered with supporting chats. 2. Compress all the files of your project 3 folder “itm332_P3” into one compressed zip file. Rename the file to “Your lastName_Your FirstName”. 3. Submit the your Lab 3 project report ( a Word file) and the compressed file (a zip file) to BlackBoard at 13 the Project Three (3) Submission link before or by 11:59PM Pacific Time of the due date. 14
Purchase answer to see full attachment