Sunday, May 26, 2019

Netw4 Essay

Netw410 Week 1Report The first objective in the LAN Modeling tutorial is Setting Up the Scenario. The final step in desktop up your scenario appears down the stairs. 1. (30 points) Once your project is created (after Step 6 above), your workspace will contain a map of the United States. Your project and scenario name can be seen in ITGurus top window border in the form of Project Scenario . Capture a screenshot of your new project workspace that clearly shows your project and scenario name, and paste it below. 2.(40 points) In college-level paragraph(s), describe how terra firma traffic affects both e-mail data and VoIP data. INTRODUCTION In this weeks lab exercise, we had the opportunity to create a interlock fashion model 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 based on the configuration of network variables. just ab appear of these objects include Appli cation Definitions, Profile Definitions, Subnets, and the various means of connecting these components in a topology.The lab exercise itself provided a foundation for creating a simulated environment that was cogitate on evaluating the have-to doe with of background tie in load on FTP traffic. After creating the initial simulation environment, we were able to validate the configuration by unified output data for FTP performance with the reference data provided in the iLab instructions document. The graphs below illustrate the student lab configuration findings compared with the iLab reference graphs. The graphs, firearm non an exact match, provide enough similarity to validate the student simulation environment. berth to guide on Utilization (reference) Figure 2 Point to Point Utilization (student) BACKGROUND LINK LOAD Impact on Email Traffic After validating the simulation environment is correctly configured, the iLab Report instructions ask us how background load affects network performance as it relates to electronic mail traffic and voice traffic. In order to assess this impact, it was necessary to adjoin email and voice services to the Profile Configuration and the server named FTP located in the Washington DC subnet.The graphs below illustrate the impact of background load on point to point throughput> and point to point employ 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 link throughput and utilization.The simulation without background loading remains steady and relatively flat with throughput at roughly 2Kbps and link utilization at chthonian 5%. When background load is added, we see a marked upward trend in utilization and throughput early in the simulation that keeps with our schem e of incrementally ramping up background load from 19,200 to 32,000 during the first 8 minutes, followed by a less pronounced continued upward trend over the remainder of the simulation. Link throughput begins to change at just over 30kbps late in the simulation, while link utilization approaches 50%.Interestingly, we see a sharp drop in email download rejoinder time during the first seconds of both scenarios even as background load is ramping up at the same 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 judgment of conviction (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) followed 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 megabucks end to end delay (seconds). Without the occasion of other voice configuration metrics such as codec selection and quality of service for voice packets, 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 Packet End to End Delay (sec) When looking at link utilization metrics, on the other hand, at that place does not appear to be a significant difference betwixt the background load simulation and the no background load simulation.Figure 7 below indicates that, with the exception of the simulation startup being pre-loaded with 19,200 k bps in background load, both scenarios show a sharp ramp up over the first 8 minutes before leveling off at just over 60kbps. Link utilization, illustrated in figure 8, produced similar results in terms of the trend lines in the midst of 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 particular implementation is not optimized for convergence. Voice services alone would consume all available bandwidth between East Coast sites making it impossible to support email and FTP services concurrently. Figure 7 Point to Point Throughput (bits/sec) Figure 8 Point to Point Utilization CONCLUSION Beginning 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 throughput for email remained under 5kbps and 5% li nk utilization with no background load present while spiking up to just about 50% of link capacity when background load is added. Finally, we learned that there is still 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 only 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.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.