Conference azur::mcc

5496.0. "Notification and Backtranslation ..." by WIZZER::MACLEAN (A Pure Dear in a Wicked World) Tue Aug 17 1993 14:06

Hi !, 
    
I am seeing behaviour that I cannot explain from MCC interacting with DNS
	       { MCC 1.3  DNS v1.1a   Vms 5.5-2 }
Node4 Notifications have stopped working with Node Numbers,However if you
specify a  Nodename instead of the Number we receive the notifications as 
usual. In either case we can see the  decnet event being sunk to the node 
and noted by Opcom .In the failing Scenario,neither the Mcc_notification.
log nor the Iconic Map notification pick this up...

We have tried manually deleting an adding a notification request , adding 
a completely new notification request, Disabling and Enabling the dna4_am 
sink ,stop/start mcc etc with no avail....

I can track back the Nodesynonym link to the object and that looks OK  as
expected. The Backtranslation link , which is where I suspected the error
may  be  , also showed  a valid  dsn$linktarget  and  dns$linktimeout  by 
checking DNS>sho link .DNA_BackTranslation.%x49.%X0029.%XAA00040027A6 att
ri dns$linktimeout /dns$linktarget etc   for example

I have also tried deleting the link and recreating the link ,and still no
joy .....surprisingly there is one x25Router which is registered as a Node4
and apparently  does not show the problem but it is in a domain with node4's
exhibiting the problem.....its entry looks exactly like the others ?!?!

Any suggestions please ?.....

Sandie/ UK CSC Comm.s