User Manual
-
Upload
emmanuel-n-onuzurike -
Category
Documents
-
view
160 -
download
7
description
Transcript of User Manual
TNMS CT 3.2
User Manual (UMN)Issue 01
January 2012
A50023-K4003-X20-1-7619
2 A50023-K4003-X20-1-7619
User Manual (UMN)
The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.
The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.
This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.
Copyright © Nokia Siemens Networks 2012. All rights reserved
f Important Notice on Product Safety Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the parts may also have elevated operating temperatures.
Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.
Therefore, only trained and qualified personnel may install and maintain the system.
The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply with the applicable safety standards.
The same text in German:
Wichtiger Hinweis zur Produktsicherheit
In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.
Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-zungen und Sachschäden führen.
Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und wartet.
Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.
A50023-K4003-X20-1-7619
3
User Manual (UMN)
Table of ContentsThis document has 75 pages.
1 Introductory Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2 Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.3 Symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.4 Further documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2 Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.1 Network Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.1.1 Supported NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.2 System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.2.1 Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.2.2 Software Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.2.2.1 TNMS CT Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.2.2.2 TNMS CT Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.3 Functional Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.3.1 LCT and NCT Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.3.2 Network Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.3.3 DCN Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.3.4 Communication Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.3.5 Telegram Protocols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.3.6 Scaled Start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.3.7 Automatic Topology Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.3.8 Automatic Recognition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.3.9 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.3.10 User Management and Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.3.11 Remote Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.3.12 Log Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.3.13 Screen Level Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.3.14 Priority/Mutable Exclusion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.1 Protective Measures and Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.1.1 Safety Precautions When the Unit is Open. . . . . . . . . . . . . . . . . . . . . . . . . 213.1.2 Protection against Excessive Contact Voltages . . . . . . . . . . . . . . . . . . . . . 213.1.3 Handling Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.2 Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.2.1 Component Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.2.2 Hardware and Software Recommendations . . . . . . . . . . . . . . . . . . . . . . . . 233.2.3 Installation Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.2.4 Installation and Cabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.2.5 Installation Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.3 Installing the Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.3.1 Before you Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.3.2 Installing Windows OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.3.3 Hardware Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4 A50023-K4003-X20-1-7619
User Manual (UMN)
3.3.4 Windows Services Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.4 Installing 3rd-Party Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.4.1 Installing an OSI Stack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.4.2 Installing Adobe Acrobat Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.5 Installing the TNMS CT Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.5.1 Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.5.2 Installing TNMS CT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.5.3 Uninstalling TNMS CT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403.5.4 Adding and Removing Individual TNMS CT Components . . . . . . . . . . . . . . 413.5.5 Changing modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423.6 Measures after Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423.6.1 Configuring Windows firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433.6.2 PPP Dial-up Setup for Q3 or QSTv2 Network Elements . . . . . . . . . . . . . . . 443.6.2.1 Setting a new connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443.6.3 Java Runtime Environment parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . 523.6.4 Initial Configuration of TNMS CT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523.6.5 Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553.6.6 Routing Settings for PCs with Multiple Network Adapters . . . . . . . . . . . . . . 553.7 Upgrading to a new release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
4 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574.1 Working With the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574.1.1 TNMS CT Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574.1.2 Working With the Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574.1.3 Working With the Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.1.4 Working With the Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.2 Basic Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.2.1 Starting a TNMS CT Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594.2.2 Starting and Stopping TNMS CT Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 594.2.3 Activating and deactivating TNMS CT Server . . . . . . . . . . . . . . . . . . . . . . . 594.2.4 Setting Date and Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594.2.5 Starting Element Manager Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . 594.2.6 Administrating NE Write Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594.2.7 Terminating a TNMS CT Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604.3 Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604.3.1 Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614.3.2 Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634.3.3 Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644.3.4 Network View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644.3.5 Serial Line View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674.3.6 DCN Management View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674.3.6.1 DCN Management Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684.3.6.2 DCN Management Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
5 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
A50023-K4003-X20-1-7619
5
User Manual (UMN)
List of FiguresFigure 1 General Structure of a TNMS CT Network . . . . . . . . . . . . . . . . . . . . . . 10Figure 2 System Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Figure 3 Overview of Software Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Figure 4 A GNE detecting its managed NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Figure 5 Labelling of electrostatic-sensitive devices (ESD symbol). . . . . . . . . . . 22Figure 6 Add or Remove Programs window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Figure 7 Windows Components Wizard and IIS dialogs . . . . . . . . . . . . . . . . . . . 29Figure 8 Programs and Features window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Figure 9 Windows Features dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Figure 10 User Accounts for Windows vista . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Figure 11 User Account Control dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Figure 12 Setup OSI Stack: Choose Destination Location . . . . . . . . . . . . . . . . . . 32Figure 13 Setup OSI Stack: How to set NSAP address. . . . . . . . . . . . . . . . . . . . . 32Figure 14 Setup OSI Stack: Company with own NSAP management . . . . . . . . . . 33Figure 15 Setup OSI Stack: NSAP derived from MAC address. . . . . . . . . . . . . . . 34Figure 16 Setup OSI Stack: Use a serial Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Figure 17 OSI Stack installation: Start Copying Files window . . . . . . . . . . . . . . . . 35Figure 18 TNMS CT installation: welcome screen . . . . . . . . . . . . . . . . . . . . . . . . . 37Figure 19 TNMS CT installation: choose LCT or NCT mode . . . . . . . . . . . . . . . . . 37Figure 20 TNMS CT installation: choose client and/or server installation . . . . . . . 38Figure 21 TNMS CT installation: license agreement . . . . . . . . . . . . . . . . . . . . . . . 38Figure 22 TNMS CT installation: choose installation folder . . . . . . . . . . . . . . . . . . 39Figure 23 TNMS CT installation: NE selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Figure 24 TNMS CT installation: installation complete . . . . . . . . . . . . . . . . . . . . . 40Figure 25 New connection wizard: welcome screen . . . . . . . . . . . . . . . . . . . . . . . 44Figure 26 New connection wizard: network connection type . . . . . . . . . . . . . . . . . 45Figure 27 New connection wizard: advanced connection options . . . . . . . . . . . . . 45Figure 28 New connection wizard: host or guest role . . . . . . . . . . . . . . . . . . . . . . 46Figure 29 New connection wizard: connection name. . . . . . . . . . . . . . . . . . . . . . . 46Figure 30 New connection wizard: select a device . . . . . . . . . . . . . . . . . . . . . . . . 47Figure 31 New connection wizard complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Figure 32 General connection properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Figure 33 Modem configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Figure 34 Connection properties: networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Figure 35 Internet protocol (TCP/IP) properties . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Figure 36 Advanced Internet protocol (TCP/IP) settings . . . . . . . . . . . . . . . . . . . . 51Figure 37 QB3 channel properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Figure 38 TNMS CT login window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Figure 39 TNMS CT graphical user interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Figure 40 Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Figure 41 Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Figure 42 Network View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Figure 43 Serial Line View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Figure 44 DCN Management View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Figure 45 DCN Management Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
6 A50023-K4003-X20-1-7619
User Manual (UMN)
List of TablesTable 1 Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Table 2 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Table 3 Supported NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Table 4 Hardware recommendations for TNMS CT . . . . . . . . . . . . . . . . . . . . . . 23Table 5 Software recommendations for TNMS CT . . . . . . . . . . . . . . . . . . . . . . . 23Table 6 Affected Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Table 7 Blue Framing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Table 8 Menu Bar Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Table 9 Main Toolbar Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Table 10 Status Bar Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Table 11 Network View Context Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Table 12 Serial Line View Context Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Table 13 DCN Management Toolbar Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Table 14 DCN Management Tree Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
A50023-K4003-X20-1-7619
7
User Manual (UMN) Introductory Notes
1 Introductory NotesThis User Manual gives a complete overview of the functions, applications, architecture and installation of TNMS CT.
1.1 Intended audienceThis document is intended for all TNMS CT users.
1.2 Structure of this documentThe User Manual (UMN) consists of the following main chapters
• InformationThis chapter provides an overview of the applications, system architecture, features and 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 well as the necessary background information (see Chp. 4).
g Some features described in this documentation may not be available. In order to identify the features released for the product, please refer to the Release Notes delivered together with the product.
The User Manual is also provided as file under the Help menu. This file can be viewed and printed using Adobe Acrobat Reader.
8 A50023-K4003-X20-1-7619
User Manual (UMN)Introductory Notes
1.3 Symbols and conventionsThe following symbols are used in this document:
The following conventions are used in this document:
1.4 Further documentationAn online help system is provided with the TNMS CT software. It includes comprehen-sive instructions on the functions offered by the user interface. The help system contains information on window contents, menus and meaning of used icons. Via the help table of contents, the user can find the tasks and procedures necessary to operate and admin-istrate TNMS CT.
Help can be invoked in any of the following ways:
– After invoking help from the menu bar, the user can search for topics via the table of contents, the index or a word search.
– Clicking the Help button in the current window, which displays information about the window contents.
– Pressing <F1>, which displays information about the contents of the active window.
Symbol Explanation
Notes provide additional useful information.
Warnings provide information on critical issues that could result in equipment damage or data loss if ignored.
Table 1 Symbols
Convention Explanation
bold Graphical user interface text, e. g., field names and button descriptions, are written in bold.
Example: Click the View menu, and then click New View.
monospace Commands, screen output, file names and paths are written in a special font.
Example: $ sqlplus /nolog< ... > Keys are represented in square brackets and bold.
Example: Press <F1>, for help on the current window.
Table 2 Conventions
A50023-K4003-X20-1-7619
9
User Manual (UMN) Information
2 InformationTNMS CT is a transparent software platform for SDH and WDM network elements that uses QB3M (QD2, QST, QSTV2, Q3) or SNMP telegram protocols. TNMS CT provides access to network elements via a network interface (ethernet) or via a serial line inter-face (RS232).
There are two operation modes for TNMS CT: the Local Craft Terminal (LCT) mode and the Network Craft Terminal (NCT) mode.
The TNMS CT menu items and dialogues allow the supported communication channels to 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 program icons for these applications are used to present the assigned network elements in the network view for the communication channel. A double-click on such an icon starts the assigned device application, i.e. an element manager, and thus permits the network element to be operated.
This chapter consists of a technical description of TNMS CT covering the following areas:
– Network Architecture (see Chp. 2.1)– System Architecture (see Chp. 2.2)– Functional Overview (see Chp. 2.3)
2.1 Network ArchitectureFigure 1shows the general structure of a transmission network managed by TNMS CT. The network elements (NEs) connect to the DCN through QB3M or SNMP channels, depending on the telegram protocol supported by the NE.
10 A50023-K4003-X20-1-7619
User Manual (UMN)Information
Figure 1 General Structure of a TNMS CT Network
Element management functions are executed via the element managers (LCTs) provided by the TNMS CT system.
TNMS CT supports line, star, ring and mesh networks comprising of WDM and SDH network elements.
2.1.1 Supported NEsTNMS CT supports the following NEs:
Management interface Supported NEs
QB3M hiT 7050, hiT 7070, hiT 7500, hiT 7540, hiT 7550, SMA1/4, SMA 4/1, SMA1K, SMA1K-CP, SMA16, SMA16/4, SL16, SLR16, SL64, WL, WLS, WTTR
SNMP FSP, hiT 7020, hiT 7025, hiT 7030, hiT 7035, hiT , hiT 7060 HC, hiT 7065, hiT 7080, hiT 7300
Table 3 Supported NEs
A50023-K4003-X20-1-7619
11
User Manual (UMN) Information
2.2 System ArchitectureTNMS CT is a scalable single-user system with a client/server architecture comprising several industry standard PCs with the Windows operating system and various software applications. External devices such as printers, tape units and remote clients are not dealt with here.
g Some NEs, such as QST and QD2 NEs, allow the connection to several manage-ment system levels. If a management system like TNMS Core enforces write access on a network element, it will override the TNMS CT write access.
Figure 2 shows an overview of the TNMS CT client/server architecture with client and server installed on different computers. A configuration with client and server installed on the same PC is also possible.
Figure 2 System Architecture
12 A50023-K4003-X20-1-7619
User Manual (UMN)Information
2.2.1 Hardware ComponentsThe TNMS CT hardware components depend directly of the network size. For more information about the minimum recommended hardware see chapter 3.2.2 Hardware and Software Recommendations.
Planning for hardware, software and licences should be undertaken on a project-specific basis.
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 all TNMS CT management functions, e.g. invoking of element managers, are available.
The Server component holds the EML packages and the NetServer frame, which provides the environment for running EML servers, DCN connectors and NE controllers.
All software components can be installed on one PC.
Figure 3 shows the TNMS CT software architecture.
Figure 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.
A50023-K4003-X20-1-7619
13
User Manual (UMN) Information
Network Management Graphical User InterfaceThe TNMS CT graphical user interface (GUI) provides the operator with several network views which contain graphical and text information about current alarms, states and resources. The main GUI contains the network map, several list and log windows, as well as specific dialog windows. Depending on the assigned user class, the operator’s access can be restricted to certain functions.
More information on operating via the GUI is given in Chp. 4.1.
Element ManagerIn order to obtain detailed information about an NE, the operator can open the element manager application associated with the corresponding network element. TNMS CT starts the corresponding process and provides the interface of the associated NE con-troller to the element manager. Element manager applications provide full access to all NE data and also enable the configuration and control of NE behavior. This way, depending on the actual NE type, performance values and alarms can be requested, and the backup and restore of configuration and other data initiated.
Network Management Data ExportData export is provided in the TNMS CT to export data for external evaluation. This enables the operator to export the content of each list and log to a file. This information is written to system data format (SDF) files. Several tools and standard applications (e.g. MS Access or MS Excel) can read these files.
Import / Export InterfaceTo import/export TNMS CT configuration data, the extended markup language (XML) format is used. These files can be used for migration purposes.
g Detailed operating information on operating TNMS CT is provided in Chapter 4 and in the Online Help.
2.2.2.2 TNMS CT ServerThe main parts of the TNMS CT Server component are the NetServer frame and the EML packages including NE controllers.
NetServer FrameThe NetServer frame is essentially a proxy for the TNMS CT Server. It facilitates the management of EML packages.
EML PackagesA 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 of EML packages required for a given TNMS CT system depends on the NE types that TNMS system configuration is required to support.
NE ControllersThe main task of an NE controller is to convert NE-specific management interfaces to a simple internal TNMS CT element management interface. In this way, network layer management in the TNMS CT Server only receives the necessary information from the element management layer.
14 A50023-K4003-X20-1-7619
User Manual (UMN)Information
A corresponding NE controller must be registered in the system for every NE type to be managed by TNMS CT. Each NE controller class can support different NE types, but each NE can only be controlled by one type of NE controller.
2.3 Functional OverviewTNMS CT provides network management functions defined in the ITU-T standard M.3010 “Principles for a Telecommunications Management Network”.
Fault and configuration management are supported on the element management and on the network management layer. Various security management features are also implemented.
2.3.1 LCT and NCT ModesDepending on the needs, two different modes are available for TNMS CT.
g Each mode requires its own license key. Furthermore, the installation routines are slightly different from each other.
LCT Mode The Local Craft Terminal (LCT) is used for local management and commissioning of network elements. The LCT can communicate with a maximum of 50 network elements. Up to three element managers may be open at the same time only.
NCT ModeThe Network Craft Terminal (NCT) is used for local or remote management of network elements. In addition to the LCT functions, the monitoring of all the alarms reported from each accessible network element is allowed. The NCT can communicate with a maximum of 150 network elements (including alarm monitoring). Up to 50 element 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 map by various graphical symbols such as icons or lines.
Network Element (NE)This object represents a physical network element. Network elements are the basis of the network topology. Each individual NE is clearly identifiable and can also be combined with other NEs by drawing lines between them representing physical connec-tions.
LinkThis object are lines drawn on the network map. These lines are drawn arbitrarily by the operator to structure the NEs according to the existing network topology. Genuine port connections, however, are not established this way. The link information is stored on the Client PC.
A50023-K4003-X20-1-7619
15
User Manual (UMN) Information
Port ConnectionThis objects represents port connections that have been established between NEs. The port connection information is stored inside the NE itself.
2.3.3 DCN ManagementThe following objects are managed by TNMS CT and handled via the graphical tree view in the DCN Management View.
ServerThe 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 NEs for network access. The Serial Line Server contains preconfigured DCN channels and NEs for RS232 access and consequently allows the Serial Line View to perform an automatic connect.
DCN ChannelsThe 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.
SubnetworksThe DCN channel nodes allow the operator to categorize network elements into subnet-works. This information is also displayed on the network map.
Network ElementsThe 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 the network map.
Gateway Network ElementsThe 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 added automatically. The ID name of the DCN channel will be set as subnetwork name for these NEs. Figure 4 shows an example of an activated GNE with its NEs starting up.
16 A50023-K4003-X20-1-7619
User Manual (UMN)Information
Figure 4 A GNE detecting its managed NEs
2.3.4 Communication InterfacesTNMS CT supports two different communication interfaces, a serial line interface and a network interface.
Serial Line (Q-F)TNMS CT provides a serial line interface via the RS232 port of the operator’s PC. The COM port can be selected via a property page in the DCN Management View. A local serial line connection can be established in both LCT and NCT mode.
Network (Q-B3)TNMS CT can establish a connection to one or more NEs via an ethernet card in the operator’s PC.
2.3.5 Telegram ProtocolsTNMS CT supports the following telegram protocols to communicate with NEs:
– QD2– QST– QSTV2– Q3– SNMPTNMS 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 supported. Accordingly, the connection to the NEs managed by a server are not established simul-taneously, but one after another. A parameter set up via theDCN Management View allows a simultaneous start-up.
2.3.7 Automatic Topology DiscoverySeveral NEs supported by TNMS CT are capable of storing topology information, such as neighboring NEs and port connections. As soon as one of these NEs is activated via
A50023-K4003-X20-1-7619
17
User Manual (UMN) Information
theDCN Management View, the topology information is available in TNMS CT. Accord-ingly, integration of network information is simplified.
g This 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 acti-vation of the NE in TNMS CT.
2.3.8 Automatic RecognitionIn case of a communication loss, an automatic reconnection to the network elements is supported. 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 and an alarm log. The alarm list is accessed via the TNMS CT Client. A global alarm list contains all alarms currently raised for all NEs in the network as well as performance management related Threshold Crossing Notification (TCN) entries. An individual list of current alarms can also be generated for each NE. As soon as an alarm is cleared, it is deleted from the alarm list.
The alarm log, by contrast, is a permanent record containing all network element layer alarms, both raised and cleared. It provides a complete alarm history for the supervised network. The size of this log can be configured as required for up to 99.999 entries. The alarm 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 referring to the alarm list. Specific symbols are used to illustrate the current access state and the highest alarm severity. These can be displayed for both the network as a whole as well
18 A50023-K4003-X20-1-7619
User Manual (UMN)Information
as for individual network elements. This allows the user to quickly assess the importance of the alarm concerned.
For further fault localization, the user can also call up the appropriate element manager.
TheAlarm Statistic window enables the operator to handle alarms conveniently. The Alarm 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 the TNMS Core/CDM user classes. Via the User Administration window users can be assigned to the user class. The set of functionality available to a given user class is fixed and cannot be changed. Only an Administrator has access to the user administration and other security functions. Additionally, the following user management features are provided:
– 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 aSecurityLog which stores the logged-on users and their actions, e.g. usage of Element Managers. Access to this from outside TNMS 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 arrangement and toggling of formerly used passwords.
– 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 the client/server architecture (see Figure 3). The TNMS CT Client may run on a different computer and access the CT Server computer via a TCP/IP connection.
g Remote login is supported in NCT mode only! Information on NCT mode is given in Chp. 2.3.1.
2.3.12 Log ManagementIn TNMS CT, specific operator activities as well as all actions and unsolicited events are stored 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 administered by the TNMS CT system. The operator can, however, specify certain attri-butes such as the maximum log size.
TNMS CT provides the following permanent logs:
A50023-K4003-X20-1-7619
19
User Manual (UMN) Information
– Alarm logThe alarm log contains a chronological list of alarms which have occurred. Toggle alarms, i.e. identical alarms which are triggered repeatedly, are entered once only if the toggle filter with a proper time setting is switched on.
– System message logThe system message log contains a chronological list of relevant administrative events. Critical events are displayed in the user interface.
– Server log and Client logThe Server log and the Client log contain a chronological list of events occurring in TNMS CT server and TNMS CT client applications, respectively. These logs will be used to determine the causes of possible TNMS CT server or client unexpected behavior.
2.3.13 Screen Level IntegrationTNMS CT supports screen level integration of UniGATE functions not covered by TNMS CT. 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 ExclusionNetwork elements from Nokia Siemens Networks, support the functionality to connect to more than one management system. Some NEs, e.g. QST and QD2 NEs, also support different management system levels, such as TNMS Core/CDM, which com-prises a network layer. Consequently, such a TMS can enforce the write access on these NEs and override the write access of TNMS CT. TNMS CT, however, is not able to enforce the write access on an NE.
20 A50023-K4003-X20-1-7619
User Manual (UMN)Installation
3 InstallationThis chapter provides a guideline of the procedures required to install TNMS CT:
– Protective Measures and Handling (see Chp. 3.1)– Preparing 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. It is supplied on DVD-ROM which includes a 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 SoftwareIn order to use the TNMS CT software, the import of corresponding license keys is required.
g Various software products referred to in this manual have been licensed by Nokia Siemens Networks and are provided together with the TNMS CT software. Any questions concerning these products should therefore be directed to Nokia Siemens Networks rather than to the original manufacturer. Questions regarding software products such as virus scanners, which may run with TNMS CT software, but which are not provided, sold or purchased by Nokia Siemens Networks, should be addressed directly to the manufacturer in question.
More information on licenses is provided under Import licenses.
g When using a virus scanner it is recommended to exclude the TNMS/LCT installa-tion folders and Java installation folders (e.g., rt.jar) from the scanning.
Additional DocumentationIn addition to the customer documentation the following information is also available upon demand:
– Delivery notes:These provide an overview of the hardware, software and documentation delivered.
– Documentation from the O&M Centre:On request, Nokia Siemens Networks Technical Sales can supply project documen-tation which provides specific information about the installation. These planning doc-uments are available 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 Nokia Siemens Networks service personnel and the customer to prove correct commissioning of the system and to provide a 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 test
A50023-K4003-X20-1-7619
21
User Manual (UMN) Installation
protocol. These provide information on the values used in system testing, and can be obtained from Nokia Siemens Networks Technical Sales.
CE Conformity DeclarationThe CE conformity declaration for the product is fulfilled if installation and cabling are carried 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 use of 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 CommissioningThe following personnel requirements must be fulfilled for commissioning:
– Training to service technician level or communications engineering equivalent.– 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 XP/Vista/Windows
7.– 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 TNMS CT installation is provided here.
g As a general rule, you should always note the manufacturer’s instructions when handling devices such as PCs, monitors, printers and tape drives, or when installing modules such as network cards.
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 electric shocks, make sure that these pins do not come into contact with foreign potential (e.g. ground).
3.1.2 Protection against Excessive Contact VoltagesWhen dealing with the power supply, observe the safety precautions as specified by the German DIN standard VDE 0105 (operation of high-voltage systems). This standard defines in detail the steps to be taken by the operators of electrical installations and the users of electrical equipment to ensure the safe maintenance of electrical installations and equipment.
22 A50023-K4003-X20-1-7619
User Manual (UMN)Installation
3.1.3 Handling ModulesModules labelled as shown in Figure 5 below are equipped with electrostatic-sensitive components.
Figure 5 Labelling of electrostatic-sensitive devices (ESD symbol)
All modules with ESD components have an outer grounding edge which is connected to the 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 when handling 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 and modules.
– Ensure that the modules are installed in the correct slots.
g European standard EN50082-1 contains detailed information on the correct handling of electrostatic-sensitive devices.
3.2 Preparing for InstallationPrior to installing TNMS CT check the following chapters to ensure that all requirements are met. Information is provided on:
– Component Delivery (see Chp. 3.2.1)– Hardware and Software Recommendations (see Chp. 3.2.2)– Installation and Cabling (see Chp. 3.2.4)– Installation Software (see Chp. 3.2.3)– Installation Sequence (see Chp. 3.2.5)
3.2.1 Component DeliveryBefore installation, ensure that:– The delivery is complete in accordance with the delivery units specified in the
delivery note (hardware, software and documentation).
A50023-K4003-X20-1-7619
23
User Manual (UMN) Installation
– The components are not damaged in any way.
3.2.2 Hardware and Software RecommendationsThe following tables provide an overview of the hardware and software recommenda-tions for running TNMS CT.
g When using machines with less memory space than the recommended, for example machines with 256MB and 512MB of memory, the ability to open several LCTs at the same time can be affected.
When running TNMS CT in Windows 7, the generic RS232 to USB adapter is only supported over XP mode.
Recommended software for running TNMS CT.
Hardware Recommendations
CPU Pentium IV 2,6 GHz/512 kB
1 GHz or faster 32-bits (x86) in case of Windows 7
Memory 1 GB
Hard Disk 40 GB
Optical Disc Drive DVD-ROM drive
LAN Ethernet card, 2x 3COM (3C982-TXM)
Graphics Card 32 MB (with DirectX 9 graphics device with WDDM 1.0 or higher driver for Windows 7)
Interface ports Ethernet port
RS232 serial port or generic RS232 to USB adapter
Monitor Color monitor 19”
Table 4 Hardware recommendations for TNMS CT
Software Recommendations
Operating system Windows XP including the latest Service Pack 3 (for TNMS CT Server the Professional edition is recommended)
or
Windows Vista including the latest Service Pack 1 (for TNMS CT Server the Business/Ultimate edition is recommended)
Windows 7 Professional 32 bits or 64 bits, including the latest Service Pack
NSAP configure OSI Stack (for TNMS CT Server OSI Stack is recommended)
Table 5 Software recommendations for TNMS CT
24 A50023-K4003-X20-1-7619
User Manual (UMN)Installation
3.2.3 Installation SoftwareAll recommended software parts must be released for the appropriate TNMS CT software version. This holds for the initial installation and for service or upgrade package installations as well.
g If additional software (not required by TNMS CT) is installed, the correct functionality cannot be guaranteed.
The following software is generally required for the installation. The corresponding order numbers are provided in the TNMS CT release documentation.
More information on the installation sequence is provided in Chp. 3.2.5.
1. Installation instructions for the operating system are provided in Chp. 3.3, however, pre-installed machines can also be used.
2. FTP Service component (required by TNMS CT Server):The File Transfer Protocol (FTP) service allows clients to connect to the TNMS CT Server machine and retrieve or store files for APS downloads and MIR uploads.This service is a component of the Internet Information Services (IIS) included with Windows XP Professional, Windows Vista Business/Ultimate or Windows 7 Profes-sional, however, it is not enabled by default and therefore must be configured man-ually. More information on how to enable this service is available in Chp.3.3.4.
3. TNMS CT:This installation contains the following software components for installation:– Integrated TNMS CT software installation package:
This installation program includes the Server and Client components. These can be installed either individually or together as required. The EML packages for QB3M and FSP are also available for selection during the TNMS CT installation. The EML packages are installed on the Server PC. More information on installing TNMS CT is provided in Chp. 3.5.2.
Additionally to the TNMS CT installation, the following 3rd-party software compo-nents are also included on this DVD:– TrapHandler:
The TrapHandler is automatically installed with the application as a service.– JavaSoft JAVA Runtime Environment:
The JRE is automatically installed on the client machine to provide an environ-ment for the Java based applications.
– OSI stack:The OSI stack software must be installed on Server PC before the Server software itself. More information on installing the OSI stack is provided in Chp. 3.4.1.
Web Browser The Online Help requires the Internet Explorer Web Browser.It is recommended using the Internet Explorer included with the Service Pack updates: IE6 for XP SP3, IE7 for Vista SP1 or IE8 for Windows 7 Professional.
PDF Reader Acrobat Reader 6 or later.(a PDF reader is required to access the TNMS CT User Manual)
Software Recommendations
Table 5 Software recommendations for TNMS CT (Cont.)
A50023-K4003-X20-1-7619
25
User Manual (UMN) Installation
– Acrobat Reader:Acrobat Reader is required for using the User Manual which is delivered as PDF file. More information on installing the Acrobat Reader is provided in Chp. 3.4.2.
Software DVD OverviewThe software is delivered on a DVD-ROM. The operating system will be delivered as part of the hardware, it is not included within the following table.
Overview of the deliverable DVD-ROM:
– TNMS CTCT application SW, element manager applications, NECs, OSI stack, JRE, Acrobat Reader
– OEMSW for FSP equipment
– Customer DocumentationUser Manual
3.2.4 Installation and CablingBefore installing the operating system, the following steps should be completed:
– The Client and Server machines should be set up and cabled in accordance with the project-specific installation documents supplied.
– The applicable recommendations for screen-based workstations should be observed.
– To guarantee 24-hour operation, an uninterrupted power supply must be available.
3.2.5 Installation Sequenceg Before installing any software component, refer to the associated readme file, where
you can find the latest informations concerning installation.
The system should be commissioned as follows:1. Set up and cable, as described in Chp. 3.2.4.2. Install the operating system and additional hardware components, and configure the
system under Windows OS as described in Chp. 3.3.3. Install FTP service on the Server machine as described in Chp.3.3.4.4. Install the OSI stack on the Server machine as described in Chp. 3.4.1.5. Install Acrobat Reader as described in Chp. 3.4.2.6. Install the TNMS CT software components on the corresponding machines as
described in Chp. 3.5.2:– TNMS CT Client– TNMS CT Server– TNMS CT EML Packages– Additional TNMS software, such as optional EML packages.
7. Configure the TNMS CT components and connect network elements as described in Chp. 3.6.4.
8. Perform system testing in accordance with the test cases described in the accep-tance test protocol. For more information, contact Nokia Siemens Networks Techni-cal Sales.
26 A50023-K4003-X20-1-7619
User Manual (UMN)Installation
3.3 Installing the Operating SystemThis Chapter describes the recommend procedures to prepare the Windows OS for running TNMS CT software platform.
g Follow the mandatory installation sequence for all software parts as described in Chp. 3.2.5.
3.3.1 Before you BeginBefore you install Windows operating system, complete the following steps:
– Determine the components to be installed.– Determine the licensing mode to be used.– Check if the system recommendations are met, as described in Chap. 3.2.2.– 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.– If you wish to pre-install a SCSI RAID system, make sure the TNMS CT hard disks
are formatted using the NTFS file system.– Determine the partition to be used for the installation, or if a new partition is required.– Backup all data and files prior to an initial installation of the OS. This does not apply
if there are no files on the computer or the existing files are damaged. You can save the files on disk, on tape or on another computer in your network.
– Decompress all DriveSpace and DoubleSpace data carriers.– Installation may only be carried out on a compressed drive if this drive was com-
pressed with the compression program of the NTFS file system.– Determine how the network IP addresses, TCP/IP configurations are to be handled.– Determine the domains names and workgroups for the servers, if required.– Disable all UPS devices, if the target computer is plugged into a UPS, remove the
serial cable before performing the setup. Windows XP/Vista/Windows 7 Setup tries to identify the devices at the serial interfaces automatically and therefore a connec-tion to an UPS is not advisable.
Licensing InformationDuring installation, the system license number is requested. This is provided on the back cover of the Windows CD.
Protocol InformationTCP/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 each server and client.
IP address assignment methods:– Static Address, where the IP number is fixed and each network device has to be
configured manually using a different IP address.– Dynamic Address (using DHCP), this method allows dynamic assignment of IP
addresses to network devices. To enable this service, a DHCP server is required.
IP addresses are provided in the form of numbers but you can also assign a name to a server IP address using what is known as name resolution. This enables user access
A50023-K4003-X20-1-7619
27
User Manual (UMN) Installation
using server names instead of IP addresses which can be difficult to remember. The main name resolution methods are:
Domain name assignment methods:– DNS (Domain Naming Service):
DNS is a distributed Internet directory service that is used mostly to translate between domain names (server hosts) and IP addresses. It facilitates name resolu-tion for clients under Windows OS.
– WINS (Windows Internet Naming Service):WINS facilitates name resolution for clients running Windows NT and older Microsoft operating systems.
3.3.2 Installing Windows OSPrior to installing Windows OS, read the information given in Chp. 3.3.1 carefully.
The Windows OS installations are supported by an installation wizard which will guide you through the installation process. Detailed information on how to install the OS is provided in the Microsoft Windows documentation delivered with the Windows OS installation CD-ROM.
After the operating system is installed, the latest Service Pack must also be installed:
– Service Pack 3 (SP3) when using Windows XP– Service Pack 1 (SP1) when using Windows Vista– Latest Service Pack when using Windows 7
It is highly recommended that available security patches for Windows are also installed.
g Before installing Windows 7, please note that the Aero user interface mode is not supported.
3.3.3 Hardware ConfigurationOnce the Windows OS has been installed, all additional hardware and software drivers must be installed and configured under 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 CardThe PCI I/O card is installed on the TNMS CT Client PC and enables external signalling.
g Before opening the antistatic envelope, make sure you are familiar with the regula-tions for electrostatic-sensitive devices (ESD) provided in Chp. 3.1.
– Switch off your computer and disconnect it from the power supply.– Open the computer.– Insert the PCI I/O card into a free slot.– Close the computer and connect it to the power supply.– Switch on the computer.
28 A50023-K4003-X20-1-7619
User Manual (UMN)Installation
– 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.3.4 Windows Services ConfigurationThis section describes how to enable or disable the required services for each the sup-ported OS and TNMS versions.
For running TNMS CT Server under Windows XP Professional:– Enable FTP Service (Windows XP Professional).
For running TNMS CT Client under Windows XP Home/Professional:– It is not necessary to enable/disable any service.
For running TNMS CT Server under Windows Vista Business/Ultimate or Windows 7 Professional:– Enable FTP Service (Windows Vista or Windows 7).– Disable User Account Control (Windows Vista or Windows 7).
For running TNMS CT Client under Windows Vista Home/Business/Ultimate or Windows 7 Professional:– Disable User Account Control (Windows Vista or Windows 7).
Enable FTP Service (Windows XP Professional)Complete the following steps to enable the FTP service required by TNMS CT Server:1. Locate the Add or Remove Programs in Control Panel.
Figure 6 Add or Remove Programs window2. Select the Add/Remove Windows Components.3. Select Internet Information Services (IIS), then click the Details button.
A50023-K4003-X20-1-7619
29
User Manual (UMN) Installation
Figure 7 Windows Components Wizard and IIS dialogs
4. Select the FTP Service check-box and click OK.5. Click OK to close all dialog boxes.
Enable FTP Service (Windows Vista or Windows 7)Complete the following steps to enable the FTP service required by TNMS CT Server:1. Locate the Programs and Features in Control Panel, or Programs -> Programs
and Features in Windows 7.
Figure 8 Programs and Features window2. Select the Turn Windows feature on or off.3. Expand the Internet Information Services and the FTP Publishing Service tree node.
30 A50023-K4003-X20-1-7619
User Manual (UMN)Installation
Figure 9 Windows Features dialog4. Select the FTP Server check-box and click OK.5. Wait a couple of minutes while the feature is configured.
Disable User Account Control (Windows Vista or Windows 7)Complete the following steps to disable the User Account Control:
1. In Windows Vista, proceed as the following, 1.1 Locate the User Accounts in Control Panel -> User Accounts and Family
Safety.1.2 Select the Turn User Account Control on or off.
Figure 10 User Accounts for Windows vista
1.3 Uncheck the Use User Account Control (UAC) to help protect your computer check box and click OK.
A50023-K4003-X20-1-7619
31
User Manual (UMN) Installation
Figure 11 User Account Control dialog2. In Windows 7, proceed as the following:
2.1 Locate the Action Center in Control Panel -> System and Security.2.2 Select the Change User Account Control settings.2.3 In Choose when to be notified about changes to your computer, move the
slider all way down to Never Notify and click OK.3. For the changes to take effect you will need to reboot.
3.4 Installing 3rd-Party SoftwareThis chapter provides an overview of the additional software installations needed to run TNMS CT correctly. The described installations include:
– JavaSoft JAVA Runtime Environment (this software is installed automatically with the TNMS CT package)
– OSI Stack (see Chp. 3.4.1)– Adobe Acrobat Reader (see Chp. 3.4.2)
g Follow the mandatory installation sequence for all software parts as described in Chp. 3.2.5.
3.4.1 Installing an OSI StackAn OSI stack must be properly installed on the Server computer and binded to a correct card before the Server software. The OSI stack is not required on the Client PC.
g During the installation process you will be asked for an NSAP address. Ask your system administrator how the NSAP addresses are handled in your company’s network and have it determined.
See Step 5. for the possibilities to set up the NSAP address.
To install an OSI stack, proceed as follows:
1. To install an OSI stack, double-click the setup.exe file in the OsiStack directory on the TNMS CT software DVD.
2. A welcome window is displayed. Press Next to continue.3. In the Choose Destination Location window, a default installation directory is
offered for the OSI stack. Press Next to continue.
32 A50023-K4003-X20-1-7619
User Manual (UMN)Installation
Figure 12 Setup OSI Stack: Choose Destination Location4. The How to set NSAP address dialog is displayed (Figure 13), please select the
appropriate option according to your company’s network management. More infor-mation about each option available in step 5.
Figure 13 Setup OSI Stack: How to set NSAP address5. Depending on the previous selection, execute one of the following options:
– When selecting “My company has own NSAP management”, then your system administrator provides you with an NSAP address.
A50023-K4003-X20-1-7619
33
User Manual (UMN) Installation
After pressing Next, the Getting NSAP window is shown. See Figure 14.Enter the provided NSAP address and press Next.
Figure 14 Setup OSI Stack: Company with own NSAP management– Select “(no NSAP management) NSAP address should be derived from
MAC address of ethernet card”, when the system has an ethernet card and your system administrator didn’t provide you with an NSAP address.After pressing Next, the Getting NSAP window is opened. See Figure 15.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.
34 A50023-K4003-X20-1-7619
User Manual (UMN)Installation
Figure 15 Setup OSI Stack: NSAP derived from MAC address– Select “I do not have an ethernet card, I can only use a serial line.”, to have
TNMS CT assign an NSAP address.After pressing Next, a Question window is opened including an NSAP address. Click Yes.
Figure 16 Setup OSI Stack: Use a serial Line6. In the Start Copying Files window ensure that the settings displayed are correct,
and if so, press Next to continue.
A50023-K4003-X20-1-7619
35
User Manual (UMN) Installation
Figure 17 OSI Stack installation: Start Copying Files window7. A setup status window is now displayed, showing the progress of the OSI stack
installation.8. The window InstallShield Wizard Complete is now displayed. Select the option for
restarting the computer, and press Finish to complete the OSI stack installation.
Once the computer has rebooted, open the OSI stack using Start -> Settings -> Control Panel -> 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 service.
Uninstalling the OSI StackIn order to uninstall the OSI Stack, open Start -> Settings -> Control Panel -> Add/Remove 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.
3.4.2 Installing Adobe Acrobat ReaderPrior to installing TNMS CT, Adobe Acrobat Reader has to be installed on the Client PC.
36 A50023-K4003-X20-1-7619
User Manual (UMN)Installation
To install Acrobat Reader, double-click the setup file in the Adobe directory on the TNMS CT software DVD. An installation wizard will guide you through the installation process.
For further installation information consult the Adobe Acrobat Reader documentation.
Uninstalling Acrobat ReaderIn 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 Softwareg Follow the mandatory installation sequence for all software parts as described in
Chp. 3.2.5.
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 uninstalled. Existing configurations should be exported and may be imported with the new installation.
– The integrated TNMS CT software installation consists of the Client, Server and EML components.
– The Client and Server components may be installed on the same (local or remote login) or on separate computers (remote login).
– The EML packages are installed on the Server machine.– The element managers are installed on the Client machine.– If one or more system in the TNMS CT platform are equipped with two network
adapters, routing settings must be configured as specified in Chp. 3.6.6 to avoid delays during connection setup between machines.
– To avoid problems during the TNMS CT installation, the user must be logged into the Windows operating system with administrator rights.
3.5.2 Installing TNMS CTg To guarantee a successful installation, it is strongly advised that you close all other
programs and do not interact with any other application while installing TNMS CT.
To install TNMS CT, proceed as follows:
1. Double-click the setup.exe file provided on the TNMS CT software DVD. A welcome window appears, press Next to continue.
A50023-K4003-X20-1-7619
37
User Manual (UMN) Installation
Figure 18 TNMS CT installation: welcome screen2. In the Setup Type window, select the desired mode (LCT or NCT), depending on
your needs and licenses. Press Next to continue.
Figure 19 TNMS CT installation: choose LCT or NCT modeg Step 3. is only performed when installing NCT as selected in Step 2. If you did
not choose to install this component, proceed to Step 4.3. In the Setup Type window, choose the components (Client or Server) you want to
install on this machine. Press Next to continue.
38 A50023-K4003-X20-1-7619
User Manual (UMN)Installation
Figure 20 TNMS CT installation: choose client and/or server installation4. A Setup Status window is displayed showing a registration process.5. In the License Agreement window, scroll down to read the complete text. Press
Yes to accept the license agreement.
Figure 21 TNMS CT installation: license agreement6. In the Choose Destination Location window, a default installation directory is
offered. Press Next to continue.
A50023-K4003-X20-1-7619
39
User Manual (UMN) Installation
Figure 22 TNMS CT installation: choose installation folder7. In the Please choose NetElements to install window, select the desired network
elements to be installed, and press Next to continue.
Figure 23 TNMS CT installation: NE selection8. In the Start Copying Files window ensure that the settings displayed are correct,
and if so, press Next to continue.
40 A50023-K4003-X20-1-7619
User Manual (UMN)Installation
9. A setup status window is displayed, showing the progress of the TNMS CT installa-tion. Various system messages are also displayed during this step, for example informing that LCTs are being installed.This step of the installation process may take long.g You may be prompted to insert the TNMS CT software DVD to continue the
installation, depending on the components you chose to install.10. Once all system components are installed, the InstallShield Wizard Complete
window is displayed. Select the option for restarting the computer, and press Finish to complete the installation.
Figure 24 TNMS CT installation: installation complete
The computer is rebooted and the installation completed.
Subsequent configuration settings are described in Chp. 3.6.
3.5.3 Uninstalling TNMS CTThe TNMS CT software can be uninstalled using the Windows control panel. The follow-ing information is removed during uninstallation:– 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 using File -> Export Configuration.2. Select TNMS CT from the software list and click the Change/Remove button.3. Store the local NSAP address of the Server in a text file.4. Close all open element managers.5. Log off the TNMS CT software and exit.
A50023-K4003-X20-1-7619
41
User Manual (UMN) Installation
6. Stop the service TNMS-CT Server on the Server computerStart -> Settings -> Control Panel -> Administrative Tools -> Services.
Complete the following steps to uninstall the software:
1. Open the Add/Remove Programs window using 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 uninstallation
starts and information windows display the software components, which are cur-rently uninstalled. This procedure will take some minutes.
5. The InstallShield Complete window is displayed, informing if some folders could not be deleted. Press Finish to complete the uninstallation process.
6. The computer is rebooted7. Delete any remaining folders manually using the Windows Explorer (for example:
“C:\Program files\Nokia Siemens Networks\TNMS CT\”).8. Check that the TNMS service mentioned above is removed from the services list.
g If the TNMS CT version initially installed required BRASS as a prerequisite, it is rec-ommended to uninstall BRASS by running the __AutoRemove.cmd located in the Prerequisites folder of the TNMS CT 3.00.196 or earlier installation CD.
The Purge toolWhen uninstalling TNMS CT, the Purge tool can be used to remove remains of still existing installations or in case the regular uninstall routine might have failed. Proceed as the following:
To stop services:
1. Stop the service by opening Control Panel -> Administrative Tools -> Services2. Double-clicking "RCTSrv" will open its property page3. Click Terminate4. Confirm that the service "TNMS-CT Server" is also terminated5. Close the property page by clicking the OK button6. Double-click the batch file "Purge.bat" out of the temporary directory. It will unregis-
ter files, remove files and directories and remove registry entries.
After this process the TNMS CT is fully removed and is installable again.
3.5.4 Adding and Removing Individual TNMS CT ComponentsTo install or remove individual TNMS CT components (e.g. specific EML packages), proceed as follows:
1. Insert the installation DVD-ROM into the DVD-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/uninstallation procedure using Start -> Settings -> Control
Panel -> Add/Remove Programs. Select TNMS CT and click the Change/Remove button.
6. In the Welcome window, press Next.
42 A50023-K4003-X20-1-7619
User Manual (UMN)Installation
7. In the Select Type window choose the mode and press Next.g To change modes (LCT to NCT and vice versa) refer to section 3.5.5 before pro-
ceeding to the next step.8. In the Select TNMS CT components window, the components already installed are
displayed. Select the components you wish to install or uninstall and press Next to continue.
9. In the Please choose NetElements to install window, select the components you wish to install or uninstall, and press Next to continue.
10. In the Repair TNMS CT window, select whether you want to repair the installations of previously installed LCTs, and press Next to continue.
11. The Setup Status window which is now displayed indicates the progress of the pro-cedure.
12. Once the selected components are installed or uninstalled, the InstallShield Complete window is displayed. Select the option for restarting the computer, and press Finish to complete the process.
13. Restart the PC to update your installation.
3.5.5 Changing modesTo change modes in TNMS CT (NCT to LCT or LCT to NCT) proceed as follows:
1. Proceed as described in steps 1. to 6. of section 3.5.4.2. In the Select Type window change from LCT mode to NCT mode or vice versa.
Press Next.g When changing from NCT mode to LCT mode, you will be restricted to local
login, and only a limited number of features will be available.When changing from LCT mode to NCT mode, install the required licenses (refer to step 7.).
3. In the Important Information window, you are notified about the required additional licenses.
4. In the Maintenance window, select Modify and press Next.5. In the Setup Type window, choose the components you want to install on this
machine. Press Next to continue.g Step 5. is performed only if you selected to change mode from LCT to NCT in
Step 2. Otherwise continue to Step 6.6. Proceed as described in steps 8. to 13. of section 3.5.4.7. After restarting the system import the required licences: open the License Informa-
tion window using Configuration -> License... Click Import... on the toolbar and select the path and file of your license XML file.
3.6 Measures after CommissioningAfter the TNMS CT software and relevant 3rd-party software have been installed, TNMS CT 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.2)
A50023-K4003-X20-1-7619
43
User Manual (UMN) Installation
– Java runtime environment parameters (see Chp. 3.6.3)– Initial configuration (see Chp. 3.6.4)– Migration (see Chp. 3.6.5)– Routing settings (see Chp. 3.6.6)
3.6.1 Configuring Windows firewallWhen TNMS CT server is installed, the Windows XP/Vista/Windows 7 firewall must be configured in order to allow communication between:
– TNMS CT server and the client (if the client is installed on a separate computer);– TNMS CT server and the NEs;
Proceed as the following to configure the Windows XP firewall:1. Open Start -> Settings -> Control Panel -> Security Center -> Windows Firewall
to 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 OK
to save the changes.4. Click OK to add the port to the exception list.
Proceed as the following to configure the Windows Vista and Windows 7 firewall:1. locate the Windows Firewall in Control Panel.
1.1 In Windows Vista, open Start -> Control Panel -> Windows Firewall.1.2 In Windows 7, open Start -> Control Panel -> System and Security ->
Windows Firewall.2. Change the firewall settings:
2.1 In Windows Vista, select Change settings to open the Windows Firewall Settings
2.2 In Windows 7, select Allow a program or feature through Windows Firewall.3. On the Windows Firewall Settings select the Exceptions tab, click the Add Port and
configure a TCP port with the name “TNMS CT” and the port number “2002”.4. Click the Change scope button, select the My Network radio button and click OK
to save the changes.5. Click OK to add the port to the exception list.
g If hiT 7300 or OPTRA NEs are present in the network, additional port exceptions must be configured. Follow the procedure above to configure.
For hiT 7300:– UDP port number “161” for establishing a communication with SNMP;– UDP port number “162” for communication with traps for SNMP;– UDP ports from number 10.000 and up (10.000+) for communication with the
LCTs (hiT 7300 4.0.1);– UDP ports from number 20.000 to 21.000 for communication between the LCT
and the NE (hiT 7300 higher than 4.0.1);– TCP port number “20” for FTP communication between the LCT and the NE;– TCP port number “21” for FTP communication between the LCT and the NE.
For OPTRA:– TCP port number “8002” for communication with traps for SNMP.
44 A50023-K4003-X20-1-7619
User Manual (UMN)Installation
3.6.2 PPP Dial-up Setup for Q3 or QSTv2 Network ElementsIn order to connect to a Q3 or QSTv2 NE using RS232, complete the following steps to setup a new dial-up network connection.
g Currently PPP Dial-up Setup and as a result serial line connection to Q3 or QSTv2 NEs are only available when running TNMS CT under Windows XP or Windows 7 (in XP mode) Operating Systems.
3.6.2.1 Setting a new connection1. Open Start -> Programs -> Accessories -> Communications -> Network Con-
nections to open the Network Connections window. Click on the Create a new connection icon in the Network Tasks panel on top left to open the New Connec-tion Wizard.Click Next to continue.
Figure 25 New connection wizard: welcome screen2. In the Network Connection Type window, select Set up an advanced connec-
tion.Click Next to continue.
A50023-K4003-X20-1-7619
45
User Manual (UMN) Installation
Figure 26 New connection wizard: network connection type
3. In the Advanced Connection Option window select Connect directly to another computer.Click Next to continue.
Figure 27 New connection wizard: advanced connection options4. In the Host or Guest window, select Guest.
Click Next to continue.
46 A50023-K4003-X20-1-7619
User Manual (UMN)Installation
Figure 28 New connection wizard: host or guest role5. In the Computer Name enter a name for the new connection, e.g. “MPU-F”.
Click Next to continue.g If a connection dialog appears, cancel it.
Figure 29 New connection wizard: connection name6. In the Select a Device window, select either Communications Port (COM1) or
Communications cable between two computers (COM1). The availability of these two options depends on whether a “Communications cable” modem has already been installed or not. If necessary, Windows XP automatically installs this modem.Click Next to continue.
A50023-K4003-X20-1-7619
47
User Manual (UMN) Installation
Figure 30 New connection wizard: select a device7. In the Completing the New Connection Wizard window click Finish to complete
your settings.If a connection dialog appears, cancel it.
Figure 31 New connection wizard complete8. Open Start -> Programs -> Accessories -> Communications -> Network Con-
nections to open the Network Connections window. Select the icon representing the 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.
48 A50023-K4003-X20-1-7619
User Manual (UMN)Installation
Figure 32 General connection properties9. In the Modem Configuration window, select “19200” for Maximum speed and
uncheck the feature Enable hardware flow control.Click OK to confirm your settings.
Figure 33 Modem configuration10. In the Connection Properties window select the Advanced tab and click the
Settings button to open the Windows Firewall window and configure the firewall settings for this connection.
11. In the Advanced tab, clear the checkbox for the “MPU-F” connection under the Network Connection Settings pane, to deactivate the firewall for this connection.
A50023-K4003-X20-1-7619
49
User Manual (UMN) Installation
12. In the Connection Properties window select the Networking tab and uncheck all protocols except for Internet Protocol (TCP/IP)Select Internet Protocol (TCP/IP) from the list and click Properties.
Figure 34 Connection properties: networking13. In the Internet Protocol (TCP/IP) Properties window, click Advanced...
50 A50023-K4003-X20-1-7619
User Manual (UMN)Installation
Figure 35 Internet protocol (TCP/IP) properties14. In the Advanced TCP/IP Settings window, uncheck Use default gateway on
remote network if you are connected to a LAN and the serial connection at the same time. This way your LAN connection will still be available while your are con-nected via serial line.Click OK twice to confirm your settings and return to the Connection Properties window.
A50023-K4003-X20-1-7619
51
User Manual (UMN) Installation
Figure 36 Advanced Internet protocol (TCP/IP) settings15. In the Connection Properties window select the Networking tab and click
Settings to open the PPP Settings window.16. In the PPP Settings window disable the following check boxes:
– Enable LCP extensions– Enable software compression– Negotiate multi-link for single link connectionsClick OK to confirm your settings and close all opened windows.
17. In TNMS CT Main window open Configuration menu -> DCN Management entry.In the DCN Management View navigate to the Serial Line Server -> Q3 Serial Line Channel and open the context menu -> Properties...In the Properties window open the QB3 Channel tab. Check the Use PPP option and enter the name of the Phonebook Entry.Click Apply to confirm your settings.
52 A50023-K4003-X20-1-7619
User Manual (UMN)Installation
Figure 37 QB3 channel properties
3.6.3 Java Runtime Environment parametersIn order to support several TNMS CT sessions, the physical memory allocated for Java Runtime Environment must be higher than the default 64 MB. Therefore extra physical memory must be allocated for Java Runtime through the following procedure:
1. Open the Windows “Control Panel”.2. Open the “Java(TM) Plug-In Control Panel” window by clicking the Java Plug-In
icon.3. Click on the Advanced tab and insert the following parameter in the Java Runtime
Parameters field to allocate 512 MB of physical memory:-Xmx512m
3.6.4 Initial Configuration of TNMS CTOnce the TNMS CT software has been installed, and the computer restarted, the TNMS CT system can be configured. The main steps of TNMS CT initial configuration are described below. Additional information is provided in the online help under Initial Con-figuration.
Start TNMS CTStart the TNMS CT interface using Start -> Programs -> TNMS CT.
g If a pop-up window appears requesting to install a certificate, answer “Always“ so the certificate is installed and ready for all future installations of Nokia Siemens Networks applets.
LoginLog in TNMS CT using the displayed login dialogue or by clicking the Login icon in the TNMS CT toolbar (see Chp. 4.3.2). When starting the TNMS CT application, the Login dialog is opened automatically.
A50023-K4003-X20-1-7619
53
User Manual (UMN) Installation
Figure 38 TNMS CT login window
– 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 created 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.
g If you are using TNMS CT in LCT mode, the field Server will not be active as Client and Server are always installed on the same machine.
Import licensesBefore working with TNMS CT, its components have to be licensed. The following license types are distinguished:
– Basic licenseEach TNMS CT system requires its own license.
– NE licenseEach NEC managed by TNMS CT requires its own license.
– Optional feature licenseIn case of additionally installed optional features, further licenses are required as well.
In order to import the licenses open the License Information window using Configura-tion -> License... Here, click Import... on the toolbar and select the path and file of your license XML file.
Depending on whether SW and/or HW have been pre-installed by Nokia Siemens Networks staff, you have been provided with the necessary license file, or you have to request it via e-mail. In case of problems concerning licensing, please contact Nokia Siemens Networks Technical Sales.
Configure user accountsA default administrator account is created during installation. Additional accounts can now be created as required.
54 A50023-K4003-X20-1-7619
User Manual (UMN)Installation
Define log configuration settingsThe available size of the various log files on the hard disk should be determined. Settings 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 during operation. If the log file size changes (expands) check the necessary disk space again.
Configure ServerAfter TNMS CT installation, the server, i.e. the Serial Line Server for local connection or the TNMS CT Server for Ethernet connection, must be linked up to the TNMS CT via the DCN Management View (see Chp. 4.3.6).
Configure and activate DCN channelsDCN channels are also configured in the DCN Management View. Once configured, the channel settings should be checked, e.g. for scheduling communication.
Configure network elementsIn the DCN Management View select the Serial Line Server and check the properties of all pre configured subordinate nodes. It is not necessary to activate a node because this 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 network elements can be added to the DCN channels. The required network element type can be selected from the list. Alternatively, GNEs may be added to the channels, which will automatically discover the NEs in the associated OSPF area. The NEs are configured by completing each tab page as described in the Online Help.
Setup the network mapThe network map can now be set up using the TNMS CT Network View. This must be done on the basis of planning data (when installing the system the first time) or by migra-tion 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 the Serial Line Interface (F-Interface).
g The 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. QB3 Interface.
Configure GNE list handling
g The configuration of GNE list handling is only available for hiT 7300 NE’s.
At the NE Property Pages set two additional variables:
– GNE list retriesThis variable defines the number of attempts to connect to the NE via the alternative route before holding on. The default number of attempts is three (3).
– GNE hold on timeThis variable defines the time the system should wait before reattempting to connect to the NE via the list of GNEs. The default is one minute (1 mn).
A50023-K4003-X20-1-7619
55
User Manual (UMN) Installation
Further settingsFurther settings can be configured depending on the individual customers needs, e.g. color settings for alarms.
3.6.5 MigrationTNMS CT V3.1 supports migration of NE configuration data from UniGATE v7.0, UniGATE v7.1, SNMPv2 and SNMPv3. In order to accomplish the migration, export your network configuration data into an xml file via UniGATE. In TNMS CT this file can be imported via File -> Import Configuration....
3.6.6 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 between the 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 A and one for an
external 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 the first 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 B is the address for the external LAN segment, and a gateway PC with routing information is not available, time out cycles will result in delayed communication.
The following connections may then be affected:
The problem can be solved by defining the sequence in which IP address information is transmitted in the network settings for each PC as follows:
1. Right-click the icon My Network Places on your desktop. Select the item Proper-ties from the menu.
2. The Network and Dial-Up Connections window is displayed. Click on Advanced in the toolbar, and from the list that appears select Advanced Settings...
3. The Advanced Settings window is now displayed. In the Connections list, select Local Area Connection. The list beneath (called Bindings for Local Area Con-nection) will now display 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 arrow on the right side of the window. Do this until Internet Protocol (TCP/IP) is the first item in the list under File and Printer Sharing for Microsoft Networks.
Connection Affected Task
Client -> Server Starting the LCT application from a Client and communi-cating with NEs
Server -> Client Starting the Client application.
Table 6 Affected Connections
56 A50023-K4003-X20-1-7619
User Manual (UMN)Installation
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 of the list.
8. Click OK to save the changes and then reboot the computer.
3.7 Upgrading to a new releaseIf you are upgrading TNMS CT to a new release, proceed as follows:
1. Stop the TNMS-CT Server service on the Server computer:Start -> Settings -> Control Panel -> Administrative Tools -> Services.
2. Install the new release by following the steps described in Chp. 3.5.2.g If new NetElements are available with the new release, select those that you
wish to install (refer to step 7. in Chp. 3.5.2).
g If the TNMS CT version initially installed required BRASS as a prerequisite, before upgrading to this new release, it is recommended to uninstall BRASS by running the __AutoRemove.cmd located in the Prerequisites folder of the TNMS CT 3.00.196 or earlier installation CD.
A50023-K4003-X20-1-7619
57
User Manual (UMN) Operation
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)
g Any step-by-step tasks as well as a detailed description of the GUI can be found in the Online Help which is also available in the appendix of this document.
4.1 Working With the GUIThis chapter describes how to work with the TNMS CT graphical user interface (GUI) in general. 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 some specific and useful features.
Blue FramesControl displays, which do not contain the information currently stored inside the NEs, are bordered with a blue frame. Table 7 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 left mouse 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 context menus. A context menu is called by clicking an object of the graphical user interface with the right mouse button. This displays a selection of menu items which are relevant for the selected object in the given situation.
g The offered menus and context menus depend on the operator’s user class.
Data to be displayed in the 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
Table 7 Blue Framing
58 A50023-K4003-X20-1-7619
User Manual (UMN)Operation
g Unless the text states otherwise, always use the left mouse button for clicking and double-clicking.
4.1.3 Working With the KeyboardThe TNMS CT user interface is driven by context menus (click on objects in the user interface with the right mouse button) and therefore cannot be operated without a mouse. Therefore this manual refers throughout to mouse control. However, it is possible 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 a mouse.
4.1.4 Working With the Online HelpThe user interfaces contain Online Help systems. The help systems provide information about the window contents, menus and meanings of used icons. Via the help table of contents 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 window contents.
• Pressing <F1> displays information about the contents of the window which is active at the moment.
g The Online Help gives detailed information on the tasks that are to be performed with TNMS CT. It also provides detailed description about the individual windows, fields, and icons used in TNMS CT.
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)
A50023-K4003-X20-1-7619
59
User Manual (UMN) Operation
4.2.1 Starting a TNMS CT SessionThe TNMS CT Client is started via Start -> Programs -> TNMS CT. Once the TNMS CT Client has been started, the operator can enter the login data. Functions authorized by the operator’s user class can now be accessed.
The Client contacts the Server and requests alarm information, port and connection data, and the data required for mapping the network. If complete data is not available for certain network elements, these are shown as unavailable on the user interface by a box containing 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 logged on. Once it has been started, a connection to all configured and activated network elements is established and their data is uploaded. An icon is displayed in the Windows XP/Windows Vista taskbar.
Once the Server has started, it is always active. Moreover, terminating the Client does not 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 for all 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 entry View -> 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 execute required functions directly at the NE.
4.2.6 Administrating NE Write AccessTNMS CT only administers write access to managed network elements which support this feature via the context menu of the NE icon on the network map. Older QD2 NEs might require an additional request via their element managers. Consequently, the TNMS CT operator also has limited control over external LCT write access.
60 A50023-K4003-X20-1-7619
User Manual (UMN)Operation
4.2.7 Terminating a TNMS CT SessionA TNMS CT session is terminated when the user logs off. All windows are closed and access 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, configuration and maintenance of the network. The set of functions available to each individual operator 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 EM of an SMA16/4) to control and configure individual network elements.
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)
Figure 39 shows an example of the TNMS CT main window indicating some of the avail-able functions.
Figure 39 TNMS CT graphical user interface
A50023-K4003-X20-1-7619
61
User Manual (UMN) Operation
4.3.1 Menu BarFigure 40 shows the menu bar of the TNMS CT main window with its menu items. When you click on one of these menu items, the pull-down menu specific to the menu item opens.
Figure 40 Menu bar
Table 8 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 system.
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
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!
Table 8 Menu Bar Entries
62 A50023-K4003-X20-1-7619
User Manual (UMN)Operation
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 displayed in TNMS-CT. This option does not apply to the alarms displayed in the opened LCT.
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 external alarm notifica-tion.
NCT mode only!
Configuration Configuring Various Tasks
DCN Management... Work in the DCN Management View.
Serial Line... Work in the Serial Line View.
Connect All Connect to all network elements.
Disconnect All 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!
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
Table 8 Menu Bar Entries (Cont.)
A50023-K4003-X20-1-7619
63
User Manual (UMN) Operation
4.3.2 ToolbarThe toolbar runs along the top edge of the main window above the working area. Clicking on one of these buttons provides quick and particularly easy access to certain frequently used functions.
The functions of the main toolbar buttons are briefly described in Table 9.
In addition to the main window toolbar, other TNMS CT windows provide their own tool-bars.
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 View2 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.
Table 8 Menu Bar Entries (Cont.)
Icon Function Menu Entry Opens Window
Log on or log off the TNMS CT Server. Security menu -> Login... entry
Security menu -> Logoff... entry
Login
Work with the Serial Line View. Configuration menu -> Serial Line... entry
Serial Line View
Work with the DCN Management View. Configuration menu -> DCN Manage-ment... 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
Table 9 Main Toolbar Icons
64 A50023-K4003-X20-1-7619
User Manual (UMN)Operation
4.3.3 Status BarThe status bar (see Figure 41) runs along the bottom of the main window. It gives infor-mation on the operating states and displays important messages, such as alarms, in short form.
Figure 41 Status Bar
Table 10 describes the TNMS CT status bar from left to right.
4.3.4 Network ViewThe Network View provides graphical representation of your network. Figure 42 shows an example of a network map indicating objects with context menus (ovals) and other objects (rectangles).
Notification Area A short help text for the currently selected window, menu entry or toolbar 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 down or 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 information 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).
Table 10 Status Bar Components
A50023-K4003-X20-1-7619
65
User Manual (UMN) Operation
Figure 42 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 background of the network plan and position your network elements in this map according to their real location.
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 Table 12.
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 FTPfiles 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.
Table 11 Network View Context Menus
66 A50023-K4003-X20-1-7619
User Manual (UMN)Operation
Acknowledge All Acknowledge all NE alarms displayed in TNMS-CT. This option does not apply to the alarms dis-played in the opened LCT.
Access Control Control the write access on the selected NE with one of the following options depending on the NEs interface type:
Connect Connect to all network elements.
Disconnect Disconnect from the selected network element.
Request Write Access Get write access on the selected NE unless any other LCT has write access on it.
Release Write Access 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 possible:- 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 unacknowledged, major unacknowledged, minor unacknowledged alarms or on unacknowledged warnings.
Properties... Display information on the selected NE.
Port Connection
Size of NE Symbols Set the size of the NE icons on the network map. The following options are possible:- 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 unacknowledged, major unacknowledged, minor unacknowledged alarms or on unacknowledged warnings.
Port Connection List... Display the Port Connection List window filtered for the selected port connection.
NCT mode only!
Connect Connect to all network elements.
Disconnect Disconnect from all network element.
Acknowledge All Acknowledge all alarms displayed in TNMS-CT. This option does not apply to the alarms displayed in the opened LCT.
Find NE... Find an NE on the network map. The found NE will be framed.
Lock NE Symbols Fix the NE icons on the network map.
Background... Assign a background bitmap to your network map or set the background color.
NCT mode only!
Network Map
Size of NE Symbols Set the size of the NE icons on the network map. The following options are possible:- 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 unacknowledged, major unacknowledged, minor unacknowledged alarms or on unacknowledged warnings.
Connect Connect to all network elements.
Disconnect Disconnect from all network element.
Acknowledge All Acknowledge all alarms displayed in TNMS-CT. This option does not apply to the alarms displayed in the opened LCT.
Table 11 Network View Context Menus (Cont.)
A50023-K4003-X20-1-7619
67
User Manual (UMN) Operation
4.3.5 Serial Line ViewTheSerial Line View provides graphical representation of your serial line connection. Figure 43 shows an example of the network map indicating objects with context menus.
Figure 43 Serial Line View
Each item of the Serial Line View offers an individual context menu as shown in Table 11.
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 context menu of the individual objects of the DCN Management tree (see Chp. 4.3.6.2). The DCN Management tree consists of the following objects in hierarchical order:
• Server • DCN Channel • 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.
Find NE... Find an NE on the network map. The found NE will be framed.
Lock NE Symbols Fix the NE icons on the network map.
Links... Configure links between NEs on the network map.NCT mode only!
Background... Assign a background bitmap to your network map or set the background color.
NCT mode only!
Table 11 Network View Context Menus (Cont.)
NE
Connect Connect to a network element, which is clearly identifiable, via the serial line interface.
Automatic Connection Connect to a network element via the serial line interface. TNMS CT tests all channels until it can estab-lish a suitable connection.
Table 12 Serial Line View Context Menus
68 A50023-K4003-X20-1-7619
User Manual (UMN)Operation
– 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.
Figure 44 below gives an example of the DCN Management View.
Figure 44 DCN Management View
4.3.6.1 DCN Management ToolbarThe DCN Management toolbar (see Figure 45) runs along the top edge of the DCN Man-agement View above the working area. Clicking on one of these buttons with the left mouse button provides quick and particularly easy access to certain frequently used functions.
Figure 45 DCN Management Toolbar
The functions of the DCN Management toolbar buttons are briefly described in Table 13.
Icon Function Context Menu Entry Opens Window
Find an NE in the DCN Management tree.
Find NE
Add a new subcomponent to the selected DCN object.
New... entry Properties
Duplicate the selected DCN object. Duplicate... entry Properties
Delete the selected DCN object. Delete... entry
Table 13 DCN Management Toolbar Icons
A50023-K4003-X20-1-7619
69
User Manual (UMN) Operation
4.3.6.2 DCN Management TreeEach DCN object provides the same sort of context menu. Table 14 shows and briefly explains the generic context menu entries.
Display the properties of the selected DCN object.
Properties... entry Properties
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
Icon Function Context Menu Entry Opens Window
Table 13 DCN Management Toolbar Icons (Cont.)
DCN Object
New... 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 information 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.
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!
Table 14 DCN Management Tree Entries
70 A50023-K4003-X20-1-7619
User Manual (UMN)Abbreviations
5 AbbreviationsBCM Border Crossing Mode
BSHR Bidirectional Self-Healing Ring
CC Cross Connection
CE Communauté Européenne
CDM Cross Domain Manager
CORBA Common Object Request Broker Architecture
CST Central Standard Time
CT Craft Terminal
DAT Digital Audio Tape
DB Database
DCC Data Communication Channel
DCN Data Communication Network
EM Element Manager
EML Element Management Layer
EM-OS Element Manager Operations System
EMS Element Management System
ESCON Enterprise System Connection
ESD Electrostatic-Sensitive Devices
FCAPS Fault Configuration Accounting Performance Security
FICON Fiber Connection
FTP File Transfer Protocol
GBE Gigabit Ethernet
GMT Greenwich Mean Time
GNE Gateway Network Element
GUI Graphical User Interface
IMN Installation Manual
ITU-T International Telecommunications Union - Telecommunications Standard Sector
LAN Local Area Network
LCAS Link Capacity Adjustment Scheme
LCT Local Craft Terminal
A50023-K4003-X20-1-7619
71
User Manual (UMN) Abbreviations
MAC Media Access Control
MDAC Microsoft Data Access Components
MIB Management Information Base
MS Microsoft
MSP Multiplex Section Protection
NCT Network Craft Terminal
NE Network Element
NML Network Management Layer
NEC Network Element Controller
NSAP Network Service Access Point
OGL Operator Guidelines
OLEDB/ADO Object Linking and Embedding Database/Active X Data Objects
OSI Open System Interconnection
OSPF Open Shortest Path First
OTH Optical Transport Hierarchy
PC Personal Computer
PCI Peripheral Component Interconnect
PDF Portable Document Format
PDH Plesiochronous Digital Hierarchy
PLET Performance Log Export Tool
PM Performance Measurement
PMP Performance Measurement Point
PPP Point-to-Point Protocol
RAID Redundancy Array of Independent Disks
SAN Storage Area Network
SCSI DAT Small Computer System Interface Digital Audio Interface
SDF Semicolon Delimited Format
SDH Synchronous Digital Hierarchy.
SMS Short Message System
SNCP Subnetwork Connection Protection
SNMP Simple Network Management Protocol
SP Service Pack
72 A50023-K4003-X20-1-7619
User Manual (UMN)Abbreviations
SSL Secure Sockets Layer
TCM Tandem Connection Monitoring
TCN Threshold Crossing Notification
TCOA TMF CORBA Agent
TCOI TMF CORBA Interface
TCOM TMF CORBA Manager
TCP/IP Transmission Control Protocol/Internet Protocol
TED Technical Description
TIF Telemetry Interface
TMF Telecommunication Management Forum
TMN Telecommunication Management Network
TMS Telecommunication Management System
TNMS Telecommunication Network Management System
TP Termination Point
TSF Tab Separated Format
UHC Ultra-High Capacity
UNO Universal Network Object
UPS Uninterruptible Power Supply
WAN Wide Area Network
WDM Wavelength Division Multiplexing
XML Extended Markup Language
A50023-K4003-X20-1-7619
73
User Manual (UMN)
IndexPDF 7
Symbols<$nopage>Gateway NE
see GNE 15<$nopage>GUI
see ’Graphical User Interface’ 13
AAccess control 66Acknowledge 62, 66Add NetServer 69Adobe Acrobat Reader 35Alarm 65
Filter 62List 62, 65List and Log 17, 61Log 62, 65Statistics 18, 65
Antistatic mat 22Application
Settings 62Architecture
Client/Server 11Network 9Software 12System 11
Automatic recognition 17Automatic topology discovery 16
BBackground bitmap 62, 66, 67Basic information
Personnel requirements 21Blue frame 57Broadcast user configuration 63
CCE conformity 21Client components 12Client/Server architecture 11Communication
Interface 16Loss 17
Context Menu 57Context menu 57, 58Copy NE name into ID name 69
DDate and time settings 59, 61
DCN 9Channel 54, 67Management 16, 17, 54, 59, 62, 67NE 67Object 59, 69Object Properties 69
DCN channelDCN management 15
DCN Management Tree 69Deactivate 69Delete 69Delivery 22Dial-up connection 44Discover topology 16Duplicate 69
EElectrostatic-sensitive devices 22Element manager 13, 65
Start 59Start offline 63
EML packages 13, 24Installation 41
ESD symbol 22Exit application 61Export 13, 61
FFault
Management 17, 62Settings 62
File transfer 65Find 61, 66, 67FSP 24
GGNE 54
DCN management 15Graphical User Interface 13, 60Grounding bracelet 22
IIcon 63, 66, 67, 68Import 13, 61Initial configuration 52Installation
Adobe Acrobat Reader 35Individual components 41PCI I/O card 27TNMS CT 36
74 A50023-K4003-X20-1-7619
User Manual (UMN)
Installation softwareEML packages 24JavaSoft JAVA Runtime Environment 24
KKeyboard 58
LLCT mode 14Licensing 62
Import 53Software 20
Links 14, 65, 67Lock 66, 67Log management 18, 54Login 52, 59, 62, 63
MMAC address 33Measuring equipment 22Menu bar 61Migration 55Mouse 57, 58Multiple network adapters 55
NNCT mode 14NE 14, 54, 65, 67
Automatic connection 67Connect 62, 66, 67Controller 13Disconnect 62, 66Element manager 13Properties 66Supported 10
NetServer 67Frame 13
NetworkArchitecture 9Interface 16Management 14, 15Map 54
Network elementDCN management 15
Network interface 16Network map 66Network View 54, 64, 65NSAP address 32
OOnline Help 58, 63, 69Open transactions 61, 64
PPassword 62PCI I/O card 27Port connection 15, 61, 65, 66Port connection list 61, 65, 66Print 61, 63, 69
QQ3 16QD2 16QST 16QSTV2 16
RRelease 66Remote login 18Request 66Resynchronization 66Routing settings 55
SSafety precautions
Electrostatic-sensitive devices 22Save 61Scaled start-up 16Screen level integration 19Security 62
Log 18Settings 62
Serial line interface 16Serial Line View 62, 67Server 13, 59, 62, 63, 67
Activate 59Configuration 54DCN management 15
SNMP 16Software architecture 12Start application 52, 59Status bar 62, 64Stop application 60, 61Structure
Network 9Subnetwork
DCN management 15Supplementary documentation
Delivery notes 20Field test protocols 20Protocols 20
System information 63System Message Log 61
Settings 62
A50023-K4003-X20-1-7619
75
User Manual (UMN)
TTelegram protocol 16Toolbar 62
DCN Management View 68Main window 63
Topology discovery 16
UUnderlined letters 58Upgrade 65User
Accounts 53, 62Administration 18Class 18
User Manual 63
VView 61, 66, 67
WWindow 63Window style 61Write access 19, 59, 66