In this section, you're going to be reintroduced to a networking model you first saw in your CCNA studies. No, it's not the OSI model or the TCP/IP model - it's the Cisco Three-Layer Hierarchical Model. Let's face it, just about all you had to do for the CCNA was memorize the three layers and the order they were found in that model, but the stakes are raised here in your CCNP studies. You need to know what each layer does, and what each layer should not be doing. This is vital information for your real-world network career as well, so let's get started with a review of the Cisco three-layer model, and then we'll take a look at each layer's tasks. Most of the considerations at each layer are common sense, but we'll go over them anyway!
Today we’ll take a look at the core layer of the Cisco model.
The term core switches refers to any switches found here. Switches at the core layer allow switches at the distribution layer to communicate, and this is more than a full-time job. It's vital to keep any extra workload off the core switches, and allow them to do what they need to do - switch! The core layer is the backbone of your entire network, so we're interested in high-speed data transfer and very low latency - that's it!
Core layer switches are usually the most powerful in your network, capable of higher throughput than any other switches in the network. Remember, everything we do on a Cisco router or switch has a cost in CPU or memory, so we're going to leave most frame manipulation and filtering to other layers. The exception is Cisco QoS, or Quality of Service. QoS is generally performed at the core layer. We'll go into much more detail regarding QoS in another tutorial, but for now, know that QoS is basically high-speed queuing where special consideration can be given to certain data in certain queues. (You’ll soon find that this is a very basic definition!)
We always want redundancy, but you want a lot of redundancy in your core layer. This is the nerve center of your entire network, so fault tolerance needs to be as high as you can possibly get it. Root bridges should also be located in the core layer.
The importance of keeping unnecessary workload off your core switches cannot be overstated. In the next part of this BCMSN tutorial, we’ll take a look at how the other layers of the Cisco three-part model do just that.
Showing posts with label layer. Show all posts
Showing posts with label layer. Show all posts
Thursday, December 25, 2008
Wednesday, December 24, 2008
Cisco CCNA Certification Exam Tutorial: The OSI Model’s Physical Layer
To pass your CCNA exam and earn this coveted certification, you've got to master the seven layers of the OSI model and what each layer does. For those of you taking the two-exam path, you can expect quite a few OSI model questions on the Intro exam. In this seven-part series, we'll spend some time taking a look at each of the OSI model layers, starting with the Physical layer.
Often, CCNA candidates ask if the OSI model has any practical uses for network administrators. I used to wonder the same thing, and I can now tell you that the answer is definitely yes!
The OSI model isn't something you want to memorize and then forget about, as using the OSI model gives you a structured approach for troubleshooting. Whenever a network device isn't working properly, I always say to "start at the physical layer". The Physical layer is Layer One of the OSI model, and this is where troubleshooting should always start. Is the device on? Is it properly connected? If everything is fine at Layer One, you just move up to Layer Two, and continue in this structured fashion until the problem is identified.
The Physical layer is the layer at which bits are transmitted over the physical media. There is no routing or switching going on at this layer. The data has been broken down into more manageable pieces until the data takes the form of ones and zeroes at the Physical layer.
Even though there's no routing or switching at the Physical layer, CCNA candidates should be familiar with a couple of network devices that work at Layer One. A repeater is a device that regenerates an electrical signal, allowing the signal to travel longer distances without fading. (The process of an electrical signal gradually fading in strength over distance is "attenuation".) A hub is basically a multiport repeater, and both of these devices are considered Physical layer devices. Ethernet and Token Ring both operate at the Physical layer as well.
Learning the OSI model's Physical layer isn't just important in your CCNA exam studies, it's the first step in any network troubleshooting. After all, your network's end users are going to have a tough time sending print jobs to a printer that's turned off!
Often, CCNA candidates ask if the OSI model has any practical uses for network administrators. I used to wonder the same thing, and I can now tell you that the answer is definitely yes!
The OSI model isn't something you want to memorize and then forget about, as using the OSI model gives you a structured approach for troubleshooting. Whenever a network device isn't working properly, I always say to "start at the physical layer". The Physical layer is Layer One of the OSI model, and this is where troubleshooting should always start. Is the device on? Is it properly connected? If everything is fine at Layer One, you just move up to Layer Two, and continue in this structured fashion until the problem is identified.
The Physical layer is the layer at which bits are transmitted over the physical media. There is no routing or switching going on at this layer. The data has been broken down into more manageable pieces until the data takes the form of ones and zeroes at the Physical layer.
Even though there's no routing or switching at the Physical layer, CCNA candidates should be familiar with a couple of network devices that work at Layer One. A repeater is a device that regenerates an electrical signal, allowing the signal to travel longer distances without fading. (The process of an electrical signal gradually fading in strength over distance is "attenuation".) A hub is basically a multiport repeater, and both of these devices are considered Physical layer devices. Ethernet and Token Ring both operate at the Physical layer as well.
Learning the OSI model's Physical layer isn't just important in your CCNA exam studies, it's the first step in any network troubleshooting. After all, your network's end users are going to have a tough time sending print jobs to a printer that's turned off!
Cisco CCNA Certification: Error Detection vs. Error Recovery
Passing the CCNA, Intro, and ICND exam is all about knowing and noticing the details. (Which makes perfect sense, since becoming a master networking administrator or engineer is also about noticing the details!) One such detail knows the difference between error detection and error recovery. While the terms are sometimes used interchangeably, they are not the same thing.
Error detection is just that - error detection only. Two common error detection methods are found at the Data Link layer of the OSI model, the FCS (Frame Check Sequence) and CRC (Cyclical Redundancy Check). A mathematical equation is run against the data in the frame, and the result is sent along with the data. The receiver runs the equation again, but this time. If the result is the same, the frame is considered valid; if the result is different, the frame is considered corrupt and is discarded.
Note that the FCS and CRC do nothing in regards to retransmission. They are strictly error detection schemes.
For an example of error recovery, we look to the Transport layer, where TCP runs. TCP performs reliable delivery, and the reason we call it "reliable" is that TCP uses sequence numbers to detect missing segments. If the sender determines from the sequence numbers that the remote host did not receive transmitted segments, the sender will retransmit the missing segments.
The key to keeping the terms straight in your head is to remember that while both error detection and error recovery both detect problems, only error recovery does anything about it. It's also worth reading an exam question twice when you see either term!
Error detection is just that - error detection only. Two common error detection methods are found at the Data Link layer of the OSI model, the FCS (Frame Check Sequence) and CRC (Cyclical Redundancy Check). A mathematical equation is run against the data in the frame, and the result is sent along with the data. The receiver runs the equation again, but this time. If the result is the same, the frame is considered valid; if the result is different, the frame is considered corrupt and is discarded.
Note that the FCS and CRC do nothing in regards to retransmission. They are strictly error detection schemes.
For an example of error recovery, we look to the Transport layer, where TCP runs. TCP performs reliable delivery, and the reason we call it "reliable" is that TCP uses sequence numbers to detect missing segments. If the sender determines from the sequence numbers that the remote host did not receive transmitted segments, the sender will retransmit the missing segments.
The key to keeping the terms straight in your head is to remember that while both error detection and error recovery both detect problems, only error recovery does anything about it. It's also worth reading an exam question twice when you see either term!
Subscribe to:
Posts (Atom)