1 00:00:10,410 --> 00:00:11,490 Your phone rings. 2 00:00:13,010 --> 00:00:15,190 Hesitantly, you answer the phone 3 00:00:18,020 --> 00:00:20,580 and it's the news that you don't want to hear. 4 00:00:21,260 --> 00:00:22,500 The network is down. 5 00:00:22,970 --> 00:00:31,610 The bosses announce users are complaining they cannot access the really important sites such as Facebook. 6 00:00:31,610 --> 00:00:34,890 com and YouTube.com. 7 00:00:35,420 --> 00:00:38,150 It's your job to fix the network. 8 00:00:45,560 --> 00:00:52,550 This is a packet tracer troubleshooting lab, you've been told that after a power outage, the network 9 00:00:52,550 --> 00:01:00,380 has stopped working entirely, assume that this is just a portion of the network where issues are occurring. 10 00:01:01,830 --> 00:01:04,890 Notice as an example, that on router 3 11 00:01:06,060 --> 00:01:07,050 we see an issue. 12 00:01:08,190 --> 00:01:15,180 File boot failed, file, not accessible, boot off test bin failed. 13 00:01:16,060 --> 00:01:21,400 Error returned file boot failed, file not accessible. 14 00:01:22,150 --> 00:01:25,000 There is a error on file open. 15 00:01:26,020 --> 00:01:33,310 The router cannot load test.bin and that seems to occur multiple times. 16 00:01:35,640 --> 00:01:43,580 We're told that no valid boot images found and the router is going to attempt autoboot from the default boot 17 00:01:43,950 --> 00:01:44,580 device. 18 00:01:46,110 --> 00:01:54,340 Now, this is important to simulate this network issue, click the power cycle devices, button in packet 19 00:01:54,360 --> 00:01:54,980 tracer. 20 00:01:55,560 --> 00:02:01,110 In other words, click here and click yes to restart the devices. 21 00:02:01,980 --> 00:02:05,880 Notice on router 2 as an example, the network is broken. 22 00:02:06,450 --> 00:02:08,340 We are in ROM monitor mode. 23 00:02:10,320 --> 00:02:16,650 On router 1, the routers seem to be booting up, but let's see if it boots successfully 24 00:02:18,680 --> 00:02:27,260 and on router 3 we have this issue where the router cannot find test.bin. So let's see if this 25 00:02:27,260 --> 00:02:28,910 router boots up successfully. 26 00:02:29,960 --> 00:02:33,090 So we've been told that the network is broken. 27 00:02:33,680 --> 00:02:39,110 We can already see a problem on router 2, we're in ROM monitor mode for some reason. 28 00:02:39,620 --> 00:02:41,150 So we need to fix that 29 00:02:42,340 --> 00:02:46,000 and then we need to check what's happening on other router's. 30 00:02:47,770 --> 00:02:55,150 Notice we end up with the system configuration dialogue and we're asked, do we want to enter the initial 31 00:02:55,150 --> 00:02:56,440 configuration dialog? 32 00:02:57,510 --> 00:03:05,910 But that's not really where we want to end up and notice on router 3, all interfaces are administratively 33 00:03:05,910 --> 00:03:06,660 shut down, 34 00:03:08,360 --> 00:03:11,870 and the router doesn't have any IP addresses. 35 00:03:13,590 --> 00:03:21,050 So we've established that there are problems in the network, remember, in this lab click this option 36 00:03:21,480 --> 00:03:31,770 power cycle devices to simulate the power outage in the network, you now need to fix the issues and 37 00:03:31,770 --> 00:03:38,400 ensure that configurations are restored properly so that the routers can ping each other's loopbacks. 38 00:03:39,090 --> 00:03:45,360 Router 1 should be able to ping its own local loopback, rrouter 2s loopback and router 3s 39 00:03:45,360 --> 00:03:46,170 loopback. 40 00:03:47,210 --> 00:03:55,570 Now, you've asked for network documentation, but to make matters worse, there's none for this site. 41 00:03:56,060 --> 00:04:00,740 In other words, you are blind when configuring the network. 42 00:04:01,340 --> 00:04:08,430 You need to somehow restore device configurations and get the network working. 43 00:04:08,900 --> 00:04:10,310 I'll give you a hint, however, 44 00:04:10,760 --> 00:04:12,770 router 1 has a loopback pf 1.1 45 00:04:12,770 --> 00:04:13,070 .1 46 00:04:13,070 --> 00:04:20,000 .1, router 2 of 2.2.2.2 and router 3 of 3.3.3. 47 00:04:20,000 --> 00:04:20,510 3. 48 00:04:21,140 --> 00:04:27,710 The routers are using EIGRP as the routing protocol in Autonomous System 100. 49 00:04:28,220 --> 00:04:30,760 That's all the information you've been given. 50 00:04:31,220 --> 00:04:39,800 You are not allowed to manually configure the loopbacks and the routing protocols, you need to restore 51 00:04:40,220 --> 00:04:41,810 device configurations. 52 00:04:42,380 --> 00:04:48,140 Once you've done that, you need to verify that things are working, again 53 00:04:48,360 --> 00:04:56,780 as I like to say, routers do what you tell them to do, not what you want them to do. 54 00:04:57,290 --> 00:05:01,610 In other words, they only do what they configured to do. 55 00:05:01,970 --> 00:05:10,160 So verify things by using the power cycle devices button once you've restored your device configurations 56 00:05:10,760 --> 00:05:17,910 and make sure that the routers come up again with the configurations and of that the loopbacks up 57 00:05:17,910 --> 00:05:18,500 pingable. 58 00:05:18,980 --> 00:05:25,970 In other words, you need to fix the network so that if a power outage happens again in future, it's 59 00:05:25,970 --> 00:05:27,650 not going to break the network. 60 00:05:28,280 --> 00:05:29,480 So can you do this? 61 00:05:29,990 --> 00:05:35,390 Download the attached packet, tracer file and see if you can complete the lab yourself. 62 00:05:35,960 --> 00:05:39,560 In the next video, I'm going to show you how to fix this network 63 00:05:40,040 --> 00:05:42,050 and I'll also show you some tips and tricks 64 00:05:42,470 --> 00:05:44,780 but try and complete the lab yourself. 65 00:05:45,350 --> 00:05:49,520 Everyone is waiting for you to fix the network. 66 00:05:49,970 --> 00:05:52,190 Can you get the network up and running again?