Transcript ROUTE10S02L09.ppt

Lab 2-4 Debrief
Implementing an EIGRP-Based Solution
© 2009 Cisco Systems, Inc. All rights reserved.
ROUTE v1.0—2-1
Lab Topology
© 2009 Cisco Systems, Inc. All rights reserved.
ROUTE v1.0—2-2
Lab Overview
 Trouble Ticket A—EIGRP Adjacency Issues
– There is no connectivity to the additional IP subnet being
deployed on a LAN segment between routers R2 and R4.
– There are issue with the EIGRP adjacency to router BBR1.
– A configuration was applied that should have improved the
metric calculation on R4, but instead resulted in no connectivity
from that router.
– Summarization was configured, but is not working as
expected.
 Trouble Ticket B—Limited Connectivity
– A new spoke location, router R3, was deployed with no
connectivity to the LAN subnets attached to routers R2 and
R4.
© 2009 Cisco Systems, Inc. All rights reserved.
ROUTE v1.0—2-3
Instructions
 Create the troubleshooting plan.
 Verify that you can see no more errors for the entries generated
on routers R2 and R4.
 Verify that EIGRP adjacency on the LAN segment between
routers R2 and R4 has been formed.
 Verify that the secondary IP address from the LAN segment is
also present on router R1, and that you can ping the IP addresses
from that subnet
 Verify that EIGRP adjacency has been formed between routers
R1 and BBR1.
 Verify that routers in your pod have received subnets
192.168.x.0/24, announced by router BBR1.
© 2009 Cisco Systems, Inc. All rights reserved.
ROUTE v1.0—2-4
Instructions (Cont.)
 Verify that routers have specific information about every subnet in
your network and that you have connectivity to those subnets.
 Verify that router R3 receives IP routing information for the IP
subnets located on the LAN segment between routers R2 and R4.
 Verify that you can ping the IP addresses from the IP subnets
located on the LAN segment between routers R2 and R4.
© 2009 Cisco Systems, Inc. All rights reserved.
ROUTE v1.0—2-5
Summary
 Connectivity issues, wrong authentication, and metric
configuration result in EIGRP adjacency issues.
 Incorrectly configuring a newly deployed site can lead to limited
connectivity.
© 2009 Cisco Systems, Inc. All rights reserved.
ROUTE v1.0—2-6
© 2009 Cisco Systems, Inc. All rights reserved.
ROUTE v1.0—2-7