HP OpenVMS Systems Documentation

This chapter describes how to configure the PATHWORKS Advanced Server and consists of the following sections:

• Section 3.1, About the Advanced Server Configuration Procedure
• Section 3.2, Before You Start the Advanced Server Configuration Procedure
• Section 3.3, How to Start the Advanced Server Configuration Procedure
• Section 3.4, How to Respond to Advanced Server Configuration Prompts
• Section 3.5, How to Change Default Configuration Settings
• Section 3.6, Configuring the Advanced Server Domain Role
• Section 3.7, Troubleshooting Configuration Procedure Problems
• Section 3.8, The Advanced Server Network Adapter
• Section 3.9, Next Steps

The Advanced Server initial configuration procedure, PWRK$CONFIG.COM, is installed by the PATHWORKS Advanced Server installation procedure. Like the installation procedure, the configuration procedure asks you a series of questions (by displaying prompts). The procedure uses your answers to configure the PATHWORKS Advanced Server.

You can use the PWRK$CONFIG.COM configuration procedure to reconfigure the server at any time later. Note that the script contents change after the first configuration.

3.1.1 What the Configuration Procedure Does

PWRK$CONFIG.COM is a command procedure that:

• Creates the PATHWORKS Advanced Server on-disk structure. (Appendix F,PATHWORKS Advanced Server Files and On-Disk Structure, shows the on-disk structure).
• Upgrades any existing file and print server user account and share databases, such as when upgrading the server from a previous version.
• If configuring a previously configured server, stores the original accounts database in specially-created directories. (For more information, see Section 3.7.2, If Problems Occur When Reconfiguring the Advanced Server.)
• Allows you to enter the Configuration Manager to modify system configuration parameters and to verify the configuration setting against the available system resources. For example, you can specify the transports the server will run and the maximum number of clients that can connect to the server simultaneously.
  For more information about the Configuration Manager, refer to the Compaq PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide.
• Creates the PATHWORKS Advanced Server user account and share databases.
• Allows you to modify server configuration default settings such as server role, domain name, and the services that are enabled.
• On a server that will run as a primary domain controller or member server, allows you to specify the Administrator account password.
• Gives you the option of starting the server.

After you install the server, you must run PWRK$CONFIG.COM before you can start the server. In an OpenVMS Cluster, before you start the server on any node, you must run PWRK$CONFIG.COM on each node where you plan to run the server. Although the nodes in an OpenVMS Cluster function as a single unit in a domain, treat them as individual units for purposes of configuration.

3.2 Before You Start the Advanced Server Configuration Procedure

Before you start the PWRK$CONFIG.COM command procedure, check that the ENQLM quota system process parameter for the user account from which you will run the PWRK$CONFIG.COM procedure is set to a value of 500 or greater. For information on how to determine the current setting and how to increase the value, see Section 1.9.7, Step 7: Check ENQLM Process Quota. In addition, check the system parameters discussed in Section 1.9.6, Step 6: Check System Parameters.

Be prepared to answer the questions discussed in the following sections. The questions asked by PWRK$CONFIG.COM depend on the options you select and on such factors as server role and whether you are configuring the server to join a new or existing domain.

3.2.1 On What OpenVMS Disk Device Do You Want to Store the Advanced Server Data Files?

The data files include:

• Configuration parameter files
• License Server data files
• Log files
• Printer spool files
• Server data files
• Security Account Manager (SAM) database files
• Client-based server administration tools and license kits
• Virtual memory section files

By default, the configuration procedure copies the data files to the system device (SYS$SYSDEVICE). However, you can specify any existing OpenVMS disk device that has at least 85,000 free blocks of disk space. The amount needed depends on the components installed.

When you select a disk for the Advanced Server data files, keep the following in mind:

• The Advanced Server frequently accesses the data files copied to the specified disk device, which generates input to and output from the disk. Having these operations occur on the system disk can degrade the performance of both the OpenVMS system and the Advanced Server. Therefore, Compaq recommends that you specify a disk device other than the system disk.
• On an OpenVMS Cluster with multiple system disks, all nodes on which you plan to run the Advanced Server must use the same disk device to store and access Advanced Server data files. Using separate disks on separate cluster members is strictly prohibited.
• You can run the PWRK$CONFIG.COM command procedure at any time, to change the disk device where Advanced Server data files are stored. PWRK$CONFIG.COM automatically copies the data files to the new location and deletes the data files from the current location.

If you respond "YES" to the prompt to change the system configuration parameters, the Configuration Manager starts. The Configuration Manager is a utility that allows you to modify and verify the system environment configuration parameter settings, such as the maximum number of clients that can connect to the server, the percentage of physical memory the server can use, and which network transports the server uses.

You can change the system configuration parameter settings after starting the Advanced Server by using the Configuration Manager (invoking the Configuration Manager with the ADMINISTER/CONFIGURATION command at the DCL prompt). For more information, refer to the Compaq PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide. Section B.2, Sample Server Configuration, shows the basic Configuration Manager screen displayed when you opt to change the system configuration parameter settings during use of PWRK$CONFIG.COM.

3.2.2.1 Configuring Transports for a Backup Domain Controller or Member Server

If you are configuring a server as a backup domain controller (BDC) or a member server, you must select at least one transport that is also used by the primary domain controller (PDC). Otherwise, the configuration will fail.

When you select the transports to run on a server that will participate in wide area networking, keep the following in mind:

• In a wide area network, the TCP/IP transport is required. (DECnet also supports wide area networks but the functionality it provides is not as extensive as that provided by TCP/IP.) In a cluster, all Advanced Server members must be in the same subnet.
• If you are configuring a BDC or member server to join an existing domain where the PDC is on a different TCP/IP subnet, both the server you are configuring and the PDC must be configured to use the TCP/IP transport, and you must set up wide area networking using either a WINS (Windows Internet Name Service) Server, a Domain Name System (DNS) server, or an LMHOSTS file for NetBIOS name resolution, as described in Chapter 6, Implementing a Wide Area Network. (You can select one, two, or all three of these methods for name resolution.)
• If you are using WINS for network name resolution, the PDC and any BDCs and member servers should use a WINS Server to provide NetBIOS name resolution.
  If your Advanced Server will run in an OpenVMS Cluster, to gain the benefits of load balancing and failover, clients should connect to the Advanced Server using the Advanced Server cluster alias. However, the Advanced Server does not dynamically register the Advanced Server cluster alias with the WINS server. Therefore, you should define a static multihomed entry for the Advanced Server alias in the WINS database. For more information, see Section 6.3.1, Setting up WINS Support for OpenVMS Clusters. If you plan to use DNS for NetBIOS name resolution, you do not define this static multihomed entry in the WINS database. (If Windows 95, Windows 98, or Windows NT clients are configured to use both WINS and DNS for NetBIOS name resolution, they first query the WINS server to resolve the name.)
• If you are using the LMHOSTS file, it must be set up on the PDC as well as the BDCs and member servers. Before you configure any BDC or member server that is not on the same subnet as the PDC, make sure that a special NetBIOS name entry for the PDC is in the LMHOSTS file on that BDC or member server; otherwise, the BDC or member server will not find the PDC and will fail to join the existing domain. This NetBIOS name entry should be the same as the domain name, space padded to 15 characters, with the hexadecimal control character 1B appended to it. You map the IP address of the PDC to this special name. For example, if the domain name is LANGROUP and the PDC of LANGROUP is DOMPDC with an IP address of 10.20.30.40, the BDCs and member servers would need to add the following lines to their LMHOSTS file:

  10.20.30.40 DOMPDC #PRE #DOM:LANGROUP 10.20.30.40 "LANGROUP \0x1B" #PRE

  
  Note that the total number of characters within the quotes should always be 20 characters (the domain name padded to 15 characters, plus the five characters required for the hexadecimal control character (\0x1B)).
  For more information, see Chapter 6, Implementing a Wide Area Network.
  If your Advanced Server will run in an OpenVMS Cluster, other domain controllers (including the PDC) that are not in the same subnet as the Advanced Server cluster must add an entry for the Advanced Server cluster alias to their LMHOSTS file. This assumes they are not using other methods (WINS or DNS) for resolving NetBIOS names. For domain operations, all the domain controllers in the cluster operate as a single domain controller identified by the Advanced Server cluster alias name, rather than by the specific computer names of the individual cluster members. However, because the LMHOSTS file does not offer any means for mapping multiple IP addresses to a single NetBIOS name, the entry for the Advanced Server cluster alias must be mapped to the IP address of one specific server cluster member. If the Advanced Server is stopped on that cluster member, you must modify the LMHOSTS file on all clients and servers to map the cluster alias name to the IP address of a cluster member on which the Advanced Server is still running. On systems running a Microsoft Windows operating system, the NetBIOS name cache must also be reloaded using the command NBTSTAT -R (capital R required).
  Due to the LMHOSTS limitations noted above, it is difficult (and perhaps unmanageable) to gain the benefits of load balancing and failover using an LMHOSTS file.
• If your Advanced Server runs in an OpenVMS Cluster and you have it set up for cluster load balancing using DNS, then enable the use of DNS for NetBIOS name resolution on all servers and clients. Remove any entries for the Advanced Server cluster alias from the LMHOSTS file and WINS database. Compaq strongly recommends that the Advanced Server cluster alias not be the same as the TCP/IP cluster alias (referred to as the TCP/IP cluster impersonator name). For information on setting up load balancing, refer to the Compaq PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide.

To enable any of the wide area networking implementations, select them using the Configuration Manager, as described in the Compaq PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide.

3.2.3 Do You Want to Change Any of the Server Configuration Settings?

The server configuration settings determine:

• Whether the License Server runs
  The License Server is a software program that you can run on your OpenVMS system to grant client-based licenses. Any client that wants to use server resources must have a valid license. Each local area network (LAN) needs only one License Server. The client license product authorization keys (PAKs) must be loaded on the system that runs the License Server.
  In an OpenVMS Cluster, the PAKs must be loaded in a shared license database available to all cluster members.
  The License Server runs only if you enable it with the configuration procedure.
  • If you are using client-based licensing, you must run the License Server. Compaq recommends that you run the License Server on a different system than the Advanced Server. See Section 1.4, About Licensing, for more information.
  • If you are using server-based licenses, you do not need to run the License Server.
  
  By default, the License Server does not run.
• Whether the Timesource service runs
  The Timesource service allows your server to act as a time server. Other servers on the network can synchronize with the time server to coordinate network events (for example, running batch programs on all computers the same time each day). Each LAN needs only one time server.
  By default, the Timesource service does not run.
• Whether the Alerter service runs
  The Alerter service sends messages called alerts to servers and clients that run the Messenger service.
  By default, the Alerter service runs.
• Names of the users who receive alert messages
  By default, alert messages are sent to the Administrator account.
• Whether the NetLogon service is enabled.
  In a domain, the NetLogon service distributes a domain-wide user accounts database to all domain controllers running NetLogon. The service allows for single domain-wide logon that enables users to access resources on any server in the domain. The NetLogon service is required for smooth operation of the domain; Compaq recommends that the NetLogon service always be enabled, even on a member server.
  By default, the NetLogon service runs.
• Domain name
  This is the domain in which your server is located. A domain is a subdivision of clients and servers on the network. For more information on domains, refer to the Compaq Advanced Server for OpenVMS Concepts and Planning Guide and the Compaq PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide.
  The default domain name is LANGROUP. You can specify a name that reflects your company or group.
• Role of the server
  This is the role of the server in the domain. You can designate an Advanced Server as either the primary domain controller (PDC), a backup domain controller (BDC), or a member server. When you install the Advanced Server in a new domain, the new server becomes the PDC by default. In an OpenVMS Cluster, all nodes on the cluster have the same role: when you change the role of one, the change applies to all the servers on the cluster.
  For more details on configuring the server domain role, see Section 3.6, Configuring the Advanced Server Domain Role.
• Computer name
  This unique name identifies your server in the domain. You define this name or accept the default value when you run the configuration procedure.
  The PWRK$CONFIG.COM procedure will not prevent you from specifying the same named PDC if another node or cluster has previously been defined and is running in that role. However, on the new (duplicate) PDC, the NetLogon service will not be started. The PDC must be unique in the domain.
  The default computer name is the same as the server's SCSNODE name.
• Advanced Server cluster alias
  If your server is a member of an OpenVMS Cluster, this is the name that all servers in the cluster share. The alias lets remote nodes (including clients) treat all server members in the cluster as a single server. For example, a client user can specify the Advanced Server cluster alias to connect to any server in the cluster; the user need not know the specific node in the cluster to which it is connected.
  If DECnet has been configured to run in the cluster, the default Advanced Server cluster alias is the same as the DECnet cluster alias. If a DECnet alias is not defined, the default Advanced Server cluster alias is nodename_ALIAS, where nodename is the SCSNODE name of the cluster member from which you initially run PWRK$CONFIG.COM.

  Note Compaq strongly recommends that the Advanced Server cluster alias and the TCP/IP cluster alias (referred to as the TCP/IP impersonator cluster name) be different. Do not use the name of the domain as the Advanced Server cluster alias; if they are the same, the NetLogon service will fail to start.

• Server announce comment
  This is the text that the Advanced Server displays when it announces its presence on the network and when you display a list of available servers.
  The default server announce comment is "PATHWORKS V6.1 for OpenVMS (Advanced Server)."

For more information about changing configuration settings, see Section 3.5, How to Change Default Configuration Settings.

For more information about each server configuration setting, refer to the Compaq PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide.

3.2.4 What Do You Want the Administrator Account Password to Be?

If you are configuring a PDC, the configuration procedure prompts you to specify the password to be set for the domain Administrator account. If you are configuring a member server, the configuration procedure prompts you for the member server's local Administrator account password to be set. The member server's local Administrator account password gives access to the member server's local security account database. As with Windows NT, there may be situtations where you would like to allow certain people to manage a member server's local database without giving them the ability to manage the entire domain.

Passwords are case sensitive and can contain up to 14 characters. Valid characters are alphanumeric characters and any of the following special characters:

! # $ % & () - . ^ _ ` { } ~

3.2.5 Are You Going to Supply Account/Password Information?

If you are configuring your server to join an existing domain (as a BDC or member server), you can either:

• Have the computer added to the domain manually by the domain administrator
• Have the computer added by supplying an administrator account user name and password during execution of the configuration procedure

The former option is useful if the domain administrator does not wish to give out the user name and password of the Administrator account in the domain to the person configuring this server to join the domain. The domain administrator can use the ADMINISTER ADD COMPUTER command or the Windows NT Server Manager to add the computer to the domain. If this is the case, answer NO to this prompt, and you will not be prompted for account/password information.

With the latter option, the configuration procedure requests the domain's PDC to add the computer to the domain. You will be prompted for a domain administrator account user name and password, as explained in Section 3.2.6, What Is the Domain Administrator Password?.

3.2.6 What Is the Domain Administrator Password?

When you choose to have the computer added automatically by the configuration procedure, you are prompted for a domain administrator account user name and password. As noted in Section 3.2.5, Are You Going to Supply Account/Password Information?, the PDC is requested to add the computer to the domain. The PDC validates the account user name and password on behalf of the configuration procedure. Enter the password, observing the rules specified in Section 3.2.4, What Do You Want the Administrator Account Password to Be?.

3.2.7 Do You Want to Enter a New Administrator Account Password?

In certain cases, you are prompted whether you want to enter a new Administrator password. This gives you the opportunity to change the password.

3.2.8 Do You Want to Start the Server?

The configuration procedure asks you if you want to start the Advanced Server. If you do not want to start the Advanced Server at this time, you can do so later from the command line after the configuration procedure completes.

Before you start the server on any OpenVMS Cluster member, Compaq recommends that you configure the Advanced Server on each cluster member that you want to use as a server. You can then use the SYSMAN utility to start the server on all cluster members. If you choose to start the server individually on each cluster member, make sure that you do so from the SYSTEM account (or a similar account) on each server node. For more information, see Section 5.3.5, How to Start the PATHWORKS Advanced Server in an OpenVMS Cluster.

For detailed information on alternate ways to start the server, see Section 5.3, Starting the PATHWORKS Advanced Server.

3.3 How to Start the Advanced Server Configuration Procedure

After the installation procedure completes, the OpenVMS system prompt ($) is displayed. If the system was rebooted following installation, log in to the SYSTEM account or an equivalent account. If the system was not rebooted, ensure that you are logged in to such an account. Then, start the configuration procedure by entering:

$ @SYS$UPDATE:PWRK$CONFIG

In an OpenVMS Cluster, PWRK$CONFIG.COM must be run on each member node on which the server is to run. If you first start the server at any node, and then attempt to run the PWRK$CONFIG.COM configuration procedure, the procedure will shut down the server.

3.4 How to Respond to Advanced Server Configuration Prompts

Table 3-1, PATHWORKS Advanced Server Configuration Prompts, tells you how to respond to the prompts that PWRK$CONFIG.COM displays.