Pinging with Fping and Collecting Ping Performance Data - Revision history

imported>Schoen.kevin at 17:57, 1 October 2020

2020-10-01T17:57:42Z

← Older revision		Revision as of 17:57, 1 October 2020
Line 1:		Line 1:
	Fping is a command line application that allows for data collection and recording of the ping command data. It is basically like Ping, but is better, and has more features and functions. The most important feature is to log pings with time and date stamps to a file. In addition, it provides an accurate millisecond calculation on the ping command. FPING also supports 64 bit operating systems.		Fping is a command line application that allows for data collection and recording of the ping command data. It is basically like Ping, but is better, and has more features and functions. The most important feature is to log pings with time and date stamps to a file. In addition, it provides an accurate millisecond calculation on the ping command. FPING also supports 64 bit operating systems.

	*Google "windows fping 3.0", ~~and download the FPING program.~~		*Google "windows fping 3.0", or use this link http://blog.perceptus.ca/2017/11/10/fping-windows-download-the-last-version/
	~~Extract and put it in~~ http://blog.perceptus.ca/2017/11/10/fping-windows-download-the-last-version/		Extract and put it in c:\fping

	==Limitations of Windows Based PC's for Reliable Ping Testing==		==Limitations of Windows Based PC's for Reliable Ping Testing==

imported>Schoen.kevin at 17:56, 1 October 2020

2020-10-01T17:56:47Z

← Older revision		Revision as of 17:56, 1 October 2020
Line 2:		Line 2:

	*Google "windows fping 3.0", and download the FPING program.		*Google "windows fping 3.0", and download the FPING program.
	Extract and put it in C:\fping		Extract and put it in http://blog.perceptus.ca/2017/11/10/fping-windows-download-the-last-version/

	==Limitations of Windows Based PC's for Reliable Ping Testing==		==Limitations of Windows Based PC's for Reliable Ping Testing==

imported>Schoen.kevin at 16:12, 28 April 2020

2020-04-28T16:12:58Z

← Older revision		Revision as of 16:12, 28 April 2020
Line 1:		Line 1:
	Fping is a command line application that allows for data collection and recording of the ping command data. It is basically like Ping, but is better, and has more features and functions. The most important feature is to log pings with time and date stamps to a file. In addition, it provides an accurate millisecond calculation on the ping command. FPING also supports 64 bit operating systems.		Fping is a command line application that allows for data collection and recording of the ping command data. It is basically like Ping, but is better, and has more features and functions. The most important feature is to log pings with time and date stamps to a file. In addition, it provides an accurate millisecond calculation on the ping command. FPING also supports 64 bit operating systems.

	*Google "windows fping 3.0"		*Google "windows fping 3.0", and download the FPING program.
	*From the ~~drop down menu, select fping~~. ~~Download the files~~ and ~~install in a directory, usually I~~ put it in c:\fping.		Extract and put it in C:\fping

	==Limitations of Windows Based PC's for Reliable Ping Testing==		==Limitations of Windows Based PC's for Reliable Ping Testing==

imported>Schoen.kevin at 16:12, 28 April 2020

2020-04-28T16:12:20Z

← Older revision		Revision as of 16:12, 28 April 2020
Line 1:		Line 1:
	Fping is a command line application that allows for data collection and recording of the ping command data. It is basically like Ping, but is better, and has more features and functions. The most important feature is to log pings with time and date stamps to a file. In addition, it provides an accurate millisecond calculation on the ping command. FPING also supports 64 bit operating systems.		Fping is a command line application that allows for data collection and recording of the ping command data. It is basically like Ping, but is better, and has more features and functions. The most important feature is to log pings with time and date stamps to a file. In addition, it provides an accurate millisecond calculation on the ping command. FPING also supports 64 bit operating systems.

	*Google fping 3.0		*Google "windows fping 3.0"
	*From the drop down menu, select fping. Download the files and install in a directory, usually I put it in c:\fping.		*From the drop down menu, select fping. Download the files and install in a directory, usually I put it in c:\fping.

imported>Schoen.kevin at 21:41, 7 April 2020

2020-04-07T21:41:16Z

← Older revision		Revision as of 21:41, 7 April 2020
Line 1:		Line 1:
	Fping is a command line application that allows for data collection and recording of the ping command data. It is basically like Ping, but is better, and has more features and functions. The most important feature is to log pings with time and date stamps to a file. In addition, it provides an accurate millisecond calculation on the ping command. FPING also supports 64 bit operating systems.		Fping is a command line application that allows for data collection and recording of the ping command data. It is basically like Ping, but is better, and has more features and functions. The most important feature is to log pings with time and date stamps to a file. In addition, it provides an accurate millisecond calculation on the ping command. FPING also supports 64 bit operating systems.

	*~~Download the file here http://www~~.~~kwakkelflap.com/downloads.html~~		*Google fping 3.0
	*From the drop down menu, select fping. Download the files and install in a directory, usually I put it in c:\fping.		*From the drop down menu, select fping. Download the files and install in a directory, usually I put it in c:\fping.

imported>Demorest.evan: /* Command Structure */

2015-04-13T04:40:08Z

Command Structure

← Older revision		Revision as of 04:40, 13 April 2015
Line 36:		Line 36:
	The command structure that should be used:		The command structure that should be used:

	*fping xxx.xxx.xxx.xxx -D -c -s 1500 -L name-of-log-file.txt		*fping xxx.xxx.xxx.xxx -D -T -c -s 1500 -L name-of-log-file.txt
	**Where xxx.xxx.xxx.xxx is the ip address of the device you are pinging.		**Where xxx.xxx.xxx.xxx is the ip address of the device you are pinging.
	**This will create a timestamped file.		**This will create a timestamped file.
Line 46:		Line 46:
	This should be used to detect issues with CRC and other line errors, generally this will stress the equipment that you are reaching. '''DO NOT PING EQUIPMENT WITH THESE COMMANDS UNLESS IT IS YOUR EQUIPMENT'''. If service providers see this type of ping traffic hitting their equipment for a while (i.e. more that a couple of minutes) or often expect to get Null Routed.		This should be used to detect issues with CRC and other line errors, generally this will stress the equipment that you are reaching. '''DO NOT PING EQUIPMENT WITH THESE COMMANDS UNLESS IT IS YOUR EQUIPMENT'''. If service providers see this type of ping traffic hitting their equipment for a while (i.e. more that a couple of minutes) or often expect to get Null Routed.

	*fping xxx.xxx.xxx.xxx -t100 -D -c -s 1500 -L name-of-log-file.txt		*fping xxx.xxx.xxx.xxx -t100 -D -T -c -s 1500 -L name-of-log-file.txt
	**Where xxx.xxx.xxx.xxx is the ip address of the device you are pinging.		**Where xxx.xxx.xxx.xxx is the ip address of the device you are pinging.
	**This will create a timestamped file.		**This will create a timestamped file.

imported>Schoen.kevin: /* Limitations of Windows Based PC's for Reliable Ping Testing */

2015-04-02T14:34:47Z

Limitations of Windows Based PC's for Reliable Ping Testing

← Older revision		Revision as of 14:34, 2 April 2015
Line 10:		Line 10:
	Pings take into account the cycle time through all routers and PC's. You will never obtain 100% low ping times on routers or PC's, because they are often doing other things. Average is what is important.		Pings take into account the cycle time through all routers and PC's. You will never obtain 100% low ping times on routers or PC's, because they are often doing other things. Average is what is important.

	Windows based PC's do not guarantee processor queues for any specific ping applications. Lost packets either on the send or the return of ping packets is common and to be expected on all windows PCs, as there is no dedicated processing at the network layer. In addition, determining why a ping was lost cannot be reliably determined on a Windows PC. ~~The device where we can reliably obtain this, because there are specific counters for each packet drop type,~~ is ~~on Cisco IOS routers~~.		Windows based PC's do not guarantee processor queues for any specific ping applications. Lost packets either on the send or the return of ping packets is common and to be expected on all windows PCs, as there is no dedicated processing at the network layer. In addition, determining why a ping was lost cannot be reliably determined on a Windows PC. Data should be considered suspect on Windows based PC's. We recommend using the 64 bit ping application if your operating system is compatible with 64 bit.

	~~Data should be considered suspect on Windows based PC's. We recommend using the 64 bit ping application if your operating system is compatible with 64 bit.~~		What we know does provide accurate testing via packet loss is Cisco IOS Router, and dedicated linux testing tends to work better, because there is less of an operating system to go through (i.e. gui, etc) to get to the network card. Dedicated network processor cards in the linux platform should.

	What we know does provide accurate testing via packet loss is Cisco IOS Router, and dedicated linux testing tends to work better, because there is less of an operating system to go through (i.e. gui, etc) to get to the network card.

	In general, reliable ping testing should primarily be performed on Cisco IOS capable routers. FPING does some cool stuff, but ACD generally focuses on ping testing from our Cisco IOS routes.		In general, reliable ping testing should primarily be performed on Cisco IOS capable routers. FPING does some cool stuff, but ACD generally focuses on ping testing from our Cisco IOS routes.

imported>Schoen.kevin: /* Command Structure */

2012-11-21T20:34:14Z

Command Structure

← Older revision		Revision as of 20:34, 21 November 2012
Line 34:		Line 34:
	'''Long term pinging'''		'''Long term pinging'''

	In command prompt type: cd C:\fping~~\x86 (32 bit) or cd C:\fping\x64 (64 bit) based on what processor you have.~~		In command prompt type: cd C:\fping

	The command structure that should be used:		The command structure that should be used:

imported>Schoen.kevin: /* Command Structure */

2012-11-21T20:33:39Z

Command Structure

← Older revision		Revision as of 20:33, 21 November 2012
Line 52:		Line 52:
	**This will create a timestamped file.		**This will create a timestamped file.
	**-s 1500 sends 1500 byte pings, which is the maximum normal size. If you cannot send 1500 byte pings, there is something wrong somewhere on the network you are using.		**-s 1500 sends 1500 byte pings, which is the maximum normal size. If you cannot send 1500 byte pings, there is something wrong somewhere on the network you are using.
	**-t100 lowers the time between pings. 100=100ms. Lower it down until you get to the point of limited responsiveness. Generally you can lower the time all of the way down to one millisecond. This is good for detecting hosts that have ping rate limiting or also have inherent limitations on the ping speed. '''PING OTHER PEOPLES STUFF WITH CAUTION, INCLUDING ACD.NET EQUIPMENT. IF YOU PING ACD FOR LONG YOU WILL BE NULL ROUTED'''		**-t100 lowers the time between pings. 100=100ms. Lower it down until you get to the point of limited responsiveness. Generally you can lower the time all of the way down to one millisecond. '''Effectively, you are pinging as quickly as the response from one ping comes back without delay. This is good for detecting hosts that have ping rate limiting or also have inherent limitations on the ping speed. '''PING OTHER PEOPLES STUFF WITH CAUTION, INCLUDING ACD.NET EQUIPMENT. IF YOU PING ACD FOR LONG YOU WILL BE NULL ROUTED BY OUR NOC.'''

	==How to use Ping testing ==		==How to use Ping testing ==

imported>Schoen.kevin: /* Limitations of Windows Based PC's for Reliable Ping Testing */

2012-11-21T20:29:46Z

Limitations of Windows Based PC's for Reliable Ping Testing

← Older revision		Revision as of 20:29, 21 November 2012
Line 16:		Line 16:
	What we know does provide accurate testing via packet loss is Cisco IOS Router, and dedicated linux testing tends to work better, because there is less of an operating system to go through (i.e. gui, etc) to get to the network card.		What we know does provide accurate testing via packet loss is Cisco IOS Router, and dedicated linux testing tends to work better, because there is less of an operating system to go through (i.e. gui, etc) to get to the network card.

	In general, reliable ping testing should primarily be performed on Cisco IOS capable routers.		In general, reliable ping testing should primarily be performed on Cisco IOS capable routers. FPING does some cool stuff, but ACD generally focuses on ping testing from our Cisco IOS routes.

	'''We are in the process of testing fping compared to ping, and seeing if there is a way to make sure the buffer queues are adequate to guarantee processing of all low priority packets. This is pending as of 03/20/12'''		'''We are in the process of testing fping compared to ping, and seeing if there is a way to make sure the buffer queues are adequate to guarantee processing of all low priority packets. This is pending as of 03/20/12'''

			'''We are in process of testing fping compared to Cisco IOS routers on unloaded Windows 7/Windows 8, etc boxes as of 10/01/12'''

	==Data relied upon for debugging or troubleshooting==		==Data relied upon for debugging or troubleshooting==