hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

LocalDirector Hardware

LocalDirector Hardware Platforms

LocalDirector 430 (LDIR-430)

LocalDirector 416 (LDIR-416)

Rack-Mount Brackets

Supported Interfaces

Interface Numbering

4-Port Interface Cards

FDDI Interfaces


LocalDirector Hardware


This chapter describes LocalDirector hardware platforms, including interface cards. This chapter contains the following sections:

LocalDirector Hardware Platforms

Supported Interfaces

LocalDirector Hardware Platforms

LocalDirector introduced the 430 and 416 hardware platforms in version 2.2.1. Support for the previous LocalDirector hardware platforms (the 410, 415, and 420, fully described in Version 2.1 of this guide) continues. shows the features offered by the 416 and 430 platforms.

Table 2-1 LocalDirector Hardware Platform Comparison

LocalDirector 430
LocalDirector 416

384 MB RAM

32 MB RAM

2 MB Flash memory

2 MB Flash memory

One 4-port 10/100 Ethernet interface card

Three 10/100 Ethernet ports


LocalDirector 430 (LDIR-430)

LocalDirector 430 includes:

384 MB of RAM

2 MB of Flash memory

One 4-port 10/100 Ethernet interface card, optional FDDI

19-in. rack-mount enclosure

DB-9 EIA/TIA-323 console interface port

3.5-in. diskette drive

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

Figure 2-1 LocalDirector 430 Front Panel

The back panel of both the LocalDirector 430 and 416 are shown in . The power cord receptacle and power switch are located at the back of the units.

Figure 2-2 LocalDirector 430 and 416 Back Panel

LocalDirector 416 (LDIR-416)

LocalDirector 416 includes:

32 MB of RAM

2 MB of Flash memory

Three 10/100 Ethernet interface ports

19-in. rack-mount enclosure

DB-9 EIA/TIA-323 console interface port

3.5-in. diskette drive

The front panel of LocalDirector 416 is shown in .

Figure 2-3 LocalDirector 416 Front Panel

Rack-Mount Brackets

Rack-mount brackets are optional on LocalDirector 430 and 416. shows you how to attach the brackets.

Figure 2-4 Attaching Rack-Mount Brackets

Supported Interfaces

shows the interfaces that are supported on LocalDirector platforms.

Table 2-2 Supported Interfaces by Platform

Platform
4-Port 10/100 Ethernet Card
1-Port 10/100 Ethernet Card
FDDI
LocalDirector 430

1 included with unit, up to 4 supported

RJ-45 connectors

Autonegotiation

Not supported

2 supported

SMT 7.3, multimode,
dual-attached, SC connectors

LocalDirector 416

Not supported

3 included with unit

RJ-45 connectors

Autonegotiation

Not supported


Interface Numbering

Interfaces on LocalDirector models are numbered left to right, top to bottom. shows the interface numbering for a LocalDirector 430 with four 4-port Ethernet interface cards installed.

Figure 2-5 Interface Numbering for LocalDirector 430

4-Port Interface Cards

One 4-port Ethernet card is shipped standard with LocalDirector 430. Up to three more
4-port Ethernet cards can be added.

LocalDirector supports two types of 4-port Ethernet cards. To check the type of card you have, use the show interface command. The output of the command tells which type of card you have. describes the types of 4-port Ethernet cards that ship with LocalDirector.

Table 2-3 4-Port Ethernet Interface Card Features

Card Type
show interface Command Output
LED Color
Features

RNS card

Hardware is rns23x0 ethernet

Amber on left edge of card

Autodetection

Intel card

Hardware is i82557 ethernet

Green on right edge of card

Autonegotiation


LEDs for Intel Ethernet Cards

Each interface port has two green LEDs. The following describes the two LEDs on the Intel Ethernet 4-port interface cards:

Flashing green—Indicates data transmission activities

Steady green—Active connection (Link Up; this is normal operation)

LEDs for RNS Ethernet Cards

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

Green—Indicates data transmission activities relative to the amount of traffic

Flashing amber—Autosensing in progress (even with no configuration and no cable connections)

Steady amber—Active connection (this is normal operation)


Note   The interface ethernet 0 auto command causes the amber LED to flash continually when the link is not up, and the interface ethernet 0 [10baset|100basetx|100full] command shuts off the amber LED when the link is not up.


Table 2-4 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 is configured with the 10baset, 100basetx, or 100full options, the link is not up yet.

On

The connection is active.

Flashing

Autosensing. If the interface is configured with the auto option, the link is not up yet.



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


Autonegotiation

The 4-port rns23x0 Ethernet card does not accept the auto option with the interface ethernet command, and returns the following error message:

ERROR: this port does not have autonegotiation capability.

The ports on the 4-port rns23x0 Ethernet card default to 100BaseTX. The 10baset, 100basetx, and 100full options are available, but the auto option is not.

If the peer port autonegotiates, the 4-port rns23x0 Ethernet interface speed must be set with the 10baset or 100basetx options; setting it to 100full confuses the autonegotiation process on the peer port, resulting in unpredictable behavior.

The LocalDirector 416 single-port Ethernet card and the LocalDirector 430 i82557 Ethernet card perform autonegotiation, but your network interface must support autodetection.


Note   The 4-port interface does not "autosense" to full duplex, causing a problem if the LocalDirector interface is at half duplex and is connected to a switch on the other end that is trying to connect at full duplex.


FDDI Interfaces

FDDI interface cards are optional on LocalDirector 430, and they cannot be mixed with Ethernet interfaces. FDDI interface cards support SMT 7.3.

An easy way to understand FDDI topology is to disregard the dual-attached interfaces. Treat dual-attached interfaces like single-attached interfaces; then treat FDDI like Ethernet; then the network topology looks like an Ethernet topology. Once the topology is determined, put the dual-attached interfaces back into the mix by keeping in mind that the dual-attached interfaces only provide topology redundancy—if a wire is cut, you have another wire to use as a backup. It does not mean you can attach additional servers because you have extra ports.

When installed in LocalDirector, port A is on the bottom of the interface, and port B is on the top as shown in .

Figure 2-6 LocalDirector FDDI Interfaces

FDDI interface boards for LocalDirector have dual-attached SC connectors as shown in .

Figure 2-7 LocalDirector FDDI Connectors

shows a LocalDirector failover implementation with FDDI interfaces.

Figure 2-8 LocalDirector Failover Implementation with FDDI


Note   The FDDI interfaces on the standby LocalDirector are active in the FDDI sense, but they do not pass load-balanced traffic unless the active LocalDirector fails.



hometocprevnextglossaryfeedbacksearchhelp

Posted: Wed Nov 10 22:59:10 PST 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.