Conference azur::mcc

3142.0. "Notification, PhaseV and multiple namespaces" by RDGENG::PRATT () Fri Jun 05 1992 14:09

Running VMS T1.2.7 using DNS

There appears to be a problem with using notification and PhaseV nodes in 
multiple namespaces.

My MCC system uses a private namespace (MCCULT_NS:), yet all of my phaseV 
routers are in the DEC: namespace, with event streams sinking into MCC. I 
originally setup notification like this...

    6  Running  Notify Domain wan_segment Entity List = (node * routing circuit
                *), Events = (any event)

However this didn't get me any notifications, although events were being 
received. I eventually tracked this down to the fact that the events were 
coming from DEC:.reo.engr28, yet MCC was only interested in events coming from
nodes in the same namespace as itself. By renaming my DECnis to 
MCCULT_NS:.reo.engr28, notification now worked with the above setup, and the
icon changed colour.

However this is not practical from an EASYnet point of view, and we would like
to keep all the routers in the DEC namespace. So I then renamed my DECnis back
into the DEC: namespace, and set up notification thus...

    7  Running  Notify Domain wan_segment Entity List = (node DEC:.reo.engr28
                routing circuit *), Events = (any events)

This worked fine with the IMPM, and I received notification, but the icon would
not change colour - this is because the icon is in the MCCULT_NS: namespace. By
using targeting I was able to redirect my DEC:.reo.engr28 to make my .reo.engr28
icon change colour.

Incidently when running this notification from the command line interface I get 
the following error when an event from DEC:.reo.engr28 is received...

%MCC-E-NOTIFOUTPERR, notify request 7 encountered an error in output parameter
%MCC-E-ILVNOTINCONS,  caller not positioned within ASN.1 constructor

Although this second solution worked with the IMPM I really want to be able to 
wildcard, and not setup individual notifications for every global node entity,
so I tried doing this...

    8  Running  Notify Domain wan_segment Entity List = (node DEC:* routing
                circuit *), Events = (any events)

and this is where the problem lies. If I use a wildcard for the node name, but
specify a different namespace then the namespace nickname is ignored, and the
wildcard looks for all events in the MCC namespace (ie MCCULT_NS:).

Questions - 

a) Is this a bug? or am I going to have to set up individual notifications for 
each node that I am monitoring?   

b) Is there anyway that I can get the icon to change colour without have to 
retarget each notification?

Regards

Ian Pratt 

    
    What you are seeing is the currently expected behavior. MCC is not
    setup to be able to handle multiple namespaces. The FM does allow
    you to specify a specific instance in another namespace and force
    things to work, but the wildcard gets based into the MCC_DNS routines
    which always go to the primary dns namespace (therefore the results
    that you are seeing).
    
    The one item i can not explain yet is why you are getting the ilv
    positioning error, unless you happened to try to assign a target
    for an entity that had three levels in the entity spec (there
    was a bug in the notificastion support of such an entity specifier
    which has now been corrected).
                                                        
    
    jill