HP TCP/IP Services for OpenVMS
Installation and Configuration
Previous Contents Index

Appendix A
Sample New TCP/IP Services Installation and Configuration

This appendix shows a sample installation and configuration of the TCP/IP Services product on a system on which the product has never been installed.

A.1 Sample New Installation Procedure

The following example shows a sample installation dialog for the TCP/IP Services. In this example, the installation takes place on a system where the product has not been installed. If TCP/IP Services had been installed previously on the system, the installation dialog would differ slightly (see Chapter 2).

Note
The symbols xx in the following example represent the product's two-digit update version number. 


Choose one or more items from the menu separated by commas: 1 
 
The following product has been selected: 
    DEC AXPVMS TCPIP V5.4-xx               Layered Product 
 
Do you want to continue? [YES] [Return]
 
Configuration phase starting ... 
 
You will be asked to choose options, if any, for each selected product and for 
any products that may be installed to satisfy software dependency requirements. 
 
DEC AXPVMS TCPIP V5.4-xx: HP TCP/IP Services for OpenVMS. 
 
    Copyright 1976, 2003 Hewlett-Packard Development Company, L.P. 
 
    Hewlett-Packard Development Company, L.P. 
 
    HP TCP/IP Services for OpenVMS offers several license options. 
 
Do you want the defaults for all options? [YES] [Return]
 
Do you want to review the options? [NO] [Return]
 
Execution phase starting ... 
 
The following product will be installed to destination: 
    DEC AXPVMS TCPIP V5.4-xx             DISK$ALPHASYS:[VMS$COMMON.] 
 
 
Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90% 
%PCSI-I-PRCOUTPUT, output from subprocess follows ... 
% TCPIP-W-PCSI_INSTALL 
% - Execute SYS$MANAGER:TCPIP$CONFIG.COM to proceed with configuration of 
%   HP TCP/IP Services. 
% 
 
Portion done: 100% 
 
The following product has been installed: 
    DEC VAXVMS TCPIP V5.4-xx               Layered Product 
 
DEC VAXVMS TCPIP T5.4-xx: HP TCP/IP Services for OpenVMS. 
 
    Check the release notes for current status of the product. 
 
$

A.2 Sample New Configuration Procedure

The following example shows a sample configuration dialog for the TCP/IP Services, in which the following components are configured:

In this example, the configuration takes place on a system where the product has never been configured. If TCP/IP Services had been configured previously on the system, the dialog would differ significantly (see Chapter 3). 


 
  TCP/IP Network Configuration Procedure 
 
This procedure helps you define the parameters required 
to run HP TCP/IP Services for OpenVMS on this system. 
 
Checking TCP/IP Services for OpenVMS configuration database files. 
 
Creating SYS$COMMON:[SYSEXE]TCPIP$SERVICE.DAT 
Creating SYS$COMMON:[SYSEXE]TCPIP$HOST.DAT 
Creating SYS$COMMON:[SYSEXE]TCPIP$NETWORK.DAT 
Creating SYS$COMMON:[SYSEXE]TCPIP$ROUTE.DAT 
Creating SYS$COMMON:[SYSEXE]TCPIP$PROXY.DAT 
Creating SYS$COMMON:[SYSEXE]TCPIP$CONFIGURATION.DAT 
 
HP TCP/IP Services for OpenVMS requires a definition for at 
least one interface.  There are no interfaces defined on this 
system. 
 
Please select the Interface option from the Core Environment Menu. 
 
  HP TCP/IP Services for OpenVMS Configuration Menu 
 
  Configuration options: 
 
       1  -  Core environment 
       2  -  Client components   
       3  -  Server components   
       4  -  Optional components 
 
       5  -  Shutdown HP TCP/IP Services for OpenVMS 
       6  -  Startup HP TCP/IP Services for OpenVMS 
       7  -  Run tests 
 
       A  -  Configure options 1 - 4 
      [E] -  Exit configuration procedure 
 
Enter configuration option: 1 [Return]
 
  HP TCP/IP Services for OpenVMS Core Environment Configuration Menu 
 
  Configuration options: 
 
       1  -  Domain                
       2  -  Interfaces 
       3  -  Routing               
       4  -  BIND Resolver         
       5  -  Time Zone 
 
       A  -  Configure options 1 - 5 
      [E] -  Exit menu 
 
Enter configuration option: A [Return]
 
DOMAIN Configuration 
 
Enter Internet domain: acme.com 
 
INTERFACE Configuration 
 
 
  The Ethernet device(s) on your system are: EWA0:  * Not Configured * 
 
  Start of configuration questions for Internet interface WE0. 
 
  WE0 is the Ethernet device ESA0: 
 
  WE0 has not been configured 
 
  HP TCP/IP Services for OpenVMS Interface WE0 Configuration Menu 
 
    Configuration options: 
 
         1  -  Configure interface manually       
         2  -  Let DHCP configure interface       
 
        [E] -  Exit menu (Do not configure interface WE0) 
 
Enter configuration option: 1 [Return]
Enter fully qualified host name: HEARTS.BUDGET.ACME.COM [Return]
Enter Internet address: 10.0.2.4 [Return]
Enter Internet network mask for hearts [255.0.1.0]: 255.1.12.1[Return]
Enter broadcast mask for hearts [10.0.2.255]: [Return]
 
    The following parameters will be used to define the 
    Internet interface WE0: 
 
      Host name:         hearts 
      Internet address:  10.0.2.4 
      Network mask:      255.0.0.0 
      Broadcast mask:    10.0.2.255 
 
 * Is the above correct [YES]: [Return]
 
                           failSAFE IP 
 
        failSAFE IP uses  multiple Network Interface Controllers 
        (NICs)  to provide  high availability  of IP  addresses. 
        In  the  event  of   a  NIC  failure,  (e.g.  any  event 
        preventing  the   NIC  from  receiving   data),  all  IP 
        addresses associated with  the failed NIC are reassigned 
        to a preconfigured failover target. 
 
        In  a  cluster  configuration,  the IP  address  may  be 
        preconfigured  on  NICs across  other  cluster  members. 
        This provides cluster-wide failover for the IP address. 
 
        See the management guide for more configuration options. 
        You  will be  asked what  other NICs on  this node  will 
        act as failover targets. 
 
* Configure failover target for failSAFE IP [NO]: [Return]
 
        End of configuration questions for Internet interface WE0 
  
 
DYNAMIC ROUTING Configuration 
 
 
     Dynamic routing has not been configured. 
 
     You may configure dynamic ROUTED or GATED routing. 
     You cannot enable both at the same time.  If you want 
     to change from one to the other, you must disable the 
     current routing first, then enable the desired routing. 
 
     If you enable dynamic ROUTED routing, this host will use the 
     Routing Information Protocol (RIP) - Version 1 to listen 
     for all dynamic routing information coming from other 
     hosts to update its internal routing tables. 
     It will also supply its own Internet addresses to 
     routing requests made from remote hosts. 
 
     If you enable dynamic GATED routing, you will be able to 
     configure this host to use any combination of the following 
     routing protocols to exchange dynamic routing information 
     with other hosts on the network: 
        Routing Information Protocol (RIP) - Version 1 & 2 
        Router Discovery Protocol (RDISC) 
        Open Shortest Path First (OSPF) 
        Exterior Gateway Protocol (EGP) 
        Border Gateway Protocol (BGP-4) 
        Static routes 
 
* Do you want to configure dynamic ROUTED or GATED routing [NO]:[Return]
 
        A default route has not been configured. 
* Do you want to configure a default route [YES]: [Return]
Enter your Default Gateway host name or address: GATE1.BUDGET.ACME.COM 
 
      gate1.budget.acme.com is not in the local host database. 
  
Enter Internet address for gate1.budget.acme.com: 10.0.2.66 
 
BIND RESOLVER Configuration 
 
 A BIND resolver has not been configured. 
 
 HP TCP/IP Services for OpenVMS supports the Berkeley Internet Name 
 Domain (BIND) resolver.  BIND is a network service that enables clients 
 to name resources or objects and share information with other objects 
 on the network. 
 
 Before configuring your system as a BIND resolver, you should 
 first be sure that there is at least one system on the network 
 configured as either a BIND primary or secondary server for 
 this domain. 
 
 You can specify a BIND server by its address or name; 
 however, if specified by name, an entry for it must 
 exist in the TCPIP$HOST database. 
 
 You will be asked one question for each server. 
 Press Return at the prompt to terminate the list. 
 
Enter your BIND server name: NUMB9.BUDGET.ACME.COM [Return]
 
   numb9.budget.acme.com is not in the local host database. 
 
Enter Internet address for numb9.budget.acme.com: 10.0.2.11 
Enter your BIND server name: [Return]
 
 Creating file TCPIP$ETC:IPNODES.DAT 
 Creating file TCPIP$ETC:SERVICES.DAT 
 
   TCPIP uses timezone information provided by the OpenVMS Operating 
   System. No additonal timezone configuration is needed for TCPIP 
   when the operating system is configured correctly. 
 
   This section verifies the current OpenVMS timezone configuration. 
   A warning message (TCPIP-W-) indicates that corrective action should 
   be taken. TCPIP will appear to operate but components may display 
   either the wrong time or a time inconsistent with other applications. 
 
%TCPIP-I-INFO, Logical name SYS$TIMEZONE_RULE found. 
-TCPIP-I-INFO, Software for automatic Summer/Winter time (TDF) change 
-TCPIP-I-INFO, is present. 
-TCPIP-I-INFO, Further action to ensure TDF change is not necessary. 
 
%TCPIP-I-NORMAL, timezone information verified 
 
Press Return to continue ... [Return]
 
 
  HP TCP/IP Services for OpenVMS Core Environment Configuration Menu 
 
  Configuration options: 
 
       1  -  Domain                
       2  -  Interfaces 
       3  -  Routing               
       4  -  BIND Resolver         
       5  -  Time Zone 
 
       A  -  Configure options 1 - 5 
      [E] -  Exit menu 
 
Enter configuration option: [Return]
 
    HP TCP/IP Services for OpenVMS Configuration Menu 
 
    Configuration options: 
 
         1  -  Core environment 
         2  -  Client components   
         3  -  Server components   
         4  -  Optional components 
 
         5  -  Shutdown HP TCP/IP Services for OpenVMS 
         6  -  Startup HP TCP/IP Services for OpenVMS 
         7  -  Run tests 
 
         A  -  Configure options 1 - 4 
        [E] -  Exit configuration procedure 
 
Enter configuration option: 2 [Return]
 
    HP TCP/IP Services for OpenVMS Client Components Configuration Menu 
 
    Configuration options: 
 
         1  -  DHCP Client      Disabled Stopped 
         2  -  FTP Client       Disabled Stopped 
         3  -  NFS Client       Disabled Stopped 
         4  -  REXEC and RSH    Disabled Stopped 
         5  -  RLOGIN           Disabled Stopped 
         6  -  SMTP             Disabled Stopped 
         7  -  SSH Client       Disabled Stopped 
         8  -  TELNET           Disabled Stopped 
         9  -  TELNETSYM        Disabled Stopped 
 
         A  -  Configure options 1 - 9 
        [E] -  Exit menu 
 
 
Enter configuration option: 8 [Return]
 
 
TELNET Configuration 
 
Service is not defined in the TCPIP$SERVICE database. 
Service is not enabled. 
Service is stopped. 
 
    TELNET configuration options: 
 
         1 - Enable service on this node 
 
        [E] - Exit TELNET configuration 
 
Enter configuration option: 1 [Return]
Creating TELNET Service Entry 
 
    HP TCP/IP Services for OpenVMS Client Components Configuration Menu 
 
    Configuration options: 
 
         1  -  DHCP Client      Disabled Stopped 
         2  -  FTP Client       Disabled Stopped 
         3  -  NFS Client       Disabled Stopped 
         4  -  REXEC and RSH    Disabled Stopped 
         5  -  RLOGIN           Disabled Stopped 
         6  -  SMTP             Disabled Stopped 
         7  -  SSH Client       Disabled Stopped 
         8  -  TELNET           Disabled Stopped 
         9  -  TELNETSYM        Disabled Stopped 
 
         A  -  Configure options 1 - 9 
        [E] -  Exit menu 
  
Enter configuration option: [Return]
 
    HP TCP/IP Services for OpenVMS Configuration Menu 
 
    Configuration options: 
 
         1  -  Core environment 
         2  -  Client components   
         3  -  Server components   
         4  -  Optional components 
 
         5  -  Shutdown HP TCP/IP Services for OpenVMS 
         6  -  Startup HP TCP/IP Services for OpenVMS 
         7  -  Run tests 
 
         A  -  Configure options 1 - 4 
        [E] -  Exit configuration procedure 
 
Enter configuration option: 3 [Return]
 
 
HP TCP/IP Services for OpenVMS Server Components Configuration Menu 
 
  Configuration options: 
 
  1 - BIND         Disabled Stopped    12 - NTP         Disabled Stopped 
  2 - BOOTP        Disabled Stopped    13 - PC-NFS      Disabled Stopped 
  3 - DHCP         Disabled Stopped    14 - POP         Disabled Stopped 
  4 - FINGER       Disabled Stopped    15 - PORTMAPPER  Disabled Stopped 
  5 - FTP          Disabled Stopped    16 - RLOGIN      Enabled  Stopped 
  6 - IMAP         Disabled Stopped    17 - RMT         Disabled Stopped 
  7 - LBROKER      Disabled Stopped    18 - SNMP        Disabled Stopped 
  8 - LPR/LPD      Disabled Stopped    19 - SSH         Disabled Stopped 
  9 - METRIC       Disabled Stopped    20 - TELNET      Enabled  Stopped 
 10 - NFS          Disabled Stopped    21 - TFTP        Disabled Stopped 
 11 - LOCKD/STATD  Disabled Stopped    22 - XDM         Disabled Stopped 
 
 
  A  -  Configure options 1 - 22 
 [E] -  Exit menu 
 
Enter configuration option: 5 [Return]
 
 
FTP Configuration 
 
Service is not defined in the SYSUAF. 
Service is not defined in the TCPIP$SERVICE database. 
Service is not enabled. 
Service is stopped. 
 
    FTP configuration options: 
 
         1 - Enable service on this node 
 
        [E] - Exit FTP configuration 
 
Enter configuration option: 1 [Return]
 
The FTP CLIENT is enabled. 
 
* Do you want to configure FTP CLIENT [NO]: [Return]
 
HP TCP/IP Services for OpenVMS Server Components Configuration Menu 
 
  Configuration options: 
 
  1 - BIND         Disabled Stopped    12 - NTP         Disabled Stopped 
  2 - BOOTP        Disabled Stopped    13 - PC-NFS      Disabled Stopped 
  3 - DHCP         Disabled Stopped    14 - POP         Disabled Stopped 
  4 - FINGER       Disabled Stopped    15 - PORTMAPPER  Disabled Stopped 
  5 - FTP          Enabled  Stopped    16 - RLOGIN      Enabled  Stopped 
  6 - IMAP         Disabled Stopped    17 - RMT         Disabled Stopped 
  7 - LBROKER      Disabled Stopped    18 - SNMP        Disabled Stopped 
  8 - LPR/LPD      Disabled Stopped    19 - SSH         Disabled Stopped 
  9 - METRIC       Disabled Stopped    20 - TELNET      Enabled  Stopped 
 10 - NFS          Disabled Stopped    21 - TFTP        Disabled Stopped 
 11 - LOCKD/STATD  Disabled Stopped    22 - XDM         Disabled Stopped 
 
 
  A  -  Configure options 1 - 22 
 [E] -  Exit menu 
 
 Enter configuration option: [Return]
 
 
    HP TCP/IP Services for OpenVMS Configuration Menu 
 
    Configuration options: 
 
         1  -  Core environment 
         2  -  Client components   
         3  -  Server components   
         4  -  Optional components 
 
         5  -  Shutdown HP TCP/IP Services for OpenVMS 
         6  -  Startup HP TCP/IP Services for OpenVMS 
         7  -  Run tests 
 
         A  -  Configure options 1 - 4 
        [E] -  Exit configuration procedure 
 
Enter configuration option: 6 [Return]
 
Begin Startup... 
 
%TCPIP-I-INFO, TCP/IP Services startup beginning at 5-SEP-2003 13:22:27 
.82 
%TCPIP-I-NORMAL, timezone information verified 
%RUN-S-PROC_ID, identification of created process is 00000058 
%TCPIP-I-SETLOCAL, setting domain and/or local host 
%TCPIP-I-STARTCOMM, starting communication 
%TCPIP-I-SETPROTP, setting protocol parameters 
%TCPIP-I-DEFINTE, defining interfaces 
%TCPIP-I-STARTNAME, starting name service 
%TCPIP-S-STARTDONE, TCP/IP Kernel startup completed 
%TCPIP-I-PROXYLOADED, loaded 0 NFS proxy records 
%TCPIP-I-LOADSERV, loading TCPIP server proxy information 
%TCPIP-I-SERVLOADED, auxiliary server loaded with 0 proxy records 
-TCPIP-I-SERVSKIP, skipped 0 communication proxy records 
-TCPIP-I-SERVTOTAL, total of 0 proxy records read 
%TCPIP-S-STARTDONE, TCPIP$PROXY startup completed 
%TCPIP-S-STARTDONE, TCPIP$FTP startup completed 
%TCPIP-S-STARTDONE, TCPIP$INET_DRIVER startup completed 
%TCPIP-I-NOMAP, no filesystem mapping information available 
%TCPIP-S-STARTDONE, TCPIP$RLOGIN startup completed 
%TCPIP-S-STARTDONE, TCPIP$TELNET startup completed 
%TCPIP-S-STARTDONE, TCP/IP Services startup completed at 5-SEP-2003 13: 
23:00.49 
 
Startup request completed. 
Press Return to continue ...

Index Contents