DR Surveillance Kit Ver 2.0 (Dated
23-11-2002)
This
document (created on 23-11-2002)describes how to use the Surveillance Kit,
during an outage in .
Kit Contents and Description
DR.BAT
This
is a batch file, which will trigger the Surveillance tool. Internally this batch file will call the VB
Script, which check the connectivity.
The batch file will be running in an infinite loop and use Ctrl + Brake
or Ctrl + C to stop at any time
DR .VBS
This
is the heart or brain of this kit. It
takes input from elemtns.txt file and ping the IP address one by one.
ELEMENTS.txt
User
can add all the IP Address one per line.
DR_ .VBS will pick up this and check for connectivity. This file can be edited on-line. ie:
User can add or remove the entries, while the tool is running.
EEEORTRACK.BAT
This
is another batch file, which will decided the way, errors are logged and decide
whether the user to be altered by an audio alarm.
This
file got two sections, Section 1 and 2.
The first one define how the output should be formatted and the second
one help the user the enable/disable audio alerts.
By
default, ERRORTRACK.BAT will log the down incidents in comma separated
fields. Fields are IP Address of the
element, which was not responding for
SoundGen.exe
This
file is created in Turbo C, which will create an audio alarm, when ever any
element is not responding for
How this kit works?
01.
DR will trigger
the script (ie : DR .VBS)
02.
The script will
take the IP address from the ELEMENT.TXT file and ping one by one
03.
If the element
is up, it prompts that it is up.
04.
If it is down,
it displays the same and ERRORTRACK.BAT
fill be trigged.
05.
ERRORTRACK.BAT
will log all the entries in a log file, called Log.txt
How to use this?
01
Create a folder
and copy all the files mentioned in the Kit Contents
02
Add the IP
Address to be monitored.
03
Start the batch
file “DR.bat” from the command prompt or by double-clicking on it.
Support:
I
created this tool to checking the connectivity of a link/device/server. If time permits, I will try to answer the questions.
This
tool was not tested in all the conditions.
There is no grantee or assurance
that this will not cause any damage.
Again, I don’t have any claims that this will work under all the
conditions. By using this tool, you (the
user) is taking the responsibility if any damage caused. I am scared of getting pulled to any kind of
debate or legal actions and so, declare again and again any bad things happens
due to this tool, the user is 100% responsible for that. I don’t ask/recommend any one to use this