We had a device that had a very bad month, starting at May 29th.
When I run the event report (Summary) for June, it reports it was down for 3 days.
When I run the event report (Detail Worst First) for the same time period it tells me I missed 23093 polls, which at one minute intervals is 16 days ( and is the number I believe to be correct).
To add another mystery to the story, there are two entries in the detail report that give an"UP (assumed)". This device does not have any dependencies, so why does it assume anything?
In the Detail listing, the following lines are of interest:
20040605 0953 UP 7273 20040606 0954 Down Timed Out 20040608 1414 UP (assumed) 1 3:04:20 20040608 1416 Down Timed Out 20040608 1428 UP (assumed) 1 12 20040623 0756 UP 15787
Note that the two missed poll values of 7272 and 15787 DO NOT have an associated Downtime with them.
When I run the same report for a longer time that includes the DOWN time stamp that occurs before the 1st line of data shown, the report does provide the downtime.
So, the problem in the report generator appears to be when it does not see a Down before an UP, it lists the missed polls but can't calculate the total downtime. If my theory is correct, then a device that is down before the month begins will not be calculated correctly.
And as to the Up (assumed), anyone got a clue to that one? That UP (assumed) without a subsequent DOWN caused the 15787 missed polls not to be calculated.
I'm running rev 8.01
Jay Drew
[EMAIL PROTECTED]
Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list.
An Archive of this list is available at: http://www.mail-archive.com/whatsup_forum%40list.ipswitch.com/
