User Manual

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 re sponsibility 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 do cumentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" a nd all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agr eement 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 er rors 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 error s in this documentation as soon as possible. IN NO EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR E RRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, 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 ar e considered protected by copyrights and other intellectual property rights accord ing to the applicable laws. The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered tr ademark 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 re served.

f

Important Notice on Product Safety This product may present safety risks due to laser, electricity, heat, and other sources of danger. Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product. The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.

The same text in German:

f

Wichtiger Hinweis zur Produktsicherheit Produktsicherheit Von diesem Produkt können Gefahren durch Laser, Ele ktrizität, Hitzeentwicklung oder andere Gefahrenquellen ausgehen. Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur dur ch geschultes und qualifiziertes Personal unter Be achtung der anwendbaren Sicherheitsanforderungen erfolgen. Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ i m Teil „Legal, Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentationssatzes.

2

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

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 re sponsibility 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 do cumentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" a nd all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agr eement 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 er rors 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 error s in this documentation as soon as possible. IN NO EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR E RRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, 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 ar e considered protected by copyrights and other intellectual property rights accord ing to the applicable laws. The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered tr ademark 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 re served.

f

Important Notice on Product Safety This product may present safety risks due to laser, electricity, heat, and other sources of danger. Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product. The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.

The same text in German:

f

Wichtiger Hinweis zur Produktsicherheit Produktsicherheit Von diesem Produkt können Gefahren durch Laser, Ele ktrizität, Hitzeentwicklung oder andere Gefahrenquellen ausgehen. Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur dur ch geschultes und qualifiziertes Personal unter Be achtung der anwendbaren Sicherheitsanforderungen erfolgen. Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ i m Teil „Legal, Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentationssatzes.

2

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Table of Contents This document has 75 pages. 1 1.1 1. 1 1.2 1. 2 1.3 1. 3 1.4 1. 4

Introductory Notes . . . . . . . Int nte end nded ed aud udiien ence ce . . . . . . . Str truc ucttur ure e of of thi this s doc docum umen ent. t. Sym ymbo bols ls an and d con conve vent ntiion ons s. Fur urth ther er do docu cum men enttati tio on. . . .

2 2.1 2. 1 2.1. 2. 1.1 1 2.2 2. 2 2.2. 2. 2.1 1 2.2. 2. 2.2 2 2.2.2. 2.2 .2.1 1 2.2. 2. 2.2. 2.2 2 2.3 2. 3 2.3. 2. 3.1 1 2.3. 2. 3.2 2 2.3. 2. 3.3 3 2.3. 2. 3.4 4 2.3. 2. 3.5 5 2.3. 2. 3.6 6 2.3. 2. 3.7 7 2.3. 2. 3.8 8 2.3. 2. 3.9 9 2.3. 2. 3.10 10 2.3. 2. 3.11 11 2.3. 2. 3.12 12 2.3. 2. 3.13 13 2.3. 2. 3.14 14

Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Nettwo Ne work rk Ar Arch chit itec ectu ture re . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Sup uppo port rted ed NE NEs s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Sys yste tem m Ar Arch chiite tect ctur ure. e. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Hard Ha rdwa ware re Co Comp mpon onen ents ts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Sof oftw twar are e Com Compo pone nent nts s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 TNMS TN MS CT Cli Client. ent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 TNMS TN MS CT Se Serv rver er . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Fun unct ctiion onal al Ov Over erv vie iew w . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 LCT LC T and and NC NCT T Mod Modes. es. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Nettwo Ne work rk Ma Mana nage geme ment nt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 DCN DC N Ma Mana nage geme ment. nt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Comm Co mmun unic icat atio ion n Int Inter erffac aces. es. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Tele Te legr gram am Pr Prot otoc ocol ols s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Sca cale led d Sta Start rt--up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Aut utom omat atiic Top Topol olog ogy y Dis Disco cove very ry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Aut utom omat atiic Rec Recog ogni niti tion. on. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Fau ault lt Ma Mana nage geme ment. nt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 User Us er Ma Mana nagem gement ent an and d Sec Secur urit ity y . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Remot Re mote e Logi Login n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Log Lo g Mana Manage geme ment. nt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Scre Sc reen en Le Leve vell Int Integ egra rati tion on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Prio Pr iori rity ty/M /Mut utabl able e Excl Exclus usio ion n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3 3.1 3. 1 3.1. 3. 1.1 1 3.1. 3. 1.2 2 3.1. 3. 1.3 3 3.2 3. 2 3.2. 3. 2.1 1 3.2. 3. 2.2 2 3.2. 3. 2.3 3 3.2. 3. 2.4 4 3.2. 3. 2.5 5 3.3 3. 3 3.3. 3. 3.1 1 3.3. 3. 3.2 2 3.3. 3. 3.3 3

Installat atiion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Prot otec ecti tive ve Me Meas asur ures es an and d Han Handl dliing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Saf afet ety y Pre Preca caut utiion ons s Whe When n the the Un Unit it is Ope Open n . . . . . . . . . . . . . . . . . . . . . . 21 Prot Pr otec ecti tion on ag agai ains nstt Exce Excess ssiv ive e Con Conta tact ct Vo Volt ltage ages. s. . . . . . . . . . . . . . . . . . . 21 Hand Ha ndllin ing g Mod Modul ules es . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Pre repa pari ring ng for In Inst stal alla lattio ion n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Comp Co mpon onen entt Del Deliv iver ery y . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Hard Ha rdwa ware re an and d Sof Softw twar are e Rec Recom omme mend ndat atio ions ns . . . . . . . . . . . . . . . . . . . . . 23 Ins nsta talllat atiion So Soft ftwa warre . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Ins nsta talllat atiion an and d Cab Cabllin ing g . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Ins nsta talllat atiion Se Sequ quen ence ce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Ins nsta talllin ing g the the Op Oper era atin ing g Sy Syst stem. em. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Bef efor ore e you you Beg egiin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Ins nsta talllin ing g Wi Wind ndow ows s OS. OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Hard Ha rdwa ware re Co Conf nfiigu gura rati tion. on. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

 A50023 -K4003-X20-1-7619 -K4003-X2 0-1-7619 Issue: 1 Issue date: October 2012

.. . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . .. ... . . . . .. . . . . .. . . . . . .. . . .. .. . . .. . .. .. . . . . . .. . . . . .. . . . .. .. . . .. .. . .. . . .. .. . . . . . .. . . . . .. . . . .. .. . .. . .. . .. . . .. .. .. . . . .. . . . . .. . . . . . .. . . . . .. . . .. . ..

7 7 7 8 8

3

User Manual (UMN)

3.3.4 3.4 3.4.1 3.4.2 3.5 3.5.1 3.5.2 3.5.3 3.5.4 3.5.5 3.6 3.6.1 3.6.2 3.6.2.1 3.6.3 3.6.4 3.6.5 3.6.6 3.7

Windows Services Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Installing 3rd-Party Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Installing an OSI Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Installing Adobe Acrobat Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Installing the TNMS CT Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Installing TNMS CT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Uninstalling TNMS CT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Adding and Removing Individual TNMS CT Components . . . . . . . . . . . 41 Changing modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Measures after Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Configuring Windows firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 PPP Dial-up Setup for Q3 or QSTv2 Network Elements . . . . . . . . . . . . 44 Setting a new connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Java Runtime Environment parameters . . . . . . . . . . . . . . . . . . . . . . . . . 52 Initial Configuration of TNMS CT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Routing Settings for PCs with Multiple Network Adapters . . . . . . . . . . . 55 Upgrading to a new release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

4 4.1 4.1.1 4.1.2 4.1.3 4.1.4 4.2 4.2.1 4.2.2 4.2.3 4.2.4 4.2.5 4.2.6 4.2.7 4.3 4.3.1 4.3.2 4.3.3 4.3.4 4.3.5 4.3.6 4.3.6.1 4.3.6.2

Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Working With the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 TNMS CT Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Working With the Mouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Working With the Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Working With the Online Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Basic Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Starting a TNMS CT Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Starting and Stopping TNMS CT Server. . . . . . . . . . . . . . . . . . . . . . . . . 59 Activating and deactivating TNMS CT Server. . . . . . . . . . . . . . . . . . . . . 59 Setting Date and Time Zone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Starting Element Manager Applications . . . . . . . . . . . . . . . . . . . . . . . . . 59 Administrating NE Write Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Terminating a TNMS CT Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Graphical User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Network View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Serial Line View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 DCN Management View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 DCN Management Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 DCN Management Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

5

Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

4

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

List of Figures Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 Figure 12 Figure 13 Figure 14 Figure 15 Figure 16 Figure 17 Figure 18 Figure 19 Figure 20 Figure 21 Figure 22 Figure 23 Figure 24 Figure 25 Figure 26 Figure 27 Figure 28 Figure 29 Figure 30 Figure 31 Figure 32 Figure 33 Figure 34 Figure 35 Figure 36 Figure 37 Figure 38 Figure 39 Figure 40 Figure 41 Figure 42 Figure 43

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

General Structure of a TNMS CT Network . . . . . . . . . . . . . . . . . . . . . . 10 System Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Overview of Software Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 A GNE detecting its managed NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Labelling of electrostatic-sensitive devices (ESD symbol). . . . . . . . . . . 22 Add or Remove Programs window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Windows Components Wizard and IIS dialogs . . . . . . . . . . . . . . . . . . . 30 Programs and Features window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Windows Features dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Setup OSI Stack: Choose Destination Location . . . . . . . . . . . . . . . . . . 32 Setup OSI Stack: How to set NSAP address. . . . . . . . . . . . . . . . . . . . . 33 Setup OSI Stack: Company with own NSAP management . . . . . . . . . . 33 Setup OSI Stack: NSAP derived from MAC address. . . . . . . . . . . . . . . 34 Setup OSI Stack: Use a serial Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 OSI Stack installation: Start Copying Files window . . . . . . . . . . . . . . . . 35 TNMS CT installation: welcome screen . . . . . . . . . . . . . . . . . . . . . . . . . 37 TNMS CT installation: choose LCT or NCT mode. . . . . . . . . . . . . . . . . 37 TNMS CT installation: choose client and/or server installation . . . . . . . 38 TNMS CT installation: license agreement . . . . . . . . . . . . . . . . . . . . . . . 38 TNMS CT installation: choose installation folder . . . . . . . . . . . . . . . . . . 39 TNMS CT installation: NE selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 TNMS CT installation: installation complete . . . . . . . . . . . . . . . . . . . . . 40 New connection wizard: welcome screen . . . . . . . . . . . . . . . . . . . . . . . 45 New connection wizard: network connection type . . . . . . . . . . . . . . . . . 45 New connection wizard: advanced connection options . . . . . . . . . . . . . 46 New connection wizard: host or guest role . . . . . . . . . . . . . . . . . . . . . . 46 New connection wizard: connection name. . . . . . . . . . . . . . . . . . . . . . . 47 New connection wizard: select a device . . . . . . . . . . . . . . . . . . . . . . . . 47 New connection wizard complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 General connection properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Modem configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Connection properties: networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Internet protocol (TCP/IP) properties . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Advanced Internet protocol (TCP/IP) settings . . . . . . . . . . . . . . . . . . . . 51 QB3 channel properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 TNMS CT login window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 TNMS CT graphical user interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Network View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Serial Line View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 DCN Management View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 DCN Management Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

5

User Manual (UMN)

List of Tables Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13 Table 14

6

Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Supported NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Hardware recommendations for TNMS CT . . . . . . . . . . . . . . . . . . . . . . 23 Software recommendations for TNMS CT . . . . . . . . . . . . . . . . . . . . . . . 23 Affected Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Blue Framing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Menu Bar Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Main Toolbar Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Status Bar Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Network View Context Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Serial Line View Context Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 DCN Management Toolbar Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 DCN Management Tree Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Introductory Notes

1 Introductory Notes This User Manual gives a complete overview of the functions, applications, architecture and installation of TNMS CT.

1.1

Intended audience This document is intended for all TNMS CT users.

1.2

Structure of this document The User Manual (UMN) consists of the following main chapters  •

 •

 •

g

Information This chapter provides an overview of the applications, system architecture, features and functions of TNMS CT (see Chp. 2). Installation This chapter contains instructions on installing the TNMS CT software (see Chp. 3). Operation This chapter contains a general description of the TNMS CT user interfaces as well as the necessary background information (see Chp. 4).

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.

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

7

Introductory Notes

1.3

User Manual (UMN)

Symbols and conventions The following symbols are used in this docum ent: Symbol

Explanation

Notes provide ad ditional useful information. Warnings provide information on critical issues that could result in equipment damage or data loss if ignored. Table 1

Symbols

The following conventions are used in this document: Convention

Explanation

Graphical user interface text, e. g., field names and button descriptions, are written in bold.

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 an d bold. Example: Press , for help on the current window.

Table 2 

1.4

Conventions

Further documentation  An online help system is provided with the TNMS CT software. It includes comprehensive 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 administrate TNMS CT. Help can be invoked in any of the following ways:

8

 •

 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 , which displays information about the contents of the active window.

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Information

2 Information TNMS 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 p rovides access to network elements via a network interface (ethernet) or via a serial line interface (RS232). There are two operation modes for TNMS CT: the Local Craft Terminal (LCT) mode 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 presen t 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:  –   –   – 

2.1

Network Architecture (see Chp. 2.1) System Architecture (see Chp. 2.2) Functional Overview (see Chp. 2.3)

Network Architecture Figure 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.

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

9

Information

User Manual (UMN)

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 NEs TNMS CT supports the following NEs: Management interface

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, hiT7060, hiT7060 HC, hiT 7065, hiT 7080, hiT 7300

Table 3

10

Supported NEs

Supported NEs

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

2.2

Information

System Architecture TNMS CT is a scalable single-user system w ith a client/server architecture comprising several industry standard PCs with the Windows ope rating 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 management 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 

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

System Architecture

11

Information

User Manual (UMN)

2.2.1

Hardware Components The TNMS CT hardware components depend directly of the network size. For more information about the minimum recommended hardware see chap ter 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 Components The 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

2.2.2.1



Overview of Software Components

TNMS CT Client The main parts of the TNMS CT client component are the network management graphical user interface including the import and expo rt interfaces and the element manag ers.

12

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Information

Network Management Graphical User Interface

The 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 ne twork 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 Manager 

In 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 controller to the element manager. Element manager applications provide full access to a ll 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 Export

Data 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 M S Excel) can read these files. Import / Export Interface

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

g 2.2.2.2

Detailed operating information on operating TNMS CT is provided in Chapter 4 and in the Online Help.

TNMS CT Server  The main parts of the TNMS CT Server component are the NetServer frame and the EML packages including NE controllers. NetServer Frame

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

 A EML package is an installation p ackage, 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 Controllers

The 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 ne cessary information from the element management layer.

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

13

Information

User Manual (UMN)

 A correspond ing NE controller must be registered in the system fo r 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 Overview TNMS 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 manage ment layer. Various security management features are also implemented.

2.3.1

LCT and NCT Modes Depending 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 n etwork elements. Up to three element managers may be open at the same time only. NCT Mode

The Network Craft Terminal ( NCT) is used for local or remote m anagement of network elements. In addition to the LCT functions, the monitoring of a ll 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 a t the same time only. Information on remote login is given in Chp. 2.3.11.

2.3.2

Network Management The 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 connections. Link

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

14

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Information

Port Connection

This objects represents port connections that have been established between NEs. The port connection information is stored inside the NE itself.

2.3.3

DCN Management The following objects are managed by TNMS CT and handled via the graphical tree view in the DCN Management View . Server 

The Server nodes provide the following functions:  –   –   – 

 Activating o r deactivating all subordinated o bjects 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 Channels

The DCN channel nodes provide the following functions:  – 

 –   – 

Handling the connection to one or more different NEs of the same DCN channel type.  Activating o r deactivating all subordinated o bjects at once. Behaving like OSPF area with up to eight GNE s. Additional OSPF settings are not necessary in TNMS CT but NEs must have OSPF activated.

Subnetworks

The DCN channel nodes allow the operator to categorize network elements into subnetworks. This information is also displayed on the network map. Network Elements

The NE nodes provide the following functions:  –   – 

Handling the connection to one network element.  Activating o r deactivating a network element.

When an NE node has been activated, a corresponding NE symbol is displayed on the network map. Gateway Network Elements

The GNE nodes provide the following functions:  –   –   – 

 Auto-detecting the network elements of the same OSPF area. Routing due to cost factors.  Automatic protection switching from the primary GNE to a secondary GNE when the connection to the primary GNE is lost.

When one or more GNEs are added to a DCN channel, the associated NEs will be 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.

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

15

Information

User Manual (UMN)

Figure 4

2.3.4

 A GNE detecting its managed NEs

Communication Interfaces TNMS 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 Protocols TNMS CT supports the following telegram protocols to communicate with NEs:

 – 

QD2 QST QSTV2 Q3

 – 

SNMP

 –   –   – 

TNMS CT is capable of u sing these protocols simultaneously.

2.3.6

Scaled Start-up To avoid DCN overload during the system start-up phase, a scaled start-up is supported.  According ly, the connection to the NEs managed by a server are not established simultaneously, but one after another. A parameter set u p via theDCN Management View allows a simultaneous start-up.

2.3.7

Automatic Topology Discovery Several NEs supported by TNMS CT are capable of storing topology information, such as neighboring NEs and port connections. As soon as o ne of these NEs is activated via

16

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Information

theDCN Management View , the topology information is available in TNMS CT. Accordingly, integration of network information is simplified.

g

2.3.8

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 activation of the NE in TNMS CT.

Automatic Recognition In 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 channels.

2.3.9

Fault Management Fault management in TNMS CT com prises 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 an d 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 a s 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 pe rmanent 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 criteria. If alarm notifications are received by the TNMS CT Server or TNMS CT Client, the following 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 e lement 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

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

17

Information

User Manual (UMN)

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. The Alarm Statistic window enables the operator to handle alarms conveniently. The  Alarm statistic windows shows:  –   –   –   – 

The number of current alarm per severity.  Alarms sep arated for unacknowledged and acknowledged state. Summary counters per severity. Summary counter of total alarms.

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

2.3.10

User Management and Security The 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 a SecurityLog 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. Additionally, the following security features are implemented:  – 

 –   – 

2.3.11

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.

Remote Login TNMS 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 2.3.12

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

Log Management In 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 p rinted 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 op erator can, however, specify certain attributes such as the maximum log size. TNMS CT provides the following permanent logs:

18

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Information

 •

Alarm log

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

The system m essage log contains a chronological list of relevant administrative events. Critical events are displayed in the user interface.  •

Server log and Client log

The 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 Integration TNMS 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:  –   – 

2.3.14

Set the UniGATE machine to host. Set the TNMS CT computer to remote controller.

Priority/Mutable Exclusion Network 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 comprises 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.

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

19

Installation

User Manual (UMN)

3 Installation This 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 numb er 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 Software

In 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 No kia 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 installation folders and Java installation folders (e.g., rt.jar) from the scanning. Additional Documentation

In addition to the customer documentation the following information is also available upon demand:  – 

 – 

 – 

 – 

20

Delivery notes:

These provide an overview of the hardware, software and docum entation delivered. Documentation from the O&M Centre : On request, Nokia Siemens Networks Technical Sales can supply project documentation which provides specific information about the installation. These planning documents are available to the customer after installation work is completed. Protocols : During commissioning, an acceptance protocol should be maintained. The acceptance 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 Issue: 1 Issue date: October 2012

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 Declaration

The CE conformity declaration for the product is fulfilled if installation and cabling are carried out in accordance with the docum entation supplied. Where necessary, projectspecific 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 subsequent problems lies with the person responsible for the de viation. Personnel Requirements for Commissioning

The following personnel requirements must be fulfilled for commissioning:  –   –   – 

 –   –   –   – 

3.1

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/Windows 7. Familiarity with LAN s/WAN s. Basic knowledge of measurement systems. Knowledge of operating electrostatic-sensitive devices.

Protective Measures and Handling Protective measures and information on handling electrical components in the TNMS CT installation is provided here.

g 3.1.1

 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.

Safety Precautions When the Unit is Open Before opening the unit, remove the power cable. Once the unit is o pen, 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 Voltages When 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.

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

21

Installation

User Manual (UMN)

3.1.3

Handling Modules Modules 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 n ot 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 Installation Prior to installing TNMS CT check the following chapters to ensure that all requirements are met. Information is provided on:  –   –   –   –   – 

3.2.1

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)

Component Delivery Before installation, ensure that:  –  The delivery is complete in accordance with the delivery units specified in the delivery note (hardware, software and documentation).

22

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manu al (U MN)

Installation

 – 

3.2.2 3.2.2

The components are not damaged in any way.

Hardw Hardware are and Softwar Software e Recomm Recommend endati ations ons The following tables provide an overview of the hardware and software recommendations for running TNMS CT. Hardware

CPU

Recommendations

Pentium IV 2,6 GHz/51 2 kB 1 GHz or faster 32-bits (x86) in case of Windows 7

Memory

1 GB

Hard Disk

40 GB

Optic Optical al Disc Disc Dri Drive ve

DVD-R DVD-ROM OM drive drive

LAN

Ethernet card , 2x 3C OM (3C98 2-TXM)

Graph Graphic ics s Car Card d

32 MB MB (wi (with th Dir Direc ectX tX 9 gra graph phic ics s devi device ce wit with h WDDM WDDM 1.0 1.0 or or high higher er driver for Windows 7)

Interface ports

Ethernet port RS232 serial port or generic RS232 to USB ada pter 

Monitor Table 4

g

Color monitor 19” Hardware recommendations for TNMS CT

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.

f

TNMS-CT does not support Hyper-Threading technology, which is used in som e Intel Pentium 4 processors. When running TNMS-CT on a machine with such a processor, Hyper-Threading must be disabled on the BIOS Setup. Recommended software for running TNMS CT. Software

Recomme ndations

Operating Operating system system Windows Windows XP including including the latest latest Service Service Pack 3 (for TNMS CT CT Server the Professional edition is recommended) or  Windows 7 Professional 32 bits or 64 bits, including the latest Service Pack NSAP NSAP confi configur gure e Table 5 

 A50023 -K4003-X20-1-7619 -K4003-X2 0-1-7619 Issue: 1 Issue date: October 2012

OSI Stac Stack k (for (for TNMS TNMS CT Server Server OSI OSI Stack Stack is is recomme recommended nded))

Software recommendations for TNMS CT

23

Installation

User Manual (UMN)

Softw are

Web Brow Browse serr

The Onlin Online e Help Help requi require res s the the Int Inter ernet net Expl Explor orer er Web Brow Browse ser. r. It is recommended using the Internet Explorer Explorer included with the Service Pack updates: IE6 for XP SP3 or IE8 for Windows 7 Professional.

PDF Reade r

Acro ba bat Reader 6 or late r. r. (a PDF reader is required to access the TNMS CT User Manual)

Table 5 

3.2. 3.2.3 3

Recomme ndations

Software recommendations for TNMS CT (Cont.)

Inst Instal alla lati tion on Soft Softwa warre  All recomm ended software s oftware parts pa rts must be released for the appropriate ap propriate TNMS CT software version. This holds for the initial installation installation and for service o r 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 T NMS CT release documentation. More information on the installation sequence is provided in Chp. 3.2.5 3.2.5.. 1.

2.

3.

24

Installation Installation instructions for the operating system are provided in Chp. 3.3 3.3,, however, pre-installed pre-installed machines can also be used. 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 included with Windows XP Professional or Windows 7 Professional, however, it is not enabled by default and therefore must be configured manually. More information on how to enable this service is available in Chp.3.3.4 Chp.3.3.4.. TNMS CT: This installation contains the following software components for installation: installation:  –  Integrated TNMS CT software installation package: This installation program 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 3.5.2..  Additionally  Addition ally to the TNM S CT installation, installatio n, the following follow ing 3rd-party 3rd-par ty software softwa re components 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 environment for the Java b ased applications.  –  OSI stack: The OSI stack software must be installed on Server PC before the Server

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manu al (U MN)

Installation

 – 

software itself. More information on installing the OSI stack is provided in Chp. 3.4.1.. 3.4.1  Acrobat Reader: Re ader:  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 3.4.2..

Software DVD Overview

The 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 de liverable DVD-ROM:  – 

 – 

 – 

3.2. 3.2.4 4

TNMS CT CT application SW, element manager applications, NECs, NECs, OSI stack, JRE, Acrobat Reader  OEM SW for FSP equipment Customer Documentation User Manual

Inst Instal alla lati tion on and and Cab Cabli ling ng Before installing the operating system, the following steps should be com pleted:  – 

 – 

 – 

3.2. 3.2.5 5

g

The Client and Server machines should be set up and cabled in accordance with the project-specific project-specific installation installation documents s upplied. The applicable recommendations for screen-based workstations should be observed. To guarantee 24-hour operation, an un interrupted interrupted power supply must be available.

Inst Instal alla lati tion on Sequ Sequen enc ce 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: 3.2.4.. 1. Set up and cable, as described in Chp. 3.2.4 hardware components, and configure the 2. Install the operating system and a dditional hardware system under Windows OS as described in Chp. 3.3 3.3.. 3. Install FTP service on the Server machine as d escribed in Chp.3.3.4 Chp.3.3.4.. 4. Install the OSI stack on the Server machine as described in Chp. 3.4.1 3.4.1.. 5. Install Acrobat Reader as described in Chp. 3.4.2 3.4.2.. 6. Install the TNMS CT software components on the corresponding machines as described in Chp. 3.5.2 3.5.2::  –  TNMS CT Client  –  TNMS CT Server   –  TNMS CT EML Packages  Addition al TNMS softwa re, such as optional EML E ML packages. pac kages.  –   Additional 7. Configure the TNMS CT components and connect network elements as described in Chp. 3.6.4 3.6.4..

 A50023 -K4003-X20-1-7619 -K4003-X2 0-1-7619 Issue: 1 Issue date: October 2012

25

Installation

User Manual (UMN)

8.

26

Perform system testing in accordance with the test cases described in the acceptance test protocol. For more information, contact Nokia Siemens Networks Technical Sales.

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

3.3

Installation

Installing the Operating System This Chapter describes the recommend procedures to prepare the Windows OS for running TNMS CT software platform.

g 3.3.1

Follow the mandatory installation sequence for all software parts as described in Chp. 3.2.5.

Before you Begin Before 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 c ertain UniGATE NEs. Determine the file system to be used. If you wish to p re-install a SCSI RAID system, make sure the TNMS CT h ard 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 an d files prior to an initial installation of the OS. This does not a pply 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 compressed 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/Windows 7 Setup tries to identify the devices at the serial interfaces automatically and therefore a connection to an UPS is not advisable.

Licensing Information

During installation, the system license number is requested. This is provided on the back cover of the Windows CD. Protocol Information

TCP/IP is the standard network protocol used by Windows OS based Server. However, if you wish, you are free to use other protocols and the corresponding network adapters. For TCP/IP you will need one IP address for 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 en able this service, a DHCP server is required.

IP addresses are provided in the form of numbers but you can also assign a nam e to a server IP address using what is known as name resolution. This enables user access

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

27

Installation

User Manual (UMN)

using server names instead of IP a ddresses which can be difficult to remember. The main name resolution methods are: Domain name assignment methods:  – 

 – 

3.3.2

DNS (Domain Naming Service) :

DNS is a distributed Internet directory service that is used mostly to translate between domain names (server hosts) an d IP addresses. It facilitates name resolution for clients under Windows OS. WINS (Windows Internet Naming Service) : WINS facilitates name resolution for clients running Windows NT and older Microsoft operating systems.

Installing Windows OS Prior 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 mu st also be installed:  –   – 

Service Pack 3 (SP3) when using Windows XP Latest Service Pack when using Windows 7

It is highly recommended that available security patches for Windows are also installed.

g 3.3.3

Before installing Windows 7, please note that the Aero user interface mode is not supported.

Hardware Configuration Once 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 Card

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

g

Before opening the antistatic envelope, make sure you are familiar with the regulations for electrostatic-sensitive devices (ESD) provided in Chp. 3.1.  –   –   –   –   – 

28

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.

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Installation

 – 

 – 

Install suitable drivers by double-clicking the Setup.exe file on the floppy disk supplied. 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 Configuration This section describes how to enable or disable the required services for each the supported 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 Client  under Windows 7 Professional :  • Disable User Account Control (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  2. 3.

 Add or Remove Programs window

Select the Add/Remove Windows Components. Select Internet Information Services (IIS), then click the Details button.

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

29

Installation

User Manual (UMN)

Figure 7  4. 5.

Windows Components Wizard and IIS dialogs

Select the FTP Service check-box and click OK. Click OK  to close all dialog boxes.

Enable FTP Service (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  2. 3.

30

Programs and Features window

Select the Turn Windows feature on or off . Expand the Internet Information Services and the FTP Publishing Service tree node.

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Installation

Figure 9 4. 5.

Windows Features dialog

Select the FTP Server  check-box and click OK. Wait a couple of m inutes while the feature is configured.

Disable User Account Control (Windows 7)

Complete the following steps to disable the User Account Control: 1.

2.

3.4

In Windows 7, proceed as the following: 1.1 Locate the Action Center  in Control Panel  -> System and Security . 1.2 Select the Change User Ac count Control settings . 1.3 In Choose when to be notified about changes to your computer , move the slider all way down to Never Notify and click OK. For the changes to take effect you will need to reboot.

Installing 3rd-Party Software This chapter provides an overview of the additional software installations needed to run TNMS CT correctly. The described installations include:  – 

 –   – 

g 3.4.1

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)

Follow the mandatory installation sequence for all software parts as described in Chp. 3.2.5.

Installing an OSI Stack  An 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.

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

31

Installation

User Manual (UMN)

See Step 5. for the possibilities to set up the NSAP address. To install an OSI stack, proceed as follows: 1.

2. 3.

To install an OSI stack, double-click the setup.exe file in the OsiStack directory on the TNMS CT software DVD.  A welcome window is displayed. Press Next to continue. In the Choose Destination Location  window, a default installation directory is offered for the OSI stack. Press Next to continue.

Figure 10  4.

32

Setup OSI Stack: Choose Destination Location

The How to set NSAP address  dialog is displayed (Figure 11), please select the appropriate option according to your company’s network management. Mo re information about each option available in step 5.

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Installation

Figure 11 5.

Setup OSI Stack: How to set NSAP address

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.  After pressing Next, the Getting NSAP window is shown. See Figure 12. Enter the provided NSAP address and press Next.

Figure 12   – 

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

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

33

Installation

User Manual (UMN)

your system administrator didn’t provide you with an NSAP address.  After pressing Next, the Getting NSAP window is opened. See Figure 13. To obtain the MAC address of your PC open a DOS shell and enter the command ip config /all The response provides you with IP information. Copy the MAC  address from the DOS shell into the field and press Next.

Figure 13  – 

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 14 6.

34

Setup OSI Stack: NSAP derived from MAC address

Setup OSI Stack: Use a serial Line

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

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Installation

Figure 15  7.

8.

OSI Stack installation: Start Copying Files window

 A setup status window is now displayed, showing the progress of the OSI stack installation. 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  + ). Set the value for Number of Channels and Ctx to greater than/equal to “500”. This is the number of O SI stack connections which can be established simultaneously. Note the network interface card to which the O SI 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 Stack

In order to uninstall the OSI Stack, open Start -> Settings  -> Control Panel  -> Add/Remove Programs :  –   –   –   – 

3.4.2

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.

Installing Adobe Acrobat Reader  Prior to installing TNMS CT, Adobe Acrobat Reader has to be installed on the Client PC.

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

35

Installation

User Manual (UMN)

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 Rea der documentation. Uninstalling Acrobat Reader 

In order to uninstall the Acrobat Reader, open Start -> Settings  -> Control Panel -> Add/Remove Programs :  –   –   –   – 

Select the Acrobat Reader from the software list. Click the Change/Remove button. Select the Remove option. Confirm the uninstall process with Finish and restart your computer.

3.5

Installing the TNMS CT Software

g

Follow the mandatory installation sequence for all software parts as described in Chp. 3.2.5.

3.5.1

Before You Begin Before installing TNMS CT, note the following information:  – 

 – 

 – 

 –   –   – 

 – 

3.5.2

g

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 e quipped 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 mu st be logged into the Windows operating system with administrator rights.

Installing TNMS CT 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.

36

Double-click the setup.exe file provided on the TNMS CT software DVD. A w elcome window appears, press Next to continue.

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Installation

Figure 16  2.

In the Setup Type  window, select the desired mode (LCT or NCT), depending on your needs and licenses. Press Next to continue.

Figure 17 

g

TNMS CT installation: welcome screen

TNMS CT installation: choose LCT or NCT mode

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 compon ents (Client or Server) you want to install on this machine. Press Next to continue.

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

37

Installation

User Manual (UMN)

Figure 18  4. 5.

 A Setup Status window is displayed showing a registration process. In the License Agreement window, scroll down to read the complete text. Press  Yes to accept the license agreement.

Figure 19 6.

38

TNMS CT installation: choose client and/or server installation

TNMS CT installation: license agreement

In the Choose Destination Location  window, a default installation directory is offered. Press Next to continue.

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Installation

Figure 20  7.

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

Figure 21 8.

TNMS CT installation: choose installation folder 

TNMS CT installation: NE selection

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 Issue: 1 Issue date: October 2012

39

Installation

User Manual (UMN)

9.

g

 A setup status window is displayed, showing the progress of the TNMS CT installation. Various system messages are also displayed du ring this step, for example informing that LCTs are being installed. This step of the installation process may take long. You may be prompted to insert the TNMS CT software DVD to continue the installation, depending on the components y ou 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 22 

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 CT The TNMS CT software can be uninstalled using the Windows control panel. The following information is removed du ring 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. 2. 3. 4.

40

Export the configuration data to an XML file using File -> Export Configuration . Select TNMS CT from the software list and click the Change/Remove button. Store the local NSAP address  of the Server in a text file. Close all open element managers.

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Installation

5. 6.

Log off the TNMS CT software and exit. Stop the service TNMS-CT Server on the Server computer  Start -> Settings  -> Control Panel  -> Administrative Tools -> Services.

Complete the following steps to uninstall the software: 1.

2. 3. 4.

5.

6. 7.

8.

g

Open the Add/Remove Programs window using Start -> Settings  -> Control Panel -> Add/Remove Programs. In the Welcome window, press Next. In the Select Type  window do not change anything, but press Next. In the  Maintenance window, select Remove and press Next. The uninstallation starts and information windows display the software components, which are currently uninstalled. This procedure will take some minutes. The InstallShield Complete  window is displayed, informing if some folders could not be deleted. Press Finish to complete the uninstallation process. The computer is rebooted Delete any remaining folders manually using the Windows Explorer (for example: “C:\Program files\Nokia Siemens Networks\TNMS CT\”). Check that the TNMS service mentioned a bove is removed from the services list.

If the TNMS CT version initially installed required BRASS as a prerequisite, 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. The Purge tool

When uninstalling TNMS CT, the Purge tool can b e 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. 2. 3. 4. 5. 6.

Stop the service by opening Control Panel  -> Administrative Tools -> Services Double-clicking "RCTSrv " will open its property page Click Terminate Confirm that the service " TNMS-CT Server " is also terminated Close the property page by clicking the OK button Double-click the batch file " Purge.bat " out of the temporary directory. It will unregister files, remove files and directories and remove registry entries.

 After this p rocess the TNMS CT is fully removed and is installable aga in.

3.5.4

Adding and Removing Individual TNMS CT Components To install or remove individual TNMS CT components (e.g. specific EML packages), proceed as follows: 1. 2. 3. 4.

Insert the installation DVD-ROM into the DVD-ROM drive. Log off and exit TNMS CT. If necessary, close all other active applications. Stop the TNMS CT Server service on the Server computer under Start -> Settings  -> Control Panel  -> Administrative Tools -> Services.

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

41

Installation

User Manual (UMN)

5.

6. 7.

g

To change modes (LCT to NCT and vice versa) refer to section 3.5.5 before proceeding to the next step. 8.

9.

10.

11.

12.

13.

3.5.5

Start the installation/uninstallation procedure using Start -> Settings  -> Control Panel -> Add/Remove Programs . Select TNMS CT and click the Change/Remove button. In the Welcome window, press Next. In the Select Type  window choose the mode and press Next.

In the Select TNMS CT components window, the compon ents already installed are displayed. Select the components you wish to install or uninstall and press Next to continue. In the Please choose NetElements to install window, select the components you wish to install or uninstall, and press Next to continue. In the Repair TNMS CT  window, select whether you want to repair the installations of previously installed LCTs, and press Next to continue. The Setup Status  window which is now displayed indicates the progress of the procedure. 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. Restart the PC to update your installation.

Changing modes To change modes in TNMS CT (NCT to LCT or LCT to NCT) proceed as follows: 1. 2.

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.

4. 5.

g

In the Important Information  window, you are notified about the required additional licenses. In the Maintenance window, select Modify  and press Next. In the Setup Type  window, choose the com ponents you want to install on this machine. Press Next to continue. Step 5. is performed only if you selected to change mode from LCT to NCT in Step 2. Otherwise continue to Step 6.

6. 7.

42

Proceed as described in steps 1. to 6. of section 3.5.4. In the Select Type  window change from LCT mode to NCT mode or vice versa. Press Next.

Proceed as described in steps 8. to 13. of section 3.5.4.  After restarting the system import the required licences: open the License Information  window using Configuration  -> License... Click Import...  on the toolbar and select the path and file of your license XML file.

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

f

Installation

 After upgrading from LCT to NCT mode, restarting the system and importing the new required licenses, the following message may be displayed in the DCN management window for some or all NEs: “No license available for NEC” . Displayed in this context this message means that the newly installed licenses are not yet loaded in the system. If presented with such message either restart the TNMS CT server or disconnect and reconnect the NEs that display the message (tip: use the checkboxes in the DCN management window to disconnect and reconnect the server or the individual NEs).

3.6

Measures after Commissioning  After 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:  – 

 –   –   –   –   – 

3.6.1

Configuring Windows XP firewall (when using a server with Windows XP op erating system) (see Chp. 3.6.1) PPP  Dial-up setup for Q3 network elements (see Chp. 3.6.2) 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)

Configuring Windows firewall When TNMS CT server is installed, the Windows XP/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.

2.

3.

4.

Open Start -> Settings  -> Control Panel  -> Security Center  -> Windows Firewall to open the Windows Firewall  window. On the Exceptions tab, click the Add Port  and configure a TCP port with the name “TNMS CT” and the port number “2002”. Click the Choose Scope  button, select the My Network radio button and click OK to save the changes. Click OK to add the port to the exception list.

Proceed as the following to configure the Windows 7 firewall: 1.

2.

3.

4.

5.

locate the Windows Firewall  in Control Panel. In Windows 7, open Start -> Control Panel  -> System and Security  -> Windows Firewall. Change the firewall settings: In Windows 7, select Allow a program or feature through Windows Firewall. 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”. Click the Change scope button, select the My Network radio button and click OK to save the changes. Click OK to add the port to the exception list.

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

43

Installation

User Manual (UMN)

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 c ommunication 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 LC T and the NE; TCP port number “21” for FTP communication between the LC T and the NE.

For OPTRA:  •

3.6.2

TCP port number “8002” for communication with traps for SNMP.

PPP Dial-up Setup for Q3 or QSTv2 Network Elements In order to connect to a Q 3 or QSTv2 NE using RS232, complete the following steps to setup a new dial-up network connection.

g

3.6.2.1

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.

Setting a new connection 1.

44

Open Start -> Programs -> Accessories -> Communications -> Network Connections  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 Connection Wizard . Click Next to continue.

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Installation

Figure 23 2.

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

Figure 24 3.

New connection wizard: welcome screen

New connection wizard: network connection type

In the Advanced Connection Option  window select Connect directly to another computer . Click Next to continue.

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

45

Installation

User Manual (UMN)

Figure 25  4.

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

Figure 26  5.

g

46

New connection wizard: advanced connection options

New connection wizard: host or guest role

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

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Installation

Figure 27  6.

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.

Figure 28  7.

New connection wizard: connection name

New connection wizard: select a device

In the Completing the New Connection Wizard  window click Finish to complete your settings. If a connection dialog appears, cancel it.

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

47

Installation

User Manual (UMN)

Figure 29 8.

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

Figure 30  9.

48

New connection wizard complete

General connection prope rties

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

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Installation

Figure 31 10.

11.

12.

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. 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. 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 32  13.

Modem configuration

Connection properties: networking

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

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

49

Installation

User Manual (UMN)

Figure 33 14.

50

Internet protocol (TCP/IP) properties

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 con nection will still be available while your are connected via serial line. Click OK  twice to confirm your settings and return to the Connection Properties window.

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Installation

Figure 34 15.

16.

17.

 Advanced Internet protocol (TCP/IP) settings

In the Connection Properties  window select the Networking tab and click Settings  to open the PPP Settings  window. In the PPP Settings  window disable the following check boxes:  • Enable LCP extensions  • Enable software compression  • Negotiate multi-link for single link connections Click OK to confirm your settings and close all opened windows. In TNMS CT Main window open Configuration menu  -> DCN Management entry. In the DCN Management View navigate to the Serial Line Serve r -> Q3 Serial Line Channel a nd 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.

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

51

Installation

User Manual (UMN)

Figure 35 

3.6.3

QB3 channel properties

Java Runtime Environment parameters In 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 ph ysical memory must be allocated for Java Runtime through the following procedure: 1. 2.

3.

Open the Windows “Control Panel” . Open the “Java(TM) Plug-In Control Panel” window by clicking the Java Plug-In icon. 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 CT Once the TNMS CT software has be en 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 o nline help under Initial Configuration . Start TNMS CT

Start 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. Login

Log in TNMS CT using the d isplayed login dialogue or by clicking the Login  icon in the TNMS CT toolbar (see Chp. 4.3.2). When starting the TNMS CT ap plication, the Login dialog is opened automatically.

52

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Installation

Figure 36   – 

 – 

 –   – 

g

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.

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 m achine. Import licenses

Before working with TNMS CT, its components have to b e licensed. The following license types are distinguished:  – 

 – 

 – 

Basic license Each TNMS CT system requires its own license. NE license Each NEC  managed by TNMS CT requires its own license. Optional feature license In case of additionally installed optional features, further licenses are required as well.

In order to import the licenses open the License Information window using Configuration  -> 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 bee n pre-installed by Nokia Siemens Networks staff, you have been provided w ith 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.

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

53

Installation

User Manual (UMN)

Configure user accounts

 A default administrator account is created during installation. Additional accounts can now be created as required. Define log configuration settings

The 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 partition where the TNMS is installed there should be at least 1 GB free d isk space during operation. If the log file size changes (expands) check the necessary disk space again. Configure Server 

 After 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 channels

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

In 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 a re configured by completing each tab page as described in the Online Help. Setup the network map

The network map can now be set u p 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 migration 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 retries

This variable defines the number of attempts to connect to the NE via the alternative route before holding on. The default number o f attempts is three (3).

54

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Installation

 •

GNE hold on time

This 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). Further settings

Further settings can be configured depending on the individual customers needs, e.g. color settings for alarms.

3.6.5

Migration TNMS CT V3.1 supports migration of NE configuration data from UniGATE v7.0, UniGATE v7.1, SNMPv2 and SNMPv3. In order to a ccomplish 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 Adapters If one or more PCs in your TNMS CT system have multiple network adapters (for networking 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, communication can be established without any problems. But if the first IP address sent by PC B is the address for the external LAN segm ent, and a gateway PC with routing information is not available, time out cycles will result in delayed c ommunication. The following connections may then be affected: Connection

Affected Task

Client -> Server

Startin g the LCT application from a Client and communicating with NEs

Server -> Client

Starting the Client application.

Table 6 

 Affected Connections

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.

2.

3.

Right-click the icon My Network Places on your desktop. Select the item Properties from the menu. The  Network and Dial-Up Connections  window is displayed. Click on Advanced in the toolbar, and from the list that appears select Advanced Settings... The Advanced Settings  window is now displayed. In the Connections  list, select Local Area Connection . The list beneath (called Bindings for Local Area Connection) will now display the preferred order in which protocols will be used.

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

55

Installation

User Manual (UMN)

4.

5. 6.

7.

8.

3.7

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 . Repeat the procedure in step four for all of the other clients listed in the window.  After changing the settings for all of the clients listed, click on the Provider Order  tab. 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. Click OK  to save the changes and then reboot the computer.

Upgrading to a new release If you are upgrading TNMS CT to a new release, proceed as follows: 1.

2.

Stop the TNMS-CT Server  service on the Server computer: Start -> Settings -> Control Panel  -> Administrative Tools -> Services. 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  __AutoRe move.cmd  located in the Prerequisites  folder of the TNMS CT 3.00.196 or earlier installation CD.

f

For some releases, the upgrade proced ure requires specific steps additional to those described above.  Always refer to the release notes for specific information on how to perform the upgrade to a new release.

56

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Operation

4 Operation This chapter provides a guideline of h ow 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 GUI This chapter describes how to w ork 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 Characteristics In addition to the Windows g raphical user interface, the TNMS CT GUI provides some specific and useful features. Blue Frames

Control 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 displays. Data to be displayed in the window is

Initialized

Not initialized

Table 7 

4.1.2

Control Displays

Blue Frame

Data value from NE

No

 Any rated modified data value

Yes

Default value

Yes

 Any rated modified data value

Yes

Blue Framing

Working With the Mouse Both 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 nu mber 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.

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

57

Operation

User Manual (UMN)

g

The offered menus and context menus depend o n the operator’s user class.

g

Unless the text states otherwise, always use the left mouse button for clicking and double-clicking.

4.1.3

Working With the Keyboard The TNMS CT user interface is driven by con text 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  key and press the underlined letters for the menu items you want to use. For example: Main window -> Configuration menu -> Licenses... entry = +, . If there are no underlined letters visible, please press .To open a context menu you can also use +. By using the  key it is p ossible 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 Help The 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 u p Help from the menu bar, you can search for topics via the tab le 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 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 Operation In this chapter, the following basic administrative operations of TNMS CT are described:  –   –   –   –   –   –   – 

58

Starting a TNMS CT Session (see Chp. 4.2.1) Starting and Stopping TNMS CT Server (see Chp. 4.2.2)  Activating a nd 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 Issue: 1 Issue date: October 2012

User Manual (UMN)

4.2.1

Operation

Starting a TNMS CT Session The TNMS CT Client is started via Start -> Programs -> TNMS CT . Once the TNMS CT Client has been started, the operator can en ter 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.

f

Each TNMS CT Server supports one client connection at a given time. When a second client tries to login to the same server the following message is displayed: “Login Failed: Concurrent login limit (1 u ser) reached"

4.2.2

Starting and Stopping TNMS CT Server  TNMS 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 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 -> Services.

4.2.3

Activating and deactivating TNMS CT Server   A TNMS CT Server and each DCN ob ject managed by the Server can have the activation 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 Zone TNMS CT allows to switch between local time, GMT  and CST via the menu bar entry View -> Time D isplay in the Client application.

4.2.5

Starting Element Manager Applications The 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 Access TNMS 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.

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

59

Operation

User Manual (UMN)

4.2.7

Terminating a TNMS CT Session  A 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 Interface This 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 o perator’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 37 shows an example of the TNMS CT main window indicating some of the available functions.

Figure 37 

60

TNMS CT graphical user interface

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

4.3.1

Operation

Menu Bar   Figure 38 shows the menu b ar 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 38 

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 l ayout 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 S tyle

Toggl e between the foll owi ng styles for the cur rently 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

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

61

Operation

User Manual (UMN)

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 notification. NCT mode only!

Configuration

Configuring Various Tasks

DCN Management...

Work in the DCN Management View .

Serial Line...

Work in the Serial Line View .

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

Bac kground...

A ssign a background bi tmap to your network map or set the background color. NCT mode only!

Security

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

Table 8 

62

Security and User Management

Working With Tools

Menu Bar Entries (Cont.)

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Operation

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.

Til e Hori zontally

Di splay al l the currently open windows next to each other.

Tile Vertically

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

 Arrange Icons

Rearrange the icons inside the main window.

1 Network Management View 2 System Message Log

List of all t he currently open windows in the form of s equentially-numbered menu items. The selected window (in the foreground) is indicated by a tick.

Working With the Online Help .

Help

Help Topics...

Open the Online Help.

On Window...

Open the Online Help on the currently selected window .

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

4.3.2

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

Icon

Function

Log on or log off the TNMS CT Server.

Menu Entry Security  menu -> Login... entry

Opens Window Login

Security  menu -> Logoff...  entry

Work with the Serial Line View .

Configuration  menu -> Serial Line...

Serial Line View

entry

Table 9

Work with the DCN Management View. Configuration  menu -> DCN Management... 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

Main Toolbar Icons

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

63

Operation

User Manual (UMN)

4.3.3

Status Bar  The status bar (see Figure 39) runs along the bo ttom of the main window. It gives information on the operating states and displays important messages, such as alarms, in short form.

Figure 39

Status Bar 

Table 10 describes the TNMS CT status bar from left to right. 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. indeterminate, 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 transactions (red).

Table 10 

4.3.4

Status Bar Components

Network View The Network View provides graphical representation of your network. Figure 40 shows an example of a network map indicating objects with context menus (ovals) and other objects (rectangles).

64

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Operation

Figure 40 

Network View

Orientation within the Network View can be improved by using a b ackground 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

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

65

Operation

User Manual (UMN)

 Acknowledge All  Access Control

Acknowledge all NE alarms displayed in TNMS-CT. This option does not apply to the alarms displayed in the opened LCT. 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.

B ackground...

As sign 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

66

Network View Context Menus (Cont.)

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Operation

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!

B ackground...

Assign a background bitmap to y our network map or set the background color. NCT mode only!

Table 11

Network View Context Menus (Cont.)

4.3.5

Serial Line View The Serial Line View provides graphical representation of your serial line con nection. Figure 41 shows an example of the network map indicating objects with context menus.

Figure 41

Serial Line View

Each item of the Serial Line View  offers an individual context menu as shown in Table 11. NE

Connect

Connect to a network element, which is clearly identifiable, v ia the serial line interface.

 Automatic Connection

Connect to a network element via the serial line interface. TNMS CT tests all channels until it can establish a suitable connection.

Table 12 

Serial Line View Context Menus

4.3.6

DCN Management View This 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.

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

67

Operation

User Manual (UMN)

 – 

TNMS CT Server allows to configure DCN channels an d network elements for local and remote connections via Ethernet/DCC.

The managed DCN objects are displayed in their current connection state and h ierarchical relation in a tree. Figure 42 below gives an example of the DCN Management View .

Figure 42 

4.3.6.1

DCN Management View

DCN Management Toolbar  The DCN Management toolbar (see Figure 43) runs along the top edge of the DCN Management 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 43

DCN Management Toolbar 

The functions of the DCN Management toolbar buttons are briefly described in Table 13. Icon

Function

Context Menu Entry

Find an NE in the DCN Management tree.

Table 13

68

Opens Window 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

DCN Management Toolbar Icons

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Operation

Icon

Function

Display the properties of the selected DCN object.

Context Menu Entry Properties... entry

Opens Window Properties

Store the complete DCN tree in SDF format.

Print the complete DCN tree.

Table 13

4.3.6.2

Close the DCN Management View .

Network View

Open the Online Help.

Online Help

DCN Management Toolbar Icons (Cont.)

DCN Management Tree Each DCN object provides the same sort of context menu. Table 14 shows and briefly explains the generic context menu entries.

DCN Object

New...

Add a subcomponent to the selected DCN object. If a channel or NE is added, a lis t 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

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

69

 Abbreviations

User Manual (UMN)

5 Abbreviations BCM BSHR

Bidirectional Self-Healing Ring

CC

Cross Connection

CE

Communauté Européenne

CDM CORBA CST CT DAT DB

Cross Domain Manager  Common Object Request Broker Architecture Central Standard Time Craft Terminal Digital Audio Tape Database

DCC

Data Communication Channel

DCN

Data Communication Network

EM EML EM-OS

Element Manager  Element Management Layer  Element Manager Operations System

EMS

Element Management System

ESCON

Enterprise System Connection

ESD

Electrostatic-Sensitive Devices

FCAPS FICON FTP

Fault Configuration Accounting Performance Security Fiber Connection File Transfer Protocol

GBE

Gigabit Ethernet

GMT

Greenwich Mean Time

GNE

Gateway Network Element

GUI

Graphical User Interface

IMN

Installation Manual

ITU-T LAN LCAS LCT

70

Border Crossing Mode

International Telecommunications Union - Telecommunications Standard Sector  Local Area Network Link Capacity Adjustment Scheme Local Craft Terminal

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

MAC MDAC MIB MS

Abbreviations

Media Access Control Microsoft Data Access Components Management Information Base Microsoft

MSP

Multiplex Section Protection

NCT

Network Craft Terminal

NE

Network Element

NML

Network Management Layer 

NEC

Network Element Controller 

NSAP OGL OLEDB/ADO OSI OSPF OTH PC PCI

Network Service Access Point Operator Guidelines Object Linking and Embedding Database/Active X Data Objects Open System Interconnection Open Shortest Path First Optical Transport Hierarchy Personal Computer  Peripheral Component Interconnect

PDF

Portable Document Format

PDH

Plesiochronous Digital Hierarchy

PLET PM

Performance Log Export Tool Performance Measurement

PMP

Performance Measurement Point

PPP

Point-to-Point Protocol

RAID SAN SCSI DAT

Redundancy Array of Independent Disks Storage Area Network 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

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

71

 Abbreviations

User Manual (UMN)

SSL

Secure Sockets Layer 

TCM

Tandem Connection Monitoring

TCN

Threshold Crossing Notification

TCOA TCOI

TMF CORBA Interface

TCOM

TMF CORBA Manager

TCP/IP TED TIF

Transmission Control Protocol/Internet Protocol Technical Description Telemetry Interface

TMF

Telecommunication Management Forum

TMN

Telecommunication Management Network

TMS

Telecommunication Management System

TNMS TP TSF

Telecommunication Network Management System Termination Point Tab Separated Format

UHC

Ultra-High Capacity

UNO

Universal Network Object

UPS

Uninterruptible Power Supply

WAN

Wide Area Network

WDM

Wavelength Division M ultiplexing

XML

72

TMF CORBA Agent

Extended Markup Language

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

User Manual (UMN)

Index PDF 7

Symbols Gateway NE see GNE 15 GUI see ’Graphical User Interface’ 13

A  Access control 66  Acknowledge 62, 66  Add NetServer 69  Adobe Acrobat Reader 35  Alarm 65 Filter 62 List 62, 65 List and Log 17, 61 Log 62, 65 Statistics 18, 65  Antistatic mat 22  Application Settings 62  Architecture Client/Server 11 Network 9 Software 12 System 11  Automatic recognition 17  Automatic topology discovery 16

B Background bitmap 62, 66, 67 Basic information Personnel requirements 21 Blue frame 57 Broadcast user configuration 63

DCN 9 Channel 54, 67 Management 16, 17, 54, 59, 62, 67 NE 67 Object 59, 69 Object Properties 69 DCN channel DCN management 15 DCN Management Tree 69 Deactivate 69 Delete 69 Delivery 22 Dial-up connection 44 Discover topology 16 Duplicate 69

E Electrostatic-sensitive devices 22 Element manager 13, 65 Start 59 Start offline 63 EML packages 13, 24 Installation 41 ESD symbol 22 Exit application 61 Export 13, 61

F Fault Management 17, 62 Settings 62 File transfer 65 Find 61, 66, 67 FSP 24

G GNE 54 DCN management 15 Graphical User Interface 13, 60 Grounding bracelet 22

C CE conformity 21 Client components 12 Client/Server architecture 11 Communication Interface 16 Loss 17 Context Menu 57, 58 Context menu 57, 58 Copy NE name into ID name 69

D Date and time settings 59, 61

 A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012

I Icon 63, 66, 67, 68 Import 13, 61 Initial configuration 52 Installation  Adobe Acrobat Reader 35 Individual components 41 PCI I/O card 28 TNMS CT 36 Installation software EML packages 24 JavaSoft JAVA Runtime Environment 24

73

User Manual (UMN)

K Keyboard 58

L LCT mode 14 Licensing 62 Import 53 Software 20 Links 14, 65, 67 Lock 66, 67 Log management 18, 54 Login 52, 59, 62, 63

M MAC address 33 Measuring equipment 22 Menu bar 61 Migration 55 Mouse 57, 58 Multiple network adapters 55

N NCT mode 14 NE 14, 54, 65, 67  Automatic connection 67 Connect 62, 66, 67 Controller 13 Disconnect 62, 66 Element manager 13 Properties 66 Supported 10 NetServer 67 Frame 13 Network  Architecture 9 Interface 16 Management 14, 15 Map 54 Network element DCN management 15 Network interface 16 Network map 66 Network View 54, 64, 65 NSAP address 33

O Online Help 58, 63, 69 Open transactions 61, 64

P

Port connection 15, 61, 65, 66 Port connection list 61, 65, 66 Print 61, 63, 69

Q Q3 16 QD2 16 QST 16 QSTV2 16

R Release 66 Remote login 18 Request 66 Resynchronization 66 Routing settings 55

S Safety precautions Electrostatic-sensitive devices 22 Save 61 Scaled start-up 16 Screen level integration 19 Security 62 Log 18 Settings 62 Serial line interface 16 Serial Line View 62, 67 Server 13, 59, 62, 63, 67  Activate 59 Configuration 54 DCN management 15 SNMP 16 Software architecture 12 Start application 52, 59 Status bar 62, 64 Stop application 60, 61 Structure Network 9 Subnetwork DCN management 15 Supplementary documentation Delivery notes 20 Field test protocols 20 Protocols 20 System information 63 System Message Log 61 Settings 62

T Telegram protocol 16

Password 62 PCI I/O card 28

74

A50023-K4003-X20-1-7619 Issue: 1 Issue date: October 2012