DECcmi_for_DIGITAL_UNIX________________________ Installation and Configuration Guide Order Number: AA-QENTF-TE This document contains information on how to install the DECcmi software on the DIGITAL UNIX operating system. Revision/Update Information: V2.17.1. This edition supersedes the V2.16 edition Operating System: DIGITAL UNIX Software Version: DECcmi V2.17 ________________________________________________________________ December 1997 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 and copied only in accordance with the terms of such license. Digital Equipment Corporation assumes no responsibility for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. © Digital Equipment Corporation 1997. All rights reserved. Printed in Europe. Trademarks: AlphaGeneration, DEC, DECnet, DECros, DECwindows, OpenVMS, ULTRIX and VAX are trademarks of Digital Equipment Corporation. Sun is a registered trademark of Sun Microsystems, Inc. SunLink is a registered trademark of Sun Microsystems, Inc. Solaris is a registered trademark of Sun Microsystems, Inc. X/Open is a trademark of the X/Open Company Limited. OSIAM is a trademark of MARBEN Produit. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. DIGITAL UNIX V3.2 is an X/Open UNIX 93 branded product. DIGITAL UNIX V4.0 is a UNIX 95 branded product. This document is available on CD-ROM. DIGITAL This document was prepared using VAX DOCUMENT, Version 2.1. ________________________________________________________________ Contents ................................................... vii Preparing for DECcmi Software Installation 1.1 Pre-Installation Procedure....................... 1-1 1.2 Licensing DECcmi on Your System.................. 1-2 1.3 DECnet-Plus and X.25............................. 1-2 1.3.1 Prerequisites ................................. 1-2 1.3.2 DECnet-Plus Configuration ..................... 1-3 1.3.3 X.25 Configuration ............................ 1-3 1.3.4 OSI Transport Templates ....................... 1-3 1.3.5 Verifying the DECnet-Plus Configuration ....... 1-4 1.3.6 Tracing DECnet-Plus Activity .................. 1-5 Installing the DECcmi Software 2.1 Installation of DECcmi Files..................... 2-1 2.2 DECcmi Environment Variables..................... 2-1 2.2.1 Mandatory Variables ........................... 2-1 2.2.2 Optional Variables ............................ 2-2 2.3 Modifying the DECcmi Default Configuration....... 2-3 2.4 Defining the Remote NSAP Addresses............... 2-7 2.4.1 LABEL Mode .................................... 2-7 2.4.2 NSAP Mode ..................................... 2-8 2.4.3 Coexistence of LABEL and NSAP Modes ........... 2-9 2.4.4 Common Syntax Rules ........................... 2-9 2.5 Using the Syslogd Utility........................ 2-10 Verifying the Installation 3.1 The Installation Verification Program............ 3-1 3.2 Preparing to Run the IVP......................... 3-1 3.3 Running the IVP.................................. 3-2 3.4 Errors from the IVP.............................. 3-2 Starting and Stopping the DECcmi Server 4.1 Starting DECcmi.................................. 4-1 4.2 Stopping DECcmi.................................. 4-2 4.3 DECcmi Administrative Account.................... 4-2 iii 5 Compiling and Running Example Programs 5.1 Compiling CMIS and ROS Examples Programs......... 5-1 5.2 Preparing to Run the Example Programs............ 5-1 5.3 Running CMIS and ROS Example Programs............ 5-2 6 Plugging your Network Application Program 6.1 Linking your Network Application Program with the CMIS or ROS API.................................. 6-1 6.2 Checking the DECcmi Version Number............... 6-1 7 DECcmi Limitations 7.1 DECcmi Memory Limitations........................ 7-1 7.1.1 Shared Memory between APIs and the DECcmi Server......................................... 7-1 7.1.2 Memory Buffers used Internally by the DECcmi Server......................................... 7-1 7.2 Maximum Number of Associations................... 7-2 7.3 Maximum Size of User Data........................ 7-3 7.4 Presentation Address Format...................... 7-3 7.5 Tuning DECcmi.................................... 7-3 A List of DECcmi Files B Sample Logs as Examples Examples B-1 DECcmi Kit Installation - No Previous DECcmi Kit Installed.................................. B-1 B-2 DECcmi Kit Installation - Previous DECcmi Kit Installed...................................... B-3 B-3 Running the IVP ............................... B-3 B-4 Starting the DECcmi Server - No Server Process Currently Running.............................. B-4 B-5 Starting the DECcmi Server - Server Process Already Running................................ B-5 B-6 Stopping the DECcmi Server .................... B-5 B-7 The DECcmi Standard Profile ................... B-6 B-8 Removing the DECcmi Kit - Server Process Currently Running.............................. B-12 B-9 NCL Command Showing the OSI Transport Templates...................................... B-13 B-10 Removing the DECcmi Kit - No Server Process Currently Running.............................. B-16 B-11 Kit Installation Failure Due to License Problem........................................ B-16 B-12 IVP Failure Due to License Problem ............ B-17 B-13 DECcmi Start Failure Due to License Problem ... B-18 iv Tables 2-1 Presentation Addresses of ROS, CMIS and XMP SAPs........................................... 2-5 A-1 Files in /usr/examples/cmip ................... A-1 A-2 Files in /usr/lib ............................. A-1 A-3 Files in /usr/bin ............................. A-1 A-4 Files in /usr/etc ............................. A-3 A-5 Files in /usr/var/cmip/conf ................... A-3 A-6 Files in /usr/include ......................... A-3 v _________________________________________________________________ Preface This guide describes how to install the DECcmi software on a DIGITAL UNIX [R] + system operating in an OSI-compliant computer network. DECcmi is a software tool that conforms to the Open Systems Interconnection (OSI) standards. It is useful to programmers for the development of OSI-compliant applications that rely on Common Management Information Services (DECcmi), and/or on the Remote Operation Service (DECros). The DECcmi server provides the Common Management Information Services as the XMP and CMI APIs, and the Remote Operation Services and Association and Control Services as the ROS API. DECros is the subset of DECcmi providing only the ROS API. In this document, DECcmi is used as a generic term to represent both DECcmi and DECros. Intended Audience This guide is intended for use by anyone who is installing DECcmi. It is assumed that the reader has a knowledge of basic system management, DIGITAL UNIX, DECnet-Plus+ and DEC X.25 for DIGITAL UNIX. Structure of This Guide The guide is structured as follows: o Chapter 1 explains the prerequisites for the installation of the DECcmi software. o Chapter 2 describes the different steps for the installation and configuration of DECcmi. o Chapter 3 describes how to verify the installation. o Chapter 4 describes how to start and stop the DECcmi server. o Chapter 5 describes how to compile and run the example programs. o Chapter 6 describes how to link your Network Application Program with the CMS or ROS API. ____________________ + UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. + Formerly known as DECnet/OSI. vii o Chapter 7 describes the limitations of the DECcmi product. o Appendix A provides a list of the DECcmi files installed. o Appendix B gives several examples recorded during an installation process. A glossary of acronyms and abbreviations can be found in the DECcmi Operator's Guide. Conventions The following conventions are used in this guide: ___________________________________________________________ Convention__Meaning________________________________________ Boldface Indicates file and path names or emphasis on an important word or concept. Italics Indicates an associated document. This 1- to 3-character symbol indicates that you press a key on the terminal keyboard. For example, is the return key, is the delete key. Messages Messages displayed on the user's terminal are shown proportionally spaced. For example: Working....Mon Nov 21 18:41:37 GMT 1994 Commands Commands entered by the user are displayed in the typeface shown below: ____________#pkgadd_-d_._CMSCML217_________________________ Associated Documents This guide is part of the TeMIP documentation set. The following is a list of the full documentation set. Note that book titles preceded by + are not applicable to Sun Solaris installations. Introductory Manuals o TeMIP Introduction (AA-Q9J1D-TE) o TeMIP Graphical ASCII Toolkit Overview (AA-QZAUB-TE) Installation Manuals o + TeMIP for DIGITAL UNIX Installation Guide (AA-Q9J2E- TE) o TeMIP for Sun Solaris Installation Guide (AA-R767A-TE) o + TeMIP for DIGITAL UNIX OSI Management Toolkit Installation Guide (AA-QEMQF-TE) o TeMIP for Sun Solaris OSI Management Toolkit Installation Guide (AA-R769A-TE) viii o + TeMIP for DIGITAL UNIX OSI Management Toolkit, OSI Access Module, Run-Time Kit Installation Guide (AA- QEMRF-TE) o TeMIP for Sun Solaris OSI Management Toolkit, OSI Access Module, Run-Time Kit Installation Guide (AA-R76AA-TE) o + TeMIP for DIGITAL UNIX Graphical ASCII Toolkit Installation Guide (AA-QZARB-TE) o TeMIP for Sun Solaris Graphical ASCII Toolkit Installation Guide (AA-R768A-TE) o + DECcmi for DIGITAL UNIX Installation and Configuration Guide (AA-QENTF-TE) o DECcmi for Sun Solaris Installation and Configuration Guide (AA-R76BA-TE) Management Manuals o TeMIP Utilities (AA-Q9JBD-TE) o TeMIP Planning Guide (AA-QXSPB-TE) o TeMIP Director Configuration and Management Guide (AA- QN8NC-TE) o TeMIP Name Service Administration Guide (AA-QXSQB-TE) o TeMIP Customization and Troubleshooting Guide (AA-QXSRB- TE) o TeMIP Framework Security Administration Guide (AA-QD9GD- TE) User Manuals o TeMIP Fault and Trouble Management Alarm Handling User's Guide (AA-Q9J4D-TE) o TeMIP Fault and Trouble Management Trouble Ticketing User's Guide (AA-Q9J8D-TE) o TeMIP Fault and Trouble Management Event Logging User's Guide (AA-Q9J6D-TE) o TeMIP Framework Iconic Map and FCL User's Guide (AA- Q9HMD-TE) o + TeMIP Framework DECnet Phase IV Access Module Use (AA-Q9HAD-TE) o + ++ TeMIP Framework DECnet-Plus Access Module Use (AA- Q9HBD-TE) o TeMIP Framework TCP/IP SNMP Access Module Use (AA-Q9HCD- TE) o TeMIP Framework Script Access Module Use (AA-Q9HDD-TE) ____________________ ++ Formerly known as DECnet/OSI ix o TeMIP Framework Circuit Access Module Use (AA-Q9HHD-TE) o TeMIP Framework Autoconfiguration Use (AA-Q9HLD-TE) o TeMIP Framework Alarms and Notification Services Use (AA-Q9HED-TE) o TeMIP Framework Security Operator's Guide (AA-QD9FD-TE) o TeMIP OSI Management Toolkit GDMO Browser User's Guide (AA-QDYPF-TE) o TeMIP OSI Management Toolkit GDMO Translator User's Guide (AA-QDYNF-TE) o TeMIP OSI Management Toolkit, OSI Access Module, User's Guide (AA-QDYMF-TE) o TeMIP Graphical ASCII Toolkit Customization Manual (AA- QZASB-TE) o TeMIP Graphical ASCII Toolkit Configuration and Troubleshooting Guide (AA-QZATB-TE) o DECcmi Operator's Guide (AA-QDYQF-TE) + Not applicable to Sun Solaris installations. Programming and Software Reference Manuals o TeMIP Framework Management Module Programming (AA-Q9H8D- TE) o TeMIP Framework Security Software Reference Manual (AA- QD9ED-TE) o TeMIP Framework System Reference Manual Volume 1 (AA- Q9HGD-TE) o TeMIP Framework System Reference Manual Volume 2 (AA- PD5LH-TE) o Visual TeMIP Reference Guide (AA-QV89C-TE) o Visual TeMIP Development Guide (AA-QV8BC-TE) o TeMIP Fault and Trouble Management Reference Guide (AA- Q9J3D-TE) o TeMIP Fault and Trouble Management OSI System AM, Module Reference Manual (AA-Q9JAD-TE) o TeMIP Fault and Trouble Management Alarm Handling FM Module Reference Manual (AA-Q9J5D-TE) o TeMIP Fault and Trouble Management Event Log FM Module Reference Manual (AA-Q9J7D-TE) o TeMIP Fault and Trouble Management Trouble Ticketing FM Module Reference Manual (AA-Q9J9D-TE) o TeMIP Fault and Trouble Management Event Filtering and Correlation FM Module Reference Manual (AA-QK7HC-TE) o TeMIP Fault and Trouble Management Event Filtering and Correlation Software Reference Manual (AA-QMWKC-TE) x Other Documents of Interest o + DECnet-Plus Planning Guide This describes how to migrate a network from DECnet Phase IV to DECnet-Plus, including configuration guidelines and task planning. o + DIGITAL UNIX Documentation Set This describes how to use and manage the DIGITAL UNIX operating system. o Sun Solaris Documentation Set This describes how to use and manage the Sun Solaris operating system. o + DIGITAL UNIX Guide to Remote Installation Services This describes how to install and maintain your remote installation environment, using the RIS utility. o ORACLE Installation and Configuration Guide This provides installation and configuration information for ORACLE databases and tools. o ORACLE Server Administrator's Guide This describes how to manage ORACLE databases. o ORACLE Server SQL Language Reference Manual This gives a complete description of the SQL language used to create, store, modify, retrieve, and manage information in an ORACLE database. o ORACLE SQL*Plus User's Guide and Reference This describes the SQL*Plus program, and gives a detailed description of each command. o ORACLE SQL*Net Administrator's Guide This describes how to use ORACLE tools and applications to access, manipulate, share, and store data in ORACLE databases, residing on remote servers. o + DECsafe Available Server Installation Guide This describes how to install the DECsafe Available Server hardware and software, to give access to applications in a network environment. o + Guide to the DECsafe Available Server This describes how to set up and manage the systems and services in the DECsafe Available Server environment. o DECcmi/DECros - Programmer's Guide o DECcmi Release Notes o + DECnet-Plus for DIGITAL UNIX - Installation and Configuration o + DECnet-Plus for DIGITAL UNIX - Network Control Language Reference o + DECnet-Plus for DIGITAL UNIX - Network Management xi o + DECnet-Plus for DIGITAL UNIX - Release Notes o + X.25 for DIGITAL UNIX Systems - Introduction o + X.25 for DIGITAL UNIX Systems - Installation Guide o + X.25 for DIGITAL UNIX Systems - Configuration Guide o + X.25 for DIGITAL UNIX Systems - Management Guide o + X.25 for DIGITAL UNIX Systems - Problem Solving Guide o + X.25 for DIGITAL UNIX Systems - Release Notes o + DIGITAL UNIX Guide to Software License Management o + Common Trace Facility for DIGITAL UNIX User's Guide. o SunLink OSI 8.1 - Communication Platform Administrator's Guide o Managing SunLink X.25 9.0 + Not applicable to Sun Solaris installations. xii 1 _________________________________________________________________ Preparing for DECcmi Software Installation This chapter describes the requirements and preparations for installing DECcmi. Topics included are: o Pre-Installation Procedure, see Section 1.1 o Licensing DECcmi on Your System, see Section 1.2 o DECnet-Plus and X.25, see Section 1.3 1.1 Pre-Installation Procedure Before you install DECcmi check the following: o You have the correct distribution kit (CMACMV217.tar file). o You have the Product Authorization Key (PAK) for DECros (ROS-RT-OA). DECcmi does not have its own specific license but uses the license associated with the DECros product. o You have access to superuser privileges and know the password for access to the root account. o Make sure there is enough free disk space for the DECcmi software files: you need about 3 megabytes in the /usr partition (df /usr command). If a DECcmi kit has been previously installed on your system, it is recommended, but not mandatory, that you remove it using the setld -i command (to identify the kit) and the setld -d command (to delete it). _______________________ Warning _______________________ During the removal of a former kit using the setld -d command, the following directories and their contents are removed: o /usr/examples/cmip o /usr/var/cmip/log o /usr/var/cmip/mbx Make sure you save the contents of these directories if you have added files or modified standard files. The /usr/var/cmip/conf directory is processed differently, only the files belonging to the kit are removed. The /usr/var/cmip/conf/cmi_profile.txt file is always saved, refer to Section 2.3 for further details. ______________________________________________________ Preparing for DECcmi Software Installation 1-1 1.2 Licensing DECcmi on Your System Before installing DECcmi, you must register your software license using the License Management Facility (LMF). Registration is not mandatory for the installation, but you cannot run the DECcmi Installation Verification Program (IVP), or start the DECcmi server if you have not run the LMF procedure. Refer to Example B-12 and Example B-13 in Appendix B for examples of licensing failures of this type. For further details of the LMF tool, refer to the DIGITAL UNIX Guide to Software License Management, or the lmf(8) manpage. The license registration information you need is contained in the Product Authorization Key (PAK) shipped separately from the DECcmi kit. Note that if a PAK is already registered because a DECcmi kit has been previously installed on your local system, you do not need to register it again. 1.3 DECnet-Plus and X.25 Because DECcmi relies on DECnet-Plus, it is essential that the DECnet-Plus software is correctly installed and configured. Note that the default environment is LAN, a WAN environment being supported only when X.25 for DIGITAL UNIX is installed. Some basic aspects of DECnet-Plus and X.25 particularly relevant to DECcmi are described in this section, but for further details refer to the following documentation: o DECnet-Plus for DIGITAL UNIX - Installation and Configuration Guide o X.25 for DIGITAL UNIX Systems - Installation Guide o X.25 for DIGITAL UNIX Systems - Configuration Guide 1.3.1 Prerequisites To be able to continue, the following steps must have been completed: o DIGITAL UNIX V3.0, V3.2, V3.2C or V4.0 must be installed and running o DECnet-Plus for DIGITAL UNIX V3.0, V3.2, V3.2C or V4.0 must be installed and running for LAN access (and also for WAN access, if required) o X.25 V1.1, V1.2, V1.3 or V3.0 for DIGITAL UNIX must be installed and running for WAN access only 1-2 Preparing for DECcmi Software Installation 1.3.2 DECnet-Plus Configuration DECnet-Plus configuration is performed using the /usr/sbin/decnetsetup configuration utility, which accepts two different options (basic or advanced). The following files are produced: o /usr/sbin/decnetstartup: shell script used to start DECnet-Plus entities o /usr/sbin/decnetshutdown: shell script used to stop DECnet-Plus activity o /var/dna/scripts/*.ncl: miscellaneous ncl script configuration files 1.3.3 X.25 Configuration The X.25 configuration is performed using the /usr/sbin/x25setup configuration utility, which accepts two different options (basic or advanced), and produces the following two files: o /usr/sbin/x25startup: shell script used to start X.25 o /var/dna/scripts/x25startup.ncl: ncl script containing the current X.25 configuration Note that X.25 can be stopped using the /usr/sbin/x25shutdown shell script command. 1.3.4 OSI Transport Templates Depending on the presence of X.25 software, several OSI Transport templates are generated at configuration time. These templates gather the characteristics of the outgoing or incoming OSI Transport connections. If only DECnet-Plus is installed (LAN environment), the following Transport templates exist after the configuration phase: o default: Uses Transport Class 4 above the CLNS network service for outgoing connections, when no explicit template is specified. o clns: Uses Transport Class 4 above the CLNS network service for outgoing connections. o any: Uses Transport Class 4 above the CLNS network service for incoming connections. If DECnet-Plus and X.25 are installed (LAN + WAN environment), the following Transport templates exist after the configuration phase: o default: Uses Transport Class 4 above the CLNS network service for outgoing connections, when no explicit template is specified. o clns: Uses Transport Class 4 above the CLNS network service for outgoing connections. o cons: Uses Transport Classes 2 and 0 above the CONS network service, for outgoing connections. Preparing for DECcmi Software Installation 1-3 o any: Uses Transport Classes 4, 2 and 0 above the CLNS or CONS network services for incoming connections. The actual configuration of OSI Transport templates can be shown by the /usr/bin/ncl utility using the command: ncl show osi transport template * all A template example is shown in Example B-9 of Appendix B. For more information about the ncl utility, refer to the DECnet-Plus for DIGITAL UNIX - Network Control Language Reference. 1.3.5 Verifying the DECnet-Plus Configuration _______________________ Warning _______________________ If you have set up a DECnet-Plus configuration different to that of the default LAN, it is highly recommended that you check this configuration before trying to run DECcmi. A simple test could consist of running the netosiivp IVP program located under /usr/examples/xti, which permits validation of the specific DECnet-Plus configuration accessed through the XTI interface. ______________________________________________________ In order to check the Transport connectivity between a system init and a system resp, you have to: o First generate the netosiivp executable file on both systems, using the command: # cc -g -o netosiivp netosiivp.c -lxti -lxtiosi -ltermcap o Then create the /etc/isonsaps file on system init and insert the following entry: resp:ns=%xRespNSAP where RespNSAP represents the NSAP of the system resp. o Run the test by issuing the following command: # netosiivp -R on machine resp and: # netosiivp -t YourTemplate -I resp on machine init where YourTemplate represents the specific OSI Transport template you have configured (for example cons for X.25). A trace execution of the netosiivp program, collected respectively on systems resp and init, is shown below (using the default clns OSI Transport template for a LAN): # ./netosiivp -R parent: forked child 7213 7213: Initiator is %X49003faa000400a4ff21/%X01000100 7213: TPDU size = 8192 octets, class 4, no checksums extended format, no expedited data, explicit flow control 7213: Recorded 0 octets of expedited data 7213: Recorded total 10001 octets of normal data 1-4 Preparing for DECcmi Software Installation 7213: Normal disconnection: Normal Disconnect (reason=128, seq=-1) # ./netosiivp -t clns -I resp TPDU size = 8192 octets, class 4, unlimited TSDU size, no checksums extended format, no expedited data, explicit flow control Sending 10000 octets of normal data in 100 octet DT TPDUs... completed (200.90 KB/sec) Sending 1 octet end of data marker... completed Recorded 0 octets of expedited data Recorded total 10001 octets of normal data The successful completion of this test ensures that the relevant DECnet-Plus configuration is valid, that is, the relevant NSAP (here RespNSAP) and the relevant OSI Transport template (here YourTemplate) is used to configure DECcmi (refer to Section 2.4). 1.3.6 Tracing DECnet-Plus Activity You can collect OSI Transport traces (TPDUs) using the CTF utility (/usr/bin/ctf). Refer to the Common Trace Facility for DIGITAL UNIX User's Guide for further details. Preparing for DECcmi Software Installation 1-5 2 _________________________________________________________________ Installing the DECcmi Software This chapter describes how to install DECcmi on your system. You can find more information in: o Installation of DECcmi Files, see Section 2.1 o DECcmi Environment Variables, see Section 2.2 o Modifying the DECcmi Default Configuration, see Section 2.3 o Defining the Remote Network Service Access Points (NSAP) Addresses, see Section 2.4 o Using the Syslog utility, see Section 2.5 2.1 Installation of DECcmi Files In order to install the DECcmi software, you need to: 1. Log in as root 2. Copy the CMACMV217.tar file to your local system 3. Extract the kit, using the command: tar xvf CMACMV217.tar 4. Install the kit from the current directory using the command: setld -l . CMACMV217 Before starting DECcmi, check that the mandatory environment variables are defined, and if necessary, modify the default DECcmi configuration file. 2.2 DECcmi Environment Variables The DECcmi environment variables are described in Section 2.2.1 and Section 2.2.2. 2.2.1 Mandatory Variables UPLROOT UPLROOT contains the name of the root directory to which the mailboxes between the DECcmi server and user are attached. Enter the following command: # setenv UPLROOT /usr/var/cmip when using csh or # UPLROOT=/usr/var/cmip; export UPLROOT Installing the DECcmi Software 2-1 when using sh or ksh. ________________________ Note ________________________ UPLROOT must be defined for both the DECcmi server process and the application processes linked within the DECcmi APIs (CMIS, ROS and XMP). ______________________________________________________ CMISE_INBOUND CMISE_INBOUND contains the listener template name used for incoming connections. Enter the following command: # setenv CMISE_INBOUND any when using csh or # CMISE_INBOUND=any; export CMISE_INBOUND when using sh or ksh. ________________________ Note ________________________ CMISE_INBOUND must only be defined for the DECcmi server process. ______________________________________________________ XDSROOT XDSROOT contains the name of the directory where XOM/XMP configuration files are located. Enter the following command: # setenv XDSROOT $UPLROOT/conf when using csh or # XDSROOT=$UPLROOT/conf; export XDSROOT when using sh or ksh. ________________________ Note ________________________ XDSROOT must only be defined for the application processes linked within the XMP API. ______________________________________________________ 2.2.2 Optional Variables DECcmi provides the following optional environment variables: ROS_WAIT_REG The optional environment variable ROS_WAIT_REG permits you to override the default timer value (3 seconds) used to wait for the Registration Confirm internal event. This event is generated by the DECcmi server when processing the Register() API primitive. 2-2 Installing the DECcmi Software If the DECcmi server is under too much stress, the Registration process may fail (timed out), and an error message of the following generic type may be displayed: [801f] Spurious #n Origin(AM #1, MBX=xxxxxxxx) ID1=yyy ID2=zzz EVN=tttt To avoid such errors, the ROS_WAIT_REG variable must be customized using one of the following commands: # setenv ROS_WAIT_REG 30 when using csh or # ROS_WAIT_REG=30; export ROS_WAIT_REG when using sh or ksh. In this example the variable has been set to 30 seconds, but in a real case it depends on the actual load on your DECcmi server. ________________________ Note ________________________ ROS_WAIT_REG must only be defined for the application processes linked within the CMIS or ROS APIs. ______________________________________________________ NB_MAX_ASSOC The default Maximum Number of Associations supported by both the CMIS API and the ROS API can be extended to 128 using the NB_MAX_ASSOC environment variable. The permitted values range from 1 up to 128, illegal values being silently ignored (in which case the default value 64 is taken instead). For example, to support 128 Associations, type the following command: # setenv NB_MAX_ASSOC 128 when using csh or # NB_MAX_ASSOC=128; export NB_MAX_ASSOC when using sh or ksh. ________________________ Note ________________________ NB_MAX_ASSOC may only be defined for the application processes linked within the CMIS or ROS APIs. ______________________________________________________ 2.3 Modifying the DECcmi Default Configuration The DECcmi server process is started by the Operator process, which uses an input file known as its profile. The profile contains Operator commands to be executed before or after the main task of the DECcmi process is started (that is, the start command). Installing the DECcmi Software 2-3 This feature allows the customization of the DECcmi server objects according to a given system configuration. The profile allows you to define the Suffixes associated with the Service Access Points (SAPs), to toggle tracing mode for debugging purposes, or to perform specific tuning or configuration actions. By default, the DECcmi startup procedure uses the profile: /usr/var/cmip/conf/cmi_profile.txt which is self-explanatory and shown in Example B-7 of Appendix B. Figure 2-1 shows the addressing information for the default DECcmi configuration. This information is summarized in Table 2-1, which in addition, gives the associated Presentation Address for each ROS, CMIS and XMP SAP. Note that a Presentation Address is made up of the concatenation of the Presentation Selector, Session Selector, Transport Selector and Network Address. For each selector, Table 2-1 gives the associated Suffix Number in parentheses (a Suffix is the DECcmi internal representation of a Selector). If want to change the Presentation Addresses in use, you must modify the relevant Suffixes in SECTION 2 of the /usr/var/cmip/conf/cmi_profile.txt file. For example, if you want to change the Session Selector of all ROS and CMIS SAPs to the new value SESSION_SEL (default value session), you must insert the following statement in SECTION 2 of cmi_profile.txt: define suffix 110 CSESSION_SEL If you want to change the Presentation Selector of ROS SAP #32 to the new value ROS2 (default value ROSWAN2), you must add the following statement in the profile: define suffix 32 CROS2 If you want to change the Presentation Selector of CMIS SAP #79 to the new value CMI9 (default value ROSCMILAN1), you must insert the following statement in SECTION 2: define suffix 59 CCMI9 Note that for CMIS SAP #79, the Suffix to change is the Suffix of the Presentation SAP #59, which is mapped by CMIS SAP #79 because CMIS SAPs have no associated suffixes. 2-4 Installing the DECcmi Software Table_2-1_Presentation_Addresses_of_ROS,_CMIS_and_XMP_SAPs_ SAP Nb P-Sel (Suf S-Sel (Suf T-Sel (Suf N- (Type)_______Nb)_____________Nb)___________Nb)___________Addr #31[1] ROSWAN1 session transport xxxxxx[5] (ROS) (#31[2]) (#110[3]) (#100[4]) #32 (ROS) ROSWAN2 (#32) session transport xxxxxx (#110) (#100) ... ... ... ... ... #38 (ROS) ROSWAN8 (#38) session transport xxxxxx (#110) (#100) #39 (ROS) ROSLAN1 (#39) session transport xxxxxx (#110) (#100) #40 (ROS) ROSLAN2 (#40) session transport xxxxxx (#110) (#100) ... ... ... ... ... #46 (ROS) ROSLAN8 (#46) session transport xxxxxx (#110) (#100) #71[6] ROSCMIWAN1 session transport xxxxxx (CMIS) (#51[7]) (#110) (#100) #72 (CMIS) ROSCMIWAN2 session transport xxxxxx (#52) (#110) (#100) ... ... ... ... ... #78 (CMIS) ROSCMIWAN8 session transport xxxxxx (#58) (#110) (#100) #79 (CMIS) ROSCMILAN1 session transport xxxxxx (#59) (#110) (#100) #80 (CMIS) ROSCMILAN2 session transport xxxxxx (#60) (#110) (#100) ... ... ... ... ... #86 (CMIS) ROSCMILAN8 session transport xxxxxx (#66) (#110) (#100) #511 (XMP) I001 SSEL TLAN xxxxxx (#111[8]) (#109[9]) (#99[10]) #512 (XMP) I002 (#112) SSEL (#109) TLAN (#99) xxxxxx ... ... ... ... ... #599 (XMP) I089 (#199) SSEL (#109) TLAN (#99) xxxxxx #600 (XMP) I090 (#200) SSEL (#109) TLAN (#99) xxxxxx (continued on next page) Installing the DECcmi Software 2-5 Table 2-1 (Cont.) Presentation Addresses of ROS, CMIS and ___________________XMP_SAPs________________________________ SAP Nb P-Sel (Suf S-Sel (Suf T-Sel (Suf N- (Type)_______Nb)_____________Nb)___________Nb)___________Addr [1]Defined_in_/usr/include/ros.h_as_RO_K_SAP1._____________ [2]Suffix #31 represents P-Selector of ROS SAP #31. [3]Suffix #110 represents S-Selector of all ROS and CMIS SAPs. [4]Suffix #100 represents T-Selector of all ROS and CMIS SAPs. [5]Represents the NSAP, refer to Section 2.4 for further details. [6]Defined in /usr/include/cmi.h as M_K_SAP1. [7]Suffix #51 represents P-Selector of CMIS SAP #71. [8]Suffix #111 represents P-Selector of XMP SAP #511. [9]Suffix #109 represents S-Selector of all XMP SAPs. [10]Suffix #99 represents T-Selector of all XMP SAPs. (continued on next page) 2-6 Installing the DECcmi Software Table 2-1 (Cont.) Presentation Addresses of ROS, CMIS and __________________XMP_SAPs_________________________________ SAP Nb P-Sel (Suf S-Sel (Suf T-Sel (Suf N- (Type)_______Nb)_____________Nb)___________Nb)___________Addr ... ... ... ... ... #637 (XMP) I127 (#237) SSEL (#109) TLAN (#99) xxxxxx #638_(XMP)___I128_(#238)_____SSEL_(#109)___TLAN_(#99)____xxxxxx For more information about the DECcmi Operator commands and internal configuration, refer to the DECcmi Operator's Guide. _______________________ Warning _______________________ If you try to install your DECcmi kit on a machine that has a previously installed, older version of DECcmi, the profile /usr/var/cmip/conf/cmi_ profile.txt is saved in the /tmp directory to preserve any customizations you have made. Therefore, you must replace your customized version after full installation of the kit. Example B-2 in Appendix B illustrates this feature. ______________________________________________________ 2.4 Defining the Remote NSAP Addresses The file /etc/nsaps must be configured with the NSAP addresses of the remote systems you want to reach. This file allows you to get the name of the OSI Transport template, to be used for initiation of an outgoing Transport Connection. There are two ways to get this information, depending on what information is held in the N-ADDRESS component of the P-ADDRESS managed at Application level. This is either a LABEL or a real NSAP. 2.4.1 LABEL Mode In this case the N-ADDRESS component is in fact a LABEL used as the search criterion. The /etc/nsaps file is consulted to get both the real NSAP and the relevant template associated with the given LABEL. Note that due to the /etc/nsaps file, the Network Management Applications manipulate logical names instead of actual NSAP addresses. The syntax of such an entry is: label/outgoing_template_name%remote_NSAP_address where: o / is the separator between the label and the outgoing_ template_name. Installing the DECcmi Software 2-7 o % is the separator between the outgoing_template_name and the remote_NSAP_address. An example of a /etc/nsaps file (LABEL mode) is shown below: # # obelix Ultrix V4.3 # lanobelix/clns%490022bb000400d4ce21 wanobelix/cons%3700001234567105 # # caraib DIGITAL UNIX V4.0 # lancaraib/clns%49002EBB000400A4FF21 wancaraib/cons%3654522410000101 # # sunws1 Sun Solaris V2.5 # lansunws1/clns%49002E123B5401 wansunws1/cons%3654522410000101 # # biniou VMS/VAX V5.5-2 # lanbiniou/clns%490022BB0004000CCD21 wanbiniou/cons%123456760 # # arctiq OpenVMS/AXP V6.1 # lanarctiq/clns%490033AA00040004CD21 wanarctiq/cons%123456790 2.4.2 NSAP Mode Here the N-ADDRESS component represents a real NSAP used as the search criterion, so the /etc/nsaps file is only consulted to get the template associated with the given NSAP. The syntax of an entry is: /outgoing_template_name%remote_NSAP_address where: o / means that the outgoing_template_name follows. o % is the separator between the outgoing_template_name and the remote_NSAP_address. An example of a /etc/nsaps file (NSAP mode) is shown below: # # comore DIGITAL UNIX V3.2C # /clns%49003ECC000400A4EE21 /cons%36519224100201 # # sunws4 Sun Solaris V2.5 # /clns%49003ECC5401 /cons%36519224100201 2-8 Installing the DECcmi Software 2.4.3 Coexistence of LABEL and NSAP Modes The choice between LABEL or NSAP mode is done dynamically and automatically, DECcmi interpreting the given N-ADDRESS component as either a LABEL or a real NSAP. ________________________ Note ________________________ If an ambiguity is detected during the interpretation of a given N-ADDRESS component (LABEL or NSAP ?), the LABEL is always chosen in order to preserve the compatibility with the former behavior (LABEL mode only supported). For example, if the given N-ADDRESS is 5051525354, it will be interpreted as the LABEL PQRST instead of the potential NSAP 5051525354. ______________________________________________________ The same remote node can be declared in the /etc/nsaps file for both modes, as shown in the following example. # # dzirad DIGITAL UNIX V4.0 # landzirad/clns%49002EDD000300A4CC21 /clns%49002EDD000300A4CC21 # # sunws4 Sun Solaris V2.5 # lansunws4/clns%49003ECC5401 /clns%49003ECC5401 2.4.4 Common Syntax Rules The following rules apply to the /etc/nsaps file: o # is the comment character, which must be located in the first column. The comment stops at the end of the line. o Entries cannot be folded. o Spaces and tabulations are forbidden at the beginning and inside an entry. o Trailing spaces or tabulations are permitted and silently ignored. ________________________ Note ________________________ To find the NSAP address of a remote system, call the /usr/sbin/decnet_dns_register DNS utility, and choose in the main menu the option 9: Show information about node names registered in the namespace. ______________________________________________________ Installing the DECcmi Software 2-9 2.5 Using the Syslogd Utility The standard syslogd(8) utility can be used to log possible abormal events occurring while DECcmi is running, without explicit use of the Operator's process (that is, cmi_cmu process not running). To log these possible abnormal events, you need to insert the following line in the /etc/syslog.conf file: local4.debug /var/adm/syslog.dated/deccmi.log and type the following command: kill -HUP `cat /var/run/syslog.pid` to take into account the new syslogd configuration. ________________________ Note ________________________ The items in each line of /etc/syslog.conf must be separated by one or more tabs (spaces are not allowed). ______________________________________________________ The relevant traces will be collected, on a day by day basis, in /var/adm/syslog.dated/dd-mmm-hh-mm/deccmi.log file, and include: - Minimum normal information at DECcmi startup/shutdown: Jul 24 15:12:47 caraib CMI_SHM[25647]: Shared Memory V2.17 allocated (131072 bytes) Jul 24 15:12:47 caraib CMI_CMU[22304]: Operator Process V2.17 started Jul 24 15:12:48 caraib CMI_SRV[28482]: Starting V2.17 Protocol Stack ... Jul 24 15:12:49 caraib CMI_CMU[22304]: Operator Process V2.17 stopped Jul 24 15:12:49 caraib CMI_CMU[5266]: Operator Process V2.17 started Jul 24 15:12:51 caraib CMI_SRV[28482]: V2.17 Protocol Stack successfully started Jul 24 15:12:53 caraib CMI_CMU[5266]: Operator Process V2.17 stopped Jul 24 16:02:33 caraib CMI_CMU[28384]: Operator Process V2.17 started Jul 24 16:02:36 caraib CMI_SRV[4711]: V2.17 Protocol Stack stopped Jul 24 16:02:37 caraib CMI_CMU[28384]: Operator Process V2.17 stopped - Possible abnormal events such as: Jul 24 22:13:23 caraib CMI_SRV[30926]: ### ERROR: shmalloc: Error in calling getmemv Jul 24 22:13:23 caraib CMI_CMU[30926]: ### ERROR: Shared Memory buffer shortage Jul 24 22:13:23 caraib CMI_SRV[30926]: ### ERROR: maksmbuf: shmalloc error Jul 24 22:13:25 caraib XMP_API[31050]: ### ERROR: Shared Memory buffer shortage - Or: Jul 25 13:15:31 caraib CMI_SRV[27605]: ### ERROR: pt_mb_uw: ipc_iw failure, ipc_typ= [0] Jul 25 13:15:31 caraib CMI_SRV[27605]: ### ERROR: stm_wr: writev error errno= [32] - Or: Jul 25 14:27:09 caraib CMI_SRV[28364]: ### ERROR: file=cmimai2.c line=243 2-10 Installing the DECcmi Software 3 _________________________________________________________________ Verifying the Installation The Installation Verification Program can be run to verify that the DECcmi software is correctly installed. ________________________ Note ________________________ The IVP does not check that the communication through DECnet-Plus is running, only the local communication with the DECcmi server, via the CMI and ROS APIs is tested. To perform actual tests through DECnet-Plus, refer to Chapter 5. ______________________________________________________ You can find more information in: o The Installation Verification Program, see Section 3.1 o Preparing to Run the IVP, see Section 3.2 o Running the IVP, see Section 3.3 o Errors from the IVP, see Section 3.4 3.1 The Installation Verification Program The IVP requests the registration and deregistration for each type of SAP provided by DECcmi. Note that because the IVP performs a comprehensive verification of the DECcmi installation, the license must have been previously installed, otherwise the IVP execution fails, see Example B-12 in Appendix B. 3.2 Preparing to Run the IVP Before you run the IVP, make sure that DECnet-Plus is installed and running. The DECcmi IVP automatically starts and stops the DECcmi server, so no specific action is required. _______________________ Warning _______________________ The IVP automatically and silently stops a possible currently running DECcmi server. So before running the IVP, check that there is no DECcmi activity, otherwise you may loose already established associations. ______________________________________________________ Verifying the Installation 3-1 3.3 Running the IVP You can issue the DECcmi Installation Verification command from any directory on your system by entering the following command: # setld -v CMACMV217 An example listing from the IVP can be found in Example B-3 of Appendix B. 3.4 Errors from the IVP The IVP performs checks to see whether all the necessary files exist, whether certain example files are present and can be compiled, and that DECcmi can be started up. Error messages can occur if files are missing, or if problems are encountered compiling the example programs. If there is an error message, check whether the files listed in Appendix A are all present. If not, restart the installation procedure from the beginning. 3-2 Verifying the Installation 4 _________________________________________________________________ Starting and Stopping the DECcmi Server This chapter describes how to start and stop the DECcmi software and related topics. You can find more information in: o Starting DECcmi, see Section 4.1 o Stopping DECcmi, see Section 4.2 o DECcmi administrative account, see Section 4.3 4.1 Starting DECcmi To load and start DECcmi, use the following command: # /usr/etc/cmi_startup An example of a trace produced by this command is given in Example B-4 of Appendix B. If you want DECcmi to start whenever you bring up the system, create the file deccmi in the /sbin/init.d directory, containing the following commands: #!/bin/sh # # DECcmi for DIGITAL UNIX System Initialization Script # UPLROOT=/usr/var/cmip export UPLROOT CMISE_INBOUND=any export CMISE_INBOUND case $1 in start) echo "Starting the DECcmi server" > /dev/console /usr/etc/cmi_startup > /dev/console ;; stop) echo "Stopping the DECcmi server" > /dev/console /usr/etc/cmi_shutdown > /dev/console ;; *) 1>&2 echo "Usage: $0 start|stop" > /dev/console exit 1 ;; esac exit Now create the two symbolic links /sbin/rc0.d/KXXdeccmi and /sbin/rc3.d/SXXdeccmi pointing to /sbin/init.d/deccmi. Starting and Stopping the DECcmi Server 4-1 ________________________ Note ________________________ The number XX in the name of the file should be chosen in such a way that the DECcmi server is started after DECnet-Plus (S28.60decnetosi for DECnet-Plus for DIGITAL UNIX V3.0, V3.2, V3.2C and V4.0). ______________________________________________________ 4.2 Stopping DECcmi To stop DECcmi, use the following command: # /usr/etc/cmi_shutdown An example of a trace produced by this command is given in Example B-6 of Appendix B. 4.3 DECcmi Administrative Account No specific access rights are necessary to operate the DECcmi server, it is up to the system administrator to define a specific policy. Nevertheless, it is recommended that the DECcmi server is started by a privileged user, to prevent a non-privileged user stopping it inadvertently. _______________________ Warning _______________________ The cmi_startup script first tries to stop a possible running DECcmi server, internally calling the cmi_ shutdown script. If a running DECcmi server exists and was started by another user, different to the user you are currently using, the current cmi_startup may fail with the following error message: # cmi_startup Stopping running DECcmi server ... Initializing shared memory ... ERROR: cannot allocate shared memory, consult /tmp/shmmgr.log file Aborting startup procedure # cat /tmp/shmmgr.log Get Shared Memory Error , errno = [17] DECcmi - Shared Memory Manager Utility [V2.17] ---------------------------------------------- Such an error is due to access right conflicts on Shared Memory. To bypass the problem, run cmi_shutdown under the account which initially started the DECcmi server (the account where the former cmi_startup was invoked). ______________________________________________________ 4-2 Starting and Stopping the DECcmi Server 5 _________________________________________________________________ Compiling and Running Example Programs The DECcmi software is delivered with simple example programs, which are installed under the /usr/examples/cmip directory during installation of the kit. These programs illustrate only the use of the CMI and ROS proprietary APIs, and do not cover the X/Open XMP API. This chapter explains how to compile and run these programs in LAN loopback mode. You can find more information in: o Compiling CMIS and ROS Example Programs, see Section 5.1 o Preparing for Running the Example Programs, see Section 5.2 o Running CMIS and ROS Example Programs, see Section 5.3 5.1 Compiling CMIS and ROS Examples Programs The CMIS example program comprises the following files: o cmi_init_com.c : CMIS initiating program o cmi_resp_com.c : CMIS responding program o cmi_com_makefile : CMIS makefile The compilation of the CMIS example program is shown below: % make -f cmi_com_makefile cmi_init_com cmi_resp_com cc -p -g -c /usr/examples/cmip/cmi_init_com.c cc -o cmi_init_com /usr/examples/cmip/cmi_init_com.o -lcmi cc -p -g -c /usr/examples/cmip/cmi_resp_com.c cc -o cmi_resp_com /usr/examples/cmip/cmi_resp_com.o -lcmi The ROS example program is made of the following files: o ros_init_com.c : ROS initiating program o ros_resp_com.c : ROS responding program o ros_com_makefile : ROS makefile The compilation of the ROS example program is shown below: % make -f ros_com_makefile ros_init_com ros_resp_com cc -o ros_init_com ros_init_com.c -lcmi cc -o ros_resp_com ros_resp_com.c -lcmi 5.2 Preparing to Run the Example Programs Before running the example programs, do not forget to customize the environment as described in Section 2.2, and to start the DECcmi server as described in Section 4.1. Compiling and Running Example Programs 5-1 In order to run the programs in LAN loopback mode, you must add the following entry in /etc/nsaps file: ROSNAP/clns%YourLanAddress where YourLanAddress represents the local NSAP of your system. 5.3 Running CMIS and ROS Example Programs In order to run the CMIS example program, you must first call cmi_resp_com and then cmi_init_com. The program produces the following traces, collected in two different windows: % cmi_resp_com DECcmi : responder example using CMI API --------------------------------------------------------- <-> Registering to a CMIP Service Access Point... <-> Waiting for an Association establishment... <-- Waiting for a M_Event_Report... --> Sending a M_Event_Report_Resp... <-> Waiting for the Association release... --> Cancelling the registration... % cmi_init_com DECcmi : initiator example using CMI API --------------------------------------------------------- <-> Registering to a CMIP Service Access Point... <-> Establishing an association... --> Sending a M_Event_Report... <-- Waiting for a M_Event_Report_Cnf... <-> Releasing the association... --> Cancelling the registration... In order to run the ROS example program, you must first call ros_resp_com and then ros_init_com. A trace of the ROS example program execution, collected in two different windows, is shown below: % ros_resp_com --------------------------------------------------------------- DECros Performance Test Program - Responder side --------------------------------------------------------------- Mode of operation : Blocking Wait <-> Registering to a ROSE Service Access Point... <-> Waiting for an Association establishment... <-> DECros API test started... ----> RO_K_INVOKE_Ind <---- RO_RESULT_Req ----> A_K_RELEASE_IND <-> DECros API test Ended... <-> Releasing the Association... <-> Cancelling the registration... === DECros Responder side: Test Successful ! === 5-2 Compiling and Running Example Programs % ros_init_com ------------------------------------------------------------ DECros Performance Test Program - Initiator side --------------------------------------------------------------- Number of iterations (RO-Inv Req + RO-Res/Err/Reject-U Ind) .....: 1 Size of APDU : 1024 Remote Presentation Address is : ROSWAN2.session.transport.ROSNAP. <-> Registering to a ROSE Service Access Point... <-> Establishing an association... <-> DECros API Test started : time is Fri Oct 3 12:16:56 1997 ----> RO_INVOKE_Req <---- RO_K_RESULT_Ind End of iteration: 1 <-> DECros API test ended : time is Fri Oct 3 12:16:56 1997 Elapsed time : 00:00:00 <-> Releasing the association... <-> Cancelling the registration... === DECros Initiator side: Test Successful ! === ________________________ Note ________________________ If you want to run the sample programs between two different DIGITAL UNIX machines, you must modify the ROSNAP/clns/%YourLanAddress entry of the /etc/nsaps file on the machine running the cmi_init_com program. Replacing YourLanAddress by the NSAP of the remote machine running the cmi_resp_com program. ______________________________________________________ Compiling and Running Example Programs 5-3 6 _________________________________________________________________ Plugging your Network Application Program This chapter does not explain how to develop a Network Management Application using the CMIS or ROS API, however, it does provide basic information about: o Linking your Network Application Program with the CMIS or ROS API, see Section 6.1 o Checking the DECcmi version number, see Section 6.2 For more information, refer to the DECcmi/DECros Programmer's Guide. ________________________ Note ________________________ The X/Open XMP API is not covered by this chapter. ______________________________________________________ 6.1 Linking your Network Application Program with the CMIS or ROS API To link your Network Management Application Program with the CMIS API, you must use the following header files: o ros.h o ros_api.h o cmi.h o cmi_api.h and actually link them with the libcmi.a library. Plugging your Network Application Program with the ROS API requires the use of the following header files: o ros.h o ros_api.h and the libcmi.a library. 6.2 Checking the DECcmi Version Number If you are in a configuration where you have developed several Network Application Programs, and you have been working with several DECcmi kit deliveries, it could be useful to check the version number of the DECcmi kit you are currently using. This can be done either by: o Using the following simple program: Plugging your Network Application Program 6-1 % cat DECcmiVers.c main() { extern char DECcmiVersionNumber[]; printf("%s\n", DECcmiVersionNumber); } compiled by: % cc DECcmiVers.c -o DECcmiVers -lcmi and which, when called, gives the version number of the libcmi.a currently installed on your system, as shown below: % DECcmiVers DECcmi Version Number is V2.17 or o By using the following simple shell script: % cat Vers #!/bin/sh # if [ $# -ne 1 ] then echo "Usage: $0 prog_name" exit fi strings $1 | grep "DECcmi Version Number is " which, when applied for example to the cmi_init_com sample program, produces the following output: % Vers /usr/examples/cmip/cmi_init_com DECcmi Version Number is V2.17 6-2 Plugging your Network Application Program 7 _________________________________________________________________ DECcmi Limitations This chapter describes the limitations of the DECcmi product. The scope of this chapter goes beyond the DECcmi/DECros protocol stack itself, because it also groups information dealing with programming features. Programming features are fully described in the DECcmi/DECros Programmer's Guide. You can find more information in: o DECcmi Memory Limitations, see Section 7.1 o Maximum Number of Associations, see Section 7.2 o Maximum Size of User Data, see Section 7.3 o Presentation-Address Format, see Section 7.4 o Tuning DECcmi, see Section 7.5 7.1 DECcmi Memory Limitations The memory limitations of DECcmi are described in Section 7.1.1 and Section 7.1.2. 7.1.1 Shared Memory between APIs and the DECcmi Server The size of the Shared Memory Segment between the CMIS/ROS/XMP APIs and the DECcmi server has a default value of 1024 KB. This may be increased by replacing the numeric argument of the cmi_shmmgr -a 128 statement in the file /usr/etc/cmi_startup by a bigger value. The default maximum Shared Memory Segment size is 4 MB, therefore the argument of the cmi_shmmgr -a Operator command can be increased up to 7.1.2 Memory Buffers used Internally by the DECcmi Server These buffers are shared by applications using both the CMIS/ROS and XMP APIs. The maximum number of Memory Buffers which may be allocated by the DECcmi server was limited in former releases, but is now theoretically infinite (in fact limited by the system) for DECcmi V2.17. If no memory is available, due to system limit reached, DECcmi enters a frozen state and periodically tries to recover from the memory starvation; the following message is displayed at the Operator's console: 18:36:57[9999] ### WARNING: OSIAM buffer shortage, trying to recover The default configuration of the DECcmi server for Memory Buffers is equivalent to the Operator command def pool 512 512 512, and allocates 512 buffers of 512 bytes at DECcmi server start time. This memory will never be released to the system. DECcmi Limitations 7-1 A theoretically infinite number of pools of 256 buffers of 512 bytes will be allocated when needed, these pools of memory being released to the system when no longer needed. Refer to DECcmi Operator's Guide for more information. 7.2 Maximum Number of Associations The default Maximum Number of Associations supported by the DECcmi server is 64, shared by both CMIS and ROS APIs, plus a possible 128 Associations dedicated to XMP API. As described for NB_MAX_ASSOC, the default Maximum Number of Associations supported by both CMIS and ROS APIs can be extended to 128 using the NB_MAX_ASSOC environment variable. The number of file descriptors consumed by the DECcmi server can be computed using the following information: o 3 : reserved by DIGITAL UNIX for stdin, stdout and stderr o 1 OSIAM mailbox o 2 listening endpoints (1 for CMIS and ROS APIs + 1 for XMP API) o 1 if logging in a file is activated using the log Operator command. o 1 if the syslogd utility is active At application level, each time the Register() service of CMIS and ROS APIs is used, a file descriptor is consumed by the DECcmi server to open the relevant application mailbox (so there is one file descriptor per Register() call, even if it is performed in the same application process). For the XMP API, the first time the Bind() service is called inside a given application process, a file descriptor is consumed by the DECcmi server to open the relevant application mailbox (so there is one file descriptor per application process, performing one or several Bind() calls). The total number of file descriptors consumed by the DECcmi server is: nb fd consumed = nb of CMIS/ROS applications registered + nb of XMP processes bound + nb of associations established + 8 Nevertheless the Maximum Number of Associations should not normally be limited by the number of file descriptors available for a given process, as this is dynamically configured later, at DECcmi server startup time (in the cmi_startup script). 7-2 DECcmi Limitations 7.3 Maximum Size of User Data When using the ROS APIs, the DECcmi server can deal with: o Outgoing User Data up to a limit of 65.000 bytes o Unlimited incoming User Data (in fact limited by the Shared Memory size) When using the CMI or XMP APIs, the size of both incoming and outgoing User Data is limited by the Shared Memory size (ISO Profile ISP 11183 recommends to support at least 10 Kbytes). Successful tests have been performed with User Data of 4.000.000 bytes, with a Shared Memory size configured accordingly (that is, set to maximum value 4095, refer to Section 7.1.1). 7.4 Presentation Address Format The different components of the Presentation Addresses used in both the CMIS/ROS and XMP APIs are limited to: o 16 bytes for the P-SELECTOR of the CMIS/ROS API (not ISO Profile ISP 11183 conformant, 4 bytes being the recommended value) o 4 bytes for the P-SELECTOR in XMP API o 16 bytes for the S-SELECTOR o 32 bytes for the T-SELECTOR o 20 bytes for the N-ADDRESS 7.5 Tuning DECcmi ________________________ Note ________________________ This section does not give precise rules for configuring your DECcmi stack, but provides some hints on how to optimize its performance. ______________________________________________________ The default DECcmi configuration for both Shared Memory and Memory Buffers is appropriate for important network traffic (high number of associations and sustained flow of operations per association). Nevertheless you may increase these configuration parameters, taking into account the following: o Amount of shared memory required: Shared Memory = Maximum nb of associations * 2 * Maximum APDU size where Shared Memory is set as described in Section 7.1.1, and Maximum APDU size is determined using the debug on Operator command at CMISE level. o Size of Memory Buffer Fragments (a Memory Buffer being made up of one or several Fragments): Dataelemsize >= Average TPDU size, DECcmi Limitations 7-3 where dataelemsize is the Fragment size represented by the second parameter of the def pool Operator command, and Average TPDU size is determined using the debug on Operator command at Transport level. 7-4 DECcmi Limitations A _________________________________________________________________ List of DECcmi Files During installation the following files are placed in the directories specified. Table A-1 shows the files placed in the /usr/examples/cmip directory: Table_A-1_Files_in_/usr/examples/cmip______________________ cmi_init.c CMIS API Example program : Initiating side cmi_resp.c CMIS API Example program : Responding side cmi_makefile CMIS API Example program : Makefile ros_init.c ROS API Example program : Initiating side ros_resp.c ROS API Example program : Responding side ros_makefile ROS API Example program : Makefile cmi_init_com.c CMIS new API Example program : Initiating side cmi_resp_com.c CMIS new API Example program : Responding side cmi_com_ CMIS new API Example program : Makefile makefile ros_init_com.c ROS new API Example program : Initiating side ros_resp_com.c ROS new API Example program : Responding side ros_com_ ROS new API Example program : Makefile makefile___________________________________________________ Table A-2 shows the files placed in the /usr/lib directory: Table_A-2_Files_in_/usr/lib________________________________ libcmi.a_________Object_library_providing_CMIS_and_ROS_APIs Table A-3 shows the files placed in the /usr/bin directory: Table_A-3_Files_in_/usr/bin________________________________ cmi_cmu DECcmi Control and Management Utility executable image cmi_fmt DECcmi Message Formatter Utility (continued on next page) List of DECcmi Files A-1 Table_A-3_(Cont.)__Files_in_/usr/bin_______________________ cmi_ivp DECcmi Installation Verification Program cmi_shmmgr DECcmi shared memory manager executable image cmi_srv__________DECcmi_server_process_executable_image____ A-2 List of DECcmi Files Table A-4 shows the files placed in the /usr/etc directory: Table_A-4_Files_in_/usr/etc________________________________ cmi_startup DECcmi startup shell script cmi_shutdown_____DECcmi_shutdown_shell_script______________ Table A-5 shows the files placed in the /usr/var/cmip/conf directory: Table_A-5_Files_in_/usr/var/cmip/conf______________________ cmi_profile.txt DECcmi configuration profile (at startup time) cmi_ DECcmi configuration profile (at shutdown shutdown.txt_____time)_____________________________________ Table A-6 shows the files placed in the /usr/include directory: Table_A-6_Files_in_/usr/include____________________________ cmi.h DECcmi include file for constants and types cmi_api.h DECcmi include file for service primitives ros.h DECros include file for constants and types ros_api.h________DECros_include_file_for_service_primitives List of DECcmi Files A-3 B _________________________________________________________________ Sample Logs as Examples This appendix contains examples recorded during the DECcmi kit installation, IVP execution, start and stop of the DECcmi server, and kit removal. It also provides a listing of the standard profile file cmi_profile.txt cmi_ profile.txt and an ncl utility example. Examples of failures due to license problems, at kit installation time, IVP run-time and at DECcmi server start time are also given. Example B-1 shows a DECcmi kit installation log when no previous DECcmi kit has been installed. Example B-1 DECcmi Kit Installation - No Previous DECcmi Kit Installed #setld -l . CMACMV217 Checking file system space required to install specified subsets: File system space checked OK. Copyright (c) Digital Equipment Corporation, 1993,1994,1995. All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. The software contained on this media is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, duplication or dissemination of the software and media is authorized only pursuant to a valid written license from Digital Equipment Corporation. RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, as applicable. DECcmi V2.17 for DIGITAL UNIX (CMACMV217) - installation script DECcmi V2.17 for DIGITAL UNIX Copying from . (disk) Verifying To start your CMIP process server you need to define the symbols UPLROOT=/usr/var/cmip CMISE_INBOUND=any (continued on next page) Sample Logs as Examples B-1 Example B-1 (Cont.) DECcmi Kit Installation - No Previous DECcmi Kit Installed Configuring "DECcmi V2.17 for DIGITAL UNIX" (CMACMV217) DECcmi V2.17 for DIGITAL UNIX (CMACMV217) - installation completed Example B-2 shows a DECcmi kit installation log when a previous DECcmi kit has been installed. B-2 Sample Logs as Examples Example B-2 DECcmi Kit Installation - Previous DECcmi Kit Installed #setld -l . CMACMV217 Checking file system space required to install specified subsets: File system space checked OK. Copyright (c) Digital Equipment Corporation, 1993,1994,1995. All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. The software contained on this media is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, duplication or dissemination of the software and media is authorized only pursuant to a valid written license from Digital Equipment Corporation. RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, as applicable. DECcmi V2.17 for DIGITAL UNIX (CMACMV217) - installation script You might have customized the /usr/var/cmip/conf/cmi_profile.txt file. This profile file is saved in /tmp/cmi_profile.txt DECcmi V2.17 for DIGITAL UNIX Copying from . (disk) Verifying To start your CMIP process server you need to define the symbols UPLROOT=/usr/var/cmip CMISE_INBOUND=any Configuring "DECcmi V2.17 for DIGITAL UNIX" (CMACMV217) DECcmi V2.17 for DIGITAL UNIX (CMACMV217) - installation completed Example B-3 shows a log resulting from running the IVP. Example B-3 Running the IVP #setld -v CMACMV217 DECcmi V2.17 for DIGITAL UNIX (CMACMV217) Copyright (c) Digital Equipment Corporation, 1993,1994,1995. All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. The software contained on this media is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, duplication or dissemination of the software and media is authorized only pursuant to a valid written license from Digital Equipment Corporation. (continued on next page) Sample Logs as Examples B-3 Example B-3 (Cont.) Running the IVP RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, as applicable. DECcmi V2.17 for DIGITAL UNIX (CMACMV217) - installation script DECcmi V2.17 for DIGITAL UNIX (CMACMV217) - Checking for CMIP library and header files... DECcmi V2.17 for DIGITAL UNIX (CMACMV217) - Checking example programs... DECcmi V2.17 for DIGITAL UNIX (CMACMV217) - Compiling example programs... DECcmi V2.17 for DIGITAL UNIX (CMACMV217) - Starting up DECcmi... Working ... DECcmi V2.17 for DIGITAL UNIX (CMACMV217) - Running IVP program... DECcmi V2.17 for DIGITAL UNIX (CMACMV217) - Stopping DECcmi... The Installation Verification Procedure has been completed successfully DECcmi V2.17 for DIGITAL UNIX (CMACMV217) - working correctly. Example B-4 shows a DECcmi Server start log when there is no server process currently running. Example B-4 Starting the DECcmi Server - No Server Process Currently Running #cmi_startup Initializing shared memory ... Loading cmi_srv process ... DECcmi - Control and Management Utility [V2.17] ----------------------------------------------- CMU [0079] 1) Process cmi_srv started CMU [0083] 2) MBX cmi_srv opened CMU [0061] 3) Sending ADM_REQ to cmi_srv CMU [0016] Command mode is DEFAULT Prefix CMU [0001] *** Received ADM_CNF from TASK cmi_srv CMU [0065] Sending ADM_CAU to cmi_srv CMU [0035] waiting for ADM_CAUCF from process cmi_srv CMU [0004] *** Received ADM_CAUCF from TASK cmi_srv CMU [0042] Command mode is EXPLICIT Prefix Starting cmi_srv process ... ********************** Bind OK **************************** ********************** Bind OK **************************** Example B-5 shows a DECcmi Server start log when a server process is already running. B-4 Sample Logs as Examples Example B-5 Starting the DECcmi Server - Server Process Already Running #cmi_startup Stopping running DECcmi server ... Initializing shared memory ... Loading cmi_srv process ... DECcmi - Control and Management Utility [V2.17] ----------------------------------------------- CMU [0079] 1) Process cmi_srv started CMU [0083] 2) MBX cmi_srv opened CMU [0061] 3) Sending ADM_REQ to cmi_srv CMU [0016] Command mode is DEFAULT Prefix CMU [0001] *** Received ADM_CNF from TASK cmi_srv CMU [0065] Sending ADM_CAU to cmi_srv CMU [0035] waiting for ADM_CAUCF from process cmi_srv CMU [0004] *** Received ADM_CAUCF from TASK cmi_srv CMU [0042] Command mode is EXPLICIT Prefix Starting cmi_srv process ... ********************** Bind OK **************************** ********************** Bind OK **************************** Example B-6 shows a DECcmi Server stop log. Example B-6 Stopping the DECcmi Server #cmi_shutdown Stopping running DECcmi server ... Releasing shared memory ... Sample Logs as Examples B-5 Example B-7 shows a DECcmi Standard profile. Example B-7 The DECcmi Standard Profile ; ; ***************************************************************** ; * * ; * Copyright (c) Digital Equipment Corporation, * ; * 1994,1995,1996 * ; * * ; * All Rights Reserved. Unpublished rights reserved under * ; * the copyright laws of the United States. * ; * * ; * The software contained on this media is proprietary to * ; * and embodies the confidential technology of Digital * ; * Equipment Corporation. Possession, use, duplication or * ; * dissemination of the software and media is authorized only * ; * pursuant to a valid written license from Digital Equipment * ; * Corporation. * ; * * ; * RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure * ; * by the U.S. Government is subject to restrictions as set * ; * forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013, * ; * or in FAR 52.227-19, as applicable. * ; * * ; ***************************************************************** ; ; ; cmi_profile.txt: ; ; File read by the Operator process cmi_cmu, during the invocation ; of cmi_startup script, to perform some dynamic configuration and ; actually start the DECcmi stack. ; ; THIS FILE MAY BE CUSTOMIZED, if the pre-configured values do not fit ; the customer's needs. ; The SECTION 1, managing the trace facility, the SECTION 2, dealing ; with P-ADDRESSes configuration, the SECTION 3, dealing with miscellaneous ; DECcmi stack parameters and the SECTION 5 dealing with private Abstract ; and Transfer syntaxes (useful only for CMI API), may be customized. ; All other SECTIONs must not be modified. ; ; NEVERTHELESS NO MODIFICATION IS NECESSARY if this pre-customization ; is used. ; ;--------------------------------------------------------------------------- ; ; ;----------------------- SECTION 0 : DO NOT MODIFY ------------------------- ; ; ; Waits for Operator process registration to OSIAM stack. ; $wait 1 ; ;--------------------- SECTION 1 : MAY BE CUSTOMIZED ----------------------- (continued on next page) B-6 Sample Logs as Examples Example B-7 (Cont.) The DECcmi Standard Profile ; ; ; Log traces in /usr/var/cmip/log/cmi_srv.log.bin file in binary format. ; To avoid flooding the relevant file system, you can comment the ; following statement to stop logging traces. ; Binary traces can be converted to source traces using cmi_fmt utility : ; cmi_fmt cmi_srv.log.bin > cmi_srv.log.txt . ; log on cmi_srv.log ; ; ;--------------------- SECTION 2 : MAY BE CUSTOMIZED ----------------------- ; ; ; This section deals with local P-ADDRESSes configuration. ; In order to modify a Selector, uncomment the relevant line and set the ; desired value; given values are default ones. ; The syntax is as follows: ; "define suffix C" where is the ascii value ; or of the selector (case sensitive) ; "define suffix H" where is the hexadecimal ; value of the selector ; WARNING: for XMP, the xom.ini file must be modified accordingly. ; ; ; XMP API P-SELECTORs (max 4 chars) ; ;define suffix 111 CI001 ;define suffix 112 CI002 ;... ;define suffix 126 CI016 ;... ;define suffix 174 CI064 ;... ;define suffix 200 CI090 ;... ;define suffix 237 CI127 ;define suffix 238 CI128 ; ; ; XMP API S-SELECTOR (max 16 chars) ; ;define suffix 109 CSSEL ; ; ; XMP API T-SELECTOR (max 32 chars) ; ;define suffix 099 CTLAN ; ; ; CMI API P-SELECTORs (max 16 chars ; 4 highly recommended to be ISP 11183 conformant) ; ;define suffix 51 CROSCMIWAN1 ;define suffix 52 CROSCMIWAN2 (continued on next page) Sample Logs as Examples B-7 Example B-7 (Cont.) The DECcmi Standard Profile ;... ;define suffix 57 CROSCMIWAN7 ;define suffix 58 CROSCMIWAN8 ;... ;define suffix 59 CROSCMILAN1 ;define suffix 60 CROSCMILAN2 ;... ;define suffix 65 CROSCMILAN7 ;define suffix 66 CROSCMILAN8 ; ; ; ROS API P-SELECTORs (max 16 chars ; 4 highly recommended to be ISP 11183 conformant) ; ;define suffix 31 CROSWAN1 ;define suffix 32 CROSWAN2 ;... ;define suffix 37 CROSWAN7 ;define suffix 38 CROSWAN8 ;... ;define suffix 39 CROSLAN1 ;define suffix 40 CROSLAN2 ;... ;define suffix 45 CROSLAN7 ;define suffix 46 CROSLAN8 ; ; ; CMI/ROS API S-SELECTOR (max 16 chars) ; ;define suffix 110 Csession ; ; ; CMI/ROS API T-SELECTOR (max 32 chars) ; ;define suffix 100 Ctransport ; ; ;--------------------- SECTION 3 : MAY BE CUSTOMIZED ----------------------- ; ; This section deals with miscellaneous parameters of the DECcmi stack, ; which can be modified in order to change its behavior, or to tune it. ; Note that all the commands of this section must be performed before the ; start of the OSIAM stack (SECTION 4). ; ;............................ 3.1 ........................................ ; ; This sub-section deals with the format of Object IDentifiers. ; The default configuration of CMISE entity expects OIDs encoded without ; Tag and Length prefixes (ex: { 1 2 3 } serialized as 2a03). ; In order to mofify this behavior, and use OIDs prefixed by their Tag ; and Length (ex: {1 2 3} serialized as 06022a03), uncomment the relevant ; line (this can be done on a per CMISE SAP basis). ; ;define feature 71 00000000 ;... (continued on next page) B-8 Sample Logs as Examples Example B-7 (Cont.) The DECcmi Standard Profile ;define feature 79 00000000 ;define feature 80 00000000 ;... ;define feature 86 00000000 ; ;............................ 3.2 ........................................ ; ; This sub-section permits to modify MCS entity parameters, to change the ; entity behavior or to configure it in regard to the DECcmi stack activity. ; Note that MCS is dedicated to XMP API and is not used by CMI and ROS APIs. ; vary entity 78 parm 00 16 ; vary entity 78 parm 00 value ; - entity 78: MCS entity ; - parm 00: confirmed request block number, representing the number of ; concurrent confirmed operations handled on invoker side ; - value: 1 up to 255, unit 10 blocks ; -> to be increased to support a high number of associations and/or ; an important flow of confirmed operations per association ; vary entity 78 parm 01 16 ; vary entity 78 parm 01 value ; - entity 78: MCS entity ; - parm 01: confirmed indication block number, representing the number of ; concurrent confirmed operations handled on performer side ; - value: 1 up to 255, unit 10 blocks ; -> to be increased to support a high number of associations and/or ; an important flow of confirmed operations per association ; vary entity 78 parm 03 0 ; vary entity 78 parm 03 value ; - entity 78: MCS entity ; - parm 03: request timer value, specifying the time to wait for the ; confirmation of a request ; - value: 0 up to 255, unit 5 seconds, 0 meaning no limit ; ;............................ 3.3 ........................................ ; ; This sub-section deals with internal DECcmi common resources, to be tuned ; using the following hints. ; Nevertheless note that normally the pre-defined configuration should ; support a heavy traffic (high number of associations, important flow of ; operations/events, huge data transfer). ; define pool 512 512 512 ; define pool nb_buf data_elem_sz nb_data_elem ; - nb_buf: number of buffer control structures (1 up to 1024) ; -> to be increased to support a high number of associations and/or an ; important flow of operations/events per association ; - data_elem_sz: size of data elements (8 up to 4096) ; -> to be increased to support huge data transfer ; -> . may impact performances, because corresponds to the size of data ; sent/received at DECnet-Plus level (Transport Interface Data Units) ; . best performances are obtained when data_elem_sz is greater or ; equal to the average size of Transport Protocol Data Units (continued on next page) Sample Logs as Examples B-9 Example B-7 (Cont.) The DECcmi Standard Profile ; (TIDU size >=TPDU size) ; . configuring a too high value may increase too much the size of the ; cmi_srv server process ; - nb_data_elem: number of data elements (4 up to 1024) ; -> to be increased to support a high number of associations and/or ; huge data transfer ; define interactions 512 ; define interactions nb_inter ; - nb_inter: number of interactions ; -> to be increased to support a high number of associations and/or an ; important flow of operations/events per association ; ; ;----------------------- SECTION 4 : DO NOT MODIFY ------------------------- ; ; ; Starts the OSIAM stack. ; $wait 1 start ; ; ;--------------------- SECTION 5 : MAY BE CUSTOMIZED ----------------------- ; ; ; This section permits to add dynamically up to 9 private Abstract or ; Transfer syntaxes to the set of syntaxes already known by the server. ; It is only useful for the CMI API, configured with "old" OID management, ; the XMP API not using this feature because configured with new OID ; management. ; In order to add your own values, replace the current values by the ; desired ones; given values are just samples. ; The syntax is as follows: ; "pst oid insert ", ; where is the encoded Object Id (OID) of the syntax. ; The following rules apply for the encoding of the OID: ; - the OID tag is not specified, ; - the seven low order bits of the first byte give the OID length, ; (maximum value for length is 11 (0x0B) ; - the high order bit (0x80) of the first byte must be set as follows: ; - 0 for a transfer syntax, ; - 1 for an abstract syntax. ; - the following bytes are the encoded form of the OID as defined ; in X.209 (chapter 22: "Encoding of an object identifier value") (continued on next page) B-10 Sample Logs as Examples Example B-7 (Cont.) The DECcmi Standard Profile ; ; As an example, the CMIP Abstract syntax is ; {joint-iso-ccitt(2) ms(9) cmip(1) cmip-pci(1) abstractSyntax(4)} ; and is coded as { 0x84, 0x59, 0x01, 0x01, 0x04 } ; with 0x84 = 0x80 + 4 (length) ; 0x59 = 40*2 + 9 (joint-iso-ccitt + ms) ; 0x01 = cmip ; 0x01 = cmip-pci ; 0x04 = abstractSyntax ; ; WARNING: the syntax indexes used in applications (P_K_PRIV_ABS[1 up to 9]) ; rely on the sequential order of the "pst oid insert ..." commands. ; So do not delete or duplicate any of the following commands, just replace ; the sample OID values by your OID if any !!! ; ; Uncomment the following line to get a trace of the syntax insertion. ;vary sap 19 trace on ; ; syntax P_K_PRIV_ABS1 pst oid insert H8459010105 ; syntax P_K_PRIV_ABS2 pst oid insert H8459010106 ; syntax P_K_PRIV_ABS3 pst oid insert H8459010107 ; syntax P_K_PRIV_ABS4 pst oid insert H8459010108 ; syntax P_K_PRIV_ABS5 pst oid insert H8459010109 ; syntax P_K_PRIV_ABS6 pst oid insert H845901010A ; syntax P_K_PRIV_ABS7 pst oid insert H845901010B ; syntax P_K_PRIV_ABS8 pst oid insert H845901010C ; syntax P_K_PRIV_ABS9 pst oid insert H845901010D ; $wait 1 ; ; ;----------------------- SECTION 6 : DO NOT MODIFY ------------------------- ; ; ; Exits from Operator process. ; $wait 1 $exit Sample Logs as Examples B-11 Example B-8 shows a log of how to remove a DECcmi kit when a server process is currently running. Example B-8 Removing the DECcmi Kit - Server Process Currently Running #setld -d CMACMV217 DECcmi V2.17 for DIGITAL UNIX (CMACMV217) - removal completed Copyright (c) Digital Equipment Corporation, 1993,1994,1995. All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. The software contained on this media is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, duplication or dissemination of the software and media is authorized only pursuant to a valid written license from Digital Equipment Corporation. RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, as applicable. DECcmi V2.17 for DIGITAL UNIX (CMACMV217) - installation script WARNING: DECcmi server is running Do you want to continue ? (y/n) :y Calling cmi_shutdown procedure ... Stopping running DECcmi server ... Releasing shared memory ... Remove the DECcmi V2.17 for DIGITAL UNIX subset ? (y/n) :y You might have customized the /usr/var/cmip/conf/cmi_profile.txt file. This profile file is saved in /tmp/cmi_profile.txt Deleting "DECcmi V2.17 for DIGITAL UNIX" (CMACMV217). B-12 Sample Logs as Examples Example B-9 shows an NCL command that displays the OSI Transport Templates. Example B-9 NCL Command Showing the OSI Transport Templates # ncl ncl> show osi transport template * all Node 0 OSI Transport Template Default AT 1994-11-23-15:19:28.741+01:00I2.497 Identifiers Name = Default Characteristics Keepalive Time = 60 SECONDS Retransmit Threshold = 8 Initial Retransmit Time = 5 SECONDS CR Timeout = 30 SECONDS ER Timeout = 30 SECONDS Network Service = CLNS Classes = { 4 } Checksums = False Maximum NSDU Size = 2048 OCTETS Expedited Data = True CONS Template = "OSI Transport" Use CLNS Error Reports = False Acknowledgement Delay Time = 1 SECONDS Local NSAP = 49::00-3F:AA-00-04-00-A4-FF:21 Send Implementation Id = True Extended Format = True Send Request Acknowledgement = True _______ Node 0 OSI Transport Template clns AT 1994-11-23-15:19:28.762+01:00I2.497 Identifiers Name = clns Characteristics (continued on next page) Sample Logs as Examples B-13 Example B-9 (Cont.) NCL Command Showing the OSI Transport Templates Keepalive Time = 60 SECONDS Retransmit Threshold = 8 Initial Retransmit Time = 5 SECONDS CR Timeout = 30 SECONDS ER Timeout = 30 SECONDS Network Service = CLNS Classes = { 4 } Checksums = False Maximum NSDU Size = 2048 OCTETS Expedited Data = True CONS Template = "OSI Transport" Use CLNS Error Reports = False Acknowledgement Delay Time = 1 SECONDS Local NSAP = 49::00-3F:AA-00-04-00-A4-FF:21 Send Implementation Id = True Extended Format = True Send Request Acknowledgement = True _______ Node 0 OSI Transport Template any AT 1994-11-23-15:19:28.764+01:00I2.497 Identifiers Name = any Characteristics Keepalive Time = 60 SECONDS Retransmit Threshold = 8 Initial Retransmit Time = 5 SECONDS CR Timeout = 30 SECONDS ER Timeout = 30 SECONDS Network Service = ANY Classes = { 0, 2, 4 } Checksums = False Maximum NSDU Size = 2048 OCTETS Expedited Data = True CONS Template = "OSI Transport" Use CLNS Error Reports = False Acknowledgement Delay Time = 1 SECONDS Local NSAP = / Send Implementation Id = True Extended Format = True Send Request Acknowledgement = True _______ Node 0 OSI Transport Template cons AT 1994-11-23-15:19:28.765+01:00I2.497 Identifiers Name = cons Characteristics (continued on next page) B-14 Sample Logs as Examples Example B-9 (Cont.) NCL Command Showing the OSI Transport Templates Keepalive Time = 60 SECONDS Retransmit Threshold = 8 Initial Retransmit Time = 5 SECONDS CR Timeout = 30 SECONDS ER Timeout = 30 SECONDS Network Service = CONS Classes = { 0, 2 } Checksums = False Maximum NSDU Size = 2048 OCTETS Expedited Data = True CONS Template = "OSI Transport" Use CLNS Error Reports = False Acknowledgement Delay Time = 1 SECONDS Local NSAP = /3654522410000101 Send Implementation Id = True Extended Format = True Send Request Acknowledgement = True _______ ncl> Sample Logs as Examples B-15 Example B-10 shows a log of how to remove a DECcmi kit when there is no Server process currently running. Example B-10 Removing the DECcmi Kit - No Server Process Currently Running #setld -d CMACMV217 DECcmi V2.17 for DIGITAL UNIX (CMACMV217) - removal completed Copyright (c) Digital Equipment Corporation, 1993,1994,1995. All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. The software contained on this media is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, duplication or dissemination of the software and media is authorized only pursuant to a valid written license from Digital Equipment Corporation. RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, as applicable. DECcmi V2.17 for DIGITAL UNIX (CMACMV217) - installation script Remove the DECcmi V2.17 for DIGITAL UNIX subset ? (y/n) :y You might have customized the /usr/var/cmip/conf/cmi_profile.txt file. This profile file is saved in /tmp/cmi_profile.txt Deleting "DECcmi V2.17 for DIGITAL UNIX" (CMACMV217). Example B-11 shows an installation failure due to a license problem. Example B-11 Kit Installation Failure Due to License Problem #setld -l . CMACMV217 Checking file system space required to install specified subsets: File system space checked OK. Copyright (c) Digital Equipment Corporation, 1993,1994,1995. All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. The software contained on this media is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, duplication or dissemination of the software and media is authorized only pursuant to a valid written license from Digital Equipment Corporation. (continued on next page) B-16 Sample Logs as Examples Example B-11 (Cont.) Kit Installation Failure Due to License Problem RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, as applicable. DECcmi V2.17 for DIGITAL UNIX (CMACMV217) - installation script WARNING: No license has been found for this product: DECcmi V2.17 for DIGITAL UNIX includes support for the License Management Facility. A Product Authorization Key ( PAK ) must be registered in the License Database ( LDB ) of the node on which this software will be used before the product can be accessed. You need the following license: ROS-RT-OA For information on registering and activating the PAK, refer to this product's Installation Guide, or to the Guide to Software Licensing, which is part of the Operating System documentation set. DECcmi V2.17 for DIGITAL UNIX Copying from . (disk) Verifying To start your CMIP process server you need to define the symbols UPLROOT=/usr/var/cmip CMISE_INBOUND=any Configuring "DECcmi V2.17 for DIGITAL UNIX" (CMACMV217) DECcmi V2.17 for DIGITAL UNIX (CMACMV217) - installation completed Example B-12 shows an IVP failure due to a license problem. Example B-12 IVP Failure Due to License Problem #setld -v CMACMV217 DECcmi V2.17 for DIGITAL UNIX (CMACMV217) Copyright (c) Digital Equipment Corporation, 1993,1994,1995. All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. The software contained on this media is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, duplication or dissemination of the software and media is authorized only pursuant to a valid written license from Digital Equipment Corporation. (continued on next page) Sample Logs as Examples B-17 Example B-12 (Cont.) IVP Failure Due to License Problem RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, as applicable. DECcmi V2.17 for DIGITAL UNIX (CMACMV217) - installation script DECcmi V2.17 for DIGITAL UNIX (CMACMV217) - Checking for CMIP library and header files... DECcmi V2.17 for DIGITAL UNIX (CMACMV217) - Checking example programs... DECcmi V2.17 for DIGITAL UNIX (CMACMV217) - Compiling example programs... WARNING: No license has been found for this product: DECcmi V2.17 for DIGITAL UNIX includes support for the License Management Facility. A Product Authorization Key ( PAK ) must be registered in the License Database ( LDB ) of the node on which this software will be used before the product can be accessed. You need the following license: ROS-RT-OA For information on registering and activating the PAK, refer to this product's Installation Guide, or to the Guide to Software Licensing, which is part of the Operating System documentation set. ERROR License not loaded Can't execute Full IVP setld: ivp failed. Example B-13 shows a start failure due to a license problem. Example B-13 DECcmi Start Failure Due to License Problem #cmi_startup Initializing shared memory ... Loading cmi_srv process ... DECcmi - Control and Management Utility [V2.17] ----------------------------------------------- ERROR: This application will not run successfully unless it is used on the processor(s) on which it is licensed. The licensed processor(s) is the one(s) on which the product requiring the ROS-RT-OA PAK will execute. A ROS-RT-OA PAK must be registered in the License Database and activated in the kernel cache before this application will run. Refer to the installation guide for the product requiring the ROS-RT-OA PAK for license database PAK registration instructions. CMU [0078] 1) Cannot start process cmi_srv Starting cmi_srv process ... B-18 Sample Logs as Examples