source based trace route is not working

Unanswered Question
Jan 5th, 2009
User Badges:

Hi guys,


I am missing something here, need your help/advise on this.


From my LAN router I can do the trace route to my esrver located in another site. However from the same router, I am not able to do the source based trace route from one of its interface to same server. Could you tell me what I am missing here.


RouterA# trace 10.6.49.165

Type escape sequence to abort.

Tracing the route to 10.6.49.165


1 10.5.86.7 0 msec 4 msec 0 msec

2 10.3.18.3 4 msec 4 msec 4 msec

3 20.232.9.101 4 msec 92 msec 132 msec

4 20.232.6.41 36 msec 40 msec 40 msec

5 20.232.6.42 40 msec 40 msec 40 msec

6 10.6.6.20 80 msec 40 msec 44 msec

7 10.6.50.2 56 msec 60 msec 64 msec

8 10.6.49.165 60 msec 56 msec 48 msec


RouterA#trace ip

Target IP address: 10.6.49.165

Source address: 17.21.1.4

Numeric display [n]:

Timeout in seconds [3]:

Probe count [3]:

Minimum Time to Live [1]:

Maximum Time to Live [30]:

Port Number [33434]:

Loose, Strict, Record, Timestamp, Verbose[none]:

Type escape sequence to abort.

Tracing the route to 10.6.49.165


1 10.5.86.7 0 msec 4 msec 0 msec

2 10.3.18.3 4 msec 0 msec 4 msec

3 * * *

4 * *


Does the router 20.232.9.101 needs to have route for 17.21.1.4 subnet. It can reache routerA on its other interface IP address.


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Jon Marshall Mon, 01/05/2009 - 01:39
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 LAN, WAN

Mohammed


"Does the router 20.232.9.101 needs to have route for 17.21.1.4 subnet. It can reache routerA on its other interface IP address."


Looks like that is the case. Obviously the source address of 17.21.1.4 is not known to all the routers in the path to the destination.


Jon


Actions

This Discussion