TeMIP OSI Management Toolkit V2.1.A Release Notes Operating System : Digital UNIX V4 Software version: V2.1.A Level 3 Date: 18 November 1997 -i- Copyright © 1997 by Digital Equipment Corporation Contents 1 Introduction iv 2 Installation prerequisites 5 2.1 Required Digital UNIX products 5 2.2 Required TeMIP Framework product 5 3 OSI Access Module 6 3.1 Known problems 6 3.1.1 Address resolution 6 3.1.2 Create response 6 3.2 Restrictions 6 3.2.1 User data limitation 6 3.2.2 Management Model update 7 3.2.3 Time Specification in Directives 7 3.2.4 Access Control 7 3.2.5 Object Class 7 3.2.6 Naming Attributes 7 3.2.7 Reference Object Instance 8 3.2.8 Attribute Identifiers 8 3.2.9 Event Type Identifiers 8 3.2.10 Action Type Identifiers 8 3.2.11 ASN.1 Data Types Mapping 8 -ii- 3.2.11.1 Recursive Data Types 8 3.2.11.2 REAL Data Type 8 3.2.11.3 BitString data type 8 3.2.11.4 ObjectInstance, RDNSequence, DistinguishedName to FullEntityName mapping 9 3.2.12 Agents 9 3.2.12.1 Maximum number of Agents 9 3.2.12.2 OSI Dictionary 9 3.2.13 Installing the TeMIP OSI Management Toolkit 9 3.2.14 Create Request 10 3.2.15 Get Directive with Iconic Map 10 3.3 Problems Reporting 10 4 GDMO Translator 12 4.1 Known problems 12 4.1.1 PARAMETER CONTEXT context-keyword 12 4.1.2 Warning Message 9300 13 4.1.3 Attribute MSL names 13 4.1.4 REGISTERED AS construct 14 4.2 Restrictions 14 4.2.1 Introduction 14 4.2.2 DeltaGDMO MCC-NAME 14 4.2.3 ASN.1 Type [1][2] ANY DEFINED BY attributeId 15 4.2.4 ASN.1 Type ANY 15 -iii- 4.2.5 Translation to TeMIP Defined Log Record Types 15 5 GDMO Browser 16 5.1 Known problems 16 5.1.1 Loading documents 16 5.1.2 Write protections 16 5.2 Restrictions 16 5.2.1 Filter option 16 5.2.2 Configuration file 17 5.2.3 Add Subordinate 17 1 Introduction TeMIP OSI Management Toolkit V2.1.A Level 3 is the SSB. The TeMIP OSI Management Toolkit Release Notes concern the following product parts: · OSI Access Module, · GDMO Translator, · GDMO Browser. For each product part, these document will describe: · known problems but not yet fixed, · existing restrictions. Please read this document before installing or using this software. 2 Installation prerequisites -iv- 2.1 Required Digital UNIX products TeMIP OSI Management Toolkit requires the Digital UNIX V4.0B (Rev. 564) to be installed. The OSFBASE410 (base system) subset is at least required. For the other OSF/1 and DECnet subsets, please refer to the TeMIP Framework V3.1.A Release Notes and the DECcmi V2.17 Release Notes. 2.2 Required TeMIP Framework product TeMIP OSI Management Toolkit requires TeMIP Framework V3.1.A to be installed. The following subsets are required: · TeMIP Framework Base System, TFRBASEV31A (level 5), · TeMIP Framework Release Notes , TFRRELV31A (level 5), · TeMIP Framework Developer Toolkit , TFRTKV31A (level 5), · TeMIP Framework Presentation Modules , TFRPMV31A (level 5), · TeMIP Framework Server, TFRSERVERV31A (level 5) 3 OSI Access Module 3.1 Known problems This chapter describes the problems known in the current release of the TeMIP OSI Access Module product. 3.1.1 Address resolution TEMIP_MNT_EXTERNAL QAR#0377 The OSI AM has an unconsistent behaviour when searching information in cache memory. Once the information about the Agent/Entity relation is stored in cache, the OSI AM becomes case unsensitive concerning the ManagedObject instance name, whereas it is case sensitive when the information is searched in MIR. In addition, the OSI AM sends to the remote Agent the instance name as it is in the in_entity and not as it has been Installation prerequisites 5 created. 3.1.2 Create response TEMIPV30 MNT EXT QAR#684 The OSI AM encodes a MSL argument in the TeMIP Create Response whereas the MSL description doesn't define any argument. The inconsistency between the OSI AM and the GDMO Translator leads to the "No Entity" error message at the FCL PM. 3.2 Restrictions Some of these restrictions are related to the usage of TeMIP Framework and some to the support of the ISO standards for GDMO, ASN.1 and CMIP. 3.2.1 User data limitation The TeMIP Framework limits user data (for outgoing and incoming directives) to 30K. 3.2.2 Management Model update Any modification of the management model supported by the OSI Access Module requires to restart the OSI AM Server process to update the OSI Dictionary from the OSI Dictionary file produced by the GDMO Translator. 3.2.3 Time Specification in Directives The OSI Access Module ignores the time specification associated with an MCC directive. It always assumes a value of NOW and processes immediately the directive. 3.2.4 Access Control There is no check on the Access Control parameter of Associate Indications. The OSI AM does not set the Access Control parameter of the CMIP operations. OSI Access Module 6 3.2.5 Object Class The ObjectClass ASN.1 data type is defined in ISO/IEC 9596-1 (CMIP)as: ObjectClass ::= CHOICE { globalForm [0]IMPLICIT OBJECT IDENTIFIER, localForm [1]IMPLICIT INTEGER } The OSI Access Module supports the globalForm for identification of object classes. 3.2.6 Naming Attributes The OSI Access Module restricts the ASN.1 data types of naming attributes to: PrintableString, GraphicsString, VisibleString, IA5String, NumericString, ObjectIdentifierString, Integer, Boolean. The ASN.1 strings are mapped into a MCC SimpleName or Latin1string for child entities and into a MCC FullName for global entities. The use of the Boolean data type for global entities is not recommended, because the registration and notification on these entities will not work. Note that the ASN.1 GeneralString data type is not supported at all. 3.2.7 Reference Object Instance MCC does not provide the capability of requesting the creation of a new object instance using only the name of a reference object of the same class as the object to be created. As a consequence the OSI Access Module does not make use of this capability of CMIP. 3.2.8 Attribute Identifiers Only the global form (ASN.1 Object Identifier) is supported for the attribute identifiers. OSI Access Module 7 3.2.9 Event Type Identifiers Only the global form (ASN.1 Object Identifier) is supported for the event type identifiers. 3.2.10 Action Type Identifiers Only the global form (ASN.1 Object Identifier) is supported for the action type identifiers. 3.2.11 ASN.1 Data Types Mapping 3.2.11.1 Recursive Data Types Recursives data types, allowed in ASN.1, are not supported by TeMIP Framework and therefore by the OSI Access Module. The only exception is the CMISFilter, specified in ISO/IEC 9596-1 (CMIP), for which a specific mapping is provided with the restriction that string assertions are not supported (refer to the GDMO Translator User's Guide). 3.2.11.2 REAL Data Type This data type is supported with the restrictions that only base 2 is supported. 3.2.11.3 BitString data type The current release of the OSI Access Module does not support the constructed form of the BER encoding of the ASN.1 BitString data type. 3.2.11.4 ObjectInstance, RDNSequence, DistinguishedName to FullEntityName mapping As the maximum size of an ILV encoding is 30K on TeMIP Framework, an attribute value whose ASN.1 data type is a set (or sequence) of ObjectInstance, RDNsequence or DistinguishedName must be encoded in BER with a length around 4K because of the expansion BER-to-ILV in this particular case. 3.2.12 Agents 3.2.12.1 Maximum number of Agents OSI Access Module 8 The maximum number of ACSE associations is limited to 128. 3.2.12.2 OSI Dictionary The OSI Dictionary which contains the Management Information Model has the following limitations: - Maximum depth of the Management Information Tree = 15 - Maximum number of child Object Classes of an Object Class = 100 - Maximum number of Attributes of an Object Class = 250 - Maximum number of Operation types of an Object Class = 50 - Maximum number of Notifications types of an Object Class = 50 - Maximum number of Processing Failure errors of an Operation = 50 - Maximum number of Arguments of an Operation, Response or Notification = 50 - Maximum number of Fields within a structured Data Type = 100 - Maximum number of Enumeration items of a Data Type = 512 - Maximum number of ASN.1 Object Identifier values associated with a GDMO Parameter = 256 - Maximum number of items of an ASN.1 Object Identifier = 15 3.2.13 Installing the TeMIP OSI Management Toolkit When installing the TeMIP OSI Management Toolkit, the GDMO translator subset must be installed before the OSI AM subset. The order of the subsets installation is: Release Notes subset, GDMO subset and then the OSI AM subset. 3.2.14 Create Request It is defined in the Recommendation X.710 that the ManagedObjectInstance is optional in the Create Request. The OSI AM doesn't implement this feature and will send exclusively an ObjectInstance or a SuperiorObjectInstance. 3.2.15 Get Directive with Iconic Map It is not possible to enter each SETOF element of the AttributeIdList argument using the "Add Another" widget. The complete argument value shall be provided at one time as it is OSI Access Module 9 done at FCL PM interface. 3.3 Problems Reporting The procedure to report problems occuring when using the OSI Access Module is the following: 1. Prepare the environment to gather the data: a. stop the TeMIP OSI AM server. b. modify the configuration file in order to set full traces. The file /usr/var/kits/temip_osi_am/temip_osi_am_configuration.dat must contain: TRACE_LOG_MODE 15 ERROR_LOG_MODE 1 c. clean the directory /var/kits/temip_osi_am/error/*.log d. clean the directory /var/kits/temip_osi_am/trace/*.log e. start the TeMIP OSI AM server f. do a script file to capture cmip traces: (1)%script cmip_trace.log (2)csh> cmi_cmu (3)when in the tool type (a)debug on (b)deb mode y 2 g. issue a GETEVENT at the FCL PM and save in a file. Use a script to catch this information: (1)%script fcl_trace.log (2)setenv MCC_FCL_PM_LOG 0x8 (3)csh> manage h. send an event from the agent. i. stop the cmip trace, in the cmip window trace, type: debug off $exit ($ must be typed) 2.Run temip utility OSI Access Module 10 when the notification has been emited through the osi_am and not been received by temip, issue the temip_qar utility. This will create a file that you will include in the QAR (or FAX it). % temip_qar 3.Return the following information: a. Description of how exactly the problem happens. b. Provide the files: cmip_trace_log, /var/kits/temip/temip_qar.txt, /var/kits/temip_osi_am/error/*.log, /var/kits/temip_osi_am/trace/*.log c. Provide the result of the MCC GETEVENT of the FCL 4 GDMO Translator 4.1 Known problems 4.1.1 PARAMETER CONTEXT context-keyword The PARAMETER template of GDMO contains a CONTEXT construct. This construct has six options, one of which takes the form: context-type -> context-keyword context-keyword -> type-reference. where identifier is the name of a field in the management PDU specified by the type reference. The interpretation of the standard used in the GDMO Translator is that the identifier is the field name of the ANY DEFINED BY field itself. However, this can be ambiguous as illustrated by the following example taken from the library file temip_DMI.g: operationalViolation NOTIFICATION BEHAVIOUR operationalViolationBehaviour; WITH INFORMATION SYNTAX Notification-ASN1Module.SecurityAlarmInfo AND ATTRIBUTE IDS securityAlarmCause securityAlarmCause, OSI Access Module 11 securityAlarmSeverity securityAlarmSeverity, securityAlarmDetector securityAlarmDetector , serviceUser serviceUser , serviceProvider serviceProvider , notificationIdentifier notificationIdentifier, correlatedNotifications correlatedNotifications, additionalText additionalText, additionalInformation additionalInformation; REGISTERED AS { smi2Notification 8}; where serviceUser and serviceProvider are defined as: ServiceProvider ::= ServiceUser ServiceUser ::= SEQUENCE { identifier OBJECT IDENTIFIER, details ANY DEFINED BY identifier } The interpretation of the standard used in the GDMO Translator requires that the CONTEXT construct of a PARAMETER template for the serviceUser field of the above notification be of the form: CONTEXT Notification-ASN1Module.SecurityAlarmInfo.details; However, as there are two `details' fields in SecurityAlarmInfo -- one for serviceUser and one for serviceProvider -- the GDMO Translator is unable to determine for which field the PARAMETER template is directed. It raises an error (9200), cannot translate type, for these fields. The problem is solved if the GDMO Translator takes a different interpretation of the standard, and allows CONTEXT constructs of the form: CONTEXT Notification-ASN1Module.SecurityAlarmInfo.serviceUser and CONTEXT Notification-ASN1Module.SecurityAlarmInfo.serviceProvider Until this change is implemented in the GDMO Translator, a workaround is to change the definition of serviceProvider in temip_DMI.g to eliminate one of the `details' fields, e.g. serviceProvider ::= SEQUENCE { identifier OBJECT IDENTIFIER, detailsFoo ANY DEFINED BY identifier } and to reference details and detailsFoo from the CONTEXT construct of different PARAMETER templates for serviceUser and serviceProvider respectively. GDMO Translator 12 4.1.2 Warning Message 9300 The GDMO Translator warning message 9300, which indicates that an ANY DEFINED BY type is not associated with a PARAMETER template, is given even if this type is referenced as the syntax of an ATTRIBUTE template. The GDMO standard does not permit the PARAMETER template to be used to populate the ANY DEFINED BY syntax of an attribute, so use of the warning in this case is inappropriate and could be misleading. Note that although the warning message is given in such cases, the GDMO Translator does generate the correct MSL, OSI dictionary, etc. output files. 4.1.3 Attribute MSL names TEMIP_MNT_EXTERNAL QAR#0258 If a GDMO model contains attribute names quite similar, it could happen that the GDMO translator generates two identical MSL names for these attributes. Therefore, the MSL generated cannot be compiled. The workaround consists in defining delta-gdmo templates to force the generation of unique symbols. 4.1.4 REGISTERED AS construct TEMIP_MNT_EXTERNAL QAR#0335 The GDMO Translator doesn't support the clause 28.11 of Rec. X208 which specifies that an ObjectIdentifier can be defined with multiple "DefinedValue". In this case, the error 6711 is retuned at compilation time for such "REGISTERED AS" object identifier. Example: The following declaration is not supported: ... REGISTERED AS {company networkManagement 2} ... where: company OBJECT IDENTIFIER ::= { 1 2 276 0 11 } networkManagement INTEGER ::= 0 Replace it by: ... REGISTERED AS {cnm 2} ... where: company OBJECT IDENTIFIER ::= { 1 2 276 0 11 } networkManagement INTEGER ::= 0 cnm OBJECT IDENTIFIER ::= {company networkManagement } GDMO Translator 13 4.2 Restrictions 4.2.1 Introduction This section lists any restrictions of the GDMO Translator over and above any that have already been documented in the GDMO Translator User's Guide . Restrictions already documented there are not repeated in these Release Notes. 4.2.2 DeltaGDMO MCC-NAME Underscore character is not allowed in the identifier given in the DeltaGDMO MCC-NAME statement. 4.2.3 ASN.1 Type [1][2] ANY DEFINED BY attributeId The GDMO Translator will map an ASN.1 type of the form "ANY DEFINED BY attributeId", where attributeId has type AttributeId (from CMIP-1), into the MCC type ATTRIB. The GDMO Translator will also determine to do the mapping to MCC ATTRIB type if the "ANY DEFINED BY" is preceeded by a single tag, e.g. [1]ANY DEFINED BY attributeId. However, if it is proceeded by more than one tag, e.g. [1][2]ANY DEFINED BY attributeId, an error is given. 4.2.4 ASN.1 Type ANY The GDMO Translator does not support the ASN.1 type ANY and, in general, ASN.1 types that use the ANY type in their definition. An error is given by the Translator if such a type is detected. Note, however, that the well-known ASN.1 types RDNSequence, RelativeDistinguishedName and DistinguishedName , which also use ANY in their definitions are now supported by special handling in the GDMO Translator (see GDMO Translator User's Guide , section B.3.6). 4.2.5 Translation to TeMIP Defined Log Record Types The OSI Access Module (OSI-AM) does not currently support the mapping of selected ASN.1 types to the following three MCC types used in TeMIP log records: TemipUserDefinedEnum TemipUserDefinedType GDMO Translator 14 TemipAdditionalInfo These non-standard mappings are not applied by default by the GDMO Translator. They are applied only if requested through use of the MCC-TYPE construct. Therefore, the MCC-TYPE construct should not be used to force the above mappings until support for these has been included in the OSI_AM. 5 GDMO Browser 5.1 Known problems 5.1.1 Loading documents In the "Load Document Window" of the TeMIP GDMO Browser, if the user does not enter the document name in quotes then the Browser does not give a warning message and it puts the document name without the quotes in the TeMIP GDMO Translator configuration file. The incorrect format in the configuration file can then cause the Translator and Browser to generate errors when using it. 5.1.2 Write protections The directories where the Browser files are installed (/usr/kits/NOE210/gdmo/...) are write protected. Therefore, if you want to use the Browser to update the GDMO Translator configuration file (load libraries, modify libraries), make a local copy as explained in the GDMO Browser User's Guide. The Browser does not currently give a warning if you load new libraries when the configuration file is not writable. It only gives an error when it tries to update the configuration file. 5.2 Restrictions 5.2.1 Filter option GDMO Translator 15 The wildcard character "*" is not supported as a word prefix, but only as a word suffix. For example, an entry of "*:*alar*" in the Filter box in the main window of the Browser when the Attribute radio button has been selected, will not match any attributes in the library files, whereas a filter of "*:alar*" will. 5.2.2 Configuration file The GDMO Browser does not support blank lines in it's configuration file. Any "blank" line must begin with the comment characters "--" (without quotes). In addition, only full path names are supported in the specification of the index and error files. If the path starts with a "~" or a variable (e.g. $USER), an error will occur while saving the database. 5.2.3 Add Subordinate The Add Subordinate Class and Add Subordinate Namebinding & Class menu items of the MIT window cause a list of possible selections to be displayed, based on matching name bindings that are valid for the (Superior) managed object class selected from the MIT. If, however, the MIT selection refers to an (MCC) ENTITY instead of a (GDMO) CLASS, then no matching name bindings will be found and no entrires will be displayed. GDMO Browser 16 GDMO Browser 17