TransNav Management System Documentation. Management Server Guide

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

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.

TRANSNAV MANAGEMENT SYSTEM SERVER GUIDE Contents Section 1 Installation and Description Chapter 1 Installation for Solaris Workstations............................... 1-1 Chapter 2 Installation for Windows Workstations.............................. 1-11 Chapter 3 Management Server Administration............................... 1-21 Section 2 Management Server s Chapter 1 Creating the Management Servers................................ 2-5 Chapter 2 Management Server SNMP..................................... 2-21 Chapter 3 Server Administration s................................. 2-27 Index......................................................... Index-1 Release TN4.2.2 Force10 Networks Page i

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

SECTION 1 INSTALLATION AND DESCRIPTION Contents Chapter 1 Installation for Solaris Workstations Before You Install Server Software................................. 1-1 Install Server Software on a Solaris Workstation...................... 1-2 Run the Server as a Daemon..................................... 1-3 Install Server Online Help Files on a Solaris Workstation................ 1-4 What is the All-In-One Online Help System?......................... 1-4 Contents................................................. 1-5 Index.................................................... 1-5 Search................................................... 1-5 Favorites................................................. 1-5 About the Java and JavaScript Implementations.................. 1-5 Install Help Files from the Force10 Infocenter (Solaris)................. 1-6 Remove Server Software from Solaris Workstation.................... 1-9 Chapter 2 Installation for Windows Workstations Before You Install Server Software................................. 1-11 Install Server Software on a Windows Workstation..................... 1-12 Install Server Online Help Files on a Windows Workstation.............. 1-13 What is the All-In-One Online Help System?......................... 1-13 Contents................................................. 1-14 Index.................................................... 1-14 Search................................................... 1-14 Favorites................................................. 1-14 About the Java and JavaScript implementations................... 1-14 Install Help Files from the Force10 Infocenter (Windows)................ 1-16 Uninstall Server Software from Windows Workstation.................. 1-20 Chapter 3 Management Server Administration Using Multiple Servers.......................................... 1-21 Server Administration Tool Description.............................. 1-22 Server Administration Components Description....................... 1-23 Management Server Parameters.................................. 1-24 Management Server Parameters for TE-206 Nodes.................... 1-28 Release TN4.2.2 Force10 Networks Page i

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

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

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

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

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... 3... done # Setting kill links for runlevels... 0... 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

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

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: www.force10networks.com 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

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

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 2-20. 11 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

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 2-49. 2 Ensure that the server is stopped. See Stop the Server, page 2-41. 3 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

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

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

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 2-45. 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

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

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

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

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: www.force10networks.com 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

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

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

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 2-20. 15 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

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 2-49. 2 Ensure that the server is stopped. See Stop the Server, page 2-41. 3 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

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

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

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

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

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

TransNav Server Guide, Section 4: Installation and Description Management Server Parameters PingClientPollLimit: Default is 120000 - is this in minutes?? PingClientTimeotLimit: (is timeout misspelled??) Default is 600000. 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 8082. SessionHttpPort: Port on which the JDMK HTTP connector is waiting for connections. Default is 8081. SessionHttpsPort: Port on which the JDMK HTTPS connector is waiting for connections. Default is 8084. Page 4-26 Force10 Networks Release TN4.2.2

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 7000. SnmpAgentSnmpAdaptorPort: Port on which the JDMK SNMP adaptor is waiting for SNMP requests. Default is 7001. SnmpAgentSnmpTrapsPort: Port to which the JDMK SNMP adaptor sends SNMP traps. Default is 7002. 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

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 7788. TL1TelnetPort: The telnet port on the server to which a user opens a TL1 session. Default is 7789. 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

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

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

SECTION 2 MANAGEMENT SERVER PROCEDURES Contents Chapter 1 Creating the Management Servers Before You Create the Management Servers......................... 2-1 Start the Server Administration Tool................................ 2-3 Configure Management Server Parameters.......................... 2-5 Configure Management Server Parameters for TE-206 Nodes........... 2-7 Set the Primary Management Server as the Primary NTP Source......... 2-9 Set NTP Server on a Solaris Workstation............................ 2-10 Set the NTP Server on a Windows 2000 Professional Workstation........ 2-11 Set the NTP Server on a Windows XP Workstation.................... 2-12 Configure Log and Error Files..................................... 2-16 Chapter 2 Management Server SNMP Supported SNMP MIBs.......................................... 2-17 Location of SNMP MIB File....................................... 2-17 Enable SNMP Agent............................................ 2-17 Configure the SNMP Access Control List............................ 2-19 Ethernet Performance Monitoring and SNMP......................... 2-20 Ethernet Interfaces......................................... 2-20 Performance Data.......................................... 2-21 Chapter 3 Server Administration s Start the Server Administration Tool................................ 2-24 Initialize the Database........................................... 2-25 Enable the Server as a Service (Windows)........................... 2-28 Start the Server................................................ 2-29 Export the Database............................................ 2-31 Manually Export the Database................................ 2-31 Automatically Export the Database............................ 2-33 Stop the Server................................................ 2-35 Promoting a Secondary Server to the Primary Role.................... 2-37 Disable Server as a Service (Windows)............................. 2-39 Modify DEP Settings on Server (Windows)........................... 2-40 Upgrade Server Software........................................ 2-43 Download the Management Software from the Turin Infocenter........... 2-44 Release TN4.2.2 Force10 Networks Page i

TransNav Server Guide, Section 2 Management Server s Import the Database............................................ 2-47 Retrieve Server Log Files........................................ 2-49 Setting Up Report Parameters..................................... 2-51 Customizing Background Images.................................. 2-54 Page ii Force10 Networks Release TN4.2.2

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-5 Start the Server Administration Tool, page 2-7 Configure Management Server Parameters, page 2-9 Configure Management Server Parameters for TE-206 Nodes, page 2-11 Set the Primary Management Server as the Primary NTP Source, page 2-13 Configure Log and Error Files, page 2-20 Note: The TransNav and TN-Xpert management system applications can co-exist and be run independently on a single workstation. The TransNav management system allows you to access the Traverse and TE-100 products, while the TN-Xpert management system application allows you to access the TE-206 nodes. Currently, the TE-206 nodes must be installed using the TN-Xpert management system and have an IP address assigned. The TE-206 nodes can then be discovered on the TransNav management system. For details on the TN-Xpert management system, see the TransNav Xpert Installation Guide and the TransNav Xpert Users Guide. Review the information in this topic before creating the TransNav 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. Reference Traverse Product Overview Guide TransNav Management System Product Overview Guide TraverseEdge 100 User Guide (optional) TraverseEdge 206 Users Guide (optional) TransNav Xpert Installation Guide (optional) TransNav Management System Product Overview Guide, Section 2 Management System Planning, Chapter 3 IP Address Planning This step depends on the server platform (Solaris or Windows) and local site practices. Contact your local site administrator. Release TN4.2.2 Force10 Networks Page 2-5

TransNav Server Guide, Section 2: Management Server s Before You Create the Management Servers Table 2-1 Before You Create the Management Servers (continued) Requirement 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 TransNav management servers. Telnet server application is installed. Reference Traverse Installation and Commissioning Guide TraverseEdge 100 User Guide (optional) TraverseEdge 206 Hardware Installation Guide (optional) TraverseEdge 206 Users Guide (optional) TransNav Xpert Installation Guide (optional) TransNav Xpert Users Guide (optional) TransNav Management System Server Guide, Section 1 Installation and Description Required to distribute TransNav software to network elements. Force10 recommends WAR FTP for Windows. Download the application for free from Adobe s site at: www.warftp.org. Required for remote access to the management servers. Page 2-6 Force10 Networks Release TN4.2.2

Chapter 1 Creating the Management Servers 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 a Terminal window: $./ems_admin.sh 4 The Server Admin dialog box displays. Figure 2-2 Server Admin Tool Release TN4.2.2 Force10 Networks Page 2-7

TransNav Server Guide, Section 2: Management Server s Start the Server Administration Tool Table 2-2 Start the Server Administration Tool (continued) 5 See the procedure, Server Administration Components Description, for a description of each server component. 6 The Start the Server Administration Tool procedure is complete. Page 2-8 Force10 Networks Release TN4.2.2

Chapter 1 Creating the Management Servers Configure Management Server Parameters 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 Force10 Technical Assistance Center for assistance in changing server administration parameters. Note: If you have TE-206 nodes in your system, also see Configure Management Server Parameters for TE-206 Nodes, page 2-11. Table 2-3 Configure Management Server Parameters 1 Start the Server Administration tool. See the procedure Start the Server Administration Tool. The Server Admin dialog box displays. 2 If the server is already started, stop the server. See the procedure Stop the Server. 3 From the Execution menu, click Configure Server, then click Parameter. Figure 2-3 Configure Server Parameters Release TN4.2.2 Force10 Networks Page 2-9

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 Figure 4-13 Server Admin Tool, 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. 6 Restart the server for the changes to take effect. See the procedure Table 2-14 Start the Server. 7 The Configure Management Server Parameters procedure is complete. Page 2-10 Force10 Networks Release TN4.2.2

Chapter 1 Creating the Management Servers Configure Management Server Parameters for TE-206 Nodes Configure Management Server Parameters for TE-206 Nodes If your network includes TE-206 nodes, the following additional management server parameters must be set. Table 2-4 Configure Management Server Parameters for TE-206 Nodes 1 Start the Server Administration tool if it is not already started. See the procedure Start the Server Administration Tool. The Server Admin dialog box displays. 2 From the Execution menu, click Configure Server, then click Parameter. Figure 2-5 Configure Server Parameters Release TN4.2.2 Force10 Networks Page 2-11

TransNav Server Guide, Section 2: Management Server s Configure Management Server Parameters for TE-206 Nodes Table 2-4 Configure Management Server Parameters for TE-206 Nodes 3 In the Execution Configuration dialog box, set the following parameters to manage TE-206 nodes from the TransNav management system. MaxNumberofRowsInReport (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,000 rows. Performance datacollectionperiod TE206: The interval at which the TransNav should start collecting 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). WebcCraftEnabled: Enables the Webcraft proxy server which acts as a proxy server allowing passthrough from the TransNav GUI to the TE-206 node. true: TransNav GUI is enabled to launch TE-206 shelf view (TN-Sight) false: TransNav GUI cannot launch TE-206 shelf view (TN-Sight) 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, Turin recommends resetting the value in this parameter to a higher number of seconds, particularly if you have a distant TE-206 node on DCC. See Section 4 Installation and Description, Chapter 3 Management Server Administration, Management Server Parameters for the descriptions of each parameter. 4 Click OK to close the Execution Configuration dialog box and return to the Server Admin tool. 5 Restart the server for the changes to take effect. See the procedure Table 2-14 Start the Server. 6 The Configure Management Server Parameters procedure is complete. Page 2-12 Force10 Networks Release TN4.2.2

Chapter 1 Creating the Management Servers Set the Primary Management Server as the Primary NTP Source 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-14 Set the NTP Server on a Windows 2000 Professional Workstation, page 2-15 For different types of configuration set-ups, refer to www.ntp.org. See the TransNav Management System Product Overview Guide, Section 2 Management System Planning, Chapter 4 Network Time Protocol (NTP) Sources 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. Release TN4.2.2 Force10 Networks Page 2-13

TransNav Server Guide, Section 2: Management Server s Set NTP Server on a Solaris Workstation 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-5 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 127.127.XType.0 prefer fudge 127.127.XType.0 stratum 0 To: server 127.127.1.1 fudge 127.127.1.1 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. Page 2-14 Force10 Networks Release TN4.2.2

Chapter 1 Creating the Management Servers 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-6 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. Release TN4.2.2 Force10 Networks Page 2-15

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 2000 Professional Workstation (continued) 9 Change the ReliableTimeSource value to 1. 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-7 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 Page 2-16 Force10 Networks Release TN4.2.2

Chapter 1 Creating the Management Servers Set the NTP Server on a Windows XP Workstation Table 2-7 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, then click OK. Figure 2-11 AnnounceFlags Edit DWORD Value Release TN4.2.2 Force10 Networks Page 2-17

TransNav Server Guide, Section 2: Management Server s Set the NTP Server on a Windows XP Workstation Table 2-7 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. Page 2-18 Force10 Networks Release TN4.2.2

Chapter 1 Creating the Management Servers Set the NTP Server on a Windows XP Workstation Table 2-7 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. Figure 2-15 Open DOS Command 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. Release TN4.2.2 Force10 Networks Page 2-19

TransNav Server Guide, Section 2: Management Server s Configure Log and Error Files Configure Log and Error Files Use this procedure to ensure the server is collecting log and error files for troubleshooting purposes. Table 2-8 Configure Log and Error Files 1 Start the server administration tool. See the procedure Start the Server Administration Tool. 2 From the Logging menu, click Configure. Figure 2-16 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-17 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. Page 2-20 Force10 Networks Release TN4.2.2

SECTION 2MANAGEMENT SERVER PROCEDURES Chapter 2 Management Server SNMP Introduction Supported SNMP MIBs Location of SNMP MIB File Enable SNMP Agent 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-21 Location of SNMP MIB File, page 2-21 Enable SNMP Agent, page 2-21 Configure the SNMP Access Control List, page 2-23 Ethernet Performance Monitoring and SNMP, page 2-24 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 2863 - the Interfaces Group MIB RFC 2819 - Remote Network Monitoring Management Information Base RFC 2665 - 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. Use the following procedure to allow the management system to receive SNMP queries and forward system events. Table 2-9 Enable SNMP Agent Components 1 Start the server administration tool. See the procedure Start the Server Administration Tool, page 2-7. 2 If the server is running, stop the server. See the procedure Stop the Server, page 2-41. Release TN4.2.2 Force10 Networks Page 2-21

TransNav Server Guide, Section 2: Management Server s Enable SNMP Agent Table 2-9 Enable SNMP Agent Components (continued) 3 From the Execution menu, click Configure Server, then click Parameter. Figure 2-18 Configure Server 4 In the Configure Server dialog box, configure the SNMP Agent components. Figure 2-19 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 7001. Set the SnmpAgentSnmpTrapsPort variable to the port on which the system sends SNMP traps; default is 7002. 5 Click OK to save the changes and close the Execution Configuration dialog box. 6 Restart the server. See the procedure Start the Server, page 2-34. 7 Continue to the procedure Configure the SNMP Access Control List, page 2-23. 8 The Enable SNMP Agent Components procedure is complete. Continue to the next procedure Configure the SNMP Access Control List, page 2-23. Page 2-22 Force10 Networks Release TN4.2.2

Chapter 2 Management Server SNMP Configure the SNMP Access Control List 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-10 Configure the SNMP Access Control List 1 Start the server administration tool. See the procedure Start the Server Administration Tool, page 2-7. 2 If the server is running, stop the server. See the procedure Stop the Server, page 2-41. 3 From the Execution menu, click Configure SNMP. Figure 2-20 Configure SNMP 4 The ACL file appears in a text editor window. 5 6 Figure 2-21 Edit the SNMP Access Control List 7 Release TN4.2.2 Force10 Networks Page 2-23

TransNav Server Guide, Section 2: Management Server s Ethernet Performance Monitoring and SNMP Table 2-10 Configure the SNMP Access Control List (continued) 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 2-34. 9 The Configure the SNMP Access Control List procedure is complete. 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 * 10 000 000 + PortIndex * 100 000 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. Page 2-24 Force10 Networks Release TN4.2.2

Chapter 2 Management Server SNMP Ethernet Performance Monitoring and SNMP 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. Data is collected from the time the PM collection is enabled on unlocked objects. Only data through the last collection period is shown. For example, if the PM collection is set to occur every 15 minutes and the last period that data was collected ended 5 minutes previously, the data collected in the last 5 minutes will not be available until the next collection period. 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 TN4.2.2 Force10 Networks Page 2-25

TransNav Server Guide, Section 2: Management Server s Ethernet Performance Monitoring and SNMP Page 2-26 Force10 Networks Release TN4.2.2

SECTION 2MANAGEMENT SERVER PROCEDURES Chapter 3 Server Administration s Introduction This chapter contains procedures for administration of the management system. Note: The TransNav and TN-Xpert management system applications can co-exist and be run independently on a single workstation. The TransNav management system allows you to access the Traverse and TE-100 products, while the TN-Xpert management system application allows you to access the TE-206 nodes. Currently, the TE-206 nodes must be installed using the TN-Xpert management system and have an IP address assigned. The TE-206 nodes can then be discovered on the TransNav management system. For details on the TN-Xpert management system, see the TransNav Xpert Installation Guide and the TransNav Xpert Users Guide. Server administration functions include the following procedures: Start the Server Administration Tool Initialize the Database Enable the Server as a Service (Windows) Start the Server Export (Backup) 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 Force10 Infocenter Import the Database Retrieve Server Log Files Setting Up Report Parameters Customizing Background Images Configuring DHCP Release TN4.2.2 Force10 Networks Page 2-27

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-11 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-22 Start Menu 3 On a Solaris platform, change to the directory where you installed the management software and enter the following command in a Terminal window: $./ems_admin.sh 4 The Server Admin dialog box displays. Figure 2-23 Server Admin Tool Page 2-28 Force10 Networks Release TN4.2.2

Chapter 3 Server Administration s Start the Server Administration Tool Table 2-11 Start the Server Administration Tool (continued) 5 See the procedure, Server Administration Components Description, for a description of each server component. 6 The Start the Server Administration Tool procedure is complete. Release TN4.2.2 Force10 Networks Page 2-29

TransNav Server Guide, Section 2: Management Server s Initialize the Database 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-12 Initialize the Database 1 Start the Server Administration tool. The Server Admin dialog box displays. See the procedure Start the Server Administration Tool. 2 From the Database menu, click Initialize. Figure 2-24 Initialize Database 3 If this is an existing server, confirm that you want to erase all previous provisioned data from the database. Otherwise, skip to 4. Figure 2-25 Database Initialize Confirmation Page 2-30 Force10 Networks Release TN4.2.2

Chapter 3 Server Administration s Initialize the Database Table 2-12 Initialize the Database (continued) 4 In the Database Initialization dialog box, first select the technology standard of the server. Figure 2-26 Database Initialization - Select Technology Standard 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. 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. 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. Release TN4.2.2 Force10 Networks Page 2-31

TransNav Server Guide, Section 2: Management Server s Initialize the Database Table 2-12 Initialize the Database (continued) Next, select the server role. Figure 2-27 Database Initialization - Select Server Role b. Select the role of the server being initialized: Primary (default): The server will be the Primary server in the network. There can be only one Primary server in a management domain. 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: The value in the ServerRole field on the Server Admin tool (Execution menu > Configure Server > Parameter) is set when the server is initialized. It will not change when the server role is changed using the CLI command. 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. c. Click Init. The initialization of the database begins. 5 The status of the initialization displays on the status bar in the Server Admin dialog box. status bar Figure 2-28 Server Status 6 The Initialize the Database procedure is complete. Continue to the next procedure Start the Server. Page 2-32 Force10 Networks Release TN4.2.2

Chapter 3 Server Administration s Enable the Server as a Service (Windows) 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-13 Enable the Server as a Service 1 The server must be stopped. To stop the server, see the procedure Stop the Server. 2 From the Execution menu, click Configure Server, then click Enable as Service. Figure 2-29 Enable as Service 3 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 TN4.2.2 Force10 Networks Page 2-33

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-14 Start the Server 1 Start the Server Administration tool. The Server Admin dialog box displays. See the procedure Start the Server Administration Tool. 2 From the Execution menu, click Start Server. Figure 2-30 Start Server Page 2-34 Force10 Networks Release TN4.2.2

Chapter 3 Server Administration s Start the Server Table 2-14 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-31 Component Status 4 When all the components are running, the Start the Server procedure is complete. Figure 2-32 Start Server Complete Release TN4.2.2 Force10 Networks Page 2-35

TransNav Server Guide, Section 2: Management Server s Export (Backup) the Database Export (Backup) 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 (explained in the procedure, Import the Database) on the Server Administration tool. The database can be exported manually or scheduled for automatic backup as defined in the following procedures. Manually Export the Database Table 2-15 Manually Export the Database 1 Before exporting the database, you may want to create a specific directory in which to store the exported database. 2 Start the Server Administration tool. The Server Admin dialog box displays. For instructions on starting the Server Administration tool, see the procedure Start the Server Administration Tool. 3 From the Database menu, click Export. Figure 2-33 Export Database 4 The Database Export dialog box displays. Click Browse. Figure 2-34 Database Export Dialog Box Page 2-36 Force10 Networks Release TN4.2.2

Chapter 3 Server Administration s Export (Backup) the Database Table 2-15 Manually Export the Database (continued) 5 The Select Export Path dialog box displays. Navigate to the directory where you plan to store the database. Figure 2-35 Database Export Dialog Box In the Folders list, select the directory where you plan to store the exported database (see 1 above), then click Select. The Database Export dialog box re-displays. Click OK. Within this Export Path, a subdirectory named Export_MM.DD.YYYY_HH.MM will be created, where MM.DD.YYYY is the date (month day year) and HH.MM (hour minute) is the time in US military format. The server database is saved under this subdirectory. Release TN4.2.2 Force10 Networks Page 2-37

TransNav Server Guide, Section 2: Management Server s Export (Backup) the Database Table 2-15 Manually Export the Database (continued) 6 The status of the export process displays on the status bar in the Server Admin dialog box. status bar Figure 2-36 Export Status 7 The Manually Export the Database procedure is complete. The status bar at the bottom of the screen will indicate the export is Done. status bar Figure 2-37 Export Database Complete If you are in the process of an upgrade, return to 3 of the Upgrade Server Software. Page 2-38 Force10 Networks Release TN4.2.2

Chapter 3 Server Administration s Export (Backup) the Database Scheduling the Server Database Backup Table 2-16 Scheduling the Server Database Backup 1 Before exporting the database, you may want to create a specific directory in which to store the exported database. 2 Start the Server Administration tool. The Server Admin dialog box displays. From the Database menu, click Export Scheduler. The Database Export Parameters dialog box displays. Figure 2-38 Database Export Parameters Dialog Box For information on how to start the Server Administration tool, see the procedure Start the Server Administration Tool. Note: Backups that were previously scheduled from the Server Admin > Execution > Configure Server > Parameters > Execution Configuration dialog box now display on the Database Export Parameters dialog box after your system is upgraded. Release TN4.2.2 Force10 Networks Page 2-39

TransNav Server Guide, Section 2: Management Server s Export (Backup) the Database Table 2-16 Scheduling the Server Database Backup (continued) 3 Set the following parameters to schedule when to backup the server database. Export Path: Use the Browse button to navigate to the directory where you plan to store the database. This field is required. Never (default): The server database files will never be backed up automatically. Every (x) hours: Enter the number of hours you want the server database to be backed up. Valid values are 1 to 1000. Daily at: Enter the time you want a daily backup of the database to occur. Weekly on: Enter the day of the week and the time of day that you want the server database to be backed up. Important: You must restart the server to have the changes made to these parameters take effect. Click OK to accept the changes or click Cancel. 4 The Scheduling the Server Database Backup procedure is complete. If you are in the process of an upgrade, return to 3 of the Upgrade Server Software. Page 2-40 Force10 Networks Release TN4.2.2

Chapter 3 Server Administration s Stop the Server 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-17 Stop the Server 1 Start the Server Administration tool. The Server Admin dialog box displays. See the procedure Start the Server Administration Tool. 2 From the Execution menu, click Stop Server. Figure 2-39 Stop Server 3 The server starts the shutdown process. Figure 2-40 Server Shutdown Process Release TN4.2.2 Force10 Networks Page 2-41

TransNav Server Guide, Section 2: Management Server s Stop the Server Table 2-17 Stop the Server (continued) 4 When all the components are stopped, the Stop the Server procedure is complete. Figure 2-41 Stop Server is Complete 5 If you are in the process of an upgrade, return to 5 of the Upgrade Server Software. Page 2-42 Force10 Networks Release TN4.2.2

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-18 Promoting a Secondary Server to the Primary Role 1 Turin recommends creating a backup of the database on the current Primary server. See the procedure Manually Export the Database. The backup captures recent server or domain-level changes to import to the database of the Secondary server being promoted. 2 Login to the Secondary server that is to be promoted to the role of Primary server and stop the server. See the procedure Stop the Server. 3 Import the copy of the backed up database from the original Primary server onto the Secondary server. Depending on the network size, this can take 1 to 5 minutes. See the procedure Import the Database. 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. Release TN4.2.2 Force10 Networks Page 2-43

TransNav Server Guide, Section 2: Management Server s Promoting a Secondary Server to the Primary Role Table 2-18 Promoting a Secondary Server to the Primary Role (continued) 5 Switch the Secondary server to the Primary server role using the following steps: a. Login to the Secondary server. b. From the server CLI, enter exec ems switch role Primary Note: The value in the ServerRole field on the Server Admin tool (Execution menu > Configure Server > Parameter) is set when the server is initialized. It will not change when the server role is changed using the CLI command. Until the original Primary server is demoted to a Secondary server role, two Primary servers will exist in the Traverse system. This ensures no alarms or events are lost. 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 Traverse system, some situations could occur involving node failure and recovery resulting in inconsistent node configuration. Force10 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. To switch the original Primary server to a Secondary server role, use the following steps: a. Login to the original Primary server. b. From the server CLI, enter exec ems switch role Secondary 7 The Promoting a Secondary Server to the Primary Role procedure is complete. Page 2-44 Force10 Networks Release TN4.2.2

Chapter 3 Server Administration s Disable Server as a Service (Windows) Disable 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-19 Disable Server as a Service 1 Start the Server Administration tool to disable the server as a service. The Server Admin dialog box displays. See the procedure Section 2 Management Server s, Table 2-2 Start the Server Administration Tool. 2 Stop the server. See the procedure Stop the Server. 3 From the Execution menu, click Configure Server, then click Disable as Service. Figure 2-42 Disable as Service 4 The Disable Server as a Service procedure is complete when (Enabled As Service) is removed from the header of the Server Admin dialog box. If you are in the process of an upgrade and have Windows 2003 Server, continue to the next procedure, Modify DEP Settings on Server (Windows). If you are in the process of an upgrade and do not have Windows 2003 Server, return to 6 of the Upgrade Server Software. Release TN4.2.2 Force10 Networks Page 2-45

TransNav Server Guide, Section 2: Management Server s Modify DEP Settings on Server (Windows) Modify DEP Settings on Server (Windows) If your server is running Windows 2003 Server, you may need to modify the DEP (Data Execution Prevention) settings to allow the Force10 system to function properly. You must be logged in as Administrator to disable the DEP service. Table 2-20 Disable DEP Service on Server 1 Right-click My Computer using the desktop icon or from Windows Explorer. Select Properties from the shortcut menu. The Systems Properties dialog box displays. 2 Click the Advanced tab. 3 In the Performance section, click Settings. Figure 2-43 System Properties Advanced tab The Performance Options dialog box displays. 4 Click the Data Execution Prevention tab. Figure 2-44 Data Execution Prevention tab Page 2-46 Force10 Networks Release TN4.2.2

Chapter 3 Server Administration s Modify DEP Settings on Server (Windows) Table 2-20 Disable DEP Service on Server There are two DEP modes; either may be used. Force10 recommends using the first method described: 1. Select Turn on DEP for essential Windows programs and services. This is a one-time action. Use when the server is on a secure network. 2. Select Turn on DEP for all programs and services except those I select. This option must be updated with the new Java executable after each TransNav installation. Navigate to the <TransNav installation directory>\jrex.x\bin where: X.X indicates the Force10 release number. Figure 2-45 Navigating the TransNav Installation Directory Select Java.exe and click Open. Figure 2-46 Select the Java Executable If you are running TransNav as a Windows service, you must also navigate to <TransNav installation directory>\ems_<release number>\db\bin Select solfe.exe and click Open. Release TN4.2.2 Force10 Networks Page 2-47

TransNav Server Guide, Section 2: Management Server s Modify DEP Settings on Server (Windows) Table 2-20 Disable DEP Service on Server Next, navigate to <TransNav installation directory>\ems_<release number>\lib\bin Select JavaService.exe and click Open. Next, navigate to <TransNav installation directory>\ems_<release number> Select JavaService.exe and click Open. Ensure the check box in the selection box in front of each service is selected. Click Apply. Click OK. Figure 2-47 Verify the Check boxes are Selected 5 The Disable DEP Service on Server procedure is complete. If you are in the process of an upgrade, return to 6 of the Upgrade Server Software. Page 2-48 Force10 Networks Release TN4.2.2

Chapter 3 Server Administration 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 control cards, then the remaining cards. For step-by-step node software upgrade procedures, refer to the Operations and Maintenance Guide, Section 7 Software Upgrades. Table 2-21 Upgrade Server Software 1 Download the correct version of the TransNav management system software from the Force10 Infocenter. See the procedure Download the Management Software from the Force10 Infocenter. Note: If you do not have access to the Force10 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, Uninstall the GUI from Windows Workstation. For UNIX workstations, see the TransNav Management System GUI Guide, Section 1 Installation and Overview, Chapter 2 Installation for Solaris Workstations, Uninstall the GUI from a Solaris Workstation. 3 Create a backup of the database on the current server. See the procedure Manually Export the Database. 4 Stop the server. See the procedure Stop the Server. 5 If this is a Windows workstation AND the server is enabled as a service, disable the server as a service and verify the Data Execution Prevention Settings are correctly set. See the procedures Disable Server as a Service (Windows) and Disable Server as a Service (Windows). 6 Install the new server software: For Solaris workstations, see Section 2 Installation and Description, Chapter 1 Installation for Solaris Workstations. For Windows workstations, see Section 1 Installation and Overview, Chapter 1 Installation for Windows Workstations. 7 Import the database that was saved in 3. See the procedure Import the Database. 8 Start the server. See the procedure Start the Server. Release TN4.2.2 Force10 Networks Page 2-49

TransNav Server Guide, Section 2: Management Server s Download the Management Software from the Force10 Infocenter Table 2-21 Upgrade Server Software (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. For UNIX workstations, see the TransNav Management System GUI Guide, Section 1 Installation and Overview, Chapter 2 Installation for Solaris Workstations. 10 The Upgrade Server Software procedure is complete. If you are in the process of a node software upgrade, return to 4 of the procedure Node Software Upgrade Process. Download the Management Software from the Force10 Infocenter Use this procedure to download the latest management server software from the Force10 Infocenter. Note: If you do not have access to the Force10 Infocenter, contact your local sales representative. Table 2-22 Download the Management Software from the Force10 Infocenter 1 On your computer, open an internet browser window. 2 In the Address bar, enter the address: www.force10networks.com 3 In the dialog box, enter your user name and password provided by the Force10 webmaster. Figure 2-48 Infocenter Login Screen Page 2-50 Force10 Networks Release TN4.2.2

Chapter 3 Server Administration s Download the Management Software from the Force10 Infocenter Table2-22 Download the Management Software from the Force10 Infocenter 4 From the Infocenter webpage, click the Software Downloads drop-down menu. Select Force10 EMS & flash Downloads to display the Force10 EMS and FLASH Downloads webpage. Figure 2-49 Software Downloads Drop-down Menu 5 In the Force10 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-50 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 release of software. To retrieve the online help files, see Section 2 Installation and Description, Chapter 1 Installation for Solaris Workstations or Chapter 2 Installation for Windows Workstations. Release TN4.2.2 Force10 Networks Page 2-51

TransNav Server Guide, Section 2: Management Server s Download the Management Software from the Force10 Infocenter Table 2-22 Download the Management Software from the Force10 Infocenter 6 Navigate to a user-defined directory to save the executable file and click Save. 7 The Download the Management Software from the Force10 Infocenter procedure is complete. Return to 2 of the procedure Upgrade Server Software. Page 2-52 Force10 Networks Release TN4.2.2

Chapter 3 Server Administration s Import the Database 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. Note: The server must be stopped before the import can occur. Table 2-23 Import the Database 1 Start the Server Administration tool. The Server Admin dialog box displays. See the procedure Start the Server Administration Tool. 2 From the Database menu, click Import. Figure 2-51 Import Database 3 Verify you want to continue the import. Click Yes to continue the import. Figure 2-52 Database Initialize Confirmation 4 The Database Import dialog box displays. Click Browse. Figure 2-53 Database Import Dialog Box Release TN4.2.2 Force10 Networks Page 2-53

TransNav Server Guide, Section 2: Management Server s Import the Database Table 2-23 Import the Database (continued) 5 The Select Import Path dialog box displays. Navigate to the directory where the previous database was exported. Select the file to be imported and click Select. Figure 2-54 Select Import Path Dialog Box 6 The Database Import dialog box re-displays with the Import Path field filled. Click OK. Figure 2-55 Database Import Dialog Box 7 When the status bar indicates that the import is done, the Import the Database procedure is complete. status bar Figure 2-56 Database Import Complete 8 If you are in the process of a server software upgrade, return to 8 of the procedure Upgrade Server Software. Page 2-54 Force10 Networks Release TN4.2.2

Chapter 3 Server Administration s Retrieve Server Log Files Retrieve Server Log Files Use this procedure to retrieve log and error files from the TransNav management server. The Force10 Technical Assistance Center uses these files troubleshoot server problems. Table 2-24 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. 2 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. 3 In a Windows Explorer window, select the logs directory. Figure 2-57 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. Go to 5. 4 On a Solaris platform, in a Terminal window, navigate to the EMS directory and type: $ tar -cf logs.tar logs/* $ gzip logs.tar Go to 5. Release TN4.2.2 Force10 Networks Page 2-55

TransNav Server Guide, Section 2: Management Server s Retrieve Server Log Files Table 2-24 Retrieve Server Log Files (continued) 5 Send the compressed file to the Force10 Technical Assistance Center for analysis. 6 The Retrieve Server Log Files procedure is complete. 1 Requires the popular compression application WinZip. See www.winzip.com/. Page 2-56 Force10 Networks Release TN4.2.2

Chapter 3 Server Administration s Setting Up Report Parameters Setting Up Report Parameters Use this procedure to set the report parameters for the server where generated SQL reports will be stored. The server should be one that is accessible to all users who need to view the generated report output. Table 2-25 Setting Up Report Parameters 1 On your computer, start the EMS server:./exec_admin.sh The Server Admin dialog box displays. 2 Select Execution, then Configure Server, then Parameter. Figure 2-58 Configure Server Report Parameters Release TN4.2.2 Force10 Networks Page 2-57

TransNav Server Guide, Section 2: Management Server s Setting Up Report Parameters Table 2-25 Setting Up Report Parameters (continued) 3 The Execution Configuration dialog box displays. Figure 2-59 Report Configuration Parameters Scroll to the Report parameters. Make changes to the following parameters as necessary. ReportHost: Indicates the IP address of the host EMS server on which the reports are run. ReportOutputDirectory: Indicates the directory on the EMS server where the reports are stored. ReportRemovalPeriod (days): Indicates the number of days report output files are stored. After the specified number of days, the system automatically deletes the files. Default is 7 days. ReportScriptDirectory: Indicates the directory on the EMS server where the SQL scripts used to collect PM template data are stored. Important: The size and number of stored output files could affect server performance. Page 2-58 Force10 Networks Release TN4.2.2

Chapter 3 Server Administration s Setting Up Report Parameters Table 2-25 Setting Up Report Parameters (continued) 4 To view the generated SQL reports, navigate to the directory where the server software is installed. Navigate the tree to the report folder, then open the output folder. Figure 2-60 Navigate to the Report Output Files 5 Select the desired report file and open using a text editor, 6 The Setting Up Report Parameters procedure is complete. Release TN4.2.2 Force10 Networks Page 2-59

TransNav Server Guide, Section 2: Management Server s Customizing Background Images Customizing Background Images Domain administrators can add additional images to use as the background image displayed in Map View on the TransNav server GUI. Up to 100 images, each 1M in size, can be scanned or copied from the web. The actual number of images that can be stored depends on the amount of available memory on your server. Additional images must be saved as.gif or.jpg images. Save the images in a file directory that is accessible from the server. Use this procedure to save an image. Table 2-26 Save Background Image for Map View 1 The background image to be used in the Map View must meet the following requirements: Format: GIF with a.gif (all lower case) extension or JPEG with a.jpg (all lower case) extension. Preferred Size: 836 x 664 pixels. 2 To load the maps into the TransNav GUI interface, logon to the GUI. 3 In Map View, right-click the background map and select Change Background. 4 The Load Background Image dialog box displays. Note: Two default map files exist: map_usa.gif and map_petaluma.gif. These maps cannot be deleted. Figure 2-61 Load Background Image Dialog Box Page 2-60 Force10 Networks Release TN4.2.2

Chapter 3 Server Administration s Customizing Background Images Table 2-26 Save Background Image for Map View 5 If adding a new image for the first time, click Import. The Open dialog box displays. Use the Look in field to navigate to the folder where the desired image file exists. If the image has been used previously, skip to 6. Figure 2-62 Open Dialog Box Release TN4.2.2 Force10 Networks Page 2-61

TransNav Server Guide, Section 2: Management Server s Customizing Background Images Table 2-26 Save Background Image for Map View 6 Select the image file name and click Open. The file name appears in the Load Background Image dialog box. Select the image to be used for the background and click Set. Click Done. Figure 2-63 Imported Image File 7 The Save Background Image for Map View procedure is complete. To change the name of group of nodes, see the TransNav Management System GUI Guide, Section 2 Administrative Tasks, Chapter 3 TransNav User Preferences, Changing Node Group Names. Page 2-62 Force10 Networks Release TN4.2.2

Chapter 3 Server Administration s Configuring DHCP Configuring DHCP Configuring DHCP from the TransNav server or from a node allows automatic IP configuration to a specified node. The server implementation is compliant with RFC213. Node-level users can then access the node via an Ethernet cable from the front Ethernet port on a GCM card. From the TransNav GUI, click a node in Map View to select the node to be configured. From the TransNav GUI or the Node-level GUI, select DHCP Configuration from the Admin menu to display the DHCP Configuration dialog box. Figure 2-64 DHCP Configuratipn Dialog Box GCM-A: Select this tab to configure the settings for the GCM card in the left-side slot on the shelf. GCM-B: Select this tab to configure the settings for the GCM card in the right-side slot on the shelf. IP from: Enter an IP address in the range for the GCM being configured. To determine the GCM IP address, from Shelf View click below the cards to display the Node view. Click the Config tab. The Node Configuration screen containing the IP address information displays. IP to: Enter a subnet IP address in the range of the GCM being configured. Gateway (Optional): Enter the IP address of the default gateway for the GCM being configured. Lease time (sec): Enter the number of seconds the node can be accessed by a node user for each session. Default is 6000 seconds. Enabled: Click the checkbox to enable the DHCP configuration on the selected GCM card. Release TN4.2.2 Force10 Networks Page 2-63

TransNav Server Guide, Section 2: Management Server s Configuring DHCP Command buttons are as follows: Show Lease: Displays a text box indicating the following information about a DHCP connection: the GCM s ID/MAC address, IP address, Subnet Mask if the connection is In-Use (True or False) the date/time when the connection (DHCP Lease) expires Update: Update any changes made to the configuration. Close: Close the DHCP Server Configuration dialog box. Page 2-64 Force10 Networks Release TN4.2.2

INDEX A administration, 2-9 AIO, see All-In-One All-In-One documentation, 1-13 implementation Java, 1-14 online help, 1-13 tabs contents, 1-14 favorites, 1-14 index, 1-14 search, 1-14 All-in-One documentation, 1-4 Java platform support, 1-5 requirements, 1-5 online help, 1-4 tabs contents, 1-5 index, 1-5 search, 1-5 Archive extract allinone.zip, 1-8, 1-18 unzip command, 1-8 zip tool, 1-18 B Backup database manually, 2-36 schedule, 2-39 C Card configuring DHCP, 2-63 D Database export manually, 2-36 scheduling, 2-39 parameters binary directory, 1-24 export path, 1-24 DHCP configure node, 2-63 E Ethernet PM SNMP, 2-24 Export database manually, 2-36 G Gateway CLI, 1-23 SNMP, 1-23 TL1, 1-23 H Help implementation Java, 1-14 JavaScript, 1-14 install files, customer portal Solaris, 1-6 Windows, 1-16 I IP address DHCP configuration, 2-63 M Management server configure parameters, 2-9 TE206 parameters, 2-11 server, help directory Solaris, 1-8 Windows, 1-18 Map view customize image, 2-60 N Node configuration DHCP, 2-63 Release TN4.2.2 Force10 Networks Index-1

Index O parameters DHCP, 2-63 Online help, see All-In-One Online help, see All-in-One S Schedule database backup, 2-39 Server Administration tool components, 1-23 starting, 2-7, 2-28 Server components administration, 1-23 alarm, 1-23 Apache, 1-23 CLI Gateway, 1-23 configuration, 1-23 database, 1-23 discovery, 1-23 event, 1-23 JDMKGateway, 1-23 map, 1-23 MBean, 1-23 network, 1-23 performance collection, 1-23 preprovisioning, 1-23 report, 1-23 RMI registry, 1-23 session, 1-23 SNMP gateway, 1-23 TL1 Gateway, 1-23 topology, 1-23 Server parameters AdminTraceLevel, 1-24 ANSITL1MetadataFile, 1-24 CliDataDictionaryFile, 1-24 CliEmsHost, 1-24 CliTelnetPort, 1-24 DatabaseBinDirectory, 1-24 DatabaseExportPath, 1-24 DiscoveryPeriod, 1-24 EMSTL1DataDictionaryFile, 1-24 GatewayTL1MetadataFile, 1-24 JdmkGatewayConnectorType, 1-24 JdmkGatewayPortNumber, 1-25 JdmkGatewayRmiAddress, 1-25 JdmkRequestTimeout, 1-25 MainBEServerIpAddress, 1-25 MaxNoOfRowsInReport TE-206, 1-29 MaxNoOfUserSessions, 1-25 MBeanDBCacheMax, 1-25 MBeanDBCacheMin, 1-25 MBeanDBProcessCaching, 1-25 MBeanDBProcessConfigFile, 1-25 PerformanceDatabase, 1-25 PerformanceDatabasePassword, 1-25 PerformanceDatabasePort, 1-25 PerformanceDatabaseUser, 1-25 PerformanceDataCollectPeriod, 1-25, 1-28 PerformanceDataRemovalPeriod, 1-25 ReportHost, 1-26 ReportOutputDirectory, 1-26 ReportRemovalPeriod, 1-26 ReportScriptDirectory, 1-26 SecurityAccessRightsFile, 1-26 SecurityOnOffFlag, 1-26 SessionHTMLConnector, 1-26 SessionHtmlPort, 1-26 SessionHTTPConnector, 1-26 SessionHttpPort, 1-26 SessionHTTPSConnector, 1-26 SessionHttpsPort, 1-26 SessionRmiAddress, 1-27 SessionRMIConnector, 1-27 SessionRmiPort, 1-27 SnmpAgentEmsHostr, 1-27 SnmpAgentEnable, 1-27 SnmpAgentHtmlAdaptorPort, 1-27 SnmpAgentSnmpAdaptorPort, 1-27 SnmpAgentSnmpTrapsPort, 1-27 SnmpCurrentCounterValidity, 1-27, 2-24 SSL_KeyValidity, 1-26 SSL_PublicKeyStorePassword, 1-26 SSL_PublicKeyStorePath, 1-26 TE100TL1DataDictionaryFile, 1-27 TL1EmsConnectorType, 1-27 TL1EmsHost, 1-27 TL1LoggingEnabled, 1-27 TL1PasswordEncryption, 1-27 TL1TcpIpPort, 1-28 TL1TelnetPort, 1-28 TraverseTL1DataDictionaryFile, 1-28 UserImagesDirectory, 1-28 UserPreferencesDirectory, 1-28 WebCraftEnabled TE-206, 1-28 WebCraftRemoteLoginTimeout TE-206, 1-28 Servers import database time, 1-22 Index-2 Force10 Networks Release TN4.2.2

Index multiple communication, 1-22 number of, 1-21 primary functions, 1-21 secondary functions, 1-21 updating database, 1-22 SNMP ems.mib, see SNMP Ethernet PM, 2-24 MIB, 2-21 T TE-206 management server required parameters, 2-11 W Web server, see Server components Release TN4.2.2 Force10 Networks Index-3

Index Index-4 Force10 Networks Release TN4.2.2

Visit our website at: www.force10networks.com Release TN4.2.2 TransNav Management System Documentation 800-0006-TN422