Open System Services NFS Management and Operations Guide

2. Install one of these NonStop TCP/IP subsystems:
• Install conventional NonStop TCP/IP by following the procedure in “Installing the
Conventional NonStop TCP/IP Subsystem” (page 37).
• Install NonStop TCP/IPv6 by following the procedures in the NonStop TCP/IPv6
Configuration and Management Manual for starting NonStop TCP/IPv6 in INET mode
and following the procedures for starting the TELNET and LISTNER applications.
• Install Parallel Library TCP/IP.
Configuring the TLAM Subsystem (D-Series RVUs)
To install and configure the TLAM subsystem on systems running D-series RVUs:
1. Use SYSGEN to install and configure the TLAM subsystem.
2. Run the subsystem manager (MLMAN) process by entering this TACL command:
MLMAN /OUT,NAME $ZLMG,NOWAIT, CPU primary-cpu / backup-cpu
3. After your Ethernet controller is configured, installed, and connected to a transceiver on the
subnetwork, use the HP Tandem Maintenance and Diagnostic System (TMDS) to verify that
the coaxial cable is properly connected and terminated. For details on testing communications
devices, see the TMDS Reference Manual.
4. Start the Ethernet line. For details on starting communications devices, see the TMDS Reference
Manual.
5. Use the following SCF command to test your TLAM configuration:
STATUS LINE $LAN1, DETAIL
6. Verify the update with this SCF command:
STATUS CONTROLLER $LAN1, DETAIL
7. Document the TLAM controller (MAC address) in the Comment Section of your HOSTS file.
This SCF command returns the MAC address:
INFO SERVICE line-object-name.#service-object-name
Configuring the SLSA Subsystem
The ServerNet LAN Systems Access (SLSA) subsystem is preconfigured and installed on NonStop
servers (except servers running D-series RVUs) and is started during the system-load sequence. For
more information about installing and configuring the SLSA subsystem, see the LAN Configuration
and Management Manual.
Installing the Conventional NonStop TCP/IP Subsystem
To install and configure conventional NonStop TCP/IP:
1. Create configuration startup (OBEY) command files containing TACL and SCF commands to
perform the steps required to start the NonStop TCP/IP subsystem. See the TCP/IP configuration
and management manual appropriate to your system for information on startup files.
2. Edit the NonStop TCP/IP data files to configure your Internet environment.
NonStop TCP/IP performs name-to-address translation in one of two ways:
• By default, the file $SYSTEM.ZTCPIP.RESCONF is used for the domain name resolver
parameter file. Alternatively, the domain name resolver parameter file is the one specified
by the DEFINE =TCPIP^RESOLVER^NAME.
• The file specified by the DEFINE =TCPIP^HOST^FILE is used as the host file.
The configuration files are described in the TCP/IP configuration and management
manuals.
NOTE: HOSTID must be set to the host IP address, or RPC services in OSS NFS will not
work.
Planning the Configuration 37