Troubleshooting with PT - NetworkChuck Edition | Cisco CCNA 200-301

Поделиться
HTML-код
  • Опубликовано: 29 сен 2024
  • Free Packet Tracer troubleshooting lab.
    Download the lab TheKeithBarker...
    Free RUclips Playlists from Keith:
    Master Playlist for Cisco CCNA 200-301 ogit.online/sloth
    Cisco CCNA 200-301 Security ogit.online/20...
    Cisco CCNA 200-301 IPv4 Subnetting ogit.online/su...
    Join our Discord server ogit.online/Jo...
    And…
    Keith’s Content at CBT Nuggets ogit.online/Ke...
    Thank you NetworkChuck for adding these wicked problems. Check out NetworkChuck's channel here:
    / networkchuck
    Check out the live stream where NetworkChuck destroys the lab:
    ogit.online/Ne...
    #CCNA #NetworkChuck #PacketTracer #CBTNuggets

Комментарии • 132

  • @KeithBarker
    @KeithBarker  4 года назад +30

    Thank you NetworkChuck for an amazing troubleshooting challenge!

    • @melvinbartlett6894
      @melvinbartlett6894 4 года назад +1

      Hi Keith, how about some labs with network automation?

    • @KeithBarker
      @KeithBarker  4 года назад +3

      Those topics are in my queue. Thanks!

  • @MrBettybologna
    @MrBettybologna 3 года назад

    I am just starting to study for my CCNA, and while I didn't really understand some of the concepts; this was a very exciting exercise. I would like to see more of the blind PT troubleshooting labs, thanks for all the content.

  • @nelsonmoreira9039
    @nelsonmoreira9039 2 года назад

    A-MAZIING! I had SO much fun watching this! It's informative AND entertaining. Diagnosing is one of the most interesting parts of my job as a sys admin, so this was better way better than watching a movie or series for me. Great job Keith and Chuck, thanks for this.

  • @JL-wl6vf
    @JL-wl6vf 4 года назад +9

    This was an amazing review of many different topics all-at-once, very nice study and lab!
    Thanks NetworkChuck & Keith for such good resource.

    • @KeithBarker
      @KeithBarker  4 года назад

      Happy to do it, thanks for the feedback Jose

  • @grahamjkeddie
    @grahamjkeddie 4 года назад +7

    Hey Keith, Looking forward to watching you fix this broken lab, wow its really messed up! I think I have most of the issues fixed, but the routing issue is racking my brain. Time to save the PT and try again tomorrow.

    • @spenserblum529
      @spenserblum529 4 года назад +2

      verify the neighbor adjacency and use traceroute to see where the problem router is. Also use your show commands to get as much information out of the protocol as possible.

  • @murraybown2502
    @murraybown2502 4 года назад +4

    I need a wall to bang my head against, tough one. :-)

  • @Protocol57
    @Protocol57 4 года назад +1

    The trunk vlan allowed all helped me ping all the top stuff. Took me way longer but im pretty green. Packet tracer crashing twice and bringing me all the way back to Christmas lights didn't help. After that started saving pt files after every command.

    • @KeithBarker
      @KeithBarker  4 года назад

      Thank you Protocol57 for working on that lab! Hands on practice is one of the best ways to build your skills, and get better. Thank you!

  • @Rustyjarz
    @Rustyjarz 4 года назад +1

    I wish I had this lab before I did the CCNA cert. This is one of the best troubleshooting labs I've seen. For me I can read the theory until the cows come home but until I 'do it' I find it hard to make the connections. Keith Barker there's one thing you forgot IMHO, and that was to form an ehterchannel between MLS1 and MLS2.

  • @MultiTechspec
    @MultiTechspec 3 года назад +1

    can we get chuck to make one for David Bombal with input from Keith?

    • @KeithBarker
      @KeithBarker  3 года назад

      Thank you Multitechspec, I would be open to that.

  • @elangovanpalanisamy6135
    @elangovanpalanisamy6135 3 года назад

    Hey keith, Awesome lab and good Tshoot stuff. I loved it..... I guess"Portfast default" cmd on Access 1 switch may create loop on trunk ports...

  • @abhishekkatiyar2151
    @abhishekkatiyar2151 4 года назад +2

    This increase my interest in switching. Thanks Keith. Oh one more thing I like your finger game.👐

  • @mohammedaljanaby315
    @mohammedaljanaby315 4 года назад +2

    Hey Keith, it is outstanding watching you work sir! this has been great! I will continue my studying and practicing in networking to hopefully become close of how great of an engineer you are. Thank you for doing this!

  • @nimesis124
    @nimesis124 3 года назад

    Hi Keith that a very nice effort though ;)... But I think some topics are not CCNA level what do you think?

  • @berndeckenfels
    @berndeckenfels 2 года назад

    If you want to challenge yourself do not use the topology and port labels diagram and overview, but only explore the network from logging in into the devices and servers. This will show you if you have a useful network plan.

  • @Welcome_cutie309
    @Welcome_cutie309 4 года назад

    Hi Expert CCNA takers kindly help me with this: (ICMP type:3, code:3, Destination port unreachable). Can someone help me with this error. I am trying to ping from 1 pc to another pc, both are on different routers and there is a serial connection between them with no encapsulation. PC1 is at network (192.168.0.2/24) network with the router's interface IP at (192.168.0.1/24) . PC2 is at (192.168.1.2/24) and router's interface at (192.168.1.1/24). the connection between the routers at 10.0.0.1/30 and 10.0.0.2/30. This is the setup done in GNS3. Have configured the static route for 192.168.1.0 network in Router 1 and 192.168.0.0 network in Router2. Able to ping from PC2 to PC1, but unable to ping from PC1 to PC2, even from router1 unable to ping using source as 192.168.0.1. Kindly suggest.

  • @binsitt
    @binsitt 4 года назад +2

    47:32 "I'll just yank out the power supply and I'll just drop in the power supply." The wonderland of packet tracer :-D

  • @AlexMaday
    @AlexMaday 2 года назад

    I have to point out that one thing that made this harder for Keith were the link lights. They didn't always match up with the simulation. At one point, a link was errdisabled but it still showed green.

  • @ganglu
    @ganglu 4 года назад +1

    Didn't take me too long to fix the layer 2 stuff, but need to brush up more on my OSPF. I did finally got it working on my own, but took longer than I wanted it too. Good lab though!

  • @isaiahgovea2319
    @isaiahgovea2319 4 года назад +1

    I loved this type of lab mix up lab challenge between you and Network Chuck. This was an excellent way to see real-world troubleshooting steps completed. Tackling it from different approaches to be efficient at the repair.
    I hope we can see some more episodes like this!

  • @rafapilecki1256
    @rafapilecki1256 2 года назад +1

    Keith, I love your videos with troubleshooting. I am impressed about your passion with networking. I downloaded some of your PT LABs and I am trying resolve OSPF thing. Even i watched your videos and read from study guide and i think i know everything i should check in real LAB there are plenty areas i will forget or didn't noticed. You are doing amazing job. ThX

  • @fernandohg225
    @fernandohg225 2 года назад

    wow what a great lab, it took me a few restarts of packet tracer and me thinking something was wrong.

  • @wally19
    @wally19 3 года назад

    I did it before watching this video and It took me about 4 hours to solve it. And here I am enjoying the pain of someone else lol

  • @ChadwickVonGriffindorIII
    @ChadwickVonGriffindorIII 3 года назад

    my packet tracer crashed during this exercise. better check the version

  • @ogechukwuemedo1882
    @ogechukwuemedo1882 4 года назад +1

    Wonderful.
    Thanks, Keith; and thanks to Chuck, too.
    His aim was to make you cry, Keith. You were close.
    :D

  • @michaelboughton5158
    @michaelboughton5158 2 месяца назад

    WOW! Talk about a challenge. I spent hours trying to complete this lab troubleshooting. I wasn't successful, but after watching you, Keith, and how you went about it, I learnt a huge amount. Thank you again for your tireless efforts to not just teach, but have fun doing it at the same time.

    • @KeithBarker
      @KeithBarker  Месяц назад

      Thank you @michaelboughton5158 for working on that lab! Hands on practice is one of the best ways to build your skills, and get better. Thank you!

  • @davidcontreras4675
    @davidcontreras4675 4 года назад +1

    Keith I was following along with you on this....I also had to save and reload the project to get my switches /spanning tree to act right. My Access1 switch cdp nei command did not show any neighbors. the others did. After reloading the project the Access1 was able to show cdp neighbors. Network Chuck did break the network!! I havent looked at his video yet. I am going to look at his video next to see what he did. Thanks Keith.

    • @KeithBarker
      @KeithBarker  4 года назад

      Thank you David for working through the lab, and for your feedback! Cheers.

  • @joelvictores3540
    @joelvictores3540 4 года назад +1

    Great idea and great video !. I had so much fun following you through the troubleshooting steps as you did fixing that network. Please post more videos like this one. Sincerely, it is a great teaching tool for those studying for the CCNA R&S and even CCNP. Thank you so much.

  • @karolydekany3149
    @karolydekany3149 4 года назад

    Keith, if i'm not mistaken you forgot to fix the ACL for NAT on R1 into the public server :P It denied everything it must be changed to permit.

    • @KeithBarker
      @KeithBarker  4 года назад +1

      Thank you Károly Dékány, during the troubleshooting, I was focused on the client to client connectivity, and when that happened I stopped. Later, while chatting with NetworkChuck, he shared with me that there were several other issues, including some with NAT, that I didn't even solve, as I didn't need to reach the external web server. If I were to do this again, I know there are more things to clean up.
      Thanks for watching, and for your thoughts.
      Happy continued studies.

  • @jonathanedge7945
    @jonathanedge7945 6 месяцев назад

    this is definitely my absolute favorite networking video

    • @KeithBarker
      @KeithBarker  6 месяцев назад

      Thank you @jonathanedge7945!

  • @mohammadalmaazi
    @mohammadalmaazi 2 года назад

    You way of explaining is super

  • @washburn969
    @washburn969 4 года назад

    Hi Keith, and what about NAT???, you skipped that part ...

    • @KeithBarker
      @KeithBarker  4 года назад

      Thank you for the observation Fero Koľvek. I only knew about the requirement for PC to PC connectivity, and not access to the server. Just didn't know until later when I watch the video where NetworkChuck injected the errors. Good eye!

  • @vyasG
    @vyasG 3 года назад

    Thanks a lot to both Keith and Network Chuck for this lab. It was an amazing experience troubleshooting this lab. Took some time to solve it. But succeeded eventually. All clients can ping the server and other clients. Hooray!
    EDIT: Highly recommended to go through the video even if troubleshooted by self. I missed the ospf adjacency log and reference bandwidth part.
    Appreciate your troubleshooting methodology. True Professional!

  • @delfimrocha4174
    @delfimrocha4174 2 года назад

    Mr. OGIT I can't express this enough, I am grateful for the labs which is getting me prepared for my certification.

  • @xRoyaltyyy
    @xRoyaltyyy 4 года назад +1

    I can't wait for this!

  • @dnab1986
    @dnab1986 4 года назад

    Thanks for the video. It was wicked watching someone with your experience go through and resolve issues and the steps you take to fault find. I learnt loads. Cheers.

  • @debasishdash2780
    @debasishdash2780 4 года назад

    I didn't know about the history command exists in packet tracer CLI. Would have made faster getting CCNA faster. Time to go and see if grep command works

    • @KeithBarker
      @KeithBarker  4 года назад

      Thank you for watching Debasish!

  • @LakedaimonII
    @LakedaimonII 10 месяцев назад

    4 and more hours of labbing, ccna not already done and finally i was able to fix it. Probably i fix some stuff not "as intended": dhcp snooping (prob more ports to trust); ip helper-address and something else, dunno.
    Let's watch this video and thanks to you and chuck for this amazing lab. It pushes me beyond my limit coz i did not looking for solutions or tricky workaround.
    These kind of labs are gold and teach you more then a course!

    • @LakedaimonII
      @LakedaimonII 10 месяцев назад

      Oh, as a complete noob the hardest of the hardest part was learn how to find an order to procede.
      I use a notepad to manually track all, but without a proper method was rly hard. This is biggest part that wasted my time.

    • @LakedaimonII
      @LakedaimonII 10 месяцев назад

      Full video watched. As i Said, i completely misunderstod the DHCP part. I removed the helper-address and creare new DHCP pool. Manually set all vtp as transparent and disable DHCP snooping. Still proud but a bit meh now.

  • @EA-fb7ug
    @EA-fb7ug 2 года назад

    Thanks

  • @ejohn926
    @ejohn926 3 года назад

    I am a CCNP and the lab help me fill in so gaps, Awesome Lab Keith

  • @johnb4932
    @johnb4932 4 года назад

    This is a funny lab for me. I've been stuck on the same part where keith was unable to ping from PC1 to the default gateway. It took me so long that my packet tracer crashed but was able to save my progress. After opening my save file, the whole thing magically started working. wth

    • @KeithBarker
      @KeithBarker  4 года назад

      Thank you John for working on that lab! Hands on practice is one of the best ways to build your skills, and get better. Thank you!

    • @johnb4932
      @johnb4932 4 года назад

      @@KeithBarker thanks Keith for all the resources and help youre giving us too! Are those occurances a common thing on real devices? Or its more just a packet tracer bug?

  • @damonec1987
    @damonec1987 4 года назад

    I have noticed sometimes Packet Tracer gets stuck. If you make the corret configuration and nothing changes , try restarting Packet Tarcer. Save your changes and restart Packet Tracer, usually clears it up.

    • @KeithBarker
      @KeithBarker  4 года назад

      Thanks for sharing

    • @damonec1987
      @damonec1987 4 года назад

      @@KeithBarker No problem. I enjoy and appreciate the content people like yourself, and networkchuck create. It is extremely helpful.

  • @ijasat
    @ijasat 4 года назад +1

    Where can I get the latest packet tracer....is it free.

    • @murraybown2502
      @murraybown2502 4 года назад

      Go to www.netacad.com/ sign up for a free account and download it.

    • @KeithBarker
      @KeithBarker  4 года назад

      Yes, Packet Tracer is free. Go to netacad.com sign up for a free account, and download the free Packet Tracer software. Enjoy!

  • @niravchauhan2278
    @niravchauhan2278 3 года назад

    Very informative 👌✌️

  • @memem1792
    @memem1792 2 года назад

    more videos like this please

  • @treygraham5854
    @treygraham5854 Год назад

    I had attempted this by myself a few times, and could never finish it. Now I can finally fix this lab by myself. Major credit to you Keith! Thanks fr being one of the main forces behind my growth :)

    • @KeithBarker
      @KeithBarker  Год назад

      Way to commit to your goal Trey Graham❗ You can do this.

  • @alittax
    @alittax 2 года назад

    Thank you for giving us an insight into how you go about troubleshooting! It helps a lot. I'm only 30 minutes in but thanks to you, I realized I needed to brush up on the topic of DHCP snooping, because it turned out that I didn't understand it as well as I thought I did. But, now I think I do. :) Thanks again!

  • @deancantave5233
    @deancantave5233 4 года назад

    Keith, excellent video. I work as an Infrastructure Manager where I work with Network Engineers and not so much hands on but I'm always educating myself. What are you using to record this video? Video and Audio items?

    • @KeithBarker
      @KeithBarker  4 года назад +1

      Thank you for the question Dean. I use Streamlabs OBS, for the recording. Painter as a painting program, and Epic Pen which allows me to write on top of any screen. Let me know if you have other questions, and thanks for watching!

  • @minuterain
    @minuterain 4 года назад

    the Maestro boldly takes the stage. It was quite hilarious and with fondness watching your sentiments & reactions sir Keith.
    Thanks Network Chuck & Wizkid for the well planned wicked injections and Thanks Keith for a glimpse into your uppeclassmanship live on screen. Above all for vocalising your thoughts and guy feeling at every juncture!! This is a rare 1st of its kind teaching method, I think you've definitively created a new learning method trend. More contents and competitions like this please maybe?

  • @djrulz1991
    @djrulz1991 3 года назад

    Hi Keith , Thank you for the session. A quick question, I see that you do not use 'show run' command a lot and rely a lot on protocol specific show commands, why is that? (out of curiosity)

    • @KeithBarker
      @KeithBarker  3 года назад

      Thank you for the question Dhananjay Parab. Show run is the static configuration of a system. It doesn't show the actual state of the system, including interfaces that may be up or down, ospf neighbors that may or many not be forming adjacencies, and the rest. In troubleshooting, that is the information that is very important to extract.

  • @ahmedabdellaoui796
    @ahmedabdellaoui796 4 года назад

    This ia a nice idea from you Keith and NetworkChuck.
    Thanks a lot for sharing this cool video
    Waiting from you more stuff like this 👍

  • @channange5813
    @channange5813 4 года назад

    I'm unable to open this lab, incompatible version. What packet tracer version I need for this? Mine is 7.1

  • @Smilin_Chris
    @Smilin_Chris 4 года назад

    What amazing insight into troubleshooting methodology. This was so fun to watch. Thanks for doing this for us y'all!

  • @jamesknotts2096
    @jamesknotts2096 4 года назад

    This was fantastic!! Its was great getting to see you work, awesome job!! Thank you for all you do.

  • @milosatanaskovic3656
    @milosatanaskovic3656 4 года назад

    I did this PT alone and it took me about two and half hour to fix it even if I am CCNP :( .
    Now I wanted to walk through once again with you Keith to see how you troubleshoot and how you think and I can say that I learned a lot from you! You are awesome! :) All the best!

    • @KeithBarker
      @KeithBarker  4 года назад

      Awesome! Thank you for the comments, and for going through the lab!

  • @mharoon77
    @mharoon77 4 года назад

    @Keith, Thanks you so much for the way of teaching and Utilizing the lockdown time . 👍

  • @0812sonu
    @0812sonu 4 года назад

    Wow, amazing to watch you troubleshoot Keith.. Thanks.

  • @dubonbiton1706
    @dubonbiton1706 4 года назад

    that was awesome troubleshooting video. I have learned alot! thanks!!

  • @johnkasonga6634
    @johnkasonga6634 4 года назад

    Brilliant!

  • @staramod
    @staramod 4 года назад

    Simply amazing 😉 quite a refresher !!

  • @blendonator
    @blendonator 4 года назад

    How many networks could a network Chuck buck, if a network Chuck could buck networks? 😁
    I'm going to have to call you out on this though! As soon as you saw IOC's, you should have restored all devices from your backups and started poking through your stealthwatch 😋
    That was cool though 👍 Personally I think I would have started by clearing out the comments and junk in the file. I'm Linux at home, so some seq/sed/awk/bash/Perl can make for very rapid text prototypes that you can output to a file, then copy paste. eg: to unset all the descriptions.
    Always a blast to watch the pros work! And gotta love PT! If only it could do everything like virl.

    • @KeithBarker
      @KeithBarker  4 года назад

      Thank you blendonator!

    • @blendonator
      @blendonator 4 года назад

      @@KeithBarker No problem, but ty for the videos!
      For others curious what I meant, in bash try this:
      for k in `seq 1 3`;do echo "int g1/0/$k";echo " no desc";done;echo -e "exit
      wr"
      It will give output similar to:
      int g1/0/1
      no desc
      int g1/0/2
      no desc
      int g1/0/3
      no desc
      exit
      wr
      Hope that helps someone out there! o/

  • @samzwell
    @samzwell 4 года назад

    This one video taught me alot ❤️.. thanks keith.

  • @melvinbartlett6894
    @melvinbartlett6894 4 года назад

    Aren't some links still in half duplex

    • @KeithBarker
      @KeithBarker  4 года назад

      Thank you Melvin, and yes. Once I got to the objective of client end to end connectivity, I stopped looking for problems. After recording I watched NetworkChuck's stream, and saw there were a few other gems they had implemented. Lots of fun all around.
      Thanks for watching!

  • @fauxz3782
    @fauxz3782 4 года назад

    You're amazing Keith!!!

  • @johnmichaelechavez5979
    @johnmichaelechavez5979 4 года назад

    the rack thing on packet tracer.. thanks

    • @KeithBarker
      @KeithBarker  4 года назад

      Thank you John! That is one of my favorite parts of PT.

  • @tolonify
    @tolonify 4 года назад

    This is pure gold¡¡

  • @memyselfimemyselfi496
    @memyselfimemyselfi496 4 года назад

    Really Good Keith

  • @kevinhughes9801
    @kevinhughes9801 4 года назад

    That was good thanks

  • @networksecuritygeek642
    @networksecuritygeek642 4 года назад

    This was so much fun!

  • @krismorrison6007
    @krismorrison6007 4 года назад

    Superb 👌

  • @ThePacketThrower
    @ThePacketThrower 4 года назад

    More Cisco!!!

    • @KeithBarker
      @KeithBarker  4 года назад

      Thank you The Packet Thrower! Let me know if you would be interested in adding a few problems into a PT lab for me. If so, I will create a new topology just for that. If interested, lets chat on Discord. ogit.online/Join_OGIT_on_Discord
      Cheers, and thanks for the post!

    • @ThePacketThrower
      @ThePacketThrower 4 года назад

      @@KeithBarker Sure I'll pop by your discord