6.4.8 IPv4 Routing Troubleshooting
IP traffic destined for a device configured with the address 10.10.34.4/24 is congesting the network. The network administrator issues a traceroute command from the local router and receives the following output: Router#traceroute 10.10.34.4 Type escape sequence to abort.Tracing the route to 10.10.34.4 1 192.168.12.2 20 msec 20 msec 20 msec2 192.168.12.1 8 msec 12 msec 8 msec3 192.168.12.2 8 msec 8 msec 12 msec4 192.168.12.1 12 msec 8 msec 8 msec5 192.168.12.2 8 msec 8 msec 12 msec6 192.168.12.1 8 msec 12 msec 8 msec ! -- remaining output omitted -- What is the cause of the problem?
A loop exists between two of the routers.
Network users are complaining that they can connect to resources within the company, but cannot use the internet. The network administrator begins troubleshooting the problem by entering privileged EXEC mode on the company router and typing the show ip route command. What is the most probable cause of the problem?
An incorrect next-hop route is statically configured on the local router.
The administrator of a corporate network is receiving complaints from internal users that they cannot access the internet. The administrator displays the routing table of the local router using the show ip route command. What should the administrator do on the local router to provide internal users access to the internet?
Configure a default route using ip route 0.0.0.0 0.0.0.0 131.108.2.2.
You are working at the console of a new router. You want to check the configuration of a neighboring router called Sales5. You type telnet Sales5 at the router prompt and receive the following message: Translating "Sales5"...domain server (255.255.255.255)% Unknown command or computer name, or unable to find computer address What should you do?
Configure an address of a DNS server for the router to contact.
Router_1 is connected to three networks, 192.168.0.0, 172.16.16.0, and 172.16.32.0. An administrator enables the RIP routing protocol on Router_1. The router isn't forwarding packets to network 172.16.16.0. The administrator examines the configuration on Router_1 using the sh run command. What should the administrator do to correct the problem?
Enable the Serial0 interface.
When attempting to make a Telnet connection to a remote router, the connection fails. You check the interface status on your local router and find the following: Serial0/1/0 is up, line protocol is upHardware is GT96K SerialInternet address is 192.168.2.1/24MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation HDLC, loopback not setKeepalive set (10 sec)... (additional output omitted) You ping the remote router, but that fails as well. At which layer of the OSI model does this problem originate?
Layer 3
Kathy executed the show interfaces command on a router and reviewed the output. Which output indicates a Layer 1 problem with the Serial0/1/1 interface?
Serial0/1/1 is down, line protocol is down.
Paul executed the show interfaces command and reviewed the output. Which output indicates a Layer 2 problem with the Serial0/1/1 interface?
Serial0/1/1 is up, line protocol is down.
RouterA, RouterB, and RouterC have been configured with IP addresses set as shown. All networks are using the default subnet mask. Users in network 10.1.1.0 claim they cannot access resources in network 192.168.2.0. From network 10.1.1.0, you can successfully ping interface 172.16.32.2, but you cannot ping 172.16.32.1. Another administrator on 192.168.2.0 claims she can ping 192.168.2.1, but not 172.16.32.1. What is most likely the problem?
The S0/1/1 interface on Router C is administratively down.
Last night, an administrator connected a new router to his network and enabled the RIP routing protocol. This morning, when the administrator returned, he discovered the router wasn't forwarding packets to networks connected to the Serial1 interface. He examines the routing table using the command show ip route. What could be the cause of the problem?
The Serial1 interface is administratively shut down.
