we have a remote probe at a site connected to a site to site vpn. Even though all other sensors are showing normal, the users are complaining that it is taking a long time to copy the data. We would like to see how long it takes for a 1 mb file at the main site takes to copy to the remote probe across the VPN over SMB, and have the threasholds set to 5 seconds for warning and 10 seconds for alarm.
We would like to know how long a file takes to copy
Votes:
0
Best Answer
Accepted Answer
Votes:
0
You can use this as a batch file sensor:
@echo off
FOR /F "skip=1 tokens=1-6" %%A IN ('WMIC Path Win32_LocalTime Get Day^,Hour^,Minute^,Second /Format:table ^| findstr /r "."') DO (
set Milisecond=%time:~9,2%
set Day=%%A
set Hour=%%B
set Minute=%%C
set Second=%%D
)
set /a Start=%Day%*8640000+%Hour%*360000+%Minute%*6000+%Second%*100+%Milisecond%
:: put your copy command here
:: and delete the ping command (only used for testing)
ping www.paessler.com > nul
FOR /F "skip=1 tokens=1-6" %%A IN ('WMIC Path Win32_LocalTime Get Day^,Hour^,Minute^,Second /Format:table ^| findstr /r "."') DO (
set Milisecond=%time:~9,2%
set Day=%%A
set Hour=%%B
set Minute=%%C
set Second=%%D
)
set /a End=%Day%*8640000+%Hour%*360000+%Minute%*6000+%Second%*100+%Milisecond%
set /a Diff=%End%-%Start%
echo %Diff%:ok
This will return the number of milliseconds it took for your copy command to finish.
Note: Calculating the end time also takes time, so the calculation is not 100% accurate. You might want to consider doing a "dry run" without a copy command and subtract the outcome (approximately 10 to 15 msec) from the result.
set /a Diff=%End%-%Start%-10
Last change on Jul 12, 2011 1:11:25 PM by
6 Replies
Votes:
0
Dear Cliff,
you could try the solution from the following article Monitoring the Available Bandwidth (Part 2)
best regards.
Created on Jul 11, 2011 3:13:43 PM by
Votes:
0
If you want to check the speed of SMB-operations (copy), then it's necessary to do that with a self-written script which then runs as a sensor in PRTG.
Created on Jul 11, 2011 4:21:12 PM by
Votes:
0
Well, that might require for example VBScript using its Timer Function, and the script to stop the time itself.
Created on Jul 11, 2011 4:38:25 PM by
Last change on Jul 11, 2011 4:39:02 PM by
Accepted Answer
Votes:
0
You can use this as a batch file sensor:
@echo off
FOR /F "skip=1 tokens=1-6" %%A IN ('WMIC Path Win32_LocalTime Get Day^,Hour^,Minute^,Second /Format:table ^| findstr /r "."') DO (
set Milisecond=%time:~9,2%
set Day=%%A
set Hour=%%B
set Minute=%%C
set Second=%%D
)
set /a Start=%Day%*8640000+%Hour%*360000+%Minute%*6000+%Second%*100+%Milisecond%
:: put your copy command here
:: and delete the ping command (only used for testing)
ping www.paessler.com > nul
FOR /F "skip=1 tokens=1-6" %%A IN ('WMIC Path Win32_LocalTime Get Day^,Hour^,Minute^,Second /Format:table ^| findstr /r "."') DO (
set Milisecond=%time:~9,2%
set Day=%%A
set Hour=%%B
set Minute=%%C
set Second=%%D
)
set /a End=%Day%*8640000+%Hour%*360000+%Minute%*6000+%Second%*100+%Milisecond%
set /a Diff=%End%-%Start%
echo %Diff%:ok
This will return the number of milliseconds it took for your copy command to finish.
Note: Calculating the end time also takes time, so the calculation is not 100% accurate. You might want to consider doing a "dry run" without a copy command and subtract the outcome (approximately 10 to 15 msec) from the result.
set /a Diff=%End%-%Start%-10
Last change on Jul 12, 2011 1:11:25 PM by
Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
Add comment