[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

4754.0. "targeting on multiple events" by COMICS::MISTRY () Wed Mar 24 1993 05:50

Hi,


I think that there is a problem with MCC V1.3 SSB and targeting. If you set up
the following notification from the iconic map.

Domain :  fred_ns:.phaseiv

Entity List: Node4 fred_ns:.xxxx circuit yyyy

Events: Circuit down, circuit down circuit fault, circuit down operator 
        initiated

Then that notifies you on any of the three events occuring, which is fine. If
however you then target these events to another entity:

Domain: fred_ns:.phaseiv

Event source : node4 fred_ns:.xxxx circuit yyyy

Event name: Circuit down, circuit down circuit fault, circuit down operator
	    initiated

Managed Object: node4 fred_ns:.xxxx circuit yyyy

Target entity: circuit zzzz

Target severity: critical

Then if a circuit down event comes in all works fine. If however, a circuit
down circuit fault or circuit down operator initiated come in then the event
isn't re-targeted. It looks as if the target code is only looking at the first
entry and isn't doing a complete search.

Bipin.
T.RTitleUserPersonal
Name		DateLines
4754.1more information pleaseTOOK::S_KOHoot mon!Fri Apr 02 1993 15:003
    
    Please show the target assignments for domain .phaseiv
    (eg - dir target domain .phaseiv)
4754.2more infoCOMICS::MISTRYMon Apr 05 1993 07:5920
Hi,


Sorry about the delay, here is the info you requested:


Event Source			Event Name 

Node4 xrou1 Circuit decnet	Circuit down operator initiated,ciruit down,
				circuit down circuit fault


Managed object			Target entity		Target Severity

Node4 xrou1 circuit decnet	circuit decnet		critical


I hope this helps

Bipin.
4754.3only one event per target assignmentTOOK::S_KOHoot mon!Mon Apr 05 1993 18:2520
    
    Make a separate assignment for each event:
    
    Assignment #1:
      Event Source	node4 xrou1 circuit decnet    
      Event Name	circuit down operator initiated 
      Target Entity	circuit decnet
      Target Severity	critical
    
    Assignment #2:
      Event Source	node4 xrou1 circuit decnet    
      Event Name	circuit down 	
      Target Entity	circuit decnet
      Target Severity	critical
    
    Assignment #3:
      Event Source	node4 xrou1 circuit decnet    
      Event Name	circuit down circuit fault      
      Target Entity	circuit decnet
      Target Severity	critical
4754.4bug or featureCOMICS::MISTRYTue Apr 06 1993 05:439
Hi,


Ok thats the workaround, but if the target assignment allows you to enter
multiple event conditions then i would expect it to work. Notification allows
you to enter multiple event statements and it works. So, is this a bug or a 
feature.

Bipin.
4754.5bugTOOK::CALLANDERMCC = My Constant CompanionWed Apr 28 1993 13:124
    it is a bug, the notification assign target command should have
    returned an error on finding more than one event specified in
    the command.  It only supports one per target command.
4754.6Another targeting limitation.CSC32::W_MCGAWFri Apr 30 1993 19:3835
    Hi,
    
    I have another BUG / FEATURE to report on targeting.  When you use
    wildcard targeting you can only enter 4 different event types.  If you
    enter the 5th event type for the same entity, the first four dissappear
    and only the last entry stays.
    
    EG:
    
    $ set verify
    $ manage/ent
    use verify
    !
            Assign Target DOMAIN TEST -
                Event Source= Node4 * Circuit * Adjacent Node *, -
                Event Name  = "Circuit Up",        -
                Managed Object  = "Node4 #1  Circuit #2 Adjacent Node #3",   -
                Target Entity   = "Node4 #3",                   -
                Target Severity = CLEAR
    
    Now enter this same assign command 4 more times only changing the event
    name.  Do a directory targets domain test after each assign command and
    you will see each get entered but upon entering the 5th assign, the
    first four will be gone.  This is also the behavior with the event
    sources of NODE4 * LINE * and NODE4 * CIRCUIT *.  The same applies if
    the notifications are added via the iconic map instead of FCL.  With
    the iconic map, it looks as though the targets are being assigned
    correctly but if you click on update display, you discover that not all
    of the targets are really there.
    
    Any suggestions for my customer to work around this problem?
    
    Walt McGaw
    CSC/CS
    Network Support