2 Jun
2007
2 Jun
'07
12:22 p.m.
Hi
The abortive attempt to cluster the two Vaxes and copy data has left me
much further back than when I started.
The network and terminal server connections are gone because I can't
start TCPWARE up.
It complains about a license and and something called NETCU (What the
hell is that?) and aborts the loading of TCPWARE.
Lesson learned,= the boot from a cluster server idea is flawed and can
damage an existing setup.
Its probably one of those things everybody has heard about but never
actually done.
Back up did somebody say Back up.?
The whole reason I attempted doing it this way is because despite the
fact that both systems have TK 70 tape drives when attempting to do a
backup on the -200 it keeps telling me the tape is write protected which
it isn't.
I'll try to sort that one out to-morrow.
Rod
2 Jun
2 Jun
3:08 p.m.
Rod Smallwood wrote:
Back up did somebody say Back up.?
The whole reason I attempted doing it this way is because despite the
fact that both systems have TK 70 tape drives when attempting to do a
backup on the -200 it keeps telling me the tape is write protected which
it isn't.
Make sure it isn't a TK50 you put in the TK70, or formatted as TK50.
Probably switch the drives between the systems ?
3:21 p.m.
On Saturday 02 June 2007 15:22, Rod Smallwood wrote:
Hi
The abortive attempt to cluster the two Vaxes and copy data has left
me much further back than when I started.
The network and terminal server connections are gone because I can't
start TCPWARE up.
It complains about a license and and something called NETCU (What the
hell is that?) and aborts the loading of TCPWARE.
I've never used TCPWARE. On the other hand, it appears that NETCU is
TCPware's "Network Control Utility":
http://www2.process.com/tcpip/tcpware57docs/NETCU/Front.htm
It's possible that if you clustered your VAX, you upset TCPware's
licensing, and made it think that you had more than one system (or a
different one) trying to run TCPware.
Lesson learned,= the boot from a cluster server idea
is flawed and can
damage an existing setup.
Its probably one of those things everybody has heard about but never
actually done.
I've done it plenty of times. I know other people on the list have done
it plenty of times, and people that I work with have done it in the
past.
If you had actually had DECnet installed, it probably would have worked
ok. LAVC's require DECnet to be installed, which the documentation
should have stated.
Why don't you get a copy of DECnet, install it, activate it using a
hobbyist license key (you're an Encompass aka DECUS member, right?
Associate memberships are free.), and try again.
Perhaps instead of insulting people on this list, you should concentrate
on figuring out what went wrong.
Back up did somebody say Back up.?
The whole reason I attempted doing it this way is because despite the
fact that both systems have TK 70 tape drives when attempting to do a
backup on the -200 it keeps telling me the tape is write protected
which it isn't.
I'll try to sort that one out to-morrow.
Do you know that the tape drive actually works? What are the LED
indicators when you stick a tape in?
Also, I believe that if you are putting media in that has been written to
as a TK50, into a TK70 drive, the media will be marked "write
protected". You'll need to degauss the media (with a *good* degausser,
not a video/audio tape one) to get it to be writable in a TK70 drive.
Pat
--
Purdue University ITAP/RCAC --- http://www.rcac.purdue.edu/
The Computer Refuge --- http://computer-refuge.org
10:29 p.m.
On Sat, 2007-06-02 at 18:21 -0400, Patrick Finnegan wrote:
For the record, I've done it plenty of times - and I've run into this
problem (In this case, it was the VAX-VMS license, which is generated
with the NO_SHARE option, and thus needs to be tied to a single node
when you're using a cluster.
On Saturday 02 June 2007 15:22, Rod Smallwood wrote:
Hmm... you may now that you are in a VAXcluster with a shared license
file have to explicitly specify which of the nodes on the cluster gets
the license (if the license is specified as being limited to a single
machine.)
(Warning: This is from somewhat hazy memory, but I don't think any of
this could harm the system.)
do this by
$ LICENSE MODIFY licensename/INCLUDE=hostname
$ LICENSE LOAD licensename
The hostname is the one gotten using
$ SHOW SYSTEM
I think this may very well solve your problem.
Hi
The abortive attempt to cluster the two Vaxes and copy data has left
me much further back than when I started.
The network and terminal server connections are gone because I can't
start TCPWARE up.
It complains about a license and and something called NETCU (What the
hell is that?) and aborts the loading of TCPWARE.
I've never used TCPWARE. On the other hand, it appears that NETCU is
TCPware's "Network Control Utility":
http://www2.process.com/tcpip/tcpware57docs/NETCU/Front.htm
It's possible that if you clustered your VAX, you upset TCPware's
licensing, and made it think that you had more than one system (or a
different one) trying to run TCPware. Lesson
learned,= the boot from a cluster server idea is flawed and can
damage an existing setup.
Its probably one of those things everybody has heard about but never
actually done.
I've done it plenty of times. I know other people on the list have done
it plenty of times, and people that I work with have done it in the
past. If you had actually had DECnet installed, it probably
would have worked
ok. LAVC's require DECnet to be installed, which the documentation
should have stated.
As we discussed on IRC, I'm not so sure about that.
Why don't you get a copy of DECnet, install it,
activate it using a
hobbyist license key (you're an Encompass aka DECUS member, right?
Associate memberships are free.), and try again.
This is a good idea in any case.
Happy hacking,
-Tore :)
4:44 p.m.
On Jun 2, 2007, at 3:22 PM, Rod Smallwood wrote:
The abortive attempt to cluster the two Vaxes and copy
data has
left me
much further back than when I started.
The network and terminal server connections are gone because I can't
start TCPWARE up.
It complains about a license and and something called NETCU (What the
hell is that?) and aborts the loading of TCPWARE.
Lesson learned,= the boot from a cluster server idea is flawed and can
damage an existing setup.
Its probably one of those things everybody has heard about but never
actually done.
You can't be serious...? Cluster-booting of VAXen is something
that has been happening in thousands of multiple-VAX installations
for two decades. I did it myself when I was still a teenager. It is
nothing unusual.
I am sorry to hear that the attempt hosed your machine.
-Dave
--
Dave McGuire
Port Charlotte, FL
6412
days inactive
6413
days old
4 comments
5 participants
participants (5)
-
emu＠e-bbes.com -
mcguire＠neurotica.com -
pat＠computer-refuge.org -
RodSmallwood＠mail.ediconsulting.co.uk -
toresbe＠ifi.uio.no