Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Problem with Traceroute output

Hello all,

I have a strange problem with my output's traceroute as shown below:

Could anyone tell me what's going on with the last 3 hops ?

bash-2.03$ traceroute 192.168.45.95

traceroute: Warning: Multiple interfaces found; using 192.168.154.248 @ eri0

traceroute to 192.168.45.95 (192.168.45.95), 30 hops max, 40 byte packets

1 r01 (192.168.154.1) 2.865 ms 1.350 ms 1.886 ms

2 192.168.154.251 (192.168.154.251) 2.423 ms 2.021 ms 2.014 ms

3 mrtr01 (192.168.232.253) 2.549 ms 2.569 ms 2.536 ms

4 192.168.45.95 (192.168.45.95) 3.797 ms 3.823 ms 3.677 ms

5 192.168.45.95 (192.168.45.95) 5.974 ms 5.935 ms 6.238 ms

6 192.168.45.95 (192.168.45.95) 8.274 ms 6.922 ms 6.793 ms

Thanks in advance.

8 REPLIES
New Member

Re: Problem with Traceroute output

Possible routing loop. But I am unsure never seen anything like it before. Good luck!!!

Re: Problem with Traceroute output

Hi

As mentioned by the other poster do check out the device which is configured with the ip 192.168.45.95..

Also if you need more assistance do post more about your topology and other connectivity details..

regds

Silver

Re: Problem with Traceroute output

It looks like there are multiple path to reach 192.168.45.95....

Re: Problem with Traceroute output

I will be looking for this answer

I have a similar problem across our MPLS cloud to only some particular destinations and the trace always shows the CE router twice

Tracing route to 172.16.119.4 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 172.16.110.3

2 * * * Request timed out.

3 1 ms 1 ms 1 ms 172.16.102.30

4 * * * Request timed out.

5 14 ms 11 ms 13 ms 192.168.172.30

6 14 ms 17 ms 18 ms 192.168.172.30

7 14 ms 12 ms 12 ms 172.16.119.4

HTH

Narayan

Re: Problem with Traceroute output

Hi

I have seen this when there is a Firewall coming in between . But Not sure for the reason for the same . Some Security experts can answer if they have found similarly.

regards

vanesh k

Re: Problem with Traceroute output

Vaneesh,

There are no firewalls in my MPLS cloud.

But these problems started when we migrated one of our redundant links to another location for POP redundnacy.

Narayan

New Member

Re: Problem with Traceroute output

hi ,

this could happen due to follwing reason

1] A possible routing loop becoz of remote network outage

2]Firewall blocking a particluar network and it's down.

3]Route loop due to wrong advertisement(network is down but other routers running routing protocol are advertising this network.

4]Convergence delay.

U may try any other traceing tools like ANT (in windows) or extended trace.

HTH

New Member

Re: Problem with Traceroute output

I have came across a similar problem because of the routing loop within our MPLS network. The issue was fixed after removing an extra route which was pointing to the CPE.

Rajesh

220
Views
0
Helpful
8
Replies
CreatePlease login to create content