Coriant is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recom-mendations for power use and proper disposal of our products and their components.

TNMS14.1 10

Coriant TNMSInstallation Manual (IMN, Windows)

A50023-K2035-X040-05-76D1

Issue: 5 Issue date: July 2014

2 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014

Installation Manual (IMN, Windows)

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 Coriant 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 Coriant. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full respon-sibility when using it. Coriant welcomes customer comments as part of the process of contin-uous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Coriant and the customer. However, Coriant has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Coriant will, if deemed necessary by Coriant, explain issues which may not be covered by the document. Coriant will correct errors in this documen-tation as soon as possible.

IN NO EVENT WILL CORIANT BE LIABLE FOR ERRORS 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 are considered protected by copyrights and other intellectual property rights according to the applicable laws.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright Coriant 2014. All rights reserved.

f Important Notice on Product SafetyThis 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 Von diesem Produkt knnen Gefahren durch Laser, Elektrizitt, Hitzeentwicklung oder andere Gefahrenquellen ausgehen.

Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheit-sanforderungen erfolgen.

Die Sicherheitsanforderungen finden Sie unter Sicherheitshinweise im Teil Legal, Safety and Environmental Information dieses Dokuments oder dieses Dokumentation-ssatzes.

Installation Manual (IMN, Windows) Table of ContentsThis document has 96 pages.

Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.1 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.2 Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.3 Symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.4 Available documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.4.1 Online Help system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.4.2 User Manual (UMN). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.4.3 Installation Manual (IMN). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.4.4 Upgrade Manual (UPMN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.4.5 Other documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.1 Component delivery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.2 Hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.2.1 Virtualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.3 Supported Operating Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.4 Prerequisites by component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.5 BIOS configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3 Server operating system configuration . . . . . . . . . . . . . . . . . . . . . . . . . 193.1 Integrated Lights-Out (iLO) management console. . . . . . . . . . . . . . . . . 193.2 Disk configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.3 Windows installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.4 HP service pack installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.5 Medium configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.6 Large configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.7 Disk partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4 Initial system configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234.1 Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234.2 Virtual memory configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234.3 Audit policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.4 FTP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.4.1 Installing Internet Information Services in Windows Server 2008 . . . . . 254.4.2 Configuring the FTP Service in Windows Server 2008 . . . . . . . . . . . . . 264.4.3 Installing Internet Information Services in Windows 7 . . . . . . . . . . . . . . 264.4.4 Configuring the FTP Service in Windows 7 . . . . . . . . . . . . . . . . . . . . . . 274.5 Domain Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274.6 System Hosts configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274.7 Dynamic Port range configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014 35 Software prerequisites installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Installation Manual (IMN, Windows) 5.1 Adobe Reader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295.2 User Account Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295.3 MSXML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295.4 MS.NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295.5 Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305.5.1 Uninstalling Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325.6 OSI Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335.6.1 Installing OSI Stack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335.6.2 Configuring OSI stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335.6.3 Uninstalling OSI stack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345.7 CopSSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345.7.1 Installing CopSSH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355.7.2 Configuring CopSSH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355.7.3 CopSSH Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375.7.4 CopSSH Hardening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385.8 Antivirus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385.9 NTI third-party software installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

6 TNMS installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416.1 Full installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416.2 Installation of separate components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446.3 About the automatic priority updates installation . . . . . . . . . . . . . . . . . . 45

7 Post-installation procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477.1 Starting services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477.2 Starting a Client session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477.3 Logging in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477.4 Default username and password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487.5 Changing the password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487.6 Terminating a Client session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487.7 Single Sign-on. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497.8 Standby server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497.9 License keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497.10 Internet Explorer configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497.11 Connection timeout configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497.12 Importing a public certificate from IOC Online Planning (IOC OP) . . . . . 50

8 Backup and restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518.1 General description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518.2 Overview of the Backup and Restore interfaces. . . . . . . . . . . . . . . . . . . 528.2.1 Interactive mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528.2.2 Non-interactive mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528.3 Backup procedures through the command line . . . . . . . . . . . . . . . . . . . 538.3.1 Backing up the Oracle database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538.3.2 Backing up the TNMS database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548.3.3 Backing up the LDAP (OpenDS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558.3.4 Backing up the TNMS database and the LDAP (OpenDS) simultaneously

558.3.5 Automating the Backup procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 4 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014

Installation Manual (IMN, Windows) 8.4 Backup procedures through the TNMS client . . . . . . . . . . . . . . . . . . . . 578.5 Recovery & Restore procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598.5.1 Recovering the Oracle database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598.5.2 Restoring the TNMS database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598.5.3 Restoring the LDAP (OpenDS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608.5.4 Restoring the TNMS database and the LDAP (OpenDS) simultaneously .

61

9 Upgrade to TNMS 14.1 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

10 TNMS and TNMS Core working together . . . . . . . . . . . . . . . . . . . . . . . 6510.1 Configuring common hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6510.1.1 Configuring a Common Netserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6810.1.2 Configuring a Common Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7010.1.3 Configuring a Common standby server . . . . . . . . . . . . . . . . . . . . . . . . . 7010.2 Importing data from TNMS Core . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7010.3 Important note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

11 TNMS uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

12 Security hardening. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7512.1 Physical and hardware hardening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7512.2 Operating System hardening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7512.2.1 Microsoft Windows security patches . . . . . . . . . . . . . . . . . . . . . . . . . . . 7512.2.2 Disable and delete unnecessary accounts . . . . . . . . . . . . . . . . . . . . . . 7512.2.3 Uninstall unnecessary applications and roles . . . . . . . . . . . . . . . . . . . . 7612.2.4 Configure Auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7612.2.5 Disable unnecessary shares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7612.2.6 Disable Remote Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7712.2.7 Windows Error Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7712.2.8 Additional Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7812.2.9 Digitally signed communications (Local Security Policy) . . . . . . . . . . . . 7812.2.10 Minimize system services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7812.2.11 Remote Access/Remote Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8012.2.12 Reduce passive FTP port range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8112.3 Networking and firewall configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 8112.3.1 List of ports to open in the firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8212.3.2 How to configure the Windows firewall . . . . . . . . . . . . . . . . . . . . . . . . . 8912.4 OEM Hardening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8912.4.1 JBoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8912.4.2 CopSSH (SFTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8912.4.3 Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9012.4.4 Internet Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9012.5 TNMS Maintenance Packages and Workaround Updates . . . . . . . . . . 9012.6 User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9012.6.1 Restricting the specified files permissions . . . . . . . . . . . . . . . . . . . . . . 92

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014 5

Installation Manual (IMN, Windows) Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 6 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014

Installation Manual (IMN, Windows) List of FiguresFigure 1 "Local Security Settings - Audit Policy" window. . . . . . . . . . . . . . . . . . . 24Figure 2 How to set the TNMS installer to run with administrator rights in Windows

7 and Windows Server 2008.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Figure 3 Backup & Restore console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Figure 4 Changing the Oracle database backup schedule settings. . . . . . . . . . . 54Figure 5 Backup submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Figure 6 Backup submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Figure 7 Backup submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Figure 8 Backup window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Figure 9 Restore submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Figure 10 Restore submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Figure 11 Restore submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Figure 12 Distributed TNMS applications (large system). . . . . . . . . . . . . . . . . . . . 65Figure 13 Distributed TNMS applications (medium system) . . . . . . . . . . . . . . . . . 66Figure 14 Common Netserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Figure 15 Common Standby Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014 7

Installation Manual (IMN, Windows) 8 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014

Installation Manual (IMN, Windows) List of TablesTable 1 Structure of the manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Table 2 Hardware requirements for new installations of TNMS 14.1 10. . . . . . . 15Table 3 Hardware recommendations for installations of TNMS 14.1 10 on reused

legacy hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Table 4 Operating System recommendations for TNMS Server, NetServer, Client

and Citrix Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Table 5 TNMS software prerequisites and their installation sequence . . . . . . . 17Table 6 Paging file size. Note that automatic management is recommended. . . 23Table 7 RAM requirements and Oracle template files . . . . . . . . . . . . . . . . . . . . 30Table 8 List of the available arguments in non-interactive mode . . . . . . . . . . . . 52Table 9 Windows default shares. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Table 10 Firewall rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Table 11 Database-related configurations and security hardenings. . . . . . . . . . . 90Table 12 Default TNMS user accounts and security hardenings. . . . . . . . . . . . . 90 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014 9

Installation Manual (IMN, Windows) 10 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014

Installation Manual (IMN, Windows) Preface 1 Preface

This Installation Manual contains a complete description of the installation and initial configuration processes of TNMS.

1.1 Intended audienceThis document is intended for commissioners of TNMS.

1.2 Structure of this documentThe IMN is a single .pdf file viewable and printable with Adobe Reader.

This document is structured as follows:

g Some features described in this documentation may not be available. To identify the features released for the product, see the Customer Release Notes delivered together with the product.

Chapter Title Subject

Chapter 1 Preface Provides an introduction for this document.

Chapter 2 Preparation Provides a guide of the hardware and software required for the instal-lation.

Chapter 3 Server operating system configuration

Describes the creation and configuration of the logical drives in the machine where the server will be installed.

Chapter 4 Initial system configuration Describes the configurations of the operating system required for TNMS correct functioning.

Chapter 5 Software prerequisites installation

Describes how to install and configure all software prerequisites of TNMS.

Chapter 6 TNMS installation Describes how to install TNMS in your operating system.

Chapter 7 Post-installation proce-dures

Describes all post-installation configurations and actions.

Chapter 8 Backup and restore Guides the TNMS administrator through the B&R procedures.

Chapter 9 Upgrade to TNMS 14.1 10 Describes the migration to version 14.1 10 from a previous TNMS release.

Chapter 10 TNMS and TNMS Core working together

Describes how to configure TNMS to share resources and data with TNMS Core.

Chapter 11 TNMS uninstallation Describes how to uninstall TNMS.

Chapter 12 Security hardening Describes the existing TNMS security hardenings.

- Abbreviations Contains a list of all acronyms and their long form used in TNMS.

Table 1 Structure of the manual A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014 11

Installation Manual (IMN, Windows)Preface 1.3 Symbols and conventions

The following sections describe the symbols and conventions used in the IMN.

Graphical user interface textWindow titles are placed inside quotation marks. Button names, keys, main or context menu entries, keystrokes are printed in bold.Example:

Click the View menu, and then click Log List....CommandsCommands and screen output are printed in a monospaced font.

Example:

Issuepowercfg.exe /hibernate off

VariablesPlaceholders are printed in , and filenames and paths are printed in italics.

Example:

Save the log file .txt to ..//binWarningsA safety message indicates a dangerous situation where personal injury is possible.

Example:

f Important Notice on Product Safety:This product may present safety risks due to laser, electricity, heat, and other sources of danger.

NoticesA notice is a must. Follow notices to avoid damage, loss or interruption. Example:

w Do not reboot while mirroring.NotesA note is an alert. Follow notes to learn about exceptions, side effects or something obscure or yet unclear. Example:

g Read the Customer Release Notes before installing.TipsA tips is a suggestion. Follow tips for convenience or efficiency. Example:

t Before mirroring, limit the size of the root filesystem.

1.4 Available documentationThe following documents are delivered with TNMS: 12 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014

Installation Manual (IMN, Windows) Preface 1.4.1 Online Help system

A context-sensitive online help system is provided with TNMS which includes informa-tion on window contents, menus and meaning of the icons shown, and comprehensive instructions on the functions offered by the user interface. You can find the tasks and procedures necessary to operate and administer TNMS on the systems table of con-tents.

That is, the Online Help system follows a two-pronged approach:

Descriptive.This is for when you want to know what any window element is, in any window. Par-ticular aspects of TNMS or deeper knowledge of it are routinely provided, together with topical best practices.

Operational.This is for when you want to know how to perform a task.

Help can be invoked in any of the following ways:

After invoking help from the menu bar, you can search for topics via the table of con-tents, 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.For most windows, F1 help is further available through the main help menu (Help > On ).

1.4.2 User Manual (UMN)The UMN is available from Main > Help and displayed in its own Adobe Reader window.It overviews TNMS architecture, describes its features and functions, takes you through all major operation topics and helps you troubleshoot common issues. This document is intended for all users of TNMS.

1.4.3 Installation Manual (IMN)The Installation Manual contains a complete description of the installation procedures of the TNMS Server, and the uninstallation procedures of the TNMS Server and TNMS Client.

1.4.4 Upgrade Manual (UPMN)The Upgrade Manual describes in detail all the upgrade procedures of the TNMS com-ponents from a previous TNMS release to the current release.

1.4.5 Other documents

TNMS Core and Network ElementsThis manual concerns TNMS only. For more detailed information on TNMS Core or the managed network elements (NEs), see the corresponding documentation. A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014 13

Installation Manual (IMN, Windows)Preface Release notesWhere applicable, contains installation hints, patch descriptions, list of supported NEs, list of supported cards and any relevant last-minute information. 14 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014

Installation Manual (IMN, Windows) Preparation 2 Preparation

2.1 Component deliveryBefore installation, be sure that:

The delivery is complete and in accordance with the delivery units specified in the delivery note (hardware, software and documentation).

The components are not damaged in any way. Make sure you use the installation packages in the target machine since TNMS

installation from a network drive is not supported.

2.2 Hardware requirementsThe tables below give a rough overview of the hardware recommendations for installing TNMS; running TNMS may require different specifications depending on parameters such as network architecture (number of Clients) or operation policies (backup, logs). The final hardware specifications and configuration must be planned specifically for each customer. Ask Coriant Technical Sales for more information.

Two hardware configurations (Medium and Large) designed for new installations are provided (Table 2).

g New TNMS installations are not recommended in a distributed environment.

In addition the Legacy hardware configuration is provided (Table 3). This configuration is designed for the reuse of hardware compatible with TNMS 13.2 1x but not with later releases.

Configuration Characteristics Medium Large

TNMS Server + Netserver

(1 optional client only for local trou-bleshooting)

Base reference model DL360p G8 orBL460c G8 (blade server)

DL580 G7 orBL660c G8 (blade server)

Minimum CPU (2x) Intel Xeon E5-2680/90 (4x) Intel Xeon E7-4870 or (4x) Intel Xeon E5-4650

Minimum RAM 32 GB 128 GB

Minimum HDD (4 x) 300 GB HD(4 x) 146 GB + (2 x) 300GB for hardware reuse

(2 x) 300 GB internal SSDs(6 x) 300 GB internal HDs

TNMS Client Base reference model ESPRIMO E710 E90+ or PY RX100S7

Minimum CPU Intel i5-3470 or Intel Xeon E3-1220v2 4C/4T 3.10 GHz 8 MB

Minimum RAM 8 GB DDR3 1600 GHz

Minimum HDD HD SATA III 500GB 7.2K or HD SATA 6G 500GB 7.2K HOT PL 3.5" BC

Table 2 Hardware requirements for new installations of TNMS 14.1 10 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014 15

Installation Manual (IMN, Windows)Preparation g A new installation using the Legacy hardware configuration does not support Optical Management.

2.2.1 VirtualizationTNMS supports virtualization using VMware ESXi 4.1. However Coriant does not provide neither is responsible for stability limits or performance in these circumstances.

Configuration Characteristics Legacy hardware

TNMS Server + Netserver

(1 optional client only for local troubleshooting)

Base reference model PY TX/RX200S7

Minimum CPU Intel Xeon E5-2420 6C/12T 1.90 GHz 15 MB

Minimum RAM 12 GB

Minimum HDD 2x HD SATA 6GB 500GB 7.2K HOT PL 3.5" BC

TNMS Client

or

Common Client

Base reference model ESPRIMO E710 E90+ or PY RX100S7

Minimum CPU Intel i5-3470 or Intel Xeon E3-1220v2 4C/4T 3.10 GHz 8 MB

Minimum RAM 8 GB DDR3 1600 GHz

Minimum HDD HD SATA III 500GB 7.2K or HD SATA 6G 500GB 7.2K HOT PL 3.5" BC

TNMS Server

(1 optional client only for local troubleshooting)

Base reference model PY RX/TX300S7

Minimum CPU Intel Xeon E5-2609 4C/4T 2.40 GHz 10 MB

Minimum RAM 24 GB DDR3 1333 GHz

Minimum HDD 2x HD SAS 6GB 300GB 15K HOT PL 2.5" EP

TNMS Netserver Base reference model ESPRIMO E710 E90+ or PY RX100S7

Minimum CPU Intel i5-3470 orIntel Xeon E3-1220v2 4C/4T 3.10 GHz 8 MB

Minimum RAM 8 GB DDR3 1600 GHz

Minimum HDD HD SATA III 500GB 7.2K or HD SATA 6G 500GB 7.2K HOT PL 3.5" BC

Common Netserver

(TNMS +TNMS Core)

Base reference model ESPRIMO E710 E90+ or PY RX100S7

Minimum CPU Intel i5-3470 orIntel Xeon E3-1220v2 4C/4T 3.10 GHz 8 MB

Minimum RAM 16 GB DDR3 1600 GHz

Minimum HDD HD SATA III 500GB 7.2K or HD SATA 6G 500GB 7.2K HOT PL 3.5" BC

Table 3 Hardware recommendations for installations of TNMS 14.1 10 on reused legacy hardware 16 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014

Installation Manual (IMN, Windows) Preparation The requisites of the virtual machines are similar to those presented in Table 2 and Table 3, except for the CPU that only requires comparable CPU resources.

2.3 Supported Operating SystemsThe following table provides the supported operating systems.

g Throughout this and the following chapters the designation of the several operating systems is often abbreviated to allow for better readability. Always refer to the table above for the exact versions supported for TNMS.

2.4 Prerequisites by componentThe following table describes which software is required for each component. Attend to the fact that the table also shows the order in which the components should be installed. After installing the operating system, the system should be commissioned as follows:

g A dedicated Java JRE installation is not mandatory given that the installer already includes the JRE versions required by TNMS. However you can manually install Java j2re-1.6.0_43 (32 or 64 bit) if required by other software.

Full Installation Server, Server + Netserver

Netserver Client Citrix Server

Microsoft Windows Server 2008 R2 SP1 (x64)1)

NTFSmandatory

Microsoft Windows Server 2008 R2 SP1 (x64) 1)

NTFSmandatory

Microsoft Windows Server 2008 R2 SP1 (x64) 1)

Microsoft Windows 7 Professional SP1 (x64)

Microsoft Windows Server 2008 R2 SP1 (x64) 1)

Microsoft Windows 7 Professional SP1 (x32/x64)

Microsoft Windows Server 2008 R2 SP1 (x64) 1)

Table 4 Operating System recommendations for TNMS Server, NetServer, Client and Citrix Server1) Both the Microsoft Windows Server 2008 R2 SP1 (x64) Enterprise Edition and the Standard Edition are sup-

ported. However If the machine has more than 32 GB of RAM you must install the Microsoft Windows Server 2008 R2 SP1 (x64) Enterprise Edition, as the Standard Edition cannot allocate more than 32 GB of RAM.

Software FullInstallation

Server + Netserver

Server Netserver Client

Adobe Reader Mandatory Optional Optional Optional Mandatory

MSXML Mandatory Mandatory Mandatory Mandatory Mandatory

MS.NET Mandatory Mandatory Mandatory Mandatory Mandatory

Oracle 11.2.0.3 Mandatory Mandatory Mandatory - -

OSI Stack Mandatory Mandatory - Mandatory -

CopSSH Mandatory Mandatory - Mandatory -

Citrix XenApp - - - - Optional

Table 5 TNMS software prerequisites and their installation sequence A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014 17

Installation Manual (IMN, Windows)Preparation To install the Java j2re-1.6.0_43 (32 or 64 bit) use the packages available in the TNMS prerequisites and follow the default installation procedure. For additional information refer to the Oracle Java documentation.

Disable all Java automatic updates on the machines where Java is installed. If Java automatic updates are enabled the system may not work properly.

2.5 BIOS configurationThe following chapter, describes the recommended configurations for the system BIOS. These refer to HP machines and may differ with other hardware configurations.

To access the BIOS, boot the machine and press F9 in the startup screen.

Disable the network:Go to System Options > Embedded NICs > NIC # Boot Options and set to Disabled. Where # represents the network interface card number.

Processor options: Go to System Options > Processor Options > Intel Virtualization Technology,

and set to Disabled. System Options > Processor Options > Intel VT-d, and set to Disabled.

Power management options: System Options >Power management options > HP Power Profile, and set to

Maximum performance. System Options > Power management options > HP Power Regulator, and set

to HP Static High Performance Mode 18 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014

Installation Manual (IMN, Windows) Server operating system configuration 3 Server operating system configuration

Before installing the server operating system, you must create and configure the logical drive where Windows will be installed.

The following chapter applies to the recommended medium and large configuration hardware only and these steps may differ in case you have any other hardware config-urations.

3.1 Integrated Lights-Out (iLO) management consoleThis chapter describes how to operate the Integrated Lights-Out (iLO) management console. This console is used to access the server machine and for administration pur-poses. Refer to the iLO specific documentation for further information.

Accessing the Integrated Remote ConsoleUse the following information to access the console:

1. Address: https://2. Username: 3. Password: 4. In the left panel tree, expand Information > Overview, and in Integrated Remote

Console, click the .NET link.

3.2 Disk configurationIt is recommended that you configure a RAID 1 for the disks where the operating systems will be installed.

While booting the machine, proceed as follows:

1. When the Press any key to view Option ROM messages appears, click ENTER.2. When the internal controller displays the message Press to run the option

ROM Configuration For Arrays Utility, click F8.3. At the Main Menu, select Create Logical Drive.4. Using the default settings, create the RAID 1 configuration with the two available

hard drives.

3.3 Windows installationThe steps below refer to the Windows operating system installation using the Integrated Lights-Out (iLO) management console.

1. Open the iLO management console.2. Click Virtual Drives menu > Image file menu entry.3. In the Mount Image File file dialog box, select the Windows 2008 R2 ISO file and

press Open.4. Restart the machine and boot from CD-ROM (typically by pressing F11 to access to

the boot menu).

The Windows installation is standard with no special configurations or inputs. Just need to create one NTFS partition on the previous created volume (RAID 1) with ~50% of the available space. The others 50% will be applied on a new partition to be created after- A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014 19wards.

Installation Manual (IMN, Windows)Server operating system configuration 3.4 HP service pack installation

It is highly recommended to update to the latest HP Service Pack for the corresponding machine model. This service pack updates drivers, software and firmware to the latest version. Check the HP support website for downloading the ISO service pack.

1. Open the iLO management console.2. Click Virtual Drives menu > Image file menu entry.3. In the Mount Image File file dialog box, select the ISO file and press Open.

A new CD-ROM drive is mapped in Windows, providing the content of the service pack.

Login in Windows and run the CD-ROM setup located via:\hp\swpackages\setup.exe

1. In the HP Smart Update Manager window, tab Welcome, click Next.2. In tab Source Selection, choose the Default Repository and click Next.3. In tab Select Targets, click the machine list item, click Edit Target and insert the

Windows Administrator username, its password and click Next.4. In tab Review/Install Updates, click Install.

The machine may reboot automatically, if not click Reboot Now, choose the appro-priate delay and click OK.

3.5 Medium configurationIn order to configure a Windows medium configuration, proceed as follows:

1. Login in Windows.2. Go to Start > All Programs > HP System Tools > HP Array Configuration Utility (64-

bits) > HP Array Configuration Utility (64-bits).3. In tab Configuration, in Select an available device... combo box, select your device

(make sure it is not the Embedded slot). 4. In System and Devices panel, expand the Smart Array tree and select the first

branch and click Create Array. 5. Select the two available disks and click OK.6. Click Create Logical Drive to create a new logical drive.7. Select RAID 1 and keep the default settings. Click Save to finish the operation.

3.6 Large configurationIn order to configure a Windows large configuration, proceed as follows:

1. Login in Windows.2. Go to Start > All Programs > HP System Tools > HP Array Configuration Utility (64-

bits) > HP Array Configuration Utility (64-bits).3. In tab Configuration, in Select an available device... combo box, select your device

(make sure it is not the Embedded slot). 4. In System and Devices panel, expand the Smart Array tree and select the first

branch and click Create Array. 20 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 20145. Select all available disks and click OK.

Installation Manual (IMN, Windows) Server operating system configuration 6. Click Create Logical Drive to create a new logical drive.7. Select RAID 5 and keep the default settings. Click Save to finish the operation.

3.7 Disk partitioningThree new partitions are needed:

One from the internal disks (D) with the other ~50% available - NTFS Two from the disk array - NTFS In order to configure the disk partitioning for medium and large configurations, proceed as follows:

1. Go to Start > Search Programs and Files > type Server Manager and press Enter.2. In Server Manager, expand the server tree Server Manager > Storage > Disk Man-

agement.In case the window Initialize Disk is displayed, click OK keeping the default set-tings.

3. Identify the disk that contains the C: drive and select the grey partition that displays an Unallocated area.3.1 Right-click the unallocated area and select New Simple Volume, click Next.3.2 Choose the recommended partition size (typically 50% of the disk size) and click

Next.3.3 Choose the drive letter D to the new partition and click Next.3.4 In the Format Partition window, format this volume with the following settings:

File system = NTFS Allocation unit size = Default Choose a volume label for the new partition Enable the Perform quick format option

3.5 Click Next and Finish to complete the partition creation step.4. Identify the disk that does not contain any partition (C, D) and select the grey parti-

tion that displays an Unallocated area.4.1 Right-click the unallocated area and select New Simple Volume, click Next.4.2 Choose the recommended partition size (typically 65% of the disk size) and click

Next.4.3 Choose the drive letter E to the new partition and click Next.4.4 In the Format Partition window, format this volume with the following settings:

File system = NTFS Allocation unit size = Default Choose a volume label for the new partition Enable the Perform quick format option

4.5 Click Next and Finish to complete the partition creation step.5. Identify the disk that contains the E: drive and select the grey partition that displays

an Unallocated area.5.1 Right-click the unallocated area and select New Simple Volume, click Next.5.2 Choose the recommended partition size (typically 35% of the disk size) and click

Next.5.3 Choose the drive letter F to the new partition and click Next.5.4 In the Format Partition window, format this volume with the following settings: A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014 21

Installation Manual (IMN, Windows)Server operating system configuration File system = NTFS Allocation unit size = Default Choose a volume label for the new partition Enable the Perform quick format option

5.5 Click Next and Finish to complete the partition creation step.6. Close the Disk Manager window. 22 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014

Installation Manual (IMN, Windows) Initial system configuration 4 Initial system configuration

4.1 Before you beginBefore installing complete the following steps:

Check the system requirements. Determine the file system to be used, the partition to be used by the installation and

the components to install.

The machine where the TNMS Server is installed should use NTFS, as it provides extra security for the Oracle database files.

Oracle must be installed in the same machine as TNMS Server. How the network, IP addresses and TCP/IP name management will be handled. Ensure that the host IP addresses are static, that is, do not use DHCP dynamic

addresses.

In the machines where the TNMS Server and/or Netserver are installed, disable Hibernate by running the following command as administrator:

powercfg.exe /hibernate off

4.2 Virtual memory configurationCoriant recommends that you configure your system to automatically manage the paging file size:

1. Go to Start > Control Panel > System.2. Click on Advanced system settings.3. In the System Properties window, go to the Advanced tab and, in the Perfor-

mance area, click on Settings.4. In the Performance Options window, go to the Advanced tab and click on

Change.5. In the Virtual Memory window, check Automatically manage paging file size for

all drives.However, if you prefer to set a limit to the paging file size for Server and Netserver, do as follows:

1. Follow the steps 1. to 4. above.2. In the Virtual Memory window, uncheck Automatically manage paging file size

for all drives.3. Select the systems drive, select Custom size and enter the paging file size (refer

to table Table 6).Click Set to save the settings and then OK to close the window.

TNMS Component Legacy Medium Legacy Large Medium Large

Server 12 GB 24 GB 16 GB 64 GB

Netserver 4 GB 4 GB - - A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014 23Table 6 Paging file size. Note that automatic management is recommended.

Installation Manual (IMN, Windows)Initial system configuration 4.3 Audit policy

w Proceed to configuring Audit policy only if your network has legacy, NEC-interfaced NEs, that is, other than hiT 7300 or hiT 7100.To enable auditing locally in the installed OS:

1. Open the Local Security Policy settings via Start menu/button > Control Panel (Windows 7 only) > Administrative tools > Local Security Policy icon.

2. In the tree pane, select Audit Policy under Local Policies.

Figure 1 "Local Security Settings - Audit Policy" window3. In the details pane double-click the following policy settings to open the properties

window: Audit Account Logon Events, to track users logon and logoff - select the

check boxes Success and Failure. Audit Account Management, to report changes to user account - select the

check boxes Success and Failure. Audit Directory Service Access, to report access and changes to the directory

service - No auditing (no check box selected). Audit Logon Events, to report success/failure of any local or remote access-

based logon - select the check boxes Success and Failure. Audit Object Access, to report file and folder access - select the check boxes

Success and Failure.

g The auditing configuration for the individual object (file or folder) must be set within its properties. Audit Policy Change, to report group policies changes - select the check boxes

Success and Failure. Audit Privilege Use, to report when permissions (read, write...) are used - 24 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014select only the check box Failure.

Installation Manual (IMN, Windows) Initial system configuration Audit Process Tracking, to report when process and programs fail (not security

related) - No auditing (no check box selected). Audit System Events, to report standard system events (not security related) -

select the check boxes Success and Failure.

4.4 FTP configurationThe following chapter provides you guidance through the needed component services configuration.

4.4.1 Installing Internet Information Services in Windows Server 2008To install the FTP server proceed as follows:

1. Open Start > Administrative tools > Server Manager > Roles.2. Click Add Roles to open the Add Roles Wizard and click Next.3. In Server Roles, select "Web Server (IIS) and click Next.4. In Web Server (IIS) click Next.5. In Role Services, select the top end following services from the tree:

Web Server Common HTTP Features

Static Content Default Document Directory Browsing HTTP Errors

Health and Diagnostics HTTP Logging Request Monitor

Security Request Filtering

Performance Static Content Compression

Management Tools IIS Management Console IIS Management Scripts and Tools Management Service IIS Management Compatibility - when you select this option a warning

pops up informing you that two other components must also be installed. Accept their installation. IIS 6 Scripting Tools

FTP Server FTP Service FTP Extensibility

6. Click Next.7. In Confirmation, click Install.8. In Results, select Close.9. Reboot your computer. A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014 25

Installation Manual (IMN, Windows)Initial system configuration Enabling ASP.NET and IISThe following description details the configuration steps necessary in IIS Manager:

1. Open Start > Administrative tools > Internet Information Services (IIS) Manager. The Internet Information Services Manager enables you to configure, control and troubleshoot IIS and ASP.NET.

2. In the Connections panel on the left, expand the server name and click in Appli-cation Pools.

3. In the Actions panel on the right, click Set Application Pool Defaults.... This opens the Application Pool Defaults window.

4. In the General section, set the Enable 32-Bit Applications option to True and click OK.

4.4.2 Configuring the FTP Service in Windows Server 2008To configure the FTP Service/Server, follow these steps:

1. Start > Administrative Tools > Internet Information Services (IIS) Manager.2. In the left pane tree, expand the Default Computer > Sites.3. In the right pane tree, select Add FTP Site. This opens the Add FTP Site window.4. Enter the FTP site name.5. In Physical Path, change the folder to C:\inetpub\ftproot, click OK and Next.6. In Binding and SSL Settings step, configure the IP Address or leave as default.7. In SSL, select Allow SSL. Click Next.8. In Authentication and Authorization Information step, select Authentication as

Basic.9. In Authorization - Allow access to All users, permissions Read and Write.10. Click Finish.

4.4.3 Installing Internet Information Services in Windows 7To install the FTP server proceed as follows:

1. Open Start > Control Panel > Programs and features > Turn Windows features on or off.

2. Select the top end following services from the tree: Internet information Services

FTP Server FTP Service FTP Extensibility

Web Management Tools IIS 6 Management Compatibility IIS 6 Management Console IIS Management Scripts and Tools Management Service

3. Click OK and confirm.4. After the installation go to Control Panel > Administrative Tools > Internet Informa-

tion Services (IIS) Manager. 26 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 20145. Reboot your computer.

Installation Manual (IMN, Windows) Initial system configuration 4.4.4 Configuring the FTP Service in Windows 7

To configure the FTP Service/Server, follow these steps:

1. Start > Control Panel > Administrative Tools > Internet Information Services (IIS) Manager.

2. In the right pane tree, select "Add FTP Site". This opens the Add FTP Site window.3. Enter the FTP site name, default.4. In Physical Path, change the folder to "C:\inetpub\ftproot", click OK and Next.5. In "Binding and SSL Settings" step, configure the IP Address or leave as default.6. In SSL, select "Allow SSL". Click Next.7. In Authentication and Authorization Information step, select Authentication as

Basic.8. In Authorization - Allow access to "All users", permissions "Read" and "Write".9. Click Finish.10. Then expand the tree in the left pane until default FTP. In the default FTP Home area

click on FTP Authentication. Then in the window right click Basic Authentication and click Enable.

4.5 Domain VerificationCheck if a network domain exists. Use the following windows steps:

1. Go to System Properties via, Start > Control Panel > System.2. In Computer name, domain, and workgroup settings, check the Domain infor-

mation. If a network domain exists and both TNMS Core and TNMS belong to it, then

log on to that domain and proceed with the installation as you normally would. If a network domain does not exist, then:

You may skip this configuration, but then you will not have Single Sign On capabilities in TNMS.

Contact your network administrator to provide you information details on how to configure the domain since domain details are specific for your network.

4.6 System Hosts configurationSince TNMS uses a static IP address configuration, it is mandatory that the system's "hosts" file is properly configured with at least " " and "127.0.0.1 localhost".

Edit Windows hosts file (typically, C:\Windows\System32\drivers\etc\hosts) and for each server insert a line likexx.xx.xx.xx where xx.xx.xx.xx is the static IP of the server in question, and full computer name follows name.domain.com as found in Control Panel > System Properties > Computer Name > Full computer name of the server in question.

If all is properly configured, the full computer name (as found in ... > Computer Name > Full computer name) will appear automatically in the OpenDS Directory Server Configuration window during the installation procedure. A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014 27

Installation Manual (IMN, Windows)Initial system configuration w The TNMS installer will check if the hosts file is correctly configured. In case the server belongs to a domain, make sure FQDN matches the domain.

If no domain exists and the hosts file is not configured, the installation will not proceed.

4.7 Dynamic Port range configurationThe default dynamic port range configuration for Windows Server 2008 and Windows 7 starts at port 49152 and ends at port 65535. This complies with the Internet Assigned Numbers Authority (IANA) recommendation. Proper installation of TNMS requires the default port range to be used.

g TNMS enforces this setting during its installation. However, to avoid warnings while installing TNMS, configure the dynamic port range before the installation (required for Server and Netserver machines), as described below.

Execute the following procedure to ensure the correct configuration of the Server and Netserver machines:

1. Open the command line (cmd) as Administrator.2. Execute the command:

netsh int ipv4 show dynamicport tcp3. If the reported start port is not 49152, then execute the command:

netsh int ipv4 set dynamicport tcp start=49152 num=16384 persistent

Windows is now prepared concerning dynamic port range configuration. 28 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014

Installation Manual (IMN, Windows) Software prerequisites installation 5 Software prerequisites installation

This chapter describes the installation and configuration of all prerequisites in the recommended installation sequence.

Refer to Table 5 TNMS software prerequisites and their installation sequence to know which prerequisites are required for each TNMS component.

5.1 Adobe ReaderYou can either download the latest Adobe Reader from the Adobe website (recom-mended) or use the version included in the Prerequisites folder.

Coriant is not responsible for issues or vulnerabilities introduced by Adobe Reader, in particular when you perform its download.

To install Adobe Reader just follow the standard options shown in its installer. Any specific information on this see the Adobe Reader documentation.

5.2 User Account ControlWhen applicable, Windows User Account Control must be disabled in order to continue with the installation. According to your windows version, the procedure may vary. Typi-cally, it can be disabled under Control Panel > User Accounts > Change User Account Control Settings > Never Notify.Restart the machine after performing this change.

5.3 MSXMLMSXML 4.0 is an XML parser. It must be installed on the system so that networkconfiguration data can be imported and exported in XML format.

To install MSXML 4.0 SP2 on all supported operating systems, proceed as follows:

1. Double-click the msxml4sp2.msi file in the MSXML directory on the software DVD.2. A welcome window is now displayed. Press Next to continue.3. In the End-User License Agreement window, accept the terms of the license

agreement, and press Next to continue.4. In the Customer Information window, enter a user name and the name of your

company in the appropriate fields. Press Next to continue.5. In the Choose Setup Type window, press Install Now.6. The window Installing Microsoft XML Parser and SDK window is now displayed.

The progress of the installation is indicated by the progress bar.7. Once the installation is complete, the window Completing the Microsoft XML

Parser and SDK Setup Wizard is displayed. Press Finish to complete the installa-tion.

5.4 MS.NETWindows Server 2008MS.NET 3.5 is installed with Windows Server 2008, but requires activation. To activate .NET 3.5, proceed as follows: A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014 29

Installation Manual (IMN, Windows)Software prerequisites installation 1. Go to Administrative Tools > Server Manager > Features.2. Click Add Features.3. Select .NET Framework 3.5.1 features.

5.5 OracleThis section describes the installation of Oracle Database 11g Release 2 (64-bit) for Microsoft Windows x64. The supported version is 11.2.0.3.

The Oracle Database must be installed in the TNMS Server machine.

Before installingTo successfully install and run TNMS, at least 40GB of free disk space must be avail-able in the destination machine before installing the Oracle database. RAM requirements are indicated in Table 7 RAM requirements and Oracle template files.

For the remaining hardware, follow the recommendations described in 2.2 Hardware requirements. Note that the values in this table are recommended and may vary accord-ing to the network dimension and the used hardware.

Before installingBy default, the TNMS Database Installer assumes the following directory locations:

Oracle installation disks: c:\oramedia TNMS INSTALLER DIRECTORY: c:\instHowever, it is possible to install from different locations. If you choose to use previous default directory locations you have to create them manually before you start the instal-lation. During the installation you will be requested to confirm the directory paths. If you use different locations you must enter them manually whenever applicable.

1 Create both default directory locations indicated above. If you want to use other locations, make sure they are accessible from the installer (in a local or mapped drive).

2 Unzip the Oracle installation disks 1 and 2 to c:\oramedia (in case of recommended default location. Only the extracted database folder is required. The directory struc-ture should be as follows:

c:\oramedia\database

3 Copy the folders from the delivered TNMS media to the (recommended default location: c:\inst). The directory structure should be as follows:

TNMS Configura-tion

RAM (GB minimal) Oracle template file

Managers

Large 128 TNMS_LW.dbt All

Medium 32 TNMS_MW.dbt All

Legacy 8 TMNS_SW.dbt Ethernet and ASON only

Table 7 RAM requirements and Oracle template files 30 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014

Installation Manual (IMN, Windows) Software prerequisites installation c:\inst\TNMS_Installer

c:\inst\TNMS_Prerequisites

InstallationThe following steps guide you through the Oracle Database installation.

1 Go to \TNMS_Prerequisites\Oracle\installation, right-click the Exec_TNMS_oracle_install.bat file and select Run as administrator.A new terminal window opens. The installation log location is c:\temp and the full path is displayed on the screen.

2 Enter your configuration: Legacy, Medium or Large, by typing Y, M or L, respec-tively.

3 Enter the drives for the ORADATA, ORALOG and ORATRACE directories, or accept the default by pressing [ENTER]. Make sure you specify a valid drive letter followed by the colon sign (for example: c:).

4 Enter the TNMS database name, or accept the default by pressing [ENTER]. The database name must be between 1 and 12 characters long and the first character must be alphabetic.

The main menu is presented as follows:

0 - Check requirements

1 - Oracle Software Installation

2 - TNMS database creation

3 - TNMS database configuration

4 - Exit

Enter the desired option.

5 Choose option 0 - Check requirements by pressing 0.The requirements check is executed, showing the available disk space and free memory. In case the requirements are met, the following message is displayed: You can now proceed with Oracle Database installation!

If the requirements are not met, the message Error: The Oracle installation cannot be done, because some requirements failed is displayed. Make sure you have enough disk space and memory before continu-ing.

6 Choose option 1 - Oracle Software Installation.Press [ENTER] to confirm the default path or enter the Oracle Installer setup.exe path (if different).

Press [ENTER] to confirm the default path or enter the TNMS.rsp file path (if differ-ent).

This action opens a new window. Wait until the Oracle Software installation finishes. The message Successfully Setup Software. Please press Enter to exit... is displayed. Press [ENTER] to close the window.

7 Choose option 2 - TNMS database creation. A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014 31

Installation Manual (IMN, Windows)Software prerequisites installation Press [ENTER] to confirm the default path or enter the template file path for your configuration:

TNMS_LW.dbt - large configuration. TNMS_MW.dbt - medium configuration. TNMS_SW.dbt - legacy configuration.

8 Type the SYS password and then retype it.Next, type the SYSTEM password and type it again.

Both SYS and SYSTEM passwords must be at least 5 characters long.

The TNMS database is created and the message Database created successfully is displayed.

If any failure occurs during the TNMS database creation, the message Error creating database. Check installation requirements is displayed. Look for errors in the log file indicated on the screen.

9 Choose option 3 - TNMS database configuration.Press [ENTER] to confirm the default path or enter the TNMSnetca.rsp file path.

Press [ENTER] to confirm the default path or enter the listener.ora file path.

The database is created and the message TNMS Database Configuration Successful. Oracle Installation finished is displayed.

10 Choose option 4 - Exit.The Oracle installation and configuration is completed. Restart the machine.

Post-installation verificationsIn order to verify the installations check the Oracle Services and the TNMS data-base:

1. Go to Start > Run and run the command services.msc.2. The following services should be started:

OracleOraDb11g_home1TNSListener OracleServiceTNMS (if the default database name was TNMS)

3. Run the application:\BIN\LSNRCTLand run the command status.

g is, by default, C:\oracle\product\11.2.0\dbhome_1\4. Check if your SID exists and if its status is READY:

Instance "tnms", status READY... (if the default database name was TNMS)

5.5.1 Uninstalling OracleTo uninstall the TNMS database and the Oracle software you must use the uninstallation tool provided by Oracle. Proceed as follows:

1. Go to Start > All Programs> Accessories > Command Prompt, opposite-click, select run as administrator and then enter the following command: 32 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014\deinstall\deinstall.bat

Installation Manual (IMN, Windows) Software prerequisites installation g is, by default, C:\oracle\product\11.2.0\dbhome_1\

The following steps describe a typical uninstallation procedure. In case the uninstallation tool requests you additional information, refer to the uninstallation tool documentation at: http://docs.oracle.com/cd/E11882_01/install.112/e16774/deinstall.htm.

2. When prompted for the Listener Name, enter LISTENER and press Enter.3. When prompted for the Oracle SID, enter TNMS and press Enter.4. When prompted for TNMS database modification, enter "n" and press Enter.

(The details of database(s) TNMS have been discovered automatically. Do you still want to modify the details of TNMS database(s)? [n]: n)

5. When prompted for continuation, enter "y" and press Enter.(Do you want to continue (y - yes, n - no)? [n]: y)

6. Wait until the uninstallation finishes and then restart the machine.7. Go to C:\ folder and delete the remaining folders and files.

C:\oracle \oradata (path chosen during installation)

5.6 OSI StackIf QB3 is to be used, an OSI stack must be installed on the NetServer PCs before the NetServer software.

5.6.1 Installing OSI StackTo install an OSI stack, proceed as follows:1. In the software DVD, go to the OSI_Stack directory, opposite-click setup.exe and

click Run as administrator.2. A welcome window is now displayed. Press Next to continue.3. In the Choose Destination Location window which is now displayed, a default

installation directory is offered for the OSI stack. Press Next to continue.4. In the Please select: window, select the NSAP address option best suited to your

companys network and press Next.5. In the Getting NSAP window, enter the NSAP address. For example, if you selected

the option NSAP should be derived from MAC address of my ethernet card on step 4., enter the MAC address of the network card and press Next.

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

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

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

5.6.2 Configuring OSI stackOnce finished the OSI stack installation and the computer rebooted, you need to proceed with the following set of configurations: A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014 33

Installation Manual (IMN, Windows)Software prerequisites installation 1. Open OSI stack as administrator via

Start > Control Panel > OSI Stack, right-click OSI Stack and select Run as admin-istrator. You may need to switch to the classic view or click View as small icons or use the search field for OSI Stack.

2. Activate the following options: Select In Bind to Network Interface Card and activate all network interfaces. In OpWin Configuration, activate "Open Stack, when Operator starts. Activate Start stack as service". Click ES-IS Stack parameter to enter the ES-IS configuration and disable

Enable emission of ES hello. Click Ok3. Exit the OSI Stack Configuration and reboot the machine in order to reset the vari-

ables properly, otherwise you may experience unexpected delays in the service readiness.

In case you have to check the environment variable OSIPIPE:

1. Click Start > Control panel > System and Security > System.2. Open the Advanced system settings > Advanced tab. 3. Click the button "Environment variables"4. In the lower list (user variables), search for OSIPIPE variable.5. The OSI stack configuration is finished.

5.6.3 Uninstalling OSI stackTo uninstall the OSI stack, follow the next steps:

1. Open Start > Control Panel > Administrative Tools > Services.2. Select the OSI stack service and press Stop.3. Open Start > Control Panel > Add/Remove Programs.4. Select the OSI stack from the software list.5. Click Uninstall.6. Confirm the uninstall process with Finish and restart your computer.

5.7 CopSSHCopSSH is a Secure Shell (SSH) File Transfer Protocol (SFTP) and Secure Copy (SCP) server used for transferring data to and from some types of NEs.

CopSSH installation is required for netservers only if there are hiT 7100, hiT 7300 or ADVA NEs in your network.

g SFTP / SCP use is recommended since it is more secure than FTP.

g In order to support SFTP or SCP transactions via the LCT, you must install and config-ure CopSSH in TNMS. 34 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014

Installation Manual (IMN, Windows) Software prerequisites installation 5.7.1 Installing CopSSH

To install CopSSH 4.7.1 proceed as follows (same procedure for all supported operating systems):

1. In the software DVD, go to the CopSSH directory, right-click the Copssh_4.7.1_x86_Installer.exe file and run as administrator

2. The setup wizards Welcome window is shown. Click Next.3. In the License Agreement window click I Agree.4. Enter an Installation folder or accept the default by clicking Next.5. Enter the service account credentials.6. You must select the user that will be used for the CopSSH account service manage-

ment, by choosing one of the following options: Keep the default CopSSH user: SvcCOPSSH (the installer generates a random

password). If you choose this option, keep that password for the future (recom-mended).

Or Select a new user (must be different from existing local machine users). In this

case you must provide a username and a password that matches the following requirements:- The username must be at least four characters in length.- Passwords cannot contain the users account name or parts of the users complete name exceeding two consecutive characters.- Passwords must be at least six characters in length.- Passwords must contain characters from three of the following four categories: English uppercase characters (A through Z). English lowercase characters (a through z). Base 10 digits (0 through 9). Non-alphabetical characters (for example: !, $, #, %).

Click Install.

7. Click Close to finish the installation.

5.7.2 Configuring CopSSHAs a security measure, CopSSHs default user cannot be used to access the machine. Therefore, new users must be created.

Configuring users in CopSSH:

1. Create a user with limited privileges in the operating system. This user will be used to perform the SFTP / SCP.

2. Grant the user write privileges on the C:\Program Files (X86)\ICW folder. Go to Properties, add the user created and give the user modify permissions.

3. Go to Start > Programs > CopSSH, opposite-click on CopSSH Control Panel and click Run as administrator.

4. In the Status tab, check if the service is running (green button). If not, click on the red button to start it.

5. Go to Users tab and click Add.6. Click Forward to begin the CopSSH User Activation wizard. A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014 35

Installation Manual (IMN, Windows)Software prerequisites installation 7. Choose the current machine for domain and the user you created earlier. Click

Forward.8. Select Shell access type:

For ADVA NEs, select Linux shell and Sftp. For hiT 7100 and/or hiT 7300 NEs, select Sftp. For ADVA and/or hiT 7300 NEs and/or hiT 7100 NEs, select Linux Shell and

Sftp.In the three options available, only Password authentication must remain checked. Uncheck the other two options Public key authentication and Allow TCP forwarding..Click Forward.

9. Click Apply to activate the user.Changing the default number of simultaneous sessionsThe following mandatory procedure is required in order to support multiple NE requests.

w Note that, if you run the CopSSH's Control Panel after the procedure below, all the changes to the passwd file will be reset.1. Edit the file C:\Program Files (x86)\ICW\etc\sshd_config

Below is a sample sshd_config file (after the CopSSH Control Panel has been run for the first time):

2. Change both MaxSessions values (lines 8 and 13) to 100. 3. Add the line MaxStartups 10:30:100 after line 8 to control the number of open

unauthenticated sessions. This avoids an overload of the SSH daemon.4. Below is the sample above after the changes:

Port 22Compression delayedLogLevel INFOTCPKeepAlive yesLoginGraceTime 120Protocol 2MaxAuthTries 6MaxSessions 10Subsystem sftp internal-sftp -l ERRORMatch User copuser

PasswordAuthentication yes PubkeyAuthentication no AllowTcpForwarding no MaxSessions 10

# Catch AllMatch User *

AllowTcpForwarding no MaxSessions 0 PasswordAuthentication no PubkeyAuthentication no 36 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014

Installation Manual (IMN, Windows) Software prerequisites installation

5. Save the sshd_config file and restart the CopSSH service using Windows Control Panel.

5.7.3 CopSSH TroubleshootingGo to Start > Programs > CopSSH > CopSSH Control Panel and in the Status tab, check that the CopSSH service is running (green color). If not:

1. Go to (Windows) Control panel > Administrative tools > Services. 2. Opposite-click the service "Openssh SSHD" and select Properties.3. In the Log On tab, select Local System account.4. Click OK.5. Start the Openssh service.

Check if the SFTP user is added to the password file:

1. Edit the file C:\Program Files (x86)\ICW\etc\passwd.It must contain the details of the SFTP user that was created and activated. For example, if the user name is FTPUser, the file will be:

Port 22Compression delayedLogLevel INFOTCPKeepAlive yesLoginGraceTime 120Protocol 2MaxAuthTries 6MaxSessions 100MaxStartups 10:30:100Subsystem sftp internal-sftp -l ERRORMatch User copuser

PasswordAuthentication yes PubkeyAuthentication no AllowTcpForwarding no MaxSessions 100

# Catch AllMatch User *

AllowTcpForwarding no MaxSessions 0 PasswordAuthentication no PubkeyAuthentication no A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014 37

Installation Manual (IMN, Windows)Software prerequisites installation

2. If the password file does not contain the details of the SFTP user, grant write access to the ICW folder to the Windows user that is used to install COPSSH.

5.7.4 CopSSH HardeningIf you wish to further restrict the CopSSH's user privileges by making connections via interactive shell impossible, do as follows:

w Note that, if you run the CopSSH's Control Panel after the procedure below, all the changes to the passwd file will be reset.1. Go to \etc\ and edit the passwd file.2. Edit the line (example) from

reguser:unused:11010:10513:reguser,U-TSVM41\TestPL,S-1-5-21-2769772405-123357289-3683661142-1010:/home/reguser:/bin/bashto(...):/bin/false

3. Save the file.

5.8 AntivirusTo protect TNMS against viruses, you should install F-Secure Client on all machines. Refer to the software release notes to see the released versions.

5.9 NTI third-party software installationThe NTI DS is a third-party software part of the TNMS prerequisites. You find the installer in the installation folder TNMS_Prerequisites > NTI_DS and it launches and controls the setup of this third-party software. The main setup also configures the software after the installation to work with TNMS.

This procedure is mandatory only if you want to have NTI operational. Otherwise, skip this procedure.

Administrator:unused:10500:10513:U-AUMELRD-TD-03\Administrator,S-1-5-21-3507081192-3007060136-515313314-500:/home/Administrator:/bin/bashFTPUser:unused:11021:10513:FTPUser,U-AUMELRD-TD-03\FTPUser,S-1-5-21-3507081192-3007060136-515313314-1021:/home/FTPUser:/bin/bashGuest:unused:10501:10513:U-AUMELRD-TD-03\Guest,S-1-5-21-3507081192-3007060136-515313314-501:/home/Guest:/bin/bashsshd:unused:11025:10513:U-AUMELRD-TD-03\sshd,S-1-5-21-3507081192-3007060136-515313314-1025:/var/empty:/bin/bashSvcCOPSSH:unused:11026:10513:U-AUMELRD-TD-03\SvcCOPSSH,S-1-5-21-3507081192-3007060136-515313314-1026:/var/:/bin/bash 38 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014

Installation Manual (IMN, Windows) Software prerequisites installation Installing the NTI third-party software:

1 Run the NTI_DS_Installer.exe file. Check the file in the folder TNMS_Prerequisites.2 Proceed as described in the setup windows. In the Welcome window, click Next.3 In the License Agreement window, choose I accept the terms of License Agree-

ment and click Next.

4 In the Choose Install Set window, click Next.Choose Full Installation as the installation type.

5 In the Directory Name (Default: C:/NTI_DS) window, enter the installation directory or select it from the Choose dialog and click Next.

6 In the Notification Service Configuration window, select one of the following options:

Contact with IMR on every server start-up: off (default option). Choose level of verbosity: fatal errors only (default option). Choose details for compact Typecodes: off (default option). Disable indirection encoding: on (default option). Please enter port number for Notification Service: 17289 (default option). Please choose maximum Java heap size for Notification Service: choose one

of the three available values. The default value is 256 MB.

Click Next.

7 In the Pre-Installation Summary window check if the installation options are correct and confirm by clicking Install.

8 In the Install Complete window, you see the message Your computer must be restarted to complete the installation. Click Finish.

9 After rebooting, proceed as follows: Go to \NoSe\bin and run the Object Viewer by double

clicking the manager.bat file. Locate the localhost of the OpenFusion object, right-click and then click Start

in the context menu. If already started, skip this step. This changes the state to Started.

Ensure the services are started through Start > Control Panel > Administrative Tools > Services.

The following services must exist and be in state Started.

JacORB IMR OpenFusion.NotificationService 4.2.3 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014 39

Installation Manual (IMN, Windows)Software prerequisites installation 40 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014

Installation Manual (IMN, Windows) TNMS installation 6 TNMS installation

This chapter describes the TNMS installation. If you have a previous TNMS version installed in your system, jump to 9 Upgrade to TNMS 14.1 10.Before you install TNMS be sure to read and follow the directions below. Failing to comply will result in a failed installation.

6.1 Full installationTo install TNMS Server, NetServer and Client in the same machine (full installation):

1. Copy all relevant priority updates into ...\TNMS Installer\PUs.2. Login on the operating system with a user that has administrative rights.3. Opposite-click the installation file in the TNMS SW CD and select Run as adminis-

trator (Figure 2).

Figure 2 How to set the TNMS installer to run with administrator rights in Windows 7 and Windows Server 2008.

The Introduction window opens and the complete list of installation steps is dis-played on the left pane.Click Next to continue.

4. Read the License Agreement and then select I accept the terms of the License Agreement.Click Next to continue.

5. In the Choose Install Set step, click Full to install all components in the machine.The available buttons describe the installation variants offered.Click Next to continue.

6. Select your type of hardware configuration: Medium, Large (see 2.2 Hardware requirements) or Legacy Hardware.Select Legacy Hardware to install TNMS Server in machines that meet the hardware requirements for TNMS 13.2 1x but not for TNMS 14.x xx.

g Optical Management is not supported in the Legacy Hardware configuration.7. A usage warning pops up to let you know that the database should not be in use by

any application.8. Select Build and click Next to continue.

w The Build option, if there is a previous TNMS version installed, will delete all the data in the database. To upgrade your installation, refer instead to the Upgrade Manual.

9. The Oracle database connection step asks you to enter a set of database connec-tion parameters: A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014 41 Database IP Address: the Oracle host IP address.

Installation Manual (IMN, Windows)TNMS installation Database port: the Oracle server port number. The default value is 1521. Database username: the user scheme of the database to be created (example:

TNMS).

g Using the same user / password in all installations is recommended since it ensures that the database is restorable in any machine. However another user / password can be used for security reasons, as long as you keep these data for future reference and you use the same user / password in the system where you perform the backup and the system where you restore it.

User password: the password for the DB user (example: fk12!igp).

g The password must meet the following requirements: Is at least four characters long. Differs from the user name. Has at least one alphabetic, one numeric and one punctuation characters. Is not simple or obvious, such as welcome, account, database, or user.

Re-enter user password: re-enter the password. Database name (SID): the name of the Oracle database (DB instance), which,

by default, is TNMS. User sys password: fill in with the password defined in 5.5 Oracle.Click Next to continue

10. In the Choose Components step: 10.1 Select the Managers to be installed.

w On Legacy hardware installations the Optical Manager will not be installed. To install and use the Optical Manager you must select the Medium or the Large configuration.

Mind that all managers can be installed but each requires a specific license to be used.Click Next to continue.

10.2 Select the North Bound Interface to install, if any.

g If you select TMF/Corba, you must have previously installed the NTI as described in 5.9 NTI third-party software installation.Click Next.

10.3 Select the LCTs to be installed. Click Next to continue.

10.4 Select the NEs to be installed and all their versions, for example:[X] hiT 7300 5.10.0x[X] hiT 7300 5.10.10[X] hiT 7300 5.10.2x[X] hiT 7300 5.30.50[X] hiT 7300 5.30.60Click Next to continue.

11. In the Choose Install Folder step: 11.1 Enter the path for the TNMS installation folder, the TNMS Data folder (see

note), the LCT installation folder and the EML Mediation installation folder. 42 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014

Installation Manual (IMN, Windows) TNMS installation Default paths are provided.Click Next to continue.

g Make sure that the TNMS Data folder is empty. If not, backup and remove the data or select a different folder.12. If CopSSH is not installed in the machine, a warning pops up to let you know that the

NetServer requires you to install it (see 5.7.1 Installing CopSSH)If CopSSH is already installed, you must provide a valid SFTP User, that is, a Windows user that was added to CopSSH (see 5.7.2).

g The user is not created again. The user mentioned in this step serves as a cross check with the user added in the CopSSH configuration (see 5.7.2 Configuring CopSSH).

13. In case you have more than one Network Interface Card (NIC) installed, the Choose host IP address panel is displayed providing a list of the IPs associated with each NIC.Click the pulldown menu and choose the IP that corresponds to the host name of the machine.In case you only have one NIC, this panel is not displayed and you must proceed to the next step.

14. Select the TNMS servers IP address (blank by default).Enter the TNMS servers IP address if you are installing the netserver on a machine other than the server (blank by default).Click Next to continue.

g This step is skipped in some cases, such as if the server has only one IP address.15. In the OpenDS Directory Server Configuration step set the following OpenDS

database server information:

g All fields except the Admin password, are automatically filled in. If not, cancel the installation wizard, complete the 4.6 System Hosts configuration and start the instal-lation once more.

Computer name: . Install directory: folder wherein the OpenDS server will be installed. Server port, Admin port: ports used respectively to communicate with OpenDS

Server and for administrative actions.The server and admin port numbers shown are default, not mandatory. You can use any port number from 1024 to 49151

Admin ID: default is admin. Admin password: select password (minimum 8 character). Re-enter Admin password: re-enter the selected password.Click Next to continue

16. In the Choose Shortcut Folder step configure the options of the icons and shortcuts to be created during installation. Click Next to continue.

17. Decide whether to have Coriants as your default desktop wallpaper. Click Next to continue. A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014 43

Installation Manual (IMN, Windows)TNMS installation 18. If one or more of the priority updates you copied into ..\TNMS Installer\PUs does not

comply with a set of preconditions a warning message is displayed (for additional information check 6.3 About the automatic priority updates installation).

w The PUs that generate warnings will not be installed.Click Next to continue or click Cancel to go back to the previous step.

19. A summary of the installation settings is given in the Pre-Installation Summary step. If the settings are correct, click Install to start the installation.

20. If an error, such as a corrupted PU file, is detected during the installation an error message is displayed (for additional information check 6.3 About the automatic priority updates installation).

21. The results of the installation are presented in the Installation Results step.Click Done to close the installation wizard.

22. Reboot the machine to complete the installation.After the TNMS Server has been installed and started, the system can be immediately operated by selecting the server name and using the default user name and password (see 7.3 Logging in and 7.4 Default username and password).

g A warning message may be displayed during the installation configuration stating that the firewall is enabled. However, if you use the Windows Firewall, in some cases, the firewall window displays the disabled status. Such contradiction arises due to the TNMS Installer use of the netsh adv commands to check the firewall status which can return a different status from that presented in the GUI. To configure the firewall refer to 12.3 Networking and firewall configuration.

g The TNMS installation creates the following services on the target machine after the full installation is completed: TNMS (automatically started). In the server machine. RCTSrv (automatically triggered off by TNMS and thus listed as Manual). In the

server machine. Open DS (automatically started). In the server machine. TNMS EmlMediator (automatically started). In the netserver machine. TNMS Generic Mediator (automatically started). In the netserver machine. TNMS TrapHandler (automatically started). In the netserver machine. TNMS Multivendor Mediator (automatically started). In the netserver machine. TNMS platform (automatically started). In the server machine.

6.2 Installation of separate componentsTo install only one of the components or a specific combination of components you must follow the procedure described in the previous section until step 5. In this step choose Client, Server, NetServer, Server and NetServer or Server and Client. The subsequent steps are a subset of those described in 6.1 Full installation. However, note that:

If you install the TNMS Client and/or the Netserver on Windows 7, go to Start > Control Panel > System > Advanced System Settings > Advanced tab > Perfor-mance pane > Settings button > Visual Effects tab and select the option adjust for best performance. 44 A50023-K2035-X040-05-76D1Issue: 5 Issue date: July 2014

Installation Manual (IMN, Windows) TNMS installation If you install the TNMS Netserver in a machine other than the Server, the TNMS

Servers IP address is requested during the installation.If you install the TNMS Netserver in the same machine as the Server, the TNMS Servers IP address is requested only if the server has more than one IP address.

6.3 About the automatic priority updates installationYou can install priority updates (PU) either manually, anytime after installing TNMS, or automatically, while installing TNMS. The automatic procedure includes several verif