5.1.9 Packet Tracer - Investigate STP Loop Prevention

hi friends welcome to all in this video we are going to discuss CCNA version 7 packet tracer activity investigate HTP loop prevention before coming to this activity friends if you like to get na CCNA project support or a CCNA online classes you can contact our team using our website link you will get from the description below consider subscribing also don't forget to enable that Bell icon near to the subscribe button so that you will get notification message whenever we upload a new video go back to our activity sure we can see the objectives in this lab we will observe spanning-tree port states and the back to the spanning tree convergence process so describe the operations of spanning tree protocol and explain how spanning tree protocol prevents switching loops while allowing redundancy in switch to the networks so it's a scenario in this activity we will use packet tracer to observe the operation of a spanning tree protocol in a simple switch to the network that has redundant paths coming to instructions in part 1 observe a converged spanning tree instance step 1 verify connectivity ping from pc1 to pc2 to verify connectivity between the hosts our ping should be successful so 4 we will verify the connectivity we will ping from pc1 to pc2 and here we can see the IP address of PC to its 192 dot 168 or to 1.1.1 coming to PC one will go to command prompt and here we will give the command ping the IP address of PC to 192.168.1.1 not 1 then press Enter and here we can see we get the replies in step 2 view spanning tree status on each switch use the show spanning tree banan one command to gather information able to spanning tree status of each switch complete the table for the purposes of the activity only consider information about the gigabit trunk ports the first apparent pores are access ports that how any device is connected and are not part of the inter as which trunk based spanning tree okay we will use this a short command so spanning tree will end one and we will update our table first of all we will go to yes when then CLI enable and here we are going to give that to show command show spanning tree it's a VLAN 1 ok then press enter and we can see each port and it's a saris in this result we can see the interfaces 1 and 0 / 2 and we can see it's a row status its forward also we can see other information so here we can see the status it's a forward so it's forwarding so we'll do that here status okay it's FWD this is also if WD now we will let check this switch is a row to bridge or not so coming to this output here we can see a route ID it's a truss it's a 0 0 0 1 2 6 double 4 8 . c 6 e 7 and we can see the bridge ID of this switch s1 so it's different that means so this s 1 is not a root bridge so we can given next we will go to this switch s2 and we will be a fight enable show spanning-tree VLAN 1 and we can verify the details sure we can see these interfaces gigabit 1/3 + 0 / 1 + 0 / - its terrace for waiting this table copy this now we will verify whether this switch is a route to bridge or not here we can see the route ID priority at trust and here itself we can see they mentioned that this bridge is the route so this is s2 is the road bridge and we can see the route ID also we can see the bridge ID here both are same so this is the road bridge we can specify that here yes to G 0 / 1 G 0 / 2 root 2 bridge yes we'll go to this s3 CLI enable will do the command to show spanning-tree VLAN 1 and here we can see the details these two interfaces G 0 / 1 and G 0 / 2 we can see its status a forwarding and block and these are all these are bridges not row to bridge so we can see G 0 / 2 is in block stage so we'll update that it should be lk g 0 / 1 is in forward state then coming to root bridge now so here we can see our table is updated packet tracer uses a different Linga light on one of the connections between the switches so what do you think this a ling light means coming to our topology here we can see that a link between this s3 and s1 and here we can see this interface a g0 / - in this history shows in amber color that means so this port is not for reading frames because a spanning tree block this pot because why it's blocked due to its redundancy I mean here we can see a loop between all these switches s 1 s 2 and s voice so using STP they block the 1 port coming to the next kitchen what path will frames take from pc1 to pc2 coming to a topology here we can see when we send a message from pc1 to pc2 it goes to s 1 then it will go to yes - not because we can see the sport g0 / - is blocked in this s way so from s when it will go to s 3 then it will go to PC - and why do the frames are known to travel through s 3 yes we already told here on this switch S 3 this port that is G 0 / 2 is blocked by spanning tree protocol so when we send a message from pc1 to pc2 or from PC to to PC 1 it won't go to s 3 we can see it will go to from PC went will go s 1 then s 2 then pc 2 coming to the last question here Hawaii has a spanning tree placed a port in blocking stage C suppose oh you just consider all these links are forwarding or or I mean all these ports are in forwarding States so what happens when this s 1 receives a frame where it will sent it may send to s3 or it mess into s 2 or it just like it works like a loop I mean obviously there will be a loop exist in the network so what happens with the loop loops can degrade network performance and even at this network may fail that's why the spanning tree protocol keeps only one path from source to destination and all other thoughts plot okay now just we'll go to party to observe a spanning tree convergence step one remove the connections between s 1 and s 2 open a CLI window on switch S 3 and issue the command shows spanning tree we ran one live with a CLA winter open then select the delete tool from the menu bar and click the cable that connects s 1 and s 2 ok we will do that just to be will give this a show spanning tree we are VLAN 1 command in yes we will go to s 3 and we'll give that command enable show spanning-tree vlan1 no we are going to delete that link between these switches s1 and s2 so just press a delete button from the keyboard then click on this cable right now coming to step to observe spanning tree convergence quickly return to the CLI prompt on a switch s3 and issue the show spanning tree we learn one command ok we can do that which will go here and we'll give that same command again press up arrow and press Enter and we can see it's a state shows both forward then use the up arrow key to recall the show spanning tree we learn one comment and issue it repeatedly until the orange link light on the cable turns green observe the status of a port g0 / - okay so adjust - again we will reconnect and we will do that because we took some time to read these instructions so we will use this copper straight through from G 0 / 2 - this G 0 / 1 and we'll wait for the convergence okay now our network is converged now again we will give that a shot command just press up arrow and give you that now we can see this is G 0 / 2 is in a blocking state okay now we are going to delete it and we are going to verify it press Delete okay now we'll come here press up arrow and we can see the details so still it's in block because it's number color see now it's a listening a lesson just press up arrow and press enter so that we can see it's uh states G 0 / 2 now it's in LS n that is listening now we can see it's learning it's changed to L R and learning these are the different states of ports now we can see it's in forwarding state okay so what do you see happened to the status of G 0 / 2 port during this process yes we have seen positive was in blocking just will go through that so here we have seen a lesson a lesson lesson yeah yeah it was in block state then it goes to a lesson that is a listening stage then it goes to learning state here we can see that laning lrn then finally it goes to forward state you have observed the transition in Port status that occurs as a spanning tree port most from blocking to forwarding state yes we have seen that now we will go to see verify connectivity by pinging from pc1 to pc2 your a ping should be successful yes it should succeed because we have a path from pc1 to pc2 just you will go to pc 1 then we'll go to command prompt and we can press up arrow so that we'll get the previous command to be given then press enter and we can see it's working coming to the final question are any ports are showing an orange link light that indicates that the port is in a spanning tree state other than for waiting why or why not coming to our topology sure we cannot see any amber color link because now we don't have any redundant paths in this topology we have only single path from pc1 to pc2 right okay that's all in this a packet tracer activity and it's only to understand this expanding tree protocol loop prevention now dear friends if you have any doubt any suggestions regarding this activity please comment below also if you liked our video give it thumb and share with all your friends and also if you like to get any technical support you can contact our team using our website link you will get from the description below stay tuned and we will meet again with the next video thank you

Channel: Tech Acad

Views: 14,888

Rating: 4.9348536 out of 5

Keywords: CISCO, CISCO Certification, CCNA, Routing and Switching, Packet Tracer, CCNAv7, STP, Spanning-Tree Protocol

Id: NUrbfsIsWgM

Length: 15min 31sec (931 seconds)

Published: Mon Jun 08 2020