10.3.5 Packet Tracer - Troubleshoot Default Gateway Issues

hi friends welcome to all in this video we are going to discuss CCNA version 7 packages for activity troubleshoot default gateway issues before coming to it France if you are watching our channel first time or if you like to get these type of technical videos in future considered subscribing also don't forget to enable that bill icon near to the subscribe button so that you will get notification message whenever we upload a new video and if you like to get more a technical contents or if you like to contact our team you can visit our website a link given in the description ok now coming back to our Pocket racer activity here we can see our addressing table and here we can see the default gateway is incomplete for these devices like s1 s2 pc-1 pc2 pc 3 and PC 4 ok we will update this incomplete addressing table we will see the objectives this activity we will verify Network a documentation and isolate problems then implement verify and document solutions also we will go through the background for a device to communicate across multiple networks it must be configured with an IP address to mask an a default gateway the default gateway is used when the house 2 wants to send a packet to a device on another network the default gateway address is generally the address of the router interface which is attached to the local network that the host is connected to in this activity we will finish documenting the network we will then verify the network or documentation by testing entity 2 into connectivity and troubleshooting issues the troubleshooting method we will use consists of the following steps here are those steps verify the network documentation and use a test to isolate problems determine an appropriate solution for a given problem implemented a solution then test to verify the problem is resolved and finally document the solution now throughout our CCNA studies we will encounter a different descriptions of the troubleshooting method as well as different ways to test and document issues and solutions this is intentional there is no set standard or template for troubleshooting each organization develops the unique processes and documentation standards even if that processes be done how one however all effective troubleshooting methodologies it generally include the steps fo they given a not here if you are proficient with the default gateway configurations this activity might seem more involved than it should be we can most likely quickly discover and solve all the connectivity issues faster than following these procedures however as we proceed in your studies then it works on problems you encounter will be become increasingly more complex in such situations the only effective way to isolate and sol issues is to use a methodical approach such as the one used in this activity ok in this activity we will go one by one and we will troubleshoot this at apology now here we can see the instructions in part of unverified Network documentation and isolate problems in part one of this activity complete the documentation and perform connectivity test to discover issues in addition we will determine an appropriate solution for implementation in Part II - coming to step 1 verify the network documentation and isolate any problems before you can effectively test a network you must have complete a documentation notice in the addressing table that some information is missing completed a dressing table by filling in the missing default gateway information for the switches and the PCs yes in the beginning itself we noticed that some of the default gateway informations are missing in this addressing table so we will updated is a dressing-table first okay here we can see our addressing table we are going to fill this a default gateway for these devices so coming to our topology here we can see the devices yes one piece even and PC two they are in one network and we can see it's connected to this interface gigabit eternal 0 / 0 hence obviously the default gateway for all these devices in this network will be the IP address of this interface Gigabit Ethernet 0 / 0 in this router r1 here we can see that IP address it's 192.168.1.1 we will update a default gateway information for those devices so IP address is 192.168.1.1 we will copy researchers and the s-1 default the gateway then PC 1 default gateway and the PC 2 default gateway okay now here we can see the devices yes - PC 3 and PC 4 are in the same network and which is connected to the interface gigabit eternal 0 / 1 in this router hence the default gateway for all these devices will be the IP address of this interface so gigabit 1/3 0 / 1 on this router r1 sure we can see that IP address it's 192.168.1.1 we will update that information in this addressing table we will copy these IP address and here we can see as to default gateway it's your and for PC 3 and PC for default gateway it's here okay all right roasting table now updated now test connectivity to devices on the same network by isolating and correcting any local access issues you can better test a remote connectivity with the confidence that local connectivity is operational okay we can do that first a verification plan can be as simple as a list of connectivity tests use the following test to verify a local connectivity and isolate any access issues the first issue is already documented but you must implement and verify the solution during party to sure we can see testing and verification documentation so from pc1 to pc2 when we ping is it successful it says no what is the issue IP address on pc 1 and the here is a solution change PC one IP address okay just we will check it we will get the IP address of PC - ok we will copy this IP address then we will go to PC 1 desktop command prompt sorry its IP configuration we'll go to command prompt and here we will let ping - PC - here is the IP address and now we are waiting for the replace request timed out no it's not working here we can see packets sent for but we can see received 0 and the lowest forum that means it's not working I mean it's not pinging from pc1 to pc2 no we have to identify the issue here itself they highlighted the issue IP address on PC 1 so we will check the IP address or PC 1 so in command prompt we will give this command ipconfig and we will verify ipv4 address sure we can see that it's 192.168.1.2 in you will check with our addressing table here we can see it's not 11.10 sure we can see it's a 10.10 so we have to change this IP address in this PC one and all other information are correct sir to mask and the default gateway you see one here we can see that it's correct okay okay next we will ping from pc-12 yes one mostly it won't communicate because we have seen they configure that IP address incorrectly on this PC one but still we will try it we will get the IP address of s1 it's you're then coming to PC 1 we will ping to our switch no it's not working okay now what we will do we will check the IP address of this switch s1 we will close this window or minimize it okay now coming to s1 we will go to CLI and we will verify its IP address enable and a better we will give a show running config and here we can see interface vlan1 IP address you will verify with our addressing table yes one 192.168.1.2 okay and the circuit to mask okay it's correct and actually I am checking for the default gateway for this rubber I think it's not configured okay anyway we will verify that you can beeping from a remote device no next is ping from pc1 to r1 so we have to get the IP address of our one interface gigabit eternal 0/0 but it obviously it won't work because PC one IP address configured incorrectly we will verify our router r1 coming to CLI enable show running config and we will go to the interface Gigabit Ethernet 0 slash 0 and here we can see IP address 192.168.1.1 and these two masks it's correct the same way we can try from PC to we will a ping to yes 1 we will get the IP address of s1 ok now coming to PC to desktop command prompt firstly we will verify its IP address I mean this PC 2 IP address we will give I P config and here we can see IPR Ross details when I into door two one six eight dot 10.11 it's correct and here we can see sir to mask default gateway everything correct okay now we will a ping to yes one enter waiting for the replies are here we can see it's working now we will try to ping to our our r1 to the interface gigabit utterance euro / 0 is 192.168.1.1 it's working now we will go to our next network here's 2 PC 3 and PC for we will a ping from PC 3 to PC 4 so we will get the IP address of a pc 4 will go to pc 3 desktop command prompt first of all we will verify its IP address with our a dressing-table 192.168.1.1 ok and the default gateway it's correct so we will then ping 2 ez 4 it's working now we will ping from a PC free to switch s2 sure we can see the IP address of a switch as 2 you will copy researchers coming to PC 3 ping - yes three and two we are waiting for the replies or request timed out oh it's not working now we will try to ping to the default a gateway to the interface view over the turn 0/1 is it correct yes he'll press up arrow and will give 11.2 1 it's working ok no we will go to PC for desktop command prompt and we will verify its IP address 192.168.1.1 it's correct as for addressing table and here we can see sub to mask and sure we can see the default gateway they configured incorrectly here we can see it's 192.168.1.1 and hear what they configured is 192.168.1.1 so we have to reconfigure or these are default gateway in this device pc 4 ok right so we will ping to PC 3 being to PC 3 it's working now we will ping to switch s2 its 11.2 + up arrow and here we will give 11.2 and we are waiting for the e replies or it cost time now it's not working something misconfigured on as - ok it's not working here we have to verify the details of our switch s2 now we will try to our a default gateway it's 11.1 and it's working okay be identified as some of the problems of when we test a local connectivity the table is an example you must create your own document you can use paper and pencil to draw a table or you can use a text editor or a spreadsheet consult your instructor if you need further guidelines no test connectivity to remote devices such as from pc1 to pc2 try and document any problems this is frequently referred to as nt to end connectivity this means that all devices in your network however the full connectivity allowed by the network policy they given a not here remote connectivity testing may not be possible yet because you must first resolve a local connectivity issues after you have solved those issues return to this step and test connectivity between networks okay that's correct people or the soul or the local issues before that we did not check the IP access or for this device s2 just we will verify that enable and we will give a show running config and you're okay here we can see they set a default a gateway 192.168.1.1 but here we can see they did not set IP address for this interface vlan1 so we have to configure these IP address also we will verify our interface we go with our own 0/1 enable show running config better ok Gigabit Ethernet 0/1 here we can see that 192.168.1.1 and here we can see to mask it's correct okay we will resolve the issues firstly coming to PC one we will close this command prompt then coming to IP configuration and here we can see this IP address configure incorrectly so we will correct it pc1 it's a 10 or 10 so we will change it to 10.10 okay then we up so that the default gateway for this device s1 is not configured but we will identify that when we test any to end connectivity or remotely hence we will configure that default gateway later no coming to PC for IP configuration and here we have seen they configured this a default gateway incorrectly its 192.168.1.2 one we will configure correctly okay also we have seen they did not configure IP a trust for this device yes - so we will configure that IP address as per our addressing table its 192.168.1.2 we will copy this IP address then coming - yes - will press control-c we will give a configure a terminal conf tab t-tapp press enter now we will go to the interface int tab VLAN be tab will n1 okay you'll give the IP address as for our dressing table we copied that it's your then this to mask okay we will give an ocean command okay now we will let test the connectivity locally we'll go to PC one command prompt and we will do all the test again sure okay it's a 10.2 we can see it's the IP address of Horus which is yes 1 and here we can see it's working ok we left right or a default gateway it's 10.1 and here we can see it's working and we will try to PC to its 10.11 and here we can see it's working now the same way we can a try from PC three command prompt and we failed to switch yes - you'll try that it's 11.2 you know we are waiting for the Europe price it's working no we have to go for a remote device connectivity okay we will ping from pc1 to pc2 a PC one to PC for X to drive the tracker will try so you will get the IP errors of TC 3 coming to PC one command prompt ping to PC three oh it's working ok we will try to ping to PC for its 11.11 it's working no we will try to ping - yes - ok here we can see IP address ok we can edit your itself it's 11.2 and now we are waiting for the replies to this cell switch yes - or Acosta timed out okay it's working we can try once more and here we can see we get the replace now we can try to ping to this interface gigabit at or 0/1 will give her one and it's working okay now we will close this PC 1 then we will a ping from this network to this network okay we will consider pc 3 then coming to command prompt okay it will a ping to a pc 1 we will get the IP address you'll copy this errors ping to pc 1 it will work because we tried from pc1 to pc2 3 when we can we can try to pc - it works no we have to try to this s 1 and R 1 first of all we will try to use one it's a 10 or 2 it won't communicate because not configured the default gateway or request timed out no no it's not working ok because the default gateway is not configured we have to do that no we will a ping to the interface a Gigabit Ethernet 0/0 it's 10.1 ok we press up arrow and here we will give 10.1 it's working ok now coming to step 2 determine appropriate solution for the problem using your knowledge of the way networks operate and URL device configuration skills search for the cause of the problem for example s 1 is not the cause of the connectivity issue between pc1 & pc2 the legal lights are green and a no configuration on s 1 would cause a traffic to not pass between pc1 & pc2 so the problem must be with pc-1 pc2 or both yes we identified and we are resolved already next verify the device addressing to ensure it matches the network documentation for example the IP address for pc 1 is incorrect as verified with the IP config command we already verified that also and actually suggest a solution that you think will resolve the problem and to document it for example I change the IP address for PC 1 to match the documentation okay actually we identified four problems first one is PC 1 IP address configured incorrectly then PC for default gateway is configured incorrectly than we have seen yes one default gateway is not configured then we have seen s2 IP address is not configured I mean a virtual interface IP address is not configured in this switch s1 now in pata to implement verify and document solutions in pata to of this activity we will implement the solutions you identified in part 1 we will then verify the solution worked you may need to return to part 1 to finish isolating all the problems ok here already we implemented the solutions for the local issues now we have to configure the default gateway for this device yes 1 implement solutions to connectivity problems refer to your documentation in part 1 choose the first issue and implement your suggested solution for example correct the IP address on PC one anyway we than that so only pending is we have to configure the default gateway for a dis device s1 ok we will do that coming to s1 enable once more we will verify with the show running config and here we can see only IP address it node falta gateway search okay so we will go to global configuration mode configure terminal we will set the default a gateway its IP default gateway its [Music] 192.168.1.1 then press enter okay now in step 2 verify that the problem is now or resolved verify your solution has solved the problem by performing the test you used to identify the problem for example can pc one now ping pc - yes now it can ping we already verified that with a problem in service all indicate so in your documentation for example in the table above a symbol check mark would suffice in the verified column okay you can do that only pending here is we have to ping from this network - is switch s1 okay we will go to pc 3 and we will a ping to that switch it's a 10.2 we are waiting for the replies request timed out and here we can see no it's work and finally step 3 verify that all issues are resolved if you still have an outstanding issue with a solution that has not yet been implemented return to part 2 step 1 anyways your everything done if all your current issues are resolved have you also resolved any remote connectivity issues such as scan PC one ping TC 4 if the answer is no return to part one step 1c to test a remote connectivity ok just we will try that we will ping from pc1 to pc2 IEP error so PC for I think it's already done and it's working coming to PC one command from okay already done it's working okay right firms in this video we sold packet restore activity troubleshoot a default gateway issues and here we can see our completion status it's a hundred percentage now if you have any doubt any suggestions please comment below also if you liked our video give a thump and share with all your friends and you don't forget to visit our website so that you will get more technical contents or you can contact our team link given in the description so stay tuned and we will meet again with the next video thank you

Channel: Tech Acad

Views: 59,485

Keywords: Default Gateway, CCNAv7, CISCO, CCNA Routing and Switching, CISCO Certification

Id: f-IP5_stg3Q

Length: 29min 59sec (1799 seconds)

Published: Thu Feb 06 2020