| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3776.1 | More details for rules... | ZTOIS1::VISTA | Renato VISTA, SIS Strasbourg, France | Mon Sep 28 1992 10:19 | 35 |
|
More details about rule (after problem has occurred) :
SHOW RULE icmp_down_1shoot_SXC003
Name : icmp_down_1shoot_SXC300
Expression : snmp sxc003 ipReachability = down,
at every=00:06:00
Severity : critical
Probable Cause : unknown
State : disabled
Substate : Time specification has expired
Disable Time : 1992-09-23-07:18:36:875
Error condition : Software logic error detected
Time of last
evaluation : 1992-09-23-07:18:36:648
Result of last
evaluation : error
Current severity : indeterminate
Creation Time : 1992-09-23-07:18:36:465
Evaluation Error : 0
Evaluation True : 0
Evaluation False : 0
Please note :
. the time interval from creation/enabling to disabling
(less than 1 second)
. no counter has been incremented
Renato
|
| 3776.2 | A tricky one | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Mon Sep 28 1992 12:47 | 31 |
| RE: .1
Renato,
This is a tricky one!
>> State : disabled
>> Substate : Time specification has expired
This means that the Rule's time specification has expired ... which can
only occur when you set an expiration time - which you have not! For
example:
( node4 foo max addr > 50, at every 00:10:00 until 17:00:00 )
sets the expiration time to 5pm
>> Error condition : Software logic error detected
Generally indicates that Alarms has detected an processing error.
Could you try the command:
show snmp sxc003 ipReachability, at every 00:06:00
to make sure it works correctly. This is the command which Alarms
is executing.
/keith
|
| 3776.3 | Yes, but why ? | ZTOIS1::VISTA | Renato VISTA, SIS Strasbourg, France | Tue Sep 29 1992 10:34 | 19 |
|
Hi Keith,
Thank you for your reply.
I've already noticed this kind of behavior in FCL mode.
But have you got any idea about the reasons of the processing error
you mentionned. How to explain that an ENABLED rule becomes DISABLED
(ie target entity is not monitored after processing error) ?
Please also note that the problem occurs once on one or two rules, very
randomly. After enabling those stopped rules again, alarms_fm seems to run
correctly.
Renato
|
| 3776.4 | Why - a short question with a long answer | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Tue Sep 29 1992 12:14 | 25 |
| RE: .3
Renato,
>> I've already noticed this kind of behavior in FCL mode.
Which behavior? Did you try the Show directive directly by the FCL:
show snmp sxc003 ipReachability, at every 00:06:00
>> But have you got any idea about the reasons of the processing error
>> you mentionned. How to explain that an ENABLED rule becomes DISABLED
>> (ie target entity is not monitored after processing error) ?
I'll have to look through the Alarms code to see where the 'software
logic error' gets set. I suspect that something went wrong which Alarms
doesn't explicitly process (software logic error is a catch-all) .. then
the Rule shutdown .. on the way down Alarms assumes it is stopping because
the time-specification is complete.
There could be a log bit to set which gives a bit more information - I'll
look there too.
/keith
|