Comments on: finding fault of Network Ping drop http://itknowledgeexchange.techtarget.com/itanswers/finding-fault-of-network-ping-drop/ Fri, 27 Nov 2009 20:07:05 +0000 http://wordpress.org/?v=2.6.2 By: Troy Tate http://itknowledgeexchange.techtarget.com/itanswers/finding-fault-of-network-ping-drop/#comment-65212 Troy Tate Tue, 07 Jul 2009 18:47:13 +0000 #comment-65212 Maybe the poster can also add information about switch models and OS versions. Then tools like Cisco's Network Assistant can look at the links/trunks between the switches. Maybe the poster can also add information about switch models and OS versions. Then tools like Cisco’s Network Assistant can look at the links/trunks between the switches.

]]> By: Troy Tate http://itknowledgeexchange.techtarget.com/itanswers/finding-fault-of-network-ping-drop/#comment-65211 Troy Tate Tue, 07 Jul 2009 18:44:54 +0000 #comment-65211 I was thinking vlan's and gateways between vlan. But you are correct. The switches will be transparent to pathping. I was thinking vlan’s and gateways between vlan. But you are correct. The switches will be transparent to pathping.

]]> By: BlankReg http://itknowledgeexchange.techtarget.com/itanswers/finding-fault-of-network-ping-drop/#comment-65202 BlankReg Tue, 07 Jul 2009 17:22:21 +0000 #comment-65202 That tool will not be much use here as these are switches, and PING only gives information about layer 3 devices on the route, switches appear transparent, so you will not get any path information, just the round trip time same as a 'normal' PING. I think that Pgreddy needs to check that spanning tree is running on all the switches. Then see if you get lost PING packets. However, remember that PING is not guaranteed, it has a low priority and can get dropped if the device is busy. If the network is quiet, out of office hours, then it should be reliable and any losses are usually due to spannign tree issues, or bad routes if the management of the switches is in a different subnet. That tool will not be much use here as these are switches, and PING only gives information about layer 3 devices on the route, switches appear transparent, so you will not get any path information, just the round trip time same as a ‘normal’ PING.

I think that Pgreddy needs to check that spanning tree is running on all the switches. Then see if you get lost PING packets. However, remember that PING is not guaranteed, it has a low priority and can get dropped if the device is busy. If the network is quiet, out of office hours, then it should be reliable and any losses are usually due to spannign tree issues, or bad routes if the management of the switches is in a different subnet.

]]>