AXEL Platine Terminal Ethernet TCP/IP Models Installing Platine Terminals on UNIX Systems May 1997 - Ref.
The reproduction of this material, in part or whole, is strictly prohibited. For additional information, please contact: Zone d'activité d'Orsay-Courtabœuf 16 Avenue du Québec BP 728 91962 LES ULIS Cedex - France Tel.: 33 1 69 28 27 27 Fax: 33 1 69 28 82 04 The information in this document is subject to change without notice. AXEL assumes no responsibility for any errors that may appear in this document. All trademarks and registered trademarks are the property of their respective holders.
1 - INTRODUCTION ........................................................................................1 1.1 - OVERVIEW ..........................................................................................2 1.1.1 - Serial Connection ...........................................................................2 1.1.2 - Network Connection .......................................................................3 1.1.3 - Multiple Logical Links ................................................................
3.3.1 - SCO UNIX 3.2v4 ..........................................................................30 3.4 - CONFIGURING A RARP SERVER.....................................................31 4 - USING MULTI-SESSION..........................................................................33 4.1 - USING WITH VIEW/HOST ASSOCIATIONS .....................................34 4.2 - USING WITH SET-UP........................................................................36 4.2.1 - Opening a Network Session..............
8.1.4 - TCP Port Number.........................................................................64 8.1.5 - Summary......................................................................................65 8.1.6 - Caution.........................................................................................68 8.1.7 - Configuration................................................................................68 8.2 - SET-UP THE PLATINE TERMINAL ....................................................69 8.2.
TCP/IP Parameters .................................................................................98 AUX1 and AUX2 Parameters................................................................. 100 Parallel Port Parameters ....................................................................... 101 Multi-session Parameters ...................................................................... 101 Terminal Parameters.............................................................................
Introduction -1INTRODUCTION ________________________________________________________________ TCP/IP AXEL Platine Terminal 1
Introduction This chapter introduces the concept and the main features of the AXEL TCP/IP Platine terminal. 1.1 - OVERVIEW Under UNIX, the connection between a host and a terminal uses a device file called tty (or ptty for pseudo-terminals). Through this device, an application running on the host can exchange data with a terminal. The application is thus isolated from the actual physical link over which data transmission takes place.
Introduction The host uses a software ‘driver' to manage a serial I/O (input/output) controller (for example COM1 on the serial I/O board). The terminal has a dedicated circuit associated with each serial port, which transmits and receives characters over the asynchronous line. 1.1.2 - Network Connection An AXEL TCP/IP Platine terminal operates quite differently from a conventional terminal.
Introduction Each AXEL Platine terminal can support up to EIGHT logical links. This feature, called Multi-connection, lets any AX3000 user run up to 8 simultaneous working sessions, on one or several hosts. 1.2 - MAIN FEATURES Each TCP/IP AXEL Platine terminal can operate as up to eight concurrent and independent virtual terminals. With this virtual terminal capability, an AXEL Platine terminal can provide multiple connections across a network.
Introduction 1.3 - EXAMPLE CONFIGURATION ! ' # (' ' & (' % & ! #$ " ' & (' ! ' & (' " % & " In this example, two distinct local area networks are linked.
Setting the Configuration -2TERMINAL CONFIGURATION ________________________________________________________________ TCP/IP AXEL Platine Terminal 7
Setting the Configuration This chapter provides the general information needed to install and configure TCP/IP AX3000 Platine terminals on an Ethernet network.
Setting the Configuration The TCP/IP Set-Up screen appears as follows: Move through the menu with arrow keys. Information, relating to each command selected, will be automatically displayed at the bottom of the screen. To confirm the selected command, press the key. To exit from the menu, select the 'Quit' command or press the key. The various options of the 'Session' menu are described in Chapter 4 (Using the Multi-Session). 2.
Setting the Configuration called “IP addresses”) are usually written as four decimal numbers separated by decimal points ('.' character). There are three main classes of IP address: Class A 0 Class B 1 0 Class C 7 bits Network 1 1 0 24 bits Host 14 bits Network 16 bits Host 21 bits Network 8 bits Host Thus every IP address occupies 4 bytes and contains both: - a network address, and - a host address. even though these may be of varying lengths.
Setting the Configuration Add Host Drop Host Add Route Drop Route AX3000 IP AX3000 Ether 2.2.1 - Ethernet Addresses Platine terminals (like other devices equipped for Ethernet networking) have a unique hardware address which is issued by the manufacturer and cannot thereafter be modified. The address is in the form of six hexadecimal bytes, separated by colons, thus: Example: 00:A0:34:01:02:09 To find a Platine terminal’s Ethernet address, select the 'AX3000 Ether' option. 2.2.
Setting the Configuration RARP protocol on the AXEL Terminal: If the AX3000 IP address has not been set (it has the value 0.0.0.0) the following screen will be displayed when the AX3000 is turned on: F I R S T I N S T A L L A T I O N Press <*> to enter set-up or press to search for the AX3000 IP address (RARP protocol) AX3000 TCP/IP Terminal Base TB105.3.M55.FR.9701.a 00:A0:34:xx:xx:xx Pressing will automatically trigger the RARP protocol.
Setting the Configuration 2.2.3 - Host Management To connect a Platine terminal to a host on the Ethernet network, using TCP/IP or TELNET protocols, the host must be identified with 2 parameters: - a name (any alphanumeric character string beginning with a letter), - an IP address, - a telnet port: the TCP port used by the telnet service of Unix (default value 23). These parameters can be found in the /etc/hosts file of the host to which you want to connect.
Setting the Configuration Note: the router list must always include the router named 'default'. If this router name is canceled in error, it will be generated again, automatically, when the Platine terminal is next switched-on. From the example configuration (cf. chapter 1.3): adding the router through the set-up of the AX3000 '192.168.1.201': Gateway Address: 192.168.1.2 (Router) Host IP Address: 192.1.1.3 (Host 3) Mask: 255.255.255.
Setting the Configuration 2.3 - SETTING MULTI-SESSION PARAMETERS The AX3000’s built-in multi-connection capability allows simultaneous access to up to 8 different hosts on one or more Ethernet networks. The necessary parameters (number of sessions and the view/host association) are set in the 'Terminal' menu of the TCP/IP Set-Up: Sessions Status Line Add View Add AUX1 Add AUX2 Drop 2.3.1 - Setting the Sessions By default, the 'Nb sessions' parameter is set to 8.
Setting the Configuration Note: it is impossible to modify these two parameters when one or more telnet sessions are active. 2.3.2 - Status Line th A status line (i.e. a 26 line) can be used to identify each session of the TCP/IP AX3000. The label associated with each session is either the name of the associated UNIX Host or a user-defined label. To set this label refer to the next chapter. Note: the 26-line display can be not supported by certain monitors. 2.3.
Setting the Configuration The 'Drop' option is used to remove a View/Host association. Select the association and press to remove it. Operation of the Platine terminal with View/Host facilities is described in Chapter 4.1. 2.4 - SETTING THE PROTOCOL The Axel Platine terminal uses five internal parameters to optimize the TCP/IP protocol to match the existing networking and applications environments. Note: these parameters have factory-default settings.
Setting the Configuration The new value will be used for the next connection made. 2.4.2 - 'window' Option This parameter defines the size (in bytes) of the Platine terminal TCP window. By default, it is set to 1000 bytes. This value can be modified but must be higher than the 'mss' parameter. If too many (received) frames are rejected by the Platine terminal, the 'window' parameter may be decreased. The new value will be used for the next connection made. 2.4.
Setting the Configuration A 'High' threshold, sets an AX3000's high reception sensitivity. Then, in case of an unexpected attenuation of signals (due to a low quality wiring, a too long cable, etc) this parameter allows the Platine to receive and process the network frames normally. Note: it is recommended that this parameter be modified with caution, because the more sensitive the AX3000 is to data reception, the more sensitive it is to external interference.
Setting the Configuration 2.5 - STATISTICS The Platine terminal monitors network performance from the time it is switched on. The logs record details of exchanged frames, rejected frames, etc. The 'statistics' menu may be used to access these logs. Ethernet ARP IP ICMP TCP Client TCP Server These statistics are mainly intended for network administration tasks, such as error diagnosis or network optimization. This manual only describes the Ethernet, the ARP and the TCP (Client and Server) options. 2.5.
Setting the Configuration terminal. An ARP request is a request to determine the Ethernet number of a host, whose IP address has been given for a terminal-to-host connection. - received: number of received ARP frames. This value is equal to the sum of the following parameters: - replies: number of responses to ARP requests sent from the Platine terminal, - badtype: wrong frames, - request-in: number of received ARP requests, - request out: number of ARP requests sent from the Platine terminal.
Setting the Configuration 2.6 - SETTING EMULATIONS Each AX3000 Ethernet model provides up to 8 independent virtual terminals. Multi-connection lets any Platine terminal user run up to 8 simultaneous working sessions (on different hosts, if required). Virtual terminals have independent set-up parameters (emulation, function keys, video attributes, etc). For example, an RS/6000 ANSI emulation can be used on one view while a VT220 emulation is being used on another.
Setting the Configuration If all sessions will use identical settings, those of one active session can be duplicated automatically to ALL other sessions, by a propagation option invoked by . Note: modifications to this setting will affect current sessions immediately. Other sessions will not be modified until they are activated. The following table shows recommended, pre-defined, set-up and TERM values for the various operating systems: Operating System Pre-defined set-up TERM SCO UNIX 3.
Setting the Configuration Example 1 This example assumes operational connection of the following views to the following hosts: view 1: SCO UNIX 3.2v4 host, view 2: IBM AIX host, The following procedure is used to establish the sessions: invoking view 1 entering Terminal Set-Up selecting SCO 4.
Setting the UNIX System -3CONFIGURING THE UNIX HOST ________________________________________________________________ TCP/IP AXEL Platine Terminal 25
Setting the UNIX System This chapter describes how to configure a UNIX host for operation with AXEL TCP/IP Platine terminals. The UNIX host configuration procedure, for the TCP/IP Platine terminal, involves two major steps: - setting network parameters, - configuring the UNIX system. On some UNIX systems, default settings may need adjustment (tuning), to optimize performance with TCP/IP terminals. 3.1 - SETTING NETWORK PARAMETERS This step modifies only one host file: /etc/hosts.
Setting the UNIX System The /etc/hosts file must be updated in order to use the embedded TCP/IP print server capability of the Platine terminal (see Chapters 5 and 7). 3.2 - CONFIGURING THE OPERATING SYSTEM 3.2.1 - Overview Unlike a serial terminal, a networked terminal is not assigned to one dedicated device. Instead a pseudo-terminal device file is allocated, dynamically, according to the sequence in which networked peripheral devices are connected.
Setting the UNIX System If no TERM value is set through the TCP/IP Set-Up, or if the session is opened [Open]), the TERM value via the TCP/IP Set-Up sequence ([Session] 'negotiated' depends on the pre-defined set-up that has been selected: - ANSI like pre-defined set-up: TERM=ANSI - VT like pre-defined set-up: TERM=DEC-VT220 The TELNET protocol, which is used to first establish a connection, only recognizes two values (both written in uppercase characters) for the TERM variable.
Setting the UNIX System To switch scancode mode on or off, the ansi terminfo entry must include the smsc and rmsc capabilities. Create the ansi terminfo source file: # cd /usr/lib/terminfo # infocmp ansi > ansi.src Add the following line to this file, at any position except the beginning or end of the file: smsc=\E[<0A, rmsc=\E[<1A, xonc=e, xoffc=g, Exit from the editor and save these modifications, then enter the following command at the UNIX prompt: # tic ansi.
Setting the UNIX System When scancode mode is switched on, the keyboard LEDs can be turned on or off by means of an escape sequence (CSI < p1;p2;p3 O). For more information, refer to the User's Guide. 3.3 - TUNING THE OPERATING SYSTEM The operating system TCP/IP package may not default to an optimized configuration for the use of TCP/IP terminals. In this situation, the system parameters may be adjusted by means of a 'tuning' procedure.
Setting the UNIX System Adjust the parameter values. The Kernel must be 're-linked' after these modifications. 3.4 - CONFIGURING A RARP SERVER For a UNIX host to act as a RARP server it must: - run the RARP daemon - /etc/rarpd, - have a list of paired Ethernet addresses and associated host names (for the relevant Platine terminals and any other devices) in the file /etc/ethers.
Using the Multi-Session -4USING MULTI-SESSION ________________________________________________________________ TCP/IP AXEL Platine Terminal 33
Using the Multi-Session This chapter describes the use of the TCP/IP AX3000 Multi-session and the View/Host associations. AXEL TCP/IP Platine terminals provide multiple and concurrent connections. This feature allows simultaneous access to multiple hosts and applications. To switch between views (sessions), use the following keystroke combination: Where represents whichever of the to function keys corresponds to the view number required.
Using the Multi-Session These View/Host associations provide two major benefits: - they enable users to make quick, automatic and faultless connections, - they initialize connection parameters without the need to enter set-up. When the Platine terminal is turned-on, automatic connections are made for the session, if the 'PowerOn Connect' parameter is set to 'y' (yes). If no session is set in this way, the View/Host association list is displayed.
Using the Multi-Session 4.2 - USING WITH SET-UP If no View/Host association has been defined, the following message is displayed when the Platine terminal is turned on: No Pre-programmed View In this case, the connection to a host will have to be made via TCP/IP Set-Up. To enter TCP/IP Set-Up, use the following keystroke combination: The TCP/IP Set-Up menu is displayed as follows: The TCP/IP Set-Up appears as a menu bar and several pull-down menus.
Using the Multi-Session To exit from the set-up, use the 'Quit' option or strike the key. The TCP/IP Set-Up 'Session' menu lists the following options: Open Close Resume Quit 4.2.1 - Opening a Network Session The 'Open' option is used to select a host from the host list. The screen is fully cleared, immediately after host selection. A login will then be displayed when the session is opened.
Using the Multi-Session After disconnection, the behavior of the Platine terminal depends on the 'Auto Reconnect' parameter of the current session. If this parameter is set to 'y' (yes), a new connection is immediately and automatically established with the current session. If this parameter is set to 'n' (no), the Platine terminal displays the first of the remaining active sessions.
Standard Print Servers -5STANDARD PRINT SERVERS ________________________________________________________________ TCP/IP AXEL Platine Terminal 39
Standard Print Servers This chapter provides the information needed to use printers attached to a Platine terminal. The lpd and rcmd utilities allow standard monitoring of network printers. This chapter provides information for installing and using these utilities to control printers attached to the Platine terminal. Note: the auxiliary ports of the Platine terminal can be also controlled by three AXEL proprietary servers.
Standard Print Servers The three following fields allow a network lpd or rcmd service to be associated with the auxiliary ports: - AUX1 Port Service, - AUX2 Port Service, - Parallel Port Service. Use the arrow keys to select the auxiliary port, then press . If the current service is printd, rtty, rcmd or lpd, the following dialog box appears: Service : printd TCP Port : 2048 Filter : none Press again to select the service.
Standard Print Servers The PRN Name field displays the auxiliary port name. This name will also be the name used by lpd for the connected printer. The Filter field (only available with lpd) allows line feed (NL) to be mapped to carriage return plus line feed (CR NL). 0Ah is mapped to 0Dh 0Ah. Note: within this set-up screen, the 'Default Auxiliary Port' field allows selection of the port to be used to perform hardcopy and local printing through escape sequences (CSI 4i and CSI 5i). 5.1.
Standard Print Servers - rcmd: the AX3000's printer is accessed by the rcmd command. This command must be added to a printer interface program or associated with a pseudo-terminal to create a system printer. 5.2.1 - Using lpd a - Overview Use the UNIX System Management Tool to add a remote printer. At least, two parameters are required: - the name of the remote host: enter the AX3000's name (refer to /etc/hosts), - the name of the printer: this name is the PRN name entered when the AX3000 was set up.
Standard Print Servers Two type of printer can be added: - Standard Processing: AIX sends a raw file to the AX3000. You can use a filter by setting the CR-NL filter through the AX3000's set-up.
Standard Print Servers 5.2.2 - Using rcmd The rcmd command reads data from 'standard input' (stdin) and sends this data to one of the auxiliary ports of the AX3000. Note: some UNIX systems use rsh instead of rcmd. To print a file, issue the following command at the UNIX prompt: $ cat file | rcmd ax3000 nport where: - ax3000 is the name for the AXEL terminal (refer to /etc/hosts), - port is the PRN name of the AX3000's port.
Standard Print Servers The printer must be attached to the slave part of the pseudo-terminal. For example, if the printer is attached to /dev/ttypf, then /dev/ptypf is used with the rcmd command. Note: the rcmd command can be added within a boot script which should be placed in the /etc/rc2.d directory.
The Terminal Server -6THE TERMINAL SERVER ________________________________________________________________ TCP/IP AXEL Platine Terminal 47
The Terminal Server This chapter provides the information needed to use serial terminals attached to a Platine terminal. The AX3000 provides two bi-directional auxiliary serial ports. Various serial peripherals can be attached to these serial ports: bar code readers, printers, scales, etc. With the embedded AX3000 Terminal Server, serial terminals can also be attached. These serial terminals are automatically controlled by the embedded telnet service. No additional software is needed.
The Terminal Server Use the arrow keys to select the auxiliary port, then press . If the current service is printd, rtty, rcmd or lpd, the following dialog box appears: Service : printd TCP Port : 2048 Filter : none Press again to select the service. The following menu appears: None printd rtty lpd rcmd rtelnet Note: if the current service is None or rtelnet, the menu appears immediately and the dialog box is omitted.
The Terminal Server 6.1.3 - Exiting the Set-Up Press then to save the current configuration and to exit Set-Up. 6.2 - TCP/IP SET-UP When the rtelnet service is associated with one serial port, it is necessary to associate this port with a UNIX host (in the same way, a session is also associated with a UNIX host). Press < > to enter TCP/IP Set-Up.
The Terminal Server - PowerOn Connect 'y': the connection will be automatically established when the Platine is powered on. 'n': Press any key on the serial terminal keyboard to establish the connection. - Auto Reconnect 'y': a new connection is automatically established after a disconnection (). 'n': Press any key on the keyboard of the serial terminal to establish a new connection. The 'Drop' option allows an association to be removed. Select the association and press to remove it. 6.
The AXEL tty Server -7AXEL TTY SERVER ________________________________________________________________ TCP/IP AXEL Platine Terminal 53
The AXEL tty Server This chapter describes the AXEL tty server and explains its installation and use. It does not apply to terminals connected via a serial port, which were covered in the previous chapter, Chapter 6. 7.1 - INTRODUCTION The AXEL tty server associates a UNIX device (ptty) on the host with an auxiliary port on the AX3000 terminal. This enables data written to the UNIX host device to be sent to the AX3000 port, and data received via the AX3000 port to be read through the UNIX host device.
The AXEL tty Server The following drawing shows the UNIX mechanisms: 7.2 - SETTING UP THE AX3000 The tty service must be initiated by means of two AX3000 Set-Up procedures: - Terminal Set-Up, which associates the tty service with an auxiliary port (serial or parallel) and configures it (baud rate, handshake, etc.
The AXEL tty Server Use the arrow keys to select the auxiliary port, then press . The following dialog box appears: Service : lpd PRN Name: parallel Filter : NL=CR+NL Press again to select the service. The following menu appears: None printd rtty lpd rcmd rtelnet tty Within this menu, use the vertical arrow keys to select the required tty service and press . If the selected port is a serial one, press to configure AUX1 (or to configure AUX2).
The AXEL tty Server 7.2.2 - TCP/IP Set-Up Enter the AX3000 TCP/IP Set-Up (< >). Select the vertical menu [Terminal] then select the item for the relevant input/output port: Add AUX1 or Add AUX2 or Add Parallel. Enter the following parameters: - Hostname enter the name of a host (which must have been previously declared in the 'Network' menu, through the 'Add Host' option - refer to Section 2.2.3). - Auto Reconnect 'y': a new connection is automatically established after a disconnection.
The AXEL tty Server 7.3 - UNIX CONFIGURATION A UNIX host accepts an AX3000 tty connection if axttyd is launched on the UNIX host and if the axttyd configuration file lists this connection. 7.3.1 - Installing Insert the floppy diskette provided. Log in as superuser and enter the following commands: # cd /tmp # tar xvf /dev/fdx # cd ttyserver (where fdx is the local name for the floppy disk drive device) Select the binary file that corresponds to the operating system you are using (axttyd.
The AXEL tty Server 7.3.2 - Using The AXEL tty server uses a configuration file which lists the authorised associations between AX3000 ports and UNIX pttys. Each entry in this file contains four parameters: - AX3000 name (see /etc/hosts) - AX3000 input/output port.
The AXEL tty Server The authorised associations, connections and disconnections are all recorded in the specified log file. Modify the association file: If the association file is modified while the AXEL tty server is running, the AXEL tty server must re-read the configuration file. This is done by sending the signal 16 to the AXEL tty server process. For example: # kill -16 pid - pid is the process ID for the AXEL tty server process. 7.3.3 - Uninstalling Remove the AXEL files from /etc and /etc/rc2.
The AXEL Proprietary Network Servers -8THE AXEL PROPRIETARY NETWORK SERVERS ________________________________________________________________ TCP/IP AXEL Platine Terminal 61
The AXEL Proprietary Network Servers This chapter introduces the TCP/IP AX3000 print and tty servers. This chapter is dedicated to the three AXEL proprietary network servers. These servers are used to control AX3000's printers. They are written in the C language and may be compiled and linked (for whichever UNIX System is being used) if the binary executable files are not available. Note: refer to the Chapter 5 to install the standard UNIX print servers: lpd and rcmd. 8.1 - INTRODUCTION 8.1.
The AXEL Proprietary Network Servers network user and is managed by the UNIX spooler with the lp and associated commands. Every auxiliary port can be accessed through a print or a tty AXEL server. It is possible to control 3 system printers attached to a single Platine terminal. 8.1.
The AXEL Proprietary Network Servers 8.1.3 - Device: Pseudo-Terminal or Named Pipe The device used by the printd server can be either a pseudo-terminal or a named pipe. Consider the following when choosing: Named Pipe: The use of a named pipe is very versatile. Because named pipes are not attached to UNIX kernel drivers, it is possible to create as many as necessary. However, these devices only provide uni-directional communication.
The AXEL Proprietary Network Servers 8.1.5 - Summary The following table describes the main characteristics of each AXEL Server: AXEL Server AX3000 Service Communication UNIX Monitoring Port Sharing UNIX Device printd printd uni-directional Yes ttyd rprint rtty rtty bi-directional uni-directional daemon or Piobe (*) daemon program pseudo-terminal or named pipe (*) pseudo-terminal None No Yes (*) IBM AIX allows both daemon monitoring and Piobe monitoring.
The AXEL Proprietary Network Servers The following examples illustrate the most common printer configurations used on UNIX Systems. a) The Printer is Directly Attached to the UNIX Host (parallel port) The UNIX System (lp program) accesses the parallel printer through a device. This parallel device (/dev/lp0), provided as a standard feature of the UNIX system, controls the parallel port of the host.
The AXEL Proprietary Network Servers printd Server: "# " In this example, the UNIX device being used is a named pipe (uni-directional device), but a pseudo-terminal could be used also. ttyd Server: In this example, the UNIX device being used is a pseudo-terminal.
The AXEL Proprietary Network Servers printd Server - Piobe Monitoring (AIX only): "# " $ The main advantage of this method of monitoring is that no UNIX device is used. Note: the rprint server works in the same way. 8.1.6 - Caution The Platine terminal is not operating as a simple terminal but as a print and tty server. So, caution must be used in switching off the Platine terminal.
The AXEL Proprietary Network Servers 8.2 - SET-UP THE PLATINE TERMINAL Up to 3 peripherals can be connected to the Platine terminal (2 bi-directional serial ports and 1 uni-directional parallel port are available).
The AXEL Proprietary Network Servers Use the arrow keys to select the auxiliary port, then press . If the current service is printd, rtty, rcmd or lpd, the following dialog box appears: Service : lpd PRN Name: parallel Filter : NL=CR+NL Press again to select the service. The following menu appears: None printd rtty lpd rcmd rtelnet Note: if the current service is None or rtelnet, the menu appears immediately and the dialog box is omitted.
The AXEL Proprietary Network Servers Note: within this set-up screen, the 'Default Auxiliary Port' field allows selection of the port to be used to perform hardcopy and local printing through escape sequences (CSI 4i and CSI 5i). 8.2.3 - Serial Port Setting or (select the auxiliary port configuration) Operating Mode: These parameters allow a choice of operating mode for the selected serial port (AUX1 or AUX2).
The AXEL Proprietary Network Servers Change to the /tmp directory, then copy the AXEL diskette files to the hard disk: # cd /tmp # tar xvf /dev/fdx where fdx is the device name for the diskette. Invoke the installation script: # ./install From the menu, select the language to be used (English or French) and the UNIX operating system (AIX, SCO, etc) under which the servers are to run. The two servers and the AXEL configurator will then be copied to the /etc directory.
The AXEL Proprietary Network Servers 8.3.1 - Platine/Device Association Option 3 allows a Platine/Device Association to be added. Five parameters are required: - AXEL Server: Select the required AXEL server (printd or ttyd) according to the Terminal Set-Up of the Platine terminal. - AXEL Platine: Enter the name of the target Platine. If this name is not listed in the /etc/hosts file, the axconf utility adds it, with its associated IP address.
The AXEL Proprietary Network Servers a) Using a Printer The most common requirement is to declare a printer attached to the Platine terminal. This printer can be added using the UNIX System Management Tool. Note: a printer can also be created or removed through options 4 and 6 of the AXEL utility. Use these options only when the printer device is a named pipe and use the UNIX System Management Tool when the printer device is a pseudo-terminal.
The AXEL Proprietary Network Servers For DAEMON Monitoring (options 3, 4, 5 and 6) refer to the previous chapter. PIOBE monitoring associates a Platine terminal with a printer (not with a device). The main benefit of this method is that the AXEL server is not a daemon (a background process) but a simple printer interface program. By selecting option 7 in the configuration menu, a Platine/Printer Association can be created. Three parameters are needed: - AXEL Platine: Enter the name of the target Platine.
TCP/IP Multishell -9TCP/IP MULTI-SHELL ________________________________________________________________ 76 TCP/IP AXEL Platine Terminal
TCP/IP Multishell This chapter deals with the installation and use of the AXEL multi-shell software provided with TCP/IP AXEL Terminals. One of the main features of the AX3000 is multi-connection. An AX3000 supports up to 8 simultaneous telnet connections to one or many hosts. When sessions are run on the same host, with the same user name, the AXEL multi-shell software allows duplicate telnet sessions to be run from the shell, without the need for multiple logons.
TCP/IP Multishell - tcpmsh.SCO - tcpmsh.SVR4 - tcpmsh.SNX : SCO UNIX : UNIX AT&T and UNIXWARE : SINIX To rename the required file tcpmsh, and to copy it to /usr/bin, enter the following command with “OS” replaced by the operating system suffix: # cp tcpmsh.OS /usr/bin/tcpmsh Because it is dedicated to the AX3000, the software is immediately operational. It has no need for configuration files, nor for the system to be rebooted. 9.
TCP/IP Multishell - For a consistent configuration, 'the value of the ‘telnet session number' multiplied by the 'multi-shell view number' must not exceed 8. 9.3 - USING MULTISHELL The tcpmsh command can be invoked either at the UNIX prompt or from a script (e.g. .profile file), and can be followed by possible options (see section 9.4). 9.3.1 - Running tcpmsh To run tcpmsh, the syntax is: $ tcpmsh [-options] Section 9.4 describes each option.
TCP/IP Multishell If a view does not already exist, the tcpmsh program allocates a pseudoterminal, launches the view and runs .profile. The maximum number of views may be altered by an option to the tcpmsh command. 9.3.3 - Deleting a View To delete a view, move to it () and exit the shell (by typing exit or pressing ). The tcpmsh software releases the associated pseudoterminal and moves to the first view. If the deleted view was the only active view, the program terminates. 9.3.
TCP/IP Multishell - 'b 2': use with ttypz, ttyqz, ttyrz and ttysz (where z is any hexadecimal value from 0 to F). By default, tcpmsh uses the '-b 0' option. Note: this option is not compatible with use of the '-p' option (see section 9.4.8) and is not available for AT&T UNIX. 9.4.2 - '-c' Option: Overscan Colour When tcpmsh software is active, the status line may be used to identify the current view. Another way to identify the current view is to associate a different overscan colour with each view.
TCP/IP Multishell Example: the cmd file: smit client This file is used through the following command: $ tcpmsh -f cmd In this example, the smit utility is invoked within view 1 and the client application within view 3. Views 2, 4, 5, 6, 7 and 8 do not have initial commands. Instead the shell remains active. 9.4.4 - '-h' Option: On-Line Help This option displays the tcpmsh syntax and gives a brief description of every option. 9.4.
TCP/IP Multishell Example: following the command: $ tcpmsh -n 4 -L UNIX the status line cells will display UNIX/1 for view 1, UNIX/2 for view 2, UNIX/3 for view 3 and UNIX/4 for view 4. 9.4.6 - '-l' Option: Status Line on line 25 This option '-l' (lowercase L) allows the use of line 25 to display a status line which specifies the active session and the number of declared views. Note: a character string can be added following this option to display a label at the right of this line.
TCP/IP Multishell Recompile the updated source file using the following command (where emul.src is the name of the modified source file): # tic /usr/lib/terminfo/emul.src AX3000 Set-Up: The 25th status line option must match the ‘Number of Lines’ parameter of the Platine terminal Set-Up. This parameter can take either of two values: - 25 lines, - 24 + 1 message line.
TCP/IP Multishell Example: $ tcpmsh -n 4 9.4.9 - '-p' Option: Predefined Pseudo-Terminals It is possible to use a fixed set of pseudo-terminals, which are listed in a parameter file which is named as the argument to the ‘-p’ option. Each line of the file lists the ptty dedicated to its view (8 lines maximum): view 1 1st line view 2 2nd line ... ... ...
TCP/IP Multishell 9.4.11 - '-x' Option: Circular Buffers A view is considered to be inactive when it is not the current view. Within a session, when n views are used, there is always one active view (the current one) and n-1 inactive views. By default, it is impossible to display data through an inactive view. When an attempt is made to send data to an inactive view, it is immediately locked (using XOFF) so that the flow of data is stopped.
TCP/IP Multishell - Moving between views: a switch between screens ( keystroke) may interrupt an output escape sequence and disturb view contents. To prevent this problem, only change screens when the display is stable. - Using buffers ('-x' option): When a new screen is activated, the tcpmsh program displays the contents of the corresponding circular buffer.
Remote Administration - 10 REMOTE ADMINISTRATION ________________________________________________________________ TCP/IP AXEL Platine Terminal 89
Remote Administration This chapter deals with TCP/IP AX3000 remote administration. 10.1 - OVERVIEW This feature permits remote administration (Set-Up) of the TCP/IP AX3000. This AX3000 Set-Up is performed by the rcmd command. A text file (given as an argument to the rcmd command) contains the value of each Set-Up parameter. This text file may contain some or all AX3000 Set-Up parameters.
Remote Administration Note: rcmd command is also called rsh on some UNIX systems. Example: # rcmd axname ax_reboot Note: to access an AX3000 with the rcmd command, the IP address of the AX3000 must already be set. The AX3000 IP address can be set: - through the AX3000 TCP/IP Set-Up, or - automatically by the RARP protocol (see section2.2.2). 10.2 - SETTING-UP A PLATINE To set-up an AX3000, use the rcmd command together with the setup_send keyword.
Remote Administration The message 'Reboot in progress...' is then displayed on the operator console, the AX3000 is reset and the new Set-Up is implemented. If a connection problem occurs, a time-out error message is displayed. 10.3 - OBTAINING A CONFIGURATION To obtain an AX3000 configuration, use the rcmd command together with the setup_get keyword.
Remote Administration 10.4.1 - Fatal Errors Fatal errors stop the rcmd command. The following fatal errors may occur: ERR 101: header label expected. Command: Cause: setup_send the AXEL header label (BEGIN_AX_SETUP) is not the first line of the configuration file. Consequence: the rcmd command is aborted, the AX3000 Set-Up is not modified. Solution: check the file. Replace it with a correct AXEL configuration file. ERR 102: bad header label protocol version.
Remote Administration Consequence: the Set-Up obtained by the command is invalid (the trailer label is missing). Solution: run the rcmd command again. ERR 105: invalid rcmd command. Command: Cause: Consequence: Solution: setup_send, setup_get or ax_reboot the rcmd keyword is unknown. no effect. use setup_send, setup_get or ax_reboot. ERR 106: cmos busy. Command: Cause: setup_send another rcmd command (setup_get or setup_send) is running, or another user has entered Set-Up, on the target AX3000.
Remote Administration Consequence: the Set-Up parameter is ignored. The current value of this parameter is retained. Solution: check the possible values of this parameter (section 10.5). ERR 203: xxx: no place to store udk value. Command: Cause: setup_send not enough memory to store the udk_xxx parameter (udk stands for User-Defined Key; a function key for example). Consequence: the default value of this udk parameter is reloaded. ERR 204: line(s) after the trailer label ignored.
Remote Administration Cause: eight screens are supported by the AX3000. This resource is shared by sessions and pages (i.e. multi_nbsession multi_nbpage 8). Consequence: to get a consistent configuration, the multi_nbpage parameter is set to one. Solution: check the number of sessions and pages. 10.5 - CONFIGURATION FILE FORMAT A configuration file can list some or all AX3000 Set-Up parameters.
Remote Administration Several formats are available for Set-Up parameter values: List: the possible values are listed (the character '|' is used as a separator). Examples: (yes | no). (none | xon-xoff | xpc |dtr) Number: maximum and minimum values are given. Character string: maximum length is given. Note: an ASCII character can be represented by its hexadecimal ASCII code, preceded with a backslash character (eg.: \1B represents Escape and \\ represents a backslash).
Remote Administration # Firmware: FK3.BV1.1a/TCP.UK.9701.a # ######################################################### # # RESET_CMOS Note: the RESET_CMOS command allows all the Set-Up parameters (except the AX3000 IP address) to be reset. When the configuration file is obtained from an AX3000, this RESET_CMOS command is displayed as a comment. Ethernet Parameters #ethernet_ipaddr=192.168.1.
Remote Administration #tcp_host7_telnetp= #tcp_host8_name= #tcp_host8_ip= #tcp_host8_telnetp= tcp_router1_ip=192.168.1.252 tcp_router1_target=192.1.1.252 tcp_router1_mask=255.255.255.0 tcp_router2_ip=192.168.1.253 tcp_router2_target=192.18.1.2 tcp_router2_mask=255.255.255.0 tcp_router3_ip=0.0.0.0 tcp_router3_target=default tcp_router3_mask=0.0.0.
Remote Administration address and the tcp_router%_mask parameter is an optional network mask used to reach the target network. - The default router is encoded by tcp_router%_ip set to 0.0.0.0, cp_router%_target set to default and tcp_router%_mask set to 0.0.0.0. AUX1 and AUX2 Parameters In the following section of the file, for ease of reading the auxiliary port number (1 or 2) has been represented by the '%' character.
Remote Administration filter_nl associate_host associate_term associate_autoconn associate_reconn Parallel Port Parameters parallel_service=none (none | rtty | printd / lpd | rcmd) parallel_service_name=parallel (character string, 8 char max.) parallel_service_num=2050 (number) parallel_filter_nl=no (yes | no) parallel_associate_reconn=no (yes | no) parallel_associate_host=dan (character string, 8 char max.
Remote Administration multi_s3=112 multi_s4=112 multi_s5=112 multi_s6=112 multi_s7=112 multi_s8=112 (number (number (number (number (number (number in in in in in in range range range range range range 2 2 2 2 2 2 to to to to to to 123) 123) 123) 123) 123) 123) Terminal Parameters term_screen=color term_screen_enhanced=no term_keyboard=english term_screensaver=yes term_screensaver_delay=2 term_numlock=on term_capslock=on term_beep=long term_keydelay=mediun term_keyspeed=low term_language=english te
Remote Administration s%_associate_autoconn=yes s%_associate_reconn=yes s%_predefined_setup=ansi s%_screen_enhanced=no s%_screen_crlf=yes s%_screen_line=25 s%_screen_column=80 s%_screen_codepage=437 s%_screen_scroll=yes s%_screen_wrap=yes s%_screen_cursor=block s%_screen_overscan=09 s%_fctn_monitor=no s%_fctn_termprg=no s%_fctn_fctnbold=bold s%_fctn_endprn=\1B[4i s%_kbd_code=scancode s%_kbd_capsmode=caps-lock s%_kbd_localcompose=no s%_color_mode=yes s%_normal_foregrnd=lt-green s%_normal_backgrnd=black s%
Remote Administration s%_udk_f1= s%_udk_f2= s%_udk_f3= s%_udk_f4= s%_udk_f5= s%_udk_f6= s%_udk_f7= s%_udk_f8= s%_udk_f9= s%_udk_f10= s%_udk_f11= s%_udk_f12= s%_udk_f13= s%_udk_f14= s%_udk_f15= s%_udk_f16= s%_udk_f17= s%_udk_f18= s%_udk_f19= s%_udk_f20= s%_udk_f21= s%_udk_f22= s%_udk_f23= s%_udk_f24= s%_udk_f25= s%_udk_f26= s%_udk_f27= s%_udk_f28= s%_udk_f29= s%_udk_f30= s%_udk_f31= s%_udk_f32= s%_udk_f33= s%_udk_f34= s%_udk_f35= s%_udk_f36= s%_udk_f37= s%_udk_f38= s%_udk_f39= (character (character (charac
Remote Administration s%_udk_f40= s%_udk_f41= s%_udk_f42= s%_udk_f43= s%_udk_f44= s%_udk_f45= s%_udk_f46= s%_udk_f47= s%_udk_f48= s%_udk_ins= s%_udk_end= s%_udk_dn= s%_udk_pgdn= s%_udk_left= s%_udk_five= s%_udk_right= s%_udk_home= s%_udk_up= s%_udk_pgup= s%_udk_minus= s%_udk_plus= s%_udk_del= s%_udk_esc= s%_udk_dot= s%_udk_backspace= (character (character (character (character (character (character (character (character (character (character (character (character (character (character (character (characte
Remote Administration End of File The configuration file must be ended with the following trailer label: END_AX_SETUP If this trailer label is missing, from the configuration file used to set-up an AX3000, the fatal error message ERR 103 will be issued in response to the rcmd command and the default factory set-up will be reloaded.
Downloading Firmware - 11 DOWNLOADING FIRMWARE ________________________________________________________________ TCP/IP AXEL Platine Terminal 107
Downloading Firmware This feature may be used to upgrade TCP/IP AX3000 firmware over a network. Firmware can be downloaded, for example to add or improve AX3000 features or to add terminal emulations. IMPORTANT: firmware can only be downloaded to an AX3000 equipped with flash memory. On AX3000s not equipped with flash memory, the download options are not available within AX3000 Set-Up.
Downloading Firmware 11.1 - RCMD OVERVIEW The rcmd command allows remote access to a network node (the rcmd command is called rsh on some UNIX systems). The general syntax is: $ rcmd name keyword - name: peripheral name (listed in /etc/hosts). Some versions of UNIX also accept the IP address of the peripheral. - keyword: the operation to be performed. Note: to access an AX3000 via the rcmd command, its IP address must already be set.
Downloading Firmware Example 1: # rcmd ax3001 ax_download /usr/firm 192.168.1.249 Example 2: a router is used # rcmd ax3002 ax_download /usr/firm vangogh 192.168.1.249 Possible errors (displayed on the operator’s console): - ERR 105: invalid rcmd command: incorrect keyword (check the syntax). - ERR 108: invalid number of parameters: bad parameter number (2 or 3 parameters are required after the keyword). - ERR 109: invalid file length: the filename is too long (more than 31 characters).
Downloading Firmware 11.2.2 - Downloading Through Set-Up Enter TCP/IP Set-Up (< >) and select the 'Flash' menu. Within this menu, select the 'Download (tftp)' item. The following information must be entered in the four fields: - Filename: path and name of the firmware file, - AX3000 IP: this is an IP address only used during the downloading operation.
Downloading Firmware IMPORTANT: The AX3000 IP layer, used for the tftp protocol, does not handle the fragmentation/defragmentation process. Therefore, if a router fragments frames (mtu lower than 600 bytes), the AX3000 will not be able to perform the download. If any problems occur, refer to Section 11.4. 11.3 - DOWNLOADING BY BOOTP AND TFTP PROTOCOLS This procedure is divided into 2 steps: - bootp: asking for firmware file information, - tftp: downloading firmware file.
Downloading Firmware - ha: Ethernet address of the AX3000 - ip: IP address of the AX3000 (the address is only used during the downloading operation) - bf: firmware file name Examples of bootp configuration files: a) The AX3000 accesses the tftp host via a router .default:\ :hn:\ :df=/etc/bootpd.dump:\ :ht=ethernet:\ :sa=192.1.1.243 :to=auto: .net1:\ :tc=.default:\ :sm=255.255.255.000:\ :gw=192.168.1.252:\ axel1:\ :tc=.net1:\ :vm=rfc1048:\ :ha=00.A0.34.00.00.01:\ :ip=192.168.1.
Downloading Firmware b) The AX3000 and the tftp host belong to the same network .default:\ :hn:\ :df=/etc/bootpd.dump:\ :ht=ethernet:\ :sa=192.168.1.252 :to=auto: axel1:\ :tc=.default:\ :ha=00.A0.34.00.00.01:\ :ip=192.168.1.242:\ :bf=/tmp/axel: IMPORTANT: if a problem occurred during a previous download operation (whatever method was used), the firmware of the target AX3000 may have been erased.
Downloading Firmware The message 'Downloading in progress...' will be displayed on the operator console if downloading can be performed (AX3000 and tftp host reachable, firmware file found, etc.). A few seconds later, the target AX3000 will be automatically reset and the new firmware will be enabled. Note: during the downloading operation, additional messages will be displayed on the target AX3000 (see Section 11.3.2).
Downloading Firmware An automatic connection to the tftp host will then be established in order to download the firmware file (see previous chapter). If any problems occur, refer to the next chapter. 11.4 - IN CASE OF PROBLEMS This chapter discusses possible problems. The error list is not exhaustive ; if an unlisted error occurs, please contact your AXEL distributor. After an error, the AX3000 should be power-cycled. 11.4.
Downloading Firmware - xxx is the error number, - label is the error message. This label is sent by the tftp host and is generated by UNIX running on the tftp host. Possible errors: 1: File not found 2: Access violation 3: Disk full or allocation exceeded 4: Illegal TFTP operation 5: Unknown Transaction Identifier 6: File already exists 7: Illegal TFTP operation 0: User-defined error For more information, refer to UNIX manuals. Tftp AX3000 Errors: tftp errno: xxx - xxx is the error number.
Zone d'activité d'Orsay-Courtabœuf 16 Avenue du Québec - BP 728 91962 LES ULIS Cedex - France Tel.
