Cisco CCNA Packet Tracer Ultimate labs: The Network is Down! Can you fix it?

#CCNA #PacketTracer #CCENT

This one of multiple Cisco config-register labs, Can you complete this CCNA Exam Lab?

Labs! Labs! And more Labs! Get the hands on experience to pass your CCNA exam!

Do you know what 0x2101, 0x2102 and 0x2142 mean on Cisco devices?

Make sure you are ready to pass the CCNA exam! Prepare practically for the Cisco CCNA certification which is the most in-demand networking certification in the world today! Make sure you can pass the Cisco CCNA Routing and Switch 200-125 exam!

This course tests your knowledge of CCNA topics with practical, hands on labs. Labs include both configuration as well as troubleshooting labs.

Ask yourself these questions:
- Are you ready and prepared for the labs in the CCNA exam?
- Are you able to troubleshoot Cisco networks?
- Are you confident with your ability to configure networks as required by Cisco to pass the CCNA?

Answer:
This course helps you prepare for the exam and gain the confidence to pass the exam!

There are many topologies and many labs in this course!

Transcription:

This is a packet tracer troubleshooting lab.
You’ve been told that after a power outage the network has stopped working entirely. Assume that this is just a portion of the network where issues are occurring.

Notice as an example that on Router 3 we see an issue, file boot failed, file not accessible, boot of test bin failed

error returned: file boot failed, file not accessible, there is error on file open.

We’re told that no valid boot image is found and the router is going to attempt autoboot from the default boot device.

Now this is important to simulate this network issue. Click the power cycle devices button in packet tracer. In other words, click here and click yes to restart the devices. Notice on router 2 as an example the network is broken. We are in ROM monitor mode.

So we’ve been told that the network is broken. We can already see a problem on router 2. We we’re in ROM monitor mode for some reason. We need to fix that and then we need to check what’s happening on other routers.

Notice we end up with the system configuration dialog and we’re asked do we want to enter the initial configuration dialogue. But that’s not really where we want to end up and notice on router 3 all interfaces are administratively shut down and the router doesn’t have any IP addresses.

So we’ve established that there are problems in the network. Remember in this lab, click this option power cycle devices to simulate the power outage in the network.

You now need to fix the issues and ensure that configurations are restored properly so that the routers can ping each other’s loop backs.

Router 1 should be able to ping its own local loopback, router 2’s loopback and router 3’s loopback.
Now you’ve asked for network documentation but to make matters worse there’s none for this site. In other words, you are blind when configuring the network. You need to somehow restore the device configurations and get the network working.

I’ll give you a hint; however Router 1 has loopback of 1.1.1.1 router 2 of 2.2.2.2 and router 2 of 3.3.3.3

The routers are using EIGRP as the routing protocol in autonomous system 100. That’s all the information you’ve been given. You are not allowed to manually configure the loopbacks and the routing protocols. You need to restore device configurations. Once you’ve done that, you need to verify that things are working again.

As I like to say, routers do what you tell them to do not what you want them to do. In other words, they only do what they are configured to do.

So verify things by using the power cycled devices button. Once you’ve restored your device configurations and make sure that the router comes up again with their configurations and that the loopbacks are pingable. In other words, you need to fix the network so that if a power outage happens again in future, it’s not going to break the network.

[davidbombal]

Transcription:

Your phone rings hesitantly you answer the phone and it’s the news that you don’t want to hear. The network is down, the bosses in arms, users are complaining, they cannot access the really important site such as Facebook.com and YouTube.com. It’s your job to fix the network.

This is a packet tracer troubleshooting lab.
You’ve been told that after a power outage the network has stopped working entirely. Assume that this is just a portion of the network where issues are occurring.

Notice as an example that on Router 3 we see an issue, file boot failed, file not accessible, boot of test bin failed

error returned: file boot failed, file not accessible, there is error on file open.
The router cannot load test.bin and that seems to occur multiple times.

We’re told that no valid boot image is found and the router is going to attempt autoboot from the default boot device.

Now this is important to simulate this network issue. Click the power cycle devices button in packet tracer. In other words, click here and click yes to restart the devices. Notice on router 2 as an example the network is broken. We are in ROM monitor mode.

On router 1, the router seems to be booting up. But let’s see if it boots successfully and on router 3 we have this issue where the router cannot find test.bin. So let’s see if this router boots up successfully.

So we’ve been told that the network is broken. We can already see a problem on router 2. We we’re in ROM monitor mode for some reason. We need to fix that and then we need to check what’s happening on other routers.

Notice we end up with the system configuration dialog and we’re asked do we want to enter the initial configuration dialogue. But that’s not really where we want to end up and notice on router 3 all interfaces are administratively shut down and the router doesn’t have any IP addresses.

So we’ve established that there are problems in the network. Remember in this lab, click this option power cycle devices to simulate the power outage in the network.

You now need to fix the issues and ensure that configurations are restored properly so that the routers can ping each other’s loop backs.

Router 1 should be able to ping its own local loopback, router 2’s loopback and router 3’s loopback.
Now you’ve asked for network documentation but to make matters worse there’s none for this site. In other words, you are blind when configuring the network. You need to somehow restore the device configurations and get the network working.

I’ll give you a hint; however Router 1 has loopback of 1.1.1.1 router 2 of 2.2.2.2 and router 2 of 3.3.3.3

The routers are using EIGRP as the routing protocol in autonomous system 100. That’s all the information you’ve been given. You are not allowed to manually configure the loopbacks and the routing protocols. You need to restore device configurations. Once you’ve done that, you need to verify that things are working again.

As I like to say, routers do what you tell them to do not what you want them to do. In other words, they only do what they are configured to do.

So verify things by using the power cycled devices button. Once you’ve restored your device configurations and make sure that the router comes up again with their configurations and that the loopbacks are pingable. In other words, you need to fix the network so that if a power outage happens again in future, it’s not going to break the network.

So can you do this download the attached packet tracer file and see if you can complete the lab yourself? In the next video I’m going to show you how to fix this network and I’ll also show you some tips and tricks but try and complete the lab yourself.

Everyone is waiting for you to fix the network. Can you get the network up and running again?

[lionelsaayman]

Hi David, I just wanted to say thank you for this series video in particular. I was on-site with my first scheduled power outage recently. A few days prior to the outage I used your videos to prepare and reading additional info. The outage occurred on the day and upon restart and with the UPS up and running most devices came back online apart from 3-5 switches. A few had Traceback issues and some were looking with errors. It was stressful but got it going, needed to xmodem a few and manually booted others. In the end I identified a bug in the software version and requested all the iOS to be upgraded to Cusco recommended. I went to Church before starting work and that gave me peace and your videos and real life scenario made me feel comfortable as it didn't seem alien to me on the day. I'm happy that it worked as I had so many Core devices and IP phones depending on the fix. Now I'm getting ready for my holiday in Fish Hoek. God bless and a huge thank you David. Appreciate all you are doing, BIG TIME!

[UltraGaivalas]

thank you David. Looking forward to CCNP labs

[TheBeach]

I love this because it relates to real world day to day stuff. I’m looking forward to learning more on troubleshooting the err-disable error on switches. I am enrolled in a few of David’s Courses on Udemy also. Great teacher.

[faizytube]

Hi David, On this LAB how did you bring it to that state of an outage, what did you do to make that happen on packet tracer.

[oluwolepetinrin]

please i've tried solving this problem but i dont seem to get it, i just started taking networking class and i was given this exact question to solve. please can i be directed to the solution. thanks

[razibulislam]

Please give me the campus network full configuration videos

[Marbell]

What version of packet tracer will this work with? I've tried 6 and 7, but get an error.