| 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 |
A customer claims he can't set up an alarm on a Translan if it's of type 'change_of' 'controller resets' and with a long description test. The command is as follows create mcc 0 alarm rule test_rule - expression=(change_of(translan tla211 line 1 controller reset,*,*) - ,at every 00:10:00),- perc sever =critical,- desc="line1111111111111111111111111111111111111111111111111111111111111111111- line2222222222222222222222222222222222222222222222222222222222222222222222222- line3333333333333333333333333333333333333333333333333333333333333333333333333- line4444444444444444444444444444444444444444444444444444444444444444444444444- line5555555555555555555555555555555555555555555555555555555555555555555555555",- in domain svenolof enable mcc 0 alarm rule test_rule, in domain svenolof He says that MCC will accept this command but if he do a show command like SHOW MCC 0 RULE ALARM RULE TEST_RULE ALL CHAR, IN DOMAIN SVENOLOF he get the errormessage "Error encoding the rule attribute read from the MIR" "Ilvstatus = %MCC-E-NOPARAMLIST, no parameter list was supplied" He cant delete the alarm either (also gives NOPARAMLIST). The only way to get rid of it is to delete the domain. If he enter a shorter description filed (less then appr 160 characters) it works. Both MCC and the Translan AM is V1.1. I have used the command above when I tried to reproduce the problem inhouse on MCC V1.1 and Translan AM V1.0. For me it worked without any problems. Can this be a problem in the AM? Any hints on how to solve this would be appreciated. Thanks Sven-Olof
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2561.1 | poss. alarms FM bug. | MCDOUG::MCPHERSON | Save a tree: kill an ISO working group. | Fri Mar 13 1992 13:22 | 102 |
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
!
| |||||
| 2561.2 | V1.1 exists, but not from DEC | GOTA1::KLASSON | Sven-Olof Klasson @GOO | Fri Mar 13 1992 14:39 | 13 |
The customer has Translan AM V1.1 (verified by SHOW MCC 0 TRANSLAN_AM ALL CHAR). He has bought this AM from another company. I think Vitalink distributes this AM via other channels. But this is just my own guess. Any chance we can blame the AM ;-) I'll check that the appriate patches are installed. Thanks Sven-Olof Ps The description lines really means nothing. I just had to type in something when I tried to reproduce this problem. Ds | |||||
| 2561.3 | This could easily be an Alarms problem | NANOVX::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Fri Mar 13 1992 17:43 | 9 |
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 | |||||