Verifying network performance using PINGs can be very misleading. Operating systems usually delay answering to ping packets to a certain amount of time, mostly if they are busy. Thus, you should correctly only compare pings to the same machine, not pings in general.
Unfortunately, the ping is by far too unreliable to pinpoint the cause of a problem - or to even indicate that there is a problem in the first place. Do you also ecounter other, different connectivity problems with the VMWare machines, or are this slow pings the only indication of a supposed problem?
Nice to meet you here again. I was basically thinking about the same - pinging the host machine but I was aware of the fact that it would be an experiment under different conditions. If the pings remain erratic then it might be an indication of a deeper problem but if the pings will be nice and uniform, does that in any way move the issue further?
I think that the erratic pings alone are somewhat disconcerting but this requires more information and more symptoms to pinpoint what is going on - and whether there is something going on at all. With virtual machines, I tend to neglect similar nuances ;)
The reason I said to ping the host machine is I've seen issues when moving files across the network from VM. If the ping to the host machine is not consistent or with a high delay value, I would suggest to investigate the network (possible hardware also).
Thanks for your replay. ping responce varies erratically. And file copying is taking just too much time. we recently upgraded from 100 mbps switches to 3560 gigabit switches. Expecting speed should increase but in contrast access time has been increased. But ping responce is most of the times good <50 ms. Ideally it should be <1 ms. How can find out why there is so much delay even though we have new gigabit switches. All the interfaces are connected at 1000 mbps.
There are no input errors and no CRC.
Maximun link utilization is Rx 3/255 amd Tx 2/255. And queues of pending packets on any of the interfaces.
One thing I noticed that cpu utilization of the switch is 22 %. But earlier I had put this doubt on forum and got one link from cisco.com that states that cpu utilization can even be upto 50 % with minimum load.
Second thing i found out that out of many 3560 switches one switch is running PVST and all other are running IEEE STP ( that is default ). can this be the bottle neck ? .
Is there any way to find out why full network is so slow. Printing files on networks is taking redicuiously longer time.
Please share the experience to find the delay or to make sure that there is not problem from cisco network side. Can STP or any subnet duplication clashing cause such problem?
Can we find the how frames are travelling across the network? Something to tracert.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...