TransNav Management System Documentation. Management Server Guide

Transcription

1 Force10 Networks Inc. TransNav Management System Documentation Management Server Guide Release TN4.2.2 Publication Date: April 2009 Document Number: TN422 Rev. A

2 Copyright 2009 Force10 Networks, Inc. All rights reserved. Force10 Networks reserves the right to change, modify, revise this publication without notice. Trademarks Force10 Networks and E-Series are registered trademarks of Force10 Networks, Inc. Traverse, TraverseEdge, TraversePacketEdge, TransAccess, are registered trademarks of Force10 Networks, Inc. Force10, the Force10 logo, and TransNav are trademarks of Force10 Networks, Inc. or its affiliates in the United States and other countries and are protected by U.S. and international copyright laws. All other brand and product names are registered trademarks or trademarks of their respective holders. Statement of Conditions In the interest of improving internal design, operational function, and/or reliability, Force10 Networks, Inc. reserves the right to make changes to products described in this document without notice. Force10 Networks, Inc. does not assume any liability that may occur due to the use or application of the product(s) described herein.

3 TRANSNAV MANAGEMENT SYSTEM SERVER GUIDE Contents 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 TN4.2.2 Force10 Networks Page i

4 TransNav Server Guide, Page ii Force10 Networks Release TN4.2.2

5 SECTION 1 INSTALLATION AND DESCRIPTION Contents Chapter 1 Installation for Solaris Workstations 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 Workstation What is the All-In-One Online Help System? Contents Index Search Favorites About the Java and JavaScript Implementations Install Help Files from the Force10 Infocenter (Solaris) Remove Server Software from Solaris Workstation Chapter 2 Installation for Windows Workstations Before You Install Server Software Install Server Software on a Windows Workstation Install Server Online Help Files on a Windows Workstation What is the All-In-One Online Help System? Contents Index Search Favorites About the Java and JavaScript implementations Install Help Files from the Force10 Infocenter (Windows) Uninstall Server Software from Windows Workstation Chapter 3 Management Server Administration Using Multiple Servers Server Administration Tool Description Server Administration Components Description Management Server Parameters Management Server Parameters for TE-206 Nodes Release TN4.2.2 Force10 Networks Page i

6 TransNav Server Guide, Section 1 Installation and Description Page ii Force10 Networks Release TN4.2.2

7 SECTION 2INSTALLATION 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 2-1 Install Server Software on a Solaris Workstation, page 2-2 Run the Server as a Daemon, page 2-3 Install Server Online Help Files on a Solaris Workstation, page 2-4 Remove Server Software from Solaris Workstation, page 2-9 See Chapter 2 Installation for Windows Workstations, page 3-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 2-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. See the TransNav Management System Product Overview Guide, 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 Management Software from the Force10 Infocenter. See Section 2 Management Server s for detailed procedures on initializing, starting, stopping, and maintaining the TransNav management server. Release TN4.2.2 Force10 Networks Page 2-1

8 TransNav Server Guide, Section 2: Installation and Description Install Server Software on a Solaris Workstation Install Server Software on a Solaris Workstation Note: Use this procedure to install the management server software on a Solaris workstation. Table 2-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 2-1 before you start this procedure. 2 On your Solaris system, ensure the Force10 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 2-3. Page 2-2 Force10 Networks Release TN4.2.2

9 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 2-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. Note: Each time the daemon script is run, it overwrites the previous version. 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) Release TN4.2.2 Force10 Networks Page 2-3

10 TransNav Server Guide, Section 2: Installation and Description Install Server Online Help Files on a Solaris Workstation Table 2-3 Run the Server as a Daemon (continued) 5 Enter Y to continue the installation. 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 Workstation, page 2-4. Install Server Online Help Files on a Solaris Workstation What is the All-In-One Online Help System? To learn more about the All-In-One, see What is the All-In-One Online Help System?, page 2-4. To install the online help files, see Install Help Files from the Force10 Infocenter (Solaris), page 2-6. TThe (HTML-based) All-In-One Documentation is the basis for the management system software online help mechanism. The online help system provides access to the complete documentation set and includes the following guides: Figure 2-1 All-In-One Online Help System Contents Page 2-4 Force10 Networks Release TN4.2.2

11 Chapter 1 Installation for Solaris Workstations What is the All-In-One Online Help System? Contents Index Search The table of Contents makes it convenient to view pages from any guide. This tab displays a fully integrated index of all guides. This tab contains a search text box that allows you to enter any word or group of words. The results (across all guides) display here as well. Favorites This tab allows you to save any page for future reference. If you often look up a particular subject, you can bookmark it here. Note: The All-In-One HTML help system is a Java implementation that uses a Java applet to display the Contents, Index, Search, and Favorites tabs. If your browser does not have Java enabled, then JavaScript will be used and you will not see a Favorites tab. If both Java and JavaScript are disabled on your browser, the browser will not be able to display the All-In-One help system. Note: The Java implementation is not supported by Internet Explorer on UNIX or Netscape 6.0 on any platform. For these browser/platform combinations, the JavaScript implementation is always used. Netscape 6.1 and later are supported, but Netscape 6.0 is not supported on any platform. About the Java and JavaScript Implementations Each WebWorks Help system incorporates two distinct implementations: one based on Java and the other based on JavaScript. The Java implementation uses a Java applet to display the Contents, Index, Search, and Favorites tabs. The JavaScript implementation provides similar functionality using only JavaScript. If Java is enabled in a user s browser, the user can successfully view either the Java or JavaScript implementation. If Java is disabled in the user s browser, the user can only run the JavaScript implementation. If both Java and JavaScript are disabled in the user s browser, the browser will not be able to display a WebWorks Help system. By default, each WebWorks Help system you create includes support for both the Java and JavaScript implementations. When a user launches your Help system, WebWorks Help tries first to run the Java implementation. If Java is disabled in the user s browser or if the Java applet fails to load for some other reason, the JavaScript implementation is automatically used instead. The Java implementation allows the four Help tabs (Contents, Index, Search, and Favorites) to display; the JavaScript implementation displays a modified search feature which includes only the Contents, Index, and Search tabs. To determine which implementation is displayed, open the WebWorks Help system. On your browser, review the string in the Address locator bar. If it includes /js/, the JavaScript implementation is used. Change /js/ to /java/ and click Enter. Note: The Java implementation is not supported by Internet Explorer on UNIX. For these browser/platform combinations, the JavaScript implementation is always used. Release TN4.2.2 Force10 Networks Page 2-5

12 TransNav Server Guide, Section 2: Installation and Description Install Help Files from the Force10 Infocenter (Solaris) You can configure a WebWorks Help system to use only the JavaScript implementation. You might do this for any of the following reasons: Your users are under security or firewall constraints that prohibit Java applets. You know that your users do not have Java enabled in their browsers. You are principally supporting browsers that are not compatible with the Java implementation. The JavaScript implementation provides better performance for some Help systems. Install Help Files from the Force10 Infocenter (Solaris) Use this procedure to install help files from the Infocenter to the management server on a Solaris workstation. Important: User registration is required to access the Infocenter. If you do not have a current CustomerID and password, contact your sales account team to register. Table 2-4 Install Help Files from the Infocenter (Solaris) 1 On your Solaris workstation, open an internet browser window. 2 In the Address bar, enter the address: 3 In the Infocenter login, enter the <username> and <password> provided by the webmaster and click OK to enter your site. Page 2-6 Force10 Networks Release TN4.2.2

13 Chapter 1 Installation for Solaris Workstations Install Help Files from the Force10 Infocenter (Solaris) Table 2-4 Install Help Files from the Infocenter (Solaris) (continued) 4 In the customer portal, click the Technical Documentation drop-down menu and select the Technical Product Documentation link to open an index page. Figure 2-2 Traverse User Documentation Index Locate and click the All-in-One Documentation download link that corresponds to your current TransNav management system release base. 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 2-3 Save As Dialog Box Release TN4.2.2 Force10 Networks Page 2-7

14 TransNav Server Guide, Section 2: Installation and Description Install Help Files from the Force10 Infocenter (Solaris) Table 2-4 Install Help Files from the Infocenter (Solaris) (continued) 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. 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. 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. Close Window menu button Figure 2-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 2 Installation and Overview, Chapter 3 Starting the Graphical User Interface, page The Install Help Files from the Infocenter (Solaris) procedure is complete. Continue to the server procedures in Section 2 Management Server s. Page 2-8 Force10 Networks Release TN4.2.2

15 Chapter 1 Installation for Solaris Workstations 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 2-5 Remove Server Software from Solaris Workstation 1 Perform the software upgrade. See Upgrade Server Software, 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. Release TN4.2.2 Force10 Networks Page 2-9

16 TransNav Server Guide, Section 2: Installation and Description Remove Server Software from Solaris Workstation Page 2-10 Force10 Networks Release TN4.2.2

17 SECTION 3 INSTALLATION 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 and customize the map view. Before You Install Server Software, page 3-11 Install Server Software on a Windows Workstation, page 3-12 Install Server Online Help Files on a Windows Workstation, page 3-13 Install Help Files from the Force10 Infocenter (Windows), page 3-16 Uninstall Server Software from Windows Workstation, page 3-20 See Chapter 1 Installation for Solaris Workstations, page 2-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 3-6 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 Guide, Section 2 Management System Planning, Chapter 1 TransNav Management System Requirements, page 2-1. You can use the user interface (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 Management Software from the Force10 Infocenter. Release TN4.2.2 Force10 Networks Page 3-11

18 TransNav Server Guide, Section 3: Installation and Description Install Server Software on a Windows Workstation Table 3-6 Before You Install the Server Software (continued) Requirement Software upgrade Server administration procedures Reference If this is a software upgrade, ensure the server is disabled as a service and verify the Data Execution Prevention (DEP) service is correctly set up. See Section 2 Management Server s, Disable 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 3-7 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 3-11 before you start this procedure. 2 Download the TransNav server release software for Windows from the Force10 Infocenter to a directory on the server. 3 In a Windows Explorer window, navigate to the directory that contains the EMS software. 4 Double-click the file PCSetup.exe to start the installation process. Figure 3-5 Executive File in Explorer Window Page 3-12 Force10 Networks Release TN4.2.2

19 Chapter 2 Installation for Windows Workstations What is the All-In-One Online Help System? Table 3-7 Install Server Software on a Windows Workstation (continued) 5 The Installer Wizard appears. Figure 3-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 3-13 Install Server Online Help Files on a Windows Workstation What is the All-In-One Online Help System? To learn more about the All-In-One, see What is the All-In-One Online Help System?, page To install the online help files to the server, see Install Help Files from the Force10 Infocenter (Windows), page 3-16 The (HTML-based) All-In-One Documentation, available on the Force10 Infocenter, is the basis for the management system software online help mechanism. Release TN4.2.2 Force10 Networks Page 3-13

20 TransNav Server Guide, Section 3: Installation and Description What is the All-In-One Online Help System? This online help system provides access to the complete documentation set and includes the following guides: Figure 3-7 All-In-One Online Help System Contents 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 one word or a phrase or group of words. The results (across all guides) display here as well. Favorites This tab allows you to save any page for future reference. If you often look up a particular subject, you can bookmark it here. Note: The All-In-One HTML help system is a Java implementation that uses a Java applet to display the Contents, Index, Search, and Favorites tabs. If your browser does not have Java enabled, then JavaScript will be used and you will not see a Favorites tab. If both Java and JavaScript are disabled on your browser, the browser will not be able to display the All-In-One help system. Note: The Java implementation is not supported by Internet Explorer on UNIX. About the Java and JavaScript implementations Each WebWorks Help system incorporates two distinct implementations: one based on Java and the other based on JavaScript. The Java implementation uses a Java applet to display the Contents, Index, Search, and Favorites tabs. The JavaScript implementation provides similar functionality using only JavaScript. Page 3-14 Force10 Networks Release TN4.2.2

21 Chapter 2 Installation for Windows Workstations What is the All-In-One Online Help System? If Java is enabled in a user's browser, the user can successfully view either the Java or JavaScript implementation. If Java is disabled in the user's browser, the user can only run the JavaScript implementation. If both Java and JavaScript are disabled in the user's browser, the browser will not be able to display a WebWorks Help system. By default, each WebWorks Help system you create includes support for both the Java and JavaScript implementations. When a user launches your Help system, WebWorks Help tries first to run the Java implementation. If Java is disabled in the user's browser or if the Java applet fails to load for some other reason, the JavaScript implementation is automatically used instead. Note: The Java implementation is not supported by Internet Explorer on UNIX. You can configure a WebWorks Help system to use only the JavaScript implementation. You might do this for any of the following reasons: Your users are under security or firewall constraints that prohibit Java applets. You know that your users do not have Java enabled in their browsers. You are principally supporting browsers that are not compatible with the Java implementation. The JavaScript implementation provides better performance for some Help systems. Release TN4.2.2 Force10 Networks Page 3-15

22 TransNav Server Guide, Section 3: Installation and Description Install Help Files from the Force10 Infocenter (Windows) Install Help Files from the Force10 Infocenter (Windows) Use this procedure to install the help files from the Force10 Infocenter to the management server on a Windows workstation. Important: User registration is required to access the Force10 Infocenter. If you do not have a current CustomerID and password, contact your sales account team to register. Table 3-8 Install Help Files from the Force10 Infocenter (Windows) 1 On your Windows workstation, open an internet browser window. 2 In the Address bar, enter the address: 3 In the Force10 Infocenter login (located in the bottom left corner of the Force10 Networks Infocenter webpage), enter the <Log-in Name> and <Password> provided by the Force10 webmaster and click OK to enter your site. Figure 3-8 Infocenter Login Screen Page 3-16 Force10 Networks Release TN4.2.2

23 Chapter 2 Installation for Windows Workstations Install Help Files from the Force10 Infocenter (Windows) Table 3-8 Install Help Files from the Force10 Infocenter (Windows) (continued) 4 In the customer portal, click the Technical Documentation drop-down menu and select the Force10 Traverse User Documentation link to open an index page. Figure 3-9 Force10 Traverse User Documentation Index Locate and click the All-in-One Documentation download link that corresponds to your current TransNav management system release base. Release TN4.2.2 Force10 Networks Page 3-17

24 TransNav Server Guide, Section 3: Installation and Description Install Help Files from the Force10 Infocenter (Windows) Table 3-8 Install Help Files from the Force10 Infocenter (Windows) (continued) 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 3-10 File Download Dialog Box 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. Page 3-18 Force10 Networks Release TN4.2.2

25 Chapter 2 Installation for Windows Workstations Install Help Files from the Force10 Infocenter (Windows) Table 3-8 Install Help Files from the Force10 Infocenter (Windows) (continued) 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 3-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 2 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 TN4.2.2 Force10 Networks Page 3-19

26 TransNav Server Guide, Section 3: Installation and Description Uninstall Server Software from Windows Workstation Uninstall Server Software from Windows Workstation After upgrading the server software, you may want to remove the previous version of the online help. 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 3-9 Uninstall Server Software from Windows Workstation 1 Perform the software upgrade. See Upgrade Server Software, page Ensure that the server is stopped. See Stop the Server, page From the Start menu, select Programs > Force10_Networks> Uninstall TransNav Management System. 4 The Uninstaller Wizard appears. Figure 3-12 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. Page 3-20 Force10 Networks Release TN4.2.2

27 SECTION 4 INSTALLATION 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 Server Administration Tool Description Server Administration Components Description Management Server Parameters 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 TN4.2.2 Force10 Networks Page 4-21

28 TransNav Server Guide, Section 4: Installation and Description Server Administration Tool Description Primary and Secondary servers do not communicate to each other. To keep information on the 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. Depending on the network size, the process of importing the Primary server database should take between one and five minutes. 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). The Server Admin dialog box appears. Figure 4-13 Server Admin Tool Page 4-22 Force10 Networks Release TN4.2.2

29 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. WebCraft Proxy: Provides passthrough from TransNav management server to TE-206 nodes To exit from the server administration functions, select Exit from the File menu or click Close (indicated by a red X ) in the top right corner of the dialog box. Release TN4.2.2 Force10 Networks Page 4-23

30 TransNav Server Guide, Section 4: 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. If your system includes TE-206 nodes, additional configuration steps are required. For more information, see Management Server Parameters for TE-206 Nodes. In the Server Admin tool, from the Execution menu click Configure Server, then click Parameter. The Execution Configuration dialog box displays. Figure 4-14 Execution Configuration Dialog Box 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 Force10 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. 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). 1 Do not change these parameters. Contact the Force10 Technical Assistance Center for assistance. Page 4-24 Force10 Networks Release TN4.2.2

31 Chapter 3 Management Server Administration Management Server Parameters 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. MainBEServerIpAddress 1 : IP address of the back end server (for distributed server only). MaxNoOfRowsInReport (thousands): Indicates the maximum number of rows of data to display in each performance monitoring report. Large reports may affect server performance while running. Default is 500 rows. MaxNoOfUserSessions: The maximum number of combined simultaneous user sessions logged into any of the user interfaces (GUI, CLI, or TL1). Default is 20. PerformanceDataCollectPeriodTraverse (minutes): Number of minutes between two uploads of performance data from the Traverse agent. Default is 15 minutes. PerformanceDataCollectPeriodTE206 (minutes): Number of minutes for TransNav to collect performance data from all TE-206 nodes in sequence. Default is 480 minutes (8 hours). This value must be set high enough to allow TransNav to collect data from all nodes. For example, if 45 nodes exist in the system, and it takes 5 minutes to collect data from each node, this value should be set to 225 minutes (45 x 5 = 225). 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. Release TN4.2.2 Force10 Networks Page 4-25

32 TransNav Server Guide, Section 4: Installation and Description Management Server Parameters PingClientPollLimit: Default is is this in minutes?? PingClientTimeotLimit: (is timeout misspelled??) Default is 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 STANDARD: Indicates the current commissioning parameter value: ANSI_default, ITU_default, or ANSI_ONLY. 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. SessionHTTPSConnector: Enables or disables the JDMK HTTP over SSL for a secure HTTP connection to the 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 Page 4-26 Force10 Networks Release TN4.2.2

33 Chapter 3 Management Server Administration Management Server Parameters 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. 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 (default): Password encryption is not enabled. Release TN4.2.2 Force10 Networks Page 4-27

34 TransNav Server Guide, Section 4: Installation and Description Management Server Parameters for TE-206 Nodes 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. Default is images. UserPreferencesDirectory 1 : Directory for storing the GUI user preferences. WebCraftEnabled: Indicates if the TransNav server is enabled to manage TE-206 nodes. true: TransNav is enabled to manage TE-206 nodes. false: TransNav can not manage TE-206 nodes. WebCraftRemoteLoginTimeout (seconds): Indicates the amount of time, in seconds, required for the TransNav server to automatically authenticate and launch TN-Sight. Default is 45 seconds. To prevent the system from timing out during the logon process, Force10 recommends resetting the value in this parameter to a higher number of seconds, particularly if you have a distant TE-206 node on DCC. 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. Management Server Parameters for TE-206 Nodes This section defines the TransNav management server parameters that are required for the TransNav GUI to manage TE-206 nodes. In the Server Admin tool, from the Execution menu click Configure Server, then click Parameter. The Execution Configuration dialog box displays. First, scroll to the WebCraftEnabled parameter and change the value to true. WebCraftEnabled: Indicates if the TransNav server is enabled to manage TE-206 nodes. true: TransNav is enabled to manage TE-206 nodes. false: TransNav can not manage TE-206 nodes. Next, set the following parameters in the order given: WebCraftRemoteLoginTimeout (seconds): Indicates the amount of time, in seconds, required for the TransNav server to automatically authenticate and launch TN-Sight. Default is 45 seconds. To prevent the system from timing out during the logon process, Force10 recommends resetting the value in this parameter to a higher number of seconds, particularly if you have a distant TE-206 node on DCC. PerformanceDataCollectPeriodTE-206 (minutes): Number of minutes for TransNav to collect performance data from all TE-206 nodes in sequence. Default is 480 minutes (8 hours). This value must be set high enough to allow TransNav to collect data from Page 4-28 Force10 Networks Release TN4.2.2

35 Chapter 3 Management Server Administration Management Server Parameters for TE-206 Nodes all nodes. For example, if 45 nodes exist in the system, and it takes 5 minutes to collect data from each node, this value should be set to 225 minutes (45 x 5 = 225). MaxNoOfRowsInReport (thousands): Indicates the maximum number of rows of data to display in each performance monitoring report. Generated report output is stored on the server. Large reports may affect server performance while running. Default is 500 rows. Output generated for TE-206 performance monitoring reports is stored on the TransNav server in the report directory under the output folder. Release TN4.2.2 Force10 Networks Page 4-29

36 TransNav Server Guide, Section 4: Installation and Description Management Server Parameters for TE-206 Nodes Page 4-30 Force10 Networks Release TN4.2.2

37 SECTION 2 MANAGEMENT SERVER PROCEDURES Contents Chapter 1 Creating the Management Servers Before You Create the Management Servers Start the Server Administration Tool Configure Management Server Parameters Configure Management Server Parameters for TE-206 Nodes 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 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 Start the Server Administration Tool Initialize the Database Enable the Server as a Service (Windows) Start the Server Export the Database Manually Export the Database Automatically Export the Database Stop the Server Promoting a Secondary Server to the Primary Role Disable Server as a Service (Windows) Modify DEP Settings on Server (Windows) Upgrade Server Software Download the Management Software from the Turin Infocenter Release TN4.2.2 Force10 Networks Page i