Scribd
Upload
102 views9 pages

Transmission Control Protocol (TCP) : A Reliable Connection Oriented Byte Stream Service Queuing Disciplines

The document describes an experiment using NetSim software to trace the congestion window for Old Tahoe and Tahoe TCP algorithms. It explains that Old Tahoe waits for a retransmission timeout before resending lost packets, while Tahoe resends after receiving three duplicate acknowledgements, allowing faster recovery from packet loss. The experiment involves simulating TCP connections under different conditions and analyzing the congestion window graphs from the trace files to observe the behaviors of the two algorithms. The results show that Tahoe has higher network utilization than Old Tahoe due to its ability to resend lost packets more quickly.

Uploaded by

T.Neeraja Akhila
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
102 views9 pages

Transmission Control Protocol (TCP) : A Reliable Connection Oriented Byte Stream Service Queuing Disciplines

The document describes an experiment using NetSim software to trace the congestion window for Old Tahoe and Tahoe TCP algorithms. It explains that Old Tahoe waits for a retransmission timeout before resending lost packets, while Tahoe resends after receiving three duplicate acknowledgements, allowing faster recovery from packet loss. The experiment involves simulating TCP connections under different conditions and analyzing the congestion window graphs from the trace files to observe the behaviors of the two algorithms. The results show that Tahoe has higher network utilization than Old Tahoe due to its ability to resend lost packets more quickly.

Uploaded by

T.Neeraja Akhila
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 9

Experiment No: 9A Page No: 53

Ref: GNITS/CN/9A G.N.I.T.S – ETM DEPARTMENT

TRANSMISSION CONTROL PROTOCOL (TCP): A Reliable


Connection Oriented Byte Stream Service Queuing Disciplines
AIM:
To trace the TCP congestion window for Old Tahoe and Tahoe algorithms.
APPARATUS:
NetSim software
THEORY:
One of the important functions of a TCP Protocol is congestion control in the
network. Given below is a description of how Old Tahoe and Tahoe variants (of TCP)
control congestion.
Old Tahoe:
Congestion can occur when data arrives on a big pipe (i.e. a fast LAN) and gets
sent out through a smaller pipe (i.e. a slower WAN). Congestion can also occur when
multiple input streams arrive at a router whose output capacity is less than the sum of the
inputs. Congestion avoidance is a way to deal with lost packets.
The assumption of the algorithm is that the packet loss caused by damaged is very
small (much less than 1%), therefore the loss of a packet signals congestion somewhere
in the network between the source and destination. There are two indications of packets
loss: a timeout occurring and the receipt of duplicate ACKs
Congestion avoidance and slow start are independent algorithms with different
objectives. But when congestion occurs TCP must slow down its transmission rate and
then invoke slow start to get things going again. In practice they are implemented
together. Congestion avoidance and slow start requires two variables to be maintained for
each connection: a Congestion Window (i.e. cwnd) and a Slow Start Threshold Size
(i.e.ssthresh). Old Tahoe algorithm is the combination of slow start and congestion
avoidance. The combined algorithm operates as follows,
 Initialization for a given connection sets cwnd to one segment and ssthresh to
65535bytes.
 When congestion occurs (indicated by a timeout or the reception of duplicate
ACKs), one-half of the current window size (the minimum of cwnd and the
receiver’s advertised window, but at least two segments) is saved in ssthresh.
Additionally, if the congestion is indicated by a timeout, cwnd is set to one
segment (i.e. slow start).
 When new data is acknowledged by the other end, increase cwnd, but the way it
increases depends on whether TCP is performing slow start or congestion
avoidance. If cwnd is less than or equal to ssthresh, TCP is in slow start. Else TCP
is performing congestion avoidance. Slow start continues until TCP is halfway to
where it was when congestion occurred (since it recorded half of the window size
that caused the problem instep 2). Then congestion avoidance takes over.

Lab Incharge HOD

GNITS/ETM/CN LAB
Experiment No: 9A Page No: 54
Ref: GNITS/CN/9A G.N.I.T.S – ETM DEPARTMENT

Slow start has cwnd begins at one segment and be incremented by one segment
everytime an ACK is received. As mentioned earlier, this opens the window
exponentially: send one segment, then two, then four, and so on. Congestion avoidance
dictates that cwnd be incremented by 1/cwnd, compared to slow start’s exponential
growth. The increase in cwnd should be at most one segment in each round trip time
(regardless of how many ACKs are received in that RTT), whereas slow start increments
cwnd by the number of ACKs received in a round-trip time.

Tahoe (Fast Retransmit):


The Fast retransmit algorithms operating with Old Tahoe is known as the Tahoe
variant.TCP may generate an immediate acknowledgement (a duplicate ACK) when an
out-of order segment is received out-of-order, and to tell it what sequence number is
expected. Since TCP does not know whether a duplicate ACK is caused by a lost segment
or just are-ordering of segments, it waits for a small number of duplicate ACKs to be
received. It is assumed that if there is just a reordering of the segments, there will be only
one or two duplicate ACKs before the re-ordered segment is processed, which will then
generate anew ACK. If three or more duplicate ACKs are received in a row, it is a strong
indication that a segment has been lost. TCP then performs a retransmission of what
appears to be the missing segment, without waiting for a re-transmission timer to expire.

PROCEDURE:
 Create Scenario for Sample: NetSim →Simulation →New → WAN →TCP
 Sample Inputs: Follow the steps given in the different samples to arrive at the
objective.
Sample 1.a:
In this Sample,
 Total no of CPE’s used: 2
 Total no of Routers used: 1
The devices are inter connected as given below,
 CPE 1 is connected with Router 1 by Link 1.
 CPE 2 is connected with Router 1 by Link 2.
Note: Enable the Trace file as given below.

GNITS/ETM/CN LAB
Experiment No: 9A Page No: 55
Ref: GNITS/CN/9A G.N.I.T.S – ETM DEPARTMENT

 After click on the Trace button, a window will appear as given below,

 From the list of attributes, select Congestion Window and Segment Start Time.
Note: Trace should be enabled for all the samples as given above. Set the
properties for each device by following the tables,

GNITS/ETM/CN LAB
Experiment No: 9A Page No: 56
Ref: GNITS/CN/9A G.N.I.T.S – ETM DEPARTMENT

Inputs for Sample 1.a:

 Simulation Time- 100 Sec


(Note: The Simulation Time can be selected only after doing the following two tasks,
 Set the properties of CPE , Router, & Link
 Then click on the Validate & Simulate button).

GNITS/ETM/CN LAB
Experiment No: 9A Page No: 57
Ref: GNITS/CN/9A G.N.I.T.S – ETM DEPARTMENT

Sample 1.b:
 Set the same properties as given in sample 1.a, except the following properties.
Inputs for Sample 1.b:

 Simulation Time - 100 Sec


(Note: The Simulation Time can be selected only after doing the following two tasks,
 Set the properties of CPE , Router, & Link
 Then click on the Validate & Simulate button).
Sample 2.a:
In this Sample,
 Total no of CPE’s used: 2
 Total no of Routers used: 1
The devices are inter connected as given below,
 CPE 1 is connected with Router 1 by Link 1.
 CPE 2 is connected with Router 1 by Link 2.
Set the properties for each device by following the tables,

Inputs for Sample 2.a:

GNITS/ETM/CN LAB
Experiment No: 9A Page No: 58
Ref: GNITS/CN/9A G.N.I.T.S – ETM DEPARTMENT

 Simulation Time - 100 Sec


(Note:The Simulation Time can be selected only after doing the following two tasks,
• Set the properties of CPE , Router, & Link
• Then click on the Validate & Simulate button).

Sample 2.b:
 Set the same properties as given in sample 2.a, except the following properties.

Inputs for Sample 2.b:

 Simulation Time - 100 Sec


(Note: The Simulation Time can be selected only after doing the following two tasks,
• Set the properties of CPE , Router, & Link
• Then click on the Validate & Simulate button).
Note: To draw the chart, get the values of congestion window and segment start time
from trace file.
 How to get the value from trace file:After completion of the experiment, import
the trace file excel sheet. Then remove therows based on the following condition.
1. If congestion window value is 0, then delete the row.
2. If the “RTO Expiration” event written, then delete the row.

GNITS/ETM/CN LAB
Experiment No: 9A Page No: 59
Ref: GNITS/CN/9A G.N.I.T.S – ETM DEPARTMENT

Note: select x axis as segment arrival time and y axis as congestion window.

EXPECTED GRAPH:

Sample 1.a) With Error

GNITS/ETM/CN LAB
Experiment No: 9A Page No: 60
Ref: GNITS/CN/9A G.N.I.T.S – ETM DEPARTMENT

SIMULATION ANALYSIS

GNITS/ETM/CN LAB
Experiment No: 9A Page No: 61
Ref: GNITS/CN/9A G.N.I.T.S – ETM DEPARTMENT

Old Tahoe and Tahoe Congestion Control Algorithms affect the utilization of the
network,differently.In the above scenario in sample1.b and sample 2.b there is no
possibility for congestionto happen, because CPE 1 is sending the packets at data rate 64
kbps & R1 is sending thepackets at same data rate 64 kbps. So, there is no possibility for
packets to be dropped. Ifthere is no congestion then both the algorithms work
similarly.Old Tahoe waits until the RTO Timer expires before retransmitting a lost
packet. ButTahoe retransmits the lost packet immediately after getting three continuous
duplicateACK’s. This results in the increased packet transmission in the case of Tahoe
ascompared to Old Tahoe as shown in the above graph sample 1.a and sample 2.a.

RESULT:

GNITS/ETM/CN LAB

You might also like