-
Notifications
You must be signed in to change notification settings - Fork 1
BSSM_Pinger
The BSSM_Pinger console command is a child of the BSSM_PingManager process which will ping the device that is passed to it and store the results in the database. This process will ping the device x many times to determine if the device is up, slow or down.
There are many pingers that will ping a device once, if it is not reachable it is down, which is usually good for small local networks, but for WANs a device can be down the first 5 pings, but up the next 2 and then down 3, which usually means that the site connection is slow, but now down. So since it was reachable 2 out of 10 times [try=x], then the device is marked as slow, and not down. In order for a device to be down it will have to fail all the amount set for the tries.
Switch | Description |
---|---|
/try=[number] | Try Pinging the device x amount of times |
/sid=[number] | Device/Server Identifier, used for database inserts |
/server=[servername] | The Server Name or IP Address that is going to be pinged |
/ip=[IPADDRESS] | The IP Address of the device, used as a backup just incase the name doesn't resolve. |
The app.config file ( BSSM_Pinger.exe.config ) file will also store other settings under the "appSettings"
Key | Value | Description |
---|---|---|
DEBUG | false | Enable Debugging Log |
CONSOLE | false | Push Messages to console window ( not useful when running as a service ) |
LOGFILE | logs\pinger.err.log | Application Error Log, if it breaks, check here |
BUGFILE | logs\pinger.debug.log | Application Debug Log, extra messages are sent to this log file to allow you to see what it is doing. |
PING_TIMEOUT | 1500 | The acceptable amount of time before the ping expires and returns as down |
REPEAT_EVT_HRS | 4 | Look back x amount of hours before repeating an alert in the Events section |
USETRACE | false | Use the trace data if available to determine where the the connect is dead at. |