8ohbfa 8365757604 DCCN Unit 5
8ohbfa 8365757604 DCCN Unit 5
Circuit Switching
o Circuit switching is a switching technique that establishes a dedicated path between
sender and receiver.
o In the Circuit Switching Technique, once the connection is established then the
dedicated path will remain to exist until the connection is terminated.
o Circuit switching in a network operates in a similar way as the telephone works.
o A complete end-to-end path must exist before the communication takes place.
o In case of circuit switching technique, when any user wants to send the data, voice,
video, a request signal is sent to the receiver then the receiver sends back the
acknowledgment to ensure the availability of the dedicated path. After receiving the
acknowledgment, dedicated path transfers the data.
o Circuit switching is used in public telephone network. It is used for voice transmission.
o Fixed data can be transferred at a time in circuit switching technology.
Communication through circuit switching has 3 phases:
o Circuit establishment
o Data transfer
o Circuit Disconnect
o In the above diagram, A and B are the sender and receiver respectively. 1 and 2 are the
nodes.
o Call request and call accept packets are used to establish a connection between the
sender and receiver.
o When a route is established, data will be transferred.
o After transmission of data, an acknowledgment signal is sent by the receiver that the
message has been received.
o If the user wants to terminate the connection, a clear signal is sent for the
termination.
Node takes routing decisions to forward the packets. Node does not take any routing decision.
Congestion cannot occur as all the packets travel in Congestion can occur when the node is busy, and it
different directions. does not allow other packets to pass through.
It is more flexible as all the packets are treated as an It is not very flexible.
independent entity.
Advantages Of Packet Switching:
o Cost-effective: In packet switching technique, switching devices do not require
massive secondary storage to store the packets, so cost is minimized to some extent.
Therefore, we can say that the packet switching technique is a cost-effective
technique.
o Reliable: If any node is busy, then the packets can be rerouted. This ensures that the
Packet Switching technique provides reliable communication.
o Efficient: Packet Switching is an efficient technique. It does not require any
established path prior to the transmission, and many users can use the same
communication channel simultaneously, hence makes use of available bandwidth very
efficiently.
Disadvantages Of Packet Switching:
o Packet Switching technique cannot be implemented in those applications that require
low delay and high-quality services.
o The protocols used in a packet switching technique are very complex and requires high
implementation cost.
o If the network is overloaded or corrupted, then it requires retransmission of lost
packets. It can also lead to the loss of critical information if errors are nor recovered.
X.25
X.25 is an ITU-T standard protocol suite for packet switched wide area network (WAN)
communication.
X.25 was originally defined by the International Telegraph and Telephone Consultative
Committee (CCITT, now ITU-T) in a series of drafts and finalized in a publication known
as The Orange Book in 1976.
.X.25 is a family of protocols that was popular during the 1980s with telecommunications
companies and in financial transaction systems such as automated teller machines.
X.25 is a standard suite of protocols used for packet switching across computer
networks. The X.25 protocols works at the physical, data link, and network layers
(Layers 1 to 3) of the OSI model.
Each X.25 packets contains up to 128 bytes of data. The X.25 network handles packet
assembly at the source device, delivery, and then dis-assembly at the destination. X.25
packet delivery technology includes not only switching and network-layer routing, but
also error checking and re-transmission logic should delivery failures occur. X.25
supports multiple simultaneous conversations by multiplexing packets and using virtual
communication channels.
Based upon existing analog copper lines that experience a high number of
errors
Uses the virtual circuit approach
An X.25 WAN consists of packet-switching exchange (PSE) nodes as the
networking hardware, and leased lines, plain old telephone service connections
or ISDN connections as physical links
Provides a way to send packets across a packet-switched public data network
The redundant error checking is done at each node
X.25 was originally designed more than 25 years ago to carry voice over analog
telephone lines (dialup networks). Typical applications of X.25 today include
automatic teller machine networks and credit card verification networks. X.25
also supports a variety of mainframe terminal/server applications.
With the widespread acceptance of Internet Protocol (IP) as a standard for
corporate networks, many X.25 applications are now being migrated to cheaper
solutions using IP as the network layer protocol and replacing the
lower layers of X.25 with Ethernet or ATM hardware.
Architecture
The X.25 specification defines only the interface between a
subscriber (DTE) and an X.25 network (DCE). X.75, a very similar
protocol to X.25, defines the interface between two X.25 networks to
allow connections to traverse two or more networks.
X.25 originally defined three basic protocol levels or architectural
layers. The layer numbers were dropped to avoid confusion with the
OSI Model layers.
Physical layer
This layer specifies the physical, electrical, functional and procedural
characteristics to control the physical link between a DTE and a DCE.
Common implementations use X.21, EIA-232, EIA-449 or other serial protocols.
Data link layer
The data link layer consists of the link access procedure for data
interchange on the link between a DTE and a DCE.
In its implementation, the, link accessed procedure balanced (lapb) is
a data link protocol that manages a communication session and
controls the packet framing.
It is a bit-oriented protocol that provides error correction and orderly
delivery.
Packet layer
This layer defined a packet-layer protocol for exchanging control and
user data packets to form a packet-switching network based on virtual
calls, according to the packet layer.
X.25 provides a set of user facilities defined and described in ITU-T
Recommendation
X.2. The X.2 user facilities fall into five categories:
1. Essential facilities;
2. Additional facilities;
3. Conditional facilities;
4. Mandatory facilities.
5. Optional facilities.
Advantages of X.25
Frame delivery is more reliable
Frames are delivered in order
Retransmission of frames is possible
Flow control is provided
X.25 supports the switched virtual circuits and permanent circuits
Disdvantage of X.25
X.25 is much slower than Frame relay
Network congestion in data networking is the reduced quality of service that occurs when a
network node or link is carrying more data than it can handle. Its effects include queueing
delay, packet loss or the blocking of new connections.
In this section, we will discuss five (5) common causes of network congestion including:
Over-subscription
Poor network design/mis-configuration
Over-utilized devices
Faulty devices
Security attack
Over-Subscription
Over-Subscription where a system (e.g. a network) is handling more traffic than it was
designed to handle per time. Over-subscription is usually done on purpose as it may result in
cost savings.
For example, An organization has 100 users and it has been determined that a 100Mbps
Internet link will be suitable for all these users.
Now imagine that most of the staff of this organization work from home. In this case, it will be
more cost efficient to go for a lower link capacity, say 50Mbps, since only a handful of
employees will be using the link per time. But what happens when there is a company-wide
meeting and all employees come into the office? You guessed right – Network congestion.
Over-Utilized Devices
Devices such as routers, switches, and firewalls have been designed to handle certain network
throughput.
For example, the Juniper MX5 has a capacity of 20Gbps. Therefore, constantly pushing ~20Gbps
of traffic through that device means that the device will be over-utilized and will likely result
in high CPU utilization and packet drops, leading to congestion on the network.
Another issue related to over-utilized devices that can cause network congestion
is Bottlenecks. As in most hierarchical designs where multiple devices feed into a higher-level
device, care must be taken to ensure that the higher-level device is capable of handling all the
traffic from the lower-level devices.
Faulty Devices
Example (lower speed device): Network performance assessment for an organization. They
were buying 100Mbps link capacity from their ISP but the users on the network were struggling
to connect to the Internet effectively.
They complained that the network was always “slow” (user speak for network congestion)
even when few people were on the network. Upon investigation, it was found that, their ISP
was truly giving the agreed upon 100Mbps, the edge device was only providing 30Mbps to the
network!
Apart from the fact that this organization had wrongly terminated the link on a FastEthernet
interface (which gives a theoretical speed of 100Mbps but much lower practical speed), that
interface was also faulty. By moving the ISP link to another interface (we used a
GigabitEthernet interface instead), the performance problem was solved.
Security Attack
Example (attacker using server) : In another organization, a network of about 10 users had
poor browsing experience even with the 4Mbps link they were getting from their ISP.
Ideally, this capacity should have been enough because the users were not doing anything
heavy on the Internet – just emails, web searches, and normal user activities.
Upon investigation, it was discovered that one of their servers had been compromised and it
seems the attacker was using this server to host illicit content resulting in a huge amount of
traffic being sent to/from this server. By cleaning up this server, the congested network was
once again “free” for normal user traffic.
Other security attacks that can result in network congestion include viruses, worms, and Denial
of Service (DoS) attacks.
3. Bandwidth Monitoring
During the investigation of the compromised server I mentioned above, we used a tool
called ntopng to discover “Top Talkers” which revealed that the server was using up all the
bandwidth on the network. In the same way, tools that monitor bandwidth can reveal network
congestion especially during a security attack or if a particular host is using up all the
bandwidth.
You can read this article for more information about performing a network performance
assessment.
values that determine if a statistic is above, below, or within a normal range on your network) then
the output line will enter into a warning state. The router will check each newly
arriving packet to see if its output line is in the warning state. If it is in the warning
state, then the router will send back a choke packet signal to the sending host.
Then the sender will not generate any more choke packets. Depending on the
threshold vale, the choke packets can contain a mild warning, a stern warning or
an ultimatum.
Drawback :
The action to be taken by the source host on receiving a choke packet is voluntary
and not compulsory.
Decongesting a network
The fix for a Congested Network will Depend on the Cause:
For oversubscribed links, you may need to purchase more bandwidth from your service
provider. Some service providers also allow you to temporarily boost your bandwidth for a
small fee. You may also want to implement Quality of Service (QoS) features which will
ensure that even in the event of congestion, critical applications can still function.
Layer 2 loops can be prevented by using loop prevention protocols such as Spanning Tree
Protocol (STP). A poor network design can be more difficult to fix since the network is
probably in use. For such cases, incremental changes can be made to improve the network
and remove congestion.
Over-Utilized devices may need to be swapped out. Alternatively, the capacity of the
system can be increased by implementing high-availability features such as clustering and
stacking.
Faulty devices definitely need to be replaced. In some cases (like the example I gave above
about the 100Mbps link reduced to 30Mbps), only a part of the device (e.g. an interface)
needs to be replaced.
Security attacks need to be combated as soon as they are discovered. In the case of the
compromised server, the first thing we did was to remove that server from the network
completely. Since this is not always a feasible solution (e.g. the compromised device is a
critical server), other temporary measures such as applying access control lists to deny the
offending traffic may need to be implemented.