T1500/T1510
N
ETWORK INSTALLATION GUIDE
W
INDOWS-BASED TERMINAL
W
T1500/T1510
N
ETWORK INSTALLATION GUIDE
September 2000
INDOWS-BASED TERMINAL
ii
Notice
The information in this document is subject to change without notice.
COMPAQ COMPUTER CORPORATION SHALL NOT BE LIABLE FOR
TECHNICAL OR EDITORIAL ERRORS OR OMISSIONS CONTAINED HEREIN;
NOR FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES RESULTING FROM
THE FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL.
This document contains information protected by copyright. No part of this
document may be photocopied or reproduced in any form without prior written
consent from Compaq Computer Corporation.
© 2000 Compaq Computer Corporation. All rights reserved. Printed in Taiwan.
COMPAQ and the Compaq logo are registered in the U.S. Patent and Trademark
Office.
Product names mentioned herein may be trademarks and/or registered trademarks
of their respective companies.
Compaq T1500/T1510 Windows-based Terminal Reference Guide
Second Edition September 2000
Federal Communications Commission Notice
This equipment has been tested and found to comply with the limits for a Class B
digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to
provide reasonable protection against harmful interference in a residential
installation. This equipment generates, uses, and can radiate radio frequency
energy and, if not installed and used in accordance with the instructions, may
cause harmful interference to radio communications. However, there is no
guarantee that interference will not occur in a particular installation. If this
equipment does cause harmful interference to radio or television reception, which
can be determined by turning the equipment off and on, the user is encouraged to
try to correct the interference by one or more of the following measures:
• Reorient or relocate the receiving antenna.
• Increase the separation between the equipment and the receiver.
• Connect the equipment to an outlet on a circuit different from that to which the
receiver is connected.
• Consult the dealer or an experienced radio/TV technician for help.
iii
Modifications
The FCC requires the user to be notified that any changes or modifications made to
this device that are not expressly approved by Compaq Computer Corporation may
void the user’s authority to operate the equipment.
Cables
Connections to this device must be made with shielded cables with metallic RFI/
EMI connector hoods in order to maintain compliance with FCC Rules and
Regulations.
Canadian Notice
This Class B digital apparatus meets all requirements of the Canadian
Interference-Causi ng Equ ipmen t Regulations.
Avis Canadien
Cet appareil numérique de la classe B respecte toutes les exigneces du Réglement
sur le matériel brouilleu r du Canad a.
iv
European Union Notice
Products with the CE Marking comply with both the EMC Directive (89/336/EEC)
and the Low Voltage Directive (73/23/EEC) issued by the Commission of the
European Community.
Compliance with these directives implies conformity to the following European
Norms (in brackets are the equivalent international standards):
• EN55022 (CISPR 22) - Electromagnetic Interference
• EN50082-1 (IEC801-2, IEC801-3, IEC801-4) - Electromagnetic Immunity
• EN60950 (IEC950) - Product Safety
Japanese Notice
License Agreement
YOU SHOULD CAREFULLY READ THE FOLLOWING TERMS AND
CONDITIONS BEFORE USING THIS SOFTWARE (TOGETHER WITH ANY
SUPPLIED DOCUMENTATION, HEREAFTER “SOFTWARE”), WHICH IS
COPYRIGHTED BY LICENSOR. USING THIS SOFTWARE INDICATES YOUR
ACCEPTANCE OF THE FOLLOWING TERMS AND CONDITIONS.
Grant
You may use the Software in conjunction with Your hardware (Terminal). You have
the right to use this Software by loading it onto a computer containing the capability
of transferring the Software (in whole or in part) to Your Terminal. You may use the
Software in this fashion to as many times as is necessary , so long as such use is
always in conjunction with Your Terminal. You may transfer ownership of the
Terminal and equipment, including the right to use the Software to another party so
long as that party agrees to accept these terms and conditions.
v
Contro l No. 075C
YOU MAY NOT USE, COPY, MODIFY, TRANSLATE OR TRANSFER THE
SOFTWARE, OR MODIFICATION THEREOF, IN WHOLE OR IN PART, EXCEPT
AS EXPRESSLY PROVIDED FOR IN THIS LICENSE. YOU MAY NOT
DECOMPILE, REVERSE ENGINEER OR OTHERWISE DECODE OR ALTER
THE SOFTWARE.
Disclaimer of Warranty
The software is provided, “AS IS,” and is delivered with no warranties, either
express or implied .
LICENSOR MAKES AND YOU RECEIVE NO WARRANTIES ON THE
SOFTWARE, EXPRESS, IMPLIED, OR STATUTORY, OR IN ANY OTHER
PROVISION OF THIS AGREEMENT OR COMMUNICATION WITH YOU, AND
LICENSOR DISCLAIMS ANY IMPLIED WARRANTIES OF MERCHANTABILITY,
NON-INFRINGEMENT AND FITNESS FOR ANY PARTICULAR PURPOSE.
LICENSOR DOES NOT WARRANT THAT THE FUNCTIONS CONTAINED IN THE
PRODUCT WILL MEET YOUR REQUIREMENTS OR THAT THE OPERATION
WILL BE UNINTERRUPTED OR ERROR FREE.
SOME STATES DO NOT ALLOW LIMITATIONS ON HOW LONG AN IMPLIED
WARRANTY LASTS SO THE ABOVE LIMITATION MAY NOT APPLY TO YOU.
THIS WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS. YOU MAY ALSO
HAVE OTHER RIGHTS WHICH VARY FROM STATE TO STATE.
vi
Limit of Liability
UNDER NO CIRCUMSTANCES SHALL LICENSOR BE LIABLE FOR LOSS OF
DATA, COST OF COVER, OR ANY INCIDENTAL OR CONSEQUENTIAL
DAMAGES, HOWEV ER CA USED A ND ON ANY TH EOR Y OF LI ABIL ITY. TH ESE
LIMITATIONS SHALL APPLY EVEN IF LICENSOR OR ITS RESELLER HAS
BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND
NOTWITHSTANDING ANY FAILURE OF ESSENTIAL PURPOSE OF ANY
LIMITED REMEDY PROVIDED HEREIN.
YOU AGREE THAT THESE ARE THE ONLY APPLICABLE TERMS OF
AGREEMENT BETWEEN US COVERING SOFTWARE AND THAT THEY
SUPERSEDE ANY OTHER COMMUNICATIONS (ORAL OR WRITTEN)
BETWEEN US RELATING TO THE SOFTWARE.
Export Restrictions
You agree You will not export or transmit the Software to any country to which
export is restricted by applicable U.S. law or regulation without the written approval
of the appropriate U.S. Government organization.
U.S. Government Restricted Rights
The Software is provided with RESTRICTED RIGHTS. Use, duplication or
disclosure by the Government is subject to restrictions as set forth in subparagraph
(c)(1)(ii) of the Rights in Technological Data and computer software clause at
DFARS 252.227-7013 or in subparagraphs (c)(1) and (2) of the Commercial
Computer Software-Restricted Rights at 8 C.F.R. 52-227-19 as applicable.
Contents
Overview
Introduction xi
How to Use This Guide xi
References xi
DHCP/BOOTP xii
Time Server xii
SNMP xii
Other RFCs xii
1 Installation Overview and Planning
Overview of Installation Procedure 2
Planning Your Installation 3
Step 1. Complete Worksheets 3
Step 2. Configure Terminal Start-Up Resources 3
Step 3. Configure Optional Terminal Start-Up Resources 4
Step 4. Configure Server Application Resources 4
Step 5. Select Location of Browser 4
Step 6. Install CD Software onto the Server(s) 4
viii
2 Configuring Terminal Start-Up Resources
BOOTP 5
DHCP 8
T1500/T1510-Specific Option Definitions 13
Option 43 Vendor-Specific ID 13
NETSVC 13
NOSWAP 14
REFLASH 14
MF_DIR 14
MF_CFG 15
XFS 15
XDMCP 15
BUDDY_BOOT 15
Packet Size 16
Option Overload 16
Option 18 vs. Option 43 vs. Options 128+ 17
Option 18 17
Option 43 19
Options 128+ 19
TFTP 20
NFS 20
DNS 22
Time Server 22
3 Configuring Optional Terminal Start-Up Resources
Network Services 23
NFS 24
SMB 24
SNMP 25
HTTP (Help) 26
Serial Internet Connections 26
PPP 26
SLIP 26
CSLIP 27
FTP 27
HTTP (Upgrades) 27
4 Configuring Server Application Resources
HTTP 29
POP3/IMAP4 30
ICA 30
RSH (X Manager) 30
Secure Shell 32
5 Selecting Browser Location
Browser Location 35
Netscape Communicator Constraints 36
6 Installing CD Software onto the Server(s)
CD Contents 39
Running the Installation Program 39
Text-Mode Installation 43
GUI-Mode Installation 44
Installing on Non-Supported Servers 45
Appendices
A T1500/T1510 Windows-Based Terminal Quick-Start Guide
Quick-Start Procedure 48
“G-Key Reset” Procedure 49
ix
B Installation Planning Worksheets
Terminal Start-Up Resources Worksheet 53
Optional Terminal Start-up Resources Worksheet 54
Server Application Resources Worksheet 55
Browser Launch Location Resources Worksheet 56
Other Images Location Worksheet 57
Software Images from the CDROM Worksheet 58
List of Figures
2-1 Bootptab File Example 7
List of Tables
2-1 DHCP Options 10
2-2 Additional Vendor-Specific Options 12
2-3 Labels and Data for Text Format Option 17
5-1 Netscape Communicator Constraints 37
x
Overview
Introduction
This guide explains how to install software from the installation CD onto your server
and how to configure the resources resident on the server to support Compaq
T1500/T1510 Windows-Based Terminals for this software release.
How to Use This Guide
For full access to all the terminal resources, you will need to plan and configure
your server setup as explained in Chapter 1 of this guide.
If you want only to verify basic operation of the terminal using local boot, go directly
to the quick-start procedure in Appendix A. However, you will have only limited
access to the terminal resources.
Terminal setup information is available from help files resident on the terminals and
complete instructions are available on line after terminal-server communication is
established.
References
The following Requests for Comments (RFCs) should be reviewed:
Note
RFCs are freely available through the World-Wide
Web. They can be accessed from sites such as: http://
www.cis.ohio-state.edu/hypertext/information/rfc.html
xii
DHCP/BOOTP
RFC 1534 - Interoperation between DHCP and BOOTP
RFC 2131 - Dynamic Host Configuration Protocol
RFC 2132 - DHCP Options and BOOTP Vendor Extensions
Time Server
RFC 868 - Time Protocol
SNMP
RFC 1155 - Structure and Identification of Management Information for
TCP/IP-based Internets
RFC 1157 - A Simple Network Management Protocol (SNMP)
RFC 1212 - Concise MIB Definitions
RFC 1213 - Management Information Base for Network Management
of TCP/IP-based internets: MIB-II
Other RFCs
RFC 1350 -The TFTP Protocol (Revision 2)
RFC 1094 - NFS: Network File System Protocol Specification
RFC 1034 - Domain Names - Concepts and Facilities
RFC 1035 - Domain Names - Implementation and Specification
RFC 2616 - Hypertext Transfer Protocol - HTTP/1.1
RFC 2617 - HTTP Authentication: Basic and Digest Access Authentication
RFC 1548 - The Point-to-Point Protocol (PPP)
RFC 1055 - A Nonstandard for Transmission of IP Datagrams Over Serial Lines:
SLIP
RFC 1939 - Post Office Protocol - Version 3
RFC 821 - Simple Mail Transfer Protocol
1 Installation Overview and
Planning
This document describes how to install the T1500/T1510 software on the following
computer servers:
• SCO OpenServer 5.0.5
•SCO UnixWare 7
• Linux (both Slackware and Red Hat)
• Windows NT Server
•HP/UX
For technical support refer to the Compaq Technical Support telephone numbers
for your area.
Note
If you are operating in a local-boot environment and
already have a network configured, and if you will be
using the default help page and time server, you might
consider using the quick-start procedure in Appendix A
rather than this procedure. Otherwise, use this
advanced procedure.
Note
If prior-release terminals are running on your network,
be careful to avoid overwriting the prior-release files
when installing this version of software.
2 Chapter 1
Server resources can be provided from platforms other than the above-listed ones,
but Compaq has not certified other environments and can not be responsible for
any problems related to incorrectly configured servers. If you are going to operate
in a different server environment, read this entire document very carefully to
determine if there are any issues that you might need to resolve.
Overview of Installation Procedure
There are two major parts to the installation:
1. The first part is the configuration of the server resources necessary to use the
terminal.
2. The second part is the installation of software provided on the installation CD.
The installation scripts on the CD are used to perform the second part; they are not
used for the first part because software tools should already exist on your server to
configure the server resources.
Note
Because portions of the software installed from the CD
depend on certain server resources, it is recommended
that you configure the server resources first before
installing software from the CD.
This document provides all the steps necessary to configure a complete set of
server resources for use with the terminals for this software release. For most of
the resources, you should refer to the instructions and manual pages that come
with the server software and operating system running on your server. Where
special configuration information applies specifically to the terminals, this document
provides that information. Many servers provide tools to configure the various
network resources required, recommended, or requested for use with the
terminals.
Installation Overview and Planning 3
Planning Your Installation
The software installation procedure is broken down into 6 basic steps, including the
planning described in this chapter. The following brief descriptions of the basic
steps do not by themselves provide enough information for you to fill in the planning
worksheets presented in Appendix B of this document; you should also read the
chapters pertaining to the individual worksheets for full information. If you fill in the
worksheets and perform the procedures presented in Chapters 2 through 6 in
order, the installation should go smoothly.
Step 1. Complete Worksheets
The worksheets in Appendix B will help you determine which server resources
must be installed/configured for the planned installation. Each worksheet pertains
to one of the categories of network resources. Steps 2 through 6 below provide
brief summaries of the configuration process, and Chapters 2 through 6 provide
details pertaining to each corresponding step.
Note
Read the instructions presented in the chapter
pertaining to a worksheet before filling in the
worksheet. This will enable you to proceed smoothly
through the remaining steps of this procedure.
Step 2. Configure Terminal Start-Up Resources
There is a minimum set of server resources that must be configured for using a
T1500/T1510 Windows-Based Terminal. Some of the resources are required in a
network- boot environment, some are required in a local boot environment, and
others are strongly recommended for either environment.
Fill out the worksheet for Step 2 in Appendix B and use the instructions in Chapter
2 to configure terminal start-up resources.
4 Chapter 1
Step 3. Configure Optional Terminal Start-Up Resources
A set of resources independent of the individual applications on the terminal is
strongly recommended for ease of use of the system as a whole. Although these
resources are optional, providing them will speed up access of certain items,
provide enhanced diagnostic capabilities (for troubleshooting problems), provide
for swapping in a local-boot environment, provide for print spooling in a local-boot
environment, allow for remote administration of the terminal, provide for Internet (or
intranet) connections via a modem, and facilitate upgrading the terminal to future
revisions.
Fill out the worksheet for Step 3 in Appendix B and use the instructions in Chapter
3 to configure optional terminal start-up resources.
Step 4. Configure Server Application Resources
Some applications on the terminal require a server to be configured with services
that the applications must access to operate properly.
Fill out the worksheet for Step 4 in Appendix B and use the instructions in Chapter
4 to configure server application resources.
Step 5. Select Location of Browser
A set of resources must be configured based on your choice of browser access.
The choice should be based upon performance, features required, and
administrative costs. The terminal is capable of running browsers locally, from a
Windows Terminal Server (via the ICA protocol), and from a UNIX server (via the X
protocol).
Fill out the worksheet for Step 5 in Appendix B and use the instructions in Chapter
5 to select the location of the browser.
Step 6. Install CD Software onto the Server(s)
After the server resources are configured, you must install software from the
installation CD onto the server(s). You do not need to install all the software on the
CD on all the servers. You need only to install the portions that correspond to server
resources configured in steps 2 through 5 above, and they need to be installed on
only the individual servers providing the associated server resources.
Fill out the worksheets for Step 6 in Appendix B and use the instructions in Chapter
6 to install CD software onto the server(s).
2 Configuring Terminal
Start-Up Resources
Several network resources are either required or recommended for starting up the
terminal initially in a network-boot environment. The resources in this category use
the following 6 network protocols:
BOOTP NFS DHCP
DNS TFTP Time Server
A brief description of the resources and any special configuration requirements for
each protocol are provided in this chapter. Some resources (such as NFS) may
also be described in other chapters of this document.
BOOTP
BOOTP is a protocol used in a network-boot environment for providing all
information that the terminal needs to start with minimal functionality. Either
BOOTP or DHCP (described below) is required in a network-boot environment.
BOOTP is not used in local-boot environments.
Note
Since DHCP has mostly superseded BOOTP, it is
recommended that DHCP be used instead of BOOTP
for network boot.
Note
BOOTP is not currently supported by Microsoft NT,
although it is supported by Windows 2000.
6 Chapter 2
When booting in a network environment, BOOTP provides the terminal with the
following required information: the terminal’s IP address; the IP address of the
TF TP boot server; the pathname of the operating system file to be loaded using the
TFTP server; the NFS directory to use for the terminal’s root file system (including
NFS server IP address and pathname on that server); and a subnet mask (typically
255.255.255.0 for Class C IP addresses and 255.255.0.0 for Class B IP
addresses).
For network boot, the terminal should have the following pieces of information, but
they are not necessarily required for the terminal to function (depending upon your
network configuration). Recommended information includes a domain name,
domain name server(s) to provide name-to-IP address resolution (for other
terminals and/or computers), and gateway IP address (for allowing you to access
computers outside your subnet).
Note
Some BOOTP server implementations allow only 64
bytes of information, including identification overhead,
to be sent in a reply message. If the provided
information plus overhead exceeds this limit, the server
will truncate the reply message to fit within the limit,
with unpredictable results. SCO Openserver contains a
BOOTP server with this limitation. This has been
reported to SCO and may be fixed in a release of
Openserver after Release 5.0.5. Because of this
restriction, the T17 option (see below) may make it
necessary to put the terminal’s root directory off the
server’s root directory (can be via a symbolic link).
To use BOOTP, you must typically make one entry per terminal, with an identifying
tag and the terminal’s MAC address. Of the fields mentioned above, the only field
that must be unique for each terminal is the IP address field. Therefore, if using a
BOOTP server that stores data in the /etc/bootptab fi le, the file can tak e a
generic approach for all other fields and use the tc entry for each terminal to refer
back to that generic entry, as in the following example:
Configuring Terminal Start-Up Resources 7
Figure 2-1 Bootptab File Example
.c_terminal:ht=1:ds=132.237.1.42:gw=132.237.20.1:sm=255.255.255.0:\
:dn=xx.com:sa=132.237.20.2:hd=/tftpboot:bf=vmlinux:\
:T17=”132.237.20.2:/nwt/root”:
term1:ha=00800c123456:ip=132.237.20.5:tc=.c_terminal
term2:ha=00800c123457:ip=132.237.20.4:tc=.c_terminal
Legend:
bf = TFTP boot file
dn = domain name
ds = domain name servers (IP)
gw = gateways
ha = hardware address
hd = home directory
ht = hardware type
ip = host IP address
sa = TFTP server address
sm = subnet mask
tc = template host (points to similar host entry)
T17 = root path
The option used here for the NFS root directory is the T17 entry, which is of the
form IPADDR:/PATH. The IPADDR entry is the IP address of the NFS server and
PATH is the full pathname on that server to what will be the root directory of the
network boot directory tree. (The quotation marks are required in the T17 entry to
allow the colon in the option data to be passed as part of the data.)
Note
IMPORTANT! The addresses of servers that support
the terminal boot process must be specified by IP
address. This is because the name resolution function
is not operational until the system is completely loaded
and initialized.
8 Chapter 2
For non-Windows server platforms, bootp can be run either at boot or from inetd.
It is recommend that bootp be run from inetd, although with many terminals and
a stable environment (i.e., an unchanging list of terminals), it may be faster to run
via automatic start-up at server boot. Consult the manual pages for the bootp
program on your server platform. Linux uses bootpd, UnixWare uses in.bootpd,
Openserver uses bootpd, and HP/UX uses bootpd. On Linux and Openserver
platforms, the entry to look for in the file /etc/inetd.conf
(/etc/inet/inetd.conf on UnixWare) begins with bootps. On Linux, HP/UX,
and Openserver platforms, the table that describes what options to provide to what
terminals is /etc/bootptab (/etc/inet/bootptab on UnixWare). For more
information, refer to the server manual pages that discuss bootptab and bootpd.
DHCP
DHCP is a protocol that can be used in both local- and network-boot environments.
In local-boot environments, it can be used to reduce the amount of configuring that
must be done on a terminal-by-terminal basis. In network boot environments, it can
be used in the same manner as BOOTP (described above). For network boot, site
policy should dictate the use of BOOTP or DHCP for providing the terminal with its
boot information. In the database for DHCP, the terminal’s MAC address and IP
address are not normally used because all information typically will be provided for
all terminals and the DHCP server manages the IP addresses for all terminals at
run time.
Note
A Microsoft NT DHCP server can provide information
allowing a terminal to network boot, provided the TFTP
and NFS services are running on supported servers.
In a network-boot environment, all fields mentioned above for BOOTP should be
entered and the same explanations apply. There are currently no other special
requirements for configuring DHCP servers to provide information to the terminals.
The server and path are provided to terminals by the DHCP protocol. DHCP uses
options 66 and 67 defined in RFC 2132.
Configuring Terminal Start-Up Resources 9
In a local-boot environment, DHCP can provide a set of configuration parameters,
which reduces the need to configure the terminal’s Select | System | Setup |
Connectivity | Internet | DHCP dialog box. The default (out of the box)
configuration assumes DHCP provides all network configuration information. As
such, the fields mentioned above for BOOTP all apply , except that the TFTP server
(sa), TFTP boot file (bf), and Root directory (T17) are not used. Providing them in
a mixed (local- and network-boot) environment is acceptable, since they are
ignored completely in a locally booted terminal.
Boot Server (see on-line help), otherwise known as “Buddy Boot,” uses these
options to give preference to a server that provides these options, servers for use
with local boot should use these options with extreme caution, since it may prevent
Boot Server from working.
The terminal renegotiates address information based upon the server’s configured
value for the lease time. If lease time is set for an infinite lease, the terminal will not
renegotiate for a lease extension or a new IP address until the terminal is rebooted.
At reboot, the terminal will once again ask for an IP address and other configuration
information.
The terminal uses the DHCP options listed in Table 2-1. Future releases may
increase the size of the list. Some of the listed options are sent by the server and
others are sent by the client. Refer to the RFCs (listed in “References” in the
“Overview” chapter of this document) for usage.
Loading...