[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

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

1109.0. "Alarm fire on adjacency down?" by SEDSWS::BAKER (Paul Baker, UK Product and Technology Group - 844 3311) Fri Jun 07 1991 11:39

    
    I've looked through this notes file for this info without success, but
    if someone knows where it is please give me a pointer.

    I'm trying to set up alarms to fire if a phase IV node goes down. The local
    designated router is sinking all events to my MCC system, and when a
    node goes down I receive a 4.18 adjacency down event. My problem is how
    to get an alarm to fire on this event, as adjacency down is not listed
    as a triggerable event when doing a "getevent node4 abcdef ?"

    I also need to be able to automatically enable all the alarms at boot
    time and have them continually active, updating any running Iconic map. 

    All ideas gratefully received.

    Paul.
T.RTitleUserPersonal
Name		DateLines
1109.1give this a tryJETSAM::WOODCOCKFri Jun 07 1991 11:5616
    
>    I've looked through this notes file for this info without success, but
>    if someone knows where it is please give me a pointer.

Note 807 gives a successful syntax for this expression. 
MCC_STARTUP_DNA4_EVL.COM must be setup and run to pass this event also.

>    I also need to be able to automatically enable all the alarms at boot
>    time and have them continually active, updating any running Iconic map. 

Submit a .com to batch which envokes MCC, enables all rules, then issue a
command with an open ended -AT EVERY- clause to keep the process running.

brad...
1109.2ThanksSEDSWS::BAKERPaul Baker, UK Product and Technology Group - 844 3311Mon Jun 10 1991 09:187
    
    Brad,
    
    Thanks for the pointer, must have mised that one. I'll give it a try.
    
    Paul.
1109.3Adjacent Events happen to Adjacent NodesTOOK::CAREYTue Jun 11 1991 14:3418
    
    Paul,
    
    One other thing to notice:  DECmcc expects events to fire against
    related entities.  In this case, the event doesn't occur against a 
    specified Node4, but against the related Adjacent Node entity,
    specified as "Node4 blah Circuit blah-blad Adjacent Node name"
    
    So if you want to see a change of adjacency on the Node4 ABCDEF, you
    could request:
    
    	GETEVENT NODE4 ABCDEF CIRCUIT * ADJ NODE * Any Event
    
    or select the specific events from the list of events available to fire
    on an adjacent node.
    
    -Jim Carey
1109.4NYFDIN::SAMBAMURTYRajaWed Feb 19 1992 13:4812
    I have tried this on T1.2.4 and it doesn't quite work (I think I read
    somewhere that the EFT has a bug). My rule is
    
    (OCCURS (NODE4 mynode CIRCUIT * ADJACENT NODE * ADJACENCY DOWN).
    
    mynode reports that adjacencies are down (I find this using the "sink"
    with rep/ena; yes I also have the MCC_*EVL running). Can someone tell
    if this is fixed in V1.2 ? Thanks
    
    reg
    
    Raja
1109.5Try the FCL getevent directiveNANOVX::ROBERTSKeith Roberts - DECmcc Toolkit TeamThu Feb 20 1992 19:5112
re: .4

  Could you try :

	getevnet NODE4 mynode CIRCUIT * ADJACENT NODE * ADJACENCY DOWN

  instead of enabling the rule.  This is the command that Alarms uses
  to get your Event Data.  If this command doesn't work correctly, then
  Alarms *can not* possible work either.

  Thanks,
  Keith
1109.6Tried and not works...NYFDIN::SAMBAMURTYRajaFri Feb 21 1992 13:5617
1109.7QAR 2183NYFDIN::SAMBAMURTYRajaFri Feb 21 1992 17:084
    Going thru the QAR database (MCC_INTERNAL), I noticed that this has
    already been entered (QAR #2183) with no response.
    
    Raja
1109.8If getevent directive is not working ... alarms OCCURS rule can't work eitherNANOVX::ROBERTSKeith Roberts - DECmcc Toolkit TeamFri Feb 21 1992 20:159
  Raja,

  If the Getevent directive is not picking up the event, the Alarms cannot
  possible get it either, as Alarms issues this same directive.

  It may be a problem in the way the Event Sink was setup ... or in the
  DNA4 AM Event code.

  /keith
1109.9problem with alarms...NYFDIN::SAMBAMURTYRajaMon Feb 24 1992 13:4013
    Keith,
    
    I think the event sink is setup ok. I had the same feature working
    under V1.1. I think this is problem in T1.2.4 (I think few other people
    have had the same problem).
    
    In my operator enabled window, I can see the adjacency up/down events
    "sinked" in. Did you try this and get this to work under T1.2.4 ? I
    would be real curious....thanks
    
    reg
    
    Raja
1109.10NYFDIN::SAMBAMURTYRajaMon Feb 24 1992 13:502
    Also, note 2158 seems to have had the same problem (and hence the QAR
    2183). There have been no solution related replies to either one.
1109.11Could someone from the DNA4-AM help here ??NANOVX::ROBERTSKeith Roberts - DECmcc Toolkit TeamMon Feb 24 1992 16:560
1109.12try new kitTOOK::JEAN_LEETue Feb 25 1992 17:5313
    Raja,
    
    	I believe this problem has been addressed and fixed in the newly
    	released base level.  The update kit was announced in MCC notesfile
    	3.135.  Please try this new kit.  Like Keith suggested, use
    	getevent directive first to make sure DNA4 has no problem.  Then
    	try alarm rule.  
    
    	DNA4 team is going thru personnel change.  Sorry we couldn't repond
    	sooner.  
    
    	Jean