HP 3000 Manuals HP 3000 Manuals
An overview of the Internet Services
Internet Services on the HP 3000 consist of four individual services that
enable the HP 3000 to communicate with other nodes on an internetwork.
The program and configuration files needed to run Internet Services is
part of version C.55.00 of the MPE/iX Fundamental Operating Software. No
separate software product is necessary to use Internet Services.
The services are briefly described in the table below.
Table 1-1. Summary of HP 3000 Internet Services
---------------------------------------------------------------------------------------------
| | |
| Service | Description |
| | |
---------------------------------------------------------------------------------------------
| | |
| inetd | The Internet daemon inetd 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, telnet, bootpd and tftpd. |
| | |
---------------------------------------------------------------------------------------------
| | |
| 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 3000. |
| | |
---------------------------------------------------------------------------------------------
| | |
| 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 3000 to boot |
| | network printers. |
| | |
---------------------------------------------------------------------------------------------
There is a fifth Internet Service, the File Transfer Protocol, or FTP,
which is also available on HP 3000 systems but is not discussed in this
manual.
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 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 3000. They are not available on earlier "classic" HP 3000
computers running MPE V.
To run Internet Services, you must:
* install one or more network interface link cards that support
TCP/IP communications protocol.
* install the Net Transport communications software which uses the
TCP/IP protocol.
The necessary software and at least one TCP/IP network interface card is
delivered with each PA-RISC HP 3000 system. Internet Services runs on
top of the Net Transport software and therefore runs over any type of
link supported by Net Transport.
Verifying the installation of the Internet Services files
If you have installed or updated to version C.55.00 of MPE/iX, use the
following steps to verify that the Internet Services files exist on your
system:
1. If necessary, log on the system as MANAGER.SYS.
2. Enter a LISTFILE command for the NET group of the SYS account:
:LISTFILE @.NET.SYS
3. Check the list displayed on your screen and make sure that you
have the following files:
SERVSAMP INETD
PROTSAMP JINETD
INCNFSMP TFTPD
INSECSMP BOOTPD
BPTABSMP BOOTPQRY
INSVXL
4. 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.)
:NMMAINT,73
You will see information similar to the figure below.
___________________________________________________________________________________
| |
| |
| NMS Maintenance Utility 32098-20014 B.00.09 (C) Hewlett Packard Co. 1984 |
| |
| THU, JAN 18, 1996, 9:55 AM |
| Data comm products build version: N.55.08 |
| |
| Subsystem version ID's: |
| |
| |
| Internet Services for the HP3000 module versions: |
| |
| NM program file: INETD.NET.SYS Version: A0000002 |
| NM program file: BOOTPD.NET.SYS Version: A0000002 |
| NM program file: BOOTPQRY.NET.SYS Version: A0000002 |
| NM program file: TFTPD.NET.SYS Version: A0000002 |
| XL procedure: INSVXL_SECURE_VERS Version: A0000004 |
| XL procedure: INSVXL_IPCSEC_VERS Version: A0000002 |
| XL procedure: INSVXL_NSRW_VERS Version: A0000002 |
| XL procedure: INSVXL_NETOF_VERS Version: A0000002 |
| XL procedure: INSVXL_SYSLOG_VERS Version: A0000003 |
| XL procedure: INSVXL_SIGNAL_VERS Version: A0000002 |
| XL procedure: INSVXL_GETTIME_VERS Version: A0000003 |
| |
| Internet Services for the HP3000 overall version = A.00.00 |
| |
___________________________________________________________________________________
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.
5. 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)
NetWare for Unix for the HP3000 overall version = ?.??.??
Using the 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 HP 3000/iX Network
Planning and Configuration Guide.
The sample configuration files
When you install or update to version C.55.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:
:LISTF @.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 the 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 edit the
file either using a POSIX or an MPE editor program, whichever you
prefer.
* 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.
The 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 the table below.
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. |
| | | | |
-------------------------------------------------------------------------------------------------
Table 1-2. Configuration files (cont.)
-------------------------------------------------------------------------------------------------
| | | | |
| Sample name | MPE name space | HFS name space | Description |
| | | | |
-------------------------------------------------------------------------------------------------
| | | | |
| 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 explains working
with the inetd configuration files.