1832987 Members
2843 Online
110048 Solutions
New Discussion

traceroute question

 
José Enrique González
Frequent Advisor

traceroute question

Hi:

I'm tracerounting from a box to another and this is what shows up:

s01:/> traceroute 161.196.180.21
traceroute to 161.196.180.21 (161.196.180.21), 30 hops max, 20 byte packets
1 cha-fe-0-0-00.gw.corpo.cantv.net (200.44.44.1) 0 ms 0 ms 0 ms
2 cha-vlan-4-00.gw.cantv.net (200.44.0.2) 1 ms 1 ms 1 ms
3 cnt-ge-7-2-00.core.cantv.net (200.44.43.205) 1 ms 1 ms 1 ms
4 172.16.65.2 (172.16.65.2) 1 ms 1 ms 1 ms
5 estadisticas.cortijos2-pb.int.cantv.net (161.196.180.21) 1 ms 1 ms 1 ms
6 estadisticas.cortijos2-pb.int.cantv.net (161.196.180.21) 47 ms 31 ms 19 ms
7 estadisticas.cortijos2-pb.int.cantv.net (161.196.180.21) 23 ms 11 ms 21 ms
s01:/>

Is it OK destination server (estadisticas) to show repeated at the end? It has just one lan card. What could it mean? Thanks it advance for your comments.
5 REPLIES 5
Steven E. Protter
Exalted Contributor

Re: traceroute question

You should not get those three duplicate entries at the end.

Are these results consistent?

If so, I'd conduct a little analysis, a look at /etc/rc.config.d/netconf

Check the switch/router configuration for irregularities, because this looks rather strange.

I'd make sure my version of traceroute is current and results are consistent in both directions.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
José Enrique González
Frequent Advisor

Re: traceroute question

That's what I'm getting in reverse traceroute:

[root@estadisticas /bin]# traceroute 200.44.44.227
traceroute to 200.44.44.227 (200.44.44.227), 30 hops max, 38 byte packets
1 161.196.180.1 (161.196.180.1) 0.736 ms 0.424 ms 0.492 ms
2 161.196.82.13 (161.196.82.13) 3.748 ms 3.342 ms 3.105 ms
3 cnt-fe-1-0-0-00.core.cantv.net (200.109.126.241) 4.056 ms 4.253 ms 3.407 ms
4 172.16.65.1 (172.16.65.1) 3.728 ms 5.115 ms 4.102 ms
5 cha-vlan-5-01.gw.cantv.net (200.44.43.203) 5.029 ms 4.081 ms 3.724 ms
6 s01.chacao-01-dii.int.cantv.net (200.44.44.227) 4.275 ms 5.713 ms 4.875 ms
7 s01.chacao-01-dii.int.cantv.net (200.44.44.227) 4.800 ms 7.771 ms 4.646 ms
[root@estadisticas /bin]#

Destination (s01) has 2 active lan cards
doug mielke
Respected Contributor

Re: traceroute question

It does look strange. Is this the result of network guys trying to raise throughput via multiple trunks incorrectly?
Brian Hackley
Honored Contributor

Re: traceroute question

Jose,
Does ping -o behave the same way?
-> Brian
Ask me about telecommuting!
Jeff Schussele
Honored Contributor

Re: traceroute question

Hi Jose,

You may want to specify which NIC the traceroute starts from - use

traceroute -i lanX dest_IP

Use the appropriate PPA for the command. traceroute was changed not too long ago such that it seems to use the first IP listed in an netstat -in output & that *may* not be where you want to originate from.

HTH,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!