| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
If it was Friday afternoon I'd guess it was user error and go
home. Why is this rule firing?
notify domain config
!%MCC-S-NOTIFSTART, Notify request 1 started
!
!!!!!!!!!!!!!!! Alarm, 10-SEP-1992 15:20:52 !!!!!!!!!!!!!! [1]
!Domain: LOCAL_NS:.config Severity: Major
!Notification Entity: Bridge LOCAL_NS:.bridge.500-2 LINE 2
!Event Source: Domain LOCAL_NS:.config Rule test2
!Event: OSI Rule Fired
!
! Event Type = QualityofServiceAlarm
! Event Time = 10-SEP-1992 15:20:49.83
! Probable Cause = Unknown
! Additional Info = { (
! significance = True,
! information = "Rule fired: Bridge
! LOCAL_NS:.bridge.500-2 LINE 2
! Transmit Multiple Collisions =
! 68341 10-SEP-1992 15:20:49.64" ),
! (
! significance = True,
! information = "(Bridge LOCAL_NS:.bridge.500-2
! LINE 2 Transmit Multiple
! Collisions > 70000, at
! every=00:01)" ) }
! Managed Object = Bridge LOCAL_NS:.bridge.500-2 LINE 2
! Perceived Severity = Major
! Additional Text = "too many collisions
! "
!
-----------------------------------------------------
I created another rule that SHOULD fire based on the above counter and
it fired. These two rules can't possibly both fire at the same
time!
----------------------------------------
!
!
!!!!!!!!!!!!!!! Alarm, 10-SEP-1992 15:21:01 !!!!!!!!!!!!!! [1]
!Domain: LOCAL_NS:.config Severity: Critical
!Notification Entity: Bridge LOCAL_NS:.bridge.500-2 LINE 2
!Event Source: Domain LOCAL_NS:.config Rule test3
!Event: OSI Rule Fired
!
! Event Type = QualityofServiceAlarm
! Event Time = 10-SEP-1992 15:20:59.95
! Probable Cause = Unknown
! Additional Info = { (
! significance = True,
! information = "Rule fired: Bridge
! LOCAL_NS:.bridge.500-2 LINE 2
! Transmit Multiple Collisions =
! 68342 10-SEP-1992 15:20:59.78" ),
! (
! significance = True,
! information = "(Bridge LOCAL_NS:.bridge.500-2
! LINE 2 Transmit Multiple
! Collisions > 60000, at
! every=00:01)" ) }
! Managed Object = Bridge LOCAL_NS:.bridge.500-2 LINE 2
! Perceived Severity = Critical
! Additional Text = "too many collisions
! "
!
!
!
exit
!
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3720.1 | QAR 3418 | TOOK::MINTZ | LKG2-2 near pole X3, cube 6072, dtn 226-5033 | Thu Sep 10 1992 16:45 | 1 |
Entered as QAR 3418 at priority M | |||||
| 3720.2 | This problem looks pervasive! | VCSESU::WADE | Bill Wade, VAXc Systems & Support Eng | Fri Sep 11 1992 11:03 | 63 |
There is something seriously wrong here -
!!!!!!!!!!!!!!! Alarm, 11-SEP-1992 09:45:59 !!!!!!!!!!!!!! [1]
!Domain: LOCAL_NS:.config Severity: Major
!Notification Entity: Bridge LOCAL_NS:.bridge.500-2
!Event Source: Domain LOCAL_NS:.config Rule test5
!Event: OSI Rule Fired
!
! Event Type = QualityofServiceAlarm
! Event Time = 11-SEP-1992 09:45:58.05
! Probable Cause = Unknown
! Additional Info = { (
! significance = True,
! information = "Rule fired: Bridge
! LOCAL_NS:.bridge.500-2 Seconds
! Operating = 861079 11-SEP-1992
! 09:45:57.93" ),
! (
! significance = True,
! information = "(Bridge LOCAL_NS:.bridge.500-2
! Seconds Operating > 900000, at
! every=00:01)" ) }
! Managed Object = Bridge LOCAL_NS:.bridge.500-2
! Perceived Severity = Major
! Additional Text = "running too long
! "
!
!
!
!
!!!!!!!!!!!!!!! Alarm, 11-SEP-1992 09:46:15 !!!!!!!!!!!!!! [1]
!Domain: LOCAL_NS:.config Severity: Major
!Notification Entity: Bridge LOCAL_NS:.bridge.500-2 PHY Port 1
!Event Source: Domain LOCAL_NS:.config Rule test6
!Event: OSI Rule Fired
!
! Event Type = QualityofServiceAlarm
! Event Time = 11-SEP-1992 09:46:14.58
! Probable Cause = Unknown
! Additional Info = { (
! significance = True,
! information = "Rule fired: Bridge
! LOCAL_NS:.bridge.500-2 PHY Port 1
! LEM Link Errors = 0 11-SEP-1992
! 09:46:14.48" ),
! (
! significance = True,
! information = "(Bridge LOCAL_NS:.bridge.500-2
! PHY Port 1 LEM Link Errors > 5,
! at every=00:01)" ) }
! Managed Object = Bridge LOCAL_NS:.bridge.500-2 PHY
! Port 1
! Perceived Severity = Major
! Additional Text = " too many errors
! "
!
!
!
exit
!
| |||||
| 3720.3 | I would guess a problem with alarms or FCL's handling of 64-bit integers | MCC1::DITMARS | Pete | Fri Sep 11 1992 12:34 | 3 |
It's been a problem (addressed several different times) in the past. Is this on ultrix? | |||||
| 3720.4 | VCSESU::WADE | Bill Wade, VAXc Systems & Support Eng | Fri Sep 11 1992 13:10 | 41 | |
Pete,
I don't remember seeing this problem addressed previously -
!
!
!
!!!!!!!!!!!!!!! Alarm, 11-SEP-1992 09:46:15 !!!!!!!!!!!!!! [1]
!Domain: LOCAL_NS:.config Severity: Major
!Notification Entity: Bridge LOCAL_NS:.bridge.500-2 PHY Port 1
!Event Source: Domain LOCAL_NS:.config Rule test6
!Event: OSI Rule Fired
!
! Event Type = QualityofServiceAlarm
! Event Time = 11-SEP-1992 09:46:14.58
! Probable Cause = Unknown
! Additional Info = { (
! significance = True,
! information = "Rule fired: Bridge
! LOCAL_NS:.bridge.500-2 PHY Port 1
! LEM Link Errors = 0 11-SEP-1992
! 09:46:14.48" ),
! (
! significance = True,
! information = "(Bridge LOCAL_NS:.bridge.500-2
! PHY Port 1 LEM Link Errors > 5,
! at every=00:01)" ) }
! Managed Object = Bridge LOCAL_NS:.bridge.500-2 PHY
! Port 1
! Perceived Severity = Major
! Additional Text = " too many errors
! "
!
!
!
exit
!
| |||||
| 3720.5 | MCC1::DITMARS | Pete | Mon Sep 14 1992 14:55 | 4 | |
I didn't mean it was something you should have known about. I meant that FCL/alarms have both had problems with 64-bit integers in the past (e.g. baselevels of V1.1/V1.2). | |||||
| 3720.6 | Fixed with new MCC_ALARMS_FM.EXE. | VCSESU::WADE | Bill Wade, VAXc Systems & Support Eng | Fri Oct 02 1992 12:33 | 6 |
I was given a new MCC_ALARMS_FM.EXE image which I tested and it
fixed the problem. But I'm not sure if a patch will be released or it
will have to wait for 1.3.
Bill
| |||||
| 3720.7 | QAR 03418 - Answered | TOOK::MINTZ | LKG2-2 near pole X3, cube 6072, dtn 226-5033 | Tue Oct 13 1992 16:27 | 1 |
The answer to this QAR indicates that the fix will be included in V1.3 | |||||