Home > IT Answers > Networking > finding fault of Network Ping drop
Pgreddy
15 pts.
0
Q:
finding fault of Network Ping drop
Network troubleshooting, Ping, Switches, Switch configuration, Network administration
I am having a bus topology network with OFC connected on ABCDEFGH switches. OFC SM link is followed from A to B to C to D to E to F to G to H to A one side and A to E with redudence line. When we ping all the switches one by one, there is no ping loss. But when all the swtiches are on, I find ping loss. Now I am unable to find the cause.
ASKED: Jul 6 2009  8:46 AM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
RELATED QUESTIONS
0
Labnuke99
26375 pts.
0
A:
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
  • AddThis Social Bookmark Button
pathping is an excellent troubleshooting utility to look at latency & packet loss along a path.

Usage: pathping [-g host-list] [-h maximum_hops] [-i address] [-n]
[-p period] [-q num_queries] [-w timeout] [-P] [-R] [-T]
[-4] [-6] target_name

Options:
-g host-list Loose source route along host-list.
-h maximum_hops Maximum number of hops to search for target.
-i address Use the specified source address.
-n Do not resolve addresses to hostnames.
-p period Wait period milliseconds between pings.
-q num_queries Number of queries per hop.
-w timeout Wait timeout milliseconds for each reply.
-P Test for RSVP PATH connectivity.
-R Test if each hop is RSVP aware.
-T Test connectivity to each hop with Layer-2 priority tags.
-4 Force using IPv4.
-6 Force using IPv6.

It’s not a gui but it does give very valuable information within a single utility about the path between a source & destination.

In the IT trenches? So am I - read my IT-Trenches blog
Last Answered: Jul 6 2009  11:45 AM GMT by Labnuke99   26375 pts.
  •   
0
0
RSS - Discussions Help
Discuss This Answer:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

BlankReg   11270 pts.  |   Jul 7 2009  5:22PM GMT

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.

 

Troy Tate   0 pts.  |   Jul 7 2009  6:44PM GMT

I was thinking vlan’s and gateways between vlan. But you are correct. The switches will be transparent to pathping.

 

Troy Tate   0 pts.  |   Jul 7 2009  6:47PM GMT

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.

 
0