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

Table of Contents

Release Notes for Cisco LocalDirector Version 3.3

Release Notes for Cisco LocalDirector Version 3.3

1 May 2000

These release notes support Cisco LocalDirector Version 3.3 up to and including Release 3.3.1.

Contents

These release notes describe the following topics:

New and Changed Information

The following sections list the new features supported by the Cisco LocalDirector Version 3.3.

New Feature for LocalDirector-DistributedDirector Interaction

The dynamic-feedback-agent command and the dynamic-feedback-agent-ip command have been added to LocalDirector Release 3.3.1 so that Cisco Systems DistributedDirectors can download availability information on virtual servers from a LocalDirector. DistributedDirectors can use this information to identify load imbalances over multiple sites and distribute Internet traffic more evenly. The process is performed by a Dynamic Feedback Protocol (DFP) manager on the DistributedDirector and a DFP agent on the LocalDirector. The DFP agent calculates an availability metric for specified virtual servers, and the DFP manager uses the metrics to make load distribution decisions.

The dyanamic-feedback-agent command enables listening for IP connection requests from DFP managers. If listening has not been enabled, LocalDirector does not honor the connection request.

[no] dynamic-feedback-agent [port]

localdirector(config)# dynamic-feedback-agent localdirector(config)# show dynamic-feedback-agent dynamic-feedback-agent 8080

The optional port parameter specifies the TCP port. The default port is 8080. The no-dynamic-feedback-agent command disables listening and closes any current DFP connections.

The dynamic-feedback-agent-ip command specifies DFP manager hosts (DistributedDirectors) that may connect to a LocalDirector for DFP communications. If the IP address has not been specified, LocalDirector will not honor the connection request. You can enter up to 256 IP addresses. Localdirector can support up to 256 connections at one time.

[no] dynamic-feedback-agent-ip ip [password]

localdirector(config)# dynamic-feedback-agent-ip 10.10.10.200 localdirector(config)# show dynamic-feedback-agent-ip dynamic-feedback-agent-ip 10.10.10.200

The ip parameter specifies the IP address of the host. The optional password parameter enables security (MD5 encryption) and specifies the security password for the connection. The no-dynamic-feedback-agent-ip command removes an IP address (and closes the connection if one for that IP address is currently open). If the password option has been specified, you must include it in a command to remove an IP address.

Feature for Cookie-based sticky options

The cookie-insert and cookie-passive options have been added to the sticky command to enable sticky connections based on a cookie in the HTTP GET request.

The sticky connection for the cookie-insert option relies on a cookie created by LocalDirector. The sticky connection for the cookie-passive option relies on a cookie created by the sticky real server.

[no] sticky virtual_id minutes [generic | ssl | cookie-insert [name] [domain] | cookie-passive name]

ld(config) 10# virtual 192.168.1.1:444:0:tcp ld(config) 11# virtual 192.168.1.1:445:0:tcp ld(config) 12# sticky 192.168.1.1:444:0:tcp 100 cookie-insert LDcookie ld(config) 13# sticky 192.168.1.1:444:0:tcp 1000 cookie-passive mycookie ld(config) 14# show sticky Virtual Machine(s) Sticky 192.168.1.1:445:0:tcp 1000 cookie-passive mycookie 192.168.1.1:444:0:tcp 100 cookie-insert LDcookie

The sticky real server association is based on the IP address of the virtual server specified by the virtual_id parameter. Cookie-insert adds the minutes value to the LocalDirector clock time (set by the clock set command described below) to calculate the date in the future when the association expires. Using the optional name and domain parameters for cookie-insert, you can enter your own cookie value and domain name (which you may find useful for tracking purposes). If you do not enter a cookie name, the default value is LocalDirector-Insert-Cookie (there is no default domain name). Cookie-passive requires you to enter a name parameter. It is a keyword used by LocalDirector to identify packets from the sticky real server. The name is limited to 128 bytes. If you enter a name that is greater than 128 bytes, LocalDirector ignores the extra bytes.

The syntax for clear sticky and show sticky has changed. You can now clear or show sticky associations per the virtual server or the real server.

clear | show sticky [virtual | real] [virtual_id | real_id]

If you select the virtual keyword, you must follow it with the virtual_id parameter (the virtual server IP address or name, port number, bind-id, and protocol). If you select the real keyword, you must follow it with the real_id parameter (the IP address or name of the real server, port number, bind-id, and protocol).

New Feature for Setting the Clock in the Cisco LocalDirector

Use the clock set command to set the date and time for LocalDirector. You must enter the Coordinated Universal Time (UTC) which is the international time standard used by LocalDirector. You can not disable the clock.

clock set hh:mm:ss month day year

localdirector(config)# clock set 17:00:00 march 21 2000 localdirector(config)# show clock set Tues 17:00:04 Mar 21 2000 UTC
Warning You must set the date and time accurately if you are using the cookie-insert option of the sticky command.

Important Notes

The following list contains important notes about the Cisco LocalDirector Version 3.3.

weight real_id number [time_value{s|m}]

[time_value{s|m}] (Optional) The amount of time before LocalDirector reverts to the static weight. An s for seconds or an m for minutes appended to the time_value input determines the time denomination. The default input time denomination is minutes.

Caveats

Caveats describe unexpected behavior in Cisco LocalDirector 3.3. This section contains open and resolved caveats for Cisco LocalDirector Version 3.3.


Warning If two servers have the same cookie name and value, the client sessions do not stick with one particular server.

Open Caveats---LocalDirector Release 3.3.1

Secondary crashed with a virtual with generic sticky and replication.
DFP: Primary and Secondary LDs crash when no virtuals are defined.
GigE cable cut does not auto-recover and shuts down all other interfaces.
LD does not forward last ACK from server causing retransmits.
For FTP data, the LD is not forwarding SYN/ACKs from client out of the server port.
In cookie-sticky mode, the cookie timer should be at least 10 minutes.
Backup virtual does not bring any real servers In Service after a failure.
Cookie-passive never times out after second real is selected.
LD reports wrong information to DistributedDirector after a change in Bind ID.
LD sending CASA packets with incorrect CASA header information.
Packet buffers consumed by Proxy services in FDDI.
Port-mapping incorrect in SSL sticky mode.
A reboot can occur if no answer from a real server in proxied connection is received.
CASA:LD locks up with conf net if configuration on tftp server is different.
Proxied connections not cleared correctly for timed out connections.
Command: clear config ? in conf iguration mode causes problems.

This section describes possible unexpected behavior in Cisco LocalDirector Release 3.3.1.

Resolved Caveats---LocalDirector Release 3.3.1

All the caveats listed in this section are resolved in Cisco LocalDirector Release 3.3.1.

CASA: LocalDirector transmits wildcard updates with a Time To Live (TTL) of zero.
CASA: LocalDirector transmits Ethernet packets in hardware byte order.
LocalDirector crashes repeatedly during internal tests.
LocalDirector crashes while processing internal test traffic.
LocalDirector crashes when the restart [virtual] command is applied to a failed virtual.
CASA: LocalDirector builds TCP RST packets incorrectly.
LocalDirector crashed once under active load during an internal test.
The component header is missing for affinity update IP packets.
CASA: LocalDirector crashes after running the no casa service-manager port command.
LocalDirector crashed during an internal test.
LocalDirector does not assign affinities for UDP traffic.
LocalDirector crashes when you use the no bind command to release an association between a real and a virtual.
Attempts to open an FTP connection through LocalDirector fail.
LocalDirector returns a defective affinity update in response to an interest match when security is enabled.
LocalDirector sends out wild cards at >64000 pps when you use the redirection command to set the wild card TTL to <1.
LocalDirector performance drops unexpectedly as you add forwarding agents.
LocalDirector crashed during an internal test while running SSL with fragmented packets.
LocalDirector does not forward the last ACK in a TCP connection to the router causing the client to retransmit the TCP FIN.
LocalDirector connection counters for virtuals and reals are incorrect when reals respond with a TCP RST for new connections.
Mixed Network Interface Cards in the LocalDirector causes the unit to fail during boot-up.
CASA: The LocalDirector redirection command allows you to set directed mode and casa simultaneously for a virtual. This combination is not supported by CASA.
LocalDirector reassigns servers after both the client and the server fail.
A LocalDirector 430 with RNS Network Interface Cards crashes when interfaces are brought up and then quickly brought down.
Generic Sticky is broken.
rotor_registerb: cannot register blocks [128].
Cleaning of enable password causes unknown enable password.
LD does not rotor UDP traffic with source port of 0.

Related Documentation

The following documents are specific to Cisco LocalDirector Version 3.3 and are located on Cisco Connection Online and the Documentation CD-ROM.

Platform-Specific Documents


Note The Gigabit Ethernet network interface cards are used only on LocalDirector hardware platform Models 420 and 430.

The following documents are specific to Cisco LocalDirector Version 3.3 and are located on CCO and the Documentation CD-ROM:

On CCO at:
Service & Support: Documentation Home Page: LocalDirector Documentation: LocalDirector Version 3.3 Documentation
On the Documentation CD-ROM at:
Cisco Product Documentation: LocalDirector Documentation: LocalDirector Version 3.3 Documentation
On CCO at:
Service & Support: Documentation Home Page: LocalDirector Documentation: LocalDirector Version 3.3 Documentation
On the Documentation CD-ROM at:
Cisco Product Documentation: LocalDirector Documentation: LocalDirector Version 3.3 Documentation

Obtaining Documentation

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.

Ordering Documentation

Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.

Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).

Obtaining Technical Assistance

Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.

Cisco Connection Online

Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.

CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.

Customers and partners can self-register on CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.

You can access CCO in the following ways:

You can e-mail questions about using CCO to cco-team@cisco.com.

Technical Assistance Center

The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.

To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.

To contact by e-mail, use one of the following:

Language E-mail Address

English

tac@cisco.com

Hanzi (Chinese)

chinese-tac@cisco.com

Kanji (Japanese)

japan-tac@cisco.com

Hangul (Korean)

korea-tac@cisco.com

Spanish

tac@cisco.com

Thai

thai-tac@cisco.com

In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.

Documentation Feedback

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

You can e-mail your comments to bug-doc@cisco.com.

To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:

Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate and value your comments.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Wed May 10 15:53:54 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.