TransNav Management System Documentation. Management Server Guide

Transcription

1 Turin Networks Inc. TransNav Management System Documentation Management Server Guide Release TN3.1.x Publication Date: March 2007 Document Number: TN31 Rev. A

2 FCC Compliance This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the installation instructions may cause harmful interference to radio communications. Canadian Compliance This Class A digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations. Cet appareil numérique de la classe A respects toutes les exigences du Règlement sur le matériel brouilleur du Canada. Japanese Compliance This is a Class A product based on the standard of the Voluntary Control Council for Interference by Information Technology Equipment (VCCI). If this equipment is used in a domestic environment, radio disturbance may occur, in which case, the user may be required to take corrective actions. International Declaration of Conformity We, Turin Networks, Inc. declare under our sole responsibility that the Traverse platform (models: Traverse 2000, Traverse 1600, and Traverse 600) to which this declaration relates, is in conformity with the following standards: EMC Standards EN55022 EN55024 CISPR-22 Safety Standards EN60950 CSA 22.2 No , ASINZS 3260 IEC Third Edition. Compliant with all CB scheme member country deviations. Following the provisions of the EMC Directive 89/336/EEC of the Council of the European Union. Copyright 2007 Turin Networks, Inc. All rights reserved. This document contains proprietary and confidential information of Turin Networks, Inc., and may not be used, reproduced, or distributed except as authorized by Turin Networks. No part of this publication may be reproduced in any form or by any means or used to make any derivative work (such as translation, transformation or adaptation) without written permission from Turin Networks, Inc. Turin Networks reserves the right to revise this publication and to make changes in content from time to time without obligation on the part of Turin Networks to provide notification of such revision or change. Turin Networks may make improvements or changes in the product(s) described in this manual at any time. Turin Networks Trademarks Turin Networks, the Turin Networks logo, Traverse, TraverseEdge, TransAccess, TransNav, and Creating The Broadband Edge are trademarks of Turin Networks, Inc. or its affiliates in the United States and other countries. All other trademarks, service marks, product names, or brand names mentioned in this document are the property of their respective owners. Government Use Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in FAR (Commercial Computer Software-Restricted Rights) and DFAR (Rights in Technical Data and Computer Software), as applicable.

3 TRANSNAV MANAGEMENT SYSTEM SERVER GUIDE Contents About this Document iii Section 1 Installation and Description Chapter 1 Installation for Solaris Workstations Chapter 2 Installation for Windows Workstations Chapter 3 Management Server Administration Section 2 Management Server s Chapter 1 Creating the Management Servers Chapter 2 Management Server SNMP Chapter 3 Server Administration s Index Index-1 Release TN3.1.x Turin Networks Page i

4 Page ii Turin Networks Release TN3.1.x

5 Server Guide [TN3.1.x] Document Description About this Document Introduction Traverse System Product Documentation This description contains the following documentation topics: Traverse System Product Documentation, page iii TraverseEdge System Product Documentation, page iv TransNav Management System Product Documentation, page v Operations Documentation, page vi Information Mapping, page vi If You Need Help, page vii Calling for Repairs, page vii Refer to What s New in the Documentation? to review the new and changed features for this release. The Traverse TM system product documentation set includes the documents described in the table below. Traverse System Product Documentation Document Description Target Audience Traverse Product Overview Traverse Installation and Configuration Traverse Provisioning This document provides a detailed overview of the Traverse system. It also includes engineering and planning information. This document provides required equipment, tools, and step-by-step procedures for: Hardware installation Power cabling Network cabling Node power up Node start-up This document provides step-by-step procedures for provisioning a network of Traverse nodes using the TransNav management system. See the TransNav Management System Product Documentation. Anyone who wants to understand the Traverse system and its applications. Installers, field, and network engineers Network engineers, provisioning, and network operations center (NOC) personnel Release TN3.1.x Turin Networks Page iii

6 TraverseEdge System Product Documentation TraverseEdge System Product Documentation The TraverseEdge 100 TM User Guide includes the sections described in the table below. TraverseEdge 100 System Product Documentation Section Description Target Audience Product Overview Description and Specifications Installation and Configuration Provisioning the Network Configuring Equipment Creating TDM Services Creating Ethernet Services Appendices This section provides a detailed overview of the TraverseEdge system. This section includes engineering and planning information. This document identifies required equipment and tools and provides step-by-step procedures for: Hardware installation Power cabling Network cabling Node power up Node start-up This section provides step-by-step procedures for provisioning a TraverseEdge network using the TransNav management system. Also see the TransNav Management System Product Documentation. This section provides step-by-step procedures for configuring module and interface parameters of a TraverseEdge using the TransNav management system. Also see the TransNav Management System Product Documentation. This section provides step-by-step procedures for provisioning a TraverseEdge network using the TransNav management system. Also see the TransNav Management System Product Documentation. This section provides step-by-step procedures for provisioning a TraverseEdge network using the TransNav management system. See the TransNav Management System Product Documentation. This section provides installation and provisioning checklists, compliance information, and acronym descriptions. Anyone who wants to understand the TraverseEdge system and its applications Field and network engineers Installers, field, and network engineers Network engineers, provisioning, and network operations center (NOC) personnel Network engineers, provisioning, and network operations center (NOC) personnel Network engineers, provisioning, and network operations center (NOC) personnel Network engineers, provisioning, and network operations center (NOC) personnel Installers and anyone who wants reference information. Page iv Turin Networks Release TN3.1.x

7 TransNav Management System Product Documentation TransNav Management System Product Documentation The TransNav TM management system product documentation set includes the documents described in the table below. TransNav Management System Product Documentation Document Description Target Audience TransNav Management System Product Overview TransNav Management System Server Guide TransNav Management System GUI Guide This document provides a detailed overview of the TransNav management system. This document includes hardware and software requirements for the management system. It also includes network management planning information. This document describes the management server component of the management system and provides procedures and troubleshooting information for the server. This document describes the graphical user interface including installation instructions and logon procedures. Anyone who wants to understand the TransNav management system Field and network engineers, provisioning, and network operations center (NOC) personnel TransNav Management System CLI Guide TransNav Management System TL1 Guide This document describes every menu, window, and screen a user sees in the graphical user interface. This document includes a quick reference to the command line interface (CLI). Also included are comprehensive lists of both the node-level and domain-level CLI commands. This document describes the syntax of the TL1 language in the TransNav environment. This document also defines all input commands and expected responses for retrieval commands as well as autonomous messages that the system outputs due to internal system events. Release TN3.1.x Turin Networks Page v

8 Operations Documentation Operations Documentation The document below provides operations and maintenance information for Turin s TransNav managed products. Operations Documentation Document Description Target Audience Node Operations and Maintenance This document identifies required equipment and tools. It also provides step-by-step procedures for: Alarms and recommended actions Performance monitoring Equipment LED and status Diagnostics Test access (SONET network only) Routine maintenance Node software upgrades Node hardware upgrades Field and network engineers Information Mapping Traverse, TransNav, and TraverseEdge 100 system documentation uses the Information Mapping format which presents information in small units or blocks. The beginning of an information block is identified by a subject label in the left margin; the end is identified by a horizontal line. Subject labels allow the reader to scan the document and find a specific subject. Its objective is to make information easy for the reader to access, use, and remember. Each procedure lists the equipment and tools and provides step-by-step instructions required to perform each task. Graphics are integrated into the procedures whenever possible. Page vi Turin Networks Release TN3.1.x

9 If You Need Help If You Need Help Calling for Repairs If you need assistance while working with Traverse products, contact the Turin Networks Technical Assistance Center (TAC): Inside the U.S., toll-free: TURINET ( ) Outside the U.S.: Online: TAC is available 6:00AM to 6:00PM Pacific Time, Monday through Friday (business hours). When the TAC is closed, emergency service only is available on a callback basis. support (24-hour response) is also available through: [email protected]. If repair is necessary, call the Turin Repair Facility at TURINET ( ) for a Return Material Authorization (RMA) number before sending the unit. The RMA number must be prominently displayed on all equipment cartons. The Repair Facility is open from 6:00AM to 6:00PM Pacific Time, Monday through Friday. When calling from outside the United States, use the appropriate international access code, and then call to contact the Repair Facility. When shipping equipment for repair, follow these steps: 1. Pack the unit securely. 2. Enclose a note describing the exact problem. 3. Enclose a copy of the invoice that verifies the warranty status. 4. Ship the unit PREPAID to the following address: Turin Networks, Inc. Turin Repair Facility Attn: RMA # 1415 North McDowell Blvd. Petaluma, CA USA Release TN3.1.x Turin Networks Page vii

10 Calling for Repairs Page viii Turin Networks Release TN3.1.x

11 SECTION 1INSTALLATION AND DESCRIPTION SECTION 1 INSTALLATION AND DESCRIPTION Contents Chapter 1 Installation for Solaris Workstations Introduction Before You Install Server Software Install Server Software on a Solaris Workstation Run the Server as a Daemon Install Server Online Help Files on a Solaris Workstations Install Help Files from CD (Solaris) Install Help Files from Your Customer Portal (Solaris) Remove Server Software from Solaris Workstation Chapter 2 Installation for Windows Workstations Introduction Before You Install Server Software Install Server Software on a Windows Workstation Install Server Online Help Files on a Windows Workstations Install Help Files from CD (Windows) Install Help Files from Your Customer Portal (Windows) What is the All-In-One Online Help System? Uninstall Server Software from Windows Workstation Chapter 3 Management Server Administration Introduction Using Multiple Servers Server Administration Tool Description Server Administration Components Description Management Server Parameters List of Figures Figure 1-1 Window Menu Button Figure 1-2 EMS & FLASH Downloads Link Figure 1-3 All-In-One Online Help Download Link Sample Figure 1-4 Save As Dialog Box Figure 1-5 Window Menu Button Figure 1-6 Executive File in Explorer Window Figure 1-7 Management Server Installer Wizard Release TN3.1.x Turin Networks Page ix

12 TransNav Server Guide, Section 1 Installation and Description Figure 1-8 Close Button Icon Figure 1-9 EMS & FLASH Downloads Link Figure 1-10 All-In-One Online Help Download Link Sample Figure 1-11 File Download Dialog Box Figure 1-14 Server Uninstall Wizard Figure 1-15 Server Admin Tool Figure 1-16 Execution Configuration Dialog Box List of Tables Table 1-1 Before You Create the Management Server Table 1-2 Install Server Software on a Solaris Workstation Table 1-3 Run the Server as a Daemon Table 1-4 Install Help Files from CD (Solaris) Table 1-5 Install Help Files from Your Customer Portal (Solaris) Table 1-6 Remove Server Software from Solaris Workstation Table 1-7 Before You Install the Management Server Table 1-8 Install Server Software on a Windows Workstation Table 1-9 Install Help Files from CD (Windows) Table 1-11 Uninstall Server Software from Windows Workstation SECTION 1 Page x Turin Networks Release TN3.1.x

13 SECTION 1INSTALLATION AND DESCRIPTION Chapter 1 Installation for Solaris Workstations Introduction Before You Install Server Software You can use the TransNav management system on either a Solaris or a Windows workstation. This chapter provides instructions on how to install management system software on the Sun Solaris workstation. Before You Install Server Software, page 1-1 Install Server Software on a Solaris Workstation, page 1-2 Run the Server as a Daemon, page 1-3 Install Server Online Help Files on a Solaris Workstations, page 1-5 Install Help Files from the Turin Infocenter, page 1-7 Remove Server Software from Solaris Workstation, page 1-10 See Chapter 2 Installation for Windows Workstations, page 1-11 for the procedures to install the management system on a Windows workstation. Before you install the management server software, understand the following requirements. Table 1-1 Before You Install the Management Server Software Requirement Disable any operating system firewall applications that may be installed on this computer. Server requirements Server software includes the GUI application Server administration procedures Reference Contact your local site administrator. TransNav Management System Product Overview, Section 2 Management System Planning, Chapter 1 TransNav Management System Requirements, page 2-1 You can use either the GUI or CLI interface on the same computer you are using as a management server. These applications are installed at the same time you install the server software. For information on downloading the server software, refer to Section 2 Management Server s, Chapter 3 Server Administration s, Download the TransNav Management Software from the Turin Infocenter.. See Section 2 Management Server s for detailed procedures on initializing, starting, stopping, and maintaining the TransNav management server. Release TN3.1.x Turin Networks Page 1-1

14 TransNav Server Guide, Section 1: Installation and Description Install Server Software on a Solaris Workstation Install Server Software on a Solaris Workstation Use this procedure to install the management server software on a Solaris workstation. Table 1-2 Install Server Software on a Solaris Workstation Important: You must install and start the server software with the same user name. The user should be a non-root user (i.e., not be the super user). 1 Read the topic Before You Install Server Software, page 1-1 before you start this procedure. 2 On your Solaris system, ensure the Turin system software CD is inserted in the CD-ROM drive, the drive is mounted, and that the drive can be accessed by the current user. The mounting procedure is site-specific. For any required help with this procedure, contact your local UNIX administrator. 3 Open a terminal window and create a user-defined directory according to local site practices. Important: The user who is going to be the EMS server administrator must have read, write, and execute permissions to this new directory. For example: $ mkdir /files/ems 4 Change to the directory you created in 3. For example: $ cd /files/ems 5 Type the following command to unzip and untar the server software in one step. For example: $ gunzip -c/cdrom/*.gz tar xvf - This particular example assumes /cdrom is the mountpoint for the CD. Change the syntax accordingly to your local setup. The spaces, the pipe character ( ) and the dash (-) must be typed exactly as shown. Important: The user who unzips the *.gz file will have the permissions on the directory files necessary to run the EMS server. To change permissions, contact your local UNIX administrator. 6 The Install Server Software on a Solaris Workstation procedure is complete. Continue to the next procedure: Run the Server as a Daemon, page 1-3. Page 1-2 Turin Networks Release TN3.1.x

15 Chapter 1 Installation for Solaris Workstations Run the Server as a Daemon Run the Server as a Daemon Use this procedure to allow the server to restart on the workstation in case the workstation turns off or power cycles. This daemon restarts the server when the workstation starts again. Important: You need Root access to the workstation on which the server is installed. Table 1-3 Run the Server as a Daemon 1 Complete the procedure: Install Server Software on a Solaris Workstation, page In the directory where the TransNav software is installed, switch to the Root user. Enter $ su Enter the password for the Root user. 3 At the command line, enter: #./ems_installdaemon.sh -u <username> -d <directoryname> where: username is the name by which the user logs onto the workstation. directoryname is the name of the directory in which the management server software is installed. 4 Verify the information is correct when the system responds: This script will install the EMS as a daemon on this machine. The EMS will then be started automatically every time this machine boots. Setup configuration: user: <username> User that will run EMS processes (use -u <user> to change) dir: <directoryname> Directory where EMS was installed (use -d <directory> to change) Do you wish to proceed? ([yes] no) 5 Enter Y to continue the installation. Release TN3.1.x Turin Networks Page 1-3

16 TransNav Server Guide, Section 1: Installation and Description Run the Server as a Daemon Table 1-3 Run the Server as a Daemon (continued) 6 The system responds: # Creating /etc/ems.conf... done # Creating /etc/init.d/ems... done # Setting start links for runlevels done # Setting kill links for runlevels done Installation complete. 7 The Run the Server as a Daemon procedure is complete. Continue to Install Server Online Help Files on a Solaris Workstations, page 1-5. Page 1-4 Turin Networks Release TN3.1.x

17 Chapter 1 Installation for Solaris Workstations Install Help Files from CD (Solaris) Install Server Online Help Files on a Solaris Workstations Install Help Files from CD (Solaris) To learn more about the All-In-One, see What is the All-In-One Online Help System?, page Select one of these access points to: Install Help Files from CD (Solaris) Install Help Files from the Turin Infocenter Use this procedure to install help files from the documentation CD to the management server on a Solaris workstation. Table 1-4 Install Help Files from CD (Solaris) 1 On your Solaris workstation, ensure the CD is inserted into the CD-ROM drive, the drive is mounted, and that the drive can be accessed by the current user. The mounting procedure is site-specific. For any required help with this procedure, contact your local UNIX administrator. 2 Open a terminal window and change directory to the management server online help directory. Important: The user who is going to be the management server administrator must have read and write permissions to this directory. For example: $ cd <server_home>/ems/help where: <server_home> is the user-defined directory assigned during the management server software installation (e.g., /server). EMS/help is the system-defined directory assigned during the management server software installation. Release TN3.1.x Turin Networks Page 1-5

18 TransNav Server Guide, Section 1: Installation and Description Install Help Files from CD (Solaris) Table 1-4 Install Help Files from CD (Solaris) (continued) 3 Type this command to download and install the help files into the management server online help directory. Important: The user who unzips the file will have the permissions on these files. To change permissions, contact your local UNIX administrator. Using the: documentation CD: $ unzip /cdrom/download/allinone<releasenumber>.zip. software CD: $ unzip /cdrom/allinone<releasenumber>.zip. where: allinone.zip is the source file containing the online help files. the target directory. symbol is known as a dot and represents the current directory. Note: This particular example assumes /cdrom is the mountpoint for the CD. Change the source directory syntax accordingly to your local setup. The spaces and dots must be typed exactly as shown. 4 In the GUI TransNav Help window, from the file menu displayed through the button at the upper left corner of the window choose Close to close the window. Window menu button Figure 1-1 Window Menu Button 5 From the GUI File menu, choose Exit to exit the application. 6 Restart the GUI application to access the new online help. Note: If you require assistance to restart the GUI, see the TransNav Management System GUI Guide, Section 1 Installation and Overview, Chapter 3 Starting the Graphical User Interface, page The Install Help Files from CD (Solaris) procedure is complete. Continue to the server procedures in Section 2 Management Server s. Page 1-6 Turin Networks Release TN3.1.x

19 Chapter 1 Installation for Solaris Workstations Install Help Files from the Turin Infocenter Install Help Files from the Turin Infocenter Use this procedure to install help files from the Turin Infocenter to the management server on a Solaris workstation. Important: User registration is required to access the Turin Infocenter. If you do not have a current CustomerID and password, contact your sales account team to register. Table 1-5 Install Help Files from the Turin Infocenter 1 On your Solaris workstation, open an internet browser window. 2 In the Address bar, enter the address: 3 In the Turin Infocenter login (located in the bottom left corner of the Turin Networks Infocenter webpage), enter the <username> and <password> provided by the Turin webmaster and click OK to enter your site. 4 In the customer portal, click the Technical Documentation drop-down menu and select the Turin Traverse User Documentation link to open an index page. a Figure 1-2 Turin Traverse User Documentation Index a. Locate and click the All-in-One Documentation download link that corresponds to your current TransNav management system release base. Release TN3.1.x Turin Networks Page 1-7

20 TransNav Server Guide, Section 1: Installation and Description Install Help Files from the Turin Infocenter Table 1-5 Install Help Files from the Turin Infocenter (continued) 5 In the Save As dialog box, navigate to a temporary directory (e.g., <user_directory>), and click OK to save the zip file. Figure 1-3 Save As Dialog Box 6 Open a terminal window and change directory to the management server online help directory. Important: The user who is going to be the management server administrator must have read and write permissions to this directory. For example: $ cd <server_home>/ems/help Where: <server_home> is the user-defined directory assigned during the management server software installation (e.g., /server). EMS/help is the system-defined directory assigned during the management server software installation. Page 1-8 Turin Networks Release TN3.1.x

21 Chapter 1 Installation for Solaris Workstations Install Help Files from the Turin Infocenter Table 1-5 Install Help Files from the Turin Infocenter (continued) 7 Type this command to download and install the source online help files into the target management server online help directory. Important: The user who unzips the file will have the permissions on these files. To change permissions, contact your local UNIX administrator. $ unzip <user_directory>/<releasenumber>_allinone.zip. Where: <user_directory> is the user-defined directory containing the zip file. <ReleaseNumber> is the version of the allinone file that corresponds to your current TransNav management system release base. allinone.zip is the source file containing the online help files. the target directory. symbol is known as a dot and represents the current directory. 8 In the GUI TransNav Help window, from the file menu displayed through the button at the upper left corner of the window choose Close to close the window. Window menu button Figure 1-4 Window Menu Button 9 From the GUI File menu, choose Exit to exit the application. 10 Restart the GUI application to access the new online help. Note: If you require assistance to restart the GUI, see the TransNav Management System GUI Guide, Section 1 Installation and Overview, Chapter 3 Starting the Graphical User Interface, page The Install Help Files from the Turin Infocenter procedure is complete. Continue to the server procedures in Section 2 Management Server s. Release TN3.1.x Turin Networks Page 1-9

22 TransNav Server Guide, Section 1: Installation and Description Remove Server Software from Solaris Workstation Remove Server Software from Solaris Workstation You many want to remove older versions of the server software to create space on the computer. Use this procedure to remove a previous version of the server software from a Solaris workstation. Table 1-6 Remove Server Software from Solaris Workstation 1 Perform the software upgrade. See Server Software Upgrade, page Ensure that the server is stopped. See Stop the Server, page Open a terminal window and change to the directory where the older version of the management server software is installed. 4 Remove the directory and all files and directories beneath it. For example: rm -rf DirectoryName Where: DirectoryName is the name of the directory where you installed the management system software. 5 The Remove Server Software from Solaris Workstation procedure is complete. Page 1-10 Turin Networks Release TN3.1.x

23 SECTION 1INSTALLATION AND DESCRIPTION Chapter 2 Installation for Windows Workstations Introduction Before You Install Server Software You can use the TransNav management system on either a Solaris or a Windows workstation. This chapter provides instructions on how to install management system software on the Windows workstation. Before You Install Server Software, page 1-11 Install Server Software on a Windows Workstation, page 1-12 Install Server Online Help Files on a Windows Workstation, page 1-13 What is the All-In-One Online Help System?, page 1-18 Uninstall Server Software from Windows Workstation, page 1-18 See Chapter 1 Installation for Solaris Workstations, page 1-1 for the procedures to install the management server on a Sun Solaris workstation. Before you install the management server software, understand the following requirements. Table 1-7 Before You Install the Server Software Requirement Disable any operating system anti-virus and firewall applications that may be installed on this computer. Server requirements Server software includes user interface applications. Reference Contact your local site administrator. TransNav Management System Product Overview, Section 2 Management System Planning, Chapter 1 TransNav Management System Requirements, page 2-1. You can use the user interface (either GUI, CLI, or TL1) on the same computer you are using as a management server. These applications are installed at the same time you install the server software. For information on downloading the server software, refer to Section 2 Management Server s, Chapter 3 Server Administration s, Download the TransNav Management Software from the Turin Infocenter. Release TN3.1.x Turin Networks Page 1-11

24 TransNav Server Guide, Section 1: Installation and Description Install Server Software on a Windows Workstation Table 1-7 Before You Install the Server Software (continued) Requirement Software upgrade Server administration procedures Reference If this is a software upgrade, ensure that the server is disabled as a service. See Section 2 Management Server s, Disable the Server as a Service (Windows), page See Section 2 Management Server s for detailed procedures on initializing, starting, stopping, and maintaining the TransNav management server. Install Server Software on a Windows Workstation Use this procedure to install the TransNav management system on a Windows workstation. Table 1-8 Install Server Software on a Windows Workstation Important: To install the server software on a Windows workstation, the WindowsXP administrator must have an English language account name for the TransNav management system to function properly. 1 Read the topic Before You Install Server Software, page 1-11 before you start this procedure. 2 Insert the software CD into the CD drive on the PC. 3 In a Windows Explorer window, navigate to the correct CD drive. 4 Double-click the file PCSetup.exe to start the installation process. Figure 1-5 Executive File in Explorer Window Page 1-12 Turin Networks Release TN3.1.x

25 Chapter 2 Installation for Windows Workstations Install Help Files from CD (Windows) Table 1-8 Install Server Software on a Windows Workstation (continued) 5 The Installer Wizard appears. Figure 1-6 Management Server Installer Wizard Follow the on-screen directions until the management server software is installed on your computer. 6 The Install Server Software on a Windows Workstation procedure is complete. Continue to Install Server Online Help Files on a Windows Workstation, page Install Server Online Help Files on a Windows Workstation Install Help Files from CD (Windows) To learn more about the All-In-One, see What is the All-In-One Online Help System?, page Select one of these access points to: Install Help Files from CD (Windows) Install Help Files from the Turin Infocenter Use this procedure to install help files from the documentation CD to the management server on a Windows workstation. Table 1-9 Install Help Files from CD (Windows) 1 On your Windows workstation, insert the documentation CD into the CD-ROM drive. 2 In an Explorer window, navigate to the correct CD-ROM drive (e.g., D: drive). Release TN3.1.x Turin Networks Page 1-13

26 TransNav Server Guide, Section 1: Installation and Description Install Help Files from CD (Windows) Table 1-9 Install Help Files from CD (Windows) (continued) 3 At the drive s top-level directory (e.g., D:\), double-click the Download directory to change directories, then double-click the <ReleaseNumber>allinone.zip file to open it. Where: <ReleaseNumber> is the version of the allinone file that corresponds to your current TransNav management system release base. allinone.zip is the source file containing the online help files. 4 From the zip tool Actions menu, choose Extract to extract the contents of the zip file. 5 In the Extract dialog box: a. Select Files, then All Files to extract all the zip files. b. Use the Folders/drives window to navigate to the management server online help directory, and click Extract to download the help files. The online help directory path is: <server_home>\ems\help Where: <server_home> is the user-defined directory where the management server software is installed (e.g., C:\server). 6 In the Confirm File Overwrite dialog box, click Yes to All. 7 From the zip tool File menu, choose Exit to exit the application. 8 From the GUI TransNav Help window, click the Close button in the upper right corner of the window to close the window. Close button Figure 1-7 Close Button Icon 9 From the GUI File menu, choose Exit to exit the application. 10 Restart the GUI application to access the new online help. Note: If you require assistance to restart the GUI, see the TransNav Management System GUI Guide, Section 1 Installation and Overview, Chapter 3 Starting the Graphical User Interface, page The Install Help Files from CD (Windows) procedure is complete. Continue to the server administration procedures in Section 2 Management Server s. Page 1-14 Turin Networks Release TN3.1.x

27 Chapter 2 Installation for Windows Workstations Install Help Files from the Turin Infocenter Install Help Files from the Turin Infocenter Use this procedure to install help files from the Turin Infocenter to the management server on a Windows workstation. Important: User registration is required to access the Turin Infocenter. If you do not have a current CustomerID and password, contact your sales account team to register. Table1-10 Install Help Files from the Turin Infocenter 1 On your Windows workstation, open an internet browser window. 2 In the Address bar, enter the address: 3 In the Turin Infocenter login (located in the bottom left corner of the Turin Networks Infocenter webpage), enter the <username> and <password> provided by the Turin webmaster and click OK to enter your site. Figure 1-8 Infocenter Login Screen Release TN3.1.x Turin Networks Page 1-15

28 TransNav Server Guide, Section 1: Installation and Description Install Help Files from the Turin Infocenter Table 1-10 Install Help Files from the Turin Infocenter (continued) (continued) 4 In the customer portal, click the Technical Documentation drop-down menu and select the Turin Traverse User Documentation link to open an index page. a Figure 1-9 Turin Traverse User Documentation Index a. Locate and click the All-in-One Documentation download link that corresponds to your current TransNav management system release base. 5 In the File Download dialog box, click Save to save the zip file to a temporary directory of your choice (e.g., <user_directory>). Figure 1-10 File Download Dialog Box Page 1-16 Turin Networks Release TN3.1.x

29 Chapter 2 Installation for Windows Workstations Install Help Files from the Turin Infocenter Table 1-10 Install Help Files from the Turin Infocenter (continued) (continued) 6 In the Save As dialog box, navigate to the <user_directory> and click Save to save the zip file. 7 From the <user_directory>, double-click the <ReleaseNumber>allinone.zip file to open it. 8 From the zip tool Actions menu, choose Extract to extract the contents of the zip file. 9 In the Extract dialog box: a. Select Files, then All Files to extract all the zip files. b. Use the Folders/drives window to navigate to the management server online help directory. Click Extract to download the help files. The online help directory path is: <server_home>\ems\help Where: <server_home> is the user-defined directory where the management server software is installed (e.g., C:\server). 10 In the Confirm File Overwrite dialog box, click Yes to All. 11 From the zip tool File menu, choose Exit to exit the application. 12 From the GUI TransNav Help window, click the Close button in the upper right corner of the window to close the window. Close button Figure 1-11 Close Button 13 From the GUI, select File, then Exit to exit the application. 14 Restart the GUI application to access the new online help. Note: If you require assistance to restart the GUI, see the TransNav Management System GUI Guide, Section 1 Installation and Overview, Chapter 3 Starting the Graphical User Interface, page The Install Help Files from Your Customer Portal (Windows) procedure is complete. Continue to the server administration procedures in Section 2 Management Server s. Release TN3.1.x Turin Networks Page 1-17

30 TransNav Server Guide, Section 1: Installation and Description What is the All-In-One Online Help System? What is the All-In-One Online Help System? Each software and documentation CD includes the (HTML-based) All-In-One Documentation, which is also the basis for the management system software online help mechanism. The All-In-One online help system (i.e., the All-In-One Documentation) provides access to the complete documentation set and includes the following guides: Figure 12 All-In-One Online Help System Contents The table of contents seen here makes it convenient to view pages from any guide. You can also click the following tabs: Index: This tab displays a fully integrated index of all guides. Search: This tab contains a search text box that allows you to enter any word or group of words. You can choose to search these words in one guide or across all guides. Uninstall Server Software from Windows Workstation After upgrading the server software, you may want to remove the previous version. On a Windows workstation, the uninstall process uses a wizard similar to the Installer Wizard. After you have opened the Uninstaller Wizard, follow the on-screen directions to remove the server software from your computer. Table 1-11 Uninstall Server Software from Windows Workstation 1 Perform the software upgrade. See Server Software Upgrade, page Ensure that the server is stopped. See Stop the Server, page From the Start menu, select Programs > Turin_Networks> Uninstall TransNav Management System. Page 1-18 Turin Networks Release TN3.1.x

31 Chapter 2 Installation for Windows Workstations Uninstall Server Software from Windows Workstation Table 1-11 Uninstall Server Software from Windows Workstation (continued) 4 The Uninstaller Wizard appears. Figure 1-13 Server Uninstall Wizard Follow the on-screen directions until the server software is removed from your computer. 5 In a Windows Explorer window, navigate to the directory where the application was installed. Remove the remaining files. 6 The Uninstall Server Software from Windows Workstation procedure is complete. Release TN3.1.x Turin Networks Page 1-19

32 TransNav Server Guide, Section 1: Installation and Description Uninstall Server Software from Windows Workstation Page 1-20 Turin Networks Release TN3.1.x

33 SECTION 1INSTALLATION AND DESCRIPTION Chapter 3 Management Server Administration Introduction Using Multiple Servers This chapter provides a brief overview of how multiple servers function in a Traverse and TraverseEdge 100 network. It also describes the TransNav management server administration tool, the management server components, and the configurable parameters for the server. Using Multiple Servers, page 1-21 Server Administration Tool Description, page 1-22 Server Administration Components Description, page 1-23 Management Server Parameters, page 1-24 The Traverse management system allows up to eight servers to be connected in the network. One server, designated the Primary server, actively manages the network. The remaining seven, or Secondary, servers, can passively view the network but cannot perform any management operations that would change the state of the network. Primary servers maintain all of the network-level information used to synchronize network elements such as alarm, PM templates, Ethernet bandwidth profiles, and classifiers. The Primary server also maintains local server information including customer records, Domain Users, report templates and schedules, alarm acknowledgements, and annotations. Secondary servers automatically collect current provisioning, service state, alarm and event information from all network elements in the domain, however, they do not collect and store PM data in the database. Users can, however, retrieve the PM data from the agent. Each Secondary server can perform the following functions: Provision and display domain users and functional groups Provision and display user preferences for domain users Display and maintain current information about network elements and services Display and log alarms and events Establish Node CLI sessions to any node in the domain Establish a connection to an NMS via a northbound interface Respond to read requests Forward alarms Release TN3.1.x Turin Networks Page 1-21

34 TransNav Server Guide, Section 1: Installation and Description Server Administration Tool Description To keep Secondary servers current, the Primary server database should be periodically exported and imported to the Secondary servers. Exporting the Primary server database will include all alarm and event information. Reports can be run to collect performance monitoring data. The reports can then be retained on a file server that is widely accessible. Server Administration Tool Description The server administration tool is a basic user interface designed to make server tasks easier. Start the server administration tool (see Section 2 Management Server s, Chapter 1 Creating the Management Servers, Start the Server Administration Tool, page 2-2). The Server Admin window appears. Figure 1-14 Server Admin Tool Page 1-22 Turin Networks Release TN3.1.x

35 Chapter 3 Management Server Administration Server Administration Components Description Server Administration Components Description The Server Administration tool allows you to view the status of each component of the management server. The function of each component is as follows: RMI Registry: Repository of references on the server components. Database: Object repository. Apache: Web server that provides access to the GUI applet. Event: Event object repository. Alarm: Alarm object repository. Topology: Configuration object repository. MBean: Configuration object repository. Configuration: Configuration object repository. Administration: Provides administrative functions to the other server components. Map: Maintains the network symbols for the graphical user interface. Network: Controls network objects such as templates. PreProvisioning: Maintains all the preprovisioned objects. Report: Schedules report generation and deletion. JDMKGateway: Interfaces between the EMS and the agents. Discovery: Uses the uploaded topology information to start the management of newly added agents. Performance Collection: Maintains the performance data (upload from agent, storage and ultimately deletion). Session: Authenticates and authorizes the client requests. SNMP Gateway: Provides SNMP northbound interface for alert management. CLI Gateway: Provides CLI management. TL1 Gateway: Provides TL1 management. To exit from the server administration functions, select Exit from the File menu or click the Close button (indicated by a red X ) in the top right corner of the dialog box. Release TN3.1.x Turin Networks Page 1-23

36 TransNav Server Guide, Section 1: Installation and Description Management Server Parameters Management Server Parameters The Server Administration tool allows you to view or change server administration parameters. In most cases, these parameters remain unchanged or you will only change them when you initially create the server. See Section 2 Management Server s, Chapter 1 Creating the Management Servers, page 2-1. In the Server Admin tool, from the Execution menu, click Configure Server, then click Parameter. The Execution Configuration dialog box displays. Figure 1-15 Execution Configuration Dialog Box Page 1-24 Turin Networks Release TN3.1.x

37 Chapter 3 Management Server Administration Management Server Parameters The Execution Configuration dialog box allows you to change the following server administration parameters: ANSITL1MetadataFile 1 : File containing the parameters of the management server ANSI TL1 Metadata file. Do not change this value. AdminTraceLevel 1 : Used for troubleshooting by the Turin Technical Assistance Center. Do not change this value. CliDataDictionaryFile 1 : Name of the XML file containing the CLI commands. Do not change this value. CliEmsHost 1 : IP address of the back end server (for distributed servers only). CliTelnetPort: Port number on which the CLI Telnet server accepts client connections. DatabaseBinDirectory 1 : Directory containing the binaries of the SOLID database tools. DatabaseExportFrequency (hours): The frequency to export the database to the path specified in DatabaseExportPath. DatabaseExportPath: Path in which to save the server database. DiscoveryPeriod (minutes) 1 : Number of minutes separating two topology audits. EMSTL1DataDictionaryFile 1 : Name of the XML file containing the parameters of the EMS TL1 file. Do not change this value. GatewayTL1MetadataFile 1 : File containing the parameters of the gateway server TL1 Metadata file. Do not change this value. JdmkGatewayConnectorType: Type of connector to be used by the JDMK Gateway component when communicating to the agent (rmi or http). JdmkGatewayPortNumber: Port to be used by the JDMK Gateway component connector when communicating to the agent. JdmkGatewayRmiAddress: If the server has two IP addresses, this is the IP address used to communicate with the nodes. Only enter an IP address if the server has two network interface cards (NIC). JdmkRequestTimeout (milliseconds): The time (in milliseconds) after a command is executed and the node does not respond. This Timeout is used by the JDMK Gateway component connector when communicating to the agent. If the system times out, an error message appears. MBeanDBCacheMax 1 : Maximum number of entries in the MBean component cache. MBeanDBCacheMin 1 : Minimum number of entries in the MBean component cache. MBeanDBProcessCaching 1 : Enable (true) or disable (false) the caching in the MBean component. MBeanDBProcessConfigFile 1 : File containing the parameters of the MBean component. 1 Do not change these parameters. Contact the Turin Technical Assistance Center for assistance. Release TN3.1.x Turin Networks Page 1-25

38 TransNav Server Guide, Section 1: Installation and Description Management Server Parameters MainBEServerIpAddress 1 : IP address of the back end server (for distributed server only). MaxNoOfUserSessions: The maximum number of combined simultaneous user sessions logged into any of the user interfaces (GUI, CLI, or TL1). Default is 20. PerformanceDataCollectPeriod (minutes): Number of minutes between two uploads of performance data from the agent. Default is 15 minutes. PerformanceDataRemovalCheckPeriod: Number of minutes between two removals of performance data from the agent. Default is 3 minutes. PerformanceDataRemovalPeriod (hours): Number of hours after which the performance data stored in the performance database is deleted. Default is 72 hours. PerformanceDatabase 1 : IP address of the performance database server (distributed server only). PerformanceDatabasePassword 1 : Password to be used to connect to the performance database. PerformanceDatabasePort 1 : Port on which the performance database is waiting for connection. PerformanceDatabaseUser 1 : Username to be used to connect to the performance database. ReportHost 1 : IP address of the server hosting the generated text reports (for distributed server only). ReportOutputDirectory 1 : Directory of the report server containing the generated text reports. ReportRemovalPeriod (days): Number of days after which the generated text reports stored on the report server are deleted from the server. ReportScriptDirectory 1 : Directory of the report server containing the scripts used for report generation. SSL_KeyValidity (days): Sets the number of days for which the secure key remains valid. Default is 180 days. SSL_PublicKeyStorePassword: p#33phr#3e SSL_PublicKeyStorePath: keystore SecurityAccessRightsFile 1 : File containing information on the users in each access group. SecurityOnOffFlag 1 : Checks the security level of users of the user interfaces. Domain-level and node-level users have different privileges. True (default): Enables the automatic checking of user security levels. False: Disables the automatic checking of user security levels. SessionHTMLConnector 1 : Enable (true) or disable (false) the JDMK HTML connector on the session component. SessionHTTPConnector: Enable (true) or disable (false) the JDMK HTTP connector on the session component. Page 1-26 Turin Networks Release TN3.1.x

39 Chapter 3 Management Server Administration Management Server Parameters SessionHTTPSConnector: Enables or disables the JDMK HTTP over SSL for a secure HTTP connection to session component. True: Enables the secure (SSL) connector for JDMK HTTP. Set the SSL keys for encryption (SSL_KeyValidity, SSL_PublicKeyStorePassword, and SSL_PublicKeySortPath). False (default): Disables the secure HTTP connection to the session component. SessionHtmlPort: Port on which the JDMK HTML connector is waiting for connections. Default is SessionHttpPort: Port on which the JDMK HTTP connector is waiting for connections. Default is SessionHttpsPort: Port on which the JDMK HTTPS connector is waiting for connections. Default is SessionRMIConnector: Enables or disables the JDMK RMI connector on the session components. True (default): Enables user sessions using RMI protocol. False: Disables users sessions using the RMI protocol. SessionRmiAddress: If the server has two IP addresses, this is the IP address used to communicate with either the GUI or CLI client workstation sessions. Only enter an IP address if the server has two network interface cards (NIC). SessionRmiPort: Port on which the JDMK RMI connector is waiting for connections SnmpAgentEnable: Enables or disables the management system to receive SNMP queries and forward system events: True: Enables the management system to receive SNMP queries and forward system events to an SNMP server. False (default): Does not allow the management system to send or receive SNMP queries. SnmpAgentHtmlAdaptorPort 1 : Port on which the JDMK HTML adaptor of the SNMP server is waiting for connection. Default is SnmpAgentSnmpAdaptorPort: Port on which the JDMK SNMP adaptor is waiting for SNMP requests. Default is SnmpAgentSnmpTrapsPort: Port to which the JDMK SNMP adaptor sends SNMP traps. Default is SnmpAgentTurinEmsHost 1 : IP address of the server (for distributed server only). Default is localhost. SnmpCurrentCounterValidity (seconds): Allows third-party equipment to query the PM counters for all Ethernet interfaces on the Traverse network through the SNMP interface. The server refreshes the PM data after the time specified in this parameter. Default is 120 seconds. TE100TL1DataDictionaryFile 1 : Name of the XML file containing the TE100 TL1 commands. TL1EmsConnectorType 1 : Type of connector to be used by the TL1 component when communicating to the TransNav server. Release TN3.1.x Turin Networks Page 1-27

40 TransNav Server Guide, Section 1: Installation and Description Management Server Parameters TL1EmsHost 1 : IP address of the server (for distributed server only). Default is localhost. TL1LoggingEnabled: Determines if logs from the TL1 interface are collected on the server: True: Enables logging of every TL1 command received and the respective response in a log file. Restart the server when you change this parameter to true. False (default): Disables the logging function. TL1PasswordEncryption: Indicates if password encryption is enabled on TL1 during log-on: true: Password encryption is enabled. false: Password encryption is not enabled. TL1TcplpPort: The port to which a machine can open a TL1 session. Used for machine-to-machine TL1 communications such as Spirent TL1 test units. Default is TL1TelnetPort: The telnet port on the server to which a user opens a TL1 session. Default is TraverseTL1DataDictionaryFile: Name of the XML file containing the parameters of the Traverse TL1 file. Do not change this value. UserImagesDirectory 1 : Directory for storing the background maps for the GUI. UserPreferencesDirectory 1 : Directory for storing the GUI user preferences. Command buttons are as follows: OK: Click to save any changes and return to the Server Admin dialog box. Cancel: Click to cancel any changes and return to the Server Admin dialog box. Page 1-28 Turin Networks Release TN3.1.x

41 SECTION 2MANAGEMENT SERVER PROCEDURES SECTION 2 MANAGEMENT SERVER PROCEDURES Contents Chapter 1 Creating the Management Servers Introduction Before You Create the Management Servers Start the Server Administration Tool Configure Management Server Parameters Set the Primary Management Server as the Primary NTP Source Set NTP Server on a Solaris Workstation Set the NTP Server on a Windows 2000 Professional Workstation Set the NTP Server on a Windows XP Workstation Configure Log and Error Files Chapter 2 Management Server SNMP Introduction Supported SNMP MIBs Location of SNMP MIB File Enable SNMP Agent Configure the SNMP Access Control List Ethernet Performance Monitoring and SNMP Ethernet Interfaces Performance Data Chapter 3 Server Administration s Introduction Start the Server Administration Tool Initialize the Database Enable the Server as a Service (Windows) Start the Server Export the Database Stop the Server Promoting a Secondary Server to the Primary Role Disable the Server as a Service (Windows) Upgrade Server Software Download TransNav Management Software from Your Customer Portal Import the Database Retrieve Server Log Files Release TN3.1.x Turin Networks Page i

42 TransNav Server Guide, Section 2 Management Server s List of Figures Figure 2-1 Start Menu Figure 2-2 Server Admin Tool Figure 2-3 Configure Server Parameters Figure 2-4 Management Server Parameters Figure 2-5 Command Buttons, Execution Configuration Dialog Box Figure 2-6 Run Dialog Box Figure 2-7 Registry Editor Figure 2-8 Run Dialog Box Figure 2-9 W23Time Config Registry Figure 2-10 Modify AnnounceFlags Figure 2-11 AnnounceFlags Edit DWORD Value Figure 2-12 NtpServer Subkey Figure 2-13 Modify NtpServer Enabled Figure 2-14 Enabled Edit DWORD Value Figure 2-15 Configure Logging Figure 2-16 Logging Configure Dialog Box Figure 2-17 Configure Server Figure 2-18 Configure Server Dialog Box Figure 2-19 Configure SNMP Figure 2-20 Edit the SNMP Access Control List Figure 2-21 Start Menu Figure 2-22 Server Admin Tool Figure 2-23 Initialize Database Figure 2-24 Database Initialize Confirmation Figure 2-25 Database Initialization Dialog Box Figure 2-26 Server Status Figure 2-27 Enable as Service Figure 2-28 Start Server Figure 2-29 Component Status Figure 2-30 Start Server Complete Figure 2-31 Export Database Figure 2-32 Database Export Dialog Box Figure 2-33 Export Status Figure 2-34 Export Database Complete Figure 2-35 Stop Server Figure 2-36 Server Shutdown Process Figure 2-37 Stop Server is Complete Figure 2-38 Disable as Service Figure 2-39 Customer Portal Screen Figure 2-40 Save Target As Figure 2-41 Import Database Figure 2-42 Database Initialize Confirmation Figure 2-43 Database Import Dialog Box Figure 2-44 Database Import Complete Page ii Turin Networks Release TN3.1.x

43 TransNav Server Guide, Section 2 Management Server s Figure 2-45 Retrieve Log Directory in Windows List of Tables Table 2-1 Before You Create the Management Servers Table 2-2 Start the Server Administration Tool Table 2-3 Configure Management Server Parameters Table 2-4 Set the Primary NTP Source on a Solaris Workstation Table 2-5 Set the Primary NTP Source on a Windows 2000 Professional Workstation Table 2-6 Set the Primary NTP Source on a Windows XP Workstation Table 2-7 Configure Log and Error Files Table 2-8 Enable SNMP Agent Components Table 2-9 Configure the SNMP Access Control List Table 2-10 Start the Server Administration Tool Table 2-11 Initialize the Database Table 2-12 Enable the Server as a Service Table 2-13 Start the Server Table 2-14 Export the Database Table 2-15 Stop the Server Table 2-16 Promoting a Secondary Server to the Primary Role Table 2-17 Disable the Server as a Service Table 2-18 Server Software Upgrade Table 2-19 Download TransNav Management Software from Your Customer Portal Table 2-20 Import the Database Table 2-21 Retrieve Server Log Files Release TN3.1.x Turin Networks Page iii

44 TransNav Server Guide, Section 2 Management Server s Page iv Turin Networks Release TN3.1.x

45 SECTION 2MANAGEMENT SERVER PROCEDURES Chapter 1 Creating the Management Servers Introduction Before You Create the Management Servers This chapter contains procedures that an administrator will perform when first installing the management system software. This chapter includes information on creating the management servers: Before You Create the Management Servers, page 2-1 Start the Server Administration Tool, page 2-2 Configure Management Server Parameters, page 2-3 Set the Primary Management Server as the Primary NTP Source, page 2-5 Configure Log and Error Files, page 2-11 Review the information in this topic before creating the Primary and Secondary management servers. Table 2-1 Before You Create the Management Servers Requirement Create a network plan. Assign IP addresses to the management servers and network elements. Add routes for the node-ips to the management servers. Install, connect, and commission nodes according to the network plan. Install the TransNav management software on each server. FTP server application is installed on all management servers. Telnet server application is installed. Reference Traverse Product Overview TraverseEdge 100 User Guide TransNav Management System Product Overview TransNav Management System Product Overview, Section 2 Management System Planning, Chapter 3 IP Address Planning, page 2-9 This step depends on the server platform (Solaris or Windows) and local site practices. Contact your local site administrator. Traverse Installation and Commissioning TraverseEdge 100 User Guide TransNav Management System Server Guide, Section 1 Installation and Description Required to distribute TransNav software to network elements. Turin recommends WAR FTP for Windows. Download the application for free from Adobe s site at: Required for remote access to the management servers. Release TN3.1.x Turin Networks Page 2-1

46 TransNav Server Guide, Section 2: Management Server s Start the Server Administration Tool Start the Server Administration Tool To access server administration functions, start the Server Administration Tool on the machine where you have the management server software installed. Table 2-2 Start the Server Administration Tool 1 For a Windows platform, go to 2. For a Solaris platform, go to 3. 2 On a Windows platform, from the Start menu, click Programs, then click Turin_Networks, then click TransNav Admin. Figure 2-1 Start Menu 3 On a Solaris platform, change to the directory where you installed the management software and enter the following command in an xterm window: $./ems_admin.sh 4 The Server Admin dialog box displays. Figure 2-2 Server Admin Tool Page 2-2 Turin Networks Release TN3.1.x

47 Chapter 1 Creating the Management Servers Configure Management Server Parameters Table 2-2 Start the Server Administration Tool (continued) 5 See the procedure, Server Administration Components Description, page 1-21, for a description of each server component. 6 The Start the Server Administration Tool procedure is complete. Configure Management Server Parameters View or change server administration parameters using the Configure Server option in the Server Admin tool. This server configuration information is stored in the environment.conf file. This file is located in the same directory in which the server software was installed. Important: Contact the Turin Technical Assistance Center for assistance in changing server administration parameters. Table 2-3 Configure Management Server Parameters 1 Start the Server Administration tool. See the procedure Start the Server Administration Tool, page 2-2. The Server Admin dialog box displays. 2 If the server is already started, stop the server. See the procedure Stop the Server, page From the Execution menu, click Configure Server, then click Parameter. Figure 2-3 Configure Server Parameters Release TN3.1.x Turin Networks Page 2-3

48 TransNav Server Guide, Section 2: Management Server s Configure Management Server Parameters Table 2-3 Configure Management Server Parameters (continued) 4 In the Execution Configuration dialog box, change any of the default values for the parameters. Figure 2-4 Management Server Parameters See Server Administration Components Description, page 1-21, for the descriptions of each parameter. Note: If you are creating a Secondary server, you must change the value of the ServerRole field on the Execution Configuration dialog box to Secondary. 5 Click OK to close the Execution Configuration dialog box and return to the Server Admin tool. Figure 2-5 Command Buttons, Execution Configuration Dialog Box 6 Restart the server for the changes to take effect. See the procedure Start the Server, page The Configure Management Server Parameters procedure is complete. Page 2-4 Turin Networks Release TN3.1.x

49 Chapter 1 Creating the Management Servers Set NTP Server on a Solaris Workstation Set the Primary Management Server as the Primary NTP Source Set the Primary management server as the primary Network Time Protocol (NTP) source. Use the following procedure for a basic stand-alone NTP server set-up: Set NTP Server on a Solaris Workstation, page 2-5 Set the NTP Server on a Windows 2000 Professional Workstation, page 2-6 For different types of configuration set-ups, refer to See the TransNav Management System Product Overview, Section 2 Management System Planning, Chapter 4 Network Time Protocol (NTP) Sources, page 2-19 for information on setting up the node NTP source in different network topologies. Important: If you change the NTP time source at any time, you must restart the Primary TransNav management server and then synchronize the Secondary servers to report any new alarms. Set NTP Server on a Solaris Workstation If Sun Solaris is the workstation for the Primary TransNav management server, use this procedure to configure the Solaris as the primary NTP server. Table 2-4 Set the Primary NTP Source on a Solaris Workstation 1 As root, execute the following commands: # cd /etc/inet/ # cp ntp.server ntp.conf 2 Edit the ntp.conf file, making the following changes: From: server XType.0 prefer fudge XType.0 stratum 0 To: server fudge stratum 12 3 To start the NTP server immediately, first stop the server in case it is already running: # /etc/init.d/xntpd stop Then start the server: # /etc/init.d/xntpd start 4 The Set the Primary NTP Source on a Solaris Workstation procedure is complete. Release TN3.1.x Turin Networks Page 2-5

50 TransNav Server Guide, Section 2: Management Server s Set the NTP Server on a Windows 2000 Professional Workstation Set the NTP Server on a Windows 2000 Professional Workstation Use this procedure to configure the computer as the primary NTP server if the Primary TransNav management server is running on a Windows 2000 Professional workstation. Table 2-5 Set the Primary NTP Source on a Windows 2000 Professional Workstation 1 From the Start menu, click Run. 2 In the Open field, type regedit and click OK to start the Registry Editor. Figure 2-6 Run Dialog Box 3 Navigate to the directory: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32 Time\Parameters Figure 2-7 Registry Editor 4 Change the REG_SZ value to 0. 5 Change the local NTP value to 1. 6 Change the Type value to NoSync. 7 From the Edit menu, click New > DWORD value. 8 Change New Value #1 to ReliableTimeSource. 9 Change the ReliableTimeSource value to 1. Page 2-6 Turin Networks Release TN3.1.x

51 Chapter 1 Creating the Management Servers Set the NTP Server on a Windows XP Workstation Table 2-5 Set the Primary NTP Source on a Windows 2000 Professional Workstation (continued) 10 Start the Administrative Tools from the Control Panel: Start > Control Panel > Administrative Tools > Services 11 In Windows Time service, set the startup time to Automatic. 12 Restart the computer. 13 The Set the Primary NTP Source on a Windows 2000 Professional Workstation procedure is complete. Set the NTP Server on a Windows XP Workstation Use this procedure to configure the computer as the primary NTP server if the Primary TransNav management server is running on a Windows XP workstation. Table 2-6 Set the Primary NTP Source on a Windows XP Workstation 1 From the Start menu, click Run. 2 In the Open field, type regedit and click OK to start the Registry Editor. Figure 2-8 Run Dialog Box Release TN3.1.x Turin Networks Page 2-7

52 TransNav Server Guide, Section 2: Management Server s Set the NTP Server on a Windows XP Workstation Table 2-6 Set the Primary NTP Source on a Windows XP Workstation (continued) 3 Navigate to the following registry entry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32 Time\Config\ Figure 2-9 W23Time Config Registry 4 In the right pane, right-click AnnounceFlags, and then click Modify. Figure 2-10 Modify AnnounceFlags 5 In the Edit DWORD Value dialog box, type 5 under Value data, and then click OK. Figure 2-11 AnnounceFlags Edit DWORD Value Page 2-8 Turin Networks Release TN3.1.x

53 Chapter 1 Creating the Management Servers Set the NTP Server on a Windows XP Workstation Table 2-6 Set the Primary NTP Source on a Windows XP Workstation (continued) 6 Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32 Time\TimeProviders\NtpServer\ Figure 2-12 NtpServer Subkey 7 In the right pane, right-click Enabled and then click Modify. Figure 2-13 Modify NtpServer Enabled 8 In the Edit DWORD Value dialog box, type 1 under Value data and then click OK. Figure 2-14 Enabled Edit DWORD Value 9 From the file menu, click Exit to close the Registry Editor. 10 From the Start menu, click Run. Release TN3.1.x Turin Networks Page 2-9

54 TransNav Server Guide, Section 2: Management Server s Set the NTP Server on a Windows XP Workstation Table 2-6 Set the Primary NTP Source on a Windows XP Workstation (continued) 11 In the Open field, type cmd and click OK to open a DOS command line prompt. 12 At the command prompt, enter the following command to restart the Windows Time service: net stop w32time && net start w32time 13 The Set the Primary NTP Source on a Windows XP Workstation procedure is complete. Page 2-10 Turin Networks Release TN3.1.x

55 Chapter 1 Creating the Management Servers Configure Log and Error Files Configure Log and Error Files Use this procedure ensure the server is collecting log and error files for troubleshooting purposes. Table 2-7 Configure Log and Error Files 1 Start the server administration tool. See the procedure Start the Server Administration Tool, page From the Logging menu, click Configure. Figure 2-15 Configure Logging 3 For each of the parameters in the Logging Configure dialog box, select one of the following output trace levels: None: No logging Summary (default): Summary-level detail Detail: Higher level of detail Verbose: Highest level of detail Figure 2-16 Logging Configure Dialog Box 4 Click OK to save configuration information and close the dialog box. 5 The Configure Log and Error Files procedure is complete. Release TN3.1.x Turin Networks Page 2-11

56 TransNav Server Guide, Section 2: Management Server s Configure Log and Error Files Page 2-12 Turin Networks Release TN3.1.x

57 SECTION 2MANAGEMENT SERVER PROCEDURES Chapter 2 Management Server SNMP Introduction Supported SNMP MIBs Location of SNMP MIB File This chapter contains procedures that an administrator will perform when first installing the management system software. This chapter includes information on enabling the subnetwork management protocol (SNMP) on the management server: Supported SNMP MIBs, page 2-13 Location of SNMP MIB File, page 2-13 Enable SNMP Agent, page 2-14 Configure the SNMP Access Control List, page 2-15 Ethernet Performance Monitoring and SNMP, page 2-17 The SNMP northbound interface implements the SNMP v1 protocol and maintains a proprietary MIB. The TransNav management system supports a subset of the following RFCs for alarm management and performance monitoring purposes: RFC the Interfaces Group MIB RFC Remote Network Monitoring Management Information Base RFC Definitions of Managed Objects for the Ethernet-like Interface Types The proprietary SNMP MIB (filename=ems.mib) file is located in the same directory where you installed the server application. Release TN3.1.x Turin Networks Page 2-13

58 TransNav Server Guide, Section 2: Management Server s Enable SNMP Agent Enable SNMP Agent Use the following procedure to allow the management system to receive SNMP queries and forward system events. Table 2-8 Enable SNMP Agent Components 1 Start the server administration tool. See the procedure Start the Server Administration Tool, page If the server is running, stop the server. See the procedure Stop the Server, page From the Execution menu, click Configure Server, then click Parameter. Figure 2-17 Configure Server 4 In the Configure Server dialog box, configure the SNMP Agent components. Figure 2-18 Configure Server Dialog Box Set the SnmpAgentEnable variable to TRUE. Set the SnmpAgentSnmpAdaptorPort variable to the port on which the system receives requests; default is Set the SnmpAgentSnmpTrapsPort variable to the port on which the system sends SNMP traps; default is Click OK to save the changes and close the Execution Configuration dialog box. 6 Restart the server. See the procedure Start the Server, page Page 2-14 Turin Networks Release TN3.1.x

59 Chapter 2 Management Server SNMP Configure the SNMP Access Control List Table 2-8 Enable SNMP Agent Components (continued) 7 Continue to the procedure Configure the SNMP Access Control List, page The Enable SNMP Agent Components procedure is complete. Continue to the next procedure Configure the SNMP Access Control List, page Configure the SNMP Access Control List The SNMP access control list (ACL) stores information on the access rights for SNMP communities and host machines. The ACL mechanism also defines the communities and managers to which the SNMP agent will send traps. When you rely on the ACL trap group, the agent sends traps to all hosts listed in the ACL file. Use the following procedure to help you configure the ACL file. Table 2-9 Configure the SNMP Access Control List 1 Start the server administration tool. See the procedure Start the Server Administration Tool, page If the server is running, stop the server. See the procedure Stop the Server, page From the Execution menu, click Configure SNMP. Figure 2-19 Configure SNMP Release TN3.1.x Turin Networks Page 2-15

60 TransNav Server Guide, Section 2: Management Server s Configure the SNMP Access Control List Table 2-9 Configure the SNMP Access Control List (continued) 4 The ACL file appears in a text editor window. 5 6 Figure 2-20 Edit the SNMP Access Control List 5 Edit the acl group: communities: Specifies a list of SNMP community names to which this access control applies. If there is more than one community name, separate the communities by commas. Default is public, private. access: Specifies the access rights to be granted to all connecting managers. There are two possible values: read-write or read-only. Default is read-only. managers: The IP addresses of the servers which can send SNMP requests. If there is more than one address, separate the list with commas. 6 Edit the trap group: trap-community: The community string the SNMP component will use to send traps. The default value is public. This value cannot contain the word trap. hosts: The IP addresses of the servers (separated by commas) to which the SNMP component will send traps. 7 Click Save, then Done to exit the text editor. 8 Restart the server. See the procedure Start the Server, page The Configure the SNMP Access Control List procedure is complete. Page 2-16 Turin Networks Release TN3.1.x

61 Chapter 2 Management Server SNMP Ethernet Performance Monitoring and SNMP Ethernet Performance Monitoring and SNMP The SNMP MIB supports performance data counters for the current day interval for every Ethernet interface in the TransNav-managed network. The management server collects the performance data and allows third-party equipment to query these PM counters through the SNMP interface. The server refreshes the data after the time specified in the server parameter SnmpCurrentCounterValidity (seconds). Default is 120 seconds. The Ethernet Interface Index is created using the following algorithm: SlotIndex * PortIndex * where: SlotIndex range is from 1 to 20 PortIndex range is from 1 to 50 Allocating 10,000,000 identifiers per slot allows SNMP to extend to lower layer interfaces but still provides the capability to manage more than 200 slots. Ethernet Interfaces The Ethernet current day table in the SNMP MIB maintains one entry per Ethernet interface in the TransNav-managed network. When SNMP is enabled, SNMP queries all nodes for all Ethernet interfaces and populates the Ethernet current day table. SNMP also updates the table when new Ethernet interfaces are created or deleted. A new entry in the Ethernet current day table has performance data counters set to zero. The counters are populated with real values from network elements only upon reception of a SNMP query. Performance Data The time is recorded every time a row in the table is updated. Each time SNMP queries a row s counter, the current time is checked against the time the counter was updated. If the elapsed time is less than 120 seconds (the time specified in the SNMPCurrentCounterValidity parameter), the data already recorded is returned to the SNMP request. When a counter s data has to be refreshed, SNMP builds the list of ALL Ethernet interfaces collocated on the same node and sends ONE query to that node to refresh all the counters. Release TN3.1.x Turin Networks Page 2-17

62 TransNav Server Guide, Section 2: Management Server s Ethernet Performance Monitoring and SNMP Page 2-18 Turin Networks Release TN3.1.x

63 SECTION 2MANAGEMENT SERVER PROCEDURES Chapter 3 Server Administration s Introduction This chapter contains procedures for day-to-day administration of the management system. Server administration functions include the following procedures: Start the Server Administration Tool, page 2-20 Initialize the Database, page 2-21 Enable the Server as a Service (Windows), page 2-23 Start the Server, page 2-24 Export the Database, page 2-26 Stop the Server, page 2-27 Promoting a Secondary Server to the Primary Role, page 2-29 Disable the Server as a Service (Windows), page 2-31 Upgrade Server Software, page 2-32 Download the TransNav Management Software from the Turin Infocenter, page 2-33 Import the Database, page 2-35 Retrieve Server Log Files, page 2-36 Release TN3.1.x Turin Networks Page 2-19

64 TransNav Server Guide, Section 2: Management Server s Start the Server Administration Tool Start the Server Administration Tool To access server administration functions, start the Server Administration Tool on the machine where you have the management server software installed. Table 2-10 Start the Server Administration Tool 1 For a Windows platform, go to 2. For a Solaris platform, go to 3. 2 On a Windows platform, from the Start menu, click Programs, then click Turin_Networks, then click TransNav Admin. Figure 2-21 Start Menu 3 On a Solaris platform, change to the directory where you installed the management software and enter the following command in an xterm window: $./ems_admin.sh 4 The Server Admin dialog box displays. Figure 2-22 Server Admin Tool Page 2-20 Turin Networks Release TN3.1.x

65 Chapter 3 Server Administration s Initialize the Database Table 2-10 Start the Server Administration Tool (continued) 5 See the procedure, Server Administration Components Description, page 1-21, for a description of each server component. 6 The Start the Server Administration Tool procedure is complete. Initialize the Database Initializing the server is only required the first time you start the database, but it can also be used to empty or clear the server database. WARNING! Use caution when initializing the server. This procedure erases all provisioning information. Table 2-11 Initialize the Database 1 Start the Server Administration Tool. The Server Admin dialog box displays. See the procedure Start the Server Administration Tool, page From the Database menu, click Initialize. Figure 2-23 Initialize Database 3 Confirm that you want to erase all previous provisioned data from the database. Figure 2-24 Database Initialize Confirmation Release TN3.1.x Turin Networks Page 2-21

66 TransNav Server Guide, Section 2: Management Server s Initialize the Database Table 2-11 Initialize the Database (continued) 4 In the Database Initialization dialog box, select the technology standard of the server, then select the server role. Figure 2-25 Database Initialization Dialog Box a. Select one of the following technology standard values: ANSI_default: The server exposes both the SONET and SDH set of commands in the user interfaces. However, upon initialization, the line cards and timing subsystem are operating in SONET mode but can still be switched at any time by an operator. ITU_default: The server exposes both the SONET and SDH set of commands in the user interfaces. However, upon initialization, the line cards and timing subsystem are operating in SDH mode but can still be switched at any time by an operator. ANSI_only: The server exposes only the SONET set of commands. Upon initialization, the line cards and timing subsystem are operating in SONET mode and can never be switched at any time by an operator. Any management server commissioned with a gateway value can manage a node commissioned in ANSI mode. SDH features will not be accessible on that node. An ANSI management server refuses to communicate to a node that is commissioned as a gateway. b. Select the role of the server being initialized: Primary (default): The server will be the Primary server in the network. Each management domain can have only one Primary server. Secondary: The server will be a Secondary server in the network. Once selected as a Secondary server, the ServerRole always remains a Secondary server. Each management domain can have up to 7 Secondary servers. Secondary servers supply redundancy for all Primary server functions except performance maintenance, and automatically collect up-to-date information on node configuration and current alarms. Secondary servers do not accept management messages from a northbound network management system. Note: A Secondary server can be made the Primary server for planned maintenance purposes or if the Primary server fails. The switch from Secondary to Primary server must be made manually. See the procedure Promoting a Secondary Server to the Primary Role, page Page 2-22 Turin Networks Release TN3.1.x

67 Chapter 3 Server Administration s Enable the Server as a Service (Windows) Table 2-11 Initialize the Database (continued) 5 The status of the initialization displays on the status bar in the Server Admin dialog box. status bar Figure 2-26 Server Status 6 The Initialize the Database procedure is complete. Continue to the next procedure Start the Server, page Enable the Server as a Service (Windows) If this is a Windows workstation, use this procedure to allow the server to restart on the workstation in case the workstation turns off or power cycles. This procedure restarts the server when the workstation starts again. Table2-12 Enable the Server as a Service 1 The server must be stopped and initialized. To stop the server, see the procedure Stop the Server, page Initialize the database. See the procedure Initialize the Database, page From the Execution menu, click Configure Server, then click Enable as Service. Figure 2-27 Enable as Service 4 The Enable the Server as a Service procedure is complete when (Enabled As Service) appears in the header of the Server Admin dialog box. Release TN3.1.x Turin Networks Page 2-23

68 TransNav Server Guide, Section 2: Management Server s Start the Server Start the Server To start the management server, select Start Server from the Execution menu. The progress is shown in the status bar. Table 2-13 Start the Server 1 Start the Server Administration Tool. The Server Admin dialog box displays. See the procedure Start the Server Administration Tool, page From the Execution menu, click Start Server. Figure 2-28 Start Server Page 2-24 Turin Networks Release TN3.1.x

69 Chapter 3 Server Administration s Start the Server Table 2-13 Start the Server (continued) 3 The server starts each component one at a time. You can monitor the status of each component in the dialog box. Figure 2-29 Component Status 4 When all the components are running, the Start the Server procedure is complete. Figure 2-30 Start Server Complete Release TN3.1.x Turin Networks Page 2-25

70 TransNav Server Guide, Section 2: Management Server s Export the Database Export the Database Export copies of provisioning data stored on a node. If you need to restore the exported copy at a later date, you can retrieve the data using the Import function (Import the Database, page 2-35) on the Server Administration Tool. Table 2-14 Export the Database 1 Start the Server Administration Tool. The Server Admin dialog box displays. See the procedure, Start the Server Administration Tool, page From the Database menu, click Export. Figure 2-31 Export Database 3 On the Database Export dialog box, click the Browse button and navigate to the correct directory. Click OK. Figure 2-32 Database Export Dialog Box Within this Export Path, a subdirectory named Export_MM.DD.YYYY_HH.MM will be created, where MM.DD.YYYY is the date and HH.MM is the time in military format. The server database is saved under this subdirectory. Page 2-26 Turin Networks Release TN3.1.x

71 Chapter 3 Server Administration s Stop the Server Table 2-14 Export the Database (continued) 4 The status of the export process displays on the status bar in the Server Admin dialog box. status bar Figure 2-33 Export Status 5 When the status bar at the bottom of the screen indicates the export is Done, the Export the Database procedure is complete. status bar Figure 2-34 Export Database Complete Stop the Server To shut down the management server, select Stop Server from the Execution menu. The progress is shown in the status bar. WARNING! The procedure below stops all server processes, as well as stopping the database. Table2-15 Stop the Server 1 Start the Server Administration Tool. The Server Admin dialog box displays. See the procedure Start the Server Administration Tool, page From the Execution menu, click Stop Server. Figure 2-35 Stop Server Release TN3.1.x Turin Networks Page 2-27

72 TransNav Server Guide, Section 2: Management Server s Stop the Server Table 2-15 Stop the Server (continued) 3 The server starts the shutdown process. Figure 2-36 Server Shutdown Process 4 When all the components are stopped, the Stop the Server procedure is complete. Figure 2-37 Stop Server is Complete Page 2-28 Turin Networks Release TN3.1.x

73 Chapter 3 Server Administration s Promoting a Secondary Server to the Primary Role Promoting a Secondary Server to the Primary Role Each TransNav management system supports up to 8 servers in the same domain; one Primary server and up to 7 Secondary servers. Use the following procedure to promote a Secondary server to the Primary server role. Important: Promoting a Secondary server requires that steps are done in the following order: export the Primary server database, stop the Secondary server to be promoted, import the saved database onto the Secondary server, restart the Secondary server, switch the Secondary server s role to the Primary server role and finally, either stop the original (previous) Primary server or switch it to a Secondary server role. Table 2-16 Promoting a Secondary Server to the Primary Role 1 Optionally, create a backup of the database on the current Primary server. See the procedure Export the Database, page Stop the Secondary server that is to be promoted to the role of Primary server. See the procedure Stop the Server, page Import the copy of the backed up database from the original Primary server onto the Secondary server. See the procedure Import the Database, page Important: If you skip this step, recent server or domain-level changes made on the original Primary server will not be in effect on the new Primary server when the role is switched. 4 Restart the Secondary server from the Server Administration Tool. See the procedure Start the Server, page Release TN3.1.x Turin Networks Page 2-29

74 TransNav Server Guide, Section 2: Management Server s Promoting a Secondary Server to the Primary Role Table 2-16 Promoting a Secondary Server to the Primary Role (continued) 5 Switch the Secondary server to the Primary server role using one of the following methods: From the server CLI, enter exec ems switch role Primary Using the server GUI, from the Execution menu, click Configure Server, then click Parameter. The Execution Configuration dialog box displays. For more information on the Execution Configuration dialog box, see Chapter 3 Management Server Administration, Management Server Parameters, page On the Secondary server, when importing the saved database, change the value in the ServerRole field. From the Execution menu, click Configure Server, then click Parameter. The Execution Configuration dialog box displays. In the ServerRole field, change the value to Primary. Each Traverse node will raise alarms when two Primary servers are detected. The alarms clear when the original Primary server is stopped or demoted to a Secondary server role. Note: If more than one Primary server exists in the TransNav management system, some situations could occur involving node failure and recovery resulting in inconsistent node configuration. Turin recommends changing the role of the original Primary server as soon as possible. 6 Stop the original Primary server or switch the role to Secondary server. To stop the server, see the procedure Stop the Server, page To switch the original Primary server to a Secondary server role, from the Execution menu, click Configure Server, then click Parameter. The Execution Configuration dialog box displays. In the ServerRole field, change the value to Secondary. 7 The Promoting a Secondary Server to the Primary Role procedure is complete. Page 2-30 Turin Networks Release TN3.1.x

75 Chapter 3 Server Administration s Disable the Server as a Service (Windows) Disable the Server as a Service (Windows) If this is a Windows workstation, use this procedure to disable the server as a service. The services must be disabled before you upgrade the server software. Table 2-17 Disable the Server as a Service 1 Start the Server Administration Tool. The Server Admin dialog box displays. See the procedure Start the Server Administration Tool, page Stop the server. See the procedure, Stop the Server, page From the Execution menu, click Configure Server, then click Disable as Service. Figure 2-38 Disable as Service 4 The Disable the Server as a Service procedure is complete when (Enabled As Service) is removed from the header of the Server Admin dialog box. Release TN3.1.x Turin Networks Page 2-31

76 TransNav Server Guide, Section 2: Management Server s Upgrade Server Software Upgrade Server Software Each version of the TransNav management system software is backward compatible with the previous major release. Use the following procedure to upgrade the server software. Important: System software upgrades require a specified order. You must first upgrade the server software, followed by the GCM modules, and then the remaining modules. For step-by-step node software upgrade procedures, refer to Node Operations and Maintenance, Section 7 Software Upgrades. Table 2-18 Server Software Upgrade 1 Download the correct version of the TransNav management system software from the software CD or the Turin Infocenter. See the procedure Download TransNav Management Software from the Turin Infocenter, page Note: If you do not have access to the Turin Infocenter, contact your local sales representative. 2 Uninstall all GUI applications from all client workstations. For Windows workstations, see the TransNav Management System GUI Guide, Section 1 Installation and Overview, Chapter 1 Installation for Windows Workstations, page 1-1. For UNIX workstations, see the TransNav Management System GUI Guide, Section 1 Installation and Overview, Chapter 2 Installation for Solaris Workstations, page Create a backup of the database on the current server. See the procedure Export the Database, page Stop the server. See the procedure Stop the Server, page If this is a Windows workstation AND the server is enabled as a service, disable the server as a service. See the procedure Disable the Server as a Service, page Install the new server software: For Solaris workstations, see Section 1 Installation and Description, Chapter 1 Installation for Solaris Workstations, page 1-1. For Windows workstations, see Section 1 Installation and Description, Chapter 2 Installation for Windows Workstations, page Import the database that was saved in 3. See the procedure Import the Database, page Start the server. See the procedure Start the Server, page Page 2-32 Turin Networks Release TN3.1.x

77 Chapter 3 Server Administration s Download the TransNav Management Software from the Turin Infocenter Table2-18 Server Software Upgrade (continued) 9 Install the upgraded GUI applications for all client workstations. For Windows workstations, see the TransNav Management System GUI Guide, Section 1 Installation and Overview, Chapter 1 Installation for Windows Workstations, page 1-1. For UNIX workstations, see the TransNav Management System GUI Guide, Section 1 Installation and Overview, Chapter 2 Installation for Solaris Workstations, page The Server Software Upgrade procedure is complete. Download the TransNav Management Software from the Turin Infocenter Use this procedure to download the latest EMS server software from the Turin Infocenter. Note: If you do not have access to the Turin Infocenter, contact your local sales representative. Table2-19 Download TransNav Management Software from the Turin Infocenter 1 On your computer, open an internet browser window. 2 In the Address bar, enter the address: 3 In the dialog box, enter your user name and password provided by the Turin webmaster.. Figure 2-39 Infocenter Login Screen Release TN3.1.x Turin Networks Page 2-33

78 TransNav Server Guide, Section 2: Management Server s Download the TransNav Management Software from the Turin Infocenter Table2-19 Download TransNav Management Software from the Turin Infocenter 4 From the Infocenter webpage click the the Software Downloads drop-down menu. Select Turin EMS & flash Downloads to display the Turin EMS and FLASH Downloads webpage. Figure 2-40 Software Downloads Drop-down Menu 5 In the Turin EMS and FLASH Downloads page, locate the download links corresponding to your system release base and management system platform. Right-click the files to download and select the menu option Save Target As. Figure 2-41 EMS and Flash Downloads Screen Select RLS <n.n.n.n> under the TransNav Management System (Windows) section to retrieve PC software. Select RLS <n.n.n.n> under the TransNav Management System (Solaris) section t to retrieve the UNIX software. where: <n.n.n.n> is the number of the latest release of software. To retrieve the online help files, see Section 1 Installation and Description, Chapter 1 Installation for Solaris Workstations or Chapter 2 Installation for Windows Workstations. Page 2-34 Turin Networks Release TN3.1.x

79 Chapter 3 Server Administration s Import the Database Table2-19 Download TransNav Management Software from the Turin Infocenter 6 Navigate to a user-defined directory to save the executable file and click Save. 7 The Download TransNav Management Software from the Turin Infocenter procedure is complete. Return to the procedure Server Software Upgrade, page Import the Database Restore a backed-up version of the provisioned data using the server administration tool. Secondary servers are synchronized to the Primary server when the Primary server database is imported to the Secondary server. Use the import function to restore copies of data. Note: The loopback state or port lock/unlock state will not be restored after a node database restore operation is performed. Instead, the system uses the current state of the port to override what was stored in the node database. Table 2-20 Import the Database 1 Start the Server Administration Tool. The Server Admin dialog box displays. See the procedure Start the Server Administration Tool, page From the Database menu, click Import. Figure 2-42 Import Database 3 Verify that you want to continue the import. Figure 2-43 Database Initialize Confirmation Release TN3.1.x Turin Networks Page 2-35

80 TransNav Server Guide, Section 2: Management Server s Retrieve Server Log Files Table 2-20 Import the Database (continued) 4 In the Database Import dialog box, click the Browse button and navigate to the correct directory. Select the file to be imported, then click OK. Figure 2-44 Database Import Dialog Box 5 When the status bar indicates that the import is done, the Import the Database procedure is complete. status bar Figure 2-45 Database Import Complete Retrieve Server Log Files Use this procedure to retrieve log and error files from the TransNav management server. The Turin Technical Assistance Center uses these files to help troubleshoot server problems. Table 2-21 Retrieve Server Log Files 1 Ensure the server is collecting log files. See the procedure Chapter 1 Creating the Management Servers, Configure Log and Error Files, page Navigate to the directory in which the server software is installed: On a Windows workstation, go to 3. On a Solaris workstation, go to 4. Page 2-36 Turin Networks Release TN3.1.x

81 Chapter 3 Server Administration s Retrieve Server Log Files Table 2-21 Retrieve Server Log Files (continued) 3 In a Windows Explorer window, select the logs directory. Figure 2-46 Retrieve Log Directory in Windows Add the entire directory to a.zip file: Right-click the logs directory. Select WinZip 1, then select Add to logs.zip. 4 In an xterm window, type: $ tar -cf logs.tar logs/* $ gzip logs.tar 5 Send the compressed file to the Turin Technical Assistance Center for analysis. 6 The Retrieve Server Log Files procedure is complete. 1 Requires the popular compression application WinZip. See Release TN3.1.x Turin Networks Page 2-37

82 TransNav Server Guide, Section 2: Management Server s Retrieve Server Log Files Page 2-38 Turin Networks Release TN3.1.x

83 INDEX A Administration, server component, 1-21 AdminTraceLevel, server parameter, 1-23 Alarm object repository, server component, 1-21 All-In-One documentation, 1-17 online help, 1-17 tabs contents, 1-18 index, 1-18 search, 1-18 ANSITL1MetadataFile, server parameter, 1-23 Apache, server component, 1-21 Archive extract allinone.zip, 1-6, 1-9, 1-14, 1-16 extract dialog box, 1-14, 1-16 unzip command, 1-6, 1-9 zip tool, 1-14, 1-16 C CLI gateway, server component, 1-21 CliDataDictionaryFile, server parameter, 1-23 CliEmsHost, server parameter, 1-23 CliTelnetPort, server parameter, 1-23 Configuration, server component, 1-21 D Database, server component, 1-21 DatabaseBinDirectory, server parameter, 1-23 DatabaseExportFrequencyHrs, server parameter, 1-23 DatabaseExportPath, server parameter, 1-23 Discovery, server component, 1-21 DiscoveryPeriod, server parameter, 1-23 E EMSTL1DataDictionaryFile, server parameter, 1-23 Ethernet PM SNMP, 2-17 Event object repository, server component, 1-21 Execution Configuration dialog box, 1-22 G GatewayTL1MetadataFile, server parameter, 1-23 H Help files install from CD (Solaris), 1-5 J Help Files (continued) install from CD (Windows), 1-13 install from customer portal (Solaris), 1-7 install from customer portal (Windows), 1-15 JDMK gateway, server component, 1-21 JdmkGatewayConnectorType, server parameter, 1-23 JdmkGatewayPortNumber, server parameter, 1-23 JdmkGatewayRmiAddress, server parameter, 1-23 JdmkRequestTimeout, server parameter, 1-23 M MainBEServerIpAddress, server parameter, 1-24 Management server help directory (Solaris), 1-5 help directory (solaris), 1-8 help directory (Windows), 1-16 help directory (windows), 1-14 Map, server component, 1-21 MaxNoOfUserSessions, server parameter, 1-24 Mbean, server component, 1-21 MBeanDBCacheMax, server parameter, 1-23 MBeanDBCacheMin, server parameter, 1-23 MBeanDBProcessCaching, server parameter, 1-23 MBeanDBProcessConfigFile, server parameter, 1-23 N Network, server component, 1-21 P Performance collection, server component, 1-21 PerformanceDatabase, server parameter, 1-24 PerformanceDatabasePassword, server parameter, 1-24 PerformanceDatabasePort, server parameter, 1-24 PerformanceDatabaseUser, server parameter, 1-24 PerformanceDataCollectPeriod, server parameter, 1-24 PerformanceDataRemovalPeriod, server parameter, 1-24 Preprovisioning, server component, 1-21 s configure the SNMP ACL, 2-15 create the management server, 2-1 before you start, 2-1 configure log and error files, 2-11 configure management server parameters, 2-3 set the server as the primary NTP source, 2-4 start the server admin tool, 2-2 Release TN3.1.x Turin Networks Page 1

84 s (continued) enable the SNMP agent on server, 2-14 install server software (Solaris), 1-2 install server software (Windows), 1-12 run the server as a daemon (Solaris), 1-3 server administration disable the server as a service (Windows), 2-31 enable the server as a service (Windows), 2-23 export the database, 2-26 import the database, 2-35 initialize the database, 2-21 promote a Secondary server to Primary server, 2-29 retrieve server log files, 2-37 start the server, 2-24 start the server admin tool, 2-20 stop the server, 2-27 upgrade server software, 2-32 server administration procedures, 2-19 uninstall server software (Solaris), 1-10 uninstall server software on Windows, 1-18 R ReportHost, server parameter, 1-24 ReportOutputDirectory, server parameter, 1-24 ReportRemovalPeriod, server parameter, 1-24 Reports, server component, 1-21 ReportScriptDirectory, server parameter, 1-24 RMI registry, server component, 1-21 S SecurityAccessRightsFile, server parameter, 1-24, 1-25 SecurityOnOffFlag, server parameter, 1-25 Server Admin tool, 1-21, 2-2, 2-20 Server components, descriptions, 1-21 administration, 1-21 alarm object repository, 1-21 Apache, 1-21 CLI gateway, 1-21 configuration, 1-21 database, 1-21 discovery, 1-21 event object repository, 1-21 JDMK gateway, 1-21 map, 1-21 Mbean, 1-21 network, 1-21 performance collection, 1-21 preprovisioning, 1-21 reports, 1-21 RMI registry, 1-21 session, 1-21 Server component, descriptions (continued) SNMP gateway, 1-21 TL1 gateway, 1-21 topology, 1-21 Server parameters, descriptions AdminTraceLevel, 1-23 ANSITL1MetadataFile, 1-23 CliDataDictionaryFile, 1-23 CliEmsHost, 1-23 CliTelnetPort, 1-23 DatabaseBinDirectory, 1-23 DatabaseExportFrequencyHrs, 1-23 DatabaseExportPath, 1-23 DiscoveryPeriod, 1-23 EMSTL1DataDictionaryFile, 1-23 GatewayTL1MetadataFile, 1-23 JdmkGatewayConnectorType, 1-23 JdmkGatewayPortNumber, 1-23 JdmkGatewayRmiAddress, 1-23 JdmkRequestTimeout, 1-23 MainBEServerIpAddress, 1-24 MaxNoOfUserSessions, 1-24 MBeanDBCacheMax, 1-23 MBeanDBCacheMin, 1-23 MBeanDBProcessCaching, 1-23 MBeanDBProcessConfigFile, 1-23 PerformanceDatabase, 1-24 PerformanceDatabasePassword, 1-24 PerformanceDatabasePort, 1-24 PerformanceDatabaseUser, 1-24 PerformanceDataCollectPeriod, 1-24 PerformanceDataRemovalPeriod, 1-24 ReportHost, 1-24 ReportOutputDirectory, 1-24 ReportRemovalPeriod, 1-24 ReportScriptDirectory, 1-24 SecurityAccessRightsFile, 1-24, 1-25 SecurityOnOffFlag, 1-25 ServerRole, 1-25 SessionHTMLConnector, 1-25 SessionHtmlPort, 1-25 SessionHTTPConnector, 1-25 SessionHttpPort, 1-25 SessionHTTPSConnector, 1-25 SessionHttpsPort, 1-25 SessionRmiAddress, 1-25 SessionRMIConnector, 1-25 SessionRmiPort, 1-25 SnmpAgentEmsHost, 1-26 SnmpAgentEnable, 1-25 SnmpAgentHtmlAdaptorPort, 1-26 SnmpAgentSnmpAdaptorPort, 1-26 SnmpAgentSnmpTrapsPort, 1-26 Page 2 Turin Networks Release TN3.1.x

85 Server parameters, descriptions (continued) SnmpCurrentCounterValidity, 1-26, 2-17 SSL_KeyValidity, 1-24 SSL_PublicKeyStorePassword, 1-24 SSL_PublicKeyStorePath, 1-24 STANDARD, 1-24 TE100TL1DataDictionaryFile, 1-26 TL1EmsConnectorType, 1-26 TL1EmsHost, 1-26 TL1LoggingEnabled, 1-26 TL1PasswordEncryption, 1-26 TL1TcpIpPort, 1-26 TL1TelnetPort, 1-26 TraverseTL1DataDictionaryFile, 1-26 UserImagesDirectory, 1-26 UserPreferencesDirectory, 1-26 ServerRole, server parameter, 1-25 Session, server component, 1-21 SessionHTMLConnector, server parameter, 1-25 SessionHtmlPort, server parameter, 1-25 SessionHTTPConnector, server parameter, 1-25 SessionHttpPort, server parameter, 1-25 SessionHTTPSConnector, server parameter, 1-25 SessionHttpsPort, server parameter, 1-25 SessionRmiAddress, server parameter, 1-25 SessionRMIConnector, server parameter, 1-25 SessionRmiPort, server parameter, 1-25 SNMP configure the SNMP ACL, 2-15 ems.mib, 2-13 enable the SNMP agent on server, 2-14 Ethernet PM, 2-17 gateway, server component, 1-21 MIB, 2-13 SNMP (continued) SnmpAgentEmsHost, server parameter, 1-26 SnmpAgentEnable, server parameter, 1-25 SnmpAgentHtmlAdaptorPort, server parameter, 1-26 SnmpAgentSnmpAdaptorPort, server parameter, 1-26 SnmpAgentSnmpTrapsPort, server parameter, 1-26 SnmpCurrentCounterValidity, server parameter, 1-26, 2-17 SSL_KeyValidity, server parameter, 1-24 SSL_PublicKeyStorePassword, server parameter, 1-24 SSL_PublicKeyStorePath, server parameter, 1-24 STANDARD, server parameter, 1-24 T TE100TL1DataDictionaryFile, server parameter, 1-26 TL1 gateway, server component, 1-21 TL1EmsConnectorType, server parameter, 1-26 TL1EmsHost, server parameter, 1-26 TL1LoggingEnabled, server parameter, 1-26 TL1PasswordEncryption, server parameter, 1-26 TL1TcpIpPort, server parameter, 1-26 TL1TelnetPort, server parameter, 1-26 TL1TraverseTL1DataDictionaryFile, server parameter, 1-26 Topology, server component, 1-21 U UserImagesDirectory, server parameter, 1-26 UserPreferencesDirectory, server parameter, 1-26 Release TN3.1.x Turin Networks Page 3

86 Page 4 Turin Networks Release TN3.1.x

87

88 Visit our website at: Release TN3.1.x TransNav Management System Documentation TN31