Network Kings

Multi-Access Year Deal

Get 55+ courses now at the best price ever! Use Code:    MULTIYEAR

d :
h :
m

OSI Model – Understanding the 7 Layer Model of Networking

The OSI Model consists of 7 layers, each with a specific function to perform. The OSI Model divides the whole task into 7 smaller and manageable tasks and assigns an independent task to all the 7 layers. To understand the functions and uses of each of these seven layers, the seven abstraction layers of the OSI model can be defined as follows, from top to bottom:

What is the OSI Model?

The OSI Model short for Open Systems Interconnection Model is a conceptual framework that describes seven layers that computer systems use to communicate over a network. The OSI model characterizes computing functions into a universal set of rules and requirements in order to support compatibility between different products and software. It was the primary standardized model for network communications, taken into action by all major computer and telecommunication companies in the early 1980s.

With changes and modern adaptations in the tech industry, the modern internet is not based on an OSI but on its simpler counterpart the TCP/IP Model. However, the OSI 7-layer is still used widely, thanks to its ability to visualize and communicate the working of networks to isolate and troubleshoot networking problems. 

7 layers of the OSI model

What is OSI Model

7. The Application Layer

The Application Layer, also known as the Desktop Layer is found at the top of the OSI Model’s stack of layers. The application layer is the only layer where the software application and the user come in direct contact. With its main users being software like web browsers and email clients this layer provides protocols that allow the softwares to send and receive useful and important data to users. Web browsers (Google Chrome, Firefox, Safari, etc.) TelNet, and FTP, are examples that use this layer for communication.

The functions of the Application layer are as follows :  

  • Network Virtual Terminal
  • FTAM-File transfer access and management
  • Mail Services
  • Directory Services

6. The Presentation Layer

The Presentation Layer, also known as the Translation layer serves the main purpose of preparing data for the Application Layer. In simpler words, Layer 6 makes the data presentable for applications to use. 

This layer has the function to decide how two devices should encode, encrypt, and compress data so it is received in the required form on the receiving end. For instance, two communicating devices may use two different encoding methods, so layer 6 is responsible for translating incoming data into a syntax that the application layer of the receiving device can understand.

The Presentation Layer also performs the function of adding encryption on the sender’s end and compressing the data received from the application layer before delivering it to layer 5. This helps in improving the overall speed of data transmission by reducing the size of data to be transferred. 

Thus, the Presentation Layer performs tasks in three major steps, i.e, Encryption, Compression and Translation.

5. The Session Layer

The Session layer is used to establish, maintain and synchronize the interaction between communicating devices. Along with the establishment and maintenance of the sessions, this layer also ensures authentication and security. In simple words, this layer is responsible for opening and closing communications between two devices. This time taken between the open and closing of communication is called a session. The session layer makes sure that the session remains open long enough to transfer the data that has to be exchanged and eventually closes the session in time to omit any wastage of resources.

The session layer also performs the function to synchronise the exchange of data using checkpoints. For instance, if data of a total of 100 MB is being transferred, the 5th layer could set checkpoints at every 10 megabytes. Now, in a case of disconnect after 69 megabytes of data transfer, with the help of the session layer, data transfer will continue from the last set checkpoint instead of a complete restart.

4. The Transport Layer

The data stored in the transport layer is called ‘segments’. The transport layer breaks data received from the session layer into different segments before sending it to layer 3, i.e the network layer. The Transport layer is primarily responsible for the end-to-end data communication between two devices. For this purpose, the transport layer reassembles the segments into data that is consumable by the session layer.

Apart from segmentation and reassembling of data, the transport layer also performs functions to control the flow and error of the data being communicated. The flow control function determines an ideal speed for the flow of data so that a high-speed sender does not overwhelm the functioning of a receiver with a comparatively slower speed.

The error control function of the 4th layer is to see that the data being received by the transport layer is correct and complete and request retransmission if it isn’t.

3. The Network Layer

The Network layer facilitates the data transfer between two networks. Although, this layer is deemed unnecessary in a scenario where two devices are communicating on the same network. The Network Layer works by breaking down the segments provided by the transport layer into smaller units called packets, on the sender’s device, and eventually reassembling these packets on the receiving device.

The Network Layer also takes care of packet routing, i.e finding the best physical path for the data to reach its destination. The Network layer is implemented by networking devices such as routers.

2. The Data Link Layer

The data link layer is similar to the network layer, the difference being that this layer facilitates the transmission of data over the SAME network. The data link layer makes and concludes a connection between two physically-connected nodes on a network. The data link layer receives packets from the network layer and breaks them down into smaller pieces called frames. 

This layer is made up of two different sublayers– Logical Link Control (LLC), which identifies network protocols, performs error checking and synchronizes frames, and Media Access Control (MAC) which makes use of MAC addresses to connect devices and define permissions to send and receive data.

1. The Physical Layer

As the name suggests, The physical layer consists of the physical equipment required for the data transfer and is responsible for the physical cable or wireless connection between network nodes. This layer is present at the bottom of the OSI Model and includes physical equipment such as cables, wires and switches. 

The data at this layer gets converted into a bit stream, which is a string of 0s and 1s. The physical layer of both devices in consideration must also be available on a signal convention so that the 1s can be differentiated from the 0s on both ends. When a networking error takes place, many networking experts go right to the physical layer to check that all of the cables are properly connected and that the power plug hasn’t been pulled from the router, switch or computer, for example.

Advantages of The OSI Model

The OSI Model helps users and computer networks operators:

  • Asses and select the required hardware and software to build a network.
  • Get understanding of the functioning and communication between components across a network.
  • Troubleshoot any errors by identifying the exact layer having issues and focusing efforts there.

The OSI model helps network device manufacturers:

  • Make devices that are compatible to communicate with products from different vendors across the industry.
  • Aware of the parts of the network that their device needs to function with.
  • Make users aware of which layer their products work at, for example, only at the application layer or across the stack.

OSI vs. TCP/IP Model

The TCP/IP Model short for Transfer Control Protocol/Internet Protocol was created before the OSI Model by the US Department of Defense (DoD). The major difference between both the models is that the TCP/IP Model is simpler, combining several OSI layers into one.

The following illustration defines how the TCP/IP Model has  collapsed different layers of the OSI Model into one:

Wrapping Up

To conclude what you have read, it is safe to say that the OSI Model has created leaps in the networking domain by aiding both manufacturer’s and user’s end. Users are now more aware about the solutions they need to carry forward and at which particular layer. On the other hand manufacturers can now define what products they need to make to cater the demand of the market. Although its former counterpart the TCP/IP Model was simpler, with the emergence of the OSI Model the concept of layers in computer networking has become much more defined. 

Top 200+ CCNA Networking Fundamentals Questions?

learn ccna
  1. What is Networking?
  2. Compare and contrast OSI and TCP/IP models
  3. Compare and contrast TCP and UDP protocols
  4. Describe the impact of infrastructure components in an enterprise network
  5. What are Firewalls?
  6. What is an Access point?
  7. What are Wireless controllers?
  8. Describe the effects of cloud resources on enterprise network architecture
  9. Traffic path to internal and external cloud services
  10. Virtual services
  11. Basic virtual network infrastructure
  12. Compare and contrast collapsed core and three-tier architectures
  13. Compare and contrast network topologies
  14. What are Star network topologies?
  15. What are Mesh network topologies?
  16. What are Hybrid network topologies?
  17. Select the appropriate cabling type based on implementation requirements
  18. Apply troubleshooting methodologies to resolve problems
  19. Perform and document fault isolation
  20. Resolve or escalate
  21. Verify and monitor resolution
  22. Configure, verify, and troubleshoot IPv4 addressing and subnetting
  23. Compare and contrast IPv4 address types
  24. What is Unicast
  25. What is Broadcast
  26. What is Multicast
  27. Describe the need for private IPv4 addressing
  28. Identify the appropriate IPv6 addressing scheme to satisfy addressing requirements in a LAN/WAN environment
  29. Configure, verify, and troubleshoot IPv6 addressing
  30. Configure and verify IPv6 Stateless Address Auto Configuration
  31. Compare and contrast IPv6 address types
  32. Global unicast
  33. Unique local
  34. Link local
  35. Multicast
  36. Modified EUI 64
  37. Autoconfiguration
  38. Anycast
  39. LAN Switching Technologies
  40. Describe and verify switching concepts
  41. MAC learning and aging
  42. Frame switching
  43. Frame flooding
  44. MAC address table
  45. Interpret Ethernet frame format
  46. Troubleshoot interface and cable issues (collisions, errors, duplex, speed)
  47. Configure, verify, and troubleshoot VLANs (normal/extended range) spanning multiple switches
  48. Access ports (data and voice)
  49. Default VLAN
  50. Configure, verify, and troubleshoot interswitch connectivity
  51. Trunk ports
  52. Add and remove VLANs on a trunk
  53. DTP, VTP (v1&v2), and 802.1Q
  54. Native VLAN
  55. Configure, verify, and troubleshoot STP protocols
  56. STP mode (PVST+ and RPVST+)
  57. STP root bridge selection
  58. Configure, verify and troubleshoot STP related optional features
  59. PortFast
  60. BPDU guard
  61. Configure and verify Layer 2 protocols
  62. Cisco Discovery Protocol
  63. LLDP
  64. Configure, verify, and troubleshoot (Layer 2/Layer 3) EtherChannel
  65. Static
  66. PAGP
  67. LACP
  68. Describe the benefits of switch stacking and chassis aggregation
  69. Routing Technologies
  70. Describe the routing concepts
  71. Packet handling along the path through a network
  72. Forwarding decision based on route lookup
  73. Frame rewrite
  74. Interpret the components of a routing table
  75. Prefix
  76. Network mask
  77. Next hop
  78. Routing protocol code
  79. Administrative distance
  80. Metric
  81. Gateway of last resort
  82. Describe how a routing table is populated by different routing information sources
  83. Admin distance
  84. Configure, verify, and troubleshoot inter-VLAN routing
  85. Router on a stick
  86. SVI
  87. Compare and contrast static routing and dynamic routing
  88. Compare and contrast distance vector and link state routing protocols
  89. Compare and contrast interior and exterior routing protocols
  90. Configure, verify, and troubleshoot IPv4 and IPv6 static routing
  91. What is contrast static routing?
  92. What is dynamic routing?
  93. What is contrast distance vector?
  94. Default route
  95. Network route
  96. Host route
  97. Floating static
  98. Configure, verify, and troubleshoot single area and multi-area OSPFv2 for IPv4 (excluding authentication, filtering, manual summarization, redistribution, stub, virtual-link, and LSAs)
  99. Configure, verify, and troubleshoot single area and multi-area OSPFv3 for IPv6 (excluding authentication, filtering, manual summarization, redistribution, stub, virtual-link, and LSAs)
  100. Configure, verify, and troubleshoot EIGRP for IPv4 (excluding authentication, filtering, manual summarization, redistribution, stub)
  101. Configure, verify, and troubleshoot EIGRP for IPv6 (excluding authentication, filtering, manual summarization, redistribution, stub)
  102. Configure, verify, and troubleshoot RIPv2 for IPv4 (excluding authentication, filtering, manual summarization, redistribution)
  103. Full Form of PPP and MLPPP
  104. Troubleshoot basic Layer 3 end-to-end connectivity issues
  105. WAN Technologies
  106. Configure and verify PPP and MLPPP on WAN interfaces using local authentication
  107. Configure, verify, and troubleshoot PPPoE client-side interfaces using local authentication
  108. Configure, verify, and troubleshoot GRE tunnel connectivity
  109. Describe WAN topology options
  110. Point-to-point
  111. Hub and spoke
  112. Full mesh
  113. Single vs dual-homed
  114. Describe WAN access connectivity options
  115. MPLS
  116. Metro Ethernet
  117. Broadband PPPoE
  118. Internet VPN (DMVPN, site-to-site VPN, client VPN)
  119. Configure and verify single-homed branch connectivity using eBGP IPv4 (limited to peering and route advertisement using Network command only)
  120. Describe basic QoS concepts
  121. Marking
  122. Device trust
  123. Prioritization and explain Voice, Video, Data, Shaping, Policing and Congestion management
  124. Infrastructure Services
  125. Describe DNS lookup operation
  126. What is Prioritization Voice?
  127. What is Prioritization Video?
  128. What is Prioritization Data?
  129. What is Prioritization Shaping?
  130. What is Prioritization Policing?
  131. What is Prioritization Congestion?
  132. Troubleshoot client connectivity issues involving DNS 
  133. Configure and verify DHCP on a router (excluding static reservations)
  134. Server
  135. Relay
  136. Client
  137. TFTP, DNS, and gateway options
  138. Troubleshoot client- and router-based DHCP connectivity issues
  139. Configure, verify, and troubleshoot basic HSRP
  140. Priority
  141. Preemption
  142. Version
  143. Configure, verify, and troubleshoot inside source NAT
  144. Static
  145. Pool
  146. PAT
  147. Configure and verify NTP operating in a client/server mode
  148. Infrastructure Security
  149. Configure, verify, and troubleshoot port security
  150. Static
  151. Dynamic
  152. Sticky
  153. Max MAC addresses
  154. Violation actions
  155. Errdisable recovery
  156. Describe common access layer threat mitigation techniques
  157. 802.1x
  158. DHCP snooping
  159. Nondefault native VLAN
  160. Configure, verify, and troubleshoot IPv4 and IPv6 access list for traffic filtering
  161. Standard
  162. Extended
  163. Named
  164. Verify ACLs using the APIC-EM Path Trace ACL analysis tool
    Configure, verify, and troubleshoot basic device hardening
  165. Local authentication
  166. Secure password
  167. Access to device
  168. Source address
  169. Telnet/SSH
  170. Login banner
  171. Describe device security using AAA with TACACS+ and RADIUS
    Static
  172. Pool
  173. PAT
  174. Configure and verify NTP operating in a client/server mode
  175. Infrastructure Management
  176. Configure and verify device-monitoring protocols
  177. SNMPv2
  178. SNMPv3
  179. Syslog
  180. Troubleshoot network connectivity issues using ICMP echo-based IP SLA
  181. Configure and verify device management
  182. Backup and restore device configuration
  183. Using Cisco Discovery Protocol or LLDP for device discovery
  184. Licensing
  185. Logging
  186. Timezone
  187. Loopback
  188. Configure and verify initial device configuration
  189. Perform device maintenance
  190. Cisco IOS upgrades and recovery (SCP, FTP, TFTP, and MD5 verify)
  191. Password recovery and configuration register
  192. File system management
  193. Use Cisco IOS tools to troubleshoot and resolve problems
  194. Ping and traceroute with extended option
  195. Terminal monitor
  196. Log events
  197. Local SPAN
  198. Describe network programmability in enterprise network architecture
  199. Function of a controller
  200. Separation of control plane and data plane
  201. Northbound and southbound APIs