Advanced Server for OpenVMS
Server Installation and Configuration Guide


Previous Contents Index


Chapter 6
Implementing a Wide Area Network

This chapter describes how to set up a wide area network (WAN) using one of the TCP/IP transport software products supported by the Advanced Server for OpenVMS software.

This chapter consists of the following sections:

6.1 Enabling Wide Area Networking

The Advanced Server for OpenVMS software allows you to use one or both of the following methods for wide area networking name resolution:

In order to use them, they must be enabled using the Configuration Manager. You can enable them through the PWRK$CONFIG.COM command procedure, which provides access to the Configuration Manager when you answer YES to the question "Do you want to change server configuration parameters." To enable one or both of the wide area networking methods, select the Transports screen and select the appropriate checkbox. Alternatively, you can run the Configuration Manager after the server is configured and started, as described in the Advanced Server for OpenVMS Server Administrator's Guide.

6.2 Using the LMHOSTS File in a Wide Area Network

The Advanced Server for OpenVMS software provides the ability to set up a wide area network with the TCP/IP transport through the use of the LMHOSTS file. This file contains a list of domain controllers and member servers that are not in the same TCP/IP subnet as the primary domain controller. The LMHOSTS file allows the Advanced Server to participate in a Windows NT wide area network as well.

Unlike a Windows NT Server, the Advanced Server does not support remote LMHOSTS files (called into the Windows NT LMHOSTS file using #INCLUDE). To include the same host names as an existing LMHOSTS file on a Windows NT Server, copy the LMHOSTS file to the Advanced Server then manually insert the entries into the Advanced Server LMHOSTS file.

6.2.1 Setting Up a TCP/IP Wide Area Network

To set up a TCP/IP wide area network, modify the LMHOSTS file, which consists of a list of the host names and TCP/IP addresses of the domain controllers and member servers in the wide area network that are in the same domain.

When you include a node in the LMHOSTS file, the primary domain controller copies the user account database onto that node and keeps it up to date. If you omit a node, its user account database may become out of date.

You can modify the LMHOSTS file at any time. As long as the LMHOSTS file exists, users can establish TCP/IP connections to any server listed in the file.

6.2.2 The LMHOSTS Directory

You set up a wide area network by supplying the following file on all OpenVMS file servers that are in different subnets:

PWRK$LMROOT:[LANMAN]LMHOSTS.

(The LMHOSTS file has no file extension.)

6.2.3 LMHOSTS File Syntax

In the LMHOSTS file, create a list of nodes by specifying the following line for each node:

address nodename #PRE #DOM:domain_name

Where:

For example, the following entry might be included in the LMHOSTS file:

12.13.14.15 SERVER #PRE #DOM:VMSDOMAIN

This entry results in NetBIOS name SERVER with Internet address 12.13.14.15 being preloaded into the cache. Both the NetBIOS name SERVER and the NetBIOS name VMSDOMAIN (the name of the domain) will be available for matching.

6.2.4 Managing the LMHOSTS File

To change the list of available nodes, you can edit the file at any time. Domain names are resolved by checking the LMHOSTS file dynamically.

To disable LMHOSTS name resolution, rename the LMHOSTS file to any name other than LMHOSTS.

When you modify or disable the LMHOSTS file, it is not necessary to restart the Advanced Server. The change is effective immediately and is referenced at the next lookup.

6.2.5 Using the LMHOSTS Log File

If errors occur when the LMHOSTS file is accessed, the errors are recorded in the following file:

PWRK$LMROOT:[LOGS]PWRK$KNBDAEMON_nodename.LOG

This file is open and being written to while the Advanced Server is running. To close the log file, you must stop the Advanced Server.

To prevent the log file from becoming too large, each error is logged only once: the first time it occurs. If an error is found in the log file, it is not logged again.

6.3 Using WINS in a Wide Area Network

You can configure the Advanced Server as a WINS client. This allows the Advanced Server to use a WINS server for NetBIOS name registration, resolution, renewal, and release in a wide area network configuration.

For more information on how to use the Configuration Manager to configure the Advanced Server to use WINS, refer to the Advanced Server for OpenVMS Server Administrator's Guide.

6.3.1 Setting up WINS for OpenVMS Clusters

To allow clients that are configured for WINS support to use an Advanced Server alias name to connect to a clustered PATHWORKS Advanced Server across a WAN, you must add to the WINS database a static multihomed entry for the Advanced Server alias name. The following is an example of an entry for the Advanced Server alias name alpha1_alias:


alpha1_alias 
16.20.240.24 

When adding the static multihomed entry for the Advanced Server alias name, you should enter the TCP/IP address of each node in the OpenVMS cluster that is running the Advanced Server.

Note

The TCP/IP address that you place at the top of the list in the WINS database should be that of the first node that will start the Advanced Server in the cluster.

For more information about adding static entries to the WINS database, refer to your WINS product documentation.


Chapter 7
Removing Advanced Server for OpenVMS Software

This chapter describes how to remove Advanced Server for OpenVMS software from your system.

If you have to reinstall the Advanced Server for OpenVMS software, you may need to remove the Advanced Server for OpenVMS software.

For example, if the Installation Verification Procedure indicated that the software installation procedure failed, you must reinstall the software. But first you might need to remove the Advanced Server software.

For more information about disk space requirements, see Section 1.8.8, Step 8: Check Disk Space Requirements.

This chapter consists of the following sections:

7.1 The Advanced Server Deinstallation Procedure

You remove the Advanced Server using a command procedure that is included when you install the Advanced Server for OpenVMS software. The deinstallation command procedure performs the following operations:

7.2 Removing Advanced Server Configuration Parameters

When you remove the Advanced Server data files, the deinstallation procedure will remove the server configuration parameters that are stored as values, and their keys, from the OpenVMS Registry.

To complete this operation, the deinstallation procedure:

7.3 Removing Advanced Server for OpenVMS Software

To start the deinstallation procedure and remove Advanced Server for OpenVMS software:

  1. Ensure that you are logged in to the SYSTEM account.
  2. Ensure that no processes are running the Advanced Server ADMINISTER command line interface.
  3. Start the deinstallation command procedure, as follows:


    $ @SYS$UPDATE:PWRK$DEINSTAL 
    

Table 7-1, PWRK$DEINSTAL Prompts, tells you how to respond to the prompts the deinstallation procedure displays.

Table 7-1 PWRK$DEINSTAL Prompts
At this prompt... If you want the removal procedure to... Enter...
Are you sure you want to deinstall Advanced Server for OpenVMS[no]: Continue YES
  Exit [Return]
     
Do you want to delete the Advanced Server data files [no]: Save the Advanced Server on-disk structure, including the user accounts database, the share files, and the server configuration parameters in the OpenVMS Registry [Return]
  Remove the Advanced Server on-disk structure, including the user accounts database, the share files, and the server configuration parameters YES

7.4 Sample Advanced Server Removal Procedure

This is a sample of the removal procedure for Advanced Server software.


This procedure shuts down all Advanced Server V7.2 for OpenVMS servers 
and deletes most Advanced Server V7.2 for OpenVMS images. 
 
Are you sure you want to deinstall Advanced Server V7.2 for OpenVMS? 
Deinstall? [no]: YES 
Do you want to delete the Advanced Server data files [no]: YES 
 
Shutting down the currently running server(s)... 
Removing Advanced Server registry parameter and keys 
Deleting Advanced Server for OpenVMS common images... 
Deleting Advanced Server for OpenVMS NETBIOS component... 
Deleting Advanced Server V7.2 for OpenVMS images... 
Deleting Advanced Server data files... 
Removing PWRK$DEFAULT and PWRK$GUEST VMS accounts... 
Removing Advanced Server for OpenVMS identifiers... 
Removing Advanced Server for OpenVMS DECnet objects... 
Deassigning Advanced Server for OpenVMS logical names... 
Advanced Server V7.2 for OpenVMS is now deinstalled. 


Appendix A
Installation and Upgrade Checklist

Table A-1 summarizes the tasks that you need to perform to install and configure the Advanced Server. You can photocopy this table and use it as a checklist as you read about and complete the tasks in this book.

Table A-1 Installation and Upgrade Checklist
[] 1. Prepare for the installation by completing all pre-installation tasks on the checklist in Section 1.8, Pre-installation Tasks, including the following:
  1. Make sure that you have the required hardware and software.
  2. Log in to the SYSTEM account and back up the system disks.
  3. Make sure that you have enough disk space to install the software.
  4. Make sure that the system parameters GBLPAGES, GBLSECTIONS, PROCSECTCNT, and SCSNODE are set properly.
  5. Make sure that the queue manager is running and that the time zone is configured correctly.
  6. Verify that DECnet (or DECnet-Plus) and TCP/IP, if needed, are running.
  7. Check OpenVMS cluster configuration, if installing on a cluster.
  8. Check that OpenVMS registry services are available on the Advanced Server system.
[] 2. Start the installation procedure and respond to installation prompts. You may choose to install the following:
  • The complete Advanced Server.
  • The license server only (if you chose not to install the Advanced Server).
  • External authentication software only (if you chose not to install the Advanced Server).
[] 3. Start the configuration procedure and respond to configuration prompts.
[] 4. Run the Installation Verification Procedure (if you did not do so when you installed the Advanced Server).
[] 5. Start the server (if you did not do so when you configured the Advanced Server).
[] 6. Install Windows NT server administration tools (optional).


Appendix B
Sample Advanced Server Installation and Configuration

This appendix shows sample installation and configuration procedures for the Advanced Server.

B.1 Sample Advanced Server Installation Procedure

The following example shows a sample installation dialog for the Advanced Server. In this example, the installation takes place on a system where the Advanced Server has not been installed previously. If the Advanced Server had been installed previously on the system, the installation dialog would differ slightly.


$ @SYS$UPDATE:VMSINSTAL ASOVMS072 SYS$DEVICE:[KITS.ASOVMS] 
 
      OpenVMS AXP Software Product Installation Procedure V7.2 
 
It is 3-NOV-1998 at 09:31. 
 
Enter a question mark (?) at any time for help. 
* Are you satisfied with the backup of your system disk [YES]? [Return]
 
The following products will be processed: 
  ASOVMS V7.2 
       Beginning installation of ASOVMS V7.2 at 09:31 


%VMSINSTAL-I-RESTORE, Restoring product save set A ... 
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. 
 
      Advanced Server V7.2 for OpenVMS Installation 
 
   © Digital Equipment Corporation 1998. All rights reserved. 
 
   Restricted Rights: Use, duplication, or disclosure by the U.S. 
   Government is subject to restrictions as set forth in subparagraph 
   (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 
   52.227-14 Alt. III, as applicable. 
 
   This software is proprietary to and embodies the confidential 
   technology of Digital Equipment Corporation. Possession, use, or 
   copying of this software and media is authorized only pursuant to a 
   valid written license from Digital or an authorized sublicensor. 
 
 
    Please select from the following install options: 
 
      Advanced Server V7.2 for OpenVMS (complete) 
      Advanced Server V7.2 for OpenVMS license server (only) 
      External Authentication images (only) 
 
* Do you want to install the complete Advanced Server for OpenVMS [YES]? [Return]
 
The following components will be installed: 
 
      Advanced Server V7.2 for OpenVMS (complete) 
 
If the selection is correct, the installation will continue. 
If the selection is not correct, you can change your selection. 
Press CTRL/Y if you want to terminate the installation. 
 
* Is the selection correct [YES]? [Return]
%ASOVMS-I-VERSION, Checking for OpenVMS version 7.2 ... 
* Do you want to run the IVP after the installation is finished [YES]? [Return]
* Do you want to purge files replaced by this installation [YES]? [Return]
%ASOVMS-I-FREEBLKS, Checking for 139500 free blocks 
 
              User Accounts and User Identification Codes (UICs) 
              -------------------------------------------------- 
 
    The Advanced Server V7.2 for OpenVMS installation creates two OpenVMS 
    accounts:  a default account, PWRK$DEFAULT, and a guest account, 
    PWRK$GUEST.  The default UIC group number for both these new accounts 
    depends on the following: 
 
    o If you are installing the server for the first time, the default is 
      the first unused UIC group number, starting with 360. 
 
    o If there is an existing account PCFS$ACCOUNT, the default is the UIC 
      group number associated with PCFS$ACCOUNT. 
 
    o If there is an existing account PWRK$DEFAULT or PWRK$GUEST, the default 
      is the UIC group number associated with PWRK$DEFAULT or PWRK$GUEST, in 
      preference to PCFS$ACCOUNT.  However, the default UIC group number will 
      not be used to change the UIC of any existing accounts. 


    For more information about UIC group numbers, see the OpenVMS System 
    Manager's Manual. 
 
* Enter default UIC group number for PWRK$DEFAULT and PWRK$GUEST [360]: [Return]
 
    All questions have been answered.  The installation of 
    the Advanced Server for OpenVMS will continue. 
 
%ASOVMS-I-ACCOUNTS, Creating OpenVMS accounts for PWRK$DEFAULT and PWRK$GUEST 
%VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named PWRK$DEFAULT. 
%UAF-I-ADDMSG, user record successfully added 
%UAF-I-RDBADDMSGU, identifier PWRK$DEFAULT value [000360,000001] added to rights database 
%VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named PWRK$GUEST. 
%UAF-I-ADDMSG, user record successfully added 
%UAF-I-RDBADDMSGU, identifier PWRK$GUEST value [000360,000002] added to rights database 
%VMSINSTAL-I-RESTORE, Restoring product save set B ... 
%VMSINSTAL-I-RESTORE, Restoring product save set C ... 
%ASOVMS-I-DEFOBJS, Defining DECnet objects PCX$SERVER and PCSA$MAIL 
%ASOVMS-I-DCLCMDS, Installing the Advanced Server DCL commands 
%ASOVMS-I-SPECIFY, Specifying target directories for the provided files 
%ASOVMS-I-OBSOLETE, Deleting obsolete files 
 
                                  Next Steps 
                                  ---------- 
 
    To continue the installation procedure, enter the following command to 
    execute the server configuration command procedure: 
 
    $ @SYS$UPDATE:PWRK$CONFIG 
 
    For information about the configuration command procedure, see the 
    Advanced Server V7.2 for OpenVMS Installation and Configuration Guide. 
 
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... 
 
    © Digital Equipment Corporation 1998. All rights reserved. 
 
      Starting Installation Verification Procedure 
      for Advanced Server V7.2 for OpenVMS 
 
%PWRK-I-NORMAL, IVP completed successfully 
 
      Installation of ASOVMS V7.2 completed at 09:40 
 
    Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY 
 
    Creating installation data file: VMI$ROOT:[SYSUPD]ASOVMS072.VMI_DATA 
 
       VMSINSTAL procedure done at 09:40 

B.2 Sample Advanced Server Configuration Procedure

The following example shows a sample configuration dialog for the Advanced Server.


$ @SYS$UPDATE:PWRK$CONFIG 
Advanced Server V7.2 for OpenVMS Configuration Procedure 
 
    The Advanced Server stores and accesses the following 
    types of data files: 
 
    o Configuration parameter files 
    o License server data files 
    o Log files 
    o Printer spool files 
    o Virtual memory section files 
 
    You can specify any existing OpenVMS disk device that has at least 
    76500 free blocks of disk space to store these data files. 
 
    Note: The server frequently accesses the data files stored on the 
    disk.  If these files are stored on the system disk, it can degrade 
    the performance of both the OpenVMS system and the server.  Therefore, 
    Digital recommends that you specify a disk other than the system disk. 
 
Enter disk device name where the Advanced Server data files will be 
stored [PWROOT:]: [Return]
Creating Advanced Server directory tree on PWROOT:... 
PWRK$LICENSE_SERVER_STATE.DAT already exists, not superseded. 
%CREATE-I-EXISTS, PWRK$COMMONROOT:[000000] already exists 
Checking to see if the OpenVMS Registry Services are available... 
%RUN-S-PROC_ID, identification of created process is 0000023B 
Populating OpenVMS Registry with required Advanced Server & NT parameters... 
Please wait, this may take one to two minutes to complete ... 
Required OpenVMS Registry file server keys and values have been created. 
Migrating LANMAN.INI parameters to the OpenVMS Registry... 
Verifying SAM database files... 
Creating Advanced Server directory tree... 
Copying client files to Advanced Server directory tree... 
 
    Changing the server configuration parameters will allow you to modify 
    this server's client capacity and select the transports to be used.  
 
    SPEEDY is currently configured to 
        + support 20 PC clients 
        + use the following transport(s): DECnet 
 
    If you want this server to be the primary domain controller, you should 
    configure it to use all the transports used by any of the backup servers 
    in the domain. 
 


    If you want this server to be a backup domain controller, you should 
    configure it to have at least one transport in common with the domain's 
    primary domain controller, otherwise this configuration will fail. 
 
    If you do not change the configuration parameters now, you may do so 
    later by typing ADMIN/CONFIG. 
 
Do you want to change the server configuration parameters now? [YES]: NO 
 
Reading current configuration parameters ... 
 
  Your Advanced Server for OpenVMS is presently configured to run as follows: 
 
   1.  Run the license server:          NO 
   2.  Enable Timesource service:       NO 
   3.  Enable Alerter service:          YES 
   3a. Alert user names:                Administrator 
   4.  Enable Netlogon service:         YES 
   5.  Advanced Server domain:          LANGROUP 
   6.  Advanced Server role:            PRIMARY 
   7.  Advanced Server computer name:   SPEEDY 
   8.  Server announce comment:    Advanced Server V7.2 for OpenVMS 
Enter item number, or RETURN to use these values [DONE]: 5 
 
  An Advanced Server domain is a collection of computers that share 
  a common security database and policy.  Each domain has a unique 
  name.  A network can have many domains. 
 
  The Advanced Server domain name can be up to 15 characters long. 
  The domain name must be different than the computer name. 
 
Enter Advanced Server domain name for this system [5]: SPUNKY.DOM 
 
  Your Advanced Server for OpenVMS is presently configured to run as follows: 
 
   1.  Run the license server:          NO 
   2.  Enable Timesource service:       NO 
   3.  Enable Alerter service:          YES 
   3a. Alert user names:                Administrator 
   4.  Enable Netlogon service:         YES 
   5.  Advanced Server domain:          SPUNKY.DOM 
   6.  Advanced Server role:            PRIMARY 
   7.  Advanced Server computer name:   SPEEDY 
   8.  Server announce comment:    Advanced Server V7.2 for OpenVMS 
Enter item number, or RETURN to use these values [DONE]: [Return]
 
Saving parameters to the OpenVMS Registry... 
Creating SAM datafiles... 
Creating sharefile PWRK$LMROOT:[LANMAN.DATAFILES]SHAREDB ... 
New sharefile has been created. 
ADMIN$ added 
IPC$ added 
PWUTIL added 
PWLICENSE added 
PWLIC added 


    The Advanced Server Administrator network account is used to 
    administer the server.  The Administrator network account 
    is mapped by default to the OpenVMS SYSTEM account. 
 
    The network account password can be up to 14 characters long 
    and the case of the characters used will be preserved. 
 
Enter Administrator network account password: 
Re-enter to verify password: 
 
Changing password for Administrator network account... 
Checking system resources... 
 
The current system configuration for SPEEDY will support 20 PC clients. 
The Advanced Server is configured to use DECnet, NetBEUI, TCP/IP. 
 
    To automatically start the Advanced Server V7.2 for OpenVMS 
    at system startup, you should add the following line to the 
    SYS$MANAGER:SYSTARTUP_VMS.COM file. 
 
      $ @SYS$STARTUP:PWRK$STARTUP 
 
    Note: Add this line below the lines that start all network transports 
    (such as DECnet). 
 
Do you want to start the Advanced Server V7.2 on node SPEEDY now [YES]: [Return]
The file server will use DECnet, NetBEUI, TCP/IP. 
Advanced Server mail notification will use DECnet. 
Process NETBIOS created with identification 00000248 
Process PWRK$NBDAEMON created with identification 0000024A 
Process PWRK$KNBDAEMON created with identification 0000024C 
Process PWRK$LICENSE_R created with identification 0000024E 
Checking to see if the OpenVMS Registry Services are available... 
The Advanced Server is configured to support 20 PC clients. 
Process PWRK$MASTER created with identification 00000251 
The master process will now start all other Advanced Server processes. 
 
$ 


Previous Next Contents Index