TeMIP Version 3.1 for Digital UNIX Release Notes : Fixed problems, Know problems and restrictions Revision: 1.0 Date: 20 December 1996 Operating System and Version: Digital UNIX V3.2 G Software Version: TeMIP Framework V3.1.0, TeMIP Fault and Trouble Management V3.1.0 TeMIP Software Developer's Tookit V3.1.0 Visual TeMIP V1.1.0 Copyright © 1996 by Digital Equipment Corporation Contents 1 Introduction 9 2 System considerations 10 2.1 Installation prerequisites 10 2.1.1 Digital UNIX Mandatory and Recommended levels 10 2.1.1.1 Digital UNIX patch for DECsafe 10 3 Installation 11 3.1 Fixed problems 11 3.2 Known problems and restrictions 11 4 TeMIP Name Service 12 4.1 Fixed problems 12 4.1.1 TEMIP_MNT_EXTERNAL#00561 12 4.1.2 TEMIP_MNT_EXTERNAL#00676 12 4.1.3 TEMIP_MNT_EXTERNAL#00535 12 4.2 Known Problems and Restrictions 12 4.2.1 TEMIP_MNT_EXTERNAL#00627 12 4.2.2 TEMIPV31_INTERNAL#00892 13 4.2.3 TEMIPV31_INTERNAL#00458 13 4.2.4 TEMIPV31_INTERNAL#00953 13 4.2.5 TEMIPV31_INTERNAL#01082 13 4.2.6 TEMIPV31_INTERNAL#01102 13 4.2.7 TEMIPV31_INTERNAL#01124 13 4.2.8 TEMIPV31_INTERNAL#01129 13 4.2.9 TEMIPV31_INTERNAL#01134 14 4.2.10 TEMIPV31_INTERNAL#01137 14 4.2.11 TEMIPV31_INTERNAL#01221 14 4.2.12 TEMIP31_INTERNAL#01255 14 4.2.13 Using TNS Tracing 15 4.2.14 Configuring TeMIP in WAN configuration 16 4.2.15 TNS messages in daemon log file 16 4.2.16 Creating large numbers of objects in a single replicated directory 17 5 TeMIP Framework Kernel 18 5.1 Fixed problems 18 5.1.1 TEMIP_MNT_EXT#16 18 5.1.2 TEMIP_MNT_EXT#59 18 5.1.3 TEMIP_MNT_EXT#139 18 5.1.4 TEMIP_MNT_EXT#181 18 5.1.5 TEMIP_MNT_EXT#262 18 5.1.6 TEMIP_MNT_EXT#353 18 5.1.7 TEMIP_MNT_EXT#368 18 5.1.8 TEMIP_MNT_EXT#354 : 18 5.1.9 TEMIP_MNT_EXT#478 : 19 5.2 Known problems and restrictions 19 6 TeMIP Framework AM 20 6.1 Fixed problems 20 6.1.1 TEMIP_MNT_EXT#449 20 6.2 Known problems and restrictions 20 6.2.1 TEMIP_MNT_EXT#580 20 6.2.2 TEMIP_MNT_EXT#689 20 7 TeMIP Security 21 7.1 Fixed problems 21 7.1.1 TEMIP_MNT_EXT#236 21 7.1.2 MCC_OSF_EXTERNAL#228 21 7.1.3 MCC_OSF_EXTERNAL#310 21 7.1.4 MCC_OSF_EXTERNAL#386 21 7.2 Known problems and restrictions 21 7.2.1 TEMIP_MNT_EXT#39 21 7.2.2 TEMIP_MNT_EXT#622 21 7.2.3 TEMIP_MNT_EXT#651 22 7.2.4 TEMIPV31_INTERNAL#1208 22 8 TeMIP Framework Toolkit 23 8.1 Fixed problems 23 8.1.1 TEMIP_MNT_EXT#119 23 8.1.2 TEMIP_MNT_EXT#334 23 8.2 Known problems and restrictions 23 9 Visual TeMIP 24 9.1 Fixed problems 24 9.1.1 Wrapper Classes 24 9.1.1.1 MThread GetXxx routines (#I160) 24 9.1.2 Framework Classes 24 9.1.2.1 Crash in application code (#I157) 24 9.1.2.2 OnCancel not called on alerts (I#358) 24 9.1.2.3 Memory leaks on exception (TEMIP_MNT_EXT#491) 25 9.1.2.4 Random problems under stress (TEMIP_MNT_EXT#506) 25 9.2 Restrictions 25 9.2.1 Wrapper Classes 25 9.2.1.1 UseValue (I#249) 25 10 Alarm Handling FM 26 10.1 Fixed problems 26 10.1.1 TEMIP_MNT_EXTERNAL#89 and #107 26 10.1.2 TEMIP_OSF_EXTERNAL#160 26 10.1.3 TEMIPV31_INTERNAL#705 26 10.1.4 TEMIP_OSF_EXTERNAL#31 26 10.1.5 TEMIP_OSF_EXTERNAL#118 26 10.1.6 TEMIP_OSF_EXTERNAL#170 26 10.1.7 TEMIP_MNT_EXTERNAL#8 26 10.1.8 TEMIP_MNT_EXTERNAL#75 27 10.1.9 TEMIP_MNT_EXTERNAL#85 27 10.2 Known problems and restrictions 27 10.2.1 TEMIP_MNT_EXTERNAL#393 27 10.2.2 TEMIP_MNT_EXTERNAL#649 27 11 Event Log FM 28 11.1 Fixed problems 28 11.2 Known problems and restrictions 28 12 Trouble Ticketing FM 29 12.1 Fixed problems 29 12.1.1 TEMIP_OSF_EXTERNAL#241 29 12.1.2 TEMIPV31_INTERNAL#239 29 12.1.3 TEMIP_V31_INTERNAL#744 29 12.1.4 TEMIP_V31_INTERNAL#733 29 12.2 Known problems and restrictions 29 12.2.1 TEMIPV31_INTERNAL#750 29 12.2.2 TEMIP_V31_INTERNAL#361 29 13 Event Filtering and Correlation FM 30 13.1 Fixed problems 30 13.1.1 TEMIPV31_INTERNAL#411 30 13.2 Known problems and restrictions 30 14 Registration FM 31 14.1 Fixed problems 31 14.1.1 TEMIPV31_INTERNAL#191 31 14.2 Known problems and restrictions 31 15 Domain FM 32 15.1 Fixed problems 32 15.1.1 TEMIPV31_INTERNAL#354 32 15.2 Known problems and restrictions 32 15.2.1 V31_INTERNAL#1103 32 16 Notification FM 33 16.1 Fixed problems 33 16.1.1 TEMIPV31_INTERNAL#590 33 16.2 Known problems and restrictions 33 17 Alarms FM 34 17.1 Fixed problems 34 17.2 Known problems and restrictions 34 17.2.1 Number of enabled rules per TeMIP director 34 17.2.2 mcc_alarms_extract_rules 34 18 Collection AM 35 18.1 Fixed problems 35 18.2 Known problems and restrictions 35 19 Alarm Generator AM 36 19.1 Fixed problems 36 19.2 Known problems and restrictions 36 20 Script AM 37 20.1 Fixed problems 37 20.2 Known problems and restrictions 37 20.2.1 TEMIPV31_INTERNAL#671 37 21 Circuit AM 38 21.1 Fixed problems 38 21.2 Known problems and restrictions 38 22 DECnet IV AM 39 22.1 Problems Fixed 39 22.2 Known Problems and Restrictions 39 22.2.1 TEMIPV31_INTERNAL#00990 39 23 DECnet/OSI AM 40 23.1 Problems Fixed 40 23.2 Known Problems and Restrictions 40 23.2.1 TEMIPV31_INTERNAL#00999 40 24 TCPIP AM and Related Applications 41 Introduction 9 24.1 Problems Fixed 41 24.1.1 TEMIP_MNT_EXTERNAL#00313 41 24.1.2 TEMIP_MNT_EXTERNAL#00395 41 24.1.3 TEMIP_MNT_EXTERNAL#00301 41 24.2 Known Problems and Restrictions 42 24.2.1 TEMIP_MNT_EXTERNAL#00269 42 24.2.2 TEMIP_MNT_EXTERNAL#00445 42 24.2.3 TEMIP_MNT_EXTERNAL#00426 42 24.2.4 TEMIP_MNT_EXTERNAL#00699 42 24.2.5 TEMIPV31_INTERNAL#00923 42 24.2.6 TEMIPV31_INTERNAL#00989 43 25 Iconic Map PM 44 25.1 Fixed problems 44 25.1.1 MCC_OSF_EXT#364 44 25.1.2 TEMIP_MNT_EXT#002 44 25.2 Known problems and restrictions 44 25.2.1 TeMIP Presentation Modules in a CDE environment 44 25.2.2 24-planes graphical board support 44 25.2.3 Syntax for SET OF AttribId 45 25.2.4 Running the Iconic Map in a backgroud process under csh 45 26 FCL PM 46 System considerations 10 26.1 Fixed problems 46 26.1.1 TEMIP_EXT 102-105 MNT_EXT 007 46 26.2 Known problems and restrictions 46 27 NMS PM 47 27.1 Fixed problems 47 27.2 Known problems and restrictions 47 27.2.1 MCC_TIME_IN_MODE 2 is mandatory 47 1 Introduction TeMIP V3.1.0 is the final version of the new TeMIP release (TeMIP V3.1). The current release notes describe fixed problems (since TeMIP T310)as well as known problems or restrictions of the current V3.1.0 release. The document is composed of the following sections : · An overview of the TeMIP V3.1 new and changed features : section 2 · System Considerations , Required Product releases : section 3 · Installation aspects : section 4 · TeMIP "Module" or " Component" Release Notes : section 5 to 30 provide information about new features and changes (since TFRV300 level 18 rel 1), compatibility aspects, known and fixed problems , for each TeMIP component : TeMIP Namespace (TNS), Framework, Toolkits , FMs, AMs , PMs · Documentation : section provides information about the TeMIP V.3.1.0 documentation set. Please read this document before installing or using the TeMIP Software. Please read also the associated TeMIP V3.1 release notes ' New and changed Features, compatibility and migration aspects '. Installation 11 2 System considerations This chapter contains the system-specific information required to run the TeMIP software on Digital UNIX. 2.1 Installation prerequisites Please refer to the TeMIP V3.1 Installation Guide for complete information. 2.1.1 Digital UNIX Mandatory and Recommended levels Please note that TeMIP V310 has been tested with the following Digital UNIX and related Product levels. If those levels are no more available, install the latest up-to-date version of Digital UNIX levels, that supersedes previous version. TeMIP V3.1 requires D-UNIX V3.2G. TeMIP V3.1 when using DECnet requires DECnet V3.2 MUP B . TeMIP V3.1 when used with DECsafe requires TruCluster Available Server V1.3 or V1.3a or TruCluster Production Server V1.0 . See also section 3.1.1.1 herafter. 2.1.1.1 Digital UNIX patch for DECsafe A Digital UNIX patch is mandatory when running TeMIP in a TruCluster / ASE environment. This patch will be officially released by DIGITAL UNIX engineering in January 97. Please contact TeMIP Support for additional information. 3 Installation 3.1 Fixed problems 3.2 Known problems and restrictions TeMIP Name Service 12 4 TeMIP Name Service 4.1 Fixed problems 4.1.1 TEMIP_MNT_EXTERNAL#00561 There is no man page available for the utility tns_clerk_setup, but it is referenced from other TNS man pages. tns_clerk_setup is an internal utility. There is no man page for it. References to it have been removed from the other TNS man pages. 4.1.2 TEMIP_MNT_EXTERNAL#00676 The tns_adv returns the following error if you try to start the tns_clerk on an Alpha Station 255 with UTP Ethernet without any physical connection in the UTP socket. Fatal error at line 149 in file adver_dli_ultrix.c The tns_adv now continues even if initialization of DLI sockets was unsuccessfull. 4.1.3 TEMIP_MNT_EXTERNAL#00535 If in the /etc/hosts file, the alias names are described before the full internet names, the tns_server crashes (core dump). Now fixed. 4.2 Known Problems and Restrictions 4.2.1 TEMIP_MNT_EXTERNAL#00627 Problems when trying to modify the initial access rights set by TNS (tns_server_setup). Create a directory where nobody is allowed to read or write. Then create a new group (blabla) without any memberships and gave this group the full rights for the new directory. Then: add dir access .blabla as group for r,w,t,c,d Although the group had no members it was possible to register entities in that directory via the FCL or Iconic Map interface. After deleting the access rights for the group, it was no longer possible to perform registration - some TNS error messages were invoked. 4.2.2 TEMIPV31_INTERNAL#00892 The TNS Administration Guide is still very much DECnet/DNS based TeMIP Name Service 13 in places. It needs to shift focus, and be better "integrated" with TeMIP : · more TeMIP-based examples · relate generic descriptions of TNS concepts/features/etc. back to TeMIP (how TeMIP uses feature X, how TeMIP is impacted by feature Y, etc.) The whole document needs to be reviewed with this goal of TeMIP integration in mind. 4.2.3 TEMIPV31_INTERNAL#00458 Problem to modify a directory's replica set (master/replica). It is possible to switch the master and the replica, but it is necessary to wait some time (maybe 24 hours) after the "set dir .xx to new epoch master yyy, read-only zzz" tnscp operation before the switch takes effect. 4.2.4 TEMIPV31_INTERNAL#00953 During tests to create 100,000 domains, the TNS server has been seen to crash after creation of between 50,000 and 60,000 domains, during server checkpointing. TNS capacity improvements and availability around checkpointing are planned for the next version. 4.2.5 TEMIPV31_INTERNAL#01082 It is not possible to show a clearinghouse entry using the high confidence level for the request. The workaround is to use medium confidence. 4.2.6 TEMIPV31_INTERNAL#01102 The tns clerk timeout does not always seem to be taken in account. In fact, the clerk timeout is used to set the maximum time to wait for a server response. When the server is available, the timeout has effect. However, if the server is unavailable, the connection fails, and the tns clerk timeout has no effect. 4.2.7 TEMIPV31_INTERNAL#01124 The command 'tnscp sho clerk remote clear angola_ch all attr' gives some strange results for the Towers and UID attributes. This is a tnscp display problem affecting these attributes only 4.2.8 TEMIPV31_INTERNAL#01129 If there are several tuples in the file /usr/var/tns/clerk/tns-defaults with the same namespace_name, this causes the failure of the TNS configuration if you try to change the clearinghouse used (with tns_server_setup for instance). When this happens, the TNS clerk can no longer connect to a TNS server. The workaround is to edit the file /usr/var/tns/clerk/tns-defaults to remove the unwanted duplicate namespace_name entries, then retry the configuration step (temip_setup or tns_server_setup). 4.2.9 TEMIPV31_INTERNAL#01134 Sometimes the tnscp command `show clerk known namespace *' doesn't complete successfully. Some namespaces are listed then the command blocks. The workaround is to stop the command using CTRL C and retry. 4.2.10 TEMIPV31_INTERNAL#01137 TeMIP Node 5 entity registration doesn't work with TNS in dual-stack mode. The partial registration of the node is caused by a lack of access rights of the 'temip' user on the DNA_NodeSynonym directory. The workaround consists of adding manually the access rights with tnscp : · add dir .DNA_NodeSynonym access .temip_users as group for r,w,c,d,t or · add dir .DNA_NodeSynonym access .norveg.temip for r,w,c,d,t 4.2.11 TEMIPV31_INTERNAL#01221 Sometimes the TNS server operating in dual-stack mode has been observed to crash immediately following an upgrade (using tns_server_setup) from a DNS server, or following re-configuration of a TNS server in single-stack mode to dual-stack mode. This problem has only been observed on certain multi-processor configurations. If the TNS server crashes immediately after using tns_server_setup to perform one of the above re-configurations, use tns_start to restart it. The TNS server performs correctly following the restart. 4.2.12 TEMIP31_INTERNAL#01255 tnscp commands involving use of the character æ cause tnscp to crash. TeMIP Name Service 15 For example, the following command will cause tnscp to crash. tnscp> create object æ DNS$Class printer DNS$ClassVersion 1.0 Either avoid use of this and other characters from the same character set, or enclose the characters within quotes. For example: tnscp> create object "æ" DNS$Class printer DNS$ClassVersion 1.0 4.2.13 Using TNS Tracing Should you experience problems with the TNS software, you may be asked by TeMIP Support to provide trace information to help locate the problem. TNS traces can be easily set and displayed using the tool `tns_trace.sh' provided with the kit. The tns_trace.sh menu allows to start and stop traces for each component of TNS (advertiser, clerk, server). A new window is created for displaying the traces. What needs to be traced is defined with flags. The only default flag is '*' which means that every operation will be traced. Normally you should not use this default flag as it has a severe impact on TNS performance. Furthermore, the output trace file size increases very quickly if many traces are enabled. Examples of the most useful trace flags to set are given below. For the server: error error_security bugchecks warning For the clerk: error ip_connect connection warning 'vi' is used to set these flags (one flag per line) The menu of tns_trace.sh is given below: SU_BALEAR_NS:.balear> tns_trace.sh Display redirected to BALEAR:0.0 [0] Exit [1] Start TNS Server traces [2] Stop TNS Server traces [3] Start TNS Clerk traces [4] Stop TNS Clerk traces [5] Start TNS Advertiser traces [6] Stop TNS Advertiser traces TeMIP Name Service 16 [7] Shell commands * Function to execute: 1 Starting the TNS server traces... The default flag is *, do you want to edit the tns_server.events to add specific flags (Y/N) ? [N] Y 4.2.14 Configuring TeMIP in WAN configuration temip_setup does not complete successfully when used in the following TNS WAN configurations: 1) No TNS server system on your LAN or installing TeMIP on your system for the first time. 2) TeMIP has been already configured on your machine and a TNS server system ( Read-Only ) exists on your LAN For case 1) set the confidence level at LOW. To do this, edit the temip_setup script and change the line MCC_DNS_CONF=MEDIUM to MCC_DNS_CONF=LOW For case 2) set the confidence level at HIGH and increase the delay between the temip_start and the manage in the call_start routine. To do this, edit the temip_setup script : - modify the confidence : line 207 MCC_DNS_CONF=MEDIUM to MCC_DNS_CONF=HIGH - modify the timer : line 113 sleep 15 --> sleep 60 " 4.2.15 TNS messages in daemon log file The tns_adv and cml log information messages in the daemon.log file. These messages can be ignored. They do not indicate an error in the operation of these components. Example: Dec 5 23:03:06 ctliams04 cml[556]: flush_cmlsocket: oob sanity counter expired Dec 5 23:03:07 ctliams04 tns_adv[558]: >DSM_openCMLSocket (classnum : 31) Dec 5 23:03:07 ctliams04 tns_adv[558]: socket (AF_UNIX 1 , SOCK_DGRAM 2 ,PF_UNSPEC 0) Dec 5 23:03:07 ctliams04 tns_adv[558]: sockaddr_cml : scml_family 1, scml_module 31, scml_tag 1 TeMIP Name Service 17 Dec 5 23:03:07 ctliams04 tns_adv[558]: bind ( s 5, .. ) Dec 5 23:03:07 ctliams04 tns_adv[558]: 100) objects at one time in a single directory, either manually using tnscp or via a script, it is recommended that you first set the DNS$Convergence to low using tnscp, in order to prevent the propogation on each object creation and thus improve performance of the TNS server during this period. When all the objects have been created, set DNS$Convergence back to medium or high and initiate a skulk in order to propogate all the updates at one time. For example: tnscp> set dir .mydir to skulk 5 TeMIP Framework Kernel 5.1 Fixed problems 5.1.1 TEMIP_MNT_EXT#16 A new option has been added to temip_config which allows to change the Director Host without having to remove the director. 5.1.2 TEMIP_MNT_EXT#59 temip_show -a will display only semaphores belonging to the TeMIP application 5.1.3 TEMIP_MNT_EXT#139 Error message changed when the maximum number of aplication or process is reached. TeMIP Framework Kernel 18 5.1.4 TEMIP_MNT_EXT#181 Defaults values changed for maximum number of applications (now 64) and maximum number of processes (now 256) 5.1.5 TEMIP_MNT_EXT#262 Repository files are now created with the right group id. 5.1.6 TEMIP_MNT_EXT#353 License problem fixed for components testobj_am and event_filter_fm. 5.1.7 TEMIP_MNT_EXT#368 The mcc_msl compiler has been modified to allow negative values for Enumerations. Enumerated values can be any valid Integer value on 32 bits. 5.1.8 TEMIP_MNT_EXT#354 : The "with" QUALIFIER doesn't work when used on attribute whose datatype is integer and on entities for wich the attribute is "Not Available". 5.1.9 TEMIP_MNT_EXT#478 : AM Server license problem. 5.2 Known problems and restrictions 6 TeMIP Framework AM 6.1 Fixed problems 6.1.1 TEMIP_MNT_EXT#449 Setting the Number Max of remote directors to 1 and creating one remote director leads to a "software error : invalid handle parameter" when issuing a "show mcc 0 rem dir *" 6.2 Known problems and restrictions 6.2.1 TEMIP_MNT_EXT#580 Soft links are not correctly restored by temip_backup/restore utilities. when a TeMIP file is a soft link, this soft link is TeMIP Framework Kernel 19 over-written by temip-restore utility. This problem is being investigated. 6.2.2 TEMIP_MNT_EXT#689 The temip_setup asks to select the user account of the director. If the operator selects root, the temip_setup delete the current root user profile: /var/mcc/acloc/user_profiles/user_root.profile and therefore it is not possible to create applications. This problem will be fixed in a future TeMIP release. 7 TeMIP Security 7.1 Fixed problems 7.1.1 TEMIP_MNT_EXT#236 The option "-i" of security when starting Iconic Map now gives a correct information about the Logging of command. 7.1.2 MCC_OSF_EXTERNAL#228 A file "temip_central_loc_notif_examples.csh" located in /usr/mcc/acloc/example has been added to the delivered kit. This file contains an example of a possible customization of the file temip_central_loc_notif.csh. 7.1.3 MCC_OSF_EXTERNAL#310 The files temip_desired_view.ksh and temip_session_config.ksh have been modified to produce a sh or a csh environment file. 7.1.4 MCC_OSF_EXTERNAL#386 A test to check that the TeMIP user is member of the same group as acloc group has been added in the init security procedure (called by each PM during its initialization). 7.2 Known problems and restrictions 7.2.1 TEMIP_MNT_EXT#39 Using the TeMIP AC compiler on a 8400 (2 CPUs) may in some circumstances give the following error (from the motif application or from the command line...) : "MXR ERR: Translated program stack allocation failed: Not enough Space". This problem is being investigated. TeMIP Framework AM 20 7.2.2 TEMIP_MNT_EXT#622 TeMIP Security requires for time being that the users of TeMIP PM have the same primary group as the user acloc. If it is not the case, the CVR MCC-E-APPREJINVGRP is returned. This problem will be fixed in a future TeMIP release. 7.2.3 TEMIP_MNT_EXT#651 Partial wildcards are not supported by security. This problem will be fixed in a future TeMIP release. 7.2.4 TEMIPV31_INTERNAL#1208 If no path is specified for MCC FILTER attribute when using temip_central_config in non interactive mode, the default path is not set leading to the interdiction to run a manage session under FCL_PM. TeMIP Security 21 8 TeMIP Framework Toolkit 8.1 Fixed problems 8.1.1 TEMIP_MNT_EXT#119 A test with emission of a correct error message has been added in temip_backup to check if a list contains too many files. 8.1.2 TEMIP_MNT_EXT#334 when mcc_msl detects some errors, it now exits with a status reflecting the problem. 8.2 Known problems and restrictions TeMIP Security 22 9 Visual TeMIP 9.1 Fixed problems All problems fixed in Visual TeMIP V100-Level 2 are included in Visual TeMIP V1.1 and are not listed in these release notes.. 9.1.1 Wrapper Classes 9.1.1.1 MThread GetXxx routines (#I160) All the GetXxx routines of the MThread class that return the thread attributes were not returning any information, as the underlying TeMIP Framework routine was not providing this information. This problem has been fixed. 9.1.2 Framework Classes 9.1.2.1 Crash in application code (#I157) If the application code generates a segmentation violation, this crash was in some cases caught by TeMIP Framework and transformed in the message : Exception in Mgt Module (id=90), CMA code = 177db005 In this case, the thread was returning abruptly without calling the destructor of the MDirectiveContext. This occured when the segmentation violation was trapped by CMA and transformed in a CMA exception. It might result in instances been left locked. The segmentation violations are no longer trapped at thread level and a segmentation violation will lead to an abort of the process. This behaviour guarantees the integrity of the data within the management module. 9.1.2.2 OnCancel not called on alerts (I#358) If an alert is received during the processing of a directive, in most of the case, the OnCancel methos is not called. The processing of the current directive is terminated and the MDirectiveContext deleted. This problem has been fixed. 9.1.2.3 Memory leaks on exception (TEMIP_MNT_EXT#491) When an exception, like an MCVRException occurs during the TeMIP Framework Toolkit 23 processing of a set directive, there was overtime an increase in the size of the process. This problem was due to the compiler DECcxx V5.1 and is fixed with the compiler DECcxx V5.4 required by Visual TeMIP V1.1. 9.1.2.4 Random problems under stress (TEMIP_MNT_EXT#506) Under heavy stress for a long duration (over 8 hours), some management modules were experimenting random segmentation violation. This problem occured only on SMP machines. This has been fixed. 9.2 Restrictions 9.2.1 Wrapper Classes 9.2.1.1 UseValue (I#249) The UseValue method of the MDescriptor class does not work on all derived classes of MDescriptor. This method is only needed for interfacing C code with Visual TeMIP and should not be needed by Management Module developers. This method should no longer be used and will be removed from the documentation in a future version. 10 Alarm Handling FM 10.1 Fixed problems 10.1.1 TEMIP_MNT_EXTERNAL#89 and #107 The Operation Context collection filtering thread will not stop unless a fatal error is encountered. All unexpected non-fatal error are logged in the Child trace file, and the collection will continue. 10.1.2 TEMIP_OSF_EXTERNAL#160 Event Type argument of disable directive (available for the Testobj class, subclass of Osi System class) and Alarm Event Type attribute of Alarm Object are now consistent. 10.1.3 TEMIPV31_INTERNAL#705 Attribute Value Change event is not emitted during the first SET Visual TeMIP 24 directive on Alarm Object Operator Note attribute. A side-effect is that the Real Time window of Alarm Handling PM is not updated. However, events are emitted for the following SET directives on the same entity. 10.1.4 TEMIP_OSF_EXTERNAL#31 The attribute Specific Problem of Alarm Object is now displayable as an alarm summarized info in the Real Time Window of Alarm Handling PM. 10.1.5 TEMIP_OSF_EXTERNAL#118 The attribute Operator Note of Alarm Object is now displayable as an alarm summarized info in the Real Time Window of Alarm Handling PM. 10.1.6 TEMIP_OSF_EXTERNAL#170 In order to be able to compute down-time equipment the new attribute Clearance Timestamp has been added on Alarm Object Problem Clearance. This attribute will be visible using the show directive on Alarm Object subclass but will not be returned by the summarize directive. In addition this attribute will be archived. 10.1.7 TEMIP_MNT_EXTERNAL#8 The argument Alarm Object Age used for purge_alarms and archive directives uses the Alarm Object termination date rather than the Alarm Object creation timestamp. 10.1.8 TEMIP_MNT_EXTERNAL#75 Clear alarms which passes the Discriminator Construct and which correlate outstanding alarms will be now created in state Terminated/Closed. 10.1.9 TEMIP_MNT_EXTERNAL#85 There is now a way to manually recover from any discrepencies between Alarm Objects and Trouble Ticket states, using the directives HANDLE, RELEASE and CLOSE (authorized for root and director users). 10.2 Known problems and restrictions 10.2.1 TEMIP_MNT_EXTERNAL#393 When the Managed Object attribute of an Alarm Object represents an entity specification with a not instanciated class at a given Visual TeMIP 25 level, sometimes the child process of the Alarm Handling crashes. Note however that the Alarm Object is not lost and is stored in the datastore of the concerned Operation Context. In addition the child process is restarted automatically. Managed Object example : Managed Object = MODEM LOCAL_NS:.m1 LINE where LINE is a subclass of the global class MODEM 10.2.2 TEMIP_MNT_EXTERNAL#649 Under certain circumstances TeMIP Alarm Handling creates datastore files with a bad group id, that is to say daemon instead of users. Note that this may be corrected choosing one of the follwoings : - start the TeMIP director under temip user rather than root user - issue a chown temip:users on datastore files Alarm Handling FM 26 11 Event Log FM 11.1 Fixed problems 11.2 Known problems and restrictions 12 Trouble Ticketing FM 12.1 Fixed problems 12.1.1 TEMIP_OSF_EXTERNAL#241 The algorithm which encodes in the SQL database the attributes values now supports a string that matches with the following regular expression : "*>*/*". 12.1.2 TEMIPV31_INTERNAL#239 Some of scripts dealing with ORACLE in /usr/kits/TNM310/examples directory will not work if Network Information Service (NIS) is used on the concerned host. 12.1.3 TEMIP_V31_INTERNAL#744 When escalating a Trouble Report, an AttributeValeChange Event is generated instead of a StateChange Event. 12.1.4 TEMIP_V31_INTERNAL#733 When using a wildcarded 'Associated Alarms Id List' search criteria, the SUMMARIZE result could give several times the same matching entity. 12.2 Known problems and restrictions 12.2.1 TEMIPV31_INTERNAL#750 If a TT Context is created while the /var/kits/temip/notify_procedures directory is badly protected, it will not be possible to delete it. The only workaround is to issue a 'stop MCC 0 APPLICATION trouble_ticketing_fm', delete /var/kits/temip/*TTFM*, and then restart the trouble ticketing application. 12.2.2 TEMIP_V31_INTERNAL#361 Alarm Handling FM 27 When deleting a RT_REPORT instance, the ObjectDeletion events are generated with the RT_REPORT instance set to '0'. 13 Event Filtering and Correlation FM 13.1 Fixed problems 13.1.1 TEMIPV31_INTERNAL#411 When a wildcarded RESUME/SUSPEND directive is issued on any of the low level filter classes, the State Change event generated for each applicable filter references the wildcarded entity (MCC .temip.host_director TAP_FILTER *), rather than the entity for which the directive currently applies (MCC .temip.host_director TAP_FILTER foo, MCC .temip.host_director TAP_FILTER bar). 13.2 Known problems and restrictions 14 Registration FM 14.1 Fixed problems 14.1.1 TEMIPV31_INTERNAL#191 When a deregister directive is issued on an entity which is also member of a domain, it is not automatically deleted as domain member. The 'delete DOMAIN foo MEMBER bar' directive has to be issued later on, by the user. 14.2 Known problems and restrictions 15 Domain FM 15.1 Fixed problems 15.1.1 TEMIPV31_INTERNAL#354 When issuing the directive 'SHOW domain foo MEMBER *', if one of the member is a deregistered domain member, the corresponding specialized exception is returned, but the out entity of the call is not correctly set to the guilty member, but to the last correct member. This is now fixed. Event Log FM 28 15.2 Known problems and restrictions 15.2.1 V31_INTERNAL#1103 When performing a mcc_call UPDATE on DOMAIN MAP the outP is NULL (call response = MCC_S_RESPONSE). In this case the outP buffer must normally contain the call response. This may cause problems when developping MM accessing domain_fm. 16 Notification FM 16.1 Fixed problems 16.1.1 TEMIPV31_INTERNAL#590 In some distributed configurations, the Notification FM sometimes crashes. Generally a message is printed either in /var/mcc/trace/notification_fm.log or in stdout (that is to say the terminal where you issued temip_start command), with the pattern 'Assertion Failed at line xxx of file yyy'. Note however, that the process will restart using both Framework AM and Notification FM recovery features. This problem is now fixed. 16.2 Known problems and restrictions 17 Alarms FM 17.1 Fixed problems 17.2 Known problems and restrictions 17.2.1 Number of enabled rules per TeMIP director We strongly recommend to minimize the number of enabled rules on a given TeMIP director. This can be achieved using the following guidelines : · Prefer rules which use wildcarded expressions rather than instanciated expressions. However in this case, remember that the matching/filtering is done regarding the members of the domain, parent instance of the concerned rule · Distribute your rules on several TeMIP directors in order to share 0the load on several alarms_fm processes Trouble Ticketing FM 29 17.2.2 mcc_alarms_extract_rules The executable /usr/mcc/mmtoolkit/bin/mcc_alarms_extract_rules does not extract DOMAIN and RULE names any more. Note however that you can extract rules using FCL scripts. 18 Collection AM 18.1 Fixed problems 18.2 Known problems and restrictions 19 Alarm Generator AM 19.1 Fixed problems 19.2 Known problems and restrictions Event Filtering and Correlation FM 30 20 Script AM 20.1 Fixed problems 20.2 Known problems and restrictions 20.2.1 TEMIPV31_INTERNAL#671 The script_am does not support commands which are executing a very long time or which produce very large outputs. Sometimes in these cases it stays blocked. You will have then to restart the application and to clean temporary files in /tmp. Registration FM 31 21 Circuit AM 21.1 Fixed problems 21.2 Known problems and restrictions Domain FM 32 22 DECnet IV AM 22.1 Problems Fixed 22.2 Known Problems and Restrictions 22.2.1 TEMIPV31_INTERNAL#00990 Attributes are not shown. For example, the TeMIP operation `show node4 dsvb20 circuit SVA-0 adjacent node SAT63 all attr' returns the following error: %MCC-E-NOPARAMLIST, no parameter list was supplied in this ILV buffer 23 DECnet/OSI AM 23.1 Problems Fixed 23.2 Known Problems and Restrictions 23.2.1 TEMIPV31_INTERNAL#00999 `getevent node 0 any event' fails. The problem concerns all directives which don't send a CMIP request: the 0 is not interpreted internally by the DNA5-AM as "LOCAL_NODE". 24 TCPIP AM and Related Applications 24.1 Problems Fixed 24.1.1 TEMIP_MNT_EXTERNAL#00313 "TCPIP TIMEOUT PROBLEM" Two problems were reported: 1)"wildcard show aborts if agent response timeout." This has been fixed, such that even if the SNMP agent is very slow and causes several timeout, the algorithm for GetNextRequest will correctly retry according to the UDP timout settings. 2)"UDP timeout setting is volatile" The setting of the UDP Notification FM 33 timeout parameters was not volatile, but got reset to default values each time the TCP/IP AM was started. This has been enhanced by adding new environment variables that will be used to set default values at TCP/IP AM startup. The new config/environment variables are: MCC_TCPIP_AM_UDP_TIMEOUT MCC_TCPIP_AM_UDP_RETRIES MCC_TCPIP_AM_ICMP_TIMEOUT MCC_TCPIP_AM_ICMP_RETRIES Please see the TCP/IP AM Use manual for information about the use of the corresponding parameters. 24.1.2 TEMIP_MNT_EXTERNAL#00395 "ENUMERATED DATA TYPE NOT MAPPED IN ADD.TEXT" The enumeration data type was not supported when using the private MIB clauses for mapping data into the OSI Alarm field AdditionalText. This restriction has been removed, support has been added for enumerated integers for use as trap variables mapped into the AdditionalText field. 24.1.3 TEMIP_MNT_EXTERNAL#00301 "ERROR IN IP AUTOCONFIG SCRIPT (MAP SNAPSHOT)" The autoconfiguration application incorrectly recommended the use of "Map Snapshot" as one of the options during run. This has been removed. 24.2 Known Problems and Restrictions 24.2.1 TEMIP_MNT_EXTERNAL#00269 IP POLLER object is volatile On a TeMIP re-start, the IP Poller FM does not retain information set on the mcc 0 ip_poller_fm entity, and loses the created IP-POLLER sub-classes entities. 24.2.2 TEMIP_MNT_EXTERNAL#00445 Show directive for wrong ATTable always successfull The SNMP show directive of a wrong attable always returns successfully. That means that a wrong ATTable can be registered. 24.2.3 TEMIP_MNT_EXTERNAL#00426 Counted string and not-counted string encoding within OID When an OCTET STRING, DisplayString, or OBJECT IDENTIFIER is part of an instanc object identifier, the TeMIP ASN.1 routines Alarms FM 34 always encodes the value with *IMPLIED* length (without a leading character count). In other words, the TCP/IP AM complies to one of the encoding variants describe in RFC 1212, Section 4.1.6. "Mapping of the INDEX clause", but with some restrictions: There may never be more than one variable-length string within th INDEX clause, and it must be the last variable. 24.2.4 TEMIP_MNT_EXTERNAL#00699 UNITS clause is not correctly processed The UNITS clause is not correctly processed by the MIB compiler (this causes a Segmentation fault). The workaround is to comment out all lines with this clause, for example put "-- UNITS "seconds" ". This problem is not so serious, since the UNITS clause doesn't do anything anyway. 24.2.5 TEMIPV31_INTERNAL#00923 TCPIP AM raise %MCC-E-ILVTOOBIG for some traps When receiving OSI Alarms from the TCP/IP AM, in some cases, you may get the error ILVTOOBIG, raised by the Iconic Map, or the FCL interface. This comes from a user error in the customer MIB file: If a MIB variable is defined both as a MIB leaf object, and a non-leaf child object, with the same object identifier, any variable defined in the subtree below the child object, will be matched against the leaf object, since the received OID may be a valid identifier for the leaf object. Since this is invalid according to the SNMP standards, the SNMP MIB compiler should discover this problem and issue an error message, to avoid the problem to occur later in run-time. 24.2.6 TEMIPV31_INTERNAL#00989 Managed Object Displayed by Getevent may be wrong on multiple register Both the TCP/IP AM and the Event Sink keep a cache of registered identifiers, i.e. instances of the global class SNMP. These identifiers are fullnames, which get mapped into the Managed Object field. Each cache holds a certain number of entries, which get replaced in a circular manner when the cache is full. A REGISTER/DEREGISTER command will immediately update the cache in the AM, but will not directly update the Sink's cache. (The Sink's cache will however, after some time become up-to-date, Collection AM 35 because of the cache replacement scheme.) 25 Iconic Map PM 25.1 Fixed problems 25.1.1 MCC_OSF_EXT#364 Saving the full pathname of icon files in a map file is confusing since icons are always search for in directory /usr/mcc/%L/icons. The default location is /usr/mcc/icons if the environment variable LANG is not set. The problem has been fixed, only the name of the icon file is now saved in the map file. Please note that the environment variable MCC_ICONS is no more supported. 25.1.2 TEMIP_MNT_EXT#002 On a PM Client configuration, it is impossible to create a new domain which managing director is a remote server. The Iconic Map raises the following message: "Cannot start application domain_fm". A workaround is to perform the domain creation through the FCL PM. This problem has been fixed. 25.2 Known problems and restrictions 25.2.1 TeMIP Presentation Modules in a CDE environment If TeMIP V3.1 is installed on a machine configured with CDE, terminals created from the CDE session manager (dtterm) have the environment variabe LANG set to "C". This causes problems in TeMIP PMs for finding icons. workaround : unsetenv LANG before starting the Iconic Map 25.2.2 24-planes graphical board support In TeMIP V3.1, Presentation Modules do not support X Servers configured with a 24-planes depth. Only the 8-planes depth is supported. To switch from a 24-planes to 8-planes, you have to perform the following setup : If you are using CDE, edit file /usr/dt/config/Xservers and, at the end of the line similar to : :0 Local local@console /usr/bin/X11/X :0 add : -vclass PseudoColor If you are using DECwindows (i.e. XDM), edit file Alarm Generator AM 36 /usr/lib/X11/xdm/Xservers and at the end of the line similar to : :0 local /usr/bin/X11/X -nice -2 add : -vclass PseudoColor The machine must be rebooted to make the change effective. 25.2.3 Syntax for SET OF AttribId The Iconic Map sometimes raises a syntax error on directives having an "Attrib Id LIST" argument which datatype is: SET OF AttribId. The problem is due to the format of the AttribId datatype vs the SET OF. To enter a Set of argument, {} or () are used as argument delimiter, Set Of items being separated by commas. The Syntax of the AttribId "((Entity Class), Attribute)" is a bit more confusing. To enter a SET OF AttribId argument, we recommend to mix brackets and parenthesis. ex: attrib id list = { ((CLASS1, SUBCLASS1), ATTRIBUTENAME), ((CLASS2, SUBCLASS2), ATTRIBUTENAME) } Note that this restriction induces the fact that the 'Add Another' feature cannot be used to enter additional members in a SET OF AttribId. The "FCL like" syntax described above must be used. 25.2.4 Running the Iconic Map in a backgroud process under csh The Iconic Map might be blocked if it is run in background and an application is launched from the toolbar or the "Application" menu (ex: start the Dictionary browser). The problem appears under csh if the following line is present in the user's .cshrc file : stty erase ^? A temporary workaround consists in removing this line from the file. 26 FCL PM 26.1 Fixed problems 26.1.1 TEMIP_EXT 102-105 MNT_EXT 007 FCL PM is now able to display the Alarm Object User Defined attributes (Specific Problem , Additional info) 26.2 Known problems and restrictions 27 NMS PM Script AM 37 27.1 Fixed problems 27.2 Known problems and restrictions 27.2.1 MCC_TIME_IN_MODE 2 is mandatory The New Trouble Ticketing PM requires the parameter (defined in temip_setup or in temip_config file or as an environmnent variable ) MCC_TIME_IN_MODE set to 2 to accept input times. Other modes are not supported in this version. Circuit AM 38 DECnet IV AM 39 DECnet/OSI AM 40 TCPIP AM and Related Applications 41 TCPIP AM and Related Applications 42 TCPIP AM and Related Applications 43 44 45 46 47 NMS PM 48