now, another term that we need to be familiar with when we're talking about are different. Apologies is our Mpls Now NPLs isn't really a topology, but it's something that allows our apologies to communicate with other networks and other apologies. NPLs stands for multi protocol label switching,
and it's a protocol switching that allows us to
use multiple different layer two protocols over the same connection.
So typically are Mpls is what we're going to use in order to transmit over a backbone and what we use. And we use layer edge router that assigns NPLs 32 bit headers. So if we have our network connected up to, we're gonna have our router
and each of these two computers here going to represent
100 computers. So we have, like, 100 computers in our small sub networks,
and they connect over to our laywer edge router.
Now our laywer ed router, using our NPLs 32 bit headers, can send information over a backbone line.
We could send it over to another layer edge router, and these
layer edge routers using NPLs aren't really aren't restricted, really by asynchronous transfer mode or frame relay or a T one or e one or E three or T three lines. They're not restricted by certain layer two protocols
that we may see if we were trying to run over just asynchronous transfer mode
or just using frame relay. NPLs allows us to its what we consider sort of in between layer two and three. In between. Our data link layer and our I P layer are in between our data link layer and our network layer. It allows us to have a
A non assigned medium A essentially, ah, in between. That doesn't really care what we're using in order to transmit that data
so it doesn't rely on a single single layer to layer to data link protocol. It doesn't require that we we use a particular layer to protocol. We could use whichever whichever suits us best.
Um and we use that layer edge router, and the layer ed router is going to assign a 32 bit NPLs header. And that header is gonna contain all the information about our packet and about the about the protocol that we're using in order to transmit this information so it will go over our backbone infrastructure
and get to our destination and then our destination will be able to read that 32 bit header in orderto understand how to read this packet.
Our NPLs can also provide us with que os quality of service and can also work with our different routing protocols to find the best, the best path to a different a certain location. Now, another thing to understand about NPLs, NPLs can utilize what are called short path labels.
Now our short path labels that we just have tacked up here
not necessarily with our multiple protocols, but our short path labels essentially allow us to connect and route data without using longer without actually using longer address network address. Name our network address I. D. S. We can simply use the short path labels
which are just shorter records which are used in place of our our actual our network addresses that are mapped to those network that our map to a certain destination and we use thes short path labels in our our laywer ed router routing tables. So using the short path labels
rather than having to use a
several of longer number longer I p address per se are longer destination address. We could just use the short path labels in our routing table to make our routing table a bit more compact and let it and making it so that our routing table protocols can work a bit faster
because they have this information and they're able to assign the short path labels.
just keep just understand what Mpls is our multi protocol label switching. Remember, it's a
It's a non discerning in between layer two and Layer three protocol, which we utilize on our laywer edge routers and allows us to transmit data over a backbone, using multiple different protocols using multiple different layer two protocols
not reliant on just a single layer to protocol.
Because we have this 32 bit header that can that can work with multiple different layer two protocols so that we can transmit data essentially whichever way we need to transmit over our backbone.
So thank you for joining us here today on cyber dot i t on this monster. We talked about some of our different network topology types. We talked about things such as our peer to peer versus client server, and we also talked about all of our different network topology types, such as our mesh bus Ring star and hybrid Apologies.
So hopefully understanding these apologies a little bit better and understanding how our networks can logically function in past data around,
we'll help you better in designing not only your own networks but in a and the ability to look at another network and understand what's going on and how data's flowing. And using that knowledge when you're actually troubleshooting in trying to figure out why data is not getting from one point to another. So again,
we thank you for joining us here, and we hope to see you here next time on cyber Dad, I think.