6.2.2.4 Packet Tracer - Configuring Trunks

- so welcome to all in this video we are going to see the packet tracer activity configuring trunks now this video is from CCNA routing and switching module two in this packet tracer activity we are going to verify VLANs and we are going to configure chunks we will come to part two one verify VLANs display the current VLANs on s1 issue the command that will display all VLANs configured there should be 10 be lands in total notice how old 24 access ports on the switch are a saint to VLAN 1 we will come to yes one enable we are going to show we learn here we can see the VLAN so we have by default VLAN 1 and we have other VLAN so 10 20 30 88 and to 99 once we count all these VLAN we can see a total 10 VLAN 1 2 3 4 5 6 7 8 9 and 10 also we can see these the 5 VLAN created manually one is two and es-3a display and verify over the VLANs are configured and are saying to the correct to support according to the accessing table yes we will come - yes - and the s3 and we will verify a VLANs in this topology we can see VLAN 10 is assigned to the porter faster thrown at 0 / 11 on s2 and s3 and VLAN 20 is assigned to faster / net 0 / 18 on both sutures and to VLAN 30 is assigned to turtle to 0/6 on s2 and s3 we will verify on cs2 enable show wheel and brief yes here we can see the lantern is a saint to port faster than 0 / 1120 is a saint to faster turn 0 / 18 and 30s are saying - faster / @ 0 / 6 now we will come to yes 3 enable show VLAN brief yes here also we can see will enter Nisus into traffic faster third 0 / 11 2013 2 0 / 18 and the 30th of a into 0 / 6 now we will come to a step to verify loss of connectivity between pcs on the same network although pc1 & tc41 the same network they cannot think one another this is because the thoughts connecting the switches are assigned to vide and one by default in order to provide connectivity between the PCs on the same network and the VLAN trunks must be configured now we will check the connectivity between PC one and PC for so coming to PC one I am going to ping to PC for 170 2.17 doe 10.24 here we can see we are not getting the reply even though these two PCs are in the same network yes now we will come to a party to configure trunks so configure trunking on s1 and use the VLAN 99 as the native VLAN configure it alternate 0 / 1 & 0 / 2 interfaces on s1 for trunking yes we will configure this now we will come to a s1 yes enable configure terminal here we are going to the interface interface if we are going to consider two interfaces that is Gigabit Ethernet 0 / 1 & 0 / 2 so together we can select with the help of range Gigabit Ethernet 2 0 / 1 - 2 yes now we are going to convert these ports to trunk mode switch port the mode us trunk yes next is the configure VLAN 99 as the native VLAN for G 0 1 and G 0 2 interfaces on s1 yes we will come to s1 again and we are going to set DNA to VLAN 99 so we have to give su support trunk Nate t wheel and 99 years yes now the trunk pour takes about a minute to become active due to as planetry click fast-forward time to split the process after the ports become active you will periodically receive the following log message so we learned miss mowcher discovered yes so we can view this the fast forward time and also we can see this native VLAN mismatch discovered on this interface we can check this mismatch message on this vs1 yes here we can see that native VLAN mismatch discovered on Gigabit Ethernet 0 / 1 so this native VLAN we have to set on s 2 and s 3 also as 99 you configured VLAN 99 as the native VLAN on s 1 however is 2 and ds3 are using VLAN 1 as the default in a 2 VLAN as indicated by the syslog message yes although you how any TV line is much things between pcs on the same VLAN are now successful why now we will ping from pc1 to pc2 in from the same network so here i am going to pink to 10 to 24 yes here we can see we are getting the reply I am going to ping from PC to to PC 5 pink 170 2.17 dot 20 to 25 yes here also we are getting the reply and we will go to PC 3 ping 172 Doh 17 to 230 dot 26 here also we are getting the reply yes here we can see a pings are successful corset ranking has been enabled on s1 dynamic trunking protocol that is a DDP and has automatically negotiated the other side of the trunk Ling's I'm in this case a s2 and s3 how now automatically configure the ports attach the to s1 are strangling ports now we will go to a step to verify trunking is enabled on s2 and s3 1 is 2 and s 3 issue the show interface trunk command to confirm that DTP has successfully negotiated trunking with s1 on s2 and s3 the output also displays information about the trunk interfaces on s2 and s3 which actually lands are allowed to cross the trunk we will verify this with the help of a show interface trunk first we will come to s to enable show interface trunk yes here we can see that the port Gigabit Ethernet 0/1 is in at running mode and also we can see the pores at 10 20 30 88 99 first we will come to is 2 here we are going to give show interface trunk here we can see the trunking port is a Gigabit Ethernet 0/1 also we can see VLANs allowed 1 10 20 30 88 and 1099 now we will come to s3 this so enable show interfaces trunk here also we can see the interface the Gigabit Ethernet 2 0 / 2 is trunking and we can see the VLANs allowed 1 10 20 30 88 and 99 yes here we can see active VLANs are allowed to cross the trunk we have 10 20 30 99 now we will come to a step 3 correct the native VLAN mismatch on s2 and s3 the configure VLAN 99 as the native VLAN for the appropriate interface as soon as - Andy s3 and we have to issue so interface trunk command to verify the correct native VLAN configuration yes we will do this now now we are going to configure VLAN 99 as the native VLAN 1 s2 and s3 and here we can see we have to set from the interface a Gigabit Ethernet to 0/1 ons to enter gigabit ethernet to 0 / 2 or not yes 3 first we will come to s 2 here we are going to configure terminal and to the interface Gigabit Ethernet to 0 / 1 and we are going to set switch port trunk native VLAN as 99 yes and we got the message unblocking Gigabit Ethernet 0 / 1 on VLAN 0 0 0 1 for consistency restore yes now we will do it on yes 3 so here we can see the mismatch of Eden mismatch on an 8 9 8 I mean the native VLAN mismatch so now it here it is we can see the native VLAN is 1 we have to set to 99 so configure terminal now we are going to the interface Gigabit Ethernet 2 0 / 2 and so we are going to sit native VLAN supported shrunken a to VLAN 99 now we have to get the message consistency restore yes now we will verify each so just coming to us to verify using show interfaces trunk now we can see the native VLAN is set to 99 also we will verify on is 3 so interface sorcerer trunk yes here also we can see the native VLAN is set to 99 now we will come to the last tip verify configurations on s2 and s3 show the I mean issue the show interface interface suit support command to verify that the native VLAN is now 99 it's already verified these two on s1 and s2 use the show VLAN command to display information regarding configured VLANs why is port gigabit 2002 0/2 one is to no longer assigned to wheel and one okay we will let check on s2 here we can see a small mistake that is on yes to this port a gigabit a third to 0 / 1 is known / assigned actually not gigabit a 10 to 0 / - if it is a Giga because in - 0 / - it is on s3 and no longer assigned to VLAN 1 we will check it we will come to yes to enable so VLAN and - here we can see Gigabit Ethernet 0 / 1 is not listed in this also we will check on s3 show VLAN here we can see Gigabit Ethernet to 0 / TUI's are not showing in this list yes why these ports I mean gigabit eternal to 0/1 on s2 and taking away the 300 0 / 2 on s3 is not displayed it is a transport and transports are not a display a small packet race or activity but most interesting activity that is the configuring trunks front so if you have any doubt of regarding configuring trunk so VLANs or even in CCNA routing and switching please comment below subscribe the channel to get uploading video information stay tuned thank you

Channel: Tech Acad

Views: 63,945

Keywords: CISCO, CCNA, CISCO Certification

Id: WykW7sOgHOc

Length: 15min 31sec (931 seconds)

Published: Tue Jun 20 2017