[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference forty2::mailbus

Title:MAILBUS - Message Router and its Gateways
Notice:Kit Copy Utility - 100.1, Problems - 5.*, Kit Support - 103.1
Moderator:FORTY2::YUILLE
Created:Thu Jun 11 1992
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3209
Total number of notes:7125

3178.0. "%MROUTER-W-INVSYSLOG, SYS$NET error" by ZPOVC::NWE () Wed Mar 12 1997 13:29

Hi

Customer is having problem with sending/receiving ALL-IN-1 mail from Singapore
to Hong Kong. Sending of mail from Singapore to other destinations are ok.
The configuration is:

OpenVMS 6.1 VAXCluster
ALL-IN-1 3.1 
Message Router V3.3-313
DECNET OSI
Multinet 3.5


When issuing $dir HKGA::  and also open/read/write a mr$node
are fine.

Singapore System

%MROUTER-E-NNODGONE, Remote node HKGA unreachable
-SYSTEM-F-LINKEXIT, network partner exited
%MROUTER-I-FAILOG_TALK_N, 19970312095527 The talker is not connected
%MR-E-NNODEGONE,  Remote node HKGA unreachable
-SYSTEM-F-LINKEXIT, network partner exited
%MROUTER-I-FAILOG_LSTN_N, 19970312095544 The listener is not connected
%MROUTER-E-DECNET, DECnet returned error
-SYSTEM-E-UNREACHABLE, remote node is not currently reachable
%MROUTER-E-NOLINK, Could not link to caller
%MROUTER-I-FAILOG_TALK_N, 19970312095604 The talker is not connected

Hong Kong System

%MROUTER-E-NOLINK, Could not link to caller
%MROUTER-I-FAILOG_LSTN_N, 19970312095736 The listener is not connected
%MROUTER-W-INVSYSLOG, SYS$NET translated to SIN.NLLFCC.NEDLLOYD.NL is
an invalid Decnet Phase IV node name
%MROUTER-E-NOLINK, Could not link to caller

%MROUTER-W-INVSYSLOG, SYS$NET translated to SIN.NLLFCC.NEDLLOYD.NL is
an invalid Decnet Phase IV node name
%MROUTER-E-NOLINK, Could not link to caller
%MROUTER-I-FAILOG_TALK_N, 19970312095813 The talker is not connected
%MROUTER-E-NNODGONE,  Remote node SIN unreachable
-SYSTEM-F-UNREACHABLE, remote node is not currently reachable



Any suggestions or pointers are welcome.

Thanks and regards,

Nwe
T.RTitleUserPersonal
Name
DateLines
3178.1IP$16.65.80.19::S_WATTUMScott Wattum - FTAM/VT/OSAK EngineeringWed Mar 12 1997 16:2114
At a guess you're running DECnet over IP, possibly using LOCAL naming and BIND?

On the Hong Kong side, You need to define SIN in the local bind database as 
SIN.NLLFCC.NEDLLOYD.NL so that when DECnet asks Multinet for the address to name
translation, DECnet will get SIN back.  In UCX you'd do this with the UCX
command SET HOST <hostname> /ADDRESS=ip_address  I'm not sure how you do it in
Multinet.

You might also have to use SYS$SYSTEM:DECNET_REGISTER to create an entry for the
system SIN.NLLFCC.NEDLLOYD.NL with a synonym of SIN that has an empty tower set,
but I'm not certain.  Start with the host database, and then if that doesn't do
it, try the DECNET_REGISTER.

--Scott
3178.2IP$16.65.80.19::S_WATTUMScott Wattum - FTAM/VT/OSAK EngineeringWed Mar 12 1997 17:265
Oh, one other thing.  Once you get the alias created for the hostname in
Multinet, you'll want to remember to flush the CDI cache, so that DECnet will
pick up the new name from Multinet, rather than using the previously cached name.

ncl> flush session control naming cache entry "*"
3178.3RE: %MROUTER-W-INVSYSLOG, SYS$NET errorZPOVC::NWEThu Mar 13 1997 12:189
    Hi
    
    Thanks for all the reply. The problem is now resolved. According to
    customer, someone did changes in DNS entries and after it revert back
    to original, everythings is fine.
    
    regards,
    
    Nwe