[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

5475.0. "can't target events to the icon" by NWTIMA::BAKER (Tom Baker - dtn 548-8849) Thu Aug 12 1993 19:02

    I have a customer witrh the following problem. Does anyone know the
    answer to his question.
    
    Thanks,
    
    Tom
    =======================================================================
Polycenter (MCC) 1.3 cannot target EVENTs to the Icon for interfaces on 
a network node. 
I've got a snmp device with 4 interfaces that is capable of sending linkup, 
linkdown traps for the interfaces. 
Under 1.2 and 1.3 Field Test, I was able to get this to work, since the 
revenue ship, it has never worked. 
What I am trying to do is target the linkup/down event directly to an icon 
representing the interface, rather than the box the interface resides in. 
For example: 

notify request
entity=snmp *   event=linkup,linkdown 
target 
entity  event   managed object          target entity           severity 
snmp * linkup   snmp #1 interface #2    snmp #1 interface #2    MAJOR 
snmp * linkdown snmp #1 interface #2    snmp #1 interface #2    MAJOR 
Under field test, this would result in the interface icon changing color. 
(the interfaces were added to the map by looking into the snmp toolbox object)
Vital stats are 
On DECstation 5000/240
Ultrix 4.3 
Decnet OSI 5.1 
Polycenter Framework (MCC) 1.3 

The customer wants to know Is this intended to work in v1.3 and if so, what 
changes to the syntax are required or when will a fix be available. 
Workaround requires excessive customer intervention/programming to implement 
functionality which was present in previous releases. 

Articles in notes files show how to parse the event message and turn the 
interface in question the appropriate color but this requires a good 
deal of effort from the customer to setup. 
    
T.RTitleUserPersonal
Name
DateLines
5475.1SPR submitted ; a possible workaround...ZTOIS1::VISTARenato VISTA, MCS/SPS France/StrasbourgMon Aug 16 1993 05:1224
    
    
    Tom,
    
    I have submitting an SPR last MAY about the expected functionality
    consisting to notify a subtree within a SNMP/MIB tree (standard,
    extended & private) (ie SNMP * INTERFACE, SNMP * CHIPCOM CHIPMIB02
    OLPORTTABLE (x,y), ...), using particularly the variables sent the
    SNMP/Traps asynchronous events.
    
    Further, to offer on my own customer platform, combining NOTIFICATION
    FM, SNMP/TCPIP AM & COLLECTOR AM, I've developed a simple mechanism
    allowing SNMP subtrees, decoding generic events such as LinkUp,
    LinkDown, but also CHIPCOM events such as chipPortUP, chipPortDOWN,
    chipSlotUP, chipSlotDOWN, chipTrunkUp, chipTrunkDOWN (both on ULTRIX &
    VMS platforms) ; it is also possible to precise SELECTED <ENTITIES> (ie
    SELECTED INTERFACE (1) (3) (9), ...
    
    Depending of what you need and what you want to do, it is simply
    possible to adapt these C-Shell/AWK procedures.
    
    Renato