EIGRP Practice Lab - For CCNP/CCIP/CCDP ROUTE Candidates (With Video Solutions)

PHYSICAL TOPOLOBY

LOGICAL TOPOLOBY 

Lab Task List

IOS Details

http://www.4shared.com/rar/VubK319Q/EIGRP_GNS.html

GNS Project File

Initial Configurations:
###################

R1
===

!
en
!
conf t
!
no cdp run
!
ho R1
!
no ip do lo
!
int lo0
 ip add 1.1.1.1 255.255.255.255
 exit
!
int s0/0
 encap frame
 ip add 123.0.0.1 255.255.255.0
 no frame inv
 frame map ip 123.0.0.2 102 b
 frame map ip 123.0.0.3 103 b
 frame map ip 123.0.0.1 102
 no sh
 exit
!
line con 0
 logging syn
 no exec-time
!
end
!

##########################################


R2
==

!
en
!
conf t
!
no cdp run
!
ho R2
!
no ip do lo
!
int lo0
 ip add 2.2.2.2 255.255.255.255
 exit
!
int s0/0
 encap frame
 ip add 123.0.0.2 255.255.255.0
 no frame inv
 frame map ip 123.0.0.1 201 b
 frame map ip 123.0.0.3 201
 frame map ip 123.0.0.2 201
 no sh
 exit
!
int s0/1
 encap frame
 ip add 205.0.0.2 255.255.255.0
 no frame inv
 frame map ip 205.0.0.5 205 b
 frame map ip 205.0.0.2 205
 no sh
 exit
!
int f0/0
 ip add 150.0.0.2 255.255.255.0
 no sh
 exit
!
int f0/1
 ip add 26.0.0.2 255.255.255.0
 no sh
 exit
!
int f1/0
 ip add 25.0.0.2 255.255.255.0
 no sh
 exit
!
line con 0
 logging syn
 no exec-time
!
end
!



##########################################


R3
===


!
en
!
conf t
!
no cdp run
!
ho R3
!
no ip do lo
!
int lo0
 ip add 3.3.3.3 255.255.255.255
 exit
!
int s0/0
 ip add 123.0.0.3 255.255.255.0
 encap frame
 no frame inv
 frame map ip 123.0.0.1 301 b
 frame map ip 123.0.0.2 301
 frame map ip 123.0.0.3 301
 no sh
 exit
!
line con 0
 logging syn
 no exec-time
!
end
!


##########################################

R4
===

!
en
!
conf t
!
no cdp run
!
ho R4
!
no ip do lo
!
int lo0
 ip add 4.4.4.4 255.255.255.255
 exit
!
int f0/0
 ip add 150.0.0.4 255.255.255.0
 no sh
 exit
!
int f0/1
 ip add 46.0.0.4 255.255.255.0
 no sh
 exit
!
int f1/0
 ip add 45.0.0.4 255.255.255.0
 no sh
 exit
!
line con 0
 logging syn
 no exec-time
!
end
!


##########################################


R5
===

!
en
!
conf t
!
no cdp run
!
ho R5
!
no ip do lo
!
int lo0
 ip add 5.5.5.5 255.255.255.255
 exit
!
int f0/0
 ip add 150.0.0.5 255.255.255.0
 no sh
 exit
!
int f0/1
 ip add 25.0.0.5 255.255.255.0
 no sh
 exit
!
int f1/0
 ip add 45.0.0.5 255.255.255.0
 no sh
 exit
!
line con 0
 logging syn
 no exec-time
!
end
!

##########################################


R6
===


!
en
!
conf t
!
no cdp run
!
ho R6
!
no ip do lo
!
int lo0
 ip add 6.6.6.6 255.255.255.255
 exit
!
int f0/0
 ip add 150.0.0.6 255.255.255.0
 no sh
 exit
!
int f0/1
 ip add 46.0.0.6 255.255.255.0
 no sh
 exit
!
int f1/0
 ip add 26.0.0.6 255.255.255.0
 no sh
 exit
!
line con 0
 logging syn
 no exec-time
!
end
!

Solution Videos

 TASK 1& 2 Solution

TASK 3 Solution

TASK 4 Solution

TASK 5 Solution

TASK 6 Solution

TASK 7 Solution

TASK 8 Solution

TASK 9 Solution

TASK 10 Solution

TASK 11 Solution

TASK 12 Solution

TASK 13 Solution

TASK 14 Solution

TASK 15 Solution

HTH...
Deepak Arora
Evil CCIE

Etherchannel Bundle Combinations - The Road To Success

Every once in a while I see Networking people debating and discussing about why ether channel is not coming up or asking if particular ether channel settings combination is gonna work. So below is the quick ref considering all possible combinations :

Further Readings:

http://blog.ipexpert.com/2009/12/23/explaining-etherchannel/

http://www.cisco.com/en/US/tech/tk389/tk213/technologies_tech_note09186a0080094714.shtml

http://blog.ipexpert.com/2010/07/12/etherchannel-over-dot1q-tunnels/

http://cciepursuit.wordpress.com/2007/10/06/port-channel-interface-charactoristics/


http://packetlife.net/blog/2010/jan/18/etherchannel-considerations/


http://packetlife.net/blog/2009/dec/10/etherchannel-costs-and-failover/


HTH...
Deepak Arora
Evil CCIE

CCIE R&S Routing Study Plan - IPv4

Every once in a while I get this request to write a CCIE R&S Routing Study Plan similar to CCIE R&S Switching study plan :

http://deepakarora1984.blogspot.com/2010/03/ccie-r-switching-study-plan.html

So lets list all routing topics and allow me to list my attack plan for each of those starting with RIP today... I'll keep adding for rest soon...

1. RIPv2

2. EIGRP

3. OSPF

4. BGP

5. REDISTRIBUTION

6. Learning each of above mentioned routing protocol from MPLS prospective.

Misc :

1. ODR

2. PBR

3. OER/PFR

4. Understanding CEF & IOS Switching

5. Understanding Load Sharing Vs Load Balancing

6. Protocol independent features

So lets begin with RIP for today :)

  RIP

####

1. INE R&S ATC VODs RIP Lectures 

http://www.ine.com/self-paced/ccie-routing-switching/bootcamps/ccie-routing-switching-advanced-technologies-class.htm

2. Jeff Doyle's TCP/IP Vol 1(2nd Edition) 

Two Chapters Just Talking about RIP along with some very good corner case scenarios. Technically one chapter talks about RIPv1 which is not on blueprint but still a good read to grasp fundamentals.

Make sure you test all RIP labs given in this book along the way.

3. Read about RIP from Ruhann's R&S Handbook :

http://routing-bits.com/handbook-for-rs/

4. Enough Theory ? .... Not yet :) ... Move onto RIP Technology Page

 http://www.cisco.com/en/US/tech/tk365/tk554/tsd_technology_support_sub-protocol_home.html

5. Okay... Enough Theory...Time to get some hands dirty with RIP Labs.

Alternatively you can follow any good R&S workbook vendor's RIP Technology Labs like - INE (www.ine.com) , IP Expert (www.ipexpert.com) Or Narbik (www.micronicstraining.com) ...Whatever works best for you

6. Some important blog posts.

http://deepakarora1984.blogspot.com/2010/08/rip-challenge-1-solve-puzzle.html

http://deepakarora1984.blogspot.com/2010/08/rip-challenge-1-solution.html

http://deepakarora1984.blogspot.com/2010/10/rip-mock-lab-finalcoming-soon.html

http://deepakarora1984.blogspot.com/2010/10/rip-configuration-mock-lab-final.html

http://ardenpackeer.com/routing-protocols/mock-lab-6-analysis-rip-summary-address-and-default-routes/

http://ardenpackeer.com/routing-protocols/tutorial-troubleshooting-split-horizon-issues-part-1/

http://ardenpackeer.com/routing-protocols/tutorial-troubleshooting-split-horizon-issues-part-2/

7. Enough ? :)... Not Yet... Lets move to final phase and read through IOS 12.4T RIP configuration & command reference guides along with 12.4 T IOS Independent Feature Guide/Command Ref and make sure next time you know where to find what.

http://www.cisco.com/en/US/docs/ios-xml/ios/iproute_rip/configuration/12-4t/irr-12-4t-book.html

http://www.cisco.com/en/US/docs/ios-xml/ios/iproute_rip/command/irr-cr-book.html

http://www.cisco.com/en/US/docs/ios-xml/ios/iproute_pi/configuration/12-4t/iri-12-4t-book.html

http://www.cisco.com/en/US/docs/ios-xml/ios/iproute_pi/command/iri-cr-book.html

8. Though by this time you should be good with RIP troubleshooting as well, but just to add one extra bit, INE R&S Troubleshooting Class On Demand is an excellent resource to prepare for this part.

http://www.ine.com/self-paced/ccie-routing-switching/bootcamps/ccie-routing-switching-advanced-troubleshooting-course.htm

HTH...

Deepak Arora

EVIL CCIE

EIGRP Practice Test - I scored 10/10...How much you gonna score ?

https://stormwind.adobeconnect.com/_a983809677/eigrprecall/

HTH...

Deepak Arora

EVIL CCIE

Free INE CCNP Workbook

Just got this URL today at IEOC.COM where Brian McGahan has provided download URL to INE CCNP Workbook. Though it was written for CCNP Ver 5. But contents are still relavant for current Route and Switch exams.

http://www.ine.com/downloads/ine.ccnp.lab.workbook.1.01.zip 

HTH...
Deepak Arora

MPLS VPN Troubleshooting - Bob Calling For Help !!!

Finally after a long gap I am back with my tutorials and labs for learning and fun. Few weeks back I posted MPLS VPN Lab topology, So before explaining it step by step I thought to bring it as challenge for people who already know MPLS from R&S lab prospective and are looking for some troubleshooting stuff on it. So I am going to bring today a MPLS VPN TS challenge for them.

So our old friend BOB was sitting free on monday after noon and then he received an email containing the following topology and two fault tickets.

The topology has got two different MPLS VPNs. One is VPN blue and another is VPN red. VPN blue site 1 should be able to reach VPN blue site 2 and vice versa and same case with VPN RED. But both VPNs shouldn't be able to talk to each other.


Below is the link to download initials for lab along with GNS topology and IOS version details to run it. See if you can help BOB with this problem.


BTW.... Avoid removing configurations completely. Also being a excellent engineer, don't use "sh run" to show your skills.


http://hotfile.com/dl/123139611/4ae9ec6/MPLS_VPN_LAB_final_config.rar.html

HTH...
Deepak Arora

IPv6 Introduction & Basic Theory

Today I am moving to next topic on my study chart which is IPv6. So In near future don't get surprised if you see many more posts talking about IPv6 and it's features.


But before that I would like to share this awesome IPv6 introduction document covering IPv6 basic theory and implementation. Document is little old so it might not be covering the latest and greatest information on IPv6 like removal of Site Local Addressing Space from RFC standard etc. But still a good read if you wan't to grasp information about future of IP and Networking.

www.ipv6-tf.com.pt/documentos/geral/cisco/ipv6_abc_Aug2002.pdf

So read through this document before I come up with more exiting posts on IPv6 in coming weeks. :-)

HTH...
Deepak Arora
CCIE - 0::0/0 Null0

Native VLAN Horror - Can you solve the puzzle ?

Around 2 years back there was section called "Resources" on NMC Website. Actually plenty of good documents were out there on different R&S blueprint topics. Some of them were my favorite one. They created some scenarios based on few simple things like "Native VLAN", "SPAN/RSPAN" etc which most of you might be thinking about...ehhh...that's easy stuff and I can do even in sleep :-)


But there is always major difference between "knowing about things" Vs "Knowing things inside out". Though it's quite a lot of hard work one needs to do to achieve "Perfection" but still it's doable.


Without saying anything further let me share on of those interesting scenarios to challenge your understandings :-)


Or what Scott Morris call is "abusing people technically and in exiting new ways" hehehe :-)


Here you go:

HTH...
Deepak Arora
CCIE - 0::0/0 Null0

Static Routing Myth - Exit Interface Vs Next Hop

Myth : It's been long time since I wanted to talk about this Myth which every CCNA deals with once in a while. It's a very common misconception that If we point two static routes for same destination with one being having next hop address vs other with exit interface; in such case load balancing will not occur. The reason given being is that the static route with exit interface option will show up in local routing table as "connected" and as we all know that connected has AD value of  "0" Vs static route pointing towards next hop with AD value of "1". So by that rule the route with exit interface wins over route with next hop and because of that load balancing won't occur.


Let's hop on to command line to verify whats going on. I am going to use two routers connected back to back using two WAN interfaces. We will create 1 loopback on each router as "x.x.x.x/24" where X =  Router Number.


After this we will point out one static route toward destination loopback of other router with same prefix length and then we will examine if load balancing is occurring for traffic or not.


Lets Hop on to routers and put the config:



R1(config)#int lo0

R1(config-if)#ip add 1.1.1.1 255.255.255.0
R1(config-if)#exit

R1(config)#int s0/0

R1(config-if)#ip add 12.12.12.1 255.255.255.0

R1(config-if)#no sh

R1(config-if)#exit

R1(config)#int s0/1

R1(config-if)#ip add 112.112.112.1 255.255.255.0

R1(config-if)#no sh

R1(config-if)#exit

R1(config)#ip route 2.2.2.0 255.255.255.0 12.12.12.2

R1(config)#ip route 2.2.2.0 255.255.255.0 serial 0/1

=====================================================

R2(config)#int lo0

R2(config-if)#ip add 2.2.2.2 255.255.255.0

R2(config-if)#no sh

R2(config-if)#exit

R2(config)#int s0/0

R2(config-if)#ip add 12.12.12.2 255.255.255.0

R2(config-if)#no sh

R2(config-if)#exit

R2(config)#int s0/1

R2(config-if)#ip add 112.112.112.2 255.255.255.0

R2(config-if)#no sh

R2(config-if)#exit

R2(config)#ip route 1.1.1.0 255.255.255.0 12.12.12.1

R2(config)#ip route 1.1.1.0 255.255.255.0 s0/1 

=====================================================

R1#sh ip ro | b ^G

Gateway of last resort is not set

     1.0.0.0/24 is subnetted, 1 subnets

C       1.1.1.0 is directly connected, Loopback0

     2.0.0.0/24 is subnetted, 1 subnets

S       2.2.2.0 [1/0] via 12.12.12.2

                is directly connected, Serial0/1

     112.0.0.0/24 is subnetted, 1 subnets

C       112.112.112.0 is directly connected, Serial0/1

     12.0.0.0/24 is subnetted, 1 subnets

C       12.12.12.0 is directly connected, Serial0/0

R2#sh ip ro | b ^G

Gateway of last resort is not set

     1.0.0.0/24 is subnetted, 1 subnets

S       1.1.1.0 [1/0] via 12.12.12.1

                is directly connected, Serial0/1

     2.0.0.0/24 is subnetted, 1 subnets

C       2.2.2.0 is directly connected, Loopback0

     112.0.0.0/24 is subnetted, 1 subnets

C       112.112.112.0 is directly connected, Serial0/1

     12.0.0.0/24 is subnetted, 1 subnets

C       12.12.12.0 is directly connected, Serial0/0

=====================================================

R1#debug ip packet detail

IP packet debugging is on (detailed)

R1#ping 2.2.2.2 so lo0 r 4 

Type escape sequence to abort.

Sending 4, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds:

Packet sent with a source address of 1.1.1.1 

!!!!

Success rate is 100 percent (4/4), round-trip min/avg/max = 4/5/8 ms

R1#

*Mar  1 00:11:24.651: IP: tableid=0, s=1.1.1.1 (local), d=2.2.2.2 (Serial0/0), routed via FIB < Packet 1

*Mar  1 00:11:24.651: IP: s=1.1.1.1 (local), d=2.2.2.2 (Serial0/0), len 100, sending

*Mar  1 00:11:24.651:     ICMP type=8, code=0

*Mar  1 00:11:24.655: IP: tableid=0, s=2.2.2.2 (Serial0/0), d=1.1.1.1 (Loopback0), routed via RIB

*Mar  1 00:11:24.655: IP: s=2.2.2.2 (Serial0/0), d=1.1.1.1, len 100, rcvd 4

*Mar  1 00:11:24.655:     ICMP type=0, code=0

*Mar  1 00:11:24.655: IP: tableid=0, s=1.1.1.1 (local), d=2.2.2.2 (Serial0/0), routed via FIB  < Packet 2

*Mar  1 00:11:24.655: IP: s=1.1.1.1 (local), d=2.2.2.2 (Serial0/0), len 100, sending

*Mar  1 00:11:24.655:     ICMP type=8, code=0

*Mar  1 00:11:24.663: IP: tableid=0, s=2.2.2.2 (Serial0/0), d=1.1.1.1 (Loopback0), routed via RIB

*Mar  1 00:11:24.663: IP: s=2.2.2.2 (Serial0/0), d=1.1.1.1, len 100, rcvd 4

*Mar  1 00:11:24.663:     ICMP type=0, code=0

*Mar  1 00:11:24.663: IP: tableid=0, s=1.1.1.1 (local), d=2.2.2.2 (Serial0/0), routed via FIB < Packet 3

*Mar  1 00:11:24.663: IP: s=1.1.1.1 (local), d=2.2.2.2 (Serial0/0), len 100, sending

*Mar  1 00:11:24.663:     ICMP type=8, code=0

*Mar  1 00:11:24.667: IP: tableid=0, s=2.2.2.2 (Serial0/0), d=1.1.1.1 (Loopback0), routed via RIB

*Mar  1 00:11:24.667: IP: s=2.2.2.2 (Serial0/0), d=1.1.1.1, len 100, rcvd 4

*Mar  1 00:11:24.667:     ICMP type=0, code=0

*Mar  1 00:11:24.667: IP: tableid=0, s=1.1.1.1 (local), d=2.2.2.2 (Serial0/0), routed via FIB < Packet 4

*Mar  1 00:11:24.667: IP: s=1.1.1.1 (local), d=2.2.2.2 (Serial0/0), len 100, sending

*Mar  1 00:11:24.667:     ICMP type=8, code=0

*Mar  1 00:11:24.671: IP: tableid=0, s=2.2.2.2 (Serial0/0), d=1.1.1.1 (Loopback0), routed via RIB

*Mar  1 00:11:24.671: IP: s=2.2.2.2 (Serial0/0), d=1.1.1.1, len 100, rcvd 4

*Mar  1 00:11:24.671:     ICMP type=0, code=0

=====================================================

Umm....Looks like CEF is not happy with us :-P Lets turn it off :-)

R1(config)#no ip cef

R1#ping 2.2.2.2 so lo0 r 4

Type escape sequence to abort.

Sending 4, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds:

Packet sent with a source address of 1.1.1.1 

!!!!

Success rate is 100 percent (4/4), round-trip min/avg/max = 4/5/8 ms

R1#

*Mar  1 00:12:25.703: IP: tableid=0, s=1.1.1.1 (local), d=2.2.2.2 (Serial0/0), routed via RIB< Packet 1

*Mar  1 00:12:25.703: IP: s=1.1.1.1 (local), d=2.2.2.2 (Serial0/0), len 100, sending

*Mar  1 00:12:25.703:     ICMP type=8, code=0

*Mar  1 00:12:25.707: IP: tableid=0, s=2.2.2.2 (Serial0/0), d=1.1.1.1 (Loopback0), routed via RIB

*Mar  1 00:12:25.707: IP: s=2.2.2.2 (Serial0/0), d=1.1.1.1, len 100, rcvd 4

*Mar  1 00:12:25.707:     ICMP type=0, code=0

*Mar  1 00:12:25.707: IP: tableid=0, s=1.1.1.1 (local), d=2.2.2.2 (Serial0/1), routed via RIB< Packet 2

*Mar  1 00:12:25.707: IP: s=1.1.1.1 (local), d=2.2.2.2 (Serial0/1), len 100, sending

*Mar  1 00:12:25.707:     ICMP type=8, code=0

*Mar  1 00:12:25.715: IP: tableid=0, s=2.2.2.2 (Serial0/0), d=1.1.1.1 (Loopback0), routed via RIB

*Mar  1 00:12:25.715: IP: s=2.2.2.2 (Serial0/0), d=1.1.1.1, len 100, rcvd 4

*Mar  1 00:12:25.715:     ICMP type=0, code=0

*Mar  1 00:12:25.715: IP: tableid=0, s=1.1.1.1 (local), d=2.2.2.2 (Serial0/0), routed via RIB

*Mar  1 00:12:25.715: IP: s=1.1.1.1 (local), d=2.2.2.2 (Serial0/0), len 100, sending < Packet 3

*Mar  1 00:12:25.715:     ICMP type=8, code=0

*Mar  1 00:12:25.719: IP: tableid=0, s=2.2.2.2 (Serial0/0), d=1.1.1.1 (Loopback0), routed via RIB

*Mar  1 00:12:25.719: IP: s=2.2.2.2 (Serial0/0), d=1.1.1.1, len 100, rcvd 4

*Mar  1 00:12:25.719:     ICMP type=0, code=0

*Mar  1 00:12:25.723: IP: tableid=0, s=1.1.1.1 (local), d=2.2.2.2 (Serial0/1), routed via RIB

*Mar  1 00:12:25.723: IP: s=1.1.1.1 (local), d=2.2.2.2 (Serial0/1), len 100, sending< Packet 4

*Mar  1 00:12:25.723:     ICMP type=8, code=0

*Mar  1 00:12:25.723: IP: tableid=0, s=2.2.2.2 (Serial0/0), d=1.1.1.1 (Loopback0), routed via RIB

*Mar  1 00:12:25.727: IP: s=2.2.2.2 (Serial0/0), d=1.1.1.1, len 100, rcvd 4

*Mar  1 00:12:25.727:     ICMP type=0, code=0

Everything seems to be in shape now :-)

R1#sh ip route 2.2.2.0

Routing entry for 2.2.2.0/24

  Known via "static", distance 1, metric 0 (connected)

  Routing Descriptor Blocks:

  * 12.12.12.2

      Route metric is 0, traffic share count is 1

    directly connected, via Serial0/1

      Route metric is 0, traffic share count is 1

so conclusion is that despite of how you configure the static route (Exit Interface Vs Next Hop), the AD is always going to be 1.

Though specifying next hop has some advantages over exit interface option on Multi Access network types. But personally I like to use what I call mix of both in which while adding static route you specify exit interface with next hop address. This way we can make sure that no route-recursion issue will occur. And if you are thinking " Route Recursion issues with Static routing - what the hack is that" ?..ummm....let me save it for my next post for CCNA guys :-)

here is the syntax BTW which I just talked about

R1(config)#ip route 2.2.2.0 255.255.255.0 s0/0 12.12.12.2

R1(config)#ip route 2.2.2.0 255.255.255.0 s0/1 112.112.112.2

Further Readings: 

http://www.thebryantadvantage.com/CCNACertificationExamTutorialStaticRoutesIPRouteCommand.htm

http://cciepursuit.wordpress.com/2007/07/09/the-administrative-distance-of-a-static-route-pointed-to-an-interface-is-not-zero/

https://learningnetwork.cisco.com/message/34352

HTH...

Deepak Arora