tnms_imn

Installation

TNMS Core/CDM 9.0

Installation Manual (IMN)

A42022-L5938-H52-1-76D1

2 A42022-L5938-H52-1-76D1

Installation Manual (IMN) InstallationTNMS Core/CDM 9.0

f Important Notice on Product SafetyElevated voltages are inevitably present at specific points in this electrical equipment. Some of thecircuit parts may also have elevated operating temperatures. Systems with forced ventilation haverotating items.

Non-observance of these conditions and the safety instructions can result in personal injury or in prop-erty damage.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to complywith the applicable safety standards.

Mount the systems in areas with restricted access only. Only trained and qualified personnel mayinstall, operate, and maintain the systems.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangsläufig bestimmte Schaltungsteile der Geräte unter Spannung.Einige Teile können auch eine hohe Betriebstemperatur aufweisen. Anlagen mit Zwangsbelüftunghaben drehende Teile.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverletzungen undSachschäden führen.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Gerätemüssen die zutreffenden Sicherheitsbestimmungen erfüllen.

Die Anlagen dürfen nur in Betriebsstätten mit beschränktem Zutritt aufgebaut werden. Die Anlagendürfen nur durch geschultes und qualifiziertes Personal installiert, betrieben und gewartet werden.

Trademarks:

All designations used in this document can be trademarks, the use of which by third parties for theirown purposes could violate the rights of their owners.

Copyright (C) Siemens AG 2004.

Issued by the Information and Communication Networks GroupHofmannstrasse 51D-81359 Munich

Technical modifications possible.Technical specifications and features are binding only insofar asthey are specifically and expressly agreed upon in a written contract.

A42022-L5938-H52-1-76D1 3

InstallationTNMS Core/CDM 9.0


This document consists of a total of 132 pages. All pages are issue 1.

Contents

1 Basic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 Supplementary Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2 CE Conformity Declaration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.3 Personnel Requirements for Commissioning . . . . . . . . . . . . . . . . . . . . . . . . 7

2 Protective Measures and Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.1 Safety Precautions When the Unit is Open. . . . . . . . . . . . . . . . . . . . . . . . . . 92.1.1 Protection against Excessive Contact Voltages . . . . . . . . . . . . . . . . . . . . . . 92.2 Handling Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3 Preparation for Commissioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.1 Component Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.2 Hardware Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.2.1 Installation and Cabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.2.2 Mirror Disks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.2.3 Standby Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.3 Required Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.3.1 Installation Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.3.2 HW/SW Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.3.3 Installation Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

4 Installing the Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184.1 Before you Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184.1.1 Licensing Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184.1.2 Protocol Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194.2 Installing Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194.2.1 Installing Windows 2000 Server (If SCSI RAID is Already Configured) . . . 194.2.2 Installing Windows 2000 Server (incl. SCSI RAID Configuration) . . . . . . . 254.2.3 Installing Windows 2000 Professional . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304.2.4 Installing Windows 2000 Service Pack 4 . . . . . . . . . . . . . . . . . . . . . . . . . . 334.2.5 Installing Windows 2000 Server Terminal Services . . . . . . . . . . . . . . . . . . 334.3 Hardware Configuration under Windows 2000 . . . . . . . . . . . . . . . . . . . . . . 334.3.1 Installing the PCI I/O Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

5 Prerequisites and 3rd-Party Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355.1 Installing MSDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355.2 Installing MSXML 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355.3 Installing an OSI Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365.4 Installing Citrix MetaFrame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375.4.1 System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375.4.2 Installing the MetaFrame Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385.4.3 Installing MetaFrame Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

6 Installing the TNMS Core/CDM Software . . . . . . . . . . . . . . . . . . . . . . . . . . 436.1 Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436.2 Installing TNMS Core/CDM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436.2.1 Deinstalling TNMS Core/CDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

4 A42022-L5938-H52-1-76D1


6.2.2 Adding and removing individual TNMS Core/CDM Components. . . . . . . . . 48

7 Installing Additional TNMS Core/CDM Software . . . . . . . . . . . . . . . . . . . . . 517.1 Installation Matrix for TNMS @P and TCOA Proxy Software . . . . . . . . . . . 517.2 Installing TCOA Proxy and SNMP Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . 517.2.1 3rd-Party Software for TCOA Proxy and RPR Manager . . . . . . . . . . . . . . . 517.3 Installing TCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567.3.1 3rd-Party Software for TCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577.3.2 TCOM Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627.3.3 TCOM Configuration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637.3.4 TCOM EML Server Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657.3.5 TCOM DCN Management Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 697.4 Installing PLET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727.5 Installing Waveline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727.6 Installing MSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737.7 Installing TNMS @P Server and Enhanced Applications. . . . . . . . . . . . . . . 74

8 Measures after Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768.1 Initial Configuration of TNMS Core/CDM Using SysAdmin . . . . . . . . . . . . . 768.2 Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 788.3 Routing Settings for PCs with Multiple Network Adapters . . . . . . . . . . . . . . 79

9 System Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809.1 Adding Additional Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809.2 Adding Additional NetServers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

10 Multi Server CDM: Protective Measures and Handling . . . . . . . . . . . . . . . . 8110.1 Safety Precautions When the Unit is Open . . . . . . . . . . . . . . . . . . . . . . . . . 8110.1.1 Protection against Excessive Contact Voltages. . . . . . . . . . . . . . . . . . . . . . 8110.2 Handling Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

11 Multi Server CDM: Preparation forCommissioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

11.1 Component Delivery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8311.2 Hardware Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8311.2.1 Installation and Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8311.2.2 Mirror Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8411.2.3 Standby Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8411.3 Required Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8411.3.1 Installation Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8411.3.2 HW/SW configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8611.3.3 Installation Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

12 Multi Server CDM: Installing the Operating System. . . . . . . . . . . . . . . . . . . 8812.1 Before you Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8812.1.1 Licensing Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8812.1.2 Protocol Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8912.2 Installing Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8912.2.1 Installing Windows 2000 Server (If SCSI RAID is Already Configured) . . . . 9012.2.2 Installing Windows 2000 Server (incl. SCSI RAID Configuration) . . . . . . . . 9512.2.3 Installing Windows 2000 Professional . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

A42022-L5938-H52-1-76D1 5



12.2.4 Installing Windows 2000 Service Pack 4 . . . . . . . . . . . . . . . . . . . . . . . . . 10312.2.5 Installing Windows 2000 Server Terminal Services . . . . . . . . . . . . . . . . . 10312.3 Hardware Configuration under Windows 2000 . . . . . . . . . . . . . . . . . . . . . 10312.3.1 Installing the PCI I/O Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

13 Multi Server CDM: Prerequisites and3rd-Party Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

13.1 Installing MSDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10613.2 Installing MSXML 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10613.3 Installing an OSI Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10713.4 Citrix MetaFrame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10813.4.1 System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10813.4.2 Installing the MetaFrame Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10913.4.3 Installing the MetaFrame Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

14 Multi Server CDM: Installing the Multi Server CDM Software. . . . . . . . . . 11414.1 Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11414.2 Installing Multi Server CDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11414.2.1 Deinstalling Multi Server CDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11714.2.2 Adding and removing individual Multi Server CDM Components . . . . . . . 118

15 Multi Server CDM: Measures afterCommissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

15.1 Initial Configuration of Multi Server CDM Using SysAdmin . . . . . . . . . . . 12015.2 Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12215.3 Routing Settings for PCs with Multiple Network Adapters . . . . . . . . . . . . 122

16 Multi Server CDM: System Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . 12516.1 Adding Additional Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

17 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

18 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

6 A42022-L5938-H52-1-76D1


A42022-L5938-H52-1-76D1 7



1 Basic InformationBefore you begin commissioning, read the general notes on documentation in the Tech-nical Description (TED) as well as chapters 1 and 2 of this manual.

Initial installation is described beginning with “Preparing for Commissioning” in chapter3. “Installing the Operating System” is given in chapter 4 and “Prerequisites and 3rd-Par-ty Software” in chapter 5. The installation of TNMS Core/CDM is described from Chapter6 onwards, deinstallation in Section 6.2.1 and the addition of individual TNMSCore/CDM components/subcomponents in Section 6.2.2. Installation of additionalTNMS/CDM software is described in chapter 7 while chapter 8 contains the measuresafter commissioning. Information on System expansion is contain in chapter 9.

Installtion information for the optional Multi Server CDM software is given from chapter10 to 16.

1.1 Supplementary DocumentationIn addition to the documentation named in the Technical Description (TED), the follow-ing information is also available:– Delivery notes :

These provide an overview of the hardware, software and documentation delivered.– Documentation from the O&M Center :

On request, Siemens Technical Sales can supply project documentation which pro-vides specific information about the installation. These planning documents areavailable to the customer after installation work is completed.

– Protocols :During commissioning, an acceptance protocol should be maintained. The accep-tance protocol supplied must be completed and signed by Siemens service person-nel and the customer to prove correct commissioning of the system and to providea record of the initial configuration in case of later queries.

– Field test protocols :To help ensure successful commissioning, you can also consult the official field testprotocol. These provide information on the values used in system testing, and canbe obtained from Siemens Technical Sales.

1.2 CE Conformity DeclarationThe CE conformity declaration for the product is fulfilled if installation and cabling arecarried out in accordance with the documentation supplied. Where necessary, project-specific documents should be taken into account.Deviations from the specifications, or modifications during installation such as the useof cable types with lower shielding dimensions may violate CE protection requirements.In such cases, the conformity declaration is invalidated. Responsibility for any subse-quent problems lies with the person responsible for the deviation.

1.3 Personnel Requirements for CommissioningThe following personnel requirements must be fulfilled for commissioning:

iTo protect TNMS Core/CDM against viruses, you should install F-Secure on all TNMSCore/CDM machines. Contact the software release notes to see the released versions.

8 A42022-L5938-H52-1-76D1


– Training to service technician level or equivalent training in communications engi-neering.

– Sound knowledge of transmission systems.– Appropriate, device-related training by the manufacturer (incl. required device and

system knowledge for the planned activity).– Detailed PC knowledge, additional knowledge of operating MS Windows 2000.– Familiarity with LANs / WANs.– Basic knowledge of measurement systems.– Knowledge of operating electrostatic-sensitive devices.– Knowledge of handling optical fibers and laser light sources.

A42022-L5938-H52-1-76D1 9



2 Protective Measures and HandlingProtective measures and information on handling electrical components in the TNMSCore/CDM installation is provided here.

2.1 Safety Precautions When the Unit is OpenBefore opening the unit, remove the power cable.

Once the unit is open, live connector pins are freely accessible. To prevent electricshocks, make sure that these pins do not come into contact with foreign potential (e.g.ground).

2.1.1 Protection against Excessive Contact VoltagesWhen dealing with the power supply, observe the safety precautions as specified by theGerman DIN standard VDE 0105 (operation of high-voltage systems). This standard de-fines in detail the steps to be taken by the operators of electrical installations and theusers of electrical equipment to ensure the safe maintenance of electrical installationsand equipment.

2.2 Handling ModulesModules labeled as shown in Fig. 2.1 below are equipped with electrostatic-sensitivecomponents.

Fig. 2.1 Labeling of electrostatic-sensitive devices (ESD symbol)

All modules with ESD components have an outer grounding edge which is connected tothe module "ground" and which can be used when gripping the circuit board.

Modules are fully protected if they are enclosed in a shielded, unopened housing.Nevertheless, the following basic safety precautions should always be followed whenhandling ESD components:– Always use a grounding bracelet connected to a grounding socket (see below) when

unpacking, packing, touching, unplugging or plugging modules bearing the ESD(German EGB) symbol. This will ensure that the modules do not get damaged.

– Avoid touching the component connections, connector contacts or conductor tracks(even if you are properly grounded).

– When unplugging and plugging modules, make sure you use the handles provided.– If modules are only gripped by the handles for plugging/unplugging, they should not

be transported in a horizontal position (danger of breakage).– When you remove the module from its subrack, place it on an antistatic mat.– Make sure that all measuring equipment used is grounded.

iAs a general rule, you should always note the manufacturer’s instructions when han-dling devices such as PCs, monitors, printers and tape drives, or when installing mod-ules such as network cards.

10 A42022-L5938-H52-1-76D1


– If you are using ungrounded measuring equipment, briefly connect the measuringprobe to ground (discharge) it before performing measurements on components andmodules.

– Ensure that the modules are installed in the correct slots.

iEuropean standard EN50082-1 contains detailed information on the correct handling ofelectrostatic-sensitive devices.

A42022-L5938-H52-1-76D1 11



3 Preparation for Commissioning

3.1 Component DeliveryBefore installation, ensure that:– the delivery is complete in accordance with the delivery units specified in the deliv-

ery note (hardware, software and documentation),– the components are not damaged in any way.

3.2 Hardware RecommendationsThis table provides an rough overview of the hardware requirements for running TNMSCore/CDM software. Together with other parameters (e.g. number of Clients, number ofNetServers) the hardware configuration must be planned specifically for each customer.More information is available from Siemens Technical Sales.

Server NetServer Client

CPU: Xeon TX300, 2.66GHzMultiprocessor operationsupported

CPU: P4, 2.4 GHzMultiprocessor operationsupported.

CPU: PIII, 1 GHzMultiprocessor operationsupported.

Memory:1 GB or 2 GB *)

Memory:2 x 512 MB

Memory:2 x 256 MB

Hard Disk:2 x 36 GB

Hard Disk:40 GB

Hard Disk:40 GB

Floppy Disk:1.44 MB

Floppy Disk:1.44 MB

Floppy Disk:1.44 MB

CD-ROM drive CD-ROM drive CD-ROM drive

Ethernet card Ethernet card, 2x Ethernet card

RAID controller - -

DAT streamer for backup - -

- - PCI I/O, optional

Color monitor 17” Color monitor 17” Color monitor 21”

Operating system:Windows 2000 Server

Operating system:Windows 2000 Profes-sional


*) Enhanced Hardware

Tab. 3.1 Hardware Requirements for TNMS Core/CDM Server, NetServer and Cli-ent

12 A42022-L5938-H52-1-76D1


3.2.1 Installation and CablingBefore installing the operating system, the following steps should be completed:– The Client, NetServer and Server PCs should be set up and cabled in accordance

with the project-specific installation documents supplied.– The applicable recommendations for screen-based workstations should be ob-

served.– To guarantee 24-hour operation, an uninterrupted power supply must be available.

3.2.2 Mirror DisksThe TNMS Core/CDM Server PC is provided with a RAID system and two additional mir-ror disks which are monitored by a SCSI RAID controller. The SCSI RAID controller en-sures automatic data synchronization between the active hard disk and the mirror disks,so if the active hard disks develops a fault, a mirror disk takes over and the system isnot affected. The faulty disk can be replaced by a new disk of the same type withoutshutting down the Server. The RAID controller then copies the data from the active harddisk to the newly installed hard disk.

3.2.3 Standby ServerYou have the option of configuring a warm standby TNMS Core/CDM Server. The warmstandby server is a second server machine with exactly the same hardware and soft-ware configuration as the active server. The operator registers the warm standby serverat the active TNMS Core/CDM Server and activates the database replication mecha-nism of TNMS. Should a failure occur, the operator simply switches manually to thewarm standby server and starts the TNMS Core/CDM Server process on the warmstandby system.A cold standby TNMS Core/CDM NetServer is also supported. The cold standby Net-Server is a second machine with exactly the same hardware and software configurationas the active NetServer. Activating a cold standby NetServer requires full DCN accessat the standby site.In both cases, the faulty system can then be repaired and implemented as the standbysystem. More information is available from Siemens Technical Sales.

3.3 Required SoftwareAll software parts mentioned in Section 3.3.1 must be released for the appropriateTNMS software version. This holds for the initial installation and for service or upgradepackage installations as well.

3.3.1 Installation SoftwareThe following software is generally required for the installation. The corresponding CDorder numbers are provided in the TNMS Core/CDM release documentation.

More information on the installation sequence is provided in Section 3.3.3.

1. ServerStart:If you are using the Fujitsu Siemens PRIMERGY server system, the ServerStart CD

iIf additional software is installed which is not required for TNMS Core/CDM, correctfunctionality of TNMS Core/CDM cannot be guaranteed.

A42022-L5938-H52-1-76D1 13



provides the necessary utility programs and drivers for configuring and installing theserver machine. More information is provided in Section 4.2.

2. Windows 2000 Professional and Windows 2000 Server incl. Service Pack 4:The Windows 2000 Professional operating system is required for the Client and Net-Server machines. Windows 2000 Server must be installed on the Server machineand on the Client machine if Metaframe XP is installed on the Client machine also.Installation instructions for both operating systems are provided in Chapter 4, how-ever, pre-installed machines can also be used.

3. Windows 2000 Terminal Services:The Windows 2000 Terminal Services component must be installed on the clientmachine so that the TNMS Core/CDM system can be accessed remotely viaMetaFrame. More information is provided in Section 4.2.5.

4. MetaFrame XP (FR2):MetaFrame XP is used to enable remote access to the TNMS Core/CDM Client andTNMS Core/CDM SysAdmin software on the TNMS Core/CDM Client machine.More information on installing MetaFrame XP is provided in Section 5.4.

5. Internet Explorer 6.0:This must be installed on the NetServer to enable MSN functionality, and on the cli-ent machine. If this is not already pre-installed, it can be downloaded from the Inter-net.

6. TNMS Core/CDM 9.0:This CD contains the following software components for installation:– Integrated TNMS Core/CDM software installation package:

This installation program includes the Server, NetServer, Backup Server, Clientand SysAdmin components. These can be installed either individually or togetheras required.The EML packages for QB3M, ELI, EMOS, Generic SNMP, PDH and UNO arealso available for selection during the TNMS Core/CDM installation. The EMLpackages are installed on the Server, NetServer and Client PC.More information on installing TNMS Core/CDM is provided in Chapter 6.

As well as the TNMS Core/CDM installation, the following 3rd-party softwarecomponents are also included on this CD:– Adobe Acrobat Reader:

The customer documentation for TNMS Core/CDM is provided in *.pdf format.The Adobe Acrobat Reader should be installed on the Server and Client ma-chines so that the documentation files can be opened.

– Microsoft Desktop Engine MSDE 2000 incl. Service Packs 2 and 3:The MSDE is installed on the TNMS Core/CDM Server. More information on in-stalling MSDE is provided in Section 5.1. For larger configurations, however, SQLServer 2000 incl. Service Packs 2 and 3 is recommended. Contact Siemens Tech-nical Sales for further information.

– Microsoft XML parser:The XML parser is installed on the client machine so that the TNMS Core/CDMsystem can support the export and import of network configuration data in XMLformat. More information on installing the XML parser is provided in Section 5.2.

– OSI stack:If QB3 is to be used, OSI stack software must be installed on NetServer PCs be-fore the NetServer software itself. More information on installing the OSI stack isprovided in Section 5.3.

7. MSN:MSN (multi-service node) is an optional EML package which is installed on the Serv-

14 A42022-L5938-H52-1-76D1


er, NetServer and Client machine. It enables individual network elements to begrouped together in a single manageable cluster. More information on installing anMSN is provided in Section 7.6.

8. Waveline:Waveline is an optional EML package which is installed on the Server, NetServerand Client machine if Waveline network elements are to be installed. More informa-tion on installing Waveline is provided in Section 7.5.

9. PLET:PLET is an optional tool used for exporting performance management information.It is installed on the TNMS Core/CDM Server. More information is provided in Sec-tion 7.6.

10. TCOM:TCOM is an optional EML package used for connecting OEM network elementswhich is installed on the TNMS Core/CDM NetServer.More information is provided in Chapter 7.3.

11. TCOA proxy:The TCOA proxy is an optional component which is installed on the Server and Cli-ent PC. It is used to connect TNMS Core/CDM with an umbrella management sys-tem.More information on installing the TCOA proxy is provided in Section 7.2.

12. 3rd-party software for TCOM, TCOA proxy and @P proxy:If the TCOM, TCOA proxy or @P proxy is installed, the following software productsare also required:– Java Runtime Environment 1.3.1_x– IONA Orbix E2A ASP 5.1.2– PrismTech OpenFusion 2.5.11 (TCOA proxy only)More information on installing the 3rd-party software is provided in Section 7.2.1.

13. SNMP proxy:The SNMP proxy is an optional component which is installed on the Server and Cli-entPC. It is used to connect TNMS Core/CDM with an umbrella management sys-tem. The SNMP proxy installation can be seelcted during the TNMS Core/CDMinstallation.

14. RPR Manager:For standardized fiber optic links used in resilient packet rings, the RPR Manager isto be installed. The RPR Manager uses TNMS @P proxy software as platform. The@P proxy is a mandatory component which is installed on the Server and Client PC.For the @P proxy software the following software product is also required:– IONA Orbix E2A ASP 5.1.2More information on installing the RPR Manager is provided in Section 7.7.

15. Hummingbird Exceed:This is used with TNMS Client for the integration of the TNMS SX and EMOS man-agement systems.

Software CD Overview

The software will be delivered on CD-ROMs. Type and content of the necessary CDsdepends on the specific planned and delivered configuration. The operating system willbe delivered as part of the hardware, it is not included within the following table.

Table of the deliverable CD-ROMs:– Exceed 7 Multiplatform 7.1– ULAF+ Library

A42022-L5938-H52-1-76D1 15



– TNMS Core/CDM 9.0 - SW for SNMP Interface– TNMS Core/CDM 9.0 - SW for Waveline Equipment– TNMS Core/CDM 9.0 - Application Software– TNMS Core/CDM 9.0 - TMF CORBA Manager Configuration Files– TNMS Core/CDM 9.0 - OEM Software for TMF CORBA Manager– TNMS Core/CDM 9.0 - TMF CORBA Manager– TNMS Core/CDM 9.0 - TMF CORBA Agent– TNMS Core/CDM 9.0 - OEM Software for TMF CORBA Agent– TNMS Core/CDM 9.0 - RPR Manager/@P– OEM Software Internet Browser

3.3.2 HW/SW ConfigurationFig. 3.1 shows a typical configuration of a TNMS Core/CDM system. Limitations are giv-en below. If other configurations are needed, such as standby server, contact SiemensTechnical Sales for further information.

Fig. 3.1 Typical HW/SW configuration

Limitations for HW/SW configuration– The maximum number of PCs is given in Fig. 3.1.– For small systems the NetServer Components may be installed on the Server PC

also.– The TNMS Core/CDM SysAdmin components may be installed on the Server PC

(recommended) and on the Client PC(s). However, a maximum of 20 SysAdmins areallowed.

– The Client components must be always installed on a separate PC.

Max. 40 Client PCs

Max. 10 NetServer PCs

TNMS Core/CDMClientSysAdmin@P SysAdmin

TNMS Core/CDMClient(SysAdmin)@P SysAdmin

TNMS Core/CDMServer(SysAdmin)@P Server

1 Server PC

TNMS Core/CDMBackup Server

1 Backup Server PC

TNMSCore/CDMNetServer



16 A42022-L5938-H52-1-76D1


Further hints are given within the chapters describing the installation details.

The installation sequence is described within Section 3.3.3. It is urgently recommendedto follow this instructions otherwise problems may occur during installation.

3.3.3 Installation Sequence

The individual stages in the commissioning process must be logged using the formssupplied for the transfer protocol. The transfer protocol documents the completeness ofthe delivery, tests performed and the test results.

Java Runtime Environment

During the software installation, various versions of JRE are installed depending on thecomponents. To avoid interferences keep the following settings in mind:– JRE 1.3.1_3 is to be installed on the Server PCs.– JRE 1.4.0 is to be installed on the Client PCs.– Some components require JRE versions different from the above. However, these

are not to be installed in the default JRE directory.

Installation Sequence

The system should be commissioned as follows:

1. Set up and cable the PCs, as described in Section 3.2.1 above.2. Install the operating system and additional hardware components, and configure the

system under Windows 2000 as described in Chapter 4.3. If QB3 is to be used, install the OSI stack on the NetServer PCs as described in Sec-

tion 5.3.4. Install the MSDE (Microsoft Desktop Engine) on the Server and Backup Server PC,

as described in Section 5.1.5. To enable import and export of XML data, install the XML parser MSXML 4.0 as de-

scribed in Section 5.2.6. If TCOA proxy, RPR Manager or TCOM is to be installed, install 3rd-party software

as described in the associated sections.7. Install the TNMS Core/CDM software components on the corresponding machines

as described in Chapter 6:– TNMS Core/CDM Client– TNMS Core/CDM Server– TNMS Core/CDM NetServer– TNMS Core/CDM Backup Server– TNMS Core/CDM EML Packages– Additional TNMS software, such as PLET or the optional EML packages.

iBefore installing any software component, have a look at the associated readme file.Here you can find the latest informations concerning installation.The displayed screenshots within this manual are examples only and the contents maydiffer depending from the actual situation.

iWhen installing the optional RPR Manager, install TCOA proxy first.

iMDAC (Microsoft Data Access Components) and Java Runtime Environment are in-stalled automatically during the TNMS Core/CDM installation.

A42022-L5938-H52-1-76D1 17



8. If the TNMS SX and EM-OS element managers are to be integrated, install Hum-mingbird Exceed.

9. Configure the TNMS Core/CDM components and connect network elements as de-scribed in Chapter 8.

10. Perform system testing in accordance with the test cases described in the accep-tance test protocol. For more information, contact Siemens Technical Sales.

18 A42022-L5938-H52-1-76D1


4 Installing the Operating System

4.1 Before you BeginBefore you install Windows 2000 operating systems, complete the following steps:– If you wish to pre-install a SCSI RAID system (see Section 3.2.2), make sure the

TNMS Core/CDM Server hard disks are formatted using the NTFS file system.– Check the system requirements.– Determine the licensing mode to be used.– Determine whether multiple operating systems should be offered for activation when

starting the computer.– Determine the file system to be used.– Determine the partition to be used for the installation, or if a new partition is required.– Determine the components to be installed.– Determine how the network, IP addresses and TCP/IP name management are to be

handled.– Determine the domains or workgroups for the servers, if required.– Save all data and files prior to an initial installation of Windows 2000 Server. This

does not apply if there are no files on the computer or the existing operating systemfiles are damaged. You can save the files on disk, on tape or on another computerin your network.

– Decompress all DriveSpace and DoubleSpace data carriers.– Installation may only be carried out on a compressed drive if this drive was com-

pressed with the compression program of the NTFS file system.– Disable all UPS devices.– If the target computer is fed by uninterrupted power supply (UPS), remove the serial

cable before performing the setup. Windows 2000 Setup automatically tries to iden-tify the devices at the serial interfaces. UPS might cause problems here.

Section 4.2 and Section 4.2.3 provide an overview of the installation steps for Windows2000 Server and Windows 2000 Professional. Detailed information is provided in the Mi-crosoft Windows 2000 documentation.

4.1.1 Licensing InformationDuring installation, the system license number is requested. This is provided on the backcover of the Windows 2000 Server/Professional CD.

Windows 2000 Server provides two licensing modes:– per workplace :

Licensing per workplace requires a separate client access license for each comput-er accessing Windows 2000 Server. With a single client access license, a clientcomputer can establish connections to as many Windows 2000 Servers as required.This licensing method should be used if you are running several Windows 2000Servers.

– per server :Licensing per server requires a client access license for every simultaneous connec-tion established to this server. This means that the corresponding Windows 2000Server supports a fixed number of client connections. There are no additional licens-

iThe installation sequence for all software parts is desrcibed in Section 3.3.3. The se-quence is obligatory.

A42022-L5938-H52-1-76D1 19



es required for these computers. Per server licensing should be used if you are run-ning a single Windows 2000 Server.

If you are not sure which mode to use, use per server licensing, as it is possible to switchsubsequently from "per server" to "per workplace" licensing at no extra cost.

If you want to use terminal services both for remote administration and for an applicationserver, use "per workplace" licensing. For the Internet Connector license of the terminalservices, however, use "per server" licensing. More information is provided inSection 5.4.

4.1.2 Protocol InformationTCP/IP is the standard network protocol used by Windows 2000 Server. However, if youwish, you are free to use other protocols and the corresponding network adapters.

For TCP/IP you will need one IP address for every server:– a dynamic address which is assigned by the software automatically, or– or a static address, where the address is fixed.

IP addresses are provided in the form of numbers. You can also assign a name to aserver IP address using what is known as name resolution. This enables user accessvia server names instead of via IP addresses which can be difficult to remember. Themain name resolution methods are:– DNS (Domain Naming Service) :

DNS is a distributed Internet directory service that is used mostly to translate be-tween domain names (server hosts) and IP addresses. It facilitates name resolutionfor clients under Windows 2000.

– DHCP (Dynamic Host Configuration Protocol) :DHCP allows dynamic assignment of IP addresses to network devices. These de-vices are generally servers and workstations, but other devices are also possible,e.g. printers and scanners. DHCP does not require the definition or administrationof static IP addresses, except in the case of Intranet servers which support DHCP,DNS and/or WINS.

– WINS (Windows Internet Naming Service) :WINS facilitates name resolution for clients running Windows NT and older Mi-crosoft operating systems.

4.2 Installing Windows 2000If you are using a Siemens Primergy computer as your TNMS Core/CDM Server, theWindows 2000 Server operating system must be installed using the ServerStart CD.

4.2.1 Installing Windows 2000 Server (If SCSI RAID is Already Configured)If you have already configured a RAID system (see Section 3.2.2) including mirroreddisks and partitions on the TNMS Core/CDM Server machine, proceed as follows:

1. Insert the ServerStart CD into the CD-ROM drive.– Reboot the system.

iUniGATE must not be installed on the same computer as the TNMS Core/CDM Serverand must not be run parallel in the network.

20 A42022-L5938-H52-1-76D1


2. "Server Start" window:"Please insert the ServerStart floppy disk..."– Insert a blank floppy disk into the disk drive.– Select "Create...".

3. "Create ServerStart Floppy Disk" window:– Select "Build ServerStart Floppy Disk".

4. "Server Start" window:"Please select your keyboard."– Select a suitable keyboard layout.

5. "Welcome to Server Start" window:– Select "Operating System Installation".

6. "Operating System Installation" window:– Select "Install MS Windows Operating Systems".

7. "Microsoft Windows Operating System Installation" window.– Select "Install Windows 2000".

8. "Installation of MS Windows 2000" window:– Select "Install Windows 2000 - Guided Mode".

9. "Installation of MS Windows 2000 (Guided Mode)" window:– Insert the floppy disk you created during step 3 into the floppy drive.– Select "Open/Create Configuration File".

10. "Open Server Start Configuration File" window:– Press the "Create" button.A ServerStart configuration file is created.

11. "Installation of MS Windows 2000 (Guided Mode)" window:– Select "System Configuration Wizard".– Select "Server Management Settings".The "SCU-Server Configuration Wizard" is started.

12. "General Server Information" window:– Accept the default settings.– Continue with "Next”.

13. "Chassis Model Configuration" window:– Accept the default settings.– Continue with "Next”.

14. "Pager Settings" window:– Accept the default settings.– Continue with "Next”.

15. "VT 100 Settings" window:– Accept the default settings.

A42022-L5938-H52-1-76D1 21



– Continue with "Next”.

16. "Counters" window:– Accept the default settings.– Continue with "Next”.

17. "Boot and Software Watchdog Settings" window:– Accept the default settings.– Continue with "Next”.

18. "Server Display Settings (Local View)" window:– Complete your configuration with "leave wizard".

19. "Installation of MS Windows 2000 (Guided Mode)" window:– Select "RAID Wizard".

20. "RAID Wz" window:– You are asked whether you want to install on a Mylex controller.– Select "No".The "RaidWz" is started.

21. "Raid Configuration" window:– Select the automatic configuration mode for the configuration of the RAID control-

ler".– Continue with "Next".

22. "RAIDWz" message windows:– A message is displayed: "There exists already a raid-array - you must check the

’Delete existing raid-array box’ or the unattended installation will fail".– Press the "OK" button.The "RAIDWz" message window is closed.– Choose the option "Delete existing RAID Array".– Complete your configuration with "leave wizard".

23. "Installation of MS Windows 2000 (Guided Mode)" window:– Select "Disk Wizard: Hard disk partitioning and formatting".The "Disk Configuration Wizard" is started.

24. "DiskWz" message window:– A message is displayed: "There must be exactly one SYSTEM- and one WINNT-

partition (default: SYSTEM- and WINNT-partition are one and the same).– Press "Ok".

25. "Disk Configuration Wizard - Disk Overview" window:Delete all existing disk partitions as instructed until the entire disk memory is shownas "unpartitioned space". The system partition should be at least 8 GB.The system partition should be at least 8 GB.– Select the first disk from the left list.– Press the "Add" button.– Press the "up" button.

22 A42022-L5938-H52-1-76D1


– Add additional disks, if there are any.The selected disk is added to the list.– Select the option "Erase all existing partitions on all displayed disks."– Complete your configuration with "leave wizard".

26. "Installation of MS Windows 2000 (Guided Mode)" window:– Select "Windows 2000 Installation Wizard".The "Windows 2000 Setup Configuration Wizard" is started.

27. "NT Setup - Windows 2000 Installation" window:– In "Installation Drive" parameters, select the option "Use default".– In "Installation Drive" parameters, select the option "Convert file system to NTFS".– Select a suitable keyboard layout.– Do not enter a "Password for Administrator account".– Enter the product ID provided on the back cover of the Windows 2000 CD.– Continue with "Next”.

28. "NT Setup - Computer Identification" window:– Select the option "Windows 2000 Server".– Select the option "Workgroup".

– Enter the administrator name in "User account to create a computer account".– Select the licensing mode for your organisation i.e. for the clients.Windows 2000 Server provides two licensing modes, "per workplace" and "per serv-er". More information is provided in Section 4.1.1.– Continue with "Next”.

29. "Installation Directory and Time Zone" window:– For the installation directory, select the "Use default" option.– Change the date, time and time zone, if required.– Specify whether changing the time from summer time to winter time and vice ver-

sa is to be performed automatically.– Continue with "Next”.

30. "User Name" window:– Enter your name and (if required) your company.– Enter the computer name. For most languages, a name of max. 15 characters

(don’t use spaces and no special characters) is recommended.– The product ID has already been entered due to your previous settings.– Continue with "Next”.

31. "Display Settings" window:– Accept the default settings.– Continue with "Next”.

32. "Network Protocol" window (information on protocols is provided in Section 4.1.2.)– Select "Install Unattended".

iDepending on your network topology, the server is included either in a workgroup or adomain. A domain identifies a group of accounts and network resources combined un-der a common domain name in a certain security area. You should use domains in allnetworks (except very small networks with only a few users).

A42022-L5938-H52-1-76D1 23



– From the left list "Protocols for this adapter" select the "TCP/IP" network protocol.– Press the "Add" button.The network protocol is added to the list "Selected Protocols for this Adapter".– Enter your settings for the IP address and subnet mask. Also define the standard

gateway, if required.– In the "DNS/WINS Configuration..." option, enter the addresses of the preferred

DNS Server, and (if required) an alternative DNS Server.

– If you want to use a WINS Server, click on "Advanced".– Switch to the WINS tab, and enter the IP address of one or more WINS Servers.– Click on "Add".If the local server is used as WINS Server, enter the previous IP address.– In the dialog boxes click OK, and continue the setup.

33. "SW Components" window:– Click on "Details" and select the desired components.TCP/IP networks normally only need the components DHCP, DNS and WINS. Moreinformation is provided in Section 4.1.2.

– If you select the "Install default components" option, the standard components areconfigured by default.


34. "Services" window:– Select the options "SNMP Service" (if required) and "Simple TCP/IP Services".– Complete your configuration with "leave wizard".

35. "Installation of MS Windows 2000 (Guided Mode)" window:– Select "Application Wizard: Select Additional Software Components".The "Application Wizard" is started.

36. "Application Wizard" window:– Select the options "FSC Server View SNMP Agent" (if required) and "FSC Server

View".– Complete your configuration with "leave wizard".

37. "Installation of MS Windows 2000 (Guided Mode)" window:– Select "Close and Save Configuration File".

38. "Save ServerStart Configuration File" window:

iIf the local server is to be used as preferred or alternative DNS Server, enter the sameIP address as in the preceding step. In this case, it is also possible to configure theWINS Server, if required.

iIf you are not familiar with DHCP or the various options for static IP addresses and thecorresponding subnetwork masks, use APIPA (Automatic Private IP Addressing). Here,the IP addresses are assigned automatically by the setup. After using APIPA you canchange over to configuration with DHCP.

iYou can also add components subsequently using the Windows Control Panel.As every component uses additional disk storage, you should only select the compo-nents you actually need.

24 A42022-L5938-H52-1-76D1


– Insert the ServerStart floppy disk created during step 3.– Press "Save As".Once the ServerStart configuration file is saved, remove the floppy disk.

39. "Installation of MS Windows 2000 (Guided Mode)" window:– Select "Start installation of MS Windows 2000".

40. "ServerStart Unattended Mode" window:The message "unattended Setup running" is displayed.The computer restarts and the Windows 2000 installation program is continued.

41. "ServerStart" message window:– When requested to do so, insert the ServerStart floppy disk created during step

3 into the floppy drive.– Confirm with the "OK" button.

42. "ServerStart Unattended Mode" window:The message "unattended installation running" is displayed.

43. "ServerStart" window:– A message informs you about SCSI controllers on your system.– Confirm with "OK".

44. "ServerStart" window:– A message informs you about network interface cards on your system.– Confirm with "OK".

45. "ServerStart" window:– A message informs you about additional hardware files to be installed on your

system.– Confirm with "OK".

46. "Insert the MS Windows 2000 CD-ROM into the CD-ROM drive." window:– Remove the ServerStart CD from the CD-ROM drive.– Insert the MS Windows 2000 Server CD into the CD-ROM drive.– Confirm with "OK".

47. "Software License Agreement” window:– Read the license agreement.– Accept with the ”I agree” button.

48. "Microsoft Windows 2000 Server Setup" window:The installation files are copied from the disk to the hard disk.

49. "ServerStart" window:– Remove any disks from the floppy and CD-ROM drives.– Continue with "OK".The server restarts and the operating system loads from the hard disk.

50. The following information will now be displayed:– Windows 2000 Server Setup (blue screen).

A42022-L5938-H52-1-76D1 25



– Setup is copying files.The server restarts and the operating system loads from the hard disk. The "Win-dows 2000 Server Setup" window appears and displays the following information:– Installing Devices– Networking Settings– Installing Components– Performing Final TasksThe message "Windows 2000 has been successfully installed" is displayed.The system reboots automatically.

51. "Welcome to Windows" window:– Log in as Administrator.An installation process is automatically launched and the following window will ap-pear: "ServerStart is installing some components (SNMP AGENTS for WindowsNT/2000; FSC ServerView)"The system will reboot automatically.

52. The Windows 2000 Server installation is now complete.

53. Install Windows 2000 Service Pack 4 (see Section 4.2.4).

54. Reactivate RAID hard disk mirroring.

4.2.2 Installing Windows 2000 Server (incl. SCSI RAID Configuration)If you have not yet configured a RAID system with mirrored disks and partitions,(see Section 3.2.2) Windows 2000 Server should be installed as follows:








26 A42022-L5938-H52-1-76D1


8. "Installation of MS Windows 2000" window:– Select "Install Windows 2000 - Expert Mode".

9. "Installation of MS Windows 2000 (Expert Mode)" window:– Select "Configure your Adaptec/DPT RAID System" for the RAID controller instal-

lation.10. "Adaptec Storage Manager - SERVERSTART" window:

– Select "Create Array Group".

11. "Select Array Type" window:– In "Fault Tolerance" options, select "Drive Fault Tolerance".– In "Chosen Array Parameters", select "Override" and "RAID LEVEL 1 Stripe Size:

None".– Confirm with "Accept".– In "Optimization" options, select "Optimize for Performance".– Press "Continue".

– Select both HD icons with the mouse. If either of the HDs has a valid partition ta-ble, the "Adaptec Storage Manager" window appears with a corresponding mes-sage.

– Select "Yes".Both HDs are shown with a green tick.

– Click on "Include Drive". Both HDs must be assigned a RAID DISK icon, i.e. aRAID1 icon must be displayed with a line pointing to each HD.

– Review the configuration and select "Done".– Confirm the following warning messages with "OK".Two black flags appear, one above the LSU icon and another above the RAID1 icon.

– In the menu bar, select File -> Set System Configuration.A warning message appears: "This will change your system configuration. Data onany arrays that you have removed or modified will be lost...".– Press "OK".

12. "Please Choose Direction" window:– Select HBA 0 BUS 0 ID 0 -> HBA 0 BUS 0 ID 1– Press "Start Copy".The black flags turn blue, and a white flag appears on each target SCSI disk.

The "Array Group Information" window appears with a status field informing youabout installation progress.– Wait until formatting has been completed and the array group has been created,

i.e. when the status field shows "optimal".– Exit the "Adaptec Storage Manager".– Reboot the system.

iThis operation can take up to two hours.

A42022-L5938-H52-1-76D1 27








18. "Installation of Windows 2000 (Expert Mode)" window:– Select "Use Disk Administrator to Partition and format your disk drives".

19. "Disk Administrator" window:– Select "Disk 1"– Create a primary partition (maximum size = 8 GB).– Press "Commit changes now".– Format the partition with the parameters unknown capacity, NTFS, default alloca-

tion size, and quick format.– Exit "Disk Administrator".

20. "Installation of Windows 2000 (Expert Mode)" window:– Select "Run Windows 2000 Installation Wizard".

21. "Server Start" window:A message is displayed: "Do you want to specify an existing configuration file to pre-set the parameters for the Operating System Wizard and the Application Wizard?"– Select "No".


23. "NT Setup - Computer Identification" window:– Select the option "Windows 2000 Server".

28 A42022-L5938-H52-1-76D1


– Select the option "Workgroup" or "Domain".




25. "User Name" window:– Enter your name and (if required) your company.– Enter the computer name. For most languages a name of max. 15 characters is

recommended.– The product ID has already been filled in due to your previous settings.– Continue with "Next”.


27. "Network Protocol" window (information on protocols is provided in Section 4.1.2.)– Select "Install Unattended".– From the left list "Protocols for this adapter" select the "TCP/IP" network protocol.– Press the "Add" button.The network protocol is added to the list "Selected Protocols for this Adapter".– Enter your settings for the IP address and subnet mask. Also define the standard


DNS Server, and (optionally) an alternative DNS Server.

– If you want to use a WINS Server, click on "Advanced".– Switch to the WINS tab, and enter the IP address of one or more WINS Servers.– Click on "Add".If the local server is used as WINS Server, enter the previous IP address.



A42022-L5938-H52-1-76D1 29



– In the dialog boxes click OK, and continue the setup.





30. "Installation of MS Windows 2000 (Expert Mode)" window:– Select "Application Wizard: Select Additional Software Components".The "Application Wizard" is started.



32. "Installation of MS Windows 2000 (Expert Mode)" window:– Select "Start installation of MS Windows 2000".








30 A42022-L5938-H52-1-76D1


37. "Insert the MS Windows 2000 CD-ROM into the CD-ROM drive." window:– Remove the ServerStart CD from the CD-ROM drive.– Insert the MS Windows 2000 Server CD into the CD-ROM drive.– Complete your configuration with "OK".




41. This following information will now be displayed:– Windows 2000 Server Setup (blue screen).– Setup is copying files.The server restarts and the operating system loads from the hard disk. The "Win-dows 2000 Server Setup window appears and displays the following information:– Installing Devices– Networking Settings– Installing Components– Performing Final TasksThe message "Windows 2000 has been successfully installed" is displayed.The system reboots automatically.

42. "Welcome to Windows" window:– Log in as Administrator.An installation process is automatically launched and the following window will ap-pear: "ServerStart is installing some components (SNMP AGENTS for WindowsNT/2000; FSC ServerView)".The system will reboot automatically.



4.2.3 Installing Windows 2000 ProfessionalOn the Client and NetServer computers, the operating system Windows 2000 Profes-sional is installed using the Windows 2000 Professional CD. During installation, the sys-tem license number is requested. This is provided on the back cover of the CD.

Proceed the installation as follows:

iIf MetaFrame XP is to be installed on the Client PC, you must install Windows 2000Server operating system. In this case, the Windows components "Terminal Services"and "Terminal Services Licensing" should also be installed.

A42022-L5938-H52-1-76D1 31



1. Insert the Windows 2000 Professional CD into the CD-ROM drive.

2. Reboot the PC from the CD.A blue screen informs you that the Windows 2000 setup has started.

3. "Welcome to Setup" window:– Select "To set up Windows 2000 now press ENTER."– Press Enter.

4. "Windows 2000 Licensing Agreement" window:– Read the license agreement.– Press "F8" to agree.

5. If Windows NT 4.0 or 2000 is already installed, you will be notified.– Choose "Fresh Copy", i.e. new installation.– Press "ESC".

6. If there is no partition on your system, create one:– Choose as size at least 1 GB (recommended whole hard disk, max. 8 GB).

7. Install Windows 2000 on highlighted partition, i.e. system partition "C":– Press "Enter" to confirm.If one partition exists, there will be a warning.– Press "C" to continue.

8. Format the partition using "NTFS file system".

9. Confirm the question about formatting.– Press "F" to format the partition.Now, message windows inform you that the partition is formatted, files are copied tothe installation folders, and setup is initialized.The computer is rebooted automatically.

10. "Welcome to the Windows 2000 Setup Wizard" window:– Continue with "Next".

11. "Windows 2000 Professional Setup" window:Wait until the devices are installed.

12. "Regional Settings" window:– Select the default settings or choose your configuration.– Continue with "Next".

13. "Personalize Your Software" window:– Enter you name and your company.– Continue with "Next".

14. "Your Product Key" window:– Enter the product ID from the back cover of the Windows 2000 CD.– Continue with "Next".

32 A42022-L5938-H52-1-76D1


15. "Computer Name and Administrator Password" window:– Enter the name of your computer (don’t use spaces and no special characters).– Enter a password.– Re-enter the password in the field "confirm password"– Continue with "Next".

16. "Date and Time Settings" window:– Change the date, time and time zone, if required.– Specify whether changing from summer time to winter time automatically.– Continue with "Next".

17. "Networking Settings" window:– Select "Typical Settings".– Continue with "Next".Wait while Windows installs networking components.

18. "Workgroup or Computer Domain" window:– Depending on your network topology, select workgroup or domain. If in doubt, ask

your system administrator.– Continue with "Next".A Setup Status window informs you about the installation progress.

19. "Performing Final Tasks" window:A message window informs you about the final installation operations.

20. "Completing the Windows 2000 Setup Wizard" window:A message is displayed, informing you that Windows 2000 has been successfullyinstalled".– Remove any CDs from your drive.– Confirm with "Finish".The computer is rebooted automatically.

21. "Welcome to Network Identification Wizard" window:– Continue with "Next".

22. "Users of This Computer" window:– Select "Users must enter a username and password to use this computer."– Continue with "Next".

23. "Completing the Network Identification Wizard" window:– Continue with "Finish".

24. "Log On to Windows" window:– Log in as Administrator.The Windows 2000 Professional installation is completed.

25. Install Service Pack 4 for Windows 2000.

A42022-L5938-H52-1-76D1 33



4.2.4 Installing Windows 2000 Service Pack 4

Once the installation is complete, install Service Pack 4 as follows:– Create an Un-Installation directory: No– Accept the license agreement.

4.2.5 Installing Windows 2000 Server Terminal ServicesThe Windows 2000 Server Terminal Services installation is performed the same way asthe standard installation. To facilitate installation, the first partition must have at least 3GB or the hard disk must not be partitioned at all. More information is provided in theMicrosoft Windows 2000 Server Terminal Services documentation.

In order to install Windows 2000 Server Terminal Services, proceed as follows:– Open Start -> Settings -> Control Panel -> Add/Remove Programs -> Add/Remove

Windows Components.– Select "Terminal Services & Terminal Services Licensing".– Select the option "Application Server Mode" (runs for 90 days).– Reboot your computer.

4.3 Hardware Configuration under Windows 2000Once Windows 2000 has been installed, all additional hardware and software compo-nents must be configured/installed under Windows 2000.

This includes:– Graphics cards: Set the font size to "Small Fonts": Start -> Settings -> Control Panel:

Double click on "Display", the "Display Properties Window" opens; press button "Ad-vanced" choose tab "Common" and set the value "Display/Font Size" to "SmallFonts". Restart the computer if necessary.

– Printers– Modems (remote login)– UPS

Installation should be completed in accordance with the relevant installation instructions.

4.3.1 Installing the PCI I/O CardThe PCI I/O card is installed on the TNMS Core/CDM Client PC and enables externalsignaling.

– Switch off the PC and disconnect it from the power supply.– Open the PC.– Insert the PCI I/O card into a free slot.– Close the PC.– Switch on the PC.

iIf required, decompress the Service Pack to a temporary folder.

iIf the Windows 2000 configuration (e.g. the printer configuration) is modified, ServicePack 4 must be installed again.

iBefore opening the antistatic envelope, make sure you are familiar with the regulationsfor electrostatic-sensitive devices (ESD) provided in Chapter 2.

34 A42022-L5938-H52-1-76D1


– Install suitable drivers by double-clicking the Setup.exe file on the floppy disk sup-plied.

– Start the TNMS Core/CDM Client after installing the drivers.

More information is provided in the I/O card documentation.

A42022-L5938-H52-1-76D1 35



5 Prerequisites and 3rd-Party Software

This chapter gives installation descriptions for the necessary software to be installed pri-or to TNMS Core/CDM and its additional components.

3rd-party software is delivered on a separate CD-ROMs (for the order number see therelease document).

5.1 Installing MSDEMSDE SP3 (Microsoft SQL Desktop Engine) must be installed directly on the Server PC.To install MSDE, double-click the "setup.bat” file in the MSDE directory on the TNMSCore/CDM 9.0 software CD.

The program installs MSDE on the computer. No additional input is required.

Reboot your computer to complete the installation.

Uninstalling MSDE

In order to uninstall the MSDE, open Start -> Settings -> Control Panel -> Add/RemovePrograms:– Select the MSDE from the software list.– Click the "Change/Remove” button.– Select the "Remove” option.– Confirm the uninstall process with "Finish” and restart your computer.

5.2 Installing MSXML 4.0MSXML 4.0 is an XML parser. It must be installed on the system so that network config-uration data can be imported and exported in XML format.

As a prerequisite, the Windows Installer 2.0 has to be installed. To do this, double-clickthe "InstMsiW.exe” file in the MSI2.0 directory on the TNMS Core/CDM 9.0 software CDand follow the instructions. After installation, reboot the PC.

To install MSXML 4.0, proceed as follows:

1. Reboot the PC (if not already done, see above).

2. Double-click the "msxml4.msi” file in the MSXML directory on the TNMS Core/CDM9.0 software CD.

3. A welcome window is now displayed. Press "Next” to continue.

4. In the "End-User License Agreement” window, accept the terms of the licenseagreement, and press "Next” to continue.

5. In the "Customer Information” window, enter a user name and the name of your com-pany in the appropriate fields. Press "Next” to continue.

6. In the ”Choose Setup Type” window, press "Install Now”.

iThe installation sequence for all software parts is described in Section 3.3.3. The se-quence is obligatory.

36 A42022-L5938-H52-1-76D1


7. The window "Installing Microsoft XML Parser and SDK” window is now displayed.The progress of the installation is indicated by the progress bar.

8. Once the installation is complete, the window "Completing the Microsoft XML Parserand SDK Setup Wizard” is displayed. Press "Finish” to complete the installation.

Uninstalling MSXML

In order to uninstall the MSXML, open Start -> Settings -> Control Panel -> Add/RemovePrograms:– Select the MSXML from the software list.– Click the "Change/Remove” button.– Select the "Remove” option.– Confirm the uninstall process with "Finish” and restart your computer.

5.3 Installing an OSI StackIf QB3 is used, an OSI stack must be installed on the NetServer PCs before the Net-Server software.

To install an OSI stack, proceed as follows:

1. To install an OSI stack, double-click the file "setup.exe” in the OsiStack directory onthe TNMS Core/CDM 9.0 software CD.


3. In the "Choose Destination Location" window which is now displayed, a default in-stallation directory is offered for the OSI stack. Press "Next” to continue.

4. In the "Please select:" window, select the NSAP address option best suited to yourcompany’s network and press "Next”.

5. In the "Getting NSAP" window, enter the local NSAP address and press "Next”.

6. In the "Start Copying Files" ensure that the settings displayed are correct, and if so,press "Next” to continue.

7. A setup status window is now displayed, showing the progress of the OSI stack in-stallation.

8. In the ”InstallShield Wizard Complete” window select the option for restarting thecomputer and press “Finish” to complete the OSI stack installation.

Once the computer has rebooted, open the OSI stack via Start -> Settings -> ControlPanel -> OSI Stack.You can now check the OSI stack settings as follows:– Note the settings of the ES-IS and IS-IS parameters (the IS-IS parameters can be

displayed by pressing Ctrl + I).– Set the value for "Number of Channels and Ctx” to greater than/equal to 140. This

is the number of OSI stack connections which can be established simultaneously.The recommended value is 500.

A42022-L5938-H52-1-76D1 37



– Note the network interface card to which the OSI is connected and check this againstthe LAN card settings in the Control Panel.

– Activate the options "Open Stack, when Operator starts” and "Start stack as ser-vice".

Uninstalling OSI stack

In order to uninstall the OSI stack, open Start -> Settings -> Control Panel -> Add/Re-move Programs:– Select the OSI stack from the software list.– Click the "Change/Remove” button.– Select the "Remove” option.– Confirm the uninstall process with "Finish” and restart your computer.

5.4 Installing Citrix MetaFrameMetaFrame XP is used to enable remote access to specific software applications on anetworked computer.In this case, MetaFrame XP is used to provide remote access to the TNMS Client andTNMS SysAdmin software on the TNMS Client machine.MetaFrame XP comprises server software (on the Server CD) and ICA Client software(on the Component CD). The server software is installed on the TNMS Client machineand the ICA Client software on the remote PC.The TNMS Client machine is therefore considered a "MetaFrame Server", and the re-mote PC is considered a "MetaFrame Client".

In other words you must install the MetaFrame Server first, then enter the correspondinglicenses, and then publish the required applications. Only when these steps have beencompleted can you install the MetaFrame Client and configure the ICA Client connec-tion.

5.4.1 System RequirementsThe MetaFrame Server (TNMS Client machine) must meet the following requirements:– 400 MB disk space for MetaFrame XP– 50 MB disk space for the Citrix Management Console– Windows 2000 Server + Service Pack 4– The Windows components "Terminal Services" and "Terminal Services Licensing"

must be installed in Application Server mode. Permissions must be compatible withTerminal Server 4.0 users.

– The Windows 2000 Server component "Internet Information Services" should not beinstalled.

– Windows Installer Version 2.0 must be installed (do not use the Windows Installer1.1 which is included with Windows 2000 Server).

The MetaFrame Client PC can be any PC in the network, however, it must meet the fol-lowing requirement:– 250 MB disk space for ICA Client software.

iWhen installing the MetaFrame XP software, you must follow the installation sequencedescribed below.

iWhen you insert the Server CD (see instructions below), you can obtain more informa-tion by clicking "View installation checklist".

38 A42022-L5938-H52-1-76D1



As MetaFrame is to be installed prior to TNMS Core/CDM, two JRE versions are in-stalled on the Client PCs:– JRE 1.4.1 for MetaFrame– JRE 1.4.0 for TNMS Core/CDM

5.4.2 Installing the MetaFrame ServerBefore you begin:– Check which Windows Installer version is installed using the command "msiexec" in

the DOS command prompt window. Windows Installer Version 2.0 is included on theMetaFrame XP Server CD (folder support\MSI20; for installing click “InstMsiW.exe).

– Ensure you are logged in with administrator rights.

Once you have completed the steps above, proceed as follows to install MetaFrame XP:

1. At the TNMS Client machine, insert the MetaFrame XP Server CD.

2. In the window which appears, select "Install or update MetaFrame XP Server".

3. In the window which appears, select "MetaFrame XP Feature Release 3".

4. In the window "Welcome to the Citrix MetaFrame XP Server for Windows with Fea-ture Release 3 Installation Wizard", press "Next".

5. In the "License Agreement" window, select "I accept the license agreement" andpress "Next".

6. In the "Product Family Selection" window, select "MetaFrame XPs" and press "Next".

7. In the "Select Product Type" window, select "Retail" and press "Next".

8. In the "Component Selection" window, select MetaFrame XP + Management Con-sole. Accept the default directory (C:\Program Files\Citrix\) by pressing "Next".

9. In the "Create or Join a Server Farm" window, select "Create a new farm" and press"Next".

10. In the "Create a Server Farm" window, enter an appropriate "Farm Name", select"Use a local database (Microsoft Access) on this server" and "Use Default ZoneName", and press "Next".

11. In the "Assign Farm Administrator Credentials" window, enter an appropriate "UserName" (e.g. TNMS) and "Domain" description for the local domain of the MetaFrameserver host (e.g. PC170). Press "Next".

12. In the "Configure shadowing" window, select "Prohibit shadowing of ICA sessions onthis server" and press "Next".

!Do not install Citrix MetaFrame after TNMS Core/CDM! The Java application will be re-placed and TNMS Core/CDM will be inoperable.

A42022-L5938-H52-1-76D1 39



13. In the "Configure Citrix XML Service Port" window, enter the default value "80" andpress "Next".

14. In the window "Review your selections listed below", ensure that the data shown iscorrect, and press "Finish" to complete this section of the installation.In the windows which follow, the progress of the installation is indicated by progressbars.

15. When installation has been completed, the window "Citrix MetaFrame XP Server forWindows with Feature Release 3 has been successfully installed" is displayed.Ensure the options "Launching the ICA Client Distribution wizard" and "View the Re-adme file" are not selected and close this window by pressing "Close".

16. A command prompt appears asking whether you wish to restart the computer -press "Yes".

Entering Licenses For MetaFrame

Once the MetaFrame Server (TNMS Client machine) has been restarted, you can enterlicensing information as follows:

1. Go to the ICA Administrator toolbar which is now visible on the screen, and pressthe button for the Citrix Management Console (this is the last button in the toolbar).

2. In the "Pass-through Authentication" window, select "Enable pass-through authenti-cation" and "Connect to this server" and press "OK".

3. The Citrix Management Console is now shown for the MetaFrame Server farm youhave just configured. In the tree view to the left of the console, right-click "Licenses"and select the option "Add License..." from the context menu which appears.

4. In the "Add License" dialog, enter the serial number of the server license and press"OK".

5. In the success window you will be asked whether you wish to activate the license atthis time - press “No”.

6. In the tree view, right-click the "Licenses" option again, select "Add License...", andin the "Add License" dialog, enter the license number for the ICA Client connection.

7. In the success window you will be asked whether you wish to activate the license atthis time - press “No”.You have a grace period of 35 days before the both licenses must be activated.

More information on activating licenses is contained in the instruction booklet providedwith the MetaFrame CDs.

Publishing Applications

As precondition, TNMS Core Client and/or TNMS SysAdmin must be installed. The ap-plications which the remote MetaFrame Client PC is permitted to access (e.g. TNMS Cli-ent or TNMS SysAdmin) can be specified on the MetaFrame Server as follows:

40 A42022-L5938-H52-1-76D1


1. In the Citrix Management Console, go to the main menu bar and select "Actions" ->"New" -> "Published Application".

2. In the window "Welcome to the Application Publishing Wizard", enter a "DisplayName" for the selected application (e.g. TNMS Client) together with an "ApplicationDescription" and press "Next".

3. In the "Specify What to Publish" window, select "Application". Specify the "Com-mand Line" by browsing to the installation directory for the relevant application andselecting the *.exe file for the application e.g. C:\Program Files\Sie-mens\TNMS\Bin\tnClient.EXE. You can also specify a "Working Directory" e.g.C:\Program Files\Siemens\TNMS\Bin. Press "Next" continue.

4. In the "Program Neighborhood Settings" window, enter a "Program NeighborhoodFolder" e.g. TNMS, and without activating either of the shortcut options, press"Next".

5. In the "Specify Application Appearance" window, set the "Session Window Size" to1024x768, and set the "Colors" to "True Color (24 bit)". Select "Maximize applicationat startup" and press "Next".

6. In the "Specify ICA Client Requirements" window, select "Enable Audio", set "En-cryption" to "Basic" and press "Next".

7. In the "Specify Servers" window, select the name of the MetaFrame Server comput-er from the "Available Servers" list. Press "Add" to add this server to the "ConfiguredServers" list, and press "Next" to continue.

8. In the "Specify Users" window, select the server name from the "Look in" field, selectthe "Show users" option, and select the appropriate user from the list provided. Thisuser will be the user entered during the MetaFrame server installation, e.g. TNMS.Once you have selected the user, press "Add" to add this user to the "ConfiguredAccounts". Press "Finish" to complete publishing for this application.

9. In the Citrix Management Console, you can now see the published application in thetree view under "Applications".

5.4.3 Installing MetaFrame ClientThe MetaFrame Client PC can be any PC in the network. It can be configured as follows:

1. At the selected PC, insert the Citrix MetaFrame XP "Components" CD.

2. In the "Citrix MetaFrame XP Components" window, select "Citrix ICA Clients".

3. In the "Citrix ICA Clients" window, select "Citrix Program Neighborhood".

4. In the window "Welcome to the Citrix ICA Client Installation Wizard", press "Next".

A42022-L5938-H52-1-76D1 41




6. In the "Destination Folder" window, accept the default directory (C:\ProgramFiles\Citrix\ICA Client\) by pressing "Next.

7. In the "Select Program Folder" window, enter "Citrix ICA Client" and press "Next".

8. In the "ICA Client Name" window, enter a name for the client PC, e.g. pc109, andpress "Next".

9. In the "Select Desired Features" window, select "No" and press "Next".

10. In the window "Ready to Install the Application", press "Next" to begin installation. Aprogress bar is now shown indicating the progress of the installation.

11. In the window "Citrix ICA Client has been successfully installed" click "Finish" tocomplete the installation.

Configuring the ICA Client Connection

Once the MetaFrame Client has been installed, access to applications published on theMetaFrame Server can be configured as follows:

1. Double-click the "Citrix Program Neighborhood" icon which is now provided on thedesktop of the MetaFrame Client PC.

2. In the Citrix Program Neighborhood, double-click “Application Set Manager”.

3. In the Citrix Program Neighborhood, double-click “Find new Application Set”.

4. In the “Find New Application Set” window, select “Local Area Network” and press“Next”.

5. In the window which appears, enter a description for the new application set and se-lect the server where the application is installed from the dropdown list “Click belowto locate the Application Set to add”. Use the “Server Location...” button to add yourMeataFrame server’s IP address or hostname to the Address List. Press “Next” tocontinue.

6. In the window which appears select “Use Server Default” for the “Window Colors”.for the “Window Size” select “Seamless Window”. Press “Next” to continue.

7. Press “Finish” to complete the connection configuration.

8. Now a new icon is created in the Citrix Program Neigborhood.

9. Double-click this new icon. A Login window is opened. Enter the user name for theMetaFrame Server as specified during Metaframe Server installation (e.g. TNMS)

42 A42022-L5938-H52-1-76D1


and enter the MetaFrame Server domain as specified during MetaFrame installation(e.g. pc170). Finally specify a password and press “OK”.

10. In the Citrix Program Neighborhood, a folder is now displayed for the published ap-plication, e.g. TNMS.

To open the application, proceed as follows:– Double-click the folder to access the program icon. Double-click the program icon,

confirm any messages with "OK". The published software application is now avail-able for use.

This file describes the most important steps in installing MetaFrame XP. Should you re-quire more detailed information, product-specific documentation is provided on theMetaFrame Server CD in the directory "\DOCS".

iThe Administrator’s Guide to Citrix MetaFrame XP (MetaFrame_XP_Guide.pdf) is par-ticularly useful.

A42022-L5938-H52-1-76D1 43



6 Installing the TNMS Core/CDM Software

6.1 Before You BeginBefore installing TNMS Core/CDM, note the following information:– Before installing the software, all previous versions must be uninstalled.– The integrated TNMS Core/CDM 9.0 software installation consists of the Server,

NetServer, Backup Server, Client, SysAdmin and EML components.– The Server and NetServer components may be installed on the same (medium con-

figuration) or on separate PCs (large configuration).– The Client software has to be installed on a separate PC.– The SysAdmin software can be installed on any PC in addition to any other TNMS

Core/CDM component.– The EML packages are installed on the Server, NetServer and Client PC.– To support distributed operation of the network, up to 40 TNMS Core/CDM Clients

can be managed simultaneously.– Depending on the number of the network elements, up to 10 NetServer PCs can be

managed simultaneously.– The Server must be installed on the server PC. Depending on the security concept,

the SysAdmin software can also be installed on the Server PC with an additionalmonitor where possible. This enables administration of the TNMS Core/CDM sys-tem to continue uninterrupted, even if the data flow between the Client and ServerPC is disrupted.

– If TCOA proxy, TCOM or RPR Manager is to be installed, the relevant 3rd-party soft-ware must also be installed on the Server PC.

– If one or more PCs in the TNMS Core/CDM system are equipped with two networkadapters, routing settings must be configured as specified in Section 8.3 to avoid de-lays during connection setup between PCs.

– To avoid problems during the TNMS Core/CDM installation, the user must be loggedinto the Windows 2000 operating system with administrator rights.

6.2 Installing TNMS Core/CDMTo install TNMS Core/CDM, proceed as follows:

1. Double-click the file "setup.exe” provided on the TNMS Core/CDM software CD. Awelcome window appear, press “Next” to continue.

2. In the "License Agreement" window, read the agreement and accept it by pressing"Yes".


iThe installation sequence for all software parts is described in Section 3.3.3. This se-quence is obligatory.Installation of service packages and upgrade packages is not part of the IMN, these aredescribed in the appropriate release notes delivered with each package.

44 A42022-L5938-H52-1-76D1


4. In the "Choose Destination Location” window, a default installation directory is of-fered. Click the “Browse” button to choose another directory and press "Next” to con-tinue.

5. In the "Select TNMS Core Components" window, select the components you wishto install. In this window, you can install the Server, NetServer, BackupServer, Client,and SysAdmin components either together or individually as required (see Section6.1 for details).

Fig. 6.1 Select TNMS Core Components Window

6. In case of Server installation, now the TNMS basic license key must be installed.

Fig. 6.2 Install TNMS Basic License Key

iSteps 6.and 7. will only be performed when installing the Server. If you did not chooseto install this component, continue with step 8.

A42022-L5938-H52-1-76D1 45



7. In the "Location of Server Database Files", a default installation directory is offered.Click the “Browse” button to choose another directory and press "Next” to continue.

8. In the "Location of Database Backup Files", a default installation directory is offered.Click the “Browse” button to choose another directory and press "Next” to continue.

9. In the "Select Program Folder” window, a default program folder is offered. Press"Next” to continue. The system now registers additional installation packages.

10. In the "Select the required EML packages" window you can select the required EMLcomponents for installation. Press “Next” to continue.

Fig. 6.3 Select the Required EML Packages Window

11. In the "Select the required interface packages" window you can select the requiredinterface packages for installation: SNMP Proxy, TCOA Proxy G7 and/or TCOA

iStep 8. will only be performed when installing the Backup Server. If you did not chooseto install one of this component, please continue with step 9.

46 A42022-L5938-H52-1-76D1


Proxy TMF. Then press “Next” to continue. Note that TCOA Proxy G7 and TCOAProxy TMF cannot be installed together; only one of them can be installed.

Fig. 6.4 Select the Required Interface Packages Window

12. The “Start Copying Files” window shows all software components to be installed.Press “Next” to continue.

13. JRE is required only by some LCTs. You will only be asked whether to install JRE incase such a LCT was selected.– Install JRE and do not deinstall any other version.During the JRE installation you will be asked to specify the used browser. Select “Mi-crosoft Internet Explorer”.

14. The "Setup Status” window which is now displayed indicates the progress of the in-stallation. Various system messages are also output during this part of the installa-tion, for example indicating that LCTs are being installed.This part of the installation could take some time.

15. Once all system components are installed, the "InstallShield Wizard Complete" win-dow is displayed. Select the option for restarting the computer, and press "Finish” tocomplete the installation.

The computer is rebooted and the installation completed.

Subsequent configuration settings are described in Chapter 8.

6.2.1 Deinstalling TNMS Core/CDMThe TNMS Core/CDM software can be deinstalled using the Windows 2000 control pan-el. The following information is removed during deinstallation:– All information used by the TNMS Core/CDM application from the Windows 2000

Registry.

A42022-L5938-H52-1-76D1 47



– All program files of the TNMS Core/CDM components.– All empty TNMS Core/CDM component directories.– The TNMS Core/CDM database.

Shared files such as OLE-Dlls are not removed.

Before uninstalling TNMS Core/CDM software, complete the following steps:

1. Create a backup of the current TNMS Core/CDM database. Do not use the defaultbackup path as the installation folder will be removed during the uninstall procedureif not explicitly prohibited by the operator.

2. Store the local NSAP address of the Server in a text file.

3. Close all element managers which are open.

4. Close any TNMS Client sessions which are open.

5. Log off the TNMS SysAdmin software from the server, and exit SysAdmin.

6. Stop all TNMS services on the Server and NetServer underStart -> Settings -> Control Panel -> Administrative Tools -> Services.The following services are possible:TNMS Backup Server, TNMS Data Provider, TNMS NetServer, TNMS Telecommu-nication Network Management System.You should also check the Windows Task Manager for running services and endthese processes where possible.

The software can now be deinstalled as follows:

1. Open the "Add/Remove Programs" window via Start -> Settings -> Control Panel->Add/Remove Programs.

2. Select TNMS Core V... and press “Change/Remove”

3. The preconditions for deinstalling are checked and a welcome window is displayed.Select "Remove” and press "Next” to continue.

4. In the "Confirm File Deletion” window, press OK to activate deinstallation. The dein-stallation starts and information windows displays the software parts, which are cur-rently deinstalled. This will take some minutes.

5. Depending on the programs that have been installed you may be prompted to con-firm the deletion of further files.

6. You will also be asked whether you wish to delete the directory containing your back-up files:– If you have stored the backup files in the default directory, i.e.

"C:\Program Files\Siemens\TNMS\data\Archive”, do not delete the directory.– If you have stored the backup files in a different directory, you may delete the de-

fault directory.

48 A42022-L5938-H52-1-76D1


7. The "Maintenance Complete” window is now displayed. If certain folders could notbe deleted, this is indicated here. Press "Finish" to complete the deinstallation pro-cess.

8. Restart the PC.

9. Delete any remaining folders manually in the Windows Explorer e.g.C:\Program files\Siemens\TNMS\Data, C:\Program files\Siemens\TNMS, C:\Pro-gram files\Siemens.

10. Check that the TNMS services listed above are removed from the services list.

6.2.2 Adding and removing individual TNMS Core/CDM ComponentsIf individual TNMS Core/CDM components (e.g. specific EML packages) are to be in-stalled or removed, proceed as follows:

1. Insert the installation CD-ROM into the CD-ROM drive.

2. Logoff and exit all client machines.

3. Stop the Server using SysAdmin.

4. Logoff and exit SysAdmin.

5. If necessary, close all other active applications.


7. Start the installation/deinstallation procedure via Start -> Settings -> Control Panel-> Add/Remove Programs. Select "TNMS" and click the "Change/Remove" button.

8. In the "Welcome” window, select the "Modify".

9. In the Select TNMS Core/CDM components" window, the components already in-stalled are displayed. Select the components you wish to install or uninstall andpress "Next” to continue.

10. In the "Select the required EML packages” window, select the components you wishto install or deinstall, and press "Next” to continue.

iIf the QB3M service is running while the OSI stack service is being closed down, youare also asked to close the QB3M service.

A42022-L5938-H52-1-76D1 49



11. The "Setup Status” window which is now displayed indicates the progress of the pro-cedure.

12. Once the selected components are installed or deinstalled, the "Maintenance Com-plete" window is displayed. Press "Finish” to complete the process.

13. Restart the PC to update your installation.

50 A42022-L5938-H52-1-76D1


A42022-L5938-H52-1-76D1 51



7 Installing Additional TNMS Core/CDM Soft-ware

7.1 Installation Matrix for TNMS @P and TCOA Proxy SoftwareThe following cases should be distinguished for installation of TNMS @P and TCOAproxy:

a) Customer wants to install TNMS @P based software but no TCOA proxy --> installORB9.0_DS.

b) Customer wants to install TNMS @P based software and/orTCOA proxy --> installTCOA9.0_DS.

c) Customer has already installed TNMS @P based software and wants to add TCOAproxy: Stop all applications, uninstall ORB9.0_DS and install TCOA9.0_DS.

7.2 Installing TCOA Proxy and SNMP ProxyThe TCOA proxy and the SNMP proxy are optional components which are installed onthe TNMS Core/CDM Server and on SysAdmin. Both proxies is used to connect TNMSCore/CDM with an umbrella management system.

The installation process for the proxies consists of the following parts:– "6.2 Installing TNMS Core/CDM" (contains TCOA Proxy and SNMP proxy installa-

tion)– "7.2.1 3rd-Party Software for TCOA Proxy and RPR Manager"

7.2.1 3rd-Party Software for TCOA Proxy and RPR Manager

Prerequisites for TCOA and RPR Manager 3rd-Party Software

To install the TCOA proxy, the following 3rd-party software is required:– Java Runtime Environment– IONA Orbix E2A ASP– PrismTech OpenFusion

For the exact software version see section 3.3.1.

If a TCOA proxy is to be installed and GUI Cut Through is used, a separate PC andMetaFrame is necessary. More information is provided in Section 5.4.


iIn order to use TCOA Proxy, an appropriate TNMS license key has to be installed.

iOn a Server PC with TCOA Proxy the third party product “OpenFusion” (installed byTCOA9.0_DS) requires “JRE 1.3.1” to be active during Setup.If under the registry key “SOFTWARE\JavaSoft\Java Runtime Environment” the valuefor “CurrentVersions” is set and the value is different from “1.3”, please reset it to “1.3”before installing TCOA9.0_DS (e.g. on a TNMS one-server-configuration where TNMSis installed before TCOA9.0_DS). After the installation of TCOA9.0_DS it may bechanged back to its original version.

52 A42022-L5938-H52-1-76D1


If multiple LAN cards are configured on a system with TCOA proxy the following instruc-tions should be completed before the installation of the TCOA Deployment Software:– Open "Start" -> "Settings" -> "Network and Dial-up Connections".– Select from the menu bar "Advanced" -> "Advanced Settings...".– Select the "Adapters and Bindings" pane.– In the "Connections" window identify the LAN connection that is used for the com-

munication between TCOA and NMS. If this connection is not at the first position inthe list, select this connection and use the arrows at the right side of this window toset this LAN connection to the first position in the list.

Installation Overview for TCOA and RPR Manager 3rd-Party Software

The "TCOA9.0_DS" CD contains the 3rd-party software in the directory "Product_CDs"and the "main setup" in the root directory of the CD. This launches and controls setupof the 3rd-party software. The "main setup" also configures the 3rd-party software afterinstallation to operate together with TNMS Core/CDM.

The MetaFrame software must be installed separately as described in Section 5.4.

Installing TCOA and RPR Manager 3rd-Party Software

The software must be installed on the TNMS Core/CDM Server machine.

1. Insert the TCOA9.0_DS CD in the CD-ROM drive.

2. Open the Windows Explorer.

3. Navigate to the root directory of the CD folder and run the "Setup.exe”.

4. Proceed as described in the setup windows:"Welcome" window:-> Confirm with "Next".

5. "License Agreement" window:-> Accept the license agreement with "Yes".

6. "TCOA Installation Guide" window:-> Print out the recommended "Readme.txt" to get the necessary information on the3rd party software.-> Confirm with "Next".

7. "Customer Information" window:-> Enter a user name (alphanumeric characters), a company name (alphanumericcharacters) and the serial number.-> Confirm with "Next".

!If you use more than one LAN card you have to complete the previous instruction for acorrectly working system. Otherwise it may be that the NMS does not receive any noti-fication emitted by the TCOA via Notification Service.

A42022-L5938-H52-1-76D1 53



8. "Choose Destination Location" window:-> Use the default installation directory for the TCOA software or click the "Browse"button, if you want to change the installation directory.-> Confirm with "Next".

9. "Choose Destination Location" window:-> Use the default installation directory for the TCOA 3rd party software, or click the"Browse" button, if you want to change the installation directory.-> Confirm with "Next".

10. A "Setup Status" window will be displayed. The installation and configuration of theJava 2 Runtime Environment are performed automatically.

11. Execute the Orbix E2A ASP setup as follows:"Installation Guide for native Orbix E2A ASP Setup” window:-> A message indicates that the Notepad file "ReadMe_Orbix2000_Setup.txt" is go-ing to be displayed. This file describes the entries necessary for the Orbix E2A ASPsetup.-> Confirm with "Ok".

12. "Orbix E2A ASP 5.1 Introduction" window:-> Confirm with "Next".

13. "License Agreement" window:-> Read the license agreement.-> Select the option "I accept the terms of the License Agreement".-> Confirm with "Next".

14. "Choose Application Server Platform Install Folder" window:-> Use the default installation directory (C:\Program files\IONA) for the Orbix E2AASP files, or click the "Choose..." button, if you want to change the installation direc-tory.-> If you want to reset your chosen directory to the default directory, click the "Re-store Default Folder" button.-> Confirm with "Next".

15. "Choose Shortcut Location" window:-> Select the desired option for the Orbix E2A ASP program group.-> If your computer is used by different users, you may also select the "Create Iconsfor all Users" option.-> Confirm with "Next".

16. "Choose Product Edition" window:-> Choose the "Standard Edition" option to get a complete installation.-> Confirm with "Next".

17. "Choose Environment" window:-> Select "Runtime Only".-> Confirm with "Next".

54 A42022-L5938-H52-1-76D1


18. "Choose Java Virtual Machine" window:-> Select "... \JavaSoft\JRE\1.3.1\bin\java.exe" located in the destination location ofthe 3rd party software (default “C:\Program Files”).-> Confirm with "Next".

19. "JDK Tools Location" window:-> Select "... \JavaSoft\JRE\1.3.1\lib\tools.jar" located in the destination location ofthe 3rd party software (default “C:\Program Files”).-> Confirm with "Next".

20. "Set Environment Variables?" window:-> Select the default radio button “Set the variables for all Users”.-> Confirm with "Next".

21. "Pre-Installation Summary" window:-> Push the "Install" button to proceed.

22. Now the Orbix Setup will transfer the files. Then a web browser window with someOrbix documentation is shown, close this window.Finally additional user input is required.

23. "Installation Complete" window:-> Push the "Done" button to proceed.

Then an information window announces to open a “Notepad” with the file“ReadMe_Orbix_E2A_ASP_ORB_Configure.txt”. This text describes the manual inputnecessary for the native Orbix E2A ASP configuration tool. Confirm with "Ok" and exe-cute the configuration as described:

1. "Orbix E2A Configuration" window:-> Confirm with "Next".

2. "Licensing" window:Select the radio button “Use installed license file” and use the default location(C:\Program files\IONA\etc\licenses.txt)-> Confirm with "Next".

3. "Choose a configuration option" window:Select the radio button “Create a configuration domain”-> Confirm with "Next".

4. "Configuration domain" window:Use the default domain name “orbix E2A”.Select the feature “Orbix E2A Services” (default).Deselect the feature “Orbix E2A Application Server” (default)Deselect “Include configuration for demo applications”.-> Confirm with "Next".

A42022-L5938-H52-1-76D1 55



5. "Choose configuration domain type" window:Select “Local File” (default)-> Confirm with "Next".

6. "Set host properties" window:Use the default settings (your host name) for the unqualified host name and for thehost DNS alias.Use the default path “C:\Program files\IONA\etc” to store the configuration files andthe default path “C:\Program files\IONA\var” to store the service databases.-> Confirm with "Next".

7. "Information" window:If the 'var' subdirectory does not exist, agree to create the directory.-> Confirm with "Yes".

8. "Location Service" window:Select “Yes” (default) to deploy a location service.-> Confirm with "Next".

9. "Setup Infrastructure services" window:Select the (default) port 3075 for the locator daemon.Select the (default) port 3079 for the node daemon.-> Confirm with "Next".

10. "Orbix E2A Services" 1st window:Select “Naming Service” (default).Deselect “Management Service” (default).-> Confirm with "Next".

11. "Orbix E2A Services" 2nd window:Deselect “Event Service” (default).Deselect “Interface Repository” (default).-> Confirm with "Next".

12. "Orbix E2A Services" 3rd window:Deselect “JMS” (default).-> Confirm with "Next".

13. "Configure service settings" window:Select “Start services on system boot.-> Push the "Finish" button to proceed.

14. "Summary of your configuration" window:-> Push the "Deploy" button to proceed.Now the native Orbix Setup will deploy the configuration.

15. “Congratulations! Your conf. successfully deployed.”:-> Push the “Close” button to proceed.

The Orbix Configuration is complete now, close the Notepad window.

56 A42022-L5938-H52-1-76D1


Then the installation of OpenFusion Notification Service is done automatically.

An additional service "OcaNotificationCleaner" is installed to remove undelivered notifi-cations on system reboot.

Last the 'InstallShield Wizard Complete' window prompts you to restart your computer.

Accept the default "Yes, I want to restart my computer now" by <Finish> to reboot yourPC immediately.

After reboot ensure the Orbix services are started by Task Bar -> Start -> Settings ->Control Panel -> Administrative Tools -> Services.

The 3 Orbix services– IT iona_services.locator.<host name> orbixE2A– IT iona_services.naming.<host name> orbixE2A and– IT iona_services.node_daemon.<host name> orbixE2A

must exist and must have the status “Started”.

Ensure the OpenFusion services are started by Task Bar -> Start -> Settings -> ControlPanel -> Administrative Tools -> Services.

The OpenFusion service “OpenFusion” must exist and must have the status “Started”.

The TCOA service “OcaNotificationCleaner” must exist and must have the status “Start-ed”.

Deinstalling TCOA and RPR Manager 3rd-Party Software– In the taskbar select: Start -> Settings -> Control Panel.– Double-click "Add/Remove programs".– From the list, select: "TCOA_DS”.– Press the button: Add/Remove.

The "InstallShield Wizard” is displayed.– Select "Remove”.– Click "Next”.– Confirm in the next window.

For deinstallation, several windows are opened one after the other. These must be con-firmed as described in the setup windows.

After finishing the "InstallShield”: Restart the system and delete the following directories(or the corresponding non-standard directories, if still available).– C:\Program Files\Iona– C:\Program Files\JavaSoft– C:\Program Files\PrismTech OpenFusion– C:\Program Files\Siemens\TCOA_DS

3rd-Party Setup Options for TCOA Proxy and RPR Manager• Custom Setup

Components should only be installed or deinstalled by specialists. There is no "Re-pair" option.

7.3 Installing TCOMTCOM is an optional software for TNMS Core/CDM supporting the TMF CORBA Man-ager and allows managing the Siemens SXC and other interanl applications, e.g. radiointegration or SM16000 integration.

A42022-L5938-H52-1-76D1 57



Prerequisites

The following prerequisites must be met before you can begin installing the TCOM soft-ware package:– TNMS Core/CDM 9.0 is installed on the Server, NetServer(s) and Client machines.

The OSI stack does not need to be installed on the TCOM NetServer.– The TCOM Deployment Software is installed on the NetServer.– If the FTP Server software must be installed during the installation process the latest

security hotfixes and service packs for the installed Windows 2000 operation systemare required. The setup program may also require the original Windows 2000 instal-lation CD-ROM.If you do not want to install the FTP Server it restricts you from getting any historicalperformance data from network elements.

In addition to the installation steps described for the TNMS Core/CDM component, thefollowing installation steps are required for TCOM operation:– Installation of the TCOM Configuration Tool on the NetServer to handle specific NEs.– Installation of the TCOM software package, also named TCOM EML Server pack-

age, on Server, NetServer(s) and Client machines.– Configuration of the NetServer, DCN channels and NEs for this server.

The complete TCOM installation process in fact consists of:– "7.3.1 3rd-Party Software for TCOM"– "7.3.2 TCOM Installation"– "7.3.3 TCOM Configuration Tool"– "7.3.4 TCOM EML Server Setup"– "7.3.5 TCOM DCN Management Configuration"

7.3.1 3rd-Party Software for TCOM

Installation Overview

Installing the TCOM software requires the following 3rd-party software:– Javasoft Java Runtime Environment– IONA Orbix E2A ASP– XML parser MSXML 4.0

For the exact software version see section 3.3.1.

The ORB9.0_DS CD contains the 3rd-party software in the directory "Product_CDs” andthe "main setup" for starting and controlling the 3rd-party software in the root directoryof the CD. The "main setup" also configures the 3rd-party software after installation tooperate together with TNMS Core/CDM.

iDeactivate the TNMS Core/CDM NetServer(s) and stop the TNMS Core/CDM Server,close all TNMS applications and stop all TNMS Windows services.

iOn a Server PC with TCOA Proxy the third party product “OpenFusion” (installed byTCOA9.0_DS) requires “JRE 1.3.1” to be active during Setup.

If under the registry key “SOFTWARE\JavaSoft\Java Runtime Environment” the valuefor “CurrentVersions” is set and the value is different from “1.3”, please reset it to “1.3”before installing TCOA9.0_DS (e.g. on a TNMS one-server-configuration where TNMSis installed before TCOA9.0_DS). After the installation of TCOA9.0_DS it may bechanged back to its original version.

58 A42022-L5938-H52-1-76D1


Installing TCOM 3rd-Party Software

1. Insert the ORB CD in the CD-ROM drive.

2. Open the Windows Explorer.

3. Navigate to the CD folder and run the "Setup.exe”.

4. Proceed as described in the ORB setup windows:"Welcome" window:-> Confirm with "Next".

5. "License Agreement" window:-> Accept the license agreement with "Yes".

6. "ORB Installation Guide" window:-> Print out the recommended "Readme.txt" to obtain the necessary information onthe 3rd party software.-> Confirm with "Next".

7. "Customer Information" window:-> Enter a user name (alphanumeric characters) and a company name (alphanu-meric characters).-> Enter the ORB serial number.-> Confirm with "Next".

8. "Choose Destination Location" window:-> Use the default installation directory (C:\Program files\Siemens\ORB) for theORB software or click the "Browse" button if you want to change the installation di-rectory.-> Confirm with "Next".

9. "Choose Destination Location" window:-> Use the default installation directory (C:\Program files) for the TCOM 3rd partysoftware, or click the "Browse" button if you want to change the installation directory.-> Confirm with "Next".

10. A "Setup Status" window will be displayed. The installation and configuration of theJava Runtime Environment are performed automatically.

11. Execute the Orbix E2A ASP setup as follows:"Installation Guide for native Orbix E2A ASP Setup” window:-> A message indicates that the Notepad file "ReadMe_Orbix2000_Setup.txt" is go-ing to be displayed. This file describes the entries necessary for the Orbix E2A ASPsetup.-> Confirm with "Ok".

12. "Orbix E2A ASP 5.1 Introduction" window:-> Confirm with "Next".

A42022-L5938-H52-1-76D1 59



13. "License Agreement" window:-> Read the license agreement.-> Select the option "I accept the terms of the License Agreement".-> Confirm with "Next".

14. "Choose Application Server Platform Install Folder" window:-> Use the default installation directory (C:\Program files\IONA) for the Orbix E2AASP files, or click the "Choose..." button, if you want to change the installation direc-tory.-> If you want to reset your chosen directory to the default directory, click the "Re-store Default Folder" button.-> Confirm with "Next".

15. "Choose Shortcut Location" window:-> Select the desired option for the Orbix E2A ASP program group.-> If your computer is used by different users, you may also select the "Create Iconsfor all Users" option.-> Confirm with "Next".

16. "Choose Product Edition" window:-> Choose the "Standard Edition" option to get a complete installation.-> Confirm with "Next".

17. "Choose Environment" window:-> Select "Runtime Only".-> Confirm with "Next".

18. "Choose Java Virtual Machine" window:-> Select "... \JavaSoft\JRE\1.3.1\bin\java.exe" located in the destination location ofthe 3rd party software (default “C:\Program Files”).-> Confirm with "Next".

19. "JDK Tools Location" window:-> Select "... \JavaSoft\JRE\1.3.1\lib\tools.jar" located in the destination location ofthe 3rd party software (default “C:\Program Files”).-> Confirm with "Next".

20. "Set Environment Variables?" window:-> Select the default radio button “Set the variables for all Users”.-> Confirm with "Next".

21. "Pre-Installation Summary" window:-> Push the "Install" button to proceed.

22. Now the Orbix Setup will transfer the files. Then a web browser window with someOrbix documentation is shown, close this window.Finally additional user input is required.

23. "Installation Complete" window:-> Push the "Done" button to proceed.

60 A42022-L5938-H52-1-76D1


Then an information window announces to open a “Notepad” with the file“ReadMe_Orbix_E2A_ASP_ORB_Configure.txt”. This text describes the manual inputnecessary for the native Orbix E2A ASP configuration tool. Confirm with "OK" and exe-cute the configuration as described:

1. "Orbix E2A Configuration" window:-> Confirm with "Next".

2. "Licensing" window:Select the radio button “Use installed license file” and use the default location(C:\Program files\IONA\etc\licenses.txt)-> Confirm with "Next".

3. "Choose a configuration option" window:Select the radio button “Create a configuration domain”-> Confirm with "Next".

4. "Configuration domain" window:Use the default domain name “orbix E2A”.Select the feature “Orbix E2A Services” (default).Deselect the feature “Orbix E2A Application Server” (default)Deselect “Include configuration for demo applications”.-> Confirm with "Next".

5. "Choose configuration domain type" window:Select “Local File” (default)-> Confirm with "Next".

6. "Set host properties" window:Use the default settings (your host name) for the unqualified host name and for thehost DNS alias.Use the default path “C:\Program files\IONA\etc” to store the configuration files andthe default path “C:\Program files\IONA\var” to store the service databases.-> Confirm with "Next".

7. "Information" window:If the 'var' subdirectory does not exist, agree to create the directory.-> Confirm with "Yes".

8. "Location Service" window:Select “Yes” (default) to deploy a location service.-> Confirm with "Next".

9. "Setup Infrastructure services" window:Select the (default) port 3075 for the locator daemon.Select the (default) port 3079 for the node daemon.-> Confirm with "Next".

A42022-L5938-H52-1-76D1 61



10. "Orbix E2A Services" 1st window:Select “Naming Service” (default).Deselect “Management Service” (default).-> Confirm with "Next".

11. "Orbix E2A Services" 2nd window:Deselect “Event Service” (default).Deselect “Interface Repository” (default).-> Confirm with "Next".

12. "Orbix E2A Services" 3rd window:Deselect “JMS” (default).-> Confirm with "Next".

13. "Configure service settings" window:Select “Start services via a startup script.-> Push the "Finish" button to proceed.

14. "Summary of your configuration" window:-> Push the "Deploy" button to proceed.Now the native Orbix Setup will deploy the configuration.

15. The “Congratulations! Your conf. successfully deployed.” window appear.-> Push the “Close” button to proceed.

16. Finally, the 'InstallShield Wizard Complete' window prompts you to restart your com-puter.-> Accept the default "Yes, I want to restart my computer now" by pressing “Finish”to reboot your PC immediately.

17. The Orbix Configuration is complete now.

Deinstalling TCOM 3rd-Party Software– In the taskbar, select: Start -> Settings -> Control Panel.– Double-click "Add/Remove programs".– From the list, select "ORB_DS”.– Press the button: Add/Remove.

The "InstallShield Wizard” is displayed.– Select "Remove”.– Click "Next”.– Confirm in the next window.

Several windows are opened for deinstallation one after the other. These must be con-firmed as described in the setup windows.

After finishing the "InstallShield”, restart the system and delete the following directories(or the corresponding non-standard directories, if still available).– C:\Program Files\Iona– C:\Program Files\JavaSoft– C:\Program Files\Siemens\ORB_DS

62 A42022-L5938-H52-1-76D1


7.3.2 TCOM Installation1. To begin installation, double-click the setup.exe provided on the TCOM CD. Do this

for the Server, NetServer and Client machines. The setup program prepares the In-stallShield Wizard, which will guide you through the rest of the setup process.

2. Next the Welcome window of the InstallShield Wizard appears. Press "Next” to con-tinue.

3. The License Agreement window is now displayed. Read the license agreement andpress "Yes” to accept the licensing terms and conditions and to continue.

4. The Customer Information window is now displayed. Enter the user name and thename of the company for which this copy of TCOM EML Server is registered, andpress "Next” to continue.

5. If the FTP Server is not yet installed, you are now asked if you want to install the FTPServer.

Click "Yes” if you want to install the FTP Server now, otherwise click "No”.After installing the FTP Server you must install the latest security hotfixes and ser-vice packs for the Windows 2000 operation system.

6. In the Choose Destination Location window you can select the destination folder toinstall the EML-TCOM. Select the "Browse” button and choose the destination folderfor the installation. Then continue with "Next”.

7. Before the files are copied, the InstallShield Wizard displays the installation settings.If you wish to modify any of these settings, press "Back”. Otherwise, you can contin-ue with "Next”.

8. The InstallShield Wizard now begins the installation. The status of the installation isindicated by a progress bar.During the installation also the embedded FTP Server installation on the NetServerwill be carried out, if "Yes” was chosen before. After successful installation the InstallWizard Complete window is displayed. Press “Finish” to complete the installation.

TCOM Software Package: Modify Installation

The “Modify” mode allows the user to add or remove components to/from the currentlyinstalled TCOM package.

1. Double-click the setup.exe provided on the TCOM CD. The setup program preparesthe InstallShield Wizard, which will guide you through the rest of the setup process.

2. In the Welcome window select "Modify” and click the "Next” button to continue.3. The Start Copying Files window appears. Click "Next” to continue.4. During the modification of the TCOM software, the Setup Status window appears.

iInstalling the FTP Server requires to have the latest security hotfixes and service packsfor the installed Windows 2000 operation system. The setup program may also requirethe original Windows 2000 installation CD-ROM.If you do not want to install the FTP Server it restricts you from getting any historical per-formance data from network elements.

A42022-L5938-H52-1-76D1 63



5. After the successful modification of the TCOM software, the Maintenance Completewindow appears. Click "Finish” to complete the modification procedure.

TCOM Software Package: Repair Installation

In order to repair the TCOM software package execute the setup.exe file.


2. In the Welcome window select "Repair” and click the ”Next” button to continue.3. During the mending of the TCOM software, the Setup Status window appears.4. Finally the Maintenance Complete window appears. Click "Finish” to complete the

repair procedure.

TCOM Software Package: Remove Installation

In order to remove the TCOM software package execute the setup.exe file and proceedas described below: During the deinstallation process you will be asked whether youwould also like to deinstall the configuration software.


2. As TCOM is already installed a Welcome window with selection criteria opens. Se-lect "Remove” at the bottom of the window.

3. A dialog box is displayed. You are asked whether you want to remove the TCOMsoftware application with all its TCOM components. Confirm this dialog box by click-ing "OK”.

4. A dialog box is displayed. If TCOM configuration software is installed, e.g. SXCTCOA or TNMS-SX TCOA, you can deinstall this configuration software during thedeinstallation. Click "Yes” if you want to deinstall the configuration software, click"No” if you want to keep the configuration software.

5. Finally the Maintenance Complete window appears. Click "Finish” to complete theremoval procedure.

7.3.3 TCOM Configuration ToolTNMS Core/CDM 9.0 needs to be configured to be able to support certain EMS sys-tems. The TCOM configuration tool currently supports:– TNMS Core TCOA (only in previous versions)– SXC TCOA (only on customer demand)– RNS TCOA– SILVX TCOA

The configuration steps shown here for the TNMS Core TCOA are identical for any othersupported EMS system.

Configuration Tool: Configure the EMS Systems

1. Now start the TCOM configuration for the specific EMS system on the NetServer:2. The Welcome window of the TCOM configuration tool appears. Press "Next” to con-

tinue.

iThe configuration tasks for the different EMS systems are identical; only the correct CD-ROM for the EMS to be installed must be used, and, during installation, the name of thesupported EMS system must be entered in the windows.

64 A42022-L5938-H52-1-76D1


3. While copying the files, the Installation Wizard displays the installation settings.If you wish to modify any of these settings, press "Back”. Otherwise, you can contin-ue with "Next”.

4. The InstallShield Wizard begins the installation of the TCOM configuration tool files.The status of the installation is indicated by a progress bar.

5. Finally the Maintenance Complete window appears. Click "Finish” to complete theinstallation procedure. When the installation has been completed, no reboot is nec-essary.

Configuration Tool: Modify the EMS Systems

The “Modify” mode allows the user to add or remove components to/from the currentlyinstalled TCOM package.

In order to modify any of the EMS systems proceed as described below:

1. Start the TCOM configuration for the specific EMS system on the NetServer.Insert the Configuration Tool CD for the EMS into the drive and double-click the set-up.exe file. The InstallShield Wizard for the configuration tool will be prepared.

2. In the Welcome window select "Modify” for modifying new program components(add new components or remove installed components).

3. Next the Setup Status window is shown, displaying the status of the modificationprocedure.

4. Finally the Maintenance Complete window appears, when the modification per-formed by the configuration tool is complete. Click "Finish”.

Configuration Tool: Repair the EMS Systems

In order to repair any of the EMS systems proceed as described below:

1. Start the TCOM configuration for the specific EMS system on the NetServer.Insert the Configuration Tool CD for the EMS into the drive and double-click the set-up.exe file. The InstallShield Wizard for the configuration tool will be prepared.

2. In the Welcome window select "Modify” for modifying new program components(add new components or remove installed components).

3. The Setup Status window appears.4. Finally the Maintenance Complete Window appears. Click "Finish” to complete the

repair procedure.

A42022-L5938-H52-1-76D1 65



7.3.4 TCOM EML Server Setup

1. To proceed with the TCOM EML Server Setup open the "DCN Management” windowunder TNMS Core/CDM SysAdmin and add a channel for the TCOM NetServer:

Fig. 7.1 Add Channel for TCOM NetServer in the DCN Management Window

2. Select the channel type from the list below, either TCOM (Go7 2.0.0) or TCOM (TMF814 2.1) and click "OK”. The channel to be used depends on the EMS to which aconnection is to be established.

Fig. 7.2 Select the TCOM Channel Type

3. In the "General” page of the "TCOM Channel Properties” window enter the uniqueID Name for the TCOM channel. If you want, you can also enter an additional text inthe description field.

iBefore starting with the TCOM EML Server Setup, open TNMS SysAdmin applicationand start all TNMS Windows 2000 services.

iDetailed information on the fields of the "General” page can be obtained by clicking the"Help” button in the window.

66 A42022-L5938-H52-1-76D1


Fig. 7.3 Enter the ID Name for the Channel on the General Page

4. If you want to control the DCN load during the system startup, you can choose “En-able Scheduled Startup” and define the maximal number of network elements to besimultaneously initialized (Fig. 7.4).

Fig. 7.4 Enable Scheduled Startup

5. Depending on the selected TCOM channel type (TCOM (Go7 2.0.0) or TCOM (TMF814 2.1)) two individual views of the "EMS Properties” page are displayed.Fig. 7.5 shows the view for the channel type TCOM (Go7 2.0.0).

iDetailed information on the fields of the "EMS Properties” page can be obtained by click-ing the "Help” button in the window.

A42022-L5938-H52-1-76D1 67



Fig. 7.5 EMS Properties Page for TCOM (Go7 2.0.0)

6. Fig. 7.6 shows the view for the channel type MTNM TMF 814 2.0.

Fig. 7.6 EMS Properties Page (in case of TMF 814 2.0)

iDetailed information on the fields of the "EMS Properties” page can be obtained by click-ing the "Help” button in the window.

68 A42022-L5938-H52-1-76D1


7. Next, if required, select the "Performance Management” register and enable the per-formance management check box and fill in the required fields.

Fig. 7.7 Performance Management Page

8. Finally you must enter the data for the GUI Cut Through to be able to open the EMSGUI in the TNMS Core/CDM GUI, if required by the EMS.

Fig. 7.8 Enter Data on the GUI Cut Through Page

iDetailed information on the fields of the "Performance Management” page can be ob-tained by clicking the "Help” button in the window.

iDetailed information on the fields of the "Performance Management” page can be ob-tained by clicking the "Help” button in the window.

A42022-L5938-H52-1-76D1 69



9. Having entered these configuration data the status "Running” will be displayed in the"DCN Management” window if– the DCN Connections check box was activated before,– the NetServer has been started,– the TCOM EML Server check box was activated, or– a physical connection to the EMS exists, the EMS has been started and is ready

for communication.

Fig. 7.9 Status is "Connecting”

7.3.5 TCOM DCN Management Configuration1. In the "DCN Management” window of TNMS Core/CDM SysAdmin select the TCOM

channel (in this example, it is the channel "Shanghai”) and invoke the context menuwith a right mouse click.Select the "Browse...” menu command to browse for the available DCN objects:

Fig. 7.10 Browse for the DCN Objects of a Channel

70 A42022-L5938-H52-1-76D1


2. Select the desired DCN object from the object list as shown below:

Fig. 7.11 Select a DCN Object from the Objects List

3. By selecting the NE and clicking the "Adopt” button with the left mouse tab, the se-lected NE will be adopted into the TNMS Core/CDM. The properties window for thisNE opens showing the "General” page. In this example, a SL64 is used.

Fig. 7.12 "General” Page of a DCN Object

Enter the ID Name; if required you can change the NE Name and enter user-definedtext into the User Text fields and click "Apply” to save your settings.

4. You can click the "NE Properties” register below to show the "NE Properties” page.

!Do not change the field "EMS Management Element Id” in the NE Properties page!

A42022-L5938-H52-1-76D1 71



Fig. 7.13 NE Properties page

Exit the window with "Close”.

5. In the "DCN Management” window, the DCN object (in the example below it is aSL64) is now displayed in the state "Deactivated”.Activate the DCN object by clicking the check box. As a result, the DCN objectchanges its state to "Starting Up” and finally to “Running”.

Fig. 7.14 DCN Management Window - SL64 in State "Deactivated”

The TCOM DCN Management configuration is now complete. The TCOM network ele-ment which was chosen to be configured is ready for use.

72 A42022-L5938-H52-1-76D1


7.4 Installing PLETPLET is an optional tool used for exporting performance logs, alarm logs, network eventlogs and system message logs. It is installed on the TNMS Core/CDM Server.

To install PLET, proceed as follows:

1. Double-click the file "TNMS-PLET.exe” provided on the PLET software CD.The files required for the PLET installation are extracted.


3. An "Information” window is now displayed.This window indicates that the installation of MDAC is prerequisite for the installa-tion.

Press "Next” to continue.

4. In the "Choose Destination Location” window, a default installation directory is of-fered. Press "Next” to continue.

5. In the "Select Program Folder” window, a default program folder is offered. Press"Next” to continue.A progress bar is now displayed indicating the progress of the installation.

6. The window "InstallShield Wizard Complete” is now shown. Select the option for re-starting the computer, and press "Finish” to complete the installation.

In order to uninstall PLET, open Start -> Settings -> Control Panel -> Add/Remove Pro-grams:– Select PLET from the software list.– Click the "Change/Remove” button.– Select the "Remove” option.– Confirm the uninstall process with "Finish” and restart your computer.

7.5 Installing WavelineWaveline is an optional EML package which must be installed on the TNMS Client, Serv-er and NetServer if Waveline network elements are to be installed. The following stepshave to be performed:

To install Waveline, proceed as follows:

1. Double-click the file "Setup.exe” provided on the Waveline software CD.



i MDAC (Microsoft Data Access Components) is installed automatically during theTNMS Core/CDM installation.

A42022-L5938-H52-1-76D1 73




5. In the "Choose Destination Location” window, a default installation directory is of-fered. Press "Next” to continue.

6. In the "Start Copying Files" window, ensure that the settings displayed are correct,and if so, press "Next” to continue.

7. The "Setup Status” window which is now displayed indicates the progress of the in-stallation.Various LCTs are installed now as well.

8. You are now asked whether you wish to install TransXpress WaveLine. Press "Yes”to continue.

9. The window "InstallShield Wizard Complete” is now shown. Select the option for re-starting the computer, and press "Finish” to complete the installation.

In order to uninstall Waveline, open Start -> Settings -> Control Panel -> Add/RemovePrograms:– Select Waveline from the software list.– Click the "Change/Remove” button.– Select the "Remove” option.– Confirm the uninstall process with "Finish” and restart your computer.

7.6 Installing MSNMSN (multi service node) is an optional EML package. It enables individual network el-ements to be grouped together in a single manageable cluster.

1. Double-click the file "setup.exe” provided on the MSN software CD.


3. In the "License Agreement" window, read the license agreement and press "Yes" toconfirm.

4. In the "Choose Destination Location” window, a default installation directory is of-fered. Use the default installation directory or click the "Browse" button, if you wantto change the installation directory. Press "Next” to continue.


6. The "Setup Status” window which is now displayed indicates the progress of the in-stallation.

7. The window "InstallShield Wizard Complete” is now shown. Press "Finish” to com-plete the installation.

74 A42022-L5938-H52-1-76D1


8. Stop and start the TNMS Server to get MSN functionality in your TNMS Server ap-plication. In the DCN management, the DCN channel type “Multi NE controller” andthe NE type “MSN” are now available.

In order to uninstall MSN, open Start -> Settings -> Control Panel -> Add/Remove Pro-grams:– Select EML-MSN from the software list.– Click the "Change/Remove” button.– Select the "Remove” option and press “Next”.– Confirm the uninstall process with "OK”.– In the window "Locked File Detected” press “Ignore” (leaves the locked file on the

system).– Confirm with "Finish”.– Stop and start the TNMS Server to apply the changes.

7.7 Installing TNMS @P Server and Enhanced ApplicationsThe TNMS @P Server software is the TNMS Core/CDM platform for the Enhanced Ap-plications (TNMS @P Platform and TNMS @P Proxy) of TNMS Core/CDM. TNMS @Pserver software and TNMS Enhanced Applications software will be delivered on thesame CD.

The overall installation process of a TNMS Core/CDM system can consequently consistof several steps with regard to:

1. TNMS Core/CDM installation2. TNMS @P Server installation3. TNMS Enhanced Applications installation

Licensing Information

For the enhanced applications, a license file is required. You must rename the originalname of the license file to “licenses.xml” and copy it into the directory C:\tnms@p\licens-es.

Prerequisites

The TNMS @P Server installation consists of the following elements:– TNMS Core/CDM is the Base Platform for the TNMS @P Server software to be in-

stalled on the TNMS Server PC. After installing the Base Platform a reboot of theTNMS Server PC should be done.

– The TNMS @P proxy must be installed on the TNMS Server PC. The proxy requiresORBIX E2A ASP, which is provided on the ORB CD. For installation information seeSection 7.2.1.

– The TNMS @P SysAdmin, RPR client and Scheduled Service Activationmust be in-stalled on the machine where TNMS SysAdmin is installed.

iTNMS @P and the enhanced applications use JRE 1.4.1. As they are installed into localsubdirectories, install them both when asked for.Do not replace any JRE version to keep TNMS Core/CDM operable!

A42022-L5938-H52-1-76D1 75



Installation

1. Terminate all TNMS Core/CDM processes and then stop the TNMS Core/CDMServer prior to installing TNMS @P proxy.

2. Double-click the file "setup.exe” provided on the TNMS @P software CD.

3. An “Introduction” window is now displayed. Press "Next” to continue, the “Choose In-stall Set” window opens where you can select the desired applications to be in-stalled:

– TNMS @P Server / TNMS @P Proxy / RPR Server– TNMS @P SysAdmin– Scheduled Service Activation– RPR Client– Remote Backup Server

4. Press “Next” to continue. In the "License Agreement" window, read the licenseagreement. Press "Next" to confirm.

5. In the "Choose Install Folder" window, enter the path where TNMS @P Server areto be installed or press “Choose” to browse for a folder. Press "Next” to continue.

6. The ”Pre-Installation Summary” gives an overview of the installation settings. Press“Previous” to choose these settings or press “Install” to start the installation.

7. The “Installing...” window displays the installation progress.

The window "Install Complete” is now shown. Press "Done” to complete the instal-lation.

8. Restart the TNMS Server.In order to uninstall TNMS @P Server, open Start -> Settings -> Control Panel ->Add/Remove Programs:– Stop the TNMS Server.– Select TNMS @P Server from the software list.– Click the “Change/Remove” button.– In the “Uninstall” window, press “Uninstall”.– In the "Uninstall Complete” window, finish the deinstallation with “Done”.– Start the TNMS Server to apply the changes

76 A42022-L5938-H52-1-76D1


8 Measures after CommissioningAfter the TNMS Core/CDM software and relevant 3rd-party software has been installed,the TNMS Core/CDM installation must be configured using the SysAdmin application.

8.1 Initial Configuration of TNMS Core/CDM Using SysAdminOnce the TNMS Core/CDM software has been installed, and the computer restarted, theTNMS Core/CDM system can be configured. The main steps to be completed duringconfiguration are listed below. Additional information is provided in the online help under"Initial configuration - TNMS Core/CDM”. This section of the help also provides links todetailed instructions for each step to be completed.

1. Start SysAdmin

Start the TNMS Core/CDM SysAdmin interface via "Start” -> "Programs” -> "TNMS 9.0”-> "System Administration”.

2. Logon

Log onto TNMS Core/CDM SysAdmin via the displayed logon dialog.

Fig. 8.1 TNMS SysAdmin Logon window

– In the field "Server", enter the name of the PC where the TNMS Core/CDM Serveris installed. If you are logging in directly to the PC where the TNMS Core/CDM Serv-er is installed, enter ".".

– In the field "User name" enter the default value "Administrator". This account is cre-ated automatically during the installation of TNMS Core/CDM.

– When you log on for the first time, the field "Password" does not have to be complet-ed.

– After confirming the entry via the "Logon” button, change the password for the de-fault administrator account as requested.

3. Configure user accounts

A default administrator account is created during installation. Additional accounts cannow be created as required. Global account settings can also be edited at any time.

iThe TNMS Core/CDM Server is still deactivated at this time.Do not activate it until step 6 below has been completed.

A42022-L5938-H52-1-76D1 77



4. Check license availability

First of all, enter the Basic License via TNMS SysAdmin to be able to start the Server.Then check whether licenses are available for the required range of functions and addthem.

5. Define log configuration settings

You can determine the available size of the various log files on the hard disk. Settingscan be entered for the size of the alarm log, system message log, network event log,security event log and custom log. Performance logs can only be created if sufficientspace is reserved for custom logs.

All log files are installed in the directory <TNMS installation path> ..\Logs. On the HDpartition where the TNMS is installed there should be at least 1 GB free disk space dur-ing operation. If the log file size will be changed (expanded) check the necessary diskspace again.

6. Configure database backup options

In TNMS Core/CDM, you can choose whether to schedule an automatic backup or toimplement a manual backup. Settings are provided for the backup host, backup file pathname and for the time and frequency of archiving in SysAdmin.

7. Start the TNMS Core/CDM Server

In order to configure DCN objects and to set cost factors for automatic routing, you muststart the TNMS Core/CDM Server. Press the “Start Server” button in the SysAdmin tool-bar and confirm with “OK”.

8. Add NetServers

After TNMS Core/CDM installation, the NetServer computers must be linked up to theTNMS Core/CDM via the "DCN Management” dialog.

9. Configure and activate DCN channels

DCN channels are also configured in the "DCN Management” dialog. Once configured,the channel settings should be checked, e.g. for scheduling communication.

10. Configure network elements

You can now add the required network elements by right-clicking relevant the DCNchannel and selecting the "Add” option. Select the required network element type fromthe list, and complete each tab page as described in the online help for the selected net-work element type.In the case of SXEM and PDH network elements, you must also start the correspondingLCT once prior to starting the element manager in TNMS Core/CDM. This provides youwith administrator access rights to the PDH/SXEM network element. This has to becompleted for each client separately after installation of the TNMS Core/CDM Clientsoftware.

iThe OSILLC protocol driver must not run on more than one ethernet card. The drivershould therefore be disabled on any other cards using Start -> Settings -> Control Panel-> Network -> "Network and Dial-up connections” tab on the NetServer PC.

iNE names of more than 39 characters can cause problems when starting the ElementManager. In this case, enter an NE name of less than 39 characters.

78 A42022-L5938-H52-1-76D1


11. Configure the SNMP proxy

If the SNMP Proxy has been installed, you can now enter configuration data for it. Then,start and activate SNMP Proxy.

12. Configure the TCOA proxy

If the TCOA Proxy has been installed, you can now enter configuration data for it. Then,start and activate TCOA Proxy.

13. Synchronize the computer date and time

For event logging, all TNMS Core/CDM computers have to have the same settings. Forthis purpose, date and time are to be taken from the server for the other computers. Theclients also have to forward these settings to the network elements.

14. Start the TNMS Client

The login procedure is the same as for "SysAdmin", however, you must log in using thenew Administrator password that you configured when you logged onto SysAdmin forthe first time.

15. Create the Network Plan

The network plan can now be created using TNMS Client. This must be done on the ba-sis of planning data (when installing the system the first time) or by migration of dataused in formerly software versions (in case of software updates).

16. Further settings

Further setting can be done depending on the individual customers needs (e.g. alarmsettings: alarm messenger, color settings).

8.2 MigrationTNMS Core/CDM 9.0 supports migration of data from TNMS Core 8.5. For data migra-tion it is recommended to install the version 9.0 software “parallely” on a separate sys-tem and connect it to the same LAN for easy data transfer between the two systems.

The migration procedure is supported by a so called “Migration Wizard”. It will be acti-vated automatically if you try to restore a 8.5 version database in a TNMS Core/CDM9.0 system.

Further information about migration is given within the Operator Guidelines OGL and theOnline Help.

iOnce you have configured NetServers, DCN channels and network elements (steps 8-10), the status of these objects is shown in the "DCN Management” window.

iWhen installing the new system, keep in mind that Server and Backup Server have tobe instaled on the same machine.

A42022-L5938-H52-1-76D1 79



8.3 Routing Settings for PCs with Multiple Network AdaptersIf one or more PCs in your TNMS Core/CDM system have multiple network adapters (fornetworking protocols in addition to TCP/IP), delays may occur in connection setup be-tween the various TNMS Core/CDM machines.

For example:– Computer A has one network adapter (for the LAN segment to computer B)– Computer B has two network adapters (one for the LAN segment to computer A and

one for an external LAN segment)

Because computer B has two network adapters, it also has two IP addresses.When establishing communication with computer A, computer B transmits both IP ad-dresses. If the first IP address sent by computer B is the address for the common LANsegment, communication can be established without any problems. But if the first IP ad-dress sent by computer B is the address for the external LAN segment, and a gatewaycomputer with routing information is not available, timeout cycles will result in delayedcommunication.

The following connections may then be affected:

The problem can be solved by defining the sequence in which IP address information istransmitted in the network settings for each PC as follows:

1. Right-click the icon "My Network Places" on your desktop. In the menu that appears,select the item "Properties”.

2. In the "Network and Dial-Up Connections” window that appears, click on "Advanced”in the toolbar, and from the list that appears select "Advanced Settings...”.

3. The "Advanced Settings” windows is now displayed. In the "Connections” list, select"Local Area Connection”. The list beneath (called "Bindings for Local Area Connec-tion”) will now show the preferred order in which protocols will be used.

4. Select the item "Internet Protocol (TCP/IP)” from the list and then click on the up ar-row on the right side of the window. Do this until "Internet Protocol (TCP/IP)” is thefirst item in the list under "File and Printer Sharing for Microsoft Networks”.

5. Repeat the procedure in step four for all of the other clients listed in the window.6. After changing the settings for all of the clients listed, click on the tab titled "Provider

Order”.7. Select the item "Microsoft Windows Network” from the "Network providers” field, and

then click on the up arrow on the right side of the screen to move it to the top of thelist.

8. Click "OK” to save the changes and then reboot the computer.

Connection Affected Task

Client -> NetServer Starting the LCT application from a Client.

Server -> NetServer Communication with NetServers/NEs.

Server -> Standby Server Starting database replication.

Server -> Client Starting the Client application or the SysAdmin applica-tion.

Tab. 8.1 Affected Connections

80 A42022-L5938-H52-1-76D1


9 System Expansion

9.1 Adding Additional ClientsUp to 40 clients can be operated on one server simultaneously. If new clients are to beadded as part of system expansion, the same software version must be installed as pro-vided on existing clients.

Proceed as follows:– Install and cable the new computers as described in Section 3.2.1.– Install operating system as described in Section 4.2.3.– Install the Client and/or SysAdmin software as described in Chapter 6.– Test the system in accordance with the test cases described in the acceptance test

protocol. For more information, contact Siemens Technical Sales.– Enter the relevant details in the field test protocol and acceptance protocol.

9.2 Adding Additional NetServersUp to 10 NetServers can be operated on one server simultaneously. If new NetServersare added as part of system expansion, the same software version must be installed asprovided on existing NetServers.

Proceed as follows:– Install and cable the new computers as described in Section 3.2.1.– Install operating system as described in Section 4.2.3.– Install an OSI stack as described in Section 5.3.

Note that every NetServer must have its own specific NSAP address provided byplanning.

– Install the NetServer software as described in Chapter 6.– Add the NetServer via in the "DCN Management" window in SysAdmin.– Test the system in accordance with the test cases described in the acceptance test


A42022-L5938-H52-1-76D1 81



10 Multi Server CDM: Protective Measures andHandling

Protective measures and information on handling electrical components in the MultiServer CDM installation is provided here.

10.1 Safety Precautions When the Unit is OpenBefore opening the unit, remove the power cable.

Once the unit is open, live connector pins are freely accessible. To prevent electricshocks, make sure that these pins do not come into contact with foreign potential (e.g.ground).

10.1.1 Protection against Excessive Contact VoltagesWhen dealing with the power supply, observe the safety precautions as specified by theGerman DIN standard VDE 0105 (operation of high-voltage systems). This standard de-fines in detail the steps to be taken by the operators of electrical installations and theusers of electrical equipment to ensure the safe maintenance of electrical installationsand equipment.

10.2 Handling ModulesModules labeled as shown in Fig. 10.1 below are equipped with electrostatic-sensitivecomponents.

Fig. 10.1 Labeling of electrostatic-sensitive devices (ESD symbol)

All modules with ESD components have an outer grounding edge which is connected tothe module "ground" and which can be used when gripping the circuit board.

Modules are fully protected if they are enclosed in a shielded, unopened housing.Nevertheless, the following basic safety precautions should always be followed whenhandling ESD components:– Always use a grounding bracelet connected to a grounding socket (see below) when

unpacking, packing, touching, unplugging or plugging modules bearing the ESD(German EGB) symbol. This will ensure that the modules do not get damaged.

– Avoid touching the component connections, connector contacts or conductor tracks(even if you are properly grounded).

– When unplugging and plugging modules, make sure you use the handles provided.

iMulti Server CDM is available only on customers’ request.

iAs a general rule, you should always note the manufacturer’s instructions when han-dling devices such as PCs, monitors, printers and tape drives, or when installing mod-ules such as network cards.

82 A42022-L5938-H52-1-76D1


– If modules are only gripped by the handles for plugging/unplugging, they should notbe transported in a horizontal position (danger of breakage).

– When you remove the module from its subrack, place it on an antistatic mat.– Make sure that all measuring equipment used is grounded.– If you are using ungrounded measuring equipment, briefly connect the measuring

probe to ground (discharge) it before performing measurements on components andmodules.

– Ensure that the modules are installed in the correct slots.

iEuropean standard EN50082-1 contains detailed information on the correct handling ofelectrostatic-sensitive devices.

A42022-L5938-H52-1-76D1 83



11 Multi Server CDM: Preparation forCommissioning

11.1 Component DeliveryBefore installation, ensure that:– the delivery is complete in accordance with the delivery units specified in the deliv-

ery note (hardware, software and documentation),– the components are not damaged in any way.

11.2 Hardware RecommendationsThis table provides an rough overview of the hardware requirements for running MultiServer CDM software. Together with other parameters (e.g. number of Clients, numberof NetServers) the hardware configuration must be planned specifically for each cus-tomer. More information is available from Siemens Technical Sales.

11.2.1 Installation and CablingBefore installing the operating system, the following steps should be completed:


Server NetServer Client


CPU: P4, 1.5 GHzMultiprocessor operationsupported.


Memory:2 x 512 MB

Memory:2 x 512 MB

Memory:2 x 256 MB

Hard Disk:2 x 36 GB

Hard Disk:20 GB

Hard Disk:20 GB

Floppy Disk:1.44 MB

Floppy Disk:1.44 MB

Floppy Disk:1.44 MB

CD-ROM drive CD-ROM drive CD-ROM drive

Ethernet card Ethernet card, 2x Ethernet card

RAID controller - -

DAT streamer for backup - -

- - PC I/O, optional

Color monitor 17” Color monitor 17” Color monitor 21”

Operating system:Windows 2000 Server



Tab. 11.1 Hardware Requirements for MS CDM Server, NetServer and Client

84 A42022-L5938-H52-1-76D1


– The Client, NetServer and Server PCs should be set up and cabled in accordancewith the project-specific installation documents supplied.

– The applicable recommendations for screen-based workstations should be ob-served.

– To guarantee 24-hour operation, an uninterrupted power supply must be available.

11.2.2 Mirror DisksThe MS CDM Server PC is provided with a RAID system and two additional mirror diskswhich are monitored by a SCSI RAID controller. The SCSI RAID controller ensures au-tomatic data synchronization between the active hard disk and the mirror disks, so if theactive hard disks develops a fault, a mirror disk takes over and the system is not affect-ed. The faulty disk can be replaced by a new disk of the same type without shutting downthe Server. The RAID controller then copies the data from the active hard disk to thenewly installed hard disk.

11.2.3 Standby ServerYou have the option of configuring a warm standby MS CDM Server. The warm standbyserver is a second server machine with exactly the same hardware and software config-uration as the active server. The operator registers the warm standby server at the ac-tive MS CDM Server and activates the database replication mechanism of TNMS.Should a failure occur, the operator simply switches manually to the warm standby serv-er and starts the MS CDM Server process on the warm standby system.A cold standby MS CDM Netserver is also supported. The cold standby NetServer is asecond machine with exactly the same hardware and software configuration as the ac-tive NetServer. Activating a cold standby NetServer requires full DCN access at thestandby site.In both cases, the faulty system can then be repaired and implemented as the standbysystem. More information is available from Siemens Technical Sales.

11.3 Required SoftwareAll software parts mentioned in Section 11.3.1 must be released for the appropriateTNMS software version. This holds for the initial installation and for service or upgradepackage installations as well.

11.3.1 Installation SoftwareThe following software is generally required for the installation. The corresponding CDorder numbers are provided in the Multi Server CDM release documentation.

More information on the installation sequence is provided in Section 11.3.3.

1. ServerStart:If you are using the Fujitsu Siemens PRIMERGY server system, the ServerStart CDprovides the necessary utility programs and drivers for configuring and installing theserver machine. More information is provided in Section 4.2.

2. Windows 2000 Professional and Windows 2000 Server incl. Service Pack 4:The Windows 2000 Professional operating system is required for the Client and Net-

iIf additional software is installed which is not required for Multi Server CDM, correctfunctionality of Multi Server CDM cannot be guaranteed.

A42022-L5938-H52-1-76D1 85



Server machines. Windows 2000 Server must be installed on the Server machineand on the Client machine if Metaframe XP is installed on the Client machine also.Installation instructions for both operating systems are provided in Chapter 4, how-ever, pre-installed machines can also be used.

3. Windows 2000 Terminal Services:The Windows 2000 Terminal Services component must be installed on the clientmachine so that the Multi Server CDM system can be accessed remotely viaMetaFrame. More information is provided in Section 4.2.5.

4. MetaFrame XP (FR2):MetaFrame XP is used to enable remote access to the MS CDM Client and MS CDMSysAdmin software on the MS CDM Client machine. More information on installingMetaFrame XP is provided in Section 5.4.

5. Internet Explorer 6.0:This must be installed on the NetServer to enable MSN functionality, and on the cli-ent machine. If this is not already pre-installed, it can be downloaded from the Inter-net.

6. Multi Server CDM 9.0:This CD contains the following software components for installation:– Integrated Multi Server CDM software installation package:

This installation program includes the Server, NetServer, Backup Server, Clientand SysAdmin components. These can be installed either individually or togetheras required.The EML packages for USO and SNC are also available for selection during theMulti Server CDM installation. The EML packages are installed on the Server,NetServer and Client PC.More information on installing Multi Server CDM is provided in Chapter 6.

As well as the Multi Server CDM installation, the following 3rd-party softwarecomponents are also included on this CD:– Adobe Acrobat Reader:

The customer documentation for Multi Server CDM is provided in *.pdf format.The Adobe Acrobat Reader should be installed on the Server and Client ma-chines so that the documentation files can be opened.

– Microsoft Desktop Engine MSDE 2000 incl. Service Packs 2 and 3.:The MSDE is installed on the MS CDM Server. More information on installingMSDE is provided in Section 5.1. For larger configurations, however, SQL Server2000 incl. Service Packs 2 and 3 is recommended. Contact Siemens TechnicalSales for further information.

– Microsoft XML parser:The XML parser is installed on the client machine so that the Multi Server CDMsystem can support the export and import of network configuration data in XMLformat. More information on installing the XML parser is provided in Section 5.2.

– OSI stack:If QB3 is to be used, OSI stack software must be installed on NetServer PCs be-fore the NetServer software itself. More information on installing the OSI stack isprovided in Section 13.3.

Software CD Overview

The software will be delivered on CD-ROMs. Type and content of the necessary CDsdepends on the specific planned and delivered configuration. The operating system willbe delivered as part of the hardware, it is not included within the following table.

86 A42022-L5938-H52-1-76D1


Table of the deliverable CD-ROMs:– ULAF+ Library– Multi Server CDM 9.0 - Application Software– OEM Software Internet Browser

11.3.2 HW/SW configurationFig. 11.1 shows a typical configuration of a Multi Server CDM system. Limitations aregiven below. If other configurations are needed, contact Siemens Technical Sales forfurther information.

Fig. 11.1 Typical HW/SW configuration

Limitations for HW/SW configuration– The maximum number of PCs is given in Fig. 11.1.– The MS CDM SysAdmin components may be installed on the Server PC (recom-

mended) and on the Client PC(s). However, a maximum of 20 SysAdmin are al-lowed.

– The Client components must be always installed on a separate PC.

Further hints are given within the Chapters describing the installation details.

The installation sequence is described within Chapter 11.3.3. It is urgently recommend-ed to follow this instructions otherwise problems may occur during installation.

Max. 40 Client PCs

MS CDM ClientMS CDM SysAdmin

MS CDM Client(MS CDM SysAdmin)

MS CDM ServerMS CDM NetServer(MS CDM SysAdmin)

1 Server/NetServer PC

A42022-L5938-H52-1-76D1 87



11.3.3 Installation Sequence

The individual stages in the commissioning process must be logged using the formssupplied for the transfer protocol. The transfer protocol documents the completeness ofthe delivery, tests performed and the test results.


During the software installation, various versions of JRE are installed depending on thecomponents. To avoid interferences keep the following settings in mind:– JRE 1.3.1_3 is to be installed on the Server PCs.– JRE 1.4.0 is to be installed on the Client PCs.– Some components require JRE versions different from the above. However, these

are not to be installed in the default JRE directory.

Installation Sequence

The system should be commissioned as follows:

1. Set up and cable the PCs, as described in Section 11.2.1 above.2. Install the operating system and additional hardware components, and configure the

system under Windows 2000 as described in Chapter 4.3. Install the MSDE (Microsoft Desktop Engine) on the Server and Backup Server PC,

as described in Section 5.1.4. To enable import and export of XML data, install the XML parser MSXML 4.0 as de-

scribed in Section 5.2.5. If QB3 is to be used, install the OSI stack on the NetServer PCs as described in

Section13.3.6. Install the Multi Server CDM software components on the corresponding machines

as described in Chapter 6:– MS CDM Client– MS CDM Server– MS CDM Netserver– MS CDM Backup Server– MS CDM EML Packages– Additional TNMS software, such as PLET or the optional EML packages.

7. Configure the Multi Server CDM components and connect network objects as de-scribed in Chapter 15.

8. Perform system testing in accordance with the test cases described in the accep-tance test protocol. For more information, contact Siemens Technical Sales.

iBefore installing any software component, have a look at the associated readme file.Here you can find the latest informations concerning installation.The displayed screenshots within this manual are examples only and the contents maydiffer depending from the actual situation.

88 A42022-L5938-H52-1-76D1


12 Multi Server CDM: Installing the OperatingSystem

12.1 Before you BeginBefore you install Windows 2000 operating systems, complete the following steps:– If you wish to pre-install a SCSI RAID system (see Section 3.2.2), make sure the MS

CDM Server hard disks are formatted using the NTFS file system.– Check the system requirements.– Determine the licensing mode to be used.– Determine whether multiple operating systems should be offered for activation when

starting the computer.– Determine the file system to be used.– Determine the partition to be used for the installation, or if a new partition is required.– Determine the components to be installed.– Determine how the network, IP addresses and TCP/IP name management are to be

handled.– Determine the domains or workgroups for the servers, if required.– Save all data and files prior to an initial installation of Windows 2000 Server. This

does not apply if there are no files on the computer or the existing operating systemfiles are damaged. You can save the files on disk, on tape or on another computerin your network.

– Decompress all DriveSpace and DoubleSpace data carriers.– Installation may only be carried out on a compressed drive if this drive was com-

pressed with the compression program of the NTFS file system.– Disable all UPS devices.– If the target computer is fed by uninterrupted power supply (UPS), remove the serial

cable before performing the setup. Windows 2000 Setup automatically tries to iden-tify the devices at the serial interfaces. UPS might cause problems here.

Section 12.2 and Section 12.2.3 provide an overview of the installation steps for Win-dows 2000 Server and Windows 2000 Professional. Detailed information is provided inthe Microsoft Windows 2000 documentation.

12.1.1 Licensing InformationDuring installation, the system license number is requested. This is provided on the backcover of the Windows 2000 Server/Professional CD.

Windows 2000 Server provides two licensing modes:– per workplace :

Licensing per workplace requires a separate client access license for each comput-er accessing Windows 2000 Server. With a single client access license, a clientcomputer can establish connections to as many Windows 2000 Servers as required.


iThe installation sequence for all software parts is desrcibed in Section 3.3.3. The se-quence is obligatory.

A42022-L5938-H52-1-76D1 89



This licensing method should be used if you are running several Windows 2000Servers.

– per server :Licensing per server requires a client access license for every simultaneous connec-tion established to this server. This means that the corresponding Windows 2000Server supports a fixed number of client connections. There are no additional licens-es required for these computers. Per server licensing should be used if you are run-ning a single Windows 2000 Server.

If you are not sure which mode to use, use per server licensing, as it is possible to switchsubsequently from "per server" to "per workplace" licensing at no extra cost.

If you want to use terminal services both for remote administration and for an applicationserver, use "per workplace" licensing. For the Internet Connector license of the terminalservices, however, use "per server" licensing.

12.1.2 Protocol InformationTCP/IP is the standard network protocol used by Windows 2000 Server. However, if youwish, you are free to use other protocols and the corresponding network adapters.

For TCP/IP you will need one IP address for every server:– a dynamic address which is assigned by the software automatically, or– or a static address, where the address is fixed.

IP addresses are provided in the form of numbers. You can also assign a name to aserver IP address using what is known as name resolution. This enables user accessvia server names instead of via IP addresses which can be difficult to remember. Themain name resolution methods are:– DNS (Domain Naming Service) :

DNS is a distributed Internet directory service that is used mostly to translate be-tween domain names (server hosts) and IP addresses. It facilitates name resolutionfor clients under Windows 2000.

– DHCP (Dynamic Host Configuration Protocol) :DHCP allows dynamic assignment of IP addresses to network devices. These de-vices are generally servers and workstations, but other devices are also possible,e.g. printers and scanners. DHCP does not require the definition or administrationof static IP addresses, except in the case of Intranet servers which support DHCP,DNS and/or WINS.

– WINS (Windows Internet Naming Service) :WINS facilitates name resolution for clients running Windows NT and older Mi-crosoft operating systems.

12.2 Installing Windows 2000If you are using a Siemens Primergy computer as your Multi Server CDM Server, theWindows 2000 Server operating system must be installed using the ServerStart CD.

iUniGATE must not be installed on the same computer as the MS CDM Server and mustnot be run parallel in the network.

90 A42022-L5938-H52-1-76D1


12.2.1 Installing Windows 2000 Server (If SCSI RAID is Already Configured)If you have already configured a RAID system (see Section 3.2.2) including mirroreddisks and partitions on the MS CDM Server machine, proceed as follows:








8. "Installation of MS Windows 2000" window:– Select "Install Windows 2000 - Guided Mode".

9. "Installation of MS Windows 2000 (Guided Mode)" window:– Insert the floppy disk you created during step 3 into the floppy drive.– Select "Open/Create Configuration File".

10. "Open Server Start Configuration File" window:– Press the "Create" button.A ServerStart configuration file is created.

11. "Installation of MS Windows 2000 (Guided Mode)" window:– Select "System Configuration Wizard".– Select "Server Management Settings".The "SCU-Server Configuration Wizard" is started.

12. "General Server Information" window:– Accept the default settings.– Continue with "Next”.

13. "Chassis Model Configuration" window:– Accept the default settings.

A42022-L5938-H52-1-76D1 91




14. "Pager Settings" window:– Accept the default settings.– Continue with "Next”.

15. "VT 100 Settings" window:– Accept the default settings.– Continue with "Next”.

16. "Counters" window:– Accept the default settings.– Continue with "Next”.

17. "Boot and Software Watchdog Settings" window:– Accept the default settings.– Continue with "Next”.

18. "Server Display Settings (Local View)" window:– Complete your configuration with "leave wizard".

19. "Installation of MS Windows 2000 (Guided Mode)" window:– Select "RAID Wizard".

20. "RAID Wz" window:– You are asked whether you want to install on a Mylex controller.– Select "No".The "RaidWz" is started.

21. "Raid Configuration" window:– Select the automatic configuration mode for the configuration of the RAID control-

ler".– Continue with "Next".

22. "RAIDWz" message windows:– A message is displayed: "There exists already a raid-array - you must check the

’Delete existing raid-array box’ or the unattended installation will fail".– Press the "OK" button.The "RAIDWz" message window is closed.– Choose the option "Delete existing RAID Array".– Complete your configuration with "leave wizard".

23. "Installation of MS Windows 2000 (Guided Mode)" window:– Select "Disk Wizard: Hard disk partitioning and formatting".The "Disk Configuration Wizard" is started.

24. "DiskWz" message window:– A message is displayed: "There must be exactly one SYSTEM- and one WINNT-

partition (default: SYSTEM- and WINNT-partition are one and the same).– Press "Ok".

92 A42022-L5938-H52-1-76D1


25. "Disk Configuration Wizard - Disk Overview" window:Delete all existing disk partitions as instructed until the entire disk memory is shownas "unpartitioned space". The system partition should be at least 8 GB.The system partition should be at least 8 GB.– Select the first disk from the left list.– Press the "Add" button.– Press the "up" button.– Add additional disks, if there are any.The selected disk is added to the list.– Select the option "Erase all existing partitions on all displayed disks."– Complete your configuration with "leave wizard".

26. "Installation of MS Windows 2000 (Guided Mode)" window:– Select "Windows 2000 Installation Wizard".The "Windows 2000 Setup Configuration Wizard" is started.


28. "NT Setup - Computer Identification" window:– Select the option "Windows 2000 Server".– Select the option "Workgroup".




30. "User Name" window:– Enter your name and (if required) your company.– Enter the computer name. For most languages, a name of max. 15 characters

(don’t use spaces and no special characters) is recommended.– The product ID has already been entered due to your previous settings.


A42022-L5938-H52-1-76D1 93







DNS Server, and (if required) an alternative DNS Server.






35. "Installation of MS Windows 2000 (Guided Mode)" window:– Select "Application Wizard: Select Additional Software Components".The "Application Wizard" is started.

36. "Application Wizard" window:




94 A42022-L5938-H52-1-76D1


– Select the options "FSC Server View SNMP Agent" (if required) and "FSC ServerView".

– Complete your configuration with "leave wizard".

37. "Installation of MS Windows 2000 (Guided Mode)" window:– Select "Close and Save Configuration File".

38. "Save ServerStart Configuration File" window:– Insert the ServerStart floppy disk created during step 3.– Press "Save As".Once the ServerStart configuration file is saved, remove the floppy disk.

39. "Installation of MS Windows 2000 (Guided Mode)" window:– Select "Start installation of MS Windows 2000".

40. "ServerStart Unattended Mode" window:The message "unattended Setup running" is displayed.The computer restarts and the Windows 2000 installation program is continued.

41. "ServerStart" message window:– When requested to do so, insert the ServerStart floppy disk created during step

3 into the floppy drive.– Confirm with the "OK" button.






46. "Insert the MS Windows 2000 CD-ROM into the CD-ROM drive." window:– Remove the ServerStart CD from the CD-ROM drive.– Insert the MS Windows 2000 Server CD into the CD-ROM drive.– Confirm with "OK".


A42022-L5938-H52-1-76D1 95





50. The following information will now be displayed:– Windows 2000 Server Setup (blue screen).– Setup is copying files.The server restarts and the operating system loads from the hard disk. The "Win-dows 2000 Server Setup" window appears and displays the following information:– Installing Devices– Networking Settings– Installing Components– Performing Final TasksThe message "Windows 2000 has been successfully installed" is displayed.The system reboots automatically.

51. "Welcome to Windows" window:– Log in as Administrator.An installation process is automatically launched and the following window will ap-pear: "ServerStart is installing some components (SNMP AGENTS for WindowsNT/2000; FSC ServerView)"The system will reboot automatically.



54. Reactivate RAID hard disk mirroring.

12.2.2 Installing Windows 2000 Server (incl. SCSI RAID Configuration)If you have not yet configured a RAID system with mirrored disks and partitions,(see Section 3.2.2) Windows 2000 Server should be installed as follows:




4. "Server Start" window:"Please select your keyboard."

96 A42022-L5938-H52-1-76D1


– Select a suitable keyboard layout.





9. "Installation of MS Windows 2000 (Expert Mode)" window:– Select "Configure your Adaptec/DPT RAID System" for the RAID controller instal-

lation.10. "Adaptec Storage Manager - SERVERSTART" window:

– Select "Create Array Group".

11. "Select Array Type" window:– In "Fault Tolerance" options, select "Drive Fault Tolerance".– In "Chosen Array Parameters", select "Override" and "RAID LEVEL 1 Stripe Size:

None".– Confirm with "Accept".– In "Optimization" options, select "Optimize for Performance".– Press "Continue".

– Select both HD icons with the mouse. If either of the HDs has a valid partition ta-ble, the "Adaptec Storage Manager" window appears with a corresponding mes-sage.

– Select "Yes".Both HDs are shown with a green tick.

– Click on "Include Drive". Both HDs must be assigned a RAID DISK icon, i.e. aRAID1 icon must be displayed with a line pointing to each HD.

– Review the configuration and select "Done".– Confirm the following warning messages with "OK".Two black flags appear, one above the LSU icon and another above the RAID1 icon.

– In the menu bar, select File -> Set System Configuration.A warning message appears: "This will change your system configuration. Data onany arrays that you have removed or modified will be lost...".– Press "OK".

12. "Please Choose Direction" window:– Select HBA 0 BUS 0 ID 0 -> HBA 0 BUS 0 ID 1

A42022-L5938-H52-1-76D1 97



– Press "Start Copy".The black flags turn blue, and a white flag appears on each target SCSI disk.

The "Array Group Information" window appears with a status field informing youabout installation progress.– Wait until formatting has been completed and the array group has been created,

i.e. when the status field shows "optimal".– Exit the "Adaptec Storage Manager".– Reboot the system.






18. "Installation of Windows 2000 (Expert Mode)" window:– Select "Use Disk Administrator to Partition and format your disk drives".

19. "Disk Administrator" window:– Select "Disk 1"– Create a primary partition (maximum size = 8 GB).– Press "Commit changes now".– Format the partition with the parameters unknown capacity, NTFS, default alloca-

tion size, and quick format.– Exit "Disk Administrator".

20. "Installation of Windows 2000 (Expert Mode)" window:– Select "Run Windows 2000 Installation Wizard".

21. "Server Start" window:A message is displayed: "Do you want to specify an existing configuration file to pre-set the parameters for the Operating System Wizard and the Application Wizard?"– Select "No".

22. "NT Setup - Windows 2000 Installation" window:

iThis operation can take up to two hours.

98 A42022-L5938-H52-1-76D1


– In "Installation Drive" parameters, select the option "Use default".– In "Installation Drive" parameters, select the option "Convert file system to NTFS".– Select a suitable keyboard layout.– Do not enter a "Password for Administrator account".– Enter the product ID provided on the back cover of the Windows 2000 CD.– Continue with "Next”.

23. "NT Setup - Computer Identification" window:– Select the option "Windows 2000 Server".– Select the option "Workgroup" or "Domain".




25. "User Name" window:– Enter your name and (if required) your company.– Enter the computer name. For most languages a name of max. 15 characters is

recommended.– The product ID has already been filled in due to your previous settings.– Continue with "Next”.



gateway, if required.


A42022-L5938-H52-1-76D1 99



– In the "DNS/WINS Configuration..." option, enter the addresses of the preferredDNS Server, and (optionally) an alternative DNS Server.






30. "Installation of MS Windows 2000 (Expert Mode)" window:– Select "Application Wizard: Select Additional Software Components".The "Application Wizard" is started.



32. "Installation of MS Windows 2000 (Expert Mode)" window:– Select "Start installation of MS Windows 2000".


34. "ServerStart" window:– A message informs you about SCSI controllers on your system.




100 A42022-L5938-H52-1-76D1


– Confirm with "OK".




37. "Insert the MS Windows 2000 CD-ROM into the CD-ROM drive." window:– Remove the ServerStart CD from the CD-ROM drive.– Insert the MS Windows 2000 Server CD into the CD-ROM drive.– Complete your configuration with "OK".




41. This following information will now be displayed:– Windows 2000 Server Setup (blue screen).– Setup is copying files.The server restarts and the operating system loads from the hard disk. The "Win-dows 2000 Server Setup window appears and displays the following information:– Installing Devices– Networking Settings– Installing Components– Performing Final TasksThe message "Windows 2000 has been successfully installed" is displayed.The system reboots automatically.

42. "Welcome to Windows" window:– Log in as Administrator.An installation process is automatically launched and the following window will ap-pear: "ServerStart is installing some components (SNMP AGENTS for WindowsNT/2000; FSC ServerView)".The system will reboot automatically.



A42022-L5938-H52-1-76D1 101



12.2.3 Installing Windows 2000 ProfessionalOn the Client and NetServer computers, the operating system Windows 2000 Profes-sional is installed using the Windows 2000 Professional CD. During installation, the sys-tem license number is requested. This is provided on the back cover of the CD.

Proceed the installation as follows:

1. Insert the Windows 2000 Professional CD into the CD-ROM drive.

2. Reboot the PC from the CD.A blue screen informs you that the Windows 2000 setup has started.

3. "Welcome to Setup" window:– Select "To set up Windows 2000 now press ENTER."– Press Enter.

4. "Windows 2000 Licensing Agreement" window:– Read the license agreement.– Press "F8" to agree.

5. If Windows NT 4.0 or 2000 is already installed, you will be notified.– Choose "Fresh Copy", i.e. new installation.– Press "ESC".

6. If there is no partition on your system, create one:– Choose as size at least 1 GB (recommended whole hard disk, max. 8 GB).

7. Install Windows 2000 on highlighted partition, i.e. system partition "C":– Press "Enter" to confirm.If one partition exists, there will be a warning.– Press "C" to continue.

8. Format the partition using "NTFS file system".

9. Confirm the question about formatting.– Press "F" to format the partition.Now, message windows inform you that the partition is formatted, files are copied tothe installation folders, and setup is initialized.The computer is rebooted automatically.

10. "Welcome to the Windows 2000 Setup Wizard" window:– Continue with "Next".

11. "Windows 2000 Professional Setup" window:Wait until the devices are installed.

12. "Regional Settings" window:– Select the default settings or choose your configuration.

iIf MetaFrame XP is to be installed on the Client PC, you must install Windows 2000Server operating system. In this case, the Windows components "Terminal Services"and "Terminal Services Licensing" should also be installed.

102 A42022-L5938-H52-1-76D1


– Continue with "Next".

13. "Personalize Your Software" window:– Enter you name and your company.– Continue with "Next".

14. "Your Product Key" window:– Enter the product ID from the back cover of the Windows 2000 CD.– Continue with "Next".

15. "Computer Name and Administrator Password" window:– Enter the name of your computer (don’t use spaces and no special characters).– Enter a password.– Re-enter the password in the field "confirm password"– Continue with "Next".

16. "Date and Time Settings" window:– Change the date, time and time zone, if required.– Specify whether changing from summer time to winter time automatically.– Continue with "Next".

17. "Networking Settings" window:– Select "Typical Settings".– Continue with "Next".Wait while Windows installs networking components.

18. "Workgroup or Computer Domain" window:– Depending on your network topology, select workgroup or domain. If in doubt, ask

your system administrator.– Continue with "Next".A Setup Status window informs you about the installation progress.

19. "Performing Final Tasks" window:A message window informs you about the final installation operations.

20. "Completing the Windows 2000 Setup Wizard" window:A message is displayed, informing you that Windows 2000 has been successfullyinstalled".– Remove any CDs from your drive.– Confirm with "Finish".The computer is rebooted automatically.

21. "Welcome to Network Identification Wizard" window:– Continue with "Next".

22. "Users of This Computer" window:– Select "Users must enter a username and password to use this computer."– Continue with "Next".

23. "Completing the Network Identification Wizard" window:

A42022-L5938-H52-1-76D1 103



– Continue with "Finish".

24. "Log On to Windows" window:– Log in as Administrator.The Windows 2000 Professional installation is completed.

25. Install Service Pack 4 for Windows 2000.

12.2.4 Installing Windows 2000 Service Pack 4

Once the installation is complete, install Service Pack 4 as follows:– Create an Un-Installation directory: No– Accept the license agreement.

12.2.5 Installing Windows 2000 Server Terminal ServicesThe Windows 2000 Server Terminal Services installation is performed the same way asthe standard installation. To facilitate installation, the first partition must have at least 3GB or the hard disk must not be partitioned at all. More information is provided in theMicrosoft Windows 2000 Server Terminal Services documentation.

In order to install Windows 2000 Server Terminal Services, proceed as follows:– Open Start -> Settings -> Control Panel -> Add/Remove Programs -> Add/Remove

Windows Components.– Select "Terminal Services & Terminal Services License Pack".– Select the option "Application Server Mode" (runs for 90 days).– Reboot your computer.

12.3 Hardware Configuration under Windows 2000Once Windows 2000 has been installed, all additional hardware and software compo-nents must be configured/installed under Windows 2000.

This includes:– Graphics cards: Set the font size to "Small Fonts": Start -> Settings -> Control Panel:

Double click on "Display", the "Display Properties Window" opens; press button "Ad-vanced" choose tab "Common" and set the value "Display/Font Size" to "SmallFonts". Restart the computer if necessary.

– Printers– Modems (remote login)– UPS

Installation should be completed in accordance with the relevant installation instructions.

iIf required, decompress the Service Pack to a temporary folder.

iIf the Windows 2000 configuration (e.g. the printer configuration) is modified, ServicePack 4 must be installed again.

104 A42022-L5938-H52-1-76D1


12.3.1 Installing the PCI I/O CardThe PCI I/O card is installed on the MS CDM Client PC and enables external signaling.

– Switch off the PC and disconnect it from the power supply.– Open the PC.– Insert the PCI I/O card into a free slot.– Close the PC.– Switch on the PC.– Install suitable drivers by double-clicking the Setup.exe file on the floppy disk sup-

plied.– Start the MS CDM Client after installing the drivers.

More information is provided in the I/O card documentation.

iBefore opening the antistatic envelope, make sure you are familiar with the regulationsfor electrostatic-sensitive devices (ESD) provided in Chapter 2.

A42022-L5938-H52-1-76D1 105



106 A42022-L5938-H52-1-76D1


13 Multi Server CDM: Prerequisites and3rd-Party Software

This chapter gives installation descriptions for the necessary software to be installed pri-or to TNMS Core and its additional components.

13.1 Installing MSDEMSDE SP3 (Microsoft SQL Desktop Engine) must be installed directly on the Server PC.To install MSDE, double-click the "setup.bat” file in the MSDE directory on the TNMSCore 9.0 software CD.

The program installs MSDE on the computer. No additional input is required.

Reboot your computer to complete the installation.

Uninstalling MSDE

In order to uninstall the MSDE, open Start -> Settings -> Control Panel -> Add/RemovePrograms:– Select the MSDE from the software list.– Click the "Change/Remove” button.– Select the "Remove” option.– Confirm the uninstall process with "Finish” and restart your computer.

13.2 Installing MSXML 4.0MSXML 4.0 is an XML parser. It must be installed on the system so that network config-uration data can be imported and exported in XML format.

As a prerequisite, the Windows Installer 2.0 has to be installed. To do this, double-clickthe "InstMsiW.exe” file in the MSI2.0 directory on the TNMS Core 9.0 software CD andfollow the instructions. After installation, reboot the PC.

To install MSXML 4.0, proceed as follows:

1. Reboot the PC (if not already done, see above).

2. Double-click the "msxml4.msi” file in the MSXML directory on the TNMS Core 9.0software CD.


4. In the "End-User License Agreement” window, accept the terms of the licenseagreement, and press "Next” to continue.




A42022-L5938-H52-1-76D1 107



6. In the ”Choose Setup Type” window, press "Install Now”.

7. The window "Installing Microsoft XML Parser and SDK” window is now displayed.The progress of the installation is indicated by the progress bar.

8. Once the installation is complete, the window "Completing the Microsoft XML Parserand SDK Setup Wizard” is displayed. Press "Finish” to complete the installation.

Uninstalling MSXML

In order to uninstall the MSXML, open Start -> Settings -> Control Panel -> Add/RemovePrograms:– Select the MSXML from the software list.– Click the "Change/Remove” button.– Select the "Remove” option.– Confirm the uninstall process with "Finish” and restart your computer.

13.3 Installing an OSI StackIf QB3 is used, an OSI stack must be installed on the NetServer PCs before the Net-Server software.

To install an OSI stack, proceed as follows:

1. To install an OSI stack, double-click the file "setup.exe” in the OsiStack directory onthe TNMS Core 9.0 software CD.


3. In the "Choose Destination Location" window which is now displayed, a default in-stallation directory is offered for the OSI stack. Press "Next” to continue.

4. In the "Please select:" window, select the NSAP address option best suited to yourcompany’s network and press "Next”.

5. In the "Getting NSAP" window, enter the local NSAP address and press "Next”.


7. A setup status window is now displayed, showing the progress of the OSI stack in-stallation.

8. In the ”InstallShield Wizard Complete” window select the option for restarting thecomputer and press “Finish” to complete the OSI stack installation.

Once the computer has rebooted, open the OSI stack via Start -> Settings -> ControlPanel -> OSI Stack.You can now check the OSI stack settings as follows:– Note the settings of the ES-IS and IS-IS parameters (the IS-IS parameters can be

displayed by pressing Ctrl + I).

108 A42022-L5938-H52-1-76D1


– Set the value for "Number of Channels and Ctx” to greater than/equal to 140. Thisis the number of OSI stack connections which can be established simultaneously.The recommended value is 500.

– Note the network interface card to which the OSI is connected and check this againstthe LAN card settings in the Control Panel.

– Activate the options "Open Stack, when Operator starts” and "Start stack as ser-vice".

Uninstalling OSI stack

In order to uninstall the OSI stack, open Start -> Settings -> Control Panel -> Add/Re-move Programs:– Select the OSI stack from the software list.– Click the "Change/Remove” button.– Select the "Remove” option.– Confirm the uninstall process with "Finish” and restart your computer.

13.4 Citrix MetaFrameMetaFrame XP is used to enable remote access to specific software applications on anetworked computer.In this case, MetaFrame XP is used to provide remote access to the TNMS Client andTNMS SysAdmin software on the TNMS Client machine.MetaFrame XP comprises server software (on the Server CD) and ICA Client software(on the Component CD). The server software is installed on the TNMS Client machineand the ICA Client software on the remote PC.The TNMS Client machine is therefore considered a "MetaFrame Server", and the re-mote PC is considered a "MetaFrame Client".

In other words you must install the MetaFrame Server first, then enter the correspondinglicenses, and then publish the required applications. Only when these steps have beencompleted can you install the MetaFrame Client and configure the ICA Client connec-tion.

13.4.1 System RequirementsThe MetaFrame Server (TNMS Client machine) must meet the following requirements:– 400 MB disk space for MetaFrame XP– 50 MB disk space for the Citrix Management Console– Windows 2000 Server + Service Pack 4– The Windows components "Terminal Services" and "Terminal Services Licensing"

must be installed in Application Server mode. Permissions must be compatible withTerminal Server 4.0 users.

– The Windows 2000 Server component "Internet Information Services" should not beinstalled.

– Windows Installer Version 2.0 must be installed (do not use the Windows Installer1.1 which is included with Windows 2000 Server).

– If installed, Java Runtime Environment 1.3.1 should be deinstalled. Java RuntimeEnvironment 1.3.0 is automatically installed with the Citrix Management Console.

iWhen installing the MetaFrame XP software, you must follow the installation sequencedescribed below.

A42022-L5938-H52-1-76D1 109



The MetaFrame Client PC can be any PC in the network, however, it must meet the fol-lowing requirement:– 250 MB disk space for ICA Client software.


As MetaFrame is to be installed prior to Multi Server CDM, two JRE versions are in-stalled on the Client PCs:– JRE 1.3.0 for MetaFrame– JRE 1.4.0 for Multi Server CDM

13.4.2 Installing the MetaFrame ServerBefore you begin:– Check which Windows Installer version is installed using the command "msiexec" in

the DOS command prompt window. Windows Installer Version 2.0 is included on theMetaFrame XP Server CD (folder ..\MSI2.0; for installing click “InstMsiW.exe).

– Ensure you are logged in with administrator rights.

Once you have completed the steps above, proceed as follows to install MetaFrame XP:

1. At the TNMS Client machine, insert the MetaFrame XP Server CD.

2. In the window which appears, select "Install or update MetaFrame".

3. In the window which appears, select "MetaFrame XP Service Pack 4".

4. In the window "Welcome to the Citrix MetaFrame XP for Windows Installation Wiz-ard", press "Next".


6. In the "Product Family Selection" window, select "MetaFrame XPs" and press "Next".

7. In the "Select Product Type" window, select "Retail" and press "Next".

8. In the "Component Selection" window, select MetaFrame XP + Citrix ManagementConsole. Accept the default directory (C:\Program Files\Citrix\) by pressing "Next".

9. In the "Create or Join a Server Farm" window, select "Create a new farm" and press"Next".

10. In the "Create a Server Farm" window, enter an appropriate "Farm Name", select"Use a local database (Microsoft Access) on this server" and "Use Default ZoneName", and press "Next".

iWhen you insert the Server CD (see instructions below), you can obtain more informa-tion by clicking "View installation checklist".

!Do not install Citrix MetaFrame after Multi Server CDM! The Java application will be re-placed and Multi Server CDM will be inoperable.

110 A42022-L5938-H52-1-76D1


11. In the "Assign Farm Administrator Credentials" window, enter an appropriate "UserName" (e.g. TNMS) and "Domain" description for the local domain of the MetaFrameserver host (e.g. PC170). Press "Next".

12. In the "Configure shadowing" window, select "Prohibit shadowing of ICA sessions onthis server" and press "Next".

13. In the "Configure Citrix XML Service Port" window, enter the default value "80" andpress "Next".

14. In the window "Review your selections listed below", ensure that the data shown iscorrect, and press "Finish" to complete this section of the installation.In the windows which follow, the progress of the installation is indicated by progressbars.

15. When installation has been completed, the window "Citrix MetaFrame XP for Win-dows, Feature Release 2 has been successfully installed" is displayed.Ensure the options "Launching the ICA Client Distribution wizard" and "View the Re-adme file" are not selected and close this window by pressing "Close".

16. A command prompt appears asking whether you wish to restart the computer -press "Yes".

Entering Licenses For MetaFrame

Once the MetaFrame Server (TNMS Client machine) has been restarted, you can enterlicensing information as follows:

1. Go to the ICA Administrator toolbar which is now visible on the screen, and pressthe button for the Citrix Management Console (this is the last button in the toolbar).

2. In the "Pass-through Authentication" window, select "Enable pass-through authenti-cation" and "Connect to this server" and press "OK".

3. The Citrix Management Console is now shown for the MetaFrame Server farm youhave just configured. In the tree view to the left of the console, right-click "Licenses"and select the option "Add License..." from the context menu which appears.

4. In the "Add License" dialog, enter the serial number of the server license and press"OK".

5. In the tree view, right-click the "Licenses" option again, select "Add License...", andin the "Add License" dialog, enter the license number for the ICA Client connection.

6. Once you have entered both licenses in this way, a command prompt appears ask-ing you whether you wish to activate your licenses at this time - press "No".You have a grace period of 35 days before the licenses must be activated.

More information on activating licenses is contained in the instruction booklet providedwith the MetaFrame CDs.

A42022-L5938-H52-1-76D1 111



Publishing Applications

The applications which the remote MetaFrame Client PC is permitted to access (e.g.TNMS Client or TNMS SysAdmin) can be specified on the MetaFrame Server as fol-lows:

1. In the Citrix Management Console, go to the main menu bar and select "Actions" ->"New" -> "Published Application".

2. In the window "Welcome to the Application Publishing Wizard", enter a "DisplayName" for the selected application (e.g. TNMS Client) together with an "ApplicationDescription" and press "Next".

3. In the "Specify What to Publish" window, select "Application". Specify the "Com-mand Line" by browsing to the installation directory for the relevant application andselecting the *.exe file for the application e.g. C:\Program Files\Sie-mens\TNMS\Bin\tnClient.EXE. You can also specify a "Working Directory" e.g.C:\Program Files\Siemens\TNMS\Bin. Press "Next" continue.

4. In the "Program Neighborhood Settings" window, enter a "Program NeighborhoodFolder" e.g. TNMS, and without activating either of the shortcut options, press"Next".

5. In the "Specify Application Appearance" window, set the "Session Window Size" to1024x768, and set the "Colors" to "True Color (24 bit)". Select "Maximize applicationat startup" and press "Next".

6. In the "Specify ICA Client Requirements" window, select "Enable Audio", set "En-cryption" to "Basic" and press "Next".

7. In the "Specify Servers" window, select the name of the MetaFrame Server comput-er from the "Available Servers" list. Press "Add" to add this server to the "ConfiguredServers" list, and press "Next" to continue.

8. In the "Specify Users" window, select the server name from the "Look in" field, selectthe "Show users" option, and select the appropriate user from the list provided. Thisuser will be the user entered during the MetaFrame server installation, e.g. TNMS.Once you have selected the user, press "Add" to add this user to the "ConfiguredAccounts". Press "Finish" to complete publishing for this application.

9. In the Citrix Management Console, you can now see the published application in thetree view under "Applications".

13.4.3 Installing the MetaFrame ClientThe MetaFrame Client PC can be any PC in the network. It can be configured as follows:

1. At the selected PC, insert the Citrix MetaFrame XP "Component" CD.

2. In the "Citrix MetaFrame XP Components" window, select "Citrix ICA Clients".

112 A42022-L5938-H52-1-76D1


3. In the "Citrix ICA Clients" window, select "Citrix Program Neighborhood".

4. In the window "Welcome to the Citrix ICA Client Installation Wizard", press "Next".


6. In the "Destination Folder" window, accept the default directory (C:\ProgramFiles\Citrix\ICA Client\) by pressing "Next.

7. In the "Select Program Folder" window, enter "Citrix ICA Client" and press "Next".

8. In the "ICA Client Name" window, enter a name for the client PC, e.g. pc109, andpress "Next".

9. In the "Select Desired Features" window, select "No" and press "Next".

10. In the window "Ready to Install the Application", press "Next" to begin installation. Aprogress bar is now shown indicating the progress of the installation.

11. In the window "Citrix ICA Client has been successfully installed" click "Finish" tocomplete the installation.

Configuring the ICA Client Connection

Once the MetaFrame Client has been installed, access to applications published on theMetaFrame Server can be configured as follows:

1. Double-click the "Citrix Program Neighborhood" icon which is now provided on thedesktop of the MetaFrame Client PC.

2. In the Citrix Program Neighborhood, double-click "Find New Application Set".

3. In the "Find New Application Set" window, select "Local Area Network" and press"Next".

4. In the window which appears, enter a description for the new application set, andselect the server where the application is installed from the dropdown list "Click be-low to locate the Application Set to add". Press "Next" to continue.

5. In the window which appears, select "Use Server Default" for the "Window Colors",and for the "Window Size", select "Seamless Window". Press "Next" to continue.

6. In the "Program ICA Neighborhood" window, enter the user name for the MetaFrameServer as specified during MetaFrame Server installation (e.g. TNMS). Enter theMetaFrame Server domain as specified during MetaFrame Server installation (e.g.PC170). Finally, specify a password, and press "OK".

7. Press "Finish" to complete the connection configuration.

A42022-L5938-H52-1-76D1 113



8. In the Citrix Program Neighborhood, a folder is now displayed for the published ap-plication, e.g. TNMS.

To open the application, proceed as follows:– Double-click the folder to access the program icon. Double-click the program icon,

confirm any messages with "OK". The published software application is now avail-able for use.

This file describes the most important steps in installing MetaFrame XP. Should you re-quire more detailed information, product-specific documentation is provided on theMetaFrame Server CD in the directory "\DOCS".

The Administrator’s Guide to Citrix MetaFrame XP (MetaFrame_XP_Guide.pdf) is par-ticularly useful.

114 A42022-L5938-H52-1-76D1


14 Multi Server CDM: Installing the Multi ServerCDM Software

14.1 Before You BeginBefore installing Multi Server CDM, note the following information:– Before installing the software, all previous versions must be uninstalled.– The integrated Multi Server CDM 9.0 software installation consists of the Server,

NetServer, Backup Server, Client, SysAdmin and EML components.– The Server and NetServer components may be installed on the same (medium con-

figuration) or on separate PCs (large configuration).– The Client software has to be installed on a separate PC.– The SysAdmin software can be installed on any PC in addition to any other Multi

Server CDM component.– The EML packages are installed on the Server, NetServer and Client PC.– To support distributed operation of the network, up to 40 MS CDM Clients can be

managed simultaneously.– Depending on the number of the network elements, up to 10 NetServer PCs can be

managed simultaneously.– The Server must be installed on the server PC. Depending on the security concept,

the SysAdmin software can also be installed on the Server PC with an additionalmonitor where possible. This enables administration of the Multi Server CDM sys-tem to continue uninterrupted, even if the data flow between the Client and ServerPC is disrupted.

– If one or more PCs in the Multi Server CDM system are equipped with two networkadapters, routing settings must be configured as specified in Section15.3 to avoiddelays during connection setup between PCs.

– To avoid problems during the Multi Server CDM installation, the user must be loggedinto the Windows 2000 operating system with administrator rights.

14.2 Installing Multi Server CDMTo install Multi Server CDM, proceed as follows:

1. Double-click the file "setup.exe” provided on the Multi Server CDM software CD. Awelcome window appear, press “Next” to continue.

2. In the "License Agreement" window, read the agreement and accept it by pressing"Yes".



iThe installation sequence for all software parts is described in Section 3.3.3. This se-quence is obligatory.

A42022-L5938-H52-1-76D1 115



4. In the "Choose Destination Location” window, a default installation directory is of-fered. Click the “Browse” button to choose another directory and press "Next” to con-tinue.

5. In the "Select TNMS Core Components" window, select the components you wishto install. In this window, you can install the Server, NetServer, BackupServer, Client,and SysAdmin components either together or individually as required (see Section15.1 for details).

Fig. 14.1 Select TNMS Core Components Window

6. In the "Location of Server Database Files", a default installation directory is offered.Click the “Browse” button to choose another directory and press "Next” to continue.

7. In the "Location of Database Backup Files", a default installation directory is offered.Click the “Browse” button to choose another directory and press "Next” to continue.

8. In the "Select Program Folder” window, a default program folder is offered. Press"Next” to continue. The system now registers additional installation packages.

iStep 6. is only performed when installing the Server. If you did not choose to install thiscomponent, continue with step 7.

iStep 7. will only be performed when installing the Backup Server. If you did not chooseto install one of this component, please continue with step 8.

116 A42022-L5938-H52-1-76D1


9. In the "Select the required EML packages" window you can select the required EMLcomponents for installation. Press “Next” to continue.

Fig. 14.2 Select the Required EML Packages Window

10. In the "Select the required interface packages" window you can select the requiredinterface packages for installation: SNMP Proxy, TCOA Proxy G7 and/or TCOAProxy TMF. Then press “Next” to continue.

Fig. 14.3 Select the Required Interface Packages Window

11. The “Start Copying Files” window shows all software components to be installed.Press “Next” to continue.

A42022-L5938-H52-1-76D1 117



12. Now, you will be asked whether to install the JRE.– If you do not have JRE installed on your computer, install it now.– If you have JRE already installed, but it is an older version, install this version now

and confirm the deinstallation of the older one.– If you have the latest JRE version installed, do not install this one.

During the JRE installation you will be asked to specify the used browser. Select “Mi-crosoft Internet Explorer”.

13. The "Setup Status” window which is now displayed indicates the progress of the in-stallation. Various system messages are also output during this part of the installa-tion, for example indicating that LCTs are being installed.This part of the installation could take some time.

14. Once all system components are installed, the "InstallShield Wizard Complete" win-dow is displayed. Select the option for restarting the computer, and press "Finish” tocomplete the installation.

The computer is rebooted and the installation completed.

Subsequent configuration settings are described in Chapter 15.

14.2.1 Deinstalling Multi Server CDMThe TNMSCDM software can be deinstalled using the Windows 2000 control panel. Thefollowing information is removed during deinstallation:– All information used by the Multi Server CDM application from the Windows 2000

Registry.– All program files of the Multi Server CDM components.– All empty Multi Server CDM component directories.– The Multi Server CDM database.

Shared files such as OLE-Dlls are not removed.

Before uninstalling TNMSCDM software, complete the following steps:

1. Create a backup of the current Multi Server CDM database. Do not use the defaultbackup path as the installation folder will be removed during the uninstall procedureif not explicitly prohibited by the operator.

2. Store the local NSAP address of the Server in a text file.

3. Close all element managers which are open.

4. Close any TNMS Client sessions which are open.

5. Log off the TNMS SysAdmin software from the server, and exit SysAdmin.

6. Stop all TNMS services on the Server and NetServer underStart -> Settings -> Control Panel -> Administrative Tools -> Services.The following services are possible:

!Make sure that you do not have two JRE versions installed on your computer.

118 A42022-L5938-H52-1-76D1


TNMS Backup Server, TNMS Data Provider, TNMS NetServer, TNMS Telecommu-nication Network Management System.You should also check the Windows Task Manager for running services and endthese processes where possible.

The software can now be deinstalled as follows:

1. Open the "Add/Remove Programs" window via Start -> Settings -> Control Panel->Add/Remove Programs.

2. Select TNMS Core V... and press “Change/Remove”

3. The preconditions for deinstalling are checked and a welcome window is displayed.Select "Remove” and press "Next” to continue.

4. In the "Confirm File Deletion” window, press OK to activate deinstallation. The dein-stallation starts and information windows displays the software parts, which are cur-rently deinstalled. This will take some minutes.

5. Depending on the programs that have been installed you may be prompted to con-firm the deletion of further files.

6. You will also be asked whether you wish to delete the directory containing your back-up files:– If you have stored the backup files in the default directory, i.e.

"C:\Program Files\Siemens\TNMS\data\Archive”, do not delete the directory.– If you have stored the backup files in a different directory, you may delete the de-

fault directory.

7. The "Maintenance Complete” window is now displayed. If certain folders could notbe deleted, this is indicated here. Press "Finish" to complete the deinstallation pro-cess.

8. Restart the PC.

9. Delete any remaining folders manually in the Windows Explorer e.g.C:\Program files\Siemens\TNMS\Data, C:\Program files\Siemens\TNMS, C:\Pro-gram files\Siemens.

10. Check that the TNMS services listed above are removed from the services list.

14.2.2 Adding and removing individual Multi Server CDM ComponentsIf individual Multi Server CDM components (e.g. specific EML packages) are to be in-stalled or removed, proceed as follows:

1. Insert the installation CD-ROM into the CD-ROM drive.

2. Logoff and exit all client machines.

A42022-L5938-H52-1-76D1 119



3. Stop the Server using SysAdmin.

4. Logoff and exit SysAdmin.

5. If necessary, close all other active applications.


7. Start the installation/deinstallation procedure via Start -> Settings -> Control Panel-> Add/Remove Programs. Select "TNMS" and click the "Change/Remove" button.

8. In the "Welcome” window, select the "Modify".

9. In the Select TNMS core components" window, the components already installedare displayed. Select the components you wish to install or uninstall and press"Next” to continue.

10. In the "Select the required EML packages” window, select the components you wishto install or deinstall, and press "Next” to continue.

11. The "Setup Status” window which is now displayed indicates the progress of the pro-cedure.

12. Once the selected components are installed or deinstalled, the "Maintenance Com-plete" window is displayed. Select the option for restarting the computer, and press"Finish” to complete the process.

13. Restart the PC to update your installation.

iIf the QB3M service is running while the OSI stack service is being closed down, youare also asked to close the QB3M service.

120 A42022-L5938-H52-1-76D1


15 Multi Server CDM: Measures afterCommissioning

After the Multi Server CDM software and relevant 3rd-party software has been installed,the Multi Server CDM installation must be configured using the SysAdmin application.

15.1 Initial Configuration of Multi Server CDM Using SysAdminOnce the Multi Server CDM software has been installed, and the computer restarted,the Multi Server CDM system can be configured. The main steps to be completed duringconfiguration are listed below. Additional information is provided in the online help under"Initial configuration - Multi Server CDM”. This section of the help also provides links todetailed instructions for each step to be completed.

1. Start SysAdmin

Start the MS CDM SysAdmin interface via "Start” -> "Programs” -> "TNMS 9.0” -> "Sys-tem Administration”.

2. Logon

Log onto MS CDM SysAdmin via the displayed logon dialog.

Fig. 15.1 TNMS SysAdmin Logon window

– In the field "Server", enter the name of the PC where the MS CDM Server is in-stalled. If you are logging in directly to the PC where the MS CDM Server is installed,enter ".".

– In the field "User name" enter the default value "Administrator". This account is cre-ated automatically during the installation of Multi Server CDM.

– When you log on for the first time, the field "Password" does not have to be complet-ed.

– After confirming the entry via the "Logon” button, change the password for the de-fault administrator account as requested.


iThe Multi Server CDM Server is still deactivated at this time.Do not activate it until step 6 below has been completed.

A42022-L5938-H52-1-76D1 121



3. Configure user accounts

A default administrator account is created during installation. Additional accounts cannow be created as required. Global account settings can also be edited at any time.

4. Check license availability

First of all, enter the Basic License via TNMS SysAdmin to be able to start the Server.Then check whether licenses are available for the required range of functions and addthem.

5. Define log configuration settings

You can determine the available size of the various log files on the hard disk. Settingscan be entered for the size of the alarm log, system message log, network event log,security event log and custom log. Performance logs can only be created if sufficientspace is reserved for custom logs.

All log files are installed in the directory <TNMS installation path> ..\Logs. On the HDpartition where the TNMS is installed there should be at least 1 GB free disk space dur-ing operation. If the log file size will be changed (expanded) check the necessary diskspace again.

6. Configure database backup options

In Multi Server CDM, you can choose whether to schedule an automatic backup or toimplement a manual backup. Settings are provided for the backup host, backup file pathname and for the time and frequency of archiving in SysAdmin.

7. Start the MS CDM Server

In order to configure DCN objects and to set cost factors for automatic routing, you muststart the MS CDM Server. Press the “Start Server” button in the SysAdmin toolbar andconfirm with “OK”.

8. Add NetServers

After Multi Server CDM installation, the NetServer computers must be linked up to theMulti Server CDM via the "DCN Management” dialog.

9. Configure and activate DCN channels

DCN channels are also configured in the "DCN Management” dialog. Once configured,the channel settings should be checked, e.g. for scheduling communication.

10. Configure subnetworks

You can now add the required subnetworks by right-clicking relevant the DCN channeland selecting the "Add” option. Both TNMS Core and 3rd-party (USO) subnetworks aresupported.

iThe OSILLC protocol driver must not run on more than one ethernet card. The drivershould therefore be disabled on any other cards using Start -> Settings -> Control Panel-> Network -> "Network and Dial-up connections” tab on the NetServer PC.

122 A42022-L5938-H52-1-76D1


11. Configure the SNMP proxy

If the SNMP Proxy has been installed, you can now enter configuration data for it. Then,activate and start SNMP Proxy.

13. Synchronize the computer date and time

For event logging, all Multi Server CDM computers have to have the same settings. Forthis purpose, date and time are to be taken from the server for the other computers. Theclients also have to forward these settings to the network elements.

14. Start the TNMS Client

The login procedure is the same as for "SysAdmin", however, you must log in using thenew Administrator password that you configured when you logged onto SysAdmin forthe first time.

15. Create the Network Plan

The network plan can now be created using TNMS Client. This must be done on the ba-sis of planning data (when installing the system the first time) or by migration of dataused in formerly software versions (in case of software updates).

16. Further settings

Further setting can be done depending on the individual customers needs (e.g. alarmsettings: alarm messenger, color settings).

15.2 MigrationMulti Server CDM 9.0 supports migration of data from Multi Server CDM 8.5. For datamigration it is recommended to install the version 9.0 software “parallely” on a separatesystem and connect it to the same LAN for easy data transfer between the two systems.

The migration procedure is supported by a so called “Migration Wizard”. It will be acti-vated automatically if you try to restore a 8.5 version database in a TMNS CDM 9.0 sys-tem.

Further information about migration is given within the Operator Guidelines OGL and theOnline Help.

15.3 Routing Settings for PCs with Multiple Network AdaptersIf one or more PCs in your Multi Server CDM system have multiple network adapters(for networking protocols in addition to TCP/IP), delays may occur in connection setupbetween the various Multi Server CDM machines.

For example:– Computer A has one network adapter (for the LAN segment to computer B)

iOnce you have configured NetServers, DCN channels and subnetworks (steps 8-10),the status of these objects is shown in the "DCN Management” window.

iWhen installing the new system, keep in mind that Server and Backup Server have tobe instaled on the same machine.

A42022-L5938-H52-1-76D1 123



– Computer B has two network adapters (one for the LAN segment to computer A andone for an external LAN segment)

Because computer B has two network adapters, it also has two IP addresses.When establishing communication with computer A, computer B transmits both IP ad-dresses. If the first IP address sent by computer B is the address for the common LANsegment, communication can be established without any problems. But if the first IP ad-dress sent by computer B is the address for the external LAN segment, and a gatewaycomputer with routing information is not available, timeout cycles will result in delayedcommunication.

The following connections may then be affected:

The problem can be solved by defining the sequence in which IP address information istransmitted in the network settings for each PC as follows:

1. Right-click the icon "My Network Places" on your desktop. In the menu that appears,select the item "Properties”.

2. In the "Network and Dial-Up Connections” window that appears, click on "Advanced”in the toolbar, and from the list that appears select "Advanced Settings...”.

3. The "Advanced Settings” windows is now displayed. In the "Connections” list, select"Local Area Connection”. The list beneath (called "Bindings for Local Area Connec-tion”) will now show the preferred order in which protocols will be used.

4. Select the item "Internet Protocol (TCP/IP)” from the list and then click on the up ar-row on the right side of the window. Do this until "Internet Protocol (TCP/IP)” is thefirst item in the list under "File and Printer Sharing for Microsoft Networks”.

5. Repeat the procedure in step four for all of the other clients listed in the window.6. After changing the settings for all of the clients listed, click on the tab titled "Provider

Order”.7. Select the item "Microsoft Windows Network” from the "Network providers” field, and

then click on the up arrow on the right side of the screen to move it to the top of thelist.

8. Click "OK” to save the changes and then reboot the computer.

Connection Affected Task

Client -> NetServer Starting the LCT application from a Client.

Server -> NetServer Communication with NetServers/NEs.

Server -> Standby Server Starting database replication.

Server -> Client Starting the Client application or the SysAdmin applica-tion.

Tab. 15.1 Affected Connections

124 A42022-L5938-H52-1-76D1


A42022-L5938-H52-1-76D1 125



16 Multi Server CDM: System Expansion

16.1 Adding Additional ClientsUp to 40 clients can be operated on one server simultaneously. If new clients are to beadded as part of system expansion, the same software version must be installed as pro-vided on existing clients.

Proceed as follows:– Install and cable the new computers as described in Section 3.2.1.– Install operating system as described in Section 4.2.3.– Install the Client and/or SysAdmin software as described in Chapter 6.– Test the system in accordance with the test cases described in the acceptance test



126 A42022-L5938-H52-1-76D1


A42022-L5938-H52-1-76D1 127



17 AbbreviationsCE Communauté Européenne

DAT Digital Audio Tape ,DHCP Dynamic Host Configuration Protocol ,DLL Dynamic Link Library ,DNS Domain Naming Service ,EML Element Management Layer ,EMOS Element Manager Operating System

EMS Element Management System

EN European Norm ,ESD Electrostatic Discharge ,IMN Installation Manual

JRE JAVA Runtime Environment. ,LAN Local Area Network

LSU Load/Store Unit ,MDAC Microsoft Data Access Components

MS CDM Multi Server Cross Domain Manager

MSDE Microsoft Desktop Engine ,MSN Multi Service Node

OLE Object Linking and Embedding ,OS Operating System ,OSI Open System Interconnection

PC Personal Computer

PCI Peripheral Component Interconnect ,PDH Plesiosynchronous Digital Hierarchy

PLET Performance Log Export Tool

RAID Redundant Arrays of Independent Disks ,RPR Resilient Packet Ring

SCSI Small Computer System Interface ,SNC Subnetwork Connection

SNMP Simple Network Management Protocol

SW Software ,TCOA TMF CORBA Agent

TCOM TMF CORBA Manager

TED Technical Description

TNMS Telecommunication Network ManagementSystem

UNO Universal Network Object

USO Universal Subnetwork Object

WAN Wide Area Network

WINS Windows Internet Naming Service ,

128 A42022-L5938-H52-1-76D1


A42022-L5938-H52-1-76D1 129



18 IndexSymbols@P proxy 14

AAdditional clients 80, 125Additional hardware 33, 103Additional NetServers 80Additional TNMS components

Installation 48, 118Adobe Acrobat Reader 13, 85Antistatic mat 9, 82

BBasic information 7

Commissioning 7Personnel requirements 7

CCabling 12, 84CE conformity 7Commissioning 11, 83

Basic information 7Final tasks 76, 120Hardware recommendations 11, 83Installation and cabling 12, 83Installation sequence 16, 87Mirror disks 12, 84Preparation 11, 83Software recommendations 12, 84Standby server 12, 84Uninterruptible power supply 12, 84

DDeinstallation

Multi Server CDM 117TCOA 3rd-party software 56TCOM 3rd-party software 61TNMS Core 46

DHCP 19, 89DNS 19, 89

EElectrostatic-sensitive devices 9, 81ELI 13EML packages

ELI 13EMOS 13PDH 13QB3M 13SNC 85SNMP 13

UNO 13USO 85Waveline 14

EMOS 13ESD symbol 9, 81

GGrounding bracelet 9, 81

HHardware recommendations 11, 83

Mirror disks 12, 84Operating system 11, 83Standalone system 11, 83Standby server 12, 84Uninterruptible power supply 12, 84

Hummingbird Exceed 14

IInitial configuration

Multi Server CDM 120TNMS Core 76

InstallationAdditional TNMS components 48, 118Licensing 18, 88MetaFrame 37, 108MSDE 35, 106MSN 73Multi Server CDM 114Operating system 18, 88OSI stack 36, 107PLET 72ServerStart 19, 25, 90, 95TCOA 3rd-party software 52TCOA proxy 51TCOM 3rd-party software 58Terminal services 33, 103Third-party software 35, 106TNMS Core 43, 51Waveline 72Windows 2000 Professional 30, 101Windows 2000 Server 19, 25, 90, 95Windows 2000 Service Pack 3 33, 103XML parser 35, 106

Installation and cabling 12, 83Installation sequence 16, 87Installation software 12, 84

@P proxy 14Adobe Acrobat Reader 13, 85EML packages 13, 85Hummingbird Exceed 14Internet Explorer 13, 85

130 A42022-L5938-H52-1-76D1


MetaFrame 13, 85Microsoft Desktop Engine 13, 85MSN 13Multi Server CDM 85OSI stack 13PLET 14RPR Manager 14ServerStart 12, 84TCOA proxy 14TCOM 14Terminal services 13, 85TNMS Core 13Waveline 14Windows 2000 13, 84XML parser 13, 85

InstallationPCI I/O card 33, 104Internet Explorer 13, 85

JJava versions 16, 38, 51, 57, 74, 87, 109

LLicensing 18, 88

MetaFrame 39, 110

MMeasures after commissioning 76, 120

Initial configuration 76, 120Routing settings 79, 122

Measuring equipment 9, 82MetaFrame 13, 85

Configuring the ICA client connection 41, 112Installation 37, 108Installing the MetaFrame Client 40, 111Installing the MetaFrame Server 38, 109Licenses 39, 110Publishing applications 39, 111System requirements 37, 108

Microsoft Desktop Engine 13, 85Mirror disks 12, 84Modules 9, 81MSDE

Installation 35, 106MSN 13

Installation 73Multi Server CDM

Deinstallation 117Initial configuration 120Installation 114

OOperating system

Installation 18, 88OSI stack 13

Installation 36, 107

PPCI I/O card 33, 104PDH 13PLET 14

Installation 72Protective measures 9, 81Protocol information 19, 89

DHCP 19, 89DNS 19, 89WINS 19, 89

QQB3M 13

RRouting settings 79, 122RPR Manager 14

SSafety precautions 9, 81

Antistatic mat 9, 82Electrostatic-sensitive devices 9, 81ESD symbol 9, 81Grounding bracelet 9, 81Labeling 9, 81Measuring equipment 9, 82Modules 9, 81Voltage 9, 81

ServerStart software 12, 19, 25, 84, 90, 95Setup options

TCOA 3rd-party software 56SNC 85SNMP 13Software recommendations 12, 84Standby Server 12, 84Supplementary documentation 7

Delivery notes 7Field test protocols 7Planning documents 7

SystemStandalone 11, 83

System expansion 80, 125Additional clients 80, 125Additional NetServers 80

TTCOA 3rd-party software

Deinstallation 56Installation 52Setup options 56

TCOA proxy 14

A42022-L5938-H52-1-76D1 131



Installation 51Third-party software 51

TCOM 14Configuration tool 63DCN management configuration 69EML server setup 65Third-party software 57

TCOM 3rd-party softwareDeinstallation 61Installation 58

Terminal services 13, 85Installation 33, 103

Third-party softwareInstallation 35, 106MetaFrame 37, 108MSDE 35, 106OSI stack 36, 107TCOA proxy 51TCOM 57XML parser 35, 106

TNMS CoreDeinstallation 46Initial configuration 76Installation 43, 51

UUninterruptible power supply 12, 84UNO 13USO 85

WWaveline 14

Installation 72Windows 2000 13, 84

Hardware configuration 33, 103Windows 2000 Professional

Installation 30, 101Windows 2000 Server

Installation 19, 25, 90, 95Windows 2000 Service Pack 3

Installation 33, 103WINS 19, 89

XXML parser 13, 85

Installation 35, 106

132 A42022-L5938-H52-1-76D1


tnms_imn

Documents