Jan is right, you shouldn't have any problems.
But, if you are using DNS (domain name services, ties the system name to the
IP address) running on NT or Unix, you may want to make a change to the
table/settings to reflect the change.
For your VT-MGR connections, if you are not using DNS, you may need to
change the host file on each/all PCs running Windows to reflect the change
to the new IP address.
If you are moving to another physical location, and you will be placed
behind a new router, you will need to check the routers routing table to
insure the new address is there.
Remember to check the number of "hops" from your system to the remote
routers too.
Of course, any telnet or fpt processes running form other systems to you e3k
will need to be changed as well.
JCL on your e3k should be okay in most cases (uses system config's IP
address).
Also, check your hosts.net.sys file on your remote e3k systems (works just
like a host file on the pc).
If you are doing any network printing to your e3k (NT, Unix, Novell, et al,
a print queue defined on a remote server directing printing to a printer
defined on the e3k), you will have to check the print queer's setup on those
remote system
Just my humble opinion,
Let me know if I was way off base, or close.
From the US, have a great labour day weekend...
mc
Mike Church
Technical Support Manager
Information Services
Our Lady of Bellefonte Hospital
Saint Christopher Drive
Ashland, Kentucky 41101
-----------------------------------
Phone : (606)833-3727
Pager : (606)327-0965
Fax : (606)833-3342
-----------------------------------
Alternate e-mail : [log in to unmask]
-----------------------------------
MY URL: http://members.tripod.com/mike_church/
OLBH: http://www.olbh.com
-----------------------------------
Daily Quote: Few are those who see with their own eyes and feel with their
own hearts. - Albert Einstein
-----Original Message-----
From: bArtoque [mailto:[log in to unmask]]
Sent: Saturday, September 02, 2000 9:45 AM
To: [log in to unmask]
Subject: [HP3000-L] changing ip-address problem...
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
|
