Beruflich Dokumente
Kultur Dokumente
Traffic from R11 destined to loopback 0 of R12 should be load balanced via EIGRP as shown in
the exhibit
R11#traceroute 145.14.14.14
3. Routing Delivery
3.1. Source R14
4. Data Transport
1. If directly connect no problems, and if EIGRP neighbors normal, but can’t ping
145.14.14.14, mostly because of ACL. Check ACL for each router interface
NOTE: You can’t remove offset-list, prefix-list, distribute-list, route-map, PBR or ACL. Must
change the ACL behind the offset-list. If there is a bandwidth statement under interface, you
can remove it
ANS Q4 – EIGRP
# Device Commands Validations
1 Check Neighbor Status
R11 sh ip eigrp nei No neighbor between R14 and R13.
R12 No neighbor between R11 and R13
R13
R14
Fix R11
int e1/0
no ip authentication mode eigrp 145 md5
sh ip eigrp neighbors
Fix R13
int e/0
no ip address 145.67.89.66 255.255.255.252
ip address 145.67.89.6 255.255.255.252
R11
sh ip eigrp neighbors
Fix R12
int e1/0
no bandwidth 1000
Fix R13
int e1/0
no delay 1000
Fix R14
T Perform Testing
R11 sh ip eigrp topology all-
R13 links
R11 traceroute 145.14.14.14 It should show load balanced
R11 sh ip eigrp topology
145.14.14.14/32
Key Steps