Conference azur::mcc

5908.0. "notif. services blocked with X500 event" by 49376::MOINET () Fri Mar 11 1994 09:41

Hi,


Background:
----------
	We have a customer who is running DECmcc (V1.3.0) on a VAX/VMS machine.
The MCC machine is configured to receive several kinds of PHASE V events sunk 
from an RISC/ULTRIX station running MTA.

Configuration:
-------------
	Node A: 	VAXstation 4000-90 128 MB 
			VAX/VMS 5.5-2
			DVNEXT mup B
			DECMCCEMS 2.3
			
	Node U:		DECstation 5000-240 
			DECnet OSI 5.1 A
			
The customer has setup an outbound stream "decmcc_stream" on node U to pass all
PHASE V events to MCC_EVL_SINK on node A.

Problem:
-------
When node U is booting, DECmcc is receiving four DSA (X500) events which are 
listed in the appendix A.

At the receipt of the first event, DECmcc outputs the following message:

	notify request 4 for domain CIBA:.chbs.is.map.root encountered an error
	%MCC-F-FAILED, fatal DECmcc error

after displaying this message, the notification services does not notify any
further received events. Closing the notification window and re-opening it 
enables again the receipt of other events.

When DECmcc has an alarm defined to receive all events from DSA sub entity the 
following message is found in the log file:

	%MCC-E-NOENTITY,  no corresponding entity instance exists
	%MCC-E-NOENTITY,  no corresponding entity instance exists
	%MCC-E-NOENTITY,  no corresponding entity instance exists
	%MCC-E-NOENTITY,  no corresponding entity instance exists

Analysis:
--------
When using the GETEVENT directive to list all known events defined in the
dictionnary, I cannot see the "State Change" event that X500 is sending when 
it is started (see appendix A for events sent).

MCC> getevent node * dsa
  Type ? for a list of valid event IDs
Event: ?
    DIB Schema Inconsistent
    Invalid Reference
    Loop Detected
    Unavailable Critical Extension
    Resource Exhausted
    DIT Error
    Alias Dereferencing Problem
    Security Violation
    Protocol Violation
    Internal Error
    Any Events
Event: 

Questions :
---------
	a) Is "State Change" event missing in the dictionnary for the DSA
	   sub-entity ?

	b) Is there any mean to upgrade the dictionnary ?

	c) Could this missing definition stop the notification services
	   of receiving other subsequent events ?

Thanks in advance.
    
    Paul.
    
Appendix A
----------
From the log file of U node :

Event: State Change,
       from: Node ciba:.chbs.is.mta1 DSA
       at  : 1994-02-11-17:29:24.480+01:00I71.722

       Old State                         = Null
       New State                         = Creating

Event: State Change,
       from: Node ciba:.chbs.is.mta1 DSA
       at  : 1994-02-11-17:29:40.245+01:00I71.723

       Old State                         = Creating
       New State                         = Off

Event: State Change,
       from: Node ciba:.chbs.is.mta1 DSA
       at  : 1994-02-11-17:29:40.437+01:00I71.723

       Old State                         = Off
       New State                         = Enabling

Event: State Change,
       from: Node ciba:.chbs.is.mta1 DSA
       at  : 1994-02-11-17:29:40.999+01:00I71.723

       Old State                         = Enabling
       New State                         = On
    

Paul,

Some answers : 

a)
If you want to be sure of what is in the dictionary, use the Dictionary Browser

From the dictionary Browser, naviguate down to the appropriate sub-class of the
Node to see if it supports the "State Change" event. If it is not listed here,
then the MCC MSL is not up-to-date with what you are receiving from your
element.  

b) 
From a pure MCC point of view, the only know way is to get the right piece of
MSL, compile it and add it to the dictionary.  Not being a Phase V expert, I
don't know what is the general availability of Phase V MSLs outside of the
development group. 

c)
Your notification request encountered a fatal error -F- which means that is no
longer running. If your notification request stops exactly when the first event
was received and if you don't have other event traffic on your machine, the
logical conclusion seems to be that this unknown event caused the notification
request to stop. If you think it is the case, please submit a CLD.  

Hope this helps,

Marc.