| The biggest problem I see here is that there IS NO version 1.1 of the Vitalink
TransLAN AM... There is only V1.0.
I have cut and pasted the alarm rule you posted verbatim (changing only the
rule, domain and translan name) and cannot reproduce the problem... Has your
customer installed all of the appropriate patches to his MCC system? This may
be part of the problem.
If you are sure there are no typos involved, then this is most likely a
problem with the alarms FM. Please note that there is NO error message that
would indicate that the TransLAN AM has anything to do with this.
See session log attached below.
regards
/doug
P.S. What the HECK is that Description field supposed to mean, anyway ?!?!
!
show mcc 0 all char
!
!MCC 0
!AT 13-MAR-1992 13:18:28 Characteristics
!
!Examination of Attributes Shows:
! Component Version = V1.1.0
! Component Identification = "DECmcc"
!
show mcc 0 translan_am all attr
!
!MCC 0 TRANSLAN_AM
!AT 13-MAR-1992 13:18:36 All Attributes
!
! Available Ports = { "ESA0:" }
! Component Identification = "DECmcc TransLAN AM"
! Component Version = V1.0.0
!
do test-rule-foo
!%MCC-S-VERIFYENTER, entering command procedure SYS$SYSDEVICE:[MCPHERSON]TEST-RULE-FOO.COM;3
!create mcc 0 alarm rule test_rule -
!expression=(change_of(translan madge_335 line 1 controller reset,*,*) -
!,at every 00:10:00),-
!perc sever =critical,-
!desc="line1111111111111111111111111111111111111111111111111111111111111111111-
!line2222222222222222222222222222222222222222222222222222222222222222222222222-
!line3333333333333333333333333333333333333333333333333333333333333333333333333-
!line4444444444444444444444444444444444444444444444444444444444444444444444444-
!line5555555555555555555555555555555555555555555555555555555555555555555555555",-
!in domain doug-test
!
!MCC 0 ALARMS RULE test_rule
!AT 13-MAR-1992 13:18:50
!
!Entity created successfully.
!
!%MCC-S-VERIFYEXIT, exiting command procedure SYS$SYSDEVICE:[MCPHERSON]TEST-RULE-FOO.COM;3
!
enable mcc 0 alarm rule test_rule, in domain doug-test
!
!MCC 0 ALARMS RULE test_rule
!AT 13-MAR-1992 13:19:22
!
!Normal operation has begun.
!
show mcc 0 alarm rule test_rule, all attributes in domain doug-test
!Using default ALL IDENTIFIERS
!%MCC-W-QUALUNKNOWN, qualifier is unknown: ALL
!
show mcc 0 alarm rule test_rule all attributes,in domain doug-test
!
!MCC 0 ALARMS RULE test_rule
!AT 13-MAR-1992 13:19:46 All Attributes
!
! NAME = test_rule
! Result of Last Evaluation = False
! State = Enabled
! Substate = Running
! Time of Last Evaluation = 13-MAR-1992 13:19:22.50
! Creation Timestamp = 13-MAR-1992 13:19:22.13
! Evaluation Error = 0
! Evaluation False = 1
! Evaluation True = 0
! Description = "line111111111111111111111111111111111
! 1111111111111111111111111111111111line
! 22222222222222222222222222222222222222
! 22222222222222222222222222222222222lin
! e3333333333333333333333333333333333333
! 333333333333333333333333333333333333li
! ne444444444444444444444444444444444444
! 4444444444444444444444444444444444444l
! ine55555555555555555555555555555555555
! 55555555555555555555555555555555555555
! "
! Expression = (change_of(translan madge_335 line 1
! controller reset,*,*) ,at every
! 00:10:00)
! Perceived Severity = critical
!
exit
!
|
| The process of the Description argument could be having a problem when
the string exceeds a certain length. I will QAR this problem.
Oh yeah, what version of DECmcc is the customer running? I imagine if
its a customer (ie, not internal) then it would be v1.1
It is also possible that this problem has been corrected in V1.2
/keith
|