user manual tnmsct v3.0

Instructions

TNMS CT V3.0

User Manual (UMN)

A42022-L5959-C53-4-7619

2 A42022-L5959-C53-4-7619

User Manual (UMN) InstructionsTNMS CT V3.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-2004.

Issued by the Information and Communication Networks GroupHofmannstraße 51D-81359 München

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

A42022-L5959-C53-4-7619 3

InstructionsTNMS CT V3.0

User Manual (UMN)

This document consists of a total of 81 pages. All pages are issue 4.

Contents

1 Introductory Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.1 Available Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.2 Symbols Used in this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.3 Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2 Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.1 Network Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.2 System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.2.1 Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.2.2 Software Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.2.2.1 TNMS CT Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.2.2.2 TNMS CT Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.3 Functional Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.3.1 LCT and NCT Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.3.2 Network Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.3.3 DCN Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.3.4 Communication Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.3.5 Telegram Protocols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.3.6 Scaled Start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.3.7 Automatic Topology Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.3.8 Automatic Recognition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.3.9 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.3.10 User Management and Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.3.11 Remote Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.3.12 Log Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.3.13 Screen Level Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.3.14 Priority/Mutable Exclusion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

3 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.1 Protective Measures and Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.1.1 Safety Precautions When the Unit is Open. . . . . . . . . . . . . . . . . . . . . . . . . 263.1.2 Protection against Excessive Contact Voltages . . . . . . . . . . . . . . . . . . . . . 273.1.3 Handling Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.2 Preparation for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.2.1 Component Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.2.2 Hardware Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.2.3 Installation and Cabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.2.4 Installation Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.2.5 Installation Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.3 Installing the Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.3.1 Before you Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.3.2 Installing Windows OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.3.3 Installing Windows OS Service Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.3.4 Hardware configuration under Windows OS. . . . . . . . . . . . . . . . . . . . . . . . 313.4 Installing 3rd-Party Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

4 A42022-L5959-C53-4-7619


3.4.1 Installing Microsoft Internet Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.4.2 Installing JavaSoft JAVA Runtime Environment . . . . . . . . . . . . . . . . . . . . . 333.4.3 Installing an OSI Stack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.4.4 Installing Adobe Acrobat Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373.5 Installing the TNMS CT Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373.5.1 Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373.5.2 Installing TNMS CT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383.5.3 Deinstalling TNMS CT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423.5.4 Adding and Removing Individual TNMS CT Components . . . . . . . . . . . . . . 433.6 Measures after Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443.6.1 Configuring Windows XP firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443.6.2 PPP Dial-up Setup for Q3 Network Elements . . . . . . . . . . . . . . . . . . . . . . . 443.6.2.1 Windows XP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443.6.2.2 Windows 2000 Professional. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513.6.3 Initial Configuration of TNMS CT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573.6.4 Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593.6.5 Routing Settings for PCs with Multiple Network Adapters . . . . . . . . . . . . . . 59

4 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614.1 Working With the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614.1.1 TNMS CT Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614.1.2 Working With the Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614.1.3 Working With the Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624.1.4 Working With the Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624.2 Basic Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624.2.1 Starting a TNMS CT Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634.2.2 Starting and Stopping TNMS CT Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 634.2.3 Activating and deactivating TNMS CT Server . . . . . . . . . . . . . . . . . . . . . . . 634.2.4 Setting Date and Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634.2.5 Starting Element Manager Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634.2.6 Administrating NE Write Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634.2.7 Terminating a TNMS CT Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644.3 Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644.3.1 Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654.3.2 Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674.3.3 Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684.3.4 Network View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694.3.5 Serial Line View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724.3.6 DCN Management View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724.3.6.1 DCN Management Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734.3.6.2 DCN Management Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

5 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

6 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

A42022-L5959-C53-4-7619 5


User Manual (UMN)

IllustrationsFig. 2.1 General Structure of a TNMS CT Network . . . . . . . . . . . . . . . . . . . . . . 14

Fig. 2.2 System Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Fig. 2.3 Overview of Software Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Fig. 2.4 Example of a Multi Service Node (MSN) . . . . . . . . . . . . . . . . . . . . . . . . 20

Fig. 2.5 A GNE detecting its managed NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Fig. 3.1 Labelling of electrostatic-sensitive devices (ESD symbol). . . . . . . . . . . 27

Fig. 3.2 OSI Stack Installation: Choose Destination Location. . . . . . . . . . . . . . . 34

Fig. 3.3 OSI Stack Installation: NSAP Address. . . . . . . . . . . . . . . . . . . . . . . . . . 35

Fig. 3.4 OSI Stack Installation: Start Copying Files . . . . . . . . . . . . . . . . . . . . . . 36

Fig. 3.5 TNMS CT Installation: Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Fig. 3.6 TNMS CT Installation: LCT/NCT Mode . . . . . . . . . . . . . . . . . . . . . . . . . 38

Fig. 3.7 TNMS CT Installation: Client/Server Installation . . . . . . . . . . . . . . . . . . 39

Fig. 3.8 TNMS CT Installation: License Agreement . . . . . . . . . . . . . . . . . . . . . . 39

Fig. 3.9 TNMS CT Installation: Choose Destination Location. . . . . . . . . . . . . . . 40

Fig. 3.10 TNMS CT Installation: NE Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Fig. 3.11 TNMS CT Installation: Start Copying Files . . . . . . . . . . . . . . . . . . . . . . 41

Fig. 3.12 TNMS CT Installation: Setup Status . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Fig. 3.13 TNMS CT Installation: Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Fig. 3.14 Network Connection Wizard: Welcome . . . . . . . . . . . . . . . . . . . . . . . . . 45

Fig. 3.15 Network Connection Wizard: Network Connection Type . . . . . . . . . . . . 45

Fig. 3.16 Network Connection Wizard: Advanced Connection Options . . . . . . . . 46

Fig. 3.17 Network Connection Wizard: Host or Guest . . . . . . . . . . . . . . . . . . . . . 46

Fig. 3.18 Network Connection Wizard: Complete . . . . . . . . . . . . . . . . . . . . . . . . . 47

Fig. 3.19 Network Connection Wizard: Select a Device . . . . . . . . . . . . . . . . . . . . 47

Fig. 3.20 Network Connection Wizard: Connection Availability . . . . . . . . . . . . . . 48

Fig. 3.21 Connection Properties: General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Fig. 3.22 Modem Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Fig. 3.23 Connection Properties: Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Fig. 3.24 Internet Protocol (TCP/IP) Properties . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Fig. 3.25 Advanced (TCP/IP) Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Fig. 3.26 Properties: QB3 Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Fig. 3.27 Network Connection Wizard: Welcome . . . . . . . . . . . . . . . . . . . . . . . . . 51

Fig. 3.28 Network Connection Wizard: Network Connection Type . . . . . . . . . . . . 52

Fig. 3.29 Network Connection Wizard: Host or Guest . . . . . . . . . . . . . . . . . . . . . 52

Fig. 3.30 Network Connection Wizard: Select a Device . . . . . . . . . . . . . . . . . . . . 53

Fig. 3.31 Network Connection Wizard: Connection Availability . . . . . . . . . . . . . . 53

Fig. 3.32 Network Connection Wizard: Complete . . . . . . . . . . . . . . . . . . . . . . . . . 54

Fig. 3.33 Connection Properties: General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Fig. 3.34 Modem Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Fig. 3.35 Connection Properties: Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Fig. 3.36 Internet Protocol (TCP/IP) Properties . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Fig. 3.37 Advanced (TCP/IP) Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Fig. 3.38 Properties: QB3 Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

6 A42022-L5959-C53-4-7619


Fig. 3.39 Login window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Fig. 4.1 TNMS CT Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Fig. 4.2 Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Fig. 4.3 Main Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Fig. 4.4 Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Fig. 4.5 Network View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Fig. 4.6 Serial Line View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Fig. 4.7 DCN Management View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Fig. 4.8 DCN Management Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

A42022-L5959-C53-4-7619 7


User Manual (UMN)

TablesTable 1.1 TNMS CT Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Table 1.2 Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Tab. 2.1 Hardware Recommendations for TNMS CT . . . . . . . . . . . . . . . . . . . . . 16

Tab. 2.2 Log Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Tab. 3.1 Affected Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Tab. 4.1 Blue Framing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Tab. 4.2 Menu Bar Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Tab. 4.3 Main Toolbar Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Tab. 4.4 Status Bar Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Tab. 4.5 Network View Context Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Tab. 4.6 Serial Line View Context Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Tab. 4.7 DCN Management Toolbar Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Tab. 4.8 DCN Management Tree Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

8 A42022-L5959-C53-4-7619


A42022-L5959-C53 9


User Manual (UMN)

1 Introductory Notes

1.1 Available DocumentationAll TNMS CT manuals are available on CD-ROM, and can be ordered in English fromSIEMENS Technical Sales.

The User Manual (UMN) consists of the following main chapters:• Information

This chapter provides an overview of the applications, system architecture, featuresand functions of TNMS CT (see Chp. 2).

• InstallationThis chapter contains instructions on installing the TNMS CT software (see Chp. 3).

• OperationThis chapter contains a general description of the TNMS CT user interfaces as wellas the necessary background information (see Chp. 4).

The Graphical User Interface Manual contains the following information:• Graphical User Interface Manual (GUIMN)

The content of the Graphical User Interface Manual is identical to the complete On-line Help, but converted to a printable PDF file. In addition, every GUI-related helpwindow is supplemented by a sample screenshot.

You may also consult the online help which is provided with the TNMS CT software. Itprovides comprehensive instructions on the functions offered by the user interface. TheContents , Index and Find tabs enable the online help to be searched quickly and con-veniently. Individual help topics can be printed, and context-sensitive help texts calledup directly from the user interface.

The User Manual is also provided as PDF file under the Help menu. This file can beviewed and printed using Adobe Acrobat Reader.

1.2 Symbols Used in this ManualThe following symbols are used in this manual:

Manual Type Order Number

CD-ROM (contains UMN andGUIMN)

A42022-L5959-C10-*-76K5

Table 1.1 TNMS CT Manuals

iAdditional information

!Warnings

Table 1.2 Symbols

10 A42022-L5959-C53


1.3 FeedbackWe aim to provide you with documentation which is easy to understand and user-friendly. Your practical experience is very important to us in achieving this objective.

We are particularly interested in your opinion on the following issues:• Where is too much/not enough detail provided?• Where do you find these instructions difficult to understand?• Where would additional graphics be useful to improve understanding?• What improvements could be made to the basic layout of the TNMS CT

documentation?

Please enter your comments, suggestions and corrections in the questionnaireon the following page. If necessary, this questionnaire can also be photocopiedor printed out from your documentation CD.So that we can contact you and discuss your comments at greater length if nec-essary, do not forget to enter your contact details.

Thank you in advance for your support!

A42022-L5959-C53 11


User Manual (UMN)

QuestionnaireCompleted questionnaires can be returned:by fax: +49 89 722 57315or by post:SIEMENS AKTIENGESELLSCHAFTInformation and Communication Networks GroupICN CP E PD DHofmannstrasse 51D-81359 München

Company/Name:

Address:

Department: Telephone:Fax:

Date: Signed:

I am using this documentation My duties include

(...) As service documentation (...) Commissioning

(...) As an installation/commissioning guide (...) Operation

(...) As a general introduction (...) Maintenance

(...) For reference purposes (...) Sales

(...) As training material (...) Training activities

(...) _______________________________ (...) _______________________________

12 A42022-L5959-C53


Page Remarks

A42022-L5959-C53-4-7619 13


User Manual (UMN)

2 InformationTNMS CT is a transparent software platform for SDH and WDM network elements usingQD2, QST, QSTV2, Q3 or SNMP telegram protocols. TNMS CT provides access to net-work elements via a network interface (ethernet) or via a serial line interface (RS232).

There are two operation modes for TNMS CT: the Local Craft Terminal (LCT) mode andthe Network Craft Terminal (NCT) mode.

The TNMS CT menu items and dialogues allow the supported communication channelsto be set up. The network element to be operated is selected by a simple procedure,adapted to the requirements of the connected communication channel.

TNMS CT enables addresses to be assigned to the network elements. The programicons for these applications are used to present the assigned network elements in thenetwork view for the communication channel. A double-click on such an icon starts theassigned device application, i.e. an element manager, and thus permits the network el-ement to be operated.

This chapter consists of a technical description of TNMS CT covering the following ar-eas:– Network Architecture (see Chp. 2.1)– System Architecture (see Chp. 2.2)– Functional Overview (see Chp. 2.3)

14 A42022-L5959-C53-4-7619


2.1 Network ArchitectureFig. 2.1 shows the general structure of a transmission network managed by TNMS CT.The network elements (NEs) provide various management interfaces. This means thatthey can be connected via the DCN to the management system in several ways.

Fig. 2.1 General Structure of a TNMS CT Network

Element management functions are executed via the element managers (LCTs, MSNmanager) provided by the TNMS CT system.

TNMS CT supports line, star, ring and mesh networks comprising of WDM, SDH andnetwork elements and Multi NE devices. A complete list of NEs supported by TNMS CTis provided in the Customer Feature List, which can be obtained from SIEMENS Tech-nical Sales.

2.2 System ArchitectureTNMS CT is a scalable single-user system with a client/server architecture comprisingseveral industry standard PCs with the Windows operating system and various software

Managementinterface

Type of network element

QB3MhiT 7050, hiT 7070, hiT 7500, hiT 7540,hiT 7550, SMA1/4, SMA4/1, SMA1K,SMA1K-CP, SMA16, SMA16/4, SL16,SLR16, SL64, WL, WLS, WTTR

SNMPFSP

DC

N

MSNMSN

TNMS CT

Integrated element managers (EMs)and MSN manager

QF Local connection to Q3, QD2and QST network elements

A42022-L5959-C53-4-7619 15


User Manual (UMN)

applications. External devices such as printers, tape units and remote clients are notdealt with here.

Fig. 2.2 shows an overview of the TNMS CT client/server architecture with client andserver installed on different computers. A configuration with client and server installedon the same PC is also possible.

Fig. 2.2 System Architecture

iSome NEs, such as QST and QD2 NEs, allow the connection to several managementsystem levels. If a management system like TNMS Core enforces write access on a net-work element, it will override the TNMS CT write access.

Managed Network

Element Manager Element Manager Element Manager

EML Package EML Package EML Package

TNMS CT Server PC

TNMS CT Client PC

Network Element

Network Element

Network Element

EM Interface EM Interface EM Interface

EML Interface EML Interface EML Interface

DCN DCN DCN

Client Interface

16 A42022-L5959-C53-4-7619


2.2.1 Hardware ComponentsThe table below provides an overview of hardware recommendations for TNMS CT in-stallations. However other configurations are possible, depending on the network size.Planning for hardware, software and licences should be undertaken on a project-specificbasis.

2.2.2 Software ComponentsThe TNMS CT software comprises of a Client and a Server component.

The Client component provides a network management user interface. Via this GUI allTNMS CT management functions, e.g. invoking of element managers, are available.

The Server component holds the EML packages and the NetServer frame, which pro-vides the environment for running EML servers, DCN connectors and NE controllers.

All software components can be installed on one PC.

Hardware Recommendations

CPU Pentium IV 2,6 GHz/512 kB

Memory 1 GB

Hard Disk 40 GB

CD-ROM 48x

LAN Ethernet card, 2x 3COM (3C982-TXM)

Graphics Card 32 MB

Monitor Color monitor 19”

Operating system Windows 2000 Professional or Windows XP

Tab. 2.1 Hardware Recommendations for TNMS CT

A42022-L5959-C53-4-7619 17


User Manual (UMN)

Fig. 2.3 shows the TNMS CT software architecture.

Fig. 2.3 Overview of Software Components

2.2.2.1 TNMS CT ClientThe main parts of the TNMS CT client component are the network management graph-ical user interface including the import and export interfaces and the element managers.

Network Management Graphical User Interface

The TNMS CT graphical user interface (GUI) provides the operator with several networkviews which contain graphical and text information about current alarms, states and re-sources. The main GUI contains the network map, several list and log windows, as wellas specific dialog windows. Depending on the assigned user class, the operator’s ac-cess can be restricted to certain functions.

TNMS CT ClientComponents

TNMS CT Frame

Network ManagementUser Interface

ElementManager

ElementManager

Export filesas *.sdf

TNMS CT Server Components

TNMS CT NetServer Frame

Import/Exportas *.xml

EML Package EML Package

NE Controller NE Controller

DCN Interfaces

Network Element Network Element

MSNManager

18 A42022-L5959-C53-4-7619


More information on operating via the GUI is given in Chp. 4.3.

Element Manager

In order to obtain detailed information about an NE, the operator can open the elementmanager application associated with the corresponding network element. TNMS CTstarts the corresponding process and provides the interface of the associated NE con-troller to the element manager. Element manager applications provide full access to allNE data and also enable the configuration and control of NE behaviour. This way, de-pending on the actual NE type, performance values and alarms can be requested, andthe backup and restore of configuration and other data initiated.

Network Management Data Export

Data export is provided in the TNMS CT to export data for external evaluation. This en-ables the operator to export the content of each list and log to a file. This information iswritten to system data format (SDF) files. Several tools and standard applications (e.g.MS Access or MS Excel) can read these files.

Import / Export Interface

To import/export TNMS CT configuration data, the extended markup language (XML)format is used. These files can be used for migration purposes.

2.2.2.2 TNMS CT ServerThe main parts of the TNMS CT Server component are the NetServer frame and theEML packages including NE controllers.

NetServer Frame

The NetServer frame is essentially a proxy for the TNMS CT Server. It facilitates themanagement of EML packages.

EML Packages

A EML package is an installation package, which contain all relevant components (e.g.the NE controller) needed to run a family of NEs within TNMS CT. The combination ofEML packages required for a given TNMS CT system depends on the NE types thatTNMS system configuration is required to support.

NE Controllers

The main task of an NE controller is to convert NE-specific management interfaces to asimple internal TNMS CT element management interface. In this way, network layermanagement in the TNMS CT Server only receives the necessary information from theelement management layer.

A corresponding NE controller must be registered in the system for every NE type to bemanaged by TNMS CT. Each NE controller class can support different NE types, buteach NE can only be controlled by one type of NE controller.

iDetailed operating information on operating TNMS CT is provided in Chapter 4 and inthe Online Help.

A42022-L5959-C53-4-7619 19


User Manual (UMN)

2.3 Functional OverviewTNMS CT provides network management functions defined in the ITU-T standardM.3010 “Principles for a Telecommunications Management Network”.

Fault and configuration management are supported on the element management andon the network management layer. Various security management features are also im-plemented.

2.3.1 LCT and NCT ModesDepending on the needs, two different modes are available for TNMS CT.

LCT Mode

The Local Craft Terminal (LCT) is used for local management and commissioning of net-work elements. The MSN Manager, organizational relationships between network ele-ments in the network and network alarms are not available for the LCT. The LCT cancommunicate with a maximum of 50 network elements. Up to three element managersmay be open at the same time only.

NCT Mode

The Network Craft Terminal (NCT) is used for local or remote management of networkelements. In addition to the LCT functions, the monitoring of all the alarms reported fromeach accessible network element is allowed. The NCT can communicate with a maxi-mum of 150 network elements (including alarm monitoring). Up to 50 element managersor up to five MSN Managers may be open at the same time only.

Information on remote login is given in Chp. 2.3.11.

2.3.2 Network ManagementThe following objects are managed by TNMS CT and represented on the network mapby various graphical symbols such as icons or lines.

Network Element (NE)

This object represents a physical network element. Network elements are the basis ofthe network topology. Each individual NE is clearly identifiable and can also be com-bined with other NEs by drawing lines between them representing physical connections.

Multi Service Node (MSN)

This object represents a set of NEs managed by a special element manager, i.e. theMSN Manager. An MSN is basically a cluster of individual network elements that is dis-played similarly to a single network element on the TNMS CT GUI. In this way, theTNMS CT operator can conveniently manage several NEs at once using a single NEcluster.

Fault management is also provided for MSNs via an alarm list. Performance manage-ment is supported in accordance with the functionality of the MSN component NEs.

The following diagram shows a typical MSN configuration:

iEach mode requires its own license key. Furthermore, the installation routines areslightly different from each other.

20 A42022-L5959-C53-4-7619


Fig. 2.4 Example of a Multi Service Node (MSN)

Link

This object are lines drawn on the network map. These lines are drawn arbitrarily by theoperator to structure the NEs according to the existing network topology. Genuine portconnections, however, are not established this way. The link information is stored on theClient PC.

Port Connection

This objects represents port connections that have been established between NEs andalso inside Multi NEs, as far as this is supported by the used NEs. The port connectioninformation is stored inside the NE itself.

2.3.3 DCN ManagementThe following objects are managed by TNMS CT and handled via the graphical tree viewin the DCN Management View .

Server

The Server nodes provide the following functions:– Activating or deactivating all subordinated objects at once.– Handling scheduled start-up.– Configuration of DCN channels.

The CT Server node allows to configure freely DCN channels, NEs and Container NEsfor network access. The Serial Line Server contains preconfigured DCN channels andNEs for RS232 access and consequently allows the Serial Line View to perform an au-tomatic connect.

DCN Channels

The DCN channel nodes provide the following functions:– Handling the connection to one or more different NEs of the same DCN channel

type.– Activating or deactivating all subordinated objects at once.– Behaving like OSPF area with up to eight GNEs. Additional OSPF settings are not

necessary in TNMS CT but NEs must have OSPF activated.

Optical line IFOptical line IF

SL64 SMA16

Tributary IF: PDH, SDH, SONET, Data

FSP 3000

hiT 7540c

A42022-L5959-C53-4-7619 21


User Manual (UMN)

Subnetworks

The DCN channel nodes allow the operator to categorize network elements into subnet-works. This information is also displayed on the network map.

Network Elements

The NE nodes provide the following functions:– Handling the connection to one network element.– Activating or deactivating a network element.

When an NE node has been activated, a corresponding NE symbol is displayed on thenetwork map.

Gateway Network Elements

The GNE nodes provide the following functions:– Auto-detecting the network elements of the same OSPF area.– Routing due to cost factors.– Automatic protection switching from the primary GNE to a secondary GNE when the

connection to the primary GNE is lost.

When one or more GNEs are added to a DCN channel, the associated NEs will be add-ed automatically. The ID name of the DCN channel will be set as subnetwork name forthese NEs. Fig. 2.5 shows an example of an activated GNE with its NEs starting up.

Fig. 2.5 A GNE detecting its managed NEs

2.3.4 Communication InterfacesTNMS CT supports two different communication interfaces, a serial line interface and anetwork interface.

Serial Line (Q-F)

TNMS CT provides a serial line interface via the RS232 port of the operator’s PC. TheCOM port can be selected via a property page in the DCN Management View . A localserial line connection can be established in both LCT and NCT mode.

22 A42022-L5959-C53-4-7619


Network (Q-B3)

TNMS CT can establish a connection to one or more NEs via an ethernet card in theoperator’s PC.

2.3.5 Telegram ProtocolsTNMS CT supports the following telegram protocols to communicate with NEs:– QD2– QST– QSTV2– Q3– SNMP

TNMS CT is capable of using these protocols simultaneously.

2.3.6 Scaled Start-upTo avoid DCN overload during the system start-up phase, a scaled start-up is support-ed. Accordingly, the connection to the NEs managed by a server are not established si-multaneously, but one after another. A parameter set up via the DCN ManagementView allows a simultaneous start-up.

2.3.7 Automatic Topology DiscoverySeveral NEs supported by TNMS CT are capable of storing topology information, suchas neighboring NEs and port connections. As soon as one of these NEs is activated viathe DCN Management View , the topology information is available in TNMS CT. Accord-ingly, integration of network information is simplified.

2.3.8 Automatic RecognitionIn case of a communication loss, an automatic reconnection to the network elements issupported. The retry interval can be set via the Properties windows of the DCN chan-nels.

2.3.9 Fault ManagementFault management in TNMS CT comprises the following alarm handling functions:– Alarm list– Alarm log– Display of alarm state– Display of alarm severity– Audible alarm– External alarm output

All alarms are administered via the TNMS CT Server and recorded in an alarm list andan alarm log. The alarm list is accessed via the TNMS CT Client. A global alarm list con-tains all alarms currently raised for all NEs in the network as well as performance man-agement related Threshold Crossing Notification (TCN) entries. An individual list of

iThis function may not be available in all network elements.Also be aware that topology information has to be stored in the NE prior to the activationof the NE in TNMS CT.

A42022-L5959-C53-4-7619 23


User Manual (UMN)

current alarms can also be generated for each NE. As soon as an alarm is cleared, it isdeleted from the alarm list.

The alarm log, by contrast, is a permanent record containing all network element layeralarms, both raised and cleared. It provides a complete alarm history for the supervisednetwork. The size of this log can be configured as required for up to 99.999 entries. Thealarm log and alarm lists can also be filtered and sorted in accordance with specific cri-teria.

If alarm notifications are received by the TNMS CT Server or TNMS CT Client, the fol-lowing actions are performed:

For each alarm notification received by the TNMS CT Server:– The notification is forwarded to the connected TNMS CT Client.– The list of current alarms is updated.– The notification is stored in the alarm log.

For each alarm notification received by the TNMS CT Client:– The alarm is updated.– The alarm log is updated.– The alarm supervision of NE icons and NE container icons is updated.

The operator can localize the network element where the alarm was raised by referringto the alarm list. Specific symbols are used to illustrate the current access state and thehighest alarm severity. These can be displayed for both the network as a whole as wellas for individual network elements. This allows the user to quickly assess the impor-tance of the alarm concerned.

For further fault localization, the user can also call up the appropriate element manager.

The Alarm Statistic window enables the operator to handle alarms conveniently. TheAlarm statistic windows shows:– The number of current alarm per severity.– Alarms separated for unacknowledged and acknowledged state.– Summary counters per severity.– Summary counter of total alarms.

The window presents the alarm statistics in a matrix view and is updated automatically.

2.3.10 User Management and SecurityThe access to TNMS CT is regulated by five user classes, which are consistent with theTNMS Core/CDM user classes. Via the User Administration window users can be as-signed to the user class. The set of functionality available to a given user class is fixedand cannot be changed. Only an Administrator has access to the user administrationand other security functions. Additionally, the following user management features areprovided:– Display of currently logged in users and their account status.– Forced log out of users to disable their accounts.– Configurable account expiration.

Moreover, user monitoring is provided by a Security Log which stores the logged-onusers and their actions, e.g. usage of Element Managers. Access to this from outsideTNMS CT is not possible, except for the system administrator and the file owner. Addi-tionally, the following security features are implemented:– Password security including password complexity and a check against logical ar-

rangement and toggling of formerly used passwords.

24 A42022-L5959-C53-4-7619


– System message after five consecutively failed login attempts.– Logout due to user inactivity.

2.3.11 Remote LoginTNMS CT supports remote login from an external computer via TCP/IP according to theclient/server architecture (see Fig. 2.3). The TNMS CT Client may run on a differentcomputer and access the CT Server computer via a TCP/IP connection..

2.3.12 Log ManagementIn TNMS CT, specific operator activities as well as all actions and unsolicited events arestored in log files on the Server PC. The log contents can be printed out or saved to a file.

TNMS CT provides logs that are permanent. Permanent logs are fixed, global logs ad-ministered by the TNMS CT system. The operator can, however, specify certain at-tributes such as the maximum log size.

The following logs are provided by TNMS CT:

The alarm log contains a chronological list of alarms which have occurred. Togglealarms, i.e. identical alarms which are triggered repeatedly, are entered once only if thetoggle filter with a proper time setting is switched on.

The system message log contains a chronological list of relevant administrativeevents. Critical events are indicated at the user interface.

2.3.13 Screen Level IntegrationTNMS CT supports screen level integration of UniGATE functions not covered by TNMSCT. For screen level integration Symantec’s pcAnywhere may be used.

In order to run TNMS CT and pcAnywhere, the following settings have to be configured:– Set the UniGATE machine to host.– Set the TNMS CT computer to remote controller.

2.3.14 Priority/Mutable ExclusionSiemens network elements support the functionality to connect to more than one man-agement system. Some NEs, e.g. QST and QD2 NEs, also support different manage-ment system levels, such as TNMS Core/CDM, which comprises a network layer.Consequently, such a TMS can enforce the write access on these NEs and override thewrite access of TNMS CT. TNMS CT, however, is not able to enforce the write accesson an NE.

iRemote login is supported in NCT mode only! Information on NCT mode is given in Chp.2.3.1.

Log Type Log Class

Alarm log Permanent log

System message log Permanent log

Tab. 2.2 Log Types

A42022-L5959-C53-4-7619 25


User Manual (UMN)

3 InstallationThis chapter provides a guideline of the procedures to be taken to install TNMS CT cor-rectly:– Protective Measures and Handling (see Chp. 3.1)– Preparation for Installation (see Chp. 3.2)– Installing the Operating System (see Chp. 3.3)– Installing 3rd-Party Software (see Chp. 3.4)– Installing the TNMS CT Software (see Chp. 3.5)– Measures after Commissioning (see Chp. 3.6)

The TNMS CT software includes a number of applications and feature components. Itis supplied on CD-ROM which includes a convenient master installation program for– installing the TNMS CT software components on the user’s hard disk,– modifying an existing installation by adding or removing selected components or

subcomponents,– removing the TNMS CT software completely from the user’s hard disk.

Licensed Software

In order to use the TNMS CT software, the import of corresponding license keys is re-quired.

Depending on functionality, the TNMS software is divided into several software packag-es, which are provided on a separate CD-ROM with individual licenses.

More information on licenses is provided under "Import licenses".

Upgrade Packages

The TNMS CT software supports subsequent integration of new network elements ornew network element versions.

The software components for managing a new network element or a new network ele-ment version are provided with a TNMS CT upgrade installation package on a separateCD. Using this package, a TNMS CT system can be upgraded with the element man-agement components required for the new network element or network element version.The upgrade can be handled via the Modify function of the Installation Wizard (seeChp. 3.5.4).

Supplementary Documentation

In addition to the customer documentation the following information is also availableupon demand:– Delivery notes :

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

On request, Siemens Technical Sales can supply project documentation which pro-

iVarious software products referred to in this manual have been licensed by Siemens AGand are provided together with the TNMS CT software. Any questions concerning theseproducts should therefore be directed to Siemens AG rather than to the original manu-facturer. Questions regarding software products such as virus scanners, which may runwith TNMS CT software, but which are not provided, sold or purchased by Siemens AG,should be addressed directly to the manufacturer in question.

26 A42022-L5959-C53-4-7619


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.

CE Conformity Declaration

The 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.

Personnel Requirements for Commissioning

The following personnel requirements must be fulfilled for commissioning:– 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/Win-

dows XP.– Familiarity with LANs/WANs.– Basic knowledge of measurement systems.– Knowledge of operating electrostatic-sensitive devices.

3.1 Protective Measures and HandlingProtective measures and information on handling electrical components in the TNMSCT installation is provided here.

3.1.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).

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.

A42022-L5959-C53-4-7619 27


User Manual (UMN)

3.1.2 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.

3.1.3 Handling ModulesModules labelled as shown in Fig. 3.1 below are equipped with electrostatic-sensitivecomponents.

Fig. 3.1 Labelling 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.– 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.

3.2 Preparation for InstallationPrior to installing TNMS CT check the following chapters to ensure that all requirementsare met. Information is provided on:– Component Delivery (see Chp. 3.2.1)– Hardware Recommendations (see Chp. 3.2.2)– Installation and Cabling (see Chp. 3.2.3)– Installation Software (see Chp. 3.2.4)– Installation Sequence (see Chp. 3.2.5)

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

28 A42022-L5959-C53-4-7619


3.2.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.2 Hardware RecommendationsTab. 2.1 provides an rough overview of the hardware requirements for running TNMSCT software.

3.2.3 Installation and CablingBefore installing the operating system, the following steps should be completed:– The Client 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.4 Installation SoftwareAll software parts mentioned below must be released for the appropriate TNMS softwareversion. This holds for the initial installation and for service or upgrade package instal-lations as well.

The following software is generally required for the installation. The corresponding CDorder numbers are provided in the TNMS CT release documentation.

More information on the installation sequence is provided in Chp. 3.2.5.

1. Windows 2000 Professional incl. Service Pack 4 or Windows XP incl. Service Pack2:Windows 2000 Professional or Windows XP operating system is required for the Cli-ent and Server machines. Installation instructions for the operating system is provid-ed in Chp. 3.3, however, pre-installed machines can also be used.

2. Internet Explorer 6.0 SP 1:The Internet Explorer must be installed on the Server to enable MSN functionality,and on the client machine. If this is not already pre-installed, it can be downloadedfrom the Internet.

3. TNMS CT V3.0:This installation program contains the following software components for installation:– Integrated TNMS CT software installation package:

This installation program includes the Server and Client components. These canbe installed either individually or together as required.The EML packages for QB3M, FSP (via an additional CD) and MSN are alsoavailable for selection during the TNMS CT installation. The EML packages are

iIf additional software is installed which is not required for TNMS CT, correct functionalityof TNMS CT cannot be guaranteed.

A42022-L5959-C53-4-7619 29


User Manual (UMN)

installed on the Server PC. More information on installing TNMS CT is providedin Chp. 3.5.2.

Additionally to the TNMS CT installation, the following 3rd-party software compo-nents are also included on this CD:– JavaSoft JAVA Runtime Environment:

The JRE is installed on the client machine to provide an environment for the Javabased applications. More information on installing JRE is provided in Chp. 3.4.2.

– OSI stack:The OSI stack software must be installed on Server PC before the Server soft-ware itself. More information on installing the OSI stack is provided in Chp. 3.4.3.

– Acrobat Reader 5.0:Acrobat Reader is required for using the User Manual which is delivered as PDFfile. More information on installing the Acrobat Reader is provided in Chp. 3.4.4.

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.

Overview of the deliverable CD-ROMs:– TNMS CT V3.0

CT application SW, element manager applications, NECs, OSI stack, JRE, AcrobatReader

– OEMSW for FSP equipment

– Customer DocumentationUser Manual

3.2.5 Installation Sequence

The system should be commissioned as follows:

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

system under Windows OS as described in Chp. 3.3.3. Install Microsoft Internet Explorer as described in Chp. 3.4.1.4. Install JavaSoft Runtime Environment as described in Chp. 3.4.2.5. Install the OSI stack on the Server PC as described in Chp. 3.4.3.6. Install Adobe Acrobat Reader as described in Chp. 3.4.47. Install the TNMS CT software components on the corresponding machines as de-

scribed in Chp. 3.5.2:– TNMS CT Client– TNMS CT Server– TNMS CT EML Packages– Additional TNMS software, such as optional EML packages.

8. Configure the TNMS CT components and connect network elements as describedin Chp. 3.6.3.

iBefore install any software component, have a look at the associated readme file. Hereyou 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.

30 A42022-L5959-C53-4-7619


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

3.3 Installing the Operating System

3.3.1 Before you BeginBefore you install Windows operating systems, complete the following steps:– If you wish to pre-install a SCSI RAID system, make sure the TNMS CT 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. This might be necessary for certain UniGATE NEs.– 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 OS. This does not

apply if there are no files on the computer or the existing operating system files aredamaged. You can save the files on disk, on tape or on another computer in yournetwork.

– 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 uninterrupted power supply (UPS) devices.– If the target computer is fed by UPS, remove the serial cable before performing the

setup. Windows 2000/Windows XP Setup tries to identify the devices at the serialinterfaces automatically. UPS might cause problems here.

Licensing Information

During installation, the system license number is requested. This is provided on the backcover of the Windows CD.

Protocol Information

TCP/IP is the standard network protocol used by Windows OS based Server. However,if you wish, 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:

iThe installation sequence for all software parts is described in Chp. 3.2.5. It is obligato-ry.

A42022-L5959-C53-4-7619 31


User Manual (UMN)

– 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 OS.

– 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 Microsoftoperating systems.

3.3.2 Installing Windows OSPrior to installing Windows OS, read the information given in Chp. 3.3.1 carefully.

The Windows 2000 Professional or the Windows XP installations are supported by aninstallation wizard, which will guide you through the installation process. Detailed infor-mation on how to install the OS is provided in the Microsoft Windows documentation de-livered with the Windows OS installation CD-ROM.

3.3.3 Installing Windows OS Service PacksAfter the operating system is installed, the corresponding Service Pack must be installedalso:– Windows 2000 Professional Service Pack 4 (SP4), or– Windows XP Service Pack 2 (SP2)

If required, decompress the Service Pack to a temporary folder and install as follows:– Create an Un-Installation directory: No– Accept the license agreement.

3.3.4 Hardware configuration under Windows OSOnce the Windows OS has been installed, all additional hardware and software compo-nents must be configured and installed under the Windows OS.

This includes:– Graphics cards display settings– Printers– Ethernet card(s) for remote login– UPS

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

Installing the Optional PCI I/O Card

The PCI I/O card is installed on the TNMS CT Client PC and enables external signalling.

– Switch off your computer and disconnect it from the power supply.– Open the computer.

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

32 A42022-L5959-C53-4-7619


– Insert the PCI I/O card into a free slot.– Close the computer and connect it to the power supply.– Switch on the computer.– Install suitable drivers by double-clicking the Setup.exe file on the floppy disk sup-

plied.– Start the TNMS CT Client after installing the drivers.

For further installation information consult the Meilhaus I/O card documentation.

3.4 Installing 3rd-Party SoftwareThis chapter provides an overview of the additional software installations needed to runTNMS CT correctly. The described installations include:– Microsoft Internet Explorer (see Chp. 3.4.1)– JavaSoft JAVA Runtime Environment (see Chp. 3.4.2)– OSI Stack (see Chp. 3.4.3)– Adobe Acrobat Reader (see Chp. 3.4.4)

3.4.1 Installing Microsoft Internet ExplorerPrior to installing TNMS CT, Microsoft Internet Explorer 6 has to be installed on the Cli-ent and Server PCs. The appropriate setup file can be obtained via Microsoft.

To install the Internet Explorer, double-click the setup file. An installation wizard willguide you through the installation process.

For further installation information consult the Microsoft Internet Explorer documenta-tion.

Uninstalling MS Internet Explorer

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


A42022-L5959-C53-4-7619 33


User Manual (UMN)

3.4.2 Installing JavaSoft JAVA Runtime EnvironmentPrior to installing TNMS CT, JavaSoft JAVA Runtime Environment 1.4.2 (InternationalVersion) has to be installed on the Client and Server PCs.

To install Java Runtime Environment, double-click the setup file in the JRE directory onthe TNMS CT V3.0 software CD. An installation wizard will guide you through the instal-lation process.

During the installation, you will be asked to select a browser. If nothing is selected, onlyJava applets designed for the Java Plug-in are executed by the Java Runtime Environ-ment, all other applets are executed by the browsers internal Java VM. To have all Javaapplets to be executed by the Java Runtime Environment, select the appropriate brows-er. The necessity to do so depends on the Java applets to be run. TNMS CT is not af-fected by this setting.

For further installation information consult the Sun Microsystems JRE documentation.

Uninstalling JRE

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

3.4.3 Installing an OSI StackAn OSI stack must be installed on the Server computer before the Server software. TheOSI stack is not required on the Client PC.

To install an OSI stack, proceed as follows:

1. To install an OSI stack, double-click the setup.exe file in the OsiStack directory onthe TNMS CT V3.0 software CD.

2. A welcome window is now displayed. Press Next to continue.

iWith this JRE installation, the data format will be displayed in the default system locale.In order to change this, open Start -> Settings -> Control Panel -> Regional Settings-> Set default... and change your settings accordingly.

iDuring the installation process you will be asked for an NSAP address. Ask your systemadministrator how the NSAP address are handled in your company’s network and haveit determined.See Step 4. for the possibilities to set up the NSAP address.

34 A42022-L5959-C53-4-7619


3. In the Choose Destination Location window, a default installation directory is of-fered for the OSI stack. Press Next to continue.

Fig. 3.2 OSI Stack Installation: Choose Destination Location

4. In the Please select: window, select the option best suited to your company’s net-work:– "My company has own NSAP management", when your system administrator can

provide you with an NSAP address.After pressing Next , the Getting NSAP window is opened.Enter the local NSAP address and press Next ..

– "NSAP address should be derived from MAC address of ethernet card", whenyour system administrator cannot provide you with an NSAP address.After pressing Next , the Getting NSAP window is opened.To obtain the MAC address of your PC open a DOS shell and enter the commandip config /allThe response provides you with IP information.Copy the MAC address from the DOS shell into the field and press Next .

A42022-L5959-C53-4-7619 35


User Manual (UMN)

– "I do not have an ethernet card", to have TNMS CT assigning an NSAP address.After pressing Next , a Question window is opened including an NSAP address.Confirm this window with OK.

Fig. 3.3 OSI Stack Installation: NSAP Address

36 A42022-L5959-C53-4-7619


5. In the Start Copying File s window ensure that the settings displayed are correct,and if so, press Next to continue.

Fig. 3.4 OSI Stack Installation: Start Copying Files

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

7. The window InstallShield Wizard Complete is now shown. Select the option for re-starting the computer, 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 "500". This

is the number of OSI stack connections which can be established simultaneously.– Note the network interface card to which the OSI is connected and check this against

the 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.

A42022-L5959-C53-4-7619 37


User Manual (UMN)

3.4.4 Installing Adobe Acrobat ReaderPrior to installing TNMS CT, Adobe Acrobat Reader 5.0 has to be installed on the ClientPC.

To install Acrobat Reader, double-click the setup file in the Adobe directory on the TNMSCT V3.0 software CD. An installation wizard will guide you through the installation pro-cess.

For further installation information consult the Adobe Acrobat Reader documentation.

Uninstalling Acrobat Reader

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

3.5 Installing the TNMS CT Software

3.5.1 Before You BeginBefore installing TNMS CT, note the following information:– Before installing TNMS CT, previous TNMS CT and UniGATE versions must be un-

installed. Existing configurations should be exported and may be imported with thenew installation.

– The integrated TNMS CT V3.0 software installation consists of the Client, Serverand EML components.

– The Client and Server components may be installed on the same (local or remotelogin) or on separate PCs (remote login).

– The EML packages are installed on the Server PC.– The element managers are installed on the Client PC.– If one or more PCs in the TNMS CT system are equipped with two network adapters,

routing settings must be configured as specified in Chp. 3.6.5 to avoid delays duringconnection setup between PCs.

– To avoid problems during the TNMS CT installation, the user must be logged into theWindows operating system with administrator rights.


38 A42022-L5959-C53-4-7619


3.5.2 Installing TNMS CTTo install TNMS CT, proceed as follows:

1. Double-click the setup.exe file provided on the TNMS CT software CD. A welcomewindow appears, press Next to continue.

Fig. 3.5 TNMS CT Installation: Welcome

2. In the Setup Type window, select the desired mode, depending on your needs andlicenses. Press Next to continue.

Fig. 3.6 TNMS CT Installation: LCT/NCT Mode

iStep 3. is only performed when installing NCT as selected in Step 2. If you did notchoose to install this component, continue with Step 4.

A42022-L5959-C53-4-7619 39


User Manual (UMN)

3. In the Setup Type window, indicate the components you want to install on this ma-chine. Press Next to continue.

Fig. 3.7 TNMS CT Installation: Client/Server Installation

4. A Setup Status window is displayed indicating a registration process.5. In the License Agreement window, scroll down to read the complete text. Press Yes

to accept the license agreement.

Fig. 3.8 TNMS CT Installation: License Agreement

40 A42022-L5959-C53-4-7619


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

Fig. 3.9 TNMS CT Installation: Choose Destination Location

7. In the Please choose NetElements to install window, select the desired networkelements to be installed, and press Next to continue.

Fig. 3.10 TNMS CT Installation: NE Selection

A42022-L5959-C53-4-7619 41


User Manual (UMN)

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

Fig. 3.11 TNMS CT Installation: Start Copying Files

9. A setup status window is now displayed, showing the progress of the TNMS CT 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 may take some time.

Fig. 3.12 TNMS CT Installation: Setup Status

42 A42022-L5959-C53-4-7619


10. 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.

Fig. 3.13 TNMS CT Installation: Complete

The computer is rebooted and the installation completed.

Subsequent configuration settings are described in Chp. 3.6.

3.5.3 Deinstalling TNMS CTThe TNMS CT software can be deinstalled using the Windows control panel. The follow-ing information is removed during deinstallation:– All information used by the TNMS CT application from the Windows Registry.– All program files of the TNMS CT components.– All empty TNMS CT component directories.

Shared files such as OLE-dlls are not removed.

Before uninstalling TNMS CT software, complete the following steps:

1. Export the configuration data to an XML file via File -> Export Configuration .2. Store the local NSAP address of the Server in a text file.3. Close all open element managers.4. Log off the TNMS CT software and exit.5. Stop the service TNMS CT Server on the Server computer

Start -> Settings -> Control Panel -> Administrative Tools -> Services .

Complete the following steps to deinstall the software:

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

2. In the Welcome window, press Next .3. In the Select Type window do not change anything, but press Next .4. In the Maintenance window, select Remove and press Next . The deinstallation

starts and information windows displays the software parts, which are currently dein-stalled. This will take some minutes.

A42022-L5959-C53-4-7619 43


User Manual (UMN)

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

6. The computer is rebooted7. Delete any remaining folders manually in the Windows Explorer e.g.

C:\Program files\Siemens\TNMS CT\8. Check that the TNMS service mentioned above is removed from the services list.

3.5.4 Adding and Removing Individual TNMS CT ComponentsIf individual TNMS CT components (e.g. specific EML packages) are to be installed orremoved, proceed as follows:

1. Insert the installation CD-ROM into the CD-ROM drive.2. Log off and exit TNMS CT.3. If necessary, close all other active applications.4. Stop the TNMS CT Server service on the Server computer under

Start -> Settings -> Control Panel -> Administrative Tools -> Services .5. Start the installation/deinstallation procedure via Start -> Settings -> Control Panel

-> Add/Remove Programs . Select TNMS CT and click the Change/Remove but-ton.

6. In the Welcome window, press Next .7. In the Select Type window you may change from LCT mode to NCT mode and vice

versa. Press Next .

8. In the Important Information window, you are notified about licenses needed addi-tionally.

9. In the Maintenance window, select Modify and press Next .

10. In the Setup Type window, indicate the components you want to install on this ma-chine. Press Next to continue.

11. In the Select TNMS CT components window, the components already installed aredisplayed. Select the components you wish to install or uninstall and press Next tocontinue.

12. In the Please choose NetElements to install window, select the components youwish to install or deinstall, and press Next to continue.

13. In the Repair TNMS CT window, select whether you want to repair the installationsof already installed LCTs additionally, and press Next to continue.

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

15. Once the selected components are installed or deinstalled, the InstallShield Com-plete window is displayed. Select the option for restarting the computer, and pressFinish to complete the process.

iWhen you are changing from NCT mode to LCT mode, you will be restricted to local lo-gin, and only a limited number of features will be available!When you are changing from LCT mode to NCT mode, you will need the appropriatelicenses!

iSteps 8. to 9. are only performed when you did not choose to change the mode as de-scribed in Step 7. If you did change the mode, continue with Step 10.

iStep 10. is only performed when you chose to change the mode to NCT as selected inStep 7. If you did not change the mode to NCT, continue with Step 11.

44 A42022-L5959-C53-4-7619


16. Restart the PC to update your installation.

3.6 Measures after CommissioningAfter the TNMS CT software and relevant 3rd-party software has been installed, TNMSCT still must be configured. The following information should be taken into account:– Configuring Windows XP firewall (when using a server with Windows XP operating

system) (see Chp. 3.6.1)– PPP Dial-up Setup for Q3 Network Elements (see Chp. 3.6.3)– Initial Configuration (see Chp. 3.6.3)– Migration (see Chp. 3.6.4)– Routing Settings (see Chp. 3.6.5)

3.6.1 Configuring Windows XP firewallWhen the TNMS CT server is installed in a PC with a Windows XP operation system,the firewall must be configured in order to allow other PCs within the network (withTNMS CT client software) to connect to the server. If the TNMS CT client and serversoftware are installed in the same PC (with Windows XP OS), then there is no need toconfigure the firewall.

In order to configure the firewall complete the following steps:

1. Open Start -> Settings -> Control Panel -> Security Center -> Windows Firewallto open the Windows Firewall window.

2. On the Exceptions tab, click the Add Port and configure a TCP port with the name“TNMS CT” and the port number “2002”.

3. Click the Choose Scope button, select the My Network radio button and click OKto save the changes.

4. Click OK to add the port to the exception list.

3.6.2 PPP Dial-up Setup for Q3 Network ElementsIn order to connect to a Q3 network element via RS232, complete the following steps tosetup a new dial-up network connection:

3.6.2.1 Windows XP1. Open Start -> Programs -> Accessories -> Communications -> Network Con-

nections to open the Network Connections window. Click on the Create a newconnection icon in the Network Tasks panel on top left to open the Network Con-

A42022-L5959-C53-4-7619 45


User Manual (UMN)

nection Wizard .Click Next to continue.

Fig. 3.14 Network Connection Wizard: Welcome

2. In the Network Connection Type window, select Set up an advanced connection .Click Next to continue.

Fig. 3.15 Network Connection Wizard: Network Connection Type

3. In the Advanced Connection Option window select Connect directly to anothercomputer .Click Next to continue.

46 A42022-L5959-C53-4-7619


Fig. 3.16 Network Connection Wizard: Advanced Connection Options4. In the Host or Guest window, select Guest .

Click Next to continue.

Fig. 3.17 Network Connection Wizard: Host or Guest

A42022-L5959-C53-4-7619 47


User Manual (UMN)

5. In the Computer Name enter a name for the new connection, e.g. “MPU-F”.Click Next to continue.If a connection dialog appears, cancel it.

Fig. 3.18 Network Connection Wizard: Complete

6. In the Select a Device window, select either Communications Port (COM1) orCommunications cable between two computers (COM1) . The availability ofthese two options depends on whether a “Communications cable” modem has al-ready been installed or not. If necessary, Windows XP automatically installs this mo-dem.Click Next to continue.

Fig. 3.19 Network Connection Wizard: Select a Device

48 A42022-L5959-C53-4-7619


7. In the Connection Availability window, select For all users .Click Next to continue.

Fig. 3.20 Network Connection Wizard: Connection Availability

8. In the Completing the Network Connection Wizard window click Finish to com-plete your settings.If a connection dialog appears, cancel it.

9. Open Start -> Programs -> Accessories -> Communications -> Network Con-nections to open the Network Connections window. Select the icon representingthe previously configured new connection, and select from its context menu -> Prop-erties . The Connection Properties: General window is opened.Click Configure to setup the modem.

Fig. 3.21 Connection Properties: General

10. In the Modem Configuration window, select “19200” for Maximum speed and un-check the feature Enable hardware flow control .Click OK to confirm your settings.

A42022-L5959-C53-4-7619 49


User Manual (UMN)

Fig. 3.22 Modem Configuration

11. In the Connection Properties window select the Advanced tab and click the Set-tings button to open the Windows Firewall window and configure the firewall set-tings for this connection.

12. In the Advanced tab, clear the checkbox for the “MPU-F” connection under the Net-work Connection Settings pane, to deactivate the firewall for this connection.

13. In the Connection Properties window select the Networking tab and uncheck allprotocols except for Internet Protocol (TCP/IP) .Select Internet Protocol (TCP/IP) from the list and click Properties .

Fig. 3.23 Connection Properties: Networking

14. In the Internet Protocol (TCP/IP) Properties window, click Advanced...

50 A42022-L5959-C53-4-7619


Fig. 3.24 Internet Protocol (TCP/IP) Properties15. In the Advanced TCP/IP Settings window, uncheck Use default gateway on re-

mote network if you are connected to a LAN and the serial connection at the sametime. This way your LAN connection will still be available while your are connectedvia serial line.Click OK to confirm your settings and close all open windows.

Fig. 3.25 Advanced (TCP/IP) Settings

16. In TNMS CT Main window open Configuration menu -> DCN Management entry.In the DCN Management View navigate to the Serial Line Serve r -> Q3 Serial LineChannel a nd open the context menu -> Properties...In the Properties window open the QB3 Channel tab. Check the Use PPP option

A42022-L5959-C53-4-7619 51


User Manual (UMN)

and enter the name of the Phonebook Entry as defined previously in Step 6.Click Apply to confirm your settings.

Fig. 3.26 Properties: QB3 Channel

3.6.2.2 Windows 2000 Professional1. Open Start -> Settings -> Network and Dial-up Connections . The Network and

Dial-up Connections Window is opened.Double-click on the Make New Connection icon, to open the Network ConnectionWizard .Click Next to continue.

Fig. 3.27 Network Connection Wizard: Welcome

52 A42022-L5959-C53-4-7619


2. In the Network Connection Type window, select Connect directly to anothercomputer .Click Next to continue.

Fig. 3.28 Network Connection Wizard: Network Connection Type

3. In the Host or Guest window, select Guest .Click Next to continue.

Fig. 3.29 Network Connection Wizard: Host or Guest

4. In the Select a Device window, select either Communications Port (COM1) orCommunications cable between two computers (COM1) . The availability ofthese two options depends on whether a “Communications cable” modem has al-ready been installed or not. If necessary, Windows 2000 Professional automatically

A42022-L5959-C53-4-7619 53


User Manual (UMN)

installs this modem.Click Next to continue.

Fig. 3.30 Network Connection Wizard: Select a Device

5. In the Connection Availability window, select For all users .Click Next to continue.

Fig. 3.31 Network Connection Wizard: Connection Availability

6. In the Completing the Network Connection Wizard window, enter a name for thenew connection, e.g. “MPU-F”.

54 A42022-L5959-C53-4-7619


Click Finish to complete your settings.If a connection dialog appears, cancel it.

Fig. 3.32 Network Connection Wizard: Complete

7. Open Start -> Settings -> Network and Dial-up Connections . The Network andDial-up Connections Window is opened.Select the icon representing the previously configured new connection, and selectfrom its context menu -> Properties . The Connection Properties: General windowis opened.Click Configure to setup the modem.

Fig. 3.33 Connection Properties: General

A42022-L5959-C53-4-7619 55


User Manual (UMN)

8. In the Modem Configuration window, select “19200” for Maximum speed and un-check the feature Enable hardware flow control .Click OK to confirm your settings.

Fig. 3.34 Modem Configuration

9. In the Connection Properties window select the Networking tab and uncheck allprotocols except for Internet Protocol (TCP/IP) .Select Internet Protocol (TCP/IP) from the list and click Properties .

Fig. 3.35 Connection Properties: Networking

56 A42022-L5959-C53-4-7619


10. In the Internet Protocol (TCP/IP) Properties window, click Advanced...

Fig. 3.36 Internet Protocol (TCP/IP) Properties

11. In the Advanced TCP/IP Settings window, uncheck Use default gateway on re-mote network if you are connected to a LAN and the serial connection at the sametime. This way your LAN connection will still be available while your are connectedvia serial line.Click OK to confirm your settings and close all open windows.

Fig. 3.37 Advanced (TCP/IP) Settings

12. In TNMS CT Main window open Configuration menu -> DCN Management entry.In the DCN Management View navigate to the Serial Line Serve r -> Q3 Serial LineChannel a nd open the context menu -> Properties...In the Properties window open the QB3 Channel tab. Check the Use PPP option

A42022-L5959-C53-4-7619 57


User Manual (UMN)

and enter the name of the Phonebook Entry as defined previously in Step 6.Click Apply to confirm your settings.

Fig. 3.38 Properties: QB3 Channel

3.6.3 Initial Configuration of TNMS CTOnce the TNMS CT software has been installed, and the computer restarted, the TNMSCT system can be configured. The main steps to be completed during configuration arelisted below. Additional information is provided in the online help under Initial Configu-ration .

Start TNMS CT

Start the TNMS CT interface via Start -> Programs -> TNMS CT .

Login

Log on TNMS CT via the displayed login dialogue or by clicking the Login icon in theTNMS CT toolbar (see Chp. 4.3.2). When starting the TNMS CT application, the Logindialog is opened automatically.

Fig. 3.39 Login window

iIf TNMS CT is the first java application to be started on a new installed PC with WindowsXP OS, answer the raised message box for jawaw with "unblock".

58 A42022-L5959-C53-4-7619


– In the field Server , enter the name of the PC where the TNMS CT Server is installed.If you are logging on directly to the PC where the TNMS CT Server is installed, enter"localhost".

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

– When you log on for the first time, the field Password is not completed.– After confirming the entry via the Login button, change the password for the default

administrator account as requested.

Import licenses

Before working with TNMS CT, its components have to be licensed. The following li-cense types are distinguished:– Basic license

Each TNMS CT system requires its own license.– NE license

Each NEC managed by TNMS CT requires its own license.– Optional feature license

In case of additionally installed optional features, further licenses are required aswell.

In order to import the licenses open the License Information window via Configura-tion -> License... Here, click Import... on the toolbar and select the path and file of yourlicense XML file.

Depending on whether SW and/or HW have been pre-installed by Siemens staff, youhave been provided with the necessary license file, or you have to request it via e-mail.In case of problems concerning licensing, please contact SIEMENS Technical Sales.

Configure user accounts

A default administrator account is created during installation. Additional accounts cannow be created as required.

Define log configuration settings

The available size of the various log files on the hard disk should be determined. Set-tings can be entered for the size of the Alarm Log and System Message Log.

All log files are installed in the TNMS installation directory under Logs. On the HD parti-tion where the TNMS is installed there should be at least 1 GB free disk space duringoperation. If the log file size will be changed (expanded) check the necessary disk spaceagain.

Configure Server

After TNMS CT installation, the server, i.e. the Serial Line Server for local connection orthe TNMS CT Server for Ethernet connection, must be linked up to the TNMS CT via theDCN Management View (see Chp. 4.3.6).

Configure and activate DCN channels

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

iIf you are use TNMS CT in LCT mode, the field Server will not be active as Client andServer are always installed on the same machine.

A42022-L5959-C53-4-7619 59


User Manual (UMN)

Configure network elements

In the DCN Management View select the Serial Line Server and check the propertiesof all pre configured subordinate nodes. It is not necessary to activate a node becausethis is performed by the automatic connection feature of the Serial Line View.

Next select the TNMS CT Server and add the appropriate DCN channels. Then networkelements can be added to the DCN channels. The required network element type canbe selected from the list. Alternatively, GNEs may be added to the channels, which willautomatically discover the NEs in the associated OSPF area. The NEs are configuredby completing each tab page as described in the Online Help.

Setup the network map

The network map can now be set up using the TNMS CT Network View . This must bedone on the basis of planning data (when installing the system the first time) or by mi-gration of data used in formerly software versions (in case of software updates).

The Serial Line View allows the establishment of a connection to a single NE using theSerial Line Interface (F-Interface).

Further settings

Further setting can be done depending on the individual customers needs, e.g. colorsettings for alarms.

3.6.4 MigrationTNMS CT V3.0 supports migration of NE configuration data from UniGATE V7.0 andV7.1. In order to accomplish the migration, export your network configuration data intoan xml file via UniGATE. In TNMS CT this file can be imported via File -> Import Con-figuration... .

3.6.5 Routing Settings for PCs with Multiple Network AdaptersIf one or more PCs in your TNMS CT system have multiple network adapters (for net-working protocols in addition to TCP/IP), delays may occur in connection setup betweenthe various TNMS CT machines.

For example:– PC A has one network adapter (for the LAN segment to PC B)– PC B has two network adapters (one for the LAN segment to PC and one for an ex-

ternal LAN segment)

Because PC B has two network adapters, it also has two IP addresses.

When establishing communication with PC A, PC B transmits both IP addresses. If thefirst IP address sent by PC B is the address for the common LAN segment, communi-cation can be established without any problems. But if the first IP address sent by PC Bis the address for the external LAN segment, and a gateway PC with routing informationis not available, time out cycles will result in delayed communication.

The following connections may then be affected:

iThe Serial Line View is supported for LCT and NCT mode via F-Interface.The Network View is supported for LCT and NCT mode via Ethernet Interface, i.e. QB3Interface.

60 A42022-L5959-C53-4-7619


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 Advancedin the toolbar, and from the list that appears select Advanced Settings...

3. The Advanced Settings window is now displayed. In the Connections list, selectLocal Area Connection . The list beneath (called Bindings for Local Area Con-nection ) 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 Provider Order

tab.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 ofthe list.

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

Connection Affected Task

Client -> Server Starting the LCT application from a Client and communi-cating with NEs

Server -> Client Starting the Client application.

Tab. 3.1 Affected Connections

A42022-L5959-C53-4-7619 61


User Manual (UMN)

4 OperationThis chapter provides a guideline of how to work with the TNMS CT user interface:– Working With the GUI (see Chp. 4.1)– Basic Operation (see Chp. 4.2)– Graphical User Interface (see Chp. 4.3)

4.1 Working With the GUIThis chapter describes how to work with the TNMS CT graphical user interface (GUI) ingeneral. Working with the GUI is based on working with Windows operating systems.

4.1.1 TNMS CT CharacteristicsIn addition to the Windows graphical user interface, the TNMS CT GUI provides somespecific and useful features.

Blue Frames

Control displays, which do not contain the information currently stored inside the NEs,are bordered with a blue frame. Tab. 4.1 below shows the rules for framing control dis-plays.

4.1.2 Working With the MouseBoth the left and the right mouse button are used when working with the GUI. The leftmouse button may be used for the following actions:– Select a context menu from the top bar of a window.– Select a menu item.– Select a function using the features available in a window (buttons, selection menus

etc.).– Confirm an action (e.g. Apply ).

A great number of operations within both interfaces can only be invoked via contextmenus. A context menu is called by clicking an object of the graphical user interface with

iAny step-by-step tasks as well as a detailed description of the GUI can be found in theOnline Help which is also available in the appendix of this document.

Data to be displayed inthe window is

Control Displays Blue Frame

Initialized Data value from NE No

Any rated modified data value Yes

Not initialized Default value Yes

Any rated modified data value Yes

Tab. 4.1 Blue Framing

62 A42022-L5959-C53-4-7619


the right mouse button. This displays a selection of menu items which are relevant forthe selected object in the given situation.

4.1.3 Working With the KeyboardThe TNMS CT user interface is driven by context menus (click on objects in the userinterface with the right mouse button) and therefore cannot be operated without amouse. Therefore this manual refers throughout to mouse control. However, it is possi-ble to use the keyboard to perform the actions listed in the main menus. Hold down the<Alt> key and press the underlined letters for the menu items you want to use.For example:Main window -> Configuration menu -> Licenses... entry = <Alt>+<C>, <L> .

If there are no underlined letters visible, please press <Alt> .

To open a context menu you can also use <Shift>+<F10> .

By using the <TAB> key it is possible to jump between the different window panels.

In the remaining chapters of this manual it is presumed that the operator works with amouse.

4.1.4 Working With the Online HelpThe user interfaces contain Online Help systems. The help systems provide informationabout the window contents, menus and meanings of used icons. Via the help table ofcontents you can also display essential steps of important operating sequences.

Help can be requested in any of the following ways:• After calling up Help from the menu bar, you can search for topics via the table of

contents, via the index or via a full-text search.• Clicking the Help button in the current window, displays information about the win-

dow contents.• Pressing <F1> displays information about the contents of the window which is active

at the moment.

4.2 Basic OperationIn this chapter, the following basic administrative operations of TNMS CT are described:– Starting a TNMS CT Session (see Chp. 4.2.1)– Starting and Stopping TNMS CT Server (see Chp. 4.2.2)– Activating and Deactivating TNMS CT Server (see Chp. 4.2.3)– Setting Date and Time Zone (see Chp. 4.2.4)– Starting Element Manager Applications (see Chp. 4.2.5)– Administrating NE Write Access (see Chp. 4.2.6)– Terminating a TNMS CT Session (see Chp. 4.2.7)

iThe offered menus and context menus depend on the operator’s user class.

iUnless the text states otherwise, always use the left mouse button for clicking and dou-ble-clicking.

iThe Online Help gives detailed information on the tasks that are to be performed withTNMS CT. It also provides detailed description about the individual windows, fields, andicons used in TNMS CT.

A42022-L5959-C53-4-7619 63


User Manual (UMN)

4.2.1 Starting a TNMS CT SessionThe TNMS CT Client is started via Start -> Programs -> TNMS CT . Once the TNMSCT Client has been started, the operator can enter the login data. Functions authorizedby the operator’s user class can now be accessed.

The Client contacts the Server and requests alarm information, port and connection da-ta, and the data required for mapping the network. If complete data is not available forcertain network elements, these are shown as unavailable on the user interface by a boxcontaining three question marks.

If the TNMS CT Server is not available, an error message is displayed.

4.2.2 Starting and Stopping TNMS CT ServerTNMS CT Server is started automatically on system startup, before any user is loggedon. Once it has been started, a connection to all configured and activated network ele-ments is established and their data is uploaded. An icon is displayed in the Windows2000/Windows XP taskbar.

Once the Server has started, it is always active. Moreover, terminating the Client doesnot result in stopping the Server and disconnecting from the NEs. To stop the Server,you have to stop its service via Start -> Control Panel -> Administrative Tools -> Ser-vices .

4.2.3 Activating and deactivating TNMS CT ServerA TNMS CT Server and each DCN object managed by the Server can have the activa-tion state activated or deactivated. The state is changed in the DCN Management View(see Chp. 4.3.6). If the TNMS CT Server is started, connections will be established forall activated network elements.

4.2.4 Setting Date and Time ZoneTNMS CT allows to switch between local time, GMT and CST via the menu bar entryView -> Time Display in the Client application.

4.2.5 Starting Element Manager ApplicationsThe element manager applications are started via the TNMS CT network map (see Chp.4.3.4). A data connection is established to the relevant NE which allows the user to ex-ecute required functions directly at the NE.

A Multi NE, such as MSN, is handled the same way. Consequently, the MSN Manageris started via the network map. Via the MSN Manager, the element managers of the NEsmanaged by the MSN are started.

4.2.6 Administrating NE Write AccessTNMS CT only administers write access to managed network elements which supportthis feature via the context menu of the NE icon on the network map. Older QD2 NEsmight require an additional request via their element managers. Consequently, theTNMS CT operator also has limited control over external LCT write access.

64 A42022-L5959-C53-4-7619


4.2.7 Terminating a TNMS CT SessionA TNMS CT session is terminated when the user logs off. All windows are closed andaccess is only provided to the login function. The Server has to be terminated on its own(see Chp. 4.2.2).

4.3 Graphical User InterfaceThis chapter describes how to operate the TNMS CT GUI.

The TNMS CT GUI gives access to all functions for supervision, operation, configurationand maintenance of the network. The set of functions available to each individual oper-ator depending on the operator’s user class which is defined by the administrator.

Via the TNMS CT GUI you can also start the element manager applications (e.g. the EMof an SMA16/4 or the MSN Manager) to control and configure individual network ele-ments.

The TNMS Client user interface consists of the following parts:• Menu Bar (see Chp. 4.3.1)• Toolbar (see Chp. 4.3.2)• Status Bar (see Chp. 4.3.3)• Network View (see Chp. 4.3.4)• Serial Line View (see Chp. 4.3.5)• DCN Management View (see Chp. 4.3.6)

Fig. 4.1 shows an example of the TNMS CT main window indicating some of the avail-able functions.

Fig. 4.1 TNMS CT Graphical User Interface

Working Area

MinimizedWindows

Menu Bar

Toolbar

Status Bar

Network View

A42022-L5959-C53-4-7619 65


User Manual (UMN)

4.3.1 Menu BarFig. 4.2 shows the menu bar of the TNMS CT main window with its menu items. Whenyou click on one of these menu items, the pull-down menu specific to the menu itemopens.

Fig. 4.2 Menu Bar

Tab. 4.2 shows and briefly explains the individual pull-down menus.

File Working With the Program Application

Export Configuration... Export your DCN and Client configuration data to an XML file.

Export of client configuration is available for NCT only.

Import Configuration... Import DCN and Client configuration data from an XML file to your TNMS CT sys-

tem.

Import of client configuration is available for NCT only.

Save Select one of the following lists/logs to be stored in SDF format:

- System Message Log

- Alarm List (NCT mode only!)

- Alarm Log (NCT mode only!)

Print Select one of the following lists/logs to be printed in SDF format:

- System Message Log

- Alarm List (NCT mode only!)

- Alarm Log (NCT mode only!)

Page Setup... Configure your page layout that is used for saving and printing lists and logs.

Exit Exit the TNMS CT application.

View Selecting the Type of View

Find NE... Find an NE on the network map. The found NE will be framed.

System Message Log... Display the System Message Log window.

Open Transactions... Display the Open Transactions window.

Port Connection... Display the Port Connection window to create, modify or delete PCs.

NCT mode only!

Port Connection List... Display the Port Connection List window.

NCT mode only!

Time Display Toggle between the following time display options:

- Local Time

- GMT

- US Central Time

Tab. 4.2 Menu Bar Entries

66 A42022-L5959-C53-4-7619


Window Style Toggle between the following styles for the currently selected window:

- MDI: Chose from a list of popup windows to be switched to MDI (internal) style.

- Popup: The window can be moved out of the TNMS CT main window.

- Docked: The window is docked to the bottom of the main window.

Functionality depends on the individual window type!

Toolbar Display or hide the toolbar.

Status Bar Display or hide the status bar.

Fault Configuring Alarms

Alarm List... Display a list of all currently raised alarms.

NCT mode only!

Alarm Log... Display a historical list of alarms.

NCT mode only!

Acknowledge All Acknowledge all alarms in your network.

NCT mode only!

Load Filter... Load alarm filter settings stored in a file on the server.

NCT mode only!

Save Filter... Save your alarm filter settings to a file on the server.

NCT mode only!

Settings... Configure the alarm settings including colors, sounds, list, log, statistic and ex-

ternal alarm notification.

NCT mode only!

Configuration Configuring Various Tasks

DCN Management... Work in the DCN Management View .

Serial Line... Work in the Serial Line View .

Connect Connect to all network elements.

Disconnect Disconnect from all network elements.

General Settings... Configure the application and System Message Log settings.

License... Display information on your licenses and import new licenses.

Background... Assign a background bitmap to your network map or set the background color.

NCT mode only!


A42022-L5959-C53-4-7619 67


User Manual (UMN)

4.3.2 ToolbarThe toolbar (see Fig. 4.3) runs along the top edge of the main window above the work-ing area. Clicking on one of these buttons with the left mouse button provides quick andparticularly easy access to certain frequently used functions.

Security Security and User Management

Login... Log on TNMS CT Server.

Logoff Logout from TNMS CT Server.

Password... Change your user password.

User Administration... Configure user accounts.

Settings... Configure global password settings and the advisory message.

Tools Working With Tools

NE User Configuration... Broadcast user configuration to certain Q3 network elements.

NCT mode only!

Window Configuring the Display of the TNMS Windows

Cascade Display all currently open windows overlapping each other.

Tile Horizontally Display all the currently open windows next to each other.

Tile Vertically Display all the currently open windows on top of to each other.

Arrange Icons Rearrange the icons inside the main window.

1 Network Management

View

2 System Message Log

List of all the currently open windows in the form of sequentially-numbered menu

items. The selected window (in the foreground) is indicated by a tick.

Help Working With the Online Help .

Help Topics... Open the Online Help.

On Window... Open the Online Help on the currently selected window <F1>.

User Manual Open the User Manual as PDF file using Acrobat Reader.

System Information Display the system information and start element managers offline.

About... Display information on the TNMS application.


68 A42022-L5959-C53-4-7619


Fig. 4.3 Main Toolbar

In addition to the main window toolbar, many other TNMS CT windows provide their owntoolbars. The functions of the toolbar buttons are briefly described in Tab. 4.3.

4.3.3 Status BarThe status bar (see Fig. 4.4) runs along the bottom of the main window. It gives infor-mation on the operating states and displays important messages, such as alarms, inshort form.

Fig. 4.4 Status Bar

Icon Function Menu Entry Opens Window

Log on or log off the TNMS CT Server. Security menu -> Login... entrySecurity menu -> Login... entry

Login

Work with the Serial Line View . Configuration menu -> SerialLine... entry

Serial Line View

Work with the DCN Management View . Configuration menu -> DCN Man-agement... entry

DCN Management

Localize an NE on the network map. View menu -> Find NE... entry Network View

Print the contents of the active window. File menu -> Print... entry

Open the Online Help. Help menu -> On Window... entry Online Help

Tab. 4.3 Main Toolbar Icons

TimeNotification Area Alarms Data SemaphoreSSLOperator Server Name Server State

A42022-L5959-C53-4-7619 69


User Manual (UMN)

Tab. 4.4 describes the TNMS CT status bar from left to right.

4.3.4 Network ViewThe Network View provides graphical representation of your network. Fig. 4.5 showsan example of a network map indicating objects with context menus (ovals) and otherobjects (rectangles).

Fig. 4.5 Network View

Orientation within the Network View can be improved by using a background bitmap.For example, you can attach the picture of a city map to be displayed in the backgroundof the network plan and position your network elements in this map according to theirreal location.

Notification Area A short help text for the currently selected window, menu entry ortoolbar button.

Operator User ID of the currently logged in operator.

Server Name Name of the connected Server.

Server State State of the TNMS CT Server, i.e. idle, starting up, shutting downor running.

Time Time display, i.e. local, GMT or CST.

Alarms Alarm severities and counters for each severity, i.e. indetermi-nate, critical, major, minor and warning (from left to right). For in-formation on alarm severities consult the Online Help.

SSL Secure connection to the server is established.

Data Semaphore Open transactions, i.e. no open transactions (green), open trans-actions (red).

Tab. 4.4 Status Bar Components

Link

NE

Network Map

Port Connection

70 A42022-L5959-C53-4-7619


Moreover, the Network View offers quick access to information concerning single NEs(e.g. current access state, alarm state).

Each item of the Network View offers an individual context menu as shown in Tab. 4.6.

NE

Start Element Manager... Open the GUI of the local element manager of the selected NE.

The availability of this menu items depends on the individual NE type!

File Transfer... Transfer files between TNMS CT and the selected NE for upgrade purposes.

The availability of this menu items depends on the individual NE type!

Links... Configure links between NEs on the network map.

NCT mode only!

Port Connection... Display the Port Connection window to create, modify or delete PCs.

NCT mode only!

Port Connection List... Display the Port Connection List window.

NCT mode only!

Alarms You have the following options to handle alarms (NCT mode only!):

Alarm Statistic... Display graphical statistics of the alarms sent by the selected NE.

Alarm List... Display an overview of all currently raised alarms of the selected NE.

Alarm Log... Display a historical overview of all alarms of the selected NE.

Acknowledge All Acknowledge all alarms of the selected NE.

Access Control Control the write access on the selected NE with one of the following options de-

pending on the NEs interface type:


Disconnect Disconnect from the selected network element.

Request Write Ac-

cess

Get write access on the selected NE unless any other LCT has write access on

it.

Release Write Ac-

cess

Allow other LCTs to get write access on the selected NE.

Resynchronize Data start a new NEC initialisation for the selected network element.

Size of NE Symbols Set the size of the NE icons on the network map. The following options are pos-

sible:

- Enlarge or Scale down

- Enlarge if disconnected or Do not enlarge if disconnected

- Symbols related to Alarms: Do not enlarge on alarms or Enlarge on critical un-

acknowledged, major unacknowledged, minor unacknowledged alarms or on

unacknowledged warnings.

Properties... Display information on the selected NE.

Tab. 4.5 Network View Context Menus

A42022-L5959-C53-4-7619 71


User Manual (UMN)

Port Connection


sible:






Port Connection List... Display the Port Connection List window filtered for the selected port connec-

tion.

NCT mode only!


Disconnect Disconnect from all network element.

Acknowledge All Acknowledge all alarms.


Lock NE Symbols Fix the NE icons on the network map.


NCT mode only!

Network Map


sible:







Disconnect Disconnect from all network element.

Acknowledge All Acknowledge all alarms.


Lock NE Symbols Fix the NE icons on the network map.

Links... Configure links between NEs on the network map.

NCT mode only!


NCT mode only!

Tab. 4.5 Network View Context Menus

72 A42022-L5959-C53-4-7619


4.3.5 Serial Line ViewThe Serial Line View provides graphical representation of your serial line connection.Fig. 4.6 shows an example of the network map indicating objects with context menus.

Fig. 4.6 Serial Line View

Each item of the Serial Line View offers an individual context menu as shown inTab. 4.5.

4.3.6 DCN Management ViewThis chapter provides an overview of the TNMS CT DCN Management View .

The DCN Management is operated via a toolbar (see Chp. 4.3.6.1) and via a contextmenu of the individual objects of the DCN Management tree (see Chp. 4.3.6.2). TheDCN Management tree consists of the following objects in hierarchical order:• Server• DCN Channel• Multi NE• NE

In the DCN Management tree, there are two Server nodes available:– Serial Line Server contains pre configured DCN channels and network elements for

local connections via RS232.– TNMS CT Server allows to configure DCN channels and network elements for local

and remote connections via Ethernet/DCC.

The managed DCN objects are displayed in their current connection state and hierarchi-cal relation in a tree.

Fig. 4.7 below gives an example of the DCN Management View .

NE

NE

Connect Connect to a network element, which is clearly identifiable, via the serial line inter-

face.

Automatic Connection Connect to a network element via the serial line interface. TNMS CT tests all chan-

nels until it can establish a suitable connection.

Tab. 4.6 Serial Line View Context Menus

A42022-L5959-C53-4-7619 73


User Manual (UMN)

Fig. 4.7 DCN Management View

4.3.6.1 DCN Management ToolbarThe DCN Management toolbar (see Fig. 4.8) runs along the top edge of the DCN Man-agement View above the working area. Clicking on one of these buttons with the leftmouse button provides quick and particularly easy access to certain frequently usedfunctions.

Fig. 4.8 DCN Management Toolbar

The functions of the DCN Management toolbar buttons are briefly described in Tab. 4.7.

Toolbar

Server

NE

DCN Channel

Multi NE

Discovered NE

OSPF area

GNE

Managed NEs

74 A42022-L5959-C53-4-7619


4.3.6.2 DCN Management TreeEach DCN object provides the same sort of context menu. Tab. 4.8 shows and brieflyexplains the generic context menu entries.

Icon Function Context Menu Entry Opens Window

Display the properties of the

selected DCN object.

Properties... entry Properties

Add a new subcomponent to

the selected DCN object.

Add... entry Properties

Delete the selected DCN ob-

ject.

Delete... entry

Duplicate the selected DCN

object.

Duplicate... entry Properties

Find an NE in the DCN Man-

agement tree.

Find NE

Store the complete DCN tree in

SDF format.

Print the complete DCN tree.

Close the DCN Management

View .

Network View

Open the Online Help. Online Help

Tab. 4.7 DCN Management Toolbar Icons

DCN Object

Add... Add a subcomponent to the selected DCN object.

If a channel or NE is added, a list of objects is opened to select the desired channel

or NE. Then, the Properties window of the selected objected is opened, where in-

formation on the selected channel or NE has to be entered.

Delete Delete the selected DCN object.

Activate/Deactivate Activate or deactivate the selected DCN object.

Duplicate... Duplicate the selected DCN object.

Tab. 4.8 DCN Management Tree Entries

A42022-L5959-C53-4-7619 75


User Manual (UMN)

Copy NE Name into ID

Name

Propagate the actual NE name into the ID name field for NEs, newly discovered

by a GNE.

Properties... Display and modify the properties of the selected DCN object. The object has to

be deactivated in order to be modified!

Tab. 4.8 DCN Management Tree Entries

76 A42022-L5959-C53-4-7619


A42022-L5959-C53-4-7619 77


User Manual (UMN)

5 AbbreviationsCE Communauté Européenne

CST Central Standard Time

CT Craft Terminal

DCC Data Communication Channel

DCN Data Communications Network (G.784)

DHCP Dynamic Host Configuration Protocol

DLL Dynamic Link Library

DNS Domain Naming Service

EML Element Management Layer

EN European Norm

ESD Electrostatic Discharge

FTP File Transfer Protocol

GMT Greenwich Mean Time

GNE Gateway Network Element

GUI Graphical User Interface

GUIMN Graphical User Interface Manual

JRE Java Runtime Environment

LAN Local Area Network

LCT Local Craft Terminal

MAC Media Access Control

MSN Multi Service Node

NCT Network Craft Terminal

NE Network Element

NEC Network Element Controller

NSAP Network Service Access Point

OLE Object Linking and Embedding

OSI Open System Interconnection

OSPF Open Shortest Path First

PC Personal Computer

PCI Peripheral Component Interconnect

PDF Portable Document Format

PPP Point to Point Protocol

RAID Redundancy Array of Independent Disks

SDF System Data Format

SNMP Simple Network Management Protocol

SP Service Pack

SSL Secure Socket Layer

SW Software

TCN Threshold Crossing Notification

TCP/IP Transmission Control Protocol/Internet Pro-

78 A42022-L5959-C53-4-7619


tocol ,TMS Telecommunication Management System

TNMS Telecommunication Network ManagementSystem

UPS Uninterrupted Power Supply

WAN Wide Area Network

WINS Windows Internet Naming Service

XML Extended Markup Language

A42022-L5959-C53-4-7619 79


User Manual (UMN)

6 IndexAAccess control 70Acknowledge 66, 70, 71Add NetServer 74Additional hardware 31Additional TNMS components

Installation 43Adobe Acrobat Reader 37Alarm 70

Filter 66List 66, 70List and Log 23, 65Log 24, 66, 70Statistics 23, 70

Antistatic mat 27Application

Settings 66Architecture

Client/Server 14Network 14Software 17System 14

Automatic recognition 22Automatic topology discovery 22

BBackground bitmap 66, 71Basic information

Personnel requirements 26Blue frame 61Broadcast user configuration 67

CCabling 28CE conformity 26Client components 17Client/Server architecture 14Commissioning 27

Final tasks 44Hardware recommendations 28Installation and cabling 28Installation sequence 29Preparation 27Uninterruptible power supply 28

CommunicationInterface 21Loss 22

Configuring Windows XP firewall 44Context Menu 61, 62Context menu 61, 62Copy NE name into ID name 75

DDate and time settings 63, 65DCN 14

Channel 58, 72Management 22, 58, 63, 66, 72MSN 72NE 72Object 63, 74Object Properties 75

DCN channelDCN management 20

DCN Management Tree 74Deactivate 74Delete 74Delivery 28DHCP 31Dial-up connection 44Discover topology 22DNS 31Duplicate 74

EElectrostatic-sensitive devices 27Element manager 18, 70

Start 63Start offline 67

EML packages 18, 28Installation 43

ESD symbol 27Exit application 65Export 18, 65

FFault

Management 22, 66Settings 66

File transfer 70Find 65, 71Firewall

Windows XP 44FSP 28

GGateway NE

see GNEGNE 59

DCN management 21Graphical User Interface 17, 64Grounding bracelet 27GUI

see ’Graphical User Interface’

80 A42022-L5959-C53-4-7619


GUIMN 9

HHardware recommendations 16, 28

Uninterruptible power supply 28

IIcon 68, 70, 71, 74Import 18, 65Initial configuration 57Installation

Additional TNMS components 43Adobe Acrobat Reader 37Cabling 28Individual components 43Internet Explorer 32Java Runtime Environment 33, 37Licensing 30Operating system 30OSI stack 33PCI I/O card 31Sequence 29Third-party software 32TNMS CT 37

Installation software 28EML packages 28Internet Explorer 28JavaSoft JAVA Runtime Environment 29OSI stack 29TNMS CT 28Windows OS 28

Internet Explorer 28, 32

JJava Runtime Environment 33

KKeyboard 62

LLCT mode 19Licensing 30, 66

Import 58Software 25

Links 20, 70, 71Lock 71Log management 24, 58Login 57, 63, 67, 68

MMAC address 34Measures after commissioning 44

Initial configuration 57

Routing settings 59Measuring equipment 27Menu bar 65Migration 59Modules 27Mouse 61, 62MSN 19, 28, 63, 72Multiple network adapters 59

NNCT mode 19NE 18, 19, 59, 70, 72

Automatic connection 72Connect 66, 70, 71, 72Controller 18Disconnect 66, 70, 71Element manager 18Properties 70Supported 14

NetServer 72Frame 18

NetworkArchitecture 14Interface 21Management 19, 20Map 59

Network elementDCN management 21

Network interface 22Network map 71Network View 59, 69, 70NSAP address 34

OOnline Help 62, 67, 68, 74Open transactions 65, 69Operating system

Installation 30OSI stack 29

Installation 33

PPassword 67PCI I/O card 31Port connection 20, 65, 70, 71Port connection list 65, 70, 71Print 65, 68, 74Protective measures 26Protocol information 30

DHCP 31DNS 31WINS 31

A42022-L5959-C53-4-7619 81


User Manual (UMN)

QQ3 22QB3M 28QD2 22QST 22QSTV2 22

RRelease 70Remote login 24Request 70Resynchronization 70Routing settings 59

SSafety precautions 26

Antistatic mat 27Electrostatic-sensitive devices 27ESD symbol 27Grounding bracelet 27Labeling 27Measuring equipment 27Modules 27Voltage 27

Save 65Scaled start-up 22Screen level integration 24Security 67

Log 23Settings 67

Serial line interface 21Serial Line View 66, 72Server 18, 63, 67, 68, 72

Activate 63Configuration 58DCN management 20

Service PacksWindows OS 31

SNMP 22Software architecture 17Start application 57, 63Status bar 66, 68Stop application 64, 65Structure

Network 14Subnetwork

DCN management 21Supplementary documentation 25

Delivery notes 25Field test protocols 26Planning documents 26

System information 67System Message Log 24, 65

Settings 66

TTelegram protocol 22Third-party software

Installation 32OSI stack 33

TNMS CTInstallation 37

Toolbar 66DCN Management View 73Main window 67

Topology discovery 22

UUnderlined letters 62Uninterruptible power supply 28Upgrade 70Upgrade package 25User

Accounts 58, 67Administration 23Class 23

User Manual 67

VView 65, 71

WWindow 67Window style 66Windows OS 28, 31

Hardware configuration 31Service Packs 31

WINS 31Write access 24, 63, 70

user manual tnmsct v3.0

Documents

user management

network management

user manual umna42022l5959

installation software283

installation sequence

log management

fault management

dcn management