cc/td/doc/product/iaabu/localdir
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Cisco LocalDirector User Interface Version 3.1.2 Installation and Release Notes

Cisco LocalDirector User Interface Version 3.1.2 Installation and Release Notes

January, 2000

This document describes the Cisco LocalDirector User Interface for Release 3.1.2.

The following sections are included:

Installation Requirements

It is important to check that the system, network, and third-party requirements have been met before you install the LocalDirector User Interface. This section describes these requirements. The remainder of the chapter provides detailed instructions for installing the LocalDirector User Interface.

Your site must have the following hardware and software components installed for the LocalDirector User Interface to run properly:

The system where you initially install the LocalDirector User Interface becomes the LocalDirector User Interface server. The system from which you access the LocalDirector User Interface becomes the client. The following sections describe in further detail the LocalDirector User Interface system requirements.

LocalDirector Requirements

You must have Cisco LocalDirector, version 3.1, connected to the network according to the instructions in the Cisco LocalDirector Installation and Configuration Guide. This can be either a serial or Telnet connection.

LocalDirector User Interface Server and Client Requirements

The LocalDirector User Interface client and server depend in part on third-party products. You must install these programs prior to installing the LocalDirector User Interface. Refer to the table below and to the product release notes for the current list of third-party requirements and specific version information.
Table 1: Server Dependencies by Platform
Platforms/Operating Systems Vendor

Solaris UNIX v2.6 Sparc OS

(February 1999 Sun recommended patch cluster)

Sun Microsystems

Windows NT v4.0 SP4

Microsoft


Table 2: Client Dependencies by Platform
Platforms/Operating Systems Vendor

Solaris UNIX v2.6 Sparc OS

(February 1999 Sun recommended patch cluster)

Sun Microsystems

  • Windows NT v4.0 SP4

  • Windows 95 SP1 or OSR2 with Windows Socket 2 Update applied

  • Windows 98

Microsoft

Disk and Memory Resources

The system where the LocalDirector User Interface is intended to run should have at least as much available RAM and disk space as shown in Table 3 and Table 4.


Table 3: Disk and Memory Resources for the LocalDirector User Interface Server
Memory Size

RAM

8 MB on UNIX

8 MB on Windows NT, Windows 95, or Windows 98

Disk space

30 MB on UNIX

30 MB on Windows NT, Windows 95, or Windows 98


Table 4: Disk and Memory Resources for the LocalDirector User Interface Client
Memory Size

RAM

32 MB on UNIX

32 MB on Windows NT

Disk space

20 MB on UNIX

20 MB on Windows NT

In addition, the LocalDirector User Interface server and client installations will install the Java Plug-in if you do not have it installed. The memory requirements in the above tables include the plug-in component. If you install the LocalDirector User Interface server and client on the same system, add the relevant memory requirements from both tables to get the total memory requirement.

Installing the LocalDirector User Interface Server

The LocalDirector User Interface server can run on either Windows NT or Solaris UNIX systems. The following sections describe how to install the LocalDirector User Interface server on each platform. Once you install the LocalDirector User Interface server, install the LocalDirector User Interface client as described in the section "Installing the LocalDirector User Interface Client."

Installing the LocalDirector User Interface Server on Windows NT Systems

The following information is required before you install the LocalDirector User Interface server on a system running Windows NT:

Follow this procedure to install the LocalDirector User Interface server on a system running Windows NT.

Step 1 Log in to the LocalDirector User Interface server host system as the administrator.

Step 2 If you are installing the LocalDirector User Interface server software from a CD, insert that CD now.

Otherwise, download the LocalDirector User Interface server self-extracting compressed file from CCO at the URL http://www.cisco.com/cgi-bin/tablebuild.pl/localdir. Double-click the file to uncompress and move it to a temporary directory on the intended host system of the LocalDirector User Interface server.

Step 3 Locate and run the Setup.exe file in the temporary directory or CD. This starts the InstallShield program. Read the introductory information and then click Next.

Step 4 Specify the location where you want to install the LocalDirector User Interface. By default, the server is installed on the C:\Program Files\Cisco\LocalDirector User Interface 3.1 folder. Click Next to continue.

Step 5 Specify the program folder where you want to install the LocalDirector User Interface server shortcuts. By default, the shortcuts are installed in the LocalDirector User Interface 3.1 folder. Click Next to continue.

A message displays indicating that the files are being copied.

Step 6 If you already have the Java plug-in installed, go to Step 9. If you do not have a Java plug-in installed, the installation prompt returns with a message that it will now install the Java plug-in onto the LocalDirector User Interface server host.

Click OK.

A message displays informing you that the installer is unpacking the Java plug-in.

Step 7 At the Software License Agreement window for the Java plug-in, read the agreement, then click Yes.

Step 8 Specify the location where you want to install the Java plug-in. By default the plug-in is installed in the folder C:\Program Files\Java Plug-in 1.1. Click Next to continue.

Step 9 If you have an existing Java Runtime Environment (JRE) installed, a window displays asking if you want to use the Java plug-in being installed as the JRE default. Click Yes or No.

An information box displays to tell you to press OK when the Java plug-in installation is complete.

Step 10 Click OK. The setup is complete.

Note This installation automatically installs the LocalDirector User Interface server as a system service and starts it. It also installs a shortcut to the LocalDirector User Interface client called LocalDirector 3.1 in Start Programs. In addition, because the LocalDirector User Interface server has started as a system service on Windows NT, you may want to set up a login password through the File menu Server Properties option in the LocalDirector User Interface main window.

Installing the LocalDirector User Interface Server on UNIX Systems

Before you install the LocalDirector User Interface server on a system running UNIX, determine the directory where you want to install the LocalDirector User Interface server.

Note Henceforth, the host where the LocalDirector User Interface is installed will be referred to as the LocalDirector User Interface server.

You install the LocalDirector User Interface server software for UNIX systems from a tar file. (The tar utility is a standard UNIX file archival utility.)

Follow this procedure to install the LocalDirector User Interface server software on a system running UNIX.

Step 1 If you are installing the LocalDirector User Interface server software into some central location such as /usr/local, log in as root. Otherwise, if you are installing the software in your local directory, you can log in as yourself.

Step 2 If you are installing the LocalDirector User Interface server software from a CD, insert that CD now.

Otherwise, download the lui31_fcs_solaris251_rel_tar.Z file from CCO.

Step 3 Go to the directory where you want to install the LocalDirector User Interface server software.

Step 4 Uncompress the lui31_fcs_solaris251_rel_tar.Z file with the following command:

uncompress lui31_fcs_solaris251_rel_tar.Z

Step 5 Untar the resulting lui31_fcs_solaris251_rel_tar file with the following command:

tar xvf lui31_fcs_solaris251_rel_tar

The LocalDirector User Interface server software is installed in the current directory. The setup is complete.

Note This installation does not automatically start the LocalDirector User Interface server. Enter the gwserver command at the command line on the host system LocalDirector User Interface server to start the LocalDirector User Interface server with default settings.

Installing the LocalDirector User Interface Client

The first time you navigate to the LocalDirector User Interface server host from a client system, the LocalDirector User Interface server installs the LocalDirector User Interface client software and a Java plug-in (if one is not already installed). The LocalDirector User Interface client software may be either on the same system as the LocalDirector User Interface server, or on a different system.

Note If multiple clients are accessing one LocalDirector User Interface server simultaneously, changes made by one client may overwrite changes made by another client.

The following sections describe how to install the LocalDirector User Interface according to the client platform.

Installing the LocalDirector User Interface Client on Windows 95, Windows 98, or Windows NT Systems

Use the procedure in this section to install the LocalDirector User Interface client on a system running Windows 95, Windows 98, or Windows NT system.

Step 1 Open a browser such as Netscape Communicator or Microsoft Internet Explorer.

Step 2 At the URL line, enter an address with the following format:

http://host_name_or_IP_address:port/LUI31.html

The host name (or IP address) and port number pair are those of the LocalDirector User Interface server host.

If the LocalDirector User Interface client is not currently installed on the client system, the LocalDirector User Interface server downloads the executable file.

Step 3 If you are using the Microsoft Internet Explorer browser and the Java 1.1.2 plug-in is not installed, the browser asks if you want to install the software. Continue to Step 8. If the Java 1.1.2 plug-in is installed, the software automatically installs the LocalDirector User Interface client from within the browser. Go to Step 15.

If you are using the Netscape Communicator browser, continue with the next step.

Step 4 Click the download icon to download the client installation executable file.

Step 5 In the download dialog box, specify a location where you want to place the client installation executable file.

Step 6 Go to the directory that contains the client installation executable file, LUI31.exe.

Step 7 Run LUI31.exe. At the Welcome to LocalDirector User Interface window, click Finish.

Step 8 The InstallShield program starts. Read the introductory information and click Next.

Step 9 Specify the location where you want to install the LocalDirector User Interface client software. By default the client is installed in the folder
C:\Program Files\Cisco\LocalDirector User Interface 3.1. Click Next to continue.

A message appears indicating that the files are being copied.

Step 10 If you already have the Java plug-in installed, go to Step 14. If you do not have a Java plug-in installed, the installation prompt returns with a message that it will now install the Java plug-in onto the LocalDirector User Interface client host.

Click OK.

A message displays informing you that the Java plug-in is downloading.

Step 11 At the Software License Agreement window for the Java plug-in, read the agreement, then click Yes.

Step 12 Specify the location where you want to install the Java plug-in. By default the plug-in is installed in the folder C:\Program Files\Java Plug-in 1.1. Click Next to continue.

Step 13 If you have an existing Java Runtime Environment (JRE) installed, a window displays asking if you want to use the Java plug-in being installed as the JRE default. Click Yes or No.

An information box displays to tell you to press OK when the Java plug-in installation is complete.

Step 14 Click OK. The setup is complete.

Step 15 If you are installing from Internet Explorer, the login window displays, allowing you to use the LocalDirector User Interface immediately. (Refer to the following caution if you are using Windows 98.) If you are installing from the Netscape Communicator, exit the browser, restart it, and reload the LocalDirector User Interface main page:

http://host_name_or_IP_address:port/LUI31.html

If you are using the Netscape Communicator, exit and restart the browser. Then reload the LocalDirector User Interface main page.

Caution If you are using the Microsoft Internet Explorer browser to install the LocalDirector User Interface client on a Windows 98 system, reboot the system, restart the browser, and reload the LocalDirector User Interface main page.

If you are using Windows 95, Windows NT, or the Netscape browser Communicator, you do not need to reboot the system.

Installing the LocalDirector User Interface Client on UNIX Systems

Follow this procedure to install the LocalDirector User Interface client software on a system running UNIX.

Step 1 Open the Netscape Communicator browser.

Step 2 At the URL line, enter an address with the following format:

http://host_name_or_IP_address:port/LUI31.html

The host name (or IP address) and port number pair are those of the LocalDirector User Interface server host.

If the LocalDirector User Interface client is not installed on the client system, the LocalDirector User Interface server downloads the executable file.

A window displays where you can specify a location for the file LUI31Client.tar. Simultaneously, the browser window displays an installation message.

Step 3 Specify a location for the client installation executable file. By default, this is the Netscape Communicator home directory. You should choose the default directory. Click OK.

Step 4 Go to the directory where the file LUI31Client.tar resides.

Step 5 Run the tar command:

tar xvf LUI31Client.tar

This extracts three files:

Step 6 Run LUI31Install.sh.

Step 7 At the Software License Agreement window for the Java plug-in, read the agreement, then click Yes.

The installation program installs the Java plug-in and places the LUI31.jar file in the $HOME/.netscape/java/lib directory.

Step 8 You can either return to the LUI31.html page and log in now, or exit the browser.

Unsupported Commands

The following commands are not supported by the LocalDirector User Interface. All other LocalDirector commands are supported.

arp (without alias)

color

pager

blocks

config net

ping

boot image

default

reload

bridge

dynamic feedback

static

casa

failover (active or reset)

who

channel

kill

clear

name (the LocalDirector User Interface accepts a name value but does not allow you to modify this value)

Changes for Version 3.1.2

This section describes the changes for Cisco LocalDirector User Interface version 3.1.2.

Changes for Version 3.1.1

This section describes the changes for Cisco LocalDirector User Interface version 3.1.1.

Fixed Bugs

Changes for Version 3.1

This section describes the changes for Cisco LocalDirector User Interface version 3.1.

New Features for Release 3.1

This section describes the changes for Cisco LocalDirector User Interface version 3.1.

Notifications resulting from these polls can take many forms, including simple event logs and SNMP traps.

Known Bugs

The following are known bugs in Release 3.1.2:

A workaround is to always enter the domain name given to the LocalDirector for consistency.
If you want to see the name of a tab that is partially covered, click on it.
A workaround is to select No if you do not want the LocalDirector User Interface JRE to be the default one.
A workaround is that you can inspect the event or system log to view messages.
A workaround is to move the pointer to the secondary window, which moves focus to that window.
A workaround is to refresh the window by clicking the Minimize button (at the top right of the LocalDirector User Interface main window), then clicking the Maximize button.
A workaround is to click the pointer in the box to mark it as checked.
As a workaround, do not create multiple LocalDirector objects for one physical LocalDirector.
As a workaround, you can select the real server, then select the Edit menu Server State option.
As a workaround, run the probe again.
As a workaround, manually resynchronize the LocalDirectors in the LocalDirector User Interface configuration after you restart the LocalDirector User Interface server.
As a workaround, do not delete lines beginning with colons from the Additional tab.
As a workaround, if you want to paste the same object again, reselect the object, copy it, then paste it.
As a workaround, you must press the top right X control to remove the window.
As a workaround, delete the LocalDirector from the LocalDirector User Interface, then recreate it.
As a workaround, be sure that the name you enter is unique.
To prevent confusion, do not create probes with the same name for the same virtual server.
As a workaround, restart the LocalDirector User Interface client.
As a workaround, edit the gwserver.exe file located in the LocalDirector User Interface base directory. Change
NLSPATH=$GEM_BASE_DIR/etc:$NLSPATH
to

NLSPATH=$GEM_BASE_DIR/etc/%N.cat:$NLSPATH

Notes and Caveats

Cisco Connection Online

Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.

Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can access CCO in the following ways:

For a copy of CCO's Frequently Asked Questions (FAQ), contact ccohelp@cisco.com. For additional information, contact ccoteam@cisco.com.

If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or csrep@cisco.com.

CD-ROM Documentation

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more up to date than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.





hometocprevnextglossaryfeedbacksearchhelp
Posted: Mon Jan 10 08:30:13 PST 2000
Copyright 2000©Cisco Systems Inc.