The Open System Interconnection Reference Model (OSI) is a seven layer model that was developed as part of the effort to standardize networking that was started in the late 1970’s as part of the Open Systems Interconnection (OSI) initiative.
This article will be a brief overview of the model itself and the tie in to the Cisco Certified Network Associate Routing & Switching exam (640-802 CCNA), as well as the Network+ exam.
Both the 640-802 CCNA exam and the Network+ exam test for some of the common knowledge of the OSI Model.
For the CCNA 640-802 exam this information is tested as part of the “Describe how a network works” domain as part of the following subtopics:
Beyond these subtopics you’ll need to have at least a general understanding of the model across some of the other exam topics as well but this is the primary area of focus.
For the Network+ exam most of this relates to subtopic 4.1 Explain the function of each layer of the OSI model.
For both certification exams you’ll need to know where in the model certain protocols function as well as knowing at what layers hardware devices such as routers, switches, bridges, et cetera work. Additionally, you’ll need to have a good understanding of how security of data is handled through the devices and what security features are offered to the data in transit and at which levels of the OSI model offer what types of security.
In summary the four layers of the OSI model are broken as follows:
The Physical Layer defines the electrical and physical properties and the operating specifications for the devices and media in use. The main job of the Physical Layer is the physical “connection” or attachment of given media and how it is configured (e.g. Token Ring cable, size of cable used, termination in place etc.). In some instances, there may be secondary responsibilities of this layer depending on the device for things such as flow control, modulation/demodulation and so forth. The protocol data unit in use at this level of the OSI model is referred to as a “bit.”
The Data Link Layer provides the practical means to transfer data between network nodes as its main job is to transfer data between network nodes in a wide area network or between nodes on the same local area network segment/subnet. It has the secondary responsibility to detect and correct errors (as permissible) that may take place at the Physical Layer. The protocol data unit in use at this level of the OSI model is referred to as a “frame.”
The Network Layer handles the forwarding and routing of data along logical paths between network connected nodes. In addition to routing and forwarding functions of this layer of the model is also performs addressing, error handling, quality of service control, congestion control and packet sequencing. The protocol data unit in use at this level of the OSI model is referred to as a “packet.”
The Transport Layer is responsible for the reliable, end to end transfer, recovery and flow control of the segments between the nodes. The protocol data unit in use at this level of the OSI model is referred to as a “segment.”
The Session Layer addresses the build up and tear down of the connection sessions between nodes on a network. The protocol data unit in use at this level (and all of the subsequent levels) of the OSI model is referred to simply as “data.”
The Presentation Layer is responsible for taking the data from applications at the application layer and breaking it down for use on the session layer as well as the reverse. It also has the task of formatting the data so that it can be sent to other nodes.
The Application Layer handles the initial connection of a given application to the network. It is where applications and application type activities such as browsing the web, sending and receiving email and performing file transfers take place. There are applications that wholly reside at the level such as Telnet and FTP.
At each layer of the OSI Model there are associated protocols that are in use.
These are not fully comprehensive lists but are examples of the more common protocols that are functioning at these different levels of the OSI Model.
At the Application layer you can find many but some of the more common ones include:
At the Presentation layer you can find these common protocols:
At the Session layer you can find socket driven connections and session establishment in Transmission Control Protocol (TCP), Session Initiation Protocol (SIP), and Real-time Transport Protocol (RTP).
You can also find Named Pipe sessions, a protocol in the Server Message Block (SMB) suite as well as the NetBIOS (Network Basic Input/Output System) application Programming Interface (since NetBIOS is not formally a true networking protocol).
Session Announcement Protocol (SAP) is a protocol for broadcasting multicast session information and it is also found at the Session layer.
At the Transport layer you can find these common protocols:
At the Network Layer you can find these common protocols:
At the Data Link Layer you can find these common protocols:
Since the Physical Layer is really for defining the physical “connection” or attachment of given media and how it is configured as well as the electrical and physical properties and the operating specifications for the devices and media in use there are no actual TCP/IP common protocols that are in use.
You can find certain combinations of media and standards at this layer such as RS-232 (Recommended Standard 232) which is the standard for data and control signals connecting between a DTE (Data Terminal Equipment) and a DCE (Data Circuit-terminating Equipment) and Digital Subscriber Line (DSL) which provides digital data transmission over local telephone lines.
In this article we reviewed the tie in of the OSI Model to the CCNA and Network+ exams as well as took a look at the breakdown of the seven layers of the OSI Model
We wrapped up with a quick look at some of the protocols that are in use at each of the OSI Model Layers
Thanks for investing your time in my Introduction to the OSI Model article. As a complement, youu can read our separate article on how to use the OSI Model to troubleshoot networks.
I am always looking forward to any feedback you have on this or any of the articles I have written so feel free to offer your feedback.
Additionally, I would welcome any suggestions topics of interest that you would like to see and based on demand and column space I’ll do what I can to deliver them to you.