Netw4 Essay

Netw410 calendar week 1Report The world-class objective in the LAN Modeling tutorial is ground Up the Scenario. The final step in setting up your scenario appears below. 1. (30 points) at a time your project is created (after Step 6 above), your workspace will contain a be of the United States. Your project and scenario name can be seen in ITGurus top window border in the form of Project Scenario . take a screenshot of your new project workspace that chokely shows your project and scenario name, and paste it below. 2.(40 points) In college- aim paragraph(s), describe how backcloth traffic affects both e-mail data and VoIP data. design In this weeks lab consummation, we had the opportunity to create a network color from the ground up using OpNet IT Guru. The purpose of the exercise was to gain familiarity with OpNet functions along with network objects and associated behavior establish on the physique of network vari equals. Some of these objects include Application Defin itions, Profile Definitions, Subnets, and the various government agency of connecting these components in a topology.The lab exercise itself provided a foundation for creating a simulated environment that was focused on evaluating the impact of mise en scene nexus unfold on transfer traffic. After creating the initial simulation environment, we were able to validate the constellation by matching output data for FTP performance with the reference data provided in the iLab instructions document. The graphs below deck the student lab configuration findings compared with the iLab reference graphs. The graphs, sm totally-arm not an demand match, provide enough similarity to validate the student simulation environment. rase to heighten physical exertion (reference) take to 2 oral sex to Point Utilization (student) BACKGROUND tie-in LOAD Impact on Email avocation After validating the simulation environment is correctly configured, the iLab Report instruction manual ask u s how background load affects network performance as it relates to email traffic and voice traffic. In order to assess this impact, it was infallible to add email and voice services to the Profile Configuration and the emcee named FTP located in the Washington DC subnet.The graphs below enlarge the impact of background load on point to point throughput& ampgt and point to point drill for the back_load and no_back_load scenarios. The data in these charts is reflective of using the predefined Email(heavy) application profile metric. Figure 3 Email Point to Point Throughput (bits/sec) Figure 4 Email Pont to Point Utilization Its clear that background load has a significant impact on connect throughput and utilization.The simulation without background loading remains steady and relatively smooth with throughput at or so 2Kbps and merge utilization at under 5%. When background load is added, we see a marked upward impulsion in utilization and throughput early in the simulatio n that keeps with our scheme of incrementally ramping up background load from 19,200 to 32,000 during the first 8 legal proceeding, followed by a slight pronounced continued upward trend over the remainder of the simulation. subsume throughput begins to stabilize at just over 30kbps late in the simulation, while link utilization approaches 50%.Interestingly, we see a sharp demean in email download response time during the first seconds of both scenarios even as background load is ramping up at the corresponding time. However, both scenarios flatten out to a more consistent level as the simulation progresses. The background load simulation stabilizes at roughly 1. 4 seconds for email download response time while the no background simulation settles at about . 7 seconds (see graph below). Figure 5 Email Download Response Time (sec) BACKGROUND LINK LOAD Impact on Voice TrafficAs with the FTP and email simulations, the topology was updated to include Voice Over IP (PCM Quality) fo llowed by running new simulations for both scenarios. In this run, we continue to look at point to point throughput? and point to point utilization?. Additionally, we measured sheaf end to end check into (seconds). Without the use of other voice configuration metrics such as codec selection and quality of service for voice parcel of lands, in either scenario voice over IP fails as a result of the high packet delay.The chart below illustrates that the no background load simulation provides better performance for voice packets with an average delay of about 7 seconds. Alternatively, the simulation including background load produced an average packet delay of roughly 8 seconds. Figure 6 Voice parcel End to End Delay (sec) When looking at link utilization metrics, on the other hand, there does not appear to be a significant difference in the midst of the background load simulation and the no background load simulation.Figure 7 below indicates that, with the exception of the simula tion startup being pre-loaded with 19,200 kbps in background load, both scenarios show a sharp ramp up over the first 8 minutes before leveling off at just over 60kbps. conjoin utilization, illustrated in figure 8, produced similar results in terms of the trend lines between the two scenarios. Both ramp up sharply over the first several minute and begin to level off as the link utilization approaches 100%.With utilization so high, its clear that this special(prenominal) implementation is not optimized for convergence. Voice services alone would consume all available bandwidth between East Coast sites making it impossible to gage email and FTP services concurrently. Figure 7 Point to Point Throughput (bits/sec) Figure 8 Point to Point Utilization CONCLUSION ancestry with the initial lab exercise of comparing throughput and link utilization for FTP stabilized at roughly 10% of capacity while adding background load resulted in a peak utilization of about 55%.Similarly, link throu ghput for email remained under 5kbps and 5% link utilization with no background load present while spiking up to virtually 50% of link capacity when background load is added. Finally, we learned that there is button up some optimization work that needs to be done in order for this topology to be ready for convergence. Both scenarios resulted in nearly 100% link utilization when voice over IP was the all supported service. In any event, its clear that background load has a significant impact on the user experience based on download response times as well as efficient use of available link bandwidth.