|
|
November, 1999
These release notes support the Cisco Local Director User Interface Version 3.1.1.
These release notes describe the following topics:
This section describes the system requirements for the Cisco Local Director User Interface, Version 3.1.1 and includes the following sections:
Table 1 and Table 2 describe the minimum memory requirements for the server and the client running the LocalDirector User Interface. The system that initially installs the LocalDirector User Interface is the LocalDirector User Interface server, and the system from which you access the LocalDirector User Interface is the client.
If the LocalDirector User Interface server and client are installed on the same system, add the relevant memory requirements from both tables to calculate the total memory requirements.
| 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 |
| Memory | Size |
|---|---|
RAM | 32 MB on UNIX 32 MB on Windows NT |
Disk space | 20 MB on UNIX 20 MB on Windows NT |
In order to use the Cisco LocalDirector User Interface Version 3.1.1, Cisco LocalDirector version 3.1 must be connected to the network.
For information on installing Cisco LocalDirector, version 3.1, see the Cisco LocalDirector Installation and Configuration Guide, Version 3.1.
LocalDirector User Interface clients and servers depend partially on third-party products. The following programs must be installed prior to installing the LocalDirector User Interface.
| Platforms/Operating Systems | Vendor |
|---|---|
Solaris UNIX v2.6 Sparc OS (February 1999 Sun recommended patch cluster) | Sun Microsystems |
Windows NT v4.0 SP4 | Microsoft |
| Platforms/Operating Systems | Vendor |
|---|---|
Solaris UNIX v2.6 Sparc OS (February 1999 Sun recommended patch cluster) | Sun Microsystems |
| Microsoft |
This section describes how to install the LocalDirector User Interface server. The LocalDirector User Interface server can be installed on either a Windows NT or a Solaris UNIX operating system. After installing the LocalDirector User Interface server, install the LocalDirector User Interface client as described in the "Installing the LocalDirector User Interface Client" section.
This section describes the following topics:
Before installing the LocalDirector User Interface on a Windows NT system, decide where to place the following directories:
The following procedure explains how to install the LocalDirector User Interface server on a Windows NT system:
Step 1 Log on 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 the CD.
Otherwise, download the LocalDirector User Interface server self-extracting compressed file from CCO at the following URL:
http://www.cisco.com/cgi-bin/tablebuild.pl/localdir
To uncompress and move the file to a temporary directory on the intended host system of the LocalDirector User Interface server, double-click the file.
Step 3 Locate and run the Setup.exe file on the temporary directory or the CD. Running the Setup. exe file starts the InstallShield program. After reading the introductory information from the InstallShield program, click Next.
Step 4 Specify the location where the LocalDirector User Interface will be installed. The default location for the LocalDirector User Interface server is at C:\Program Files\Cisco\LocalDirector User Interface 3.1. Click Next to continue.
Step 5 Select the location of the program folder for the LocalDirector User Interface server shortcuts. The default location for the shortcuts is in the LocalDirector User Interface 3.1 folder. Click Next to continue.
A message display indicating that the files are being copied should appear.
Step 6 If the Java plug-in is already installed, proceed to Step 9. If the Java plug-in is not installed, the installation prompt will return with a message indicating that the Java plug-in will be installed onto the LocalDirector User Interface server host.
Click OK.
A message display indicating that the installer is unpacking the Java plug-in should appear.
Step 7 Read the Software License Agreement window for the Java plug-in. After reading the agreement, click Yes.
Step 8 Specify the location for the Java plug-in. The default folder for the plug-in is C:\Program Files\Java Plug-in 1.1. Click Next to continue.
Step 9 If an existing Java Runtime Environment (JRE) is installed, a window appears asking if you would like to use the new Java plug-in as the JRE default. If you'd like to preserve compatibility with existing applications without risk, click No. Click Yes or No to proceed.
Follow the screen instructions, which will instruct you to press the OK button when the Java plug-in installation is complete.
Step 10 Click OK. The setup is complete.
Before you install the LocalDirector User Interface server on a UNIX system, determine the directory where the LocalDirector User Interface server should be installed.
LocalDirector User Interface server software for UNIX systems is installed from a tar file.
The following procedure explains how to install the LocalDirector User Interface server on a UNIX system:
Step 1 If the LocalDirector User Interface server software is being installed to a central location such as /usr/local, log on as root. If you are installing the software into your local directory, log on as yourself.
Step 2 If LocalDirector User Interface server software is being installed from a CD, insert the CD.
Otherwise, download the lui31_fcs_solaris251_rel_tar.Z file from CCO.
Step 3 Locate 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.
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 a Java plug-in is not already installed). The LocalDirector User Interface client software can be used on the same system as the LocalDirector User Interface server or on a different system.
This section describes the following topics:
Follow this procedure to install the LocalDirector User Interface client on a system running Windows 95, Windows 98, or Windows NT system:
Step 1 Open a web 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 from 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 will download the executable file.
Step 3 If you are using Netscape Communicator, continue with the next step.
If the Microsoft Internet Explorer browser is used while the Java 1.1.2 plug-in is not installed, a window will appear asking if you want to install the Java plug-in 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 16.
Step 4 Click the download icon to download the client installation executable file.
Step 5 In the download dialog box, specify the end location for the client installation executable file.
Step 6 Locate 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. After reading the introductory information, click Next.
Step 9 Specify the location for the LocalDirector User Interface client software. The default folder for the client is located at the following path:
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 the Java plug-in is already installed, proceed to Step 14. If the Java plug-in is not installed, the installation prompt indicates that the Java plug-in will be installed onto the LocalDirector User Interface client host.
Click OK.
A message will inform you that the Java plug-in is downloading.
Step 11 After reading the Software License Agreement, click Yes.
Step 12 Specify the location for the Java plug-in. The plug-in is installed in the following folder by default: C:\Program Files\Java Plug-in 1.1. Click Next to continue.
Step 13 If an existing Java Runtime Environment (JRE) is installed, a window appears asking if you would like to use the new Java plug-in as the JRE default. If you'd like to preserve compatibility with existing applications without risk, click No. Click Yes or No to proceed.
An information box displays to tell you to press OK when the Java plug-in installation is complete.
Step 14 Click OK to complete the setup.
Step 15 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.
Step 16 If you are installing from Internet Explorer, the login window appears and allows you to use the LocalDirector User Interface immediately. If you are installing from the Netscape Communicator, exit the browser, restart, and reload the LocalDirector User Interface main page:
http://host_name_or_IP_address:port/LUI31.html
Follow this procedure to install the LocalDirector User Interface client software on a UNIX system.
Step 1 Open the Netscape Communicator browser.
Step 2 Enter an address with the following format in the URL line:
http://host_name_or_IP_address:port/LUI31.html
The host name (or IP address) and port number pair are from the LocalDirector User Interface server host.
If the LocalDirector User Interface client is not installed on the client system, the LocalDirector User Interface server will download the executable file.
A window display specifies a location for the file LUI31Client.tar. The browser window simultaneously displays an installation message.
Step 3 Specify a location for the client installation executable file. The Netscape Communicator home directory is the default location. Cisco Systems advises you to change this location. Click OK.
Step 4 Go to the directory where the LUI31Client.tar file resides.
Step 5 Run the tar command:
tar xvf LUI31Client.tar
Running the tar command extracts three files:
Step 6 Run LUI31Install.sh.
Step 7 Read the Software License Agreement window for the Java plug-in, 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 login now, or exit the browser.
The following sections list the new features supported by the Cisco LocalDirector User Interface Version 3.1.
This section describes the changes for the Cisco LocalDirector User Interface Version 3.1.
LocalDirector User Interface Release 3.1 uses either a Windows NT (workstation or server) or Solaris UNIX server component.
LocalDirector User Interface Release 3.1 uses a web-based Java client component.
All changes made in the LocalDirector User Interface Release 3.1 are now immediately reflected in the LocalDirector.
LocalDirector User Interface Release 3.1 can now poll all the real servers of a virtual server for the following information:
Notifications resulting from these polls can take many forms, including simple event logs and SNMP traps.
LocalDirector User Interface Release 3.1 supports the Out-of-service Failed LocalDirector server state. Out-of-service Failed is a server state where the server is taken out of service upon failure of one of the above polls.
The following sections contain important notes about Cisco LocalDirector User Interface Version 3.1.1.
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) |
|
Web Browsers, such as Netscape and Internet Explorer, cannot run multiple applets. Although multiple applets can be opened by more than one window, such as a LocalDirector User Interface, browsers share the same applet between all windows. As a result, attempts to browse away from the applet in any window will result in unloads that will destroy the only LocalDirector User Interface applet.
If the LocalDirector User Interface is used with a LocalDirector that has previously been configured for the Network Director environment, the LocalDirector User Interface may remove the Network Director portions of the configuration.
The workaround is to not use the LocalDirector User Interface with Network Director.
Caveats describe unexpected behavior in Cisco Local Director User Interface Version 3.1.
This section describes possibly unexpected behavior by Cisco LocalDirector User Interface Version 3.1.1.
NLSPATH=$GEM_BASE_DIR/etc:$NLSPATH
All the caveats listed in this section are resolved in Cisco LocalDirector User Interface Version 3.1.1.
The following documents are specific to Cisco Local Director Version 3.1 and are located on CCO and the Documentation CD-ROM:
On CCO at:
Service & Support: Documentation Home Page: Internet Service Unit: LocalDirector Documentation: LocalDirector Version 3.1: Documentation
On the Documentation CD-ROM at:
Cisco Product Documentation: Internet Service Unit: LocalDirector Documentation: LocalDirector Version 3.1: Documentation
On CCO at:
Service & Support: Documentation Home Page: Internet Service Unit: LocalDirector Documentation: LocalDirector Version 3.1: Documentation
On the Documentation CD-ROM at:
Cisco Product Documentation: Internet Service Unit: LocalDirector Documentation: LocalDirector Version 3.1: Documentation
On CCO at:
Service & Support: Documentation Home Page: Internet Service Unit: LocalDirector Documentation: LocalDirector Version 3.1: Documentation
On the Documentation CD-ROM at:
Cisco Product Documentation: Internet Service Unit: LocalDirector Documentation: LocalDirector Version 3.1: Documentation
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.
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.
Posted: Fri Jan 7 14:37:21 PST 2000
Copyright 2000©Cisco Systems Inc.