Trunking - Video By Sikandar Shaik || Dual CCIE (RS/SP) # 35012

[Music] so the next concept to the VLANs we'll discuss the concept of truncated now here in this in this section concept of chunking we are going to deal with the same content of violence but what if I have some VLANs users of VLAN 10 connecting on switch 1 in some of the VLANs of 10 connecting on the others which we are going to see how the how exactly the traffic is flowed between the same VLAN users on different features so that is that's where your concept of chunking comes the picture now before we we actually discussed about the complex ranking concepts first we'll try to understand why there is a need for chunking or what exactly very quiet to do here but first single three a single wheel and can span over multiple features now a single wheel and can span over multiple features means there is a possibility that in your production networks you have some users of IT department may be sitting on the on the ground or maybe on a Fusco here and there are some things of IT department may be some users on the second floor and there is a possibility that there are some some users of the IT department on the first way now connecting everyone to the same switch physically it's not possible right so let me let me show you a little bit in a diagram bit just like an example this is my building and I have some multiple flows in that and there are some users of IT department some devices there are some users sitting in the ground pool or there they are doing the work in the grant row and there are some users on the next source and there are some users on this floor and there are some users on this place now as they are geographically somewhat far from each other connecting them to the same switch is not possible but if you want to do that then in yes I need to bring some cabling here and then cabling from the top floor and their cabling from here and then some extra cabling required from this line so which means kind of physically connecting everyone to the same switch it's going to require some extra cooling so instead what we do is we go with a solution ways we connect these users to the nearest possible pitch and then these users head to the nearest possible switch in the same flow and then all the users of this will be connecting to the nearest possible fish generally and then the users on the ground sauce will be connecting to the nearest possible pitches and then we can extend the land by connecting a cost cable between fish to switch now this is something what you will find in the production networks and this is these domains we connect because it's not really possible for everyone to connect on the things which if they're in the same building that may be possible but if you if you just assume that there's one more building and there are some users of ID present here and connecting everyone to the same is not possible so there's something what we do and it's something we should not do it so now what I mean to say here is a single VLAN can span over multiple switches means there is a possibility that the users of the same VLAN symbol and in same departments might be on different features then they might be on different different system like some users of IT correcting on this particular feature some users of ID connecting on the switch now we want to understand how the communication process happens in this scenario we are saying that same VLAN same door tells domain and they can communicate with each other but if they are on different switches how the communication process happens now in order to forward the traffic of the same VLAN user from one $1,000,000.00 wheel and there is one solution we can use we can pass a traffic using a software link for each and every beam us that is one possible solution we can think about where you can have some bean and one user if you want to defend the traffic from VLAN 1 as there are different cities we can have a separate link for VLAN 1 1 separately for VLAN 1 and 1 software link for belong to and then once operating for B lambda if it is operating for balancing so which means between fish to switch we can have one subject we Lansford each and every user each and every beam and but this is not a scalable solution because let's take an example I got 20 VLANs will go with 20 links between the switches this is something not possible so we don't use this scenario so parting the VLANs are using separate links for each and every VLAN is something not scalable not really applicable in the production network instead what we do now what we can do is we can use only one common link which can carry all the VLAN traffic which means we can we can ensure that the VLAN 1 traffic will end to traffic VLAN three traffic they all can go on the same link without interfering with each other that is possible so that's what we are going to see how it is possible how it is going to Ehlo the multiple VLAN traffic on the same link without interfering with each other without conflicting each other so to understand that process so before we get into the actual process that is what same tagging let's try to understand there are two different types of links we have here the first link we have something about access links access link or the links which are connecting to the N divided these are all access links so they they belong to just one VLAN by default they belong to VLAN 1 but we can shift them into VLAN 10 or VLAN 20 or VLAN 30 as per your requirement but at the end the pores which are connecting to the end devices we call them and access links and they just belong to only one winner but the link which is cutting between crystal switch and this particular link it does not belong to any peeler so which means it's not a member of any VLAN but it's going to carry multiple banana traffic so multiple and traffic means here if you if you just take an example here I got three different VLANs you can see the names here are given some names as the radius there's any one user of the wheel and red want to communicate with with the user or the we landed on a different page it should go from the same link and that link we call it as funk link which means it is carrying the B lambda traffic and also it is kind of VLAN boot blue traffic you can see the user of the VLAN blue want to communicate this with a blue blue VLAN user on the difference which he should be going on the same link and also there is one more pale and green VLAN can see here if the green beeline user want to talk Greenville on user it will be going on the same link so just like here even though they are going on the same link still I am going to differentiate right so even though they are going on the same link but now the question is how the switch is going to differentiate each and every VLANs okay so the tunneling is running which carries multiple VLAN traffic but now the question is how it is going to identify like here I'm using different colors for identification but in case of switches there is a method called frame tagging happens now this frame tagging is a method which will ensure that even though they are going on the same link till they will be differentiated without interfering with each other without without having an issues so let's see what is this train tagging happen and so in order to make sure that the same VLAN users on two different pictures to talk to each other like here you can see the blue wheel and VLAN one should communicate with VLAN one on a difference which they will be going on the same links but there is a color differentiation here the belong to communicating this belong to on a different page they will be going on the same link here and the VLAN belong three that is the green wheel and communicating with the Greenville on our difference which they are going on the same link now what exactly features will do is when when the particular frame is saying like in this scenario the second example be line one is sending a frame before it sends on the trunk link you put it send it is going to add the frame with some tag information so we call this earth frames I can process now this type is actually containing something called VLAN ID now in that particular tag it is going to add the VLAN number and it is going to send over the short link now here for easy understanding we got different colors but the frame is sent with the act and in that tag tag is like extra header information added or inside your frame or the package now why this doing that because the switch one knows exactly from where it is coming it's coming from VLAN one but the switch to do not know exactly which we landed below because all looks same they all are friends now there should be some differentiation to inform the remote side of the switch that is switched now it will be sent with the tags now the switch to will receive the frame is a tag and it will see the tag information it realizes that it belongs to B line one okay and it will remove the tags and it is going to send back to the switch one as a normal frame if you just try to observe here when when the switch is sending it is sending as a normal frame or even the PC is sending and when the fit is receiving it is not a normal train and mate is sending on this side it is just as a normal frame so it is just that frame to frame but when when the particular which is sending on the front link it is going to add the tag here which means when it is sending it is going to add the tag on that parting of frame and once it's refused on the other side it is going to see the tag and it's going to remove that particular tag because once it sees the that it comes to know that this frame belongs to real and one so the fish too will ensure that it is going to send only to the VLAN 1 and it will not send to any other alight now this frame timing is a method way which is going to ensure that even though there are multiple VLANs optic going on the same link but still each and every frame is differentiated and identified on the remote switches and this will ensure that even though they are going on the same link till the VLAN traffic is differentiated they become a part of the software broadcast domain now this is what frame tiny method and this frame tiny methods one happens only on the front links and when it is sending anything it is going to add the tag once is refused anything it will simply remove the tag by seeing after seeing that particular VLAN information in that now sub same thing is mandatory and it is a default process which happens on the trunk links [Music]

Channel: Sikandar Shaik

Views: 77,369

Keywords: ccna, ccna videos, trunking, ccna trunking, noa, noa videos, ccnp, cisco, ccie, subnetting, ccna security, bgp, ospf, firewall, ccna subnetting, ipv6, bgp videos, stp, ccna vdieos, ccna free video, ccie certification, ios, iou, virtual, eigrp, cisco virtual lab, iosv, asav, gns3, routing, noa vdieos, noa solutions, zone based firewall, zone pair, zbf, flsm, cisco firewall, cisco security, cisco certifications, wan, ip addressing, netmetric, vlsm, eigrp configuration, vlan, ccnp, cisco

Id: VaUtJOAeXrE

Length: 12min 3sec (723 seconds)

Published: Wed Jan 18 2017