[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

4125.0. "Notification brocken for DECnet events" by BERN02::FUCHS (FRED FUCHS) Fri Nov 20 1992 15:13

    DECmcc BMS V.1.2.0 on VAX Station 3100/48 with DECdns installed at a 
    Customer site.
    
    Notification and Targeting for DECnet Events
    was setup and running for more than a month.
    
    Now, a week a go we have created a new domain and moved some 
    entities into the new domain. Notification worked in the new domain
    but not in the "old" one.
    "Old" domain .mcc.gs  
    "New created deomain" .mcc.gspc
    
    So we deleted all notifications and retargetings. Then we rebootet 
    the System and createt new notifications and retargetings.
    
    But now the tification is brocken for DECnet events in all domains.
    We see notification for alarm rules and collector AM.
    
    We also see some events with teh GETEVENT directive but not with the 
    FCL NOTIFY request.
    
    We created new domains with the same result.  
    We checked the MCC_DNA4_EVL.LOG. All seems to be ok. Then we enrolled
    the ALARM and NOTIFY FM new but it ditn't help.
    
    Anhelp will be appreciated
    
    Fred and Edgar
T.RTitleUserPersonal
Name		DateLines
4125.1more information, pleaseTOOK::S_KOHoot mon!Tue Nov 24 1992 09:1416
    
    how many systems are synching their events to your DECmcc system?
    
    Please check the outbound stream remote sink monitor setup for the
    local node and for each node synching their events to your DECmcc
    system:
    
    mcc> show node4 <n1> outb stream <sink_node> remote sink monitor all char
    	
    	where <n1> is the node which is sending events
    	and <sink_node> is the node receiving the events (the DECmcc
    	    system)
    
    please check sys$manager:evl.log for any errors.
    
    what events do you see coming through using GETEVENT?
4125.2Requested informationsBERN01::GMUERThu Nov 26 1992 06:06196
Here are the requested informations:

Event sinking and forwarding:

GSEDI0>mana/enter
DECmcc (V1.2.0)

MCC> show node4 gsedi4 outb stream gsedi0 remote sink moni all chara

Node4 59.4 Outbound Stream 59.10 Remote Sink Monitor
AT 26-NOV-1992 11:17:21 Characteristics

Examination of Attributes shows:
                           EventsFilter = { (
                                     Choice = C5,
                              Source_Entity = All Sources,
                                      Event = { 0.0 event records lost,
                                                0.4 line counters zeroed,
                                                0.5 node counters zeroed,
                                                0.6 Passive loopback,
                                                0.7 Aborted service request,
                                                0.9 Counters zeroed } ),
                                           (
                                    Choice = C5,
                              Source_Entity = All Sources,
                                      Event = { 2.0 Local node state change,
                                                2.1 Access control reject } ),
                                            (
                                     Choice = C5,
                              Source_Entity = All Sources,
                                      Event = { 3.1 Invalid flow control,
                                                3.2 Data base reused }),
                                            (
                                     Choice = C5,
                              Source_Entity = All Sources,
                                      Event = { 4.0 Aged packet loss,
                                                4.1 Node unreachable packet loss ,
                                                4.2 Node out-of-range packet
                                                    loss,
                                                4.3 Oversized packet loss,
                                                4.4 Packet format error,
                                                4.5 Partial routing update loss,

                                                4.6 Verification reject,
                                                4.8 Circuit down,
                                                4.9 Circuit down operator
                                                initiated,
                                                4.10 Circuit up,
                                                4.11 Initialization failure
                                                line fault,
                                                4.12 Initialization failure,
                                                4.14 Node reachability change,
                                                4.15 Adjacency up,
                                                4.16 Adjacency rejected,
                                                4.17 Area reachability change,
                                                4.18 Adjacency down } ),
                                           (
                                     Choice = C5,
                              Source_Entity = All Sources,
                                      Event = { 5.3 Send error threshold,
                                                5.4 Receive error threshold,
                                                5.14 Send failure on line,
                                                5.15 Receive failed on line or
                                                circuit } ),
                                            (
                                     Choice = C5,
                              Source_Entity = All Sources,
                                      Event = { 6.0 Data set ready transition,
                                                6.2 Unexpected carrier
                                                transition } ) }
mcc>


GSEDI0>mc ncp show loggi moni


Logging Volatile Summary as of 26-NOV-1992 12:05:13


 Logging sink type = monitor

    Sink Node       Source               Events                   State Name

                                                                   on
   59.10 (GSEDI0)   (All sources)        4.0-19               MCC_DNA4_EVL

GSEDI0>


Here is one example for a GETEVENT directive. I could not test more,
because I am remote to the customer:


MCC> getevent node4 * circuit * adjacent node *
  Type ? for a list of valid event IDs
Event: any event

Node4 59.4 Circuit ETHER-1 Adjacent Node 59.92
AT 26-NOV-1992 11:58:59 Any Event

Successfully received events:
Event: Adjacency Down
 Adjacency Down
                                 Reason = Adjacency listener receive
timeout
                  Adjacent Node Address = 59.92
MCC> show node4 59.4
Using default ALL IDENTIFIERS

Node4 59.4
AT 26-NOV-1992 12:00:23 Identifiers

Examination of Attributes shows:
                                Address = 59.4
                                   Name = GSEDI4
MCC>


Other informations which may be usefull:

Open files on system disk:

EVL             00000090  [SYS0.SYSMGR]EVL.LOG;37
EVL             00000090  [VMS$COMMON.SYSEXE]EVL.COM;1
EVL             00000090  [VMS$COMMON.SYSEXE]EVL.EXE;1
EVL             00000090  [VMS$COMMON.SYSMSG]NETWRKMSG.EXE;1
MCC_DNA4_EVL    000000B0  [VMS$COMMON.SYSEXE]MCC_MAIN.EXE;2
MCC_DNA4_EVL    000000B0  [VMS$COMMON.SYSLIB]CMA$LIB_SHR.EXE;2
MCC_DNA4_EVL    000000B0  [VMS$COMMON.SYSLIB]CMA$RTL.EXE;2
MCC_DNA4_EVL    000000B0  [VMS$COMMON.SYSLIB]CMA$OPEN_RTL.EXE;2
MCC_DNA4_EVL    000000B0  [VMS$COMMON.SYSLIB]CMA$OPEN_LIB_SHR.EXE;2
MCC_DNA4_EVL    000000B0  [VMS$COMMON.SYSLIB]MCC_DNA4_EVL.EXE;2


Open files on disk with MCC account:

MCC_DNA4_EVL    000000B0  [NETMAN]MCC_DNA4_EVL.LOG;2
MCC_DNA4_EVL    000000B0  [MCC]MCC_DNA4_EVL.COM;2


Log files and history:

WORK3:[NETMAN]MCC_DNA4_EVL.LOG;2
....
$ manage/enter/presen=mcc_dna4_evl
Declared network object MCC_DNA4_EVL,20-NOV-1992 16:25:22.60
Wait for EVL link,20-NOV-1992 16:25:22.60
Connected to EVL,20-NOV-1992 16:25:37.76


WORK3:[NETMAN]MCC_DNA4_EVL.LOG;1
....
$ manage/enter/presen=mcc_dna4_evl
Declared network object MCC_DNA4_EVL,20-NOV-1992 16:22:58.49
Wait for EVL link,20-NOV-1992 16:22:58.50


SYS$SYSROOT:[SYSMGR]MCC_DNA4_EVL.LOG;17
....
$ manage/enter/presen=mcc_dna4_evl
Declared network object MCC_DNA4_EVL,20-NOV-1992 15:01:26.12
Wait for EVL link,20-NOV-1992 15:01:26.13
Connected to EVL,20-NOV-1992 15:07:07.60


SYS$SYSROOT:[SYSMGR]MCC_DNA4_EVL.LOG;16
....
$ manage/enter/presen=mcc_dna4_evl
Declared network object MCC_DNA4_EVL, 9-NOV-1992 10:34:32.96
Wait for EVL link, 9-NOV-1992 10:34:32.97


SYS$SYSROOT:[SYSMGR]EVL.LOG;37
....
!  Copyright (c) 1987 Digital Equipment Corporation.  All rights reserved.
$ SET NOON
$ IF "" .NES. "" THEN EVL$COMMAND
$ RUN SYS$SYSTEM:EVL


SYS$SYSROOT:[SYSMGR]EVL.LOG;36  <-- This file was created on 9-NOV-1992 10:31
....
$ !  Copyright (c) 1987 Digital Equipment Corporation.  All rights reserved.
$ SET NOON
$ IF "" .NES. "" THEN EVL$COMMAND
$ RUN SYS$SYSTEM:EVL
%EVL-E-OPENMON, error creating logical link to monitor process GSEDI0::"TASK=MCC
_DNA4_EVL"
-SYSTEM-F-INVLOGIN, login information invalid at remote node
%EVL-E-WRITEMON, error writing event record to monitor process MCC_DNA4_EVL
-SYSTEM-F-FILNOTACC, file not accessed on channel
$ PURGE/KEEP=3 EVL.LOG
$ LOGOUT/BRIEF
  DECNET       job terminated at 20-NOV-1992 14:55:52.46
4125.3a few more questionsTOOK::S_KOHoot mon!Wed Dec 02 1992 08:5233
    hi,

    a few comments and a couple more questions...

    o	the DECmcc host system (gsedi0) is filtering all events except for
    	4.0-19, so any of the other events being sent from gsedi4 are
     	ignored.

    o   when the node4 GSEDI0 local sink monitor was enabled from the
    	SYSTEM account (see SYS$SYSROOT:[SYSMGR]MCC_DNA4_EVL.LOG;16)
    	no connection was made from DECnet EVL to the MCC EVL monitor
    	program.

    o   the EVL log file from Nov 9 indicates that the EVL process on the
    	sending system cannot create a link to the DECmcc host system
    	GSEDI0 because the login information is invalid for the account
    	associated with TASK object.

    o   please check the EVL.LOG files on the systems synching their
    	events to the DECmcc host.  Do you see any errors logged
    	indicating a problem connecting to GSEDI0?

    o	Please make sure that the node4 entities (eg - GSEDI4) are fully 
    	registered and in the selected domain where the notify requests 
    	apply.
    	    
    o	What do your notify requests look like?  We are currently looking
    	at a problem with notify requests that specify specific events.
    
    thank you,
    -s
4125.4Correlated with domainsBERN01::GMUERFri Dec 04 1992 04:32219
Thanks for your reply. Here are some more informations which shows that
the problem must have something to do with the domain structures:


1) I have setup the event sinking on the router GSEDI4 and the MCC
   station GSEDI0:

$ mc ncp tell gsedi4 show loggi moni
 
 Logging Volatile Summary as of  3-DEC-1992 17:55:10
 
 Logging sink type = monitor
 
    Sink Node       Source               Events                   State Name
 
   59.10 (GSEDI0.)  (All sources)        0.0 4-7 9
                    (All sources)        2.0-1
                    (All sources)        3.1-2
                    (All sources)        4.0-6 8-12
                                         14-18 
                    (All sources)        5.3-4 14-15
                    (All sources)        6.0 2


$ mc ncp show loggi moni
  
Logging Volatile Summary as of  3-DEC-1992 17:55:11
 
 Logging sink type = monitor
 
    Sink Node       Source               Events                   State Name
 
                                                                   on
   59.10 (GSEDI0)   (All sources)        0.0-9                MCC_DNA4_EVL
                    (All sources)        2.0-1
                    (All sources)        3.0-2
                    (All sources)        4.0-19
                    (All sources)        5.0-21
                    (All sources)        6.0-5
                    (All sources)        7.0-11




2) The event sink logs are now OK:

File EVL.LOG:

$ !  Copyright (c) 1987 Digital Equipment Corporation.  All rights reserved.
$ SET NOON
$ IF "" .NES. "" THEN EVL$COMMAND
$ RUN SYS$SYSTEM:EVL


File MCC-DNA4_EVL.LOG:

$ manage/enter/presen=mcc_dna4_evl
Declared network object MCC_DNA4_EVL, 3-DEC-1992 17:23:48.13
Wait for EVL link, 3-DEC-1992 17:23:48.14
Connected to EVL, 3-DEC-1992 17:24:46.46



3) I have setup following procedure to test the notification for the
adjacency of a node4:

$ mana/enter
   dir node4 gsedi4
   show domain ??? member .edi-gs.gs.gsedi4
   notify domain ??? enti list = (node4 * circuit * adjacent node *),-
     event = (adjacency down, adjacency up)
   getevent node4 * circuit * adjacent node * any event
   display notif
   getevent node4 * circuit * adjacent node * any event
   exit



4) I have created a new domain TEST with some node4 entities. This domain
is not a member of any old domains and contains no other domains. The 
notification (Notif window and FCL) works for this domain !!

$ mana/enter
DECmcc (V1.2.0)

   dir node4 gsedi4

Node4 gsedi4 
AT  3-DEC-1992 17:55:21 

Directory successful.
                        Registered Name = EDI:.edi-gs.gs.gsedi4
                                   Name = GSEDI4
                                Address = 59.4
   show domain .test member .edi-gs.gs.gsedi4
Using default ALL IDENTIFIERS

Domain EDI:.test Member EDI:.edi-gs.gs.gsedi4 
AT  3-DEC-1992 17:55:23 Identifiers

Examination of attributes shows
                             MemberName = EDI:.edi-gs.gs.gsedi4
   notify domain .test enti list = (node4 * circuit * adjacent node *),-
     event = (adjacency down, adjacency up)
%MCC-S-NOTIFSTART, Notify request 1 started
   getevent node4 * circuit * adjacent node * any event

Node4 59.4 Circuit ETHER-1 Adjacent Node 59.11 
AT  3-DEC-1992 17:56:38 Any Event

Successfully received events: 
Event: Adjacency up
 Adjacency Up 
                  Adjacent Node Address = 59.11
   display notif

Notify requests currently in progress:

Entry  Status   Command
-----  ------   -------
    1  Running     notify domain .test enti list = (node4 * circuit * adjacent 
                node *),     event = (adjacency down, adjacency up)

   getevent node4 * circuit * adjacent node * any event

%%%%%%%%%%%%%% Event,  3-DEC-1992 17:56:40 %%%%%%%%%%%%%% [1]
Domain: EDI:.test                                     Severity: Indeterminate
Notification Entity: Node4 EDI:.edi-gs.gs.gsedi4 Circuit ETHER-1 Adjacent Node 59.11 
Event Source: Node4 EDI:.edi-gs.gs.gsedi4 Circuit ETHER-1 Adjacent Node 59.11 
Successfully received events: 
Event: Adjacency up
 Adjacency Up 
                  Adjacent Node Address = 59.11



%%%%%%%%%%%%%% Event,  3-DEC-1992 17:59:36 %%%%%%%%%%%%%% [1]
Domain: EDI:.test                                     Severity: Indeterminate
Notification Entity: Node4 EDI:.edi-gs.gs.gsedi4 Circuit ETHER-1 Adjacent Node 59.11 
Event Source: Node4 EDI:.edi-gs.gs.gsedi4 Circuit ETHER-1 Adjacent Node 59.11 
Successfully received events: 
Event: Adjacency Down
 Adjacency Down 
                                 Reason = Adjacency listener receive timeout
                  Adjacent Node Address = 59.11



Node4 59.4 Circuit ETHER-1 Adjacent Node 59.11 
AT  3-DEC-1992 17:59:36 Any Event

Successfully received events: 
Event: Adjacency Down
 Adjacency Down 
                                 Reason = Adjacency listener receive timeout
                  Adjacent Node Address = 59.11
   exit



5) Back to the old domain .mcc.gs there is still no reaction in the 
notification window or in the FCL interface:

$ mana/enter
DECmcc (V1.2.0)

   dir node4 gsedi4

Node4 gsedi4 
AT  3-DEC-1992 18:02:59 

Directory successful.
                        Registered Name = EDI:.edi-gs.gs.gsedi4
                                   Name = GSEDI4
                                Address = 59.4
   show domain .mcc.gs member .edi-gs.gs.gsedi4
Using default ALL IDENTIFIERS

Domain EDI:.mcc.gs Member EDI:.edi-gs.gs.gsedi4 
AT  3-DEC-1992 18:03:02 Identifiers

Examination of attributes shows
                             MemberName = EDI:.edi-gs.gs.gsedi4
   notify domain .mcc.gs enti list = (node4 * circuit * adjacent node *),-
     event = (adjacency down, adjacency up)
%MCC-S-NOTIFSTART, Notify request 1 started
   getevent node4 * circuit * adjacent node * any event

Node4 59.4 Circuit ETHER-1 Adjacent Node 59.11 
AT  3-DEC-1992 18:04:34 Any Event

Successfully received events: 
Event: Adjacency up
 Adjacency Up 
                  Adjacent Node Address = 59.11
   display notif

Notify requests currently in progress:

Entry  Status   Command
-----  ------   -------
    1  Running     notify domain .mcc.gs enti list = (node4 * circuit * 
                adjacent node *),     event = (adjacency down, adjacency up)

   getevent node4 * circuit * adjacent node * any event

Node4 59.4 Circuit ETHER-1 Adjacent Node 59.11 
AT  3-DEC-1992 18:06:34 Any Event

Successfully received events: 
Event: Adjacency Down
 Adjacency Down 
                                 Reason = Adjacency listener receive timeout
                  Adjacent Node Address = 59.11
   exit



Regards, Edgar
4125.5Domain tree perhaps corrupted by a loopBERN01::GMUERTue Dec 08 1992 12:039
Another hint,

My colleague (Fred Fuchs), who was out for a week, told me that there was
once a message about a loop in the domains. Although we have no loop today
this may have corrupted the domain tree structure.

We would be happy for an answer, because we do not know how to proceed.

Regards, Edgar and Fred
4125.6please check the domainTOOK::S_KOHoot mon!Mon Dec 14 1992 19:5615
    
    
    please show output for the following requests:
    
    	mcc> show domain .test all attr
    	mcc> show domain .test member * all attr
    
    	mcc> show domain mcc.gs all attr
    	mcc> show domain mcc.gs member * all attr
    
    if you do not see any evidence of corrupted domain, could you please
    make notify requests in the two domains (one at a time) with the
    logical MCC_NOTIFICATION_FM_LOG set to 6 and post the output?
4125.7More info by VAXmailBERN01::GMUERThu Dec 17 1992 11:035
Hallo Stella

I have sent you two log-files by VAXmail with the requested information.

Regards, Edgar