next we're gonna talk about are different types of apologies on are typically going to be seen on our land network. Now, when we're talking about are different apologies. We're essentially talking aboutthe way that our computers are interconnected and what they look like and how they send and receive data throughout throughout our network.
So let's take a look at what that means.
Now, keep in mind that we have what we may refer to as our physical topology versus our logical department apology. Now, Ah, physical topology versus our logical topology means that if we are physically looking at the way this network is connected, this is what we would guess it. It looks like,
for example, if we have a hub
Anak Chua ll hub connected to multiple computers, we may look at it and say, Oh, this looks like a start apology. Because if we have a, we have a device in the centre that is connect that X as a token ring device and we connect them multiple computers to one single device. We may say, Oh, this looks like a
it's a star, A star network because it's multiple computers connected to one single device. But if that device is actually acting in a token ring capacity in passing along to each computer who's allowed to talk, then it's actually a logical token ring topology,
and we'll talk about the star versus the token ranked apology and a little bit.
But But that being said, just keep in mind that just because a certain network looks like something
doesn't mean it actually logically functions that way. When you're drawing a pure, networked apology, you don't you don't necessarily want to draw it up just like how it looks physically. You want to draw it up. How the data passes logically between all the other devices. If there is a switch and that switch
connects all the different devices, connect all your different devices and then transmits passes the data and science ports to Mac addresses, then it would be a like a start apology. But we'll get into our individual apologies one at a time, and our first apology that we're gonna talk about is our messed apology
Now are in our messed apology. We have notes that are connected to one or more Notes
are more than one notes
and this may be seen in a fully meshed versus a partial meshed apology.
So we have over here the beginnings of our network. So how would we connect these intermeshed apology? Well, if these were connected in our messed apology,
we would have computers that are connected
So more than one node.
Now, what we have here is we have a fully meshed
t'pol. It are fully meshed meshed apology. Which means that every computer is connected
toe every other computer.
That's a full mashed apology.
In addition to our full mashed apology, we can also have a partial mashed apology,
which would be like our red here. In our partial meshed apology,
we still have computers that are connected to multiple other computers.
But not every computer is connected to every other computer.
So, for example, in this partial meshed apology, we have some computers that are connected to multiple other computers. But we only have one computer here that's connected to our computer computer. Be down here.
So this would be a partial mashed apology. So keep that in mind. A full mesh in a full mashed apology, every node is connected to every other node
not through any other nodes. It's directly connected to every other node
and then a partial messed apology. We have connections that have at least more than one connection to other devices. But not every device is necessarily connected to every other note that be a partial match. Topology.
So what are some of the benefits of our meshed apology? Well, with our messed apology, we have Maur traffic room. We have Maur area where we can pass data.
So if we have device a here
trying to pass data on down to device
e. So if we have computer a year trying to pass data over to computer see, it's going to pass data over its direct connection and then at the same time computer be could be talking to Computer E without any use of this links. Resource is so they're using two completely separate links.
They have full control over those links, and they can directly talk to each other
without having toe wait their turn while these other computers talk. So we have more room for traffic, so we may have typically have faster connections. We also have Maur redundancy,
so if for any reason this connection between Computer, e and Computer be
or even both of these connections say we had a Ah, we had an outage in. Both of these connections were destroyed.
All of our computers can still talk. Now they have to talk through other nodes. Computer A would have to go through our no day would have to go through node be to go to no snowed see. But they're still connected even though we had two links that were completely destroyed, All of our nodes are still connected, and they are still functional.
We may notice a decrease in our traffic rate,
but we have that additional redundancy for a network. So if redundancy and up time are very, very big components in your network, you may want to consider a, uh, at least a partially meshed or a full meshed apology, because the more connections you have between your device is the better redundancy you'll have. If some of those links go down,
you'll have other devices
and other paths that your data can go through
now. Now, to our bad of our messed apology.
Now, with our messed apology, we have high set up costs. If every device is connected to every other device, we're going to be pulling cables all over the place. There's gonna be a lot more connections going on. The more connections that we have. Two other devices, the more costs were going to ring up because we're gonna happen because these are actual costs of physical links.
Another bats is going to be difficult maintenance. Say we do have a line that goes down between A and C and E and B say our connections did go down Well, now our data is still getting to all of our nodes.
But are you off our end? Users are in points were noticing a lot of ah lot of decreased traffic speed.
It's taking a lot longer for from trap for traffic to get from computer a computer, see? And we may not. It may take us a lot longer to figure out why we may say OK, well, it was working fine this morning, and then we have to do some troubleshooting steps on Lee to eventually find out
that Oh, it was someone was moving a chair and they unplugged. They unplugged a certain switch or they unplugged a certain hub.
So we need to be aware that it's going to be higher. Maur difficult maintenance because there's so much redundancy going on. There's so much meshing going on, and we're trying to make sure that we're maintaining all of these different links. That is gonna be more maintenance Now, you may say, Well, it's redundant, there's redundancy. So even if one link goes down, I can just let it stay down
while I'm fixing the rest of my network
or I'm just I'm just letting it the day to run through the rest of my network. You don't really want to do that. We don't wanna have a network where we say, Oh, we have a mess to Paula Full mashed apology but, uh, links between this, this switch and this server that that goes down sometimes
and this link to this link, it's
it's sort of on and off, and this one's completely cut because someone someone cut this cable by accident. You don't want that in your network. You always want to be making sure that your network is up and running as it should be as it's set up in your apology. If you don't have the if you don't have the maintenance team, if you don't have the resource is available to have that
that full matched apology,
you may want to consider a different type of apology.
But again, our mesh network is great for having a apology. With
a lot of traffic speed,
it gives us increased redundancy between our different nodes
and, as always, the Mawr connections to other devices we have the better with our full with our messed apology.