CCNA exam success depends on mastering the fundamentals, and two important fundamentals are knowing exactly what the terms "collision domain" and "broadcast domain" mean. In this free Cisco tutorial, we'll take a look at the term "collision domain" and how a collision domain is defined.
A collision domain is an area in which a collision can occur. Fair enough, but what "collision" are we talking about here? We're talking about collisions that occur on CSMA/CD segments, or Carrier Sense Multiple Access with Collision Detection. If two hosts on an Ethernet segment transmit data at exactly the same time, the data from the two hosts will collide on the shared segment. CSMA/CD exists to lessen the chances of this happening, but collisions can still occur. To lessen the chances of collisions occurring, we may decide to create multiple, smaller collision domains.
Let's say we have four hosts on a single Ethernet segment. The entire segment is a collision domain; any data sent by one of the hosts can collide with data sent by any of the other hosts. We have one collision domain containing four devices.
To create smaller collision domains, we'll need to introduce some type of networking device into this example. Hubs and repeaters have their place as far as extending the reach of a network segment and cutting down on attenuation, but these OSI Layer One devices do nothing to define collision domains. We could connect each host into a separate port on a hub (a hub is basically a multiport repeater) and we'd still have one single collision domain with four hosts in it.
The most common and most effective way to create multiple collision domains is to use a switch. If we connect each of these four hosts to their own separate switch port, we would now have four separate collision domains, each with one host; each switch port actually acts as a single collision domain, making collisions between these four hosts impossible.
Passing the CCNA is all about knowing the details of how things work, and knowing CSMA/CD theory and how to define collision domains is one of the many details you've got to master. In the next part of this CCNA tutorial, we'll take a look at broadcast domains, and how defining broadcast domains in the right places can dramatically cut down on unnecessary traffic on your network.
Showing posts with label domain. Show all posts
Showing posts with label domain. Show all posts
Thursday, December 25, 2008
Cisco CCNP / BSCI Certification: Introduction To ISIS Terminology
When you're studying to pass the BSCI exam and earn your CCNP certification, you're going to be introduced to ISIS. ISIS and OSPF are both link-state protocols, but ISIS works quite differently from OSPF. You must master these details in order to earn your CCNP.
One of the major differences between OSPF and ISIS will be evident to you when you first begin your BSCI exam studies, and that is the terminology. ISIS uses terms that no other protocol you've studied to date uses, and learning these new terms is the first step to BSCI and CCNP exam success.
First off, what does "IS" stand for in "ISIS"? It stands for "Intermediate System", which sounds like a group of routers. As opposed to Autonomous Systems, which are logical groups of routers, an Intermediate System is simply a single router. That's it.
You'll also become familiar with End Systems, referred to in ISIS as an "ES". The End System is simply an end host.
ISIS and OSPF both use the concept of areas, but ISIS takes a different approach to this concept. ISIS routers use three different types of routing levels, according to the area a router has been placed in. Level 2 routers are connected only to the backbone and serve as a transit device between non-backbone areas. Level 1 routers are totally internal to a non-backbone area.
ISIS uses both Level-1 and Level-2 Hellos, meaning that the two types of routers just mentioned cannot form an adjacency. Luckily for us, there is a middle ground, and that is the Level 1-2 router. These routers connect non-backbone areas to backbone areas. L1-L2 routers keep two separate routing tables, one for L1 routing and another for L2 routing. This is the default setting for a Cisco router, and L1-L2 routers can form adjacencies with both L1 and L2 routers.
Part of the challenge of learning ISIS is getting used to the differences between ISIS and OSPF. Keep studying the terminology, master one concept at a time, and soon you'll be a master of ISIS and a CCNP to boot!
One of the major differences between OSPF and ISIS will be evident to you when you first begin your BSCI exam studies, and that is the terminology. ISIS uses terms that no other protocol you've studied to date uses, and learning these new terms is the first step to BSCI and CCNP exam success.
First off, what does "IS" stand for in "ISIS"? It stands for "Intermediate System", which sounds like a group of routers. As opposed to Autonomous Systems, which are logical groups of routers, an Intermediate System is simply a single router. That's it.
You'll also become familiar with End Systems, referred to in ISIS as an "ES". The End System is simply an end host.
ISIS and OSPF both use the concept of areas, but ISIS takes a different approach to this concept. ISIS routers use three different types of routing levels, according to the area a router has been placed in. Level 2 routers are connected only to the backbone and serve as a transit device between non-backbone areas. Level 1 routers are totally internal to a non-backbone area.
ISIS uses both Level-1 and Level-2 Hellos, meaning that the two types of routers just mentioned cannot form an adjacency. Luckily for us, there is a middle ground, and that is the Level 1-2 router. These routers connect non-backbone areas to backbone areas. L1-L2 routers keep two separate routing tables, one for L1 routing and another for L2 routing. This is the default setting for a Cisco router, and L1-L2 routers can form adjacencies with both L1 and L2 routers.
Part of the challenge of learning ISIS is getting used to the differences between ISIS and OSPF. Keep studying the terminology, master one concept at a time, and soon you'll be a master of ISIS and a CCNP to boot!
Cisco CCNP / BCMSN Exam Tutorial: Static VLANs
BCMSN exam success and earning your CCNP certification requires you to add to your knowledge of VLAN configuration. When you studied for your CCNA exam, you learned how to place ports into a VLAN and what the purpose of VLANs was, but you may not be aware that there are two types of VLAN membership. To pass the BCMSN exam, you must know the details of both types.
In this tutorial, we'll take a look at the VLAN type you are most familiar with, the "static VLAN". As you know, VLANs are a great way to create smaller broadcast domains in your network. Host devices connected to a port belonging to one VLAN will receive broadcasts and multicasts only if they were originated by another host in that same VLAN. The drawback is that without the help of a Layer 3 switch or a router, inter-VLAN communication cannot occur.
The actual configuration of a static VLAN is simple enough. In this example, by placing switch ports 0/1 and 0/2 into VLAN 12, the only broadcasts and multicasts hosts connected to those ports will receive are the ones transmitted by ports in VLAN 12.
SW1(config)#int fast 0/1
SW1(config-if)#switchport mode access
SW1(config-if)#switchport access vlan 12
% Access VLAN does not exist. Creating vlan 12
SW1(config-if)#int fast 0/2
SW1(config-if)#switchport mode access
SW1(config-if)#switchport access vlan 12
One of the many things I love about Cisco switches and routers is that if you have forgotten to do something, the Cisco device is generally going to remind you or in this case actually do it for you. I placed port 0/1 into a VLAN that did not yet exist, so the switch created it for me!
There are two commands needed to place a port into a VLAN. By default, these ports are running in dynamic desirable trunking mode, meaning that the port is actively attempting to form a trunk with a remote switch in order to send traffic between the two switches. The problem is that a trunk port belongs to all VLANs by default, and we want to put this port into a single VLAN only. To do so, we run the switchport mode access command to make the port an access port, and access ports belong to one and only one VLAN. After doing that, we placed the port into VLAN 12 with the switchport access vlan 12 command. Running the switchport mode access command effectively turns trunking off on that port.
The hosts are unaware of VLANs; they simply assume the VLAN membership of the port they're connected to. But that's not quite the case with dynamic VLANs, which we'll examine in the next part of this BCMSN tutorial.
In this tutorial, we'll take a look at the VLAN type you are most familiar with, the "static VLAN". As you know, VLANs are a great way to create smaller broadcast domains in your network. Host devices connected to a port belonging to one VLAN will receive broadcasts and multicasts only if they were originated by another host in that same VLAN. The drawback is that without the help of a Layer 3 switch or a router, inter-VLAN communication cannot occur.
The actual configuration of a static VLAN is simple enough. In this example, by placing switch ports 0/1 and 0/2 into VLAN 12, the only broadcasts and multicasts hosts connected to those ports will receive are the ones transmitted by ports in VLAN 12.
SW1(config)#int fast 0/1
SW1(config-if)#switchport mode access
SW1(config-if)#switchport access vlan 12
% Access VLAN does not exist. Creating vlan 12
SW1(config-if)#int fast 0/2
SW1(config-if)#switchport mode access
SW1(config-if)#switchport access vlan 12
One of the many things I love about Cisco switches and routers is that if you have forgotten to do something, the Cisco device is generally going to remind you or in this case actually do it for you. I placed port 0/1 into a VLAN that did not yet exist, so the switch created it for me!
There are two commands needed to place a port into a VLAN. By default, these ports are running in dynamic desirable trunking mode, meaning that the port is actively attempting to form a trunk with a remote switch in order to send traffic between the two switches. The problem is that a trunk port belongs to all VLANs by default, and we want to put this port into a single VLAN only. To do so, we run the switchport mode access command to make the port an access port, and access ports belong to one and only one VLAN. After doing that, we placed the port into VLAN 12 with the switchport access vlan 12 command. Running the switchport mode access command effectively turns trunking off on that port.
The hosts are unaware of VLANs; they simply assume the VLAN membership of the port they're connected to. But that's not quite the case with dynamic VLANs, which we'll examine in the next part of this BCMSN tutorial.
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!
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: DNS And The IP Name-Server Command
DNS behaviors of a Cisco router are important topics for both the CCNA exam and real-world production networks, and you probably didn't know there were so many DNS details before you began studying for the exam! In this tutorial, we'll look at the ip name-server command and its proper usage.
When a command is mistyped on a Cisco router, the default behavior of the router is to attempt to resolve it via DNS. First, the router looks for an IP Host table on the local router to perform this resolution – that’s what the “translating” word in the output is referring to. If there’s no IP Host table or the IP Host table doesn’t contain an entry for what you typed, the router will send a broadcast in an attempt to resolve this name through a remote DNS server. To prevent this broadcast, enter the global command no ip domain-lookup. Of course, to use DNS to resolve hostnames, ip domain-lookup would have to be reenabled if it’s been turned off.
R2#contin
Translating "contin"...domain server (255.255.255.255)
% Unknown command or computer name, or unable to find computer address
A command is mistyped as “contin”. The Cisco router’s default behavior is to resolve this entry locally via an IP Host table, which isn't present on the router. A broadcast is then sent out to find a DNS server to perform the name resolution. The DNS lookup attempt must time out before the configuration can continue.
R2#conf t
R2(config)#no ip domain-lookup
R2#contin
Translating "contin"
% Unknown command or computer name, or unable to find computer address
With “no ip domain-lookup” configured, the router doesn’t attempt to find a remote DNS server. It sees there is no local resolution configured and almost immediately sends a message to the console that the name can’t be resolved.
R2#conf t
R2(config)#ip domain-lookup
R2(config)#ip name-server 10.1.1.1
R2#contin
Translating "contin"...domain server (10.1.1.1)
A DNS server is installed on the network with the IP address 10.1.1.1. DNS lookup is reenabled with the command ip domain-lookup, and the IP address of the DNS server is specified with the ip name-server command.
It's just that easy to tell a Cisco router exactly where the DNS server is!
When a command is mistyped on a Cisco router, the default behavior of the router is to attempt to resolve it via DNS. First, the router looks for an IP Host table on the local router to perform this resolution – that’s what the “translating” word in the output is referring to. If there’s no IP Host table or the IP Host table doesn’t contain an entry for what you typed, the router will send a broadcast in an attempt to resolve this name through a remote DNS server. To prevent this broadcast, enter the global command no ip domain-lookup. Of course, to use DNS to resolve hostnames, ip domain-lookup would have to be reenabled if it’s been turned off.
R2#contin
Translating "contin"...domain server (255.255.255.255)
% Unknown command or computer name, or unable to find computer address
A command is mistyped as “contin”. The Cisco router’s default behavior is to resolve this entry locally via an IP Host table, which isn't present on the router. A broadcast is then sent out to find a DNS server to perform the name resolution. The DNS lookup attempt must time out before the configuration can continue.
R2#conf t
R2(config)#no ip domain-lookup
R2#contin
Translating "contin"
% Unknown command or computer name, or unable to find computer address
With “no ip domain-lookup” configured, the router doesn’t attempt to find a remote DNS server. It sees there is no local resolution configured and almost immediately sends a message to the console that the name can’t be resolved.
R2#conf t
R2(config)#ip domain-lookup
R2(config)#ip name-server 10.1.1.1
R2#contin
Translating "contin"...domain server (10.1.1.1)
A DNS server is installed on the network with the IP address 10.1.1.1. DNS lookup is reenabled with the command ip domain-lookup, and the IP address of the DNS server is specified with the ip name-server command.
It's just that easy to tell a Cisco router exactly where the DNS server is!
Cisco CCNA Certification: Defining Broadcast Domains
When you're studying to pass the CCNA exam and earn your certification, you're introduced to a great many terms that are either totally new to you or seem familiar, but you're not quite sure what they are. The term "broadcast domain" falls into the latter category for many CCNA candidates.
A broadcast domain is simply the group of end hosts that will receive a broadcast sent out by a given host. For example, if there are ten host devices connected to a switch and one of them sends a broadcast, the other nine devices will receive the broadcast. All of those devices are in the same broadcast domain.
Of course, we probably don't want every device in a network receiving every single broadcast sent out by any other device in the network! This is why we need to know what devices can create multiple, smaller broadcast domains. Doing so allows us to limit the broadcasts traveling around our network - and you might be surprised how much traffic on some networks consists of unnecessary broadcasts.
Using the OSI model, we find devices such as hubs and repeaters at Layer One. This is the Physical layer, and devices at this layer have no effect on broadcast domains.
At Layer Two, we've got switches and bridges. By default, a switch has no effect on broadcast domains; CCNA candidates know that a switch will forward a broadcast out every single port on that switch except the one upon which it was received. However, Cisco switches allow the creation of Virtual Local Area Networks, or VLANs, that are logical segments of the network. A broadcast sent by one host in a VLAN will not be forwarded out every other port on the switch. That broadcast will be forwarded only out ports that are members of the same VLAN as the host device that sent it.
The good news is that broadcast traffic will not be forwarded between VLANs. The bad news is that no inter-VLAN traffic at all is allowed by default! You may actually want this in some cases, but generally you're going to want inter-VLAN traffic. This requires the use of a router or other Layer 3 device such as a Layer 3 Switch. (Layer 3 Switches are becoming more popular every day. Basically, it's a switch that can also run routing protocols. These switches are not tested on the CCNA exam.)
That router we just talked about also defines broadcast domains. Routers do not forward broadcasts, so broadcast domains are defined by routers with no additional configuration.
Knowing how broadcasts travel across your network, and how they can be controlled, is an important part of being a CCNA and of being a superior network administrator. Best of luck to you in both of these pursuits!
A broadcast domain is simply the group of end hosts that will receive a broadcast sent out by a given host. For example, if there are ten host devices connected to a switch and one of them sends a broadcast, the other nine devices will receive the broadcast. All of those devices are in the same broadcast domain.
Of course, we probably don't want every device in a network receiving every single broadcast sent out by any other device in the network! This is why we need to know what devices can create multiple, smaller broadcast domains. Doing so allows us to limit the broadcasts traveling around our network - and you might be surprised how much traffic on some networks consists of unnecessary broadcasts.
Using the OSI model, we find devices such as hubs and repeaters at Layer One. This is the Physical layer, and devices at this layer have no effect on broadcast domains.
At Layer Two, we've got switches and bridges. By default, a switch has no effect on broadcast domains; CCNA candidates know that a switch will forward a broadcast out every single port on that switch except the one upon which it was received. However, Cisco switches allow the creation of Virtual Local Area Networks, or VLANs, that are logical segments of the network. A broadcast sent by one host in a VLAN will not be forwarded out every other port on the switch. That broadcast will be forwarded only out ports that are members of the same VLAN as the host device that sent it.
The good news is that broadcast traffic will not be forwarded between VLANs. The bad news is that no inter-VLAN traffic at all is allowed by default! You may actually want this in some cases, but generally you're going to want inter-VLAN traffic. This requires the use of a router or other Layer 3 device such as a Layer 3 Switch. (Layer 3 Switches are becoming more popular every day. Basically, it's a switch that can also run routing protocols. These switches are not tested on the CCNA exam.)
That router we just talked about also defines broadcast domains. Routers do not forward broadcasts, so broadcast domains are defined by routers with no additional configuration.
Knowing how broadcasts travel across your network, and how they can be controlled, is an important part of being a CCNA and of being a superior network administrator. Best of luck to you in both of these pursuits!
Cisco CCNA Certification: Defining And Creating Collision Domains
When you're studying to pass the CCNA exam and earn your certification, you're introduced to a great many terms that are either totally new to you or seem familiar, but you're not quite sure what they are. The term "collision domain" falls into the latter category for many CCNA candidates.
What exactly is "colliding" in the first place, and why do we care? It's the data that is being sent out onto an Ethernet segment that we're concerned with here. Ethernet uses Carrier Sense Multiple Access / Collision Detection (CSMA/CD) to avoid collisions in the first place. CSMA/CD is a set of rules dictating when hosts on an Ethernet segment can and cannot transmit data. Basically, a host that wants to transmit data will "listen" to the ethernet segment to see if another host is currently transmitting. If no one else is transmitting, the host will go forward with its own transmission.
This is an effective way of avoiding a collision, but it is not foolproof. If two hosts follow this procedure at the exact same time, their transmissions will collide on the Ethernet segment and both transmissions will become unusable. The hosts that sent those two transmissions will then send a jam signal out onto the segment, indicating to all other hosts that they should not send data. The two hosts will each start a random timer, and at the end of that time each host will begin the listening process again.
Now that we know what a collision is, and what CSMA/CD is, we need to be able to define a collision domain. A collision domain is any area where a collision can theoretically take place, so only one device can transmit at a time in a collision domain.
In another free CCNA certification tutorial, we saw that broadcast domains were defined by routers (default) and switches if VLANs have been defined. Hubs and repeaters did nothing to define broadcast domains. Well, they don't do anything here, either. Hubs and repeaters do not define collision domains.
Switches do, however. A Cisco switchport is actually its own unshared collision domain! Therefore, if we have 20 host devices connected to separate switchports, we have 20 collision domains. All 20 devices can transmit simultaneously with no danger of collisions. Compare this to hubs and repeaters - if you have five devices connected to a single hub, you still have one large collision domain, and only one device at a time can transmit.
Mastering the definition and creation of collision domains and broadcast domains is an important step toward earning your CCNA and becoming an effective network administrator. Best of luck to you in both these worthwhile pursuits!
What exactly is "colliding" in the first place, and why do we care? It's the data that is being sent out onto an Ethernet segment that we're concerned with here. Ethernet uses Carrier Sense Multiple Access / Collision Detection (CSMA/CD) to avoid collisions in the first place. CSMA/CD is a set of rules dictating when hosts on an Ethernet segment can and cannot transmit data. Basically, a host that wants to transmit data will "listen" to the ethernet segment to see if another host is currently transmitting. If no one else is transmitting, the host will go forward with its own transmission.
This is an effective way of avoiding a collision, but it is not foolproof. If two hosts follow this procedure at the exact same time, their transmissions will collide on the Ethernet segment and both transmissions will become unusable. The hosts that sent those two transmissions will then send a jam signal out onto the segment, indicating to all other hosts that they should not send data. The two hosts will each start a random timer, and at the end of that time each host will begin the listening process again.
Now that we know what a collision is, and what CSMA/CD is, we need to be able to define a collision domain. A collision domain is any area where a collision can theoretically take place, so only one device can transmit at a time in a collision domain.
In another free CCNA certification tutorial, we saw that broadcast domains were defined by routers (default) and switches if VLANs have been defined. Hubs and repeaters did nothing to define broadcast domains. Well, they don't do anything here, either. Hubs and repeaters do not define collision domains.
Switches do, however. A Cisco switchport is actually its own unshared collision domain! Therefore, if we have 20 host devices connected to separate switchports, we have 20 collision domains. All 20 devices can transmit simultaneously with no danger of collisions. Compare this to hubs and repeaters - if you have five devices connected to a single hub, you still have one large collision domain, and only one device at a time can transmit.
Mastering the definition and creation of collision domains and broadcast domains is an important step toward earning your CCNA and becoming an effective network administrator. Best of luck to you in both these worthwhile pursuits!
Subscribe to:
Posts (Atom)
