Advanced Server for OpenVMS
Server Installation
and Configuration Guide
Chapter 3
Configuring the Advanced Server
This chapter describes how to configure the Advanced Server, and consists
of the following sections:
- Section 3.1, About the Advanced Server Configuration Procedure
- Section 3.2, Migrating LANMAN.INI Parameters to the OpenVMS Registry
- Section 3.3, Before You Start the Advanced Server Configuration Procedure
- Section 3.4, How to Start the Advanced Server Configuration Procedure
- Section 3.5, How to Respond to Advanced Server Configuration Prompts
- Section 3.6, How to Change Configuration Settings
- Section 3.7, Troubleshooting Configuration Procedure Problems
- Section 3.8, Selecting the Advanced Server Network Device
- Section 3.9, Defining Communications Devices
- Section 3.10, Next Steps
3.1 About the Advanced Server Configuration Procedure
The Advanced Server initial configuration procedure, PWRK$CONFIG.COM, is
installed by the Advanced Server for OpenVMS 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 Advanced Server.
3.1.1 What the Configuration Procedure Does
PWRK$CONFIG is a command procedure that:
- Creates the Advanced Server on-disk structure (shown in
Figure E-1, On-Disk Structure Diagram).
- If necessary, upgrades any existing file server user account and
share databases.
- Starts the Registry server if necessary.
- Migrates the server configuration parameters from the LANMAN.INI
file to the OpenVMS Registry, if necessary. (See Section 3.2, Migrating LANMAN.INI Parameters to the OpenVMS Registry, for
more information.)
- 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, or the maximum number of clients
that can connect to the server simultaneously.
- 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, allows
you to specify the Administrator account password.
- Gives you the option of starting the server.
After you install the server, you must run the PWRK$CONFIG
configuration procedure before you can start the server. In an OpenVMS
cluster, before you start the server, you must run PWRK$CONFIG 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.)
For more information about the Configuration Manager, refer to the
Advanced Server for OpenVMS Server Administrator's Guide.
3.2 Migrating LANMAN.INI Parameters to the OpenVMS Registry
On PATHWORKS for OpenVMS servers, the LANMAN.INI file is used to modify
and store server parameters. The Advanced Server stores the server
configuration parameters in the OpenVMS Registry, which is similar to
the Windows NT registry. The Advanced Server does not read parameter
settings from the LANMAN.INI file. For information about managing the
server configuration parameters in the OpenVMS Registry, refer to the
Advanced Server for OpenVMS Server Administrator's Guide.
If you are upgrading a system from PATHWORKS for OpenVMS to
Advanced Server for OpenVMS, the parameters and settings in the existing LANMAN.INI
file are migrated to the OpenVMS Registry when you run the
PWRK$CONFIG.COM configuration procedure for the first time after
installation. After they have been migrated to the OpenVMS Registry,
you manage the parameters in the registry. The LANMAN.INI file is
retained in case the system will run PATHWORKS for OpenVMS again later.
The PWRK$CONFIG.COM configuration procedure performs a one-time
migration of the parameters. At the time the parameters are migrated
into the registry, the PWRK$CONFIG procedure sets the data associated
with the LanmanIniMigrated value in the OpenVMS
Registry. If this value exists and has data associated with it, the
PWRK$CONFIG procedure will omit the parameter migration process.
You can display the value and its associated data in the OpenVMS
Registry using the following commands:
$ REGUTL :== $SYS$SYSTEM:PWRK$REGUTL.EXE
$ REGUTL SHOW VALUE * LANMANINIMIGRATED
Key: SYSTEM\CurrentControlSet\Services\AdvancedServer\Parameters
Value: LanmanIniMigrated
Type: String
Current Data: 29-OCT-1998 19:02:57.19
|
As shown in this example, the LanmanIniMigrated
value's data is the time stamp indicating when the LANMAN.INI
parameters were migrated.
Refer to the Advanced Server for OpenVMS Server Administrator's Guide for more information about
using the PWRK$REGUTL utility to manage server configuration parameters
in the OpenVMS Registry.
3.3 Before You Start the Advanced Server Configuration Procedure
Before you start the PWRK$CONFIG command procedure, answer the
following questions:
- 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
- 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 84,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.
- You can run the PWKR$CONFIG command procedure at any time, to
change the disk device where Advanced Server data files are stored.
- Do you want to change the system configuration parameters now?
If you respond "YES" to the prompt to change the system
configuration parameters, you start the Configuration Manager. The
Configuration Manager is a utility that allows you to modify and verify
the server configuration parameter settings, such as the maximum number
of clients that can connect to the server 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. For more information, refer to the Advanced Server for OpenVMS Server Administrator's Guide.
Configuring Transports for a Backup Domain Controller
If you are configuring a server as a backup domain controller, you
must select at least one transport that will also be run by the primary
domain controller. 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:
- If you are configuring a backup domain controller to join an
existing domain where the primary domain controller is on a different
TCP/IP subnet, both the backup domain controller and the primary domain
controller must be configured to use the TCP/IP transport, and you must
set up wide area networking using either a WINS (Windows Internet
Naming Service) Server or an LMHOSTS file for network name resolution,
as described in Chapter 6, Implementing a Wide Area Network.
- If you are using WINS for network name resolution, both the backup
domain controller and the primary domain controller must use a WINS
Server to provide NetBIOS name resolution.
- If you are using the LMHOSTS file, it must be set up on both the
backup domain controller and the primary domain controller. Make sure
that the entry for the primary domain controller is in the LMHOSTS file
on the backup domain controller before you configure the backup domain
controller. If there is no entry for the primary domain controller in
the LMHOSTS file on the backup domain controller when you configure it,
the backup domain controller will not find the primary domain
controller and will fail to join the existing domain. For more
information, refer to Chapter 6, Implementing a Wide Area Network.
To enable one or both of the wide area networking implementations,
select them using the Configuration Manager, as described in the
Advanced Server for OpenVMS Server Administrator's Guide.
- Do you want to change any of the server configuration settings?
These 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.3, 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 servers 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. Do not
answer "NO" to this option.
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.
The default
domain name is LANGROUP. Compaq Computer Corporation recommends that you specify
another name for your domain.
- 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 or as a backup domain controller. In an OpenVMS cluster, all
nodes on the cluster must have the same 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 procedure will not prevent you from
specifying the same named primary domain controller if another node or
cluster has previously been defined and is running in that role.
However, on the new (duplicate) primary domain controller, the Netlogon
service will not be started. The primary domain controller 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 the entire cluster as though it were a single
server. For example, a client user can specify the 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 DECnet has
not been configured to run, the default Advanced Server cluster alias
is nodename_alias.
- 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 "Advanced
Server V7.2 for OpenVMS."
For more information about changing configuration settings, refer
to Section 3.6, How to Change Configuration Settings.
For more information about each server
configuration setting, refer to the Advanced Server for OpenVMS Server Administrator's Guide.
- What is the Administrator account password?
If you are configuring a primary domain controller, the
configuration procedure prompts you to specify a password for the
Advanced Server Administrator account, from which you administer the
domain. Passwords are case sensitive and can contain up to 14
alphanumeric characters as well as any of the following special
characters:
! # $ % & () - . ^ _ ` { } ~
- 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 on each server node. For
more information, refer to Section 5.4.4, How to Start the Advanced Server in an OpenVMS Cluster.
3.4 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:
- Ensure that you are logged in to the SYSTEM account.
- Start the configuration procedure by entering:
$ @SYS$UPDATE:PWRK$CONFIG
|
3.5 How to Respond to Advanced Server Configuration Prompts
Table 3-1, Advanced Server Configuration Prompts, tells you how to respond to the prompts that PWRK$CONFIG
displays.
Table 3-1 Advanced Server Configuration Prompts
At this prompt... |
If you want the configuration procedure to... |
Enter... |
Do you want to continue with configuration [YES]:
1
|
Shut down the server or, if your server is part of an OpenVMS cluster,
all servers in the cluster
|
[Return]
|
|
Abort the configuration procedure
|
NO
|
|
|
|
Enter disk device name where Advanced Server data files will be stored [
default_device]:
|
Copy the Advanced Server on-disk structure to the default OpenVMS disk
device displayed
If you ran PWRK$CONFIG previously, the default disk device is the
one you specified the last time you configured the server; otherwise,
the default device is SYS$SYSDEVICE.
|
[Return]
|
|
Copy the Advanced Server on-disk structure to an OpenVMS disk device
different from the default displayed
|
device_name
|
|
|
|
Do you want to change the server configuration parameters now? [YES]:
|
Enter the Configuration Manager tool
|
[Return]
For detailed information about using the Configuration Manager,
refer to the Advanced Server for OpenVMS Server Administrator's Guide.
|
|
Complete the configuration without entering the Configuration Manager
|
NO
|
|
|
|
Enter item number, or RETURN to use these values [DONE]:
|
Accept the configuration parameters displayed
|
[Return]
|
|
Change the configuration settings displayed
|
The number associated with a setting you want to change.
For detailed information on changing these default configuration
settings, see Section 3.6, How to Change Configuration Settings.
|
|
|
|
Do you want to enter a new Administrator account password [NO]:
2,3
|
Keep the existing Administrator account password
|
[Return]
|
|
Prompt you to enter a new Administrator account password
|
YES
|
|
|
|
Enter Administrator network account password
3:
|
Associate a password with the Administrator account
|
password
If your server will be part of a domain, enter the password to the
domain's existing Administrator account.
|
Re-enter to verify password
3:
|
|
password
|
|
|
|
Do you want to start the Advanced Server V7.2 for OpenVMS on node
node_name now [YES]:
4
|
Start the server automatically after the configuration procedure
completes
|
[Return]
|
|
Not start the server
|
NO
|
1This prompt is displayed only if the server is running.
2This prompt is displayed if you ran PWRK$CONFIG previously.
3This prompt is displayed only if you are configuring a
primary domain controller.
4This prompt is displayed only if the Advanced Server can be
started without first executing AUTOGEN or rebooting the system.
3.6 How to Change Configuration Settings
After you exit the Configuration Manager, the configuration procedure
displays a list of server configuration settings and a prompt that lets
you change them; for example:
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: COBRAZ
7a. Advanced Server OpenVMS cluster alias: COBRAZ_ALIAS
8. Server announce comment: Advanced Server V7.2 for OpenVMS
Enter item number, or RETURN to use these values [DONE]:
|
- To change a server configuration setting, enter the number of the
setting you want to change. A prompt is then displayed that lets you
change that setting. Table 3-2, Configuration Settings, describes possible values for each
setting.
- To save the settings after you complete your changes or to accept
the settings displayed, press [Return] to use the default
answer DONE. For more information about server configuration, refer to
the Advanced Server for OpenVMS Server Administrator's Guide.
Table 3-2 Configuration Settings
Setting |
Possible Values |
1. Run the license server:
|
YES, to run the license server.
NO, to use the default and not run the license server.
|
2. Enable Timesource service:
|
YES, to enable the Timesource service.
NO, to use the default and not enable the Timesource service.
|
3. Enable Alerter service:
|
YES, to accept the default and enable the Alerter service.
NO, to disable the Alerter service.
|
3a. Alert user names:
1
|
A comma-delimited list of user names (each containing up to 20
characters), who can receive alert messages.
|
4. Enable Netlogon service:
|
YES, to accept the default and enable the Netlogon service.
NO, to disable the Netlogon service.
|
5. Advanced Server domain:
|
A domain name of up to 15 characters.
Press
[Return] to use the default. The default domain name is
LANGROUP. Compaq recommends that you specify another name for the
domain.
|
6. Advanced Server role:
|
PRIMARY, to designate the server as the primary domain controller
BACKUP, to designate the server as a backup domain controller.
|
7. Advanced Server computer name:
|
A computer name of up to 15 characters.
Press
[Return] to use the default. If this is the first time
running the configuration procedure, the default is your system's
SCSNODE name.
|
7a. Advanced Server for OpenVMS cluster alias:
2
|
The Advanced Server cluster alias for the OpenVMS cluster to which your
server belongs.
Press
[Return] to use the default. If DECnet is configured to run,
the default is the DECnet cluster alias. If DECnet is not configured to
run, the default is
nodename_alias.
|
8. Server announce comment:
|
A text string of up to 48 characters that the server uses to announce
its presence on the network.
Press
[Return] to use the default.
|
1Displayed only if Alerter service is enabled.
2Displayed only in an OpenVMS cluster.