Conference azur::mcc

    
    I am also seeing this problem.  The very first command you pass either
    enable or disable seems to work if the exec has been just set to state
    on.

    basically the dna4 event logging is not working.\

    I manually entered the sink data against the logging monitor in the
    permanent database, when I restart the exec the dna4 process is now
    running, I then issue the commands to set up the streams which all
    execute OK -- but alas no events

    Amrit

	Hi Christine -
	   Below is the portion of the release notes that is relevant
	to you.
        First let me ask you a few questions.
	( 1 ) did this work under T1.2.7?

	( 2 ) has anything changed on your system since T1.2.7?

        ( 3 ) have you set the initial and volatile name to
              mcc_dna4_evl_monitor?
              MCC> SET node4 <local node> local sink MONITOR name /usr/etc/mcc_dna4_evl_monitor, -
	           by user root, by password <>
              MCC> SET node4 <local node> local sink MONITOR initial name /usr/etc/mcc_dna4_evl_monitor, -
	           by user root, by password <>

        ( 4 ) you should try the following and see if you
              have any success:
              ncp> set exec state off
              ncp> set exec state on
              % ls -l /tmp/*evl*
                >>> this should contain:
                    evl_prc_log, evl_prc_pid and mcc_dna4_evl_pipe
              % ls -l /usr/etc/*evl*
                >>> this should contain:
                    evl, evl.mcc and mcc_dna4_evl_monitor

        ( 5 ) review the release notes below

        ( 6 ) Please call or send mail to me at:
              226-5345
              took::d_ball or Kitfox::ball






- darryl

=============================================================================
================ release notes ==============================================
=============================================================================
        4.6     DECnet PHASE IV ACCESS MODULE  . . . . . . . . .  4-13
        4.6.4     ULTRIX DECnet Phase IV Event Management  . . .  4-16
     4.6  DECnet PHASE IV ACCESS MODULE
     4.6.4  ULTRIX DECnet Phase IV Event Management

     The installation kit contains a special EVL image evl.mcc.
     During the DECmcc installation, this file is placed in the
     /usr/etc directory.

     Use this special EVL image only if you wish to use the DECmcc
     DECnet Phase IV event monitor to receive event messages.  This
     EVL image sends event messages in the binary NICE-coded format
     whereas the original EVL image sends ASCII text.

     Their functions are the same in all other aspects.  If you choose
     to use an event monitor other than DECmcc to receive event
     messages from EVL, you should switch the EVL image to the
     original EVL by copying /usr/etc/evl.original to /usr/etc/evl.

     After DECmcc installation is complete, perform the following
     steps to install the new EVL image and enable the DECmcc DECnet
     Phase IV   event sink monitor:

     1.  You must become the superuser (root) account to perform this
         task by either logging into the root account or switching
         user to root via the %su command.

     2.  Define the event sink monitor name to be
         mcc_dna4_evl_monitor.  In order for the change to be
         automatically effective at network startup time, it is made
         to the permanent database.

         MCC> set Node4 0 local sink monitor initial name -
         /usr/etc/mcc_dna4_evl_monitor, by user root, by password <>


>>>  3.  Change the executor state to off: <<<

         MCC> disable Node4 0, by user root, by password <>


     4.  Save the old EVL image:

         # cp /usr/etc/evl /usr/etc/evl.original


     5.  Replace the old image with the new EVL image:

         # cp /usr/etc/evl.mcc /usr/etc/evl


     6.  Change the executor state to on via NCP command:

>>>      NCP> set exec state on <<<

         Once this new image is installed, it stays there until the
         user decides to switch back to the original EVL.

SOFTWARE NOTES FOR MANAGEMENT MODULES                   Page 4-17


     7.  Define the event filter, sink node and event sources using
         the PASS /CREATE command.  In order for the changes to be
         automatically effective at network startup time, they are
         made to the permanent database.  Refer to the DECmcc DECnet
         Phase IV Access Module Use document for detailed information.

     8.  Enable the DECmcc event sink monitor:

         MCC> enable Node4 0 local sink monitor, -
         by user root, by password <>

         DECmcc provides a shell script mcc_dna4_evl_setup.sh template
         to demonstrate normal startup of the event sink.  The file
         needs to be edited with node-specific information.  The
         script file resides in the /usr/mcc/mcc_system directory.

    After a days worth of hair pulling and stink my finger where it does'nt
    belong ;-)....
    
    I got the dna4 evl to work.  re .1 I had wrong version od DECnet (don't
    ask why or how...SORRY!!.) now that Ultrix is 4.2a and decnet is 4.2 -- all
    subsets installed.
    
    The only way I could get it to work was to define the logging consol
    and logg monitor to be state off, and the file state on
    
    # ncp def log cons know event state off
    # ncp def log mon state off
    # ncp def log file know eve state on
    
    # ncp set exec state on
    
    now run the modified dna4 evl set up, in this file I only issue the
    create outbound stream nad pass outbound streem commands, initial this
    was done just for the local node
    
    Atleast now I get the events from the local node, 
    ONLY PROBLEM IS I CAN,T ALLWAYS GET EVENTS FROM A REMOTE NODE
    CALLED SIRENE... CAN SOME ONE SEE ANY MISTAKES IN THE SCRIPT ATTACHED.
    
    ===ATTACHMENT===
    
#!/bin/sh 
#	The first line of the file must indicate which shell is used to execute
# the remaining commands.  In this case, use /bin/csh rather than /bin/sh.
#
#	Before enabling the sink to collect events from EVL, perform the 
#  following setups:
#
#  1.  The state of the local sink monitor must be off
#  2.  The local sink monitor must have a name of /usr/etc/mcc_dna4_evl_monitor
#  3.  The outbound stream sink node must be defined.
#  4.  The event filter must be properly defined on the node where the 
#	    sink is executed.
#
#	Note: This command procedure is intended to perform all of these
#	tasks as long as you have the privileges to execute them.
#
#	You may also modify the event filter or event sources to tailor the 
# events processed to the specific needs of your network (Refer DECNET PHASE 
# IV ACCESS MODULE USE).
#
#	Edit the following commands by replacing <os_node> occurrances with
# the name of the local system (where DECmcc is located).  If you have
# superuser password, then after excuting this procedure you will have:
#	- a Local Sink Monitor setup to be /usr/etc/mcc_dna4_evl_monitor
#	- A process, mcc_dna4_evl_process listening to DECnet's EVL.
#	- All supported DECnet Phase IV Events will be passed to
#	  mcc_dna4_evl so that you can GETEVENT against them to
#	  collect the events.
#
#	You can modify this procedure to:
#	- filter unwanted events from being passed to MCC_DNA4_EVL
#	  to reduce the amount of work the Local Sink process does.
#	  Change the Create Remote Sink or Pass directives to do this.
#	- Non-local events can also be sent to this system by setting up
#	  Remote Sinks on other systems that have an Outbound Stream of
#	  <os_node>.  This can be done in this procedure, or on the remote
#	  systems directly.
#
#PURGE MCC_DNA4_EVL.LOG/keep=10
#
#	The following line invokes the MCC FCL, using the following lines
# as command input, until the string "EOF" is reached.  If output is ignored, 
# sent to /dev/null.  You may want to leave off everything after the EOF, so 
# that the user can see the output.
#
# manage <<-EOF > /dev/null	
#  
manage <<-EOF 
!
!	the state of local sink must be off before clearing up the sink 
!
!DISABLE node4 <local node> local sink MONITOR, by user root, by password manageip
! 
!	before create the local sink, clear it from data base first
!
!DELETE node4 <local node> local sink MONITOR, by user root, by password manageip
!
!CREATE node4 <local node> local sink MONITOR, by user root, by password manageip
!
!	name of the DECmcc sink monitor must be /usr/etc/mcc_dna4_evl_monitor.
!
!SET node4 <local node> local sink MONITOR name /usr/etc/mcc_dna4_evl_monitor, -
!	by user root, by password manageip
!
!	Make sure no old Remote Sinks are lying around.
!
DELETE node4 DECUS1 outbound stream DECUS1 remote sink MONITOR, -
	by user root, by password manageip
DELETE node4 SIRENE outbound stream DECUS1 remote sink MONITOR, -
	by user system, by password thisisthepasswordforaugust
!
!	Set up the event filter:  os_node => should be the local node.
!				  os_node => is where events will be received.
!
!	Set up to sink local events of class 0 to the Local Sink Monitor.
!
CREATE node4 DECUS1 outbound stream DECUS1 remote sink MONITOR class 0,-
	event type = {0,6}, by user root, by password manageip
CREATE node4 SIRENE outbound stream DECUS1 remote sink MONITOR class 0,-
	event type = {0,6}, by user system, by password thisisthepasswordforaugust 
!
!	Set up to sink local events of class 2 to the Local Sink Monitor.
!
PASS node4 DECUS1 outbound stream DECUS1 remote sink MONITOR class = 2, -
	event type = {0,1}, by user root, by password manageip
PASS node4 SIRENE outbound stream DECUS1 remote sink MONITOR class = 2, -
	event type = {0,1}, -
	by user system, -
	by password thisisthepasswordforaugust 
!                   
!	Set up to sink local events of class 3 to the Local Sink Monitor.
!
PASS node4 DECUS1 outbound stream DECUS1 remote sink MONITOR class = 3, -
	event type = {2}, by user root, by password manageip
PASS node4 SIRENE outbound stream DECUS1 remote sink MONITOR class = 3, -
	event type = {2}, -
	by user system, -
	by password thisisthepasswordforaugust 
!
!	Set up to sink local events of class 4 to the Local Sink Monitor.
!
PASS node4 DECUS1 outbound stream DECUS1 remote sink MONITOR class = 4,-
   	event type = {3,4,6,7,8,9,10,11,12,13,14,15,18}, -
	by user root, -
	by password manageip
PASS node4 SIRENE outbound stream DECUS1 remote sink MONITOR class = 4,-
   	event type = {3,4,6,7,8,9,10,11,12,13,14,15,18}, -
	by user system, -
	by password thisisthepasswordforaugust 
!
!	Set up to sink local events from class 5 to the Local Sink Monitor.
!
PASS node4 DECUS1 outbound stream DECUS1 remote sink MONITOR class = 5,-
   event type = {0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21}, -
   by user root, by password manageip
PASS node4 SIRENE outbound stream DECUS1 remote sink MONITOR class = 5,-
   event type = {0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21}, -
   by user system, by password thisisthepasswordforaugust 
!
!	Set up to sink local events of from class 6 to the Local Sink Monitor.
!
PASS node4 DECUS1 outbound stream DECUS1 remote sink MONITOR class = 6, -
	event type = {0,1,2,3,4,5}, by user root, by password manageip
PASS node4 SIRENE outbound stream DECUS1 remote sink MONITOR class = 6, -
	event type = {0,1,2,3,4,5}, -
	by user system, -
	by password thisisthepasswordforaugust 
!
!	Set up to sink local events of from class 7 to the Local Sink Monitor.
!
PASS node4 DECUS1 outbound stream DECUS1 remote sink MONITOR class = 7, -
	event type = {0,1,2,3,4,5,6,7,8,9,10,11}, -
	by user root, by password manageip
PASS node4 SIRENE outbound stream DECUS1 remote sink MONITOR class = 7, -
	event type = {0,1,2,3,4,5,6,7,8,9,10,11}, -
	by user system, by password thisisthepasswordforaugust 
!
!	Start the sink -- create a detached MCC_DNA4_EVL process to receive 
!	Decnet IV events and set its state on to make them available to DECmcc.
!
ENABLE node4 0 local sink monitor, by user root, by password manageip
ENABLE node4 SIRENE local sink monitor, -
	by user system, -
	by password thisisthepasswordforaugust 
exit
EOF
    

    Ok, so I said I sort a got it going... but it does'nt seem to be
    stable.
    
    The problem now seems to be that any commands to the remote node SIRENE
    hange untill I hity a ^C.  The same command work fine when you issue
    them to the local node.  NCP loops from the mcc system to SIRENE work
    ok.
    
    I can get all events from the local mcc system, at this time the
    /tmp/evl_monitor_log and evl_proc_log are updated correctly.  but
    messages from the node SIRENE are not seen comming into the mcc system,
    no update in the log files etc...
    
    I want to restart the node4 am is there a clean way to kill all node4
    processes ?

**IHAVE UPDATED THIS NOTE**
    Still no resolve to this problem -- has anyone got it to work
    consistently ?

    I log in as root, the account sources the login file for mcc.

    I set exec state off
    mcc is all shutdown
    I remove the .log etc files in /tmp ( I want to create new ones so that
    I can see what is going on)

    Set the exec state on, the evl process comes up and the appropriate log
    files get created in /tmp.

    In two windows I tail the /tmp/evl_prc_log and /tmp/evl_monitor_log

    Issue the evl set up script indicated in the previous note.

    I issue a ncp set cir sva-0 state off, I see two events come in in
    evl_monitor_log, nothing in evl_prc_log -- ok thats probably because
    circuit is down.  Set cir state up, I see two events come in in
    evl_monitor_log, I see two events processed in the evl_prc_log, first
    translates to event 415 (4.10 circ up), and next one to 415 (4.15 adj
    up)...  a message in the log file states failed to send event 510 to
    MCC event manager, NOEVENTREQ (makes sense mcc IMPM not running yet)
    ... so looks like things are working

    Now start mcc_iconic_map, set the cir state off, and on -- I see events
    coming into the evl_monitor_log, and in
    evl_prc_log with the message Sent event ### to MCC event manager, but
    no notification (notify request for NODE4 * ANY EVENT enabled)


    note to engineering, a time stamping in the log file would be useful...
     
    So come on, what am I doing wrong !!

    Amrit

    

    managed to get my hands on a Ultrix system running decnet, event
    logging from that to mcc works fine, and the local event also works
    fine -- after a reboot.

    the events from the decnet node SIRENE LAVc node exhibit a bizarre
    behavior, I suspect that this is a problem on the decnet node... NOT
    MCC (Plenty of humble pie being eat as I write ;-) )

    set up event logging as described before.  bounce the circuit a few
    times, no events in mcc.  Wait for a while say ~10 mins, and issue a 
    NCP> CLEAR LOG MON SINK NODE DECUS1 ALL EVENT on the end decnet node
    and all of a sudden the previous events come out in a burst on the mcc
    screen, all with a very close time stamp.  Almost as if the VMS decnet
    system is holding onto the events for some reason.

    I also am having a problem with logging events.  I have an occurs rule
    monitoring Counters Zeroed on the local node that DECmcc is running.  I
    followed the steps in the release notes and also .2.  In /tmp I see two
    *pid* files and one pipe files.  Whenever zero counters on the local
    node (which I have to enter access info), nothing happens.  Does anyone
    have any ideas that would help??  I've struggled with this for the last
    couple of days.  I'm running V1.2 on DECstation 5200.
    
    Thanks,
    
    /Dave
    

    you are looking for
    
    	getevent node4 name remote node name counters zeroed
    
    and not
    	
    	getevent node4 name counters zeroed
    
    DECnet returns the counters zerored event against the remote node
    child entity, even when you are on the "remote node".