[Info-vax] Migrated VMS 5.X to simh - TCPWare error
Dave
BaxterD at tessco.com
Thu Feb 17 14:37:23 EST 2011
On Feb 17, 1:58 pm, Bob Gezelter <gezel... at rlgsc.com> wrote:
> On Feb 17, 12:14 pm, "gregor.oelze" <gregor.oe... at gmail.com> wrote:
>
>
>
>
>
> > Hello there,
>
> > once upon a time, there was a VAX 3100 running VMS 5.1 until these
> > days but then the hardware crashed. We managed to attach the harddrive
> > (400MB-SCSI) to a random
>
> > linux computer and made a dump of the harddrive with dd. At first we
> > just wanted to recover the files, but by the time we were searching
> > for a way to mount it, we
>
> > found the solution to emulate the VAX Hardware, using simh for linux.
>
> > So we bought a new computer, installed the latest server(x64) version
> > of ubuntu, installed simh from the current repositories of ubuntu and
> > copy'n'pasted the
>
> > configuration file (vms.ini) from a tutorial that we found in the www:
>
> > (http://www.wherry.com/gadgets/retrocomputing/vax-simh.html). After
> > renaming the .dd file in a .dsk file, we bootet up simh and it worked.
> > So we have a runnin
>
> > machine with ethernet support.
>
> > But: We cant get the TCPWare TCP-IP Stack to run on the simulated vax.
> > The goal is to communicate with a GenRad Testappliance which is
> > running fine in a BNC-Network.
>
> > There are some scripts in the VMS System !ftp which automatically
> > initiates a ftp-connection to the Genrad-Machine-but since the tcp-
> > stack isnt running-its not
>
> > working. Note: The Network is fine. We can access the Genrad-Machine
> > with the Ubuntu Host with a PCI BNC-Nic successfully.
>
> > The error, which appears after booting the virtual Vax is:
>
> > ---|
> > SNIP|---------------------------------------------------------------------------------------
>
> > %STARTNET-F-ERROR, error during execution (NETCU START/IP SVA-0
> > 192.9.201.130 /FLAGS=NOTRAILERS)
> > -STARTNET-I-SHUTNET, shutting down TCPware ...
>
> > %SET-I-INTSET, login interactive limit = 64, current interactive value
> > = 0
> > 17-FEB-2011 14:15:35
> > SYSTEM job terminated at 17-FEB-2011 14:15:37.82
>
> > Accounting information:
> > Buffered I/O count: 1605 Peak working set
> > size: 690
> > Direct I/O count: 787 Peak page file
> > size: 3447
> > Page faults: 8171 Mounted
> > volumes: 0
> > Charged CPU time: 0 00:00:05.09 Elapsed time: 0
> > 00:00:10.09
>
> > ---|
> > SNIP|---------------------------------------------------------------------------------------
>
> > The IP-Address of the GenRad machine: 192.9.201.131 the former ip of
> > the VAX: 192.9.201.130-the IP of the Ubuntu-machine: 192.9.201.130.
>
> > The vms.ini file:
>
> > ---|SNIP|--------------------------
> > set cpu 32m
> > set tto 7b
> > set tti 7b
> > set cr dis
> > set lpt dis
> > set rl dis
> > set rq0 ra81
> > att rq0 vms2.dsk
> > set rq1 dis
> > set rq2 dis
> > set rq3 dis
> > set ry dis
> > set ts dis
> > set tq tk50
> > att tq0 tape.tap
> > set tq1 dis
> > set tq2 dis
> > set tq3 dis
> > set xq enabled
> > set xq type=DEQNA
> > set xq mac=00-4f-49-03-1a-93
> > att xq eth1
> > ;set console telnet=23
> > ;att nvr vms.nvr
> > ;dep bdr 0
> > boot cpu
> > ---|SNIP|--------------------------
>
> > Simh says that the second nic, was attached properly. But with, or
> > without the right network configuration, the error message, mentioned
> > above is appearing at
>
> > startup.
>
> > Our best guess at the moment is, that the System is refering to paths
> > which dont exist anymore. The 400MB drive used to be DKA0 , but the
> > simh-hdd is recognized as
>
> > DUA0. Could it be, that the system should be "reroutet" internally to
> > the new HDD-Device name.
>
> > If we can't get the internal TCPIP communication to run - is there a
> > way to get binary files out of the simh-simulated vms system? I read
> > about kermit, enabled
>
> > telnet in simh, started the kermit-server in vms and typed "telnet
> > 127.0.0.1" on c-kermit on the ubuntu-machine - but the connection
> > could not be established.
>
> > So. It would be great if you could give me/us some points where we
> > cant start-because I am not really used to the VMS System at all (even
> > if I can now "browse"
>
> > through the file-system, edit and show files" - and understand the
> > help system).
>
> > best regards
>
> > Anaxagoras
> > aka. Gregor Oelze
>
> Gregor,
>
> That is an old one. 5.x is a while ago.
>
> I strongly suspect that you are suffering a device naming problem. I
> would have to dig out some old material, but SVA-0 is the name for the
> integral Ethernet adapter on the non-Qbus MicroVAX/VAXstation systems.
>
> The easiest path is to redo the IP configuration. It should default
> the device name correctly.
>
> You may also want to involve someone who is familiar with OpenVMS,
> changing random settings can cause problems [Disclosure: We do provide
> such services].
>
> - Bob Gezelter,http://www.rlgsc.com- Hide quoted text -
>
> - Show quoted text -
you could also try, on your VAX simulator,
$ mc ncp show known circuits
Known Circuit Volatile Summary as of 17-FEB-2011 14:27:53
Circuit State Loopback Adjacent
Name Routing Node
EIA-0 on
EWA-0 on
EWA-1 on
This will show you the names of your circuits. You will probably
only have one.
now look for a file called TCPWARE_CONFIGURE.COM in the logical
location TCPWARE:, i.e.
$ dir TCPWARE:TCPWARE_CONFIGURE.COM
Directory SYS$SYSROOT:[TCPWARE]
TCPWARE_CONFIGURE.COM;12 TCPWARE_CONFIGURE.COM;11
edit this file (I know, I know! it says dont edit this file), and look
for the string "SVA-0", and replace it with the circuit name you got
from NCP.
It should appear on a line which looks something like;
$ NETCU_LINES == "LPB-0 127.0.0.1,EIA-0 10.20.110.207 /
MASK=255.255.255.0 /"
^ ^
here, (circuit)
(IP Address)
See if that fixes your problem. (assuming your IP addresses are
correct). it might get you past the TCPWARE startup in anycase.
Dave.
More information about the Info-vax
mailing list