LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices

Reply
 
Search this Thread
Old 08-24-2010, 03:07 PM   #1
BiFo
LQ Newbie
 
Registered: Aug 2010
Posts: 11

Rep: Reputation: 0
[Tcptraceroute/Traceroute/Ping] Windows VMs & Linux VMs


Hi!
The Scenario:
A Blade running VMWare with several Virtual Machines. Some of them running Windows 2003 Server and others running Red Hat 5.4.
The Blade is directy connected to a Cisco Switch that has several Cisco Switchs connected to it. To this point all was running perfectly fine.

A new Cisco Switch is purchased, configured and then the Blade and all the other Cisco Switchs are connected directly to this New Cisco Switch.
Something really strange begins to happen:
* PING fails from Linux Virtual Machines to all the Switchs except the New Cisco Switch.
* Traceroute/Tracert from Linux Virtual Machines to the New Cisco Switch never reaches the destination.
* PING succeded from Windows Virtual Machines to all the Switchs except the New Cisco Switch. Seems important to note that the FIRST PING made, fails.
* Tracert from Windows Virtual Machines to the New Cisco Switch reaches the destination in 2 Hops.

I start to investigate a little with Google and i found the Linux command "tcptraceroute".
The first time i use it to reach any of the old Routers i get something like this:
Code:
# tcptraceroute WWW.XXX.YYY.ZZZ
traceroute to WWW.XXX.YYY.ZZZ (WWW.XXX.YYY.ZZZ), 30 hops max, 40 byte packets
 1   (AAA.BBB.CCC.DDD)  1.399 ms  0.488 ms *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * *  (WWW.XXX.YYY.ZZZ)  2005.795 ms
27 HOPs to reach the destination? Thats confussing...
After doing that, making PING, Traceroute and Tracert from the Linux Virtual Machines to the same IP works fine and without errors.
I've run tcptraceroute from the Linux Virtual Machines to all the Switchs to make them work and now its all working fine!

However i cant understand two things:
1) Why the Linux Virtual Machines couldnt be able to PING or Traceroute to the old Switchs before running the tcptraceroute?
...and...
2) Why the tcptraceroute made 27 HOPs to reach a destination that should take only 2 HOPs?

Please any help would be really appreciated.

Thanks in advance,
Bye!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Ubuntu's Koala food mixes with Windows VMs LXer Syndicated Linux News 0 06-16-2010 02:30 PM
Using Xen VMs for Development & Testing of Supercomputer and HPC Cluster MPICH Apps Teo En Ming Linux - Virtualization and Cloud 0 10-30-2009 07:45 AM
LXer: Using Xen With LVM-Based VMs Instead Of Image-Based VMs (Debian Etch) LXer Syndicated Linux News 0 01-14-2009 09:20 PM
VAX/VMS to Linux Migration arpan_bansal Linux - Software 6 01-22-2007 06:26 AM
Linux Suse and VMs murshed Linux - Newbie 3 02-18-2002 10:42 AM


All times are GMT -5. The time now is 06:13 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration