| 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 |
Can someone help me with Phase event alarming.
Am receiving events from the WANrouter.
mcc fcl
--------
getevent node PAUL01 routing circuit * any event,to file working.txt
Node MCC_NS:.PAUL01 Routing Circuit syn-0-0
AT 29-MAR-1992 22:18:04 CONFIGURATION EVENTS <---------IS THIS A EVENT
TRIGGER
Successfully received events:
Event: Circuit Change <--------- I THOUGHT THIS IS THE EVENT TRIGGER
New Circuit State = off <------ CAN I INCLUDE THIS
IN THE OCCURS ALARM RULE
(HOPE SO, IF NOT THERE HAS
BEEN A BALLS-UP)
---------------------------------------------------------------------------
getevent node PAUL01 routing circuit * circuit change ,to file working.txt
Node MCC_NS:.PAUL01 Routing Circuit syn-0-0
AT 29-MAR-1992 22:07:33 Any Event
Successfully received events:
Event: Circuit Change
New Circuit State = on
---------------------------------------------------------------------------
getevent node PAUL01 routi circ syn-0-0 circu change ,to file working.txt
Node MCC_NS:.PAUL01 Routing Circuit syn-0-0
AT 29-MAR-1992 22:09:18 CONFIGURATION EVENTS
Successfully received events:
Event: Circuit Change
New Circuit State = on
---------------------------------------------------------------------------
getevent node PAUL01 routi circ syn-0-0 circu change ,to file working.txt
Node MCC_NS:.PAUL01 Routing Circuit syn-0-0
AT 29-MAR-1992 22:09:29 CONFIGURATION EVENTS
Successfully received events:
Event: Circuit Change
New Circuit State = off
-=-------------------------------------------------------------------------
MCC FCL USE MODE FORM
=======================
MCC 0 ALARMS RULE becky
AT 29-MAR-1992 22:10:36 All Attributes
NAME = becky
State = Disabled
Substate = Disabled by error condition
Disable Time = 29-MAR-1992 21:51:32.84
> Error Condition = "%MCC-E-INV_IN_P, invalid argument or
> attribute , The rule has been
> disabled
"
Time of Last Evaluation = 29-MAR-1992 21:51:32.29
Result of Last Evaluation = Error
Current Severity = Indeterminate
Error Entity = Node MCC_NS:.PAUL01 Routing Circuit
syn-0-0
Creation Timestamp = 29-MAR-1992 21:51:31.03
Evaluation Error = 0
Evaluation True = 0
Evaluation False = 0
Expression = (occurs(node .PAUL01 routing circuit
>WHATS MISSING "NO SYNTAX ERROR" syn-0-0 circuit change))
Perceived Severity = Indeterminate
Probable Cause = Unknown
I can find any documentation to help with Phasev alarm rules.
The FCL help is a waste of time and the error message fails to give me any
clues.
A few sample OSI alarms rule would be great.
occurs rule
polling rules etc
Gary
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2660.1 | need to coordinate this with phase-5 team | MOLAR::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Tue Mar 31 1992 12:04 | 8 |
Sorry but you can not write a rule on Event Arguments 8( As far as the error condition (Invalid In-P) .. the Alarms Team must coordinate this with DECnet Phase 5 team, to figure out why the GETEVENT NODE <foo> directive (Alarms uses this directive to get the events from the Phase-5 am) is returning this error code. /keith | |||||
| 2660.2 | QARed? | RDGENG::PRATT | Wed Apr 01 1992 09:15 | 4 | |
As I raised this same problem in 2585 can someone check that it has actually been QARed. Ian | |||||
| 2660.3 | Try events generated by HDLC | RDGENG::PRATT | Wed Apr 01 1992 10:11 | 28 | |
Gary, Re .0 You should be able to resolve you circuit up/down problem by setting your alarm to look for the following events... HDLC LINK xxx Link Up and HDLC LINK xxx Link Down or possibly HDLC LINK xxx LOGICAL STATION xxx Station Halted and HDLC LINK XXX LOGICAL STATION xxx Station Running Although you will not be able to test/prove these until the bug with GetEvent has been fixed (although you could use Any Event as temp solution - this is what I'm currently using). Cheers Ian | |||||
| 2660.4 | Alarms is building the Event Id List correctly | MOLAR::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Wed Apr 01 1992 10:39 | 12 |
RE: .2 The QAR on how Alarms builds the Event Id List (used by the GetEvent directive to specify which events are wanted) is built correctly. The QAR which was filed on this was a mistake -- the real problem was something else. In the mean time, I am trying to find out why the Invalid In-P error is getting generated for this Rule. /keith | |||||
| 2660.5 | DNA5 AM Validation of In-P | MOLAR::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Thu Apr 02 1992 08:40 | 8 |
I checked with the DNA5 AM team about how the In-P Call Argument is validated. They are checking the Descriptor 'dtype' field for a specific value. Alarms is not setting this field. The DNA5 team will be changing their validation code to not check this field. I imagine this fix will be in the Field Test Update kit. /keith | |||||