3.2.8 Packet Tracer - Investigate a VLAN Implementation

hi friends welcome to all in this video we are going to discuss CCNA version 7 packet tracer activity investigate a VLAN implementation before coming to this activity if you like to get CCNA version 7 online classes or if you like to contact our team for any project support you can visit our website link you will get from the description below and also if you like to get this type of technical videos in future considered subscribing also don't forget to enable that Bell icon new to the subscribe button so that you will get a notification message whenever we upload a new video now back to our activity here we can see our addressing table with the devices interface and its IP address subnet mask and default gateway the objectives observe broadcast traffic in a VLAN implementation and observe a broadcast traffic without be lanced background in this activity we will observe how broadcast traffic is forwarded by the switches and when VLANs are configured and when millions are not configured coming to the instructions in part 1 observe broadcast traffic in a VLAN implementation step 1 ping from pc1 to pc2 coming to our topology here we can see our PC 1 also we can see our a pcs 6 here PC 6 and here is PC 1 we are going to ping from pc1 to this PC 6 wait for all the links lights to 10 to green to accelerate this process click fast-forward time located in the bottom toolbar okay now here everything in green color otherwise we can approach this fast-forward time here now click the smell tab and they use the add a symbol PDO tool the PC one and then click PC six okay we will go to simulation tab now we are in real time we will click on this simulation and we just close this simulation panel now we will let's select this add a single PDO then we will click on PC one then on PC 6 then click the capture bar for wait button to step through the process observe the ARP request as they traverse the network when the buffer full beam to appear so click the view previous events button ok we will do that here we can see a two PDUs you will click capture bar forward and we can see this IRP goes to s 2 it goes to s 1 ok and here we can see IC and B failed where the pings successful explained so here we can see at that ICMP packet a dropped from that PC 1 itself why it is failed because maybe this PC one and this pc 6 are indifferent to VLAN we can verify that here we can see PC 1 is in faster and 0 / 11 just we will verify our Avilan enabled chauvelin brief and we will verify this interface we can see interface fastethernet 0/1 which is in VLAN 10 okay now here coming to pc seeks connected to faster or 0/6 enable show VLAN brief and we will find this port faster at 0 / 6 and we can see this faster at 0 / 6 is in VLAN 30 that means pc 1 is in VLAN 10 and the pc 16 Valente and here we can see they labeled that VLAN 10 and the VLAN 30 in this topology we are not using any layer 3 devices so interval and communication is not possible let's just look at the simulation panel where did s3 send the packet after or receiving it okay you know just we can go back to this backward we can see from s 1 it goes to s 3 then from s1 1 message go to PC 3 because these pieces are the same bill and VLAN 10 here we can see VLAN 10 PC 7 7 also in VLAN 10 then here we can see this a pc 4 also in VLAN 10 so this arp sends to these surfaces but this pc 4 and PC 7 are not the destination we given its PC 6 that's where this arp had dropped by these pcs pc 4 and PC 7 in normal operation when a suture receives a broadcast frame on one of its ports it forwards the frame out all other ports notice that is to only sense the ARP request out faster of 0 / 1 to s 1 also notice that is 3 only since they are play requests out faster on 0 / 11 - pc 4 because they are the same VLAN VLAN 10 pc 1 and the pc for both are belong to VLAN 10 years PC 6 belongs to VLAN 30 because broadcast traffic is contained within the VLAN PC 6 and never receives the ARP request from pc1 because pc 4 is another destination it discards the ARP request the pin from PC one fails because PC 1 and never receives an ARP replay from PC 6 yes this is the explanation so coming to step to pin from pc1 to pc2 the new button under the scenario 0 drop-down tab now click on the add a simple preview icon on the right side of the packet tracer and ping from pc1 to pc2 that we will maximize our packet tracer and here we can see maybe if this hidden you can expand it using this cell left arrow and here we can see the scenario we will click on new then we will resize it in this scenario we are going to a sent I mean we are going to add a symbol P do from this PC 1 to this a PC 4 and these 2 pcs pc1 & pc2 same VLAN in VLAN 10 we will click on this add symbol PDO then coming to PC 1 then we will click on a pc 4 click the capture bar forward button to step through the process observe the arp request as they traverse the network when the buffer a full window appears click the view previous events button where the ping successful explaining we have to verify whether it will succeed or not so we will click on capture bar forward and we can see this arp goes to yes - then it goes to s 1 then we can see one goes to pc 7 because pc 7 also in VLAN 10 and then one goes to is 3 this is switch then it goes to pc 4 and we can see this pc 4 is giving arp back to this a pc 1 the mac address of this pc 4 to this PC 1 because pc 4 is the destination okay now goes back us a unicast communication to pc 1 yes - then to pc 1 and we can see pc 1 received the MAC address of pc 4 again we will capture bar forward so we can see this ICMP goes to its destination then on s 1 then s 3 then 2 pc 4 so he received the ICMP now he has sent backs the acknowledgment to pc 1 and here we can see it succeeded examine the simulation panel when the packet reached s 1 why does it also forward the packet to PC 7 we can see this PC 7 is also in VLAN 10 and that's why at this ARP broadcasted to this same VLAN in PC 7 coming to party - of server broadcast traffic without VLANs step one clear other configurations on all three switches and delete the VLAN database returned to real-time mode ok we will do that then I delete the static configuration on all three switches what command is used to delete the startup configuration of the switches obviously we can use erase command to delete this type of configuration where is the villain file stored in the switches usually VLAN file is stored in the flash memory now we will let delete the startup configuration or hold these three switches coming - yes - CLI here we will check the erase command and here we can see that arrays startup-config arrays contents of configuration memory ok then press Enter confirm again press Enter each lies to the geometry of NV ROM or candy here we can see a rise of NVRAM complete now we will go to s1 CLI array startup-config confirm again we will go to s3 CLI raise startup-config confirm yes next is our delete the VLAN file on all three switches what command deletes the VLAN file stored in the switches yes all DB told this Avilan file is stored in flash and we can delete that using the delete command you will come - yes - and here we will give a show flash and here we can see that a VLAN file we think extension thought that we can delete this file using delete we learned out that when presenter so delete file name will entered that again press enter delete flash we learned out that again be a confirmation okay again press enter sure their prompted this confirmation two times ok now we will go to yes one here we will let delete that file delete VLAN dot that file now we will go to s3 CLI delete wheel and out that after this we have to reload these switches reload the switches use the reload commands in privilege it X Sigma 2 or reset all the switches wait for the entire a link to turn green to asteroid this process click fast forward time located in the bottom yellow toolbar now in this a new packet I saw version this color is not yellow it's a blue here we can see that button we will go to each switches and we will reload it yes - and here we will give reload confirm now we will go to s1 and to reload it confirm now we will go to s 3 CL I reload now here we can see all the links are up here in step 3 click capturable forward to send a LP request and the pings after the switches are reload under the link lights return to green the network is all ready to forward your ARP and the ping traffic now select scenario 0 from the drop down tab to return to scenario 0 we can do that we will maximize this packet tracer and sure we will let's select scenario 0 ok then from simulation mode click the capture bar for red button to step through the process notice that the switches in our forward ARP request out old thoughts except the port on which they are peer request of also received this default action of Assisi's Y VLANs can improve network performance broadcast traffic is contained within each VLAN when the buffer full window appears click the view previous events button ok we will do that we will go to simulation mode and will cross the simulation panel so that we can view this topology fully you will click on capture bar forward and here we can see that ARP goes - yes - then it broadcasted to all the devices VLAN but I mean PC to PC 3 & 2 this is 1 and here again broadcast to all the pcs and then to this s 3 then to all these pcs but still see this piece even drops this ICMP packet now all the devices are in the default - VLAN but the IP address for his PC one and this pc six they are in different networks that's why this ICMP failed now we have some reflection questions here if a PC in VLAN 10 cents a broadcast message which devices or receive it obviously at this message will receive all the devices those who are in VLAN 10 only in the same way if a PC in a VLAN 20 and the VLAN 30 cents a broadcast a message a which device a receive it obviously if we learn 20 cents then only the devices of each are in VLAN 20 will receive this message the same way VLAN 30 sends about that message all the devices that are on VLAN 30 will receive this message next ISA what happens to a frame sent from a PC in VLAN 10 to a PC in VLAN 30 yes so previously we have seen it will drop because the one PC is in VLAN 10 and the other one is in VLAN 30 and one thing we have to keep in mind it will not happen if we configured a inter VLAN routing using a layer 3 devices ok now in terms of ports what are the collision domains on the switch usually in switch each port is a separate a collision domain that means just consider a switch which got 26 ports that means 26 separate collision domain coming to the final question in terms of ports what are the broadcast domains on this switch obviously they are divided by the number of VLANs in the switch and here we can see in this topology we have a 3 VLANs VLAN 10 bill and 20 and VLAN 30 so here we have 3 broadcast domains okay that's all in this packet tracer activity that is investigate a VLAN implementation dear friends if you have any doubt any suggestions regarding this video or any other technical points you can comment below or you can contact our team using our website stay tuned and we will meet again with an extra video thank you

Channel: Tech Acad

Views: 12,039

Rating: 4.9674797 out of 5

Keywords: CISCO Certification, CISCO, CCNA, Packet Tracer, VLAN

Id: nbHvypFILAg

Length: 17min 34sec (1054 seconds)

Published: Sat Apr 25 2020