From: Huan Pham (huan.pham@valuenet.com.au)
Date: Fri Jan 04 2008 - 02:54:07 ARST
Hi Uyota
It is too early to indicate this is an IOS bug ;-)
Having a route to the destination subnet simply just indicates you have a
route toward it. Being able to ping from your router to a destination host,
involves ALL the intermediate nodes on your path that have route to the
destination. In addition, all the routers along the path must not drop the
Ping packets (ICMP).
So let's do a trace and see where you get lost. You can also go to all the
routers along the path and do sh ip route for destination subnet. Check ACL
that are applied to interface of all the routers along the path from the
source to destination. The destination router or host must also have a route
back to source.
Cheers,
Huan
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
uyota oyearone
Sent: Friday, 4 January 2008 3:34 PM
To: CCIE
Subject: ios bug OR am i missing something????
Hi Group,
I have a scenario here, an having problems ping a remote site, although it
shows on the
Routing table, I still cant ping. could this possibly be an ios bug ? i
tried
debug to no avail
R2#sh ip route
B 155.1.4.0 [200/0] via 155.1.12.1, 00:03:37
R2#sh ip bgp
Network Next Hop Metric LocPrf Weight Path
*>i155.1.4.0/24 155.1.12.1 0 100 0 3 i
R2#ping 155.1.4.4
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to timeout is 2 se...
.....
Success rate is 0 percent (0/5)
This archive was generated by hypermail 2.1.4 : Fri Feb 01 2008 - 10:37:57 ARST