[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

5215.0. "DECnet phase V event for reachability ???" by COPCLU::OVESEN (Michael Ovesen @DMO 857-2739) Thu Jun 17 1993 06:06

    We use a DECwanrouter 500 and get the below events which should
    trigger the node and reset the node back again. Using DECnet IV
    there was two event types to test for. 
    
    Is there any hints who to setup this (without testing on the another
    router running DECnet IV)
    
    Thanks for any hints
    

    This event should clear the target node:
    
Message from user SYSTEM on WATCHA
Event: ID Reachability Change from: Node WATCHA_NS:.dkwr01 Routing Circuit csmacd-0,
        at: 1993-06-17-08:04:35.30000 + 00:00 I 28147497.67107
        Adjacency Name=RTG$0804, New ID Reachability=Up, Adjacent Node=AA-00-04-00-15-0A, LANAddress=AA-00-04-00-15-0A
        eventUid   40F20D49-D96A-CC11-8040-08002B1188FA
        entityUid  C0240A94-3E66-CC11-8040-08002B1188FA
        streamUid  A0F74640-3E66-CC11-8040-08002B1188FA

    This event should set the target node to Critical
    

%%%%%%%%%%%  OPCOM  17-JUN-1993 08:22:20.57  %%%%%%%%%%%
Message from user SYSTEM on WATCHA
Event: ID Reachability Change from: Node WATCHA_NS:.dkwr01 Routing Circuit csmacd-0,
        at: 1993-06-17-08:18:02.64000 + 00:00 I 28147497.67107
        Adjacency Name=RTG$07CA, New ID Reachability=Down, Adjacent Node=AA-00-04-00-FC-09, Reason=Holding Timer Expired, LANAddress=AA-00-04-00-FC-09
        eventUid   0041442A-DB6A-CC11-8040-08002B1188FA
        entityUid  C0240A94-3E66-CC11-8040-08002B1188FA
        streamUid  A0F74640-3E66-CC11-8040-08002B1188FA

T.R Title User Personal
Name Date Lines

5215.1 Not possible RDGENG::PRATT Thu Jun 17 1993 09:44 18

T.R	Title	User	Personal Name	Date	Lines
5215.1	Not possible	RDGENG::PRATT		`Thu Jun 17 1993 09:44`	18
	Hi, Unfortunately the current versions of Polycenter do not allow you to write alarm rules or notifications that check for an alarm rule argument. The phaseV architecture specifies a common event, with the important attributes passed as arguments. In this case the common event is ID Reachability Change, and the argument is New ID Reachability (Up/Down). This lack of functionality has been reported to Network Management Engineering by EASYnet/Corporate Telecoms, however I do not have any idea when (or if) it will be implemented. A workaround would be to write some DCL that would parse the event argument, and then use the collector to change the colour of the icon as appropriate. Ian

Hi,

Unfortunately the current versions of Polycenter do not allow you to write alarm
rules or notifications that check for an alarm rule argument. The phaseV
architecture specifies a common event, with the important attributes passed as
arguments.

In this case the common event is ID Reachability Change, and the argument is 
New ID Reachability (Up/Down).

This lack of functionality has been reported to Network Management Engineering
by EASYnet/Corporate Telecoms, however I do not have any idea when (or if) it
will be implemented.

A workaround would be to write some DCL that would parse the event argument, and
then use the collector to change the colour of the icon as appropriate.

Ian