Welcome, everyone. Now for trunking trunking. Well, alright, you could extend your one to one VLANs by using a physical cabling, but it's not feasible as well as learning the CCNA. You will use layer three devices creating virtual interfaces, blah, blah, blah. Okay, so now they're talking about trunking ports. Okay?

If you when you create a trunk, okay, because it says here, extending your VLANs you need a layer three, because if you have VLAN 20 over here and VLAN 21 over here, they're not gonna talk to each other. It was just through layer two. Now, you need it to go across layer three device normally as a router or layer three switch. Well, what is it that you have to do? Ah, you have to trunk your ports. You have to trunk your ports.

Now it's going to get into ISIL, which is proprietary to Cisco, and it'll talk We can all play without one. Right? All vendors, I don't use the one we use. Okay, I saw we don't use even though there's three switches in the new Packet Tracer. And even in Europe in new iOS, it's there. I mean for backward compatibility with some older equipment, what have you, but ISIL is not what we want to use, we want to use it'll to one two.

So what is it that you do and again, it's gonna be a lab for this you're going to see it I mean, if you think if you took the CCNA there's a reason why you're going for the ccmp I switch. So that means you pass the CCNA you pass the CCNP route nine going to CCNP switch. Okay, so you should know this already. If you don't, is a good reminder. You know, you need to create a trunk you create our VLANs we assigned our VLANs Okay, and we need to trunk the ports which ports do e trunk, we turn the ports to internetworking devices and especially on that Top switch, or the switch that's connected to the router, that port must also be trunk with the same type of encapsulation. Now, when you go to your router, you're not going to get a router and put 20 million different interfaces in there.

No, you're going to go ahead and create sub interfaces, you turn on the physical interface. And then you create the sub interface for the encapsulation, the same encapsulation that you're using able to on cue. And then you put the IP address, which is really your default gateway for that particular VLAN. And that's it all barrel barrel or barrel and do what you got to do. And again, we'll be allowed for this and you'll see this again. All right, and she's no big deal.

Alright, so yeah, as you know, layer three in order to extend VLANs. Now the 8021 Q. And those was interesting because now I was getting a little bit more into the nitty gritty of it, and suddenly comes out each frame with an ID header and trailer h1 Q and embeds Italian information within the layer to frame something they may ask. Okay, in the test, they may ask you in the test it on cue, does it encapsulate each frame or does it embed it tagging information? Now something to that effect. So this is called single tagging or internal tagging.

I know you want to sound smart and the IT department, you want to tell them that well, that's really internal tagging, whatever. for test purposes, that's all you need to know. Also, I just want to introduce the concept of the native VLAN. This frame is within the VLANs are not tagged at all. Exactly. Remember when I said that the native VLAN the special native VLAN does not get tagged.

It has a special period, remember? Okay, so when he's going across whatever trunk ports, he can go, it can go anywhere? No, no, no, you're not. I mean, I go right ahead. I don't need to put you where you need to go. But the other VLANs you must tag them.

They must have frame tagging because they were going You're going this way, okay, but not the native VLAN. Now the native VLAN. Now, if I am bringing it up, they get this granular I doubt it. All right, the first two bytes are used as a tag protocol identifier. This is the value your x at 100 if you're monitoring it, now you know what it is three bytes are used for tag control information, and the last 12 bytes or their VLAN ID or V. This last bullet point, if you want to look at it a little bit more deeply look at it, just look at it, see if it sticks. Okay?

They may ask a question maybe about the number. But other than that, I don't think it's gonna it's gonna happen, okay, but just know, just know that you know, as is when talking about it now, because there's issues when you start tagging it with ASL or it'll join you. Alright, because I saw ads three bytes, and no two on cue adds four bytes to the actual frame, which is now going to exceed 1518. Okay, 1518, which is not good. Good because then you start getting errors. And it says right here, okay?

Can I tell you to make all these dinner frames to exceed their size called baby giant frames, and then report them as Ethernet errors or oversized frames. And it's just because they went overboard, but it'll go on to Haha, complies with the IEEE 8023, a C standard, which actually makes the frame bigger, it extends the frame to 1522. So we don't have that issue. We don't have that issue. So definitely, no two on cue, everybody can participate in it. So that's the way you want to go.

Again, there's going to be a lot but remember, if you're going to extend the whole purpose, if you're going to extend your VLANs, you're going to extend your VLANs. Okay, you need a layer three device, meaning sub interfaces, meaning the same type of encapsulation, and then the IP address. You've done this a million times for the CCNA there should be no issue. When it comes to this. They asked you about All those VLAN creates any issue tagging those encapsulation, or trunking, or port creating issues. Yeah, it creates a bigger frame.

So well, well with ISIL. You gotta have some external piece of hardware that's going to look at it where it's built in, in the 8021 Q. Okay. No said pretty simple. See you in the next one.