iaep-acer#ping 204.118.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 204.118.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent, round-trip min/avg/max = 748/894/1052 ms
iaep-acer#ping 204.212.248.10
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 204.212.248.10, timeout is 2 seconds:
!!!!!
Success rate is 100 percent, round-trip min/avg/max = 480/551/648 ms
iaep-acer#ping www.ibm.com
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 204.146.46.133, timeout is 2 seconds:
!!!!!
Success rate is 100 percent, round-trip min/avg/max = 220/229/236 ms
iaep-acer#ping 204.118.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 204.118.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent, round-trip min/avg/max = 112/247/456 ms
iaep-acer#ping 204.212.248.10
Type escape sequence to abort.
***this is when i enable the 2500 on the other side******
Sending 5, 100-byte ICMP Echos to 204.212.248.10, timeout is 2 seconds:
UUUUU
Success rate is 0 percent
iaep-acer#
*** the router I'm at is an igs...**** ....it was working yesterday...
thanks,
rick osteen
It looks like the other router is some corrupting your route to
204.212.248.10. Your router still has a route to the destination
network, otherwise you would get '.'s instead of 'U's. So, your
router is sending it on to someone else who is confused.
Did you give it a little while for convergence to finish, especially
if you are using a distance vector routing protocol?
You may want to turn off the romote 2500, trace through to
204.212.248.10, print a copy of 'sh ip route' on all the routers that
you pass through, turn on the remote 2500, wait a few minutes, trace
again, print the routing tables and compare them. Look for routes
that have changed into weirdness.
I'm assuming that you've followed all the normal ip rules: no
duplicate or overlapping subnets, if distance vector routing: only one
mask per classful address and no discontiguous nets.
Fun problem! If you get it working, let me know the resolution!
Hope this helps.
Kennedy Clark
>thanks,
>rick osteen
Do you have a 'timers basic' parameter configured on your routers?
I've seen this type of thing happening when one router's timers basic
values are set differently from the others (or isn't configured at all
in that particular router).)
Dianne Cameron
Technical Specialist
Bank of Nova Scotia
Toronto, Ontario
Canada