Freeway ® User Guide DC 900-1333P Protogate, Inc.
Protogate, Inc. 12225 World Trade Drive, Suite R San Diego, CA 92128 (858) 451-0865 Freeway User Guide © 2002 Protogate, Inc. All rights reserved Printed in the United States of America This document can change without notice. Protogate, Inc. accepts no liability for any errors this document might contain. Freeway is a registered trademark of Simpact, Inc. All other trademarks and trade names are the properties of their respective holders.
Contents List of Figures 9 List of Tables 13 Preface 15 1 23 Freeway Introduction 1.1 1.2 2 Freeway Overview . . . . Freeway Concepts . . . . 1.2.1 Freeway Services . . 1.2.2 User Customization 1.2.3 Server Management 1.2.4 SNMP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Freeway User Guide 2.2.2.3 CPIO Format Distributions . . . . . . . . . . . . . 2.2.3 Modify the Boot and Load Files . . . . . . . . . . . . . . 2.2.4 Build the DLI and TSI Files. . . . . . . . . . . . . . . . . 2.2.5 Build the CS API Library File. . . . . . . . . . . . . . . . 2.2.6 Compile the Example Server-Resident Application . . . . 2.2.7 Compile the Server Toolkit . . . . . . . . . . . . . . . . . 2.2.8 Build the Loopback Tests . . . . . . . . . . . . . . . . . . 2.
Contents 3 Customize the System Configuration 97 3.1 3.2 Determine If You Need to Customize System Configuration Customize the Default Boot Configuration File . . . . . . . 3.2.1 Configuration Parameters for ICP_IP Virtual Devices . 3.3 Server TSI Configuration . . . . . . . . . . . . . . . . . . . 3.3.1 TSI Configuration Overview. . . . . . . . . . . . . . . 3.3.2 Default Server TSI Configuration File (muxcfg) . . . . 3.4 Customize the Default Server TSI Configuration File . . . . 4 . . . . . . . .
Freeway User Guide 4.4.5.3 Display IP Statistics. . . . . . . . . . . 4.4.5.4 Display ICMP Statistics . . . . . . . . 4.4.6 Display User Names. . . . . . . . . . . . . . 4.4.7 Display Current System Time . . . . . . . . 4.5 Modify Configuration . . . . . . . . . . . . . . . 4.5.1 Modify Boot Parameters . . . . . . . . . . . 4.5.2 Modify User Names . . . . . . . . . . . . . . 4.5.3 Modify System Time . . . . . . . . . . . . . 4.6 Trace Functions . . . . . . . . . . . . . . . . . . 4.7 Disk Drive Options . .
Contents A Installation at a Glance 197 A.1 UNIX Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 A.2 VMS Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 A.3 Windows NT Installations . . . . . . . . . . . . . . . . . . . . . . . . . . 208 B Freeway Files B.1 Default Directory Structure. . B.1.1 Server-resident Software . B.1.2 ICP-resident Software . . B.1.3 Client-resident Software . 215 . . . . . . . . . . . . . . . . . . . . . . . .
Freeway User Guide 8 DC 900-1333P
List of Figures Figure 1–1: Freeway Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Figure 2–1: Sample UNIX /etc/hosts File . . . . . . . . . . . . . . . . . . . . . . . . . 35 Figure 2–2: Sample Load File for ICP6000 . . . . . . . . . . . . . . . . . . . . . . . . . 48 Figure 2–3: Sample Load File for ICP2432 . . . . . . . . . . . . . . . . . . . . . . . . . 69 Figure 2–4: Sample Load File for ICP2424 . . . . . . . . . . . . . . . . . . . . . . . . .
Freeway User Guide Figure 4–18: Display Circular Queue of Messages . . . . . . . . . . . . . . . . . . . . . 140 Figure 4–19: Display Network Statistics Menu . . . . . . . . . . . . . . . . . . . . . . 141 Figure 4–20: Display TCP Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Figure 4–21: Display UDP Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Figure 4–22: Display IP Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List of Figures Figure 4–50: Copy Hard Disk File to Floppy Disk . . . . . . . . . . . . . . . . . . . . . 185 Figure 4–51: Floppy Disk Maintenance Options Menu. . . . . . . . . . . . . . . . . . . 186 Figure 4–52: Display Floppy Disk Directory . . . . . . . . . . . . . . . . . . . . . . . . 187 Figure 4–53: Delete Floppy Disk File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Figure 4–54: Rename Floppy Disk File . . . . . . . . . . . . . . . . . . . . . . . . . . .
Freeway User Guide 12 DC 900-1333P
List of Tables Table 2–1: Summary of Software Installation Steps . . . . . . . . . . . . . . . . . . . . 30 Table 2–2: Protocol Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Table 2–3: Client TSI Configuration Files (UNIX) . . . . . . . . . . . . . . . . . . . . 54 Table 2–4: Client DLI Configuration Files (UNIX) . . . . . . . . . . . . . . . . . . . . 55 Table 2–5: Client TSI Configuration Files (UNIX) . . . . . . . . . . . . . . . . . . . .
Freeway User Guide 14 DC 900-1333P
Preface Purpose of Document This document describes how to install and operate software on Protogate’s Freeway server. Note The information in this document refers to the Freeway models from Protogate and Simpact that use the VxWorks operating system. As of this document revision (Feb 2002), these Freeway models have been replaced with newer hardware models. The specifications of the newer hardware will be reflected in a later edition of this document. Go to Protogate’s web page (www.protogate.
Freeway User Guide • Power cord (Freeway 1300 and 8800 have two power cords) • Set of keys (for hinged front panel on Freeway 1100/1150/1200/1300) • Console cable (each end of the cable has both a 9-pin and a 25-pin connector) (Freeway 1100/1150/1200/1300) • Cable with a 9-pin and a 25-pin connector on each end (Freeway 2000/4000/8800 with an MVME 2600 CPU board) • Appropriate serial cables to connect the ICPs to the data communications equipment (Freeway 1100/1150/1200/1300) • Boot parameter in
Preface • Cables for connecting Freeway to the LAN and WAN • Synchronous modem for loopback testing Organization of Document Chapter 1 gives an overview of the Freeway server. Chapter 2 describes the Freeway software installation procedures. Chapter 3 describes how to customize the system configuration. Chapter 4 describes the Freeway menus used in basic operation.
Freeway User Guide Hardware Support • • • • • • • • • • • Freeway 500 Hardware Installation Guide DC-900-2000 Freeway 1100/1150 Hardware Installation Guide DC-900-1370 Freeway 1200/1300 Hardware Installation Guide DC-900-1537 Freeway 2000/4000 Hardware Installation Guide DC-900-1331 Freeway 3100 Hardware Installation Guide DC-900-2002 Freeway 3200 Hardware Installation Guide DC-900-2003 Freeway 3400 Hardware Installation Guide DC-900-2004 Freeway 3600 Hardware Installation Guide DC-900-200
Preface Application Program Interface (API) Programming Support • • • Freeway Data Link Interface Reference Guide DC-900-1385 Freeway Transport Subsystem Interface Reference Guide DC-900-1386 QIO/SQIO API Reference Guide DC-900-1355 Socket Interface Programming Support • Freeway Client-Server Interface Control Document DC-900-1303 Toolkit Programming Support • Freeway Server-Resident Application and Server Toolkit Programmer Guide DC-900-1325 • • OS/Impact Programmer Guide DC-900-1030 Pr
Freeway User Guide Document Conventions The term “Freeway” refers to any of the Freeway models (for example, 1100, 1150, 1200, 1300, 2000, 4000, or 8800). A Freeway with an MVME 162 CPU board is a 68K-based Freeway 2000/4000/8800 with 5/24/99 Ginni: Eric says to leave CPU 7 in this list in case a customer with an older Freeway gets this manual. a CPU 7, 8, 9, or 10 based on the Motorola MVME 162 single-board computer. The handle of the CPU board is labelled “MVME 162.
Preface Revision Release Date Description DC 900-1333G March 1996 Updated for version 2.4 release Removed bootp information Clarified server toolkit information Replaced X.25 loopback test with CS API test Added information on: • DDCMP • ICP6030 • Marketfeed 2000 • TACMIL • Windows NT DC 900-1333H May 1997 Updated for version 2.7 server release Added Freeway 8800 information DC 900-1333I August 1997 Updated for version 2.7.
Freeway User Guide Customer Support If you are having trouble with any Protogate product, call us at (858) 451-0865 Monday through Friday between 8 a.m. and 5 p.m. Pacific time. You can also fax your questions to us at (877) 473-0190 any time. Please include a cover sheet addressed to “Customer Service.” We are always interested in suggestions for improving our products. You can use the report form in the back of this manual to send us your recommendations.
Chapter 1 Freeway Introduction This manual describes how to install and operate software on your Freeway server. Before installing the server software, you should familiarize yourself with basic Freeway concepts as described in this introductory chapter. Then you can proceed to Chapter 2 which contains the software installation procedures. Refer to the Glossary for Freeway terminology and acronyms. 1.
Freeway User Guide Freeway can be configured with multiple WAN interface processor boards, each of which is a Protogate ICP. Each ICP runs the communication protocol software using Protogate’s real-time operating system. AAAAAAAA AAAAAAAA AAAAAAAA AAAAAAAA AAAAAAAA AAAAAAAA AAAAAAAA AAAAAAAA AAAAAAAA Industry Standard Bus AA AA AA AA AA AA AA AA Server Processor WAN Interface Processors WAN Protocol Options SCADA ICP Defense Commercial X.25 Bisync HDLC . . .
1: Freeway Introduction Summary of product features: • Provision of WAN connectivity either through a LAN-based Freeway server or directly using an embedded ICP • Elimination of difficult LAN and WAN programming and systems integration by providing a powerful and consistent data link interface • Variety of off-the-shelf communication protocols available from Protogate which are independent of the client operating system and hardware platform • Support for multiple WAN communication protocols simult
Freeway User Guide 1.2 Freeway Concepts Decreased size of body paragraphs and headings to get last sentence on this page. The following concepts support the Freeway features described in Section 1.1. 1.2.1 Freeway Services Freeway can be configured to offer a number of services to clients residing on the LAN. These services are shared among applications designed to operate in the client/server model of today’s distributed computing environment.
1: Freeway Introduction 1.2.4 SNMP Support Freeway software provides an SNMP v1/v2c-compliant SNMP agent that supports read-only SNMP access to Freeway-supported MIBs. Freeway provides SNMP support for the MIBs listed below, regardless of which ICP-resident protocol service is used. • Protogate enterprise MIB for Freeway • RFC-1213 (MIB-II) support for LAN interfaces Selected ICP-resident protocol services provide additional SNMP support for read-only access to the MIBs listed below.
Freeway User Guide 28 DC 900-1333P
Chapter 2 Software Installation This chapter describes how to install the Freeway server/client, protocol, and toolkit software. You must have installed the Freeway hardware as described in the appropriate Freeway hardware installation guide. Note After you have followed the detailed software installation procedures outlined in this chapter, you can refer to the “Installation at a Glance” summary in Appendix A as a quick reference for future installations.
Freeway User Guide Table 2–1 summarizes the software installation steps. Table 2–1: Summary of Software Installation Steps Steps Reference Section(s) 1. Select a UNIX, VMS, or Windows NT computer on the same LAN as Freeway that supports TCP/IP and the file transfer protocol (FTP) or, for UNIX or Windows NT, remote shell (RSH). You will use this computer for Freeway software installation and also configure it as the Freeway boot server. 2. Configure the computer to act as a boot server. 3.
2: Software Installation The software installation procedures described in this chapter refer to file names that include a “ppp” identifier to indicate a specific protocol. Table 2–2 shows the “ppp” identifiers for various protocols. For example, pppalp translates to awsalp for AWS, fmpalp for FMP, or spsalp for protocol toolkit.
Freeway User Guide 2.1 Configure the Boot Server Before you can boot Freeway, the boot server and Freeway must be configured to communicate with each other. Multiple Freeway servers can be configured to boot from the same boot server. The following steps are required: 1. Create a file transfer protocol (FTP) or remote shell (RSH) user account on the boot server (Section 2.1.2); as shipped, the boot parameters are set to boot the system using FTP. 2.
2: Software Installation 2.1.1 Configure FTP or RSH The boot server must support the file transfer protocol (FTP) or remote shell (RSH). RSH is available on UNIX and Windows NT systems, but not on VMS systems. Freeway uses FTP or RSH to request each of its download files from the boot server. To respond to the download requests, the boot server must also have the FTP or RSH daemon process running. On UNIX systems, the /etc/inetd.conf command file usually starts the FTP or RSH daemon process.
Freeway User Guide In UNIX systems, the files to which Freeway requires access are in the default /usr/local/freeway directory which is created during the installation procedure described in Section 2.2.2. In VMS systems, the files to which Freeway requires access are in the default 7/23: SAVE THIS MARGINPAR Ron Tabor says it’s okay to say the default directories for NT are installed under C:\freeway; even for 4.
2: Software Installation For Windows NT systems, the Internet addresses and system names of computers on the network are maintained in the hosts or lmhosts file. If your network is managed by a domain name server, the hosts file should not be edited locally, as it is maintained and distributed by the domain name server. If you are not using a domain name server, this file can be edited on the boot server.
Freeway User Guide Step 2: Select a system name and Internet address for the Freeway server and enter them on a line in the hosts files of the Freeway boot server and any LAN network device that will be communicating with Freeway. If you have more than one Freeway server, enter one line for each server. In the sample hosts file in Figure 2–1, two Freeway servers have been defined. The first has an Internet address of 192.168.45.6 and a system name of freeway1. The second has an Internet address of 192.
2: Software Installation 2.2 Install the Freeway Software onto a UNIX Computer This section describes how to install the Freeway software from the distribution media onto a UNIX computer. Later in these procedures you will use this computer as a boot server to boot Freeway. Note After you have followed the detailed software installation procedures outlined in this chapter, you can refer to the “Installation at a Glance” summary in Appendix A as a quick reference for future installations. 2.2.
Freeway User Guide 2.2.1.1 Server/Client Software The server/client distribution media is labeled Freeway Server Software. The following files are in the freeway directory: • readme.ser provides general information about the server software • relnotes.ser provides specific information about the current release of the server software • env486, env68k, envcom, and envppc are environment definition files for the exam- ple server-resident application (SRA) • MakeSRA.I486, MakeSRA.68K, and MakeSRA.
2: Software Installation • fw2604 is the system boot file for a Freeway 2000/4000/8800 with an MVME 2600 CPU • fw486.sym is the symbol table for the Freeway 1100/1150/1200/1300 boot image • fw162.sym is the standard symbol table for the boot image of a Freeway 2000/4000/8800 with an MVME 162 CPU 9 or CPU 10 • fw162l.sym is the limited memory symbol table for the boot image of a Freeway 2000/4000/8800 with an MVME 162 CPU 7 or CPU 8 • fw2604.
Freeway User Guide • fw162d is the debug version of the standard system boot file for a Freeway 2000/4000/8800 with an MVME 162 CPU 9 or CPU 10 • fw2604d is the debug version of the system boot file for a Freeway 2000/4000/8800 with an MVME 2600 CPU • fw486d.sym is the symbol table for the Freeway 1100/1150/1200/1300 debug server image • fw162d.sym is the standard symbol table for the debug server image of a Freeway 2000/4000/8800 with an MVME 162 CPU 9 or CPU 10 • fw2604d.
2: Software Installation 2.2.1.2 Server Toolkit Software The Server Toolkit distribution media is labeled Freeway Server Toolkit Software. The following files delivered with the Server Toolkit are in the freeway directory: • readme.stk provides general information about the Server Toolkit software • relnotes.stk provides specific information about the current release of the Server Toolkit software • MakeSTK.I486, MakeSTK.68K, and MakeSTK.
Freeway User Guide 2.2.1.3 Protocol or Protocol Toolkit Software The protocol or protocol toolkit distribution media is labeled Freeway [Name] Software. Note The ppp variable mentioned below specifies the particular protocol or toolkit you are using (refer to Table 2–2 on page 31). The following files are in the freeway directory: • readme.ppp provides general information about the protocol or protocol toolkit software • relnotes.
2: Software Installation Source code for the OS/Impact delivered with the protocol toolkit is in the freeway/ icpcode/os_sds directory. 2.2.2 Retrieve Files from the UNIX Distribution Media Use the following procedure to install the Freeway software from the distribution media onto your UNIX computer. Caution Remember that installing new software overwrites the previous software. Step 1: On the boot server (previously configured as described in Section 2.
Freeway User Guide Step 3: Insert the protocol or toolkit distribution media into the appropriate drive. For CD-ROM distributions, follow the instructions in Section 2.2.2.1. For tar format distributions, follow the instructions in Section 2.2.2.2. For cpio format distributions, follow the instructions in Section 2.2.2.3. Insert the server/client distribution media and retrieve the files in the same manner.
2: Software Installation 2.2.2.3 CPIO Format Distributions If the files on your distribution media are in cpio format, use the cpio command to retrieve them. Here is an example of the cpio command (the device on your system might be different): cpio -ivduBm < /dev/rst0 The cpio command creates a directory called freeway in the /usr/local directory and copies the software into it from the distribution media. 2.2.
Freeway User Guide The download_script parameter in the boot configuration file defines the path name of the load file. The load file contains the commands that download the protocol or protocol toolkit software to the ICP. cd /usr/local/freeway/boot Step 1: Edit the boot file (bootcfg.xxx) For a Freeway 1100 with both ICP2424 and ICP2432 boards installed, merge the bootcfg.isa and bootcfg.
2: Software Installation 5. If you will be using the server-resident application (SRA), uncomment the lines sra_module = sraxxx.o1 and sra_entry = sraInit to load and run the example SRA soft- ware at boot time. Also modify the tsi_config_file parameter to use the muxcfg.sra file. Step 2: Edit the load file (pppload) Freeway server release G (and later) installs the XIO image files in the freeway/boot directory.
Freeway User Guide # the below is an example for the icp2424 # #LOAD xio_2424.mem 801200 #LOAD bsc3270_fw_2424.mem 818000 #LOAD bsc3780_fw_2424.mem 849000 #INIT 818000 # # the below is an example for the icp2432 # #LOAD xio_2432.mem 801200 #LOAD bsc3270_fw_2432.mem 818000 #LOAD bsc3780_fw_2432.mem 849000 #INIT 818000 # # the below is an example for the icp6000 # LOAD xio_6000.mem 40001200 LOAD bsc3270_fw_6000.mem 40018000 LOAD bsc3780_fw_6000.
2: Software Installation 2. From your op-sys directory, create the bin and lib directories if they don’t already exist. cd op-sys Scrunched step 2 and cd op-sys lines above to get bottom list on this page. mkdir bin mkdir lib Step 2: Run the make file From the freeway/lib directory, enter one of the following commands depending on the system you are using. The newly created files will be placed in the proper freeway/client/op-sys/bin or freeway/client/op-sys/lib directory.
Freeway User Guide 2.2.6 Compile the Example Server-Resident Application To build the example SRA, you must have installed a GNU cross compiler compatible with the target CPU in your Freeway. It is recommended that you use the GNU cross compiler provided with the Wind River Systems Tornado tool set. The target CPU-specific portion of the Tornado tool set is called the Board Support Package (BSP).
2: Software Installation Step 3: Run the make file From the freeway directory, enter one of the make commands listed below. This compiles all the necessary source code and links the object files to form the SRA object module, which is then placed in the freeway/boot directory. The name of the object module generated is sra486.o for Freeway 1100/1150/1200/1300, sra68K.o for a Freeway 2000/4000/8800 with an MVME 162 CPU, or srappc.o for a Freeway 2000/4000/8800 with an MVME 2600 CPU.
Freeway User Guide 2.2.7 Compile the Server Toolkit To build a customized Freeway image using the optional Server Toolkit product, you must have purchased and installed Tornado from Wind River Systems with the appropriate Board Support Package (BSP) for your Freeway. The pc486 BSP is required for Freeway 1100/1150/1200/1300, the mv162 BSP is required for a Freeway 2000/4000/8800 with an MVME 162 CPU, and the mv2604 BSP is required for a Freeway 2000/4000/8800 with an MVME 2600 CPU.
2: Software Installation Step 3: Run the make file. From the freeway directory, enter one of the following commands.
Freeway User Guide changing the default value of the Freeway server parameter, freeway_0, to the name (or Internet address) of your current Freeway server. A client TSI configuration file might reference the server parameter more than once, and must be changed at each occurrence. Note If the server name and Internet address have not already been added to the /etc/hosts file during hardware installation, refer to Section 2.1.3 on page 34.
2: Software Installation If you are installing DDCMP, protocol toolkit, or X.25 on Freeway 1100/1150/ 1200/1300, skip to Step 3. The electrical interface for DDCMP and protocol toolkit is specified when you run the loopback test. The electrical interface for X.25 is specified in the .setup file in the freeway/client/test/x25mgr directory. If you are installing AWS, BSC, or FMP on Freeway 1100/1150/1200/1300, change to the freeway/client/test/ppp directory.
Freeway User Guide make -f makefile.sol all (for a Solaris system) make -f makefile.sun all (for a SunOS system) Go to Section 2.5 on page 93 for the next step in the installation procedure. For a description of the Freeway files you have just installed onto your boot server, refer to Appendix B.
2: Software Installation 2.3 Install the Freeway Software onto a VMS Computer This section describes how to install the Freeway software from the distribution media onto a VMS computer. Later in these procedures you will use this computer as a boot server to boot Freeway. Note After you have followed the detailed software installation procedures outlined in this chapter, you can refer to the “Installation at a Glance” summary in Appendix A as a quick reference for future installations. 2.3.
Freeway User Guide The following general files are in the FREEWAY.BOOT directory: • BOOTCFG.IP is an example boot configuration file for ICP_IP virtual devices • BOOTCFG.ISA is the boot configuration file for a Freeway 1100 with ICP2424s (ISAbus boards) • BOOTCFG.PCI is the boot configuration file for a Freeway 1100 with ICP2432s (PCI boards) and Freeway 1150/1200/1300 • BOOTCFG.
2: Software Installation • XIO_2424.MEM XIO_2432.MEM, or XIO_6000.MEM1 are the executable objects for the system-services module Various files specific to the server-resident application (SRA), such as buffer.size, ftst, and the sra files, are also in the FREEWAY.BOOT directory; however, SRA is not available on VMS. The data link interface (DLI) and transport subsystem interface (TSI) software is in the FREEWAY.LIB directory. 2.3.1.
Freeway User Guide For software releases prior to June 1, 1998, the executable object for the protocol or protocol toolkit software, ppp_FW_2424.MEM1, ppp_FW_2432.MEM9, ppp_FW_6000.MEM2, was distributed in the FREEWAY.ICPCODE.ICPXXXX.PROTOCOLS directory. For releases after June 1, 1998, these files are in the FREEWAY.BOOT directory. Source code for the loopback tests is in the FREEWAY.CLIENT.TEST.ppp directory. Source code for the protocol toolkit is in the FREEWAY.ICPCODE.PROTO_KIT directory.
2: Software Installation You might find it useful to perform the installation at a hardcopy terminal. This provides a printed record that you can use for troubleshooting if needed. Step 1: On the boot server (previously configured as described in Section 2.1), log in to an account that has system-manager privileges. Step 2: Change to the default directory called SYS$SYSDEVICE. The installation procedure is designed to use this default directory and the directory structure under it.
Freeway User Guide • Do you have adequate account quotas for installing software? VMSINSTAL checks for the various quota values. • Is DECnet up and running? (This is only checked by older versions of VMSINSTAL.) • Are any users logged on the system? Problems might occur if someone tries to use Freeway while you are installing a new release of the software. Step 4: If there are potential problems with the account quotas, the computer dis- plays: The following account quotas may be too low.
2: Software Installation Step 6: The computer displays: Enter the products to be processed from the first distribution volume set. * Products: * Enter an asterisk (this causes all products to be installed). Step 7: Depending on the release number, you will see either * Enter installation options you wish to use (none): or * Options: Refer to Digital’s VMS Installation Guide for a list of the VMSINSTAL options and how to enter them. Press to select the standard installation options.
Freeway User Guide The following products will be processed: The computer displays product names, then displays the following (Vnnnn is the current software version number): Beginning installation of Product Vnnnn at current time. %VMSINSTAL-I-RESTORE Restoring product save set A ... The computer displays other verification messages. Caution The next two steps ask you to specify the disk and directory locations where the software will be installed.
2: Software Installation Remember that ddcu means a device name. Press to answer yes (this is highly recommended). If you answer no, you are prompted to enter the name of a directory. Step 12: The computer displays: There are no more questions. The installation will proceed. The procedure completes automatically without the need for you to take any action. Depending on the speed of your system, this will take several minutes.
Freeway User Guide 2.3.3 Modify the Boot and Load Files Edit the boot configuration and load files to match your Freeway setup. Your Freeway can be set up to use both physical ICP boards and virtual ICP devices. (Virtual ICPs, or ICP_IP devices, behave just like physical ICP boards except that they transmit and receive data via an IP network rather than via a serial line.) You must modify one [FREEWAY.BOOT]BOOTCFG file to include all the information needed.
2: Software Installation Edit the boot configuration file ([FREEWAY.BOOT]BOOTCFG.xxx1) as follows: 1. Uncomment the physical parameters associated with each ICP in your Freeway. 2. For all Freeways, modify the slave_address entry of each ICP to match your configuration. For Freeway 1150/1200/1300, also modify the bus_number entry of each ICP. Appropriate slave addresses (and bus numbers where applicable) are shown in a table at the beginning of the boot configuration file. 3.
Freeway User Guide Step 2: Edit the load file (pppLOAD) Freeway server release G (and later) installs the XIO image files in the FREEWAY.BOOT directory. Prior to June 1, 1998, the XIO image files were distributed in the FREEWAY. ICPCODE.ICPXXXX.OSIMPACT directory. As a result, the load files provided with pro- tocols with a release date prior to June 1, 1998 contain a fully qualified path for the protocol and XIO image files. Such files should be modified to remove the path to the XIO image.
2: Software Installation # the below is an example for the icp2424 # #LOAD xio_2424.mem 801200 #LOAD bsc3270_fw_2424.mem 818000 #LOAD bsc3780_fw_2424.mem 849000 #INIT 818000 # # the below is an example for the icp2432 # LOAD xio_2432.mem 801200 LOAD bsc3270_fw_2432.mem 818000 LOAD bsc3780_fw_2432.mem 849000 INIT 818000 # # the below is an example for the icp6000 # #LOAD xio_6000.mem 40001200 #LOAD bsc3270_fw_6000.mem 40018000 #LOAD bsc3780_fw_6000.
Freeway User Guide 2. From your OP-SYS directory, create the BIN and LIB directories if they don’t already exist. SET DEF OP-SYS CREATE /DIR [.BIN] CREATE /DIR [.LIB] Step 2: Run the MAKE_DLI_TSI command From the FREEWAY.LIB directory, enter one of the following commands. The newly created files will be placed in the proper FREEWAY.CLIENT.OP-SYS.BIN or FREEWAY. CLIENT.OP-SYS.LIB directory. SET DEF SYS$SYSDEVICE[FREEWAY.
2: Software Installation 2.3.6 Build the QIO/SQIO API Library File If you have purchased the QIO/SQIO API, you must build the library file needed by the Freeway software. A make command is included that performs this operation. From the FREEWAY.LIB.QAPI directory, enter one of the following commands. The newly created file will be placed in the FREEWAY.CLIENT.OP-SYS.LIB directory. SET DEF SYS$SYSDEVICE[FREEWAY.LIB.
Freeway User Guide Note There is a separate server TSI configuration file, usually called MUXCFG, which does not require modification for most sites. Table 2–5: Client TSI Configuration Files (UNIX) AUTODIN AWS BSC3270 BSC2780/3780 AUTODINALTCFG AWSALTCFG DDCMP FMP ADCCP NRM Protocol Toolkit DDCMPALTCFG FMPALTCFG NRMALTCFG SPSALTCFG STD1200B Military/Government Protocol X.
2: Software Installation Open each file and locate each occurrence of ElecInterface. Remove the double slashes (//) from the beginning of each ElecInterface line. If you will not be using the default EIA-232 electrical interface, replace EIA232 with one of the following: • EIA449 • EIA530 • V35 Table 2–6: Client DLI Configuration Files (VMS) AWS AWSALDCFG BSC3270 BSC2780/3780 BSC3270ALDCF BSC3780ALDCF G G FMP FMPALDCFG Step 3: Run the MAKEVMS command From the FREEWAY.CLIENT.TEST.
Freeway User Guide Note The installed files have an owner User Identification Code (OWNER_UIC) of [1,4] that corresponds to the SYSTEM account. To be able to access the installed files, you must select (or create) a user account intended to use Freeway and set the ownership of all Freeway files and directories to that particular User Identification Code. Go to Section 2.5 on page 93 for the next step in the installation procedure.
2: Software Installation 2.4 Install the Freeway Software onto a Windows NT Computer This section describes how to install the Freeway software from the distribution media onto a Windows NT (Alpha or Intel) computer. Later in these procedures you will use this computer as a boot server to boot Freeway.
Freeway User Guide The following files are in the freeway\boot directory: • bootcfg.ip is an example boot configuration file for ICP_IP virtual devices • bootcfg.isa is the boot configuration file for a Freeway 1100 with ICP2424s (ISA- bus boards) • bootcfg.pci is the boot configuration file for a Freeway 1100 with ICP2432s (PCI boards) and Freeway 1150/1200/1300 • bootcfg.
2: Software Installation • xio_2424.mem, xio_2432.mem, or xio_6000.mem1 are the executable objects for the system-services module The following files specific to the server-resident application (SRA) are also in the freeway\boot directory: • buffer.
Freeway User Guide • sps_fw_2432.mem, sps_fw_6000.mem, and sps_fw_2424.mem are the executable objects for the protocol toolkit used with the example SRA • sra486.o, sra68K.o, and srappc.o are the object modules for the example SRA • sraload is the load file for the example SRA • muxcfg.sra is the server TSI configuration file used with the example SRA The example SRA source code is in the freeway\client\test\sra directory.
2: Software Installation The Freeway server software library archive called libserv.a and the server DLI/TSI object library called libvxwfw.o are stored in the freeway\server\lib\mv162, freeway\server\lib\mv2604, and freeway\server\lib\pc486 directories. Source code that may be modified to tailor the VxWorks operating system of the Freeway server is provided in the freeway\server\vw\config directory. Make files for rebuilding the server DLI/TSI object library are provided in the freeway\lib directory. 2.
Freeway User Guide distributed in the freeway\icpcode\icpxxxx\protocols directory. For releases after June 1, 1998, these files are in the freeway\boot directory. Source code for the loopback tests is in the freeway\client\test\ppp directory. Source code for the protocol toolkit is in the freeway\icpcode\proto_kit directory. Source code for the OS/Impact delivered with the protocol toolkit is in the freeway\ icpcode\os_sds directory. 2.4.
2: Software Installation If your Windows NT computer does not have a browser enabled, open the readme.txt file on the CD-ROM and follow the instructions. 2.4.2.2 Diskette Distributions Use the following procedure to install the Freeway software from the diskettes onto your Alpha NT or Intel NT computer. Step 1: On the boot server (previously configured as described in Section 2.1), log in to a privileged account.
Freeway User Guide 2.4.3 Modify the Boot and Load Files Edit the boot configuration and load files to match your Freeway setup. Your Freeway can be set up to use both physical ICP boards and virtual ICP devices. (Virtual ICPs, or ICP_IP devices, behave just like physical ICP boards except that they transmit and receive data via an IP network rather than via a serial line.) You must modify one freeway\boot\bootcfg file to include all the information needed.
2: Software Installation Edit the boot configuration file (freeway\boot\bootcfg.xxx1) as follows: 1. Uncomment the physical parameters associated with each ICP in your Freeway. 2. For all Freeways, modify the slave_address entry of each ICP to match your configuration. For Freeway 1150/1200/1300, also modify the bus_number entry of each ICP. Appropriate slave addresses (and bus numbers where applicable) are shown in a table at the beginning of the boot configuration file. 3.
Freeway User Guide release date prior to June 1, 1998 contain a fully qualified path for the protocol and XIO image files. Such files should be modified to remove the path to the XIO image. This allows the Freeway to boot the local copy of the XIO image provided in the boot directory with the current Freeway server release. Edit the load file (freeway\boot\pppload) for your protocol or toolkit as follows: 1. Uncomment the lines associated with the type of ICP in your Freeway. 2.
2: Software Installation # the below is an example for the icp2424 # LOAD xio_2424.mem 801200 LOAD bsc3270_fw_2424.mem 818000 LOAD bsc3780_fw_2424.mem 849000 INIT 818000 # # the below is an example for the icp2432 # #LOAD xio_2432.mem 801200 #LOAD bsc3270_fw_2432.mem 818000 #LOAD bsc3780_fw_2432.mem 849000 #INIT 818000 # # the below is an example for the icp6000 # #LOAD xio_6000.mem 40001200 #LOAD bsc3270_fw_6000.mem 40018000 #LOAD bsc3780_fw_6000.
Freeway User Guide Step 3: Dynamic link libraries must reside in the current working directory or in a directory specified in your “PATH” environment variable. Do one of the following: Add C:\freeway\client\op-sys\lib to your path. or Copy the .dll files from C:\freeway\client\op-sys\lib to your bin directory or to another directory in your path. 2.4.5 Build the CS API Files If you are using the X.25 protocol, you must build the CS API files needed by the Freeway software.
2: Software Installation 2.4.6 Compile the Example Server-Resident Application To build the example SRA, you must have installed a GNU cross compiler compatible with the target CPU in your Freeway. It is recommended that you use the GNU cross compiler provided with the Wind River Systems Tornado tool set. The target CPU-specific portion of the Tornado tool set is called the Board Support Package (BSP).
Freeway User Guide If you are using the GNU tool set distributed with Tornado to compile your SRA, you must create a custom build project using the Tornado development environment. Start by launching the Tornado development environment, then from the menu bar select Project, Customize..., then Add.... Enter one of the following for the name of the build tar- get: For Freeway 1100/1150/1200/1300: -f MakeSRA.I486 clean all For a Freeway 2000/4000/8800 with an MVME 162 CPU: -f MakeSRA.
2: Software Installation 2.4.7 Compile the Server Toolkit To build a customized Freeway image using the optional Server Toolkit product, you must have purchased and installed Tornado from Wind River Systems with the appropriate Board Support Package (BSP) for your Freeway. The pc486 BSP is required for Freeway 1100/1150/1200/1300, the mv162 BSP is required for a Freeway 2000/4000/8800 with an MVME 162 CPU, and the mv2604 BSP is required for a Freeway 2000/4000/8800 with an MVME 2600 CPU.
Freeway User Guide -f MakeSTK.I486 clean all For a Freeway 2000/4000/8800 with an MVME 162 CPU: -f MakeSTK.68K clean all For a Freeway 2000/4000/8800 with an MVME 2600 CPU: -f MakeSTK.ppc clean all Enter the path of your Freeway installation directory (for example, C:\freeway) for the working directory of the customized build just created.
2: Software Installation A client TSI configuration file might reference the server parameter more than once, and must be changed at each occurrence. Note If the server name and Internet address have not already been added to the hosts file during hardware installation, refer to your system manual for the location of the hosts file and add the appropriate information. Note There is a separate server TSI configuration file, usually called muxcfg, which does not require modification for most sites.
Freeway User Guide specified when you run the loopback test. The electrical interface for X.25 is specified in the .setup file in the freeway\client\test\x25mgr directory. If you are installing AWS, BSC, or FMP on Freeway 1100/1150/1200/1300, change to the freeway\client\test\ppp directory. Specify the electrical interface by editing the data link interface (DLI) configuration files listed in Table 2–8. Open each file and locate each occurrence of ElecInterface.
2: Software Installation 2.5 Modify the Freeway System Boot Parameters In the Freeway System Boot Parameters menu, modify the path name for the System Boot Directory. See Section 4.5.1 on page 148 for details on how to modify the boot parameters. During the UNIX default installation, example boot configuration and load files were installed in the /usr/local/freeway/boot directory. During the VMS default installation, example boot configuration and load files were installed in the SYS$SYSDEVICE:[FREEWAY.
Freeway User Guide 2.6 Boot Freeway It is assumed that you have configured the Freeway boot parameters as described in the appropriate Freeway hardware installation guide. Return to the local console next to the Freeway unit and select option 1 at the Freeway Boot System Main Menu (shown in Figure 2–5) to start the boot process. See Section 4.3.1 on page 122 for boot process details.
2: Software Installation Caution With the example server-resident application (SRA) software specified in the boot configuration file, the loopback test runs automatically when Freeway is booted. A three-headed loopback cable must be installed between links 0 and 1 of ICP 0 and a synchronous modem before booting Freeway. The loopback test opens the DLI sessions and enables the two links, then transfers data on both links.
Freeway User Guide The Freeway Interactive Menu is then displayed. Chapter 4 describes the Interactive Menu in detail. You can change the Freeway user name and password as described in Section 4.5.2 on page 154. Freeway software installation is now complete. The next section describes additional procedures. 2.
Chapter 3 Customize the System Configuration Freeway system configuration information is contained in a boot configuration file and a server transport subsystem interface (TSI) configuration file. Default versions of these files are shipped with your Freeway software and are sufficient for most sites. If you need to customize the system information in these files, follow the procedures described in this chapter. The boot configuration file (freeway/boot/bootcfg.xxx, explained further in Section 3.
Freeway User Guide 3.1 Determine If You Need to Customize System Configuration Most sites, especially sites using the default installation and only one protocol, only need to edit the bootcfg.xxx file to specify the protocol for each ICP. You might, however, decide to further customize the files for any of the following reasons: • If you installed more than one protocol (for example, FMP and X.25), you must edit the boot configuration file (freeway/boot/bootcfg.
3: Customize the System Configuration • If you want to load a server-resident application (SRA) and/or spawn an SRA task to run on Freeway, you can indicate the name of the application object module and the function name of the application’s entry point in the boot configuration file (freeway/boot/bootcfg.xxx1) See Section 3.2.
Freeway User Guide Changed space above 3.2 and top/bottom spaces in list to fit it on this page. 3.2 Customize the Default Boot Configuration File When you followed the software installation procedures in Chapter 2, the default boot configuration files were installed in the freeway/boot directory on the boot server. The boot configuration files are: • bootcfg.ip for any Freeway with ICP_IPs (virtual ICP devices) • bootcfg.isa for a Freeway 1100 with ICP2424s (ISAbus boards) • bootcfg.
3: Customize the System Configuration #----------------------------------# # ICP0 Physical Parameters # #----------------------------------# # device_name = icp0 device_type = icp2432 slave_address = 0x14 bus_number = 0 download_script = fmpload #----------------------------------# # ICP1 Example Physical Parameters # #----------------------------------# # device_name = icp1 device_type = icp2432 slave_address = 0x13 bus_number = 0 download_script = fmpload #----------------------------------# # ICP2 Examp
Freeway User Guide #---------------------------# # Server wide parameters #---------------------------# # tsi_config_file #route_add = muxcfg = 0 192.192.192.192 #sra_module #sra_entry = sra486.o = sraInit vxworks_shell = FALSE #added_interface_type = elt,2 #added_interface_mask = ffffff00 #added_interface_addr = 207.207.207.207 Figure 3–1: Freeway 1100/1150/1200/1300 Boot Configuration File (bootcfg.
3: Customize the System Configuration Device Type The device_type parameter for both ICPs in the example file is ICP2432. This indicates that the device type is an intelligent communications processor that can be downloaded with software. All ICP devices installed in a Freeway 1100/1150/1200/1300 server must be of type ICP2424, ICP2432, or ICP_IP, while those installed in a Freeway 2000/4000/8800 server must be of type ICP6000 or ICP_IP.
Freeway User Guide Download Script If the service provider owns a device that is downloadable, Freeway executes a load program on behalf of the service provider before starting the service provider image. The download_script parameter should define the name of a download script file that can be used by the download utility. If no path name is provided, Freeway searches the System Boot Directory specified in the System Boot Parameters menu (described in Section 4.5.
3: Customize the System Configuration SRA Module The optional sra_module parameter indicates the name of an object module to be downloaded at boot time by the Freeway service provider. If no path name is provided, Freeway searches the System Boot Directory specified in the System Boot Parameters menu (described in Section 4.5.1 on page 153) for the object module name indicated. A fully qualified path name to the object module may be used if the module is placed in another directory.
Freeway User Guide VxWorks Shell The vxworks_shell parameter indicates whether or not access to the VxWorks operating system through a command shell is desired. If this parameter is set to TRUE, an option will appear in the main menu of the Freeway Interactive Menus providing access to the shell.
3: Customize the System Configuration If you are using dual Ethernet or dual fast Ethernet with the elt, fei, or dc type of interface, and you anticipate switching between the primary and secondary Ethernet interface for your boot device while still connecting to the other interface, you may enter just elt,[1, 2, or 3], fei, or dc for the added_interface_type parameter. Freeway will interpret this as an instruction to attach to the first unused interface of the elt, fei, or dc type.
Freeway User Guide 3.2.1 Configuration Parameters for ICP_IP Virtual Devices ICP_IP virtual devices behave just like physical ICP boards except that they send and receive data via an IP network rather than via a serial line. This section describes the parameters in the boot configuration file used for ICP_IP devices. These parameters specify the configuration of the IP link implemented by an ICP_IP device (for example, the IP addresses and ports, data format, and so on).
3: Customize the System Configuration Socket Type The socket_type parameter must be sock_dgram, sock_stream_listen, or sock_stream_connect. (The sock_stream parameter string can be used in place of sock_stream_connect.) The sock_dgram parameter specifies a UDP/IP packet data stream. The sock_stream_listen parameter specifies a TCP/IP server (listening) socket and the sock_stream_connect parameter specifies a TCP/IP client (connecting) socket.
Freeway User Guide Time to Live The ttl parameter specifies the time-to-live of outgoing data packets. Receive Buffer Size The rcv_buf_size parameter specifies the size of the IP receive buffer in bytes. Send Buffer Size The snd_buf_size parameter specifies the size of the IP send buffer in bytes. Send Queue Size The snd_q_size parameter specifies the number of packets to be queued on a TCP/IP connection if the other side of the connection stops reading. The default is 48 packets.
3: Customize the System Configuration 3.3 Server TSI Configuration While building the loopback test program, you modified the client TSI configuration file (freeway/client/test/ppp/pppaltcfg). There is also a server TSI configuration file (freeway/boot/muxcfg 1) for the server TSI software running on Freeway. This section gives an overview of TSI configuration and describes the muxcfg file. See the Freeway Transport Subsystem Interface Reference Guide for complete details regarding TSI configuration. 3.
Freeway User Guide All sections of the TSI configuration file have the following format: connection-name { parameter-name = parameter-value; // comments... . . . } Techpubs: If you change this section, also change the equivalent section in chapter 3 of the Freeway TSI Reference Guide. 3.3.
3: Customize the System Configuration // // source control identifier // @(#)$Id: muxcfg,v 1.6 1998/06/15 21:57:25 jcolston Exp $ // //---------------------------------------------------------------------------// // // This file is for the server resident TSI configuration processor. // It is used by the TSI interface for msgmux (message multiplexor) // // Date Initials Abstracts // 27Jan94 KietD Original coding...
Freeway User Guide // Server2 { transport = "tcp-socket"; logLev = 0; traceLev = 3; timeout = 63999; MaxInQ = 10; MaxOutQ = 10; asyncio = "yes"; wellknownport = 0x'2011'; // protocol specifics } Figure 3–2: TSI Configuration File (muxcfg) for Server-Resident Software (Cont’d) Changing the AsyncIO parameter to “no” or omitting it prevents the server TSI software from operating as designed.
3: Customize the System Configuration • The parameters can appear in any order in the configuration file and can be upper-case, lower-case, or a mixture. • If a parameter is not explicitly contained in the file, the default is used (defaults are shown in Figure 3–2 on page 113). 3.
Freeway User Guide 116 DC 900-1333P
Chapter 4 Operations The Freeway server provides many facilities to manage its operation, such as: • Server management service provider (SMSP) • Simple network management protocol (SNMP) task • Interactive server management services The SMSP task starts the Freeway services at boot time. The SNMP task is an SNMP v1/v2c-compliant SNMP agent.
Freeway User Guide 4.1 Startup and Shutdown Procedures The following sections describe the typical sequence of steps used to startup and shutdown Freeway. Because startup and shutdown requirements might vary, you should check with your system administrator to establish the best procedures for your site. Note that Freeway is designed for continuous operation. Most sites leave the unit online twenty-four hours a day, seven days a week, shutting down only to perform maintenance or install upgrades. 4.1.
4: Operations You can also use rlogin (or telnet) to log in to Freeway from the boot server or any other computer on the network; for example: rlogin freeway1 telnet freeway1 Freeway User Login: simpact Freeway User Login: simpact Password: password Password: password The password is not actually displayed on the screen. When you first install Freeway, the default user name (simpact) and password (password) are in effect. Use the Modify User Names menu described in Section 4.5.
Freeway User Guide 4.2 Freeway Interactive Menu After you log in as described in Section 4.1.1 on page 118, the Freeway Interactive Menu is displayed as shown in Figure 4–1. Items 1 through 7 have their own menus as described in the following sections. The Disk Drive option is not displayed if your Freeway does not contain a disk drive. The VxWorks Shell option is only displayed if the vxworks_shell parameter in the boot configuration file is set to TRUE at boot time.
4: Operations Note After entering a selection in a Freeway menu, press . For example, to select the first menu choice, enter 1 then press .
Freeway User Guide 4.3 Shutdown Options To access the Shutdown Options menu as shown in Figure 4–2, enter ‘1’ at the Freeway Interactive Menu. Shutdown Options ---------------1) Return to Interactive Menu 2) Reboot Server Select: Figure 4–2: Shutdown Options Menu 4.3.1 Reboot Server To reboot the Freeway server, enter ‘2’ at the Shutdown Options menu. All currently running tasks are terminated immediately. Note After power up or during reboot, Freeway first executes system diagnostics.
4: Operations puter on the network, the connection to Freeway is broken when the boot process begins and you must log in again. The following operations occur during system boot: Step 1: Determine the Boot Parameters Freeway must know its boot parameters in order to download files from the boot server. Freeway obtains the boot parameters from local non-volatile memory.
Freeway User Guide • freeway/boot/bootcfg.pci defines the configuration for a Freeway 1100/1150/1200/1300 with ICP2432s (PCI boards) • freeway/boot/bootcfg.vme defines the configuration for a Freeway 2000/ 4000/8800. • The server TSI configuration file (freeway/boot/muxcfg1) describes the TSI configuration for Freeway. See Section 3.3 on page 111 for details on the muxcfg file.
4: Operations 4.4 Display Options To access the Display Options menu as shown in Figure 4–3, enter ‘2’ at the Freeway Interactive Menu.
Freeway User Guide 4.4.1 Display Log Messages To retrieve and display log messages stored on the message queue, enter ‘2’ at the Display Options menu. Note Displaying the log messages also purges them. The latest status or error messages are displayed in increments of 10 messages. You can quit at any time by pressing ‘q’ or ‘Q’, or you can view the next 10 messages by pressing . 4.4.
4: Operations 4.4.2.1 Display Physical Configuration To display the current values for each device in the Freeway server, enter ‘2’ at the Display Configuration menu. Figure 4–5 is a sample display for one device on a Freeway 1100. Freeway maintains information on each physical device installed in the system. The physical configuration database is initially configured at boot time by Freeway, which reads and parses the boot configuration file described in Chapter 3.
Freeway User Guide 4.4.2.2 Display Service Provider Configuration To display the current values for each service provider in the Freeway server, enter ‘3’ at the Display Configuration menu. Figure 4–6 is a sample display for one service provider on a Freeway 1100. Freeway maintains information on each service provider installed in the system. The service configuration database is initially configured at boot time by Freeway, which reads and parses the boot configuration file described in Chapter 3.
4: Operations 4.4.2.3 Display Boot Parameters To display the current Freeway boot parameters, enter ‘4’ at the Display Configuration menu. Figure 4–7 is a sample display for a Freeway 1100.
Freeway User Guide 4.4.3 Display Network Information To access the Display Network Information menu as shown in Figure 4–8, enter ‘4’ at the Display Options menu.
4: Operations 4.4.3.1 Display IP Network Interface Information To display the IP network interface information as shown in Figure 4–9, enter ‘2’ at the Display Network Information menu. This figure shows the display for a Freeway 1100 booting from the primary Ethernet interface. “elt” in the figure refers to the interface type as defined in the Boot Device parameter of the System Boot Parameters menu described in Section 4.5.1 on page 153.
Freeway User Guide 4.4.3.2 Display IP Network Hosts To display the IP network hosts as shown in Figure 4–10, enter ‘3’ at the Display Network Information menu. IP Network Hosts ---------------hostname inet address aliases ------------------------freeway1 192.9.200.169 localhost 127.0.0.1 antares 192.9.200.
4: Operations 4.4.3.3 Display IP Network Routing Tables To display the IP network routing tables as shown in Figure 4–11, enter ‘4’ at the Display Network Information menu. IP Network Routing Tables ------------------------ROUTE NET TABLE destination gateway flags Refcnt Use Interface --------------------------------------------------------------------192.9.200.0 192.9.200.
Freeway User Guide 4.4.3.4 Ping Another IP Host To ping another IP host as shown in Figure 4–12, enter ‘5’ at the Display Network Information menu. You must enter either an IP address in decimal dot notation (for example, 192.168.123.134) or a hostname known to the Freeway system. Ping another IP Host -------------------Enter host to ping (dot-separated IP address or hostname): 192.168.123.134 Attempting to ping "192.168.123.134" ... 192.168.123.134 is alive.
4: Operations 4.4.4 Display System Information To access the Display System Information menu as shown in Figure 4–13, enter ‘5’ at the Display Options menu.
Freeway User Guide 4.4.4.1 List I/O Devices To list the I/O devices as shown in Figure 4–14, enter ‘2’ at the Display System Information menu. I/O Devices ----------drv name 0 /null 1 /tyCo/0 1 /tyCo/1 5 /ram1/ 5 /sd6/ 7 antares: 2 /dev/pty.0S 3 /dev/pty.0M 2 /dev/pty.1S 3 /dev/pty.1M 2 /dev/pty.2S 3 /dev/pty.2M 2 /dev/pty.3S 3 /dev/pty.
4: Operations 4.4.4.2 Display TCB Summary To display the task control block (TCB) summary as shown in Figure 4–15, enter ‘3’ at the Display System Information menu.
Freeway User Guide 4.4.4.3 List Free Memory Blocks To list the free memory blocks as shown in Figure 4–16, enter ‘4’ at the Display System Information menu.
4: Operations 4.4.4.4 Display Task Stack Usage To display the task stack usage as shown in Figure 4–17, enter ‘5’ at the Display System Information menu.
Freeway User Guide 4.4.4.5 Display Circular Queue of Messages To display the circular queue of messages as shown in Figure 4–18, enter ‘6’ at the Display System Information menu. This shows the last 300 messages sent to the Freeway log.
4: Operations 4.4.5 Display Network Statistics To access the Display Network Statistics menu as shown in Figure 4–19, enter ‘6’ at the Display Options menu.
Freeway User Guide 4.4.5.1 Display TCP Statistics To display the transmission control protocol (TCP) statistics as shown in Figure 4–20, enter ‘2’ at the Display Network Statistics menu.
4: Operations 4.4.5.2 Display UDP Statistics To display the user datagram protocol (UDP) statistics as shown in Figure 4–21, enter ‘3’ at the Display Network Statistics menu.
Freeway User Guide 4.4.5.3 Display IP Statistics To display the Internet protocol (IP) statistics as shown in Figure 4–22, enter ‘4’ at the Display Network Statistics menu.
4: Operations 4.4.5.4 Display ICMP Statistics To display the ICMP statistics as shown in Figure 4–23, enter ‘5’ at the Display Network Statistics menu.
Freeway User Guide 4.4.6 Display User Names To display the user names for the Freeway server as shown in Figure 4–24, enter ‘7’ at the Display Options menu. Users ----freeway1 freeway2 freeway3 Press RETURN to continue Figure 4–24: Display User Names 4.4.7 Display Current System Time To display the current system time for the Freeway server as shown in Figure 4–25, enter ‘8’ at the Display Options menu.
4: Operations 4.5 Modify Configuration To access the Freeway Modify Configuration menu as shown in Figure 4–26, enter ‘3’ at the Freeway Interactive Menu.
Freeway User Guide 4.5.1 Modify Boot Parameters To modify the Freeway boot parameter settings, enter ‘2’ at the Modify Configuration menu. Figure 4–27 shows typical boot parameter settings for a Freeway 2000. Any changes made to these parameters are stored in Freeway’s non-volatile memory. Table 4–1 describes each parameter.
4: Operations Freeway System Boot Parameters -----------------------------Enter '.' to erase parameter Enter '' for no parameter change Boot Device Processor Number FTP User Name FTP Password Flags Freeway Server Name Freeway Inet Address Freeway Subnet Mask Boot Server Name Boot Server Inet Address System Boot Directory System Boot File Name Configuration File Name Secondary Net Interface Gateway Inet Address : : : : : : : : : : : : : : : ei 0 freeway password 0 freeway2 192.168.45.
Freeway User Guide Table 4–1: Freeway System Boot Parameter Descriptions Boot Parameter Boot Device Description Freeway 1100/1150/1200/1300: • to boot over Ethernet from the boot server using the primary 3Com Etherlink III network interface card (NIC), set the boot device to one of the following depending on the physical connector you will be using: elt,1 to use the AUI connection elt,2 to use the BNC connection elt,3 to use the RJ45 connection • to boot over Ethernet from the boot server using the se
4: Operations Table 4–1: Freeway System Boot Parameter Descriptions (Cont’d) Boot Parameter Description Processor Number This parameter is the number of server processors in the Freeway server minus one. Currently, a Freeway server can support only one server processor. The only valid number for this parameter is 0. FTP User Name If booting from the boot server, Freeway uses this name to log in to its FTP (or RSH). The default is freeway. This is not required if you are booting from the local disk.
Freeway User Guide Table 4–1: Freeway System Boot Parameter Descriptions (Cont’d) Boot Parameter System Boot Directory Description If the Freeway boot files will be stored in the home directory of the FTP (or RSH) user account, clear this field. Otherwise, enter the full path name of the boot directory. The default UNIX directory is /usr/local/freeway/boot. The default VMS directory is SYS$SYSDEVICE:[FREEWAY.BOOT]. For Windows NT versions earlier than 4.0, the default directory is c:\freeway\boot.
4: Operations Table 4–1: Freeway System Boot Parameter Descriptions (Cont’d) Boot Parameter Gateway Inet Interface Description If your Freeway and boot server are on the same network, clear this parameter, which is the default. If they are on different networks, enter the IP address of the gateway processor on the Freeway’s network that provides access to the boot server’s network.
Freeway User Guide 4.5.2 Modify User Names To modify the Freeway user names, enter ‘3’ at the Modify Configuration menu. The Modify User Names menu is shown in Figure 4–28. You can then select ‘2’ to add a user name or ‘3’ to delete one. In either case, you are prompted to enter the user name, then asked to enter the password twice. There can be up to 10 user names. User names can be up to 80 characters in length and can include spaces.
4: Operations 4.5.3 Modify System Time To modify the current system time for the Freeway server as shown in Figure 4–29, enter ‘4’ at the Modify Configuration menu and type in the date and time in the same format as shown on the screen.
Freeway User Guide 4.6 Trace Functions The current trace status is shown in parentheses in the Trace Function option in the Freeway Interactive Menu. To access the Trace Functions menu as shown in Figure 4–31, enter ‘4’ at the Freeway Interactive Menu. Enter ‘2’ to turn trace on. Freeway then saves messages moving to and from the client in a circular buffer. When trace data fills the buffer, the oldest trace data is overwritten with new trace data.
4: Operations If you booted Freeway from a local disk, you can use the File Transfer Protocol to move the file from the local disk to your local directory. Figure 4–30 shows an example using a Freeway 1100. If you are using a Freeway 2000/4000/8800, the directory is /sd6/, with the slash at both ends, rather than /ide. antares% ftp freeway1 Connected to freeway1. 220 VxWorks (5.1.
Freeway User Guide Trace Functions --------------1) Return to Interactive Menu 2) Turn MSGMUX Trace On 3) Turn MSGMUX Trace Off 4) Process Trace Data Select: Figure 4–31: Trace Functions Menu 158 DC 900-1333P
4: Operations 4.7 Disk Drive Options To access the Disk Drive Options menu as shown in Figure 4–32, enter ‘5’ at the Freeway Interactive Menu. Note If your Freeway does not have a certain drive (for example, a hard disk), the options for that drive are not displayed. On a Freeway 2000/4000/8800, the floppy menu will not be displayed until after a floppy is inserted in the floppy disk drive; after that, the menu will be displayed even if no floppy is in the drive.
Freeway User Guide 4.7.1 Hard Disk Copy Options To access the Hard Disk Copy Options menu as shown in Figure 4–33, enter ‘2’ at the Disk Drive Options menu.
4: Operations 4.7.1.1 Display Hard Disk Directory To display the hard disk directory as shown in Figure 4–34, enter ‘2’ at the Hard Disk Copy Options menu. Note File names for the Freeway 2000/4000/8800 are case sensitive. Display Disk Devices -------------------ID LUN VendorID ProductID Rev.
Freeway User Guide 4.7.1.2 Display Hard Disk File To display a hard disk file as shown in Figure 4–35, enter ‘3’ at the Hard Disk Copy Options menu. If you change your mind about displaying a file, simply press , then you will be prompted to press again. Note File names for the Freeway 2000/4000/8800 are case sensitive.
4: Operations 4.7.1.3 Copy Boot Server File to Hard Disk To copy a boot server file to the hard disk as shown in Figure 4–36, enter ‘4’ at the Hard Disk Copy Options menu. If you change your mind about copying a file, simply press , then you will be prompted to press again. Note The Freeway 1100/1150/1200/1300 hard disk uses an MS-DOS file system.
Freeway User Guide 4.7.1.4 Copy Hard Disk File to Floppy Disk To copy a hard disk file to the floppy disk as shown in Figure 4–37, enter ‘5’ at the Hard Disk Copy Options menu. If you change your mind about copying a file, simply press , then you will be prompted to press again. Note The Freeway 1100/1150/1200/1300 hard disk uses an MS-DOS file system.
4: Operations 4.7.1.5 Copy Floppy File to Hard Disk To copy a floppy file to the hard disk as shown in Figure 4–38, enter ‘6’ at the Hard Disk Copy Options menu. If you change your mind about copying a file, simply press , then you will be prompted to press again. Note The Freeway 1100/1150/1200/1300 hard disk uses an MS-DOS file system.
Freeway User Guide 4.7.2 Hard Disk Maintenance Options To access the Hard Disk Maintenance Options menu as shown in Figure 4–39, enter ‘3’ at the Disk Drive Options menu.
4: Operations 4.7.2.1 Display Hard Disk Directory To display the hard disk directory as shown in Figure 4–40, enter ‘2’ at the Hard Disk Maintenance Options menu. Note File names for the Freeway 2000/4000/8800 are case sensitive. Display Disk Devices -------------------ID LUN VendorID ProductID Rev.
Freeway User Guide 4.7.2.2 Build Hard Disk from Boot Server To build the hard disk from the boot server, enter ‘3’ at the Hard Disk Maintenance Options menu. Note To build the hard disk, you must have previously configured a computer on your network to serve as the Freeway boot server and installed all the server and protocol software on the boot server. These procedures are explained in Chapter 2. Table 4–3 shows a summary of the steps you must perform to build the hard disk from the boot server.
4: Operations Freeway 2000/4000/8800 uses the VxWorks DOS file system long name support feature. This feature allows the use of file names longer than MS-DOS’s 8.3 convention. These names can be up to 40 characters long and can be made up of any ASCII characters. In addition, a period, which in MS-DOS indicates a file-name extension, has no special significance. File names for the Freeway 2000/4000/8800 are case sensitive.
Freeway User Guide • Freeway 2000/4000/8800: freeway/icpcode/icp6000/protocols/x25_fw_ 6000.
4: Operations on page 148 describes how to modify the boot parameters. Any changes made to these parameters are stored in Freeway’s non-volatile memory. Table 4–1 on page 150 describes each parameter. Figure 4–41 shows the System Boot Parameters screen modified for booting from the boot server. Freeway System Boot Parameters -----------------------------Enter '.
Freeway User Guide Step 4: Boot Freeway from the Boot Server To verify that the boot parameters are correct, boot Freeway by selecting “Shutdown Options” at the Freeway Interactive Menu, then selecting “Reboot Server.” Rebooting is described in Section 4.3.1 on page 122. If the boot fails, the hard disk cannot be built. When the boot process is successful, the login prompt appears. Log in to the Freeway server with the default user name (simpact) and password (password).
4: Operations 3. Opens the boot configuration file on the hard disk to determine the ICP device name and the name of the ICP download script file. 4. Copies the download script file (for example, freeway/boot/x25load) from the boot server to the hard disk. 5. Opens the download script file on the hard disk. 6. Copies the executable object for the system-services module from the boot server to the hard disk: • Freeway 1100 with ICP2424s (ISAbus boards): freeway/icpcode/icp2424/ osimpact/xio_2424.
Freeway User Guide 8. Repeats Step 4 through Step 7 for all download script files listed in the boot configuration file 9. Copies any modules identified in the boot configuration files with the sra_module parameter to the hard disk. 10.
4: Operations Freeway System Boot Parameters -----------------------------Enter '.' to erase parameter Enter '' for no parameter change Boot Device Processor Number FTP User Name FTP Password Flags Freeway Server Name Freeway Inet Address Freeway Subnet Mask Boot Server Name Boot Server Inet Address System Boot Directory System Boot File Name Configuration File Name Secondary Net Interface Gateway Inet Address : : : : : : : : : : : : : : : ide=0,0 0 freeway password 0 freeway1 192.168.45.
Freeway User Guide Log in to the Freeway server with the default user name (simpact) and password (password). You can log in from the local console, or use rlogin or telnet to log in from the boot server or any other computer on the network. The Freeway Interactive Menu is displayed. The boot process includes reading the system boot file from the hard disk into server memory and transferring control to it. Then the boot configuration file is read from the hard disk into server memory.
4: Operations 4.7.2.3 Delete Hard Disk File To delete a hard disk file as shown in Figure 4–43, enter ‘4’ at the Hard Disk Maintenance Options menu. If you change your mind about deleting a file, simply press , then you will be prompted to press again. Note The Freeway 1100/1150/1200/1300 hard disk uses an MS-DOS file system.
Freeway User Guide 4.7.2.4 Rename Hard Disk File To rename a hard disk file as shown in Figure 4–44, enter ‘5’ at the Hard Disk Maintenance Options menu. If you change your mind about renaming a file, simply press , then you will be prompted to press again. Keep these points in mind regarding file names on a Freeway hard disk: • The Freeway 1100/1150/1200/1300 hard disk uses an MS-DOS file system.
4: Operations Enter file name to rename: Figure 4–44: Rename Hard Disk File DC 900-1333P 179
Freeway User Guide 4.7.3 Floppy Disk Copy Options To access the Floppy Disk Copy Options menu as shown in Figure 4–45, enter ‘4’ at the Disk Drive Options menu.
4: Operations 4.7.3.1 Display Floppy Disk Directory To display the floppy disk directory as shown in Figure 4–46, enter ‘2’ at the Floppy Disk Copy Options menu. Note File names for the Freeway 2000/4000/8800 are case sensitive. Display Disk Devices -------------------ID LUN VendorID ProductID Rev.
Freeway User Guide 4.7.3.2 Display Floppy Disk File To display a floppy disk file as shown in Figure 4–47, enter ‘3’ at the Floppy Disk Copy Options menu. If you change your mind about displaying a file, simply press , then you will be prompted to press again. Note File names for the Freeway 2000/4000/8800 are case sensitive.
4: Operations 4.7.3.3 Copy Boot Server File to Floppy Disk To copy a boot server file to the floppy disk as shown in Figure 4–48, enter ‘4’ at the Floppy Disk Copy Options menu. If you change your mind about copying a file, simply press , then you will be prompted to press again. Note The Freeway 1100/1150/1200/1300 hard disk uses an MS-DOS file system.
Freeway User Guide 4.7.3.4 Copy Floppy Disk File to Hard Disk To copy a floppy disk file to the hard disk as shown in Figure 4–49, enter ‘5’ at the Floppy Disk Copy Options menu. If you change your mind about copying a file, simply press , then you will be prompted to press again. Note The Freeway 1100/1150/1200/1300 hard disk uses an MS-DOS file system.
4: Operations 4.7.3.5 Copy Hard Disk File to Floppy Disk To copy a hard disk file to the floppy disk as shown in Figure 4–50, enter ‘6’ at the Floppy Disk Copy Options menu. If you change your mind about copying a file, simply press , then you will be prompted to press again. Note The Freeway 1100/1150/1200/1300 hard disk uses an MS-DOS file system.
Freeway User Guide 4.7.4 Floppy Disk Maintenance Options To access the Floppy Disk Maintenance Options menu as shown in Figure 4–51, enter ‘5’ at the Disk Drive Options menu.
4: Operations 4.7.4.1 Display Floppy Disk Directory To display the floppy disk directory as shown in Figure 4–52, enter ‘2’ at the Floppy Disk Maintenance Options menu. Note File names for the Freeway 2000/4000/8800 are case sensitive. Display Disk Devices -------------------ID LUN VendorID ProductID Rev.
Freeway User Guide 4.7.4.2 Delete Floppy Disk File To delete a floppy disk file as shown in Figure 4–53, enter ‘3’ at the Floppy Disk Maintenance Options menu. If you change your mind about deleting a file, simply press , then you will be prompted to press again. Note The Freeway floppy disk uses an MS-DOS file system. File names must follow the DOS convention of having a base name of no more than eight characters followed by a period and an extension of no more than three characters.
4: Operations 4.7.4.3 Rename Floppy Disk File To rename a floppy disk file as shown in Figure 4–54, enter ‘4’ at the Floppy Disk Maintenance Options menu. If you change your mind about renaming a file, simply press , then you will be prompted to press again. Note The Freeway floppy disk uses an MS-DOS file system. File names must follow the DOS convention of having a base name of no more than eight characters followed by a period and an extension of no more than three characters.
Freeway User Guide 4.8 Run VxWorks Shell To access the VxWorks shell as shown in Figure 4–55, enter ‘6’ at the Freeway Interactive Menu. The VxWorks shell allows you to interactively invoke any subroutine that has been loaded into Freeway’s memory, including those supplied by the VxWorks operating system, those supplied by Protogate, and those defined in any of your own application modules that have been loaded using the sra_module parameter in the boot configuration file (Section 3.
4: Operations Loading symbol table from scribe:/rose/ron/2/freeway/boot/fw486.sym ...
Freeway User Guide 4.9 Example SRA Menu To access the Example SRA Menu as shown in Figure 4–56, enter ‘7’ at the Freeway Interactive Menu. Note This option is only displayed if the example SRA is loaded and run using the sra_module and sra_entry parameters in the boot configuration file. See the Freeway Server-Resident Application and Server Toolkit Programmer Guide for information on modifying this menu option.
4: Operations 4.9.1 Display Loaded Modules To display the object modules that have been loaded onto Freeway as shown in Figure 4–57, enter ‘2’ at the Example SRA Menu. See the Freeway Server-Resident Application and Server Toolkit Programmer Guide for information on modifying the Example SRA Menu options. MODULE NAME MODULE ID GROUP # TEXT START DATA START BSS START --------------- ---------- ---------- ---------- ---------- ---------sra486.
Freeway User Guide Enter number of minutes to run (1 - 60): 1 Task "sraalp" spawned. (1 minutes). Press RETURN to continue0x591bdc (sraalp): 981203_111057: STATUS: Open_Sess: Session 0 opened to msgmux. 0x591bdc (sraalp): 981203_111057: STATUS: Open_Sess: Session 1 opened to msgmux. 0x591bdc (sraalp): 981203_111058: STATUS: Attach: Session 0 attached to ICP. 0x591bdc (sraalp): 981203_111059: STATUS: Attach: Session 1 attached to ICP.
4: Operations 4.10 Logout To logout of your Freeway session, select the Logout option in the Freeway Interactive Menu. If you logout from a local console, you return to the Freeway User Login prompt. If you logout from an rlogin or telnet session, you return to your system prompt.
Freeway User Guide 196 DC 900-1333P
Appendix A Installation at a Glance After you are familiar with the detailed software installation procedures described in Chapter 2, you can use one of the following summaries as a quick reference for a default installation. Section A.1 describes a UNIX installation, Section A.2 describes a VMS installations, and Section A.3 describes a Windows NT installation. If you need more information on any of the summary steps, see the page number reference shown in italics.
Freeway User Guide A.1 UNIX Installations Step 1: Install the Freeway software Chapter 2 Note Remember that the ppp variable indicates the particular protocol or toolkit you are using (refer to Table 2–2 on page 31). a. Log in to a root or other privileged account. page 43 b. cd /usr/local page 43 c. Insert the distribution media into the appropriate drive. page 44 d. Copy the software onto your computer. page 45 Step 2: Edit the boot configuration file (bootcfg.
A: Installation at a Glance d. Modify the name of the load file in each download_script entry. e. If you have moved the load file from the boot directory, enter the path name for the load file in each download_script entry. f. If you will be using the SRA, uncomment the lines sra_module = sraxxx.o1 and sra_entry = sraInit to load and run the example SRA software at boot time. Also modify the tsi_config_file parameter to use the muxcfg.sra file. g. For ICP_IP virtual devices, modify the bootcfg.
Freeway User Guide c. Run the make file: cd /usr/local/freeway/lib make -f Makefile.op-sys all The op-sys variable indicates the operating system: DEC, HPUX, SGI, SOL, or SUN. The newly created files will be placed in the proper freeway/client/ op-sys/bin or freeway/client/op-sys/lib directory. Step 5: Build the CS API library file (X.25 only) page 49 a. Run the make file: cd /usr/local/freeway/lib/cs_api make -f makefile.
A: Installation at a Glance e. Run the make file: cd /usr/local/freeway For a Freeway 1100/1150/1200/1300: /usr/wind/host/sun4-sunos4/bin/make -f MakeSRA.I486 clean all For a Freeway 2000/4000/8800 with an MVME 162 CPU: /usr/wind/host/sun4-sunos4/bin/make -f MakeSRA.68K clean all For a Freeway 2000/4000/8800 with an MVME 2600 CPU: /usr/wind/host/sun4-sunos4/bin/make -f MakeSRA.
Freeway User Guide (Freeway 2000/4000/8800 with an MVME 162 CPU) or freeway/envppc file (Freeway 2000/4000/8800 with an MVME 2600 CPU). c. Run the make file. For Freeway 1100/1150/1200/1300: /usr/wind/host/sun4-solaris2/bin/make -f MakeSTK.I486 clean all For a Freeway 2000/4000/8800 with an MVME 162 CPU: /usr/wind/host/sun4-solaris2/bin/make -f MakeSTK.68K clean all For a Freeway 2000/4000/8800 with an MVME 2600 CPU: /usr/wind/host/sun4-solaris2/bin/make -f MakeSTK.
A: Installation at a Glance Step 9: Modify the Freeway system boot parameters page 93 If you did not install the software in /usr/local, modify the path name for the System Boot Directory. Log in to Freeway. From the Freeway Interactive Menu, select “Modify Configuration,” then select “Modify Boot Parameters.” Step 10: Boot Freeway to download the software page 94 To boot Freeway from the Freeway Interactive Menu, select “Shutdown Options,” then select “Reboot Server.
Freeway User Guide A.2 VMS Installations Step 1: Install the Freeway software Chapter 2 Note Remember that the ppp variable indicates the particular protocol or toolkit you are using (refer to Table 2–2 on page 31). a. Log in to an account that has system-manager privileges. page 61 b. SET DEF SYS$SYSDEVICE page 61 c. Insert the distribution media into the appropriate drive. page 61 d. Copy the software onto your computer.
A: Installation at a Glance d. If you have moved the load file from the BOOT directory, enter the path name for the load file in each download_script entry. e. For ICP_IP virtual devices, modify the BOOTCFG.IP file to reflect your network configuration as described in Section 3.2.1 on page 108. Step 3: Edit the load file (pppLOAD) page 68 a. Uncomment the lines associated with the type of ICP in your Freeway. b. Modify path names as needed. c.
Freeway User Guide Step 5: Build the CS API library file (X.25 only) page 70 a. Run the MAKEVMS command: SET DEF SYS$SYSDEVICE[FREEWAY.LIB.CS_API] @MAKEVMS "" [MULTINET, TCPWARE, or UCX] The newly created file will be placed in the FREEWAY.CLIENT.OP-SYS.LIB directory. Step 6: Build QIO/SQIO API library file page 71 a. Run the MAKEVMS file: SET DEF SYS$SYSDEVICE[FREEWAY.LIB.QAPI] @MAKEVMS "" [MULTINET, TCPWARE, or UCX] The newly created file will be placed in the FREEWAY.CLIENT.OP-SYS.LIB directory.
A: Installation at a Glance c. Run the MAKEVMS command: @MAKEVMS "" [MULTINET, TCPWARE, or UCX] The newly created files will be placed in the FREEWAY.CLIENT.OP-SYS.BIN directory. Step 8: Modify the Freeway system boot parameters page 93 Modify the path name for the System Boot Directory. Log in to Freeway. From the Freeway Interactive Menu, select “Modify Configuration,” then select “Modify Boot Parameters.
Freeway User Guide A.3 Windows NT Installations Step 1: Install the Freeway software Chapter 2 Note Remember that the ppp variable indicates the particular protocol or toolkit you are using (refer to Table 2–2 on page 31). a. Log in to a privileged account. page 81 b. Insert the diskette in the appropriate drive. page 81 c. Copy the software onto your computer. page 81 Step 2: Edit the boot configuration file (bootcfg.
A: Installation at a Glance e. If you will be using the SRA, uncomment the lines sra_module = sraxxx.o1 and sra_entry = sraInit to load and run the example SRA software at boot time. Also modify the tsi_config_file parameter to use the muxcfg.sra file. f. For ICP_IP virtual devices, modify the bootcfg.ip file to reflect your network configuration as described in Section 3.2.1 on page 108. Step 3: Edit the load file (pppload) page 83 a. Uncomment the lines associated with the type of ICP in your Freeway.
Freeway User Guide The newly created files will be placed in the proper freeway\client\ op-sys\bin or freeway\client\op-sys\lib directory. d. Modify the dynamic link libraries to reside in the current working directory or in a directory specified in your “PATH” environment variable. Add C:\freeway\client\op-sys\lib to your path. or Copy the .dll files from C:\freeway\client\op-sys\lib to your bin directory or to another directory in your path. Step 5: Build CS API library file (X.25 only) page 86 a.
A: Installation at a Glance Step 6: Compile the example SRA page 87 a. Modify the path assigned to FWBASE in the freeway\envcom file. b. If you are using the GNU tool set distributed with Tornado to compile your SRA, create a custom build project using the Tornado development environment. Launch the Tornado development environment, then from the menu bar select Project, Customize..., then Add.... Enter one of the following for the name of the build target: For a Freeway 1100/1150/1200/1300: -f MakeSRA.
Freeway User Guide Step 7: Compile the Server Toolkit page 89 To build a customized Freeway image using the optional Server Toolkit product, you must have purchased and installed Tornado from Wind River Systems with the appropriate Board Support Package for your Freeway. a. Edit freeway\envcom. Modify the path assigned to FWBASE in the freeway\envcom file to match your Freeway installation directory. b.
A: Installation at a Glance Step 8: Build the loopback tests (except the example SRA) page 90 cd C:\freeway\client\test\ppp a. Edit the client TSI configuration file (pppaltcfg1), changing the default value of the Freeway server parameter, freeway_0, to the name (or Internet address) of your current Freeway server. b. If you are using AWS, BSC, or FMP on a Freeway 1100/1150/1200/1300, edit the DLI configuration file (pppaldcfg), setting the ElecInterface parameter to the correct electrical interface. c.
Freeway User Guide Step 11: Run the loopback test Freeway Loopback Test Procedures Refer to the Freeway Loopback Test Procedures to run the loopback test program for your protocol.
Appendix B Freeway Files B.1 Default Directory Structure After you have installed the Freeway files as described in Chapter 2, the files reside in a default directory structure. The freeway/include directory contains the header files your protocol needs to interface with the DLI and TSI layers. The other directories are grouped into three areas according to the types of files they contain: client-resident, server-resident, or ICP-resident software. This software is described in the following sections.
Freeway User Guide B.1.2 ICP-resident Software ICP-resident software includes any software that runs on the Freeway ICPs. This software is in the freeway/boot directory (for example, xio_2432.mem, sps_fw_2432.mem, and fmp_fw_2432.mem). Prior to June 1, 1998, these files were distributed in separate subdi- rectories under the freeway/icpcode directory.
Glossary The common Freeway terms and acronyms are defined below. BOOTP Bootstrap protocol boot server A client computer that downloads software onto Freeway (that is, “boots” Freeway). During this operation, Freeway becomes a client of the boot server. client An entity on the LAN that uses the services offered by Freeway.
Freeway User Guide Freeway Freeway refers to the entire server in terms of hardware and software. The hardware includes items such as the server processor board and the ICPs. The software includes functions such as server management, LAN and protocol services, and protocol software executing on the ICPs. For a specific product configuration, the terms Freeway 1100, Freeway 1150, Freeway 2000, Freeway 4000, and Freeway 8800 are used.
Glossary LAN protocol The hardware and software which comprise the LAN and form the basis of communications between Freeway servers and clients. An example LAN protocol is TCP/IP running over Ethernet. MIB Management information base NVRAM Non-volatile random access memory operating system Code that provides the necessary scheduling and management functions for tasks and services.
Freeway User Guide SDK Software development kit server processor The Freeway server processor board, which is capable of executing the server’s operating system and functions such as server management. server-resident Software that runs on the server processor board and processes software the data stream between the LAN and WAN connections. Server-resident software can be either supplied by Protogate or customized by the user.
Glossary task “Task” is used to differentiate between code executing on Freeway’s server processor board or the ICP, and code executing on a LAN host, which is referred to as a “process”.
Freeway User Guide 222 DC 900-1333P
Index A added_interface_addr 107 added_interface_mask 107 added_interface_type 106 Address added interface 107 foreign 109 local 109 local interface 109 Addresses Internet 34, 35 Allocation error 99 Application customization 26 Audience 15 B Boot configuration file parameters added interface address 107 added interface mask 107 added interface type 106 bus number 103 connect period 110 device name 102, 108 device type 103, 108 download script 104 foreign address 109 foreign port base 109 internal protocol
Freeway User Guide bootcfg.vme 38 Booting Freeway 122 boot parameters 148 Internet addresses 34, 35 process 94 reset action selection 153 Buffer allocation error 99 buffer.
Index Floppy disk, delete file 188 Floppy disk, display directory 181, 187 Floppy disk, display file 182 Floppy disk, maintenance 186 Floppy disk, rename file 189 foreign_address 109 foreign_port_base 109 Free memory blocks 138 Freeway concepts 26 overview 23 services 26 Freeway Inet address 151 Freeway server name 151 Freeway subnet mask 151 FTP password 151 FTP user name 151 ftstdcfg 39 ftsttcfg 39 fw162 38 fw162d 40 fw162d.sym 40 fw162l 38 fw162l.sym 39 fw162.sym 39 fw2604 39 fw2604d 40 fw2604d.
Freeway User Guide display options 125, 130, 131, 132, 133, 134 display configuration 126 display boot parameters 129 display physical configuration 127 display service provider configuration 128 display current system time 146 display log messages 126 display network statistics 141 display ICMP statistics 145 display IP statistics 144 display TCP statistics 142 display UDP statistics 143 display system information 135 display circular queue of messages 140 display task stack usage 139 display TCP summary 1
Index foreign 109 local 109 Processor number 151 Product features 25 Product support 22 Protocol software UNIX 42 VMS 59 Windows NT 79 Protogate server example 113 Q QAPI library file, build VMS 71 R rcv_buf_size 110 readme.ser 38 readme.stk 41 Reboot server 122 Reference documents 17 relnotes.ser 38 relnotes.
Freeway User Guide Technical support 22 telnet 26, 94 Time to live 110 Time, modify system 155 Time, system 146 Toolkit software UNIX 42 VMS 59 Windows NT 79 Trace functions 156 TSI configuration overview 111 TSI files, build UNIX 48 VMS 69 Windows NT 84 tsi_config_file 104 ttl 110 U UDP statistics 143 UNIX Build CS API library file 49 Build DLI files 48 Build loopback tests 53 Build TSI files 48 distribution media 37 modify boot file 45 modify load file 45 Protocol software 42 Server/client software 38 TAR
Freeway User Guide DC 900-1333P Customer Report Form We are constantly improving our products. If you have suggestions or problems you would like to report regarding the hardware, software or documentation, please complete this form and mail it to Protogate, Inc. at 12225 World Trade Drive, Suite R, San Diego, CA 92128, or fax it to (877) 473-0190. If you are reporting errors in the documentation, please enter the section and page number.
Protogate, Inc.
