The OSI 7 Layer Model

For the next several weeks we are going to work on one of the critical areas of the MCSE program. It is the OSI 7 Layer Model, a structure generated to separate different parts of networking into different categories and defining the relationships between categories. This is BY FAR the most complex part of the Networking Essentials test, as it pulls together protocol stacks, network types, hardware, software, and every other component of networking into a single view. You can pass the test without fully understanding the OSI model, but you will never fully understand networking without it. What Is The OSI Model? The International Organization for Standardization (ISO) began developing the Open Systems Interconnection (OSI) reference model in 1977. It was created to standardize the rules of networking in order for all systems to be able to communicate. In order for communication to occur on a networking using different device drivers and protocol stacks, the rules for communication must be explicitly defined. The OSI model deals with the following issues; How a device on a network sends it's data, and how it knows when are where to send it How a device on a network receives it's data, and how to know where to look for it. How devices using different languages communicate with each other. How devices on a network are physically connected to each other. How protocols work with devices on a network to arrange data.

The OSI model is broken down into 7 layers. Although the first layer is #1, it is always shown at the bottom of the model. We'll explain why later. For now, remember this little trick; Please Do Not Tell Secret Passwords Anytime. (From A+ Certification For Dummies, IDG 1999) Here are the seven layers. 1. 2. 3. 4. 5. 6. 7. Protocol Stacks In order for each layer of the model to communicate with the levels above and below it, certain rules were developed. These rules are called Protocols, and each protocol provides a specific layer of the model with a specific set of tasks or services. Each layer of the model has it's own set of protocols associated with it. When you have a set of protocols that create a complete OSI model, it is called a Protocol Stack. An example of a protocol stack is TCP/IP, the standard for communication over the internet, or Appletalk for Macintosh computers. As stated before, protocols define how layers communicate with each other. Protocols specifically work with ONLY the layer above and below them. They receive services from the protocol below, and provide services for the protocol above them. This order maintains a standard that is common to ALL forms of networking. In order for two devices on a network to communicate, they must both be using the same protocol stack. Each protocol in a stack on one device must communicate with it's equivalent stack, or peer, on the other device. This allows computers running different operating systems to communicate with each other easily, such as having Macintosh computers on a Windows NT network. Physical Layer Data Link Layer Network Layer Transport Layer Session Layer Presentation Layer Application Layer

Communications Between Stacks When a message is sent from one machine to another, it travels down the protocol stack or layers of the model, and then up the layers of the stack on the other machine. As the data travels down the stack, it picks up headers from each layer (Except the physical layer). Headers contain information that is read by the peer layer on the stack of the other computer. As the data travels up the levels of the peer computer, each header is removed by it's equivalent protocol. These headers contain different information depending on the layer they receive the header from, but tell the peer layer important information, including packet size, frames, and datagrams. Each layer's header and data are called data packages, or service data units. Although it may seem confusing, each layer has a different name for it's service data unit. Here are the common names for service data units at each level of the OSI model Application Presentation Session Transport Network Data Link Physical The Physical Layer The lowest layer on the OSI model, and probably the easiest to understand is the physical layer. This layer deals with the physical, electrical, and cable issues involved with making a network connection. It associates with any part of the network structure that doesn't process information in any way. The physical layer is responsible for sending the bits across the network media. It does not define what a bit is or how it is used merely how it's sent. The physical layer is responsible for transmitting and receiving the data. It defines pin assignments for serial connections, determines data synchronization, and defines the entire network's timing base. Items defined by the physical layer include hubs, simple active hubs, terminators, couplers, cables and cabling, connectors, repeaters, multiplexers, transmitters, receivers, and transceivers. Any item that does not process information but is required for the sending and receiving of data is defined by this layer. There are several items addresses by this layer. They are; Network connections types, including multi-point and point-to-point networks. Network Topologies, including ring, star, bus, and mesh networks. Analog or Digital signaling. Bit Synchronization (When to send data and when to listen for it). Baseband Vs. Broadband transmissions. Multiplexing (Combining multiple streams of data into one channel). Termination, to give better signal clarity and for node segmentation. Messages and Packets Packets Packets Datagrams, Segments, and Packets Datagrams and Packets Frames and Packets Bits and Packets

The Data Link Layer The Data Link Layer is responsible for the flow of data over the network from one device to another. It accepts data from the Network Layer, packages that data into frames, and sends them to the Physical Layer for distribution. In the same way, it receives frames from the physical layer of a receiving computer, and changes them into packets before sending them to the Network Layer.