[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

1815.0. "EVL crashes." by HOO78C::DOOLAARD (All for the best) Thu Nov 14 1991 09:50

    I'm having the following problem with EVL:
    
    MCC_DNA4_EVL keeps crashing the following way,
    
    Network object MCC_DNA4_EVL is declared, Status = 52854793
    Tracing error paths in Event Manager
    Waiting for the event message from EVL.....
    The connection with EVL is established.
    ** Connected to NMCC successfully **
    Ready to read the next event message...
    Ready to read the next event message...
    Ready to read the next event message...
    Ready to read the next event message...
    Ready to read the next event message...
    Ready to read the next event message...
    Ready to read the next event message...
    Ready to read the next event message...
    
    ...................
    Ready to read the next event message...
    Ready to read the next event message...
    Ready to read the next event message...
    Failed to receive an event from EVL, status = 8420
    EDQ_DEQW_SUBSCR_EVENT found alert termination request
    Get Event was Alerted
    OPS_DNA4_STOP_SINK_MONITOR Failed at step 5, status = 52877226
    STOP_SINK_MONITOR is terminated, thread id = 65539, status=52854793
    %SYSTEM-F-LINKABORT, network partner aborted logical link
      SYSTEM       job terminated at 13-NOV-1991 20:30:55.53
    
    
    The multi processor patch is already installed although the node isn't
    a multi processor. The patch did improve the crashing frequency from
    almost emidiately to about 10 hours (see note 1720)
    Also the error message isn't the same as in note 1720.
    
    This frequently crashing of EVL makes alarming on DECnet events very
    unreliable.
    
    Please advise.
    
    Carlo.

T.R Title User Personal
Name Date Lines

1815.1 try note 807 JETSAM::WOODCOCK Thu Nov 14 1991 12:58 14

T.R	Title	User	Personal Name	Date	Lines
1815.1	try note 807	JETSAM::WOODCOCK		`Thu Nov 14 1991 12:58`	14
	Hi, I'm not sure if this is an identical problem because the initial error at a glance looks a bit different than what I remember, but the end result of a LINKABORT is the same. You can try note 807 if you'd like to try and ease the pain. I might help. Also what I do is put an icon of the mngmt station in the top domain, write an occurs rule for "automatic counters", and enable it in the mainline batch which starts all rules. I set the counter timer for the ENET circuit to something like every 20 minutes and the icon changes color (green for go if you like) to ensure the integrity of all the alarms processes running. been there, brad...

Hi,

I'm not sure if this is an identical problem because the initial error at
a glance looks a bit different than what I remember, but the end result
of a LINKABORT is the same. You can try note 807 if you'd like to try and
ease the pain. I might help. Also what I do is put an icon of the mngmt
station in the top domain, write an occurs rule for "automatic counters",
and enable it in the mainline batch which starts all rules. I set the
counter timer for the ENET circuit to something like every 20 minutes and
the icon changes color (green for go if you like) to ensure the integrity
of all the alarms processes running.

been there,
brad...