[Info-vax] Migrated VMS 5.X to simh - TCPWare error

[Peter 'EPLAN' LANGSTOEGER]

In article <7e63e91c-4bfd-4e1d-bd8a-f68aa421022b at e8g2000vbz.googlegroups.com>, "gregor.oelze" <gregor.oelze at gmail.com> writes:
>On 18 Feb., 18:26, pe... at langstoeger.at (Peter 'EPLAN' LANGSTOEGER) wrote:
>> In article <c7e127e1-5c77-463a-837c-6a7a4989a... at n18g2000vbq.googlegroups.com>, Dave <Baxt... at tessco.com> writes:
>>
>> >I guess my next move would be to disable startup of DECNet and TCPWARE
>> >in =A0SYSTARTUP_V5.com (??), reboot, and then run NETCONFIG.com
>> >(including the running of the commands) =A0 =A0This should populate the
>> >circuits and lines in ncp, with what OpenVMS actually sees.
>>
>> And my "next move" (after SHOW DEVICE and fixing SIMH and also the
>> duplicate IP address) would be (if still neccessary) to @TCPWARE:CNFNET
>> to fix TCPware and not touch DECnet at all (as the OP doesn't require it)
>
>I just re-ran the cnfnet script and the following message appeared:

You re-ran the cnfnet script before problems by SIMH has been ruled out?

>Provide your distributor or Process Software Corporation with the
>following information to obtain a software password for this system:
>
>    o  Hardware ID: "2B-AA-BB-CC".
>
>    o  System ID:   "01-0A".
>
>    o  The product name and version number for the product(s)
>       you are installing on this system.
>
>Refer to your product documentation for more information on obtaining
>a software password.
>
>Enter new software password [NO CHANGE]:
>
>I just pushed "enter" to "not change" anything - could it be, that the
>whole TCPWare problem is based on a licence problem?

No (and yes)!

1st problem is, that we're still guessing (!) what the cause of the
problem is, because we haven't seen the real error message
(but only some after-effects - which started us posting ;-)

To see real error messages, one would need to see the whole output
of the commands in the STARTNET script. But this would probably be
umpteen hundred lines.

eg. You could add a "$ SET VERIFY" as the first line in TCPWARE:STARTNET.COM
and then reboot.
Where do you see the messages you posted so far? In PuTTY?
Or in SYS$SYSTEM:STARTUP.LOG?

2nd problem is the Network Hardware (I think, this is proved now).
You fixed it already (first with the editor, now *again* with CNFNET)
in TCPware (and not in SIMH).

btw. Have you checked the differences of the old TCPIP_CONFIGURE.COM
with the new one (you created with CNFNET)? This might be wort a look!

3rd problem was the IP address (I think, this is proved now).
You fixed it already (or so you wrote).

4th problem is the TCPware license.

Iff you fix the Hardware ID and the Mac Addr (in SIMH) to match the
previous (real) hardware, then no TCPware license change is neccessary.
IIRC it checks for F$GETSYI("SID"), F$GETSYI("CPU") and F$GETSYI("XCPU")

But as the old/real VAX hardware is broken, it might be hard to get SIMH
identical (as you can't check it and be sure then).
 
>Do I have to re-licence TCPWare because the hardware has changed?

You could fix SIMH (hardware ID, Serial Number and Mac Addr) iff you can
*or* ask PSC (http://www.process.com) for a relicense.

-EPLAN

PS: I tend to think, that you better get a VMS consultant
(as this seems not trivial at all)
-- 
Peter "EPLAN" LANGSTÖGER
Network and OpenVMS system specialist
E-mail  Peter at LANGSTOeGER.at
A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist