IMHO, a better alternative is to use a second NIC. (This connection must be
routed as the HP3000 can't be 'multi homed') Most HP3000 systems only
require 10BaseT anyway. 10baseT cards are half high and very inexpensive. If
you have a system that is large enough to require 100BaseT, a second
100BaseT as a backup is almost a requirement. This way a simple DNS change
can reroute connections around a hung NI.  Rather than attempting to reset
the NI, or reboot the system.

Also, in the above situation, you can configure and test the client parts of
the new addressing scheme in advance.  Frequently, I find systems that have
two NICs anyway, one for DTC use, and one configured for TCP/IP use. In this
case the DTC NIC can be configured tested in advance for the new address.
This approach does not solve any server side address configurations issues,
but these are usually minor compared to client side routing and
connectivity.

Cordially,

Mike Hornsby
Co-founder/Chief Technical Officer
Beechglen Development Inc. (beechglen.com)
513-922-0509
[log in to unmask]


----- Original Message -----
From: "rosenblatt, joseph" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Wednesday, October 17, 2001 8:33 AM
Subject: Re: [HP3000-L] Changing IP Addresses


> Russ Smith asks:
> - do your PCs find the 3000 using a hosts file, a resolved name or a fixed
> IP in their logon scripts, and do you have a migration plan to check and
> update them.
> - do you have any jobs or scripts running which FTP to your 3000 with a
> hardcoded IP in them.
> - do you have a telnet listener job running to catch routed messages
coming
> through a pinhole in your router that would have to be changed, and if so
> - do you have multiple 3000s talking to each other through DSLINE, and how
> are they addressing each other.
> - are you using your 3000 as a web server and if so how does your front
end
> find the 3000.
>
> Having run this system prior to the original poster I think I can answer
> these questions.
> They use DHCP.
> No FTP
> No Listeners
> Only one HP3000
> The 3000 is not the web server.
>
> However they are running an Oracle Database. I recall early in my stay at
> I2S that I "fixed" something in the network configuration using NMMGR and
> the Oracle app lost communication and came down. They do not have Oracle
> support so there is no help from that quarter.
> I hope this contributes something to the discussion.
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *