HP t1000 T1500/T1510 Windows-based Terminal Network Installation Guide - Page 20

for Class C IP addresses and 255.255.0.0 for Class B IP

Get HP t1000 - Terminal Thin Client PC PDF manuals and user guides View all HP t1000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 20 highlights

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 TFTP 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 file, the file can take 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:

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
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
TFTP 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
file, the file can take 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: