EIGRP

Topology Diagram

Addressing Table
Device Interface Fa0/0 HQ S0/0/0 S0/0/1 Lo1 Fa0/0 BRANCH1 S0/0/0 S0/0/1 Fa0/0 BRANCH2 PC1 PC2 PC3 S0/0/0 S0/0/1 NIC NIC NIC IP Address Subnet Mask Default Gateway N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 1 of 2

CCNA Exploration Routing Protocols and Concepts: EIGRP

Lab 9.6.2: Challenge EIGRP Configuration Lab

Learning Objectives
Upon completion of this lab, you will be able to: Create an efficient VLSM design given requirements. Assign appropriate addresses to interfaces and document. Cable a network according to the Topology Diagram. Erase the startup configuration and reload a router to the default state. Configure routers including EIGRP. Configure and propagate a static default route. Verify EIGRP operation. Test and verify full connectivity. Reflect upon and document the network implementation.

Scenario
In this lab activity, you will be given a network address that must be subnetted using VLSM to complete the addressing of the network shown in the Topology Diagram. A combination of EIGRP routing and static routing will be required so that hosts on networks that are not directly connected will be able to communicate with each other. EIGRP must be configured so that all IP traffic takes the shortest path to the destination address.

Task 1: Subnet the Address Space.

Step 1: Examine the network requirements. The addressing for the network has the following requirements: The 172.16.0.0/16 network must be subnetted to provide addresses for the three LANs. The HQ LAN will require 500 addresses. The BRANCH1 LAN will require 200 addresses. The Branch 2 LAN will require 100 addresses.

The loopback address representing the link between the HQ router and the ISP will use the 209.165.200.224/30 network. The 192.168.1.16/28 address space must be subnetted to obtain the addresses for the links between the three routers.

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 2 of 2