capturing router congestion and router

8/2/2019 Capturing Router Congestion and Router

1/12

CAPTURING ROUTER

CONGESTION AND DELAY

K.NARESH(08JP1A0523)

K.MANOJ(08JP1A0524)

K.SUDHEER (08JP1A0548)

K.SIDDU(08JP1A0520)


2/12

ABSTRACT:

using unique monitoring experiment we capture all packets crossing

a(lightly utilized) operational access router from a tier-1 provider.

Provide detailed examination of router congestion and delay.

This enables a comprehensive examination of congestion and delay

from three points of view: The understanding of origins.

Measurement.

Reporting.

In particular, the traffic reporting enables a rich description of the

diversity of micro congestion behavior, without achievablecomputational cost.


3/12

EXISTING SYSTEM:

However since the tier-1 router only had one input and oneoutput link, which were of the same speed, the internal

queueing was extremely limited.

In this paper we work with a data set recording all IP packets

traversing a Tier-1 access router over a 13 hour period. since Tier-1 networks tend to be under-provisioned.

In this system use backbone access router and their traffic

today

This conjecture requires testing against more data sets. Examine the origins of congestion and hence delay .

taxonomy of link congestion has not been used previously.


4/12

PROPOSED SYSTEM:

We use a powerful methodology of virtual or semi- experiments.

We identify, and evaluate the contributions of, three known canonicalmechanisms:

i) Reduction in link bandwidth from core to access.

ii) Multiplexing of multiple input streams.

iii) Burstiness of the input traffic streams.

All input and output links were monitored, allowing a complete picture ofcongestion, and in particular router delays, to be obtained.

Our specific conclusions are strictly speaking limited to a single data setwith low loss and delay.

we aim to provide a physical model capable of explaining the observeddelay and congestion.

It gives an innovative solution to a non-trivial problem.

A key advantage is that a generically rich description is reported, withoutthe need for any traffic assumptions.


5/12

MODULES:

Server

Client

User Interface Design

Output Link


6/12

SERVER:

It will accepts data send by the client.

It will display number of Nodes.

It will display

Delay.

Bandwidth.

Busy.

Congestion of each Client .


7/12

CLIENT:

We can select the required data.

It will send the data to Server


8/12

USER INTERFACE DESIGN:

In this module we design the user interface for

Client A,

Client B,

Client C,

Client D,

Client E and,

Server displaying window.

These windows are designed in order to display all the

processes in this project.


9/12

OUTPUT LINK:

This module measure the minimum excess packet transittime between each input and the given output.

De-fine the overall minimum packet transit time as the

minimum over all input links. Calculate the IP bandwidth of the output link.

Obtain packet delays by aggregating the input traffic

corresponding to the given output link.


10/12

CONCLUSION:

We explored in detail router congestion and packet delay,

based on a unique data set where all IP packets crossing

router were measured.

We presented empirical results about packet delays.

Finally, we examined the difficult problem of compactly

summarizing the richness of micro congestion behavior.

We showed how this metric captures important information

about the delay process without any model based

preconceptions.


11/12

HARDWARE REQUIRMENTS:

Processor : Intel Pentium Family

Processor Speed : 250MHz to 667 MHz

RAM :128 MB to 512 MB

Hard Disk : 4 GB or higher Keyboard : Standard 104 enhanced keyboard


12/12

SOFTWARE REQUIRMENRS:

Front End :AWT,Swing

Tools Used : MY-Eclipse

Operating System :Windows-Xp

capturing router congestion and router

Documents