|
TcpLink 3000 CS |
INAC Computer Innovative Netzwerkanwendungen |
||
| Benutzerhandbuch TcpLink 3000 CS in englischer Sprache | |||
ASPECT diskTCP/IP network,
or to operate the SPECSTORE unit for archiving
a program called TCP
is required on the ASPECT . Additionally, a number
of files must be available on the ASPECT that contain configuration
information of different kind. All these files are marked by the
ADAKOS file name extension .tcp. The TCP program
is delivered on the installation diskette and is transferred to
the ASPECT during the installation procedure. This is at the same time
a test that the ASPECT is working correctly together with TCPLINK
or SPECSTORE.
Insert the installation diskette in the floppy disk drive.
Turn the power of the unit on.
Press the boot button. The installation program is now
invoked from the diskette. Move over to the ASPECT keyboard.
There you must enter a small boot program that fetches
the program TCP from the installation diskette.
You need enter this program only once. Then you store it on disk
and archive it on an ASPECT diskette if you need it again at a
later stage.
Press the STOP, CLEAR, and TEST1 buttons on the ASPECT front panel
in this sequence. On the LED display (or printer, not on the
graphics monitor), you will get
the prompt >. Now you must enter the numbers of the list
shown below into the computer locations starting at 1000.
Typing 1000/ opens address 1000,
and its current contents are printed. It can be overriden by
entering the first number of the list on the keyboard, followed
by the Line Feed or CTRL/J key. The effect is, that
the next computer address is opened automatically, and the next
number from the list may be enterd. The very last number
should be terminated by the Return or Enter key in
oder to close the last location. A location that was closed
inadvertently by typing Return instead of Line Feed
can be re-opened by typing the address, followed by a /.
The second column is the list of numbers to be entered. The first column displays the corresponding computer address in octal number representation.
1000 6000026
1001 1123025
1002 4010003
1003 6000023
1004 1413024
1005 1437026
1006 6000020
1007 2413026
1010 1421023
1011 1535024
1012 4010006
1013 6000013
1014 1123023
1015 302000
1016 1241026
1017 457001
1020 7000001
1021 14
1022 13
1023 0
1024 0
1025 12345670
1026 1777
1027 0
1030 617111
1031 4010002
1032 633111
1033 5010005
After having entered the list, please verify if everything is
correct. Open again location 1000 by typing 1000/, and
continue by hitting the Line Feed or CTRL/J key.
Inspect each number printed and compare it with the list until
list end.
The next step is to store the program on disk. Restart the ASPECT
in order the obtain the ADAKOS asterisk (*) prompt (do not switch
computer power off!). Type in
STO BOOT 1000-1033;1000'P
The boot program is now available under the name BOOT.
If you want to save it on dikette, you would do it using the
command COP BOOT/=F1.
The purpose of the boot program is to fetch the program TCP
from the installation diskette. Perform this step now by
typing RUN BOOT. After a few seconds the ASPECT should
stop. This can be recognized from the front panel on the computer
where the green LED of the STOP button should be lit.
Booting the program TCP failed if either this is not the case,
or if the red LED labelled AC shows a zero.
Turn the computer power off and check the connection
cable to TCPLINK or SPECSTORE unit in this case. Then restart the
unit and the ASPECT , and type again RUN BOOT.
After successfully booting TCP , write down the number displayed
by the AC LED. Then type CTRL/E and
press the CONTINUE button of the ASPECT front panel
in order to get the ADAKOS prompt back,
and store TCP on disk by entering the following ADAKOS
command line:
STO TCP 2000-NUMBER;2001'IXP
NUMBER is the number you have written down from the AC display.
Installation of TCP is now complete.
ASPECT . You may use for example
teco or the DISNMRcommands ed or edit.
| File | Contents |
|---|---|
| HOSTS.TCP | List of ethernet stations to be accessed |
| CONFF.TCP | Ethernet hardware configuration file |
| CONFP.TCP | Ethernet software configuration file |
| <destination>.TCP | destination file(s ) |
Please set up the required files in the format given by the following examples. Ajust the parameters according to your particular installation. The explaining text in parentheses must not be included.
This file must contain in the first line the internet address of your unit, followed by the name under which you want to access it. The following lines must contain the internet addresses of all computers on the network you want to exchange data with.
100.7.100.14 name localhost (internet address & name of TCPlink unit)100.7.150.10 sparc (from here, specify the list of the hosts and their)
160.9.100.38 pc1 (names to be accessed from TCPlink)
180.7.200.28 indigo
exit (must terminate the file)
This file and the next one (confp.tcp) are required when you configureTCPLINKlater on via the commandTCP C. Please check these items with your network administrator.182.7.204.74 (insert here the internet address of your TCPlink)subnet 0 (network and subnetwork routing mask)
show (display hardware configuration status)
exit (must terminate the file)
hostname name1 (define symbolic name of TCPlink unit)userid name2 (user id for use by other hosts)
window 512 (set smaller for hosts that overrun TCPlink)
gw 182.7.200.247 (in case of more than 1 LAN, define gateway)
show (display software configuration status)
exit (must terminate the file)
You may select the name of this file yourself (the extension .tcp is mandatory), and you may set up several of these files if you want to use different destinations. Each file contains the description of a target system to which you want to sent data (or retrieve them).The file format is slightly different whether the target is a
UNIXcomputer on the network, aDOSPC on the network, or an archiving device such as diskette connected to you unit. Destination file for data transfer withUNIXhosts:The host name must have been assigned a network address in the file hosts.tcp.indigo (destination host name)max (user login id on destination host)
xam12xrt (user password on destination host)
/usr/people/max/datafiles (destination directory on host )
exit (must terminate the file)
Destination file for data transfer with
DOSPC hosts:The difference tocompaq (destination host name)max (user login id on destination host)
xam12xrt (user password on destination host)
d:/data/nmr (destination directory on host )
exit (must terminate the file)
UNIXhost destination files is that the destination directory must start with the name of theDOSdevice where the directory is located.Destination file for data transfer with local devices: Host name, login id and password are not required. Instead, the archiving device must be selected via its device code.
Please note that the simplest form of a destination directory is /. Each unit has at least one archiving device available, namely a 3.5 inch floppy disk drive. Additionala: (device code of the archive, e.g. 'a:'=floppy drive)/data (destination directory on archive )
exit (must terminate the file)
SPECSTOREdevices will get device codes such as e:, f:, ... assigned.
SPECSTORE magnetic devices, but
TCP/IP operation over the network is not required.
Host computers on the TCP/IP network can communicate
with TCPLINK if an ftp server is active on the host.
This is usually true by default for UNIX systems. On
DOS PCs the server must be started explicitely by the user.
TCPLINK was tested using the server ftpsrv of
FTP Software.
A few commands provided by TCP require that a remote shell
can be executed on the host and are therefore not available
for DOS PCs on the network. These commands are the format
control commands for directory listings, and remote command
execution. A particular restriction is the following: you
can only transfer files from a PC via network back to the ASPECT if
the file fits entirely in the memory of TCPLINK. The standard
equipment of TCPLINK is such that 512K data points can be
handled. Larger data sets require extra memory. Please note
that this restriction applies only to PC hosts under DOS,
and to the back transfer of data.
The following installation work must be performed on UNIX host
computers that are to communicate with the ASPECT .
TCPLINK unit must be made known to the
host. This is done by editing the files /etc/hosts and
/etc/hosts.equiv, or by adding the information to a name
server if one is active. This work is usually done by the system
or network administrator.
TCPLINK makes use of the TCP/IP client program rsh.
It is required that this command may be executed for the current
user of TCPLINK on the host. Any user of TCPLINK must have a
user id and a password on the host. In the home directory of the
user a file .rhosts must be created (if not yet existing) that
contains the node name of TCPLINK .
If rsh cannot be executed on the host, data transfer will
work with the few restrictions mentioned above for DOS PCs.
ASPECT . This is decribed later in more detail.
Alternatively, extra memory in TCPLINK can be installed.
ASPECT text files are to be converted to the
UNIX text file format, or vice versa.
This is also decribed later in more detail.
TCP ip
configuration is dependent on the particular software package used
and must be performed according to the manufacturer's manual.
TCPLINK configurationSPECSTORE magnetic devices, but
TCP/IP operation over the network is not required.
If the hardware and software installation was performed successfully as
described in the previous sections, you have to provide
TCPLINK the configuration information as contained in the files
conff.tcp, confp.tcp, and hosts.tcp.
Please proceed as follows:
Insert the operation diskette in the TCPLINK unit and
re-boot. This procedure takes about one minute. The boot procedure is
finished as soon as the floppy drive is no longer active. Move
over to the ASPECT keyboard and type in the following command:
TCP C. After about 30 seconds, the configuration information
is returned, indicating that it was successful. The displayed text
is also stored in the file prot.tcp and may be
printed from there.
Please not that whenever you made changes to the files conff.tcp, confp.tcp, and hosts.tcp you must re-execute this configuration procedure in order to make them effective.