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

Table of Contents

Cisco LocalDirector Version 1.6.6 Release Notes

Cisco LocalDirector Version 1.6.6 Release Notes

February, 1998

This document describes changes to features and commands that are different or not described in the Cisco LocalDirector Installation and Configuration Guide, Version 1.6.3 (Document Number 78-3456-05).

The following sections are included:

Changes for Version 1.6.6

Cisco LocalDirector version 1.6.6 includes the following changes:

Bug Fixes in Version 1.6.6


Note This problem seems much more prevalent on older Intel NICs, and has only been seen twice with a LocalDirector connected to 10BaseT hubs.

LocalDirector Platforms

There are three LocalDirector platforms - the new LocalDirector 420, the new LocalDirector 410, and the original LocalDirector. The original LocalDirector (CA-LDIR) is now referred to as the LocalDirector 415. See the Cisco Product Bulletin at http://www.cisco.com/ld for more information about the LocalDirector 420 and 410.

LocalDirector 420

LocalDirector version 1.6.5 and later supports the 4-port Ethernet interface in the LocalDirector 420. The ports are numbered 0 to 3, with port 0 on the top of the interface and port 3 on the bottom. Only port 0 and port 1 are enabled at this time. The other two ports are disabled until version 2.x. It does not matter which port connects to the client network and which connects to the real server network. Multiple 4-port cards will be supported in version 2.x.


Note Ports 2 and 3 on the LocalDirector 420 are disabled until version 2.x.

The front panel of the LocalDirector 420 is shown in Figure 1. Note that the diskette drive, interfaces, console port, and failover port are accessed from the front panel.


Figure 1: LocalDirector 420 Front Panel

The back panel of the LocalDirector 420 is shown in Figure 2. The power cord receptacle and power switch are located at the back of the unit.


Figure 2: LocalDirector 420 and 410 Back Panel

LocalDirector 410

The front panel of the LocalDirector 410 is shown in Figure 3:


Figure 3: LocalDirector 410 Front Panel

The LocalDirector 410 back panel is the same as the LocalDirector 420, shown in Figure 2.

LocalDirector version 1.6.5 and later supports two of the 10/100 interfaces on the LocalDirector 410. The ports are numbered 0 to 2 from the left to the right, and port 2 on the third interface is disabled until version 2.x.


Note Port 2 on the third interface of the LocalDirector 410 is disabled until version 2.x.

LocalDirector 415

Version 1.6.x software is supported on the LocalDirector 415.


Note In version 1.6.5 and earlier, interfaces on the LocalDirector 415 are read right to left, which is the opposite of the LocalDirector 410 and 420. In LocalDirector version 2.x, all interfaces will be numbered left to right, top to bottom. Interface numbers of existing units will change to conform to this numbering scheme.

Rackmount Brackets

Rackmount brackets are optional on the LocalDirector 420 and 410. To attach the rackmount brackets, refer to Figure 4.


Figure 4:

Attaching Rackmount Brackets

Supported Interfaces

Table 1 shows the interfaces that are supported on the LocalDirector platforms:


Table  1: Supported Interfaces by Platform
Platform 4-Port 10/100 Ethernet Card 1-Port 10/100 Ethernet Card FDDI
LocalDirector 420 1 supported in version 1.6.5 and later, up to 4 in version 2.x not supported 2 supported (multimode, dual-attached, SC connectors)
LocalDirector 415 (original platform, CA-LDIR) 1 supported in version 2.x 2 supported in version 1.6.5 and later, 3 supported in version 2.x 2 supported (multimode, dual-attached, SC connectors)
LocalDirector 410 not supported 2 supported in version 1.6.5 and later, 3 supported in version 2.x not supported

4-port Ethernet cards are supported on the LocalDirector 420, and the LocalDirector 415 will support one 4-port Ethernet card in version 2.x. The LocalDirector 410 does not support 4-port Ethernet.

Interface Numbering

The LocalDirector interface numbering scheme will change with the introduction of 4-port Ethernet cards. The 4-port interfaces on the LocalDirector 420 are numbered left to right, top to bottom.

Interfaces on the LocalDirector 415 are numbered right to left, bottom to top. Interface numbering on existing LocalDirector 415 units will remain the same in version 1.6.x, but will change to left to right, top to bottom in version 2.x.


Note Interface numbering on the LocalDirector 415 will remain the same in version 1.6.x, but will reverse when upgraded to version 2.x.

LEDs

Each interface port has two LEDs, one amber and one green. Table 2 explains the states of the LEDs on the 4-Port interface cards.


Table  2: 4-Port Interface LEDs
LED LED State Indication

Green

off No data transmission.
on Steady data transmission.
flashing Intermittent data transmission.

Amber

off Disabled or unused. If the interface was configured with the 10baset, 100basetx, or 100full options, the link is not up yet.
on The connection is active.
flashing Autosensing. If the interface was configured with the auto option, the link is not up yet.

Note The LED behavior on the 4-port Ethernet interface is different from other Cisco products. Use this information to determine if the LED activity indicates normal interface operation.

Autonegotiation

The 4-port card in the LocalDirector does not autonegotiate. When a 4-port interface is
configured using the int eth 1 auto command, it will perform autosense. The main difference between autosense and autonegotiation is that autosense can not be used to establish full-duplex links. Use the int eth 1 100full command to set full-duplex mode.

The single-port card will autonegotiate, but your network interface must support auto-detection.


Note The 4-port interface will not "autosense" to full duplex. This will cause a problem if the LocalDirector interface is at half duplex and is connected to a switch on the other end trying to do full duplex.

Notes and Caveats


Note A failover IP address must be set for failover to work properly. Failover changed significantly in version 1.6, and failover must be re-configured when LocalDirector units are upgraded from a previous version.
snmp ifc 1 = LD ifc 0
snmp ifc 2 = LD ifc 1

Documentation Errata

The configuration example for Secure Socket Layer Protocol in Chapter Three, "Configuring LocalDirector," of the Cisco LocalDirector Installation and Configuration Guide, Version 1.6.3, incorrectly uses a real server IP address with the sticky command. The example should read as follows:

The virtual command is used to identify 192.168.1.100 443 as a virtual server accepting traffic on port 443 (SSL):

LocalDirector(config)# virtual 192.168.1.100 443

The sticky command is used to ensure that requests from the same client will be sent to the same real server until 10 minutes of inactivity have elapsed:

LocalDirector(config)# sticky 192.168.1.100 443 10

Known Bugs


Note The only time this could be a problem is if you use unregistered IP addresses on real machines. The client cannot communicate directly with a real machine that has an unregistered IP address across the Internet.

Bug Fixes in Version 1.6.5

Bug Fixes in Version 1.6.4

Bug Fixes in Version 1.6.3

Bug Fixes in Version 1.6.2

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, select Documentation, and click Enter the feedback form. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.



hometocprevnextglossaryfeedbacksearchhelp
Copyright 1989-1998 © Cisco Systems Inc.