Variable ping times through PowerConnect 3024

Question

Pinging from one Linux box to another Linux box through my PowerConnect 3024 results in a wide variety of ping times - all below 1ms, but still a wide variety, as you see below: PING 172.20.1.11 (172.20.1.11) 56(84) bytes of data. 64 bytes from 172.20.1.11: icmp_seq=1 ttl=64 time=0.340 ms 64 bytes from 172.20.1.11: icmp_seq=2 ttl=64 time=0.530 ms 64 bytes from 172.20.1.11: icmp_seq=3 ttl=64 time=0.464 ms 64 bytes from 172.20.1.11: icmp_seq=4 ttl=64 time=0.395 ms 64 bytes from 172.20.1.11: icmp_seq=5 ttl=64 time=0.329 ms 64 bytes from 172.20.1.11: icmp_seq=6 ttl=64 time=0.262 ms 64 bytes from 172.20.1.11: icmp_seq=7 ttl=64 time=0.195 ms 64 bytes from 172.20.1.11: icmp_seq=8 ttl=64 time=0.129 ms 64 bytes from 172.20.1.11: icmp_seq=9 ttl=64 time=0.194 ms 64 bytes from 172.20.1.11: icmp_seq=10 ttl=64 time=0.130 ms 64 bytes from 172.20.1.11: icmp_seq=11 ttl=64 time=0.565 ms 64 bytes from 172.20.1.11: icmp_seq=12 ttl=64 time=0.496 ms 64 bytes from 172.20.1.11: icmp_seq=13 ttl=64 time=0.432 ms 64 bytes from 172.20.1.11: icmp_seq=14 ttl=64 time=0.237 ms However, when I do this same ping between two Linux boxes on a cheap Linksys switch, I get the following: PING 192.168.1.100 (192.168.1.100) 56(84) bytes of data. 64 bytes from 192.168.1.100: icmp_seq=1 ttl=64 time=0.136 ms 64 bytes from 192.168.1.100: icmp_seq=2 ttl=64 time=0.142 ms 64 bytes from 192.168.1.100: icmp_seq=3 ttl=64 time=0.130 ms 64 bytes from 192.168.1.100: icmp_seq=4 ttl=64 time=0.141 ms 64 bytes from 192.168.1.100: icmp_seq=5 ttl=64 time=0.142 ms 64 bytes from 192.168.1.100: icmp_seq=6 ttl=64 time=0.130 ms 64 bytes from 192.168.1.100: icmp_seq=7 ttl=64 time=0.144 ms 64 bytes from 192.168.1.100: icmp_seq=8 ttl=64 time=0.144 ms 64 bytes from 192.168.1.100: icmp_seq=9 ttl=64 time=0.144 ms 64 bytes from 192.168.1.100: icmp_seq=10 ttl=64 time=0.145 ms 64 bytes from 192.168.1.100: icmp_seq=11 ttl=64 time=0.133 ms 64 bytes from 192.168.1.100: icmp_seq=12 ttl=64 time=0.144 ms 64 bytes from 192.168.1.100: icmp_seq=13 ttl=64 time=0.143 ms Any ideas on why this might be?

markf424 · Answer

Nothing? Does this seem trivial to most people, or isn't anyone else experiencing it? I'd love to hear something from Dell.

GregG1 · Answer

There are multiple factors that could influence this (managed vs. unmanaged, store-and-forward vs. cut-through/fragment-free switching methods, etc.). No performance issues have been reported on the 3024/3048 family using the latest firmware.   Note:  The forum should not be utilized for directly contacting Dell. See the 'PowerConnect-Managed Switches: PLEASE READ BEFORE POSTING' message for more information on proper use of the forum.

Networking General

Was this post helpful?