Pings increase randomly to netgear switch
Quick little problem I have noticed.
We have a few Netgear FS726T switches. If I'm plugged into one directly and ping it, this is what happens:
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=47ms TTL=128
Reply from 10.4.0.10: bytes=32 time=82ms TTL=128
Reply from 10.4.0.10: bytes=32 time=123ms TTL=128
Reply from 10.4.0.10: bytes=32 time=167ms TTL=128
Reply from 10.4.0.10: bytes=32 time=208ms TTL=128
Reply from 10.4.0.10: bytes=32 time=249ms TTL=128
Reply from 10.4.0.10: bytes=32 time=293ms TTL=128
Reply from 10.4.0.10: bytes=32 time=336ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=19ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=24ms TTL=128
Reply from 10.4.0.10: bytes=32 time=78ms TTL=128
Reply from 10.4.0.10: bytes=32 time=93ms TTL=128
Reply from 10.4.0.10: bytes=32 time=132ms TTL=128
Reply from 10.4.0.10: bytes=32 time=163ms TTL=128
Reply from 10.4.0.10: bytes=32 time=207ms TTL=128
Reply from 10.4.0.10: bytes=32 time=248ms TTL=128
Reply from 10.4.0.10: bytes=32 time=289ms TTL=128
Reply from 10.4.0.10: bytes=32 time=333ms TTL=128
Reply from 10.4.0.10: bytes=32 time=374ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
As you can see pings randomly increase then return to 10ms (which should really be <1 ms)
Has anyone seen this sort of thing before?
This happens with no other computers connected to the switch. The switch is factory setup apart from us setting an ip for it.
On another note if I connect another machine to the switch and ping that, I get nice <1ms replies.
Cheers,
Paul.
We have a few Netgear FS726T switches. If I'm plugged into one directly and ping it, this is what happens:
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=47ms TTL=128
Reply from 10.4.0.10: bytes=32 time=82ms TTL=128
Reply from 10.4.0.10: bytes=32 time=123ms TTL=128
Reply from 10.4.0.10: bytes=32 time=167ms TTL=128
Reply from 10.4.0.10: bytes=32 time=208ms TTL=128
Reply from 10.4.0.10: bytes=32 time=249ms TTL=128
Reply from 10.4.0.10: bytes=32 time=293ms TTL=128
Reply from 10.4.0.10: bytes=32 time=336ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=19ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=24ms TTL=128
Reply from 10.4.0.10: bytes=32 time=78ms TTL=128
Reply from 10.4.0.10: bytes=32 time=93ms TTL=128
Reply from 10.4.0.10: bytes=32 time=132ms TTL=128
Reply from 10.4.0.10: bytes=32 time=163ms TTL=128
Reply from 10.4.0.10: bytes=32 time=207ms TTL=128
Reply from 10.4.0.10: bytes=32 time=248ms TTL=128
Reply from 10.4.0.10: bytes=32 time=289ms TTL=128
Reply from 10.4.0.10: bytes=32 time=333ms TTL=128
Reply from 10.4.0.10: bytes=32 time=374ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
Reply from 10.4.0.10: bytes=32 time=10ms TTL=128
As you can see pings randomly increase then return to 10ms (which should really be <1 ms)
Has anyone seen this sort of thing before?
This happens with no other computers connected to the switch. The switch is factory setup apart from us setting an ip for it.
On another note if I connect another machine to the switch and ping that, I get nice <1ms replies.
Cheers,
Paul.
ASKER
Tried 5 different cables, ranging from 1 metre to 5 metres. Same problem.
Jasonr0025 had a good suggestion. I would say something is flooding the network. Have you tried a different switch with the same patch cable and computer? If the problem does not follow you to a new switch I would say you have a bad switch. The other thing I would try (you probubly have already) is a different port on that switch. Also make sure you have updated to the latest firmware for that switch. You can find the latest firmware at: http://kbserver.netgear.com/products/FS726T.asp
You could also have a bad network card in that PC since the problem disapears with another machine. Do you have another network card you could try in that same machine?
You could also have a bad network card in that PC since the problem disapears with another machine. Do you have another network card you could try in that same machine?
ASKER
I have the exact same problem with 9 switches of the same model (Netgear FS726T).
All switches have been upgraded to the latest firmware using their utility + downloaded from the website.
I have tried multiple ports on the switch.
I have tried a number of client computers.
I'm wondering if this is a flaw in the design of the switch perhaps... if anyone else out there has this problem with a netgear smart switch..
All switches have been upgraded to the latest firmware using their utility + downloaded from the website.
I have tried multiple ports on the switch.
I have tried a number of client computers.
I'm wondering if this is a flaw in the design of the switch perhaps... if anyone else out there has this problem with a netgear smart switch..
Seems to be a managed sw. with spanning tree capability.
http://www.netgear.com/upload/product/fs726t/enus_ds_fs726t.pdf
Suppose you have a loop in your network.
If then spt is enabeled the spt protocol will then try to avoid the the broadcast storm by blocking one of the ports.
From time to time spt will try to find out if the loop has gone away by opening the blocked port.
If this is the case the ping replytime will grow from time to time.
So look for network loops.
http://www.netgear.com/upload/product/fs726t/enus_ds_fs726t.pdf
Suppose you have a loop in your network.
If then spt is enabeled the spt protocol will then try to avoid the the broadcast storm by blocking one of the ports.
From time to time spt will try to find out if the loop has gone away by opening the blocked port.
If this is the case the ping replytime will grow from time to time.
So look for network loops.
On the other hand you mentioned 'random'
I guess SPT would have a regular pattern, perhaps opening up every 2 min. or so.
I guess SPT would have a regular pattern, perhaps opening up every 2 min. or so.
ASKER
This is a lone switch connected to a lone computer... a loop is not possible.. STP is disabled.
Sorry for reading your org. q. with wide closed eyes 8-)
So you are connecting to the management IP of the sw.
In this sw. there must be a CPU and management program running, including webserver, collecting and computing stats etc.
It seems these programs have some sort of routine of sometimes 'atentive listening (incl. responding ping)' and somtimes 'doing other stuff ' .
If you can watch the CPU somehow, there could be up and downs here as well.
I would be concerned if ping between ports seemed to be a problem.
So you are connecting to the management IP of the sw.
In this sw. there must be a CPU and management program running, including webserver, collecting and computing stats etc.
It seems these programs have some sort of routine of sometimes 'atentive listening (incl. responding ping)' and somtimes 'doing other stuff ' .
If you can watch the CPU somehow, there could be up and downs here as well.
I would be concerned if ping between ports seemed to be a problem.
Have you considered the environmental contiditions?
Microwave ovens? 2.4 or 5.8 ghz phones? cellular phones?
Speakers or other magnetic sources?
Are all electrical divices in the equation properly grounded to an *EARTH GROUNDED* ground outlet?
Have you tested the outlets with a ground fault test plug?
Are the outlets in use orange? (indicating that they are 'clean' power)?
Have you tried connecting the computer to the switch with both the pc and the switch connected to a UPS to check if it is because of voltage spikes/hollows in your AC power?
Hope this helps
-- Chris
Microwave ovens? 2.4 or 5.8 ghz phones? cellular phones?
Speakers or other magnetic sources?
Are all electrical divices in the equation properly grounded to an *EARTH GROUNDED* ground outlet?
Have you tested the outlets with a ground fault test plug?
Are the outlets in use orange? (indicating that they are 'clean' power)?
Have you tried connecting the computer to the switch with both the pc and the switch connected to a UPS to check if it is because of voltage spikes/hollows in your AC power?
Hope this helps
-- Chris
ASKER
I'm just trying to determine whether ICMP is actually usable on these netgear switches as a tool for testing my network... If I have another machine on the switch, I can ping through the switch and it is <1ms... But really the switch should be replying with that too- just screams out something is wrong to me.
Say you do a traceroute
switch 12 17 12
pc <1 <1 <1
Or when setup through our netgear L3 Managed switched (GSM7312)
smartswitch 15 10 9
l3switch 12 17 30
smartswitch 19 17 23
pc <1 <1 <1
Seems to be a problem with a few netgear switches.....
I have not tested outlets with a ground fault plug, the power outlets are not filtered, however our power is quite clean here as far as I know (have no issues with any other equipment). I'm afraid that I will test on a UPS and find the same result. I have tried these switches in a number of buildings (different grounds and power links) with the same problem.
Thanks,
Paul.
Say you do a traceroute
switch 12 17 12
pc <1 <1 <1
Or when setup through our netgear L3 Managed switched (GSM7312)
smartswitch 15 10 9
l3switch 12 17 30
smartswitch 19 17 23
pc <1 <1 <1
Seems to be a problem with a few netgear switches.....
I have not tested outlets with a ground fault plug, the power outlets are not filtered, however our power is quite clean here as far as I know (have no issues with any other equipment). I'm afraid that I will test on a UPS and find the same result. I have tried these switches in a number of buildings (different grounds and power links) with the same problem.
Thanks,
Paul.
H4Inf,
The only thing you can do to be sure about what is happening is to look at what is happening over the wire. We can all guess all day but in the end you will need to do take a look.
The product I recomend is Wireshark, it is the same thing as Ethereal, just a new name and updated versions. Go to the page below, download and install this application. You will want to try running it from the same port you were attached to and just let it capture for a while, so you can get the pattern a couple of times. When you are done you can look at the results and see what might be happening. You will even get some imporntant clues about who is involved.
http://www.wireshark.org/
Jon
The only thing you can do to be sure about what is happening is to look at what is happening over the wire. We can all guess all day but in the end you will need to do take a look.
The product I recomend is Wireshark, it is the same thing as Ethereal, just a new name and updated versions. Go to the page below, download and install this application. You will want to try running it from the same port you were attached to and just let it capture for a while, so you can get the pattern a couple of times. When you are done you can look at the results and see what might be happening. You will even get some imporntant clues about who is involved.
http://www.wireshark.org/
Jon
yep. that was my next recomendation.
Wireshark will be able to tell you what traffic is hitting the NIC of the PC, which should tell you what is going on network-wise.
Wireshark will be able to tell you what traffic is hitting the NIC of the PC, which should tell you what is going on network-wise.
ASKER
Having just spoken with a Netgear engineer, he says that ping packets are of no priority compared to everything else... This is just normal.. Although from my point of view this is really quite poor of them to design it this way - not very good for troubleshooting.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
hth
Jason