Showing posts with label model. Show all posts
Showing posts with label model. Show all posts

Thursday, December 25, 2008

Cisco CCNP / BCMSN Exam Tutorial: The Core Layer Of Cisco's Three-Layer Model

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.

Cisco CCNA Exam Tutorial: Mapping The OSI Model To The TCPIP Model

The OSI model is the model that most networking personnel are familiar with, but to earn your CCNA, you need to know the OSI model, the TCP/IP model, and how the two map to each other.

The four layers of the TCP/IP architecture can be compared to certain levels of the OSI model. It’s important to know what each level of the TCP/IP protocol architecture does, and how these layers map to the OSI model.

The Application Layer of the TCP/IP model performs much the same tasks as the Application, Presentation, and Session layers of the OSI model.

The Transport layer in the TCP/IP architecture is similar to the Transport layer in the OSI model. This layer can use TCP or UDP as well.

The Internetwork layer in the TCP/IP architecture uses IP addresses to determine how packets should be routed. Remember that the OSI model uses IP addresses, or “Layer 3 Addresses”, at the Network layer. The two layers do much the same thing. This layer is also referred to in the TCP/IP model as the Internet layer.

The Network Interface layer in the TCP/IP architecture serves to define the protocols and the hardware needed to actually deliver the data across the network. The Network Interface model does the work of both the Data Link and Physical Layers in the OSI model.

Keeping all this straight can be very confusing when you first start your CCNA studies. Concentrate on the OSI model in your studies, but make sure you know how the TCP/IP model maps to that model and you'll be ready for CCNA exam success!

Wednesday, December 24, 2008

Cisco CCNA Certification Tutorial: Segmenting Your Network

When you're getting started on your CCNA studies on your way to earning this certification, you're swamped with network device types that you're familiar with, but not quite sure how to use. Let's look at these networking devices and their main purposes.

Hubs and repeaters operate at Layer One of the OSI model, and they have one main purpose - regenerating the electrical signal that Layer One technologies carry. This regeneration helps to avoid attenuation, the gradual weakening of a signal. Much like a radio signal, the electric signals that travel at Layer One gradually weaken as they travel across the wire. Hubs and repeaters both generate a "clean" copy of the signal.

While hubs and repeaters can be helpful, they do nothing as far as network segmentation is concerned. The first such device we encounter as we move up the OSI model is the switch. Operating at Layer 2, a switch creates multiple collision domains by default each switch port is considered its own little collision domain. If 12 PCs are connected to a Cisco switch, you have 12 separate collision domains.

Switches can be used to segment the network into smaller broadcast domains, but this is not a default behavior. Virtual LAN (VLAN) configuration segments the network into smaller broadcast domains, since a broadcast sent by a host in one VLAN is heard only by other devices in the same VLAN.

Routers operate at Layer 3 of the OSI model and segment a network into multiple broadcast domains by default. Routers do not forward broadcasts as switches do, making the router the only device of the four we've discussed today that create multiple broadcast domains by default.

Knowing what each of these devices can and cannot do is essential to passing the CCNA and becoming a great network administrator. Good luck to you in both of these goals!

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!

Cisco CCNA Certification: The (Many) Different Kinds Of Switching

When you're studying for your CCNA exam, whether you're taking the Intro-ICND path or the single-exam path, you're quickly introduced to the fact that switching occurs at Layer 2 of the OSI model. No problem there, but then other terms involving switching are thrown in, and some of them can be more than a little confusing. What is "cell switching"? What is "circuit switching"? Most confusing of all, how can you have "packet switching"? Packets are found at Layer 3, but switching occurs at Layer 2. How can packets be switched?

Relax! As you'll see in this article, the terms aren't that hard to keep straight. Packet switching, for example, describes a protocol that divides a message into packets before they're sent. The packets are then sent individually, and may take different paths to the same destination. Once the packets arrive at the final destination, they are reassembled.

Frame switching follows the same process, but at a different layer of the OSI model. When the protocol runs at Layer 2 rather than Layer 3, the process is referred to as frame switching.

Cell switching also does much the same thing, but as the name implies, the device in use is a cell switch. Cell-switched packets are fixed in length. ATM is a popular cell-switching technology.

The process of circuit switching is just a bit different, in that the process of setting up the circuit itself is part of the process. The channel is set up between two parties, data is transmitted, and the channel is then torn down. The circuit-switching technology most familiar to CCNA candidates is ISDN.

Don't let these terms confuse you. The four different terms are describing much the same process. The main difference is that they are occurring at different levels of the OSI model, and using a different transport method to get the data where it needs to go.