bArtoque wrote:
>
> Hi there,
>
> I was playing around with a machine of ours to find out what the exact
> procedure for a migration to another network segment should be. Changing to
> a new ip number on the machine itself 'only' required a reboot (a network
> restart should have been enough, but since the machine will have to be
> physically moved anyway, a reboot would make everything alright (new
> ip-number/gateway/subnetmask)). But what does have to be done on HP3000
> (MPE5.5, PP7) machines which have to connect to the changed machine through
> the sysname entry as stated within 'nmmgr' via 'remote:<sysname>'?
> I found out that just changing the ip-number of the changed machine in
> 'nmmgr' on the other machines isn't enough, you have to delete the changed
> machine's entry out of their cache from within 'nettool' since the cache
> still refers to the previous ip-number (or is there a way to update the
> config again with a certain force, so that the cache is refreshed?). But
> deleting the cache entry only works if you open a new session to the
> machine, NOT in the existing sessions.
>
> The thing I was wondering about is, if the same goes out for already running
> jobs? Does a running job (even after deleting the changed machine's entry
> from its cache) look for the old or for the new ip-number? I'm not sure
> myself, just looking at the behaviour of sessions, where a new session needs
> to be initiated until changes take effect.
>
> The problem for me is that I want to know in advance whether I have to
> restart the network/the jobs  on the other machines, at all, to make them
> able to connect to the changed machine through VS/VT via the
> 'remote:<sysname>' command.
>
> Thanx in advance,
>
> bArtoque

bArtoque,


Based on experience with changes in the networks at our compagny, a
network restart may be needed.

We had some CISCO routers changed for new models and we had to restart
the network software on the HPe3000's to reconnect to their gateways.


Regards,


Jan Gerrit Kootstra