____________________________________________________ POLYCENTER Network Manager 400 Installation Guide Order Number: AA-R612A-TE Revision/Update Information: This is a new manual Operating System and Version: OpenVMS Alpha V7.1 Software Version: POLYCENTER Network Manager 400 Version 3.0 Digital Equipment Corporation ________________________________________________________________ The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. © Digital Equipment Corporation 1997. All Rights Reserved. The postpaid Reader's Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: AlphaGeneration, Alpha, DECnet, DECwindows, DIGITAL, OpenVMS, VMS, and the DIGITAL logo. DIGITAL The following are third-party trademarks: Motif, OSF, and OSF/Motif are trademarks of Open Software Foundation, Inc. ORACLE is is a registered trademark of Oracle corporation. PostScript is a registered trademark of Adobe Systems, Inc. This document was prepared using VAX DOCUMENT, Version 2.1. _________________________________________________________________ Contents Preface................................................... vii 1 Before Installing the DECmcc Enterprise Management Station Software 1.1 Overview......................................... 1-1 1.2 Meeting Software Requirements.................... 1-2 1.3 Meeting Hardware Requirements.................... 1-3 1.4 Registering the License for DECmcc EMS........... 1-3 1.5 Performing a System Backup....................... 1-4 1.6 Reading the Release Notes........................ 1-5 1.7 Time Required for Installation................... 1-5 1.8 Required System Privileges....................... 1-5 1.9 Required Disk Space.............................. 1-6 1.10 Required System Parameters....................... 1-7 1.10.1 DECmcc BMS System Parameter Settings .......... 1-7 1.10.2 Checking System Parameter Values .............. 1-7 1.10.3 Calculating the Values for GBLPAGES and GBLSECTIONS.................................... 1-7 1.10.4 Changing System Parameter Values with AUTOGEN........................................ 1-8 1.10.4.1 Setting Dynamic System Parameter Values..... 1-9 1.11 Required Process Quotas.......................... 1-9 1.11.1 DECmcc BMS Process Quota Settings ............. 1-10 1.11.2 How to Modify Process Quota Settings .......... 1-10 1.12 Preparing to Install DECmcc BMS.................. 1-11 1.12.1 Location of the BMS Files ..................... 1-11 1.12.2 Determining Your Time Differential Factor ..... 1-11 1.12.3 Choosing A Namespace .......................... 1-13 1.12.4 Obtaining Your Network Address Initial Domain Part........................................... 1-15 1.12.5 Installing the Unsupported DECmcc Reports Package........................................ 1-18 iii 2 Installing the DECmcc EMS Software 2.1 The Installation Procedure - Step by Step........ 2-1 2.2 Installing Specific Management Applications...... 2-10 2.2.1 Installing DECmcc BMS ......................... 2-11 2.2.2 Building the MIR Dictionary ................... 2-15 2.2.3 Building and Updating the Help Files .......... 2-16 2.2.4 Adding a Command to Your System Startup Command Procedure...................................... 2-18 2.3 Post-Installation Messages....................... 2-19 2.3.1 Post-Installation Messages for DECmcc BMS ..... 2-19 2.3.2 Post-Installation Messages for TCP/IP DA FM ... 2-20 2.3.3 Post-Installation Messages for DECmcc ELM AM .. 2-20 2.3.4 Post-Installation Messages for DECmcc ELM FM .. 2-21 2.4 Running the IVP.................................. 2-21 2.5 Completing the Installation...................... 2-21 2.6 Installation Errors.............................. 2-22 3 Verifying the Installation of the DECmcc EMS Software 3.1 Running the IVPs on Individual Applications...... 3-1 3.1.1 DECmcc BMS Installation Verification Procedure...................................... 3-2 3.1.2 TCP/IP DA FM IVP ............................. 3-4 3.1.3 DECmcc ELM AM IVP ............................. 3-5 3.1.4 DECmcc ELM FM Installation Verification Procedure...................................... 3-6 3.1.5 DECmcc EMS Installation Verification Completion..................................... 3-6 3.2 What to Do if the IVP Fails...................... 3-7 4 After Installing the DECmcc EMS Software 4.1 Editing the System Startup File.................. 4-1 4.1.1 DECmcc Startup Commands ....................... 4-2 4.1.2 Rebooting the System .......................... 4-2 4.2 Running an Application in the Cluster Environment...................................... 4-2 4.2.1 Running DECmcc BMS in a Cluster Environment ... 4-2 4.3 Setting User Account Privileges.................. 4-3 4.4 Setting User Account Quotas...................... 4-4 4.5 Enhancing DECmcc EMS Performance................. 4-4 4.5.1 Installing Shared Images ...................... 4-4 4.5.2 Tuning for Good Performance ................... 4-6 iv 4.5.3 Using the DECmcc System Audit Utility ......... 4-7 4.6 Troubleshooting and Reporting Problems........... 4-9 4.7 DECmcc BMS Post-Installation Procedures.......... 4-10 4.7.1 Setting Up the DNS Namespace .................. 4-10 4.7.2 Setting File Protection for DECmcc BMS Files .. 4-10 5 Using the Distributed Name Service with DECmcc 5.1 DNS Overview..................................... 5-2 5.2 DNS Components and Terminology................... 5-3 5.3 Structuring DNS Namespaces....................... 5-5 5.4 Planning to Set Up and Use DNS with DECmcc....... 5-7 5.5 Planning the DNS Directory Hierarchy for DECmcc.. 5-9 5.6 Planning and Creating DNS Access Control Groups.. 5-12 5.7 Setting Up the DNS Namespace..................... 5-15 5.7.1 Creating the DNS Directories Required for DECmcc......................................... 5-16 5.7.2 Creating the .DNA_Registrar Access Control Group.......................................... 5-17 5.7.3 Creating Additional DNS Directories ........... 5-19 5.7.4 Managing the .DNA_Registrar Access Control Group.......................................... 5-21 5.7.5 Creating a Procedure to Register DECnet Phase IV Nodes....................................... 5-22 5.7.6 Specifying Privileges for any Additional Access Control Groups................................. 5-25 5.8 Verifying DECmcc and DNS Interoperability........ 5-26 5.9 Troubleshooting the DNS Namespace................ 5-27 A Required Quotas and Parameter B Time Differential Factors (TDFs) C Updating DECmcc From a Previous Version C.1 Steps You Must Perform Before Upgrading to DECmcc V3.0............................................. C-1 C.2 Steps You Must Perform After Upgrading to DECmcc V3.0............................................. C-4 v Figures 5-1 Sample Configuration of DNS Clerks and Servers on a LAN....................................... 5-4 5-2 How a DNS Client, Clerk and Server Interact ... 5-5 5-3 Sample Namespace Directory Hierarchy .......... 5-7 Tables 1-1 Checking for Prerequisite Software ............ 1-3 1-2 Disk Space Requirements (in Blocks) ........... 1-6 1-3 Process Quota Values Required for Installing DECmcc BMS .................................... 1-10 1-4 IDP Parameter Values .......................... 1-15 1-5 Sample IDPs ................................... 1-17 3-1 Commands to Run the IVP for Individual Applications................................... 3-1 4-1 Management Application System Startup Command........................................ 4-2 4-2 Minimum Values of Required DECmcc EMS User Account Quota.................................. 4-4 4-3 DECmcc EMS Executable Image Name .............. 4-6 4-4 Process Quota Values .......................... 4-6 4-5 SYSGEN Parameter Values ....................... 4-7 4-6 DECmcc BMS File Protection .................... 4-11 A-1 Product Process Quotas ........................ A-1 A-2 Product SYSGEN Parameter ...................... A-2 B-1 Region: Europe ................................ B-2 B-2 Region: North America ......................... B-2 B-3 Region: Central and South America ............. B-4 B-4 Region: Africa ................................ B-6 B-5 Region: Asia .................................. B-6 B-6 Region: South Pacific ......................... B-7 B-7 Region: Antarctica ............................ B-7 vi _________________________________________________________________ Preface In this manual, POLYCENTER Network Manager 400 is referred to as the DECmcc Enterprise Management System (EMS), which includes the DECmcc Basic Management System (BMS). The POLYCENTER Framework and Applications are referred to as DECmcc. The DECmcc Basic Management System (previously called POLYCENTER Network Manager 200), is now bundled with the POLYCENTER Network Manager 400 kit, and is not available separately. All references to VMS in this manual pertain to the new product title, the OpenVMS Alpha operating system. This installation guide explains how to install the DECmcc EMS software on an Alpha system configured with the VMS operating system and Motif[R] software. This software includes the network management applications supported by DECmcc EMS. Intended Audience This guide isintended for the System Manager or Network Manager responsible for installing the DECmcc EMS software on an Alpha system. To use this guide effectively, you should be familiar with the VMS operating system and the VMSINSTAL Utility. vii Associated Documents The following documents are associated with this release of DECmcc EMS: o POLYCENTER Network Manager 400 Use Provides an overview of DECmcc EMS. o POLYCENTER Network Manager 400 Release Notes (online) This collection of notes contains information and updates not included in the POLYCENTER Network Manager 400 manuals. The release notes are delivered online as part of the software distribution kit. o POLYCENTER Framework and Applications Use Describes how to use the presentation modules (user interfaces) and the features of the DECmcc software. o POLYCENTER Framework and Applications DECnet Phase IV Access Module Use Describes how to use DECmcc to manage a DECnet Phase IV network. o POLYCENTER Framework and Applications DECnet/OSI Access Module Use Describes how to use DECmcc to manage a DECnet/OSI network. o POLYCENTER Framework and Applications TCP/IP SNMP Access Module Use Describes how to use DECmcc to manage TCP/IP hosts. o POLYCENTER Framework and Applications Ethernet Access Module Use Describes how to use DECmcc to manage Ethernet stations. o POLYCENTER Framework and Applications Script Access Module Use Describes how to execute scripts and integrate the output data into DECmcc as individual attributes. o POLYCENTER Framework and Applications Bridge Access Module Use Describes how to use DECmcc to manage LAN bridges. viii o POLYCENTER Framework and Applications DECconcentrator Access Module Use Describes how to use DECmcc to manage FDDI concentrators. o POLYCENTER Framework and Applications Circuit Access Module Use Describes how to use DECmcc to manage circuits. o POLYCENTER Framework and Applications Autoconfiguration and Autotopology Use Describes how to use the DECmcc Autoconfiguration and Autotopology modules. o POLYCENTER Framework and Applications Alarms and Notification Services Use Describes how to use the DECmcc Alarms and Notification Services modules. o POLYCENTER Framework and Applications Historical Data Services Use Describes how to use the DECmcc Historian and Exporter modules. o POLYCENTER Framework and Applications Performance Analyzer Function Module Use Describes how to make effective use of the DECmcc Performance Analyzer module. o POLYCENTER Framework and Applications TCP/IP Diagnostic Assistant FM Use Describes how to use DECmcc TCP/IP Diagnostic Assistant function module. o POLYCENTER Framework and Applications Reports Use Describes how to create reports from data stored by DECmcc. (Unsupported package). o POLYCENTER Framework and Applications Messages Describes all DECmcc management module messages for the various interfaces. o POLYCENTER Framework and Applications Master Index ix Combines all DECmcc Basic Management System document indexes. o POLYCENTER Framework and Applications System Reference Manual Describes the interfaces defined by the DECmcc architecture and provides details about the way they are used. o POLYCENTER Framework Management Module Programming Provides tutorial information about how to plan, design, implement, and test a DECmcc management module. o POLYCENTER Framework Developer's Toolkit Reference Describes the programming tools needed to enroll and test management modules. o Enterprise Management Architecture General Description Provides an overview of Digital's Enterprise Management Architecture (EMA). o Network Troubleshooting Guide (online version) Provides an overview of network troubleshooting tools and methodologies, and detailed troubleshooting procedures for specific network problems. The Bookreader (online) version of this manual will be on the media with the DECmcc Enterprise Management Station software. You can choose to install this book in your Bookreader library. Conventions Familiarizing yourself with the conventions discussed in this section will help you use this manual more effectively. ___________________________________________________________ Convention__Meaning________________________________________ Monospace Indicates system output or user input. x ___________________________________________________________ Convention__Meaning________________________________________ UPPERCASE In command lines, indicates keywords to be entered. Note that you can type the characters in either uppercase or lowercase. Command keywords can be abbreviated to the smallest number of characters that your system accepts. For example, the following two commands are the same: NCP> SHOW NODE node-name NCP> SH N node-name italics In command lines, indicates a variable to be entered. You enter an appropriate value for the variable. For example, node-name is a variable in the following command: NCP> SHOW NODE node-name [ ] In installation dialogs, indicates that the enclosed value is the default. To choose the default, just press RETURN. To choose another value, type it after the brackets and press RETURN. In command lines, indicates that you can enter one, and only one, of the enclosed options, but that none is required. Do not type the brackets when you enter the option. { } Indicates that you must enter one, and only one, of the enclosed options. Do not type the braces when you enter the option. Enter Means that after the user input you must press RETURN. CTRL-X Indicates that you should hold down the CTRL ____________key,_while_pressing_the_key_specified_by_x.____ xi 1 _________________________________________________________________ Before Installing the DECmcc Enterprise Management Station Software This chapter discusses the following requirements and preparations necessary for installing the DECmcc Enterprise Management Station (EMS) software and the applications that run under it: o Overview o Meeting Software Requirements o Meeting Hardware Requirements o Registering the License for DECmcc EMS o Performing a System Backup o Reading the Release Notes o Time Required for Installation o Required System Privileges o Required Disk Space o Required System Parameters o Required Process Quotas o Preparing to Install DECmcc 1.1 Overview This guide describes the step-by-step procedures that you must follow to install the DECmcc EMS package. To install the DECmcc EMS package, install the following applications: o DECmcc Basic Management System (BMS) V3.0 Before Installing the DECmcc Enterprise Management Station Software 1-1 o Additional DECmcc EMS Products - Extended LAN Manager (ELM) V3.0 - TCP/IP Diagnostic Assistant V3.0 1.2 Meeting Software Requirements This section lists the software that must be licensed, installed, and running on your system before you install and run DECmcc EMS: o VMS V7.1 operating system; you also need DECwindows Motif V1.2 (or later) software for workstations running Motif. o DECnet-Plus+ for OpenVMS Version V7.1 If you plan to use the unsupported BMS Performance Analyzer Function Module Reports Package, you need the following: o DATATRIEVE (DTR) o Oracle CDD/Plus (CDD) o Oracle Rdb/VMS (RDB) runtime must be installed on the target system to which data is exported using the Export FM. To verify the VMS software version, enter the following command: $ SHOW SYSTEM The VMS version number is displayed in the first line. To verify that the prerequisite software is installed and running, make sure that the appropriate processes, shown in Table 1-1, are running. ____________________ + Formerly known as DECnet/OSI. 1-2 Before Installing the DECmcc Enterprise Management Station Software Table_1-1_Checking_for_Prerequisite_Software_______________ Software____Look_For___________If_Not_Running,_Refer_To____ DECnet NETACP and REMACP DECnet/Alpha Installation Guide Rdb/VMS_____RDMON______________Rdb_Installation_Guide______ 1.3 Meeting Hardware Requirements The performance of the DECmcc EMS depends on a number of factors, including the following: o Host system CPU size o Other applications being run on the host system o Size of the network being monitored o Management application functions being invoked System tuning is the responsibility of the system manager. For information on system tuning, refer to the VMS System Management Subkit. The DECmcc EMS host system should not be a designated area router because designated area routers typically handle large amounts of traffic. If the host system were a designated area router, the management application would have to compete with DECnet for system resources and this could result in timeouts for the LAN. This is not a failure condition, but the performance of the network and the Ethernet application will suffer. The following sections describe hardware issues you need to consider before installing particular EMS applications. 1.4 Registering the License for DECmcc EMS To run DECmcc EMS software, you must register your software license with the VMS License Management Facility (LMF). To run DECmcc EMS software on a cluster, you must register the license on each node in the cluster. The license registration information you need is contained in the Product Authorization Key (PAK) that is shipped with DECmcc EMS. The PAK is a paper certificate that contains information about your license to run the software product. Before Installing the DECmcc Enterprise Management Station Software 1-3 It is best to register your DECmcc EMS license before you perform the installation. During the installation, you are asked if you have registered the DECmcc EMS license and loaded the appropriate authorization key. If you have not, you can still complete the installation; however, you will not be able to run the Installation Verification Procedure (IVP), the DECmcc EMS software, or any of the management applications. Once you perform the license registration and have loaded an authorization key, you will be able to run the startup procedures and use DECmcc EMS. To register a license, first log in to the system manager's account, SYSTEM. There are two ways you can perform the registration: o Start the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your PAK. o At the DCL prompt, issue the LICENSE REGISTER command with the corresponding qualifiers given in the PAK. For complete information on using LMF, refer to the VMS License Management Utility manual. 1.5 Performing a System Backup Before installing DECmcc EMS and its supported applications, it is a good idea to back up your system disk to ensure its integrity. Early in the installation procedure, VMSINSTAL asks whether you are satisfied with your system backup and gives you a chance to terminate the installation if you wish to do so. When performing an installation over an existing DECmcc installation, it is recommended that you backup all DECmcc software directories, for example, MCC_COMMON. 1-4 Before Installing the DECmcc Enterprise Management Station Software 1.6 Reading the Release Notes The distribution kit includes release notes, which contain information that is not in the documentation. It is recommended that you read this information before proceeding with the installation. The release notes for DECmcc EMS include notes about all the management applications in the package. You can display or print the release notes during product installation. Include OPTIONS N in the command that invokes VMSINSTAL, so that the installation procedure asks if you want to display or print the release notes. Refer to Chapter 2 for more information on the options for displaying and printing release notes. It is important to review the DECmcc EMS release notes before you continue with the installation, because they may contain information that affects the product installation. The DECmcc EMS package release notes contain release notes for the applications included in the package. VMSINSTAL copies the release notes to the text file SYS$HELP:MCCEMS030.RELEASE_NOTES. 1.7 Time Required for Installation The amount of time required for the DECmcc EMS installation depends on the type of media, system configuration, and DECmcc EMS package you are installing. The amount of time required for installation means the amount of time it takes VMSINSTAL to install the entire package; it is assumed that all pre-installation procedures have been completed. 1.8 Required System Privileges To install DECmcc EMS, one of the following must apply: You must be logged in to the system manager's account, SYSTEM, or to an account that has either of the following privileges: o SETPRV o CMKRNL, NETMBX, SYSPRV, TMPMBX, and WORLD Note that VMSINSTAL turns off the BYPASS privilege at the start of the installation. Before Installing the DECmcc Enterprise Management Station Software 1-5 1.9 Required Disk Space During the installation procedure DECmcc EMS requires a certain amount of free storage disk space. Once DECmcc EMS is installed, less storage space is required. Table 1-2 shows the storage requirements for each of the network management applications within DECmcc EMS and shows the total space required for the EMS package. Table_1-2_Disk_Space_Requirements_(in_Blocks)______________ Kit_____________________________During_Installation________ DECmcc BMS 180,000[1] ELM AM/FM 13,000 TCP/IP DA FM 7,000 Network Troubleshooting Guide 3,500 EMS Package Total 210,000 [1]If_you_place_the_common_files_on_a_disk_other_than_the__ system disk, and specify an Alternate Working Device (AWD), then you won't require this total amount on the system disk. ___________________________________________________________ ________________________ Note ________________________ The total number of blocks may be less after installation, depending on the other layered products you have installed on your system. ______________________________________________________ These figures refer to the disk space required on the system disk and are approximations; actual sizes can vary, depending on the system environment, configuration, and software options selected. To determine the number of free disk blocks on the current system disk, enter the following command at the DCL prompt: $ SHOW DEVICE SYS$SYSDEVICE 1-6 Before Installing the DECmcc Enterprise Management Station Software 1.10 Required System Parameters This section lists the minimum required system parameter values for installing and using DECmcc EMS and its management applications. The default values are sufficient for those parameters not specifically listed. Depending on the types of programs and applications running at your site, you might need higher values for some settings. 1.10.1 DECmcc BMS System Parameter Settings The minimum value for the GBLPAGES system parameter required for installing and using DECmcc BMS is 7,250 global page table entries. 1.10.2 Checking System Parameter Values To check the values of your system parameters, enter the following command at the DCL prompt to start the System Generation Utility (SYSGEN): $ RUN SYS$SYSTEM:SYSGEN SYSGEN> At the SYSGEN> prompt, enter the SHOW command to display the value of a system parameter. The values displayed should equal or exceed the value of each system parameter listed in the previous sections. The following example displays the value for the SRPCOUNT system parameter: SYSGEN> SHOW SRPCOUNT Compare the system parameter settings with those required by each network management application that you will install. Note which system parameters must be modified. After checking the parameters with the SHOW command, enter the EXIT command at the SYSGEN> prompt to return to DCL level. 1.10.3 Calculating the Values for GBLPAGES and GBLSECTIONS You must have sufficient free global pages and global sections for all of the applications that you plan to install and run with DECmcc EMS. You must first find out how many free global pages and sections you have on your system. Then use AUTOGEN if you need to increase the GBLPAGES and GBLSECTIONS system parameters. Before Installing the DECmcc Enterprise Management Station Software 1-7 You can use the WRITE command with the F$GETSYI lexical function to find the number of free global pages and global sections. The following example shows how to get this information at your terminal (the default for SYS$OUTPUT): $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") 15848 $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") 24 If the values displayed by the system are greater than the required values, you do not need to increase the values for these parameters. If the value of free global pages or global sections is less than the required value, you must increase the system parameter setting. Section 1.10.4 describes the procedures for increasing these values by using AUTOGEN. 1.10.4 Changing System Parameter Values with AUTOGEN Use the AUTOGEN command procedure to change system parameters. AUTOGEN automatically adjusts values for parameters that are associated with the values you reset manually. To change system parameters with AUTOGEN, edit the following file: SYS$SYSTEM:MODPARAMS.DAT Use an editor to access the file. To change a parameter value listed in this file, delete the current value associated with that parameter and enter the new value. To add a new parameter, add a line to the file that includes both the name of the parameter and its value. For example: SRPCOUNT = 4096 To modify incremental parameters such as GBLPAGES and GBLSECTS, use ADD. The following example increases the global page setting by 2000: ADD_GBLPAGES = 2000 When you set the page file quota, do not use a value that exceeds the amount of page file space available on the system. 1-8 Before Installing the DECmcc Enterprise Management Station Software After you make all your changes, exit from the editor and execute the AUTOGEN procedure to recalculate your system parameters. Enter the following command at the DCL prompt: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT When you specify REBOOT, AUTOGEN performs an automatic system shutdown and then reboots the system. Any users logged on to the system are immediately disconnected during the shutdown. The automatic reboot puts the new parameter values into effect. The AUTOGEN Utility automatically adjusts some of the SYSGEN parameters based on the consumption of resources since the last reboot. If you do not want to take advantage of this automatic adjustment, include the NOFEEDBACK qualifier on the AUTOGEN command line. For more information about using AUTOGEN, refer to the VMS System Management Subkit. 1.10.4.1 Setting Dynamic System Parameter Values Use the System Generation Utility (SYSGEN) to set dynamic parameters. Dynamic parameters changed with the SYSGEN WRITE ACTIVE command become active immediately without any need to reboot your system. In fact, rebooting returns dynamic system parameter values to their previous settings. Once you change dynamic parameter values, you should complete the installation before rebooting the system. 1.11 Required Process Quotas This section lists the minimum required process quota values for installing and using DECmcc EMS and its management applications. The default values are sufficient for those quotas not specifically listed. Depending on the types of programs and applications running at your site, you may need higher values for some settings. Refer to Section 1.11.1 for information on modifying the settings. Before Installing the DECmcc Enterprise Management Station Software 1-9 1.11.1 DECmcc BMS Process Quota Settings Table 1-3 lists the process quotas and their required values for installing DECmcc BMS. Note that the values indicated in Table 1-3 are DECmcc BMS requirements only. If you choose to use the DNS namespace, check the VAX Distributed Name Service Installation Guide for VAX DNS requirements. Table 1-3 Process Quota Values Required for Installing __________DECmcc_BMS_______________________________________ Process_Quota_______Value__________Unit____________________ ASTlm 200 ASTs BIOlm 100 Buffered I/O operations Bytlm 65,000 Bytes DIOlm 100 Direct I/O operations Enqlm 2,000 Blocks Fillm 400 Number of Files Pgflquota 150,000 Pages PRclm 20 Subprocess creations TQElm 300 Entries in queue WSextent 16,000 Pages WSquota_____________4,096__________Pages___________________ 1.11.2 How to Modify Process Quota Settings This section gives some examples of how to show the current process quota settings and how to modify them. Before modifying process quotas, you should understand how they are used by VMS and you should know how to use the VMS tools to modify settings. For more information, refer to the VMS System Management Subkit. The following procedure is an example of how you can determine the current process quota values and modify them to satisfy the requirements listed in the previous sections (you must have system manager privileges before you begin): 1. To verify that your process quotas are set correctly, enter the following commands: 1-10 Before Installing the DECmcc Enterprise Management Station Software $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> SHOW account-name This command shows your process quota settings. 2. To change a quota, use the MODIFY command, which has the following format: UAF> MODIFY account-name / quota-name=nnnn The following example changes the ASTlm quota for the SYSTEM account: UAF> MODIFY SYSTEM /ASTLM=200 3. To exit from the Authorize utility, enter EXIT and press RETURN. After you exit from the utility, messages will indicate whether changes have been made. Once the changes have been made, you must log out and log in again for the new quotas to take effect. 1.12 Preparing to Install DECmcc BMS This section contains information specific to DECmcc BMS installation. 1.12.1 Location of the BMS Files The DECmcc BMS command files are created in a directory called SYS$COMMON:[MCC]. The DECmcc BMS installation procedure gives you the option of defining (or redefining) the directory name, or leaving it as the default name, SYS$COMMON:[MCC]. 1.12.2 Determining Your Time Differential Factor If your system is not running DIGITAL Distributed Time Services (DECdts), the installation procedure will ask you to enter your Time Differential Factor (TDF). The TDF is the time difference between your time zone and Coordinated Universal Time (UTC). Your TDF is the constant (a fixed number of hours and minutes used to determine the local time. DECmcc calculates the local time by adding the TDF to the UTC. The UTC (formerly GMT, Greenwich Mean Time) is centered in Greenwich, England. Before Installing the DECmcc Enterprise Management Station Software 1-11 By defining your TDF as a logical name, DECmcc makes it very easy to change your local time, if you change during the spring or summer and change back in the fall or winter. For each time change, just redefine the logical name MCC_ TDF in the file SYS$STARTUP:MCC_LOGICAL_DIR.COM, then re-execute the DECmcc startup procedure SYS$STARTUP:MCC_ STARTUP_DIR.COM. If DECdts is running on your system, it supplies the default TDF for DECmcc. The installation procedure uses the DECdts TDF to define MCC_TDF. You can setup DECdts to automatically change from standard to daylight time, if you wish. Refer to DECdts Management for information on how to use DECdts. If your system does not have DECdts, the installation procedure asks you to supply a TDF. If you have previously installed DECmcc on your system, the installation procedure displays the current value of MCC_TDF as the default for your selection. If you do not have DECmcc on your system, but you do have a DNS server, the installation procedure uses the DNS TDF as the default. If the TDF is undefined on your system, the installation procedure uses -5:00 as the default. ________________________ Note ________________________ If you are using the DNS as your namespace, the DECmcc TDF must match the DNS TDF; otherwise, namespace access problems can occur. In some cases, the installation procedure may not be able to determine the DNS TDF, even if there is a DNS server on the system. In those cases, the installation procedure displays a warning message. ______________________________________________________ To calculate your TDF, determine what time zone you are in and calculate the difference between your time zone and the UTC. The range is from -12:00 to +13:00. A negative (-) TDF value means that you are located west of Greenwich, England. A positive (+) TDF means that you are located east of Greenwich, England. The format is +hh:mm or -hh:mm, where hh indicates the number of hours and mm indicates the number of minutes. Examples of different TDFs are as follows: 1-12 Before Installing the DECmcc Enterprise Management Station Software o California (Pacific Standard Time) is -8:00 hours from UTC. o Oklahoma (Central Standard Time) is -6:00 hours from UTC. o New York (Eastern Standard Time) is -5:00 hours from UTC. o New York (Eastern Daylight Time) is -4:00 hours from UTC. o Ontario, west of longitude W.63 degrees is -5:00 hours from UTC. o Ontario, east of longitude W.63 degrees is -4:00 hours from UTC. o Newfoundland is -3:30 hours from UTC. o Great Britain, Iceland, Portugal, Upper Volta are at UTC, or 0:0. o Great Britain (Summer Time) is +1:00 hour from UTC. o Greece is +2:00 hours from UTC. o India is +5:30 hours from UTC. o Singapore is +7:30 hours from UTC. o Japan is +9:00 hours from UTC. o Australia Capital Territory is +10:00 hours from UTC. ________________________ Note ________________________ For a more complete list of TDFs, refer to Appendix B. ______________________________________________________ 1.12.3 Choosing A Namespace DECmcc requires a namespace service for the storage of network entity information. The installation procedure allows you to select a local namespace or a distributed namespace (DNS). Namespace information includes global entity registered names and other identifiers (for example, device addresses, child entity identifiers, reference attributes, domain names, and domain members.) The namespace, whether local or Before Installing the DECmcc Enterprise Management Station Software 1-13 distributed, is part of the DECmcc Management Information Repository (MIR). You should select DNS, if you have multiple DECmcc systems that need to share namespace information. You should also select DNS if you are running DECnet/OSI and are using its distributed namespace service. Otherwise you should select the local namespace. The default is the local namespace, unless you previously used DNS for DECmcc. For DECnet/OSI, DNS is the DIGITAL Distributed Name Service (DECdns); for earlier versions of DECnet, DNS is the VAX Distributed Name Service V1.1 or later. If you are running the DIGITAL Distributed File Services (DFS) or the Remote System Manager (RMS), a DNS namespace already exists. To use DNS with DECmcc, it is important to plan and configure the DNS namespace according to the instructions in Chapter 5, and run the DNS Setup procedure described in Chapter 5. It is also important to plan your namespace before populating it, if you choose the local namespace and intend to use the DECmcc DECnet Phase IV Autoconfiguration or IP Autoconfiguration applications. The Autoconfiguration applications use two-level, hierarchical names for the entities they register. The manual POLYCENTER Framework and Applications Autoconfiguration and Autotopology Use contains instructions on planning entity names that apply to both the local namespace and DNS. Chapter 5 of this manual presents the same instructions from the point of view of the DNS user. The installation procedure creates the logical name MCC_ DNS_SELECTION. Its value is MIR for the local namespace, or DNS for the distributed namespace. After installation you can change namespaces by redefining this logical. Before redefining the logical, you should extract the entity instance data to a file so that you can insert it into the new namespace. The DECmcc directives that are namespace specific are Register, Deregister, and Directory. 1-14 Before Installing the DECmcc Enterprise Management Station Software 1.12.4 Obtaining Your Network Address Initial Domain Part If your network is or will be connected with other OSI networks, you must obtain a network address Initial Domain Part (IDP) from one of the recognized allocation authorities such as Consultative Committee for International Telephony and Telegraphy (CCITT). The installation procedure asks you for your network address IDP. The format of a network address IDP is AFI:IDI:, where: o AFI is the Authority and Format Identifier. This is two decimal digits indicating the IDP allocation authority. o IDI is the Initial Domain Identifier. This is a string of decimal digits that the allocation authority allocates specifically for your network. If your network will never be interconnected with other OSI networks, you can use the default value of "49". If you are not sure whether your network will be interconnected with other OSI networks in the future, Digital Equipment Corporation highly recommends that you obtain an IDP from one of the recognized allocation authorities. Refer to Table 1-4 for IDP parameter values and to Table 1-5 for sample IDPs. Table_1-4_IDP_Parameter_Values_____________________________ Number of Allocation Value of Digits in Selection for Authority_______AFI________the_IDI[1]____Leading_IDI_Digit_ X.121 37 0 to 14 1 to 9 53 0 to 14 0, 2 to 9 F.69 41 0 to 8 1 to 9 55 [2] 0 to 8 0, 2 to 9 E.163 43 0 to 12 1 to 9 57 [2] 0 to 12 0, 2 to 9 [1]Digits_in_the_IDI_must_be_decimal_(0_to_9)______________ [2]Value when padded (continued on next page) Before Installing the DECmcc Enterprise Management Station Software 1-15 Table_1-4_(Cont.)_IDP_Parameter_Values_____________________ Number of Allocation Value of Digits in Selection for Authority_______AFI________the_IDI[1]____Leading_IDI_Digit_ E.164 45 0 to 15 1 to 9 59 [2] 0 to 15 0, 2 to 9 ISO DCC 39 3 (exactly) 0 to 9 ISO 6523 - ICD 47 4 (exactly) 0 to 9 Private 49 0 N/A network [1]Digits_in_the_IDI_must_be_decimal_(0_to_9)______________ [2]Value when padded ___________________________________________________________ You can obtain your IDP using one of the following two methods: 1. Use an AFI that refers to a telecommunications authority and construct the IDI part by using a number already allocated for that type of telecommunication. Register this IDI value with the appropriate authority. o X.121 is the CCITT numbering plan for X.21 and X.25 networks. Construct the IDI from a DTE number you are using. o F.69 is the CCITT numbering plan for the telex network. Construct the IDI from the TELEX number you are using. o E.163 is the CCITT numbering plan for the telephone network. Construct the IDI from a POTS (telephone network) number you are using. o E.164 is the CCITT numbering plan for ISDN networks. Construct the IDI from an ISDN number you are using. 2. Go to an ISO (International Standards Organization) geographic or non-geographic IDP allocation authority and ask for a unique IDI. Geographic is for national organizations or networks; non-geographic is for 1-16 Before Installing the DECmcc Enterprise Management Station Software international organizations such as the UN, the Red Cross, and others. o ISO Geographic, an ISO-defined scheme that allows a country to assign addressing domains independently of public networks according to geographic locations. o ISO Non-geographic, an ISO-defined scheme that allows international organizations to assign domains that do not imply the location of systems within the domain. In the United States, you can call the IDP registrar of the American National Standards Institute (ANSI), at 212-398-0023. Table_1-5_Sample_IDPs______________________________________ If the Authority is:_________Then_the_IDP_will_look_like:___________________ X.121 (37 The IDI consists of the globally unique address or 53) prefix, identifying the Data Network and the Private Network (the company using the address), and one or more addresses within that Private Network. o Address prefix identifying the company's subnetwork is 8107654 o Address within the company's subnetwork is 1234 o Resulting X.121 address is 81076541234 o Used as an IDP, the value is 37:81076541234: (continued on next page) Before Installing the DECmcc Enterprise Management Station Software 1-17 Table_1-5_(Cont.)_Sample_IDPs______________________________ If the Authority is:_________Then_the_IDP_will_look_like:___________________ F.69 (41 The IDI consists of a country-specific or a or 55) network-specific number as defined by CCITT F.69 recommendation, plus the local telex local number. Note that some telex numbers do not conform to the CCITT F.69 recommendation, and should not be used. o Country or network number is 45 (Switzerland) o Local telex number is 43 61 92 o Resulting F.69 number is 45 43 61 92 o Used as an IDP, the value is 41:45436192: E.163 (43 The IDI consists of the world zone number, or 57) country or geographic area number, and local number. o World zone number is 1 (USA) o Geographic area number is 508 (MA) o Local number is 494-5892 o Resulting E.163 address is 15084945892 o Used as an IDP, the value is 43:15084945892: ___________________________________________________________ 1.12.5 Installing the Unsupported DECmcc Reports Package The DECmcc BMS installation procedure gives you the option of installing the DECmcc Reports package. The Reports package allows you to use DATATRIEVE to create reports with data exported to an Rdb/VMS (RDB) database from DECmcc. Refer to the DECmcc POLYCENTER Framework and Applications PerformanceAnalyzer FM Use manual for information on using DECmcc Reports with DATATRIEVE. 1-18 Before Installing the DECmcc Enterprise Management Station Software Before you can use the Reports package, you must also install the following VMS layered products: o ORACLE CDD/Plus o DATATRIEVE o ORACLE Rdb/VMS Together, these products require about 50K blocks of storage. Refer to the installation manuals for these products for information on their installation requirements. If you choose to install DECmcc Reports, please make sure you have all the licenses required for these products. Also, when you are installing DECmcc on a system where these products are present, you may have to adjust your process quotas and SYSGEN parameters. Refer to Appendix A for additional information. Install the products in the following order: o Install ORACLE Rdb/VMS o Execute the SYS$STARTUP:RMONSTOP command procedure o Install ORACLE CDD/Plus o Install DATATRIEVE If you choose to install the unsupported Reports Package, the installation procedure asks you to specify a directory for the files. If you selected the default directory for DECmcc common files, the default subdirectory location for the Reports files is: SYS$COMMON:[MCC_MCC_REPORTS_FILES]. Before Installing the DECmcc Enterprise Management Station Software 1-19 2 _________________________________________________________________ Installing the DECmcc EMS Software This chapter describes how to install the DECmcc EMS software and the management applications it supports. You can install the entire DECmcc EMS package or you can select individual management applications in the DECmcc EMS package to install. The detailed procedure described here includes information on installing each management application. Section 2.1 contains a step-by-step description of the installation procedure. ________________________ Note ________________________ In order to ensure correct installation of the other management applications, BMS needs to be installed. If you have not yet installed BMS, you can do so as part of the installation procedure, as explained in the following step by step instructions. Alternatively, if you have already installed BMS, you need to run the BMS startup procedure SYS$STARTUP:MCC_STARTUP_BMS.COM before you begin the installation procedure. ______________________________________________________ 2.1 The Installation Procedure - Step by Step The installation dialog consists of a series of questions and informational messages. To terminate the installation procedure at any time, press CTRL-Y. The installation procedure deletes all files it has created up to that point and exits. You can then start the installation again. Installing the DECmcc EMS Software 2-1 Each question in the installation starts with an asterisk (*). Some questions show the default response in brackets; for example [YES]. If you want to give the default response, press RETURN. The following is a step-by-step discussion of the installation procedure. 1. Ensure that there are no DECmcc processes or event sinks running. All users must have exited from DECmcc before you install. To ensure that there are no DECmcc event sinks are running, use the following commands: MCC> DISABLE MCC 0 COLLECTION_AM SINK DECNET MCC> DISABLE MCC 0 DNA5 SINK MCC> DISABLE NODE4 0 LOCAL SINK MONITOR 2-2 Installing the DECmcc EMS Software 2. Invoke VMSINSTAL. To start the installation, invoke the VMSINSTAL command procedure from a privileged account, such as the SYSTEM account. VMSINSTAL is in the SYS$UPDATE directory. $ @SYS$UPDATE:VMSINSTAL saveset-name device-name- _$OPTIONS N,AWD=disk:[directory] The following list defines the elements of the VMSINSTAL command procedure: saveset-name The installation name for the component. For DECmcc Enterprise Management Station (EMS), use the following installation name: MCCEMS030 device-name The name of the device on which you plan to mount the media. For example, MUA0: is the device name for a tape drive. It is not necessary to use the console drive for this installation. However, if you do use the console drive, you should replace any media you removed once the installation is complete. OPTIONS N An optional parameter that indicates you want to be prompted to display or print the release notes. If you do not include the OPTIONS N parameter, VMSINSTAL does not ask you about the release notes. You should review the release notes before proceeding with the installation in case they contain additional information about the installation. If you are restarting the installation and have already reviewed the release notes, you do not need to specify OPTIONS N. AWD=disk:[directory] Installing the DECmcc EMS Software 2-3 Alternate working device (AWD) option: An optional parameter that lets you specify an alternate working device for the temporary working directory, thus enabling you to perform an installation with fewer free blocks on the system disk than is otherwise required. ________________________ Note ________________________ Be sure you do not leave a blank space between OPTIONS N and the AWD option. The command should be: OPTIONS N,AWD=disk:[directory]. ______________________________________________________ Other Options Note that there are several other options you can select when you invoke VMSINSTAL: o Auto_answer option (A): Initially creates a file that contains your answers to VMSINSTAL questions and prompts. You can then use the option (and the answer file) to save time during a reinstallation (typically after upgrading your system). o Get save set option (G): Lets you store product save sets temporarily on a magnetic tape or in a disk directory. o File log option (L): Logs all activity on the terminal during installation. Refer to the VMS documentation on software installation in the VMS System Management Subkit for detailed information on these options. If you specify more than one option, separate the options with commas (OPTIONS A, N). The following example invokes VMSINSTAL to install DECmcc EMS from tape drive MUA0: and displays the system response. This example uses the OPTIONS N release note parameter, and uses DUA2:[INSTALL] for the AWD parameter. 2-4 Installing the DECmcc EMS Software $ @SYS$UPDATE:VMSINSTAL MCCEMS030 _$ MUA0: OPTIONS N,AWD=DUA2:[INSTALL] It is 24-JUL-1996 at 15:56. Enter a question mark (?) at any time for help. If you do not supply either the product name or the device name, VMSINSTAL prompts you for this information in the installation procedure. VMSINSTAL does not prompt you for any options, so be sure to include OPTIONS N on the VMSINSTAL command line to access the release notes during the installation. 3. Confirm system backup. VMSINSTAL asks if you are satisfied with your system backup. * Are you satisfied with the backup of your system disk [YES]? You should always back up your system disk and DECmcc directories before performing an installation, especially if this is an update installation. If you are satisfied with the backup of your system disk, press RETURN. Otherwise, enter NO and press RETURN to discontinue the installation. After you back up your system disk, you can restart the installation. 4. Mount the media. VMSINSTAL identifies the device name on which the distribution volume is to be mounted and asks if you are ready to continue with the installation. Please mount the first volume of the set on MUA0: * Are you ready? You should now mount the first distribution volume on the device you specified when you invoked VMSINSTAL. If you entered the wrong device name when you invoked VMSINSTAL and need to restart the installation, enter NO and press RETURN in response to the prompt. Enter YES and press RETURN to indicate that you are ready. VMSINSTAL displays a message that the media containing the DECmcc Enterprise Management Station has been mounted on the specified device and that the installation has begun. Installing the DECmcc EMS Software 2-5 %MOUNT-I-MOUNTED, MCCEMS030 MOUNTED ON $MUA0: The following products will be processed: MCCEMS V3.0-000 Beginning installation of MCCEMS V3.0-000 at hh:mm %VMSINSTAL-I-RESTORE, Restoring product saveset A... * Where will the distribution volumes be mounted: MUA0: Enter the products to be processed from the first distribution volume set. * Products: MCCEMS030 The following products will be processed: MCCEMS V3.0-000 5. Select a release notes option. If you specified OPTIONS N when you invoked VMSINSTAL, you are now given four options for reviewing the release notes. Release notes included with this kit are always copied to SYS$HELP as indicated by the installation message. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: 2 * Queue name [SYS$PRINT]: If you select option 1, VMSINSTAL displays the release notes immediately on the terminal. Note that these release notes are quite lengthy. You can terminate the display at any time and return to the installation by pressing CTRL-C. If you select option 2, VMSINSTAL prompts you for the name of the print queue that you want to use: * Queue name [SYS$PRINT]: You can enter a queue name or press RETURN to send the file to the default output print device. 2-6 Installing the DECmcc EMS Software If you select option 3, VMSINSTAL displays the release notes immediately on the terminal. Note that these release notes are quite lengthy. It then prompts you for the name of the print queue for the printed version. If you select option 4, VMSINSTAL does not display or print the release notes; however, it does automatically copy them to SYS$HELP. 6. Continue the installation. VMSINSTAL now asks if you want to continue the installation. * Do you want to continue the installation [NO]? To continue, enter YES and press RETURN. Otherwise, press RETURN to answer NO. In either case, the release notes are copied to SYS$HELP. If you are running VMSINSTAL just to get the release notes, press RETURN to terminate the installation. If you continue, VMSINSTAL displays the following messages: %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. ************************************************************ * * * DECmcc EMS V3.0-000 * * Integrated Package * * * * Installation Procedure * * * ************************************************************ The DECmcc EMS release notes are copied to: EMS - SYS$HELP:MCCEMS030.RELEASE_NOTES 7. Confirm registration of the software license. If you entered YES in Step 6 to continue the installation, the installation procedure displays information about the particular license, then asks whether the authorization key has been registered and loaded. Installing the DECmcc EMS Software 2-7 Product: DECMCC-EMS-ALPHA Producer: DEC Version: Release Date: * Does this product have an authorization key registered and loaded? If you have registered and loaded the authorization key, enter YES and press RETURN. If you have not registered and loaded your authorization key, you must answer NO to this question. You will be able to install DECmcc EMS but you will not be able to run the Installation Verification Procedure (IVP) or use the software until you register and load the authorization key. For more information about registering the software license, refer to Section 1.4. 8. Purge files. VMSINSTAL now asks whether it should purge files that are superseded by this installation. * Do you want to purge files replaced by this installation [YES]? If you press RETURN to answer YES to this question, VMSINSTAL purges files from previous versions of DECmcc EMS and previous versions of the management applications. VMSINSTAL will prompt you later in the installation procedure about purging or retaining these database files. Purging is recommended; however, if you need to keep files from the previous version of DECmcc EMS or any of the management applications, enter NO and press RETURN in response to the question. 9. Choose the Installation Verification Procedure option. VMSINSTAL asks if you want to run the DECmcc EMS IVP automatically after the end of the installation. The IVP ensures that the product is installed successfully. * Do you want to run the DECmcc EMS IVP after the installation [YES]? 2-8 Installing the DECmcc EMS Software Press RETURN to run the IVP immediately after the installation. If you did not register and load the PAK for the DECmcc EMS, the installation procedure will not run the IVP. Refer to Chapter 3 for more information on the IVP. 10.Install the DECmcc EMS applications. VMSINSTAL asks whether you want to install all the applications you have selected. * Do you want to install the entire EMS product set [YES]? Press RETURN to answer YES and to install all the applications in the DECmcc EMS package. If you answer NO, you can choose to install particular applications by responding to the following prompts. ________________________ Note ________________________ BMS installation is required in order to ensure correct installation of the other applications. Therefore, if you answer NO to the previous question and you have not yet installed BMS, you must answer YES to the first question below. Alternatively, if you have previously installed BMS, then in order to ensure correct installation of the other applications, you need to run the BMS startup procedure SYS$STARTUP:MCC_STARTUP_BMS.COM before beginning the installation procedure (as mentioned at the beginning of this chapter). ______________________________________________________ * Do you want to install DECmcc BMS? [YES]? DECmcc Basic Management System (BMS) will be installed... * Do you want to install DECmcc TCP/IP DA? [YES]? DECmcc DECmcc TCP/IP DA will be installed... * Do you want to install DECmcc ELM AM and FM? [YES]? DECmcc ELMS AM and FM will be installed... * Do you want to install The Network Trouble Shooting Guide? [YES]? DECmcc Network Trouble Shooting Guide will be installed... Installing the DECmcc EMS Software 2-9 If you select a product, VMSINSTAL displays a message confirming that the product will be installed. VMSINSTAL then proceeds to install the management applications you select and displays one or more of the following lines: %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... %VMSINSTAL-I-RESTORE, Restoring product save set D ... %VMSINSTAL-I-RESTORE, Restoring product save set E ... The Network Troubleshooting Guide is shipped on the media with your DECmcc EMS software. The guide provides an overview of network troubleshooting tools and methodologies, and detailed troubleshooting procedures for specific network problems. If you choose to install the Network Troubleshooting Guide, the installation procedure will install it in your Bookreader library. You can use the Bookreader application to select and view the contents of the guide online. Similarly, if you choose to install all products in the EMS product set, the installation procedure automatically installs the Network Troubleshooting Guide in your Bookreader library. The remainder of this chapter discusses the installation of individual management applications. It shows the questions VMSINSTAL asks and the responses provided for each application you install. 2.2 Installing Specific Management Applications This section describes the questions VMSINSTAL asks for each of the management applications that you can install as part of DECmcc EMS. The questions that VMSINSTAL asks you and their order of appearance within the installation procedure depend on which products you select for installation. If you choose to install all of the applications, VMSINSTAL asks the questions in the order that the following sections appear. If you choose to install only some (or one) of the applications, refer to the appropriate section(s). Section 2.2.1 describes the DECmcc BMS installation. 2-10 Installing the DECmcc EMS Software 2.2.1 Installing DECmcc BMS If you install the DECmcc Basic Management System, VMSINSTAL displays an introductory message and proceeds as follows: Asking DECmcc BMS Questions ... 1. Check active processes. VMSINSTAL displays a list of any active DECmcc processes and asks if you want to continue the installation. The default response to the question is NO. Enter YES and press RETURN to continue. Press RETURN to answer NO if you want to exit the installation procedure to stop any of the active processes before you install this product. You can restart the installation from Section 2.1 Step 1. 2. Name a directory for system common files. You must specify the directory where VMSINSTAL copies the DECmcc common files. The default directory is SYS$COMMON:[MCC]. DECmcc requires a directory where the DECmcc common files will be installed. If the logical MCC_COMMON has been redefined, the new definition will be used as the default. If the logical is not defined, the default is for the files to be installed in a directory on the system disk called SYS$COMMON:[MCC]. The installer may override the default. The target directory for the files as it is now defined is shown below. Press RETURN to use the value shown or enter a new disk and directory specification. * Target directory for DECmcc Common files [SYS$COMMON:[MCC]]: Press RETURN to select the value shown, or enter a new disk and directory specification. VMSINSTAL displays the following messages: %VMSINSTAL-I-SYSDIR, This product creates system directory [MCC]. %VMSINSTAL-I-SYSDIR, This product creates system specific directory [MCC]. Installing the DECmcc EMS Software 2-11 If you intend to execute this layered product on other nodes in your VAXcluster, and you have the appropriate software license, you must prepare the system-specific roots on the other nodes by issuing the following command on each node (using a suitably privileged account): $ CREATE/DIRECTORY SYS$SPECIFIC:[MCC]/OWNER_UIC=PARENT - /PROT=(S:RWE,O:RWE,G:RE,W:R) %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSTEST.MCC]. %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.MCC]. 3. Enter your Time Differential Factor (TDF). The Time Differential Factor (TDF) is a constant (a fixed number of hours and minutes) used to determine the local time. The DECmcc Director calculates the local time by adding the TDF to the Coordinated Universal Time (UTC). To calculate your TDF, determine in what time zone you are and calculate the difference between your time zone and the UTC. The installation procedure provides you with examples of TDFs, (see also Section 1.12.2 and Appendix B). The Time Differential Factor (TDF) is the difference between your time zone and the international standard Coordinated Universal Time (UTC) A negative (-) TDF value means that this node is west of UTC A positive (+) TDF value means that this node is east of UTC The range is from -12:00 to +13:00. The format is +hh:mm or -hh:mm with hh indicating the number of hours and mm indicating the number of minutes. A few examples are: Eastern Standard Time is -5:00 hours from UTC. Eastern Daylight Time is -4:00 hours from UTC. Great Britain, Iceland, Portugal, Upper Volta are at UTC or 0:0. Great Britain, Summer Time +1:00 hour from UTC. Japan is +9:00 hours from UTC. Using the DECdns TDF as the default TDF * Time Differential Factor [-5:00]: Enter your TDF and press RETURN. 4. Enter your namespace. 2-12 Installing the DECmcc EMS Software You must select a namespace for the storage of entity information. For additional information, refer to Section 1.12.3 and Chapter 5. DECmcc requires the use of a namespace service for the storage and retrieval of network entity information. You can select a local namespace or a distributed namespace (DNS). Select the local namespace, unless you have multiple DECmcc systems that need to share namespace information, or you are running DECnet/OSI and are using its distributed namespace. If either of these conditions apply, select the DNS; otherwise, select the local namespace. You may choose only one namespace. If you select the DNS, please see the DNS chapter in the DECmcc Planning and Installation for VMS manual on how to configure your namespace. If you intend to use the DECmcc Autoconfiguration applications with the local namespace, please see the Autoconfiguration and Autotopology Use manual on how to plan your entity name structure. * Use DECmcc Local MIR as the DECmcc Name Service [YES]? Using DECmcc Local MIR as the DECmcc Name Service * Is this correct [YES]? 5. Enter your network address IDP. VMSINSTAL prompts you for your network address Initial Domain Part (IDP). VMSINSTAL uses this IDP for the DECmcc BMS startup procedure. You must specify the IDP (or network address initial domain part) for your network. This must either be the default value of "49::", or a value explicitly allocated for your network by one of the recognized allocation authorities. The format is: afi:idi: where: afi = The "authority and format identifier". This is two decimal digits indicating the IDP allocation authority Installing the DECmcc EMS Software 2-13 idi = The "initial domain identifier". This is a string of decimal digits that has been allocated specifically for your network. An IDP of "49::" may be used if your network will not be interconnected with other OSI networks (there is no "idi" associated with this "afi"). * Initial Domain Part [49::]: Enter your IDP and press RETURN. 6. Specify whether you want to install the unsupported DECmcc Reports Package. The DECmcc Reports Package allows you to use DATATRIEVE to create reports with data exported to an Oracle Rdb database from DECmcc. VMSINSTAL displays information about the Reports Package and asks if you want to install the package: The DECmcc Reports Package consists of files that allow you to use DATATRIEVE to create reports using data exported from DECmcc. Please see the Reports Package section of the DECmcc Performance Analyzer Use manual for information on using the DECmcc Reports Package with DATATRIEVE. The Reports Package requires 1750 blocks. * Do you want to install the unsupported DECmcc Reports Package [No]? Yes Enter YES and press RETURN to install the package; or, press RETURN if you do not want to install the package. If you choose to install the Reports Package, VMSINSTAL asks you to specify a directory for the files. * Target directory for DECmcc Reports files [SYS$COMMON:[MCC.MCC_REPORTS_FILES]]: Enter a target directory and press RETURN; or, press RETURN to use the default, which is the subdirectory: SYS$COMMON:[MCC.MCC_REPORTS_FILES]. The directory you select defines the logical name MCC_ REPORTS_FILES. When you want to move the reports files to another directory, edit the file SYS$STARTUP:MCC_ LOGICAL_BMS.COM to redefine that logical name. 2-14 Installing the DECmcc EMS Software The following message is displayed: VMSINSTAL asks no additional questions. VMSINSTAL completes the installation and displays one or more of the following messages, depending on which products you have installed on your system: %VMSINSTAL-I-RESTORE, Restoring product save set J ... %VMSINSTAL-I-RESTORE, Restoring product save set K ... %VMSINSTAL-I-RESTORE, Restoring product save set L ... %VMSINSTAL-I-RESTORE, Restoring product save set M ... %VMSINSTAL-I-RESTORE, Restoring product save set N ... %VMSINSTAL-I-RESTORE, Restoring product save set O ... %VMSINSTAL-I-RESTORE, Restoring product save set P ... %VMSINSTAL-I-RESTORE, Restoring product save set Q ... %VMSINSTAL-I-RESTORE, Restoring product save set T ... Linking mcc_mts_priv_shr... 2.2.2 Building the MIR Dictionary This section of the installation builds the MIR dictionary. Updating DECmcc dictionary and parse tables ... $ MANAGE/TOOLKIT/DICTIONARY %DAP-S-USE_DICT, Using dictionary file: dka200:[sys0.sysupd.MCCEMS030]mcc_fdictionary.dat;1 DECmcc Dictionary Administrator Program Version V3.0 Installing the DECmcc EMS Software 2-15 Percent of file processed = Percent of file processed = 5% Percent of file processed = 10% Percent of file processed = 15% Percent of file processed = 20% Percent of file processed = 25% Percent of file processed = 30% Percent of file processed = 35% Percent of file processed = 40% Percent of file processed = 45% Percent of file processed = 50% Percent of file processed = 55% Percent of file processed = 60% Percent of file processed = 65% Percent of file processed = 70% Percent of file processed = 75% Percent of file processed = 80% Percent of file processed = 85% Percent of file processed = 90% Percent of file processed = 95% Percent of file processed = 100% Now writing processed records to dictionary file... CTRL-C and CTRL-Y are disabled while the records are being written. ________________________ Note ________________________ The installation procedure continues to display many others files, along with the percentage of the files processed. ______________________________________________________ 2.2.3 Building and Updating the Help Files The installation procedure builds and updates the Help files. Updating DECmcc HELP files ... DECmcc Help File Builder Component Version: V3.0 2-16 Installing the DECmcc EMS Software Cleaning up any intermediate files... Processing file VMI$ROOT:[MCC]MCC_ALARMS_FM.HELP Processing file VMI$ROOT:[MCC]MCC_BRIDGE_AM.HELP Processing file VMI$ROOT:[MCC]MCC_CIRCUIT_AM.HELP Processing file VMI$ROOT:[MCC]MCC_COLLECTION_AM.HELP Processing file VMI$ROOT:[MCC]MCC_CONC_AM.HELP Processing file VMI$ROOT:[MCC]MCC_DNA4_AM.HELP Processing file VMI$ROOT:[MCC]MCC_DNA5AM_HELP.HELP Processing file VMI$ROOT:[MCC]MCC_DOMAIN_FM.HELP Processing file VMI$ROOT:[MCC]MCC_ENET_AM.HELP Processing file VMI$ROOT:[MCC]MCC_EXPORTER_HELP.HELP Processing file VMI$ROOT:[MCC]MCC_FDDI_AM.HELP Processing file VMI$ROOT:[MCC]MCC_FDDI_FM.HELP Processing file VMI$ROOT:[MCC]MCC_GENERAL_HELP.HELP Processing file VMI$ROOT:[MCC]MCC_HISTORIAN_HELP.HELP Processing file VMI$ROOT:[MCC]MCC_KERNEL_AM.HELP Processing file VMI$ROOT:[MCC]MCC_NOTIFICATION_FM.HELP Processing file VMI$ROOT:[MCC]MCC_PA_BRIDGE_FM.HELP Processing file VMI$ROOT:[MCC]MCC_PA_FM.HELP Processing file VMI$ROOT:[MCC]MCC_STM_FM.HELP Processing file VMI$ROOT:[MCC]MCC_TCPIP_AM.HELP Processing file VMI$ROOT:[MCC]MCC_TCPIP_DA_FM.HELP Processing file VMI$ROOT:[MCC]MCC_TCPIP_EXP_RMON.HELP Processing file VMI$ROOT:[MCC]MCC_TCPIP_STD_RMON.HELP Verifying hierarchy... Verifying for character cell Verifying for windows Processing file(s).... MCC help files updated. MCC help files updated. Cleaning up any intermediate files... Installing the DECmcc EMS Software 2-17 2.2.4 Adding a Command to Your System Startup Command Procedure VMSINSTAL directs you to modify your local system startup command procedure to set up DECmcc BMS automatically. Refer to Section 4.1 for more information on how to modify your system startup procedure. Following the copying of the files, the DECmcc EMS startup command procedure(s) will be invoked. To automatically set up DECmcc EMS on your system, edit your local system start-up command procedure SYS$MANAGER:SYSTARTUP_V5.COM (OpemVMS V5.n) or SYS$MANAGER:SYSTARTUP_VMS.COM (OpenVMS V6.n or higher) so that it invokes the following startup procedure(s) If DECmcc BMS has been installed, please make sure its startup procedure is first. Add: @SYS$STARTUP:MCC_STARTUP_BMS.COM @SYS$STARTUP:MCC_TCPIP_DA_FM_STARTUP.COM @SYS$STARTUP:MCC_STARTUP_ELM_AM.COM @SYS$STARTUP:MCC_STARTUP_ELM_FM.COM after the statement that invokes the DECnet start-up command file (STARTNET.COM). NOTE: If you have previously installed the DECmcc DIRECTOR on this system, you should REMOVE the line: @SYS$STARTUP:MCC_STARTUP_DIR.COM from your SYS$MANAGER:SYSTARTUP_V5.COM procedure (OpenVMS V5.n) or from SYS$MANAGER:SYSTARTUP_VMS.COM (OpenVMS V6.n) Following the DECmcc EMS start-up the DECmcc EMS IVP command procedure(s) will be invoked. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... 2-18 Installing the DECmcc EMS Software 2.3 Post-Installation Messages If the installation procedure has been successful thus far, VMSINSTAL moves the new or modified files to their target directories, updates help files, and updates DCL tables, if necessary. If you asked for files to be purged, the purging is done now. The installation procedure displays messages that provide post-installation information and setup suggestions. If you chose to install all of the applications, the installation procedure displays the messages in the order in which the following sections appear. If you chose to install only some (or one) of the applications, refer to the appropriate section(s). Refer to Chapter 5 for information on performing the post-installation tasks. The installation will now display the following message: Beginning DECmcc EMS V3.0-000 Post-Installation Procedure ... The following sections show the post-installation messages displayed for each DECmcc EMS application. 2.3.1 Post-Installation Messages for DECmcc BMS The installation procedure for DECmcc BMS creates and deletes an alarm rule. It displays the following post- installation messages for DECmcc BMS: Beginning DECmcc BMS Post-Installation Procedure ... Deleting obsolete DECmcc verbs... The MCC_STARTUP_BMS startup procedure for DECmcc V3.0 is now running. DECmcc (V3.0) MCC 0 ALARMS RULE __dummy_test AT 24-JUL-1996 17:58:12 Entity created successfully. MCC 0 ALARMS RULE __dummy_test AT 24-JUL-1996 17:58:13 Entity deleted successfully. The MCC_STARTUP_BMS startup procedure for DECmcc is now ending. Completing DECmcc BMS Post-Installation Procedure ... Installing the DECmcc EMS Software 2-19 2.3.2 Post-Installation Messages for TCP/IP DA FM The TCP/IP DA FM post-installation procedure displays the following messages. Beginning DECmcc TCPIP DA FM Post-Installation Procedure ... Startup procedure for DECmcc TCP/IP DA FM running. DECmcc (V3.0) Startup procedure for DECmcc TCP/IP DA FM ending. Completing DECmcc TCPIP DA FM Post-Installation Procedure ... 2.3.3 Post-Installation Messages for DECmcc ELM AM The DECmcc ELM AM post-installation procedure displays the following messages. Beginning DECmcc ELM AM Post-Installation Procedure ... The MCC_STARTUP_ELM_AM startup procedure for DECmcc V3.0 is now running. Note: The DECmcc Director or BMS Startup procedures should be run prior to executing this procedure. DECmcc (V3.0) %MCC-I-ENRDUPLENTRY, enrollment successful; duplicate entries found and replaced %MCC-I-ENRDUPLENTRY, enrollment successful; duplicate entries found and replaced MCC 0 ALARMS RULE __dummy_test AT 24-JUL-1996 17:58:24 Entity created successfully. MCC 0 ALARMS RULE __dummy_test AT 24-JUL-1996 17:58:25 Entity deleted successfully. The MCC_STARTUP_ELM_AM startup procedure for DECmcc V3.0 is now ending. Completing DECmcc ELM AM Post-Installation Procedure ... 2-20 Installing the DECmcc EMS Software 2.3.4 Post-Installation Messages for DECmcc ELM FM The DECmcc ELM FM post-installation procedure displays the following messages. Beginning DECmcc ELM FM Post-Installation Procedure ... The MCC_STARTUP_ELM_FM startup procedure for DECmcc V3.0 is now running. Note: The DECmcc Director or BMS Startup procedures should be run prior to executing this procedure. DECmcc (V3.0) The MCC_STARTUP_ELM_FM startup procedure for DECmcc V3.0 is now ending. Completing DECmcc ELM FM Post-Installation Procedure ... 2.4 Running the IVP VMSINSTAL automatically runs the Installation Verification Procedure (IVP) for DECmcc EMS, provided you answered YES to the question at the beginning of the installation that asked if you wanted the IVP to run. Refer to Chapter 3 for information about the IVPs for DECmcc EMS and the IVPs for the individual applications. 2.5 Completing the Installation The following message indicates that the installation is complete (this message identifies the DECmcc EMS product that you installed): Completing DECmcc EMS V3.0-000 Post-Installation Procedure ... You can now log out of the privileged account. Note that VMSINSTAL deletes or changes entries in the process symbol tables during the installation for the duration of the session. Therefore, if you are going to continue using the system manager's account and you want to restore these symbols, you should log out and log in again. Installing the DECmcc EMS Software 2-21 2.6 Installation Errors If errors occur during the installation, VMSINSTAL displays descriptive error messages. If the installation fails, the following message is displayed: %VMSINSTAL-E-INSFAIL, The installation of DECmcc EMS V3.0-000 has failed. Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect. o A prerequisite software version is incorrect. o Quotas necessary for successful installation are insufficient. o System parameter values for successful installation are insufficient. o The VMS help library is currently in use. For descriptions of the error messages generated by these conditions, refer to the VMS documentation on system messages, recovery procedures, and VMS software installation. If you are notified that any of these conditions exist, you should take the appropriate action, as described in the message. Refer to Chapter 1 for information on installation requirements. 2-22 Installing the DECmcc EMS Software 3 _________________________________________________________________ Verifying the Installation of the DECmcc EMS Software This chapter discusses the Installation Verification Procedures (IVPs), which you can run to verify that the DECmcc EMS software has been properly installed. The IVPs can be run automatically by the installation procedure or independently after the installation. To run the IVPs after the installation, the IVP for each installed network management product must be run separately. Section 3.1 describes how to run the IVP for an individual management product. Section 3.2 discusses the failure of an IVP. 3.1 Running the IVPs on Individual Applications This section describes how to run the IVPs on individual management applications. First, set the default directory to SYS$TEST: $ SET DEFAULT SYS$TEST Then enter the command that initiates the IVP, as listed in Table 3-1. Table 3-1 Commands to Run the IVP for Individual __________Applications_____________________________________ Application___________Command______________________________ DECmcc BMS @MCC_BMS_IVP TCP/IP DA @MCC_TCPIP_DA_FM ELM AM @MCC_ELM_AM_IVP ELM_FM________________@MCC_ELM_FM_IVP______________________ The next sections describe the messages the IVP provides for successful verification of each management application. Section 3.2 discusses the failure of an IVP. Verifying the Installation of the DECmcc EMS Software 3-1 3.1.1 DECmcc BMS Installation Verification Procedure The output of the IVP for DECmcc BMS follows: The IVP for DECmcc BMS will now be run. DECmcc (V3.0) MCC 0 AT 24-JUL-1996 17:58:35 Test Successful DECmcc (V3.0) MCC 0 FCL AT 24-JUL-1996 17:58:38 Test Successful DECmcc (V3.0) MCC 0 REGISTRATION_FM AT 24-JUL-1996 17:58:41 Test Successful DECmcc (V3.0) MCC 0 DNA4_AM AT 24-JUL-1996 17:58:44 Test Successful DECmcc (V3.0) MCC 0 DNA5_AM AT 24-JUL-1996 17:58:47 Test Successful. DECmcc (V3.0) MCC 0 ICONICMAP AT 24-JUL-1996 17:58:50 Test Successful DECmcc (V3.0) MCC 0 DOMAIN_FM AT 24-JUL-1996 17:58:53 Test Successful DECmcc (V3.0) 3-2 Verifying the Installation of the DECmcc EMS Software MCC 0 SAMPLE_AM AT 24-JUL-1996 17:58:56 Test Successful. DECmcc (V3.0) MCC 0 ETHERNET_AM AT 24-JUL-1996 17:58:59 Test successful. DECmcc (V3.0) MCC 0 TCPIP_AM AT 24-JUL-1996 17:59:02 Test Successful. DECmcc (V3.0) MCC 0 CIRCUIT_AM AT 24-JUL-1996 17:59:05 Test Successful. DECmcc (V3.0) MCC 0 ALARMS AT 24-JUL-1996 17:59:10 Test Successful. DECmcc (V3.0) MCC 0 HISTORIAN_FM AT 24-JUL-1996 17:59:13 Test Successful DECmcc (V3.0) MCC 0 PA AT 24-JUL-1996 17:59:16 Test Successful DECmcc (V3.0) MCC 0 EXPORTER_FM AT 24-JUL-1996 17:59:19 Test Successful DECmcc (V3.0) Verifying the Installation of the DECmcc EMS Software 3-3 MCC 0 NOTIFICATION_FM AT 24-JUL-1996 17:59:22 Test Successful DECmcc (V3.0) MCC 0 COLLECTION_AM AT 24-JUL-1996 17:59:25 Test Successful. DECmcc (V3.0) MCC 0 SCRIPT_AM AT 24-JUL-1996 17:59:28 Test Successful. %DAP-S-USE_DICT, Using dictionary file: sys$common:[mcc]mcc_fdictionary.dat;2 POLYCENTER Dictionary Administrator Program Version V3.0 MCC_TBD Version 1.4-0 DECmcc BMS V3.0 Installation Successful Completing DECmcc BMS Installation Verification Procedure .. Successful completion of the IVP indicates that the DECmcc BMS software is installed correctly. 3.1.2 TCP/IP DA FM IVP The DECmcc TCP/IP DA FM IVP displays the following messages. Beginning DECmcc TCP/IP DA FM Installation Verification Procedure The IVP for DECmcc TCP/IP DA FM will now be run. MCC 0 TCPIP_DA_FM AT 24-JUL-1996 17:59:35 Test successful. DECmcc TCP/IP DA FM Installation Successful Completing DECmcc TCP/IP DA FM Installation Verification Procedure 3-4 Verifying the Installation of the DECmcc EMS Software 3.1.3 DECmcc ELM AM IVP The DECmcc ELM AM IVP displays the following messages. Beginning DECmcc ELM AM Installation Verification Procedure ... The IVP for DECmcc ELM AM V3.0 will now be run. DECmcc (V3.0) MCC 0 ALARMS AT 24-JUL-1996 17:59:39 Test successful. DECmcc (V3.0) MCC 0 PA AT 24-JUL-1996 17:59:41 Test Successful DECmcc (V3.0) MCC 0 BRIDGE_AM AT 24-JUL-1996 17:59:44 Test successful. DECmcc (V3.0) MCC 0 CONC_AM AT 24-JUL-1996 17:59:47 Test successful. DECmcc (V3.0) MCC 0 FDDI_AM AT 24-JUL-1996 17:59:50 Test successful. DECmcc ELM AM V3.0 Installation Successful Completing DECmcc ELM AM Installation Verification Procedure ... Verifying the Installation of the DECmcc EMS Software 3-5 3.1.4 DECmcc ELM FM Installation Verification Procedure The DECmcc ELM FM IVP displays the following messages. Beginning DECmcc ELM FM Installation Verification Procedure ... The IVP for DECmcc ELM FM V3.0 will now be run. DECmcc (V3.0) MCC 0 STM_FM AT 24-JUL-1996 17:59:53 Test successful. DECmcc (V3.0) MCC 0 FDDI_FM AT 24-JUL-1996 17:59:56 Test successful. DECmcc (V3.0) MCC 0 ICONICMAP APPLICATION LAN_TOPOLOGY_PM AT 24-JUL-1996 17:59:59 Test Successful DECmcc ELM FM V3.0 Installation Successful Completing DECmcc ELM FM Installation Verification Procedure ... 3.1.5 DECmcc EMS Installation Verification Completion The text of a successful completion is as follows: Completing DECmcc EMS V3.0-000 Installation Verification Procedure .. Installation of MCCEMS V3.0-000 completed at 17:59 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]MCCEMS030.VMI_DATA Enter the products to be processed from the next distribution volume set. * Products: VMSINSTAL procedure done at 18:00 3-6 Verifying the Installation of the DECmcc EMS Software 3.2 What to Do if the IVP Fails If you receive a failure message, the installation procedure may not have installed the required files. Ensure that you have all the prerequisite hardware and software products specified in the Software Product Description (SPD) and described in Chapter 1. Repeat the installation procedure, described in Chapter 2, for the management application(s) not installed properly. If the problem persists, contact your Digital Equipment Corporation representative. Verifying the Installation of the DECmcc EMS Software 3-7 4 _________________________________________________________________ After Installing the DECmcc EMS Software This chapter discusses tasks you need to perform after you have installed DECmcc EMS and its supported management applications. Section 4.1 through Section 4.6 describe the following tasks you need to perform for the EMS applications: o Editing the system startup file o Rebooting the system o Running an application in the cluster environment o Setting user account privileges o Setting user account quotas o Enhancing DECmcc EMS performance o Reporting Problems The remaining sections discuss procedures you need to perform for specific applications. 4.1 Editing the System Startup File After installing DECmcc EMS, you must edit the system startup file, SYS$MANAGER:SYSTARTUP_VMS.COM, to provide for automatic startup of the installed products when your system is rebooted. Startup commands for each application appear in Table 4-1 These commands must appear after the command that invokes the network startup command procedure. Each command must be preceded by the dollar sign prompt ($). After Installing the DECmcc EMS Software 4-1 Table_4-1_Management_Application_System_Startup_Command____ Application_______Startup_Command__________________________ DECmcc BMS @SYS$STARTUP:MCC_STARTUP_BMS TCP/IP DA @SYS$STARTUP:MCC_TCPIP_DA_FM_STARTUP.COM ELM AM @SYS$STARTUP:MCC_STARTUP_ELM_AM.COM ELM_FM____________@SYS$STARTUP:MCC_STARTUP_ELM_FM.COM______ 4.1.1 DECmcc Startup Commands Place the DECmcc startup commands after the startup commands for the Distributed Name Service (DNS) and DECnet. 4.1.2 Rebooting the System You can reboot your system after you have installed DECmcc EMS and edited the system startup file. A system reboot verifies that DECmcc EMS is ready for use and ensures that the edits to the system startup command file have been taken into account. Rebooting is optional. 4.2 Running an Application in the Cluster Environment To run the application on a cluster, you must register the product license on each node in the cluster. For more information about the VMS License Management Facility (LMF), see Section 1.4. 4.2.1 Running DECmcc BMS in a Cluster Environment To use DECmcc BMS in a VAXcluster environment, you must perform the following tasks on each node in the cluster: 1. Prepare system-specific roots on the nodes other than the one on which you installed DECmcc BMS. Log into the node's SYSTEM account and create a root directory by entering the following command: $ CREATE/DIRECTORY SYS$SPECIFIC:[MCC]/OWNER_UIC=PAR/PROT=(G:RE,W:RWE) 2. Use the Install utility to replace the DCLTABLES file. $ INSTALL INSTALL>REPLACE SYS$COMMON:[SYSLIB]DCLTABLES.EXE/HEADER/OPEN/SHARE INSTALL>EXIT 4-2 After Installing the DECmcc EMS Software This makes the DECmcc DCL command verbs accessible on all the nodes in the cluster. For more information on the Install Utility, see the VMS Install Utility manual. 3. Add the MANAGE/ENTERPRISE command to the process DCL table. $ SET COMMAND SYS$COMMON:[MCC]MCC_COMMANDS.CLD 4. Ensure that the DNS clerk is started up. Run the MCC startup command files. $ @SYS$STARTUP:MCC_STARTUP_BMS.COM 5. Add the MCC startup command files to the system startup procedure, SYS$MANAGER:SYSTARTUP_VMS.COM. 4.3 Setting User Account Privileges To use DECmcc EMS, an account must have at least the TMPMBX and NETMBX privileges. Use the VMS Authorize utility to ensure that users have the privileges they require. Additional privileges required by individual management applications are listed in the following sections. The following example shows how to use Authorize to grant the necessary privileges. The user name in this example is SMITH. $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> MODIFY SMITH/PRIV=TMPMBX %UAF-I-MDFYMSG, user record(s) updated UAF> MODIFY SMITH/PRIV=NETMBX %UAF-I-MDFYMSG, user record(s) updated UAF> EXIT %UAF-I-DONEMSG, system authorization file modified %UAF-I-NAFNOMODS, no modifications made to network authorization file %UAF-I-RDBNOMODS, no modifications made to rights database $ For more information on modifying user privileges, see the description of the Authorize utility in the VMS System Management Subkit. After Installing the DECmcc EMS Software 4-3 4.4 Setting User Account Quotas To use DECmcc EMS, user accounts on your system must have sufficient quotas. Table 4-2 summarizes the minimum values of the required user account quotas. Table 4-2 Minimum Values of Required DECmcc EMS User __________Account_Quota____________________________________ Account_Quota____EMS_Value_________________________________ ASTlm 200 BIOlm 100 Bytlm 65,000 DIOlm 100 Enqlm 2,000 Pgflquo 150,000 PRClm 20 TQElm 300 WSdef [1] 512 WSquo 4,096 WSextent 16,000 [1]_The_values_for_WSextent_must_be_equal_to_or_greater____ than the WSDEF value. ___________________________________________________________ Refer to Section 1.11.2 for information on modifying your account quotas. 4.5 Enhancing DECmcc EMS Performance Section 4.5.1, Section 4.5.2 and Section 4.5.3, provide information on improving DECmcc EMS system performance. 4.5.1 Installing Shared Images This section explains how to install the various DECmcc EMS management applications as shared images to enhance their performance. If DECmcc EMS applications will be used extensively on your system, you can reduce the system overhead and memory requirements by installing each application as a shared image. 4-4 After Installing the DECmcc EMS Software To install an application as a shared image on a system that is currently running, use the VMS Install Utility (INSTALL). You should perform the installation on a system that has just been bootstrapped because the available space in the global page table is less likely to be fragmented. First, determine the number of available global pages and global sections on your system. See Section 1.10 for information on displaying system parameter values. Once you have set the system parameter values, invoke the VMS Install Utility from a privileged account and install the application as a shared image. The following commands install a shared image for a management application: $ INSTALL INSTALL> ADD name /OPEN /SHARED INSTALL> EXIT $ Table 4-3 provides the image name for each application; substitute the name in the table for the name in the ADD command. You must also add the Install commands to the appropriate system startup command file, so that each time the system is started, the application is available as a shared image. (If your site has modularized your startup procedures, be sure you add the lines to the correct file.) The default startup command file is: SYS$MANAGER:SYSTARTUP_VMS.COM Add the following line to the system startup file: $ INSTALL INSTALL> ADD name /OPEN /SHARED INSTALL> EXIT $ Again, replace name in the ADD command by the name in Table 4-3. After Installing the DECmcc EMS Software 4-5 Table_4-3_DECmcc_EMS_Executable_Image_Name_________________ Application________Executable_Image_Name___________________ DECmcc BMS SYS$SYSTEM:MCC_ALARMS_EXTRACT_RULES.EXE SYS$SYSTEM:MCC_DAP_MAIN.EXE, SYS$SYSTEM:MCC_DNS_SETUP.EXE, SYS$SYSTEM:MCC_EXPORTER_FM_BG.EXE, SYS$SYSTEM:MCC_EXPORTER_FM_WRITER.EXE, SYS$SYSTEM:MCC_HFB_MAIN.EXE, SYS$SYSTEM:MCC_HISTORIAN_FM_BG.EXE, SYS$SYSTEM:MCC_MAIN.EXE, ___________________SYS$SYSTEM:MCC_RBMS_CONVERT_MAIN.EXE____ 4.5.2 Tuning for Good Performance DECmcc performance can be hindered if a system parameter or user quota is too low. It is impossible to recommend values that will be optimal for every DECmcc user, since performance is configuration dependent. Table 4-4 lists suggested values for a typical system. These values are guidelines only. They are intended to point out the areas in which a system manager can improve performance. Table 4-4 lists user process quotas, and Table 4-5 lists SYSGEN parameters. The supplied DECmcc System Audit utility checks for the values listed in Table 4-4 and Table 4-5, as well as for other potential sources of run-time problems, such as disk space and prerequisite software. Refer to Section 4.5.3 for instructions on the DECmcc System Audit Utility. Table_4-4_Process_Quota_Values_____________________________ Process_Quota______________Value___________________________ Fillm 400 Bytlm 65000 BIOlm 100 (continued on next page) 4-6 After Installing the DECmcc EMS Software Table_4-4_(Cont.)_Process_Quota_Values_____________________ Process_Quota______________Value___________________________ Prclm 20 DIOlm 100 ASTlm 200 WSquo 4096 TQElm 300 WSextent 16000 Enqlm 2000 Pgflquo [1] 150000 [1]_The_Pagefile_size_must_be_greater_than_Pgflquo._300000_ blocks would be typical. ___________________________________________________________ Table_4-5_SYSGEN_Parameter_Values__________________________ SYSGEN_Parameter___________Value___________________________ CLISYMTBL 250 LOCKIDTBL_MAX 2048 PROCSECTCNT 200 REHASHTBL 512 MAXBUF 1200 PAGEDYN 1000448 NPAGEDYN 900096 GBLPAGFIL 12200 CTLPAGES 32 PQL_MASTLM 600 WSMAX 16000 CHANNELCNT_________________512_____________________________ 4.5.3 Using the DECmcc System Audit Utility You can check for potential sources of run-time problems by running the DECmcc System Audit utility. After Installing the DECmcc EMS Software 4-7 The DECmcc System Audit utility checks for the sample user quotas and SYSGEN parameters listed in Table 4-4 and Table 4-5. It also checks disk space, memory, prerequisite software, and other resources to determine if your environment is well set up for efficient use of DECmcc. You need SYSPRV privilege to run the utility. To invoke the audit utility, enter the following command: $ @MCC_COMMON:MCC_AUDIT [user-name] If you supply the user-name, the utility will perform only its user quota checks and only for the specified user. If you do not supply the user-name, the utility will perform all its checks but only for the user issuing the command. The audit utility provides two kinds of output. It displays warning messages on your screen, and produces a file whose contents are properly formatted for use in SYS$SYSTEM:AUTHORIZE (UAF) commands, which set user quotas, and in the SYS$SYSTEM:MODPARAMS.DAT file, which contains SYSGEN parameters. The name and location of the output file is SYS$LOGIN::MCC_AUDIT_FIX.TXT. The contents of a sample output file are as follows: ! !Authorization file changes for User COLLEEN ! by MCC_AUDIT for DECmcc V3.0 ! MODIFY COLLEEN /FILLM=200 MODIFY COLLEEN /BYTLM=65000 MODIFY COLLEEN /BIOLM=100 MODIFY COLLEEN /ASTLM=200 MODIFY COLLEEN /WSQUO=4096 MODIFY COLLEEN /TQELM=300 MODIFY COLLEEN /WSEXTENT=16000 MODIFY COLLEEN /PGFLQUO=150000 ! !Sysgen changes for system PARIS:: ! by MCC_AUDIT for DECmcc V3.0, on 25-JUL-1996 16:59:58.84 ! 4-8 After Installing the DECmcc EMS Software PROCSECTCNT = 200 REHASHTBL = 512 NPAGEDYN = 900096 GBLPAGFIL = 1220 PQL_MASTLM = 600 Please keep in mind that the values suggested by the audit utility will not apply to all configurations. They are intended as pointers to possible problem areas. 4.6 Troubleshooting and Reporting Problems If you encounter a problem with the DECmcc EMS software or documentation, please document the problem thoroughly and submit a report on that problem to DIGITAL. If an error occurs and you believe that the error is due to a problem in DECmcc EMS, document that error by using the following guidelines: o Describe the state of the system and the circumstances when the problem occurred as accurately as possible. Ensure that you specify the version number of the DECmcc EMS application that you are running. Use SHOW MCC 0 ALL CHARACTERISTICS to get the version number. Illustrate the problem with specific examples. If you report a documentation error, specify the title of the document as well as the section and page number where the error was found. o Isolate the error as much as possible. o Submit sources on machine-readable media (magnetic tape), if possible. All media will be returned to you when the problem report is answered. o Report only one problem at a time. This will facilitate a faster response. Experience shows that many problem reports do not contain sufficient information to duplicate or identify the problem. Complete and concise information will help DIGITAL give accurate and timely service to software problems. The following list describes the kind of information you should include in a problem report. o Your network configuration After Installing the DECmcc EMS Software 4-9 o Any enrollment data o Problem occurred in foreground or background mode o Entity that was being managed o Problem in access, function, or interface management module o Who supplied the software (for example, DIGITAL, third party name, or your company) o Problem occurred in management or user interface o Other network management products installed 4.7 DECmcc BMS Post-Installation Procedures This section discusses post-installation procedures you may need to perform to use DECmcc BMS. 4.7.1 Setting Up the DNS Namespace If you have chosen the DNS namespace, refer to Chapter 5 for planning and setup information. 4.7.2 Setting File Protection for DECmcc BMS Files If non-privileged users need to use DECmcc BMS, you must change the protection to allow them to access several files. When DECmcc BMS is first installed, file protections are set for system, owner, and group to have full access, and world to have READ-ONLY access. If a non-privileged user attempts to execute a directive that requires privileges, error messages appear indicating that a file protection violation exists. Follow your company security policy to change the protection to allow non-privileged users access to DECmcc BMS. The following examples show how you might open a DECmcc BMS common file so that the non-privileged user, Wanda James, can access it. Refer to the specific access or function module manual in the DECmcc BMS documentation set for examples of how to open specific files for access by non-privileged users. 4-10 After Installing the DECmcc EMS Software o This example illustrates how to change access control for one user only: $ SET FILE MCC_SPECIFIC:MCC_DISPATCH_TABLE.DAT - /ACL=(IDENTIFIER=[NETMAN,W_JAMES],ACCESS=READ+WRITE) o This example illustrates how to change the file protection: $ SET PROTECTION=(W:RW) MCC_COMMON:MCC_DISPATCH_TABLE.DAT Table 4-6 shows the privileges required for access to key DECmcc BMS files. Table_4-6_DECmcc_BMS_File_Protection_____________________________ Default File_Name____________Contents____________ProtectioAccess_Required MCC_SPECIFIC: This directory S:RWE Change to match contains DECmcc O:RWE access of files system specific G:RW within this files. W:R directory. MCC_COMMON: This directory S:RWE Change to match contains the O:RWE access of files remaining files G:RW within this listed in this W:R directory. table. MCC_DISPATCH_ Dispatch tables S:RWED To enroll new TABLE.DAT for DECmcc O:RWED Management Management G:RE Modules, you Modules. W:R must have RW access. MCC_META_ Dictionary S:RWED To use the DICTIONARY.DAT hierarchy for MCC_ O:RWED DECmcc DICTIONARY.DAT. G:RWED Developer's W:R Toolkit, you must have R access. (continued on next page) After Installing the DECmcc EMS Software 4-11 Table_4-6_(Cont.)_DECmcc_BMS_File_Protection_____________________ Default File_Name____________Contents____________ProtectioAccess_Required MCC_META_ Data that S:RWED To use the DEFINITION.DAT describes all O:RWED DECmcc known definitions G:RWED Developer's for W:R Toolkit, you MCC_ must have R DEFINITION.DAT. access. MCC_MIR_ List of all known S:RWED To use the DIRECTORY.DAT repositories for O:RWED DECmcc Director DECmcc BMS. G:RWED or DECmcc BMS, W:R you must have R access. To use the DECmcc Developer's Toolkit, Historian, Exporter, and Alarms FMs, you must have RW access. MCC_MIR_ Location and RMS S:RWED To use the ATTRIBUTE.DAT file attributes O:RWED DECmcc Director for all known G:RWED or DECmcc BMS, repositories of W:R you must have DECmcc BMS. R access. To use the DECmcc Developer's Toolkit, Historian, Exporter, and Alarms FMs, you must have RW access. (continued on next page) 4-12 After Installing the DECmcc EMS Software Table_4-6_(Cont.)_DECmcc_BMS_File_Protection_____________________ Default File_Name____________Contents____________ProtectioAccess_Required MCC_DICTIONARY.DAT Entity class S:RWED To use the hierarchies. O:RWED DECmcc Director G:RWED or DECmcc BMS, W:R you must have R access. To use the DECmcc Developer's Toolkit, you must have RW access. MCC_DEFINITION.DAT Entity meta-data. S:RWED To use the O:RWED DECmcc Director G:RWED or DECmcc BMS, W:R you must have R access. To use the DECmcc Developer's Toolkit, you must have RW access. MCC_PTB_PARSER.BPT Command parser S:RWED To use the information. O:RWED DECmcc Director G:RWED or DECmcc BMS, W:R you must have R __________________________________________________access.________ After Installing the DECmcc EMS Software 4-13 5 _________________________________________________________________ Using the Distributed Name Service with DECmcc This chapter should be read by all users who have chosen the Distributed Name Service (DNS) as the DECmcc namespace. The chapter includes the following topics: o DNS Overview o DNS Components and Terminology o Structuring DNS Namespaces o Planning to Set up and Use the DNS with DECmcc o Planning the DNS Directory Hierarchy for DECmcc o Planning and Creating DNS Access Control Groups o Setting Up the DNS Namespace - Creating the DNS Directories Required for DECmcc - Creating the .DNA_Registrar Access Control Group - Creating Additional DNS Directories - Managing the .DNA_Registrar Access Control Group - Creating a Procedure to Register DECnet Phase IV Nodes - Specifying Privileges for Any Additional Access Control Groups o Verifying DECmcc and DNS Interoperability o Troubleshooting the DNS Namespace Using the Distributed Name Service with DECmcc 5-1 5.1 DNS Overview The Distributed Name Service is a network-wide service that makes it possible to refer to and use resources without knowing their physical location in the network. If you select DNS, it stores the registered names you create for DECmcc global entities. You also supply the entities' network addresses. The names are then available to all DECmcc users on the network. DNS also stores other relevant information, including the names of child entities, reference data, and a list of the domains of which an entity is a member. Location-independent naming is especially useful in a changing distributed computing environment. As networks grow and resources change location, the information stored with a name might change, but the name itself never needs to change. In addition to location-independent naming, DNS offers the following features: o Unique network-wide names - All DNS users and applications in the network use the same unique name to access a resource. o Expandability - New names are easily accommodated as the network grows and more applications use DNS. o Simplified management of network entity names - Entity names are stored and maintained by DNS, eliminating the need to update and maintain permanent node databases on DECnet systems. o Caching of frequently used information - DNS software caches, or saves, information obtained from previous requests to look up a name. Caching maximizes overall performance and reduces network traffic. o Security - Access to DNS names can be assigned to individuals or to access control groups. o Flexibility - DNS runs on both VMS and ULTRIX systems and works in both LAN and WAN environments. Operation of the name service involves several major components: o DNS servers 5-2 Using the Distributed Name Service with DECmcc o Clearinghouses o DNS client applications, such as DECmcc o DNS clerks A system running DNS server software is a DNS server. A server stores and maintains DNS names and handles requests to create, modify, or look up data. When a server is running, it advertises its availability to other nodes on the same LAN. DNS uses a client-server model; an application, such as DECmcc, that depends on DNS to store and retrieve information for it is a client of DNS. DECmcc can manage DNS clerk and server nodes through the DECnet Phase IV and DECnet/OSI access modules. 5.2 DNS Components and Terminology The DNS client/server model uses clerks and clearinghouses. Clerks are the interfaces between clients and servers, and clearinghouses are the databases that store namespace information. DECmcc and other client applications communicate with DNS servers through a DNS component called the clerk. The clerk receives a request from a client application, sends the request to a server, and returns the resulting information to the client. This process is called a lookup. The clerk is also the interface through which client applications create and modify names. Every DNS server stores names and their attributes in a database file called a clearinghouse. The clearinghouse is where a DNS server adds, modifies, deletes, and retrieves data on behalf of client applications and DNS managers. Usually only one clearinghouse exists on each server. Figure 5-1 shows a sample configuration of DNS clerks and servers on a nine-node LAN. A clerk exists on every node in the network, and DNS servers are running on two selected nodes. Because servers manage clearinghouses, they require more disk space and processing power than clerks. As the figure illustrates, clerks and servers can reside on the same node. Using the Distributed Name Service with DECmcc 5-3 Figure 5-1 Sample Configuration of DNS Clerks and Servers on a LAN +---+ +---+ +---+ +---+ | C | | C | |C/S| | C | +-+-+ +-+-+ +-+-+ +-+-+ | | | | o----+----+----+----+----+----+----+----+----+----o | | | | | +-+-+ +-+-+ +-+-+ +-+-+ +-+-+ | C | |C/S| | C | | C | | C | +---+ +---+ +---+ +---+ +---+ Legend: C = clerk, S = server Figure 5-2 shows how a DNS client, clerk, and server typically interact during a simple lookup. The clerk receives the lookup request from the client application (step 1) and checks its cache. Not finding the name there, the clerk contacts the server on Node 2 (step 2). The server finds the name in its clearinghouse and returns the requested information over the network to the clerk, which passes it on to the client application (steps 3 through 6). 5-4 Using the Distributed Name Service with DECmcc Figure 5-2 How a DNS Client, Clerk and Server Interact Node_1:: +---------------------------------------------------+ | | | User_1 <-----+ | | | | | +=v===================+<~~~~~~~~~~~+ | | User_2 <---> Client Application | | | | +=^===================+[1]-----+ | | | | | | | | User_3 <-----+ | [6] | | +=======+=============V===+ | | ... | cache | DECdns clerk | | | +=======+=============+===+ | | [2] ^ | +----------------------------------------- | | -+ | | | | | | | | Node_2:: | | +----------------------------------------- | | -+ | | [5] | | +=============v===+ | | -------------<----[3]+ DECdns server | | | /_______________\ +=================+ | | | Clearinghouse | ^ | | | | | | | +---------------+[4]~~~~~~~~~~~~~~~~~~~~~+ | | | +---------------------------------------------------+ Legend: [1], [2] and [3] = request path [4], [5] and [6] = response path 5.3 Structuring DNS Namespaces Namespaces are organized into hierarchically structured directories. Using the Distributed Name Service with DECmcc 5-5 The total collection of names that one or more DNS servers know about, look up, manage, and share is called a namespace. Any number of applications such as DECmcc, Distributed File Services, and the Remote System Manager, can use the same namespace. Planning a namespace involves organizing DNS names into a hierarchical structure of directories. DNS directories are conceptually similar to the directories in an operating system's file system. (This hierarchical structure of DNS directories is separate from the DECmcc entity class hierarchy.) DNS directories are a logical way to group names for DNS-specific management or usage purposes. You only need to create these directories once per namespace. The highest-level directory in the namespace is the root directory, denoted by a period (.). A DNS namespace containing the root directory is created when the DNS software is installed on a server node. A namespace administrator or server manager can then create and name other directories below the root. Any directory that has one or more levels of directory beneath it is considered the parent of the directory immediately below it in the namespace. Any directory that has one or more levels above it is considered a child of the directory immediately above it. A DECmcc global entity's registered name reflects the complete path through your namespace from the root directory to the entity entry in a particular directory. Therefore, all DNS names begin with a dot character (.), which denotes the root directory. For more information about namespace management, refer to the documentation for your DNS software, the Digital Distributed Name Service (DECdns) for DECnet/OSI users, or the VAX Distributed Name Service for users of earlier versions of DECnet. Figure 5-3 shows a simple directory structure based on hierarchically organized geographical names. The root directory (.) is the parent of the directories named West and FarEast. The FarEast directory is the parent of the Tokyo and Nagasaki directories. 5-6 Using the Distributed Name Service with DECmcc For small networks that do not expect much growth, a minimum number of directory levels is necessary in the namespace. For large networks, multiple directory levels provide greater flexibility in distributing, assigning access to, and managing many names. Distribution of names and distribution of DNS directories to DNS servers help to balance the workload on DNS servers. Figure 5-3 Sample Namespace Directory Hierarchy Root(.) ^ / \ / \ / \ West FarEast ^ / \ / \ / \ Tokyo Nagasaki 5.4 Planning to Set Up and Use DNS with DECmcc You should plan your namespace hierarchy and the access control groups that will have privileges to access it before you set up DNS for use with DECmcc. In order to use DNS with DECmcc, you must properly set up the DNS namespace for use with DECmcc. The steps you should follow to set up your namespace for DECmcc are as follows: 1. Plan the entity name structure and the corresponding hierarchy of DNS directory names. 2. Plan the access control groups. 3. Install the DNS software (if you have not already done so). 4. Create the access control groups. 5. Specify the privileges that access control groups have in the DNS root directory. 6. Specify who has privileges for adding and deleting members to the access control groups. Using the Distributed Name Service with DECmcc 5-7 7. Create the child directories required by DECmcc and any additional child directories you desire by using the supplied DNS Setup procedure. 8. Optionally, you can now use DNS Setup to add members to the .DNA_Registrar access control group; or you can add members to this group later, using the DNS Setup procedure. 9. Optionally, you can now use DNS Setup to create a command procedure that automatically registers all your DECnet Phase IV nodes. If you choose not to create the DECnet Phase IV registration procedure now, you can create it later using DNS Setup; or, later, you can use the DECmcc DECnet Phase IV Autoconfiguration application to automatically find and register DECnet Phase IV nodes in specific areas. 10.Specify the access privileges that access control groups have to the additional directories. 11.Verify DECmcc Interoperability with DNS. It is important to follow the steps in the order shown. In particular, you should plan the namespace hierarchy and correctly define and establish access control before creating the directories used by DECmcc. It is also important to plan your entity name structure before planning your directory structure and to plan your directory structure before creating the directories where you will register entities. Your directory structure should be consistent with the name structure you want. When you have registered an entity in one directory, you cannot register it in another directory, unless you deregister it from the first. In planning the namespace hierarchy, you should include all the child directories required by the client applications that will be using DNS. Refer to Section 5.5 for the directories that DECmcc and the DECmcc Autoconfiguration application use by default. You should also include in your plan any child directories that you want in your namespace, even though no client application requires them. For example, you might want to create local or site-specific directories. Then, you can 5-8 Using the Distributed Name Service with DECmcc create access control groups whose privileges apply only to those directories. Access control groups define the users who have specific access privileges to a directory and the objects in the directory. The access control groups in effect at the time of access to a DNS directory determine which users can perform which operations. The possible privileges are READ, WRITE, DELETE, TEST, and CONTROL. CONTROL is the privilege to change other access privileges. In order to register Node and Node4 entities in a directory, you need the CONTROL privilege for the objects in the directory. In addition to creating access control groups and defining access privileges for their members, you can define who has access privileges for adding and deleting members to the groups. The creator of a directory object or an access control group automatically has all privileges to the object or group. Access control defined for a directory is inherited by child directories created subsequently. Therefore, by defining the access control groups for the root directory before creating the DECmcc child directories, you ensure that access privileges for newly created directories are automatically propagated to the access control groups in the way you desire. You do not have to populate your access control groups at the time you create them. Therefore, your planning does not have to include the names of all the individuals in the groups. Subsequent topics in this chapter discuss the steps previously listed for setting up DNS for DECmcc. 5.5 Planning the DNS Directory Hierarchy for DECmcc You should start by planning your DNS directory hierarchy. DECmcc requires a number of directories in the DNS root. You might also need to create other directories in the root. Using the Distributed Name Service with DECmcc 5-9 You must plan your DNS directory hierarchy before you plan your access control groups. Begin by planning the entity name structure to which the directory hierarchy will correspond. Be sure to include the directories required by DECmcc and any other DNS client applications you are running. DECmcc requires that a number of directories be created in the root, in order for DECmcc to find them. The provided DNS Setup procedure creates these directories automatically. You should account for these directories in your planning, in order to define the privileges you want for different access control groups. The directories required by DECmcc are as follows: o .DNA_BackTranslation This directory is used to translate an address into a name. It contains one child directory for each IDP in the network. Each IDP child directory contains one child directory for each local area defined within that IDP. Each local area child directory contains one soft link for each node defined in that local area. The soft link for each node is created when you register the node. o .DNA_NodeSynonym This directory holds soft links used to translate a DECnet Phase IV node synonym to a DECmcc registered name. It contains a soft link for each node that has a DECnet Phase IV node synonym. Synonym soft links for nodes are created when you register the nodes. o .DTSS_GlobalTimeServers This is used by DECdts to hold the names and network locations of global time servers. DECmcc does not use this directory, but it is needed by other software. o .DNA_Node The command procedure created by function 2 of the DNS Setup menu, the DECnet Phase IV Autoconfiguration application, and other tools register DECnet Phase IV nodes in this directory by default. If you edit a tool to register Phase IV entities in a different directory, the directories must exist before you use the tool. o .MCC 5-10 Using the Distributed Name Service with DECmcc This directory holds objects containing information about the various installed DECmcc directors known to this namespace. o .MCC_global-entity-class-name_BackTranslation These directories contain soft links for every instance of a specified global entity registered by DECmcc. The DNS Setup procedure automatically sets up the following directories: - .MCC_Bridge_BackTranslation - .MCC_Concentrator_BackTranslation - .MCC_Sample_BackTranslation - .MCC_SNMP_BackTranslation - .MCC_Station_BackTranslation - .MCC_Terminal_Server_BackTranslation Some option packages require that you create a class- specific backtranslation directory in the root. The directory names have the form: .MCC_global-entity-class-name_BackTranslation The variable global-entity-class-name is the ASCII string for the registered name of a global entity class. See each package's Use manual or release notes for its DNS requirements and for the name of the global entity class(es). The DNS Setup procedure automatically creates .DNA_ BackTranslation child directories for all the possible areas in a DECnet Phase IV network. To support the translation of DECnet Phase IV addresses to addresses usable by systems running DECnet/OSI V5.0 or later, the names of these directories have the form: o .DNA_BackTranslation.IDP (where IDP is a string representing each Initial Domain Part as a hexadecimal number, for example, %X49; refer to Section 1.12.4, Obtaining Your Network Address Initial Domain Part in Chapter 1 for further details.) Using the Distributed Name Service with DECmcc 5-11 o .DNA_BackTranslation.IDP.area (where area is a string representing each area in your DECnet network as a four-digit hexadecimal number with leading zeros, for example, area 15 is .%X000F). Function 4 on the DNS Setup procedure menu allows you to create additional backtranslation directories for new areas you add to your network. Function 3 of the DNS Setup procedure allows you to create other directories, as you wish. If you plan to register SNMP entities, you should create a child directory specifically for them. You should also create a child directory for Domains, if you will be using the Iconic Map interface. If you plan to use the DECmcc Autoconfiguration applications to automatically register entities and add them to Iconic Map domains, the directories in the DNS root for Domains, DECnet Phase IV nodes, and SNMP hosts must match the directory paths specified in the Autoconfiguration prefix file. Th prefix file specifies the following directories by default: .DOMAIN, for Iconic Map domains, .DNA_Node, for DECnet Phase IV Autoconfiguration, and .IP, for IP Autoconfiguration. You can edit the prefix file if you wish to use other directories. Refer to the POLYCENER Framework and Applications Autoconfiguration and Autotopology Use manual for further information. 5.6 Planning and Creating DNS Access Control Groups Before creating your DNS directories, plan your access control groups. You can populate these groups later. Create access control groups for the root directory before you create child directories in the root. You should plan and create your access control groups before creating your DNS directories. When child directories are created, they inherit the access privileges already assigned to access control groups for the parent directory. 5-12 Using the Distributed Name Service with DECmcc For example, if you give access control group MCC_ MANAGERS TEST privileges for the root directory, that group automatically acquires TEST privileges for child directories subsequently created in the root. However, that group does not automatically acquire TEST privileges for child directories already existing in the root. If you want MCC_MANAGERS to have TEST privileges to already existing child directories, you have to assign them that privilege manually. Therefore, it is more efficient and reliable to plan and create the access control groups before the child directories. When you create the access control groups, they are empty. You can add and delete members from them at any time. Access groups can be members of other access groups; so you can add and delete members by groups. The DNS Setup procedure automatically creates an access control group named .DNA_REGISTRAR. Members of this group have READ, WRITE, DELETE, TEST and CONTROL access to all DNS directories and objects in the directories. You can use this access control group for people who control the namespace. You might want to define other access control groups. These groups could have all privileges to DNS directories and objects, or could be groups that have only READ access to the root directory but all access to local or site directories, or groups that have only READ and WRITE access to local or site directories, and so on. Access control groups for ordinary DECmcc users must have READ, WRITE, DELETE, TEST and CONTROL access to the objects in the DECmcc directories, but not necessarily to the directories. Use the DECmcc DNS Setup procedure to add and delete members to the .DNA_REGISTRAR access control group. You must use the DNS$CONTROL utility to create and manage other access control groups. The commands for creating and managing access control groups in the root directory are as follows. The keyword DEFAULT in the /FLAGS qualifier specifies that the privileges apply to the objects subsequently created in the directories, but not to the directories themselves. Using the Distributed Name Service with DECmcc 5-13 To execute these commands, you must have WRITE and CONTROL privileges to objects in the DNS root. The creator of the DNS namespace has all privileges to the DNS root and its objects. That person assigns privileges to others. For more information on DNS$CONTROL, refer to the documentation for your DNS software. 1. The following command calls DNS$CONTROL: $ MCR DNS$CONTROL 2. The following command creates the access control group .GLOBAL_ALL: DNS> CREATE GROUP .GLOBAL_ALL 3. The following command gives members of the .GLOBAL_ ALL access control group all access privileges to the objects subsequently created in the root directory and in all the child directories subsequently created in the root directory: DNS> ADD ACCESS .GLOBAL_ALL DIRECTORY . /FLAGS=(GROUP,DEFAULT) - /RIGHT = (R,W,T,C,D) 4. The following command gives members of the .GLOBAL_ ALL access control group all access privileges to the root directory and all the child directories subsequently created in it, but not to the objects in the directories: DNS> ADD ACCESS .GLOBAL_ALL DIRECTORY . /FLAGS=(GROUP) - /RIGHT=(R,W,T,C,D) 5. The following command gives members of the .GLOBAL_ALL access control group all access privileges to the group itself: DNS> ADD ACCESS .GLOBAL_ALL GROUP .GLOBAL_ALL /FLAGS=(GROUP) - /RIGHT=(R,W,T,C,D) 6. The following command gives an individual user all access privileges to the .GLOBAL_ALL group: DNS> ADD ACCESS PARIS::MARY GROUP .GLOBAL_ALL /RIGHT=(R,W,T,C,D) 7. The following command adds an individual to the .GLOBAL_ ALL group: DNS> ADD MEMBER PARIS::SMITH GROUP .GLOBAL_ALL /FLAGS=(GROUP) 5-14 Using the Distributed Name Service with DECmcc 8. The following command adds the members of access control group MCC_OPS to .GLOBAL_ALL: DNS> ADD MEMBER MCC_OPS GROUP .GLOBAL_ALL /FLAGS=(GROUP) 5.7 Setting Up the DNS Namespace If you selected the DNS namespace, DECmcc assists you in setting it up by providing a command procedure to partially automate the process. To use the DNS namespace, the DNS clerk and server must be running when DECmcc is running. The server, containing the appropriate clearinghouse, must be accessible. To verify that DNS software is installed and operational, look for the DNS$ADVER process on the client and the DNS$TA and DNS$BACK processes on the server. If these processes are not running, refer to your DNS installation documentation. The following steps describe how to configure the namespace for DECmcc, using the DNS Setup command procedure provided. o Enter the following command on the DNS server node: $ @MCC_SYSTEM:MCC_DNS_SETUP DECmcc namespace setup procedure Type a question mark (?) at any prompt to obtain help Press "CTRL/Z" at any prompt to exit from a function This command procedure sets up default directories for DECmcc, creates a directory for each global entity class for which DIGITAL provides an access module, and sets up DECnet/OSI-compatible .DNA_BackTranslation child directories for all the possible areas in a DECnet Phase IV network. The procedure also creates an access control group named .DNA_Registrar, which you can use to list those who have READ, WRITE, DELETE, TEST, and CONTROL access to all DNS directories and objects in the directories. The procedure sets WORLD READ and TEST access and WORLD READ and TEST default access privileges to the .MCC_ global-entity-class-name_BackTranslation directories it creates. For all other directories it creates, the procedure sets WORLD READ and TEST access and default access privileges. Using the Distributed Name Service with DECmcc 5-15 o The procedure prompts you for the name of the namespace to use. If you do not supply a name, the procedure uses the default established when the DNS software was installed. * Namespace to use (DEF=[DNS_default]): corp_ns The "corp_ns:" namespace will be used 5.7.1 Creating the DNS Directories Required for DECmcc DECmcc requires a number of directories in the DNS root directory. The DNS Setup procedure will create the required directories for you. The DNS Setup procedure informs you that the default namespace has not been set up with the required DECmcc directories: o .DNA_BackTranslation o .DNA_Node o .DNA_NodeSynonym o .DTSS_GlobalTimeServers o .MCC o .MCC_Bridge_BackTranslation o .MCC_Concentrator_BackTranslation o .MCC_Sample_BackTranslation o .MCC_SNMP_BackTranslation o .MCC_Station_BackTranslation o .MCC_Terminal_Server_BackTranslation The DNS Setup procedure asks if you want to create these directories. You should choose to create them the first time you run the DNS Setup procedure. After creating the .DNA_BackTranslation directory, the procedure creates the following DECnet/OSI-compatible child directories in it: o .DNA_BackTranslation.IDP (where IDP is a string representing each Initial Domain Part as a hexadecimal number, for example, %X49). 5-16 Using the Distributed Name Service with DECmcc o .DNA_BackTranslation.IDP.area (where area is a string representing each area in a DECnet Phase IV network as a four-digit hexadecimal number with leading zeros, for example, area 15 is .%X000F). The following example illustrates this step. Warning - the corp_ns: namespace has not yet been properly set up The following directories do not exist: corp_NS:.DNA_BackTranslation corp_NS:.DNA_NodeSynonym corp_NS:.DNA_Node corp_NS:.DTSS_GlobalTimeServers corp_NS:.MCC corp_NS:.MCC_Bridge_BackTranslation corp_NS:.MCC_Concentrator_BackTranslation corp_NS:.MCC_Sample_BackTranslation corp_NS:.MCC_SNMP_BackTranslation corp_NS:.MCC_Station_BackTranslation corp_NS:.MCC_Terminal_Server_BackTranslation * Initialize the namespace directories now (Y/N, DEF=Yes): Create the initial namespace directories Press CTRL-Z at any question to cancel the initialization 5.7.2 Creating the .DNA_Registrar Access Control Group The DNS Setup procedure sets the proper access control for the created directories. It also creates an access control group named .DNA_Registrar. The procedure prompts you to supply the names of the clearinghouses for the master and READ-ONLY replicas. For the master replica, the procedure uses the default established when the DNS software was installed. The clearinghouse for the READ-ONLY replica is optional. The procedure first creates an access control group named .DNA_Registrar that you can use to list those users who have READ, WRITE, DELETE, TEST, and CONTROL access to all DNS directories and objects in the directories. Using the Distributed Name Service with DECmcc 5-17 The following example illustrates this step. * Clearinghouse for master replica (DEF=[DNS_default]): corp_ch * Clearinghouse for read-only replica (DEF=[none]): The DNS directories and group will now be created. This might take up to 33 minutes or more, depending on the speed of the DNS server system, and the amount of traffic on the network. Creating the ."DNA_Registrar" group Setting READ,WRITE,DELETE,TEST,CONTROL access for corp_ns:.DNA_Registrar Setting READ,TEST access for WORLD (corp_ns:.*...) Creating the corp_ns:."DNA_BackTranslation" directory (in clearinghouse corp_ns:corp_ch) Setting READ,WRITE,DELETE,TEST,CONTROL access for corp_ns:.DNA_Registrar Setting READ,WRITE,DELETE,TEST,CONTROL default access for corp_ns:.DNA_Registrar Setting READ,TEST access for WORLD (corp_ns:.*...) Setting READ,TEST default access for WORLD (corp_ns:.*...) Creating the corp_ns:."DNA_BackTranslation".%X49 directory (in clearinghouse corp_ns:corp_ch) Setting READ,WRITE,DELETE,TEST,CONTROL access for corp_ns:.DNA_Registrar Setting READ,WRITE,DELETE,TEST,CONTROL default access for corp_ns:.DNA_Registrar Setting READ,TEST access for WORLD (corp_ns:.*...) Setting READ,TEST default access for WORLD (corp_ns:.*...) Creating the ."DNA_BackTranslation".%X49.%X0001 directory (in clearinghouse corp_ch) . . . Creating the corp_ns:."MCC_Station_BackTranslation" directory (in clearinghouse corp_ns:corp_ch) Setting READ,WRITE,DELETE,TEST,CONTROL access for corp_ns:.DNA_Registrar Setting READ,WRITE,DELETE,TEST,CONTROL default access for corp_ns:.DNA_Registrar Setting READ,WRITE,TEST access for WORLD (corp_ns:.*...) Setting READ,TEST default access for WORLD (corp_ns:.*...) DNS namespace setup is complete * Press RETURN to continue The following were created: 5-18 Using the Distributed Name Service with DECmcc Group: corp_ns:.DNA_Registrar Directory: corp_ns:.DNA_BackTranslation . . . * Press RETURN to continue 5.7.3 Creating Additional DNS Directories Use the DNS Setup procedure to create additional directories, if you need them. In particular, access modules you purchase in addition to those supplied with DECmcc might require special directories. Function 3 on the DNS Setup procedure menu allows you to create additional directories in the DNS root directory. Some option packages require that you create a class- specific backtranslation directory in the root directory. The directory names have the form: .MCC_global-entity-class-name_BackTranslation where global-entity-class-name is the registered name of a global entity class. Refer to each option package's Use manual(s) or release notes for its DNS requirements and for the name of its global entity class(es). The DNS Setup procedure prompts you to supply the names of the clearinghouses for the master and READ-ONLY replicas. For the master replica, the procedure uses the default you specified earlier. The clearinghouse for the READ-ONLY replica is optional. You should use the DNS Setup procedure to create all your DNS directories. The procedure automatically sets WORLD READ and TEST access and WORLD READ and TEST default access privileges to the .MCC_global-entity-class-name_ BackTranslation directories it creates. If you intend to register SNMP entities, be sure to create a directory in the DNS root directory for them. If you intend to use the Iconic Map interface, create a directory in the root for Domains. Using the Distributed Name Service with DECmcc 5-19 Function 4 on the DNS Setup procedure menu allows you to create additional back translation directories for new areas you add to your network, and Function 8 allows you to delete directories from the namespace. The following example illustrates this step. Choose one of the following functions by specifying its function number, or request help by typing HELP or a question mark (?) 0. Exit 1. Create the initial namespace directories 2. Create a command file to help register existing Phase IV nodes 3. Create additional directories in the name space 4. Create back translation directories for new network IDPs and areas 5. Add members to the access control group 6. Remove members from the access control group 7. Show members of the access control group 8. Delete directories in the name space * Function to execute: 3 Create additional directories for node names Press CTRL-Z when done * Directory name: .paris * Clearinghouse for master replica (Def=corp_ch): * Clearinghouse for read-only replica (Def=[none]): Creating the corp_ns:."paris" directory (in clearinghouse corp_ns:corp_ch) Setting READ,WRITE,DELETE,TEST,CONTROL access for corp_ns:.DNA_Registrar Setting READ,WRITE,DELETE,TEST,CONTROL default access for corp_ns:.DNA_Registrar Setting READ,TEST access for WORLD (corp_ns:.*...) Setting READ,TEST default access for WORLD (corp_ns:.*...) * Directory name: Use Ctrl/Z to exit. 5-20 Using the Distributed Name Service with DECmcc 5.7.4 Managing the .DNA_Registrar Access Control Group You can use the DNS Setup procedure to add, delete, and display members of the .DNA_Registrar access control group. Functions 5, 6, and 7 on the DNS Setup procedure menu allow you to manage the .DNA_Registrar access control group. Members of that group can have READ, WRITE, DELETE, TEST, and CONTROL access to all DNS directories and objects in the directories. Use function 7 to show any users who are already in the .DNA_Registrar access control group. Use function 5 if you want to add members to the group. The setup procedure prompts you to specify the member to be added. Supply a user name in the form node::user, where node is a DECnet Phase IV or later node name. Function 6 on the DNS Setup procedure menu deletes members from the group. The following example illustrates these steps. Choose one of the following functions by specifying its function number, or request help by typing HELP or a question mark (?) . . . 5. Add members to the access control group 6. Remove members from the access control group 7. Show members of the access control group * Function to execute: 7 Show members of the access control group Group name ."DNA_Registrar" No information * Press RETURN to continue Using the Distributed Name Service with DECmcc 5-21 Choose one of the following functions by specifying its function number, or request help by typing HELP or a question mark (?) . . . 5. Add members to the access control group 6. Remove members from the access control group 7. Show members of the access control group * Function to execute: 5 Add members to the access control group Specify the members to be added, one at a time Press CTRL-Z when finished * Member: paris::system Adding member corp_ns:.DNS$IV.paris.system to ."DNA_Registrar" * Member: . . . * Function to execute: 7 Show members of the access control group Group name ."DNA_Registrar" Member ____ corp_NS:.dns$iv.paris.system * Press RETURN to continue 5.7.5 Creating a Procedure to Register DECnet Phase IV Nodes The DNS Setup procedure can create a command procedure for automatically registering DECnet Phase IV nodes with DECmcc. The DECnet Phase IV Autoconfiguration Application can also register DECnet Phase IV nodes automatically. To create the registration procedure, select function 2 from the menu. The DNS Setup procedure prompts you to supply a name for the file. The DNS Setup procedure creates the file you name and one secondary command procedure for each area in the network. The secondary procedures have the same name as the main registration procedure with "_nn" appended. "nn" is the number of the area. For example: 5-22 Using the Distributed Name Service with DECmcc PHASE4_REGISTRATION.COM_09 Each file created is placed in the MCC_COMMON: directory by default. The primary and secondary registration procedures place the nodes they register in the .DNA_Node directory. The registered name of each node reflects the full DNS directory hierarchy of the node starting from the root. Unless you edit the secondary procedures, the registered name of each node will have the form: root_NS:.DNA_NODE.node4 If you want a different child directory hierarchy in the registered name, you can edit the secondary procedures to replace .DNA_NODE with any child directory path you wish. The child directories you choose must exist before you execute the procedures. You can also use the DECnet Phase IV Autoconfiguration application to automatically register DECnet Phase IV nodes. The DNS Setup procedure and the Autoconfiguration application use different methods for finding nodes to register. The DNS Setup procedure registers all the DECnet Phase IV nodes known to the local node's database. The Autoconfiguration application registers all the DECnet Phase IV nodes in an area you specify, using the connectivity information known to the area routers. DECmcc also provides the IP Autoconfiguration application for registering SNMP entities. Refer to the POLYCENTER Framework and Applications Autoconfiguration and Autotopology Use manual for further information on the Autoconfiguration applications. You should use one of the supplied automated methods when registering multiple entities. ________________________ Note ________________________ Before using any method for automatically registering entities, ensure that DECmcc and DNS are properly set up to work together, see Section 5.8, Verifying DECmcc and DNS Interoperability. ______________________________________________________ Using the Distributed Name Service with DECmcc 5-23 The following example illustrates this step. If this is the first time you have set up the namespace directories, you should use MCC_DNS_SETUP to: - Create a command file to automatically register previously defined Phase IV nodes, and then execute that command file. . . . * Press RETURN to continue Choose one of the following functions by specifying its function number, or request help by typing HELP or a question mark (?) 0. Exit 1. Create the initial namespace directories 2. Create a command file to help register existing Phase IV nodes 3. Create additional directories in the name space 4. Create back translation directories for new network IDPs and areas 5. Add members to the access control group 6. Remove members from the access control group 7. Show members of the access control group * Function to execute: 2 Create a command file to help register existing Phase IV nodes Press CTRL-Z at any question to cancel the function * Name of file to create: mcc_dns_node_registration.com Creating the Phase IV node registration command file. The ".DNA_Node" directory will be used for all node registrations. The information used to create this command file will be read from the Phase IV permanent data file: SYS$SYSTEM:NETNODE_REMOTE.DAT This data file contains definitions for all Phase IV nodes that were entered using the "NCP DEFINE NODE" command. Working ... The resulting files have been named: Primary command file to execute: SYS$COMMON:[MCC]MCC_DNS_NODE_REGISTRATION.COM 5-24 Using the Distributed Name Service with DECmcc Secondary command files, one for each network area "nn" SYS$COMMON:[MCC]MCC_DNS_NODE_REGISTRATION.COM_nn * Press RETURN to continue 5.7.6 Specifying Privileges for any Additional Access Control Groups After you have created your DNS directory hierarchy, you should use the DNS$CONTROL utility to assign access privileges to any additional access control groups you have created. When you give a group privileges in a directory, the group automatically acquires the same privileges in any child directory subsequently created. The group does not automatically acquire privileges in child directories that already exist. The following example illustrates commands for invoking DNS$CONTROL and defining an access control group's privileges in a directory, the privileges later child directories will inherit. The keyword DEFAULT in the /FLAGS qualifier specifies that the privileges apply to the objects subsequently created in the directories, but not to the directories themselves. 1. The following command calls DNS$CONTROL: $ MCR DNS$CONTROL 2. The following command gives the .MCC_OPS access control group all privileges to the objects subsequently created in the .MCC child directory and in all its subsequently created child directories: DNS> ADD ACCESS .MCC_OPS DIR .MCC /FLAGS = (GROUP,DEFAULT) - /RIGHT=(R,W,T,C,D) 3. The following command gives the .MCC_OPS access control group all access privileges to the .MCC child directory and all the child directories subsequently created in it, but not to the objects in the directories: DNS> ADD ACCESS .MCC_OPS DIR .MCC /FLAG = (GROUP) /RIGHT=(R,W,T,C,D) 4. The following command gives the .MCC_OPS access control group all access privileges to the object .dna_ node.paris in the current directory: Using the Distributed Name Service with DECmcc 5-25 DNS> ADD ACCESS .MCC_OPS OBJECT .DNA_NODE.PARIS /FLAG = (GROUP) - /RIGHT=(R,W,T,C,D) 5.8 Verifying DECmcc and DNS Interoperability When you have finished setting up the DNS namespace, you should verify that DECmcc and DNS are properly configured to work together. Do this before you do anything else with DECmcc. When you have finished setting up the DNS namespace, the first thing you should do is to start DECmcc and attempt to register a network addressable entity using the Forms and Command Line (FCL) interface. Successful registration will tell you that DECmcc and DNS are communicating properly. Unsuccessful registration can be due to the absence of a required DNS directory or to a failure to communicate with the DNS server. An error message will indicate which. If a directory is missing, run the DNS Setup procedure again. Failure to communicate with the DNS server can occur for a variety of reasons. Refer to Section 5.9 for a list of some of the more common reasons. Since the problem might be temporary, you should try to register the entity again, before looking for the reason. The following example assumes that your local node is Node4 Paris. The OPERATION = PLAN argument specifies that the DECmcc Register directive only places the name .Paris in the DNS namespace. o Start DECmcc. The FCL interface is the default. $ MANAGE/ENTERPRISE MCC> o Register your local node, for example, Node4 Paris. MCC> REGISTER NODE4 .PARIS OPERATION = PLAN NODE4 PARIS AT 3-MAR-1995 Registration successful MCC> 5-26 Using the Distributed Name Service with DECmcc 5.9 Troubleshooting the DNS Namespace Problems running DECmcc can occur if the DNS namespace is not properly set up or if you cannot communicate with the DNS server. o You can use the following DNS$CONTROL command to determine that the required DNS directories exist: $ MCR DNS$CONTROL SHOW DIR . KNOWN CHILD DECmcc requires the following child directories in the DNS root: - .DNA_BackTranslation - .DNA_Node - .DNA_NodeSynonym - .DTSS_GlobalTimeServers - .MCC - .MCC_Bridge_BackTranslation - .MCC_Concentrator_BackTranslation - .MCC_Sample_BackTranslation - .MCC_SNMP_BackTranslation - .MCC_Station_BackTranslation - .MCC_Terminal_Server_BackTranslation An access module you add might require a directory of the following form in the root: .MCC_[global_entity_class_name]_BackTranslation If a directory is missing, run the DNS Setup procedure again. o The MCC_SYSTEM:MCC_DNS_SETUP.COM procedure creates child directories for the .DNA_BackTranslation directory. Use the following DNS$CONTROL command to ensure that child directories exist for the IDP that you are using: $ MCR DNS$CONTROL SHOW DIR .DNA_BACKTRANSLATION KNOWN CHILD Using the Distributed Name Service with DECmcc 5-27 o DECmcc must be able to communicate with the DNS server. If not, you receive an error message. Some of the more common reasons for failure to communicate with the server are listed below. Since the problem might be temporary, you should retry the directive that failed before looking for the reason. If any of the following problems occur when the DNS server is your local system, see your system manager. If the DNS server is a remote system, see the DNS manager. - The DNS server has not been started. - The link to the DNS server went down. - No more links are available to the DNS server. - No more processes are available on the DNS server. - The requester does not have the correct DNS access privileges. - The DNS process on the server had a low priority, causing a timeout of the link. - There is a problem with the DNS server system. 5-28 Using the Distributed Name Service with DECmcc A _________________________________________________________________ Required Quotas and Parameter This appendix lists the process quotas and SYSGEN parameters required for installing DECmcc when you have the VMS layered products required for various DECmcc options on your system. In the following tables, the recommended values assume your system has all these layered products. Except where noted, the recommended value is not a total of the values for each product, but is a large enough value for any of the products. Table A-1 lists the process quotas for the products. Table_A-1_Product_Process_Quotas___________________________ Quotas___DNS____BMS____Rdb____CDD____DTR____Recommended____ Fillm 30 200 150 60 30 400 Bytlm 20000 65000 20480 25000 BIOlm 100 18 100 DIOlm 100 18 100 ASTlm 200 24 200 WSquo 4096 4096 TQElm 300 300 WSextent 16000 16000 Enqlm 2000 2000 2000 600 2000 Pgflquo_________150000_20000__40000_________150000_________ Table A-2 lists the required SYSGEN parameters for the products. Required Quotas and Parameter A-1 Table_A-2_Product_SYSGEN_Parameter_________________________ Parameters_____DNS_BMS_Rdb___CDD___DTR_GRPH_UCX_Recommended CHANNELCNT 512 512[1] CLISYMTBL 250 250 250 250 250 GBLPAGES[2] 334 76181396 2120 843 100 196014371[4] GBLSECTIONS[2] 12 55 80 106 6 5 27 290[5] LOCKIDTBL_MAX 20482048 2048 2048 PROCSECTCNT 200 64 200 REHASHTBL 512 512 512 512 VIRTUALPAGECNT 2000 40000[3] MAXBUF 12001200 1200 PAGEDYN 1000441000448 1000448 NPAGEDYN 900096900096 900096 GBLPAGFIL 12200 12200 12200 CTLPAGES 32 32 32 [1]Minimum:_the_actual_value_must_be_greater_than_the______ largest Fillm on the system. [2]The value must be equal to, or greater than the total of the values for each product. [3]Minimum: the actual value must be greater than the largest Pgflquota on the system. [4]This value also includes 220 GBLPAGES for TCP/IP DA and 1292 GBLPAGES for TSAM. These global pages are used by EMS only. If you have a number of other images installed, you might want to increase this value. [5] This value also includes 2 GBLSECTIONS for TCP/IP DA, and 3 GBLSECTIONS for TSAM. ___________________________________________________________ After installing DECmcc, you may want to retune your system parameters. Refer to Section 4.4 for more information. A-2 Required Quotas and Parameter B _________________________________________________________________ Time Differential Factors (TDFs) This appendix lists TDF's by region. Within each region, specific areas are listed alphabetically. Most areas have two TDFs. The "UTC Offset" column lists the TDFs for "Standard" or winter time. For example, a TDF of -5:00 specifies US Eastern Standard Time. When an area has only one TDF, it is listed in the "UTC Offset column. The "Summer Time" column lists the TDFs for "Daylight" or summer time and when to change back to Standard or winter time. The values shown are in the time from which the change is made: the values in "Change to Summer Time" column are in Standard or winter time; the values in the "Change Back to UTC" column are in Daylight or summer time. For example, you change to US Eastern Daylight time at 2:00 a.m. US Eastern Standard Time; and you change back to US Eastern Standard Time at 2:00 a.m. US Eastern Daylight time. Table B-1 lists European TDFs. Table B-2 lists North American TDFs. Table B-3 lists Central and South American TDFs. Table B-4 lists African TDFs. Table B-5 lists Asian TDFs. Table B-6 lists South Pacific TDFs. Table B-7 lists Antarctica TDFs. Time Differential Factors (TDFs) B-1 Table_B-1_Region:_Europe___________________________________ UTC Summer Change to Change Back to Zone_________Offset_Time___Summer_Time_____UTC_____________ Eastern +2:00 +3:00 3:00 a.m. 3:00 a.m. Europe last Sunday in last Sunday March. in September. Great +0:00 +1:00 1:00 a.m. 1:00 a.m. Britain/Eire last Sunday in last Sunday March. in October. Iceland +0:00 Middle +1:00 +2:00 2:00 a.m. 2:00 a.m. Europe last Sunday in last Sunday March. in September. Poland +1:00 +1:00 1:00 a.m. 1:00 a.m. last Sunday in last Sunday March. in September. Turkey +3:00 +4:00 1:00 a.m. 1:00 a.m. last Sunday in last Sunday March. in September. Western +0:00 +1:00 1:00 a.m. 1.00 a.m. Europe last Sunday in last Sunday ___________________________March.__________in_September.___ Table_B-2_Region:_North_America____________________________ UTC SummerChange to Change Back to Zone___________OffsetTime__Summer_Time_____UTC_____________ Canada/Atlantic- - 2:00 a.m. 2:00 a.m. 4:00 3:00 first Sunday last Sunday in April. in October. Canada/Central - - 2:00 a.m. 2:00 a.m. 6:00 5:00 first Sunday last Sunday in April. in October. Canada/Eastern - - 2:00 a.m. 2:00 a.m. 5:00 4:00 first Sunday last Sunday in April. in October. (continued on next page) B-2 Time Differential Factors (TDFs) Table_B-2_(Cont.)_Region:_North_America____________________ UTC SummerChange to Change Back to Zone___________OffsetTime__Summer_Time_____UTC_____________ Canada/East - Saskatchewan 6:00 Canada/Mountain- - 2:00 a.m. 2:00 a.m. 7:00 6:00 first Sunday last Sunday in April. in October. Canada/Newfound-and - 2:00 a.m. 2:00 a.m. 3:30 2:30 first Sunday last Sunday in April. in October. Canada/Pacific - - 2:00 a.m. 2:00 a.m. 8:00 7:00 first Sunday last Sunday in April. in October. Canada/Yukon - - 2:00 a.m. 2:00 a.m. 9:00 8:00 first Sunday last Sunday in April. in October. USA/Alaska - - 2:00 a.m. 2:00 a.m. 9:00 8:00 first Sunday last Sunday in April. in October. USA/Aleutian - - 2:00 a.m. 2:00 a.m. 10:00 9:00 first Sunday last Sunday in April. in October. USA/Arizona - 7:00 USA/Central - - 2:00 a.m. 2:00 a.m. 6:00 5:00 first Sunday last Sunday in April. in October. USA/Eastern - - 2:00 a.m. 2:00 a.m. 5:00 4:00 first Sunday last Sunday in April. in October. USA/East - Indiana 5:00 USA/Hawaii - 10:00 (continued on next page) Time Differential Factors (TDFs) B-3 Table_B-2_(Cont.)_Region:_North_America____________________ UTC SummerChange to Change Back to Zone___________OffsetTime__Summer_Time_____UTC_____________ USA/Michigan - - 2:00 a.m. 2:00 a.m. 5:00 4:00 first Sunday last Sunday in April. in October. USA/Mountain - - 2:00 a.m. 2:00 a.m. 7:00 6:00 first Sunday last Sunday in April. in October. USA/Navajo - - 2:00 a.m. 2:00 a.m. 7:00 6:00 first Sunday last Sunday in April. in October. USA/Pacific - - 2:00 a.m. 2:00 a.m. 8:00 7:00 first Sunday last Sunday in April. in October. USA/Pacific - - 2:00 a.m. 2:00 a.m. [1] 8:00 7:00 first Sunday second Sunday in April. n November. USA/Samoa - 11:00 [1]Presidential_election_years.____________________________ ___________________________________________________________ Table_B-3_Region:_Central_and_South_America________________ UTC Summer Change to Change Back to Zone_________Offset_Time___Summer_Time_____UTC_____________ Brazil/Acre -5:00 -4:00 2:00 a.m. 2:00 a.m. second fourth Saturday in Saturday in February. October. Brazil/DeNoro-2:00 -1:00 2:00 a.m. 2:00 a.m. second fourth Saturday in Saturday in February. October. (continued on next page) B-4 Time Differential Factors (TDFs) Table_B-3_(Cont.)_Region:_Central_and_South_America________ UTC Summer Change to Change Back to Zone_________Offset_Time___Summer_Time_____UTC_____________ Brazil/East -3:00 -2:00 2:00 a.m. 2:00 a.m. second fourth Saturday in Saturday in February. October. Brazil/West -4:00 -3:00 2:00 a.m. 2:00 a.m. second fourth Saturday in Saturday in February. October. Chile/Easter -6:00 -5:00 12:00 a.m. 2:00 a.m. second Island second Sunday Sunday in March. in October. Chile/Regiona-4:00 -3:00 12:00 a.m. 2:00 a.m. second second Sunday Sunday in March. in October. Cuba -5:00 -4:00 12:00 a.m. 2:00 a.m. second Sunday second Sunday in May. in October. Jamaica -5:00 -4:00 12:00 a.m. 2:00 a.m. first Sunday last Sunday in April. in October. Mexico/BajaNo-8:00 -7:00 2:00 a.m. 3:00 a.m. first Sunday last Sunday in April. in October. Mexico/BajaSu+2:00 Mexico/Genera-6:00_________________________________________ Time Differential Factors (TDFs) B-5 Table_B-4_Region:_Africa___________________________________ UTC Summer Change to Change Back to Zone_________Offset_Time___Summer_Time_____UTC_____________ Egypt[1] +2:00 +3:00 2:00 a.m. 2:00 a.m. 303rd 152nd day in day in the year. the year. Libia[1] +2:00 +3:00 2:00 a.m. 2:00 a.m. 303rd 121st day in day in the year. the year. [1]Days_are_specified_as_Julian_day_n_(1_<_n_<_365)________ skipping February 29 ___________________________________________________________ Table_B-5_Region:_Asia_____________________________________ UTC Summer Change to Change Back to Zone_________Offset_Time___Summer_Time_____UTC_____________ Hong Kong +8:00 Iran +3:30 +4:30 2:00 a.m. 2:00 a.m. last Sunday in third Sunday March. in September. Israel +3:00 +4:00 2:00 a.m. 2:00 a.m. fourth third Sunday Saturday in in April. August. Japan +9:00 PRC +8:00 +9:00 2:00 a.m. 2:00 a.m. second Sunday second Sunday in April. in September. Singapore +8:00 ROC +8:00 ROK +9:00 +10:00 2:00 a.m. 3:00 a.m. second Sunday second Sunday ___________________________in_May._________in_October._____ B-6 Time Differential Factors (TDFs) Table_B-6_Region:_South_Pacific____________________________ UTC SummerChange to Change Back to Zone___________OffsetTime__Summer_Time_____UTC_____________ Australia/North+9:00 Australia/NSW +10:00+11:002:00 a.m. 3:00 a.m. first last Sunday in Sunday in March. October. Australia/Queen+10:00 [1] Australia/Queen+10:00+11:002:00 a.m. 3:00 a.m. first (e.g. NSW) last Sunday in Sunday in March. October. Australia/South+9:30 +10:302:00 a.m. 3:00 a.m. third fourth Sunday Sunday in March. in October. Australia/Tasma+10:00+11:002:00 a.m. 3:00 a.m. third fourth Sunday Sunday in March. in October. Australia/Victo+10:00+11:002:00 a.m. 3:00 a.m. third fourth Sunday Sunday in March. in October. Australia/West +8:00 Australia/NSW +12:00+13:002:00 a.m. 3:00 a.m. first last Sunday in Sunday in March. October. [1]Standard_Time_only______________________________________ ___________________________________________________________ Table_B-7_Region:_Antarctica_______________________________ UTC Summer Change to Change Back to Zone_________Offset_Time___Summer_Time_____UTC_____________ Antarctica___0:00__________________________________________ Time Differential Factors (TDFs) B-7 C _________________________________________________________________ Updating DECmcc From a Previous Version This appendix lists steps you should perform before updating your current DECmcc system to Version 3.0. C.1 Steps You Must Perform Before Upgrading to DECmcc V3.0 The three steps you should perform before upgrading to DECmcc V3.0 are: 1. Identify DECmcc jobs to stop on the system. 2. Detect and record which optional modules are present. 3. Record private MIBs that have been added to the system Instructions for performing these steps follow. 1. Identify DECmcc jobs on the system. To install DECmcc, you must make sure no DECmcc processes are running. a. Enter the Show System command and look for any processes beginning with MCC_. The presence of these processes indicates that DECmcc is running on your system. In the following example, one DECmcc process is running on your system: MCC_EVC_SINK. $ SHOW SYSTEM VAX/VMS V5.5-2 on node PARIS 20-JAN-1995 16.13.09.72 Uptime 13 23:17:42 Pid Process Name State Pri I/O CPU Page flts Ph.Mem . . . 00000066 MCC_EVC_SINK COM 3 93 0 00:51:28.79 4799 338 . . . Updating DECmcc From a Previous Version C-1 b. If there are other people who use DECmcc on the system, you should check that they have exited DECmcc. c. To stop these processes, enter the corresponding Pid's for the processes on your system. Using the preceding example, the command is: $ STOP PROCESS/ID=00000066 2. Detect and record optional modules. The installation of POLYCENTER Network Manager 400 packages requires that optional modules be reinstalled. After installing DECmcc V3.0, you must reinstall the optional modules, ensuring that the versions of the optional module packages are compatible with DECmcc V3.0. The following commands will assist you in identifying what optional modules have been previously installed on your system. $ DEFINE/USER_MODE SYS$OUTPUT MCC_SNMP_MIB.LOG $ MANAGE/TOOL/DIRECTORY SHOW $ TYPE MCC_SNMP_MIB.LOG Class (1) : NODE 1 Class (1) : MCC 7 Class (1) : DOMAIN 8 Class (1) : BRIDGE 9 Class (1) : STATION 11 Class (1) : NODE4 12 Class (1) : SAMPLE 15 Class (1) : SNMP 18 Class (1) : COLLECTOR 25 Class (1) : FDDI-STATION 37 Class (1) : COMMON 52 Class (1) : CIRCUIT 53 Class (1) : CONCENTRATOR 330 Class (1) : REFERENCE 332 Class (1) : GENERAL 16382 $ C-2 Updating DECmcc From a Previous Version If the following items appear in the preceding example, the DECmcc ELM product is installed on your system. Class (1) : BRIDGE 9 Class (1) : FDDI-STATION 37 Class (1) : CONCENTRATOR 330 If the following item is not present on your system, then you have only the POLYCENTER Framework (formerly Director) kit installed. Class (1) : COLLECTOR 25 3. Determine and record private MIB extensions. The installation of POLYCENTER Framework or POLYCENTER Network Manager packages requires that you reload the private MIB extensions after installing DECmcc V3.0. Enter the following commands to display private MIB extensions that have been previously loaded on your system, and send the output to a file for future reference. $ DEFINE/USER_MODE SYS$OUTPUT MCC_CLASS.LOG $ MANAGE/TOOL/DIRECTORY SHOW CLASS SNMP $ TYPE MCC_CLASS.LOG . . . Definition (3) : INSTANCE_DATATYPE Subclass (2) : INTERFACE 2 Subclass (2) : ATTABLE 3 Subclass (2) : IP 4 Subclass (2) : ICMP 5 Subclass (2) : TCP 6 Subclass (2) : UDP 7 Subclass (2) : EGP 8 Subclass (2) : SNMP 11 Subclass (2) : EXP_RMON 527 Subclass (2) : PROTEON 5001 Subclass (2) : WELLFLEET 5018 Subclass (2) : SUN 5042 Subclass (2) : SYNOPTICS 5045 Subclass (2) : CHIPCOM 5049 Attribute (5) : SYSDESCR 1 Attribute (5) : SYSOBJECTID 2 . Updating DECmcc From a Previous Version C-3 . . $ Your private MIB extensions in the preceding example begin with the item after SNMP 11, and end prior to the first Attribute. In this example, the first private MIB extension is EXP_RMON, and the last private MIB extension is CHIPCOM 5049. C.2 Steps You Must Perform After Upgrading to DECmcc V3.0 After installing DECmcc V3.0, perform the following steps: 1. Identify DECmcc jobs on the system. Installing DECmcc V3.0 might have started some processes on your system. Check with your system and stop them before continuing. Refer to Step 1 in Section C.1 for instructions. 2. Install optional modules. Reinstall the optional modules as listed in Step 2 in Section C.1. 3. Load the private MIB extensions. For instructions on loading private MIB extensions, refer to the POLYCENTER Framework and Applications TCP/IP SNMP Access Module Use manual. C-4 Updating DECmcc From a Previous Version