Freeway ® User Guide DC 900-1333Q Protogate, Inc.
Protogate, Inc. 12225 World Trade Drive, Suite R San Diego, CA 92128 (858) 451-0865 Freeway User Guide © 2000-2013 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 Protogate, Inc. All other trademarks and trade names are the properties of their respective holders.
Contents List of Figures 11 List of Tables 15 Preface 17 1 25 Freeway Introduction 1.1 1.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 . . . . . . . 1.3 Freeway Server Configurations . 1.3.1 Standard Freeway. . . . . . 1.3.2 Custom Freeway . . . . . . 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Freeway User Guide 2.2.6 Continue the Freeway Boot. . . . . . . . . . . . 2.2.7 Connect the Freeway to the Network . . . . . . 2.2.8 Check the Network Connection to the Freeway . 2.2.8.1 Remote Login . . . . . . . . . . . . . . . . 2.2.8.2 Ping Another System from Freeway . . . . 2.2.9 Check the Protocol (serial) Connections . . . . 2.3 Freeway Server Shutdown . . . . . . . . . . . . . . . 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 4 Freeway Interactive Menu 4.1 Freeway Menu Access . . . . . . . . . . . . . . . . . 4.1.1 Local Serial Console Port . . . . . . . . . . . . 4.1.2 Local VGA Monitor and Keyboard . . . . . . . 4.1.3 Network Access . . . . . . . . . . . . . . . . . . 4.1.4 Web Browser . . . . . . . . . . . . . . . . . . . 4.2 Freeway Login Access . . . . . . . . . . . . . . . . . 4.2.1 Default Usernames and Passwords . . . . . . . 4.2.2 Access Levels . . . . . . . . . . . . . . . . . . . 4.3 Freeway Main Menu . .
Freeway User Guide 4.6 Modify Configuration . . . . . . . . . . . . . . . 4.6.1 Modify Boot Parameters . . . . . . . . . . . 4.6.2 Modify User Names . . . . . . . . . . . . . . 4.6.3 Modify System Time . . . . . . . . . . . . . 4.7 Trace Functions . . . . . . . . . . . . . . . . . . 4.8 Disk Drive Options . . . . . . . . . . . . . . . . 4.8.1 Hard Disk Copy Options . . . . . . . . . . . 4.8.1.1 Display Hard Disk Directory. . . . . . 4.8.1.2 Display Hard Disk File . . . . . . . . . 4.8.1.
Contents 5.1.5 Read Boot Parameters . . . . . . . . . 5.1.6 FreewayOS Daemon Starts. . . . . . . 5.1.7 Initialize and Download ICP Boards . 5.1.8 Enable the Ethernet connection . . . . 5.1.9 Execute Command File: rc.startsra . . 5.1.10 Execute Command File: command.sh. 5.1.11 Enable User Logins . . . . . . . . . . . 5.2 Freeway Operations . . . . . . . . . . . . . 5.2.1 Client Socket Connections . . . . . . . 5.2.2 Interactive Menu . . . . . . . . . . . . 5.2.3 SNMP . . . . . . . . . . . . . . . . . . 5.
Freeway User Guide 7 Software Updates 185 7.1 7.2 Determining Whether or Not to Install an Update . Installing Freeway Server Software Updates . . . . 7.2.1 Freeway CDROMs “X-B” (3.1-3) or later . . . 7.2.2 Freeway CDROMs “W-A” (3.1-1) or earlier . . 7.3 Installing Protocol Software Updates . . . . . . . . 7.4 Installing SRA Software Updates . . . . . . . . . . 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Glossary 217 Index 223 DC 900-1333Q 9
Freeway User Guide 10 DC 900-1333Q
List of Figures Figure 1–1: Freeway Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Figure 2–1: Sample Initial Freeway Boot Display . . . . . . . . . . . . . . . . . . . . . 35 Figure 2–2: Sample Freeway Initial Boot Menu . . . . . . . . . . . . . . . . . . . . . . 36 Figure 2–3: Example of Modifying Freeway Boot Parameters. . . . . . . . . . . . . . . 38 Figure 2–4: Freeway Console Login Prompt . . . . . . . . . . . . . . . . . . . . . . . .
Freeway User Guide Figure 4–19: Display Network Statistics Menu . . . . . . . . . . . . . . . . . . . . . . 98 Figure 4–20: Display TCP Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Figure 4–21: Display UDP Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Figure 4–22: Display IP Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Figure 4–23: Display ICMP Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . .
List of Figures Figure 4–51: Display Floppy Disk Directory . . . . . . . . . . . . . . . . . . . . . . . . 135 Figure 4–52: Delete Floppy Disk File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Figure 4–53: Rename Floppy Disk File . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Figure 4–54: BSD Shell Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Figure 5–1: Boot File Roadmap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Freeway User Guide 14 DC 900-1333Q
List of Tables Table 2–1: Installation and Initial Boot Steps . . . . . . . . . . . . . . . . . . . . . . . 33 Table 2–2: Protocol Loopback Test Programs . . . . . . . . . . . . . . . . . . . . . . . 43 Table 3–1: Summary of Client Software Installation Steps . . . . . . . . . . . . . . . . 48 Table 3–2: Program subdirectory names. . . . . . . . . . . . . . . . . . . . . . . . . . 62 Table 3–3: Client TSI Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . .
Freeway User Guide 16 DC 900-1333Q
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 3000 series models from Protogate that use the BSD operating system. If you are using an older Freeway model from Simpact with the VxWorks operating system, please refer to earlier versions of this document (Revision P and before).
Freeway User Guide • Power cord (Freeway models with dual power supplies have two power cords) • Set of keys (for hinged front panel on Freeway) • Console cable which can be connected to the Freeway serial console (each end of the cable has both a 9-pin and a 25-pin connector) • Appropriate serial cables to connect the ICPs to the data communications equipment (ICP2432B) • Two-headed loopback cable (for protocol loopback testing using internal ICP clock source) • Software distribution media on C
Preface Organization of Document Chapter 1 gives an overview of the Freeway server. Chapter 2 describes the Freeway server installation and initial boot up. Chapter 3 describes how to install the DLI/TSI library and protocol loopback programs on a client system. Chapter 4 describes the Freeway server interactive menu choices. Chapter 5 describes the details of the Freeway boot procedure and general operation. Chapter 6 describes how to customize the Freeway system configuration.
Freeway User Guide General Product Overviews • ICP2432 Technical Overview 25-000-0420 Hardware Support • • • • • • • Freeway 3112 Hardware Installation Guide DC-900-2016 Freeway 3212 Hardware Installation Guide DC-900-2017 Freeway 3412 Hardware Installation Guide DC-900-2018 Freeway 3612 Hardware Installation Guide DC-900-2019 ICP2432B Hardware Description and Theory of Operation DC-900-2006 ICP2432 Electrical Interfaces (Addendum to DC-900-2006) DC-900-1566 ICP2432B Hardware Installation
Preface • Protocol Software Toolkit Programmer Guide DC-900-2007 Protocol Support • • • • • • • • • • • ADCCP NRM Programmer Guide DC-900-1317 Asynchronous Wire Service (AWS) Programmer Guide DC-900-1324 Bit-Stream Protocol Programmer Guide DC-900-1574 BSC Programmer Guide DC-900-1340 BSCDEMO User Guide DC-900-1349 BSCTRAN Programmer Guide DC-900-1406 DDCMP Programmer Guide DC-900-1343 Military/Government Protocols Programmer Guide DC-900-1602 X.
Freeway User Guide 22 Revision Release Date Description DC 900-1333B September 1994 Added Freeway 1000 information Updated installation procedures Updated operation procedures DC 900-1333C November 1994 Updated installation procedures DC 900-1333D February 1995 Updated installation procedures DC 900-1333E March 1995 Added more detailed Freeway 1000 information DC 900-1333F May 1995 Enhanced boot parameters information, updated menus, and added loopback information for AWS and ADCCP NRM D
Preface Revision Release Date Description DC 900-1333O December 1999 Added new boot flag, 0x2000 Added snd_q_size, connect_period, linger_on, and linger_off configuration parameters to Section 3.2.1 Added sock_stream_listen and sock_stream_ connect to socket type parameter DC 900-1333P February 2002 Update document with Protogate contact information. DC 900-1333Q September 2013 Update for newer Freeway server releases. Update document to reflect the FreeBSD operating system.
Freeway User Guide 24 DC 900-1333Q
Chapter 1 Freeway Introduction This manual describes how to install and operate your Freeway server. Before starting the Freeway server, you should familiarize yourself with basic Freeway concepts as described in this introductory chapter. Then you can proceed to Chapter 2 which contains the initial installation and boot procedure. Refer to the Glossary for Freeway terminology and acronyms. 1.
Freeway User Guide The Freeway server can be any of several models depending on the size and number of PCI slots available. For example, Freeway 3112 (1U), Freeway 3212 (2U), Freeway 3412 (4U), or Freeway 3612 (6U). Figure 1–1 shows a typical Client-Freeway-ICP configuration.
1: Freeway Introduction Summary of Freeway product features: • Elimination of difficult LAN and WAN programming and systems integration by providing a powerful and consistent data link interface (DLI) • Access to communication protocols from multiple different client operating systems and hardware platforms • Support for multiple WAN communication protocols simultaneously • Support for multiple ICPs (two, four, or eight communication lines per ICP) • Creation of customized server-resident applica
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/v3-compliant SNMP agent that supports read-only SNMP access to Freeway-supported MIBs. In addition to the usual systemrelated and IP-network-related SNMP OIDs, additional OIDs which are specific to Freeway and to some ICP protocols are available. These additional SNMP OIDs are specified in these two files located on the Freeway disk drive: /usr/local/freeway/include/RS-232-MIB.
Freeway User Guide 1.3.2 Custom Freeway A Freeway configuration is considered “custom” when it contains software (SRAs) loaded on the Freeway server in addition to the Freeway OS. On a custom Freeway, the WAN lines are normally accessed by the SRA and the client accesses the SRA by means other than the DLI API.
Chapter 2 Freeway Installation and Initial Boot This chapter describes how to install and boot the Freeway server for the first time. You must have installed the Freeway hardware as described in the appropriate Freeway hardware installation guide. 2.1 Freeway Server Software and CDROMs Freeway server and protocol software is almost always pre-installed at the Protogate factory on the Freeway’s flash or hard disk drive. Also, the Freeway is configured to boot itself from its hard or flash drive.
Freeway User Guide • If you want to run a specific protocol loopback program on your client system, you can obtain the source code for that loopback program from the CDROM for that specific protocol. See chapter Chapter 3 for details. • If you need the Freeway to boot over the LAN from a boot server on the network, refer to Chapter 8 for instructions on how to configure a system to act as a “boot server” for the Freeway.
2: Freeway Installation and Initial Boot 2.2.1 Initial Boot Summary Table 2–1 summarizes the steps required when booting a Freeway for the first time. These steps are described in detail later in this section. Table 2–1: Installation and Initial Boot Steps Steps Reference Section(s) 1. Connect a console device to the Freeway. Section 2.2.2 on page 33 2. Power up the Freeway. Section 2.2.3 on page 35 3. Stop the Freeway Boot. Section 2.2.4 on page 36 4. Change the Freeway IP Address. Section 2.2.
Freeway User Guide Insert one end of the console cable in the 9-pin connector on the rear of the Freeway. Insert the other end of the console cable into a device that can be used as a serial ASCII display terminal. The following are some examples of serial display devices. • Windows-based PC or Laptop: You can use a Windows-based PC or laptop as a console by connecting the console cable to one of the serial ports (COM1, COM2, etc.
2: Freeway Installation and Initial Boot ports on the Freeway are normally disabled after boot-up. The Freeway Console does not require a mouse device. Caution Never connect or disconnect the PS2 keyboard while the Freeway server is powered on. 2.2.3 Power up the Freeway In order to power up the Freeway server, the power switches on the power supply (or both power supplies for redundant power systems) must be turned on. Then turn on the main power switch at the front of the unit.
Freeway User Guide 2.2.4 Stop the Freeway Auto-Boot While the Freeway is booting up, it will display several lines of information from the BSD operating system. At one point, the boot process will reach the actual Freeway boot. At this point the boot sequence gives you a chance to interrupt the boot process in order to display or change the boot parameters. You must hit the enter (return) at this time in order to stop the boot process.
2: Freeway Installation and Initial Boot 2.2.5 Display and modify the Boot Parameters Display the Freeway’s current boot parameter settings by entering 2 from the initial boot menu, or entering 2, 3, then 4 from the Freeway Main Menu. Unless you have made prior arrangements with Protogate before your Freeway was shipped, you will at least have to change the IP address (and possibly the subnet mask) of the Freeway so that it can appear as a device on your network.
Freeway User Guide Select: 3 Freeway System Boot Parameters -----------------------------Enter '.
2: Freeway Installation and Initial Boot 2.2.6 Continue the Freeway Boot After you have set the correct IP address, hit return to get back to the initial boot main menu and select 1 to boot the Freeway box. From the Freeway menus, hit 1 and return repeatedly until you get to the Shutdown Options. Then hit 2 to reboot the system. As the Freeway boots, it will display several informational messages on the console and then eventually display the login prompt shown in Figure 2–4.
Freeway User Guide 2.2.7 Connect the Freeway to the Network Using an RJ-45 cable, connect the Freeway to your network by plugging the connector into one of the RJ-45 jacks at the rear of the Freeway. Although both network connectors can be active on the Freeway, only one of the connectors are configured to run during single-Ethernet operations. That Ethernet connector is marked as “primary”. The connector that is not used is marked as “secondary”.
2: Freeway Installation and Initial Boot 2.2.8.2 Ping Another System from Freeway You can also check your network connection by pinging another system from the Freeway. To do this, log in to Freeway from the local console with the username (freeway) and password (password): Freeway User Login: freeway Password: password • At the main menu select Display Options (2) • At the Display Options menu select Display Network Information (4).
Freeway User Guide 2.2.9 Check the Protocol (serial) Connections All Protogate protocols and toolkits are supplied with loopback programs that test the serial connections on the ICP boards. These programs can be run from a client system on your network, however, Protogate normally installs executable versions of these programs on the Freeway disk drive as well. This section describes how to run the protocol loopback programs from the Freeway console.
2: Freeway Installation and Initial Boot Note If you are having problems logging in remotely as a “root” user, refer to Section B.5 on page 215 for instructions on how to log in using the “freeway” account. 3. Change to the directory where the loopback program executable files are kept.
Freeway User Guide Answer the questions asked by the loopback program. Make sure to choose “internal clocking” if you are using a two-headed loopback cable. The loopback program transfers test data from one port to the other for the amount of time you specify. When the program completes, it will display the statistics of the data transfer. Step 4: Exit the FreeBSD Shell After the loopback program completes, you can exit the FreeBSD Unix Shell by typing exit at the prompt.
2: Freeway Installation and Initial Boot If you have a custom Freeway server configuration, you must power off the unit in a controlled manner using a BSD shell command. Otherwise, you risk having file corruption in the read-write partition of the disk drive if you just turn the power off with the switch. To perform a controlled system shutdown, use the following steps: 1. Log into the Freeway from either the local or remote console. Freeway User Login: root Password: setup 2.
Freeway User Guide 46 DC 900-1333Q
Chapter 3 Client Software Installation This chapter describes how to install the DLI API software library and protocol loopback software on a client system. This particular client system is a computer on your network that you will use to develop an application program to communicate with the Freeway server and the protocols loaded on the ICP boards. This client system must have the proper development environment (C compiler and linker).
Freeway User Guide 3.2 Client Software Installation Summary The client software installation steps described in this chapter are summarized in Table 3–1. Table 3–1: Summary of Client Software Installation Steps Steps Reference Section(s) 1. Select a computer on the same network as the Freeway Section 3.3 on page 48 that has development tools (C compiler and linker). You will use this computer for client software development and testing with the Freeway. 2.
3: Client Software Installation 3.3.1 Prepare the System for Installation Make sure you have enough disk space for the software installations. Freeway client software is approximately 25 MB maximum. Protocol software (loopback program) installations are much smaller. The software installations copy files from the CDROM to the hard drive on your client system. All the files are contained within the “Freeway directory tree” where “freeway” is the top level directory in the tree.
Freeway User Guide # This is the master Internet address file for XYZ Corporation. # If you need an address, check here first to make sure it is not # being used. If it is not, add the address, the system name for the # device, and the owner. You can then export this file to your device # if it is appropriate. # # # ************************************************************* # TCP/IP HOST TABLE # ************************************************************* # # 127.0.0.1 loopback --- do not remove.
3: Client Software Installation Windows systems: The IP addresses and system names of computers on the network are maintained in a hosts file that is similar to the file used in the UNIX example above. On Windows, the hosts file is normally located in the following directory path: C:\WINDOWS\system32\drivers\etc\ Once you locate the hosts file, open it for editing and add the Freeway server names and addresses. Refer to the UNIX example above.
Freeway User Guide 3.4 Installing the Freeway Software onto a Client Computer This section describes how to install the Freeway software (which includes the DLI/TSI library) from the Freeway distribution CDROM onto a client computer. You need to install this software on your system if you plan to use this system to compile and run the protocol loopback programs or if you plan to develop your own client program on this system.
3: Client Software Installation The Freeway server and DLI/TSI documentation consist User Guides and Reference Manuals in PDF format. These documents are also available on Protogate’s web site (www.protogate.com). Caution Note Remember that installing new software overwrites the previous software. It is recommended that you use the default directory structure. If you install the software in a non-default directory, you must later modify certain files if you plan to use this client as a boot server. 3.
Freeway User Guide Step 4: The Freeway Software tar file (PF-100-0136.tar) is located in the directory /parts/PF-100/ on the CDROM. You may either copy this file to your local directory (/usr/local/) or leave it on the CDROM and extract the files from there. Below is an example of a command to copy the tar file to your local directory: cp /dev/cdrom/parts/PF-100/PF-100-0136.tar . Step 5: Use the tar x command to retrieve the Freeway software files from the tar file.
3: Client Software Installation installing the server/client software on VMS systems. Use the following procedure to install the DLI/TSI software from the distribution media onto your VMS computer. Note Step 1: If you can not find the VMS saveset file on your distribution CDROM, please contact Protogate for assistance. On the client system (previously configured as described in Section 3.3), log in to an account with SYSTEM privileges.
Freeway User Guide Note Do not use VMSINSTAL to open the backup saveset file included in the Freeway distribution CDROM. Use the following command if you want the Freeway directory tree installed as a root directory on your disk: $ backup/new serfwo025.bck/save [000000...] Use the following command if you want to install the Freeway directory tree as a subdirectory of an already existing directory (in this example [user.protogate]): $ backup/new serfwo025.bck/save [user.protogate...
3: Client Software Installation Step 2: Click on the Freeway software product name, then right-click on the zip file and select “SaveTarget As” and save the file into a directory where you can find the file later. Close or minimize the browser window. Step 3: Go to the directory where you saved the zip file. Right-click on the zip file and select “Extract All...”. Browse to the location where you want the Freeway directory tree to start (such as C:\) and click on the “Extract” button.
Freeway User Guide 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 /usr/local/freeway/lib directory, enter one of the following commands depending on the system you are using. cd /usr/local/freeway/lib make -f Makefile.AIX all make -f Makefile.LNX all make -f Makefile.HPUX all make -f Makefile.SGI all make -f Makefile.
3: Client Software Installation 2. From your op-sys directory, create the bin and lib directories if they don’t already exist. set def [.op-sys] Scrunched step 2 and cd op-sys lines above to get bottom list on this page. create/dir [.bin] create/dir [.lib] Step 2: Run the make file From the [freeway/lib] directory, enter one of the following commands depending on the TCP/IP package you are using. set def [freeway.
Freeway User Guide cd C:\freeway\client mkdir int_nt 2. From the int_nt directory, create the bin and lib directories if they don’t already exist. cd int_nt mkdir bin mkdir lib Step 3: Run the make file From the freeway\lib directory, enter the following command. The newly created files will be placed in the proper freeway\client\int_nt\bin or freeway\client\int_nt\ lib directory.
3: Client Software Installation Protocol software products are distributed on CDROM separate from the Freeway Client Software. The number of protocol CDROMs you need to install depend on what protocols you have purchased with your Freeway server. 3.6.1 What the Protocol Software CDROM Includes Individual protocol software distribution CDROMs may vary in content depending on the type of protocol.
Freeway User Guide Table 3–2: Program subdirectory names Program Subdirectory Name (name) AUTODIN (Mode I) loopback autodin AUTODIN demo program adndemo AWS loopback aws Milstar loopback mst STD1300 loopback s13 DDCMP loopback ddcmp VOX loopback vox VOX demo program voxdemo ADCCP NRM loopback nrm Protocol Toolkit sps1 STD1200B loopback s12 Military/Government mil X.
3: Client Software Installation the protocol distribution or if you just need to extract a few files from the distribution, you can do so using this directory. Use the following procedure to install the Protocol software from the distribution media onto your UNIX computer. Step 1: On the client system (previously configured as described in Section 3.3), log in to a root or other privileged account. Step 2: Change to the directory that is just above your installed freeway directory tree.
Freeway User Guide tar xvf PF-100-xxxx.tar tar xvf /dev/cdrom/parts/PF-100/PF-100-xxxx.tar Note that xxxx represents the four-digit number of the filename you find in the CDROM directory. The tar command creates additional subdirectories within the directory /usr/local/freeway (or whatever your specific Freeway directory tree is) and copies the software into them from the distribution media. Step 6: Unmount the CDROM.
3: Client Software Installation Step 3: Insert the Protocol Software distribution CDROM into the appropriate drive and mount the CDROM. Below is an example of the mount command (the device name on your system might be different): $ mount dka400: Step 4: Locate the saveset file for your protocol. Depending on the date of your pro- tocol release, the saveset may be located in a subdirectory under [parts.PF-200] on the CDROM, or under a different location.
Freeway User Guide Step 6: Dismount the CDROM. Below is an example of the dismount command (the device name on your system might be different): $ dismount dka400: 3.6.4 Installing Protocol Software on a Windows system Insert the CD into the drive. If your Windows computer is set up for auto-run of CDROMs and you have a browser enabled, the installation page will come up automatically.
3: Client Software Installation (Where name is one of the protocol names in Table 3–2 on page 62.) When using FTP to copy the protocol software, use BINARY transfer for the protocol (*.mem) files, and ASCII transfer for the other files. 3.7 Build the Loopback Test Programs All protocols are supplied with one or more loopback test programs. These programs are designed to perform a complete data loop test of your Freeway and ICP.
Freeway User Guide 3.7.1 Build the Loopback Programs on UNIX systems Step 1: Point the TSI configuration files to your Freeway server For all protocols and programs (except certain demo programs1), you must point the transport subsystem interface (TSI) configuration files in freeway/client/test/name to your Freeway server’s name or IP address. The TSI configuration file names for each protocol are listed in Table 3–3. The protocol subdirectories (name) are listed back in Table 3–2 on page 62.
3: Client Software Installation make -f makefile.sol all (for a Solaris system) make -f makefile.sun all (for a SunOS system) The newly created files will be placed in the freeway/client/op-sys/bin directory. For a description of the Freeway files you have just installed onto your client system, refer to Appendix B. 3.7.
Freeway User Guide Step 2: Run the make file From the [freeway.client.test.name] directory, enter one of the following commands depending on the TCP/IP software you are using. @MAKEVMS "" UCX (for standard TCP/IP) @MAKEVMS "" MULTINET (for VMS with Multinet) @MAKEVMS "" TCPWARE (for VMS with TCPware) The newly created files will be placed in the [freeway.client.op_sys.bin] directory. For a description of the Freeway files you have just installed onto your client system, refer to Appendix B. 3.7.
3: Client Software Installation 2. Edit the TSI configuration file and change the server parameter freeway_0 to the name or IP address of your current Freeway. A client TSI configuration file might reference the server parameter more than once, and must be changed at each occurrence. Step 2: Run the make file From the \freeway\client\test\name directory, enter the following command: nmake -f makefile.int all The newly created files will be placed in the \freeway\client\int_nt\bin directory.
Freeway User Guide The string name represents the short name of the protocol in most cases and alp stands for “asynchronous loopback program”. Once you start the loopback program it will prompt you for some information before it starts sending data. The loopback program is designed to transfer test data from an odd numbered ICP port to the adjacent even-numbered ICP port (example: ports 0 and 1).
Chapter 4 Freeway Interactive Menu The user interacts with Freeway using a menu-driven interface called the Freeway Interactive Menu. This interface is composed of a series of menus that provide access to statistics, error reports, configuration, and control of server operation. This chapter describes all the choices available using the Freeway Interactive Menu. 4.1 Freeway Menu Access The Freeway Interactive Menu is available for use once the Freeway system has completely booted up.
Freeway User Guide Connect the other end of the console cable to any ANSI or VT200 compatible terminal. You may also use one of the serial COM ports on a PC or laptop as long as you have a terminal emulation program (such as HyperTerminal) available on the system. If you are using a PC with HyperTerminal, use the following settings on the “Port Settings” tab: Bits per second:9600 Data bits: 8 Parity: None Stop bits: 1 Flow control: None Once connected, hit the Enter key to get to the login prompt. 4.1.
4: Freeway Interactive Menu 4.1.3 Network Access If the Freeway IP address and subnet mask are set up correctly, you can access the Freeway Interactive Menu over the network by means of Telnet, rlogin, or ssh (secure shell) from a computer system located on the same subnet. If you want to access the Freeway from a system on a different subnet, you must insure that the gateway router address is set up correctly in the Freeway boot parameters.
Freeway User Guide 4.2 Freeway Login Access You must provide a username and password in order to access the Freeway Interactive Menu. Once you make a connection to the Freeway via local or remote console, the following login prompt appears: Freeway User Login: At this point you can log in to the Freeway using the Freeway user name (default is freeway) and password (default is password): Freeway User Login: freeway Password: password The password is not actually displayed on the screen.
4: Freeway Interactive Menu Table 4–1: Freeway Default Usernames and Passwords Username Password Access Level root setup root shell setup root user PicoBSD user freeway password user protogate password user simpact password user The “shell” and “user” accounts are meant as fail-safe entry points which can be used to login even if the Freeway software itself fails to start; they take the user to a plain command shell rather than into the Freeway menus.
Freeway User Guide dures. You must log in as root in order to do many of the higher-level functions in the FreeBSD shell. Users at the user level are allowed to do all functions related to Freeway operations except add and delete user accounts. Also, some BSD functions are restricted. Users at the display only level have access to the display menus and trace functions. Users at this level are not allowed to reboot the Freeway.
4: Freeway Interactive Menu 4.3 Freeway Main Menu After you log in as described in Section 4.1.1 on page 73, the Freeway Main Menu is displayed as shown in Figure 4–1. Items 1 through 7 have their own menus as described in the following sections. If you logout from the Freeway 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. VI-200-3290: FWSER 3.
Freeway User Guide 4.4 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.4.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: Freeway Interactive Menu 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 (refer to Chapter 5 for a more detailed description of the boot process): Step 1: Determine the Boot Parameters Freeway must know its boot parameters in order to download files from its disk drive or a boot server. Freeway obtains the boot parameters from its flash or hard drive.
Freeway User Guide 4.5 Display Options To access the Display Options menu as shown in Figure 4–3, enter ‘2’ at the Freeway Interactive Menu.
4: Freeway Interactive Menu 4.5.1 Display Log Messages To retrieve and display log messages stored on the message queue, enter ‘2’ at the Display Options menu. 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 . Note Displaying the log messages also purges them from this menu selection.
Freeway User Guide 4.5.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 3100. 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 6.
4: Freeway Interactive Menu 4.5.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 3100. Freeway maintains information on each service provider installed in the system.
Freeway User Guide 4.5.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 of Freeway boot parameters.
4: Freeway Interactive Menu 4.5.3 Display Network Information To access the Display Network Information menu as shown in Figure 4–8, enter ‘4’ at the Display Options menu.
Freeway User Guide 4.5.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 3100 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.6.1 on page 108.
4: Freeway Interactive Menu 4.5.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 ---------------gw2 (192.168.1.2) at 00:e0:81:01:53:00 on em0 [ethernet] fwy29 (192.168.1.
Freeway User Guide 4.5.3.3 Display IP Network Routing Tables To display the IP network routes as shown in Figure 4–11, enter ‘4’ at the Display Network Information menu. IP Network Routing Tables ------------------------Routing tables Internet: Destination default localhost 192.168.
4: Freeway Interactive Menu 4.5.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.1.201 Attempting to ping "192.168.1.201" ... PING 192.168.1.201 (192.168.1.201): 56 data bytes --- 192.168.1.
Freeway User Guide 4.5.4 Display System Information To access the Display System Information menu as shown in Figure 4–13, enter ‘5’ at the Display Options menu.
4: Freeway Interactive Menu 4.5.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 ----------MAKEDEV acd0a acd0c . . . [most devices omitted for brevity] . .
Freeway User Guide 4.5.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. TCB Summary ----------USER PID %CPU %MEM VSZ RSS TT STAT STARTED root 0 0.0 0.0 0 0 ?? DLs 8:44PM freeway 1913 0.0 0.4 628 440 d0 S+ 9:02PM freeway 1898 0.0 3.3 8452 3800 d0 S+ 8:44PM root 1897 0.0 0.6 960 708 v2 Is+ 8:44PM root 1896 0.0 0.6 960 708 v1 Is+ 8:44PM root 1895 0.0 0.6 960 708 v0 Is+ 8:44PM root 1894 0.0 0.
4: Freeway Interactive Menu 4.5.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. Free Memory Blocks (each block is 4096 bytes) --------------------------------------------vm.stats.vm.
Freeway User Guide 4.5.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. Task Stack Usage ---------------PID TT STAT 1898 d0 S+ 1917 d0 S+ TIME COMMAND 0:00.05 -bsdfwysh (bsdfwysh) 0:00.
4: Freeway Interactive Menu 4.5.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.
Freeway User Guide 4.5.5 Display Network Statistics To access the Display Network Statistics menu as shown in Figure 4–19, enter ‘6’ at the Display Options menu.
4: Freeway Interactive Menu 4.5.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.
Freeway User Guide 4.5.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.
4: Freeway Interactive Menu 4.5.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.
Freeway User Guide 4.5.5.4 Display ICMP Statistics To display the ICMP statistics as shown in Figure 4–23, enter ‘5’ at the Display Network Statistics menu.
4: Freeway Interactive Menu 4.5.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 ----root root shell freeway display Press RETURN to continue Figure 4–24: Display User Names 4.5.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.
Freeway User Guide 4.6 Modify Configuration To access the Freeway Modify Configuration menu as shown in Figure 4–26, enter ‘3’ at the Freeway Interactive Menu.
4: Freeway Interactive Menu 4.6.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–2 describes each parameter.
Freeway User Guide 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 0x1000 freeway2 192.168.
4: Freeway Interactive Menu Table 4–2: Freeway System Boot Parameter Descriptions Boot Parameter Boot Device Description Freeway 31xx/32xx/34xx/36xx: • to boot from the internal IDE or SATA disk drive, set the boot device to ide=0,0 • to boot over Ethernet from the boot server using the on-board NIC, set the boot device to fei 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
Freeway User Guide Table 4–2: Freeway System Boot Parameter Descriptions (Cont’d) Boot Parameter Description Freeway Server Name Enter the system name assigned by the system administrator for this Freeway. Freeway Inet Address Enter the Internet address assigned by the system administrator for this Freeway in decimal dot notation (for example, 192.168.1.45). Freeway Subnet Mask If your Freeway is located on a subnet, enter the subnet mask in hexadecimal format (for example, ffffff00).
4: Freeway Interactive Menu Table 4–3: Flags for Reset Action Flags Parameter Value Reset Action 0x0000 (default) Upon system reset, wait 7 seconds before autobooting. 0x0004 Upon system reset, display the Freeway Boot System Main Menu. Do not autoboot. 0x0008 Upon system reset, wait 2 seconds before autobooting. 0x1000 Display version numbers of .mem files downloaded to an ICP during boot.
Freeway User Guide 4.6.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 must be logged in as a “root” level user in order to modify user names. If you are not logged in as a “root” level user, then you are only allowed to change the password on your login account.
4: Freeway Interactive Menu Caution The Freeway user name and password are used to access the Freeway Interactive Menu. They are not to be confused with the FTP user name and FTP password (which have defaults of freeway and password). The latter are Freeway system boot parameters which are used between Freeway and the boot server during system boot (see Section 4.6.1 on page 105). 4.6.
Freeway User Guide 4.7 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–30, enter ‘4’ at the Freeway Interactive Menu. Trace Functions --------------1) Return to Interactive Menu 2) Turn MSGMUX Trace On 3) Turn MSGMUX Trace Off 4) Process Trace Data Select: Figure 4–30: Trace Functions Menu Enter ‘2’ to turn trace on.
4: Freeway Interactive Menu • (1) TSI: TSI header and TSI data area • (2) DLI: TSI header, TSI data area, DLI header, and DLI data area Note From most tracing purposes, you should select trace level (2) DLI because it gives you more protocol specific information. You are then prompted to enter a file name and press . A ‘snapshot’ of the current trace data is then written to the specified file located in the /tmp directory of the Freeway local disk.
Freeway User Guide see the Display Boot Parameters screen (page 86). To capture the trace data to a file on the boot server, the user defined in FTP User Name in the System Boot Parameters menu (page 106) must have write privileges in the system boot directory on the boot server.
4: Freeway Interactive Menu 4.8 Disk Drive Options To access the Disk Drive Options menu as shown in Figure 4–32, enter ‘5’ at the Freeway Interactive Menu.
Freeway User Guide 4.8.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: Freeway Interactive Menu 4.8.1.1 Display Hard Disk Directory To display the hard disk directory, enter ‘2’ at the Hard Disk Copy Options menu. When using the normal Freeway console, this menu selection will display only the root directory of the login account as shown in Figure 4–34. Display Disk Devices -------------------total 1 drwx------ 2 root wheel 512 Jun 21 02:31 .
Freeway User Guide 5. - Hard Disk Copy Options 1. Return to Disk Drive Options Menu Display Directory 2. Directory: /usr/local/freeway/client/test/sps Display File 3. Filename: 4. Filename: Copy File to Hard Disk 5. Filename: Copy File to Floppy Disk 6.
4: Freeway Interactive Menu 4.8.1.2 Display Hard Disk File To display a hard disk file as shown in Figure 4–36, 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. You may enter the entire path name of the file to be displayed. Note All Freeway file names are case sensitive.
Freeway User Guide 4.8.1.3 Copy Boot Server File to Hard Disk This command will copy a file from the remote boot server’s Freeway boot directory to the Freeway hard disk. To copy a boot server file to the hard disk as shown in Figure 4–37, enter ‘4’ at the Hard Disk Copy Options menu. If you change your mind Enter file name to copy.
4: Freeway Interactive Menu 4.8.1.4 Copy Hard Disk File to Floppy Disk To copy a hard disk file to the floppy disk as shown in Figure 4–38, 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 uses the BSD Unix DOS file system long name support feature. This feature allows the use of file names longer than MS-DOS’s 8.3 convention.
Freeway User Guide 4.8.1.5 Copy Floppy File to Hard Disk To copy a floppy file to the hard disk as shown in Figure 4–39, 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 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: Freeway Interactive Menu 4.8.2 Hard Disk Maintenance Options To access the Hard Disk Maintenance Options menu as shown in Figure 4–40, enter ‘3’ at the Disk Drive Options menu.
Freeway User Guide 4.8.2.1 Display Hard Disk Directory To display the hard disk directory, enter ‘2’ at the Hard Disk Maintenance Options menu. When using the normal Freeway console, this menu selection will display only the root directory of the login account as shown in Figure 4–41. Note File names for the Freeway hard drive are case sensitive. Display Disk Devices -------------------total 1 drwx------ 2 root wheel 512 Jun 21 02:31 .
4: Freeway Interactive Menu 4.8.2.2 Build Hard Disk from Boot Server If the Freeway is configured to boot from a remote boot server, this menu option copies all the files from the boot directory on the boot server to the permanent boot directory on the Freeway disk drive (/usr/local/freeway/boot.src). This is usually done in preparation for configuring the Freeway to boot from its own disk drive.
Freeway User Guide 4.8.2.3 Delete Hard Disk File To delete a hard disk file as shown in Figure 4–42, 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. Always include the full path name when deleting a file. Select: 4 Enter file name to remove: /tmp/boot/bootcfg.prev File /tmp/boot/bootcfg.prev is removed.
4: Freeway Interactive Menu 4.8.2.4 Rename Hard Disk File To rename a hard disk file as shown in Figure 4–43, 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. Always include the full path name in the source and destination when renaming a file. Select: 5 Enter file name to rename: /tmp/boot/swtcfg Enter new file name: /tmp/boot/swtcfg.
Freeway User Guide 4.8.3 Floppy Disk Copy Options To access the Floppy Disk Copy Options menu as shown in Figure 4–44, enter ‘4’ at the Disk Drive Options menu. Note Floppy Disk Copy options will only work on Freeway servers that are equipped with a physical floppy disk drive.
4: Freeway Interactive Menu 4.8.3.1 Display Floppy Disk Directory To display the floppy disk directory as shown in Figure 4–45, enter ‘2’ at the Floppy Disk Copy Options menu. Select: 2 Display Disk Devices -------------------total 957 -rwxr-xr-x 1 root wheel -rwxr-xr-x 1 root wheel -rwxr-xr-x 1 root wheel -rwxr-xr-x 1 root wheel -rwxr-xr-x 1 root wheel (END) 498988 470480 6955 586 1350 Jul Jul Oct Jul Jul 12 2005 b32_2432b.mem 12 2005 b37_2432b.mem 22 10:38 bootcfg 31 11:37 bootparm.
Freeway User Guide 4.8.3.2 Display Floppy Disk File To display a floppy disk file as shown in Figure 4–46, 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. Select: 3 Enter file name to display: bootcfg Attempting to list contents of file: "bootcfg" ... #----------------------------------------------------------------------# # This is the Freeway server boot file for PCI bus ICP2432's.
4: Freeway Interactive Menu 4.8.3.3 Copy Boot Server File to Floppy Disk To copy a boot server file to the floppy disk as shown in Figure 4–47, 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. Enter file name to copy.
Freeway User Guide 4.8.3.4 Copy Floppy Disk File to Hard Disk To copy a floppy disk file to the hard disk as shown in Figure 4–48, 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. .
4: Freeway Interactive Menu 4.8.3.5 Copy Hard Disk File to Floppy Disk To copy a hard disk file to the floppy disk as shown in Figure 4–49, 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. Always include the full path name in the file to be copied.
Freeway User Guide 4.8.4 Floppy Disk Maintenance Options To access the Floppy Disk Maintenance Options menu as shown in Figure 4–50, enter ‘5’ at the Disk Drive Options menu.
4: Freeway Interactive Menu 4.8.4.1 Display Floppy Disk Directory To display the floppy disk directory as shown in Figure 4–51, 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.8.4.2 Delete Floppy Disk File To delete a floppy disk file as shown in Figure 4–52, 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: Freeway Interactive Menu 4.8.4.3 Rename Floppy Disk File To rename a floppy disk file as shown in Figure 4–53, 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.
Freeway User Guide 4.9 Run BSD Shell To access the BSD shell as shown in Figure 4–54, enter ‘6’ at the Freeway Interactive Menu. The BSD shell allows you to interactively run BSD Unix commands on the Freeway server. Access to the BSD shell provides a powerful interface that could cause the Freeway to crash if used improperly. Therefore, you should use caution when entering shell commands as a “root” or “shell” user.
4: Freeway Interactive Menu VI-200-3290: FWSER 3.
Freeway User Guide 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 a remote session, you return to your system prompt.
Chapter 5 Freeway Boot and Operation This chapter describes the Freeway server boot process in detail and also provides some information on Freeway operation. Note Additional information about Freeway operation can be found on the Protogate web site at www.protogate.com/faq.html. 5.1 Freeway Boot Procedure When the Freeway server is powered up, it follows a certain boot-up procedure that brings it to full operational status.
Freeway User Guide nvram.txt fwybsd (boot parameters) bootcfg ppploadb (icp0) ppploadb osp_2432b.mem ppp_2432b.mem osp_2432b.mem (icp1) ppp_2432b.mem muxcfg drwg 4025 ppp = protocol designation Figure 5–1: Boot File Roadmap Table 5–1 outlines the steps of the boot process in the order that the Freeway executes them. These steps are defined in sections below. Table 5–1: Freeway Boot Sequence Boot Stages Reference Section(s) 1. Power turned on Section 5.1.1 on page 143 2.
5: Freeway Boot and Operation 5.1.1 Freeway Power-up The Freeway CPU board has a built-in BIOS similar to most PC systems. The Freeway BIOS settings are pre-configured at the Protogate factory. If you have a VGA monitor and keyboard connected to the Freeway at power-up, you can access the BIOS by typing the DEL key right after power-up. Protogate does not recommend changing any of the Freeway BIOS settings unless you have a special requirement (such as enabling the USB ports). 5.1.
Freeway User Guide 5.1.4 Check for Update: bootparm.txt You may change the boot parameters stored in nvram.txt at boot time by creating a text file called bootparm.txt that the Freeway can read during this step of the boot process. To do this, create an ordinary CDROM (non-bootable) containing an ASCII text file named bootparm.txt in the root directory. That file should contain lines which specify any changes you want to make in the boot parameters. The lines must be in the format as shown in Figure 5–2.
5: Freeway Boot and Operation whitespace character are taken as comments and have no effect on any boot parameters. Boot parameters without a corresponding line in the bootparm.txt file will remain unchanged. Below are a few examples of why you would want to use the bootparm.txt file: • If you maintain two (or more) alternate boot configuration files (example: bootcfg1 and bootcfg2) on the Freeway disk drive, then you can use bootparm.
Freeway User Guide Depending on the value of the boot_device parameter, the Freeway determines whether to continue to boot from the internal disk drive, or boot over the network from a boot server. For more information about booting the Freeway over the network, refer to Chapter 8. 5.1.6 FreewayOS Daemon Starts The FreewayOS daemon (fwybsd) is started. This file was specified in the boot parameters as System_Boot_File_Name. 5.1.
5: Freeway Boot and Operation • Configure and enable the secondary Ethernet port, or set up the secondary Ethernet port as a fail-over for the primary port • Set up the Freeway to access an NTP server • Set up a network firewall • Start a Server Resident Application (SRA) • Start the system log (syslog) utility • Use cron to run a shell script at timed intervals • Start the Freeway web server Refer to Chapter 6 for information on customizing the Freeway using the rc.startsra file. 5.1.
Freeway User Guide 5.1.11 Enable User Logins At the end of the boot sequence, Freeway user logins are enabled. If a serial or VGA console is attached, the “Login:” prompt will be displayed on the screen. At this point users may login to access the Freeway interactive menus. 5.2 Freeway Operations Once a standard Freeway with boots up, it becomes a listening device on the network. That is, it does not attempt to connect to other devices on the network.
5: Freeway Boot and Operation 5.2.3 SNMP SNMP access is available on the Freeway, and is enabled by default. There are also a full set of client SNMP tools, such as snmpwalk. The MIBs which are specific to the Freeway are described in the freeway/include/ directory on your Freeway software CDROM, in the files SIMPACTFREEWAY-MIB.txt and RS-232-MIB.txt . Those files are also installed in the Freeway disk drive in the directory /usr/local/share/snmp/mibs/ .
Freeway User Guide snmpwalk snmpwalk snmpwalk snmpwalk snmpwalk snmpwalk snmpwalk -v -v -v -v -v -v -v 2c 2c 2c 2c 2c 2c 2c -c -c -c -c -c -c -c public public public public public public public localhost localhost localhost localhost localhost localhost localhost rs232SyncPortMode rs232SyncPortIdlePattern rs232SyncPortMinFlags rs232InSigState rs232InSigChanges rs232OutSigState rs232OutSigChanges From another machine (not a Freeway), commands like these should work, if "fwy_ip_addr" is the IP address
5: Freeway Boot and Operation 5.3 Maintenance Tools The following sections list some helpful tools available on the Freeway. 5.3.
Freeway User Guide MSGMUX trace is accessible through the Freeway interactive menu. To turn tracing on, login to the Freeway and select: "4) Trace Functions (Trace Disabled)", then "2) Turn MSGMUX Trace On" Then start your client program and run your test. While the test is running, trace data is stored in a buffer in Freeway memory. The trace uses a circular buffer, and new data coming in will eventually overwrite the oldest data.
5: Freeway Boot and Operation ------------------------------------------------------------------------------@@@@@ Actual Data offset 291 000000: 00 00 00 00 00 000016: 00 32 00 00 00 000032: 14 ea 1d 08 20 000048: 00 17 08 05 40 000064: 00 00 00 00 04 000080: bd 25 a4 @@@@@ Decoding begins Size = 83 00 00 00 00 04 00 00 2c 00 00 00 00 00 06 00 00 00 00 00 00 0c 10 00 00 00 00 c1 06 00 00 14 be 00 00 00 00 6c 00 88 a5 02 a1 00 13 68 00 1c 00 00 b5 <====(READ 83 bytes)Conn 2: Mon Aug 26 00:10:19.
Freeway User Guide 5.3.3 ICP Reset Utility The ICP reset utility is used to reset and download an individual ICP board without affecting the other ICP boards on the Freeway. The ICP reset utility is located in the /tmp/boot directory on the Freeway. To use the utility, login to the Freeway as root/setup and choose “6) Run FreeBSD Shell” from the main menu.
5: Freeway Boot and Operation <@@> SA-100-0190: VOX 1.3-2 Protogate Voice Data (VOX) Protocol 04-Sep-13 for the ICP2432B (PCI) comm board Free buffer pool = 401d7000 to 42000000 Created 26007 buffers @ 1024 (+ 192 overhead) LCT addresses for all links (LCT size = 400 hex): LCT0=4012fe7c LCT1=4013027c LCT2=4013067c VOX time stamp: DAY0001 - 07:17:51.
Freeway User Guide 156 DC 900-1333Q
Chapter 6 Customizing the System Configuration This chapter describes how to customize the Freeway system configuration by modifying and/or adding system configuration files. Note Additional information on customizing the Freeway system can be found on the Protogate web site at www.protogate.com/faq.html. The majority of the Freeway system configuration information is contained in three configuration files: • bootcfg • muxcfg • rc.
Freeway User Guide • Virtual devices within the Freeway server, such as the ICP_IPs. Freeway uses this information to define the characteristics of IP data streams. • Services or protocols that run on the physical or virtual devices. Freeway uses this information to download the appropriate software to these devices during the boot process. • Server-wide parameters to be used by the Freeway system service provider to configure Freeway at startup.
6: Customizing the System Configuration 6.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 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, AWS and X.
Freeway User Guide For example, if you get an error similar to the following when you boot Freeway, you might edit the existing muxcfg file to set maxbuffers = 256. (The value you require for maxbuffers might be different.) 0x38ddf8 (msg_mux): memPartAlloc: block too big 1318912 in partition 0x1d3708. 0x38ddf8 (msg_mux): ERROR: tInit: tserrno = -10 • If you are using ICP_IP virtual devices, you must modify the boot configuration file as described in Section 6.3.2.
6: Customizing the System Configuration 6.2 Modifying Server Files The Freeway server makes use of read-only partitions and RAM-disk partitions specifically so the server can be switched off at any time without damage to the disk drive. Operational files are stored in the read-only partitions and copied to the RAM-disk partitions at boot time. Earlier in this chapter we mentioned that the server configuration files were located in the /tmp/boot/ directory.
Freeway User Guide 6.2.2 Menu Update Method (5-3-3) The preferred method of manually updating Freeway operational files is to first update the files in the read-write operational directory (/tmp/boot) and then save the changes to the non-volatile area (/usr/local/freeway/boot.src). That way if you accidentally overwrite or delete the wrong file, you can always just reboot the Freeway server and start over.
6: Customizing the System Configuration WARNING: Are you sure you want to rebuild the disk?. The system was booted from this disk. If you are sure you want to copy the temporary files back to the permanent area of the disk, press "y", otherwise press any other key to continue without copying files: y Press RETURN to continue What this menu item does is copy all of the files in the operational directory (/tmp/boot) back to the non-volatile storage directory (/usr/local/freeway/boot.
Freeway User Guide of the boot-up sequence. You can use these commands to do anything you want, including making changes to configuration files. When using this method to update files in the operational directory (/tmp/boot), your commands must update the same files in the nonvolatile storage directory (/usr/local/freeway/boot.src) in order to make the changes permanent. The following procedure is an example of updating the bootcfg file on the Freeway server using the CDROM update method.
6: Customizing the System Configuration to see the “echo” text lines printed on the console at the end of the normal boot sequence. Step 5: Remove the CDROM from the Freeway’s CD/DVD drive and reboot the Freeway server again. The Freeway server will use the updated bootcfg file during this boot-up procedure. 6.2.4 Text Files: Windows vs. UNIX The format of text files differs slightly between Windows (DOS) and UNIX operating systems.
Freeway User Guide If you find that a boot or configuration file is not working properly on the Freeway server, you can use the vi editor to check the text file to see if it is in Windows format. The vi editor will display the carriage returns in Windows text files with Ctrl-m ( ^M ) characters at the end of each line.
6: Customizing the System Configuration 6.3 Customizing the Boot Configuration File The default boot configuration file (bootcfg) is located on the Freeway server in the /tmp/boot/ directory. If you are booting the Freeway from the network, the bootcfg file is normally located in the /freeway/boot directory on the boot server (or whatever directory is specified in the Freeway boot parameters).
Freeway User Guide #----------------------------------# # ICP0 Physical Parameters # #----------------------------------# # device_name = icp0 device_type = icp2432 slave_address = 0x14 bus_number = 0 download_script = x25loadb #----------------------------------# # ICP1 Physical Parameters # #----------------------------------# # device_name = icp1 device_type = icp2432 slave_address = 0x13 bus_number = 0 download_script = awsloadb #---------------------------# # Server wide parameters #-----------------
6: Customizing 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 a PCI-based intelligent communications processor model ICP2432 or ICP2432B that can be downloaded with software. All ICP devices installed in a Freeway 3xxx server must be of type ICP2432 or ICP_IP.
Freeway User Guide 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). Each ICP_IP device may be configured independently of all other ICP_IP devices. The bootcfg.ip file contains examples of the ICP_IP parameters.
6: Customizing the System Configuration Local Address The local_address parameter specifies the IP address at which Freeway receives packets. This field may be left blank or set to 0.0.0.0, in which case any configured IP address of Freeway will be used. For devices that will receive multicast packets, this field must be set to the multicast IP address. (Receiving multicast packets requires a special version of Freeway.
Freeway User Guide 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. Connect Period The connect_period parameter specifies the number of seconds to wait between attempts to connect. (This field applies only to socket_type == sock_stream_connect.) Linger Off The linger_off parameter sets the “linger” socket parameter off. This is the default.
6: Customizing the System Configuration mon, and must be explicitly informed about a gateway. The first parameter indicates the Internet address of a destination network or machine, and the second parameter indicates the Internet address of a gateway to that network or machine. For example: route_add 126.0.0.0 207.67.135.10 tells Freeway that the machine with Internet address 207.67.135.10 is the gateway to network 126.0.0.0.
Freeway User Guide to be used to specify each, are as defined for the Boot Device parameter in Table 4–2 on page 107. The added_interface_type parameter may be repeated along with the added_interface_mask and added_interface_addr parameters to indicate multiple added interfaces. Added Interface Mask For each added_interface_type parameter, the optional added_interface_mask parameter may be used to specify the subnet mask to be set for the interface.
6: Customizing the System Configuration TSI connections are defined in a server TSI configuration file (such as muxcfg). Two types of configuration sections are included in the TSI configuration file. The first section (called “main”) specifies the TSI configuration for non-connection-specific operations. Subsequent sections define the operational environment for one or more specific connections.
Freeway User Guide // // 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...
6: Customizing the System Configuration // Server2 { transport = "tcp-socket"; logLev = 0; traceLev = 3; timeout = 63999; MaxInQ = 10; MaxOutQ = 10; asyncio = "yes"; wellknownport = 0x'2011'; // protocol specifics } Figure 6–2: TSI Configuration File (muxcfg) for Freeway Server (Cont’d) configure the server-resident TSI software so it can communicate (using the Freeway message multiplexor) with the client TSI software.
Freeway User Guide • The Transport parameter for each connection name has no default and must be defined. • Unlike the client TSI configuration file you modified, the server parameter is not required for muxcfg because the server TSI software automatically uses the address of the machine on which it is running. • The parameters can appear in any order in the configuration file and can be upper-case, lower-case, or a mixture.
6: Customizing the System Configuration 6.5 Customizing the Server TSI Configuration File Use the following procedure to customize the server TSI configuration file (muxcfg): Step 1: You can use any ASCII text editor to edit the muxcfg file. If a default parameter value is desired, you can omit the parameter line from the file. Parameters in the “main” section apply to non-connection-specific operations. Parameters in the “connectiondependent” section apply to a single connection only.
Freeway User Guide 6.6 Customizing the SRA Startup File Use the following procedure to create or customize the SRA startup file (rc.startsra): 6.6.1 Main SRA Startup File (rc.startsra) Instructions for starting a Server Resident Application (SRA) normally reside in a file called rc.startsra in the /tmp/boot directory. When the Freeway server boots up, it first executes the instructions in the bootcfg file. Then it looks for the existence of the rc.startsra file. If it exists, the Freeway will treat rc.
6: Customizing the System Configuration any text that the SRA may generate (from printf statements) into the null device (bit bucket). If you are unfamiliar with the vi editor, type i to start inserting text, then to get out of insert mode: [If running your SRA from the operational directory, enter the following text:] echo Starting my SRA > /dev/console cd /tmp/boot .
Freeway User Guide However, if you receive later updates to the existing SRA, the updates may overwrite the existing rc.startsra file and your added commands will be deleted. To prevent this from happening, you can place your SRA start commands in a file named rc.startsra.local. Protogate adds commands in the rc.startsra files it distributes to also check for “local” command files of the form rc.startsra.local*.
6: Customizing the System Configuration #!/bin/sh # # file name: rc.startsra # Additional commands for the Monitor Freeway system ● ● ● [ startup commands ] ● ● ● # # # # Allow local configuration overrides (rc.startsra.local can be created by customers to customize a specific Freeway, without the risk of being overwritten by the next software upgrade -- because software upgrades will not overwrite any rc.startsra.local* file). if [ -f /tmp/boot/rc.startsra/local ]; then . /tmp/boot/rc.startsra.
Freeway User Guide 184 DC 900-1333Q
Chapter 7 Software Updates This chapter describes the process of installing software updates for the Freeway server. Protogate periodically issues software updates for the Freeway to customers who have active software maintenance contracts. Freeway software updates are always delivered in CDROM format. There are three types of software updates: 1. Freeway Server Software 2. Protocol Software 3.
Freeway User Guide If you are still undecided, learning what features and bug fixes you will gain by upgrading to the new version may help you decide. If you insert your new Freeway CDROM into any machine with a web browser, you can find the release notes and the release notes history (or take the plain text versions of those files directly from the root of the CDROM; they are the files “relnotes.ser” and “relhist.ser”).
7: Software Updates disk (previous versions had to be explicitly commanded to perform this service by setting “PRESERVE_PARTS=yes”). Another enhancement starting with that version is that now when the Freeway is booted from the CDROM, it determines the IP address which is used by the Freeway when booted normally (from its own disk), and sets an alias to that IP address. So if, for example, your Freeway ordinarily uses IP address 192.168.100.
Freeway User Guide The above command attempts to preserve your boot parameters, configuration files and some programs, but isn't guaranteed not to overwrite any of those (which is why you backed up your own programs earlier). If you want to simply clobber all the permanent storage on the entire Freeway and do a completely clean install, you can use the command PRESERVE_CFG=no ; . /etc/rc.buildfwy instead of the one above.
7: Software Updates backed up your own programs earlier). If you wanted to simply clobber all the permanent storage on the entire Freeway and do a completely clean install, you could use the following command instead of the one above: . /etc/rc.buildfwy If you do that, you will have to re-enter your boot parameters and re-install any protocols that were on that Freeway before (We don't suggest doing it this way; the “PRESERVE_PARTS=yes” command shown above seems to work best for most customers).
Freeway User Guide work for a particular environment, it’s very quick and easy to revert back to the previous version of the protocol. To install a protocol software update: Step 1: Insert the protocol software CDROM into the CD/DVD drive on the Freeway Step 2: Reboot the Freeway Step 3: Remove the CDROM from the CD/DVD drive Step 4: Reboot the Freeway once more The installation will save the previous version of the protocol image under a different name and install the new version.
7: Software Updates • ADIN Message Switch In general, the installation procedure for SRA software updates is the same as for protocol software updates (see Section 7.3). However, you should always follow the installation instructions on the label of the CDROM as some products may require additional steps.
Freeway User Guide 192 DC 900-1333Q
Chapter 8 Configuring a Boot Server This chapter describes how to configure a client system as a “boot server” for one or more Freeway systems on the network. A “boot server” is essentially a system that acts as an FTP server for the Freeway. When the Freeway server is configured to boot from a boot server, it uses FTP to get all the necessary files from the boot server rather than load the files from it own disk drive.
Freeway User Guide Table 8–1: Summary of Boot Server Configuration Steps Steps Reference Section(s) 1. Select a computer on the same network as the Freeway that supports TCP/IP and the file transfer protocol (FTP) or, for UNIX or Windows, remote shell (RSH). You will use this computer as the Freeway boot server. 2. Configure the computer to act as a boot server. Section 8.1 on page 194 3. Load the Freeway software from the distribution Section 8.2 on page 198 CDROM onto the boot server1. 4.
8: Configuring a Boot Server During the boot process Freeway is considered a client while it downloads files over the Ethernet from the Freeway boot directory located on the boot server. After the boot process completes, Freeway starts its normal role as a communications server for its clients. Section 5.1 on page 141 describes the boot process. Freeway supports the FTP or RSH configuration in the boot process (Section 8.1.1 through Section 8.1.3).
Freeway User Guide account, freeway, must have read/write/execute access to all installed files in the directories and subdirectories below freeway. For instructions on how to create user accounts, refer to your system administrator’s guide or consult your system administrator. If you prefer to use RSH on your UNIX or Windows NT system, you must still set up a user account, but the password is not used for accessing the boot server through its remote shell daemon.
8: Configuring a Boot Server ceed with Section 8.2 If not, refer to Section 3.3.2 on page 49 for instructions on how to define names on your client system.
Freeway User Guide 8.2 Install the Freeway Software onto the Boot Server You need to load the Freeway software onto the boot server in order to create the Freeway directory tree where the Freeway boot files are stored. Your system administrator might have already completed this step during the Client software installation procedure described in Chapter 3. If so, skip this section and proceed with Section 8.3 If not, refer to Section 3.
8: Configuring a Boot Server 8.4 Create (or Copy) the Boot File The main boot configuration file for the Freeway server is called bootcfg and contains specific information for loading protocol software on the ICP boards. The file is custom created by Protogate for each Freeway server delivery. As such, the bootcfg file specific to your Freeway server is not located on any of the Freeway or Protocol installation CDROMs. It is located only on the Freeway internal disk drive.
Freeway User Guide Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Admin>cd \freeway\boot C:\freeway\boot>ftp fwy28 Connected to fwy28. 220 fwy28 FTP server (Version 6.00LS) ready. User (fwy28:(none)): root 331 Password required for root. Password: setup (note: password not echoed) 230 User root logged in. ftp> cd /tmp/boot 250 CWD command successful. ftp> ascii 200 Type set to A. ftp> get bootcfg 200 PORT command successful.
8: Configuring a Boot Server Step 1: Obtain the PCI bus and slot numbers for each ICP board You can obtain the PCI bus and slot numbers from the version of the Freeway 3xxx Hardware Installation Guide that matches your model of Freeway server. In each guide there is a drawing of the rear of the Freeway unit with the PCI bus and slot numbers marked for each available PCI slot. Look at that drawing to find the PCI slots occupied by ICP boards on your system, and write down the numbers.
Freeway User Guide 2. The device_name represents the ICP number (icp0, icp1, icp2, etc.). You may number the ICP boards in any order, however, Protogate normally starts ICP numbering (icp0) from the lowest board on 1U and 2U Freeways, and the left-most board on 4U and 6U models. 3. The device_type is always icp2432 for PCI-based ICP boards. 4. Modify the slave_address entry of each ICP to match your configuration. This number may be represented in either decimal or hexadecimal.
8: Configuring a Boot Server # #----------------------------------# # ICP0 Physical Parameters # #----------------------------------# # device_name = icp0 device_type = icp2432 slave_address = 0x14 bus_number = 0 download_script = awsloadb #----------------------------------# # ICP1 Physical Parameters # #----------------------------------# # #device_name = icp1 #device_type = icp2432 #slave_address = 0x13 #bus_number = 0 #download_script = mstloadb Figure 8–2: Sample ICP Entries for bootcfg file 8.
Freeway User Guide 6. Change the System Boot Directory to the directory on your boot server where the boot configuration and load files are located. 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.BOOT] directory.
8: Configuring a Boot Server 8.6 Boot Freeway After you have configured and saved the Freeway boot parameters as described in the previous section, return to the Freeway Main Menu and select 1, then 2, to reboot the Freeway. When the Freeway reboots, it should download the files from the boot server via FTP. Note DC 900-1333Q Protogate recommends having a serial console attached to the Freeway when booting from a boot server for the first time.
Freeway User Guide 206 DC 900-1333Q
Appendix A Freeway File Reference This Appendix provides a quick reference to directories and files located on the Freeway server. A.1 Freeway Disk Partitions The Freeway server disk drive consists of either a flash drive or a rotating disk drive. The disk drive contains a UNIX partition for the Freeway server software. The UNIX partition is divided into several sub-partitions by the FreeBSD OS.
Freeway User Guide /var This partition is created as a READ/WRITE partition and is mainly used for system logging, capture data storage, cron, and similar applications. On standard Freeway servers, this partition is created in RAM memory inside the /tmp partition. /cache This partition is only available on rotating hard drives. This partition represents the remaining area of the drive that is not used by the Freeway OS (usually hundreds of gigabytes).
A: Freeway File Reference protocol software). An example is the Sample Protocol Software where the subdirectory name is sps and the loopback source file name is spsalp.c. The make file invokes the compiler and linker to generate the object file (spsalp.o) and executable file (spsalp). The make file also generates the binary DLI/TSI configuration files, then places them along with the executable file in the /usr/local/freeway/client/bsd/bin directory.
Freeway User Guide /usr/local/freeway/include This directory contains the source code “include” files (.h files) for the DLI/TSI library. These files are accessed by the C compiler when compiling any program code that uses the DLI API. /tmp/boot This is the main operational directory used by the Freeway during runtime. This directory contains the basic Freeway configuration and executable files. Since this directory is located in the RAM-disk partition, it is always mounted read-write.
A: Freeway File Reference Note The /usr partition is mounted READ_ONLY during normal Freeway operations. You must first mount the /usr partition as READ_WRITE before editing, compiling, and linking files in the /usr partition. 1.3.1 Example Filter SRA The files provided with the Freeway server distribution that are used to build the example filter SRA are located in /usr/local/freeway/client/test/sra. They are described below: filter.c This is the source code for the example message filtering SRA.
Freeway User Guide loopback program” which means that it uses non-blocking I/O when interfacing with the DLI API. spsaldcfg This is the text version of the DLI configuration file used by the SPS loopback program. spsaltcfg This is the text version of the TSI configuration file used by the SPS loopback program. makefile.bsd This is the make file that compiles and links the loopback program and creates the executable file (spsalp).
Appendix B Useful Shell Commands This appendix lists several BSD shell commands that are useful in the Freeway environment. To access the BSD shell, log in to the Freeway as root/setup and select “6) Run FreeBSD Shell” from the main menu. B.1 Directory Commands Change default directory to /tmp/boot: cd /tmp/boot Show default directory: pwd List files in directory (with sizes and dates): ls -al B.
Freeway User Guide Dismount a CDROM in the CD/DVD drive: umount /cdrom Mount the “s2g” filesystem as a read-write partition (rotating hard drives only): mount /cache B.3 File Commands Copy a file from CDROM to /tmp/boot (preserving date): cp -p /cdrom/filename /tmp/boot/ Delete a file: rm filename Rename a file: mv filename1 filename2 Display a text file (a page at a time): cat file.txt | more Edit a text file vi file.txt Execute a make (build) file: make -f makefile.bsd B.
B: Useful Shell Commands Exit the shell and return to the Freeway Main Menu: exit B.5 Remote Login Commands The most current Freeway servers do not allow remote logins as root or shell over unsecure applications such as rlogin or telnet. If you need to login to a Freeway as root/shell from a client that only has one of these applications, you can login as “freeway” and then “set user” to shell as shown in the following steps: Step 1: Log into the Freeway from the remote console.
Freeway User Guide 216 DC 900-1333Q
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 tate data transfer to and from Freeway using a standard interface across protocols. 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.
Glossary ICP-resident Protogate-supplied communication protocol software or user- software customized software that runs on the ICP to process the data stream between the ICP and the WAN devices. Refer to the Freeway Protocol Software Toolkit Programmer’s Guide for customized software. IP Internet protocol, described by RFC-791 LAN Local area network LAN protocol The hardware and software which comprise the LAN and form the basis of communications between Freeway servers and clients.
Freeway User Guide RFC Request For Comment is a method of establishing requirements for the INTERNET network (formerly, ARPANET). These requirements form the basis for much of the LAN connectivity used with Freeway, including TCP/IP, User Datagram Protocol (UDP), telnet, SNMP, FTP, bootp, etc. RSH Remote shell; networking software used during the boot process to transfer files.
Glossary service user An entity that uses server resources by interfacing to a service provider. Service users can be tasks that reside on the server and access the service providers directly or they can be processes, or clients, which reside on other machines and access the service providers across the network.
Freeway User Guide 222 DC 900-1333Q
Index A added_interface_addr 174 added_interface_mask 174 added_interface_type 173 Address added interface 174 foreign 171 local 171 local interface 171 Addresses Internet 49, 51 Allocation error 159 Application customization 28 Audience 17 B Boot configuration file parameters added interface address 174 added interface mask 174 added interface type 173 bus number 169 connect period 172 device name 167, 170 device type 169, 170 download script 169 foreign address 171 foreign port base 171 internal protocol
Freeway User Guide reset action selection 109 Booting the Freeway 31 BSD shell commands 213 BSD Unix 25 Buffer allocation error 159 Build hard disk overview of steps 125 Building the SRA files 210 bus_number 169 C Circular queue of messages 97 Client software installation 47 Configuration boot server 194 TSI 176 Configuration file name 108 Configuration, modify 104 Configuring a boot server 193 overview of steps 193 connect_period 172 Console display Freeway initial boot menu 36 initial BSD boot 35 modify b
Index Floppy disk, copy file to hard disk 132 Floppy disk, copy hard disk file to 133 Floppy disk, copy options 128 Floppy disk, delete file 136 Floppy disk, display directory 129, 135 Floppy disk, display file 130 Floppy disk, maintenance 134 Floppy disk, rename file 137 foreign_address 171 foreign_port_base 171 Free memory blocks 95 Freeway boot 31, 32 concepts 28 distribution media 52 initial boot steps 33 installation 31 overview 25 SBC 25 services 28 WAN 25 Freeway configuration Modifying files 161 Fr
Freeway User Guide display log messages 83 display network statistics 98 display ICMP statistics 102 display IP statistics 101 display TCP statistics 99 display UDP statistics 100 display system information 92 display circular queue of messages 97 display task stack usage 96 display TCP summary 94 list free memory blocks 95 list I/O devices 93 display user names 103 logout 140 modify configuration 104 modify boot parameters 105 modify system time 111 modify user names 110 shutdown 80 trace functions 112 Int
Index S SBC 25 Secondary network interface 108 Server management 28 Server resident application 159 Shutdown options menu 80 reboot server 80 slave_address 169 snd_buf_size 171 snd_q_size 172 SNMP 27 SNMP support 29 socket_type 170 Software installation DLI Library 52 overview of steps for client 48 Support, product 23 System boot directory 108 System boot file name 108 System Boot Parameters Menu, modify 203 System time 103 System time, modify 111 U UDP statistics 100 UNIX Build DLI files 57 Build loopba
Freeway User Guide 228 DC 900-1333Q
Freeway User Guide DC 900-1333Q 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.
