6.2.2.5 Lab - Configuring VLANs and Trunking

hi friends welcome to all in this video we are going to see the lab activity configuring villains and trunking before coming to this lab activity firms if you are watching my channel first time or if you have not yet subscribed this channel considered subscribing also enable the bell icon near to the subscribe button so that you will get the notification message when they upload the new new videos here we can see our addressing table also objectives we will go through that in part two one built the network and the configure basic device settings in party to create VLANs and assign suit supports in part three maintain VLAN port assignments and the VLAN database in part for configure an eight node 2.1 q trunk between the switches in plateau 5 delete the VLAN database also we will go through the background modern switches use virtual local area networks that is VLANs to improve network performance by separating large layer to broadcast domains into smaller ones billions can also be used as a security measure by controlling which horse can communicate in general valence make it easier to design a network to support the goals of an organization relent trunks are used to span VLANs across multiple devices trunks allow the traffic from multiple VLANs to travel over a single link while keeping the villain identification and segmentation intact in this lab we will create VLANs on both switches in the topology assemble ins to switch access ports verify that the villains are working as expected and then create a VLAN chunk between the two sutures to allow house in the same villain to communicate through the trunk regardless of which such the house is actually attached to here we can see the regular sources for this a lab activity two sutures Cisco two and six zero then three pcs serving those seven then we record the ethernet cables as showing the topology coming to part one build the network and the configure basic device settings in part one we will set up the network topology and the configure basic settings on the PC host and switches step 1 cable the network as shown in the topology attaches devices are shown in the topology diagram and the cable as necessary also in step 2 initialize and reload the switches as necessary we will build and connect this topology on this a cisco packet tracer tune and six.hoorah switchers then the PCs and now we are going to connect to these devices copper a straight-through 4 2003 rosin r6 to this a PC first return 0 / 11 to this PC first apparent 0 / 18 to this PC copper crossover fastethernet 0/1 to First Lutheran 0 / 1 right people or rename these devices this is CS 1 sure we have s 2 this is TC - a DC - B and we have PC - see also we will label these support details this is a F 0 / 1 this is also of slaw / 1 these protists are faster thorn 0 / 18 this port is the first eternity surah / 11 then T sport is the first appearance Rosner 6 now we will highlight the villains different colors turn leaves at our colors for this turn sure also right you cannot just all these you're the link between a s1 and the years - should be trunk pure is a villain 20 name is a faculty this is civilian ten name is student we can see the same VLAN here also so this labeling will help us to do the configuration without making any errors all right now we will come to step three configure basic settings for each switch consoling to the switch and the entire global configuration mode copy the following basic configuration and de paste it to the running configuration on the switch here we can see that we will copy these commands and we will keep it on a notepad coming two years one CLI enable configure terminal here we are going to paste those commands coming two years to CLI configure terminal and here is that those commands coming to see configure the hostname as shown in the topology coming two years one hostname yes one coming - yes - you'll set the hostname as s - coming to D configure the IP address listed in the addressing table for VLAN 1 on the switch coming to our addressing table here we can see a device s1 and tears - with its IP address also we can see the subject to mask here we will copy this is one IP address coming to s1 we have to go to the interface vlan1 and here we are going to set the IP address here is that then disappear - mask 255.255.255.0 we will give no command here we can see the IP address of s2 coming to us to interface vlan1 IP address and the subnet mask 255.255.255.0 no shutdown coming to e administratively deactivate all unused to ports on the switches so coming to yes one here we can see here we used two ports first of the non 0 / 1 as well as zeros on our 6 so we will deactivate all other ports coming - yes 1 here we can verify that using show IP interface brief and here we can see that first deterrent 0/1 is up also co-star six also up configure terminal you'll go to the interface as arranged faster towards euro / - till 5 also faster turret 0 / 7 till 24 also - Gigabit Ethernet G 0 / 1 + it - he will give Sharon command here coming to suit yes - here we can see we used 2 3 ports first 2/3 0 / 1 0 / 11 + 0 / 18 we can verify that using the short command show IP interface brief and here we can see those interfaces 0 / 1 0 / 11 + 2 0 / 18 so we are going to chat on all other interfaces except these 3 configure terminal interface ray into fast eternal 0 / - we will go till 10 then we have a fast ethernet - 0 / 11 no 11 we have to exclude so tall till 17 also we have a faster turret surah / 19 to 24 also we have a two gigabit authority ports G 0 / 1 and it - here we are going to shut down these ports coming to yes copy the running configuration to the startup configuration coming to es one copy running-config startup config coming two years to copy running-config startup config no we will come to step before configure pc horse refer to the addressing table for PC house and trust information coming to a trusting table here we can see PC devices and its IP addresses coming to PC - a desktop IP configuration here we can see the IP address you'll copy that then the subject to mask also the default gateway then coming to PC - B desktop IP configuration here is the IP address or so this up into mask here is a default gateway coming to PC - see here is the IP address submit to mask here is a default to Gateway now we will come to step of five tests to connectivity verify that the PC horse can ping one another they're given a note also it may be necessary to disable the PCs firewall to ping between PCs when we if you are using there are real pcs so we must disable this pcs firewall can PC a ping PCB we have to check that we will get the IP address of PC - B here is that we will copy this coming to PC - a command prompt and here we are going to ping to PC - B and here we can see we are getting the replay yes spinning next is a can pc - a ping PC - C we will check that to come into PC - C and we will get the IP address coming back to PC - a command prompt into PC - see here is the address and to be are waiting for the replay because timed out no here we are not getting the replay from PC - a - PC - see no next is a can PC - a ping yes one you will get the IP address of s1 here is that coming to PC - a command prompt ping - yes one we are waiting for the replay because timed out it's not communicating because they are in different networks no it's not so here the answer is No next is again PC - be a ping PC - see we will get the IP address of B C - C coming to PC - be command prompt in - PC - see here also you are not going to get the replay because timed out no we are not getting the replay here the answer is known can t see - beeping s - coming to pc - b and we will ping - s - ping two years - here is the IP address it's not going to work because timed out no we are not getting the replaying no a kiss again pc - si ping is - coming to PC - C and we will try to ping - yes - he researches it won't work because timed out no it's not thinking can s1 ping s - we will check that coming two years one Cisco enable password class ping two years - here is the IP address here we can see success Freud is 60% it's communicating because they are the same network yes if you answered no to any of the above questions why were the pings and successful all day I told here we got and some of the unsuccessful pings here we can see this pca and the PCB are in the same network s1 and s2 in the same network so these s1 and s2 will communicate pca and the pc b will communicate but we can see pca and the pcc one communicate because they are in different different networks even PCC - yes - or PC - C - yes one or a PC - C - these two devices also it won't communicate now we will come to party to create VLANs and are seen such reports in party - we will create student faculty and management - VLANs on both the sutures we will then assign the VLANs to the appropriate interface the show VLAN command is used to verify our configuration settings coming to step 1 create VLANs on the switches a create the VLANs on s1 here we can see the command - might be have to give we will do that on s1 coming to the suti s1 configure terminal VLAN 10 name as student I will create VLAN 20 name as a faculty then we're a 99 nameís management coming to be created the same villains on s2 coming two years to password Cisco enable password is class configure terminal VLAN 10 name as student VLAN 20 name as a faculty VLAN 99 name as a management coming to see issue the show villian command to view the list of villains on yes one yourself they given the output for show villain here we can see the villains what we created 10 student twenty faculty and 99 management we will give his command on our sushi s1 coming two years one privilege to X Sigma we are going to give a show VLAN and to here we can see the details here is the violence of what we created what is the default to VLAN here we can see the default to VLAN it's a villain one then what ports are assigned to the default VLAN here we can see all the ports is assigned to this VLAN 1 now we will come to step two yes say in villians to the collector switch interfaces aim as in VLANs to the interfaces on s1 as st. PCA to the student to VLAN here we can see how we have to uh say in it we have to change the mode to access we will do that coming to the suti s1 configure terminal we will go to the interface fastethernet 0/0 port the mode as access such a port access a VLAN 10 coming to to move the suture IP address a VLAN 99 so we have to go to that interface VLAN 1 and we have to remove the IP address and we are going to assign that IP address to this Sevilla 99 or we will do that on s1 we will exit and we'll go to the interface VLAN 1 and here we are going to give a no IP address now we will go to the interface VLAN 99 and here we are going to set the IP address 192.168.1.1 decided to mask 255.255.255.0 coming to be you should the show villain brief command and to verify that the villains are assigned to the correct interfaces chauvelin brief here we can see this port fast Turin co-star six is insane to VLAN 10 named is 2/10 we will verify that on our associates one show VLAN brief and here we can see that first apparent zero star six is a saint to VLAN 10 student coming to see issue the show IP interface brief command what is the status of VLAN 99 and - why coming two years one here we are going to give the show command show IP interface brief and we will verify the VLAN 99 status here we can see with a 99 I P addresses are st. here we can see the status is up but here we can see the protocol is down why this protocol is down here coming to a previous a show command that is a chauvelin brief here we can see no ports are a saint to this VLAN 99 that's why it shows this I mean I deserve a protocol shows down coming to D use the topology to assign VLANs to the appropriate ports on s - coming to the suti has two here we can see they used two ports faster on 0 / 11 here we can see we have two and say in two VLAN 10 also we can see faster turn 0 / 18 we have to assign to VLAN 20 coming to the zoo cheers to configure terminal we have we will go to this interface faster third 0 / 11 interface fastethernet 0/1 support the modest access switch port access VLAN 10 now we will go to at this interface fastethernet 0/1 interface faster 3rd 0 / 18 support mod as access support access VLAN 20 coming to e remove the IP address for VLAN 1 on s2 also a configure an IP address for VLAN 99 on s2 according to the addressing table so we will come to our addressing table sure is that we can see the IP address here they are given for this interface VLAN 1 so we will remove that configure terminal interface VLAN 1 no IP address now we will assign that this IP address for the interface VLAN 99 we will go to the interface VLAN 99 and here we are going to give IP address here is the actress submit the mask 255.255.255.0 coming to G use the show villain brief command to verify that the villains are assigned to the correct interfaces giving this show command show VN brief himself they given the output here we can see this port faster third 0 / 11 is assigned to VLAN 10 then the faster parent 0 / 18 is a saint to VLAN 20 we will verify that coming to our switches to show VLAN brief and here we can see the details here we can see the port of fasterthan 0 / 11 is assigned to VLAN 10 then the port faster R 0 / 18 is assigned to VLAN 20 it's correct is PC - a able to ping PC - B Y B R ago we are going to ping from PC - a to PC - B both are in the same VLAN he will try that we will get the IP address of a PC - be coming to PC - a the stop command prompt here we are going to do ping to PC - B hricko's timed out no we are not getting the replay here the answer is no because we have to configure an eighth note to dot1q trunk between these two sutures that is s1 and s2 next is s1 able to ping is 2y we will try that - coming to the Sochi s 1cl I think two years - here is the IP address of s 2 and we are waiting for the replay it's not going to ping Yuri can see success rate is 0% so here answer is no why it's not pinging so here are the IP addresses for the switches have we given in VLAN 99 and to be the 99 traffic will not be sent over this link of faster than 0 / 1 until we set this link between s 1 and s 2 and said trunk no we will come to part 3 maintain VLAN port assignments and the VLAN database in part 3 we will change VLAN assignments to ports and removal answer from the VLAN database step 1 assign a VLAN to multiple interfaces here we can see on s1 as Seine interfaces faster third 0 / 11 - 24 VLAN 10 here we can see that command we will go those interfaces as a range and we are giving switch Oporto mode as access support access VLAN 10 we will do that coming to the switch s1 configure terminal interface range faster thurid 0 / 11 till 24 switch port modest access support access a VLAN 10 coming to be issued a show beyond brief command to verify VLAN assignments coming two years one show we done brief and here we can see the details here we can see no from fastethernet 0/1 till 24 now it's in VLAN 10 including this port faster than 0 star 6 coming to see reassign faster third 0 / 11 and faster karatsu Rosner's 21 - v 9 20 so we are going to and say in these two ports - VLAN 20 on s1 coming to s1 configured terminal interface we will go as a range faster third 0 / 11 coma faster third 0 / 21 such a port access civilian 20 coming to d verify that the VLAN assignments are correct coming to the tsuchiya's one and two we will verify that by giving this a show VLAN brief command and here we can see now these two ports are removed from the VLAN 10 and it's assigned to VLAN 20 coming to step to remove a VLAN assignment from an interface use the no switch port access VD n command to remove the VLAN 10 assignment to foster parent 0/24 here we can see the command interface AF 0 / 24 no suji port access VLAN we will do that coming to the suti s1 configure terminal interface fastethernet 0/1 d4 no tsuita port access VLAN coming to be verified that the villain change was made so coming to s1 here we are going to give the command show we didn't brief and you know we will check the interface faster third 0/24 will belongs to which to VLAN here we can see that 1st to 3rd 0/24 we can see it belongs to the default to VLAN now VLAN 1 because of your removed from VLAN 10 which you villain is faster on 0/24 now associated with its VLAN 1 now we will come to step 3 remove a VLAN ID from the VLAN database a add VLAN 32 interface a faster throught cirrhosis 24 without issuing the VLAN command here we can see that coming - yes 1 configure terminal interface fastethernet 0/1 t4 switch port access a VLAN 30 here we can see access villain does not exist creating VLAN 30 right because we did not create this avail and 30 now it's created yes here we can see that message they given a note regarding this the current su technology no longer request that the VLAN command be issued to add a VLAN to the database by assigning an unknown VLAN to a port the VLAN adds to the VLAN database so that's why here the Shaunda message it's created this VLAN 30 automatically coming to be verified that the new villain is displayed in the VLAN table by giving this a chauvelin brief command here we can see that now VLAN 30 is added with a default we lend name and here we can see the support fasterthan 0/24 is a saint - at this VLAN 30 we will check it on our switch yes one chauvelin brief and here we can see VLAN 30 with the VLAN default in name for this villain 30 and here we can see this port the faster of 0 / 24 now is assigned to this bill and 13 what is the default the name of VLAN 30 so there we have seen that here we can see VLAN 0 0 3 0 coming to see use the no VLAN 30 command to removal and 30 from the VLAN database no VLAN 30 coming two years one configured terminal no wheel and 30 coming 2d issued the chauvelin brief command her first appearance rows last 24 was a saint - VLAN 30 yes it's correct so after deleting VLAN 30 what villain is worth faster than 0/24 assigned to what happens to the traffic this time - the host attached to EF 0/24 coming to the suti s1 here we are going to give a show wheel and brief and now we can see the VLAN 30 is remote and here we cannot see the port faster than zeros last 24 that means that that port is not assigned to any VLAN and this Porter will not transfer any traffic here also we can see the output for the show command to show villain brief issue the no tsuita port access VLAN command to own interface fastethernet 0/1 t for coming to yes one configure terminal interface fastethernet 0/1 d4 and here we are going to give the command to no tsuita port access VLAN coming to yes issue the show VLAN brief command to determine the villain assignment for F 0/24 - V - VLAN is F 0/24 assigned coming back - yes 1 again so we then brief and now we can see the port of faster third 0/24 is assigned to the default - VLAN 1 so it's a VLAN 1 and here they given a note before removing a VLAN from the database it is recommended that you re a sane all the ports are seen to that VLAN here we have a question why I should reassign a port to another wheel and before removing the villain from the villain databases so previously we have seen that the interfaces are saying to a VLAN that is are removed from the VLAN database are unavailable and it will not send to the traffic until they are reassigned to another wheel and that's why we serious in a port to another wheel and before removing the villain from the VLAN database now we will come to power for configure an eighth-note - dot1q chang between the switches in part ofour we will configure interface AF 0/1 to use the dynamic trunking protocol that is a DTP to allow it to negotiate the trang mode after this has been accomplished and verified we will disable DTP on interface F 0 / 1 and to manually configure it as a trunk coming to step one use DTP to initiate chunking on faster thorn 0/1 the default DDP mode of eight two nine six zero support is dynamic auto this allows the interface to convert the link to a trunk if the neighboring interface is it - trunk or dynamic desirable mod so set F 0 / 1 on s1 to negotiate a triangle mode here we can see the command coming to yes one configure terminal we have to go to the interface fastethernet 0/1 support the more dynamic desirable here we can see the messages you should also receive a link status message on yes to so here we can see that those messages coming to be issued the show VLAN brief command on s1 and the s to interface fastethernet 0/1 is no longer as saying to VLAN 1 shank the interfaces are not listed in the VLAN table so we are going to give this command to show VLAN brief coming to our Suchi s1 okay class a show VLAN brief coming to the output so we can see now they are this port I of 0 / 1 is no longer assigned to this Seville and one coming to see issue the show interfaces trunk command to view trying to interfaces notice that the mode on s1 is a city - desirable and the mode on s2 is City - Auto coming - yes 1 again here we are going to give show interfaces a trunk and here we can see the details here we can see the mode desirable 40 CF 0 /a 1 coming - yes - so interfaces brief not briefly here to give a show interface as a trunk and here we can see the mod is Otto Porter FAS euro / one they given a note here by default old villains are allowed on a trunk the supported trunk command allows you to control what villains have access to the trunk for this lab keep the default settings which allows all VLANs to traverse you have 0 / 1 no coming to D verify that to VLAN traffic is traveling over trunk interface yep 0 / 1 can s one thing is to be have to check that the coming two years one and we will ping two years to here is the IP atrás success rate is 60% yes it's working yes no be able to ping can't PC - a ping PC - B it should work we will get the IP address of PC - B then coming to PC - a command prompt and we will give a ping to PC - B and - here we can see we are getting a replaying yes next user can pc - a ping TC - see you will get the IP address of PC - see here is that which one work because so they are in different different VLAN coming to PC - a command prompt ping - PC - see rico's timed out no it's not No next you scan PC - beeping PC - si from PC - B - B C - C - one worker here till we can see PC - B is in VLAN 10 PC - C is in VLAN 20 we can make it possible to ping be happy to keep a router and we have to configure inter VLAN routing anyways here it's not going to work we will check that and we will get the IP address of a PC - C coming to PC - being command prompt ping - DC - see it's not working no next gistic and PC - a ping es1 from PC - a to s1 into one worker because this PC - a is in 10.0 network and - this s1 we configured as a 1.0 need to work they are in different different networks so it won't communicate anyways we will check that command prompt ping - 192.168.1.1 no it's not can PC - beeping as - same like previous case it won't communicate from PC - B - years - because they are in different networks to one ninety two dot one sixty eight dot one dot at all no it's not can PC - C ping is - here also no because we can see a PC - C and is - they are in different different networks anyways we will let ping ping and we will check it ping to one ninety two dot one sixty eight dot one dot well here is the result if you answered no to any of the above questions explained below so here itself we explained to her why it's not pinging no we will come to step to manually configure a trunk interface of 0/1 the suitport the modak trunk command is used to manually configure a port a set trunk this command should be issued on both ends of the link coming to aim change the switch port mode on interface AF 0/1 to force chunking make sure to do this on both switches we will do that on our sutures first of all we will do it on s1 configure terminal interface fastethernet 0/1 support the mode as a chunk now we will go to us to configure terminal interface fastethernet 0/1 support more does the trunk coming to be issue the show interfaces at rung command to view the chang mode notice that the mode had changed from desirable to on right so we will give this command show interfaces a trunk here we can see the mode is on coming to us to here we can see the mod is on but here in this show interfaces trunk command here we can see the native eden what they shown here is 99 but previously they shown it's a 1 because we did not set DNA TVland it's a by default it's 1 here we can see that you know we are in a TV land one on both sutures right so why might you want to manually configure an interface to chang mode instead of using DTP yes here the reason is the not all equipment users at DTP so here i using the commanders which i put the more the trunk ensure that the port will become a trunk now we will come to part 2 5 delete the VLAN database in part 2 phi we will delete the VLAN database from the switch it is necessary to do this event initializing a switch back to its default settings coming to step 1 determine if the VLAN database x is issue the show flash command to determine if a VLAN dot dat file exists in flash so we are going to give this command and here we can see the file we rendered that they given a note also if there is a we landed that file located in flash then the villain database does not contain its default settings coming towards susi s1 here we are going to give you the command is show flash and here we can see the file wheel and dot that now we will come to step to delete the VLAN database yeah issued that delete villian dot that command to delete the VLAN dot that file from flash and reset the VLAN database back to its default settings you will be prompted twice to confirm that you want to delete the VLAN toward that file press enter both times so we will give that coming two years one here we are going to give you delete VLAN dot that delete file name will end or that presenter so again they are confirming it can be able to press Enter coming to be issue the show flash command to verify that the VLAN dot that file has been deleted it will give that show flash no here we cannot see the file named villian door dad it's deleted coming to this question to initialize a suit back to its default settings what other commands are needed so we recruited two more commands no one is erased a startup config then a reload coming to the reflection questions first when parties are needed to allow her on VLAN 10 to communicate to her on VLAN 20 this is already we discussed a B how to keep a layer 3 device such as a rotor or a layer 3 switch coming to the second question what are some primary benefits that an organization can receive through effective use of a villains some of the benefits are better security cost-saving higher performance smaller broadcast domains also broadcast storm mitigation well that's all in this lab activity that is configuring VLANs and the tracking ferns if you have any doubt in this a lab activity please comment below also if you liked my video give a thump and share with your friends and don't forget to subscribe the channel so that you will get letters to uploading video info into your Gmail thank you

Channel: Tech Acad

Views: 46,848

Keywords: VLANs, CISCO, CCNA

Id: UOrQdbooO4Y

Length: 53min 22sec (3202 seconds)

Published: Wed Jun 06 2018