The fact that you were able to ping r4's loopback from r1 unless sourced from
its loopback0 leads me tp believe that r4 didn't have a route for 200.0.0.1.
Also in looking over the lab tasks you should not have had a network statement
for r1's loopback0 which should have been redistributed via a connected
statement.
Possibly no way to know now since this was almost 24 hrs ago. Let us know if
you figure out the cause
Sent from my T-Mobile myTouch 3G Slide
----- Reply message -----
From: "Nilesh Mehta" <[email protected]>
Date: Sun, Oct 10, 2010 1:52 pm
Subject: [OSL | CCIE_RS] WB1 - LAB9 task 22
To: "Di Bias, Steve" <[email protected]>
Cc: "[email protected]" <[email protected]>
I do not have output from R1 now but I am pretty sure there was network
statement for 200.0.0.1.on R1 and I was able to ping 200.0.0.1 from all other
routers through tcl script and .
after redistbution I should be able to see 200.0.0.1 route on R4 which I was
not able to see.
On Sat, Oct 9, 2010 at 9:21 PM, Di Bias, Steve
<[email protected]<mailto:[email protected]>> wrote:
Also please post the output from R1
show run | section eigrp
make sure you have a network statement for 200.0.0.1
From:
[email protected]<mailto:[email protected]>
[mailto:[email protected]<mailto:[email protected]>]
On Behalf Of Di Bias, Steve
Sent: Saturday, October 09, 2010 9:17 PM
To: Nilesh Mehta;
[email protected]<mailto:[email protected]>;
[email protected]<mailto:[email protected]>;
[email protected]<mailto:[email protected]>
Subject: Re: [OSL | CCIE_RS] WB1 - LAB9 task 22
Are you seeing a route back to R1’s loopback on R4? Is R1 routing for this
loopback?
On R4 run show ip route 200.0.0.1
Steve
From:
[email protected]<mailto:[email protected]>
[mailto:[email protected]<mailto:[email protected]>]
On Behalf Of Nilesh Mehta
Sent: Saturday, October 09, 2010 9:03 PM
To: [email protected]<mailto:[email protected]>;
[email protected]<mailto:[email protected]>;
[email protected]<mailto:[email protected]>
Subject: [OSL | CCIE_RS] WB1 - LAB9 task 22
I was working on task 22 lab 9 and redistributation between eigrp 1001 and
eigrp 2004 did not work on R2 and R4
I have same config as per DSG. but I was not able to ping 200.0.0.4 if I
sourced from Lo0of R1. I started debug but did not get much useful info. Here
is the config for R2/R4 not sure what I am missing.
R2#sh run | s ei
no ip split-horizon eigrp 1001
router eigrp 1001
timers active-time 2
redistribute connected metric 100000 100 255 1 1500 route-map eigrp-connect
redistribute eigrp 2004
passive-interface default
no passive-interface GigabitEthernet0/0
no passive-interface Serial0/1/0.24
no passive-interface Serial0/1/0.256
no passive-interface Serial0/2/0
offset-list 2 in 20000000 Serial0/2/0
network 0.0.0.0
maximum-paths 1
default-metric 1 1 1 1 1
no auto-summary
router eigrp 2004
timers active-time 2
redistribute eigrp 1001
passive-interface default
no passive-interface Serial0/1/0.24
network 150.100.12.0 0.0.0.255
network 150.100.24.0 0.0.0.255
network 150.100.25.0 0.0.0.255
network 150.100.100.0 0.0.0.255
network 200.0.0.2 0.0.0.0
default-metric 1 1 1 1 1
no auto-summary
eigrp stub connected
route-map eigrp-connect permit 10
match interface Loopback0
----------------------------------------------------------------
R4#sh run | s ei
router eigrp 2004
passive-interface default
no passive-interface Serial0/0/0
network 150.100.24.0 0.0.0.255
network 150.100.40.0 0.0.0.255
network 150.100.41.0 0.0.0.255
network 200.0.0.4 0.0.0.0
no auto-summary
eigrp stub connected
route-map eigrp-connect permit 10
match interface Loopback0
==========================================================
R1#ping 200.0.0.4
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 200.0.0.4, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/60 ms
R1#ping 200.0.0.4 so lo0
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 200.0.0.4, timeout is 2 seconds:
Packet sent with a source address of 200.0.0.1
.....
Success rate is 0 percent (0/5)
R1#
UHS Confidentiality Notice: This e-mail message, including any attachments, is
for the sole use of the intended recipient(s) and may contain confidential and
privileged information. Any unauthorized review, use, disclosure or
distribution of this information is prohibited, and may be punishable by law.
If this was sent to you in error, please notify the sender by reply e-mail and
destroy all copies of the original message.
UHS Confidentiality Notice: This e-mail message, including any attachments, is
for the sole use of the intended recipient(s) and may contain confidential and
privileged information. Any unauthorized review, use, disclosure or
distribution of this information is prohibited, and may be punishable by law.
If this was sent to you in error, please notify the sender by reply e-mail and
destroy all copies of the original message.
UHS Confidentiality Notice: This e-mail message, including any attachments, is
for the sole use of the intended recipient (s) and may contain confidential and
privileged information. Any unauthorized review, use, disclosure or
distribution of this information is prohibited. If this was sent to you in
error, please notify the sender by reply e-mail and destroy all copies of the
original message.
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
