Skip to main content

OSI MODEL vs TCP /IP MODEL

This article is on TCP/IP model vs OSI model. It is meant to highlight the differences between the two set standards of the industry. TCP/IP model and the OSI model have been the two protocol suites on which communication industry heavily relies on.
Both, TCP/IP model and OSI model, work in very similar fashions. But they do have very subtle differences. Knowing these differences is crucial to learning computer networking. This article will try to show the comparison between TCP/IP model vs OSI model.

A Background
OSI reference model came into existence way before TCP/IP model was created. Advance research project agency (ARPA) created OSI reference model so that they can logically group the similarly working components of the network into various layers of the protocol. But after the advent of the Internet, there arose the need for a streamlined protocol suite, which would address the need of the ever growing Internet. So the Defense Advanced Research Project Agency (DARPA), decided to create TCP/IP protocol suite. This was going to address many, if not all the issues that had arisen with OSI reference model.

TCP/IP Model Layers Explained
So, what does TCP/IP stand for? It is a suite of protocol which is named after its most significant pair of protocols. That is Transmission Control Protocol and Internet Protocol. TCP/IP are are made up of layers. Each layer is responsible for a set of computer network related tasks. Every layer provides service to the the layer above it. There are in all four layers in the TCP/IP reference model.
  • Application Layer: This is the topmost layer of the TCP/IP suite. This is responsible for coding of the packet data.
  • Transport layer: This layer monitors end to end path selections of the packets. It also provides service to the application layer.
  • Internet Layer: This layer is responsible for sending packets through different networks.
  • Link Layer: It is the closest layer to the network hardware. It provides service to Internet layer.
OSI Model Layers Explained
In OSI reference model there seven layers of protocols. Again, in OSI reference model, each layer provides services to the layer above it. There are in all seven layers of in OSI. They are
  • Physical Layer: It is the lower most layer of the OSI reference model. It is layer which is responsible for direct interaction of OSI model with hardware. The hardware provides service to the physical layer and it provides service to the datalink layer.
  • Datalink Layer: There may be certain errors, which may occur at physical layer. If possible, these errors are corrected by datalink layer. Datalink layer provides the way by which various entities can transfer the data to the network.
  • Network Layer: It does not allow the quality of the service to be degraded that was requested by transport layer. It is also responsible for data transfer sequence from source to destination.
  • Transport Layer: The reliability of the data is ensured by the transport layer. It also retransmits those data that fail to reach the destination.
  • Session Layer: The sessions layer is responsible for creating and terminating the connection. Management of such connection is taken care of by sessions layer.
  • Presentation Layer: This layer is responsible for decoding the context (syntax and semantics) of the higher level entities.
  • Application Layer: Whichever software application that implements socket programming will communicate with this layer. This layer is closest to the user.
TCP/IP Model vs OSI Model

Sr. No.TCP/IP Reference ModelOSI Reference Model
1Defined after the advent of Internet.Defined before advent of internet.
2Service interface and protocols were not clearly distinguished beforeService interface and protocols are clearly distinguished
3TCP/IP supports Internet workingInternet working not supported
4Loosely layeredStrict layering
5Protocol Dependant standardProtocol independent standard
6More CredibleLess Credible
7TCP reliably delivers packets, IP does not reliably deliver packetsAll packets are reliably delivered

Popular posts from this blog

UPGRADING EOS in the ARISTA Switches

UPGRADING EOS in the ARISTA Switches: EOS is the Firmware for Arista Switches whereas IOS for Cisco. This blog post shows the detailed procedures to follow and to upgrade the EOS in the Arista Switches. This Post was supports for any platform or the Version you are going to upgrade in the Arista Switches. This Post was divided into three parts : Pre-Upgrade Process Upgrade Process Post-Upgrade Process PRE-UPGRADING-PROCESS: 1       1)        Check the Upgrade Path tool by clicking the below link. https://www.arista.com/en/support/mlag-portal/mlaglist and confirm it is in mlag issu compatible 2)       Check if the  STP agent is restartable by giving the command switch-1# show spanning-tree bridge detail | grep agent Stp agent restartable                      :            True NOTE :    A switch can continue supporting MLAG when its peer is offline if the STP agent is restartable. When one peer is offline, data traffic flows from the devices through the

VPC in Cisco Nexus and Failover scenarios.

Etherchannel is the technology that binds multiple physical links in to the single logical link in the switch which fools the spanning tree to be visible as a single port id instead of multiple physical ports id's this causes all the ports to be in the forward state to pass the traffic without creating the loops in the network. We can configure the etherchannel either through static or dynamic. Static ether channel works by manually binding the physical ports into one logical port, this is not recommended because it is not aware the state of the other end physical ports whereas LACP (Link aggregation control protocol) and PAGP (Port aggregation group protocol) are the two dynamic protocols. LACP is the IEEE standard and the PAGP is the Cisco proprietary protocol, LACP is the most commonly used protocol in the networks it works by negotiating with the other end of the ports and would form the portchannel once the set of parameters match on both ends. We can bind max 16 ports to a si

FORTIGATE ACTIVE PASSIVE UPGRADE

FORTIGATE ACTIVE PASSIVE UPGRADE : This blog post shows the detailed procedures to follow and to upgrade the firmware in the Fortigate Firewall. This Post was supports for any platform or the Version you are going to upgrade in the Fortigate Firewall This Post was divided into three parts : Pre-Upgrade Process Upgrade Process Post-Upgrade Process PRE UPGRADE STEPS: 1   1)     Go to the below website and check the Upgrade Path https://docs.fortinet.com/upgrade-tool 2)        Next Login to the Fortigate Console and check the HA Status ( it is to be In sync and higher Priority enabled for the required primary device) 3)        Login to the Console and give the command Config global – get sys ha status Also check session pickup is in enable to avoid session interruptions in failover. 4)        Download all the Firmware’s and the md5 files in the list and check with the software MD5sum.exe to avoid the download errors. NOTE : Must and should configuration backup have t