3Com 09-0487-002 User Manual

LinkBuilder FDDI Workgroup Hub User Guide

LinkBuilder® FDDI Workgroup Hub

Release Note

1

User Guide

Release Note

Part No. 09-0487-002/October 1993

This release note to the 3Com
discusses the following topics:

■ Change in FCC compliance

■ Contents of the LinkBuilder diskette

■ Corrections in the User Guide

– Software-related
– Hardware-related

■ Replacing the fuse

Change in FCC Compliance

This notification of FCC compliance replaces the FCC compliance and
verification statements on page v of the LinkBuilder FDDI Workgroup Hub User
Guide. This notification acknowledges compliance with the limits for a Class A
digital device instead of a Class B digital device.

WARNING: This equipment has been tested and found to comply with the limits for a Class A digital device,
pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against
harmful interference in a commercial installation. This equipment generates, uses and can radiate radio
frequency energy and, if not installed and used in accordance with the instructions, may cause harmful
interference to radio communications. Operation of this equipment in a residential area is likely to cause
harmful interference, in which case, the user will be required to correct the interference at the user’s own
expense.

®

LinkBuilder® FDDI Workgroup Hub User Guide

Changes or modifications not expressly approved by 3Com could void the user’s authority to operate this
equipment.

Contents of the LinkBuilder Diskette

The diskette shipped with the LinkBuilder FDDI Workgroup Hub contains the
following:

■ Backup copy of LinkBuilder

■ Readme file

FDDI system software image, version 1.0

2

LinkBuilder FDDI Workgroup Hub User Guide

The system software has been preloaded into the hub management module flash
memory. Downloading the image to the FDDI Workgroup Hub disrupts the
ring. The download sequence isolates the hub from the ring during the power­on self-test (POST) and may cause the ring to wrap or to isolate attached
stations. Downloads impact the ring the least when the hub is attached to the
ring in a ring of trees configuration as a single attachment hub.

Corrections in the User Guide

The information provided in this section corrects software- and hardware-related
errors and omissions.

Software-Related Corrections

The corrections below are software corrections:

Release Note

Page 2-14: Check the Baud Rate Setting After

When the power-on self-test (POST) is run, the hub’s serial port output def aults
to 9600 baud regardless of the baud rate setting in nonvolatile RAM. If you
have set the console baud rate to other than 9600, you may need to adjust the
attached terminal baud rate after POST has finished. The default baud rate
setting is 9600.

Page 2-14: Removing Modules

The first two steps for removing modules as given in the User Guide should be
reversed. They should read:

1. Enter the disconnect command.

This disables all ports and isolates the hub from the ring.

2. Disconnect all cables connected to the module that you want to
remove.

If possible, you should always turn off the power before attempting to remove or
insert hardware.

Post

LinkBuilder FDDI Workgroup Hub User Guide

Release Note

3

Removing modules from the hub with the power on will not damage the
hardware. However, the software may not be able to distinguish between
intentional removal and catastrophic failure of a media module. As a result,
some errors will be entered in the fault log and in some cases may fill the fault
log entirely. The most common error resulting from the removal of a media
module is 05000002 (bus error). Other errors may also occur. Check the fault
log for valid errors before you remove any module. Also, clear the fault log
(using the clear log command) after all changes are complete and the syste m has
been reinitialized.

Pages 3-9, 3-10, and 3-11: Accessing the Primitive Console
Command Mode

The procedure for accessing the primitive console command mode has been
modified. To access the primitive console command mode:

1. Press the RESET button once, or enter the reset command.

During the subsequent power-on self-test (POST), the status LED flashes
amber/green for 10 seconds, indicating that the primitive console command
mode is being accessed.

2. Press the RESET button again.

POST is reinitialized. When POST is completed, this prompt appears for
10 seconds:

Press Ctrl-P to enter Primitive console

All other keys except [Ctrl] and [P] are ignored during this 10-second
interval.

3. Press [Ctrl] + [P].

The hub is now in the primitive console command mode.

If you do not access the primitive console command mode, POST executes the
system software resident in flash memory. Prior to execution of the system
software, POST verifies that flash memory is not corrupted. This process takes
about 20–30 seconds. During this time the status LED is off.