| Previous | Contents | Index |
This chapter describes tasks you can perform after you install the Advanced Server and consists of the following sections:
Before you start the Advanced Server, make sure you have:
If the installation verification procedure (IVP) did not run when you installed the Advanced Server, you can run it now (or anytime later) to make sure that the server installed successfully. (When you specify the /NOTEST qualifier with the PRODUCT INSTALL command, the IVP procedure does not run.)
To run the IVP, enter the following command:
$ @SYS$TEST:PWRK$PCSI_IVP |
| If the installation... | Then the IVP displays... | And you should... |
|---|---|---|
| Succeeded | The message: %PWRK-I-NORMAL, IVP completed successfully | |
| Start the server, as described in Section 5.3, Starting the Advanced Server. | ||
| Failed |
An error message, followed by:
-PWRK-E-IVPFAIL, IVP has failed |
|
| Reinstall the software, as described in Chapter 2, Installing Advanced Server for OpenVMS Software. | ||
The following sections describe how to start the Advanced Server and how
to automate server startup.
5.3.1 When to Start the Advanced Server
You must configure the Advanced Server before you can start it for the
first time. After running the configuration procedure, you can start
and stop the Advanced Server at any time.
5.3.2 What the Startup Procedure Does
You can start the Advanced Server:
If you did not start the Advanced Server during the configuration procedure, you can start it now by entering:
$ @SYS$STARTUP:PWRK$STARTUP |
The Advanced Server starts, and messages similar to the following are displayed:
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. |
To make sure that the Advanced Server starts automatically each time you boot your OpenVMS system, edit the site-specific startup file, SYS$STARTUP:SYSTARTUP_VMS.COM. Add the Advanced Server startup command to the file below all lines that start network transports. For example:
$ START/NETWORK DECNET . . . $ @SYS$STARTUP:PWRK$STARTUP |
If you installed and configured the Advanced Server on multiple members of the same OpenVMS Cluster, Compaq recommends that you use the SYSMAN utility to start the Advanced Server manually and simultaneously on all cluster members.
To start the Advanced Server on all cluster members at the same time, make sure you are logged in to the SYSTEM account on one of the member nodes, then run SYSMAN as follows:
| Enter this command... | To... |
|---|---|
| $ RUN SYS$SYSTEM:SYSMAN | Start the SYSMAN utility. |
| SYSMAN> SET ENVIRONMENT/NODE=(SPEEDY,SPIN,SPAN) | |
| Define the OpenVMS Cluster members on which to start the server. For example, SPEEDY, SPIN, and SPAN. | |
| SYSMAN> DO @SYS$STARTUP:PWRK$STARTUP | |
| Start the Advanced Server on all the nodes you defined in the previous command. | |
| SYSMAN> EXIT | Exit the SYSMAN utility. |
Some of the problems that prevent the Advanced Server from starting are discussed in the following sections:
Advanced Server processes are detached processes. During startup, all detached processes must execute the site-specific system login procedure (by default, SYS$MANAGER:SYLOGIN.COM).
If Advanced Server startup does not complete successfully, check the SYLOGIN.COM procedure. Make sure that only commands that should be executed by detached processes are executed during Advanced Server startup.
In SYLOGIN.COM, you can use the DCL lexical function F$MODE or F$GETJPI
to conditionalize DCL commands, such as $SET TERM/INQUIRE, that should
be executed only by nondetached processes, so that they are not
executed during Advanced Server startup. Refer to the OpenVMS DCL Dictionary for
more information.
5.4.4.2 OpenVMS Registry Services Not Available
The Advanced Server will start only if the OpenVMS registry services are available. For information about starting the Registry Server, refer to the OpenVMS System Manager's Manual or the OpenVMS Connectivity Developer's Guide (included in the OpenVMS Documentation CD-ROM).
If the Registry Server is started as part of Advanced Server startup, a message similar to the following is displayed by the startup procedure:
Checking to see if the OpenVMS Registry Services are available... %RUN-S-PROC-ID, identification of created process is 0000023B |
If the Registry Server cannot be started, the following message is displayed and the startup procedure is terminated:
SYS$REGISTRY must be defined to start the VMS Registry.
%PWRK-F-NOREGISTRY, OpenVMS Registry services not configured for
this system
%PWRK-F-STARTERR, severe error encountered during start-up
OpenVMS Registry Services are not available on this system.
Some file server parameters are stored in the OpenVMS Registry.
For the file server or file server utilities to be able to access
these parameters, OpenVMS Registry Services must be available
on this system. Without them the file server cannot start.
$
|
The Advanced Server startup procedure records a list of all Advanced Server parameters that are set in the OpenVMS Registry. You can use this list as a reference if you should ever need the latest parameter values. The list is stored in the following location, where nodename is the name of your server node:
PWRK$PARAMS:PWRK$REGISTRY_PARAMS_nodename.LIS |
You can stop the Advanced Server at any time for any reason, which can include the following:
To stop the Advanced Server, enter the following command:
$ @SYS$STARTUP:PWRK$SHUTDOWN Shutting down the currently running server(s)... |
For a cluster server, enter:
$ @SYS$STARTUP:PWRK$SHUTDOWN CLUSTER |
To stop the Advanced Server as part of an orderly system shutdown, add the shutdown command to the site-specific system shutdown procedure. In addition, prior to shutting down the server, announce the planned shutdown to connected users by using the ADMINISTER SEND/USERS command, as in the following example, which alerts all users connected to server WOODMAN:
LANDOFOZ\\TINMAN> SEND/USERS/SERVER=WOODMAN "Shutdown at 1pm today!!!" |
Compaq provides numerous command procedures that, for example, provide shortcuts for invoking certain server management commands and procedures. You can see a list of these commands by examining the contents of the file SYS$STARTUP:PWRK$DEFINE_COMMANDS.COM.
You can define these Advanced Server management commands automatically when you log in to the account that you use to manage the Advanced Server. To define Advanced Server commands at login, edit the LOGIN.COM file of the privileged account to add the following line:
$ @SYS$STARTUP:PWRK$DEFINE_COMMANDS |
The OpenVMS operating system Versions 7.1 and higher provide support for external authentication. Advanced Server participates with the operating system to allow Advanced Server domain users to log in to the OpenVMS operating system using the Advanced Server domain user name and password.
External authentication can provide automatic password synchronization between an OpenVMS account and a corresponding Advanced Server domain account. The passwords are synchronized whenever a user logs in to the OpenVMS account, provided that an Advanced Server domain controller is available to service the request. With external authentication enabled, users who have both OpenVMS and Advanced Server domain accounts can avoid maintaining two different passwords.
By default, external authentication is disabled. However, when you start the Advanced Server, server external authentication is automatically enabled, if the OpenVMS system administrator has defined logical names in SYSTARTUP_VMS.COM and marked user accounts in the SYSUAF, as described in the OpenVMS Guide to System Security.
No additional configuration is necessary on cluster members running the Advanced Server to enable the Advanced Server to participate in the external authentication process. However, to use external authentication in an Advanced Server cluster, all cluster members should be configured to be able to process OpenVMS logon requests for network users, so that externally authenticated users can log on to the cluster through any node in the cluster. A cluster member that is not running the complete Advanced Server can be configured to authenticate logon requests from network users if it has access to external authentication software on a shared cluster disk. If it does not have access to external authentication software on a shared cluster disk, you can enable external authentication on that system by copying only the external authentication images to the system disk, following the steps given in Section 5.7.1, Setting Up External Authentication in OpenVMS Clusters.
To provide external authentication on the Advanced Server system, perform the following procedures:
| Step | Procedure | Refer to... | |
|---|---|---|---|
| 1. |
Install one of the following:
|
Chapter 2, Installing Advanced Server for OpenVMS Software. | |
| 2. | Enable external authentication for the OpenVMS system. | OpenVMS Guide to System Security | |
| 3. | Set the OpenVMS user account to invoke external authentication. | OpenVMS Guide to System Security | |
| 4. | Establish host mapping between the Advanced Server domain user account and the OpenVMS user account, if necessary. | Compaq Advanced Server for OpenVMS Server Administrator's Guide | |
| 5. | If your Advanced Server is participating in an OpenVMS Cluster, set up external authentication on all cluster members. | Section 5.7.1, Setting Up External Authentication in OpenVMS Clusters | |
| 6. | If you want to change the default domain used for external authentication (the local server's domain is the default domain for users when external authentication is established: if a user does not specify a domain name at login, the system uses the default domain for authentication), set the system logical PWRK$ACME_DEFAULT_DOMAIN accordingly. | Compaq Advanced Server for OpenVMS Server Administrator's Guide | |
| 7. | If establishing external authentication for users in trusted domains, add the name of the trusted domain(s) to the OpenVMS Registry value HOSTMAPDOMAINS. | Compaq Advanced Server for OpenVMS Server Administrator's Guide |
If external authentication is being used in an OpenVMS Cluster, Compaq recommends that all cluster members be configured to be able to process OpenVMS logon requests for network users. If one or more members do not support external authentication, users that have external authentication set in their account records will not be able to log on to those hosts not configured for external authentication.
Once external authentication is enabled properly on each OpenVMS system in the cluster, as described in the OpenVMS Guide to System Security, no additional configuration is necessary on Advanced Server cluster members to enable them to participate in the external authentication process. External authentication is enabled automatically when the Advanced Server is started.
A cluster member that is not running the complete Advanced Server can authenticate logon requests from network users if it has access to external authentication software on a shared cluster disk. Note that external authentication is not supported on OpenVMS systems prior to V7.1. Therefore, to ensure that external authentication works properly on the cluster, Compaq recommends that you make sure all systems in the cluster that are not running the Advanced Server are running OpenVMS V7.1 or later.
If the cluster member does not have access to external authentication software on a shared cluster disk, you can enable external authentication on that system by performing the following steps; for a cluster member that does have access to external authentication software on a shared cluster disk, you need only perform steps 2 and 3:
| File | Destination on VAX Node |
|---|---|
| SYS$LIBRARY:PWRK$ACME_MODULE_VAX.EXE | SYS$COMMON:[SYSLIB] |
| SYS$STARTUP:PWRK$ACME_STARTUP.COM | SYS$COMMON:[SYS$STARTUP] |
| File | Destination on Alpha V7.1 Node |
|---|---|
| SYS$LIBRARY:PWRK$ACME_MODULE_ALPHA.EXE | SYS$COMMON:[SYSLIB] |
| SYS$STARTUP:PWRK$ACME_STARTUP.COM | SYS$COMMON:[SYS$STARTUP] |
$ DEFINE/SYSTEM/EXE PWRK$ACME_SERVER scsnode1_name[,scsnode2_name,...] |
If you specify a subset of the Advanced Server member nodes, in order for external authentication requests to be processed properly, the Advanced Server should be running (available) on at least one of those specified cluster members. Otherwise, even if another Advanced Server member node not specified in the list is currently running, the requests will not be processed. |
To allow users to be externally authenticated over DECnet-Plus for
OpenVMS, set the OpenVMS system parameter NET_CALLOUTS to 255. This
enables Advanced Server user ID mapping and authentication for network
logins.
5.7.2.1 Configuring the Server Capacity for External Authentication
By default, the Advanced Server can support up to 10 simultaneous
external authentication logon requests (signons). You can modify this
maximum to suit the server requirements, using the Configuration
Manager. For more details, refer to the Compaq Advanced Server for OpenVMS Server Administrator's Guide.
5.7.3 Configuring Externally Authenticated Client Connections
By default, the Advanced Server supports the processing of up to 10 simultaneous external authentication requests. You can modify this maximum to suit the Advanced Server requirements, using the Configuration Manager. To start the Configuration Manager, enter the following command:
$ ADMINISTER/CONFIGURATION |
The basic server parameters include the number of simultaneous activations for users with external authentication.
For more information about using the Configuration Manager, refer to the Compaq Advanced Server for OpenVMS Server Administrator's Guide.
| Previous | Next | Contents | Index |