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 announce users are complaining they cannot access the really important sites 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 off test bin failed.
Error returned file boot failed, file not accessible.
There is a error on file open.
The router cannot load test.bin and that seems to occur multiple times.
We're told that no valid boot images 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 routers seem 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're in ROM monitor mode for some reason.
So we need to fix that
and then we need to check what's happening on other router's.
Notice we end up with the system configuration dialogue and we're asked, do we want to enter the initial
configuration dialog?
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 loopbacks.
Router 1 should be able to ping its own local loopback, rrouter 2s loopback and router 3s
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 device configurations and get the network working.
I'll give you a hint, however,
router 1 has a loopback pf 1.1
.1
.1, router 2 of 2.2.2.2 and router 3 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 configured to do.
So verify things by using the power cycle devices button once you've restored your device configurations
and make sure that the routers come up again with the configurations and of that the loopbacks up
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?