- summarize 172.16.0.0 on f1/0 & f0/0
FENIX(config-if)# ip summary-address eigrp 123 172.16.0.0 255.255.248.0 90
- either static route(cheat) or tune bandwidth (not cheat)
FENIX(config)#int f1/0
FENIX(config-if)#bandwidth 10000
could block 3.3.3.3 route from entering FENIX at f1/0 with a route map + distribute list, denying routes for 3.3.3.3 from 192.168.13.0.
- On Santiago configure on f0/0 & f1/0
Santiago(config-if)#ip summary-address eigrp 123 10.0.0.0 255.255.252.0 90
Santiago(config-if)#ip summary-address eigrp 123 10.0.4.0 255.255.252.0 90
-remove last config & on f0/0 & f1/0 on Santiago
Santiago(config-if)#ip summary-address eigrp 123 10.0.0.0 255.255.224.0 90
- just add static default route EIGRP should distribute it fine
COLE(config)#ip route 0.0.0.0 0.0.0.0 l0
you can block this out of f1/0 to ensure route is propagated in one direction
COLE(config)#ip access-list standard BLOCK
COLE(config-std-nacl)#deny 0.0.0.0
COLE(config-std-nacl)#permit any
+ apply in eigrp
COLE(config-router)#distribute-list out BLOCK f1/0
EIGRP Summarization
Scenario:
The owner of this network has been complaining about performance issues for awhile. You as the junior network engineer have just learned about summarization and the possible advantages this might bring to your network. It's up to you to bring summarize the networks and bring the glory back to the routers...
Goal:
- All IP addresses have been preconfigured for you.
- EIGRP AS123 has been preconfigured for you and is advertising all networks.
- There are plenty of loopbacks with IP addresses configurated for you to summarize.
- You are not allowed to use EIGRP auto-summarization.
- Ensure router Cole and Santiago only have a single 172.16.0.0 /21 entry in their routing table.
- Ensure router Fenix will send traffic for 3.3.3.3 towards router Santiago. Do not change the Administrative Distance or Metric(s) to achieve this.
-
Ensure router Fenix only sees 2 entries for the 10.0.0.0 network range.
10.0.0.0 /22 and 10.0.4.0 /22. - Further summarize the 10.0.0.0 /22 and 10.0.4.0 /22 network so router Fenix and Cole only see the 10.0.0.0 /19 entry in their routing table.
- Advertise a default route on router Cole towards router Fenix, you are not allowed to use the default-network command.
IOS:
c3640-jk9s-mz.124-16.bin
Topology:
You need to register to download the GNS3 Topology File. (Registration is Free!)

Video Solution:
- Related Articles
Comments (6)
-
Ollie 2011-07-20 17:47:45
-
ReneMolenaar 2011-07-21 00:17:27Hi Oliver,
You can finish this lab by using summaries only, no need for distribute-lists, route-maps, access-lists and so on.
I have the solution for this one on Youtube but I didn't add them to the site yet. If you want to see it check my youtube channel (youtube.com/gns3vault) or wait 24 hours and i'll make sure it's here.
Rene
-
ndmitri 2011-12-05 23:17:46Rene,
I am missing something here.
Why did router Fenix placed 'D 3.3.3.0/24 [90/158720] via 192.168.12.2, 00
0:11, FastEthernet0/0'route after receiving 'ip summary-address eigrp 123 3.3.0.0 255.255.0.0' from router Cole?Thank you.
-
ReneMolenaar 2011-12-09 20:42:02Hello Dmitri,
Routers will always prefer most specific prefixes.
When we configure a summary on router Cole on the FastEthernet0/0 interface it will no longer advertise 3.3.3.0/24. It will still advertise this prefix through it's FastEthernet1/0 interface.
Router Fenix will learn a more specific prefix (3.3.3.0/24) from router Santiago and will use this path.
-
rak 2012-05-14 23:15:18Learnt lot here. Thanks for the lab.
Regards
Rakesh
-
ReneMolenaar 2012-05-16 09:10:15your welcome & thanks.





