2
2 AA5500002233--KK44000033--XX2200--11--77661199
Issue: 1
Issue: 1 Issue date: Issue date: October October 20122012 User Manual (UMN) User Manual (UMN)
The information in this document is subject to
The information in this document is subject to change without notice and describes only thechange without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for 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 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 the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior
in any form or means without the prior written permission of Nokia Siemens Networks. Thewritten permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly
documentation has been prepared to be used by professional and properly trained personnel,trained personnel, and the customer assumes full re
and the customer assumes full re sponsibility when using it. Nokia Siemens Networks welcomessponsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the customer comments as part of the process of continuous development and improvement of the documentation.
documentation.
The information or statements given in this do
The information or statements given in this do cumentation concerning the suitability, capacity,cumentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" a
or performance of the mentioned hardware or software products are given "as is" a nd all liabilitynd all liability arising in connection with such hardware or software products shall be defined conclusively and arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agr
finally in a separate agreement between Nokia Siemens Networks and the customer. However,eement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructionsto ensure that the instructions contained in the document are adequate and free of material er
contained in the document are adequate and free of material er rors and omissions. Nokiarors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues whichSiemens Networks, explain issues which may not be covered by the document.
may not be covered by the document. Nokia Siemens Networks will correct error
Nokia Siemens Networks will correct error s in this documentation as soon as possible. IN s in this documentation as soon as possible. IN NONO EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR E
EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR E RRORS IN THIS DOCUMEN-RRORS IN THIS DOCUMEN-TATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, TATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES,
INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOTSUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.
THE INFORMATION IN IT.
This documentation and the product it describes ar
This documentation and the product it describes ar e considered protected by copyrights ande considered protected by copyrights and other intellectual property rights accord
other intellectual property rights accord ing to the applicable laws.ing to the applicable laws. The wave logo is a trademark of Nokia
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trSiemens Networks Oy. Nokia is a registered tr ademarkademark of Nokia Corporation. Siemens is a registered
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.trademark of Siemens AG. Other product names mentioned in this document may be trademarks
Other product names mentioned in this document may be trademarks of their respectiveof their respective owners, and they are mentioned for identification purposes only.
owners, and they are mentioned for identification purposes only. Copyright © Nokia Siemens Networks 2012. All rights re
Copyright © Nokia Siemens Networks 2012. All rights re served.served.
f
f
Important Notice on Product Safety
Important Notice on Product Safety
This product may present safety risks due to laser, electricity, heat, and other sources This product may present safety risks due to laser, electricity, heat, and other sources of danger.
of danger.
Only trained and qualified personnel may install,
Only trained and qualified personnel may install, operate, maintain or otherwise handleoperate, maintain or otherwise handle this product and only after having carefully
this product and only after having carefully read the safety information applicable to thisread the safety information applicable to this product.
product.
The safety information is provided in
The safety information is provided in the Safety Information section in the “Legal, Safetythe Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.
and Environmental Information” part of this document or documentation set.
The same text in German: The same text in German:
f
f
Wichtiger Hinweis zur
Wichtiger Hinweis zur Produkts
Produktsicherheit
icherheit
Von diesem Produkt können Gefahren durch Laser, EleVon diesem Produkt können Gefahren durch Laser, Ele ktrizität, Hitzeentwicklung oderktrizität, Hitzeentwicklung oder andere Gefahrenquellen ausgehen.
andere Gefahrenquellen ausgehen.
Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur dur Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur dur chch geschultes und qualifiziertes Personal unter Be
geschultes und qualifiziertes Personal unter Be achtung der anwendbaren Sicherheits-achtung der anwendbaren Sicherheits-anforderungen erfolgen.
anforderungen erfolgen.
Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ i
Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ i m Teil „Legal,m Teil „Legal, Safety and Environmental Information“ dieses Dokuments oder dieses Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentations-satzes.
User Manual (UMN) User Manual (UMN)
The information in this document is subject to
The information in this document is subject to change without notice and describes only thechange without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for 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 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 the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior
in any form or means without the prior written permission of Nokia Siemens Networks. Thewritten permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly
documentation has been prepared to be used by professional and properly trained personnel,trained personnel, and the customer assumes full re
and the customer assumes full re sponsibility when using it. Nokia Siemens Networks welcomessponsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the customer comments as part of the process of continuous development and improvement of the documentation.
documentation.
The information or statements given in this do
The information or statements given in this do cumentation concerning the suitability, capacity,cumentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" a
or performance of the mentioned hardware or software products are given "as is" a nd all liabilitynd all liability arising in connection with such hardware or software products shall be defined conclusively and arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agr
finally in a separate agreement between Nokia Siemens Networks and the customer. However,eement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructionsto ensure that the instructions contained in the document are adequate and free of material er
contained in the document are adequate and free of material er rors and omissions. Nokiarors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues whichSiemens Networks, explain issues which may not be covered by the document.
may not be covered by the document. Nokia Siemens Networks will correct error
Nokia Siemens Networks will correct error s in this documentation as soon as possible. IN s in this documentation as soon as possible. IN NONO EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR E
EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR E RRORS IN THIS DOCUMEN-RRORS IN THIS DOCUMEN-TATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, TATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES,
INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOTSUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.
THE INFORMATION IN IT.
This documentation and the product it describes ar
This documentation and the product it describes ar e considered protected by copyrights ande considered protected by copyrights and other intellectual property rights accord
other intellectual property rights accord ing to the applicable laws.ing to the applicable laws. The wave logo is a trademark of Nokia
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trSiemens Networks Oy. Nokia is a registered tr ademarkademark of Nokia Corporation. Siemens is a registered
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.trademark of Siemens AG. Other product names mentioned in this document may be trademarks
Other product names mentioned in this document may be trademarks of their respectiveof their respective owners, and they are mentioned for identification purposes only.
owners, and they are mentioned for identification purposes only. Copyright © Nokia Siemens Networks 2012. All rights re
Copyright © Nokia Siemens Networks 2012. All rights re served.served.
f
f
Important Notice on Product Safety
Important Notice on Product Safety
This product may present safety risks due to laser, electricity, heat, and other sources This product may present safety risks due to laser, electricity, heat, and other sources of danger.
of danger.
Only trained and qualified personnel may install,
Only trained and qualified personnel may install, operate, maintain or otherwise handleoperate, maintain or otherwise handle this product and only after having carefully
this product and only after having carefully read the safety information applicable to thisread the safety information applicable to this product.
product.
The safety information is provided in
The safety information is provided in the Safety Information section in the “Legal, Safetythe Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.
and Environmental Information” part of this document or documentation set.
The same text in German: The same text in German:
f
f
Wichtiger Hinweis zur
Wichtiger Hinweis zur Produkts
Produktsicherheit
icherheit
Von diesem Produkt können Gefahren durch Laser, EleVon diesem Produkt können Gefahren durch Laser, Ele ktrizität, Hitzeentwicklung oderktrizität, Hitzeentwicklung oder andere Gefahrenquellen ausgehen.
andere Gefahrenquellen ausgehen.
Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur dur Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur dur chch geschultes und qualifiziertes Personal unter Be
geschultes und qualifiziertes Personal unter Be achtung der anwendbaren Sicherheits-achtung der anwendbaren Sicherheits-anforderungen erfolgen.
anforderungen erfolgen.
Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ i
Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ i m Teil „Legal,m Teil „Legal, Safety and Environmental Information“ dieses Dokuments oder dieses Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentations-satzes.
A50023
A50023-K4003-X2-K4003-X20-1-76190-1-7619
Issue: 1 Issue date: October 2012 Issue: 1 Issue date: October 2012
3 3 User Manual (UMN)
User Manual (UMN)
Table of Contents
Table of Contents
This document has 75 pages. This document has 75 pages. 1 1 IInnttrroodduuccttoorry y NNootteess. . . 77 1. 1.11 IIntnteendnded ed aaududiienencece. . . 77 1. 1.22 SStrtrucuctturure oe of tf thihis ds dococumumenent. . t. . . 77 1. 1.33 SSymymbobols ls anand cd cononveventntiionons . . s . . . 88 1. 1.44 FFururthther er dodocucummenenttaatitioon. . n. . . 88 2 2 IInnffoorrmmaattiioon. . n. . . 99 2. 2.11 NeNettwowork rk ArArchchititecectuture re . . . 99 2. 2.1.1.11 SSupuppoportrted ed NENEs s . . . 1010 2. 2.22 SSysystetem Am Arrchchiitetectcturure. . e. . . 1111 2. 2.2.2.11 HaHardrdwaware re CoCompmpononenents . . ts . . . 1212 2. 2.2.2.22 SSofoftwtwarare Ce Comompoponenentntss. . . 1212 2.22.2.2..2.11 TNTNMS MS CT CT CliClient. ent. . . 1212
2. 2.2.2.2.2.22 TNTNMS MS CT CT SeServrverer. . . 1313 2. 2.33 FFununctctiiononal al OvOverervvieiew w . . . 1414 2. 2.3.3.11 LCLCT aT and nd NCNCT MT Mododes. . es. . . 1414 2. 2.3.3.22 NeNettwowork rk MaMananagegemement . nt . . . 1414 2. 2.3.3.33 DCDCN N MaMananagegemement. . nt. . . 1515 2. 2.3.3.44 CoCommmmununicicatatioion In Intntererffacaces. . . es. . . 1616 2. 2.3.3.55 TeTelelegrgram am PrPrototococolols . . s . . . 1616 2. 2.3.3.66 SScacaleled Sd Statartrt--up up . . . 1616 2. 2.3.3.77 AAututomomatatiic Tc Topopolologogy Dy Disiscocovevery ry . . . 1616 2. 2.3.3.88 AAututomomatatiic Rc Rececogogninitition. . on. . . 1717 2. 2.3.3.99 FFauault lt MaMananagegemement. . nt. . . 1717 2.
2.3.3.1010 UsUser er MaMananagemgement ent anand Sd Sececururitity y . . . 1818
2.
2.3.3.1111 ReRemotmote Le Logiogin n . . . 1818
2. 2.3.3.1212 LoLog Mg Manaanagegemement. . . nt. . . 1818 2. 2.3.3.1313 ScScrereen en LeLevevel Il Intntegegraratition . . . on . . . 1919 2. 2.3.3.1414 PrPrioiorirityty/M/Mututablable Ee Exclxclususioion . . n . . . 1919 3 3 IInnssttaallllatatiion on . . . 2200 3. 3.11 PPrrototecectitive ve MeMeasasurures es anand Hd Hanandldliing . ng . . . 2121 3. 3.1.1.11 SSafafetety Py Prerecacaututiionons Ws Whehen tn the he UnUnit it iis Os Opepen n . . . 2121 3.
3.1.1.22 PrPrototecectition on agagaiainsnst Et Excexcessssivive Ce Conontatact ct VoVoltltageages. s. . . 2121
3. 3.1.1.33 HaHandndllining Mg Mododulules . . . es . . . 2222 3. 3.22 PPrerepapariring ng ffor or InInststalallalattioion . . n . . . 2222 3. 3.2.2.11 CoCompmpononenent Dt Deleliviverery y . . . 2222 3. 3.2.2.22 HaHardrdwaware re anand Sd Sofoftwtwarare Re Rececomommemendndatatioions . . . ns . . . 2323 3. 3.2.2.33 IInsnstatallllatatiion on SoSoftftwawarre e . . . 2424 3. 3.2.2.44 IInsnstatallllatatiion on anand Cd Cabablliningg . . . 2525 3. 3.2.2.55 IInsnstatallllatatiion on SeSeququenence ce . . . 2525 3. 3.33 IInsnstatallllining tg the he OpOpereraattining g SySyststem. em. . . 2277 3. 3.3.3.11 BBefeforore ye you ou BBegegiinn. . . 2727 3. 3.3.3.22 IInsnstatallllining Wg Wiindndowows Os OS. . . S. . . 2828 3. 3.3.3.33 HaHardrdwaware re CoConfnfiiguguraratition. . on. . . 2828
User Manual (UMN)
3.3.4 Windows Services Configuration . . . 29
3.4 Installing 3rd-Party Software. . . 31
3.4.1 Installing an OSI Stack . . . 31
3.4.2 Installing Adobe Acrobat Reader . . . 35
3.5 Installing the TNMS CT Software . . . 36
3.5.1 Before You Begin . . . 36
3.5.2 Installing TNMS CT. . . 36
3.5.3 Uninstalling TNMS CT . . . 40
3.5.4 Adding and Removing Individual TNMS CT Components . . . 41
3.5.5 Changing modes. . . 42
3.6 Measures after Commissioning . . . 43
3.6.1 Configuring Windows firewall . . . 43
3.6.2 PPP Dial-up Setup for Q3 or QSTv2 Network Elements . . . 44
3.6.2.1 Setting a new connection . . . 44
3.6.3 Java Runtime Environment parameters . . . 52
3.6.4 Initial Configuration of TNMS CT . . . 52
3.6.5 Migration . . . 55
3.6.6 Routing Settings for PCs with Multiple Network Adapters . . . 55
3.7 Upgrading to a new release . . . 56
4 Operation . . . 57
4.1 Working With the GUI . . . 57
4.1.1 TNMS CT Characteristics . . . 57
4.1.2 Working With the Mouse. . . 57
4.1.3 Working With the Keyboard . . . 58
4.1.4 Working With the Online Help. . . 58
4.2 Basic Operation . . . 58
4.2.1 Starting a TNMS CT Session . . . 59
4.2.2 Starting and Stopping TNMS CT Server. . . 59
4.2.3 Activating and deactivating TNMS CT Server. . . 59
4.2.4 Setting Date and Time Zone. . . 59
4.2.5 Starting Element Manager Applications . . . 59
4.2.6 Administrating NE Write Access . . . 59
4.2.7 Terminating a TNMS CT Session . . . 60
4.3 Graphical User Interface. . . 60
4.3.1 Menu Bar . . . 61
4.3.2 Toolbar . . . 63
4.3.3 Status Bar . . . 64
4.3.4 Network View . . . 64
4.3.5 Serial Line View . . . 67
4.3.6 DCN Management View . . . 67
4.3.6.1 DCN Management Toolbar . . . 68
4.3.6.2 DCN Management Tree . . . 69
5 Abbreviations . . . 70
A50023-K4003-X20-1-7619
Issue: 1 Issue date: October 2012
5 User Manual (UMN)
List of Figures
Figure 1 General Structure of a TNMS CT Network . . . 10
Figure 2 System Architecture. . . 11
Figure 3 Overview of Software Components . . . 12
Figure 4 A GNE detecting its managed NEs . . . 16
Figure 5 Labelling of electrostatic-sensitive devices (ESD symbol). . . 22
Figure 6 Add or Remove Programs window . . . 29
Figure 7 Windows Components Wizard and IIS dialogs . . . 30
Figure 8 Programs and Features window . . . 30
Figure 9 Windows Features dialog. . . 31
Figure 10 Setup OSI Stack: Choose Destination Location . . . 32
Figure 11 Setup OSI Stack: How to set NSAP address. . . 33
Figure 12 Setup OSI Stack: Company with own NSAP management . . . 33
Figure 13 Setup OSI Stack: NSAP derived from MAC address. . . 34
Figure 14 Setup OSI Stack: Use a serial Line . . . 34
Figure 15 OSI Stack installation: Start Copying Files window . . . 35
Figure 16 TNMS CT installation: welcome screen . . . 37
Figure 17 TNMS CT installation: choose LCT or NCT mode. . . 37
Figure 18 TNMS CT installation: choose client and/or server installation . . . 38
Figure 19 TNMS CT installation: license agreement . . . 38
Figure 20 TNMS CT installation: choose installation folder . . . 39
Figure 21 TNMS CT installation: NE selection. . . 39
Figure 22 TNMS CT installation: installation complete . . . 40
Figure 23 New connection wizard: welcome screen . . . 45
Figure 24 New connection wizard: network connection type . . . 45
Figure 25 New connection wizard: advanced connection options . . . 46
Figure 26 New connection wizard: host or guest role . . . 46
Figure 27 New connection wizard: connection name. . . 47
Figure 28 New connection wizard: select a device . . . 47
Figure 29 New connection wizard complete . . . 48
Figure 30 General connection properties. . . 48
Figure 31 Modem configuration . . . 49
Figure 32 Connection properties: networking . . . 49
Figure 33 Internet protocol (TCP/IP) properties . . . 50
Figure 34 Advanced Internet protocol (TCP/IP) settings . . . 51
Figure 35 QB3 channel properties . . . 52
Figure 36 TNMS CT login window . . . 53
Figure 37 TNMS CT graphical user interface. . . 60
Figure 38 Menu bar . . . 61
Figure 39 Status Bar . . . 64
Figure 40 Network View . . . 65
Figure 41 Serial Line View . . . 67
Figure 42 DCN Management View . . . 68
User Manual (UMN)
List of Tables
Table 1 Symbols . . . 8
Table 2 Conventions . . . 8
Table 3 Supported NEs . . . 10
Table 4 Hardware recommendations for TNMS CT . . . 23
Table 5 Software recommendations for TNMS CT . . . 23
Table 6 Affected Connections . . . 55
Table 7 Blue Framing . . . 57
Table 8 Menu Bar Entries . . . 61
Table 9 Main Toolbar Icons . . . 63
Table 10 Status Bar Components . . . 64
Table 11 Network View Context Menus . . . 65
Table 12 Serial Line View Context Menus . . . 67
Table 13 DCN Management Toolbar Icons . . . 68
A50023-K4003-X20-1-7619
Issue: 1 Issue date: October 2012
7
UserManual(UMN) IntroductoryNotes
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
• 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).
g
Some features described in this documentation may not be available. In order to identify the features released for the product, please refer to the Release Notes delivered together with the product.The User Manual is also provided as file under theHelp menu. This file can be viewed and printed using Adobe Acrobat Reader.
User Manual (UMN) Introductory Notes
1.3
Symbols and conventions
The following symbols are used in this docum ent:
The following conventions are used in this document:
1.4
Further documentation
An online help system is provided with the TNMS CT software. It includes comprehen-sive instructions on the functions offered by the user interface. The help system contains information on window contents, menus and meaning of used icons. Via the help table of contents, the user can find the tasks and procedures necessary to operate and admin-istrate TNMS CT.
Help can be invoked in any of the following ways:
• After invoking help from the menu bar, the user can search for topics via the table of
contents, the index or a word search.
• Clicking the Help button in the current window, which displays information about the
window contents.
• Pressing<F1>, which displays information about the contents of the active window.
Symbol Explanation
Notes provide additional useful information.
Warnings provide information on critical issues that could result in equipment damage or data loss if ignored.
Table 1 Symbols
Convention Explanation
bold Graphical user interface text, e. g., field names and button descriptions, are written in bold.
Example: Click the View menu, and then clickNew 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 <F1>, for help on the current window. Table 2 Conventions
A50023-K4003-X20-1-7619
Issue: 1 Issue date: October 2012
9
UserManual(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 inter-face (RS232).
There are two operation modes for TNMS CT: the Local Craft Terminal (LCT) mode and the Network Craft Terminal (NCT) mode.
The TNMS CT menu items and dialogues allow the supported communication channels to be set up. The network element to be operated is selected by a simple procedure, adapted to the requirements of the connected communication channel.
TNMS CT enables addresses to be assigned to the network elements. The program icons for these applications are used to 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:
– Network Architecture (see Chp. 2.1) – System Architecture (see Chp. 2.2) – Functional Overview (see Chp. 2.3)
2.1
Network Architecture
Figure 1shows the general structure of a transmission network managed by TNMS CT. The network elements (NEs) connect to theDCN through QB3M or SNMP channels, depending on the telegram protocol supported by the NE.
User Manual (UMN) Information
Figure 1 General Structure of a TNMS CT Network
Element management functions are executed via the element managers (LCTs) provided by the TNMSCT 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 Supported NEs
QB3M hiT 7050, hiT 7070, hiT 7500, hiT 7540, hiT 7550, SMA1/4, SMA 4/1, SMA1K, SMA1K-CP, SMA16, SMA16/4, SL16, SLR16, SL64, WL, WLS, WTTR SNMP FSP, hiT 7020, hiT 7025, hiT 7030, hiT 7035, hiT7060,
hiT7060 HC, hiT 7065, hiT 7080, hiT 7300 Table 3 Supported NEs
A50023-K4003-X20-1-7619
Issue: 1 Issue date: October 2012
11
UserManual(UMN) Information
2.2
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.
User Manual (UMN) Information
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 Overview of Software Components
2.2.2.1
TNMS CT Client
The main parts of the TNMS CT client component are the network management graph-ical user interface including the import and expo rt interfaces and the element manag ers.
A50023-K4003-X20-1-7619
Issue: 1 Issue date: October 2012
13
UserManual(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 con-troller 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
Detailed operating information on operating TNMS CT is provided in Chapter 4 and in the Online Help.2.2.2.2
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 package, which contain all relevant components (e.g. the NE controller) needed to run a family of NEs within TNMS CT. The combination of EML packages required for a given TNMS CT system depends on the NE types that TNMS system configuration is required to support.
NE 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.
User Manual (UMN) Information
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 management 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 connec-tions.
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.
A50023-K4003-X20-1-7619
Issue: 1 Issue date: October 2012
15
UserManual(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.
TheCT 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 theSerial 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 GNEs. 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 subnet-works. This information is also displayed on the network map.
Network Elements
The NE nodes provide the following functions:
– Handling the connection to one network element. – Activating 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.
User Manual (UMN) Information
Figure 4 A GNE detecting its managed NEs
2.3.4
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 theDCN 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
simul-taneously, 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
A50023-K4003-X20-1-7619
Issue: 1 Issue date: October 2012
17
UserManual(UMN) Information
theDCN Management View, the topology information is available in TNMS CT. Accord-ingly, integration of network information is simplified.
g
This function may not be available in all network elements.Also be aware that topology information has to be stored in the NE prior to the activation of the NE in TNMS CT.
2.3.8
Automatic Recognition
In case of a communication loss, an automatic reconnection to the network elements is supported. The retry interval can be set via theProperties windows of the DCN chan-nels.
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 cri-teria.
If alarm notifications are received by the TNMS CT Server or TNMS CT Client, the fol-lowing actions are performed:
For each alarm notification received by the TNMS CT Server:
– The notification is forwarded to the connected TNMS CT Client. – The list of current alarms is updated.
– The notification is stored in the alarm log.
For each alarm notification received by the TNMS CT Client:
– The alarm is updated. – The alarm log is updated.
– The alarm supervision of NE icons and NE container icons is updated.
The operator can localize the network 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
User Manual (UMN) Information
as for individual network elements. This allows the user to quickly assess the importance of the alarm concerned.
For further fault localization, the user can also call up the appropriate element manager. TheAlarm Statistic window enables the operator to handle alarms conveniently. The Alarm statistic windows shows:
– The number of current alarm per severity.
– Alarms sep arated for unacknowledged and acknowledged state. – Summary counters per severity.
– Summary counter of total alarms.
The window presents the alarm statistics in a matrix view and is updated automatically.
2.3.10
User Management and 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 aSecurityLog which stores the logged-on users and their actions, e.g. usage of Element Managers. Access to this from outside TNMS CT is not possible, except for the system administrator and the file owner. Addi-tionally, the following security features are implemented:
– Password security including password complexity and a check against logical
arrangement and toggling of formerly used passwords.
– System message after five consecutively failed login attempts. – Logout due to user inactivity.
2.3.11
Remote 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
Remote login is supported in NCT mode only! Information on NCT mode is given in Chp. 2.3.1.2.3.12
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 printed out or saved to a file. TNMS CT provides logs that are permanent. Permanent logs are fixed, global logs administered by the TNMS CT system. The op erator can, however, specify certain attri-butes such as the maximum log size.
A50023-K4003-X20-1-7619
Issue: 1 Issue date: October 2012
19
UserManual(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 message 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:
– Set the UniGATE machine to host.
– Set the TNMS CT computer to remote controller.
2.3.14
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 com-prises a network layer. Consequently, such aTMS 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.
User Manual (UMN) Installation
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 ques-tions 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:
– 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 documen-tation which provides specific information about the installation. These planning doc-uments are available to the customer after installation work is completed.
– Protocols:
During commissioning, an acceptance protocol should be maintained. The accep-tance protocol supplied must be completed and signed by Nokia Siemens Networks service personnel and the customer to prove correct commissioning of the system and to provide a record of the initial configuration in case of later queries.
– Field test protocols:
A50023-K4003-X20-1-7619
Issue: 1 Issue date: October 2012
21
UserManual(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
TheCE conformity declaration for the product is fulfilled if installation and cabling are carried out in accordance with the docum entation supplied. Where necessary, project-specific documents should be taken into account.
Deviations from the specifications, or modifications during installation such as the use of cable types with lower shielding dimensions may violate CE protection requirements. In such cases, the conformity declaration is invalidated. Responsibility for any subse-quent problems lies with the person responsible for the de viation.
Personnel Requirements for Commissioning
The following personnel requirements must be fulfilled for commissioning:
– Training to service technician level or communications engineering equivalent. – Sound knowledge of transmission systems.
– Appropriate, device-related training by the manufacturer (incl. required device and
system knowledge for the planned activity).
– Detailed PC knowledge, additional knowledge of operating MS XP/Windows 7. – Familiarity with LANs/WANs.
– Basic knowledge of measurement systems.
– Knowledge of operating electrostatic-sensitive devices.
3.1
Protective Measures and Handling
Protective measures and information on handling electrical components in the TNMS CT installation is provided here.
g
As a general rule, you should always note the manufacturer’s instructions when handling devices such as PCs, monitors, printers and tape drives, or when installing modules such as network cards.3.1.1
Safety Precautions When the Unit is Open
Before opening the unit, remove the power cable.Once the unit is open, live connector pins are freely accessible. To prevent electric shocks, make sure that these pins do not come into contact with foreign potential (e.g. ground).
3.1.2
Protection against Excessive Contact 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.
User Manual (UMN) Installation
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 theESD (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:
– Component Delivery (see Chp. 3.2.1)
– Hardware and Software Recommendations (see Chp. 3.2.2) – Installation and Cabling (see Chp. 3.2.4)
– Installation Software (see Chp. 3.2.3) – Installation Sequence (see Chp. 3.2.5)
3.2.1
Component Delivery
Before installation, ensure that:– The delivery is complete in accordance with the delivery units specified in the
A50023
A50023-K4003-X2-K4003-X20-1-76190-1-7619
Issue: 1 Issue date: October 2012 Issue: 1 Issue date: October 2012
23 23 U
UsseerrMMaannuuaall ((UUMMNN)) IInnssttaallllaattiioonn
–
– The components are not damaged in any way.The components are not damaged in any way.
3.2
3.2.2
.2
Har
Hardw
dware
are and
and Sof
Softwar
tware
e Rec
Recomm
ommend
endati
ations
ons
The following tables provide an overview of the hardware and
The following tables provide an overview of the hardware and software recommenda-software recommenda-tions for running TNMS CT.
tions for running TNMS CT.
g
g
When using machines with less memory space than the recommended, for exampleWhen 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 machines with 256MB and 512MB of memory, the ability to open several LCTs at the same time can be affected.same time can be affected.
When running TNMS CT in Windows 7, the generic RS232 to USB adapter is only When running TNMS CT in Windows 7, the generic RS232 to USB adapter is only sup-ported over XP mode.
ported over XP mode.
f
f
TNMS-CT does not support Hyper-Threading technology, which is used in somTNMS-CT does not support Hyper-Threading technology, which is used in som e Intele Intel Pentium 4 processors. WhenPentium 4 processors. When running TNMS-CT on a machine with such running TNMS-CT on a machine with such a processor,a processor, Hyper-Threading must be disabled on the BIOS Setup.
Hyper-Threading must be disabled on the BIOS Setup. Recommended software for running TNMS CT.
Recommended software for running TNMS CT. H
Haarrddwwaarree RReeccoommmmeennddaattiioonnss C
CPPUU PPeennttiiuum m IIV V 22,,6 6 GGHHzz//55112 2 kkBB
1 GHz or faster 32-bits (x86) in case
1 GHz or faster 32-bits (x86) in case of Windows 7of Windows 7 M
Meemmoorryy 1 1 GGBB H
Haarrd d DDiisskk 440 0 GGBB Opt
Opticical al DisDisc Dc Dririveve DVDVD-RD-ROM OM dridriveve L
LAANN EEtthheerrnneet t ccaarrdd, , 22x x 33CCOOM M ((33CC998822--TTXXMM)) Gr
Graphaphicics Cs Carardd 32 M32 MB (B (wiwith Dth DirirecectX 9 gtX 9 graraphphicics des devivice wce witith WDh WDDM 1DM 1.0 o.0 or hir highgherer driver for Windows 7)
driver for Windows 7) IInntteerrffaacce e ppoorrttss EEtthheerrnneet t ppoorrtt
RS232 serial port or generic RS232 to USB ada RS232 serial port or generic RS232 to USB ada pter pter M
Moonniittoorr CCoolloor r mmoonniittoor r 1199”” Table 4
Table 4 Hardware recommendations for TNMS CTHardware recommendations for TNMS CT
S
Sooffttwwaarree RReeccoommmmeennddaattiioonnss Operat
Operating sying systemstem WindowWindows XP includs XP including the lateing the latest Servist Service Pack 3 (for TNMS Cce Pack 3 (for TNMS CTT Server the Professional edition is recommended)
Server the Professional edition is recommended) or
or
Windows 7 Professional 32 bits or 64
Windows 7 Professional 32 bits or 64 bits, including the latestbits, including the latest Service Pack
Service Pack NSA
NSAP conP confifigurguree OSI SOSI Stactack (fok (for TNMr TNMS CT SerS CT Server Over OSI StSI Stack iack is recos recommemmendednded)) Table 5
User Manual (UMN) User Manual (UMN) Installation
Installation
3.
3.2.
2.3
3
In
Inst
stal
alla
lati
tion
on So
Soft
ftwa
warre
e
All recommAll recomm ended sended software paoftware parts must be rts must be released released for the apfor the appropriate propriate TNMS CTTNMS CT software version. This holds for the initial installat
software version. This holds for the initial installation and for service oion and for service o r upgrade packager upgrade package installations as well.
installations as well.
g
g
If additional software (not required by If additional software (not required by TNMS CT) is installed, the correct functionalityTNMS CT) is installed, the correct functionality cannot be guaranteed.cannot be guaranteed.
The following software is generally required for the installation. The corresponding order The following software is generally required for the installation. The corresponding order numbers are provided in the T
numbers are provided in the T NMS CT release documentation.NMS CT release documentation. More information on the installation sequence is provided in Chp.
More information on the installation sequence is provided in Chp. 3.2.53.2.5..
1.
1. Installation instructions for the operating system Installation instructions for the operating system are provided in Chp.are provided in Chp. 3.33.3, however,, however,
pre-instal
pre-installed machines can also led machines can also be used.be used.
2.
2. FTP Service component (required by TNMS CT Server):FTP Service component (required by TNMS CT Server):
The File Transfer Protocol (FTP) service allows clients to connect to
The File Transfer Protocol (FTP) service allows clients to connect to the TNMS CTthe TNMS CT Server machine and retrieve or store files for APS downloads and
Server machine and retrieve or store files for APS downloads and MIR uploads.MIR uploads. This service is a component
This service is a component of the Internet Information Services (IIS) inclof the Internet Information Services (IIS) included withuded with Windows XP Professional or Windows 7 Professional, however, it is not
Windows XP Professional or Windows 7 Professional, however, it is not enabled byenabled by default and therefore must be configured manually. More information on
default and therefore must be configured manually. More information on how tohow to enable this service is available in Chp.
enable this service is available in Chp.3.3.43.3.4..
3.
3. TNMS CT:TNMS CT:
This installation contains the
This installation contains the following software components for following software components for installatinstallation:ion:
–
– Integrated TNMS CT software installation package:Integrated TNMS CT software installation package:
This installation progr
This installation program includes the Server and am includes the Server and Client components. These canClient components. These can be installed either individually or together as
be installed either individually or together as required.required. The EML packages for
The EML packages for QB3M and FSP are QB3M and FSP are also available for selection duringalso available for selection during the TNMS CT installation. The EML packages are installed on the
the TNMS CT installation. The EML packages are installed on the Server PC.Server PC. More information on installing TNMS CT is provided in Chp.
More information on installing TNMS CT is provided in Chp. 3.5.23.5.2.. Addition
Additionally to the TNMally to the TNM S CT installatioS CT installation, the follown, the following 3rd-paring 3rd-party softwaty software compo-re compo-nents are also included on
nents are also included on this DVD:this DVD:
–
– TrapHandler:TrapHandler:
The TrapHandler is automatically installed with the application as
The TrapHandler is automatically installed with the application as a service.a service.
–
– JavaSoft JAVA Runtime Environment:JavaSoft JAVA Runtime Environment:
The JRE is automatically installed on the client machine to provide an
The JRE is automatically installed on the client machine to provide an environ- environ-ment for the Java b
ment for the Java b ased applications.ased applications.
–
– OSI stack:OSI stack:
The OSI stack software must be installed on Server
The OSI stack software must be installed on Server PC before the ServerPC before the Server Web
Web BrBrowowseserr The The OnlOnlinine Hee Help lp rerequiquireres ts the Ihe Intnterernet net ExExplplororer er Web Web BrBrowowseser.r. It is recommended using the
It is recommended using the Internet ExplorInternet Explorer included with theer included with the Service Pack updates: IE6 for XP SP3 or
Service Pack updates: IE6 for XP SP3 or IE8 for Windows 7 Pro-IE8 for Windows 7 Pro-fessional.
fessional. P
PDDF F RReeaadde re r AAccrro bo baat t RReeaaddeer r 6 6 oor r llaatte re r..
(a PDF reader is required to access
(a PDF reader is required to access the TNMS CT User Manual)the TNMS CT User Manual) S
Sooffttwwaarree RReeccoommmmeennddaattiioonnss
Table 5
A50023
A50023-K4003-X2-K4003-X20-1-76190-1-7619
Issue: 1 Issue date: October 2012 Issue: 1 Issue date: October 2012
25 25 U
UsseerrMMaannuuaall ((UUMMNN)) IInnssttaallllaattiioonn
software itself. More information on installing the OSI stack
software itself. More information on installing the OSI stack is provided in is provided in Chp.Chp. 3.4.1
3.4.1..
–
– Acrobat Re Acrobat Reader:ader:
Acrobat Reader is required for using
Acrobat Reader is required for using the User Manual which is the User Manual which is delivered as PDFdelivered as PDF file. More information on installing the Acrobat Reader is provided in Chp.
file. More information on installing the Acrobat Reader is provided in Chp. 3.4.23.4.2.. Software DVD Overview
Software DVD Overview The software is delivered on a
The software is delivered on a DVD-ROM. The operating system will be delivered asDVD-ROM. The operating system will be delivered as part of the hardware, it is not
part of the hardware, it is not included within the following table.included within the following table. Overview of the de
Overview of the de liverable DVD-ROM:liverable DVD-ROM:
–
– TNMS CTTNMS CT
CT application SW, element manager
CT application SW, element manager applications, NECapplications, NECs, OSI stack, JRE, Acrobats, OSI stack, JRE, Acrobat Reader Reader – – OEMOEM SW for FSP equipment SW for FSP equipment –
– Customer DocumentationCustomer Documentation
User Manual User Manual
3.
3.2.
2.4
4
In
Inst
stal
alla
lati
tion
on an
and C
d Cab
abli
ling
ng
Before installing the operating system, the following steps
Before installing the operating system, the following steps should be comshould be com pleted:pleted:
–
– The Client and Server machines should be set up and cabled in accordance with theThe Client and Server machines should be set up and cabled in accordance with the
project-specifi
project-specific c installatiinstallation on documents sdocuments s upplied.upplied.
–
– The applicable recommendations for screen-based workstations should beThe applicable recommendations for screen-based workstations should be
observed. observed.
–
– To guarantee 24-hour operation, an unTo guarantee 24-hour operation, an un interruptinterrupted power supply must ed power supply must be available.be available.
3.
3.2.
2.5
5
In
Inst
stal
alla
lati
tion
on Se
Sequ
quen
enc
ce
e
g
g
Before installing any software component, refer to the associated readme file, whereBefore installing any software component, refer to the associated readme file, where you canyou can find the latest informations concerning installation.find the latest informations concerning installation. The system should be
The system should be commissioned as follows:commissioned as follows:
1.
1. Set up and cable, as described in Chp.Set up and cable, as described in Chp. 3.2.43.2.4.. 2.
2. Install the operating system and aInstall the operating system and a dditional hardwardditional hardware components, and e components, and configure theconfigure the
system under Windows OS as described in Chp. system under Windows OS as described in Chp. 3.33.3..
3.
3. Install FTP service on the Server machine as dInstall FTP service on the Server machine as d escribed in Chp.escribed in Chp.3.3.43.3.4.. 4.
4. Install the OSI stack on the Install the OSI stack on the Server machine as described in Chp.Server machine as described in Chp. 3.4.13.4.1.. 5.
5. Install Acrobat Reader as described in Chp.Install Acrobat Reader as described in Chp. 3.4.23.4.2.. 6.
6. Install the TNMS CT software components on the Install the TNMS CT software components on the corresponding machines ascorresponding machines as
described in Chp. described in Chp. 3.5.23.5.2:: – – TNMS CT ClientTNMS CT Client – – TNMS CT Server TNMS CT Server –
– TNMS CT EML PackagesTNMS CT EML Packages –
– Addition Additional TNMS softwaal TNMS softwa re, such as re, such as optional Eoptional EML pacML packages.kages. 7.
7. Configure the TNMS CT components and Configure the TNMS CT components and connect network elements as describedconnect network elements as described
in Chp.
User Manual (UMN) Installation
8. Perform system testing in accordance with the test cases described in the
accep-tance test protocol. For more information, contact Nokia Siemens Networks Techni-cal Sales.
