If I remember right Multinet caches the IP address and does not flush it. Let's not
forget that Process Software does not support anything but a reboot!
It is not that big a hit. In the future the hit will be even less when I make some
changes to the startups and the hardware.
So far I have not heard of any complaints when it reboots. I suspect that no one even
notices... It really does amount to noise.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Rok
Vidmar
Sent: Wednesday, December 21, 2011 11:15 PM
To: hecnet at update.uu.se
Subject: Re: [HECnet] Multinet Tunnel Links defined
I have written a DCL procedure that does IP address lookups at
predetermined (configurable) intervals. If it finds a mismatched IP
address it reconfigures the the TCP-0-n (where "n" is the area - in my
case) IP address and schedules a reboot.
To avoid reboot, did you try
$ ncp set circ TCP-0-n sta off
$ multinet set/decnet/remote=new_IP_addr/device=TCPAn:/connect
$ ncp set circuit TCP-0-n state on cost 9 hello timer 300
These commands execute without error. I have no means yet to test
if remote address gets really changed.
--
Regards, Rok