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

Table of Contents

Cisco LocalDirector Version 3.1.4
Release Notes

Cisco LocalDirector Version 3.1.4
Release Notes

November, 1999

These release notes support Cisco Local Director Version 3.1, up to and including Version 3.1.4.

Use these release notes with the Cisco LocalDirector Installation and Configuration Guide on CCO and the Documentation CD-ROM.

Contents

These release notes describe the following topics:

New and Changed Information

The following sections list the new features supported by the Cisco Local Director version 3.1.

New Features in Cisco LocalDirector 3.1.3

There are no new features supported by the Cisco LocalDirector version 3.1.3.

New Features in Cisco LocalDirector 3.1.2

There are no new features supported by the Cisco LocalDirector version 3.1.2.

New Features in Cisco LocalDirector 3.1.1

These following sections list the new and modified features supported by the Cisco LocalDirector 3.1.1:

New Features

A maximum of 256 aliases are allowed.

Modified Features

The following changes have been made to existing LocalDirector features for the 3.1.1 release:

Important Notes

The following sections contain important notes about the Cisco LocalDirector.

This problem is inherent in the Netscape/Apache combination, and occurs whether or not LocalDirector is present. [CSCdk91721]
We have found that Internet Explorer (4.0) does not work with IIS because the server responds to the client's Version 2 hello message with a version 2 server hello message. [CSCdm46555]
The table below shows which combination of browsers and servers are performing correctly:
Browser Apache IIS

Netscape Navigator

works

works

Opera

works

works

Microsoft Internet Explorer

works

works if SSL version 2 is turned off (see CSCdm46555 ReleaseNote or Microsoft customer service document Q187498 for instructions)


This provides the ability to manually override the dynamic weight being fed into LocalDirector.
This is not a LocalDirector problem. This problem is due to the way the CLI reads virtual machine types. The LocalDirector does not know if a port or sticky timer is being specified in the CLI. To remove a sticky timer, specify the following syntax:
no sticky [virt:port:bindid]. [CSCdk90873]

Caveats

Caveats describe unexpected behavior in Cisco LocalDirector 3.1. This section contains open and resolved caveats for the Cisco Local Director version 3.1.

Open Caveats-Version 3.1.4

This section describes possibly unexpected behavior by Cisco LocalDirector version 3.1.4.

The number of sticky connection objects on a standby unit increases faster than the number of sticky connection objects on a primary unit.
Robust FTP is not implemented for static reals.
When using the static command, the LocalDirector does not translate the IP address in the data portion of the packet. This inability to translate the IP addresses causes FTP problems when a server inside the LocalDirector initiates an FTP session.
Pings from standby units usually fail. Arp and bridge tables are not updated when the IP address being pinged is on the same subnet as an alias of the LocalDirector.
Fragmented proxy packets (SSL sticky or robust FTP packets) are not processed correctly if the first packet received is out of sequence and does not contain the entire TCP header.
Proxy connections (SSL sticky or robust FTP) are not reassigned.
Failovers after a configure net with configuration files with lines that are larger than 5k do not always synchronize properly.

Resolved Caveats---Version 3.1.4

The following caveats were resolved for Cisco LocalDirector version 3.1.4.

RNS 4-port Ethernet cards with Intel chips can have 2% alignment errors.
Write mem failures do not generate syslog entries.
False OKs are returned through telnet connections.
If you are replicating FTP connections for a failover scenario, you also have to configure a 'default' virtual port for the virtual IP address in order to receive the data connections which are being replicated to the standby unit.
Backup machines are not properly cleared before replicating the failure configuration.
No error message is printed when a real that was specified by the weight command does not exist.
The weight value for all predictors must be greater than zero. If the weight value for a predictor is less than zero, the real machine will not be used. This behavior is similiar to the real machine behavior in oos maintenance mode.
The real machine does not default to a static weight when a dynamic weight change via DFP times out.
The data-in counter for the show real command does not get decremented correctly if the feature is not turned on for the real machine.
The LocalDirector mishandles ICMP error type 3 code 4 for dispatched mode.
If configuration file fails to download to the flash memory card, a cryptic error message is generated.
The second packet of LDAP traffic is delayed when bridged through the LocalDirector.
If the machines primary is removed a first, a backup machine can not be removed.
The default mode for redirect mode is assisted redirect mode. The default redirect mode should be local redirect mode.
The delay command parameters are hardcoded to 5 minutes.
The weight command is not saved if the weight parameter is the default parameter while the weight timeout parameter is not the default weight timeout parameter.
The LocalDirector weighted / loaded behavior can be unpredictable.
Buddy associations in the standby unit are not cleared during bootup or write standby.
The console does not distinguish between the non-existant sh e 4 command and the existant shu e 4 command. The console should return an error message.
Reals bound to sticky virtuals with SSL enabled will not fail.
The LocalDirector connection counter does not decrement properly.
If names are on, the delay command writes the name instead of the IP address into the configuration terminal. The end result is the loss of the command on reboot.
If the LocalDirector has a 4-port RNS card with the DEC chip set, internal looping occurs when you manually change the line speeds from 10baset to 100basetx and then back to 10baset.
If the no data command is invoked without keywords, no error message is displayed and nothing is changed. Additionally, the no data real_ip_address command does not return the value to 0; the data real_ip_address 0 command must be used to return the value to 0.
Clearing the default gateway with the clear configuration secondary command causes problems when the user invokes this command from a telnet session within a firewall.
Concurrent boot image commands from either a console or a telnet session will cause the LocalDirector to reload.
Concurrent conf net and write net commands from either a console or a telnet session will cause the LocalDirector to pause indefinitely.
The LocalDirector does not fail an FTP virtual when robust FTP for the virtual is enabled.
New connections are not reassigned to new reals when an RST is sent from the real.
The Ethernet driver can be corrupted by proxy or local telnet if either service retransmits packets.
Repeated use of the show error command causes the LocalDirector to reboot.
Reassign commands fail due to invalid TCP checksums in SYN.
The write standby command does not work.
LocalDirector is displayed in telnet password prompts.
Packets that arrive at a virtual server for a non-existent connection generate an RST to the client with a source IP address of 0.0.0.0.
Client connections are not RST'd when a real server is not available for a virtual server.
Real servers and virtual servers must have the same port to enable bind in dispatched mode.

Resolved Caveats---Version 3.1.3

The following caveat was resolved for Cisco LocalDirector version 3.1.3.

A telnet session to the LocalDirector caused a reboot after exiting the session.

Resolved Caveats---Version 3.1.2

The following caveat was resolved for Cisco LocalDirector version 3.1.2

The proxy code, which is used in the SSL sticky feature, dropped the first packet that completed the SSL handshake and contained data. The client had to resend the data, based on TCP timers, for the SSL session to continue. Although the SSL connections worked, the connections were slow because of the DATA resend that was required for the data dropped in the packet. This problem was compounded when the web page was composed of several sessions.

Resolved Caveats---Version 3.1.1

The following caveats were resolved for Cisco LocalDirector version 3.1.1:

Packets destined for servers on a different subnet than the LocalDirector traversed the outside Ethernet three times before being forwarded to the appropriate server if directly-connected multiple logical subnets were running on the inside interface.
Using the sticky command created a load inbalance when clients were coming from a site that used a proxy server to access the Internet. Since sticky in Version 2.x used the client's IP address for storing the association to a real server, all clients coming from a proxy server were sent to the same real server.
LocalDirector had to disable the Cisco Syslog MIB, so traps were not sent for every SYSLOG message when an SNMP host was configured.
The show interface command would display only interface 0 statistics when the show interface ethernet n command was issued, regardless of what interface number n represented.
Connection replication only occured at the beginning of a connection. If failover occured, a connection remained intact on the newly active box. However, if the previously active box was rebooted and failover switched back , the connection was lost. All replication was lost on connections that were established before replication was enabled (even though the connection still existed) or if the standby box was rebooted.
If the standby unit was not present when the active LocalDirector was receiving connections in a failover configuration, the established connections were not replicated to the standby unit when they became available.
Support for the UDP protocol was needed for virtual servers and real servers.
The show memory command output was static. LocalDirector pre-allocated its memory on bootup in accordance to the configuration.
This was misleading to users who looked at the command as a way of determining how loaded their system was. Typically, this output did not change, regardless of the load on the system.
The command telnet 0.0.0.0 255.255.255.0 was accepted, but failed to perform any action. However, the command telnet 0.0.0.0 0.0.0.0 worked.
You could only retrieve the value for the first MIB instance in the cldVirtualTable.
If you attempted to create a real server that already existed on LocalDirector, an error message without a carriage return would display, making the output look garbled.
There was no value for the SNMP object sysobjectOID.
The oos command was not understood when downloading a configuration from a TFTP server with the config net file ip command.
When trying to bind a server on a port higher than 32768, LocalDirector responded with the following error message:
machine does not exist; can't bind
If the snmpwalk or snmpget was used against LocalDirector, the incorrect value of 0 for ifAdminStatus was received.
Snmpwalk returned no information and produced the "End of MIB" message for walks on anything short of or equal to .1.3.6.1.2.
When binding an existing virtual server to a non-existent real server by IP address, LocalDirector responded with a correct error message. However, if an invalid name was used, the incorrect error message "arg2: invalid IP address" was returned.
Using the conf f command without a floppy disk in the drive failed to generate an error message.
An snmpget of cldRealTotalConnections using an index of (cldRealIPAddress,cldRealPort) with port value 0 resulted in LocalDirector returning the incorrect object, cldRealIPAddress, instead of the requested object.
LocalDirector performed a gratuitous ARP for each enabled interface. These gratuitous ARPs were propagated to each interface. This caused additional log entries in the networks when log events such as MAC address changed for IP addresses.
When LocalDirector would fail, it would shut down its interfaces. This was done as a precautionary measure to prevent a failed unit from harming the rest of the network (by constantly transmitting trash, and so forth). If you used the write mem command on LocalDirector while it was failed, it saved the information when the interfaces were down.
The arp command returned incorrect information if a colon was incorrectly used in the IP address.
SNMP traps that referenced real servers and virtual servers were not correct. For example, the trap (output from CWW):
4/8/99   21:31:44 LD              Trap: P3  1, 
ent=ciscoLocalDirectorMIBNotificationPrefix, comm=public, cldVirtualTable.4.5.4.3.2.1.0.0=2     LD
referenced cldVirtualTable.4, but there is no variable "4" in cldVirtualTable. Instead of: 
cldVirtualTable.4.5.ip_address.port.bind_id=value
Below is the correct output:
cldVirtualTable.cldVirtualTableEntry(1).cldVirtualState(4).ip_address.port.bind_id=value
If a failover cable was not connected and the write standby command was issued, the configuration was not replicated and the error message was not returned.
In a failover setup, the active unit replicates the configuration to the standby unit when the standby unit is available. Before the configuration is replicated, the current configuration on the standby unit is erased. However, in version 2.2.2, the static commands were not erased before replication, which led to a reboot on the show static command.

Related Documentation

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

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: Wed Nov 24 18:21:14 PST 1999
Copyright 1989-1999©Cisco Systems Inc.