CCNA Cisco Certified Network Associate (#897)

Section: Version 2.0

Scenario You are implementing EIGRP between the main office and branch offices. In Phase 1, you must implement and verify EIGRP configurations as mentioned in the topology. In Phase 2, your colleague is expected to do NAT and ISP configurations. Identity the issues that you are encountering during Phase 1 EIGRP implementation.

Router R1 connects the main office to the Internet and routers R2 and R3 are internal routers.

Routers Branch1 and Branch2 connect to router R2 in the main office.

Users from the Branch1 LAN network are expected to perform testing of the application that is hosted on the servers in Server farm1, before servers are available for production.

The GRE tunnel is configured between R3 and Branch1, and traffic between server farm 1 and Branch1 LAN network is routed through the GRE tunnel using static routes.

The link between Branch1 and Branch1 is used as a secondary path in the event of failure of the primary path to main office.

You have console access on R1, R2, R3, Branch1, and Branch2 devices. Use only show commands to troubleshoot the issues. Instructions

Enter IOS commands on the device to verify network operation and answer for multiple-choice questions.


Click on the device icon to gain access to the console of the router No console or enable passwords are required.

To access the multiple-choice questions, click on the numbered boxes on the left of the top panel.

There are four multiple questions with this task. Be sure to answer all four questions before selecting the Next button.

Examine the R1 routing table. None of the internal routes other than locally connected appear in the routing table. Which cause of the issue is true?

EIGRP neighbor relationship was not formed due to AS mismatch between routers R1 and R2.
EIGRP neighbor relationship was not formed due to K values mismatch between routers R1 and R2.
EIGRP packets were blocked by the inbound ACL on R1.
IP address was misconfigured between the R1 and R2 interfaces.