TeMIP OSI Management Toolkit V2.1.0 Release Notes Revision: V2.1.0 Level 1 Date: 6 November 1996 -i- Copyright © 1996 by Digital Equipment Corporation For Internal Use Only Contents 1 Introduction v 2 Installation prerequisites 6 2.1 Required Digital UNIX products 6 2.2 Required TeMIP Framework product 6 3 OSI Access Module 7 3.1 Enhancements and Changes 7 3.1.1 New mandatory environment variable : XDSROOT 7 3.1.2 Support mapping integer-asn <--> fullname-ilv for global class 7 3.1.3 ObjectIdentifier/FullName data type mapping 7 3.1.4 RelativeDistinguishedName/ATTRIB data type mapping 8 3.1.5 AP-Invocation and AE-Invocation parameters 8 3.1.6 Empty LocalDistinguishedName 9 3.1.7 OSI AM Demonstration 9 3.1.8 De-enrolling OSI AM Client 9 3.2 Problems fixed 10 3.2.1 Empty multiple replies 10 3.2.2 Bad encoding of reason code 10 3.2.3 IVP: Incorrect build of nsap entry 10 3.2.4 XMP Data limitation 10 -ii- 3.2.5 OSI AM Server shutdown 11 3.2.6 OSI AM Server startup 11 3.2.7 REAL datatype decoding 11 3.2.8 Multiple substrings in CMIS Filteritem truncated 11 3.2.9 Crash of OSI AM server onto strncat 12 3.2.10 Crash of DECcmi server under stress condition 12 3.3 Known Problems 12 3.3.1 Address resolution 12 3.4 Restrictions 12 3.4.1 User data limitation 13 3.4.2 Management Model update 13 3.4.3 Time Specification in Directives 13 3.4.4 Access Control 13 3.4.5 Object Class 13 3.4.6 Naming Attributes 13 3.4.7 Reference Object Instance 14 3.4.8 Attribute Identifiers 14 3.4.9 Event Type Identifiers 14 3.4.10 Action Type Identifiers 14 3.4.11 ASN.1 Data Types Mapping 14 3.4.11.1 Recursive Data Types 14 3.4.11.2 REAL Data Type 14 -iii- 3.4.11.3 BitString data type 15 3.4.11.4 ObjectInstance, RDNSequence, DistinguishedName to FullEntityName mapping 15 3.4.12 Agents 15 3.4.12.1 Maximum number of Agents 15 3.4.12.2 OSI Dictionary 15 3.4.13 Installing the TeMIP OSI Management Toolkit 16 3.4.14 Create Request 16 3.4.15 Get Directive with Iconic Map 16 3.5 Problems Reporting 16 4 GDMO Translator 18 4.1 Enhancements and Changes 18 4.2 Problems fixed 18 4.2.1 GDMO compiler produces bad attribute code 18 4.2.2 Inconsistent GDMO versus Visual TeMIP templates 18 4.2.3 DeltaGDMO MCC-CODE 0 does not work 19 4.2.4 GDMOxlat #include_msl_files_dir parsing problem 19 4.2.5 Vector File Optimisation 19 4.2.6 Generate DYNAMIC=TRUE as default 19 4.2.7 Support for additional ASN.1/MSL data type translations 20 4.3 Known problems 20 4.3.1 PARAMETER CONTEXT context-keyword 20 4.3.2 Warning Message 9300 22 -iv- 4.3.3 Attribute MSL names 22 4.3.4 REGISTERED AS construct 22 4.4 Restrictions 23 4.4.1 Introduction 23 4.4.2 DeltaGDMO MCC-NAME 23 4.4.3 ASN.1 Type [1][2] ANY DEFINED BY attributeId 23 4.4.4 ASN.1 Type ANY 23 4.4.5 Translation to TeMIP Defined Log Record Types 23 5 GDMO Browser 25 5.1 Enhancements and Changes 25 5.2 Problems fixed 25 5.3 Known problems 25 5.3.1 Loading documents 25 5.3.2 Write protections 25 5.4 Restrictions 26 5.4.1 Filter option 26 5.4.2 Configuration file 26 5.4.3 Add Subordinate 26 1 Introduction TeMIP OSI Management Toolkit V2.1.0 Level 1 is a new release which brings some bug fixes and enhancements to the previous major release V2.0.0. -v- 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: · the enhancements or changes since the previous release, · the problems fixed since the previous release, · the problems known but not yet fixed in the current release, · the restrictions existing in the current release. Please read this document before installing or using this software. 2 Installation prerequisites 2.1 Required Digital UNIX products TeMIP OSI Management Toolkit requires the Digital UNIX V3.2C (Rev. 214) to be installed. The OSFBASE350 (base system) subset is at least required. For the other OSF/1 and DECnet subsets, please refer to the TeMIP Framework V3.1.0 Release Notes and the DECcmi V2.15 Release Notes. 2.2 Required TeMIP Framework product TeMIP OSI Management Toolkit requires TeMIP Framework V3.1.0 to be installed. The following subsets are required: · TeMIP Framework Base System, TFRBASEV310 (level 1), · TeMIP Framework Release Notes , TFRRELV310 (level 1), · TeMIP Framework Developer Toolkit , TFRTKV310 (level 1), · TeMIP Framework Presentation Modules , TFRPMV310 (level 1), · TeMIP Framework Server, TFRSERVERV310 (level 1) Installation prerequisites 6 3 OSI Access Module 3.1 Enhancements and Changes 3.1.1 New mandatory environment variable : XDSROOT Due to a new release of the DECcmi stack, a new mandatory variable is needed before starting the OSIAM server: XDSROOT. This variable must be initialized as follow : (with csh) : setenv XDSROOT $UPLROOT/conf (with sh or ksh) : XDSROOT=$UPLROOT/conf ; export XDSROOT 3.1.2 Support mapping integer-asn <--> fullname-ilv for global class TEMIP-MNT-EXT QAR#00162 Integer-asn to fullname-ilv was not supported for global class and naming attribute of a class couldn't be of integer data type. OSI AM and GDMO translator now support this mapping. 3.1.3 ObjectIdentifier/FullName data type mapping Some Information Models contain the "agentCME" global managed object class whose definition comes from the NMF Library Volume 1. This class is named by the "cmeID" attribute with the "AE-title" syntax, defined in ASN.1 as follows : AE-title ::= CHOICE { AE-title-form1, AE-title-form2 } AE-title-form1 ::= Name AE-title-form2 ::= OBJECT IDENTIFIER As only the "AE-title-form2" is required for conformance, the OSI AM has been improved to support the ASN.1 Object identifier from/to MSL FullName mapping. The GDMO Translator will provide this mapping information in the OSI dictionary file for the global entity classes whose Naming attributes are defined with ASN.1 Object Identifier data type. OSI Access Module 7 3.1.4 RelativeDistinguishedName/ATTRIB data type mapping OSIAM_EXTERNAL QAR #0121 Some Information Models contain attributes with the "RelativeDistinguishedName" syntax, defined in ASN.1 as follows : RelativeDistinguishedName ::= SET OF AttributeValueAssertion AttributeValueAssertion ::= SEQUENCE {AttributeType, AttributeValue} AttributeType ::= OBJECT IDENTIFIER AttributeValue ::= ANY As only a single AVA is authorized when using OSI systems management, the ASN.1 "RelativeDistinguishedName" is mapped into the MSL ATTRIB datatype. The GDMO Translator generated MSL will specify MSL ATTRIB for any direct use of the ASN.1 RelativeDistinguishedName datatype. Existing special mappings of ASN.1 types which indirectly use RelativeDistinguishedName (e.g. DistinguishedName, ObjectInstance) are not affected by this new mapping. 3.1.5 AP-Invocation and AE-Invocation parameters OSIAM_EXTERNAL QAR #0098 In the previous release, the AgentTitle and ManagerTitle attributes of the Agent_Record class contained only information about the APTitle and AEQualifier. In the current release, the user is able to provide additional information such as: · the Application Process Invocation Identifier, · the Application Entity Invocation Identifier. The AgentTitle and ManagerTitle MSL data type becomes: TYPE APTitleType = 13 RECORD APtitle = 1 : ObjectIdentifierTypeString; AEQualifier = 2 : UNSIGNED32; APInvocation = 3 : UNSIGNED32; AEInvocation = 4 : UNSIGNED32; END RECORD; Example: TeMIP> show mcc 0 osi_am agent_record agent_1 Agent Title MCC LOCAL_NS:.temip.lisbon_director OSI_AM AGENT_RECORD "agent_1" On director: LOCAL_NS:.temip.lisbon_director AT Wed OSI Access Module 8 Jul 17 19:12:23 Characteristics Agent Title = ( APtitle = "{ 1 2 7 8 }", AEQualifier = 2, APInvocation = 1, AEInvocation = 2 ) If the APInvocation and AEInvocation fields are not provided in the AgentTitle and ManagerTitle attributes, the default values are set to 0. 3.1.6 Empty LocalDistinguishedName In the previous release, if the LDN Flag attribute was defined in the Agent_Record and if the FullEntityName contained only the global class level, the OSI AM built a DistinguishedName in despite of the LDN Flag presence. In the current version, If the LDN Flag is set and the FullEntityname contains only one AES level, the OSI AM maps the MSL class code into the CMIP Object Class and build an empty LocalDistinguishedName. Note that this is supposed to work for agents which manage only a single global instance. 3.1.7 OSI AM Demonstration A new directory ( /usr/kits/NOE210/temip_osi_am/demo) is now installed by the TeMIP OSI AM subset in order to provide an example of OSI AM customization and configuration. The goal of the TeMIP OSI AM demo is to make an OSI AM Manager communicate through the CMIP protocol stack, with two Agents (local or remote) responsible of managed objects described in a GDMO information model. For more information, please refer to chapter 7 of TeMIP OSI Managment Toolkit, OSI AM User's Guide document. 3.1.8 De-enrolling OSI AM Client Each time the "temip_osi_setup" script is run, the entries of the previous OSI AM Client enrolled are removed from the dispatch table and the new one are added. 3.2 Problems fixed OSI Access Module 9 This chapter describes the problems fixed since the previous major release of the TeMIP OSI Access Module product. 3.2.1 Empty multiple replies TEMIP_MNT_EXTERNAL QAR#0278 When the agent doesn't return any object selected on a wildcarded directive, the OSI AM encodes a Out_Entity equals to the In_Entity instead of mapping the CMIP Response into the MCC Exception "No Such Entity". New release returns now the MCC Exception "No Such Entity". 3.2.2 Bad encoding of reason code TEMIP MNT EXTERNAL QAR#0454 The OSI AM ILV encoding of the ReasonCode for constructed datatype was wrong : the Constructed level was omitted. This problem occured when using a FM build with Visual TeMIP which follows the regular ILV encoding rule. New OSI AM provides default values for all the unexistant AttributeValue. 3.2.3 IVP: Incorrect build of nsap entry TEMIP_MNT_EXTERNAL QAR#0433 When performing OSI AM IVP, the automatic build of nsap entry into /etc/nsaps was incorrect. Two problems have been solved : - incorrect build of nsap entry from DECnet address. - bad padding of nsap (IDI field of nsap address). 3.2.4 XMP Data limitation TEMIP_MNT_EXTERNAL QAR #0257, QAR#0287 In the previous release, the XMP API didn't support user data exceeding 10K in CMIP responses, CMIP exceptions and CMIP events. The annoying side effect was that confirmed CMIP events were never confirmed because ignored by XMP. In the current release, the limitation on user data size has been removed from the DECcmi stack.But a new limitation is now reached because the maping into TeMIP internal ILV structure is OSI Access Module 10 limited to 30K of data. 3.2.5 OSI AM Server shutdown TEMIP_MNT_EXTERNAL QAR #0290 In the previous release, the message "OSI AM server can not be stopped" was not adapted in the case where the Framework AM killed the process. In the current release, the message becomes: "temip_osi_server process has been forced to stop" 3.2.6 OSI AM Server startup TEMIP_MNT_EXTERNAL QAR #0396 On previous release, the message returned was confusing when OSI AM server could not be started because the Framework was not started. In the current release, the message becomes: "Failure !!" "The temip_osi_am process can not be started" " Run first temip_start to start TeMIP Framework" 3.2.7 REAL datatype decoding TEMIP_MNT_EXTERNAL QAR #0396 In the previous release, the BER encoding of a received REAL value should contain a length equal to 0, 9 or 10. If not, the error returned by the OSI AM was MCC_S_ILVNOTIMPLYET. In the current release, no restriction exists on the BER REAL encoding length. 3.2.8 Multiple substrings in CMIS Filteritem truncated CMIP QAR#00142 With previous version, multiple substrings in CMIS Filteritem were always truncated to the last substring. New OSI AM support multiple substring. 3.2.9 Crash of OSI AM server onto strncat OSI Access Module 11 OSIAM-EXT QAR#0046 The OSI AM server crashed when the OSI AM was making a call to the standard C run-time library routine 'strncat' to process a character string which was located at the limit of a shared memory segment. New OSI AM correct this problem by replacing 'strncat' with 'memcpy'. 3.2.10 Crash of DECcmi server under stress condition CMIP QAR#00198 Under stress condition the DECcmi server crashed when multiple associations were alternatively opened and closed. Problem fixed in Presentation and ROSE entities. 3.3 Known Problems This chapter describes the problems known in the current release of the TeMIP OSI Access Module product. 3.3.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 created. 3.4 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.4.1 User data limitation OSI Access Module 12 The TeMIP Framework limits user data (for outgoing and incoming directives) to 30K. 3.4.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.4.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.4.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. 3.4.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.4.6 Naming Attributes The OSI Access Module restricts the ASN.1 data types of naming attributes to: PrintableString, GraphicsString, VisibleString, IA5String, NumericString, OSI Access Module 13 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.4.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.4.8 Attribute Identifiers Only the global form (ASN.1 Object Identifier) is supported for the attribute identifiers. 3.4.9 Event Type Identifiers Only the global form (ASN.1 Object Identifier) is supported for the event type identifiers. 3.4.10 Action Type Identifiers Only the global form (ASN.1 Object Identifier) is supported for the action type identifiers. 3.4.11 ASN.1 Data Types Mapping 3.4.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 OSI Access Module 14 that string assertions are not supported (refer to the GDMO Translator User's Guide). 3.4.11.2 REAL Data Type This data type is supported with the restrictions that only base 2 is supported. 3.4.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.4.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.4.12 Agents 3.4.12.1 Maximum number of Agents The maximum number of ACSE associations is limited to 128. 3.4.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 = 50 - Maximum number of Attributes of an Object Class = 200 - 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 OSI Access Module 15 Notification = 50 - Maximum number of Fields within a structured Data Type = 50 - Maximum number of Enumeration items of a Data Type = 256 - 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.4.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.4.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.4.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 done at FCL PM interface. 3.5 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 OSI Access Module 16 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 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 OSI Access Module 17 4.1 Enhancements and Changes None 4.2 Problems fixed This chapter describes the problems fixed since the previous minor release of the TeMIP OSI Access Module product. 4.2.1 GDMO compiler produces bad attribute code OSIAM_EXTERNAL QAR #0258 With the previous version, the GDMO translator produced wrong MSL when the GDMO contained two attributes with similar names. The GDMO translator generated a single MSL code for the two attributes, thus MSL compilation was impossible. A "general" fix is not possible without a major re-design. This is not planned as the problem has an easy easy workaround, namely to use deltaGDMO to assign unique MSL symbols/codes to attributes. However, in this version the GDMO Translator symbol generating algorithm has been modified slightly to reduce the probability of hitting (but not eliminate) this problem. 4.2.2 Inconsistent GDMO versus Visual TeMIP templates OSIAM_EXTERNAL QAR #0339 With the previous version, the templates of the standard MSL directives (Set, Show, etc.) used by GDMO translator were not compatible with the ones used by Visual TeMIP, causing problems for Management Modules using both the GDMO Translator and Visual TeMIP components. In this version, the GDMO Translator templates have been aligned with those used by Visual TeMIP. A corresponding alignement has been made in the OSI-AM code. 4.2.3 DeltaGDMO MCC-CODE 0 does not work OSIAM_EXTERNAL QAR #0544 With the previous version, using the DeltaGDMO statement MCC-TYPE 0 in temip_DMI.dg to force zero-relative field codes for the ManagementExtension TYPE didn't work. GDMO Translator 18 Fixed in this version. 4.2.4 GDMOxlat #include_msl_files_dir parsing problem OSIAM_EXTERNAL QAR #0554 With previous version, the symbol #include_msl_files_dir of the GDMOXLAT config file was not correctly parsed. Fixed in this version. 4.2.5 Vector File Optimisation OSIAM_EXTERNAL QAR #0093 In previous versions of the product, the GDMO Translator did not attempt to optimize the contents of the vector file generated. Without optimization, large vector files are always generated for large information models, with much duplication , e.g. entries for the standard directives like Set and Show for each child entity. For some models, pre-defined TeMIP limits for dispatch table size were exceeded. These had to be pruned manually to provide a workaround. In this version of the product, the GDMO Translator now generates a single ellipsis entry in the vector file for each of the standard directives (Set, Show, etc.) at the immediate child entity level for each global entity. This substantially reduces the size of vector file generated for large information models. As part of this enhancement, the self-management dispatch table entries for the OSI-AM are no longer generated by temip_gdmoxlat. 4.2.6 Generate DYNAMIC=TRUE as default OSIAM_EXTERNAL QAR #0072. The MSL DYNAMIC definition, which applies only to child entity classes, is a boolean field that indicates whether the configuration information (about instances of the child entity) is to be stored in the MIR when the entity is registered. If TRUE, the information is not stored; if FALSE, the information is stored. If not specified, the default value for DYNAMIC is FALSE. In previous versions of the product, the GDMO Translator assumes this default and does not generate any DYNAMIC definition unless otherwise overwritten by the user via use of the deltaGDMO DYNAMIC statement on the MCC-ENTITY template. GDMO Translator 19 Customer feedback shows that users of the OSI-AM always change the DEFAULT value on child entities to TRUE. This requires all users to develop a deltaGDMO MCC-ENTITY template for each child class in their model. For a large model this can be very time consuming. In this version of the product, the GDMO Translator now generates an MSL DYNAMIC=TRUE statement as default for child entities. 4.2.7 Support for additional ASN.1/MSL data type translations OSIAM_EXTERNAL QAR #0120 , QAR #0121 In this version of the product, support has been added for the following ASN.1/MSL data type translations : o ASN.1 ObjectIdentifier -> MSL FullName o ASN.1 RelativeDistinguishedName -> MSL ATTRIB The first mapping applies only for attributes used to name global managed object classes (global entities). 4.3 Known problems 4.3.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, GDMO Translator 20 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 21 4.3.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.3.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.3.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 22 4.4 Restrictions 4.4.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.4.2 DeltaGDMO MCC-NAME Underscore character is not allowed in the identifier given in the DeltaGDMO MCC-NAME statement. 4.4.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.4.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.4.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 23 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 Enhancements and Changes None 5.2 Problems fixed None 5.3 Known problems 5.3.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.3.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 GDMO Translator 24 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.4 Restrictions 5.4.1 Filter option 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.4.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.4.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 25 GDMO Browser 26