ALPHA MICROSYSTEMS RIGHT. FROM THE START. ALPHA MICROSYSTEMS RIGHT. FROM THE START. ALPHA MICROSYSTEMS RIGHT. FROM THE START. ALPHA MICROSYSTEMS RIGHT. FROM THE START. ALPHA MICROSYSTEMS RIGHT. FROM THE START. ALPHA MICROSYSTEMS RIGHT. FROM THE START. ALPHA MICROSYSTEMS RIGHT. FROM THE START. ALPHA MICROSYSTEMS RIGHT. FROM THE START. ALPHA MICROSYSTEMS RIGHT. FROM THE START. ALPHA MICROSYSTEMS RIGHT. FROM THE START. ALPHA MICROSYSTEMS RIGHT. FROM THE START. ALPHA MICROSYSTEMS RIGHT. FROM THE START.
© 1996 Alpha Microsystems REVISIONS INCORPORATED REVISION DATE 00 March 1989 01 July 1990 02 November 1991 03 February 1995 04 June 1996 05 September 1996 AlphaNET Installation Guide To re-order this document, request part number DSO-00064-00. This document applies to AlphaNET version 2.4 and later. The information contained in this manual is believed to be accurate and reliable.
Table of Contents CHAPTER 1 - INTRODUCTION PREPARING FOR THE FUTURE ALPHA MICRO COMMUNICATIONS PRODUCTS ABOUT THIS BOOK CHAPTER 2 - BUILDING A SIMPLE NETWORK STEPS TO BUILDING A NETWORK 1. Download AlphaNET Software 2. Enter the Product Installation Code 3. Install the Required Network Hardware Installing the Hardware 4. Create a Network Initialization File DRIVER= NETWORK= GROUP= NODE= NODECHECK= NODECOUNT= GROUPCOUNT= NAME= DEVICEADDRESS= 5. Create a Network Ersatz File 6. Create a SYSNAM.DAT File 7.
Page ii Table of Contents Setting Up Sharable Memory Adding the VTSER Background Job VTSER and Network Security TDVDEF (AMOS 2.
Chapter 1 - Introduction PREPARING FOR THE FUTURE Constructing and planning a network takes a bit of thought. Although building an AlphaNET network is not difficult, as time goes by, you may find your simple two- or three-node Ethernet network needs to expand to reach out to other AlphaNET networks or to non-AlphaNET networks such as Novell® PC LANs, or UNIX TCP/IP networks.
Page 1-2 Chapter One AlphaTCP, see the AlphaTCP User’s Guide, AlphaTCP Administrator’s Guide, and AlphaTCP Release Notes. This product is available separately from AlphaNET. ABOUT THIS BOOK Chapter 2 of this book gives an overview of building a simple, two-node Ethernet network. Chapter 3 contains more detailed information on installing AlphaNET, with more in-depth explanations. The explanations are oriented towards building an Ethernet network, but also apply to serial connection SerialNET networks.
Chapter 2 - Building a Simple Network Sometimes people find building a network a rather confusing task. This chapter gives an overview of what is involved in constructing a simple, two-computer AlphaNET network. Rather than going into detail on each hardware and software step, we touch briefly on each concept and direct you to detailed explanations later in this book.
Page 2-2 Chapter Two 2. Enter the Product Installation Code After copying the AlphaNET software onto your computer, you must code that software to run on your specific computer. See “Installing the Product Installation Code” in Chapter 3 for details on using the NETINI command to enter the Product Installation Code (PIC). 3. Install the Required Network Hardware Before we discuss the software configuration procedures required to define a network, we need to determine what hardware we need.
Building a Simple Network Page 2-3 Figure 1. Two Computer Network Configuration 3. Now we have two computers with all the hardware and software required to create a network environment. The next step is to define the network. 4. Create a Network Initialization File The network initialization file contains all the parameters used to define your computer on the network. Each time the system boots, the computer processes this file and uses the information to initialize your network device driver.
Page 2-4 Chapter Two DRIVER=AM319 NETWORK=100 GROUP=1 NODE=1 ; Each computer must have unique node number ; within same network and group. NODECHECK=ON NODECOUNT=2 GROUPCOUNT=1 NAME=Accounting Network ; DEVICEADDRESS=6 The sections below discuss each of these lines. DRIVER= Our network is based on two Eagle 300s, which use a driver called AM319.NDV, so the correct entry for the DRIVER statement is AM319. (It is not necessary to enter the .NDV extension.
Building a Simple Network Page 2-5 NODECHECK= If NODECHECK is set to ON, AlphaNET will check to see if the node exists before it attempts to communicate with it. If the node cannot be located, you will immediately get the error message: Node does not exist. If NODECHECK is set to OFF, if AlphaNET cannot find a node you will still get the same error message, but it will take a few extra seconds.
Page 2-6 Chapter Two 1677787137You use a cpuID whenever you communicate with another computer on the network. (See the AlphaNET User’s Guide for examples.) By creating a network ersatz file, you can assign unique, easy to remember names to represent the cpuID number for each computer on the network, including your own. See “Defining Ersatz Names for Your Network” in Chapter 3 for more details. Finding out the cpuID for a particular computer is easy.
Building a Simple Network Page 2-7 Systems Available: Accounting Network (self) 16777871377 DAVE: 1677787138- Status: Node is on the network Accounts Receivable AMOS/32 2.1(353)Company Payroll AMOS/32 2.2B(416) 7. Modify the System Initialization Command File So far, we have created everything required to make our network functional.
Page 2-8 Chapter Two MOUNT DSK1: MOUNT DSK2: MOUNT DSK3: MOUNT DSK4: ; SETJOB JOB2,TERM2,400K,SETJOB.JIN ; SETJOB TASK,MANAGR,200K,TSKMGR.JIN WAIT TASK ; SETJOB MALSER,MALSER,80K,MALSER.JIN WAIT MALSER ; SETJOB NETSER,NETSER,100K,NETSER.JIN WAIT NETSER ; SETJOB VTSER,VTSER,32K,VTSER.JIN ; LOG SYSTEM SERVICE LOG OPR: ; SET LINK DAVE: ; MEMORY 0 The sections below discuss the marked lines briefly, but see Chapter 3 for detailed information.
Building a Simple Network Page 2-9 connection process. The number specification following the ETHZON statement will always be assigned the same number as used in the first element of the TRMDEF statement. TDVDEF AM62A,AM62,AM72,AM75 TDVDEF is only supported on AMOS 2.1 or later releases; it is not supported in AMOS 1.X releases. The TDVDEF statement loads the specified terminal drivers for use by virtual terminal connections.
Page 2-10 Chapter Two SETJOB VTSER,VTSER,32K,VTSER.JIN Virtual terminal connections afford remote users essentially the same user privileges as local users. If you choose to support virtual terminal connections, make sure you read the section dealing with network security in Chapter 3. This statement attaches the VTSER job, allocates memory for the job, and processes the VTSER job initialization file (VTSER.JIN).
Building a Simple Network Page 2-11 TESTING THE NETWORK In order to test our work, we need to bring up the computers on the network using the modified TEST.INI file; type: LOG OPR: RETURN MONTST AMOS32,TEST.INI RETURN or: LOG OPR: RETURN MONTST AMOSL,TEST.INI RETURN depending on which monitor your computer uses. As each of the computers is booting up on the modified TEST.INI file, watch the terminal screens and make sure the computers boot without error.
Chapter 3 - Installing the AlphaNET Software Installing the AlphaNET software is much the same no matter what physical method of interconnecting your computers you choose to use. This chapter describes how to install that common body of software prior to performing any hardware specific installation which is covered in the hardware installation documentation accompanying your Ethernet interface board for Ethernet installations, or in Chapter 4 for SerialNET installations.
Page 3-2 Chapter Three Once the software has been copied onto your hard disk drive, use the VERIFY command to make sure all software transferred without error. Type: VERIFY NET.DIR RETURN The VERIFY program will check each file and report any errors. Installing the Product Installation Code Under AMOS 2.3 and later, this procedure is not necessary. Beginning with AMOS 2.3, the AlphaNET software is enabled when you enter the PIC for AMOS. There is no separate AlphaNET PIC.
Installing the AlphaNET Software Page 3-3 If you do not create a SYSNAM.DAT file, NTSTAT will display a blank for your computer description. The release contains a sample file named SYSNAM.NEW. UPDATING THE SYSTEM INITIALIZATION FILE Installing the AlphaNET software consists of adding the following items to your system initialization command file: • An increased number of available jobs to allow for virtual terminal connections and remote procedure calls.
Page 3-4 Chapter Three bytes of system memory, so it is best to be on the safe side and allocate more JOBS than you think you actually need. Adding the NETSER Background Job AlphaNET requires one job be running the NETSER program in the background to act as a server for other computers. 1. Add the jobname NETSER to the JOBALC statement. 2. Define a TRMDEF statement for a terminal named NETSER using the PSEUDO interface driver and NULL terminal driver. 3.
Installing the AlphaNET Software Page 3-5 Adding the VTSER Background Job A background job is required to execute VTSER, the virtual terminal server program. If you do not wish to have other computers connect virtual terminals to your computer, you do not need to set up this job. 1. Add the jobname VTSER to the JOBALC statement. 2. Define a TRMDEF statement for a terminal named VTSER using the PSEUDO interface and NULL terminal driver. 3.
Page 3-6 Chapter Three :T LOG DSK0:[1,4] VTSER/S MAGICWORD The password, which appears in bold type in the example, can be up to 10 characters long; VTSER does not distinguish between upper and lower case letters. To protect your VTSER password, the file containing the password should be located on a logical disk device which can’t be accessed over the network. The system initialization command file with the above VTSER job should also contain the command SET NOACCESS DSK0:.
Installing the AlphaNET Software Page 3-7 Initializing the Remote Procedure Call System The remote procedure call facility requires you allocate and initialize a support module, RPC.SYS, within system memory. To do so, add the command SYSTEM RPC.SYS/N to the other SYSTEM commands within the system initialization command file. Defining a Network For each network your computer connects to, you must define the network using the NETINI command.
Page 3-8 Chapter Three The value defined in the GROUPCOUNT statement must be equal to, or greater than, the number of groups defined on your network. If you do not include a GROUPCOUNT statement in your network initialization file, the GROUPCOUNT number defaults to 1. This is not a problem if you only have one group defined on your network, but if you have more than one group defined, you will not be able to communicate with all the groups defined on your network.
Installing the AlphaNET Software Page 3-9 Turning on the Network The SET LINK command turns on the network and allows your computer to both send and receive data over the network. You can use SET LINK from within the system initialization command file or at AMOS command level, but log into OPR: first in either case. You can specify a node ersatz name or you can use your cpuID number.
Page 3-10 Chapter Three SYSTEM SMEM 1M ; MOUNT DSK1: MOUNT DSK2: MOUNT DSK3: MOUNT DSK4: ; SETJOB JOB2,TERM2,400K,SETJOB.JIN ; SETJOB TASK,MANAGR,200K,TSKMGR.JIN WAIT TASK ; SETJOB MALSER,MALSER,80K,MALSER.JIN WAIT MALSER ; SETJOB NETSER,NETSER,100K,NETSER.JIN WAIT NETSER ; SETJOB VTSER,VTSER,32K,VTSER.JIN ; LOG SYSTEM SERVICE LOG OPR: ; SET LINK DAVE: ; MEMORY 0 The job initialization file NETSER.JIN should contain the following: :T LOG DSK0:[1,4] NETSER The job initialization file VTSER.
Installing the AlphaNET Software Page 3-11 Why Use Type 2 Connections? Type 2 connections provide substantially higher performance than the standard Type 1 connections. With Type 1 connections, all communication between the connecting terminal and the host computer go through a single job, VTSER. This makes VTSER a bottleneck when multiple connections are in effect, slowing down communication.
Page 3-12 Chapter Three This is similar to the traditional TRMDEF statement. The #10 causes 10 TCBs with associated terminal buffers to be made available for use by remote job connections. You can have only one TRMDEF #count statement in your initialization file. If you have more than one, all of them after the first are ignored. For best results, the special TRMDEF statement described above should be the last TRMDEF statement in your system initialization command file. In AMOS 2.
Installing the AlphaNET Software Page 3-13 Once the computer has booted correctly, use SYSTAT to make sure the job running NETSER is in an MS state, and the job running VTSER is in an SL state. If not, recheck your TEST.INI file to make sure these jobs were properly initialized. If you are unsuccessful after several tries, you may wish to attach either one of these background jobs to a real terminal during the boot process so you may see any error messages they may be reporting.
Chapter 4 - Installing SerialNET This chapter gives you an overview of the hardware used by SerialNET. SerialNET uses the existing serial terminal interface hardware on your computer. Due to the availability of serial interfaces on every Alpha Micro computer, SerialNET makes an ideal interconnection for setting up gateways between networks.
Page 4-2 Chapter Four Network type: Topology: Maximum Segment Length: Max. Nodes/Net: Medium: Bit Rate: Termination: Packet Size: Point-to-point asynchronous connection Point-to-point 50 ft. (RS-232), 1000 ft. (RS-422) 2 Shielded cable recommended Up to 57,600 BPS Not needed 12 to 4096 bytes per packet BUILDING CABLES FOR SERIALNET The cables used by SerialNET are constructed in the same manner as normal terminal cables, including shielding and length considerations.
Installing SerialNET Page 4-3 DO NOT modify your system initialization command file directly, but create a test copy, TEST.INI, and modify that. Once this copy is executing properly, you may replace your original system initialization command file with the test copy. CREATING A NETWORK INITIALIZATION FILE FOR SERIALNET The following is an example of the file (SERnnn.NIN) that will install your computer on the network. For more details on the network initialization file, see Chapter 3.
Page 4-4 Chapter Four CHECKING OUT THE INSTALLATION Once you have made all of the changes to system initialization command file and the network initialization command file, you are ready to start testing. See Chapter 3 for information on testing the system initialization command file.
Chapter 5 - Installing Network Gateways Gateways allow you to gain access to networks your computer is not physically connected to. This is done by routing all traffic for that network to a network node which does have a physical connection. This extra routing is transparent to both you and the software in use. You must, however, pre-define all networks to which you wish to connect, and establish routing paths for each.
Page 5-2 Chapter Five Four Networks AlphaNET Installation Guide, Revision 05
Installing Network Gateways Page 5-3 Look at the network example in the figure above; note there are network initialization files defining each computer (node) on all four networks. However, the elements necessary for creating a gateway between the networks are missing. Without the gateway defined, the communication between computers in our network example would be very limited.
Page 5-4 Chapter Five INITIALIZATION FILES DEFINING NETWORKS AND GATEWAYS Function of Initialization File Computer’s own network definition. Gateway definition linking computer to Ethernet Network 4. Gateway definition linking computer to Serial Network 1. Gateway definition linking computer to Serial Network 2 Gateway definition linking computer to Serial Network 3. COMPUTER A COMPUTER B COMPUTER C Serial Network 1 cpuID 16842754SER001.
Installing Network Gateways Page 5-5 INITIALIZATION FILES DEFINING NETWORKS AND GATEWAYS (PART 2) Function of Initialization File Computer’s own network definition. COMPUTER D Ethernet Network 4 cpuID 67174401ETH004.NIN DRIVER=ETHER NETWORK=4 GROUP=1 NODE=1 NODECOUNT=3 NODECHECK=OFF NAME=Ethernet 4 COMPUTER E Ethernet Network 4 cpuID 67174402ETH004.NIN DRIVER=ETHER NETWORK=4 GROUP=1 NODE=2 NODECOUNT=3 NODECHECK=OFF NAME=Ethernet 4 COMPUTER F Ethernet Network 4 cpuID 67174403ETH004.
Page 5-6 Chapter Five When actually defining a FORWARDTO address, you may use an ersatz name in place of the cpuID number (that’s the big decimal number). See Chapter 3 of this document for more information on the use of ersatz names.
Index . G .GIN file · 5-1 .NIN file · 3-7 Gateway · 5-1 FORWARDTO · 5-3 initialization file (.
Page ii O Operating system compatibility · 3-1 Index Spawned jobs · 3-3, 3-12 SYSNAM.DAT · 3-2 System initialization command file · 3-3 sample · 3-9 testing · 3-3, 3-13 P Password · 3-6 PIC · 3-2 review · 3-2 Product Installation Code · See PIC Protecting devices · 3-6 R Remote procedure call handler · See RPC.SYS RPC.SYS · 3-3, 3-7 S SerialNET · 4-1 cables, building · 4-2 features · 4-1 hardware · 4-1 initialization file, SERnnn.INI · 4-3 installation · 4-1 specifications · 4-2 SERnnn.
