Conference azur::mcc

6021.0. "DEMSA = events ok, DECNIS = events ko" by BLG03::ROSSI () Thu Jun 16 1994 05:30

Hi,

	An important customer (Barilla Foods, Parma, Italy) has 
about 30 VAX in a local LAN (2 x 10000, 12 x 4100, several 3100). 
The network is monitored using DECMCC 1.3. 

No problem in monitoring events, using the Notification Service 
feature. When a node goes down, the iconic map shows the node in
red colour and a red line is added in the Notification Window.

In the past, connecting a remote LAN via 2 x DECROUTER 2000 (DEMSA) 
and using the REMOTE SINK feature of DECNET LOGGING MONITOR we had no 
problem to get the events from the remote LAN.

Now we have intorduced 2 DECNIS to interconnect the remote
LAN instead of DEMSA. The customer need to receive a notification of 
events like "ADJACENCY DOWN" or "ADJACENCY UP" when in the remote LAN 
a node goes down or up. 

					local LAN
==========+===================+=================================
          |                   |
    +-----+-----+       +-----+-----+
    |  DECMCC   |       |  DECNIS   |
    +-----------+       +-------+---+
                                |
                                \
                                 \
                               ---  
                               \
                                \
 +---------------------+         |
 | if this decnet IV   | +-------+---+
 | end node goes down  | |   DECNIS  |
 | an event must appear| +----+------+
 | in notific.window   |      |
 +---------------------+      |
           |                  |               remote LAN
===========+==================+=====================================

The goal is to have the same behaviour for nodes in the local LAN 
and nodes in the remote LAN seen via 2 x DECNIS as seen in the past
with 2 x DEMSA. Is this possible ?

Could someone tell me about all steps in detail to reach such goal,
defining outbound streams (how and where), how to launch DNA5_EVL 
process (is there a .com like MCC_DNA4_EVL?), how to define the 
notification request about events coming from the remote LAN and 
some other things to do ?

Reading preceeding notes I had to test a lot of indications very 
dispersed in a lot of documents. No good results obtained. The 
customer is a bit disappointed about the DECMCC documentation that 
seems not useful in this case.

Could someone help me ?

Thank in advance.


Bye



Giuseppe Rossi

Hi,

I don't know which version of MCC you use (see 4018.4), on which node etc..
but below are the main steps to reach your goal (assuming you have rights
to perform these operations)

1.First allow your node 4 (A) to sink the requested events to a phase V node (B)
(I give here some examples of events, I'm not sure these are those you want)

-create node4 A  outbound stream  B remote sink monitor class 0,-
event type ={0,1,2,3,4,5,6,7,8,9}
enable node4 A local sink monitor

2.Start the dna5 sink on MCC station to receive phase V events
-enable mcc 0 dna5_am sink

3.Then allow the node B to redispatch these events to the MCC station:
phase 4 events are relayed through relay entity


-create node B event dispatcher outbound stream MCC_STREAM
-set node B event dispatcher outbound stream MCC_STREAM -
     sink node = MCC_NODE, -
     sink end user name = MCC_EVL_SINK

-pass node B event dispatcher outbound stream  MCC_STREAM -
     global filter ((Node,Event dispatcher, relay, logging),all)
-enable node B event dispatcher outbound stream MCC_STREAM




4. Start your notification services
here is an example with getevent

getevent <node4 A entity> <type of event> 



Usually, MCC_NODE = B, but B can also a DECNIS 


NB : Another way to specify the sink location is to set the sink address:
(work more surely than setting sink node/sink end user name )
set node B event dispatcher outbound stream  MCC_STREAM sink address = -
               {([DNA_CMIP-MICE,None],-
                 [DNA_SessionControlV3, name= MCC_EVL_SINK],-
                 [DNA_NSP,None],-
                 [DNA_OSInetwork,<MCC_NODE address> ])},-


Hope it will help. Vincent

Hi,
	thank You Vincent for your answer.

The version of MCC is 1.3. The rights are OK to do what You tell me 
about. The MCC node (VAXSTATION) is VMS 5.5-2 Decnet IV extensions.

I'll test at the customer site all your helps.

The biggest problem for me is how to specify a Notification Request
to get the event and put a line in the Notificatin Window. 

Could someone tell me, please, the sintax that, when a remote DECNIS 
discover on its LAN an Adjacency Down from an end node IV, puts a 
line into the Notification Window telling that there is an adjacency
down.

Thanks in Advance.


Best Regards,



Giuseppe Davide