| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2851.1 | Sounds like a bug | TOOK::MINTZ | Erik Mintz, DECmcc Development, dtn 226-5033 | Fri Apr 24 1992 18:25 | 11 |
| It sounds like you have re-discovered a bug we thought we had fixed.
Can you supply some more details for a QAR, like:
Which operating system?
What kind of rules (expression, occurs, ...)?
About how many rules?
Thanks,
-- Erik
|
| 2851.2 | Does it work from FCL? | TOOK::MINTZ | Erik Mintz, DECmcc Development, dtn 226-5033 | Fri Apr 24 1992 18:51 | 4 |
| Also, can you try to delete the same rules through the FCL, and let us know
if the results are any different?
-- Erik
|
| 2851.3 | | SEVERN::BREWTON | | Mon Apr 27 1992 19:23 | 34 |
| Operating System - VMS 5.5 SSB
rule -
create mcc 0 alarms rule TNSBUM_line_SVA-0_contention -
expression = -
(change_of(NODE4 .DNA_NODE.TNSBUM line SVA-0 send failure,*, *), -
at every 01:00:00), -
procedure = mcc_common:mcc_alarms_mail_alarm.com, -
exception handler = mcc_common:mcc_alarms_mail_exception.com, -
category = "Transmit problems", -
description = "If a line cannot send a packet after 16 attempts -
this counter will increase. This is only true for -
ethernet lines and usually indicates that the -
channel is very heavily used.", -
queue = "SYS$BATCH:", -
parameter = "SEVERN::BREWTON", -
perceived severity = minor, -
in domain = mcc.domain.tjr
# of rules 15-20
I also tried the FCL interface and got the same error.
Steve
|
| 2851.4 | more data | SEVERN::BREWTON | | Mon Apr 27 1992 19:39 | 27 |
| I tried a wildcard delete of all my rules in a particular domain. Only
the rules taht are returning errors were not deleted. It turns out that
the rules I am having trouble with are illegal for the particular node.
Listed below is the mail message I get back on one of these rules:
Subj: Notification of exception " MCC 0 ALARMS RULE
DMS06_line_SYN-1_contention 27-APR-1992 15:33:06.99"
Rule name: MCC 0 ALARMS RULE DMS06_line_SYN-1_contention
Domain: Domain SEVERN_NS:.MCC.DOMAIN.LANDOVER
Occurred at: 27-APR-1992 15:33:06.99
Category: Transmit problems
Description: If a line cannot send a packet after 16 attempts
this counter will increase. This is only true for
ethernet lines and usually indicates that the
channel is very heavily used.
Severity: Indeterminate
Expression: (change_of(NODE4 .DNA_NODE.DMS06 line SYN-1 send
failure,*, *), at every 01:00:00)
Exception: Rule could not be evaluated as the attribute was not
returned
by the Entity.
Steve
|
| 2851.5 | QAR 2829 | TOOK::MINTZ | Erik Mintz, DECmcc Development, dtn 226-5033 | Mon Apr 27 1992 19:42 | 1 |
| QAR 2829
|
| 2851.6 | alarms having problems talking to other modules | TOOK::CALLANDER | MCC = My Constant Companion | Fri May 15 1992 14:29 | 9 |
| it looks like the rule is actually stuck in a bad state. It
is having problems talking to the module it is using for
getting the data (this is the transmit error); once this
happens all bets are off. We have been looking at why the
connections are lost and how to fix this problem but at this point
in time we are not certain if we have completely fixed it.
Thanks for the input.
|
| 2851.7 | Can't delete alarms | SALISH::SAFRAN_RO | | Fri Jul 10 1992 19:49 | 10 |
| The rules seem to get stuck because of the character count in the
description field. What I have done is to extract (or save off
somewhere in the first place) the distribution copies of the alarms
mir files. The only way of deleting these alarms is to copy over the
original files.
There are several of the example alarms that have too many characters
for their descriptions and cause this behavior.
Bob
|