What is INTERNETWORKING in Computer Network – CCNA COURSE

0
6
INTERNETWORKING

In this article, we will learn something basics about internetworking in the computer network.

Before we explore internetworking models and the specifications of the OSI reference model, you have got to understand the big picture and learn the answer to the key question, why it is so important to learn Cisco internetworking?

Networks and networking have grown exponentially over the last 15 years understandably so. They have had to evolve at light speed just to keep up with huge increases in basic mission-critical user needs such as sharing data and printers as well as more advanced demands such as video conferencing.

Unless everyone who needs to share network resources is located in the same office are which is an increasingly uncommon situation, the challenge is to connect the sometimes many relevant networks together so all users can share the network’s wealth.

Starting with a look at figure 1.1, you get a picture of a basic LAN network that’s connected together using a hub. This network is actually one collision domain and one broadcast domain but no worries if you have no idea what this means because I’m going to talk about both collision and broadcast domains so much throughout this whole chapter, you will probably even dream about them!

Okay, about figure 1.1… how would you say the PC named yogi communicates with the PC named Ravi? Well, they are both on the same LAN connected with a multiport repeater (a hub). So dies Yogi just send out a data message, “Hey Ravi, you there?” or does Yogi use Ravi’s IP address and put things more like, “Hey 192.168.0.3, are you there?” Hopefully, you picked the IP address option, but even if you did, the news is still bad-both answers wrong! Why? Because Yogi is actually going to use Ravi’s MAC address known as a hardware address, which is burned right into the network card of Ravi’s PC, to get a hold of her.

Great, but how does Yogi get Ravi’s MAC address since Yogi knows only Ravi’s name and doesn’t even have her IP address yet? Yogi is going to start with name resolution (hostname to IP address resolution), something that’s usually accomplished using domain name service (DNS). And of note, if there two are on the same LAN, Yogi can just broadcast to Ravi asking her for the information (no DNS needed) welcome to Microsoft Windows (Vista included)! Here’s an output from a network analyzer depicting a simple name resolution process from Yogi to Ravi:

Time          source          destination            protocol                    info

53.892794     192.168.0.2    192.168.0.255       NBNS Name query          NB Ravi<00>

As I already mentioned, since the two hosts are on a local LAN, windows (Yogi) will just broadcast to resolve the name Ravi (the destination 192.168.0.255 is a broadcast address). Let’s take a look at the rest of the information:

EthenetII,Src:192.168.0.2(00:14:22:be:18:3b).Dst:Broadcast (ff:ff:ff:ff:ff:ff)

What this output shows is that Yogi knows his own MAC address and source IP address but not Ravi’s IP address or MAC address, so Yogi sends a broadcast address of all fs for the MAC address (a Data Link Layer broadcast) and an IP LAN broadcast of 192.168.0.255. Again, don’t freak you are going to learn all about broadcasts. “Subnetting, variable length subnet masks (VLSMs), and troubleshooting TCP/IP.”

Before the name is resolved, the first thing Yogi has to do is broadcast on the LAN to get Ravi’s MAC address so he can communicate to her PC and resolve her name to an IP address.

Time       source        destination          protocol                   info

5.153054    192.168.0.2     Broadcast    ARP Who has 192.168.0.3? Tell 192.168.0.2

Now, check out Ravi’s response:

Time      source        destination                 protocol                               info

5.153403   192.168.0.3    192.168.0.2        ARP        192.168.0.3 is at 00:0b:db:99:d3:5e

 5.53.89317    192.168.0.3     192.168.0.2        NBNS Name query response NB 192.168.0.3

Okay, sweet Yogi now has both Ravi’s IP address and her MAC address. These are both listed as the source address at this point because this information was sent from Ravi back to Yogi. So, finally, Yogi has all the goods he needs to communicate with Ravi. And just so you know, I’m going to tell you all about ARP and show you exactly how Ravi’s IP address was resolved to a MAC address. “IP Routing.”

By the way, I want you to understand that Ravi still had to go through the same resolution processes to communicate back to Yogi Sounds crazy, huh? Consider this a welcome to IPv4 and basic networking with Windows (and we haven’t even added a router yet!).

To complicate things further, it’s also likely that at some point you will have to break up one large network into a bunch of smaller ones because user response will have dwindled to a slow crawl as the network grew and grew. And with all that growth, your LAN’s traffic congestion has reached epic proportions. The answer to this is breaking up a really big network into a number of smaller ones something called network segmentation. You do this by using devices like routers, switches, and bridges. Figure 1.2 displays a network that’s been segmented with a switch so each network segment connected to the switch is now a separate collision domain. But make note of the fact that this network is still one broadcast domain.

Keep in mind that the hub used in figure 1.2 just extended the one collision domain from the switch port. Here’s a list of some of the things that commonly cause LAN traffic congestion:

  • Too many hosts in a broadcast domain
  • Broadcast storms
  • Multicasting
  • Low bandwidth
  • Adding hubs for connectivity to the network
  • A bunch of ARP or IPX traffic (IPX is a Novell protocol that is like IP, but really, really, chatty. Typically not used in today’s networks.)

Take another look at figure 1.2. did you notice that I replaced the main hub from figure 1.1 with a switch? Whether you did or didn’t, the reason I did that is that hubs don’t segment a network; they just connect network segments together. So basically, it’s an inexpensive way to connect a couple of PCs together, which is great for home use and troubleshooting, but that’s about it!

Now routers are used to connect networks together and route packets of data from one network to another. Cisco became the de facto standard of routers because of its high-quality router products, great selection, and fantastic service. Routers, by default, break up a broadcast domain the set of all devices on a network segment that hears all the broadcasts sent on that segment. Figure 1.4 shows a router in our little network that creates an internetwork and breaks up broadcast domains.

Frames, routers (layer 3 switches) use logical addressing and provide what is called packet switching. Routers can also provide packet filtering by using access lists, and when routers connect two or more networks together and use logical addressing (IP or IPv6), this is called an internetwork. Last, routers use a routing table (map of the internetwork) to make path selections and to forward packets to remote networks.

Conversely, switches aren’t used to create internetworks (they do not break up broadcast domains by default); they’re employed to add functionality to a network LAN. The main purpose of a switch is to make a LAN work better to optimize its performance providing more bandwidth for the LAN’s users. And switches don’t forward packets to other networks as routers do. Instead, they only “switch” frames from one port to another within the switched network. Okay, you may be thinking “wait a minute, what are frames and packets?” I’ll tell you all about them later in this chapter, I promise!

By default, switches break up collision domains. This is an Ethernet term used to describe a network scenario wherein one particular device sends a packet on a network segment, forcing every other device on that same segment to pay attention to it. At the same time, a different device tries to transmit, leading to a collision, after which both devices must retransmit, one at a time. Not very efficient! This situation is typically found in a hub environment where each host segment connects to a hub that represents only one collision domain and only one broadcast domain. By contrast, each and every port on a switch represents its own collision domain.

The term bridging was introduced before routers and hubs were implemented, so it’s pretty common to hear people referring to bridges as switches. That’s because bridges and switches basically do the same thing break up collision domains on a LAN (in reality, you cannot buy a physical bridge these days, only LAN switches, but they use bridging technologies, so Cisco still calls them multiport bridges.).

So what this means is that a switch is basically just a multiple-port bridge with more brain-power, right? Well, pretty much, but there are differences. Switches do provide this function, but they do so with greatly enhanced management ability and features. Plus, most of the time, bridges only had 2 or 4 ports. Yes, you could get your hands on a bridge with up to 16 ports, but that’s nothing compared to the hundreds available on some switches!

Figure 1.3 shows how a network would look with all these internetwork devices in place. Remember that the router will not only break up broadcast domains for every LAN interface, but it will also break up collision domains as well.

When you looked at figure 1.3, did you notice that the router is found at center stage and that it connects each physical network together? We have to use this layout because of the older technologies involved bridges and hubs.

On the top internetwork in figure 1.3, you’ll notice that a bridge was used to connect that hub to a router. The bridge breaks up collision domains, but all the hosts connected to both hubs are still crammed into the same broadcast domain. Also, the bridge only created two collision domains, so each device connected to a hub is in the same collision domains as every other device connected to that same hub. This is actually pretty lame, but it’s still better than having one collision domain for all hosts.

Notice something else: the three hubs at the bottom that are connected also connect to the router, creating one collision domain and one broadcast domain. This makes the bridged network look much better indeed!

The network in figure 1.4 is a pretty cool network. Each host is connected to its own collision domain, and the router has created two broadcast domains. And don’t forget that the router provides connections to WAN services as well! The router uses something called a serial interface for WAN connections, specifically, a V3.5 physical interface on a Cisco router.

Breaking up a broadcast domain is important because when a host or server sends a network broadcast, every device on the network must read and process that broadcast unless you’ve got a router. When the router’s interface receives this broadcast, it can respond by basically saying, “Thanks, but no thanks,” and discard the broadcast without forwarding it on to other networks. Even though routers are known for breaking up broadcast domains by default, it’s important to remember that they break up collision domains as well.

There are two advantages of using routers in your network:

  • They don’t forward broadcasts by default.
  • They can filter the network based on layer 3 (network layer) information (e.g. IP address), four router functions in your network can be listed as follows:
    • Packet switching
    • Packet filtering
    • Internetwork communication
    • Path selection

Remember that routers are really switches; they’re actually what we call layer 3 switches (we’ll talk about layers later in future posts). Unlike layer 2 switches, which forward or filter.

The best network connected to the router is the LAN switch network below. Why? Because each port on that switch breaks up the collision domain. But it’s not all good all devices are still in the same broadcast domain. Do you remember why this can be a really bad thing? Because all devices must listen to all broadcasts transmitted, that’s why. And if your broadcast domains are too large, the users have less bandwidth and required to process more broadcasts, and network response time will slow to a level that could cause office riots.

Once we have only switches in our network, things change a lot! Figure 1.5 shows the network that is typically found today.

Okay, here I’ve placed the LAN switches at the center of the network world so the routers are connecting only logical networks together. If I implemented this kind of setup, I’ve created virtual LANs (VLANs), something. “Virtual LANs (VLANs).” So don’t stress. But it is really important to understand that even though you have a switched network, you still need a router to provide your inter-VLAN communication or internetworking. Don’t forget that!

Obviously, the best network is one that’s correctly configured to meet the business requirements of the company it serves. LAN switches with routers, correctly placed in the network, are the best network design. These articles will help you understand the basics of routers and switches so you can make tight, informed decisions on a case-by-case basis.

Let’s go back to figure 1.4 again. Looking at the figure, how many collision domains and broadcast domains are in this internetwork? Hopefully, you answered nine collision domains and three broadcast domains! The broadcast domains are definitely the easiest to see because only routers break up broadcast domains by default. And since there are three connections, that gives you three broadcast domains. But do you see the nine collision domains? Just in case that’s a no, I’ll explain. The all-hub network is one collision domain; the bridge network equals three collision domains. Add in the switch network of five collision domains one for each switch port and you’ve got a total of nine.

Now in figure 1.5, each port on the switch is a separate collision domain and each VLAN is a separate broadcast domain. But you still need a router for routing between VLANs. How many collisions domains do you see here? I’m counting 10. Remember that connections between the switches are considered a collision domain!

So now that you’ve gotten an introduction to internetworking and the switches and the various devices that live in an internetwork, it’s time to know your response for this article.

If you like the article on Internetworking, then you can share it. You can give your useful comments below. We’ll be glad to read those.