Hi!
Since yesterday we are using UNC-test to survey our important shares on the LAN.
The test is configured to check every 5 minutes if a share is down or not.
There were no problems but one thing.
We got a mail timestamped at 06:52 pm with bad status.
Another mail was sent at 06:57 pm with good status.
So this share should have been down for less than 5 minutes. But it wasn´t.
Our cluster manager would have entries in his logs but it has not.
Question:
Do you know a certain case in which the UNC-test cannot reach a share although it works properly? Maybe too much traffic on that share?
If there is no explanation for this incident we will have to set up the tests to check twice bad status before sending alarm, don´t we?
Problem with UNC-test
-
iis5_rulez
- Posts: 32
- Joined: Tue Dec 17, 2002 6:00 pm
Sometimes it happens when HostMonitor checks many Netware shares at the same time.Do you know a certain case in which the UNC-test cannot reach a share although it works properly? Maybe too much traffic on that share?
There is option on Miscellaneous page in the Options dialog:
UNC test mode
This parameter defines behavior of UNC tests.
Normal - HostMonitor can start many tests simultaneously.
OnePerServer - HostMonitor will start only 1 test per server at one time, but can start several tests for different servers at the same time.
OneByOne - only 1 attempt at one time (one attempt means - if "UNC test retries" value greater than 1, HostMonitor tries to get information from 1st server; if this try failed, HostMonitor will pause test for this server and will try to check another servers, after 900ms HostMonitor returns to 1st server and performs 2nd attempt).
Try to use OnePerServer mode.
Yes, you may use "Repeat test" action to confirm result.If there is no explanation for this incident we will have to set up the tests to check twice bad status before sending alarm, don´t we?
Regards
Alex