Internet Services on the HP e3000 consist of eight individual
services that enable the HP e3000 to communicate with other nodes
on an internetwork. The program and configuration files needed to
run Internet Services is part of the MPE/iX Fundamental Operating
Software. No separate software product is necessary to use Internet Services.
The services are briefly described in Table 1-1
Summary of HP e3000 Internet Services.
Summary of HP e3000 Internet Services
Table 1-1 Summary of HP e3000 Internet Services
Service
Description
inetd
The Internet daemoninetd is the master server for the group of Internet Services
rather than an individual network service. You must install and configure
inetd on your system to use the other services as listed below.
telnet
The telnet server uses the standard virtual terminal protocol to allow
users on a remote node that supports Internet Services to log on and run
most applications on the host HP e3000.
bootpd
The Bootstrap Protocol daemon, or bootpd, is used to boot, or
start, devices such as routers, printers, X-terminals and diskless
workstations. Client systems use bootpd to find their own IP
address and the name of the boot file to load into memory and
execute.
tftpd
The Trivial File Transfer Protocol daemon tftpd is used to
transfer the boot files needed to start network devices. In this
implementation of Internet Services, tftpd enables an HP e3000 to
boot network printers.
remsh
The remote shell client allows a user on an HP e3000 to access a remote
UNIX host and execute a UNIX command or script without logging on.
ftp
The File Transfer Protocol (FTP) is an ARPA service that allows users to
transfer files among other networked systems. FTP is the file transfer
program that uses the ARPA standard File Transfer Protocol. FTP can be used
with systems supporting the ARPA FTP service such as other HP systems,
UNIX systems, and non-UNIX systems.
Samba
Samba for MPE/iX is a suite of programs which allow clients to access a
server's file space and printers via the Server Message Block (SMB)
protocol. It allows the MPE/iX shell operating system to act as a file and
printer server for SMB clients, which are primarily, Windows NT, Windows 95
and Windows for Workgroups.
DNS
BIND (Berkeley Internet Name Domain) is an implementation of the Domain
Name System (DNS). A complete implementation of DNS BIND/iX is available on
MPE/iX. DNS BIND/iX will enable MPE/iX host to act as a DNS server, both
responding to queries as well as communicating with other DNS servers on
the local network and the Internet.
NOTE: Throughout this manual, the term
daemon, which is familiar to UNIX
users, and the term server are used
interchangeably.
System Requirements
The Internet Services program and configuration files come
with version C.55.00 or greater, of the MPE/iX Fundamental Operating
Software (FOS). (The exception to this is the Telnet Client, which
was made available to customers on the earlier version of MPE/iX,
C.50.00.) As part of MPE/iX FOS, Internet Services can run on any
Precision Architecture-RISC model of the HP e3000. They are not
available on earlier "classic" HP e3000 computers running MPE V.
To run Internet Services, you must:
Configure one or more network interface link cards that support
TCP/UDP/IP communications protocol.
Configure the Net Transport communications software which uses the
TCP/UDP/IP protocol.
The necessary software and at least one TCP/UDP/IP network interface
card is delivered with each PA-RISC HP e3000 system. Internet Services runs on
top of the Net Transport software and therefore runs over any type of link
supported by Net Transport.
Verifying Installation of Internet Services Files
If you have installed or updated to version C.60.00 of MPE/iX,
use the following steps to verify that the Internet Services files
exist on your system:
If necessary, log on the system as MANAGER.SYS.
Enter a LISTFILE command for the NET group of the SYS
account:
:LISTFILE @.NET.SYS
Check the list displayed on your screen and make sure that you
have the following files:
BOOTPD
BOOTPQRY
BPTABSMP
INETD
INSECSMP
INSVXL
JINETD
PROTSAMP
REMSH
SERVSAMP
TFTPD
Run the Node Manager Maintenance utility to verify that you have
successfully installed the set of Internet Services files (except for
Telnet files, which you will check in Chapter 3
Telnet Service)
:NMMAINT,73
You will see information similar to the following:
: nmmaint,73
NMS Maintenance Utility 32098-20014 B.00.09 (C) Hewlett Packard Co. 1984
WED, JUL 23, 1997, 11:08 AM Data comm products build version: N.55.15
Subsystem version ID's:
Internet Services for the HP e3000 module versions:
NM program file: INETD.NET.SYS Version: B0001003
NM program file: BOOTPD.NET.SYS Version: B0001003
NM program file: BOOTPQRY.NET.SYS Version: B0001002
NM program file: TFTPD.NET.SYS Version: B0001002
NM program file: REMSH.NET.SYS Version: B0001003
XL procedure: INSVXL_SECURE_VERS Version: B0001004
XL procedure: INSVXL_IPCSEC_VERS Version: B0001002
XL procedure: INSVXL_NSRW_VERS Version: B0001003
XL procedure: INSVXL_NETOF_VERS Version: B0001002
XL procedure: INSVXL_SYSLOG_VERS Version: B0001003
XL procedure: INSVXL_SIGNAL_VERS Version: B0001002
XL procedure: INSVXL_GETTIME_VERS Version: B0001003
Internet Services for the HP e3000 overall version = B.00.01
The final line of information, which displays the current overall
version of these software files, is useful when you need to call the
Hewlett-Packard support staff.
Check for any error messages, such as a module is missing, or a
message telling you of a version mismatch, for example:
Version levels differ in one or more modules. (NMERR 103)
Internet Services for the HP e3000 overall version = ?.??.??
Using Domain Name Resolver
To use the domain name resolver to resolve domain names to their IP addresses,
you will need to configure a set of ASCII files on each node that contain the
necessary information. Refer to the "Configuring the DNS Resolver" section of
this chapter, or the HP e3000/iX Network Planning and Configuration
Guide.
Sample Configuration Files
When you install or update to version C.60.00 of MPE/iX, a set of
sample configuration files is automatically copied to the NET
group of the SYS account for you. For example, INCNFSMP is
the name of the sample inetd configuration file. These files were
named and installed in this form to prevent overwriting any genuine
configuration files already in use.
To view the group of files installed in NET.SYS, enter:
:LISTFILE @.NET.SYS
To configure Internet Services, you will do one of two things:
If there are configuration files already in use, you will add the
information needed to use each of the Internet Services to those
files.
If you are not already using Internet Services configuration
files, you will use the sample configuration files that were
installed with the FOS as templates for your own set. In this case,
you will use the COPY command to create each of the
configuration files, then create a symbolic link from a file name in
the POSIX name space to the actual file, which exists in the MPE name
space. (Linking the files is explained next.) Finally, you will edit
the new configuration files to suit your needs.
Linking Configuration Files
The Internet Services software looks for some of its configuration
files in the POSIX name space and not in the MPE name space. For
example, it accesses the /etc directory and looks for the file named
inetd.conf to read inetd configuration data. It does not
look for the file INETDCNF.NET.SYS.
Rather than create two copies of the configuration file, one
for each name space, Hewlett-Packard recommends that you create
a symbolic link from a POSIX-named file to the MPE-named file. The instructions
in the remainder of this manual describe this process. Linking the
files, as opposed to making another copy of each one, offers three
important advantages.
Linking the file ensures consistency of content because regardless
of which name you use to access the file, you will be reading or
updating the same file.
Giving the file a name in each name space allows you to view the
file from either the POSIX or the MPE name space, but it is
recommended that you use an MPE text editor to make changes. This is
due to potential conflicts with the MPE/iX EOF marker if any lines
are added using a POSIX editor program.
Making the POSIX name point to the MPE name ensures that the file
will be backed up with standard MPE STORE procedures in case
you haven't modified your STORE command to back up new or
changed files in the POSIX name space.
Installed Configuration Files
If you install and configure all of the Internet Services according to the
instructions in this manual, you will have the set of files described in
Table 1-2 Configuration Files.
Table 1-2 Configuration Files
Sample name
MPE name space
HFS name space
Description
SERVSAMP.NET.SYS
SERVICES.NET.SYS
/etc/services
The services name file, which associates an official service name and
alias with the port number and
protocol that a service uses. You will edit the services file for each
new service you are adding to your system. The executing program uses
the file named SERVICES.NET.SYS.
PROTSAMP.NET.SYS
PROTOCOL.NET.SYS
/etc/protocols
The file containing a list of protocols known to the system and the
identification number and one or more aliases for each. You will
rarely, if ever, need to edit this file. The executing program uses the
file named PROTOCOL.NET.SYS.
INCNFSMP.NET.SYS
INETDCNF.NET.SYS
/etc/inetd.conf
The configuration file for the Internet daemon inetd, which
determines which installed Internet Services are available to users.
The executing program uses the file named
/etc/inetd.conf.
INSECSMP.NET.SYS
INETDSEC.NET.SYS
/usr/adm/inetd.sec
The optional security file for inetd, which lets you control
access to individual services by specific nodes. The executing program
uses the file named /usr/adm/inetd.sec.
BPTABSMP.NET.SYS
BOOTPTAB.NET.SYS
/etc/bootptab
The configuration file for the Bootstrap protocol daemon,
bootpd. The executing program uses the file named
/etc/bootptab.
For each individual service you install, you will always edit the
services file and the inetd configuration file. It is unlikely
that you will need to edit the protocols file. The remainder of this chapter
explains the services and protocols file.
Chapter 2 Internet Daemon explains working with
the inetd configuration files.