HP OpenVMS Systems Documentation

HP TCP/IP Services for OpenVMS
Installation and Configuration

Contents

Index

4.2 Configuring an IPv6 Router

To configure your system as an IPv6 router, follow the steps provided in this section.

Invoke the TCPIP$IP6_SETUP.COM configuration procedure by entering the following command:
$ @SYS$MANAGER:TCPIP$IP6_SETUP
The procedure displays information about the IPv6 network configuration procedure and tells you that you can configure the system as either an IPv6 host or an IPv6 router.
Choose to configure the system as an IPv6 router by entering YES at the following prompt:
Configure this system as an IPv6 router? [NO]:
Indicate whether you want to configure a 6to4 interface:
Configure a 6to4 interface? [NO]:
A 6to4 interface is needed to configure a border router. If you do not want to configure a 6to4 interface, press Enter. The configuration procedure continues at step 7.
If you want to configure a 6to4 interface, enter YES. The configuration procedure then displays the 6to4 tunnel interface:
The 6to4 tunnel is: TN1
You are prompted to enter information about the interface in subsequent steps.
Enter the node's IPv4 address in response to the following prompt:
Enter this node's IPv4 address to use when generating your site's 6to4 prefix:
Enter the IPv4 address in dotted-decimal format (d.d.d.d). The configuration procedure automatically generates a 6to4 site prefix based on the IPv4 address entered, and displays the prefix as in the following example:
Your 6to4 site prefix is: 2002:x:x::/48
This site prefix is advertised to hosts on the interfaces attached to the IPv6 site. This address must be a valid, globally unique IPv4 address configured on the router's interface to the IPv4 network.
The configuration procedure asks whether you want this system to function as a 6to4 relay router:
Configure a 6to4 relay router? [NO]:
If hosts in this border router's 6to4 site need to communicate with native IPv6 sites (IPv6 only), configure this system as a 6to4 relay router. Enter YES.
If you do not want the system to function as a 6to4 relay router, press Enter. The configuration procedure continues at step 7.
Specify the address of a relay router:
Enter 6to4 address of a 6to4 relay router [2002:C058:6301::]:
The address of the default relay router is displayed. To use the default, press Enter. Otherwise, enter the 6to4 unicast address of a 6to4 relay router.
For each interface on your system, the procedure asks whether you want to enable IPv6 on that interface, as in the following example, where ddn is the interface name (such as WE0):
Enable IPv6 on interface ddn [YES]?
If you want to enable IPv6 on this interface, press Enter; if not, enter NO.
For each interface on your system, the configuration procedure repeats steps 7 through 9.
Indicate whether you want the router to run the RIPng protocol on the designated interface:
Enable RIPng on interface ddn? [YES]:
The RIPng protocol allows this router to exhange IPv6 routes with other routers. If you want the router to run the RIPng protocol, press Enter; otherwise, enter NO.
The configuration procedure asks whether you want the router to advertise an IPv6 address prefix on the designated interface:
Enter an address prefix to advertise on interface ddn [DONE]:
If you want the router to advertise an IPv6 address prefix, enter a 64-bit address prefix for the interface. You can configure multiple address prefixes for this interface. You are prompted for additional address prefixes until you enter DONE.
If you do not want the router to advertise an IPv6 address prefix on the designated interface, enter DONE.
Indicate whether you want to configure an automatic tunnel:
Configure an IPv6 over IPv4 automatic tunnel interface? [NO]:
If you do not want to configure an automatic tunnel, press Enter. The configuration procedure continues at step 12.
If you want to configure an automatic tunnel, enter YES; the procedure displays the automatic tunnel interface as in the following example, and in the next step prompts you for the tunnel's address.
The automatic tunnel is: TN0
Note
Because of potential IPv4-compatible address routing problems, HP recommends that you avoid using automatic tunnels.
Enter the IPv4 address to use when constructing the automatic tunnel's endpoint:
Enter the IPv4 address to use when creating your automatic tunnel:
Enter the IPv4 address in dotted-decimal format (d.d.d.d).
The configuration procedure asks whether you want to create an IPv6-over-IPv4 configured tunnel:
Create IPv6 over IPv4 configured tunnels? [NO]:
If you want to create an IPv6-over-IPv4 configured tunnel, enter YES. You are prompted for information about this tunnel in subsequent steps.
If you do not want to create an IPv6-over-IPv4 configured tunnel, press Enter; the procedure continues at step 18.
Enter the tunnel's source IPv4 address:
Enter the source IPv4 address of tunnel ITn:
Enter the tunnel's source IPv4 address in the dotted-decimal format (d.d.d.d).
Enter the tunnel's destination IPv4 address in response to the following prompt:
Enter the destination IPv4 address of tunnel ITn:
Enter an IPv4 address in dotted-decimal format d.d.d.d. The tunnel's destination address must differ from the source address entered in step 13.
Indicate whether you want to enable the RIPng protocol:
Enable RIPng on interface ITn? [YES]:
The RIPng protocol allows this router to exchange IPv6 routes with other routers. If you want to enable the RIPng protocol on the tunnel interface, press Enter; if you do not, enter NO.
Indicate whether you want the router to advertise an IPv6 address prefix on the tunnel interface:
Enter an address prefix to advertise on interface ITn? [DONE]:
If you want the router to advertise an IPv6 address prefix, enter a 64-bit address prefix for the designated interface. You can configure multiple address prefixes for this interface. You are prompted for additional address prefixes until you enter DONE.
If you do not want the router to use an IPv6 address prefix on the tunnel interface, enter DONE.
The configuration procedure asks whether you want to create another IPv6-over-IPv4 configured tunnel:
Create another IPv6 over IPv4 configured tunnel? [NO]:
If you want to create another IPv6-over-IPv4 configured tunnel, enter YES. The procedure repeats steps 13 through 16 for each additional configured tunnel you choose to create.
If you do not want to create another IPv6-over-IPv4 configured tunnel, press Enter.
The procedure asks whether you want to create an IPv6-over-IPv6 configured tunnel:
Create IPv6 over IPv6 configured tunnels? [NO]:
If you want to create an IPv6-over-IPv6 configured tunnel, enter YES. You are prompted to enter information about this tunnel in subsequent steps.
If you do not want to create an IPv6-over-IPv6 configured tunnel, press Enter; the configuration procedure continues at step 24.
Enter the tunnel's source IPv6 address in response to the following prompt:
Enter the source IPv6 address of tunnel ITn:
Enter the tunnel's source IPv6 address in the dotted-decimal format (d.d.d.d).
Enter the IPv6-over-IPv6 tunnel's destination IPv6 address in response to the following prompt:
Enter the destination IPv6 address of tunnel ITn:
Enter an IPv6 address in dotted-decimal format d.d.d.d. The tunnel's destination address must differ from the source address entered in step 19.
Indicate whether you want to enable the RIPng protocol on the interface:
Enable RIPng on interface ITn? [YES]:
The RIPng protocol allows this router to exchange IPv6 routes with other routers. Press Enter if you want to enable the RIPng protocol on this interface; enter NO if you do not.
Indicate whether you want the router to advertise an IPv6 address prefix on the tunnel interface:
Enter an address prefix to advertise on interface ITn? [DONE]:
If you want the router to advertise an IPv6 address prefix, enter a 64-bit address prefix for the designated interface. You can configure multiple address prefixes for this interface. You are prompted for additional address prefixes until you enter DONE.
If you do not want the router to use an IPv6 address prefix on the tunnel interface, enter DONE.
You are asked whether you want to create another IPv6-over-IPv6 configured tunnel:
Create another IPv6 over IPv6 configured tunnel? [NO]:
If you want to create another IPv6-over-IPv6 configured tunnel, enter YES. The procedure repeats steps 19 through 22 for each additional configured tunnel you choose to create.
If you do not want to create another IPv6-over-IPv6 configured tunnel, press Enter.
Indicate whether you want to define manual routes to an adjacent router or remote IPv6 network:
Configure manual IPv6 routes? [NO]?
If you want to define a manual IPv6 route, enter YES. In subsequent steps, the procedure asks you to specify information for that route.
If you do not want to define manual routes, enter NO; the procedure continues at step 29.
Enter an address prefix of a destination IPv6 network:
Enter the destination network address prefix:
Enter the address prefix of the destination IPv6 network, or enter DEFAULT for the default route.
Enter the name of the interface through which you will send traffic to the remote IPv6 network:
Enter interface to use when forwarding messages:
The procedure asks you to enter the link-local IPv6 address of the first router in the path to the destination network. This address along with the IPv6 address prefix constitute the static routing table entry.
Enter the next node's IPv6 address:
If the next node is on the same link as this node or is reachable through a configured tunnel, enter the link-local address. If the next node is reachable through an automatic tunnel, enter the IPv4-compatible IPv6 address. For all other connections, enter the IPv6 address.
Indicate whether you want to configure another manual IPv6 route to an adjacent router or remote IPv6 network:
Configure another manual IPv6 route? [NO]:
If you want to configure another manual route, enter YES. The configuration procedure repeats steps 25 through 27 for each additional manual IPv6 route you choose to configure. If you do not want to configure another manual route, press Enter.

At this point, the configuration procedure displays a summary of your new IPv6 router configuration, as shown in the following example:

        You configured this node as an IPv6 router with the
        following:

    Daemons:

      IP6RTRD

    Interfaces:

      WE0       RIP Enabled
      IT0       RIP Enabled
                Tunnel Source ::1
                Tunnel Destination ::2
                Prefix AAAA::/64
                Prefix BBBB::/64
      TN1       6to4 Tunneling Enabled using 1.2.3.4
                Relay Router 2002:C058:6301::

    Manual Routes:

      ::4/64                      WE0       ::5

The configuration procedure asks whether you want to create router configuration files based on the choices you have made:


      Create new IPv6 network configuration files? [YES]:

If you are not satisfied with the configuration, enter NO; the configuration procedure ends immediately without changing the current IPv6 network configuration.
If you are satisfied with the configuration, press Enter. The configuration procedure creates new router configuration files and displays the following information:

      A  new  IPv6  configuration  file,  SYS$SYSTEM:TCPIP$INET6_CONFIG.DAT,
      has been created.  The previous configuration file  (if any)  has been
      renamed to SYS$SYSTEM:TCPIP$INET6_CONFIG.DAT_OLD.

      A new IPv6 configuration file, SYS$SYSTEM:TCPIP$IP6RTRD.CONF, has
      been created.  The previous configuration file  (if any)  has been
      renamed to SYS$SYSTEM:TCPIP$IP6RTRD.CONF_OLD.

      This new IPv6 network configuration will become active the  next  time
      TCP/IP Services for OpenVMS is started.

4.3 Configuring failSAFE IP IPv6 Addresses

Standby failSAFE IP IPv6 addresses must be configured manually. IPv6 supports addresses with various scopes; only link-local addresses need to be configured with standby addresses. (Link-local addresses are those that have high-order bits with the hexadecimal value FE80.)

To configure standby failSAFE IP IPv6 addresses, follow these steps:

Determine the link-local IPv6 addresses that have been dynamically created on each interface by using the ifconfig command, as in the following example. The last line for each interface contains the IPv6 link-local address. Note that the IPv4 addresses have already been configured with standby addresses. (The instructions for configuring IPv4 standby addresses are given in Section 3.4.4.3.)

$ ifconfig -a
IE0: flags=c43<UP,BROADCAST,RUNNING,MULTICAST,SIMPLEX>
     failSAFE IP Addresses:
        inet 16.176.56.81 netmask fffffe00 broadcast 10.0.255.255 (on GRYFFIIE1)
    *inet 16.176.56.65 netmask ff000000 broadcast 16.255.255.255 ipmtu 1500
    *inet6 fe80::202:a5ff:fe60:a368

IE1: flags=c43<UP,BROADCAST,RUNNING,MULTICAST,SIMPLEX>
     failSAFE IP Addresses:
        inet 16.176.56.65 netmask fffffe00 broadcast 10.0.255.255 (on GRYFFIIE0)
    *inet 16.176.56.81 netmask fffffe00 broadcast 16.176.57.255 ipmtu 1500
    *inet6 fe80::202:a5ff:fe60:a369

Create standby IPv6 addresses by executing the following commands, specifying the IPv6 addresses obtained in step 1:
$ ifconfig ie1 inet6 alias fe80::202:a5ff:fe60:a368 $ ifconfig ie0 inet6 alias fe80::202:a5ff:fe60:a369
In this example, the link-local IPv6 address configured on interface IE0 is added to IE1 as a standby. Similarly, the IPv6 address configured on interface IE1 is added to IE0 as a standby.

Restart the failSAFE IP service to make the configuration changes take effect (see Section 3.6). To make the changes take effect each time TCP/IP Services starts, edit SYS$STARTUP:TCPIP$SYSTARTUP.COM and add the following commands, which include the same ifconfig commands specified in step 2:

$!
$! IPv6 failSAFE Addresses
$!
$ ifconfig ie1 inet6 alias fe80::202:a5ff:fe60:a368
$ ifconfig ie0 inet6 alias fe80::202:a5ff:fe60:a369
$!
$! Restart failSAFE to pick up IPv6 address changes
$!
$ @sys$startup:tcpip$failsafe_shutdown
$ @sys$startup:tcpip$failsafe_startup
$!

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 an OpenVMS Alpha system on which 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.

Output for installations on OpenVMS I64 systems are similar. One difference is the TCP/IP Services product name: on OpenVMS I64 systems it is HP I64VMS TCPIP, while on OpenVMS Alpha systems it is DEC AXPVMS TCPIP (as shown in the following example).

Choose one or more items from the menu separated by commas: 1

The following product has been selected:
    DEC AXPVMS TCPIP V5.5-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.5-xx: HP TCP/IP Services for OpenVMS.

    Copyright 1976, 2004 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.5-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-I-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.5-xx               Layered Product

DEC VAXVMS TCPIP V5.5-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:

Core environment
TELNET client
FTP server

In this example, the configuration takes place on a system on which 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-2004 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-2004 13:
23:00.49

Startup request completed.
Press Return to continue ...