GNS3 Lab & Exercise: CCNA - CCNP ROUTE - EIGRP Lab
Written by LBSources from http://www.gns3-labs.com on March 18th, 2010 | 16 CommentsSo as expected - we’re going to start seeing some folks rolling out labs that are based on the new CCNP track topologies. This new submission comes from Steve - He turned multiple CCNP ROUTE study exercises into a full EIGRP lab exercise as best as he can while covering almost everything possible in regards to EIGRP configuration. Definitely a FULL EIGRP lab giving some great practice to candidates of CCNA, CCNP and even CCIE 
Thanks Steve..
Topology:
- 2 Core routers
- 2 Wan routers (Wan/core a linked through a switch)
- 3 Branch routers, each having a Frame-Relay PVC to each Wan Router.
All routers are 2691 used with IOS c2691-adventerprisek9-mz.124-5a.bin
(7x 192Mo)
EIGRP Topics covered:
- Basic EIGRP config
- Dynamic Neighborship
- Auto-summary issues
- Split-horizon
- Neighborship settings (hello-timer, hold-timer eigrip RID)
- Static neighborship
- EIGRP authentication
- Passive interface
- Interface bandwidth over frame-relay
- EIGRP bandwidth usage
- Stub routers
- Offset-list
Usage of that feature in the lab is not the best solution to solve the
issue i mentioned in the lab
but at least it’s an occasion to configure it, to analyze EIGRP RD/FD
and to see the effect of such settings.
- Variance
- Default-route/network
- EIGRP Summarization
- Route filtering (prefix-list / route-map)
You’ll find 2 archives .. one with basic config (hostname, interface
config etc), and the second with the full config of the lab.
Both contain the PNG file. Explanations can be fond in each lab and on
the PNG file too.
Steve
Routers Used: 2691
IOS: c2691-adventerprisek9-mz.124-5a
Feature of Topology: Basic EIGRP, Dynamic Neighbors, Auto-summary, Split-horizon, Neighbor settings (hello-timer, hold-timer, EIGRP RID, Static neighbors, EIGRP authentication, Passive interface, Interface bandwidth over frame-relay, EIGRP bandwidth usage, Stub routers, Offset-list, Variance, Default-route/network, Summarization, Route filtering (prefix-list / route-map)
Image: 
Download: GNS3 Lab & Exercise: CCNA - CCNP ROUTE - EIGRP Lab
12,597 viewsTags: CCNA, CCNP ROUTE, CCNP v6, EIGRP, Frame-Relay, GNS3 Lab and Exercise, GNS3 Topology
You can leave a response, or trackback from your own site.
Subscribe to GNS3 Labs :: Cisco Router Simulator Network Topologies
March 18th, 2010 at 12:37 pm
[...] Le deuxième était d’ensuite de le partager via gns3-labs.com. Ce qui est chose faite (voir l’article à propos du lab sur gns3-labs.com) et c’est aussi la raison pour laquelle les explicatifs contenu dans le lab sont entièrement [...]
March 20th, 2010 at 2:56 am
its good but i can note open it couse i don’t have IOS image for 2691 series please show me how to find its helpfully for me right now because soon i will in exam.
thanks
March 20th, 2010 at 9:00 am
Sorry - Thats not something I can help with - You can though change the .net file to use a different router
April 9th, 2010 at 10:10 pm
[...] from: GNS3 Lab & Exercise: CCNA – CCNP ROUTE – EIGRP Lab | GNS3 Labs … If you enjoyed this article please consider sharing [...]
May 7th, 2010 at 3:40 am
Awesome lab ! Thanks so much.
May 20th, 2010 at 1:36 am
Very cool lab, opened fine. Thanks
May 26th, 2010 at 10:29 am
Good day, I have installed GNS3, but I want to do a lab in my network OSPF (Router main, office router, Switch Core, Switch distribution and access switches), the problem I have is not as associate IOS Switch to the multilayer, which are in the GNS3.
I would appreciate your advice.
Attentively
Oreste Torres
ostorres@cantv.net
May 26th, 2010 at 10:44 am
Here is a list of what is missing with the 16 port switching module (NM-16ESW) for the 3725 in comparison to the 3550/3460 Catalyst switches in the CCIE lab.
Access Switch Device Manager (SDM) Template
ACL - Improved Merging Algorithm
ARP Optimization
BGP Increased Support of Numbered as-path Access Lists to 500
BGP Restart Neighbor Session After max-prefix Limit Reached
BGP Route-Map Continue Support for Outbound Policy
Clear Counters Per Port
DHCP Snooping
DHCP Snooping Counters
Diagnotics Options on bootup
ErrDisable Reactivation Per Port
ErrDisable timeout
EtherChannel
EtherChannel - Flexible PAgP
Etherchannel Guard
Fallback Bridging
Flex Link Bi-directional Fast Convergence
Flex Link VLAN Load-Balancing
Flex Links Interface Preemption
GOLD - Generic Online Diagnostics
IEEE 802.1ab, Link Layer Discovery Protocol
IEEE 802.1s - Multiple Spanning Tree (MST) Standard Compliance
IEEE 802.1s VLAN Multiple Spanning Trees
IEEE 802.1t
IEEE 802.1W Spanning Tree Rapid Reconfiguration
IEEE 802.1x - Auth Fail Open
IEEE 802.1x - Auth Fail VLAN
IEEE 802.1x - VLAN Assignment
IEEE 802.1x - Wake on LAN Support
IEEE 802.1x Authenticator
IEEE 802.1X Multi-Domain Authentication
IEEE 802.1x RADIUS Accounting
IEEE 802.1x with Port Security
IEEE 802.3ad Link Aggregation (LACP)
IEEE 802.3af Power over Ethernet
IGMP Fast Leave
IGMP Version 1
IGRP
IP Phone Detection Enhancements
IP Phone Enhancement - PHY Loop Detection
IPSG (IP Source Guard)
Jumbo Frames
L2PT - Layer 2 Protocol Tunneling
MAC Authentication Bypass
MLD Snooping
Multicast Etherchannel Load Balancing
NAC - L2 IEEE 802.1x
NAC - L2 IP
NAC - L2 IP with Auth Fail Open
Packet-Based Storm Control
Per Port Per VLAN Policing
Port Security
Port Security on Private VLAN Ports
Private VLANs
QoS Policy Propagation via Border Gateway Protocol (QPPB)
Rapid-Per-VLAN-Spanning Tree (Rapid-PVST)
Reduced MAC Address Usage
Remote SPAN (RSPAN)
Smart Port
Spanning Tree Protocol (STP) - Loop Guard
Spanning Tree Protocol (STP) - Portfast
Spanning Tree Protocol (STP) - PortFast BPDU Filtering
Spanning Tree Protocol (STP) - Portfast Support for Trunks
Spanning Tree Protocol (STP) - Root Guard
Spanning Tree Protocol (STP) - Uplink Load Balancing
SRR (Shaped Round Robin)
Standby Supervisor Port Usage
STP Syslog Messages
Switching Database Manager (SDM)
Trunk Failover
Trusted boundary (extended trust for CDP devices)
Unicast Mac Filtering
UniDirectional Link Detection (UDLD)
VLAN Access Control List (VACL)
VLAN Aware Port Security
Weighted Tail Drop (WTD)
June 2nd, 2010 at 3:28 am
[...] thì quyết định tự học tiếp CCNP. Gần đây mình có download về cái lab này :GNS3 Lab & Exercise: CCNA - CCNP ROUTE - EIGRP Lab | GNS3 Labs :: Cisco Router Simulator Networ… rồi dùng GNS3 thực tập trên đó. Điều thắc mắc của mình là sao router Wan2 [...]
June 9th, 2010 at 5:55 pm
Part 4. on this lab doesn’t really make sense to me. Anyone care to explain?
June 10th, 2010 at 11:50 am
@Drew, You sure this lab? I don’t see part 4
July 4th, 2010 at 3:13 am
I know what Drew means. I am stuck on this part, then again I’m terrible with frame relay and I’m sure that’s what the issue is. I looked at the resolved answers specifically for these interfaces on WAN1 and Branch1/2 and I am not seeing what is required.
Here is the question:
4 - Take a closer look at Branch1/2 routing tables. Both know routes to Branch3 but not for each other … why ? \n ( it’s a normal behavior at this time … why? ). Configure interface S0/0.1 on each Wan router so that Eigrp will advertise Branch1 route to Branch 2 .. and Branch2 toute to Branch 1.
Not sure how much further I can say without spoiling the lab for anyone. I’ll brush on my frame relay skills…
July 4th, 2010 at 3:50 am
Figured it out.
August 5th, 2010 at 7:14 am
Hello,
I’ve got question about configuration of bandwidth percentage use, as was stated we should use up to 32kbps, and in my opinion there should be added command:
ip bandwidth-percent eigrp 15 25
as it is 0.25 * 256/2(PVC) = 32
below is resolved part of Wan1 config without this configuration. Am I right?
!
interface Serial0/0.1 multipoint
bandwidth 256
ip address 193.10.25.1 255.255.255.0
ip authentication mode eigrp 15 md5
ip authentication key-chain eigrp 15 EIGRPLAB
no ip split-horizon eigrp 15
frame-relay interface-dlci 101
frame-relay interface-dlci 102
!
September 8th, 2010 at 7:53 am
@dziczek, that is what I did, I think it is correct.
In section 6 after removing branch 1/2/3 from the query process it is pointed out that core1 and core2 do not have wan2 anywhere in their eigrp topology tables. I understand the CIR makes wan1 the successor for all branches, however I do not understand why wan2 is not forwarding it’s topology table with the longer path through wan1 to the core routers. I can “sho ip eigrp topo” on wan2 and see the entries in the toplogy table via s0/0.1 & 2, what is the specific reason these paths are not on core1 and core2?
September 8th, 2010 at 8:50 am
Never mind, split horizon kicks in. I understand now.