ࡱ> rtopqG Objbjَ LL]        dz  GT.     I S TTTTTTT$uUiW2T EI2TC  ; HCCC8   T   TCC)% J T  Ao  jNS TeMIP Version 3.2 for Digital UNIX V4.0D TFR V3.2.0 Level 1 SSB Release Notes Revision: TFRV320 Level 1 rev D Date: 31 July 1998 Operating System and Version: Digital UNIX V4.0D Software Version: TeMIP Framework V3.2 for Digital UNIX V4.0 TeMIP Fault and Trouble Management V3.2 for Digital UNIX V4.0 Visual TeMIP V2.0 (including Local TAL) for Digital UNIX V4.0  TOC \o "1-3" 1. Preface  PAGEREF _Toc426522750 \h 4 2. Introduction  PAGEREF _Toc426522751 \h 4 3. Upgrading from TeMIP V3.2 level 4C FTU to TeMIP V3.2 level 1D SSB  PAGEREF _Toc426522752 \h 6 3.1 Dictionary  PAGEREF _Toc426522753 \h 6 3.2 Visual TeMIP Modules  PAGEREF _Toc426522754 \h 6 4. Preparing to Upgrade from TeMIP V3.1 to TeMIP V3.2  PAGEREF _Toc426522755 \h 6 4.1 Upgrading the TeMIP Software  PAGEREF _Toc426522756 \h 6 4.2 Migrating TeMIP V3.1 to TeMIP V3.2  PAGEREF _Toc426522757 \h 6 4.2.1 Licensing  PAGEREF _Toc426522758 \h 6 4.2.2 Migration strategy  PAGEREF _Toc426522759 \h 6 4.2.3 TeMIP Mode of Operation  PAGEREF _Toc426522760 \h 7 4.2.4 Identification of the TeMIP Version  PAGEREF _Toc426522761 \h 7 4.2.5 MIB Translator Utility (MTU)  PAGEREF _Toc426522762 \h 8 4.2.6 TNS Version 3.2 interoperation with TNS Version 3.1  PAGEREF _Toc426522763 \h 8 4.2.7 Upgrading TeMIP Layered Software  PAGEREF _Toc426522764 \h 9 5. Migrating TeMIP data and applications  PAGEREF _Toc426522765 \h 10 5.1 TFRV310L01P03 Migration Patch  PAGEREF _Toc426522766 \h 10 5.2 Migrating domains  PAGEREF _Toc426522767 \h 10 5.3 Migrating Datastores  PAGEREF _Toc426522768 \h 11 5.4 Migration detailed procedure  PAGEREF _Toc426522769 \h 11 5.4.1 TeMIP dictionary information  PAGEREF _Toc426522770 \h 11 5.4.2 Migration of a PM Client  PAGEREF _Toc426522771 \h 11 5.4.3 Migration of an FM/AM Server  PAGEREF _Toc426522772 \h 12 6. TeMIP V3.2 Software Prerequisites  PAGEREF _Toc426522773 \h 13 7. Installing and Setting up the TeMIP license environment  PAGEREF _Toc426522774 \h 14 7.1 FLEXlm and TeMIP  PAGEREF _Toc426522775 \h 14 7.2 TeMIP licenses server(s) configuration  PAGEREF _Toc426522776 \h 14 7.3 Obtaining of a valid license file  PAGEREF _Toc426522777 \h 14 7.4 TeMIP licenses servers installation  PAGEREF _Toc426522778 \h 15 7.5 TeMIP licenses client installation  PAGEREF _Toc426522779 \h 15 8. Installing TeMIP V3.2  PAGEREF _Toc426522780 \h 16 9. TeMIP V3.2 position regarding Patches and Extraordinary Patches  PAGEREF _Toc426522781 \h 16 9.1 V3.1 and V3.1A Patches  PAGEREF _Toc426522782 \h 16 9.2 EPATCHES post V310L01P03  PAGEREF _Toc426522783 \h 16 9.3 EPATCHES post V32IL06  PAGEREF _Toc426522784 \h 16 9.4 EPATCHES post V32TL02  PAGEREF _Toc426522785 \h 16 10. Configuring TeMIP V3.2  PAGEREF _Toc426522786 \h 16 11. Fixed Problems in TFRV320-1D  PAGEREF _Toc426522787 \h 17 12. Known problems in TFRV320-1D  PAGEREF _Toc426522788 \h 18 1. Preface 4 2. Introduction 4 3. Upgrading from TeMIP V3.2 level 4C FTU to TeMIP V3.2 level 1D SSB 6 1- Dictionary 6 2- Visual TeMIP Modules 6 4. Preparing to Upgrade from TeMIP V3.1 to TeMIP V3.2 6 1- Upgrading the TeMIP Software 6 4.2- Migrating TeMIP V3.1 to TeMIP V3.2 6 4.2.1 Licensing 6 4.2.2 Migration strategy 6 4.2.3 TeMIP Mode of Operation 7 4.2.4 Identification of the TeMIP Version 8 4.2.5 MIB Translator Utility (MTU) 8 4.2.6 TNS Version 3.2 interoperation with TNS Version 3.1 8 4.2.7 Upgrading TeMIP Layered Software 9 5. Migrating TeMIP data and applications 10 5.1- TFRV310L01P03 Migration Patch 10 5.2- Migrating domains 10 Usage examples : 11 5.3- Migrating Datastores 11 5.4- Migration detailed procedure 11 5.4.1 TeMIP dictionary information 11 5.4.2 Migration of a PM Client 12 5.4.3 Migration of an FM/AM Server 12 6. TeMIP V3.2 Software Prerequisites 14 7. Installing and Setting up the TeMIP license environment 14 7.1- FLEXlm and TeMIP 14 7.2- TeMIP licenses server(s) configuration 14 7.3- Obtaining of a valid license file 15 7.4- TeMIP licenses servers installation 15 7.5- TeMIP licenses client installation 16 8. Installing TeMIP V3.2 16 9. TeMIP V3.2 position regarding Patches and Extraordinary Patches 16 9.1- V3.1 and V3.1A Patches 16 9.2- EPATCHES post V310L01P03 17 9.3- EPATCHES post V32IL06 17 9.4- EPATCHES post V32TL02 17 10. Configuring TeMIP V3.2 17 11. Fixed Problems in TFRV320-1D 17 12. Known problems in TFRV320-1D 18  Preface The current Release Notes describe critical information related to the TeMIP V3.2 SSB, referenced as TFRV320-1D software kit. It is composed of the following sections: An introduction presenting the current software kit in the TeMIP V3.2 Program A set of sections containing information on how to install TeMIP V3.2 in your environment: Migrating from TeMIP V3.1 Patch 3 to TeMIP V3.2 Migrating TeMIP data and applications TeMIP V3.2 Installation Prerequisites Installing and Setting up TeMIP license environment Installing TeMIP V3.2 Configurating TeMIP V3.2 A list of TFRT320-4C (TeMIP V3.2 FTU) fixed problems A list of TFRV320-1D (TeMIP V3.2 SSB) known problems Please read this document before installing or using the TeMIP Software. Introduction TeMIP V3.2 is the next product release of TeMIP following TeMIP V3.1 (First Customer Shipment January 97). All post TeMIP V3.1 extension kits enhancements are integrated in this release: TeMIP V3.2H: TeMIP documentation on HTML TeMIP V3.2S: Alarm archiving on Sybase TeMIP V3.2T: TCPIP enhancements TeMIP V3.2I: Iconic Map and NMS PM (also called V3.2N) related enhancements TeMIP V3.2J: NMS PM enhancements over V3.2I Additionally TeMIP V3.2 provides a set of enhancements, focusing the following areas : D-UNIX V4.0 benefits, including Millennium Compliance Performance & Sizing Platform connectivity : Enhance SNMP connectivity , Provide connectivity with NT applications through the NT Client / Server toolkit (CORBA based) , Enhance Q3 connectivity through the new OSI PM component of the OSI Toolkit, Enhance ASCII connectivity through the GAT V2.0 Toolkit, provide Expert System Connectivity through the TeMIP ESA Toolkit Customer Wishes (mostly GUI or application (Fault Management) enhancements) Platform OSIness : OSI Toolkit enhancements . Development Toolkit enhancements , including the new NT Toolkit and its TeMIP Access Layer (TAL) Functional and usability enhancements : new NT Alarm handling GUI Functional enhancements : new productised expert system interface (ESA) TeMIP V3.2 packaging consists of the following software kits and products: D-UNIX software kits : TeMIP V3.2 for D-UNIX V4.0d (this kit) , including products : TeMIP Framework TeMIP Fault and Trouble Management Visual TeMIP including TeMIP Access Library Toolkit (TAL Local) OSI Management Toolkit V3.2 for TeMIP V3.2 , D-UNIX V4.0d, including products : TeMIP OSI Management Development Toolkit TeMIP OSI Access Module RunTime TeMIP OSI Agent Presentation Module Runtime TeMIP OSI Protocol Stack GAT Toolkit V2.0 for TeMIP V3.2 , D-UNIX V4.0d , including products Graphical ASCII Development Toolkit Graphical ASCII Toolkit Run-Time TeMIP TAL Server V1.0 for D-UNIX V4.0, including product TeMIP Access Library Toolkit (TAL Server) TeMIP ESA V1.0 for TeMIP V3.2, D-UNIX V4.0, including product TeMIP Expert System Access Sun Solaris Product kits : TeMIP V3.2 for Sun Solaris V2.6 , including TeMIP Framework TeMIP Fault and Trouble Management Visual TeMIP including TeMIP Access Library Toolkit (TAL Local) OSI Management Toolkit V3.2 for TeMIP V3.2 , Sun Solaris V2.6, including products TeMIP OSI Management Development Toolkit TeMIP OSI Access Module RunTime TeMIP OSI Agent Presentation Module Runtime TeMIP OSI Protocol Stack GAT Toolkit V2.0 for TeMIP V3.2 , Sun Solaris V2.6 Graphical ASCII Development Toolkit Graphical ASCII Toolkit Run-Time NT Software kits : TeMIP Client V1.0 for NT V4.0 , including TeMIP Fault and Trouble Management for NT: TeMIP Alarm Handling TeMIP Access Library Toolkit (TAL Client) The current software kit TFRV320-1D is the SSB kit of TeMIP V3.2 for D-UNIX V4.0d Please read also the TeMIP V3.2 Program Overview associated document and presentation featuring the new features and enhancements for the whole TeMIP V3.2 deliverables. Upgrading from TeMIP V3.2 level 4C FTU to TeMIP V3.2 level 1D SSB Dictionary We recommend that you upgrade the dictionary with the new one from FTU. This choice can be made during temip_setup, when you will be asked to overwrite the dictionary or not. Visual TeMIP Modules Given that several header files of Visual TeMIP have changed, it is recommended to recompile the Visual TeMIP modules with the FTU kit. Preparing to Upgrade from TeMIP V3.1 to TeMIP V3.2 Upgrading the TeMIP Software A TeMIP software upgrade is the installation of a newer TeMIP version, on a system already running a previous version of TeMIP. Different situations can occur, depending on whether the new version is a patch only, or a standard TeMIP version. Hereunder, we address the upgrade to the new version of TeMIP (TeMIP V3.2) where the system is currently running the earlier version (TeMIP V3.1), possibly with patches installed. This situation is an actual migration because the TeMIP software has to be completely de-installed and re-installed, and some data may have to be migrated. This requires careful migration study and planning. Migrating TeMIP V3.1 to TeMIP V3.2 This section describes the issues and procedures to upgrade from TeMIP V3.1 to TeMIP V3.2. Licensing The LMF system of licensing is no longer supported and the new FLEXlm licensing system must be used. Refer to the Cover Letter supplied with the kit for further information. Migration strategy Most TeMIP-based solutions are made of many networked Alpha systems, each configured to run TeMIP as either a Full Server, AM Server or Client. When a configuration of this type has to be migrated from TeMIP version N to N+1, it must be done one TeMIP system at a time as stopping the entire distributed configuration is unaffordable. Consequently the distributed solution will be composed of some systems running TeMIP version N, and some other systems running TeMIP version N+1. This situation may last a significant period of time (many days, weeks or months), depending on the total number of TeMIP systems and the geographical distance between them. The co-existence of interconnected TeMIP systems running different versions raises the following issues: Interoperability must be provided between TeMIP Framework kernels running different versions. In other words, a TeMIP request generated by a system running version N must be accepted and correctly processed by a system running TeMIP version N+1, and vice-versa. The setting of a TEMIP_MODE environment variable provides this interoperability. For further information about this variable and how it works, please refer to the TeMIP Mode of operation section. You must ensure that the new features of the version N+1 do not corrupt data or disturb the operations on a director running version N. For this reason, it is recommended that you follow a top-down migration strategy. It means that you have to migrate the PM clients first and then the FM and AM servers. An example of a migration from TeMIP V3.1 to TeMIP V3.2 in a distributed environment is given below. It is assumed that the distributed configuration is composed of three directors, D1 (PM Client), D2 (FM Server) and D3 (AM Server) all running TeMIP V3.1. Proceed as follows: Step 1: Install TeMIP V3.2 on D1(PM Client). Set TEMIP_MODE to "V3.1" so that D1 can communicate with D2 and D3. Step 2: Install TeMIP V3.2 on D2 (FM Server). Set TEMIP_MODE to "V3.1" so that D2 can communicate with D1 and D3. Step 3: Install TeMIP V3.2 on D3 (AM Server) Set TEMIP_MODE to "V3.1" so that D3 can communicate with D1 and D2. Now, you can set all your system to V3.2 mode. Step 4: Set TEMIP_MODE to V3.2 on D1, D2 and D3. TeMIP Mode of Operation The new TeMIP V3.2 features do not inter-operate with TeMIP V3.1 due to different behavior. However, TeMIP V3.2 does provide enough backward compatibility to allow a smooth migration from a TeMIP V3.1 distributed configuration to a TeMIP V3.2 distributed configuration. To make the transition possible, TeMIP V3.2 provides a way to disable the new features until the upgrade is complete on all sites. This is done by setting the environment variable TEMIP_MODE (using temip_setup utility) as follows: Set to "V3.1", the environment variable makes TeMIP V3.2 function as TeMIP V3.1 in terms of features and data exchange format. The TeMIP V3.1 format is used to issue the call request, providing compatibility with directors running TeMIP V3.1. In this mode, incoming calls using the V3.2 format are also supported. Set to "V3.2" (or not set), the environment variable enables TeMIP V3.2 to implement all the new features. The new call request format is used to issue the call request. In this mode, incoming calls using the V3.1 format are also supported. However, if an outgoing call is issued to a TeMIP V3.1 director, it will be rejected because TeMIP V3.1 cannot handle it. In this case, inter-operation with TeMIP V3.1 is not possible. The default value is "not set". Identification of the TeMIP Version The identification of the TeMIP version is required to check the coherence of a distributed configuration. The director attribute Director Version is used for this purpose. As for any other director attribute, the version of the director and the version of its related remote directors is read at director startup and maintained by the Remote Director Monitoring (RDM) feature. If the TEMIP_MODE of the local director is "V3.2" and the RDM detects that a remote director is "V3.1", then the RDM sets the Remote Director State to disabled or off-line with an Additional Text string stating the version mismatch and emits the corresponding RDM State Change event. MIB Translator Utility (MTU) The new MIB Translator Utility (MTU) now translates MIBs generating dictionary OIDs that are not compatible with those of version V3.1 dictionary. The MIB Translator Utility (MTU) and TCPIP_AM therefore works by default in V3.1 compatibility mode. The RFC 1213 and RFC 1215 arefactory preloaded in the dictionary. This allows the dictionary OIDs to match these of TeMIP V3.1. Working in V3.1 compatibility mode or not does not affect performances issues. A new option has been added to the MIB compiler (mcc_tcpip_mtu): "-n" . specifying this option on the compiler command line forces it to work in non V3.1 compatible mode. In that case, RFC1213 and RFC1215 mibs should not be preloaded (best is to start from an empty SNMP class). The mcc_tcpip_mtu configuration file (mcc_tcpip_mtu.config) now accepts a "PRELOADED" keyword. This keyword is used for the MSL generation in V3.1 compatibility mode. It must be specified on any line in the configuration defining an Alias or filename for RFC1213 or RFC1215 mibs. "PRELOADED" keyword is useless in non-compatible mode. A new question has been added to the mcc_tcpip_mtu.csh shell script: -- (V3.1 compatibility option): Do you use a V3.1 SNMP compatible dictionary ? [y]: This question assumes that the default answer is to maintain V3.1 compatibility. A new check box has been added to the mcc_tcpip_mtu.gui graphical interface: NO V3.1 Compatibility Checking this box forces the non-compatible mode. TNS Version 3.2 interoperation with TNS Version 3.1 It is suggested, in order to have a smooth tns migration and interoperation, to change as described below the /etc/services on ALL the hosts (tns clerk and servers) of the platform, BEFORE starting the migration : in this way, all V31 directors will use the new port, and be able to connect each other as well as to new V32 directors. In the specific case where a TNS Clerk running the 3.1 version has to communicate with an OFF-LAN TNS Server running the 3.2 version you need to modify the port number used by the TNS Clerk to connect to the TNS Server. To achieve that requirement: 1) Stop the TNS Clerk (# tns_clerk_stop) 2) modify the /etc/services file (on the system running the V3.1 ) as follow: Before the changes: # more /etc/services ### BEGIN TNS UPDATE # THIS PART WILL BE REMOVED DURING DE-INSTALL OF TNS # DO NOT INSERT MODIFICATIONS BETWEEN THESE FLAGS tns_cml 437/tcp # TNS communication processing tns 1000/tcp # TNS SERVER PORT ### END TNS UPDATE After the changes: # more /etc/services ### BEGIN TNS UPDATE # THIS PART WILL BE REMOVED DURING DE-INSTALL OF TNS # DO NOT INSERT MODIFICATIONS BETWEEN THESE FLAGS tns_cml 590/tcp # TNS communication processing tns-adv 3309/udp # TNS advertiser tns-server 3308/tcp # TNS SERVER PORT ### END TNS UPDATE If a TNS Clerk running V3.2 has to communicate with a TNS Server running V3.1 you have to follow the same operation; change the /etc/services on the system running V3.1 3) Restart the TNS Clerk (# tns_clerk_start) Upgrading TeMIP Layered Software TeMIP layered software is any kind of software that operates "on top of" TeMIP or that interfaces with TeMIP. For the purpose of migration, the layered software can be classified according to the coupling level, as follows: Management Modules (AMs, FMs, PMs) These have the closest dependency with TeMIP, because they use the TeMIP APIs directly and are enrolled, that is, plugged into the TeMIP Framework kernel. They can be Management Modules that form part of the TeMIP product set (OSI AM, GAT AM, Visual TeMIP Management Modules), Management Modules developed by a TeMIP partner or third party software provider, or in-house modules. Non-Management Modules These are applications that have an interface with TeMIP, like a Metrica application, or Expert System application. These applications can interface with TeMIP by means of data files, FCL command scripts, the PM launch mechanism, or a TeMIP API. Whatever kind of TeMIP layered software is running on your system, you must consider it during the migration study and planning. Either this software can run without changes to the new version of TeMIP, or it must be migrated itself. In this case, one of the following situations can occur: The layered Management Module is part of the product set family (OSI AM, GAT AM, TAL, ESA ...) or has been developed using a TeMIP toolkit (for example, Visual TeMIP). In this case, the corresponding toolkit will provide the detailed information about the migration. In most cases, a new version of the toolkit is released synchronously with a new release of TeMIP, and a re-linking, or re-compilation, or re-generation of the Management Module is either recommended or mandatory. This development activity must be completed and the new Management Module tested before the actual migration of the operational system can start. Therefore, a development and test system running the new TeMIP version must be available some time before the migration. A TeMIP partner or a third party has provided the layered Management Module. You must contact the Management Module provider to obtain a guarantee that it will run with the new version of TeMIP, or to obtain a new release of the Management Module. This activity must be planned accordingly. The layered Management Module is a pure in-house developed Management Module. In this case it is your responsibility to migrate it as appropriate. The Visual TeMIP Development Guide of the new TeMIP version will provide detailed information about the compatibility of the APIs between the two versions. Frequently, a re-linking or re-compilation is recommended or mandatory. This requires a development and test system. The layered application is not a Management Module, and is only loosely coupled with TeMIP. You must make sure that the interface between TeMIP and this application does not change in the new TeMIP version. If there are changes, or a suspicion of incompatibility, a specific migration and testing activity must be planned. Migrating TeMIP data and applications TFRV310L01P03 Migration Patch As explained below, in order to properly migrate, it is mandatory to install a specific migration dedicated Extraordinary Patch on top of V310L01P03 (plus possibly extension kits V3.2I/J/T/S). This patch is named TFRPATCHMIGRATIONV310L01P03. It is delivered separately from the TFRV320-1D itself, and has to be installed using standard EPATCHES installation procedure. It contains the temip_migrate_domain tool plus updated backup group files. Refer to the file README.MIGRATION delivered with this patch for installation details. Note that this migration patch will be part of the official CDROM. Migrating domains Due to the (new) storage of DOMAIN and MEMBER instances in standard MIR files, the V3.2 domain FM is not compatible with the V3.1 DOMAIN FM in term of data (MIR/TNS). A migration tool called temip_migrate_domain is provided in order to rebuild Domain FM data while upgrading a TeMIP director from V3.1 to V3.2. The aim of this tool is to generate two command files associated with the domain topology of a specified director. It does not have any effect on the data before executing the command files. One generated file contains the FCL PM directives to be used to remove all domain data stored with the V3.1 DOMAIN FM storage format. This command file should be run before de-installing the V3.1 director. The other generated file contains the FCL PM directives to be used to recreate all domain data with the V3.2 new DOMAIN FM storage format. This command file should be run after installing the V3.2 director. Usage examples : In the following exemple, .temip.venise_director is the name of one director while all the domain associated to this director are created under the nse TNS directory. If you have to migrate venise from V3.1 to V3.2, the temip_migrate_domain could be invoked with the following arguments: * temip_migrate_domain -w/usr/users/temip/migration/results -d.temip.venise_director -t nse -v -f Once completed, in the /usr/users/temip/migration/results directory, are created: 1 create_domains_venise_nse.cmd, (the command file that is used to re-create the domain on V3.2 ) 2 and delete_domains_venise_nse.cmd (the command file to be used to delete the V3.1 domain instances) For further information of how to use it, please refer to its on-line documentation by typing temip_migrate_domain on the prompt. Migrating Datastores In TeMIP V3.1, the datastores belonging to operation contexts were indexed using one specific and unique identifier. In TeMIP V3.2, multiple indexing is possible, which improves performance time when database queries are carried out. However, to enable the data contained in TeMIP V3.1 datastores to be used with TeMIP V3.2, the datastores must be migrated. Migration requires restructuring of the V3.1 tables, which are rebuilt with the original unique identifier plus two new indexes related to the Problem Status and AO Status fields. These two fields correspond with the most frequently requested search criteria. By searching in this more specific way, data can be retrieved quickly from large datastores containing many alarms without having to search the whole datastore based on the single unique identifier. Migration is an off-line procedure that should be carried out after migration of the TeMIP platform. Migration is done using the temip_ds_migrate_V31_to_V32 utility. Refer to the TeMIP Utilities manual for details of how to use this utility. Migration detailed procedure TeMIP dictionary information In a distributed solution, some systems will run TeMIP V3.1, and some other will run TeMIP V3.2. Consequently, the dictionary format will not be the same on each director. Due to this fact, it is recommended to upgrade manually your dictionary instead of using the dictionary propagation facility. It means that for each specific Management Modules, Management Information Bases (MIB), and so on, you must recompile the MSL files in order to have a consistent dictionary on each system. Migration of a PM Client TeMIP V3.2 introduces new application resources as long as new default values within the mcc_resource.dat and temip_resource.dat resource files. It is recommended to remove those files and install an up-to-date version. You can also keep your customization as follow: Save the resource files from the user home directory to another directory, Remove those from the user home directory, Start the TeMIP V3.2 iconic map PM and the NMS PM, customize the default settings respectively through the Options and Customize menus, Save the new settings and leave the applications, Compare the saved files with the new ones and update the new ones with the settings you are interested in the saved ones, Re-start the PMs and check yours updates are taken into account. Note also that if you use some customized security profiles you must recompile them. The procedure for upgrading a PM Client director from TeMIP V3.1 to TeMIP V3.2 is the following: Backup the whole TeMIP data (apply the temip_backup utility on the TeMIP group as well as on your own groups, if you have some ). Some of TeMIP V3.1 backup groups have to be modified prior to perform the temip_backup. We recommend you to install the correct groups provided within the e-patch (TFRPATCHMIGRATIONV310L01P03). Stop TeMIP (temip_stop) Stop TNS (tns_stop for a master server or replica and tns_clerk_stop for a client) De-install the TeMIP software, version 3.1, and accompanying patches (setld d) De-install all the extension kits first : V3.2T, V3.2J and V3.2I De-install the TeMIP V3.1 patch 3 De-install the TeMIP V3.1 SSB Upgrade your system, the additional software (DECnet, C++, and so on) and TeMIP Software pre-requisites, if necessary Install the TeMIP V3.2 software prerequisites (setld l) Install and configure the (new) TeMIP license environment (refer to the related FLEXlm section in the installation guide). Install the TeMIP software, version 3.2 Start TNS (tns_start or tns_clerk_start for a client) Restore the whole TeMIP data you had previously saved (apply the temip_backup utility on the TeMIP groups as well as on your own groups, if you have some). Configure TeMIP (run the temip_setup utility, keep the current director previously defined in V3.1 and allow the TeMIP V3.1 interoperability mode.) Start TeMIP V3.2 ( temip_start ) Upgrading TeMIP Layered Software if any. Start using TeMIP V3.2 Migration of an FM/AM Server The procedure for upgrading a FM/AM Server director from TeMIP V3.1 to TeMIP V3.2 is the following: 1. Prepare Domain Migration (logon into the director you want to migrate, and perform the following steps. For further information about the Domain migration, please refer to the Migrating Domains section.) Install the domain migration script (that is an additional tool that comes within the e-patch TFRPATCHMIGRATIONV310L01P03) run the temip_migrate_domain script file. This file will collect for you domain information: When migration concerns only one director, we recommend to run temip_migrate_domain with the -d and the -t option. Check that the run of the temip_migrate_domain has created for you 2 set of files : one to delete domain, and another one to re-create these domains. Check carefully that you don't miss any other domains (-d and -t option set to the appropriate value). 2. Backup the whole TeMIP data (apply the temip_backup utility on the TeMIP group as well as on your own groups, if you have some ). Some of TeMIP V3.1 backup groups have to be modified prior to perform the temip_backup, we recommend to install the groups provided within the e-patch TFRPATCHMIGRATIONV310L01P03, prior starting the temip_backup steps. 3. Stop TeMIP (temip_stop) in order to kill all the domain_fm associated processes 4. Start TeMIP (temip_start), don't start any others applications. 5. Set the TNS confidence level to HIGH as follow : >manage set mcc 0 TNS confidence level = high 6. Delete the domains you want to migrate (run the delete script created while running the temip_migrate_domain utility) 7. Stop TeMIP (temip_stop) 8. Stop TNS (tns_stop for a master server or replica and tns_clerk_stop for a client) 9. De-install the TeMIP software, version 3.1, and accompanying patches (setld d) De-install all the extension kits first : V3.2T, V3.2J and V3.2I De-install the TeMIP V3.1 patch 3 De-install the TeMIP V3.1 SSB 10. Upgrade your system, the additional software (DECnet, C++, and so on) and TeMIP Software pre-requisites, if necessary 11. Install the TeMIP V3.2 software prerequisites (setld l) 12. Install and configure the (new) TeMIP license environment (refer to the related FLEXlm section in the installation guide). 13. Install the TeMIP software, version 3.2 14. Start TNS (tns_start or tns_clerk_start for a client) 15. Restore the whole TeMIP data you had previously saved (apply the temip_backup utility on the TeMIP groups as well as on your own groups, if you have some). 16. Migrate the Alarm Handling FM and the Event log FM alarms/event datastore : run the temip_ds_migrate_V31_to_V32 utility on each Alarms/Events datastore files) 17. Configure TeMIP (run the temip_setup utility, keep the current director previously defined in V3.1 and allow the TeMIP V3.1 interoperability mode.) 18. Start TeMIP V3.2 ( temip_start ) 19. Set the TNS confidence level to HIGH as follow : >manage set mcc 0 TNS confidence level = high 20. Re-create the domain on V3.2 using the command file created in the step  REF _Ref423773128 \w \h  \* MERGEFORMAT 1 while running the temip_migrate_domain utility ) 21. Upgrading TeMIP Layered Software if any. 22. Start using TeMIP V3.2 Migration from TeMIP V3.0 to TeMIP V3.1 is addressed in the TeMIP V3.1 documentation Migration from TeMIP V3.1 to TeMIP V3.1A is addressed in the TeMIP V3.1A documentation TeMIP V3.2 Software Prerequisites TFRV320-1 must be installed on: DIGITAL UNIX V4.0D Associated Oracle release (optional Alarm Archiving and Trouble Ticketing) : 7.3.4 Associated Sybase release (optional : Alarm Archiving) : 10.1 Interoperability with latest DECnet release (optional) : 4.0 TruCluster V1.5 DECsafe function and TruCluster Available Server V1.5 on Digital UNIX V4 (optional) Cxx release V5.7 (optional : Visual TeMIP) Note that Rogue Wave Tools h++ (Rogue Software) is no more a new prerequisite software for TeMIP V3.2 FTU / Visual TeMIP as it is now integrated in the kit. In addition to the installation requirements above, you are encouraged to install Digital UNIX V4.0D patches coming with BL1. See your Digital Representative to obtain the complete set of available Digital UNIX V4.0D patches and installation instructions. Installing and Setting up the TeMIP license environment TeMIP V3.2 makes use of FLEXlm as license manager . FLEXlm and TeMIP FLEXlm is a license manager used in the software industry to control the use of software products. FLEXlm is based on a client-server architecture. Each TeMIP node can be seen as a client, which can use a daemon to ask a server for a token to access a feature. There can be one or more servers located anywhere in the network. The list of available server(s) and features (i.e. TeMIP licenses) are listed in a license file. FLEXlm daemons (client and server) are shipped with TeMIP, therefore you don't need to purchase anything from GLOBEtrotter Software Incorporation. These two executables lmgrd.temip (server) and temipdec (client) are absolutely no use to anyone without a valid license file. You can obtain additional info about FLEXlm at the following URL: http://www.globetrotter.com/flexlm.htm TeMIP licenses server(s) configuration First of all, you have to determine your TeMIP license server(s) configuration. A single TeMIP license server In this case, if the license server host has a failure, TeMIP will no longer be available until the server host gets back. Three redundant TeMIP licenses servers In this case, at least 2 of the 3 servers must be up and running so that TeMIP licenses check could work. The second solution (3 redundant servers) is obviously the recommended configuration. Note that the host(s) of the license server(s) are not necessarily the same as TeMIP hosts. Obtaining of a valid license file The next step is to obtain from Digital a valid license file. For running TFRV320-1 You just need to ask a valid license file to the TeMIP Support Team ( HYPERLINK mailto:VBETEMIPSUPP@digital.com VBETEMIPSUPP@digital.com) . You will have to give in input: The number of license servers: 1 or 3 (and optionally the host name for each server) The list of features you want to use among those described in section 2.5 of the TeMIP Planning Guide (TEMIP-TFR-CS, TEMIP-NMS-CS, TEMIP-VISUAL-DVT ) All this information has to be filled in the temip_license_form.txt which is delivered with the kit. In return, you will then receive a valid TeMIP license file. TeMIP licenses servers installation First of all, on each host of the TeMIP licenses server(s), you will have to: Install the subset TFRLICV320 (in the TFRV320 software kit) Run the utility: /usr/mcc/licenses/temip_licenses_setup - Select the 'Server' option - Enter the location of the license file (provided externally by the TeMIP support). - Then you will be prompted for servers' names and a free port number. The utility takes into account these parameters to modify the license file, which is then copied in /usr/mcc/licenses. The utility also creates files in /sbin/init.d and /sbin/rc3.d to start the license server automatically at boot time. Finally, the utility starts the TeMIP licenses server. TeMIP licenses client installation On each host supporting TeMIP (unless a TeMIP license server is already installed on this host), before installing the standard TeMIP subsets, you will have to: Install the subset TFRLICV320 (in the TFRV320 software kit) Run the utility: /usr/mcc/licenses/temip_licenses_setup - Select the Client option - Enter the location of the license file (provided externally by TeMIP support) . - Then you will be prompted for server(s) name(s) and associated port number (must be the same as in step #4). The utility takes into account these parameters to modify the license file, which is then copied in /usr/mcc/licenses. At this point, TeMIP can be installed and will run accordingly. Installing TeMIP V3.2 The TNS server must be upgraded to TeMIP V3.2 prior to upgrading the TeMIP director. TeMIP TFR V3.2 software kit installation is quite similar to TeMIP TFR V3.1 installation, except the following changes : A new TFRLICV320 subset has been added , including the software license manager materials (see section above) The TeMIP framework Developer Toolkit subset (TFRTK) no longer exists (it has been moved to TFRBASEV320 subset). TeMIP V3.2 position regarding Patches and Extraordinary Patches V3.1 and V3.1A Patches V320L01 SSB includes all the fixes coming from the maintenance patches TFRV310L01P03 and TFRV31AL05P01. EPATCHES post V310L01P03 All the extraordinary patches on top of V310L01P03 as of July 29th, are integrated in the V320L01 SSB, except the TFRFIXE568. EPATCHES post V32IL06 All the extraordinary patches on top of V32IL06 as of July 29th, are integrated in the V320L01 SSB. EPATCHES post V32TL02 All the extraordinary patches on top of V32TL02 until July 1st, are integrated in the V320L01 SSB, except the TFRFIXE595 and the TFRFIXE598. Configuring TeMIP V3.2 A new temip_setup utility is available, with new features implemented. The main modifications are: Each step (Basic configuration, Director creation, Documents configuration, ...) can be run separately Old options (-v and -s) are suppressed. Using -f option, you can configure your platform using a pre-defined configuration file. Some templates are available in /usr/mcc/mmtoolkit/examples/temip*.conf. The format is described in temip_setup man pages The current TeMIP configuration can be saved and re-used. Only the root user can run this tool. After installing TFRV320, run temip_setup and select the option Run a full TeMIP configuration, then type the command man temip_setup to get more information about the new features of the utility. Fixed Problems in TFRV320-1D We reference hereafter, only the main problems fixed in this kit and which were documented as known problems in the TFRT320-4C, known as TeMIP V3.2 FTU. Functional ModulesQAR DBID/RefComponentDescriptionSolutionV32_EXT18DOMAIN FMPopulate domain with not registered entity Returns common exception with status normal TeMIP> populate domain france selec list (mcc foobar) Domain rachel_ns:.france On director: rachel_ns:.temip.rachel_director AT Mon Jun 29 17:30:40 The requested operation cannot be completed MCC Routine Error = %MCC-S-NORMAL, normal successful completion Now, when populating a domain with a non-existing entity in select list argument, there is just the populate exception "No member populated" which is returned. This exception is raised when there is no member creation for the domain after the polulate directive. This can also be raised when populating a domain with entities already members of the domain. V32_INT985ALARMS FMSometime software logical error is returned during rule evaluation mainly when unexpected exception is returned by the underneath access moduleThe specialized exception handling has been corrected in the mcc_alarms_fm module. Access ModulesQAR DBID/RefComponentDescriptionSolutionV32_INT1004/1031TCPIP AMIfAdminState/ifOperStatus used with different Id code in the Circuit AM and the TCP/IP AM.In V3.2 the dictionary is build by using the following files: rfc1213_enum_preloaded_V31.ms Rfc1213_preloaded_V31.ms Rfc1215_preloaded_V31.ms These files are equivalent to the V3.1 mcc_tcpip_am_mgt_if.ms file. KittingQAR DBID/RefComponentDescriptionSolutionV32_EXT57KITtemip_setup does not prompt the user as to whether or not the Director should be started and does not automatically start Director.temip_setup behavior has been corrected.V32_INT1138KITSometime, temip_setup tool says than another temip_setup session is running on the system.This has been fixed. Known problems in TFRV320-1D The System Testing phase for this kit has identified the following main issues: Presentation ModulesQAR DBID/RefComponentDescriptionWorkaroundV32_EXT35FCL_PMSome exceptions are not raised when using the SHOW directive and the WITH qualifier on the command line Ex: show domain dom rule * , with state = disabledNone.39TEMIP_PMThe Event Log PM cannot be started from the Iconic Map on a Client PM system3 solutions: Start manually the EL PM giving the name of a remote OSI_SYSTEM/LOG as argument ex: temip_el_pm osi_3 log_1 In an Iconic Map view, add a remote OSI_SYSTEM instance, select it and click the Operations->Monitor Logs menu option Specify the name of a remote OSI_SYSTEM in file /var/kits/temip/osi_system_id.dat (Warning ! this workaround to be used only on client PM systems) 60FCL_PMThe length of an input command is limited to 8k (8192 characters). Additional characters are truncated. Try to split FCP_PM inputs.V32_INT554FCLIn the FCL PM, the Specific Problems attribute of Alarm Objects is no longer displayed as a User Defined datatype.None.615AH_PMAH PM crashing at startup due to discrepancies between the actual contents of the file temip_an_add_fields.dat (number of additional columns) and the value of the temip.ah_listmask resource in temip_resource.dat Restore the default value of the resource. Defined in: /usr/lib/X11/appdefaults/temip_resource.dat) Ex: temip.ah_listmask: 0xc0003fff Functional ModulesQAR DBID/RefComponentDescriptionWorkaroundV32_EXT31NOTIF FMGetevent on global class is compulsory else the notification FM will not collect event/alarm on the child classesAdd the support of the Getevent directive on your global class, even if your access module doesn't generate alarm/event.16REGISTRATION FMRegistering an SNMP child class leads to a registration_fm hang, when the child class is at least 11 levels depth.The MIB compilation has to be customized in order to force pruning, in order to not pass beyond the 11 class levels TeMIP kernel limit.V30_EXT240TTFMAO might be associated with wrong tt_report id : For instance, a tt_report " 4" is different from tt_report "4". Aclose of the tt_report will not close the associated alarm. Under temip account, close the AO.V31_EXT474NOTIF FMTarget Severity is not set in the eventNot supportedV32_INT1061NOTIF FMProblem visible at the notification level, MCC-S-INV-ENTITY might be returned while starting a notification, or while resuming an OC/LOGUnder Investigation. No workaround available. We recommend to avoid to cross-member entity with domain that doesn't belong to the same managing director.1052DOMAIN FMWhen trying to create a domain on an inexistant TNS directory, the returned exception is not self explanatory. It is : %MCC-S-SPECIALIZED_EXCEPTION, success with management module-specific exception reply.None.1065CIRCUIT AMIf by accident, you enter a null string in the objectname of the AEndPoint or the Zendpoint, the show all char on the circuit cause a circuit_am crah TeMP> set circuit toto aEndpointName = ( instance = snmp rachel inter 2, ob jectid = %X303030, objectname = "")Avoid to use an objectname null.Not540SCRIPT AMSometime script returns bad or no outputThe temporary workaround consists in adding the following line to the begining of all shells provided as example in /usr/mcc/mcc_system/mcc_scripts : echo `uname` > /dev/nul Access ModulesQAR DBID/RefComponentDescriptionWorkaroundV31_EXT529DNA5 AMIt's not possible to register node5 entities with NSAP address length greater than 40 characters.None.V32_INT1220TCPIP AMImpossible to browse a table when the index is based on a not readable attribute. TCPIP AM returns a No such entity error messageV32_EXT62TCPIP AMOSI alarms are not correctly targeted to the right SNMP child entity instance. Managed Object field is always equal to the global SNMP entity.By the means of MANAGEOBJECT-DEFAULT, alarms can be associated to a child SNMP entity class (instead of an instance).V32_EXT72TCPIP AMThe tcpip_sink terminates sometimes with the following traces: Unexpected return status 52875002 in routine mcc_time_get_current at line 54 7 in file ./tfc_wp_time.hxx Error text is : %MCC-E-INSUFBUFFER, data not returned due to lack of return data buffer space. EF_RT: Unexpected exception in scheduling thread, disabling EFNone. Kernel / Visual TeMIPQAR DBID/RefComponentDescriptionWorkaroundV32_EXT34 still existsEXECWhen setting the trace file to a TTY to get traces on the screen, if the variable MCC_CHECK_TRACE_FILE_SIZE is set, after the maximum file size is reached a file /dev/ttyp4.1 is created and it is no more possible to get the traces on the screen.54EXECWhen lauching FCL from Iconic Map if we use the exit command in FCL the dxterm hang.The dxterm may be closed with menu item Exit afterwards.The problem is only reproducible under sh shell, so another shell can be used.59TFCThe following code generates in V32 compilation errors: MUnsigned32 foo = 1; if (foo == 1) foo = 2; We have to cast the rvalue or the lvalue. For instance: if ((MCC_T_Unsigned32)foo==1) Seems incomplete !V32_INT784 still existsTFCWhen several directives (create/delete/show) access the same TFC management module concurrently, some of them may fail with the error MCC-E-IN_USE_ERROR. TNSQAR DBID/RefComponentDescriptionWorkaroundV32_INT1172TNSThe TNS server crashes itself when it has received a request older than the current time.We strongly recommend to use NTP for synchronizing TNS/TeMIP machines.V32_EXT25 still existsTNSThe customer would like to be able to perform all TNS management activities without being root user on the system.To be fixed in a future patch.  34^i~2EH9:;U½zzHh#'HhmHj}UmH jUmHjUmHjHh#'HUmHHh#'HmH jUCJCJWCJWOJQJ CJ(OJQJ5CJ$OJQJ5CJ,OJQJ5CJOJQJ CJOJQJ, 34YZ[\]^_$@&$@&$ 34YZ[\]^_EZY G. u  9 s 9 }  U 1 y SC-½YHEZpiiibbi  !  ! H & FC$Eƀ!'DC$Eƀ UVWXYij89:TUVWXjUmHjkUmHjUmHjqUmHjUmHHh#'HhmHjwUmHjHh#'HUmHHh#'HmH jUmHjUmH6Y G. u  9 s 9 }  U 1 y S !  !   ! '(BCDEFqr  ) * + , - U V p q r s t » jUmHjSUmHjUmHjYUmHjUmHj_UmHjUmH jUmHjeUmHjHh#'HUmHHh#'HmH7    3 4 5 7 8 R S m n o q r   3 4 5 7 8 \ ] w x y { |     j UmHj; UmHj UmHjA UmHj UmHjG UmHjUmH jUmHjMUmHHh#'HmHjHh#'HUmH8   " # 3 4 5 O P Q S T U X Y     + , - / 0 1 4 5 W X Y s t u w x jUmHj)UmHj UmHj/ UmHj UmH jUmHj5 UmHHh#'HhmHHh#'HmHjHh#'HUmH: 23MNOQRpq"#=>?ABdejUmHjUmHjUmHjUmHjUmHjUmHjUmH jUmHj#UmHHh#'HmHjHh#'HUmH8SC-=W(Ty 0J^ !  !  !  X!   ! *-:=Tt945 N, f !&"F"###D######$$6$C$K$P$]$$$$$%%%O&&&¸´´²²²nHB*h5>*5CJKHOJQJ5h jCJUcHdh"'gHhmHcHdh"'gHmHHh#'HmHjHh#'HUmHD-=W(Ty 0J^{6t=YĿ~ytoje`[.JuQy )=W}3_0JZ!^{6t=Y9] X!  !  !  ! 9]  89?e456XŽ}zrolif` % ef  w   , -.G  ]           mnij  *Nl"  89sF & FEƀ 'CEƀ '. ?eq*F & FEƀ 'F & FEƀ 'F & FEƀ 'qooF & FEƀ 'F & FEƀ '456qooooF & F Eƀ 'F & F Eƀ 'XlM & F% hEƀ 'CEƀ '.@A?»_ N_<\ , »}urolg_\Y\  u;  {  STU    B  q       e %  5%  U%  |%  cM & F% hEƀ 'M & F% hEƀ '@AcaaM & F% hEƀ 'M & F% hEƀ '?q*F & FEƀ 'F & FEƀ 'F & FEƀ '»_q*F & FEƀ 'F & FEƀ 'F & FEƀ '_ N_lhhhF & FEƀ '1$F & FEƀ ' <\ , kF & FEƀ 'F & FEƀ ', f ! !5!F!i!!!&"F"r""""####D####$$$$$$$%%~{xpma^h/  /0  LMKLx  >r  S    -l    #, f ! !mgaaahF & FEƀ 'F & FEƀ ' !5!F!i!!!&"F"r""mkkF & FEƀ 'F & FEƀ ' """####D####e_F & FEƀ ' hF & FEƀ ' #$$$$$$$%%%wCEƀ '..CEƀ '. %%%N&O&P&&&&))<)=)))))R*S*f*g*++,,a-b-0/1/e0f0g1h1|1Ⱥ|wolda^[X^_`a  d  e_`9   9hi  OP   UV@  @  ^t   t!%%N&O&P&&wCEƀ '.CEƀ '..&&&))<)=)))vtttCEƀ '..1$CEƀ '..&))R*f*a-b- 3<3U3d4e4+565M55R8S8w8;<<>>^>g>.?7??@@»@@@BBDE)FXFDGEGfGgGHHkHIJJJJLL'MO O,P-PQQSnVVV]YnYoYYYZZZ[w[[[ \\o````|c 5B*hnH  B*hnH hnH5B* 6hnH >* CJhnH  5hnH hhnH Q)))R*S*f*g*++,,a-b-1$CEƀ ' b-0/1/e0f0g1h1|1~1lH & F1$Eƀ ' 1$H & F1$Eƀ ' |1~1111!2e2f22223 3<3=3U3V3d4e4L5M566R8S8w8x8%9&999;;.;/;}zwtqnkhZWV{   {NO9   9^(  )c  dKLZ[O   O Q 3`  a  H  J"~1111!2e2f2gH & F1$Eƀ ' 1$1$hH & F1$Eƀ ' f22223 3<3=3`^O & FQ1$h 8hEƀ '1$1$hH & F1$Eƀ '=3U3V3d4e4L5M566oH & F1$Eƀ '1$CEƀ '6R8S8w8x8%9&999;;.;/;qqoCEƀ '1$H & F1$Eƀ ' /;;<<<<>>s>-?d?e???@W@X@@»@@@#A$AsBtBPCQCnCoCCCCCCCD|ytoje`[deyz>?   ,?  -?   Wq?  r?  U#/;;<<<<>>s>-?d?e?d```|J & F?|Eƀ '1$J & F?|Eƀ ' e???@W@X@@»@@@cJ & F?|Eƀ ' |J & F?|Eƀ '  @#A$AsBtBPCQCnCoCCCCCCCD(D]DDCEƀ 'D(D]DDDEEE(E)E>ESEEEE)FXFlFmFGGDGEGfGgGGGHHHkHlHIIJJJJLL'MMO¿}zwpmj» L ! J LM pG qQRG   GKL 9i$9:MNa:O(DDEEE(E)E>ESEEEE)FXFlFmFGGDGEGEGfGgGGGHHHkHlHIIpk1$hF & FGEƀ '1$CEƀ ' IJJJJLL'MMO Olgg1$hF & FLEƀ '!1$F & FJEƀ ' O O,P-PQQSSS=S>S\SUpUUUUUnVoVWW\Y]YnYoYZZZ[[X[[ \!\\\|yvspmjm"#hi ` a   AUL  LM   O  N  M $ O,P-PQQnF & FNEƀ '1$F & FMEƀ 'QSSS=S>SsCEƀ '.F & FOEƀ '>S\SUpUUUUUnVoVWW\Y]Ywuu CEƀ '..CEƀ '.. ]YnYoYZZZ[[X[[ \!\\\\\ ^!^^^__1$CEƀ '..\\\ ^!^^^__````aaa a c"c#c0d1d|dd3eeee f"fwfzfff½wogb]XURZ\T  T  IT  T   T  KU LYZM   MTUU  UV   5)*AB]^   _````aatrCEƀ '..D1$Eƀq'f1$aa a c"c#c0d1d|dlM & FU hEƀ 'CEƀ '|cccc fzfgg,h6hBhJhnh|hhhj j»jjjj'k3kkk*l5lPndnnnoooo3oGo\ojooooo@pLpbqnqqqqqrrrsss;sIsssttuuuuvvvv*w5wwwzx{xxxxxxx»xx%yzy{yy{/|>*j U jUB*5hnH6[|dd3ecM & FT hEƀ 'M & FT hEƀ '3eeeecM & FT hEƀ 'M & FT hEƀ 'e f"fwfzfff heF & F!Eƀ '.1$M & FT hEƀ 'f h8hhhi>i\ii jjjjkl8lalylllllmHnopļxjgda^WMC]  ]   ] UV   !  D!  e!  !  !  !  !  p!  !   !  >/  `/   / !  D!  \!   !  h8hhhq*F & F!Eƀ '.F & F!Eƀ '.F & F!Eƀ '.hi>icM & F/ hEƀ 'qM & F/ hEƀ 'q>i\ii jj#F & F!Eƀ '.F & F!Eƀ '.M & F/ hEƀ 'q jjjjq*F & F!Eƀ ' .F & F!Eƀ '.F & F!Eƀ '.jkl8lq*F & F!Eƀ ' .F & F!Eƀ ' .F & F!Eƀ ' .8lalylllq.,CEƀ'F & F!Eƀ '.F & F!Eƀ ' .lllmHnoaM & F]8 h8Eƀ 'M & F]8 h8Eƀ 'opvqq r@rnrrsXssst,tttduuujvM & F]8 h8Eƀ 'pvqq r@rnrrsXssst,tttduuujv wwwx.xxy"y#y$y%yzy{yyyyyyyz.zzzzrj    - O PQ  qr!F"\EA~#v)jv wwwx.xxy"y#y$y%yzy{yyyyyyyDC$Eƀ '.yz.zzzl%F & FEƀ ' F & FEƀ ' F & FEƀ ' & Fzzd{{{.|/|0}1}2}k}l}}}}}}~~M~abtuހ߀XYwۂ}zwtqnkhe9`aKL   89"ab  9:    I    'zzd{{{q*(F & FEƀ 'F & FEƀ 'F & FEƀ '{.|/|0}1}2}k}l}}}}}}~uCEƀ ' ..DC$Eƀ '. /|c|/}0}1}2}}}}}݀߀Yv89:\#$%=>ň舙`: &ș˙|»زئءhnH5H*0JjUhnH jUhnH 5CJcHdh"'gHmH  5>*hnH  >*B*hnH hnH h 5hnH OJQJhnH 5B*OJQJhnH  >*B*hB*h=~~M~abtuހ߀XYwCEƀ ' ..ۂ܂89:\]CDdwCEƀ ' ..CEƀ!' ۂ܂89:\]CDdPQjkTUˆÈĈň|yvspmjVklNO   \]IijPQk   kr wx(PQjkTUCEƀ ' ..ˆÈĈň鈊ljȉpqCEƀ ' ..ň鈊ljȉpqXYdefg&'@»vspb_Z   \3  3      \]  WX78pqOP   $XYoF & FEƀ 'DC$Eƀ '. defgqDC$Eƀ ' .F & FEƀ '&'@wCEƀ '..CEƀ '..֎:;Qޏߏ>Z鐼 ȓғޓ|wrmhd_  xy            »UV  fh23Z   i     [\     ]   "֎:;QޏߏwCEƀ '..CEƀ '..ߏ>ZqF & FEƀ 'DC$Eƀ ' .鐼q*(F & FEƀ 'F & FEƀ 'F & FEƀ ' ȓғޓ$$l4"R& $DC$Eƀ ' .(TҔaߕ$hX 1$$$#$$l"Z R& (TҔaߕ$h  ½}xtqnkhc_Z  TU  defghi    L  V  Z  bc  d  l      <          J  v  w            8  c  m  p#  $09$$l4"R& $$$l"Z R&$09:BLU &?ș˙ϙS|}½xsnid`[      f                      !  :  S          &'  0  <  F  M#9:BLU &?(ٷ٘$$l4"R& $$l"Z R&1$$$#$$l"Z R& ș˙ϙS|}$$l"Z R&1$$#$$l"Z R& $|}'(z|}ě֛wx[_wx tؠܠA@APQ56iuʨ#'(AB䫠6hnH  >*B*hnH  6B*hnH h B*hnH hnH5W%&'()*z{|}~Ûě̛ϛ֛>qwxy|Ҝߜmwxy| tؠ»  YZ[\]^_`ab  w      I%&'()*z{|}~$DC$Eƀ ' .1$Ûě̛ϛ֛>qwxy|Ҝ߼ߟ$$l"Z R&#$$l"Z R& $$$l4"R& Ҝߜmwl$H & F-$Eƀ '-H & F-$Eƀ '-H & F-$Eƀ '-$wxy| tؠD($$$l"Z R&)5@AILUǡ@ABEUȢPQY]b56>BKt"åͥDIJ[ʨ˨̨ͨΨϨިߨ#&'(03<˪ABJMVbd)5@AILUǡ@ABEUȢP߼ߟ@$$l"Z R&#$$l"Z R& $$$l4"R& PQY]b56>BKt"åͥD4$$$l"Z R&IJ[ʨ˨̨ͨΨϨިߤ$$l"Z R&$ިߨ#&߼ߟp$$l"Z R&#$$l"Z R& $$$l4"R& &'(03<˪ABJMVbhߘ$$$$l"Z R&$b¬ɬЬڬ { T-.Oez{İΰڰQ(GHIJKLNOO¬ɬЬڬ { ߼Tߟ$$l"Z R&#$$l"Z R& $$$l4"R& T-.Oez{ $$l"Z R&$İΰڰQ$$l"Z R&1$$#$$l"Z R& $$l4"R& $1$󰘱GJOhnH5(GHIJKLMNO1$$$l"Z R&$1$$ / =!"#$%}DyK _Toc426522750}DyK _Toc426522751}DyK _Toc426522752}DyK _Toc426522753}DyK _Toc426522754}DyK _Toc426522755}DyK _Toc426522756}DyK _Toc426522757}DyK _Toc426522758}DyK _Toc426522759}DyK _Toc426522760}DyK _Toc426522761}DyK _Toc426522762}DyK _Toc426522763}DyK _Toc426522764}DyK _Toc426522765}DyK _Toc426522766}DyK _Toc426522767}DyK _Toc426522768}DyK _Toc426522769}DyK _Toc426522770}DyK _Toc426522771}DyK _Toc426522772}DyK _Toc426522773}DyK _Toc426522774}DyK _Toc426522775}DyK _Toc426522776}DyK _Toc426522777}DyK _Toc426522778}DyK _Toc426522779}DyK _Toc426522780}DyK _Toc426522781}DyK _Toc426522782}DyK _Toc426522783}DyK _Toc426522784}DyK _Toc426522785}DyK _Toc426522786}DyK _Toc426522787}DyK _Toc426522788}DyK _Ref423773128DyK VBETEMIPSUPP@digital.comyK @mailto:VBETEMIPSUPP@digital.com" [$@$NormalmH ` Heading 1$ & F<@&EƀX'.5CJ,KHOJQJ` Heading 2 & F@&C$Eƀ)'F56CJ OJQJnH ` Heading 3$ & F@&C$Eƀ'5CJhmH nH R`R Heading 4$ & F<@&5CJOJQJhnH @`@ Heading 5 & F<@&CJmH D`D Heading 6 & F<@& 6CJmH D`D Heading 7 & F<@& OJQJmH H`H Heading 8 & F<@&6OJQJmH N `N Heading 9 & F<@&56CJOJQJmH *B**B@R* Body Text5,`,TOC 1x 56CJ.`.TOC 2 x5CJ"`"TOC 3"`"TOC 4X"`"TOC 5 "`"TOC 6"`"TOC 7"`"TOC 8x"`"TOC 9@JC@JBody Text IndentB*OJQJhnH 4Q@4 Body Text 3 B*hnH HR@HBody Text Indent 2 !1$hhnH OOLU  &|c/||O$S^_, !"#%&)b-~1f2=36/;e?@DEGI OQ>S]Y_a|d3ee hh>i jj8llojvyz{~򌧍ߏ9ҜwPި&O»    !"#%-, %|1/;DO\fpzۂňbO  UnknownJean-Marc BronoelC-VENE:VXi9UW'CEq*,Uqs47Rnq47\x{4PS , / X t w   2 N Q p   " > A d zttt$=O %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%X/X$2$g a+iry@0(  B S  ?O7 _Toc414360809 _Toc414360810 _Toc426522750 _Toc414360811 _Toc426522751 _Toc426522752 _Toc426522753 _Toc426522754 _Toc400863285 _Toc414360812 _Toc426522755 _Toc426522756 _Toc426522757 _Toc426522758 _Toc426522759 _Toc426522760 _Toc426522761 _Toc426522762 _Toc426522763 _Toc426522764 _Toc426522765 _Toc426522766 _Toc426522767 _Toc426522768 _Toc426522769 _Toc426522770 _Toc426522771 _Toc426522772 _Ref423773128 _Toc414360819 _Toc426522773 _Toc414360820 _Toc426522774 _Toc414360821 _Toc426522775 _Toc414360822 _Toc426522776 _Toc414360823 _Toc426522777 _Toc414360824 _Toc426522778 _Toc414360825 _Toc426522779 _Toc414360826 _Toc426522780 _Toc426522781 _Toc426522782 _Toc426522783 _Toc426522784 _Toc426522785 _Toc414360827 _Toc426522786 _Toc426522787 _Toc414360829 _Toc426522788 !P"P"P""%%S&=/S47OQX\] _yhhuu2y2yyy||::ńńg';ߋߋP  !"#$%&'()*+,-./0123456 !!""";%%e&T/v4-7"=eCEFKrwDIot h!s!!!!!."3"j"o"x"}"""""""########$$z$$#%(%1%6%~%%%%%%l&q&&&1'6']'b'( (6(;((() )))))E*J* ++I+LP<T &mLPJean-Marc Bronoel8C:\Users\bronoel\Public\SSB\TMPV32_REL_TFRV3201D_V10.DOCJean-Marc Bronoel8C:\Users\bronoel\Public\SSB\TMPV32_REL_TFRV3201D_V10.DOCJean-Marc Bronoel8C:\Users\bronoel\Public\SSB\TMPV32_REL_TFRV3201D_V10.DOCJean-Marc Bronoel9C:\TEMP\AutoRecovery save of TMPV32_REL_TFRV3201D_V10.asdJean-Marc Bronoel8C:\Users\bronoel\Public\SSB\TMPV32_REL_TFRV3201D_V10.DOCJean-Marc Bronoel8C:\Users\bronoel\Public\SSB\TMPV32_REL_TFRV3201D_V10.DOCJean-Marc Bronoel8C:\Users\bronoel\Public\SSB\TMPV32_REL_TFRV3201D_V10.DOCJean-Marc Bronoel8C:\Users\bronoel\Public\SSB\TMPV32_REL_TFRV3201D_V10.DOCJean-Marc Bronoel8C:\Users\bronoel\Public\SSB\TMPV32_REL_TFRV3201D_V10.DOCJean-Marc Bronoel9C:\TEMP\AutoRecovery save of TMPV32_REL_TFRV3201D_V10.asd\ Cv = L 6L kY|<\  +  {Z4 SV t8tPxVRx( 6M e  Dn aro p y, ܶ ( b  oLL ay!S" bKb"  -S%ef% yi% ^& *V& ~' i R'!,F .T!. Sk/ jO2 Xe3 4x4I5FfN*5 *f7 P8 f8 #9L d9 89 +,9 q: bf; 7~z>АoDL ED vEPxVDvJ M>K PLM $N R x%R J):S E V\fWt`pNY Y d^(^^ SRa84e )i JjPxV!Cl Anpy X o csN t Kft th .tPxVt huDwj Tx UO!|"GZ w}|Zt8~ zW bj( *@h hOJQJo( hhOJQJo(hh. hhOJQJo(hho(-@ OJQJo(hho(hho(.0o(..88o(... 88o( .... `o( ..... `o( ...... o(....... o(........@hh.hh.@ OJQJo( hhOJQJo(@ OJQJo( 88OJQJo(@ OJQJo(hh.hh.hh.hh.@ OJQJo(hh. hhOJQJo(hho(- hhOJQJo(hh.hho(-@ OJQJo( hhOJQJo( hhOJQJo(@h hOJQJo( hhOJQJo( hhOJQJo( hhOJQJo( hhOJQJo(hh.@ OJQJo(h8.1.1.1 hhOJQJo( hhOJQJo( hhOJQJo( hhOJQJo(@h hOJQJo(@h hOJQJo(h.1.1hh.hh.hh.hh.hho(-hhCJOJQJo(q hhOJQJo( hhOJQJo(hh. hhOJQJo(88o(-hho(- hhOJQJo( 88OJQJo(hh. hhOJQJo( hhOJQJo( hhOJQJo( hhOJQJo(hh. hhOJQJo(@ OJQJo(h.1@h hOJQJo( hhOJQJo(@ OJQJo(hh.@h hOJQJo( hhOJQJo( hhOJQJo( 88OJQJo( hhOJQJo(hho(- hhOJQJo(@h hOJQJo(hh.@h hOJQJo(P.@@.0..``...  ....  .....  ...... `....... 00........ 88OJQJo(hh.@ OJQJo(@ OJQJo(hh.h.1.1P@@.0..``...  ....  .....  ...... `....... 00........ hhOJQJo(hh.hho(hho(.0o(..88o(... 88o( .... `o( ..... `o( ...... o(....... o(........` tYbjro*f7f8+ bj <\ LoD#9oL6.T!.*V& Y89Xe3Sk/PLMP+,9NYKft -S%x4!,4cs~'w}SRa jO2J):Se N t*5)i7~z>SVAnRd9x%Rb x(q:tCvM>KEDef%^&bKb"bf;8~84e X oXP8tDnzWS"d^i R'khuRay!E Vt8{Z4 DwavEJj.tyi%!Cl (6My, j Tx(^^=$NDvJp\fWUO!|I5T  \ @h hOJQJo( @h hOJQJo(`@| OJQJo(d`@ OJQJo(\@88`??88O`@GTimes New Roman5Symbol3& Arial;& HELVETICA;Wingdings"1h#'#''6I2$0dTeMIP V3.2 Release NotesTelecom EngineeringJean-Marc BronoelOh+'0 , H T ` lxTeMIP V3.2 Release Notes0eMITelecom Engineeringele Normal.dotiJean-Marc Bronoelg2anMicrosoft Word 8.0@@pf»@gn@gn6՜.+,D՜.+,@ hp  Compaq2I TeMIP Version 3 Title4(RZ _PID_GUID _PID_HLINKSAN{8620E340-A907-11D1-8409-0000F8048D50}Ax<{ mailto:VBETEMIPSUPP@digital.com  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~»      !"#$%&()*+,-./013456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^`abcdefhijklmnsRoot Entry F_,opouData 'o1Table2 XWordDocumentLSummaryInformation(_DocumentSummaryInformation8gCompObjj  FMicrosoft Word Document MSWordDocWord.Document.89q