PATHWORKS for Digital UNIX Server Installation and Configuration Guide Part Number: AA-Q01HE-TE October 1996 This guide describes how to install a PATHWORKS for Digital UNIX server, as well as how to configure it for systems that use PATHWORKS Advanced Server and PATHWORKS NetWare services. Revision/Update Information: This document supersedes the PATHWORKS for DEC OSF/1 Server Installation Guide, part number AA-Q01HD-TE. Operating System and Version: Digital UNIX Version 4.0 Software Version: PATHWORKS Version 6.1 for Digital UNIX (Advanced Server) PATHWORKS V5.0B for Digital UNIX (NetWare) Digital Equipment Corporation Maynard, Massachusetts First published March 1994 Revised, March 1996 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation and other parties. Possession, use, or copying of the software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. c Digital Equipment Corporation 1996. All rights reserved. The following are trademarks of Digital Equipment Corporation: Alpha Station, AXP, DEC, DECnet, Digital, EtherWORKS, PATHWORKS, PCSA, VAX, and the DIGITAL logo. The following are third-party trademarks: 3Com and EtherLink are registered trademarks of 3Com Corporation. PostScript is a registered trademark of Adobe Systems, Inc. IBM and OS/2 are registered trademarks of International Business Machines Corporation. Windows is a trademark and MS Windows, Windows NT, and Windows 95 are registered trademarks of Microsoft Corporation. NetBIOS is a trademark of Micro Computer Systems, Inc. NetWare is a registered trademarks of Novell, Inc. OSF/1 is a registered trademark of the Open Software Foundation. UNIX is a registered trademark of UNIX Systems Laboratories, Inc., a wholly-owned subsidiary of Novell, Inc. All other trademarks and registered trademarks are the property of their respective holders. Table of Contents 1 PREPARING TO INSTALL PATHWORKS FOR DIGITAL UNIX BEFORE YOU BEGIN DECIDING WHICH SOFTWARE TO INSTALL PLANNING TO INSTALL PATHWORKS ADVANCED SERVER SOFTWARE DETERMINING THE SERVER TYPE FOR SERVER UPGRADES FOR NEW SERVERS CHECKING DISK SPACE FOR INSTALLATION SUBSETS DETERMINING ADEQUATE DISK SPACE FOR PATHWORKS ADVANCED SERVER FILES STORING PATHWORKS DATA IN CUSTOMIZED LOCATIONS DETERMINING THE NUMBER OF CLIENTS DETERMINING THE NUMBER OF SERVER SESSIONS DETERMINING THE AMOUNT OF SHARED MEMORY DETERMINING ACCESS TO DIGITAL UNIX AND PATHWORKS NETWARE DETERMINING USERS, GROUPS, SECURITY AND PERMISSIONS CONFIGURING PCSA MAIL PLANNING TO INSTALL PATHWORKS NETWARE SOFTWARE CHECKING DISK SPACE FOR INSTALLATION SUBSETS DETERMINING ADEQUATE DISK SPACE FOR PATHWORKS NETWARE FILES STORING PATHWORKS NETWARE DATA IN CUSTOMIZED LOCATIONS DETERMINING THE INTERNAL ADDRESS, NETWORK ADDRESS AND FRAME TYPE DETERMINING THE NUMBER OF CONNECTIONS DETERMINING ACCESS TO DIGITAL UNIX AND PATHWORKS ADVANCED SERVER DETERMINING IF YOU SHARE BYTE LOCKING INFORMATION DETERMINING DIRECTORIES, CLIENTS, SECURITY AND LOGIN SCRIPTS PLANNING TO INSTALL PATHWORKS ADVANCED SERVER AND PATHWORKS NETWARE SOFTWARE INSTALLING AND CONFIGURING PATHWORKS ADVANCED SERVER AND PATHWORKS NETWARE CREATING DIGITAL UNIX ACCOUNTS CREATING PATHWORKS ADVANCED SERVER ACCOUNTS CREATING PATHWORKS NETWARE ACCOUNTS CREATING SHARES AND VOLUMES PLANNING LICENSING DECIDING WHERE TO INSTALL THE LICENSE SERVER ADDING PRODUCT LICENSES CONFIGURING SERVER LICENSES FOR A WINDOWS NT ADVANCED SERVER OR MICROSOFT RETAIL CLIENT PREPARING THE DIGITAL UNIX SYSTEM CHECKING DIGITAL UNIX SUBSETS AND LAYERED PRODUCTS CHECKING DIGITAL UNIX KERNEL COMPONENTS CHECKING DIGITAL UNIX SWAP SPACE CHECKING THE NUMBER OF OPEN FILES CONFIGURING TCP/IP INSTALLING DECNET/OSI BACKING UP THE SYSTEM CHECKING THE HARDWARE CONFIGURATION UPGRADING THE OPERATING SYSTEM GENERAL PROCEDURE REMOVING THE PREVIOUS PATHWORKS PRODUCT CREATING A BACKUP COPY OF SERVER FILES NEXT STEPS 2 INSTALLING PATHWORKS FOR DIGITAL UNIX INSTALLATION SUBSETS COMMON SUBSETS PATHWORKS ADVANCED SERVER SUBSETS PATHWORKS NETWARE SUBSETS USING THE CDMENU AND SETLD UTILITIES INSTALLING RELEASE NOTES INSTALLING PATHWORKS FOR DIGITAL UNIX SUBSETS INSTALLING PATHWORKS ICONS RESTORING BACKUP SERVER FILES NEXT STEPS 3 CONFIGURING PATHWORKS FOR DIGITAL UNIX CONFIGURING NETWORK CONTROLLERS SUPPLYING PATHWORKS ADVANCED SERVER CONTROLLER INFORMATION CONFIGURING WAN SUPPORT SUPPLYING PATHWORKS NETWARE CONTROLLER INFORMATION CHANGING CONTROLLER INFORMATION USING PWSETUP KERNEL REBOOTING THE SYSTEM CONFIGURING THE SERVER HOW THE PWSETUP CONFIGURE UTILITY WORKS CONFIGURING PATHWORKS ADVANCED SERVER SYSTEMS CONFIGURING PATHWORKS NETWARE SYSTEMS CONFIGURING PATHWORKS ADVANCED SERVER AND PATHWORKS NETWARE SYSTEMS CONFIGURING PATHWORKS FOR DEC OSF/1 UPGRADES UPGRADING A STANDALONE SERVER UPGRADING A MEMBER SERVER UPGRADING A PRIMARY OR BACKUP SERVER CONFIGURING PATHWORKS ADVANCED SERVER ON A NEW SERVER CONFIGURING PATHWORKS ADVANCED SERVER PRIMARY DOMAIN CONTROLLER CONFIGURING A BACKUP DOMAIN CONTROLLER USING A PATHWORKS FOR DEC OSF/1 BACKUP SERVER IN A PATHWORKS ADVANCED SERVER DOMAIN INSTALLING WINDOWS NT SERVER TOOLS INSTALLING WINDOWS NT SERVER TOOLS SOFTWARE EDITING CONFIG.SYS AND AUTOEXEC.BAT CLIENT FILES INSTALLING WINDOWS NT ADMINISTRATIVE TOOLS INSTALLING ON A WINDOWS 3.X OR WINDOWS NT COMPUTER INSTALLING ON A WINDOWS 95 COMPUTER SETTING UP BROWSING CONFIGURING A PATHWORKS NETWARE SERVER CONFIGURING THE LICENSE SERVER CONFIGURING PATHWORKS IN A TRUCLUSTER ENVIRONMENT NEXT STEPS 4 SERVER SETUP AND TUNING SETTING UP AND TUNING PATHWORKS ADVANCED SERVER SOFTWARE SPECIFYING THE NUMBER OF CLIENTS SPECIFYING THE NUMBER OF SERVER SESSIONS RESETTING THE NUMBER OF SESSIONS FOR THE NETBEUI TRANSPORT RESETTING THE NUMBER OF SESSIONS FOR THE TCP/IP TRANSPORT MODIFYING SHARED MEMORY ON PATHWORKS ADVANCED SERVER SYSTEMS CONFIGURING PCSA MAIL TUNING PATHWORKS NETWARE SOFTWARE SPECIFYING PATHWORKS NETWARE CONNECTIONS SETTING UP AND TUNING PATHWORKS ADVANCED SERVER AND PATHWORKS NETWARE SOFTWARE SETTING UP SHARES AND VOLUMES MODIFYING CONTROLLER INFORMATION RE-RUNNING PWSETUP KERNEL EDITING THE PATHWORKS.INI CONFIGURATION FILE A THE PATHWORKS CONFIGURATION FILE FILE ORGANIZATION PATHWORKS.INI FILE SECTIONS FILE SYNTAX SAMPLE PATHWORKS.INI FILE MODIFYING THE PATHWORKS.INI FILE USING THE PWINICONF UTILITY PATHWORKS.INI KEYWORDS [PWIPNET] KEYWORDS [PWDECNET] KEYWORDS [PWDATALINK] KEYWORDS [LICENSESERVER] KEYWORDS [LICENSEREGISTRAR] KEYWORDS [PWSERVER] KEYWORDS B THE LMXUPGRADE COMMAND C CONFIGURING THE PATHWORKS ADVANCED SERVER REMOTE BOOT SERVICE REMOVING REMOTE BOOT SERVICE SETTING UP REMOTE BOOT SERVICE SETTING UP REMOTE BOOT SERVICE OVER MOP CONFIGURING DOS WORKSTATIONS PREVIOUS TO VERSION 4.01 ADDITIONAL INFORMATION D ERROR CONDITIONS INSTALLATION ERROR MESSAGES PATHWORKS ADVANCED SERVER INSTALLATION VERIFICATION (IVP) ERRORS CONFIGURATION ERROR MESSAGES Preface Purpose This guide explains how to install PATHWORKS for Digital UNIX (Advanced Server) Version 6.0 and PATHWORKS for Digital UNIX (NetWare) Version 5.0A. Product Naming Conventions This guide uses the following product names: Name Description PATHWORKS for Digital Refers to the most UNIX recent version of the product, which includes both PATHWORKS Advanced Server and PATHWORKS NetWare software. PATHWORKS for DEC Refers to the previous OSF/1 version of PATHWORKS for Digital UNIX, which includes both PATHWORKS LAN Manager, Version 5.0G and PATHWORKS NetWare, version 5.0A. Audience This guide is written for system administrators who are installing PATHWORKS for Digital UNIX. Organization This guide is organized as follows: Chapter Description Preparing to Describes prerequisites to Install PATHWORKS the installation for Digital UNIX procedure. Installing Describes how to install PATHWORKS for PATHWORKS for Digital UNIX Digital UNIX software. Configuring Describes how to configure PATHWORKS for PATHWORKS for Digital UNIX Digital UNIX software. Server Setup and Describes how to setup and Tuning tune PATHWORKS for Digital UNIX after the installation is complete. The PATHWORKS Describes the Configuration File pathworks.ini file. This file defines the configuration of your PATHWORKS for Digital UNIX software. The lmxupgrade Describes how to use the Command lmxupgrade command to upgrade a PATHWORKS for DEC OSF/1 server. Configuring the Provides an overview of PATHWORKS Advanced how to configure the Server Remote Boot Remote Boot service on a Service PATHWORKS for Digital UNIX server. Error Conditions Describes error conditions and recommends ways to correct them. Related Documents Table 1, PATHWORKS for Digital UNIX (Advanced Server) Documentation, provides more information about PATHWORKS for Digital UNIX software: Table 1: PATHWORKS for Digital UNIX (Advanced Server) Documentation Document Description PATHWORKS for Digital Explains how to use UNIX (Advanced Server) PATHWORKS for Digital System Guide UNIX software. PATHWORKS Remote Boot Provides task based Guide (Advanced information about Server) Remote Boot software. PATHWORKS for Digital Provides conceptual UNIX Installation and and task based Configuration information about how to install and configure a PATHWORKS for Digital UNIX server. PATHWORKS for Digital Provides an overview UNIX (Advanced Server) of PATHWORKS for Concepts and Planning Digital UNIX software. Guide Table 2, PATHWORKS for DEC OSF/1 NetWare Documentation, provides information about PATHWORKS NetWare: Table 2: PATHWORKS for DEC OSF/1 NetWare Documentation Document Description PATHWORKS for DEC Provides conceptual OSF/1 NetWare Concepts information about NetWare concepts and terminology. PATHWORKS for DEC Explains how to plan OSF/1 NetWare Planning and configure a and Setup NetWare network. PATHWORKS for DEC Provides detailed OSF/1 NetWare System information for system Administration managers about how to use SCONSOLE to manage NetWare file systems and users. PATHWORKS for DEC Provides details about OSF/1 NetWare common network Troubleshooting and problems and how to System Messages solve them. Also lists system messages and recommended actions. PATHWORKS for DEC Provides detailed OSF/1 NetWare Print information for system Server managers about how to set up and manage NetWare print services. PATHWORKS for DEC Provides detailed OSF/1 NetWare information for both Utilities system managers and end users about how to use NetWare Utilities. Table 3, Common Documents, includes information about both PATHWORKS Advanced Server and PATHWORKS NetWare software: Table 3: Commonn Documents Document Description Guide to Managing Provides conceptual PATHWORKS Licenses and task based information about License Management Software. PATHWORKS for Digital Provides step-by-step UNIX Installation and instructions about how Configuration to install and configure your PATHWORKS for Digital UNIX software. PATHWORKS for Digital This guide explains UNIX TruCluster Family how to install, set Administrator's Guide up, maintain and troubleshoot PATHWORKS for Digital UNIX as a highly available service in a TruCluster Family Software environment. Conventions Table 4, Conventions Used in this Guide, lists the conventions used in this guide: Table 4: Conventions Used in this Guide Convention Meaning Ctrl x key While you hold down Ctrl, press another key or a pointing device button. Return key Press the key that executes commands or terminates a sequence. This key is labeled Return or Enter, depending on your keyboard. "enter" Type all required text, spaces, and punctuation marks; then press Return or Enter, depending on your keyboard. case Digital UNIX commands are case-sensitive. You must enter commands in the correct case, as printed in the text. monospace text Indicates examples of system output or user input. Note Notes provide information of special importance. Caution Cautions provide information to prevent damage to equipment or software. 1 Preparing to Install PATHWORKS for Digital UNIX This chapter provides an overview of the requirements for installing PATHWORKS Advanced Server and PATHWORKS NetWare software, and provides worksheets that you can use during installation. If you are installing PATHWORKS for Digital UNIX for the first time, read this chapter to learn about system prerequisites and requirements. If you are upgrading PATHWORKS for Digital UNIX, read this chapter for information about removing previous versions. This chapter describes how to: Decide which software to install Plan a PATHWORKS Advanced Server configuration Plan a PATHWORKS NetWare configuration Plan a PATHWORKS Advanced Server and a PATHWORKS NetWare configuration Decide where to install licensing software Prepare the Digital UNIX system Check the hardware configuration Upgrade the operating system Remove the previous version of PATHWORKS Before you Begin Check your Distribution Kit before you begin the installation. The Distribution Kit contains the software parts list, which specifies the number and contents of the media you receive. Be sure to check the contents of your kit with that information. If your kit is damaged or parts are missing, contact your Digital representative. Deciding Which Software to Install PATHWORKS for Digital UNIX includes PATHWORKS Advanced Server and PATHWORKS NetWare software. The software you install depends on the kind of clients in your configuration. If your configuration includes PATHWORKS LAN Manager clients or retail LAN Manager clients, install PATHWORKS Advanced Server software. If your configuration includes PATHWORKS NetWare clients or retail NetWare clients, install PATHWORKS NetWare software. If your configuration includes both PATHWORKS LAN Manager or retail LAN Manager clients and PATHWORKS NetWare clients or retail NetWare clients, install both PATHWORKS Advanced Server and PATHWORKS NetWare software. Planning to Install PATHWORKS Advanced Server Software Table 1-1, Worksheet for Installing PATHWORKS Advanced Server Software, provides a worksheet of the things you should determine before installing PATHWORKS Advanced Server software. The sections that follow this worksheet provide details about each checklist item. Table 1-1 : Worksheet for Installing PATHWORKS Advanced Server Software Worksheet for Installing PATHWORKS Advanced Server Software The type of server (backup or primary) that you want to install: Backup ______ Primary _____ The amount of disk space required for installation of PATHWORKS Advanced Server subsets: Space in the /usr partition ______ The amount of disk space for the PATHWORKS Advanced Server files (configuration files, error and log files, shared directories and programs, user data): Space in the /var directory ______ The number of clients that will use the server: Number of clients ______ The number of simultaneous PATHWORKS sessions you need to service client requests: Number of sessions ______ The amount of shared memory you need for your configuration: Amount of shared memory ______ Which PATHWORKS Advanced Server users need access to PATHWORKS NetWare, and to the Digital UNIX server: Users: __________________________ ___________________________ ___________________________ ___________________________ Sample plan to set up user accounts, groups, security and permissions: (attach separately) Do you need to configure PCSA Mail for PATHWORKS clients that use TCP/IP or DECnet? Yes ______ No ______ Do you plan to use PATHWORKS as a service in a Digital UNIX TruClusters environment? Yes ______ No ______ Determining the Server Type The following section describes how to decide the server role. For Server Upgrades The PATHWORKS Advanced Server supports the primary domain controller and backup domain controller server types. However, both the standalone or member server types are no longer available. If your previous configuration contained either a standalone or member server, Digital recommends that you: Upgrade the standalone server to a primary server type Upgrade the member server to a backup server type For more information, see Configuring PATHWORKS for DEC OSF/1 Upgrades, in this guide. For New Servers Before you install PATHWORKS Advanced Server software, you must decide whether the server you are installing is one of the following: Primary domain controller This is a server that maintains user account information and distributes it to backup domain controllers in the same domain. A primary domain controller also validates logon requests made by clients. The primary domain controller must be the first PATHWORKS Advanced Server that you install on the domain. Only one primary domain controller is allowed in a domain. If you configure a server as a primary domain controller in a domain that already exists, the result will be two domains of the same name, neither of which will operate properly. Backup domain controller This is a server that receives user account information and user logon scripts from the primary domain controller. A backup domain controller can also validate logon requests made by clients. If the primary domain controller fails, a backup domain controller can be promoted to primary. To install a backup domain controller, a primary domain controller must be running on the domain. For more information about setting up a domain and about server roles in a domain, see the PATHWORKS for Digital UNIX (Advanced Server) System Guide. Checking Disk Space for Installation Subsets Check the /usr partition to ensure you have enough disk space for the subsets that you want to install. Table 1-2, PATHWORKS Advanced Server Subsets, lists the disk space requirements for PATHWORKS Advanced Server subsets. Table 1-2: PATHWORKS Advanced Server Subsets Software Subset Name Space (MB) PATHWORKS for Digital PWKBASE610 41 UNIX PATHWORKS NetBIOS for PWKTCP4610 1 TCP/IP Driver PATHWORKS NetBIOS for PWKDNA4610 1 DECnet Driver PATHWORKS NetBEUI PWKNBU4610 1 Driver PATHWORKS Remote Boot PWKRPL610 2 Service Total 46 In addition, you will need disk space for the following common subsets. The PATHWORKS Configuration subsets are required by both PATHWORKS Advanced Server and PATHWORKS NetWare. Table 1-3, Common Subsets, lists the common subsets and their space requirements: Table 1-3: Common Subsets Software Subset Name Space (MB) PATHWORKS PWKCONFIG610 3 Configuration PATHWORKS Man Pages PWKMAN610 1 License Server PWKLIC610 1 PATHWORKS Release PWKRNOTE610 1 Notes Total 6 To determine the amount of free disk space in the /usr directory, enter the following: # df -k /usr The system displays information similar to the following: Filesystem 1024-blocks Used Avail Capacity Mounted on /dev/rz3g 741095 323065 343902 48% /usr Determining Adequate Disk Space for PATHWORKS Advanced Server Files Check your file system to ensure that you have enough space to run the PATHWORKS Advanced Server, to store PATHWORKS Advanced Server files, and to provide for shared network resources. The amount of space you need depends on the: Number of users Amount of user data Number and size of shared programs and directories Procedures for storing error, log, and configuration files Unless you specify otherwise, PATHWORKS Advanced Server software stores your files in /var/net/servers, and creates a symbolic link from /usr/net/servers to /var/net/servers. Check the /var directory to ensure adequate disk space for the files your server will use. For example: df -k /var Storing PATHWORKS Data in Customized Locations PATHWORKS Advanced Server software provides you with a way to specify a directory, other than the default, to store server shares and server home directories. This is so you can place data in a location where, for example, you have sufficient disk space, or where other similar data resides. To select a location for server shares, specify either the default location or the location that you want at the system prompt during the installation procedure. If you select the default location, PATHWORKS Advanced Server places the lanman shares in the /usr/net/servers/lanman/shares directory. If you select a new location, PATHWORKS Advanced Server creates a soft link from /usr/net/servers/lanman/shares to the directory you specify. Any files that you add after installation reside in the directory you specify. Be sure that this directory has enough disk space to store any files you plan to add. To select a location for server home directories, you must respond to a system prompt that displays during server configuration. By default, PATHWORKS for Digital UNIX creates the /usr/net/servers/lanman/users directory. You can accept the default directory, or you can specify another location. If you want PATHWORKS Advanced Server users to have access to their home directory, you will need to make it a share after you complete the installation and configuration of PATHWORKS Advanced Server software. Determining the Number of Clients The number of clients you should configure depends on how your clients are configured and how quickly you want the server to respond. For example, diskless clients and clients that use shared applications typically consume more server resources than clients that run applications locally. By default, the PATHWORKS Advanced Server is configured to allow 250 clients to connect to the server. If you want to adjust this number after you complete the PATHWORKS Advanced Server installation, see Chapter 4, Server Setup and Tuning, in this guide. Determining the Number of Server Sessions PATHWORKS for Digital UNIX opens a session each time a client connects to the server. The number of server sessions you set determines how many simultaneous sessions your server can open. For example, a server with both a NetBEUI and TCP/IP controller, each set at 256 sessions, can service 256 simultaneous client connections on each controller. If your configuration supports an unusually large number of clients, it may be necessary to add additional sessions. By default, sessions for the PATHWORKS Advanced Server are set to the values shown in Table 1-4: Table 1-4: PATHWORKS Session Defaults Transport Default Setting NetBEUI 256 TCP/IP 256 The server may use up to 16 of these sessions for its own ` internal use, leaving approximately 240 sessions available to the user. DECnet/OSI Determined by the DECnet/OSI software and your system configuration. Refer to DECnet/OSI documentation for additional information For additional information see Chapter 4, Server Set up and Tuning, in this guide, after you complete PATHWORKS Advanced Server installation. Determining the Amount of Shared Memory The PATHWORKS Advanced Server uses shared memory to store information about client connections, files that each client opens, file and record locks, and so on. PATHWORKS allocates shared memory automatically, based on server configuration parameters. PATHWORKS Advanced Server configurations that are very large occasionally must allocate additional shared memory. You should allocate additional memory carefully, and only if the server denies file open requests. For information about how and when to allocate additional memory, see Chapter 4, Server Setup and Tuning, in this guide, after you complete PATHWORKS Advanced Server installation. Determining Access to Digital UNIX and PATHWORKS NetWare Before you create the PATHWORKS Advanced Server users, you should consider who needs access to the Digital UNIX server, and set up the appropriate server account. See Creating Digital UNIX Accounts, in this guide, for additional information. Also, consider which users need access to PATHWORKS NetWare services. See Creating PATHWORKS NetWare Accounts, in this guide, for additional information. Determining Users, Groups, Security and Permissions To set up a PATHWORKS Advanced Server system, you need to plan the user accounts, groups, security, and permissions that you want to use. See the PATHWORKS for Digital UNIX (Advanced Server) System Guide for information about how to set up your server after it is installed and configured. Configuring PCSA Mail To use PCSA Mail, you must have mh installed and configured on your system. The subset that contains mh software is OSFMH400. To configure PCSA mail on a PATHWORKS LAN Manager client that uses TCP/IP or DECnet, you must provide the user with restricted access to the PATHWORKS for Digital UNIX server. For additional information, see Chapter 4, Server Setup and Tuning, in this guide. Planning to Install PATHWORKS NetWare Software Table 1-5, Worksheet for Installing PATHWORKS NetWare, provides a worksheet of the things you should consider before installing PATHWORKS NetWare software. The sections that follow the worksheet provide details about each worksheet item. Table 1-5: Worksheet for Installing PATHWORKS NetWare Worksheet for Installing PATHWORKS NetWare The amount of disk space required for installation of PATHWORKS NetWare subsets: Space in the /usr partition ______ The amount of disk space for the PATHWORKS Netware files (configuration files, error and log files, shared directories and programs, user data): Space in the /var directory ______ The internal address, network address, and frame type you want the server to use: Internal address __________________ Network address __________________ Frame Type __________________ The number of simultaneous PATHWORKS sessions you need to service client requests: Number of sessions ______ Which PATHWORKS NetWare users need access to PATHWORKS Advanced Server and to the Digital UNIX server: Users: __________________________ __________________________ ___________________________ ___________________________ The existence of byte locking information that you share with other applications: Shared with other applications _______ Not shared with other applications _______ Sample plan for set up of directory structure, clients, security, and login scripts:(attach separately) Do you plan to use PATHWORKS as a service in a Digital UNIX TruClusters environment? Yes ______ No ______ Checking Disk Space for Installation Subsets Check the /usr partition to ensure you have enough disk space for the subsets that you want to install. PATHWORKS NetWare subsets require the following disk space shown in Table 1-6: Table 1-6: PATHWORKS NetWare Subsets Software Subset Name Space (MB) NetWare 3.11b System PWKNW3SVOL610 15 Volume NetWare Services PWKNWBASE610 7 NetWare Transports PWKNWTRAN4610 2 Total 24 The subsets listed in Table 1-7 are used by both the PATHWORKS Advanced Server and PATHWORKS NetWare servers: Table 1-7: Common Subsets Software Subset Name Space (MB) PATHWORKS PWKCONFIG610 3 Configuration PATHWORKS Man Pages PWKMAN610 1 License Server PWKLIC610 1 PATHWORKS Release PWKRNOTE610 1 Notes Total 6 To determine the amount of free space in the /usr directory, enter the following: # df -k /usr The terminal displays information similar to the following: Filesystem 1024-blocks Used Avail Capacity Mounted on /dev/rz3g 741095 323065 343902 48% /usr Determining Adequate Disk Space for PATHWORKS NetWare Files Check your file system to ensure that you have enough space to run PATHWORKS NetWare, to store PATHWORKS NetWare files, and to provide for shared network resources. The amount of space you need depends upon the: Number of users Amount of user data Number and size of shared volumes Procedures for storing error, log, and configuration files Unless you specify otherwise, PATHWORKS NetWare software stores your files in /var/net/servers, and creates a symbolic link from /usr/net/servers to /var/net/servers. Check the /var directory to ensure adequate disk space for the files your server will use. For example: df -k /var Storing PATHWORKS NetWare Data in Customized Locations PATHWORKS NetWare software provides you with a way to specify a directory, other than the default, to store the NetWare System Volume (subset PWKNW3SVOL610) and the server home directories. This is so you can store this data in a directory where, for example, you know you have sufficient disk space, or in a location where similar data resides. To specify a location for the NetWare system volume, you must respond to the system prompt that is displayed during PATHWORKS NetWare installation. If you select the default location, PATHWORKS NetWare places the System Volume in the /usr/opt directory, and then creates a softlink to /usr/net/servers/netware/vol/sys. If you select a new location, PATHWORKS NetWare places the System Volume in the /usr/opt directory, and creates a softlink to the location you specify. Any files that you add after installation reside in the directory you specify. The PATHWORKS NetWare System Volume, with no additional files, uses 17MB of disk space. You must make sure that the /usr/opt directory has enough disk space to store the System Volume, regardless of the directory location that you specify during installation. To select a location for server home directories, you must respond to a system prompt that is displayed during server configuration. By default, PATHWORKS for Digital UNIX creates the /usr/net/servers/netware/users directory. You can accept the default directory, or you can specify another location. Note that if you want PATHWORKS NetWare users to have access to their home directory, you will need to make it a volume after you complete the installation and configuration of PATHWORKS NetWare software. Determining the Internal Address, Network Address and Frame Type The PATHWORKS NetWare configuration procedure prompts you for the internal address, network address, and frame type that you want the server to use. The internal address is a four byte hexadecimal number that uniquely identifies your server. During configuration, PATHWORKS NetWare creates an internal address by converting the address of the first TCP/IP controller it locates to a hexadecimal value. You can accept the internal network address or enter one of your own. If TCP/IP is not configured on your system, PATHWORKS NetWare is unable to find a TCP/IP controller, and will not generate a default internal address. You must specify your own internal address when the configuration program prompts you. The address you specify can be any hexadecimal number from 1 to FFFFFFFE. However, the number that you select must uniquely identify the server you are installing. The network address identifies the physical network that the server connects to. During installation, PATHWORKS NetWare displays a network number for each controller you choose to configure. You can accept the network address or enter one of your own. The frame type is the kind of message packet that you want your server to use. Table 1-8, PATHWORKS NetWare Supported Frame Types, lists the frame types supported by PATHWORKS NetWare. Table 1-8: PATHWORKS NetWare Supported Frame Types Hardware Supported Frame Types Ethernet Ethernet II IEEE 802.2 IEEE 802.2 SNAP SAP IEEE 802.3 RAW Token Ring IEEE 802.2 IEEE 802.2 SNAP SAP FDDI IEEE 802.2 IEEE 802.2 SNAP SAP The NET.CFG file, on the client, contains frame type information. Unless you specify otherwise, PATHWORKS NetWare software uses Ethernet II. Refer to PATHWORKS for DEC OSF/1 NetWare Concepts, PATHWORKS for DEC OSF/1 NetWare System Administration, and PATHWORKS for DEC OSF/1 NetWare Utilities for information about how to use network addresses and frame types. Determining the Number of Connections The number of connections available on a PATHWORKS NetWare server is determined by the value of the max_connections parameter in the /usr/net/servers/netware/etc/NWConfig file. The default value is 50 connections; the maximum is 1000. If your configuration includes more than 50 clients, you should reset this default after you complete the installation. If you reset this default to a value greater than 250, you must also set the shm-size parameter in the NW Config file. For information about increasing the number of connections after you complete PATHWORKS NetWare installation, see Chapter 4, Server Setup and Tuning, in this guide. Determining Access to Digital UNIX and PATHWORKS Advanced Server Before you create the PATHWORKS NetWare users, you should consider who needs access to the Digital UNIX server, and set up the appropriate server account. Also consider which users need access to PATHWORKS Advanced Server. For additional information, see Creating PATHWORKS NetWare Accounts, in this guide. Determining If You Share Byte Locking Information The native_locks.flag in the /usr/server/netware/etc/NWConfig file should be set inactive on servers that share no byte locking information. Set the native_locks flag to inactive if both of the following are true : Your server is configured to run only PATHWORKS NetWare software Your server does not share PATHWORKS for Digital UNIX or PATHWORKS for DEC OSF/1 byte locking information with any other Digital UNIX applications Determining Directories, Clients, Security and Login Scripts To set up a PATHWORKS NetWare server, you need to plan the directory structure, clients, network security, and login scripts. Refer to PATHWORKS for DEC OSF/1NetWare Planning and Setup for additional information. Planning to Install PATHWORKS Advanced Server and PATHWORKS NetWare Software Table 1-9, Worksheet for Installing PATHWORKS Advanced Server and PATHWORKS NetWare, provides a list of what you need to do to install both PATHWORKS Advanced Server and PATHWORKS NetWare software. The sections that follow the worksheet provide details about each checklist item. Table 1-9: Worksheet for Installing PATHWORKS Advanced Server and PATHWORKS NetWare Worksheet for Installing PATHWORKS Advanced Server and PATHWORKS NetWare Install and configure server software: PATHWORKS Advanced Server software installed______ PATHWORKS NetWare software installed______ Determine which users will need access to the host system: User 1 ____________________________ User 2 ____________________________ User 3 ____________________________ Create the host system accounts for each user: User 1 ____________________________ User 2 ____________________________ User 3 ____________________________ Determine the users that will need access to PATHWORKS Advanced Server services. User 1 ____________________________ User 2 ____________________________ User 3 ____________________________ Create the PATHWORKS Advanced Server accounts for each user: User 1 ____________________________ User 2 ____________________________ User 3 ____________________________ Determine the users that will need access to PATHWORKS NetWare services. User 1 ____________________________ User 2 ____________________________ User 3 ____________________________ Create the PATHWORKS NetWare accounts for each user: User 1 ____________________________ User 2 ____________________________ User 3 ____________________________ Create the PATHWORKS Advanced Server shares and PATHWORKS NetWare volumes that you need: Create PATHWORKS Advanced Server shares ______ Create PATHWORKS NetWare volume: ______ Installing and Configuring PATHWORKS Advanced Server and PATHWORKS NetWare You can install both PATHWORKS Advanced Server and PATHWORKS NetWare software on the same host system. For additional information, see Planning to Install PATHWORKS Advanced Server Software and Planning to Install PATHWORKS NetWare Software, in this guide. Creating Digital UNIX Accounts Determine who needs login access to the host system, and then create the Digital UNIX accounts. You should do this before you create the corresponding PATHWORKS user account. This is because the PATHWORKS user account automatically checks for an existing Digital UNIX account of the same name. If there is an existing account, PATHWORKS uses it to determine ownership and access to files on the Digital UNIX system. If there is no existing account, PATHWORKS creates one for you. However, the Digital UNIX account that PATHWORKS creates does not provide login access to the host system, and in an Enhanced Security Environment the accounts are also created locked. For additional information about PATHWORKS Advanced Server accounts, see the PATHWORKS for Digital UNIX (Advanced Server) System Guide. For information about PATHWORKS NetWare accounts, see PATHWORKS for DEC OSF/1 NetWare Concepts and PATHWORKS for DEC OSF/1 NetWare System Administration. Creating PATHWORKS Advanced Server Accounts To create a user account from the server, use the pwadmin utility. To create a user account from the client, use either Digital's ManageWORKS Workgroup Administrator interface or the User Manager for Windows. The PATHWORKS Advanced Server accounts you create use Digital UNIX accounts in the following ways: If you add a PATHWORKS Advanced Server account and a Digital UNIX account of the same name exists, PATHWORKS references the Digital UNIX account for file ownership and group access information. For example, if a Digital UNIX user named Jonsey creates a file as a PATHWORKS Advanced Server user Jonsey, the PATHWORKS Advanced Server files created are owned by user Jonsey, and carry the group access that is defined in Jonsey's Digital UNIX account. If you subsequently remove the PATHWORKS Advanced Server account, PATHWORKS deletes the Advanced Server account and leaves the Digital UNIX account untouched. This is because the account was created with Digital UNIX utilities, and existed prior to the creation of the PATHWORKS account. When you add a PATHWORKS Advanced Server account and a Digital UNIX account of the same name does not exist, PATHWORKS automatically creates a Digital UNIX account of the same name. PATHWORKS references the Digital UNIX account to determine file ownership and group access. However, the Digital UNIX account exists only in conjunction with PATHWORKS. It does not provide the user with login privileges to the Digital UNIX system, and you should not use it to set privileges, rights, or attributes on the host system. If you subsequently decide to remove the PATHWORKS Advanced Server account, PATHWORKS deletes both the Advanced Server account and the Digital UNIX account. If you add a PATHWORKS Advanced Server account, and a Digital UNIX account with the same name exists and is marked as the account of a PATHWORKS NetWare user, PATHWORKS tags the account as that of a PATHWORKS Advanced Server user, and then references it to determine file ownership and group access information. For example, if you create a PATHWORKS Advanced Server account for Jonsey, PATHWORKS checks to see if Jonsey's Digital UNIX account is tagged with the NetWare attribute. If it is, PATHWORKS tags the account as that of a PATHWORKS Advanced Server user as well. When Jonsey subsequently creates a file using the PATHWORKS Advanced Server, the file is owned by user Jonsey and carries the group access that is defined in Jonsey's Digital UNIX account. If you subsequently remove the PATHWORKS Advanced Server account, PATHWORKS deletes the Advanced Server account and removes the Advanced Server attribute from the Digital UNIX account. This retains the user's access to NetWare, but removes access to the PATHWORKS Advanced Server. Note The createunixuser keyword, in the lanman.ini file, must be set to YES to automatically create the UNIX account that the system uses to map to the corresponding PATHWORKS Advanced Server account. Refer to the PATHWORKS for Digital UNIX (Advanced Server) System Guide for additional information about adding user accounts and modifying the lanman.ini file. Creating PATHWORKS NetWare Accounts You can create PATHWORKS NetWare accounts using any of the following utilities: sconsole or nwuser utilities, on the host system SYSCON utility, on the client system Digital's ManageWORKS Workgroup Administrator interface, on the client system All PATHWORKS NetWare user accounts that you create on a PATHWORKS for Digital UNIX server are hybrid accounts. This means that the PATHWORKS NetWare user has a related account of the same name on the Digital UNIX system. The PATHWORKS NetWare account is related to Digital UNIX account in the following ways: If you add a PATHWORKS NetWare account and a Digital UNIX account of the same name exists, PATHWORKS references the Digital UNIX account for file ownership and group access information. For example, if a Digital UNIX user named Jonsey creates a file as a PATHWORKS NetWare user Jonsey, the PATHWORKS NetWare files created are owned by user Jonsey, and carry the group access that is defined in Jonsey's Digital UNIX account. If you subsequently remove the PATHWORKS NetWare account, PATHWORKS deletes the NetWare account and leaves the Digital UNIX account untouched. This is because the account was created with Digital UNIX utilities and it existed prior to the creation of the PATHWORKS account. When you add a PATHWORKS NetWare account and a Digital UNIX account of the same name does not exist, PATHWORKS automatically creates a Digital UNIX account of the same name. PATHWORKS references the Digital UNIX account to determine file ownership and group access. However, the Digital UNIX account exists only in conjunction with PATHWORKS. It does not provide the user with login privileges to the Digital UNIX system, and you should not use it to set privileges, rights, or attributes on the host system. If you subsequently decide to remove the PATHWORKS NetWare account, PATHWORKS deletes both the NetWare account and the Digital UNIX account. If you add a PATHWORKS NetWare account and a Digital UNIX account with the same name exists and is marked as the account of a PATHWORKS Advanced Server user, PATHWORKS tags the account as that of a PATHWORKS NetWare user, and then references it to determine file ownership and group access information. For example, if you create a PATHWORKS NetWare account for Jonsey, PATHWORKS checks to see if Jonsey's Digital UNIX account is tagged with the Advanced Server attribute. If it is, PATHWORKS tags the account as that of a PATHWORKS NetWare user as well. When Jonsey subsequently creates a file as PATHWORKS NetWare user Jonsey, the file is owned by user Jonsey and carries the group access that is defined in Jonsey's Digital UNIX account. If you subsequently remove the PATHWORKS NetWare account, PATHWORKS deletes the NetWare account and removes the NetWare attribute from the Digital UNIX account. This retains the user's access to the PATHWORKS Advanced Server, but removes access to NetWare. Refer to PATHWORKS for DEC OSF/1 NetWare Server Administration, PATHWORKS for DEC OSF/1 NetWare Utilities, and PATHWORKS for DEC OSF/1 NetWare Concepts for additional information. Creating Shares and Volumes PATHWORKS Advanced Server and PATHWORKS NetWare let you define the server directories you can use to store shared data. As long as the protections are set correctly, PATHWORKS Advanced Server and PATHWORKS NetWare users can share files and directories. If you plan to create a PATHWORKS Advanced Server share that maps to the same Digital UNIX directory location as a PATHWORKS NetWare volume, you must ensure that the directory and file access is compatible for both PATHWORKS Advanced Server and PATHWORKS NetWare users. For additional information, see Chapter 4, Server Setup and Tuning, in this guide. Planning Licensing The License Server subset contains a program that you can run on your server to assign and validate PATHWORKS Advanced Server and PATHWORKS NetWare client licenses. When the License Server is installed, clients can be assigned a license and use resources on any PATHWORKS server in the network. Clients cannot obtain a client license unless a License Server is installed and running on at least one server in the network. Deciding Where to Install the License Server Only one PATHWORKS server in each network should be configured to run the License Server. The PATHWORKS server that you configure with the License Server must be the same server that has the LMF client license product authorization keys (PAKs) loaded. The PATHWORKS for Digital UNIX installation procedure lets you install the License Server software subset on any server that you want. You must also install the PATHWORKS Configuration subset, and the subsets that contain transport software for the PATHWORKS clients. For example, if you plan to use the License Server to validate PATHWORKS NetWare clients, you must also install the PATHWORKS Configuration subset (PWKCONFIG610), and the NetWare Transports Subset (PWKNWTRAN4610). Adding Product Licenses There are two ways you can add product licenses to the License Server. You can: Load the PAKs you plan to use onto the PATHWORKS for Digital UNIX server and then configure PATHWORKS for Digital UNIX. The configuration procedure automatically adds all the available licenses to the License Server. Load the PAKs after the PATHWORKS for Digital UNIX configuration is complete. Then, use the License Manager to add the products with the licenses that you want to assign. PATHWORKS Advanced Server requires that you have a minimum version of 5.00 for client licenses, running on the server. Version 4.1 client licenses will not work. Refer to lmf(8), in the Digital UNIX Reference Pages, or to the Guide to Managing PATHWORKS Licenses for additional information about the License Server. Configuring Server Licenses for a Windows NT Advanced Server or Microsoft Retail Client You must configure the PATHWORKS Advanced Server software to include a server license for each Microsoft Retail Client (for example, Windows 95 client ) or Server (for example, a Windows NT server) with which it will communicate. A PATHWORKS Advanced Server configured without licenses cannot communicate with the NT Advanced Server. PATHWORKS clients require a server or client license. Preparing the Digital UNIX System Table 1-10, Worksheet for Preparing the Digital UNIX System, provides a checklist of the things you must do to prepare the Digital UNIX server. PATHWORKS for Digital UNIX is supported on Digital UNIX Version 4.0. Complete all the items on this list before you install PATHWORKS for Digital UNIX. The following sections provide details about each worksheet item. Table 1-10: Worksheet for Preparing the Digital UNIX System Worksheet for Preparing the Digital UNIX System Check for these required Digital UNIX subsets and layered products: The OSFSVID24xx UNIX SVID2 Compatibility Subset ______ The OSFPRINT4xx Local Printer Support Subset ______ DECnet OSI for Digital UNIX, Version 4.0 or DECnet for Small Configuration Version 4.0(Lightweight DECnet Configuration environment). One of these subsets is required only if you plan to install PATHWORKS LAN Manager software with the NetBIOS for DECnet driver subset, or if you plan to configure PATHWORKS Remote Boot service using the MOP protocol. ______ Check for these required Digital UNIX kernel components: File on File System (FFM) network option ______ ISO 9660 Compact Disk File System (CDFS) ______ Data Link Bridge (DLB) network option, if you want to install the PATHWORKS NetBIOS for DECnet subset or the PATHWORKS NetBEUI subset ______ Data Link Provider Interface (DLPI), if you want to install the PATHWORKS NetBEUI subset ______ X/Open Transport Interface (XTISO, TIMOD, TIRDWR) network option, if you want to install PATHWORKS NetBIOS for TCP/IP ______ Check for sufficient swap space. Amount of swap space ______ Check the number of open files available on the Digital UNIX system. Number of open files ______ Configure TCP/IP, if required. Install and configure DECnet/OSI Version 4.0, or DECnet for Small Configurations Version 4.0, if required. Install and configure TruClusters Version 1.4, if required. Back up the server system. Checking Digital UNIX Subsets and Layered Products Follow these steps to check software subsets: 1.Log into the Digital UNIX system. login: username Password: 2.Enter the /usr/sbin/setld -i | grep installed | more command to display the software subsets installed on the Digital UNIX system. For more information about the /usr/sbin/setld command, see setld(8), in the Digital UNIX Reference Pages. To display the Local Printer Support Subset, enter /usr/sbin/setld -i| grep OSFPRINT. The system displays information similar to the following: # /usr/sbin/setld -i | grep OSFPRINT OSFPRINT400 installed Local Printer Support (Printing Environment) To display the UNIX SVID2 Compatibility subset, enter /usr/sbin/setld -i | grep OSFSVI. The system display is similar to the following: # /usr/sbin/setld -i | grep OSFSVI OSFSVID2400 installed UNIX(tm) SVID2 Compatibility (General Applications) To display the DECnet/OSI subset, enter /usr/sbin/setld -i | grep DNABASE. The system display is similar to the following: # /usr/sbin/setld -i | grep -e DNABASE -e DNALITE DNABASE installed DECnet/OSI Base Components (DECnet/OSI Standard Run-time Environment) Checking Digital UNIX Kernel Components Follow these steps to verify Digital UNIX kernel components: 1.Check the /usr/sys/conf directory for the file that has the same name as your system. This file name is uppercase. For example, the kernel configuration file for a system named sparrow would be SPARROW. To display the file, enter the following: # more /usr/sys/conf/SPARROW ident sparrow . . options DLB options DLPI options TIRDWR options TIMOD options XTISO options FFM_FS options CDFS 2.Use the Digital UNIX doconfig command to add the kernel components that you need to the system configuration file. 3.To activate your changes, copy the new kernel file to the root directory, and reboot your system. Checking Digital UNIX Swap Space The Digital UNIX system must have sufficient swap space for PATHWORKS for Digital UNIX operations to complete. Whenever the Digital UNIX swap space is low, the system displays the message "Swap space below 10 percent free." If swap space is insufficient, the system displays the message "Not enough core" usually after an application failure. If you have configured more than 250 NetWare clients, you may require more than 256 MB of swap space. The maximum number of clients is 1000 which may require more than 580MB of swap space. You can estimate the amount of swap space you need for a particular number of clients by using the following formula which makes use of the keyword values max_proc and max_connections in the NW Config file: 30MB + 12MB *(max_procs) + 0.25*(max_connections) If you suspect that swap space is low, you can use the Digital UNIX swapon -s command to display the swap space available on your system. For example: # swapon -s Swap partition /dev/rz3b (default swap): Allocated space: 16384 pages (128MB) In-use space: 3838 pages ( 23%) Free space: 12546 pages ( 76%) . . You can also use this command to add swap space, if necessary. If additional partitions are available, you can add swap space without rebooting the system. For additional information, see the Digital UNIX Guide to System Tuning and Performance Management for additional information. Checking the Number of Open Files The Digital UNIX system must allow enough open files for PATHWORKS for Digital UNIX to operate. The messages "file table overflow", "out of vnodes", and "file table full," following a PATHWORKS for Digital UNIX failure, can indicate the number of open files has exceeded the Digital UNIX limitation. Digital UNIX sets the number of open files based upon the value of the maxusers parameter in the kernel configuration file. To increase the number of open files, you must increase the value of this parameter. Refer to the Digital UNIX Guide to System Administration for additional information. Configuring TCP/IP You can install the TCP/IP transport during installation of your Digital UNIX Operating System. You must configure TCP/IP on your server if you plan to install PATHWORKS Advanced Server software with the NetBIOS for TCP/IP driver subset. You can configure TCP/IP by using the Common Desktop Environment (CDE) application, if your system has graphics capability. If not, use the netsetup utility. To configure TCP/IP using the netsetup utility: 1.Log into the root account on the Digital UNIX system. login: root Password: 2.Run the netsetup program and follow the prompts. When netsetup prompts you for the net mask parameter for the network, be sure to enter the same value that you plan to use for each client. To run netsetup, enter the following: # netsetup For information about the netsetup command, see netsetup(8) in the Digital UNIX Reference Pages. For information about installing network services and the CDE application, see the Digital UNIX Installation Guide. Installing DECnet/OSI DECnet/OSI for Digital UNIX Version 4.0, and DECnet for Small Configuration Version 4.0 (Lightweight DECnet Configuration environment) are separate products that include both DECnet Phase IV and DECnet/OSI functionality. You must install and configure DECnet Phase IV on your server if you plan to install the PATHWORKS Advanced Server with the NetBIOS for DECnet driver subset. For additional information, see the DECnet/OSI Installation Guide and the DECnet/OSI Introduction and Planning Guide. Backing Up the System To safeguard against the loss of valuable information, Digital recommends that you do a system backup before you install any layered products on the operating system. Use the Digital UNIX backup or dump command to perform a system backup. For information about the backup command, see the Digital UNIX Guide to Backup and Restore. For information about the dump command, see dump(8) in the Digital UNIX Reference Pages. Checking the Hardware Configuration Before you install PATHWORKS for Digital UNIX, ensure that the network, including cables, servers, and other hardware, is connected. For a list of supported hardware, see the Software Product Description (SPD) included in your kit. If you plan to install the PATHWORKS Remote Boot Service subset, refer to the PATHWORKS Remote Boot Guide for specific information about client hardware requirements. Upgrading the Operating System This version of PATHWORKS for Digital UNIX is supported on Digital UNIX Version 4.0 systems. If you are planning to install TruClusters™, you must install Digital UNIX Version 4.0a. If your server uses a previous operating system version, you must upgrade to Version 4.0 before you begin PATHWORKS installation. General Procedure If you have PATHWORKS files that you want to save, you must create a backup copy of the files you want before you upgrade the operating system.This version of Complete the following steps to save PATHWORKS files and upgrade your operating system: 1.Remove PATHWORKS. See Removing, in this guide. 2.Follow special instructions to create a backup copy your server and shared user files. See Creating a Backup Copy of Server Files, in this guide. 3.Manually remove any remaining PATHWORKS directories. See Creating a Backup Copy of Server Files, in this guide. 4.Install Digital UNIX. 5.Install PATHWORKS for Digital UNIX. See Chapter 2, Installing PATHWORKS for Digital UNIX, in this guide. 6.Restore the backup of your server and shared user files. See Chapter 2, Installing PATHWORKS for Digital UNIX, in this guide. 7.Configure the server. See Chapter 3, Configuring PATHWORKS for Digital UNIX, in this guide. Caution You must remove any previous PATHWORKS product and save any files that you want before you upgrade to Digital UNIX Version 4.0. This is because the Digital UNIX upgrade procedures may delete or corrupt the PATHWORKS data and configuration files that you need to save. Removing the Previous PATHWORKS Product You must remove all subsets in the previous version of PATHWORKS before you can install the latest software. This is necessary to ensure that the latest version of PATHWORKS for Digital UNIX installs and configures properly. During removal, PATHWORKS prompts you for the account, user, and configuration information that you can save, saves the information you request, and then removes the subsets you specify. You must create a backup of the information you want after the subsets are removed so that you can restore it when you complete server installation. Before you remove PATHWORKS from your server, broadcast a message to all client workstations. In the message, tell users how much time they have to finish their tasks before the file server is removed and how long the server will be unavailable. For information about broadcasting messages, see the PATHWORKS for Digital UNIX (Advanced Server) System Guide. To remove PATHWORKS software, follow these steps: 1.Make sure that you are logged into the root account, then enter /usr/sbin/setld -i to display the PATHWORKS for DEC OSF/1 subsets to be deleted. For example: # /usr/sbin/setld -i |grep PWK | grep installed PWKBASE510 installed PATHWORKS for DEC OSF/1 AXP - LAN Manager Services (PATHWORKS for DEC OSF/1 AXP(LAN Manager)) PWKCONFIG510 installed PATHWORKS for DEC OSF/1 AXP - PATHWORKS Configuration (PATHWORKS for DEC OSF/1 AXP (Common)) PWKLIC510 installed PATHWORKS for DEC OSF/1 AXP-- License Server (PATHWORKS for DEC OSF/1 AXP (Common)) PWKDNA3510 installed PATHWORKS for DEC OSF/1 AXP--DECnet Driver (PATHWORKS for DEC OSF/1 AXP (LAN Manager)) PWKNBU3510 installed PATHWORKS for DEC OSF/1 AXP - NetBEUI Driver (PATHWORKS for DEC OSF/1 AXP (LAN Manager)) PWKNW3SVOL510 installed PATHWORKS for DEC OSF/1 AXP - NetWare System Volume (PATHWORKS for DEC OSF/1 AXP (NetWare)) PWKNWBASE510 installed PATHWORKS for DEC OSF/1 AXP - NetWare Services (PATHWORKS for DEC OSF/1 AXP (NetWare)) PWKNWTRAN3510 installed PATHWORKS for DEC OSF/1 AXP - NetWare Transports (PATHWORKS for DEC OSF/1 AXP (NetWare)) PWKRNOTE510 installed PATHWORKS for DEC OSF/1 AXP - Release Notes (PATHWORKS for DEC OSF/1 AXP (Common)) PWKRPL510 installed PATHWORKS for DEC OSF/1 AXP - Remote Boot Service (PATHWORKS for DEC OSF/1 AXP (LAN Manager)) PWKTCP3510 installed PATHWORKS for DEC OSF/1 AXP - TCP/IP Driver (PATHWORKS for DEC OSF/1 AXP (LAN Manager)) 2.Enter /usr/sbin/setld -d followed by all the PATHWORKS for DEC OSF/1 subsets that you want to delete. For example: # /usr/sbin/setld -d PWKBASE510 PWKCONFIG510 PWKLIC510 PWKNBU3510 PWKNW3SVOL510 PWKNWBASE510 PWKNWTRAN3510 PWKRNOTE510 PWKRPL510 PWKDNA3510 PWKTCP3515 3.The system stops the server and displays a series of prompts about items that you can save. The prompts that are displayed depend on the software subsets that you installed. Answer y after each prompt if you want to save the files associated with that item. Caution If you enter n, any files associated with the item will be lost. If you installed PATHWORKS NetWare software, the system prompts you for these items: - NetWare user accounts. This is the user account information, home directories, printer information and user mail files that are stored in the system volume. - NetWare user application and templates files stored in the system volume public area. This area typically consists of PATHWORKS NetWare utilities and programs. - NetWare server audit and error logs. These files contain records of server errors and network events. - The NetWare Configuration files. These files contain the configuration information you created when you installed PATHWORKS NetWare, as well as any information about volume assignments and printer configuration. The removal procedure saves the files you requested, and displays an informational message about any additional volumes that are automatically preserved. For example: The following public volumes are referenced by the NWConfig file: /usr/netware/vol1 /usr/netware/vol2 These volumes will not be removed by this deinstallation procedure. PATHWORKS for DEC OSF/1 AXP files and directories will now be removed. Directories in the System Volume that contain data you requested to save will not be removed. Other directories containing user data will be preserved, and must be manually backed-up and removed. Removing softlinks for PWKNWBASE510...done. Deleting "PATHWORKS for DEC OSF/1 AXP- NetWare Server" (PWKNWBASE510) Removing /usr/opt/PWKNWBASE510 . . . 4.When removal of PATHWORKS NetWare is complete, the system checks for PATHWORKS LAN Manager subsets. If you installed PATHWORKS LAN Manager, the system prompts you for the following: - Remote Boot Configuration Files. These are the files used by the Remote Boot service. Saved files include DOS executables, workstation and profile information, remote boot configuration files and server "update" files, created on the client. Saving Remote Boot files may require some additional steps, depending upon how your server is configured and the PATHWORKS for DEC OSF/1 version you are removing. Refer to Remote Boot service, later in this guide, for additional information. - User files stored in public share areas (such as dos, lib, pccommon, os2, and printlog) that are not created during the server installation procedure. - Customized print processor scripts you created. - Shared printer information (server, client, or both). This refers to a record of the printers that are available to network users by means of the server. These printers can be attached either to the server or to specific clients. If you save shared printer information, the removal procedure may prompt you to restart the LP spooler subsystem. If you do not save shared printer information, the removal procedure displays a list of the client (but not the server) printers that are removed. - Share file. This is a list of the file and printer shares that are available to network users by means of the server. The removal procedure only prompts you to save or remove the share file if you did not save shared printer information previously. If you did save shared printer information, then the share file is saved automatically. - Users added by means of the server. These are DEC OSF/1 user accounts created for users who needed access to a PATHWORKS for DEC OSF/1 server with user- level security. - Configuration file. This is the lanman.ini file, used to configure the PATHWORKS LAN Manager server software. Parameters in this file include the maximum file size, maximum number of connections, number of permissions and logon violations that trigger an alert message, and so on. - Important user account information. The default location is /usr/net/servers/lanman/users. These files contain information about LAN Manager users and their accounts. 5.When removal of PATHWORKS LAN Manager is complete, the system checks for subsets used by both PATHWORKS LAN Manager and PATHWORKS NetWare. The system prompts you to save the following: - The pathworks.ini file. This file contains parameters that define interoperability between PATHWORKS LAN Manager and PATHWORKS NetWare software, and also contains parameters for the License Server. - License Registrar Log file. This file contains log and error information for the license registrar. If you installed License Server software, the system prompts you for the following items: - License Server Data File. This file contains a list of licenses used by clients, information about client license PAKs, and information about licensing groups. - License Server and Group Logs. These files contain log and error information for the License Server. The system saves the files you requested, removes PATHWORKS for DEC OSF/1 subsets, and returns you to the root prompt. Creating a Backup Copy of Server Files To save the files you need, you must first follow the removal procedure in Removing in this guide. This enables you to remove PATHWORKS LAN Manager subsets and save the files you want. In addition, you must: Create a backup copy, on disk or tape, of all the server and user data files you choose to save during the removal procedure. Manually remove any remaining PATHWORKS directories. Create a backup copy, on a separate tape or directory location, of the DEC OSF/1 files that you will need. These are the /etc/printcap, /etc/group and /etc/passwd files. These files contain information about printer configuration and system users. However, you must be careful not to add or modify users or printers until after you have installed the new version of Digital UNIX and restored these files. To create a backup of PATHWORKS and DEC OSF/1 files after you remove PATHWORKS for DEC OSF/1: 1.Make sure you are logged into the root account. 2.Create a backup copy of the server files you saved during PATHWORKS for DEC OSF/1 removal. For example, to create a backup copy on tape of the files in /usr/net/servers, insert a blank tape into the appropriate drive. Enter the following, using the name of your tape drive for the device_name: # cd /usr/net/servers # tar cvf /dev/device_name . 3.Create a backup copy of the DEC OSF/1 files that you need. Copy these files to a separate tape, or to a location not on the system disk of the DEC OSF/1 server you are upgrading. For example, to copy the files to a non-system disk, enter the following, using the name of a directory location not on your system disk for the directory_location. # cp -p /etc/printcap directory_location # cp -p /etc/group directory_location # cp -p /etc/passwd directory_location 4.Manually remove the /var/net and /usr/net directories. - Change to the /var/net directory. Enter rm -rf * - Change to the /usr/net directory. Enter rm -rf * Copy the DEC OSF/1 files back to the server after you complete the Digital UNIX upgrade. For example: # cp -p directory_location/group /etc # cp -p directory_location/passwd /etc # cp -p directory_location/printcap /etc Copy the PATHWORKS files back to the server after you complete the installation of PATHWORKS for Digital UNIX subsets. For more information, see Chapter 2, Installing PATHWORKS for Digital UNIX, in this guide. Next Steps Digital recommends that you install PATHWORKS for Digital UNIX software in the following order: 1.Install the Release Notes from the installation media. Release Notes may contain information that impacts the installation procedure. If you are ready to install Release Notes, refer to Chapter 2, Installing PATHWORKS for Digital UNIX, in this guide. 2.Install PATHWORKS for Digital UNIX subsets. - Select the subsets you need and then use the /usr/sbin/setld utility to install them from the installation media. - Load the backup copy of the server files, if required by your installation. If you are ready to install subsets, see Chapter 2, Installing PATHWORKS for Digital UNIX, in this guide. 2 Installing PATHWORKS for Digital UNIX During installation, PATHWORKS for Digital UNIX copies the subsets you select onto your server. Read this chapter after you complete the installation prerequisites in Chapter 1, Preparing to Install PATHWORKS for Digital UNIX, when you are ready to install software. This chapter contains information about how to: Select the subsets you need Use the cdmenu and the setld utility to install software Install the Release Notes subset Install PATHWORKS Advanced Server and PATHWORKS NetWare subsets Installation Subsets PATHWORKS for Digital UNIX includes the following: Common subsets PATHWORKS Advanced Server subsets PATHWORKS NetWare subsets Common Subsets Table 2-1, Common Subsets, describes subsets that are used for both PATHWORKS Advanced Server and PATHWORKS NetWare software. You must install the PATHWORKS Configuration subset (PWKCONFIG610) to complete the PATHWORKS for Digital UNIX installation. You must also install the License Server subset, along with the appropriate transport subsets, on at least one server in the network if your configuration includes PATHWORKS Advanced Server or PATHWORKS NetWare clients and you want to use client licenses. The PATHWORKS Man Page subset (PWKMAN610) is installed in /usr/share/man. To install PATHWORKS Man Pages, you must be able to write to the /usr/share/man directory on the host system. Table 2-1: Common Subsets Subset Description Name PATHWORKS Provides PWKRNOTE610 Release Notes information about PATHWORKS for Digital UNIX that may impact the installation or operation of PATHWORKS software. PATHWORKS Provides license PWKLIC610 License Server management functions and utilities. PATHWORKS Man Provides manual PWKMAN610 Pages pages for PATHWORKS for Digital UNIX. PATHWORKS Provides files PWKCONFIG610 Configuration and utilities required to configure the PATHWORKS Advanced Server and PATHWORKS NetWare services. PATHWORKS Advanced Server Subsets Table 2-2, PATHWORKS Advanced Server Subsets, describes the subsets you can install. To complete PATHWORKS Advanced Server installation, you must install the subset for at least one driver, as well as the PATHWORKS Advanced Server services subset. Table 2-2: PATHWORKS Advanced Server Subsets Subset Description Name PATHWORKS Provides PWKTCP4610 NetBIOS for PATHWORKS TCP/IP Driver Advanced Server support over a TCP/IP transport. PATHWORKS Provides PWKDNA4610 NetBIOS for PATHWORKS DECnet Driver Advanced Server support over a DECnet transport. PATHWORKS Provides PWKNBU4610 NetBEUI Driver PATHWORKS Advanced Server support over NetBEUI. Includes the NetBEUI transport. PATHWORKS Provides PWKBASE610 Advanced Server PATHWORKS Advanced Server Services functions. Includes the PCSA Mailsoftware. PATHWORKS for Provides remote PWKRPL610 Digital UNIX boot services Remote Boot to DOS and OS/2 service workstations. You must also install the PATHWORKS NetBEUI driver subset if you plan to install and configure the Remote Boot service. PATHWORKS NetWare Subsets Table 2-3, PATHWORKS NetWare Subsets, describes the subsets you can install. You must install the NetWare Transport subset (PWKNWTRAN4610) and the NetWare Services subset (PWKNWBASE610) to complete PATHWORKS NetWare installation. Table 2-3: PATHWORKS NetWare Subsets Subset Description Name NetWare System Contains the PWKNW3SVOL610 Volume client applications (such as on- line help, SYSCON and NDIR) that reside in SYS:PUBLIC. This subset is optional. If your clients can map to SYS:PUBLIC on another NetWare server, you can save disk space by using the other server to execute client functions. However, your clients can map to SYS:PUBLIC only on the server you are installing, you should include this subset. NetWare Provides PWKNWBASE610 Services PATHWORKS NetWare server functions. NetWare Provides PWKNWTRAN4610 Transports PATHWORKS NetWare support over the IXP/SPX transport. Using the cdmenu and setld Utilities The cdmenu utility is a program on the Layered Product Disk that provides a menu that you can use to begin installing PATHWORKS Advanced Server and PATHWORKS NetWare software. During installation, cdmenu calls the /usr/sbin/setld utility. The /usr/sbin/setld utility sets up the PATHWORKS environment, extracts files, and provides the prompts and questions you answer when installing or removing software. You will use both cdmenu and setld to install PATHWORKS Advanced Server and PATHWORKS NetWare software. Installing Release Notes Digital recommends that you read the Release Notes before you begin installation. Release Notes may contain important information that is not in the published documentation, and which may affect your installation procedure. To install Release Notes: 1.Check to see that you are in multi-user mode, then log into the root account on the Digital UNIX system. 2.Insert the Layered Products Compact Disk into the drive. 3. Mount the Layered Products Compact Disk, in read- only mode, to an existing directory. # mount -r /dev/device_name /directory_name 4. Change to the mounted directory and display the directory's contents. # cd /directory_name # ls The system displays the directories available on the disk. 5. Define the environmental variable CD_DIRECTORY to point at the mounted directory. If you use the C shell: setenv CD_DIRECTORY directory_name If you use the Bourne or Korn shell: CD_DIRECTORY=directory_name export CD_DIRECTORY 6. Change to the cdrom directory. # cd /directory_name 7. Run the cdmenu utility to begin installation. # ./cdmenu The system displays the CD Menu banner, followed by trademark information. 8. Press Return to continue. The system displays the Main Menu. 9. Select 6 - Install Product 10. The system displays a listing of product names and index numbers, and prompts you for the index number of the product you want to install. Enter the index number for either PATHWORKS for Digital UNIX (Advanced Server) or PATHWORKS for Digital UNIX (NetWare). 11. At the prompt, enter y to continue with the installation. Continue with the installation? (y/n)? y 12. The system displays PATHWORKS for Digital UNIX subsets, and asks which subsets you want to install. Executing the following command: /usr/sbin/setld -l /cdrom/PWK610/kit The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. - PATHWORKS for Digital UNIX (Advanced Server): 1) PATHWORKS for Digital UNIX -- Advanced Server 2) PATHWORKS for Digital UNIX -- DECnet Driver 3) PATHWORKS for Digital UNIX -- NetBEUI Driver 4) PATHWORKS for Digital UNIX -- Remote Boot Service 5) PATHWORKS for Digital UNIX -- TCP/IP Driver - PATHWORKS for Digital UNIX (Common): 6) PATHWORKS for Digital UNIX -- License Server 7) PATHWORKS for Digital UNIX -- PATHWORKS Configuration 8) PATHWORKS for Digital UNIX -- PATHWORKS Man Pages 9) PATHWORKS for Digital UNIX -- Release Notes - PATHWORKS for Digital UNIX (NetWare): 10) PATHWORKS for Digital UNIX -- NetWare Services 11) PATHWORKS for Digital UNIX -- NetWare System Volume 12) PATHWORKS for Digital UNIX -- NetWare Transports Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): Or you may choose one of the following options: 13) ALL of the above 14) CANCEL selections and redisplay menus 15) EXIT without installing any subsets Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6):9 13. Enter the number for the Release Note subset. The system displays your choice and requests confirmation: You are installing the following optional subsets: - PATHWORKS for Digital UNIX (Common): - PATHWORKS for Digital UNIX -- Release Notes Is this correct? (y/n) y 14. Enter y to confirm your choice. The system copies the Release Note subset and displays informational messages. For example: Checking file system space required to install selected subsets: File system space checked OK. 1 subset(s) will be installed. Loading 1 of 1 subset(s) (c) Digital Equipment Corporation. 1995-1996. All Rights Reserved. PATHWORKS for Digital UNIX -- Release Notes Copying from (disk) Verifying 1 of 1 subset(s) installed successfully. Creating softlinks for PWKRNOTE610 ...done Changing permissions, groups and ownership of installed files. Configuring PATHWORKS for Digital UNIX - Release Notes (PWKRNOTE600) # PATHWORKS for Digital UNIX installs the Release Notes file in /usr/net/servers/pathworks/relnotes. The rel_notes.ps file is the PostScript version. The rel_notes.txt file is the ASCII text version, which is provided for on-line viewing. Installing PATHWORKS for Digital UNIX Subsets To install PATHWORKS for Digital UNIX subsets: 1.Check to see that you are in multi-user mode, then log into the root account on the Digital UNIX system. 2.Insert the Layered Products Compact Disk into the drive. 3.Mount the Layered Products Compact Disk, in read-only mode, to an existing directory. # mount -r /dev/device_name /directory_name 4.Change to the mounted directory and display the directories available on the disk. # cd /directory_name # ls 5.Define the environmental variable CD_DIRECTORY to point to the mounted directory. 6.Change to the cdrom directory. # cd cd /directory_name 7.Run the cdmenu utility to begin installation. # ./cdmenu The system displays the CD Menu banner, followed by trademark information. 8.Press return to continue. The system displays the Main Menu. 9.Select 6 - Install Product 10. The system displays a listing of product names and index numbers and prompts you for the index number of the product you want to install. Enter the index number for either PATHWORKS for Digital UNIX (Advanced Server) or PATHWORKS for Digital UNIX (NetWare). 11. At the prompt, enter y to continue with the installation. Continue with the installation? (y/n)? y 12. The system displays PATHWORKS for Digital UNIX subsets, and asks which subsets you want to install. Executing the following command: /usr/sbin/setld -l /cdrom/PWK610/kit The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. - PATHWORKS for Digital UNIX (Advanced Server): 1) PATHWORKS for Digital UNIX -- Advanced Server 2) PATHWORKS for Digital UNIX -- DECnet Driver 3) PATHWORKS for Digital UNIX -- NetBEUI Driver 4) PATHWORKS for Digital UNIX -- Remote Boot Service 5) PATHWORKS for Digital UNIX -- TCP/IP Driver - PATHWORKS for Digital UNIX (Common): 6) PATHWORKS for Digital UNIX -- License Server 7) PATHWORKS for Digital UNIX -- PATHWORKS Configuration 8) PATHWORKS for Digital UNIX -- PATHWORKS Man Pages 9) PATHWORKS for Digital UNIX -- Release Notes - PATHWORKS for Digital UNIX (NetWare): 10) PATHWORKS for Digital UNIX -- NetWare Services 11) PATHWORKS for Digital UNIX -- NetWare System Volume 12) PATHWORKS for Digital UNIX -- NetWare Transports Or you may choose one of the following options: 13) ALL of the above 14) CANCEL selections and redisplay menus 15) EXIT without installing any subsets Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6):13 13. You can install individual subsets by entering the number of the subset. To install more than one subset, enter each subset number separated by a space. To install all software, release notes, and manpages, enter the number for "ALL of the above". The system displays your choices and requests confirmation. For example: You are installing the following optional subsets: - PATHWORKS for digital UNIX (Advanced Server): PATHWORKS for Digital UNIX -- Advanced Server PATHWORKS for Digital UNIX -- DECnet Driver PATHWORKS for Digital UNIX -- NetBEUI Driver PATHWORKS for Digital UNIX -- Remote Boot Service PATHWORKS for Digital UNIX -- TCP/IP Driver - PATHWORKS for Digital UNIX (Common): PATHWORKS for Digital UNIX -- License Server PATHWORKS for Digital UNIX -- PATHWORKS Configuration PATHWORKS for Digital UNIX -- PATHWORKS Man Pages PATHWORKS for Digital UNIX -- Release Notes - PATHWORKS for Digital UNIX (NetWare): PATHWORKS for Digital UNIX -- NetWare Services PATHWORKS for Digital UNIX -- NetWare System Volume PATHWORKS for Digital UNIX -- NetWare Transports Is this correct? (y/n) y 14. Enter y to confirm your choices. The system copies each requested subset and displays an informational message, similar to the following: Checking file system space required to install selected subsets: File system space checked OK. 12 subset(s) will be installed. Loading 1 of 12 subsets. (c) Digital Equipment Corporation. 1995-1996 All Rights Reserved. PATHWORKS for Digital UNIX -- PATHWORKS Configuration Copying from (disk) Verifying Loading 2 of 12 subsets... (c) Digital Equipment Corporation. 1995-1996 All Rights Reserved. PATHWORKS for Digital UNIX -- Release Notes Copying from (disk) Verifying Loading 3 of 12 subsets... (c) Digital Equipment Corporation. 1995-1996. All Rights Reserved. PATHWORKS for Digital UNIX -- PATHWORKS Man Pages Copying from (disk) Verifying Loading 4 of 12 subsets... (c) Digital Equipment Corporation. 1995-1996. All Rights Reserved. PATHWORKS for Digital UNIX -- TCP/IP Driver Copying from (disk) Verifying Loading 5 of 12 subsets... (c) Digital Equipment Corporation. 1995-1996 All Rights Reserved. PATHWORKS for Digital UNIX -- NetBEUI Driver Copying from (disk) Verifying Loading 6 of 12 subsets... (c) Digital Equipment Corporation. 1995-1996. All Rights Reserved. PATHWORKS for Digital UNIX -- DECnet Driver Copying from (disk) Verifying Loading 7 of 12 subsets... (c) Digital Equipment Corporation. 1995-1996 All Rights Reserved. PATHWORKS for Digital UNIX -- NetWare Transports Copying from (disk) Verifying Loading 8 of 12 subsets... (c) Digital Equipment Corporation. 1995-1996. All Rights Reserved. PATHWORKS for Digital UNIX -- License Server Copying from (disk) Verifying Loading 9 of 12 subsets... (c) Digital Equipment Corporation. 1995-1996 All Rights Reserved. PATHWORKS for Digital UNIX -- Advanced Server Copying from (disk) Working....Wed Jul 24 13:29:27 EDT 1996 Verifying Working Wed Jul 24 13:31:02 EDT 1996 Loading 10 of 12 subsets... (c) Digital Equipment Corporation. 1995-1996 All Rights Reserved. PATHWORKS for Digital UNIX -- Remote Boot Service Copying from (disk) Loading 11 of 12 subsets... (c) Digital Equipment Corporation. 1995-1996 All Rights Reserved. PATHWORKS for Digital UNIX -- NetWare Services Copying from (disk) Working....Wed Jul 24 13:31:44 EDT 1996 Verifying Loading 12 of 12 subsets.. (c) Digital Equipment Corporation. 1995-1996 All Rights Reserved. PATHWORKS for Digital UNIX -- NetWare System Volume Copying from (disk) Working....Wed Jul 24 13:32:05 EDT 1996 Verifying 12 of 12 subset(s) installed successfully.. Creating softlinks for PWKCONFIG610...done Changing permissions, groups and ownership of installed files. Configuring "PATHWORKS for Digital UNIX - PATHWORKS Configuration" (PWKCONFIG610) . . . If you installed the PATHWORKS Advanced Server services subset, the system prompts you for the location for the Advanced Server shares. You may choose the directory location for the Advanced Server Shares, or accept the default location (/usr/net/servers/lanman/shares). Use default location /usr/net/servers/lanman/shares [y/n]? y 15. Enter y to accept the default location, or enter n and follow system prompts to specify a new one. The system displays informational messages and continues installation. If you installed the PATHWORKS NetWare services subset, the system prompts you for the directory location of the NetWare system volume. You may choose the directory location for the NetWare System Volume, or accept the default location (/usr/net/servers/netware/vol/sys). Use default location /usr/net/servers/netware/vol/sys [y/n]? y 16. Enter y to accept the default location, or enter n and follow system prompts to specify a new one. The system continues installation. When installation is complete, the system returns you to the root prompt. Note During installation, PATHWORKS for Digital UNIX automatically modifies the /etc/passwd and /etc/group files. Certain products, such as DECtrade System Manager V3.5, protect these files from modification. If your server includes such a product, the PATHWORKS for Digital UNIX installation fails, and displays a message similar to the following: ERROR: Failed to add login to /etc/passwd: lanman setld: "PATHWORKS for Digital UNIX- Main Server (PWKBASE610) failed in su If this occurs, you must remove PATHWORKS for Digital UNIX subsets, disable protections for /etc/group and for /etc/passwd, and reinstall PATHWORKS for Digital UNIX. You can begin configuration after installation completes. To configure your system, you must: 1.Execute /usr/sbin/pwsetup kernel. 2.Reboot the system if indicated. 3.Execute /usr/sbin/pwsetup configure. 4.For additional information, see Chapter 3, Configuring PATHWORKS for Digital UNIX, in this guide. Installing PATHWORKS Icons The PATHWORKS installation procedure automatically installs desktop icons that you can use to invoke pwadmin, pwlsadmin, and sconsole. If your system is not configured properly, PATHWORKS displays a message similar to the following: ***************************Please Note**************************** * PWKBASE610 has been installed, however setld is unable to load * * the pwadmin icon onto your desktop. Please ensure that your * * DISPLAY variable is set correctly, and that you can write to * * your own desktop. Then, as root, run the following command: * * /usr/dt/bin/dtaction ReloadActions * ****************************************************************** To configure you system, set the DISPLAY environmental variable to :0.0. Then, make sure your system can communicate with the X-server, and reload the icons. To set the DISPLAY environmental variable, enter the Digital UNIX commands for the shell that you use. To connect to the X-server: 1. From the desktop, click the Application Manager icon. 2. From the Application Manager display, click the System_Admin icon. 3. From the System_Admin display, click the System_Management_Utilities icon. 4. From the System_Management_Utilities display, click the DailyAdmin icon. 5. From the DailyAdmin display: a) Select the Host Manager icon. b) From the Menu bar, select Options, then select Add All Hosts to X Access List. c) From the Menu bar, select Host/Mgr, and then select Save. 6.Follow standard commands and procedures to exit the desktop utility. To reload the icons: 1. Enter /usr/dt/bin/dtaction ReloadActions Restoring Backup Server Files If you created a backup copy of the server files, you must now load the backup onto the server. For example, if the backup is saved to tape, insert the tape into the appropriate drive. Enter the following, using the name of your device in place of device_name. # cd /usr/net/servers # tar xvf /dev/device_name Next Steps After you complete the installation, you must complete the following steps. These are described in Chapter 3, Configuring PATHWORKS for Digital UNIX, in this guide. 1.Run /usr/sbin/pwsetup kernel to specify network parameters: If you installed PATHWORKS Advanced Server software, use /usr/sbin/pwsetup kernel to configure your network adapter. - The PATHWORKS NetBIOS for DECnet subset supports only one network controller. If your server includes more than one controller, you must choose the one you want and use pwsetup kernel to configure it. For additional information, see Configuring Network Controllers, in this guide. - The PATHWORKS NetBIOS for TCP/IP subset provides support for multiple network controllers. You must use pwsetup kernel to specify which controllers you want to use. You can also use pwsetup kernel to configure WAN support. - The PATHWORKS NetBEUI subset provides support for Ethernet, FDDI, and Token Ring network hardware. However, if your system includes more than one controller for the same network hardware (for example, two FDDI controllers) you must use pwsetup kernel to configure all the controllers that you want. If you installed PATHWORKS NetWare software, use pwsetup kernel to specify the internal address, network address and frame type that you want. 2.Run shutdown -r with chosen time to reboot your system if indicated. 3.Run /usr/sbin/pwsetup configure to configure PATHWORKS for Digital UNIX. 4.Install and configure Windows NT server tools, and Windows NT administrative tools, if you want to manage your PATHWORKS Advanced Server software from either a Windows or Windows NT client. 5.Set up browsing on a Windows NT server, Windows NT Workstation, or Windows for Workgroups system in the PATHWORKS Advanced Server domain. 3 Configuring PATHWORKS for Digital UNIX This chapter describes how to use pwsetup kernel utility to configure PATHWORKS for Digital UNIX controllers and configure WAN support. This chapter also describes how to use the pwsetup configure utility to configure server software, and to verify that the software runs correctly. Specifically, this chapter describes how to: Specify PATHWORKS Advanced Server controller information Configure WAN support Specify PATHWORKS NetWare controller information Reboot the system if indicated Configure and validate a PATHWORKS Advanced Server system Maintain a PATHWORKS for DEC OSF/1 server in a PATHWORKS Advanced Server domain Install Windows NT server tools Set up browsing on a Windows NT server, Windows NT Workstation, or Windows for Workgroups system in the PATHWORKS Advanced Server domain Configure and validate a PATHWORKS NetWare system Configure the license server software Configure PATHWORKS as a Service in a Digital UNIX TruCluster Environment Configuring Network Controllers The pwsetup kernel utility provides you with a way to: Supply PATHWORKS Advanced Server controller information Configure WAN support Supply PATHWORKS NetWare controller information Modify controller information, after you install and configure PATHWORKS for Digital UNIX. Samples of how the pwsetup kernel utility runs are given in the following sections. Supplying PATHWORKS Advanced Server Controller Information If you install PATHWORKS Advanced Server software on a server with more than one controller, you can use pwsetup kernel to select the controllers that you want. The pwsetup kernel utility checks all the controllers installed on your server, and prompts you for configuration information. The number of controllers you can select depends on the transport that you use: If you installed the PATHWORKS NetBIOS for TCP/IP subset, your server can support multiple NetBIOS controllers over the TCP/IP transport. The pwsetup kernel utility automatically locates and displays all the NetBIOS controllers configured for TCP/IP. You must use pwsetup kernel to choose the ones you want. If you installed the PATHWORKS NetBIOS for DECnet subset, your server can support a single controller for NetBIOS over the DECnet transport. The pwsetup kernel utility automatically locates and configures this controller for you. However, if your server has more than one DECnet controller, you must choose the one you want and then select it by running pwsetup kernel. If you installed the PATHWORKS NetBEUI Drivers subset, your server can support up to eight controllers over Ethernet, FDDI, and Token Ring hardware. The pwsetup kernel utility automatically locates and configures these controllers for you. However, if your server includes more than one controller for the same hardware (for example, two FDDI adapters), you must use pwsetup kernel to specify every controller you want. Note You must configure your PATHWORKS controllers according to these guidelines for your server to run properly: You cannot use NetBEUI on networks where two interfaces are bridged together, causing the packets from one controller to loop to the other. If your system is configured this way, you must reconfigure it so that NetBEUI uses only one interface. Although PATHWORKS NetBIOS for TCP/IP supports multiple controllers, you can configure only one NetBIOS controller on each subnet. Refer to Chapter 4, Server Setup and Tuning, in this guide, for additional information about how to display, select, and configure network controllers. Configuring WAN Support PATHWORKS Advanced Server software provides WAN support for servers configured to use PATHWORKS over the TCP/IP transport. You can configure your PATHWORKS Advanced Server to provide WAN support by means of three different mechanisms in addition to the default NetBIOS B-Node function. The additional mechanisms are: Local LMHOSTS file to store name to IP address mappings. You need to create an lmhosts file on the local server, and then update the pathworks.ini file. Use pwsetup kernel to create the lmhosts file and update the pathworks.ini file to enable usage of an LMHOSTS file. Contacting a NetBIOS Name Server (NBNS) to resolve names. For example, Microsoft's WINS server, running on Windows NT server is a NetBIOS Name Server. Using the Internet Domain Naming Service (DNS). For additional information about configuring WAN support, see the PATHWORKS for Digital UNIX (Advanced Server) System Guide. Supplying PATHWORKS NetWare Controller Information If you install PATHWORKS NetWare, the pwsetup kernel utility locates the controllers installed on your server, and prompts you for an internal address, network address, and frame type for each controller. Refer to Chapter 1, Preparing to Install PATHWORKS for Digital UNIX, in this guide, if you need additional information about these values. Changing Controller Information You can use pwsetup kernel to change the controller information and WAN configuration you entered during PATHWORKS for Digital UNIX installation. Refer to Chapter 4, Server Setup and Tuning, in this guide, for additional information. Using pwsetup kernel The following shows how to use the pwsetup kernel utility to specify controller information. 1. Check to see that you are in multi-user mode, then log into the root account and enter: # /usr/sbin/pwsetup kernel The pwsetup kernel utility checks to see if you installed PATHWORKS Advanced Server subsets. If not, pwsetup kernel begins configuration of PATHWORKS NetWare. Go to step 10, in this section, to continue configuration. If you installed PATHWORKS Advanced Server software, the pwsetup kernel utility asks if you want to configure it: Do you wish to configure the kernel for Advanced Server Transports[y/n]? y 2.Answer y to begin configuration. The pwsetup kernel asks if you want to configure controllers. Configuring kernel for Advanced Server Transports.. Would you like to configure the controllers [y/n]? y 3.If you have only a single controller for each transport, and you do not configure WAN support, answer n. PATHWORKS automatically selects the controller you have, and checks to see if you need to begin NetWare configuration. Go to step 10, in this procedure, if you need to configure NetWare controllers. Answer y if you need to configure more than one controller on any transport or if you want to configure WAN support. If you answer y, the pwsetup kernel utility displays any available controllers for the transports you have configured. In this example, pwsetup kernel displays controllers for the TCP/IP transport. The default controller, ln0, is displayed in square brackets. ********************************************** PATHWORKS NetBIOS over TCP/IP Setup ********************************************** Select a controller for PATHWORKS NetBIOS over TCP/IP. The "pathworks.ini" file will be modified accordingly. ln0 @ address: 130.200.150.72 none Enter the controllers separated by a comma or type ? for help: [ln0] 4.You can select up to four controllers for the TCP/IP transport. To select the default controllers, press Return. To select new controllers, enter the new controller names, as well as the names of any default controllers that you want. Use a comma to separate each controller name. After you select the controllers you want, the pwsetup kernel utility prompts you for confirmation. You have selected the default controller ln0. Is this correct? [yes]? modifying the pathworks.ini file with ln0. 5. The pwsetup kernel utility displays the WAN support screen, asks if you want to enable WAN support. ***************************************************** PATHWORKS WAN Support ***************************************************** By turning on WAN support your server will be able to become part of domains that span IP subnets. To enable WAN support, you must select at least one of the following mechanisms: -.lmhosts file - Name Resolution via NetBIOS Name Service (NBNS) - e.g. WINS Client - Name Resolution via Domain Name Service (DNS) Do you want to use lmhosts file? [no]? y lmhosts filename:[/usr/net/servers/pathworks/datafiles/lmhosts] Do you want to edit the lmhosts file now [yes]? no Do you want to enable NBNS name resolution [no]? y Enter IP address (XXX.XXX.XXX.XXX) of NBNS server: [no default] 130.200.150.34 Do you want to enable DNS name resolution [no]? yes Enter list of DNS subdomains separated by commas: [no default] london.com,paris.com You've selected the following options for WAN support: Use lmhosts file /usr/net/servers/pathworks/datafiles/lmhosts Use NBNS server, address 130.200.150.34 Use DNS server, subdomains london.com,paris.com Are you satisfied with these choices [yes]? y Modifying the pathworks.ini file with WAN choices. 6.The pwsetup kernel utility searches for and displays the controllers for any additional transports. If none are located, pwsetup kernel checks for the required kernel components, and indicates whether or not it is necessary to relink the kernel. In this case, pwsetup kernel locates and displays controllers for the NetBEUI-Datalink transport. The default controller, ln0 is displayed in square brackets. ***************************************************** PATHWORKS NetBEUI-Datalink Controller Selection ***************************************************** Select the controllers for the PATHWORKS NetBEUI transport. ln0 none Enter the controllers separated by a comma or type ? for help: [ln0] You can select up to eight controllers for the NetBEUI- Datalink transport. To select the default controllers, press Return. To select new controllers, enter the new controller names, as well as the names of any default controllers that you want. Use a comma to separate each controller name. After you select the controllers you want, the pwsetup kernel utility prompts you for confirmation. You have selected the defaultln0. Is this correct? [yes]? Modifying the "pathworks.ini" file with ln0 7.Enter Return to confirm your selection. The pwsetup kernel utility searches for and displays the controllers for any additional transports. pwsetup kernel displays controllers for the DECnet transport. The default controller, ln0, is displayed in square brackets. ********************************************** PATHWORKS NetBIOS over DECnet Setup ********************************************** Select a controller for PATHWORKS NetBIOS over DECnet. The "pathworks.ini" file will be modified accordingly. Select a controller or type ? for help [ln0] 8. You can select one controller for the DECnet transport. To select the default controller, press Return. To select a new controller, enter the controller name. After you select the controller you want, the pwsetup kernel utility prompts you for confirmation. You have selected ln0. Is this correct? [no]? y Answer y to confirm your selection. Modifying the "pathworks.ini" file with ln0 9. The pwsetup kernel utility searches for and displays the controllers for any additional transports. When all PATHWORKS Advanced Server controllers are configured, the pwsetup kernel utility checks for PATHWORKS NetWare subsets. If installed, the pwsetup kernel utility displays some informational messages, and then asks if you want to configure PATHWORKS NetWare controllers: Do you wish to configure the kernel for NetWare Services [y/n]? y 10.Answer y to begin configuration. If you are using PATHWORKS as a service in a Digital UNIX TruCluster environment, pwsetup kernel utility displays the following: This system appears to reside in a DECsafe/TruCluster environment. In such an environment, the name of the Netware Server must be unique, and the same for each server in the cluster. Enter the name of the Netware server or press enter to select `shark_nw': shark_nw The pwsetup kernel utility displays the controllers installed on the server and asks which ones you want to configure. The default selection, in this case ln0, is displayed in square brackets at the bottom of the screen. You can enter a new controller name, press enter to accept the default, or press ? to display help. Configuring kernel for NetWare Service Transports... Enter requested information at each prompt or [Return] to select the default (if present) or type ? for help. Configuring server SHARK_NW Select the controllers you wish to configure ln0 [82C89648] Enter the controller(s) separated by a comma [ln0,ln1,tra0]:ln0 11.Select the controllers you want, separated by a comma, or press Return to accept the default selections. The pwsetup kernel utility displays your selection and prompts you for confirmation. You have selected "ln0". Is this correct [yes]? 12.Press Return to confirm your selection. If you selected a controller that does not have TCP/IP configured, the pwsetup kernel utility displays the name of the controller with no address. You must enter the hexadecimal address that you want. If you selected one or more TCP/IP controllers, the pwsetup kernel utility uses the address of the first controller configured to create the internal address. You can press Return to accept the address, or enter a hexadecimal address of your own. For example, if a TCP/IP controller is selected: Internal Network [82C89648]: 13.Press Return to accept the address, or specify an address of your own. The pwsetup kernel displays the internal network number and prompts you for confirmation. Press Return to confirm your selection. Internal Network is 82C89648. Is this correct [yes]? 14.The pwsetup kernel utility displays the network address of the first controller. You can press Return to accept the address, or enter a hexadecimal address of your own. Configuring Network 1: ln0 Lan Network [82C89648]: 15.The pwsetup kernel utility displays available frame types for the controller. The number for the default, ETHERNET_II, is displayed in square brackets at the bottom of the screen. Enter the number for the frame type you want, or press Return to select the default. Select Frame Type 1. ETHERNET_802.2 2. ETHERNET_II 3. ETHERNET_SNAP 4. ETHERNET 802.3 FRAME TYPE [2]: 16.The pwsetup kernel utility displays network information and prompts you for confirmation. Press Return to confirm your selections. Lan Name: ln0 Frame type: ETHERNET_II Lan Network: 82C8F096 Lan 1 Network configuration. Is this correct [yes]? 17.The pwsetup kernel utility checks for the required kernel components, indicates whether or not it is necessary to relink the kernel, and then configures your selections into the PATHWORKS NetWare software. If you choose to configure additional controllers during step 10, the pwsetup kernel utility displays prompts for each controller's internal address, network address and frame type. Return to step 10, in this section, to continue configuration. Rebooting the System After you complete pwsetup kernel, if a reboot was indicated, you must reboot your system to activate your modifications. To reboot your system, use your system specific shutdown procedure. In cases where required kernel components were missing, a "pwsetup kernel" may be necessary after the reboot. Follow the displayed instructions to complete configuration of the system. Configuring the Server The pwsetup configure utility provides you with a way to configure PATHWORKS Advanced Server and PATHWORKS NetWare software. This utility provides an installation script and configuration activities based on the software you installed and the server data, if any, that you saved. Note The transports for the server being configured MUST be running before the corresponding server can be successfully configured and brought up. How the pwsetup configure Utility Works The following sections describe what pwsetup configure does when you use it to configure a PATHWORKS server. The actions that pwsetup configure takes depend on whether you are: Configuring a PATHWORKS Advanced Server software Configuring a PATHWORKS NetWare server software Configuring both PATHWORKS Advanced Server and PATHWORKS NetWare software Configuring PATHWORKS in a TruCluster Environment. (If you are configuring PATHWORKS as a service in a TruCluster environment, refer to the PATHWORKS for Digital UNIX TruCluster Family Administrator's Guide) Configuring PATHWORKS Advanced Server Systems If you upgrade PATHWORKS Advanced Server software using saved data from a previous version, the pwsetup configure utility: 1.Checks the previous configuration. If the previous configuration is a primary or backup server, pwsetup configure displays an abbreviated script, and updates server software using the same parameters as your previous configuration. If the previous configuration is a standalone or member server, pwsetup configure prompts you for the closest supported server type (primary or backup). 2.Asks if you want to run lmivp to validate the PATHWORKS Advanced Server configuration. 3.Asks if you want to configure license server software, if you have it installed on your system. If you install PATHWORKS Advanced Server software as a first-time installation, the pwsetup configure utility: 1.Prompts you for the server type, and for other server parameters. 2.Asks if you want to run lmivp to validate PATHWORKS Advanced Server configuration. 3.Asks if you want to configure license server software, if you have it installed on your system. Configuring PATHWORKS NetWare Systems If you upgrade PATHWORKS NetWare software using saved data from a previous version, the pwsetup configure utility: 1.Configures PATHWORKS NetWare using the same parameters as your previous configuration. 2.Asks if you want to run nwivp to validate PATHWORKS NetWare. 3.Asks if you want to configure license server software, if you have it installed on your system. If you install PATHWORKS NetWare software as a first-time installation, the pwsetup configure utility: 1.Configures PATHWORKS NetWare. 2.Asks if you want to run nwivp to validate PATHWORKS NetWare. 3.Asks if you want to configure license server software, if you have it installed on your system. Configuring PATHWORKS Advanced Server and PATHWORKS NetWare Systems If you upgrade PATHWORKS Advanced Server and PATHWORKS NetWare software using data from a previous version, the pwsetup configure utility: 1.Checks the previous configuration. If the previous configuration was a primary or backup server, pwsetup configure displays an abbreviated script and updates server software using the same parameters as your previous configuration. If the previous configuration is a standalone or member server, pwsetup configure prompts you for the closest supported server type (primary or backup). 2.Asks if you want to run lmivp to validate the PATHWORKS Advanced Server configuration. 3.Configures PATHWORKS NetWare, using the parameters and server data that you saved. 4.Asks if you want to run nwivp to validate the PATHWORKS NetWare configuration. 5.Asks if you want to configure license server software, if you have it installed on your system. If you install PATHWORKS Advanced Server and PATHWORKS NetWare software as a first-time installation, the pwsetup configure utility: 1.Prompts you for PATHWORKS Advanced Server type and other server parameters and then configures PATHWORKS Advanced Server software. 2.Asks if you want to run lmivp to validate the PATHWORKS Advanced Server configuration. 3.Configures PATHWORKS NetWare. 4.Asks if you want to run nwivp to validate the PATHWORKS NetWare configuration. 5.Asks if you want to configure license server software, if you have it installed on your system. Configuring PATHWORKS for DEC OSF/1 Upgrades The following sections describe how to configure PATHWORKS Advanced Server software if you are upgrading an existing installation. Upgrading a Standalone Server PATHWORKS for Digital UNIX does not support the standalone server type that was available in the previous version. If you have a standalone server, Digital recommends you follow installation prompts and reconfigure it as a primary domain controller. The configuration procedure automatically upgrades all data items and files that you saved from the previous configuration. Users from the PATHWORKS for DEC OSF/1 environment become accounts in the PATHWORKS Advanced Server domain. The lanman.ini file is configured to support the new Advanced Server domain. Keywords and parameters that are no longer supported are ignored or upgraded. The share list file is maintained and the access control lists are upgraded. The following shows how to use pwsetup configure to upgrade a PATHWORKS for DEC OSF/1 standalone server: 1.Check to see that you are in multi-user mode, then login to the root account and enter /usr/sbin/pwsetup configure. The system asks if you want to configure the PATHWORKS Advanced Server. DECsafe Available Server Environment detected. Configure PATHWORKS for Digital UNIX to run in the DECsafe Available Server environment [y/n]? n Do you wish to configure Advanced Server Services [y/n]? y 2.Answer y to begin configuration. PATHWORKS Advanced Server If you saved user account information from the previous configuration, the system displays upgrade information and a confirmation prompt. Go to step 3 to continue the installation. If you removed user account information from the previous configuration, the system prompts you for the account location. This is a directory on the server that contains the home directories of the PATHWORKS Advanced Server users. You can accept the default location, or you can enter the name of a directory where, for example, you know you have sufficient disk space. You may choose the directory location for your Advanced Server accounts, or accept the default location (/usr/net/servers/lanman/users). Use default directory /usr/net/servers/lanman/users [y/n]? y Creating default directory: /usr/net/servers/lanman/users 3.Enter y to accept the default location, or enter n and follow system prompts to specify your own directory name. The system displays information similar to the following: Upgrading saved LAN Manager information. Your LAN Manager role was standalone server in the domain. PATHWORKS for Digital UNIX Advanced Server has removed this role. The most appropriate mapping is to a primary domain controller. You can choose to have your standalone role automatically changed to primary and your old accounts upgraded to the new account format. Alternatively, you may wish to simply remove your old accounts and create a new primary or backup server, plus new account files. Do you want an automatic upgrade [y/n]y 4.Enter y to upgrade your server automatically. Caution If you enter n, the system removes the user account and configuration information used by your previous configuration and also overwrites server configuration files. You cannot restore the previous configuration unless you have a backup of these files. Refer to Chapter 1 for information about creating a backup of server files. 5.The system displays the following and then prompts you for the server name: PATHWORKS for Digital UNIX ADVANCED Server provides a NETLOGON service which simplifies the administration of multiple servers. A single user accounts database can be shared by multiple servers grouped together into an administrative collection called a domain. Within a domain, each server has a designated role. A single server, called the primary domain controller, manages all changes to the user accounts database and automatically distributes those changes to other servers, called backup domain controllers, within the same domain. You may now supply a server name (the name by which this server will be known on the network), the role that this server will perform in that domain (primary or backup), and the domain name. Enter the name of the server or press Enter to select 'servername':shark 6.Enter the server name or press Enter to accept the default name. The system displays the following and prompts you for the type of server you want to install: Each server must be given a role in the domain. The possible roles are: primary domain controller: Administration server. Distributes user accounts information to backup domain controllers. Validates network logon requests. There can be only one primary domain controller per domain. backup domain controller Receives user account information from the primary domain controller. Validates network logon requests and can be promoted to primary if the primary domain controller is not accessible. Enter role or press Enter to select 'primary': 7.To specify the server's role as a primary domain controller, press Enter. The system prompts you for the domain name: Enter the name of the domain or press Enter to select `shark.dom':shark.dom 8.To use the default domain name, press Enter, or enter a name of your own. The name that you enter can be up to 15 alphanumeric characters. 9.Follow the prompts to change or confirm the information you specified. For example, if you specified primary as the server's role, medusa as the server name, and shark.dom as the domain, the installation procedure displays the following: Confirm choices: server name : shark: role : primary domain : shark.dom Is this correct:y 10.To confirm the information, specify y. To return to Step 6 and change the information, enter n. The installation procedure creates an Administrative account, and prompts you for password information: This server will be the primary controller for the domain. An administrative account 'Administrator' will now be created for you to manage the domain. Enter the password for Administrator: 11.Enter an administrative password. The password can be up to 14 alphanumeric characters. You must specify this password when you log onto the server from a client to perform administrative tasks. The system prompts you for confirmation. Re-enter the password: Start PATHWORKS for Digital UNIX Advanced Server now [y/n]? y 12.Enter y to start PATHWORKS Advanced Server. However, if you want to start the server later, you can enter n and start the server at a later time by entering /usr/bin/net start server. Starting the PATHWORKS for Digital UNIX Advanced Server.... You have PATHWORKS for Digital UNIX Remote Boot service installed. It is recommended that you configure it at this time. Would you like to configure Remote Boot service? [y/n]? y 13.Enter y to configure the Remote Boot service now. However, you can also configure Remote Boot service later, by entering /usr/sbin/pwsetup remoteboot. The system asks if you want to replicate the remote boot directory to other servers. Because the Remote Boot service contains many files and directories, you may want to replicate the remote boot subdirectory on another server. Replicating files balances the server load while maintaining central version control. When you update files on one server, the Replicator service copies the updates to the replicated files on other servers. Refer to the PATHWORKS for Digital UNIX (Advanced Server) System Guide for additional information about the Replicator service. The Remoteboot directory can be replicated to other servers in the domain using the replication service. If you answer yes to replicating the remoteboot directory, this directory will be included in the export list for replication. Do you want to replicate the remoteboot directory to other servers [y/n]? n 14.Enter y to replicate the Remote Boot service to other servers. Answer n if you do not want replication. The installation procedure displays installation information for the Remote Boot service, and then asks if you would like to start PATHWORKS Advanced Server. For example: PATHWORKS for Digital UNIX Remote Boot service will use the IBM DLC protocol. Configuring dlc.so for "/dev/streams/dlpi" device Protocol is NetBEUI Adding RPLUSER group Adding RPLADMIN group Adding RPL share Adding RPLFILES share Adding BINFILES share Adding GUEST to RPLUSER group Starting the Remote Boot Service. 15.You can run IVP (Installation verfication Procedure) now or later. To run the ivp manually, type `lmivp' at the system prompt. You can run the ivp (Installation Verification Procedure) now or later. To run the ivp manually, type lmivp at the system prompt. Would you like to run the ivp now [y/n]? y 16.Enter y to run IVP: The system display is similar to the following: Starting the IVP (c) Digital Equipment Corporation. 1995-1996. All Rights Reserved. Verification #1 via network netbeui Create Share netbeui...Succeeded Grant user access to share...Succeeded Attempting connection to \\SHARK\netbeui...Succeeded List file...Succeeded Create file ...Succeeded Write data to file ...Succeeded Close data file ...Succeeded Open file for reading ...Succeeded Read data from file ... Succeeded Data verification...Succeeded Close data file ...Succeeded Tree disconnect ...Succeeded Remove access ...Succeeded Remove share NetBEUI ...Succeeded Network netbeui complete. . . . 17.The installation procedure checks for any user account data you saved from the previous configuration (accounts.lmx file). If no data is located, you can begin configuration of PATHWORKS NetWare or license server subsets. Go to step 18 to continue configuration. If the file is located, you must upgrade it to configure your users. The installation procedure displays the following prompt: Users, Groups and Access Control Entries can be upgraded from LAN Manager 2.x accounts file (/usr/net/servers/lanman/datafiles/accounts.lmx). Do you want to upgrade now [y/n]:y 18.Enter y to upgrade your PATHWORKS LAN Manager 2.x accounts. 19.The system checks to see if you installed PATHWORKS NetWare or license server subsets. If you did not, configuration is complete, and pwsetup configure returns you to the root prompt. If you installed PATHWORKS NetWare subsets, pwsetup configure displays the following prompt: Do you wish to configure NetWare Services [y/n]? y Turn to Step 3 in Configuring a PATHWORKS NetWare Server to continue configuration. If you installed license server software, pwsetup configure displays the following: Do you wish to configure the license server? [y/n]? y Turn to Step 2 in Configuring the License Server to continue configuration. Upgrading a Member Server The role of member server is not supported in this version of PATHWORKS for Digital UNIX. If you have a member server, Digital recommends that you follow prompts in the configuration scripts and reconfigure it as a backup domain controller. The following shows how to use pwsetup configure to upgrade a PATHWORKS for DEC OSF/1 member server: 1.Check to see that you are in multi-user mode, then login to the root account and enter /usr/sbin/pwsetup configure. 2.ASE TruCluster Environment detected. Configure PATHWORKS for Digital UNIX to run in the ASE TruCluster environment [y/n] ? n 3.Do you wish to configure Advanced Server Services [y/n]? y 4.Answer y to begin configuration. If you saved user account information from the previous configuration, the system displays upgrade information and a confirmation prompt. If you removed user account information from the previous configuration, the system prompts you for the account location. This is a directory on the server that contains the home directories of the PATHWORKS Advanced Server users. You can accept the default location, or you can enter the name of a directory where, for example, you know you have sufficient disk space. You may choose the directory location for your Advanced Server accounts, or accept the default location (/usr/net/servers/lanman/users). Creating default directory: /usr/net/servers/lanman/users/[y/n]?y 5.Enter y to accept the default location, or enter n and follow system prompts to specify your own directory name. The system displays information similar to the following: Updating saved LAN Manager information... Your LAN Manager role was member server in the domain. PATHWORKS for Digital UNIX Advanced Server has removed this role. The most appropriate mapping is to a backup domain controller. You can choose to have your member role automatically changed to backup and your old accounts upgraded to the new account format. Alternatively, you may wish to simply remove your old accounts and create a new primary or backup server, plus new account files. If you answer 'yes' to the following prompt, your old accounts will be upgraded. An answer of 'no' will remove your old accounts and allow you to create a new primary or backup server. Do you want to perform an automatic upgrade [y/n]?y 6.Enter y to upgrade your server automatically. Caution If you enter n, the system removes the user account and configuration information used by your previous configuration, and then overwrites server configuration files. You cannot restore the previous configuration unless you have a backup of these files. Refer to Chapter 1 for information about creating a backup of server files. 7.The system displays the following, and then prompts you for the server name: ADVANCED Server for UNIX provides a NETLOGON service which simplifies the administration of multiple servers. A single user accounts database can be shared by multiple servers grouped together into an administrative collection called a domain. Within a domain, each server has a designated role. A single server, called the primary domain controller, manages all changes to the user accounts database and automatically distributes those changes to other servers, called backup domain controllers, within the same domain. You may now supply a server name (the name by which this server will be known on the network), the role that this server will perform in that domain (primary or backup), and the domain name. Enter the name of the server or press Enter to select 'servername':bluefish 8.Enter the server name or press Enter to accept the default name. The system displays the following and prompts you for the type of server you want to install: Each server must be given a role in the domain. The possible roles are: primary domain controller: Administration server. Distributes user accounts information to backup domain controllers. Validates network logon requests. There can be only one primary domain controller per domain. backup domain controller Receives user account information from the primary domain controller. Validates network logon requests and can be promoted to primary if the primary domain controller is not accessible. Enter role (primary or backup):backup Enter the name of the domain or press ENTER to select `bluefish.dom': bluefish.dom 9.To specify the server's role as a backup domain controller, press Enter. The system prompts you for the name of the primary domain controller, and for the name and password of the administrative account, on the primary, that you will use to manage the server. The installation will configure the server as a backup domain controller for you. You will be prompted to enter the name of the primary domain controller, and an administrative account name on the primary along with its password. In order for this configuration to complete successfully, the primary domain controller must be running and connected to the network. Enter the name of the primary domain controller or press Enter to select 'servername':shark 10.Enter the name of the primary domain controller. The name you enter must be the node name of the primary domain controller, not the name of the domain. The system prompts you for the name of the administrative account. Enter the name of the administrative account on 'shark': or press Enter to select 'administrator': 11.Enter the name of the administrative account on the primary server or press Enter to select the default name. The system prompts you for the administrative account's password: Enter the password for administrator: 12.Enter the password for the administrative account. The system prompts you for confirmation. Re-enter the password: The Digital UNIX system tries to contact the primary domain controller and then prompts you for the administrator's password. If the system does not make contact, the installation procedure displays an informational error message. For example: Contacting the server 'shark' ...failed ERROR: Creation of remote account failed - access denied The account or password is invalid or 'Administrator' is not an administrative account. Do you want to retry[y/n]y Check to see that the primary domain server is active on the network and that it is configured with an administrative account and password. To re-enter the name of the primary domain controller and the administrator's password, answer y. If contact is again unsuccessful and the system displays the same prompt, enter n. This causes the system to configure your server as a primary domain controller on a randomly generated domain. When configuration is complete, the software prompts you for confirmation of the server role and domain. You can run the joindomain command, after installation is complete, to change the server role to backup and join the domain of the primary controller. A message similar to the following is displayed. This server could not be configured as a backup domain controller at this time. Installation will continue with this server configured as a primary domain controller with a randomly generated domain name. After installation is complete and the problems contacting the primary domain controller are resolved, run the command: joindomain which is located in the directory: /usr/net/servers/lanman/bin. With this command you can configure the server as a backup controller in a domain or as a primary domain controller. Confirm choices: servername : bluefish: role : primary domain : shark.do7065 If the system makes contact, the installation procedure displays an informational message and then prompts you for confirmation of your choices. For example: Contacting the server 'shark' ... Success Confirm choices servername : bluefish: role : backup domain : shark.dom primary : shark Is this correct:y Enter y to confirm your choices, or n to modify your choices by returning to Step 6. The system creates the user accounts database, a new access control list, and a new share list file. The PATHWORKS Advanced Server is started, and a list of available resources is displayed. The primary domain controller replicates the user accounts database to the backup domain controller. 13.The system displays informational messages, then checks for Remote Boot software. If you did not install this subset, the installation procedure asks if you want to start the PATHWORKS Advanced Server Start PATHWORKS for Digital UNIX Advanced Server now [y/n]? y 14.Enter y to start PATHWORKS Advanced Server. However, if you want to start the server later, you can enter n and start the server at a later time by entering /usr/bin/net start server. Starting the PATHWORKS for Digital UNIX Advanced Server... If you installed Remote Boot software, the system displays the following: You have PATHWORKS for Digital UNIX Remote Boot service installed. It is recommended that you configure it at this time. Would you like to configure Remote Boot service? [y/n]? y 15.Enter y to configure the Remote Boot service now. However, you can also configure Remote Boot service later, by entering /usr/sbin/pwsetup remoteboot. The system asks if you want to replicate the remote boot directory to other servers. Because the Remote Boot service contains many files and directories, you may want to replicate the remote boot subdirectory on another server. Replicating files balances the server load while maintaining central version control. When you update files on one server, the Replicator service copies the updates to the replicated files on other servers. Refer to the PATHWORKS for Digital UNIX (Advanced Server) System Guide for additional information about the Replicator service. The Remoteboot directory can be replicated to other servers in the domain using the replication service. If you answer yes to replicating the remoteboot directory, this directory will be included in the export list for replication. Do you want to replicate the remoteboot directory to other servers [y/n]? n 16.Enter y to replicate the Remote Boot service to other servers. Answer n if you do not want replication. The installation procedure displays installation information for the Remote Boot service, and then asks if you would like to start PATHWORKS Advanced Server. For example: PATHWORKS for Digital UNIX Remote Boot service will use the IBM DLC protocol. Configuring dlc.so for "/dev/streams/dlpi" device Protocol is NetBEUI Adding RPLUSER group Adding RPLADMIN group Adding RPL share Adding RPLFILES share Adding BINFILES share Adding GUEST to RPLUSER group Starting the Remote Boot Service. 17.The system displays start up messages, and asks if you want to run the Installation Verification Procedure (IVP). You can run the IVP by entering y at the prompt. If you prefer to run the IVP later, enter n. You can run the IVP at any time by entering lmivp. You can run the ivp (Installation Verification Procedure) now or later. To run the ivp manually, type lmivp at the system prompt. Would you like to run the ivp now [y/n]? y 18.Enter y to run the IVP. The system display is similar to the following: Waiting for server process to start up... Starting the IVP (c) Digital Equipment Corporation. 1995-1996. All Rights Reserved. Verification #1 via network netbeui Create share netbeui...Succeeded Grant user access to share...Succeeded Attempting connection to \\SHARK\netbeui...Succeeded List file...Succeeded Create file ...Succeeded Write data to file ...Succeeded Close data file ...Succeeded Open file for reading ...Succeeded Read data from file ... Succeeded Data verification...Succeeded Close data file ...Succeeded Tree disconnect ...Succeeded Revoke user access to share ...Succeeded Remove share netbeui ...Succeeded Network netbeui complete. . . 19.When IVP is complete, the installation procedure displays an informational message, advising you to run lmxupgrade after you complete this installation. This command upgrades your user account information (accounts.lmx file) so that it is compatible with the PATHWORKS Advanced Server software. Access Control Entries can be upgraded from the LAN Manager 2.x accounts file (/usr/net/servers/lanman/datafiles/accounts.lmx) after the user accounts and groups have been replicated to this backup controller. You will need to manually run /usr/net/servers/lanman/bin/lmxupgrade after this installation is complete. 20.The system checks to see if you installed PATHWORKS NetWare or license server subsets. If you did not, configuration is complete and pwsetup configure returns you to the root prompt. If you installed PATHWORKS NetWare subsets, pwsetup configure displays the following prompt: Do you wish to configure NetWare Services [y/n]? y Turn to Step 3 in Configuring a PATHWORKS NetWare Server to continue configuration. If you installed license server software, pwsetup configure displays the following: Do you wish to configure the license server? [y/n]? y Turn to Step 2 in Configuring the License Server to continue configuration. Upgrading a Primary or Backup Server If you are upgrading PATHWORKS for Digital UNIX using the data saved from a previous version, the pwsetup configure utility displays an abbreviated script. This is because you do not need to reconfigure items that you saved from the previous configuration, and these items are omitted from the configuration script. If you are ready to upgrade your primary or backup server, see Configuring PATHWORKS Advanced Server Primary Domain Controller or Configuring a Backup Domain Controller, below, for additional information. Because you are upgrading, your system may not display every prompt discussed in these sections. Configuring PATHWORKS Advanced Server on a New Server The following sections describe how to configure PATHWORKS Advanced Server software for the first time. Configuring PATHWORKS Advanced Server Primary Domain Controller The following shows how to use pwsetup configure to configure a PATHWORKS Advanced Server primary domain controller: 1. Check to see that you are in multi-user mode, then log into the root account and enter /usr/sbin/pwsetup configure. 2. If PATHWORKS is being configured on a system within a Digital UNIX TruCluster Environment, you will see the following display: ASE TruCluster Environment detected. Configure PATHWORKS for Digital UNIX to run in the ASE TruCluster environment [y/n] ? n If you wish to configure PATHWORKS for Digital UNIX to run in the TruCluster environment, refer to the section later in this chapter for the procedure that you need to follow. 3.Do you wish to configure Advanced Server Services [y/n]? y 4.Answer y to begin configuration. PATHWORKS Advanced Server The system prompts you for the location of the user account directory. This is a directory on the server that contains the home directories of the PATHWORKS Advanced Server users. You can accept the default location, or you can enter the name of a directory where, for example, you know you have sufficient disk space. You may choose the directory location for your Advanced Server accounts, or accept the default location (/usr/net/servers/lanman/users). Use default directory /usr/net/servers/lanman/users [y/n]? y Creating default directory: /usr/net/servers/lanman/users 5.Enter y to accept the default location, or enter n and follow system prompts to specify your own directory name. The system displays information similar to the following: ADVANCED Server for UNIX provides a NETLOGON service which simplifies the administration of multiple servers. A single user accounts database can be shared by multiple servers grouped together into an administrative collection called a domain. Within a domain, each server has a designated role. A single server, called the primary domain controller, manages all changes to the user accounts database and automatically distributes those changes to other servers, called backup domain controllers, within the same domain. You may now supply a server name (the name by which this server will be known on the network), the role that this server will perform in that domain (primary or backup), and a domain name. Enter the name of the server or press Enter to select 'servername':shark 6.Enter the server name, or press Enter to accept the default name. The system displays the following and prompts you for the type of server you want to install: Each server must be given a role in the domain. The possible roles are: primary domain controller: Administration server. Distributes user accounts information to backup domain controllers. Validates network logon requests. There can be only one primary domain controller per domain. backup domain controller Receives user account information from the primary domain controller. Validates network logon requests and can be promoted to primary if the primary domain controller is not accessible. Enter role (primary or backup):primary 7.To specify the server's role as a primary domain controller, enter primary at the prompt. The installation procedure prompts you for the domain name. Enter the name of the domain or press Enter to select 'domainname':shark.dom 8.To use the default domain name, press Enter, or enter a name of your own. The name that you enter can be up to 15 alphanumeric characters. 9.Follow the prompts to change or confirm the information you specified. For example, if you specified primary as the server's role, shark as the server name, and shark.dom as the domain, the installation procedure displays the following: Confirm choices: servername : shark role : primary domain : shark.dom Is this correct [y/n]? y 10.To confirm the information, specify y. To return to Step 4, and modify your choices, enter n. The installation procedure creates an Administrative account and prompts you for password information. This server will be the primary controller for the domain. An administrative account 'Administrator' will now be created for you to manage the domain. Enter the password for Administrator: 11.Enter an administrative password. The password can be up to 14 alphanumeric characters. You must specify this password when you log onto the server from a client to perform administrative tasks. The system prompts you for confirmation. Re-enter the password: 12.Enter your password again. The installation procedure displays informational messages, then checks for Remote Boot software. If you did not install this subset, the installation procedure asks if you want to start the PATHWORKS Advanced Server Start PATHWORKS for Digital UNIX Advanced Server now [y/n]? y 13.Enter y to start PATHWORKS Advanced Server. However, if you want to start the server later, you can enter n and start the server at a later time by entering /usr/bin/net start server. Starting the PATHWORKS for Digital UNIX Advanced Server... If you installed Remote Boot software, the system displays the following: You have PATHWORKS for Digital UNIX Remote Boot service installed. It is recommended that you configure it at this time. Would you like to configure Remote Boot service? [y/n]? y 14.Enter y to configure the Remote Boot service now. However, you can also configure Remote Boot service later, by entering /usr/sbin/pwsetup remoteboot. The system asks if you want to replicate the remote boot directory to other servers. Because the Remote Boot service contains many files and directories, you may want to replicate the remote boot subdirectory on another server. Replicating files balances the server load while maintaining central version control. When you update files on one server, the Replicator service copies the updates to the replicated files on other servers. Refer to the PATHWORKS for Digital UNIX (Advanced Server) System Guide for additional information about the Replicator service. The Remoteboot directory can be replicated to other servers in the domain using the replication service. If you answer yes to replicating the remoteboot directory, this directory will be included in the export list for replication. Do you want to replicate the remoteboot directory to other servers [y/n]? n 15.Enter y to replicate the Remote Boot service to other servers. Answer n if you do not want replication. The installation procedure displays installation information for the Remote Boot service and then asks if you would like to start the PATHWORKS Advanced Server. For example: PATHWORKS for Digital UNIX Remote Boot service will use the IBM DLC protocol. Configuring dlc.so for "/dev/streams/dlpi" device Protocol is NetBEUI Adding RPLUSER group Adding RPLADMIN group Adding RPL share Adding RPLFILES share Adding BINFILES share Adding GUEST to RPLUSER group 16.If you answered y, the system displays startup messages, and asks if you want to run IVP. You can run IVP by entering y at the prompt. If you prefer to run IVP later, enter n. You can run IVP at any time by entering lmivp. You can run the ivp (Installation Verification Procedure) now or later. To run the ivp manually, type lmivp at the system prompt. Would you like to run the ivp now [y/n]? y 17.Enter y to run IVP: The system display is similar to the following: Starting the IVP (c) Digital Equipment Corporation. 1995-1996. All Rights Reserved. Verification #1 via network netbeui Create share netbeui...Succeeded Grant user access to share...Succeeded Attempting connection to \\SHARK\netbeui...Succeeded List file...Succeeded Create file ...Succeeded Write data to file ...Succeeded Close data file ...Succeeded Open file for reading ...Succeeded Read data from file ... Succeeded Data verification...Succeeded Close data file ...Succeeded Tree disconnect ...Succeeded Revoke user access to share ...Succeeded Remove share netbeui ...Succeeded Network netbeui complete. . . . 18.The system checks to see if you installed PATHWORKS NetWare or license server subsets. If you did not, configuration is complete, and pwsetup configure returns you to the root prompt. If you installed PATHWORKS NetWare subsets, pwsetup configure displays the following prompt: Do you wish to configure NetWare Services [y/n]? y Turn to Step 3 in Configuring a PATHWORKS NetWare Server to continue configuration. If you installed license server Software, pwsetup configure displays the following: Do you wish to configure the license server? [y/n]? y Turn to Step 2 in Configuring the License Server to continue configuration. Configuring a Backup Domain Controller The following describes how to use pwsetup configure to configure a PATHWORKS Advanced Server backup domain controller: 1.Check to see that you are in multi-user mode, then login to the root account and enter /usr/sbin/pwsetup configure. 2.If PATHWORKS is being configured on a system in a Digital UNIX TruCluster Environment, you will see the following display: ASE TruCluster Environment detected. Configure PATHWORKS for Digital UNIX to run in the ASE TruCluster environment [y/n] ? n If you wish to configure PATHWORKS for Digital UNIX to run in the ASE TruCluster environment refer to the section later in this chapter for the procedure that you need to follow. 3.Do you wish to configure Advanced Server Services [y/n]? y 4.Answer y to begin configuration. The system prompts you for the location of the user account directory. This is a directory on the server that contains the home directories of the PATHWORKS Advanced Server users. You can accept the default location, or you can enter the name of a directory where, for example, you know you have sufficient disk space. You may choose the directory location for your Advanced Server accounts, or accept the default location (/usr/net/servers/lanman/users). Use default directory /usr/net/servers/lanman/users [y/n]? y Creating default directory: /usr/net/servers/lanman/users 5.Enter y to accept the default location, or enter n and follow system prompts to specify your own directory name. The system displays information similar to the following: PATHWORKS for Digital UNIX ADVANCED Server provides a NETLOGON service which simplifies the administration of multiple servers. A single user accounts database can be shared by multiple servers grouped together into an administrative collection called a domain. Within a domain, each server has a designated role. A single server, called the primary domain controller, manages all changes to the user accounts database and automatically distributes those changes to other servers, called backup domain controllers, within the same domain. You may now supply a server name (the name by which this server will be known on the network), the role that this server will perform in that domain (primary or backup), and the domain name. Enter the name of the server or press Enter to select 'servername':bluefish 6.Enter the server name, or press Enter to accept the default name. The system displays the following, and prompts you for the type of server you want to install: Each server must be given a role in the domain. The possible roles are: primary domain controller: Administration server. Distributes user accounts information to backup domain controllers. Validates network logon requests. There can be only one primary domain controller per domain. backup domain controller Receives user account information from the primary domain controller. Validates network logon requests and can be promoted to primary if the primary domain controller is not accessible. Enter role (primary or backup):backup 7.To specify the server's role as a backup domain controller, enter backup at the prompt. The system prompts you for the name of the primary domain controller, and for the name and password of the administrative account, on the primary domain controller, that you will use to manage the server. The installation will configure the server as a backup domain controller for you. You will be prompted to enter the name of the primary domain controller, and an administrative account name on the primary along with its password. In order for this configuration to complete successfully, the primary domain controller must be running and connected to the network. Enter the name of the primary domain controller: shark 8.Enter the name of the primary domain controller. The name you enter must be the node name of the primary domain controller, not the name of the domain. The system prompts you for the name of the administrative account. Enter the name of the administrative account on 'shark': or press Enter to select 'administrator': 9.Enter the name of the administrative account on the primary domain controller, or press Enter to select the default name. The system prompts you for the administrative account's password: Enter the password for administrator: 10.Enter the password for the administrative account. The system prompts you for confirmation. Re-enter the password: Re-enter your password. The Digital UNIX system tries to contact the primary domain controller, and then prompts you for the administrator's password. _ If the system does not make contact, the installation procedure displays an informational message. For example: Contacting the server 'shark' ...failed ERROR: Creation of remote account failed - server unavailable The primary controller 'shark' is not running or is not connected to the network. Do you want to retry[y/n]:y _ Check to see that the primary domain server is active on the network, and that it is configured with an administrative account and password. To re-enter the name of the primary domain controller and the administrator's password, answer y. If contact is again unsuccessful, the system displays the same prompts. Enter n. This causes the system to configure your server as a primary domain controller with a randomly generated domain name. When configuration is complete, the system prompts you for confirmation of the server role and domain. You can run the joindomain command, after installation is complete, to change the server role to backup and join the domain of the primary controller. A message similar to the following displays: This server could not be configured as a backup domain controller at this time. Installation will continue with this server configured as a primary domain controller with a randomly generated domain name. After installation is complete and the problems contacting the primary domain controller are resolved, run the command: joindomain which is located in the directory: /usr/net/servers/lanman/bin. With this command you can configure the server as a backup controller in any domain or as a primary domain controller. Confirm choices: servername : bluefish role : primary domain : shark.do7065 _ If the system makes contact, the installation procedure displays an informational message and then prompts you for confirmation of your choices For example: Contacting the server 'shark' ...success Confirm choices servername : bluefish: role : backup domain : shark.dom Is this correct:y _ Enter y to confirm your choices. To return to Step 4 and modify your selections, enter n. The system creates the user accounts database, a new access control list, and a new share list file. The PATHWORKS Advanced Server is started, and a list of available resources is displayed. The Primary Domain controller replicates the user accounts database to the backup domain controller. 11.The installation procedure displays informational messages, then asks if you want to start the PATHWORKS Advanced Server. Start PATHWORKS for Digital UNIX Advanced Server now [y/n]? y 12.Enter y to start PATHWORKS Advanced Server. However, if you want to start the server later, you can enter n and start the server at a later time by entering /usr/bin/net start server. Starting the PATHWORKS for Digital UNIX Advanced Server... 13.If you installed Remote Boot software, the system displays the following: You have PATHWORKS for Digital UNIX Remote Boot service installed. It is recommended that you configure it at this time. Would you like to configure Remote Boot service? [y/n]? y 14.Enter y to configure the Remote Boot service now. However, you can also configure Remote Boot service later, by entering: /usr/sbin/pwsetup remoteboot. The system asks if you want to replicate the remote boot directory to other servers. Because the Remote Boot service contains many files and directories, you may want to replicate the remote boot subdirectory on another server. Replicating files balances the server load while maintaining central version control. When you update files on one server, the Replicator service copies the updates to the replicated files on other servers. Refer to the PATHWORKS for Digital UNIX (Advanced Server) System Guide for additional information about the Replicator service. The Remoteboot directory can be replicated to other servers in the domain using the replication service. If you answer yes to replicating the remoteboot directory, this directory will be included in the export list for replication. Do you want to replicate the remoteboot directory to other servers [y/n]? y 15.Enter y to replicate the Remote Boot service to other servers. Answer n if you do not want replication. The installation procedure displays installation and configuration information for the Remote Boot service, and then asks if you would like to start PATHWORKS Advanced Server . For example: PATHWORKS for Digital UNIX Remote Boot service will use the IBM DLC protocol. Configuring dlc.so for "/dev/streams/dlpi" device Protocol is NetBEUI Adding RPLUSER group Adding RPLADMIN group Adding RPL share Adding RPLFILES share Adding BINFILES share Adding GUEST to RPLUSER group Starting the Remote Boot Service. 16.If you answered y, to start the Advanced Server, the system displays start up messages, and asks if you want to run the IVP. You can run the IVP by entering y at the prompt. If you prefer to run the IVP later, enter n. You can run the IVP at any time by entering lmivp. You can run the ivp (Installation Verification Procedure) now or later. To run the ivp manually, type lmivp at the system prompt. Would you like to run the lmivp now? [y/n]? y 17.Enter y to run the IVP. The system display is similar to the following: Starting the IVP (c) Digital Equipment Corporation. 1995-1996. All Rights Reserved. Verification #1 via network netbeui Create share netbeui...Succeeded Grant user access to share...Succeeded Attempting connection to \\BLUEFISH\netbeui...Succeeded List file...Succeeded Create file ...Succeeded Write data to file ...Succeeded Close data file ...Succeeded Open file for reading ...Succeeded Read data from file ... Succeeded Data verification...Succeeded Close data file ...Succeeded Tree disconnect ...Succeeded Revoke user access to share ...Succeeded Remove share netbeui ...Succeeded Network netbeui complete. 18.The system checks to see if you installed PATHWORKS NetWare or license server subsets. If you did not, configuration is complete, and pwsetup configure returns you to the root prompt. If you installed PATHWORKS NetWare subsets, pwsetup configure displays the following prompt: Do you wish to configure NetWare Services [y/n] y? Turn to Step 3 in Configuring a PATHWORKS NetWare Server to continue configuration. If you installed license server software, pwsetup configure displays the following: Do you wish to configure the license server? [y/n]? y Turn to Step 2 in Configuring the License Server to continue configuration. Using a PATHWORKS for DEC OSF/1 Backup Server in a PATHWORKS Advanced Server Domain A PATHWORKS for DEC OSF/1 backup domain controller can be part of a PATHWORKS Advanced Server domain and can function as a backup domain controller. That is, it will maintain a valid list of PATHWORKS Advanced Server accounts and can perform logon validation for the PATHWORKS Advanced Server domain. However, it cannot function as a primary domain controller in the PATHWORKS Advanced Server domain. Use the following procedure to move a PATHWORKS for DEC OSF/1 backup domain controller to an Advanced Server domain: On the PATHWORKS Advanced Server primary domain controller: 1.Make sure the PATHWORKS for DEC OSF/1 administrative account admin is created. Confirm that the password is the same as the one on the backup server. 2.Make sure that the PATHWORKS for DEC OSF/1 administrative account admin is added to the Advanced Server group Domain Admins. On the PATHWORKS for DEC OSF/1 backup domain controller: 1.Using the net accounts command, change the role of the PATHWORKS for DEC OSF/1 server to standalone by entering the following command: net accounts /role:standalone 2.Stop the PATHWORKS for DEC OSF/1 server. 3.If necessary, edit the lanman.ini file to change the domain of the PATHWORKS for DEC OSF/1 server to the domain of the Advanced Server. 4.Start the PATHWORKS for DEC OSF/1 server. 5.Log onto the Advanced Server domain using the PATHWORKS for DEC OSF/1 administrative account and password. 6.Using the net accounts command, change the role of the PATHWORKS for DEC OSF/1 server to backup domain controller by entering the following command: net accounts /role:backup Changing the role of the PATHWORKS for DEC OSF/1 server will result in the following: The SERVERS group will be created on the Advanced Server and the LAN Manager machine account will be added as a member of that group. The Advanced Server primary domain controller will replicate the user account database to the LAN Manager backup controller. Installing Windows NT Server Tools You must install the Windows NT server Tools program if you want to administer your PATHWORKS Advanced Server from a Windows 3.1 or Windows for Workgroups client. Before you begin, check to see that the client has the latest network redirector software and network API library for Windows. They are as follows: For Windows for Workgroups Version 3.11, the Windows NT server Tools Setup program installs a new redirector (VREDIR.386) and network API library (NETAPI.DLL). For LAN Manager for MS-DOS Client, you must upgrade to Version 2.2c, which includes the latest redirector. Installing Windows NT Server Tools Software To install Windows NT server tools you first copy the software, from the server, to the client machine. You must then edit several files that reside on the client. Complete the following procedure to install Windows NT Server Tools software. The names of menu options may vary slightly on Windows for Workgroups screens. 1.Log onto the Advanced Server as administrator. Establish a connection to the shared resource ASTOOLS on the Advanced Server using File Manager. On the client computer, select Disk from the menu bar. 2.Select Connect Network Drive... from the Disk menu. 3.On the Network Drive Connection screen, enter \\servername\ASTOOLS to specify the location of the ASTOOLS share, substituting the name of the primary domain controller for servername. Click the Connect button. The connection displays in the Current Connections box. 4.Click the Close button. 5.In the File Manager window, select the icon for the drive that you just created. 6.In the ASTOOLS directory, select WINDOWS. The system displays the Windows NT Server Tools program files. 7.Scroll to the SETUP.EXE program. 8.Choose Run from the File menu to execute the SETUP.EXE program. The system displays the Windows NT Tools Setup Program window on the client computer. 9.Click Continue. 10.Select the Install all files button. Windows NT Server Tools will be installed at the root drive in the SRVTOOLS directory. 11.Select the appropriate entry in the Select Time Zone dialog box. After the Windows NT Server Tools program group installation completes, the system displays a message to edit files and reboot the computer. Before completing the installation process, you must return to the File Manager and disconnect the connection to the shared resource ASTOOLS. 12.Select Connect Network Drive... from the Disk menu. 13.In the Current Connections pane, select the connection to the ASTOOLS resource. Click the Disconnect button. 14.Click the Close button. Editing CONFIG.SYS and AUTOEXEC.BAT Client Files When you install Windows NT server Tools, there are several files in the client computer that you must edit manually. During the installation of Windows NT server Tools, the Setup program creates the NEW-CONF.SYS and NEW-VARS.BAT files in the client computer's SRVTOOLS directory. Each of these files contains lines that you must copy to the client computer's CONFIG.SYS and AUTOEXEC.BAT files. Follow the steps below to copy information to the CONFIG.SYS and AUTOEXEC.BAT files and complete the installation: 1.Edit the CONFIG.SYS file to contain the line: files=x where x is a number equal to or greater than 30. The files statement in the \SRVTOOLS\NEW-CONFIG.SYS file is the recommended number of files. 2.Edit the AUTOEXEC.BAT file to reflect the following changes: The directory containing the Windows NT Server Tools must be on the PATH line. If you are in a time zone other than Pacific Standard Time (PST), copy the time zone statement recommended in the \SRVTOOLS\NEW.VARS.BAT file and add a set tz line to set the time zone. For example, if you are in New York, you would add the following: set tz=uct+05:00 3.Reboot the client computer. Installing Windows NT Administrative Tools You must install Windows NT Administrative Tools to administer your PATHWORKS Advanced Server from a Windows 3.x, Windows NT, or Windows 95 computer. Installing on a Windows 3.x or Windows NT Computer Complete the following steps to install Windows NT Administrative tools on a Windows 3x or Windows NT computer: 1.From a Windows NT Workstation computer, log onto the PATHWORKS Advanced Server as administrator. Establish a connection to the shared resource ASTOOLS in the Advanced Server using File Manager. 2.Select Disk from the menu bar of the File Manager. 3.Select Connect Network Drive... from the Disk menu. 4.From the Shared Directories pane in the Connect Network Drive dialog box, select the primary domain controller for your domain. 5.Select ASTOOLS from the displayed share names. The ASTOOLS share contains the Windows NT Administrative Tools software. ASTOOLS displays in the Path: box with the next available drive letter. 6.Click the OK button. The ASTOOLS shared resource displays. 7.If you are installing on a Windows NT Administrative Tools on a Windows NT computer, in the ASTOOLS directory, click winnt. If you are installing Windows NT Administrative Tools on a Windows 3.x computer, in the ASTOOLS directory click windows. The system displays the Windows NT Administrative Tools program files. 8.If you are installing Windows NT Administrative Tools on a Windows NT computer, scroll to the SETUP.BAT program. If you are installing Windows NT Administrative Tools on a Windows 3.x computer, scroll to the SETUP.EXE program. 9.From the File menu Choose Run to execute either SETUP.BAT or SETUP.EXE program. The client-based network administrative tools are installed. The system displays a message indicating that program icons may be created for the following program items: Server Manager, User Manager for Domains, and User Profile Editor. Refer to Windows NT or Windows 3.x documentation for information how to create program items and icons. Before completing the installation process, return to the File Manager window and disconnect the connection to the shared resource ASTOOLS. 12.Select Connect Network Drive... from the Disk menu. 13.In the Current Connections pane, select the connection to the ASTOOLS resource. Click the Disconnect button. 14.Click the Close button. Installing on a Windows 95 Computer Complete the following steps to install Windows NT Administrative tools on a Windows 95 computer: 1. From a Windows 95 computer, log onto the PATHWORKS Advanced Server as Administrator. 2. Establish a connection to the shared resource ASTOOLS on the PATHWORKS Advanced Server using the Explorer. 3. Select Tools from the menu bar of the Explorer Window. 4. Select Map Network Drive... from the Tools menu. 5. In the Path: field, enter \\controller\astools, substituting the name of the primary domain controller for controller. Click OK. 6. The system displays the new drive under the Folders section of the Explorer window. 7.Click the Start button in the Task Bar, then point to Settings. 8.Click Control Panel. 9.On the Control Panel screen, click twice on Add/Remove Programs. 10.On the Add/Remove Program Properties screen, select the Windows Setup tab. 11.Click the Have Disk button, and then specify the drive that you defined in step 4 by entering drivername:\win95, substituting the name of your drive for drivername. Select OK. 12.On the Have Disk screen, locate the box to the right of the Windows NT Server Tools text, inside the title bar of the scroll box. Click the box. 13.The system displays a check mark within the box. 14.Click the Install button at the bottom of the Have Disk screen. When all files are copied, click OK. 15.The system installs Windows NT Administrative tools in the \srvtools directory on the system's boot drive. 16.To use Windows NT Administrative Tools, select the Start button from the Task Bar. Then select Program Option, followed by Windows NT Server Tools. Setting Up Browsing Master Browser election occurs automatically between servers in the domain. This release of PATHWORKS Advanced Server automatically becomes a Master Browser when it is installed on a Primary Domain Controller. Configuring a PATHWORKS NetWare Server Use the pwsetup configure utility to configure a PATHWORKS NetWare server. Follow these steps: 1.Check to see that you are in multi-user mode, then log into the root account and enter: /usr/sbin/pwsetup configure 2.If PATHWORKS is being configured on a system within a Digital UNIX TruCluster Environment, you will see the following display: ASE TruCluster Environment detected. Configure PATHWORKS for Digital UNIX to run in the ASE TruCluster environment [y/n] ? n If you wish to configure PATHWORKS for Digital UNIX to run in the ASE TruCluster environment refer to the section later in this chapter for the procedure that you need to follow 3.If you installed PATHWORKS Advanced Server subsets, the pwsetup configure utility asks if you wish to configure PATHWORKS Advanced Server services. Do you wish to configure Advanced Server services [y/n]? y Answer n. The pwsetup configure utility asks if you wish to configure PATHWORKS NetWare. Do you wish to configure NetWare Services [y/n]? y 4.Enter y to begin configuration. The pwsetup configure utility prompts you for the location of the user account directory. This is a directory on the server that contains the home directories of the PATHWORKS NetWare users. You can accept the default location, or you can enter the name of a directory where, for example, you know you have sufficient disk space. You may choose the directory location for your NetWare accounts, or accept the default location (/usr/net/servers/netware/users). Use default location /usr/net/servers/netware/users [y/n]? y 5.Enter y to accept the default location, or enter n and follow system prompts to specify your own directory name. The pwsetup configure utility asks if you would like to start the server. Start the PATHWORKS for Digital UNIX NetWare Server now [y/n]? y 6.Answer y to start the server. The pwsetup configure utility starts the server. Starting NetWare Server /sbin/init.d/nw_srv: NetWare starting... 7.The system asks if you want to run the NetWare Installation Verification Procedure (IVP). To run NetWare IVP, enter y at the prompt. If you prefer to run IVP later, enter n. You can run IVP at any time by entering nwivp. You can run the NetWare IVP (Installation Verification Procedure) now or later. To run the IVP manually, type nwivp at the system prompt. Would you like to run the NetWare IVP now? [y/n]? y 8.Answer y to run the NetWare IVP. The system display is similar to the following: Waiting for NetWare server process to start up... NetWare Server started Starting the IVP (c) Digital Equipment Corporation. 1995-1996. All Rights Reserved. Verification #1 for NetWare Server SHARK Opening /dev/streams/ipx ....Succeeded. Opening /dev/streams/nspx ....Succeeded. Opening /dev/streams/ripx ....Succeeded. Attempting to attach to Server SHARK_NW ....Succeeded Attempting to login as SUPERVISOR....Succeeded Creating Hybrid User IVPTEST....Succeeded Attempting to attach to Server SHARK_NW....Succeeded Attempting to login as IVPTEST....Succeeded Attempting to attach to Server SHARK_NW ....Succeeded Attempting to login as SUPERVISOR....Succeeded Deleting Hybrid User IVPTEST....Succeeded Verifying that SYS Volume exists....Succeeded Create Directory ...Succeeded Create File ...Succeeded Write data to file ...Succeeded Close data file ...Succeeded Open file for reading ...Succeeded Read data from file ...Succeeded Data Verification ...Succeeded Close data file ...Succeeded Deleting data file ...Succeeded Delete Directory ...Succeeded Logging out ....Succeeded Detaching from server....Succeeded Closing transports....Succeeded Verification #1 Complete for NetWare server SHARK_NW 9.When NetWare IVP is complete, the system checks if you installed the license server subset. If you did not, configuration is complete, and pwsetup configure returns you to the root prompt. However, if you installed the license server, the system displays the following: Do you wish to configure the license server? [y/n]? y Turn to Step 2 in Configuring the License Server to continue configuration. Configuring the License Server To configure the license server on a separate system, you must install and configure at least one PATHWORKS for Digital UNIX transport. If your domain includes PATHWORKS NetWare clients, you must also install the NetWare Services subset (PWKNWBASE610). Refer to Chapter 2, Installing PATHWORKS for Digital UNIX, in this guide, for information about how to select transports subsets. Refer to Configuring Network Controllers in this guide for specific controller configuration information. Follow these steps to configure the license server: 1.Check to see that you are in multi-user mode, then log onto the root account and enter /usr/sbin/pwsetup configure. The pwsetup configure utility asks if you wish to configure PATHWORKS Advanced Server services. Do you wish to configure Advanced Server services [y/n]? n 2.Answer n. The pwsetup configure utility asks if you wish to configure PATHWORKS NetWare. Do you wish to configure NetWare Services [y/n]? n 3.Enter n. The pwsetup configure utility asks if you wish to configure the license server. Do you wish to configure the license server [y/n]? y 4.Answer y to begin configuration. The system checks for license server software running on the system. If the software is detected, the installation program automatically exits. You cannot configure the license server on a system where it is already running. If no licensing software is running, the system displays the following information, and then asks if you want to run the license server software. Configuring the license server... PATHWORKS for Digital UNIX requires that each client connecting to a PATHWORKS server must obtain a license. There are two kinds of licenses that a client may obtain: a client-based license or a server-based license (for more information, see the Guide to Managing PATHWORKS Licenses). The license server is the program that assigns and verifies client-based licenses. Clients cannot obtain a client-based license unless the license server software is installed and running. Only one PATHWORKS for Digital UNIX server in each Local Area Network should be configured to run the license server. The PATHWORKS for Digital UNIX server with the license server software must also have the LMF client- based license authorization keys loaded. Refer to lmf(8), in the DEC OSF/1 reference pages, for more information. Would you like to run the license server [y/n]? y 5.Answer y to run the license server now. The system starts the server and displays the following message, then returns you to the root prompt. Starting license server Note If you entered "n" to the question "Would you like to run the license server" in order to run the license server at a later time, you must first reset the `runserver' parameter in the pathworks.ini file. You can do this by either editing the file directly (runserver=yes), or by re-running `pwsetup configure' to configure the license server in a different way. Configuring PATHWORKS in a TruCluster Environment To perform this function refer to the PATHWORKS for Digital UNIX TruCluster Family Administrator's Guide. Next Steps You may need to complete some post-installation tasks after you finish the PATHWORKS for Digital UNIX configuration. Refer to Chapter 4, Server Setup and Tuning, in this guide, if you need to: Tune PATHWORKS Advanced Server parameters for large configurations, including values for number of clients, sessions, and shared memory. Configure PCSA mail for clients configured with TCP/IP. Tune server connections for PATHWORKS NetWare servers with over 50 clients. Use pwsetup kernel to modify the controller information you entered during PATHWORKS for Digital UNIX configuration. Modify the network controllers you configured during PATHWORKS for Digital UNIX installation. 4 Server Setup and Tuning This chapter describes how to set up and tune PATHWORKS for Digital UNIX after you complete installation. Read this chapter if you need to set up shares and volumes, modify the controller information and WAN parameters that you entered during the installation procedure, or tune server parameters. This chapter describes how to setup and tune a server with: PATHWORKS Advanced Server software PATHWORKS NetWare software PATHWORKS Advanced Server and PATHWORKS NetWare software Setting Up and Tuning PATHWORKS Advanced Server Software This section describes how to specify clients, server sessions, and shared memory on a PATHWORKS Advanced Server system. You may need to set these parameters if you want to accomplish either of the following: Limit the number of clients that can access the PATHWORKS Advanced Server Configure the PATHWORKS Advanced Server to support an unusually large number clients and connections Specifying the Number of Clients By default, the PATHWORKS Advanced Server is configured to allow 250 clients to connect to the server. If you want to limit the number of users that can access the server, you can change this default to a lower value by modifying the maxclients keyword in the [server] section of the lanman.ini file. If you want to increase this number, you may also need to increase the number of sessions that your server can support. Refer to the PATHWORKS for Digital UNIX (Advanced Server) System Guide for information about how to modify the lanman.ini file. Specifying the Number of Server Sessions If your configuration is very large, you may need to reset the number of sessions your PATHWORKS Advanced Server can open. Table 4-1, Default Session Limits, shows the default session limits for PATHWORKS Advanced Server transports. Table 4-1: Default Session Limits Transport Default Sessions NetBEUI 256 TCP/IP 256 (255 if WAN support is enabled) DECnet/OSI Determined by the DECnet/OSI software and your system configuration. Refer to DECnet/OSI documentation for additional information. Resetting the number of sessions for the NetBEUI transport To reset the number of NetBEUI sessions, add the following lines to the /etc/sysconfigtab file: netbeui: nb_sessions=128 For example: # HISTORY # # (c) Copyright 1990, 1991, 1992, 1993 OPEN SOFTWARE FOUNDATION, # INC, ALL RIGHTS RESERVED # OSF/1 1.2 vm: ubc-maxpercent=70 ubc-borrowpercent=20 vm-page-free-target=256 netbeui: nb_sessions=128 You must reboot the system to activate your changes. Resetting the number of sessions for the TCP/IP transport To reset the number of TCP/IP sessions, add the following lines to the /etc/sysconfigtab file: knbtcp: knbsessions=128 For example: # HISTORY # # (c) Copyright 1990, 1991, 1992, 1993 OPEN SOFTWARE FOUNDATION, # INC, ALL RIGHTS RESERVED # OSF/1 1.2 vm: ubc-maxpercent=70 ubc-borrowpercent=20 vm-page-free-target=256 knbtcp: knbsessions=128 You must reboot the system to activate your changes. Modifying Shared Memory on PATHWORKS Advanced Server Systems If a server denies client file open requests after you complete the installation procedure, you may need to adjust shared server memory. You should allocate additional memory carefully and only if you are experiencing server problems. You can modify the amount of shared memory the PATHWORKS Advanced Server allocates by editing the ustruct parameter in the lanman.ini file. A ustruct element is used in shared memory, to manage open files and record locks. The default ustruct value is 1000 elements. Follow the guideline below to compute the number of elements you need. The parameter you specify is activated the next time you start the PATHWORKS Advanced Server. ustructs = maximum number of open files + 2* maximum number of open locks + maximum number of file locks If you increase the ustruct parameter, you may also need to increase the parameter that specifies the amount of Digital UNIX shared memory. Refer to the Digital UNIX Guide to System Tuning for information about shared memory. Refer to the PATHWORKS for Digital UNIX (Advanced Server) System Guide for information about parameters within the lanman.ini file. Configuring PCSA Mail To configure PCSA mail on a PATHWORKS client that uses TCP/IP, you must add a shell to the /etc/passwd entry for the user, move the pcsamail executable to a new directory location, and create a profile in the user's home directory. To do so: 1.As root, edit the /etc/passwd entry for the user and add the Rsh shell. The Rsh shell provides the user with restricted access to. the PATHWORKS Advanced Server. It enables the user to log into the server and use PCSA mail commands, but does not allow them to execute any other Digital UNIX commands. For example, to add the Rsh shell for user suep, locate the entry for suep in the /etc/passwd file: suep:*:203:1:.LAN Server .LMX:/usr/net/servers/lanman/users/suep: /bin/false Change the shell from /bin/false to restricted: suep:*:203:1:.LAN Server .LMX:/usr/net/servers/lanman/users/suep: /bin/Rsh 2.Create the new directory for the pcsamail executable. Enter: mkdir /usr/rbin 3.Locate the directory path for the pcsamail executable on your system. The path varies, depending on the version of PATHWORKS for Digital UNIX that you have installed. Enter: ls -l /usr/bin/pcsamail lrwxrwxrws 1 root system 36 Nov 22 1838 /usr/bin/pcsamail -> usr/E506/usr/bin/pcsamail 4.Copy the pcsamail executable to the /usr/rbin directory location. For example, to copy the previous file, enter: cp -p /usr/E506/usr/bin/pcsamail /usr/rbin 5.Create a .profile in the user's home directory on the PATHWORKS for Digital UNIX server. For example, to create a .profile for suep, create a .profile in the /usr/net/servers/lanman/users/suep directory and enter the following: PATH=/usr/rbin export PATH echo "This account is for mail server only and is running a restricted shell." Tuning PATHWORKS NetWare Software This section describes how to specify the number of PATHWORKS NetWare connections. Specifying PATHWORKS NetWare Connections If your configuration includes more than 50 clients, or if you want to limit the number of users that can access your server, you must reset the max_connections parameter in the /usr/net/servers/netware/etc/NWConfig file. If PATHWORKS NetWare is running, send a message to PATHWORKS users and advise them that you plan to stop the server. Use the following syntax: C: SEND "message" /server_name /EVERYBODY For example: C: SEND "Server SHARK will be stopped in 30 minutes"/SHARK/EVERYBODY Then, follow directions below to reset the max_connections parameter: 1.Log into the server as root and activate sconsole. Enter: sconsole 2.From the Main Menu, select 2, Configuration. 3.From the Configuration Menu, select 1, Services Configuration. 4.From the Services Configuration Menu, select 1, File Services Configuration. 5.From the File Services Configuration Menu, select 1, File Services Parameters. 6.Follow directions at the bottom of the screen to modify the value for Maximum Connections. Enter the value you want. 7.Press r to return to the previous menu, and exit sconsole. 8.Restart PATHWORKS NetWare. Enter: /sbin/init.d/nw_srv restart The max_connections parameter is activated when PATHWORKS NetWare restarts. Setting Up and Tuning PATHWORKS Advanced Server and PATHWORKS NetWare Software This section describes how to: Set file and directory access for a PATHWORKS Advanced Server share and a PATHWORKS NetWare volume that map to the same Digital UNIX directory. Modify the network controllers that you selected during the installation procedure. Setting Up Shares and Volumes If you create a PATHWORKS Advanced Server share and a PATHWORKS NetWare volume that map to the same Digital UNIX directory, you must ensure directory and file compatibility for both PATHWORKS Advanced Server and PATHWORKS NetWare users. Note PATHWORKS for Digital UNIX supports concurrent file sharing between PATHWORKS Advanced Server and PATHWORKS NetWare software. However, during file opens, the PATHWORKS server views a client that has both PATHWORKS Advanced Server and PATHWORKS NetWare software on a single workstation as two clients. This may impact applications that open files on the client in DOS compatibility mode. To create a PATHWORKS Advanced Server and PATHWORKS NetWare volume: 1.Modify the default permissions that PATHWORKS NetWare sets for files and directories. These are defined in the /usr/net/servers/netware/etc/NWConfig file. NetWare users must have read access to files on the host system to read and write them. NetWare users cannot access files if they have only write access. By default, the PATHWORKS NetWare files are created with rw permission for file owners and no access for group and others. To provide access for other users, you must set the default protections that PATHWORKS NetWare uses. By default, permissions for directories are created with rwx permissions for owners and no access for group or others. To provide access for other users, you must set the default protections that PATHWORKS NetWare uses. To set PATHWORKS NetWare default protections for files and directories, edit the file_mask and dir_mask options in the /usr/net/servers/netware/etc/NWConfig file. For example, to set protections for files to rw for owners, and r for group and others, modify the NWConfig file as follows: file_mask = 0644 To set protections for directories to rwx for owners and to rx for group and others, enter the following: dir_mask = 0755 2.Use the sconsole utility to create the PATHWORKS NetWare file volume, as follows: a.Enter sconsole to display the sconsole Main Menu. b.From the Main Menu, select 2, Configuration. c.From the Configuration Menu, select 1, Services Configuration. d.From the Services Configuration Menu, select 1, File Services Configuration. e.From the File Services Menu, select 3, Add a Volume. f.Enter the volume name, namespace, and directory name. Choose a directory name that does not exist on the Digital UNIX server. This ensures that the directory you create is owned by PATHWORKS NetWare. See the PATHWORKS for DEC OSF/1 NetWare Server Administration Guide for additional information. 3.Exit sconsole to enter your changes. Enter e on any menu. 4.To activate your changes, stop and start the PATHWORKS NetWare server, as follows: a.Enter sconsole to display the sconsole Main Menu. b.From the Main Menu, select 1, Administration. c.From the Administration Menu, select 1, Startup/Shutdown NetWare. d.From the Startup/Shutdown Menu, select 5, Shutdown NetWare Server. e.After the server shuts down and you return to the Startup/Shutdown Menu, select 2, Start NetWare Server. 5.Change the permissions of the Digital UNIX directory where the NetWare volume is located. This allows users to access this directory. As root, log into the Digital UNIX system and enter the following: # chmod 777 directory_name 6.Use pwadmin to create the PATHWORKS Advanced Server share, mapped to the same directory as the PATHWORKS NetWare volume, as follows: a.Execute /usr/sbin/pwadmin. b.Log in as administrator. The effective user name must be administrator. c.Respond to the Successful Logon prompt. d.Tab to View in the menu bar. e.Press Enter. f.Select Shared Resources. g.Press Enter. h.Tab to Button Line, right arrow to AddShare followed by Enter or F11 a. i.Press Enter or Tab to OK followed by Enter or F11 o. j.At the Share a Directory with the Network screen: In the Sharename field, enter the name of the Share for the PATHWORKS Advanced Server Share. In the Path field, enter the path to the same directory that you used for the PATHWORKS NetWare Volume. k.Press Enter or Tab to OK followed by Enter or F11 o. By default, the PATHWORKS Advanced Server sets protections for files and directories to rw for owners, and to r for group and others. You can modify these values if you want, but you do not need to reset them to provide access for other users. After you set directory and file protections to ensure compatibility for PATHWORKS Advanced Server and PATHWORKS NetWare users, you can follow standard NetWare and Advanced Server procedures to complete other network setup tasks. For information about PATHWORKS NetWare refer to the PATHWORKS for DEC OSF/1 NetWare Utilities, FILER Utility, and to PATHWORKS for DEC OSF/1 NetWare Planning and Setup for additional information. For information about the PATHWORKS Advanced Server, refer to the PATHWORKS for Digital UNIX (Advanced Server) System Guide. Modifying Controller Information PATHWORKS for Digital UNIX provides you with two ways to modify the network controllers or WAN support parameters that you selected during the installation procedure. You can: Execute the /usr/sbin/pwsetup kernel and specify new controller information or WAN parameters. Edit the pathworks.ini file. This file contains parameters for PATHWORKS Advanced Server controllers. Re-Running pwsetup kernel To modify a controller or change WAN parameters, use pwsetup kernel as follows: 1.Make sure that you are logged into the root account. Then enter: /usr/sbin/netstat -i to display the network controllers available on your system. The display shows the name and type of network for each network controller. The name is displayed in the "Name" column. The type of network is displayed under the "Network" Column. This column shows Datalink networks with the letters DLI, TCP/IP networks with a numerical network address, and DECnet networks with the letters "OSI". For example: $ /usr/sbin/netstat -I Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll ln0 1500 DLI none 940109 0 180836 16 31319 ln0 1500 150.300.240 fish 940109 1 180836 16 31419 ln1 1500 150.300.254 fish_1 874106 1 190871 14 23419 ln0 1500 OSI none 91774 4 179966 12 23418 . . . 2.Identify the name of the controller that you want, then run the pwsetup kernel utility. Enter: /usr/sbin/pwsetup kernel 3.The /usr/sbin/pwsetup kernel checks the software installed on your system, and asks which the kind of server you want to configure. For example: Do you wish to configure the kernel for Advanced Server services [y/n]? y 4.Answer y or n to select the kind of server ( PATHWORKS Advanced Server or PATHWORKS NetWare) that you want. The /usr/sbin/pwsetup kernel utility displays an informational prompt about your selection and asks if you want to configure controllers. Answer y to continue configuration. For example: Configuring kernel for Advanced Server Transports ... Would you like to configure the controllers [y/n]? y 5.The system displays information about the controllers you have configured for the transports you use. Answer the system prompts to specify the controllers you want. Refer to Chapter 3, Configuring PATHWORKS on Digital UNIX, in this guide, for detailed information. 6.When your information is complete, the system returns you to the root prompt. Reboot the system if indicated. The next time PATHWORKS for Digital UNIX starts, it automatically activates your modifications. Editing the pathworks.ini Configuration File The /usr/net/servers/pathworks/pathworks.ini file contains the controller configuration information for the parameters you entered during the installation procedure, if you changed any of the default settings. You can add or modify controller information by editing the pathworks.ini file. To modify a PATHWORKS Advanced Server controller: 1.Edit the /usr/net/servers/pathworks/pathworks.ini file. 2.Search the file for the section of the controller you want. Locate the [pwipnet] section to specify a TCP/IP controller, the [pwdecnet] section to specify a DECnet controller, and the [pwdatalink] section to specify a NetBEUI controller. Type in the section name if it is not included in the file. 3.Enter the name of the controller you want. For example, the following pathworks.ini file section specifies TCP/IP controller ln1: . . . [pwipnet] controller=ln1 . . . A The PATHWORKS Configuration File The pathworks.ini file is a configuration file for the PATHWORKS for Digital UNIX server. The contents of this file, a collection of keywords and associated values, provides you with a way to configure PATHWORKS on your server. When you install PATHWORKS for Digital UNIX, default values are assigned to keywords in the pathworks.ini file. File Organization The pathworks.ini file is divided into six sections. Four sections configure network controllers and two configure PATHWORKS licensing software. Each section name appears in the file on a line by itself, above the set of keywords contained in that section. Section names are enclosed in brackets ([]). pathworks.ini File Sections Table A-1 describes pathworks.ini file sections: Table A-1: pathworks.ini File Sections Section Description [pwipnet] Contains keywords that specify a controller for the TCP/IP transport. Also enables Wide Area Network addressing using the lmhosts file, NBNS, and DNS. [pwdecnet] Contains keywords that specify a controller for the DECnet transport. [pwdatalink] Contains keywords that specify the controllers that you want to use with the NetBEUI-Datalink transport. [licenseserver] Contains keywords that configure license server software. License server software assigns and verifies client licenses, and provides you with a way to allocate and manage the client licenses on your network. [licenseregistrar] Contains keywords that configure license registrar software. The license registrar decides if a client can connect to the server based on the availability of client-based licenses, and also grants server-based licenses, when required. [pwserver] Contains keywords that enable PATHWORKS Advanced Server and PATHWORKS NetWare software to work together. File Syntax Within each section, the keywords are listed as follows: The name of each keyword is at the beginning of a line, followed by an equal sign and the value assigned to it: keyword=value Comments start with a semicolon (;). If a semicolon precedes a keyword on the line, that keyword is ignored. When a list of values is assigned to a keyword, the values are separated by commas: keyword=value,value,value... If a numeric value begins with 0 it is octal; if it begins with X it is hexadecimal; if it begins with a number from 1 to 9 it is decimal. When a keyword has no assigned value (nothing to the right of the equal sign), the value is 0 for a keyword that requires a number and null for a keyword that requires a character string. Sample pathworks.ini file The following example shows the syntax of a sample pathworks.ini file: [licenseserver] maxlogfilesize=2000000 lmfsync=1 datafilesync=1 clienttimeout=2 nwclienttimeout=5 logverbose=no versionlimit="+2.5" runserver=yes [licenseregistrar] maxlogfilesize=2000000 lmfsync=1 clienttimeout=2 nwclienttimeout=5 logverbose=no versionlimit="+2.5" [pwipnet] controller=ln0 uselmhosts=yes lmhostsfile=/usr/net/servers/pathworks/datafiles/lmhosts enablenbns=yes nbnsservaddr=130.200.240.34 enabledns=yes dnssubdomains=london.com,paris.com [pwdecnet] controller=ln1 [pwdatalink] controller=ln0,ln1,fza0,fza1,tra0 [pwserver] noslocks=no ...auditoptions=auditlogonlogoff Modifying the pathworks.ini File The pathworks.ini file is created automatically during PATHWORKS for Digital UNIX installation. However, you can add to and modify the file's contents to change PATHWORKS for Digital UNIX software defaults. You can modify the pathworks.ini file by: Using a text editor Using the pwiniconf utility Using the pwsetup kernel. Refer to Chapter 4, Server Setup and Tuning, in this guide, for additional information about the sections and keywords you can modify. Using the pwiniconf Utility The /usr/net/servers/pathworks/bin/pwiniconf utility provides a command line interface that enables you to modify the pathworks.ini file. The pwiniconf utility uses the following syntax: pwiniconf -s section,keyword=value [section,keyword=value]... Use the -s to set, or write the section, keywords, and value in the pathworks.ini file. Replace section with the name of the section, keyword with the name of the keyword, and value with the keywords new value. Use a space to separate more than one section,keyword=value argument. For example, the following command resets the value for data file synchronization to 120 minutes: pwiniconf -s licenseserver,datafilesync=120 pathworks.ini Keywords The following sections describe the keywords in each section of the pathworks.ini file. [pwipnet] Keywords lmhostsfile Specifies a location other than the default for the lmhosts file. A prototype lmhosts file resides in the directory. Default: /usr/net/servers/pathworks/datafiles/lmhosts uselmhosts Enables addressing using the lmhosts file. Default: no enablenbns Lets you enable NBNS such as WINS (Windows Internet Name Service) Default: no nbnsservaddr Specifies the TCP/IP address (XXX.XXX.XXX.XXX) of the NBNS server. enabledns Lets you enable Domain Name Service Default: no dnssubdomains Specifies a comma separated list of DNS subdomains. Values: 0 - 20 subdomains Default: None controller Specifies a comma-separated list of controllers for the TCP/IP transport. If your server has more than one controller configured, PATHWORKS Advanced Server software selects the first controller it locates, and uses this as the default when you run /usr/sbin/pwsetup kernel. If your server has only one controller, PATHWORKS for Digital UNIX automatically selects it for you when you run /usr/sbin/pwsetup kernel. [pwdecnet] Keywords controller Specifies a controller for the DECnet transport. If your server has more than one DECnet controller, use this keyword to specify the one that you want to use. If your server has only one controller, PATHWORKS for Digital UNIX automatically selects it for you when you run /usr/sbin/pwsetup kernel. [pwdatalink] Keywords controller Specifies all the controllers that you want to use with the NetBEUI transport. The PATHWORKS NetBEUI Driver subset provides support for Ethernet, FDDI, and Token Ring hardware. Unless you have more than one controller for the same hardware (for example, two FDDI controllers) PATHWORKS for Digital UNIX automatically locates and configures your controllers for you. Note that you cannot use NetBEUI on networks where two interfaces are bridged together causing the packets from one controller to loop to the other. If your system is configured this way, you must reconfigure it so that NetBEUI uses only one interface. [licenseserver] Keywords This section describes the keywords that configure the PATHWORKS for Digital UNIX license server. Refer to the Guide to Managing PATHWORKS Licenses for additional information about license server keywords. maxlogfilesize Specifies the size of the /usr/net/serverrs/pathworks/logs/pwicsrv.log and the /usr/net/servers/pathworks/logs/pwlicsrv.log~ log files. These files contain license server information. Possible values are: Minimum: 30720 bytes Maximum: unlimited bytes Default: 2,000,000 bytes lmfsync Sets the time of LMF synchronization. This is the time that both the license server and the license registrar check the LMF database to verify the total license counts for all products in the license server database. To set the lmfsync keyword, compute the number of minutes after midnight that you want synchronization to occur. For example, to set synchronization at 1:00 AM use a value of 60. The default value is 00:01:00 (12:01 AM). datafilesync Specifies how often the license server writes the data file. The data file contains the most recent server data, and is used in the event of a system crash. Possible values are: Minimum: 1 minute Maximum: 1 day Default: 1 minute clienttimeout Specifies the time the license server waits for a PATHWORKS Advanced Server client to respond to a server request. Possible values are: Minimum: 1 second Maximum: 60 seconds Default: 2 seconds nwclienttimeout Specifies the time the license server waits for a PATHWORKS NetWare client to respond to a server request. Possible values are: Minimum: 1 second Maximum: 60 seconds Default: 5 seconds logverbose Adds additional information to the license server log file. Possible values are: Yes: Record additional events No: Record only significant events versionlimit Specifies the number of subsequent software versions the license server uses if no licenses are available for the version requested. To specify an absolute version, enter the value of the major and minor release that you want. For example, a value of 6.2 causes the software to look for a major release up to and including version 6.0, and a minor release up to and including .2. To specify a relative version, use the plus sign (+) followed by a value for the major and minor releases you want. For example, a value of +1.3 specifies one major release beyond the requested version, and all minor releases up to and including .3. By default, the license server looks for licenses two major releases beyond the client request. runserver Specifies where the License Server will run. In most cases, you will want the license server to run on only one server within a PATHWORKS domain. You can prevent the license server from running on a system where it is installed by setting the runserver keyword to no. Then stop and start the server. As root, enter /sbin/init.d/lic_srv restart. [licenseregistrar] Keywords maxlogfilesize Specifies the size of the /usr/net/servers/pathworks/logs/pwlicreg.log and /usr/net/servers/pathworks/logs/pwlicreg.log~ files. These files contain license registrar log information. Possible values are: Minimum: 30720 bytes Maximum: unlimited bytes Default: 2,000,000 bytes lmfsync Sets the time of LMF synchronization. This is the time that both the license server and the license registrar check the LMF database to verify the total license counts for all products in the license server database. To set the lmfsync keyword, compute the number of minutes after midnight that you want synchronization to occur. For example, to set synchronization at 1:00 AM, use a value of 60. The default value is 00:01:00 (12:01 AM). clienttimeout Specifies the time the license registrar waits for a PATHWORKS Advanced Server client to respond to a server request. Possible values are: Minimum: 1 second Maximum: 60 seconds Default: 2 seconds nwclienttimeout Specifies the time the license registrar waits for a PATHWORKS NetWare client to respond to a server request. Possible values are: Minimum: 1 second Maximum: 60 seconds Default: 5 seconds logverbose Adds additional information to the license registrar log file. Possible values are: Yes: Record additional events No: Record only significant events versionlimit Specifies the number of subsequent software versions the License Registrar uses if no licenses are available for the version requested. To specify an absolute version, enter the value of the major and minor release that you want. For example, a value of 6.2 causes the software to look for a major release up to and including version 6.0, and a minor release up to and including 6.2. To specify a relative version, use the plus sign (+) followed by a value for the major and minor releases you want. For example, a value of +1.3 specifies one major release beyond the requested version, and all minor releases up to and including 6.3. By default, the License Registrar looks for licenses two major releases beyond the client request. [pwserver] Keywords noslocks Enables a server with PATHWORKS Advanced Server and PATHWORKS NetWare to share open file locking information. This keyword must be set to yes on configurations where PATHWORKS Advanced Server users access PATHWORKS NetWare data, or PATHWORKS NetWare users access PATHWORKS Advanced Server data. Configurations that do not require users to access data from more than one network operating system can optimize server performance by setting this keyword to no. However, if this keyword is set to no on a configuration with both PATHWORKS Advanced Server and PATHWORKS NetWare, file locking will not work and data files may become corrupted. If you change the value of a parameter that affects shared memory on a PATHWORKS for Digital UNIX server with noslocks set to yes, you must stop and start both the PATHWORKS Advanced Server and PATHWORKS NetWare. Values that affect shared memory are: the fs_shm_size parameter, in the /usr/net/servers/netware/etc/NWConfig file the maxclients parameter in the [server] section of the lanman.ini file the hashsize, maxvcperproc, or ustructs parameter in the [lmxserver] section of thelanman.ini file Possible values are: Yes: Share file locking information No: Do not share file locking information Default: Yes auditoptions Specifies the audit values for the server. Values: noaudit - turns all auditing for the server process off auditnochange - does not change anyauditing events for the server process. auditlogonlogoff - audits only Logon andLogout events for the server process. auditpreferred - audits Logon and Logoutevents if they weren't being audited, and turns off auditing of seteuid, setuid, and setygid system calls. Default: auditpreferred B The lmxupgrade Command The lmxupgrade command is used to upgrade a PATHWORKS for DEC OSF/1 system. You can execute lmxupgrade as part of the installation script or you can run it manually using the syntax below. The lmxupgrade command accepts the following arguments: lmxupgrade [-i file] [-YUGAynv] where: -i Identifies the input file. If there is no entry, the system uses the following file: /usr/net/servers/lanman/datafiles/acco unts.lm2. -Y Specifies that all users, groups, and access control entries should be upgraded and no routine questions are to be asked during the upgrade procedure. This option cannot be used with any other option except the -i and -v options. -U Specifies that users (-U), groups (- -A G), and access control entries (-A) -G are to be upgraded. Any combination of these flags is valid. If multiple flags are specified, groups are updated first, followed by users, and then access control entries. For example, if only users are specified, it is important that the groups were updated previously. Otherwise, group memberships for each user will not be preserved because the groups will not exist. The same is true for access control entries. If a group, user, or access privilege already exists, the lmxupgrade command will overwrite the existing information for that item with information from the input file. If the server being upgraded is a backup domain controller, only access control entries can be upgraded and therefore only the -A option can be specified. Before upgrading each user, group, or access control entry, the lmxupgrade command prompts you for the name of the object to be upgraded and asks you whether you want to upgrade the object. You can reply y to upgrade or n to skip the object. If you skip an object, any subsequent objects that are dependent on it may not upgrade correctly. For example, membership in a skipped group or an access control entry may not be upgraded correctly when a user has been skipped. -y Used in conjunction with the -U, -G, and -A options, this option specifies that each upgrade prompt will be automatically answered as y. This option provides a visible log of upgrade activity. -n Used in conjunction with the -U, -G, and -A options, this option specifies that each upgrade prompt will be automatically answered as n. This option provides a visible log of what would have been upgraded. No changes are made to the Advanced Server if this option is used. -v Specifies verbose output. The -v option displays additional information about upgrading users, groups, and access control entries. C Configuring the PATHWORKS Advanced Server Remote Boot Service This appendix describes how to: Remove the previous version of Remote Boot service. Configure the Remote Boot service on a new or upgraded server. Removing Remote Boot Service If you are removing PATHWORKS for DEC OSF/1 Version 5.0C or greater, the removal procedure provides you with a way to save and re-install Remote Boot configuration files. To save Remote Boot files, follow the standard removal procedure described in Chapter 1 of this guide. Answer y when you see the following prompt: Do you want to save the Remote Boot Configuration File? PATHWORKS for Digital UNIX saves Remote Boot configuration files for you. Saved files include DOS executables, workstation and profile information, remote boot configuration files, and server "update" files created on the client. The rpl.map and rplmgr.ini file are saved in the /usr/net/servers/lanman/rpl directory. The sav suffix appended to the file indicates the saved version (rpl.map.sav). When you re-install Remote Boot Service software, PATHWORKS automatically copies a new rpl.map and rplmgr.ini file into the /usr/net/servers/lanman/rpl directory. There are two exceptions to this: If you modified the boot block records of the rpl.map file, or made any changes to the rplmgr.ini file, you must add these changes into the new rpl.map and rplmgr.ini file before you run /usr/sbin/pwsetup configure. If you made no changes to these files, PATHWORKS for Digital UNIX automatically locates and reuses the files you saved when you run /usr/sbin/pwsetup remoteboot. If you upgrade PATHWORKS LAN Manager on a system where you have built your own bootsect.com file, you must recreate the bootsect.com file after installation. This is true even if you saved all the Remote Boot data that you used in the previous installation. PATHWORKS LAN Manager always installs a default bootsect.com file. This file overwrites any bootsect.com file that you built. The default bootsect.com file, installed by PATHWORKS LAN Manager, may cause Remote Boot clients to fail following installation. Setting Up Remote Boot Service Setting up the Remote Boot service is done at a workstation, using the Remote Boot Manager. To set up Remote Boot on a PATHWORKS Advanced Server that has remote boot configuration files saved, you need to complete only step 2 of the following procedure. All other required files are saved and reloaded during PATHWORKS for Digital UNIX installation. To set up remote boot on PATHWORKS Advanced Server, follow these steps: 1.Set up the Remote Boot service to start automatically, when the server starts. 2.Execute the Update Server option, on the Actions menu, to copy files from your client to the server. 3.Install each version of DOS that you plan to remote boot on the PATHWORKS for Digital UNIX server. 4.Complete the workstation configuration: a) Create the workstation profile b) Create a workstation record. c) Set up the workstation adapter for Remote Program Load (RPL) over Maintenance Operations Protocol (MOP) if you are configuring remote boot over MOP. Setting Up Remote Boot Service Over MOP If you set up your workstation to use RPL over MOP, you must have DECnet/OSI installed and running on your server. You must also run the /usr/net/servers/lanman/rpl/setrplmop utility after you complete the steps above. Workstations that have a DEPCA, EtherWORKS with MOP ROM, 3Com Etherlink II, or 3Com Etherlink/MC adapter use the MOP protocol. The setrplmop utility takes the set up information you created in Step 4c of the procedure outlined in the "Setting Up Remote Boot Service" section, and updates the server's DECnet database. To run setrplmop, log onto the server as root and enter: usr/net/servers/lanman/rpl/setrplmop Configuring DOS Workstations Previous to Version 4.01 Workstations using versions of DOS previous to Version 4.01 do not have support for extended memory (XMS). However, during configuration of a workstation profile for the Remote Boot service, PATHWORKS Advanced Server automatically references the extended memory driver file. This causes an error during workstation startup. To create a profile on a workstation without extended memory, follow the steps below to edit the CONFIG.SYS file and remove the reference to the driver file: 1.Edit the CONFIG.SYS file. 2.Search the file for the following line: device=c:\dos\himem.sys 3.Add a comment to the beginning of this line. For example: rem device=c:\dos\himem.sys Some versions of DOS may display an error at reboot. Ignore the error. It has no impact on how either PATHWORKS Advanced Server software or the DOS client operate. Workstations using non-Microsoft versions of DOS should check the CONFIG.SYS file to ensure that the reference to the extended memory driver file is correct. To check the reference to the extended memory driver file: 1.Edit the CONFIG.SYS file. 2.Search the file for the following line: device=c:\dos\himem.sys 3.Add a comment to the beginning of this line. For example: rem device=c:\dos\himem.sys 4.Add a new line, with the correct file name. The file name will vary, depending on the manufacturer and the version of DOS you are using. For example, if you are using a COMPAQ version of DOS, enter the following: device=c:\dos\himem.exe Additional Information Detailed information about Remote Boot configuration and management is provided in the PATHWORKS Remote Boot Guide, the workstation help files, and the workstation on-line tutorial. D Error Conditions This appendix describes the error conditions that can occur during installation and when you run the PATHWORKS for Digital UNIX Installation. Installation Error Messages Extraction Error Explanation: One or more PATHWORKS processes are still active during installation. User Action: Ensure that you have removed existing versions of the software and that no PATHWORKS services are running. Refer to Chapter 1, Preparing to Install PATHWORKS for Digital UNIX, in this guide, for additional information. Wrong Run Level Explanation: The system you are installing on is not in multi-user mode. User Action: Switch to multi-user mode, then begin installation. Incorrect Version of Operating System Explanation: The version of the operating system you are using is incompatible with the software. User Action: Install Digital UNIX version 4.0. Refer to Chapter 1, Preparing to Install PATHWORKS for Digital UNIX, in this guide, for additional information. Required Transport Not Installed Explanation: TCP/IP, DECnet, NetBEUI, or IPX/SPX is not installed on your system. User Action: Install the TCP/IP, DECnet, NetBEUI or IPX/SPX network transport. Refer to Chapter 2, Installing PATHWORKS for Digital UNIX, in this guide, for additional information. Required Subset Not Installed Explanation: You attempted to install a subset without first installing the prerequisite subsets. User Action: Refer to Chapter 1, Preparing to Install PATHWORKS for Digital UNIX, in this guide, for information about prerequisites. PATHWORKS for Digital UNIX Not Installed Explanation: PATHWORKS for Digital UNIX must be installed on your system before you can configure this subset. User Action: Install PATHWORKS for Digital UNIX. Refer to Chapter 2, Installing PATHWORKS for Digital UNIX, in this guide, for information about installation and configuration requirements. PATHWORKS for Digital UNIX Already Installed Explanation: A version of PATHWORKS for Digital UNIX is already installed on your system. User Action: Before you begin the installation procedure, remove the currently installed version of the server. For information about removing PATHWORKS for Digital UNIX, refer to Chapter 1, Preparing to Install PATHWORKS for Digital UNIX, in this guide. Software Subset Already Exists Explanation: A version of the software subset is already installed on your system. User Action: Before you begin the installation procedure, remove the subset that is installed on the server. For information about removing subsets, refer to Chapter 1, Preparing to Install PATHWORKS for Digital UNIX, in this guide. Not Enough Group Entries Available Explanation: For PATHWORKS Advanced Server software, indicates that the eight required group entries are not available. User Action: Edit the /etc/group file and reassign or delete at least three group IDs under 99. No Home Directory Created Explanation: During the installation procedure, the Digital UNIX system failed to create a home directory. The full path to the directory displays in an error message. User Action: After you complete the installation procedure, create this home directory. File Does Not Exist Explanation: The installation procedure failed to find a file it expected. User Action: Remove the server software and try to install it again. For information about removing PATHWORKS for Digital UNIX, see Chapter 2, Installing PATHWORKS for Digital UNIX, in this guide. File Not Unpacked Explanation: The installation procedure failed to unpack a file (the file name is displayed in an error message). User Action: After the installation procedure is completed, unpack the file manually. Cannot Create Administrative Login Explanation: Not enough administrative logins with IDs under 100 are available. User Action: Check the /etc/passwd file to see if any users have login IDs under 100. If so, reassign these users so that they have login IDs over 100. Login Not Added to /etc/passwd File Explanation: The installation procedure could not add a login ID to /etc/passwd; your password file may be corrupted or inaccessible because of protections.. User Action: After you complete the installation procedure, verify that the password file is formatted correctly. Refer to passwd (4) in the Digital UNIX Reference Manual for additional information. Special Login in Use Explanation: A user is using a special login ID that should not be available. User Action: Remove the user or reassign the user's login ID. If you reassign, use a value over 100 that is not assigned to another user. LP Spooler Cannot Restart Explanation: The installation procedure modified the Digital UNIX LP subsystem, and the system cannot restart the LP Spooler. User Action: After you complete the installation procedure, restart the LP Spooler. For information about restarting the LP Spooler, see Digital UNIX documentation for the LP command. Cannot Shut Down LP Spooler\no_lp_stop Explanation: The installation procedure did not finish because it failed to shut down the LP Spooler. One or both of the following conditions exist: You are installing the server, but you are not logged into the root account. Print jobs are queued. User Action: If you are not logged into the root account, logout of your present account, and then login to the root account and start the installation procedure again. If print jobs are queued, print or cancel the jobs to clear the queue, then start the installation procedure again. PATHWORKS Advanced Server Installation Verification (IVP) Errors If an error occurs during the PATHWORKS Advanced Server Installation Verification procedure, type net helpmsg with the error message number to display help. For example: # net helpmsg 2114 net 2114: The server service isn't started. EXPLANATION The specified server is not started. The server must be started before you run this command. ACTION Try the command again after the server has been started. If you need help, see your network administrator. Configuration Error Messages The following error messages may occur if your PATHWORKS Advanced Server is not configured correctly: A NET3055 error indicates that the PATHWORKS Advanced Server is not correctly configured. A NET3226 or SYS0154 error indicates a synchronization mismatch between the PATHWORKS Advanced Server backup server and the NT Advanced primary server. The account databases are synchronized correctly at the next interval, or when you enter the net accounts /sync command.