Quantcast
Channel: VMware Communities : Popular Discussions - VI: VMware ESX® 3.0
Viewing all articles
Browse latest Browse all 60069

Ping to ESX/VM - is it normal?

$
0
0

Hi,

 

I just wanted to ask You guys one question about network things in VMWare. I noticed, that when I ping my ESX hosts by IP assigned to console, then response is as below:

 

Pinging IP_Address with 32 bytes of data:

 

Reply from IP_Address: bytes=32 time=1ms TTL=62

Reply from IP_Address: bytes=32 time=4ms TTL=62

Reply from IP_Address: bytes=32 time<1ms TTL=62

Reply from IP_Address: bytes=32 time<1ms TTL=62

Reply from IP_Address: bytes=32 time=10ms TTL=62

Reply from IP_Address: bytes=32 time=5ms TTL=62

Reply from IP_Address: bytes=32 time<1ms TTL=62

Reply from IP_Address: bytes=32 time=1ms TTL=62

Reply from IP_Address: bytes=32 time=10ms TTL=62

Reply from IP_Address: bytes=32 time=7ms TTL=62

Reply from IP_Address: bytes=32 time<1ms TTL=62

Reply from IP_Address: bytes=32 time=2ms TTL=62

Reply from IP_Address: bytes=32 time<1ms TTL=62

Reply from IP_Address: bytes=32 time=2ms TTL=62

Reply from IP_Address: bytes=32 time=9ms TTL=62

Reply from IP_Address: bytes=32 time=3ms TTL=62

Reply from IP_Address: bytes=32 time=1ms TTL=62

Reply from IP_Address: bytes=32 time=2ms TTL=62

Reply from IP_Address: bytes=32 time=1ms TTL=62

Reply from IP_Address: bytes=32 time=8ms TTL=62

Reply from IP_Address: bytes=32 time=1ms TTL=62

Reply from IP_Address: bytes=32 time<1ms TTL=62

Reply from IP_Address: bytes=32 time<1ms TTL=62

Reply from IP_Address: bytes=32 time=10ms TTL=62

Reply from IP_Address: bytes=32 time<1ms TTL=62

Reply from IP_Address: bytes=32 time=3ms TTL=62

Reply from IP_Address: bytes=32 time<1ms TTL=62

Reply from IP_Address: bytes=32 time=5ms TTL=62

Reply from IP_Address: bytes=32 time=4ms TTL=62

Reply from IP_Address: bytes=32 time<1ms TTL=62

Reply from IP_Address: bytes=32 time=39ms TTL=62

Reply from IP_Address: bytes=32 time=6ms TTL=62

Reply from IP_Address: bytes=32 time=4ms TTL=62

Reply from IP_Address: bytes=32 time=2ms TTL=62

Reply from IP_Address: bytes=32 time<1ms TTL=62

Reply from IP_Address: bytes=32 time=5ms TTL=62

Reply from IP_Address: bytes=32 time<1ms TTL=62

Reply from IP_Address: bytes=32 time=5ms TTL=62

Reply from IP_Address: bytes=32 time<1ms TTL=62

Reply from IP_Address: bytes=32 time=1ms TTL=62

Reply from IP_Address: bytes=32 time<1ms TTL=62

Reply from IP_Address: bytes=32 time=1ms TTL=62

Reply from IP_Address: bytes=32 time=1ms TTL=62

Reply from IP_Address: bytes=32 time=2ms TTL=62

Reply from IP_Address: bytes=32 time=3ms TTL=62

Reply from IP_Address: bytes=32 time<1ms TTL=62

Reply from IP_Address: bytes=32 time=6ms TTL=62

Reply from IP_Address: bytes=32 time=2ms TTL=62

Reply from IP_Address: bytes=32 time=5ms TTL=62

Reply from IP_Address: bytes=32 time=3ms TTL=62

Reply from IP_Address: bytes=32 time=9ms TTL=62

**********************************************************************************************************************************

When I ping from my PC server that is hosted by this ESX (pinged above) then it responds "normally" <1 or =1ms

 

Pinging Server_FQDN with 32 bytes of data:

 

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time=1ms TTL=126

Reply from Server_IP: bytes=32 time=2ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time=1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time=1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time=1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time=1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

Reply from Server_IP: bytes=32 time=1ms TTL=126

Reply from Server_IP: bytes=32 time=2ms TTL=126

Reply from Server_IP: bytes=32 time<1ms TTL=126

************************************************************

 

What can be the issue? Do You also have such problem? Maybe it is not a problem and such situation is very normal in VMWare?

 

Thanks in advance for any info regarding this matter.


Viewing all articles
Browse latest Browse all 60069

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>