HowTo Change Pathworks Workstation Addresses?
Robert A. Matern
How do we set/change the network addresses for the new workstations?
The contractor who is supposed to do this is being uncooperative...
Doug Oleinik
You did not specify what kind of workstations you are trying to
set up (or what protocol you are using for Pathworks), however,
if you are setting up VMS workstations with DECNET, then you
would use the NCP command to define the NODE information.
Doug Oleinik
--
\\ // Wm. K. Walthers, Inc. Serving Hobbyists since 1932
\\ /\ //
\/ \/ a l t h e r s Visit The Model Railroad Mall
= o o o ==================== http://www.walthers.com
Hans Bachner
Robert A. Matern <rama...@SEND.MEuninetsNO.SPAM.net> wrote:
> We're swapping out workstations on a VAX 6430's Pathworks network.
>
> How do we set/change the network addresses for the new workstations?
What exactly are you trying to do? Are these VMS workstations running in a
cluster with the 6430, or are these Windows workstations accessing the
6430's Pathworks shares?
In the first case, SYS$MANAGER:CLUSTER_CONFIG.COM has an option to modify a
satellite's hardware address, so you can boot the new workstation into the
root of the replaced one. If the hardware (especially the amount of memory)
is different, don't forget to run AUTOGEN after the hardware swap.
In the second case, do you have client based or server based Pathworks
licensing?
If you can come up with some more details, you'll probably get more /
better suggestions how to proceed.
--
------------ speaking only for myself ------------
Hans Bachner E-Mail: Hans.B...@hp.com
HP Services / Consulting & Integration
Hewlett-Packard Ges.m.b.H. Linz / Austria
Robert A. Matern
The stations are VMS workstations (a 3100 and a 4000) in a cluster with the
6430.
I've got the MAC addresses for both of them. What other info do I need for
cluster_config.com ? Do I need to set anything on the workstations? These
stations appear to have a local disk - would AUTOGEN be necessary in this
case? Since I don't have access to the original stations, I don't know if
the hardware is different - so it's probably best to assume that it is.
These stations were in use on an older VAX 6210, so they're ready for use
once I can add them into the new system.
In trying to get information off the sister system (another 6430), it was
discovered that the accounting data hadn't been cleaned out in 2 years - the
system froze when the disk filled. So I had to fix it before I could look
at it. That's the problem I'm having - the admins who are supposed to be
doing this work are in a contract/money fight with management. They use the
traditional job security method - keep it all in your head. There is no
system notebook, no install notes, no procedures, no nothing. Grrr! I am
having to figure out what the configuration is on one system, and then try
to clone it onto the sister system (with the usual differences). Not an
easy task at all.
We'll be continuing the work tomorrow morning, so any suggestions are most
welcome!
Bob
"Hans Bachner" <Ha...@Bachner.priv.at> wrote in message
news:Xns947FCEC...@10.0.0.3...
Robert A. Matern
sysgen, modparams.dat,etc.) and it boots up fine. Now, we're working to get
the licenses changed over so that DECNet, etc., will start up so we can add
in the other nodes (changes in NCP & cluster_config.com). At least we made
some good progress today.
I'll post a detailed summary once we get this completed.
Bob
p.s. - I would still welcome any suggestions, gotchas, etc.! :) thanks
Robert A. Matern
We need to get the correct licenses onto this VMS disk. Do I have to remove
the ones currently in the license database (the disk was copied from a
working system), or can I modify them to match the info on the license
certificates for this system? It would be nice to know how to proceed
without just trying different methods...
We're trying to get at the license database on the old disk for this system
(older version of VMS) since it already has the correct licenses (though the
limits would have to be modified since the old system had fewer CPUs), but
although it mounts we are having trouble reading the disk. Any special
gotchas when mounting a disk that is a different system disk?
"Robert A. Matern" <rama...@SEND.MEuninetsNO.SPAM.net> wrote in message
news:c0br19$kud$1...@ngspool-d02.news.aol.com...