transnav server guide - force10networks.com · transnav server guide, ... server administration...

TransNav Management Server GuideRelease TN4.2.3 March 2010 Edition 1

Copyright © 2010 Force10 Networks, Inc.

All rights reserved. Force10 Networks ® reserves the right to change, modify, revise this publication without notice.

TrademarksForce10 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 ConditionsIn 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 DescriptionChapter 1Installation for Solaris Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Chapter 2Installation for Windows Workstations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13Chapter 3Management Server Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23

Section 2 Management Server ProceduresChapter 1Creating the Management Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Chapter 2Management Server SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23Chapter 3Server Administration Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1

Release TN4.2.3 Force10 Networks Page i

TransNav Server Guide

Page ii Force10 Networks Release TN4.2.3

SECTION 1 INSTALLATION AND DESCRIPTION

Contents

Chapter 1Installation for Solaris Workstations

Before You Install Management System Software . . . . . . . . . . . . . . . . . . . . . 1-1Install Management System Software on a Solaris Workstation. . . . . . . . . . . 1-2Run the Server as a Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Install Server Online Help Files on a Solaris Workstation . . . . . . . . . . . . . . . . 1-5What is the All-In-One Online Help System? . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Favorites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6About the Java and JavaScript Implementations . . . . . . . . . . . . . . . . . . 1-6

Install Help Files from the Force10 Website (Solaris) . . . . . . . . . . . . . . . . . . . 1-7Uninstall Server Software from Solaris Workstation . . . . . . . . . . . . . . . . . . . . 1-11

Chapter 2Installation for Windows Workstations

Before You Install Management System Software . . . . . . . . . . . . . . . . . . . . . 1-13Install Software on a Windows Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14Install Online Help Files on a Windows Workstation . . . . . . . . . . . . . . . . . . . . 1-17What is the All-In-One Online Help System? . . . . . . . . . . . . . . . . . . . . . . . . . 1-17

Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17Favorites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17About the Java and JavaScript implementations. . . . . . . . . . . . . . . . . . . 1-18

Install Help Files from the Force10 Website (Windows) . . . . . . . . . . . . . . . . . 1-19Uninstall the Management System Software from Windows Workstation. . . . 1-21

Chapter 3Management Server Administration

Using Multiple Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23Server Administration Tool Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24Server Administration Components Description . . . . . . . . . . . . . . . . . . . . . . . 1-25Management Server Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26Management Server Parameters for TE-206 Nodes. . . . . . . . . . . . . . . . . . . . 1-31


TransNav Server Guide, Section 1 Installation and Description


SECTION 1INSTALLATION AND DESCRIPTION

Chapter 1 Installation for Solaris Workstations

Introduction 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 a Sun Solaris server or client workstation. • Before You Install Management System Software• Install Management System Software on a Solaris Workstation• Run the Server as a Daemon• Install Server Online Help Files on a Solaris Workstation• Uninstall Server Software from Solaris Workstation

See Chapter 2—“Installation for Windows Workstations” for the procedures to install the management system on a Windows workstation.

Before You Install Management System Software

Before you install the management system software, understand the following requirements.

Table 1-1 Before You Install the Management System Software

Requirement Reference

Disable any operating system firewall applications that may be installed on this computer.

Contact your local site administrator.

Server requirements See the TransNav Management System Product Overview Guide, Section 2—Management System Planning, Chapter 1—“TransNav Management System Requirements”.

Server software includes the GUI application

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 Procedures, Chapter 3—“Server Administration Procedures,” Download the Management Software from the Force10 Website.

Server administration procedures See Section 2—Management Server Procedures for detailed procedures on initializing, starting, stopping, and maintaining the TransNav management server.

Release TN4.2.3 Force10 Networks Page 1-1

TransNav Server Guide, Section 1: Installation and DescriptionInstall Management System Software on a Solaris Workstation

Install Management System Software on a Solaris Workstation

Use this procedure to install the management system software on a Solaris workstation from the Force10 Networks corporate website. A Customer Portal Account is required. If you do not have a Customer Portal Account, you can request one from the Force10 website at www.force10networks.com by selecting Services & Support, then Account Request.

Note: If you will be managing TE-206 nodes from the TransNav management server, the download procedures are the same. For more information on setting up the TransNav server to manage TE-206 nodes, see Section 1—Installation and Description, Chapter 3—“Management Server Administration”.

Table 1-2 Install Management System Software on a Solaris Workstation

Step Procedure

Important: You must install and start the management system 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 Management System Software before you start this procedure.

2 Download the TransNav Management System software from the Force10 Networks corporate website (www.force10networks.com). From Services & Support, select Customer Login. Enter your Force10 User ID and Password, then click Login.

Right-click the software release to download the WinZip software file to a directory on your management server. The file must be able to be accessed by the current user. For any required help with this procedure, contact your system 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 Step 3.

For example:

$ cd /files/EMS

Page 1-2 Force10 Networks Release TN4.2.3

Chapter 1 Installation for Solaris WorkstationsInstall Management System Software on a Solaris Workstation

5 Type the following command to unzip and untar the management system software in one step.

For example:

$ gunzip -c /<yourdirectory>/*.gz | tar xvf -

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 must have the permissions on the directory files necessary to run the EMS server. To change permissions, contact your system administrator.

6 The Install Management System Software on a Solaris Workstation procedure is complete.

Continue to the next procedure: Run the Server as a Daemon, page 1-4.

Table 1-2 Install Management System Software on a Solaris Workstation

Step Procedure


TransNav Server Guide, Section 1: Installation and DescriptionRun the Server as a Daemon

Run the Server as a Daemon

Use this procedure to allow the server to restart on the workstation in case the workstation turns off or power cycles. This daemon restarts the server when the workstation starts again.

Important: You need Root access to the workstation on which the server is installed.

Table 1-3 Run the Server as a Daemon

Step Procedure

1 Complete the procedure: Install Management System Software on a Solaris Workstation.

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)


Chapter 1 Installation for Solaris WorkstationsWhat is the All-In-One Online Help System?

Install Server Online Help Files on a Solaris Workstation

To learn more about the All-In-One, see What is the All-In-One Online Help System?, page 1-5.

To install the online help files, see Install Help Files from the Force10 Website (Solaris), page 1-7.

What is the All-In-One Online Help System?

The All-In-One online help is HTML-based and 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 1-1 All-In-One Online Help System Contents

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 1-5.

Table 1-3 Run the Server as a Daemon (continued)

Step Procedure


TransNav Server Guide, Section 1: Installation and DescriptionWhat is the All-In-One Online Help System?

Contents

The table of Contents makes it convenient to view information for any topic. Each topic is comprised of guides defining specific details for that topic.

Index

This tab displays a fully integrated index of all guides.

Search

This tab contains a search text box that allows you to enter any word or group of words. 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.• The Java implementation is not supported by Internet Explorer on UNIX; the

JavaScript implementation is always used. You must have Java enabled on your browser to view the Favorites tab.

About the Java and JavaScript Implementations

Force10 uses a program by Quadralay WebWorks to produce the All-In-One help system. 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 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.

By default, each WebWorks Help system you create includes support for both the Java and JavaScript implementations. When a user launches the 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. For this browser/platform combination, the JavaScript implementation is always used. The Firefox browser is supported on UNIX.

You can configure a WebWorks Help system to use only the JavaScript implementation. This might be done 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.


Chapter 1 Installation for Solaris WorkstationsInstall Help Files from the Force10 Website (Solaris)

Rel

• 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 Website (Solaris)

Use this procedure to install the help files from the Force10 website to the management server on a Solaris workstation.

Table 1-4 Install Help Files from the Force10 website (Solaris)

Step Procedure

1 On your Solaris workstation, open an internet browser window.

2 In the Address bar, enter the address:

www.force10networks.com

3 From the Force10 website, select Services & Support, then click Documentation.

Figure 1-2 Force10 Website, Documentation Selection

ease TN4.2.3 Force10 Networks Page 1-7

www.turinnetworks.com

TransNav Server Guide, Section 1: Installation and DescriptionInstall Help Files from the Force10 Website (Solaris)

4 From the Documentation page, select the plus sign to the left of Force10 Traverse/TransNav All-in-One Files to expand the file and see the selections.

Figure 1-3 Open the All-in-One File

Locate and click the zip file for the download link that corresponds to your current TransNav management system release base. For example, TR3.2.2/TN4.2.2.

Table 1-4 Install Help Files from the Force10 website (Solaris) (continued)

Step Procedure


Chapter 1 Installation for Solaris WorkstationsInstall Help Files from the Force10 Website (Solaris)

5 In the Save As dialog box, navigate to a temporary directory (e.g., <user_directory>), and click OK to save the zip file.

Figure 1-4 Save As Dialog Box

6 Open a terminal window and change directory to the management server online help directory.

Important: The user who is going to be the management server administrator must have read and write permissions to this directory.

For example:

$ cd <server_home>/EMS/help

where:• <server_home> is the user-defined directory assigned during the

management server software installation (e.g., /server).• EMS/help is the system-defined directory assigned during the

management server software installation.


Step Procedure


TransNav Server Guide, Section 1: Installation and DescriptionInstall Help Files from the Force10 Website (Solaris)

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>_All-in-One.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.• All-in-one.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.

Figure 1-5 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.

11 The Install Help Files from the Force10 website (Solaris) procedure is complete. Continue to the server procedures in Section 2—Management Server Procedures, Chapter 3—“Server Administration Procedures”.


Step Procedure

Close Window menu button


Chapter 1 Installation for Solaris WorkstationsUninstall Server Software from Solaris Workstation

Uninstall Server Software from Solaris Workstation

You many want to remove older versions of the server software to create space on the computer. Use this procedure to remove a previous version of the server software from a Solaris workstation.

Table 1-5 Uninstall Server Software from Solaris Workstation

Step Procedure

1 Perform the software upgrade. See the procedure, Upgrade Server Software.

2 Ensure that the server is stopped. See the procedure, Stop the Server.

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 Uninstall Server Software from Solaris Workstation procedure is complete.


TransNav Server Guide, Section 1: Installation and DescriptionUninstall Server Software from Solaris Workstation



Chapter 2 Installation for Windows Workstations

Introduction 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 a Windows server or client workstation and customize the map view on the server GUI. • Before You Install Management System Software• Install Software on a Windows Workstation• Install Online Help Files on a Windows Workstation• Install Help Files from the Force10 Website (Windows)• Uninstall the Management System Software from Windows Workstation

See Chapter 1—“Installation for Solaris Workstations” for the procedures to install the management server on a Sun Solaris workstation.

Before You Install Management System Software

Before you install the management system software, understand the following requirements.

Table 1-6 Before You Install the Management System Software


Disable any operating system anti-virus and firewall applications that may be installed on this computer.

Contact your local site administrator.

Server requirements TransNav Management System Product Overview Guide, Section 2—Management System Planning, Chapter 1—“TransNav Management System Requirements”.

Server software includes user interface applications.

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 Procedures, Chapter 3—“Server Administration Procedures,” Download the Management Software from the Force10 Website.


TransNav Server Guide, Section 1: Installation and DescriptionInstall Software on a Windows Workstation


Install Software on a Windows Workstation

Use this procedure to install the TransNav management system on a Windows workstation from the Force10 Networks corporate website. A Customer Portal Account is required. If you do not have a Customer Portal Account, one can can be requested from the Force10 website at www.force10networks.com by selecting Services & Support, then Account Request.

Software upgrade 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 Procedures, Disable Server as a Service (Windows).

Server administration procedures

See Section 2—Management Server Procedures, Chapter 3—“Server Administration Procedures” for detailed procedures on initializing, starting, stopping, and maintaining the TransNav management server.

Table 1-6 Before You Install the Management System Software (continued)


Table 1-7 Install Software on a Windows Workstation

Step Procedure

Important: To install the 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 Management System Software before you start this procedure.

Chapter 2 Installation for Windows WorkstationsInstall Software on a Windows Workstation

2 Download the TransNav Management System software from the Force10 Networks corporate website (www.force10networks.com). From Services & Support, select Customer Login. Enter your Force10 User ID and Password, then click Login.

Select the Software Center tab, then select Traverse/Traverse Edge from the list of available software. A list of software releases and the corresponding release notes for each software release displays

Figure 1-6 Force10 Software Center Screen

Right-click the software release to download the WinZip software file to a directory on your management server. The file must be able to be accessed by the current user. For any required help with this procedure, contact your system administrator.

3 In a Windows Explorer window, navigate to the directory that contains the EMS software.

Table 1-7 Install Software on a Windows Workstation (continued)

Step Procedure


TransNav Server Guide, Section 1: Installation and DescriptionInstall Software on a Windows Workstation

4 Double-click the file <release number>-PCSetup.exe to start the installation process.

Figure 1-7 Executive File in Explorer Window

5 The Installer Wizard appears.

Figure 1-8 Management Server Installer Wizard

Follow the on-screen directions until the management system software is installed on your computer.

6 The Install Software on a Windows Workstation procedure is complete. Continue to Install Online Help Files on a Windows Workstation.

Table 1-7 Install Software on a Windows Workstation (continued)

Step Procedure


Chapter 2 Installation for Windows WorkstationsWhat is the All-In-One Online Help System?

Install Online Help Files on a Windows Workstation

To learn more about the All-In-One, see What is the All-In-One Online Help System?, page 1-17.

To install the online help files, see Install Help Files from the Force10 Website (Windows), page 1-19.

What is the All-In-One Online Help System?

The (HTML-based) All-In-One Documentation is the basis for the management system software online help mechanism.It is available on the Force10 corporate website (www.force10networks.com) from the Services & Support > Documentation webpage.

This online help system provides access to the complete documentation set and includes the following guides:

Figure 1-9 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.


TransNav Server Guide, Section 1: Installation and DescriptionWhat is the All-In-One Online Help System?

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.

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.


Chapter 2 Installation for Windows WorkstationsInstall Help Files from the Force10 Website (Windows)

Install Help Files from the Force10 Website (Windows)

Use this procedure to install the online help files from the Force10 website.

Table 1-8 Install Help Files from the Force10 Website (Windows)

Step Procedure

1 On your Windows workstation, open an internet browser window. In the Address bar, enter the address:


2 From Services & Support, select Documentation. The Force10 Documentation webpage displays.

Figure 1-10 Force10 Documentation Webpage

Select the plus sign to the left of Force10 Traverse/TransNav All-in-One Files to expand the file and see the selections.

Locate and click the zip file for the download link that corresponds to your current TransNav management system release base. For example, TR3.2.3/TN4.2.3.

3 A file download box displays for the zip file. Save the zip file to a temporary directory of your choice (e.g., <user_directory>).

4 From the <user_directory>, double-click the <ReleaseNumber>_All-in-One.zip file to open it.

5 From the zip tool Actions menu, choose Extract to extract the contents of the zip file.



TransNav Server Guide, Section 1: Installation and DescriptionInstall Help Files from the Force10 Website (Windows)

6 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).

7 In the Confirm File Overwrite dialog box, click Yes to All.

8 From the zip tool File menu, choose Exit to exit the application.

9 From the GUI TransNav Help window, click the Close button in the upper right corner of the window to close the window.

Figure 1-11 Close Button

10 From the GUI, select File, then Exit to exit the application.

11 Restart the GUI application to access the new online help.

Note: If you require assistance to restart the GUI, see the TransNav Management System GUI Guide, Section 1—Installation and Overview, Chapter 4—“Starting the Graphical User Interface.”.

12 The procedure, Install Help Files from the Force10 Website (Windows), is complete. Continue to the server administration procedures in Section 2—Management Server Procedures, Chapter 3—“Server Administration Procedures”.

Table 1-8 Install Help Files from the Force10 Website (Windows) (continued)

Step Procedure

Close button


Chapter 2 Installation for Windows WorkstationsUninstall the Management System Software from Windows Workstation

Uninstall the Management System Software from Windows Workstation

After upgrading the management system 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 management system software from your computer.

Table 1-9 Uninstall Management System Software from Windows Workstation

Step Procedure

1 Perform the software upgrade. See Upgrade Server Software, page 2-48.

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 1-12 Server Uninstall Wizard

Follow the on-screen directions until the management system 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 Management System Software from Windows Workstation procedure is complete.


TransNav Server Guide, Section 1: Installation and DescriptionUninstall the Management System Software from Windows Workstation



Chapter 3 Management Server Administration

Introduction 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

Using Multiple Servers

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. Node synchronization must be performed from the Primary server.

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


TransNav Server Guide, Section 1: Installation and DescriptionServer 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 Procedures, Chapter 1—“Creating the Management Servers,” Start the Server Administration Tool). The Server Admin dialog box appears.

Figure 1-13 Server Admin Tool


Chapter 3 Management Server AdministrationServer Administration Components Description

Server Administration Components Description

The Server Admin 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 the 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.


TransNav Server Guide, Section 1: Installation and DescriptionManagement 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 Procedures, 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 1-14 Execution Configuration Dialog Box

Use the Execution Configuration dialog box to change the following server administration parameters:

ANSITL1MetadataFile1: File containing the parameters of the management server ANSI TL1 Metadata file. Do not change this value.

AdminTraceLevel1: Used for troubleshooting by the Force10 Technical Assistance Center. Do not change this value.

CliDataDictionaryFile1: Name of the XML file containing the CLI commands. Do not change this value.

CliEmsHost1: IP address of the back end server (for distributed servers only).

CliTelnetPort: Port number on which the CLI Telnet server accepts client connections.

1 Do not change these parameters. Contact the Force10 Technical Assistance Center for assistance.


Chapter 3 Management Server AdministrationManagement Server Parameters

DatabaseBinDirectory1: Directory containing the binaries of the SOLID database tools.

DiscoveryPeriod (minutes)1: Number of minutes separating two topology audits.

EMSTL1DataDictionaryFile1: Name of the XML file containing the parameters of the EMS TL1 file. Do not change this value.

GatewayTL1MetadataFile1: File containing the parameters of the gateway server TL1 Metadata file. Do not change this value.

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.

MBeanDBCacheMax1: Maximum number of entries in the MBean component cache.

MBeanDBCacheMin1: Minimum number of entries in the MBean component cache.

MBeanDBProcessCaching1: Enable (true) or disable (false) the caching in the MBean component.

MBeanDBProcessConfigFile1: File containing the parameters of the MBean component.

MainBEServerIpAddress1: 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.

ReportHost1: IP address of the server hosting the generated text reports (for distributed server only).



ReportOutputDirectory1: 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.

ReportScriptDirectory1: 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.

SecurityAccessRightsFile1: File containing information on the users in each access group.

SecurityOnOffFlag1: 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.

SessionHTMLConnector1: Enable (true) or disable (false) the JDMK HTML connector on the session component. TR323

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.

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.

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


Chapter 3 Management Server AdministrationManagement Server Parameters

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.

SnmpAgentHtmlAdaptorPort1: 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.

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.

TE100TL1DataDictionaryFile1: Name of the XML file containing the TE100 TL1 commands.

TE206ConnectionEstablishmentTimeout(seconds): The time needed to establish a connection from TransNav to a TE-206 node. If the system times out, an error message is logged. Default is 10.

TE206TL1LoggingEnabled: Determines if TL1 logs from TE-206 nodes are collected on the server:• • true (default): Enables logging of every TL1 command received and the

respective response in a log file.• • false: Disables the logging function.

TE206TL1MaxNoOfLogBackup: The maximum number of backups to keep in the rolling TL1 logs for TE-206 nodes. Default is 4.

TL1EmsConnectorType1: Type of connector to be used by the TL1 component when communicating to the TransNav server.

TL1EmsHost1: 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.



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.

UserPreferencesDirectory1V: Directory for storing the GUI user preferences.

WebCraftEnabled: Indicates if the TransNav allows access to TE-206 shelf view.• • true (default): TransNav allows access to TE-206 shelf view. • • false: TransNav doesn't allow access to TE-206 shelf view.

WebCraftProxyHelperPort: Web Server port for accessing files from the server's local cache. Default is 3129.

WebCraftProxyPort: Web Server proxy port used for forwarding HTTP requests to TE-206 nodes. Authentication is enforced on this port for security purpose. Default is 3128.

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.


Chapter 3 Management Server AdministrationManagement Server Parameters for TE-206 Nodes

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:

WebCraftProxyHelperPort:Web Server port for accessing files from the server's local cache. Default is 3129.

WebCraftProxyPort: Web Server proxy port used for forwarding HTTP requests to TE-206 nodes. Authentication is enforced on this port for security purpose. Default is 3128.


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

TE206ConnectionEstablishmentTimeout(seconds): The time needed to establish a connection from TransNav to a TE-206 node. If the system times out, an error message is logged. Default is 10.

TE206TL1LoggingEnabled: Determines if TL1 logs from TE-206 nodes are collected on the server:• true (default): Enables logging of every TL1 command received and the respective

response in a log file.• false: Disables the logging function.

TE206TL1MaxNoOfLogBackup: The maximum number of backups to keep in the rolling TL1 logs for TE-206 nodes. Default is 4.

Output generated for TE-206 performance monitoring reports is stored on the TransNav server in the report directory under the output folder.


TransNav Server Guide, Section 1: Installation and DescriptionManagement Server Parameters for TE-206 Nodes


SECTION 2 MANAGEMENT SERVER PROCEDURES

Contents

Chapter 1Creating the Management Servers

Before You Create the Management Servers . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Start the Server Administration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Configure Management Server Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Configure Management Server Parameters for TE-206 Nodes . . . . . . . . . . . 2-7Configure HTTPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9Set the Primary Management Server as the Primary NTP Source . . . . . . . . . 2-12Set NTP Server on a Solaris Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12Set the NTP Server on a Windows 2000 Professional Workstation . . . . . . . . 2-13Set the NTP Server on a Windows XP Workstation . . . . . . . . . . . . . . . . . . . . 2-14Configure Log and Error Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

Chapter 2Management Server SNMP

Supported SNMP MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19Location of SNMP MIB File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19Enable SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19Configure the SNMP Access Control List . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21Ethernet Performance Monitoring and SNMP. . . . . . . . . . . . . . . . . . . . . . . . . 2-22

Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23

Chapter 3Server Administration Procedures

Start the Server Administration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26Initialize the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28Enable the Server as a Service (Windows). . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31Start the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31Export (Backup) the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33

Manually Export the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33Scheduling the Server Database Backup . . . . . . . . . . . . . . . . . . . . . . . . 2-35


TransNav Server Guide, Section 2 Management Server Procedures

Stop the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37Promoting a Secondary Server to the Primary Role . . . . . . . . . . . . . . . . . . . . 2-38Disable Server as a Service (Windows) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40Modify DEP Settings on Server (Windows) . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41Upgrade Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44Download the Management Software from the Force10 Website . . . . . . . . . . 2-45Import the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48Retrieve Server Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50Setting Up Report Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-51Customizing Background Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54Configuring DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56Setting a Broadcast Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57Terminating User Sessions in Bulk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59Setting Administrative Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60

Message of the Day . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60Setting a Security Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62Global User Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-63

Restore Default Server Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-66


SECTION 2MANAGEMENT SERVER PROCEDURES

Chapter 1 Creating the Management Servers

Introduction 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• Start the Server Administration Tool• Configure Management Server Parameters• Configure Management Server Parameters for TE-206 Nodes• Configure HTTPS• Set the Primary Management Server as the Primary NTP Source• Configure Log and Error Files

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 nodes, 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. Seamless interoperability exists between the Traverse, TE-100, and TE-206 nodes. For details on the TN-Xpert management system, see the TransNav Xpert Installation Guide and the TransNav Xpert Users Guide.

Before You Create the Management Servers

Review the information in this topic before creating the TransNav Primary and Secondary management servers.

Table 2-1 Before You Create the Management Servers


Create a network plan. 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)

Assign IP addresses to the management servers and network elements.

TransNav Management System Product Overview Guide, Section 2—Management System Planning, Chapter 3—“IP Address Planning”


TransNav Server Guide, Section 2: Management Server ProceduresBefore You Create the Management Servers

Add routes for the node-ips to the management servers.

This step depends on the server platform (Solaris or Windows) and local site practices. Contact your local site administrator.

Install, connect, and commission nodes according to the network plan.

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)

Install the TransNav management software on each server.

TransNav Management System Server Guide

FTP server application is installed on all TransNav management servers.

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.

Telnet server application is installed. Required for remote access to the management servers.

Table 2-1 Before You Create the Management Servers (continued)



http://www.warftp.org

Chapter 1 Creating the Management ServersStart 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

Step Procedure

1 For a Windows platform, go to Step 2.

For a Solaris platform, go to Step 3.

2 On a Windows platform, from the Start menu click Programs, then click Force10 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


TransNav Server Guide, Section 2: Management Server ProceduresStart the Server Administration Tool

4 The Server Admin dialog box displays.


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.

Table 2-2 Start the Server Administration Tool (continued)

Step Procedure


Chapter 1 Creating the Management ServersConfigure 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.

Note: If you have TE-206 nodes in your system, also see Configure Management Server Parameters for TE-206 Nodes, page 2-11.

Important: Contact the Force10 Technical Assistance Center for assistance in changing server administration parameters.

Table 2-3 Configure Management Server Parameters

Step Procedure

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


TransNav Server Guide, Section 2: Management Server ProceduresConfigure Management Server Parameters

4 In the Execution Configuration dialog box, change any of the default values for the parameters.

Figure 2-4 Management Server Parameters

See Chapter 3—“Management Server Administration,” Server Administration Components Description, 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 Chapter 3—“Server Administration Procedures,” Start the Server.

7 The Configure Management Server Parameters procedure is complete.

Table 2-3 Configure Management Server Parameters (continued)

Step Procedure


Chapter 1 Creating the Management ServersConfigure 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

Step Procedure

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.


Figure 2-5 Configure Server Parameters


TransNav Server Guide, Section 2: Management Server ProceduresConfigure 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)


See Section 1—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.

Table 2-4 Configure Management Server Parameters for TE-206 Nodes

Step Procedure


Chapter 1 Creating the Management ServersConfigure HTTPS

Configure HTTPS

Secure HTTPS connections can be set up on the TransNav server to allow clients to securely login to the TransNav server.

To enable HTTPS, a server key must be generated before the server is started. After the server key has been generated, clients can be granted access before or after the server is started. HTTPS access to the client requires the client IP address.

On the Server Admin tool, from the Execution menu click Configure HTTPS, then click Generate Keys. The system generates a secure key to be used to allow clients to access the server. After the secure key has been generated, manually restart the server from the Execution menu by clicking Start Server.

To view the server key after it has been generated, from the Execution menu click Configure HTTPS, then click View Server Key. The View Server Key dialog box displays:

Figure 2-6 View Server Key Dialog Box

Subject: The server IP address.

Issuer: The server IP address.

Serial Number: The serial number of the system-generated certificate.

(Before/After Validity dates): Indicates the beginning and ending dates that the server key will be valid. The length of time between these two dates is 180 days (6 months).

MD5 Fingerprint: Server key hash fingerprint, displayed in hex, calculated using the MD5 (Message-Digest Algorithm 5) cryptographic hash function.

SHA1 Fingerprint: Server key hash fingerprint, displayed in hex, calculated using the SHA-1 (Secure Hash Algorithm 1) cryptographic hash function.

Click OK to return to the Server Admin tool.

The last step to configuring HTTPS is to enable clients to view the server. This requires the IP addresses of the client workstations.


TransNav Server Guide, Section 2: Management Server ProceduresConfigure HTTPS

From the Execution menu click Configure HTTPS, then click Client Key. The Client Key dialog box displays:

Figure 2-7 Client Key Dialog Box

Enter the following information:

Client Address: Enter the IP address of the client to be allowed access to the server using HTTPS.

Key Validity(days): Enter the number of days that the client will be able to access the server using HTTPS. The default is 180 days.

Click Enable Client to allow the client IP address HTTPS access to the server. The client IP address that has been enabled displays.

Figure 2-8 Client Key Dialog Box with Enabled Client


Chapter 1 Creating the Management ServersConfigure HTTPS

Each time a client key is added, the server keys must be regenerated to activate the change. On the Server Admin tool, from the Execution menu click Configure HTTPS, then click Generate Keys. You do not need to restart the server.

To view the client key, select the client IP address to view and then click View Client. The View <Client IP Address> dialog box displays.

Figure 2-9 View Client Key Dialog Box

Subject: The client IP address.

Issuer: The server IP address.

Serial Number: The serial number of the system-generated certificate.

(Before/After Validity dates): Indicates the beginning and ending dates that the server key will be valid. The length of time between these two dates is 180 days (6 months).

MD5 Fingerprint: Server key hash fingerprint, displayed in hex, calculated using the MD5 (Message-Digest Algorithm 5) cryptographic hash function.

SHA1 Fingerprint: Server key hash fingerprint, displayed in hex, calculated using the SHA-1 (Secure Hash Algorithm 1) cryptographic hash function.:

Click OK to return to the Client Key dialog box. Click OK to exit the Client Key dialog box.


TransNav Server Guide, Section 2: Management Server ProceduresSet 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-16• Set the NTP Server on a Windows 2000 Professional Workstation, page 2-17

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.

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.

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.

Table 2-5 Set the Primary NTP Source on a Solaris Workstation

Step Procedure

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


http://www.ntp.org

Chapter 1 Creating the Management ServersSet 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

Step Procedure

1 From the Start menu, click Run.

2 In the Open field, type regedit and click OK to start the Registry Editor.

Figure 2-10 Run Dialog Box

3 Navigate to the directory:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters

Figure 2-11 Registry Editor

4 Change the REG_SZ value to 0.

5 Change the local NTP value to 1.

6 Change the Type value to NoSync.

7 From the Edit menu, click New > DWORD value.

8 Change New Value #1 to ReliableTimeSource.

9 Change the ReliableTimeSource value to 1.


TransNav Server Guide, Section 2: Management Server ProceduresSet the NTP Server on a Windows XP Workstation

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.

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.

Table 2-6 Set the Primary NTP Source on a Windows 2000 Professional Workstation (continued)

Step Procedure

Table 2-7 Set the Primary NTP Source on a Windows XP Workstation

Step Procedure


2 In the Open field, type regedit and click OK to start the Registry Editor.

3 Navigate to the following registry entry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\

Figure 2-12 W23Time Config Registry


Chapter 1 Creating the Management ServersSet the NTP Server on a Windows XP Workstation

4 In the right pane, right-click AnnounceFlags, and then click Modify.

Figure 2-13 Modify AnnounceFlags

5 In the Edit DWORD Value dialog box, type 5 under Value data, then click OK.

Figure 2-14 AnnounceFlags Edit DWORD Value

6 Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer\

Figure 2-15 NtpServer Subkey

7 In the right pane, right-click Enabled and then click Modify.

Table 2-7 Set the Primary NTP Source on a Windows XP Workstation (continued)

Step Procedure


TransNav Server Guide, Section 2: Management Server ProceduresSet the NTP Server on a Windows XP Workstation

8 In the Edit DWORD Value dialog box, type 1 under Value data and then click OK.

Figure 2-16 Enabled Edit DWORD Value

9 From the file menu, click Exit to close the Registry Editor.


11 In the Open field, type cmd and click OK to open a DOS command line prompt.

12 At the command prompt, enter the following command to restart the Windows Time service:net stop w32time && net start w32time

13 The Set the Primary NTP Source on a Windows XP Workstation procedure is complete.

Table 2-7 Set the Primary NTP Source on a Windows XP Workstation (continued)

Step Procedure


Chapter 1 Creating the Management ServersConfigure 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

Step Procedure

1 Start the server administration tool. See the procedure Start the Server Administration Tool.

2 From the Logging menu, click Configure.

Figure 2-17 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-18 Logging Configure Dialog Box


TransNav Server Guide, Section 2: Management Server ProceduresConfigure Log and Error Files

4 Click OK to save configuration information and close the dialog box.

5 The Configure Log and Error Files procedure is complete.

Table 2-8 Configure Log and Error Files (continued)

Step Procedure



Chapter 2 Management Server SNMP

Introduction This chapter contains procedures that an administrator performs 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-23• Location of SNMP MIB File, page 2-23• Enable SNMP Agent, page 2-23• Configure the SNMP Access Control List, page 2-25• Ethernet Performance Monitoring and SNMP, page 2-26

Supported SNMP MIBs

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

Location of SNMP MIB File

The proprietary SNMP MIB (filename=ems.mib) file is located in the same directory where you installed the server application.

Enable SNMP Agent

Use the following procedure to allow the management system to receive SNMP queries and forward system events.

Table 2-9 Enable SNMP Agent Components

Step Procedure

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.


TransNav Server Guide, Section 2: Management Server ProceduresEnable SNMP Agent


Figure 2-19 Configure Server

4 In the Configure Server dialog box, configure the SNMP Agent components.

Figure 2-20 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-35.

7 Continue to the procedure Configure the SNMP Access Control List, page 2-25.

8 The Enable SNMP Agent Components procedure is complete.

Continue to the next procedure Configure the SNMP Access Control List, page 2-25.

Table 2-9 Enable SNMP Agent Components (continued)

Step Procedure


Chapter 2 Management Server SNMPConfigure 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

Step Procedure

1 Start the server administration tool. See the procedure, Start the Server Administration Tool.

2 If the server is running, stop the server. See the procedure, Stop the Server.

3 From the Execution menu, click Configure SNMP.

Figure 2-21 Configure SNMP

4 The ACL file appears in a text editor window.

Figure 2-22 Edit the SNMP Access Control List

Step 5

Step 6

Step 7


TransNav Server Guide, Section 2: Management Server ProceduresEthernet Performance Monitoring and SNMP

Ethernet Performance Monitoring and SNMP

The SNMP MIB supports performance data counters for the current day interval for every Ethernet interface in the TransNav-managed network.

The management server collects the performance data and allows third-party equipment to query these PM counters through the SNMP interface. The server refreshes the data after the time specified in the server parameter SnmpCurrentCounterValidity (seconds). Default is 120 seconds.

The Ethernet Interface Index is created using the following algorithm:

SlotIndex * 10 000 000 + PortIndex * 100 000

where:SlotIndex range is from 1 to 20PortIndex 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.

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.

9 The Configure the SNMP Access Control List procedure is complete.

Table 2-10 Configure the SNMP Access Control List (continued)

Step Procedure


Chapter 2 Management Server SNMPEthernet 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.


TransNav Server Guide, Section 2: Management Server ProceduresEthernet Performance Monitoring and SNMP



Chapter 3 Server Administration Procedures

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 nodes, 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. Seamless interoperability exists between the Traverse, TE-100, and TE-206 nodes. 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 Website• Import the Database• Retrieve Server Log Files• Setting Up Report Parameters• Customizing Background Images• Configuring DHCP• Setting a Broadcast Message• Terminating User Sessions in Bulk• Setting Administrative Options

– Message of the Day


TransNav Server Guide, Section 2: Management Server ProceduresStart the Server Administration Tool

– Setting a Security Warning– Global User Block

• Restore Default Server Parameters

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

Step Procedure

1 For a Windows platform, go to Step 2.

For a Solaris platform, go to Step 3.

2 On a Windows platform, from the Start menu click Programs, then click Force10 then click TransNav Admin.

Figure 2-23 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


Chapter 3 Server Administration ProceduresStart the Server Administration Tool

4 The Server Admin dialog box displays.


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.

Table 2-11 Start the Server Administration Tool (continued)

Step Procedure


TransNav Server Guide, Section 2: Management Server ProceduresInitialize 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

Step Procedure

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-25 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 Step 4.

Figure 2-26 Database Initialize Confirmation


Chapter 3 Server Administration ProceduresInitialize the Database

4 In the Database Initialization dialog box, first select the technology standard of the server.

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

Table 2-12 Initialize the Database (continued)

Step Procedure


TransNav Server Guide, Section 2: Management Server ProceduresInitialize the Database

Next, select the server role.

Figure 2-28 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. The status

displays in the status bar at the bottom of the Server Admin dialog box.

5 The Initialize the Database procedure is complete. Continue to the next procedure, Start the Server.

Table 2-12 Initialize the Database (continued)

Step Procedure


Chapter 3 Server Administration ProceduresStart the Server

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.

Start the Server

To start the management server, select Start Server from the Execution menu. The progress is shown in the status bar.

Table 2-13 Enable the Server as a Service

Step Procedure

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.

Table 2-14 Start the Server

Step Procedure

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


TransNav Server Guide, Section 2: Management Server ProceduresStart the Server

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.

Table 2-14 Start the Server (continued)

Step Procedure


Chapter 3 Server Administration ProceduresExport (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

Step Procedure

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.


TransNav Server Guide, Section 2: Management Server ProceduresExport (Backup) the Database

3 From the Database menu, click Export.

Figure 2-32 Export Database

4 The Database Export dialog box displays. Click Browse.

Figure 2-33 Database Export Dialog Box

5 The Select Export Path dialog box displays. Navigate to the directory where you plan to store the database.

In the Folders list, select the directory where you plan to store the exported database (see Step 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 U.S. military format. The server database is saved under this subdirectory.

The status of the export process displays on the status bar at the bottom of the Server Admin dialog box.

After the export is done, if you are in the process of an upgrade, return to Step 3 of the Upgrade Server Software.

Table 2-15 Manually Export the Database (continued)

Step Procedure


Chapter 3 Server Administration ProceduresExport (Backup) the Database

Scheduling the Server Database Backup

Table 2-16 Scheduling the Server Database Backup

Step Procedure

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-34 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 will display on the Database Export Parameters dialog box after your system is upgraded.


TransNav Server Guide, Section 2: Management Server ProceduresExport (Backup) the Database

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 these parameter changes take effect.

Click OK to accept the changes or click Cancel.

The Scheduling the Server Database Backup procedure is complete.

4 If you are in the process of an upgrade, return to Step 3 of the Upgrade Server Software.

Table 2-16 Scheduling the Server Database Backup (continued)

Step Procedure


Chapter 3 Server Administration ProceduresStop 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.

Table 2-17 Stop the Server

Step Procedure


2 From the Execution menu, click Stop Server.

Figure 2-35 Stop Server

The server starts the shutdown process.

When all the components are stopped, the Stop the Server procedure is complete.

3 If you are in the process of an upgrade, return to Step 5 of the Upgrade Server Software.


TransNav Server Guide, Section 2: Management Server ProceduresPromoting 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

Step Procedure

1 Force10 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.


Chapter 3 Server Administration ProceduresPromoting a Secondary Server to the Primary Role

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

Table 2-18 Promoting a Secondary Server to the Primary Role (continued)

Step Procedure


TransNav Server Guide, Section 2: Management Server ProceduresDisable 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

Step Procedure

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 Procedures, 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-36 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 Step 6 of the Upgrade Server Software.


Chapter 3 Server Administration ProceduresModify 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

Step Procedure

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-37 System Properties Advanced Tab

The Performance Options dialog box displays.

4 Click the Data Execution Prevention tab.

Figure 2-38 Data Execution Prevention Tab


TransNav Server Guide, Section 2: Management Server ProceduresModify DEP Settings on Server (Windows)

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>\jre\bin

Figure 2-39 Navigating the TransNav Installation Directory

– Select Java.exe and click Open.

Figure 2-40 Select the Java Executable

You return to the Data Execution Prevention tab. Click Add to continue.


Step Procedure


Chapter 3 Server Administration ProceduresModify DEP Settings on Server (Windows)

– If you are running TransNav as a Windows service, you must also navigate to<TransNav installation directory>\ems_<release number>\db\bin

– Select solid.exe and click Open. You return to the Data Execution Prevention tab. Click Add to continue.

– Next, navigate to <TransNav installation directory>\ems_<release number>\lib\bin

– Select JavaService.exe and click Open. You return to the Data Execution Prevention tab.

– Ensure the check box in front of each service is selected in the selection box on the Data Execution Prevention tab. Click Apply.

Figure 2-41 Verify the Check boxes are Selected

Click OK.

5 The Disable DEP Service on Server procedure is complete.

If you are in the process of an upgrade, return to Step 6 of the Upgrade Server Software.


Step Procedure


TransNav Server Guide, Section 2: Management Server ProceduresUpgrade 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

Step Procedure

1 Download the correct version of the TransNav management system software from the Force10 website.

See the procedure Download the Management Software from the Force10 Website.

2 Uninstall all GUI applications from all client workstations. • For Windows workstations, see the TransNav Management System

GUI Guide, Section 1—Installation and Description, Chapter 2—“Installation for Windows Workstations”.

• For UNIX workstations, see the TransNav Management System GUI Guide, Section 1—Installation and Description, Chapter 1—“Installation for Solaris Workstations”.

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 Modify DEP Settings on Server (Windows).

6 Install the new server software: • For Windows workstations, see the TransNav Management System

GUI Guide, Section 1—Installation and Description, Chapter 2—“Installation for Windows Workstations.”

• For Solaris workstations, see the TransNav Management System GUI Guide, Section 1—Installation and Description, Chapter 1—“Installation for Solaris Workstations.”

7 Import the database that was saved in Step 3. See the procedure Import the Database.

8 Start the server. See the procedure Start the Server.


Chapter 3 Server Administration ProceduresDownload the Management Software from the Force10 Website

Download the Management Software from the Force10 Website

Use this procedure to download the latest management server software from the Force10 website.

Note: A Customer Portal Account is required. If you do not have a Customer Portal Account, you can request one from the Force10 website at www.force10networks.com by selecting Services & Support, then Account Request.

9 Install the upgraded GUI applications for all client workstations. • For Windows workstations, see the TransNav Management System

GUI Guide, Section 1—Installation and Description, Chapter 2—“Installation for Windows Workstations.”

• For Solaris workstations, see the TransNav Management System GUI Guide, Section 1—Installation and Description, Chapter 1—“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 Step 4 of the procedure Traverse Node Software Upgrade Process.

Table 2-21 Upgrade Server Software (continued)

Step Procedure

Table 2-22 Download the Management Software from the Force10 Website

Step Procedure

1 On your computer, open an internet browser window.

In the Address bar, enter the address:


2 From Services & Support, select Customer Login. Enter your Force10 User ID and Password, then click Login.



TransNav Server Guide, Section 2: Management Server ProceduresDownload the Management Software from the Force10 Website

3 The Force10 Customer Support webpage displays. Click the Software Center tab.

Figure 2-42 Force10 Customer Support Webpage

4 From the Software Center webpage, click Traverse/TraverseEdge on the left side of the webpage. The Software Releases Transport Products webpage displays.

Figure 2-43 Software Releases Transport Products Webpage


Step Procedure


Chapter 3 Server Administration ProceduresDownload the Management Software from the Force10 Website

5 Software releases are organized by product in tables. Links to the Windows and Solaris software builds for each release are provided, along with the corresponding release notes.

Click the build file to download. An Opening or File Download dialog box displays depending on the type of browser used. Follow the instructions to download the software build to a user-defined directory and click Save.

To retrieve the online help files, see Section 1—Installation and Description, Chapter 1—“Installation for Solaris Workstations” or Chapter 2—“Installation for Windows Workstations.”

6 The Download the Management Software from the Force10 Website procedure is complete. Return to Step 2 of the procedure Upgrade Server Software.


Step Procedure


TransNav Server Guide, Section 2: Management Server ProceduresImport 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

Step Procedure


2 From the Database menu, click Import.

Figure 2-44 Import Database

3 Verify you want to continue the import. Click Yes to continue the import.

Figure 2-45 Database Initialize Confirmation

4 The Database Import dialog box displays. Click Browse.

Figure 2-46 Database Import Dialog Box


Chapter 3 Server Administration ProceduresImport the Database

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-47 Select Import Path Dialog Box

6 The Database Import dialog box re-displays with the Import Path field filled. Click OK.

Figure 2-48 Database Import Dialog Box

7 When the status bar indicates that the import is done, the Import the Database procedure is complete.

Figure 2-49 Database Import Complete

8 If you are in the process of a server software upgrade, return to Step 8 of the procedure Upgrade Server Software.

Table 2-23 Import the Database (continued)

Step Procedure

status


TransNav Server Guide, Section 2: Management Server ProceduresRetrieve 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 to troubleshoot server problems.

Table 2-24 Retrieve Server Log Files

Step Procedure

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

On a Solaris workstation, go to Step 4.

3 In a Windows Explorer window, select the logs directory.

Figure 2-50 Retrieve Log Directory in Windows

Add the entire directory to a .zip file:• Right-click the logs directory.• Select WinZip1, then select Add to logs.zip.

Go to Step 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 Step 5.


Chapter 3 Server Administration ProceduresSetting 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.

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

Table 2-24 Retrieve Server Log Files (continued)

Step Procedure

Table 2-25 Setting Up Report Parameters

Step Procedure

1 On your computer, start the EMS server:

./exec_admin.sh

The Server Admin dialog box displays.

2 Select Execution, Configure Server, then Parameter.

Figure 2-51 Configure Server Report Parameters


http://www.winzip.com/

TransNav Server Guide, Section 2: Management Server ProceduresSetting Up Report Parameters

3 The Execution Configuration dialog box displays.

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

Table 2-25 Setting Up Report Parameters (continued)

Step Procedure


Chapter 3 Server Administration ProceduresSetting Up Report Parameters

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

Table 2-25 Setting Up Report Parameters (continued)

Step Procedure


TransNav Server Guide, Section 2: Management Server ProceduresCustomizing 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

Step Procedure

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-54 Load Background Image Dialog Box


Chapter 3 Server Administration ProceduresCustomizing Background Images

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 Step 6.

Figure 2-55 Open Dialog Box

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-56 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 4—“TransNav User Preferences,” Changing Node Group Names.

Table 2-26 Save Background Image for Map View

Step Procedure


TransNav Server Guide, Section 2: Management Server ProceduresConfiguring 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, you must 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-57 DHCP Configuration 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.

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)


Chapter 3 Server Administration ProceduresSetting a Broadcast Message

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

Setting a Broadcast Message

An administrator can send broadcast messages to inform other users who are logged onto the server using the TransNav GUI of important events with little notice, such as a server or node having to be shut down or rebooted. The broadcast message is only sent once. The administrator sending the message will not receive a copy of the message. A record of the message and the user who sent it are recorded in an event log when the message is sent.

Users who are logged into the system using the server CLI can block the receipt of a broadcast message. GUI and TL1 users cannot block the message receipt.

Note: Users who are logged onto a node using node CLI, node TL1, or the Node-level GUI will not receive the broadcast message.

Table 2-27 Setting a Broadcast Message

Step Procedure

1 Logon to the TransNav GUI. From the Admin menu, click Session List. The Session List dialog box displays. The dialog box shows the UserName of all users who are logged onto the system, the method used to logon (CLI, TL1 or TransNav EMS GUI), the IP Address and Hostname of the server or node where the user is logged on from, and the time the user logged onto the system.

Figure 2-58 Session List Dialog Box

To send a broadcast message to a single user, select the UserName of the person, then click Send Message to enter the message text.

To send a broadcast message to a few specific users, hold the Shift key down and then click the UserNames of the users who are to receive the message. Click Send Message to enter the message text.

To send a broadcast message to all users, click Send Message to enter the message text.


TransNav Server Guide, Section 2: Management Server ProceduresSetting a Broadcast Message

2 The Broadcast Message dialog box displays. Enter a message that will be sent to all selected users.

Figure 2-59 Broadcast Message Dialog Box

3 Click Send. The message is sent to all of the selected users. A confirmation dialog box displays. Click OK to close the confirmation dialog box. The Session List dialog box re-displays.

4 Click Close to close the Session List dialog box. The procedure, Setting a Broadcast Message, is complete.

Table 2-27 Setting a Broadcast Message (continued)

Step Procedure


Chapter 3 Server Administration ProceduresTerminating User Sessions in Bulk

Terminating User Sessions in Bulk

User sessions can be terminated (deleted) in bulk by an administrator as described below.

Note: Users who are logged onto a node using node CLI, node TL1, or the Node-level GUI cannot not be terminated in this manner.

Note: To delete a single user at a time, see the TransNav Management System GUI Guide, Section 2—Administrative Tasks, Chapter 1—“Managing Server Security,” Domain Users to delete a domain user, or Section 2—Administrative Tasks, Chapter 2—“Managing Node Security,” Node Users to delete a node user.

Table 2-28 Terminating User Sessions in Bulk

1 Logon to the TransNav GUI. From the Admin menu, click Session List. The Session List dialog box displays. The dialog box shows the UserName of all users who are logged onto the system, the method used to logon (CLI, TL1 or TransNav EMS GUI), the ipAddress and Hostname of the server or node where the user is logged on from, and the time the user logged onto the system.

Figure 2-60 Session List Dialog Box

2 To terminate a few specific users, hold the Shift key down and then click the UserNames of the users to receive the message. Click Terminate to remove the users from the system.

Note: The UserName of the administration performing the bulk termination cannot be deleted while executing this task.

3 Click Close to close the Session List dialog box. The procedure, Terminat-ing User Sessions in Bulk, is complete.


TransNav Server Guide, Section 2: Management Server ProceduresSetting Administrative Options

Setting Administrative Options

Options such as a message of the day and security features are available for administrative use. The different available features are described below.

Message of the Day

Administrators can set up a message of the day that will be seen when system users logon to the primary server. Use the message of the day to inform users of scheduled server or node shut downs, upgrades, or other key events. The message of the day will not expire at the end of the day. If multiple servers exist in the network, only one message of the day can be set on a server at a time.

If the text of the message is changed but is not blank, users will receive a message broadcast that includes the updated message.

Note: Users who are logged onto a node using node CLI, node TL1, or the Node-level GUI will not receive the message of the day.

Table 2-29 Setting a Message of the Day

Step Procedure

1 Logon to the TransNav GUI. From the Admin menu, click Admin Operations. The Admin Operations dialog box displays.

Figure 2-61 Admin Operations Dialog Box


Chapter 3 Server Administration ProceduresSetting Administrative Options

2 Click the Message of the Day tab. Enter the text to appear when users logon to the system.

Figure 2-62 Admin Operations, Message of the Day Dialog Box

Click Update. The text will display in a Message of the Day dialog box that appears when a user successfully logs onto the system.

Note: To clear the message, delete the text and click Update.

3 Click Close to close the Admin Operations dialog box. The procedure, Setting a Message of the Day, is completed.

Table 2-29 Setting a Message of the Day (continued)

Step Procedure



Setting a Security Warning

An administrator can use this procedure to set a security warning to warn users of the consequences of unauthorized system usage. The security warning message appears when users logon to the system.

Table 2-30 Setting a Security Warning

Step Procedure



2 If it is not already selected, click the Security Warning tab.



Global User Block

Occasionally it may be necessary to block all users from logging onto the server. This can be done using the Global User Block feature.

To block an individual domain user, see the TransNav Management System GUI Guide, Section 2—Administrative Tasks, Chapter 1—“Managing Server Security,” Domain Users. To block an individual node-level user, see the TransNav Management

3 Enter the warning text to display. The text displays in a warning message that appears each time before users log into the system.

Warning messages created from the GUI can be multiple lines in length. Warning messages entered from the CLI or TL1 must be only one line in length. All messages can be up to 1000 characters long.

Figure 2-64 Admin Operations Security Warning Tab

Click Update to set the message to display when a user attempts to login to the system.

Note: To clear the message, delete the text and click Update.

4 Click Close to close the Admin Operations dialog box. The procedure, Setting a Security Warning, is completed.

Table 2-30 Setting a Security Warning

Step Procedure



System GUI Guide, Section 2—Administrative Tasks, Chapter 2—“Managing Node Security,” Node Users.

Table 2-31 Setting up the Global User Block

Step Procedure

1 Global User Blocks can be set up in the following two methods: • From the TransNav GUI. For instructions, go to Step 2.• From the Server Admin tool. For instructions, go to Step 5





3 If it is not already selected, click the Global User Block tab. The Global User Block screen displays.

Figure 2-66 Admin Operations Global User Block Tab

Select the ON/OFF checkbox to block all users from logging onto the system. When selected, users cannot log on. When cleared, users are allowed to log on to the system.

4 Click Update to set the change or click Close to return to the previous screen. Go to Step 9.

5 To enable the Global Login Blocked feature from the Server Admin tool, start the Server Admin tool. For more information, see the procedure Start the Server Administration Tool.

6 From the Execution menu, select Configure Server, then Global Login Blocked. The Global User Block dialog box displays.

Figure 2-67 Global User Block Dialog Box

7 Select the ON/OFF checkbox to block all users from logging onto the system. When selected, users cannot log on. When cleared, users are allowed to log on to the system.

Table 2-31 Setting up the Global User Block (continued)

Step Procedure


TransNav Server Guide, Section 2: Management Server ProceduresRestore Default Server Parameters

Restore Default Server Parameters

Use the following procedure to restore the default parameters on the Execution Configuration screen for the management server.

8 Click Update to set the change or click Close to return to the previous screen.

9 The procedure, Setting up the Global User Block, is completed.

Table 2-31 Setting up the Global User Block (continued)

Step Procedure

Table 2-32 Restore Default Server Parameters

1 On your computer, start the EMS server:

./exec_admin.sh

The Server Admin dialog box displays.

2 Select Execution, Configure Server, then Restore Default Parameter.

Figure 2-68 Restore Default Parameter

The server parameters are restored to the original default settings. A dialog box displays indicating the reset was successful.

3 The procedure, Restore Default Server Parameters, is completed.


INDEX

AACL, see SNMP, access control listadministration, 2-9AIO, see All-In-OneAll-In-One

documentation, 1-5, 1-17implementation

Java, 1-6, 1-18online help, 1-5, 1-17tabs

contents, 1-17favorites, 1-17index, 1-17search, 1-17

All-in-OneJava

requirements, 1-6tabs

contents, 1-6index, 1-6search, 1-6

Archive extractallinone.zip, 1-10unzip command, 1-10zip tool, 1-19

BBackup

databasemanually, 2-37schedule, 2-39

CCard

configuringDHCP, 2-60

ConfigurationHTTPS

seeServers

DDatabase

exportmanually, 2-37scheduling, 2-39

DHCPconfigure

node, 2-60

EEthernet

PMSNMP, 2-26

Exportdatabase

manually, 2-37

GGlobal block

users, 2-67

HHelp

implementationJava, 1-6, 1-18JavaScript, 1-6, 1-18

install files, customer portalSolaris, 1-7Windows, 1-19

HTTPSconfigure

seeServers, configuration

IIP address

DHCPconfiguration, 2-60

MManagement

serverconfigure parameters, 2-9TE206 parameters, 2-11

server, help directorySolaris, 1-9Windows, 1-20

Map viewcustomize image, 2-58

Messageof the day, 2-64set up

broadcast, 2-61informational, 2-64security warning, 2-66

Release TN4.2.2 Force10 Networks Index-1

Index

NNode

configurationDHCP, 2-60

parametersDHCP, 2-60

synchronizeprimary server, 1-23

OOnline help, see All-In-One

SSchedule

databasebackup, 2-39

Securityserver

https setupServer

parametersTE-206, 1-31

primarynode synchronization, 1-23

Server Admiin toolcomponent descriptions, 1-25

Server Administration toolstarting, 2-7, 2-30

Server parametersSnmpCurrentCounterValidity, 2-26

Serversconfiguration

HTTPS, 2-13import database

time, 1-24multiple

communication, 1-24number of, 1-23

primaryfunctions, 1-23

secondaryfunctions, 1-23updating database, 1-24

SNMPaccess control list, 2-25ems.mib, 2-23Ethernet PM, 2-26MIB, 2-23

Synchronizationnodes

multiple servers, 1-23

TTE-206

management serverrequired parameters, 2-11

Terminateuser sessions

bulk, 2-63

UUser

accessglobal block, 2-67

session. bulk delete, 2-63sessions

bulk termination, 2-63

Index-2 Force10 Networks Release TN4.2.2

transnav server guide - force10networks.com · transnav server guide, ... server administration...

Documents