Netw4 essay

Netw410 Week 1Report The initially objective in the LAN Building tutorial is Setting Up the Circumstance. The final step in setting up your scenario shows up below. 1 ) (30 points) Once building your shed is created (after Step 6 above), your work area will include a map states. Your project and scenario name can be seen in ITGuru’s top windowpane border as Project: Circumstance:. Capture a screenshot of your new job workspace that clearly shows your project and scenario term, and substance it under.

2.(40 points) In college-level paragraph(s), describe how background traffic affects both e-mail data and VoIP data. INTRODUCTION In this week’s lab exercise, we had the opportunity to create a network simulation 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. Some of these objects include Application 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 focused on evaluating the impact of background link load on FTP traffic. After creating the initial simulation environment, we were able to validate the configuration by matching 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, while not an exact match, provide enough similarity to validate the student simulation environment.

Point to Point 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 email traffic and voice traffic. In order to assess this impact, it was necessary to add 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 usage for the back_load and no_back_load situations. The data during these charts is definitely reflective of using the predetermined Email(heavy) app profile metric. Figure several ” Email Point to Point Throughput (bits/sec) Figure 5 ” Email Pont to Point Utilization It’s clear that backdrop load contains a significant influence on link throughput and utilization.

The simulation without backdrop loading remains steady and relatively level with throughput at about 2Kbps and link usage at under 5%. Once background insert is added, we see a marked upward trend in utilization and throughput early in the simulation that keeps with this scheme of incrementally ramping up history load coming from 19, two hundred to 32, 000 throughout the first almost eight minutes, followed by a fewer pronounced ongoing upward craze over the remainder of the ruse. Link throughput begins to support at just more than 30kbps later in the simulation, while hyperlink utilization approaches 50%.

Oddly enough, we see a pointy drop in email download response time during the initially seconds of both scenarios even as background load can be ramping up at the same time. Nevertheless , both scenarios flatten out to a more steady level as the simulation progresses. The backdrop load simulation stabilizes at roughly 1 ) 4 secs for email download response time even though the no backdrop simulation forms at about. six seconds (see graph below). Figure 5 ” Email Download Response Time (sec) BACKGROUND LINK LOAD Effect on Voice Visitors

As with the FTP and email ruse, the topology was current to include Voice Over IP (PCM Quality) followed by running new simulations for the two scenarios. In this run, we continue to take a look at point to level throughput? and point to level utilization?. In addition , we measured packet end to end wait (seconds). With no use of additional voice configuration metrics including codec selection and service quality for voice packets, in either scenario voice over IP does not work out as a result of the high supply delay.

The chart under illustrates that the no backdrop load ruse provides improved productivity for words packets with an average delay of about six seconds. Otherwise, the simulation including background load made an average supply delay of roughly almost 8 seconds. Physique 6 ” Voice Packet End to get rid of Delay (sec) When looking at website link utilization metrics, on the other hand, there does not appear to be a significant difference between the history load simulation and the zero background load simulation.

Determine 7 under indicates that, with the exception of the simulation new venture being pre-installed with nineteen, 200 killerbytes per second in history load, both equally scenarios show a sharp increase over the initially 8 minutes before progressing off at only over 60kbps. Link use, illustrated in figure eight, produced similar results in terms of the trend lines between your two situations. Both ramp up sharply within the first a number of minute and commence to level off because the link utilization approaches fully.

With usage so high, it’s clear that particular implementation is not really optimized for convergence. Voice services alone would consume all available bandwidth among East Seacoast sites so that it is impossible to back up email and FTP services concurrently. Number 7 ” Point to Point Throughput (bits/sec) Figure almost eight ” Indicate Point Use CONCLUSION Beginning with the initial laboratory exercise of comparing throughput and hyperlink utilization pertaining to FTP stable at roughly 10% of capacity although adding backdrop load triggered a optimum utilization of about 55%.

Likewise, link throughput for email remained under 5kbps and 5% hyperlink utilization without background weight present although spiking approximately nearly 50 percent of hyperlink capacity the moment background fill is added. Finally, we all learned that there is certainly still a lot of optimization work that needs to be done in order for this topology to get ready for affluence. Both scenarios resulted in practically 100% hyperlink utilization when ever voice over IP was the only backed service. The point is, it’s very clear that history load provides a significant influence on the user encounter based on download response times along with efficient utilization of available website link bandwidth.

1

Tweet