Guide to Operations

DOC-7016/1.0

CrossFire 8650/51

Guide to Operations

High-Speed Token-Ring UEM

CrossFire 8650/51 High-Speed Token-Ring UEM

Guide to Operations

ii

,

rks of

ce. e time

suant armful rates,

e

be

any

id his

TrademarksGoCard and the Olicom clasped hands logo are registered trademarks of Olicom A/S. CellDriverClearServer, ClearSession, ClearSight, CrossFire, LANscout, PowerMACH and RapidFire are trademarks of Olicom A/S. ClearCare, ClearPartner, ClearStep and ExpertWatch are service maOlicom A/S. Olicom is a registered trademark. Other brand and product names are trademarks, registered trademarks, service marks or registered service marks of their respective holders.

CopyrightsOlicom A/S reserves the right to modify the information given in this publication without prior notiThe warranty terms and conditions applicable for your purchase of this equipment are given at thof purchase. Please consult your place of purchase for details.

Publication: DOC-7016 v. 1.0, P/N: 710001605

© Copyright Olicom A/S, Denmark, July 1998

All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher.

FCC ComplianceThis equipment has been tested and found to comply with the limits for a Class A digital device, purto Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against hinterference when the equipment is operated in a commercial environment. This equipment geneuses and can radiate radio frequency energy and, if not installed and used in accordance with thinstruction manual, 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 required to correct the interference at his own expense.

Warning: This is a Class A product. In a domestic environment this product may cause radio interference in which case the user may be required to take adequate measures.

This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept interference received, including interference that may cause undesired operation.

Declaration of ConformityWe Olicom A/S

Nybrovej 114DK-2800 LyngbyDenmark

declare under our sole responsibility that the productsCrossFire 8650 High-Speed Token-Ring UEMCrossFire 8651 High-Speed Token-Ring UEM

to which this declaration relates are in conformity with the following standards or other normativedocuments

EN 50082-1EN 55022EN 60950 incl. amendments.EN 60825-1

following the provisions of 89/336/EEC Directive and 73/23/EEC Directive.

ModificationsIf the device is changed or modified without the express approval of Olicom A/S the user may voor her authority to operate the equipment.

CLASS 1 LASER PRODUCT

CrossFire 8650/51 High-Speed Token-Ring UEM v. 1.0, P/N: 710001605

iii

Table of Contents

1. Introduction 1

2. Installation 3Package Contents . . . . . . . . . . . . . . . . . . . . . . . . . 3Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . 3Physical Installation . . . . . . . . . . . . . . . . . . . . . . . . 4Software Installation . . . . . . . . . . . . . . . . . . . . . . . . 5

TFTP Download . . . . . . . . . . . . . . . . . . . . . . . . 6Serial Download . . . . . . . . . . . . . . . . . . . . . . . . 7

Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Power-On Self Test . . . . . . . . . . . . . . . . . . . . . . . . 9Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Default Configuration . . . . . . . . . . . . . . . . . . . . . 10

3. Console Configuration 11Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Ports, Port Groups and VLANs. . . . . . . . . . . . . . . . 12HSTR Virtual Ports and VLAN Tagging . . . . . . . . . . . 12Virtual Port Restriction . . . . . . . . . . . . . . . . . . . . 13Ring Number Restriction . . . . . . . . . . . . . . . . . . . 13

General Guidelines . . . . . . . . . . . . . . . . . . . . . . . . 14Navigating within the Menus . . . . . . . . . . . . . . . . . 15

Configuration Overview . . . . . . . . . . . . . . . . . . . . . 15VLAN Configuration . . . . . . . . . . . . . . . . . . . . . . . 16

BRF Configuration . . . . . . . . . . . . . . . . . . . . . . 16Local VLAN Port Configuration. . . . . . . . . . . . . . . . 17

Port Configuration - HSTR Ports . . . . . . . . . . . . . . . . . 18Virtual Port Configuration. . . . . . . . . . . . . . . . . . . . . 20

4. Statistics 23Statistics Menu . . . . . . . . . . . . . . . . . . . . . . . . . . 24Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Port Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

General Statistics. . . . . . . . . . . . . . . . . . . . . . . 27Virtual Port Statistics . . . . . . . . . . . . . . . . . . . . . 32802.5 MAC Information. . . . . . . . . . . . . . . . . . . . 33


iv

5. Getting in Touch with Technical Support 35Before You Contact Olicom Technical Support . . . . . . . . . . 35Hotline Support . . . . . . . . . . . . . . . . . . . . . . . . . . 35Fax Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Bulletin Board Service . . . . . . . . . . . . . . . . . . . . . . . 36

Standard Modem Requirements. . . . . . . . . . . . . . . . 36ISDN Modem . . . . . . . . . . . . . . . . . . . . . . . . . 36

Internet E-Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Anonymous Internet FTP Server . . . . . . . . . . . . . . . . . 37Internet World Wide Web Server (WWW) . . . . . . . . . . . . . 37Olicom Support WEB . . . . . . . . . . . . . . . . . . . . . . . 37Problem Report Form . . . . . . . . . . . . . . . . . . . . . . . 38

Appendix A. Abbreviations 41


v

List of Figures

Figure 1. CrossFire 8650 High-Speed Token-Ring UEM. . . . . . . . . 1Figure 2. Removing the Expansion Slot Cover . . . . . . . . . . . . . . 5Figure 3. Installing the CrossFire 865x module . . . . . . . . . . . . . 5

List of Tables

Table 1. LEDs at the Left on the Front Panel. . . . . . . . . . . . . . . 8Table 2. LEDs at the Right of Every Port . . . . . . . . . . . . . . . . . 9Table 3. HSTR Port Configuration: Status Values . . . . . . . . . . . 18Table 4. Virtual Port Configuration: Status Values . . . . . . . . . . . 20Table 5. Virtual Port Configuration: Maximum Frame Size . . . . . . . 21Table 6. Config Loss Values . . . . . . . . . . . . . . . . . . . . . . 28


vi

this

h-M

e

other

Summary of Contents

Following is a short description of the content of the chapters and appendixes inpublication:

Chapter 1, “Introduction” , is a general introduction to the CrossFire 8650 HigSpeed Token-Ring UEM and the CrossFire 8651 High-Speed Token-Ring UE(CrossFire 865x module refers to both of these module types).

Chapter 2, “Installation” , lists the CrossFire 865x module package contents, explains module installation and cabling, describes the front panel LEDs, andexplains configuration and testing of the module.

Chapter 3, “Console Configuration”, deals with setting up and configuring theCrossFire 865x module using a direct console connection.

Chapter 4, “Statistics”, lists and explains the statistics that are available for thCrossFire 865x module.

Chapter 5, “Getting in Touch with Technical Support”, lists Olicom’s support services such as hotline support, fax support and the support web, as well asservices such as the bulletin board service, FTP server and e-mail.

Appendix A, “Abbreviations” contains a list of the abbreviations used in this publication.

❏


1

s

ing

dule e

SC

ps

port

a

and the

1. IntroductionThe CrossFire 8650 and CrossFire 8651 2-port High-Speed Token-Ring UEMfrom Olicom provide connectivity to 100 Mbps High-Speed Token-Ring for theCrossFire 8600 Token-Ring Switch. Designed for high performance and low latency, these modules provide seamless integration between legacy Token-Rnetworks and a HSTR backbone.

The CrossFire 865x module mounts in one of the two front panel expansion moslots on the CrossFire 8600 Token-Ring Switch. Two versions of the CrossFir865x module are available—one for UTP-5 copper with a RJ-45 connector interface (CrossFire 8650), and one for multimode optical fiber with a duplex connector (CrossFire 8651).

Figure 1. CrossFire 8650 High-Speed Token-Ring UEM

The CrossFire 865x module conforms to the IEEE 802.5t standard for 100 MbHigh-Speed Token-Ring, and implements the standard DTR MAC protocol.

A HSTR port can connect to a standard HSTR adapter or it can act as a trunkand carry traffic from all possible 63 VLANs configured in the switch. This is achieved using standard IEEE 802.1Q VLAN frame tagging. For each VLAN virtual port is created, which behaves much like an ordinary Token-Ring port.

The CrossFire 865x module enables standard Token-Ring source routing andsupports all the switching modes implemented in the switch.

Six LEDs on the front panel indicate the overall operational state of the modulethe two ports. Configuration and detailed status information is available from switch console or from the graphical management application.

CrossFire 8650/51 High-Speed Token-Ring UEM v. 1.0, P/N: 710001605 Introduction

2

❏

CrossFire 8650/51 High-Speed Token-Ring UEM v. 1.0, P/N: 710001605 Introduction

3

the

s

s

elf oth

, the

s

tch

2. InstallationThis chapter contains instructions for installing, connecting and starting to useCrossFire 865x module. The following main topics are covered:

• Package Contents

• Installation Procedure

• Cabling

• LEDs

• Power-On Self Test

• Configuration

Package ContentsYour CrossFire 865x module package contains the following items:

• One CrossFire 8650 2-port High-Speed Token-Ring UEM (UTP)ORone CrossFire 8651 2-port High-Speed Token-Ring UEM (MMF).

• One OC-8830 Token-Ring Switch Program disk set.

• One OC-8840 Token-Ring Switch Manager for HP OpenView for Windowdisk set.

• One Cross Fire 8650/51 High-Speed Token-Ring UEM Guide to Operation (this manual).

Installation ProcedureThe CrossFire 865x module is packaged with software for both the module itsand the CrossFire 8600 Token-Ring Switch. The switch is also supplied with bsoftware images. To ensure compatibility between the module and the switchlatest of the two software revisions should be installed.

The switch and CrossFire 865x module software is also available via Olicom’online services, for example on the Internet.

Install the CrossFire 865x module, as follows:

1. Install the software in the CrossFire 8600 Token-Ring Switch. See the swimanual for instructions on downloading the software.

CrossFire 8650/51 High-Speed Token-Ring UEM v. 1.0, P/N: 710001605 Installation

4

lots.

are

ction

the

y

600

tlet. lug

65x

the 2 oved.

2. Optionally, clear the NVRAM in the base switch. This will erase all configuration in the switch.

3. Reset the switch to activate the new software.

4. If the NVRAM was cleared in step 2, re-establish the switch configuration.Verify that the switch is operating correctly.

5. Turn off the switch.

6. Physically install the CrossFire 865x module in one of the two expansion sSee section “Physical Installation” below for detailed instructions.

7. Turn on the switch.

8. Download the software for the CrossFire 865x module. See section “SoftwInstallation” below for detailed instructions.

9. If you plan to use the graphical switch manager application, install it now.

10. If necessary, configure the CrossFire 865x module. For details, see the se“Configuration” below as well as Chapter 3, “ Console Configuration”.

➽ Warning: Be sure to install a version of the base switch software that supportsCrossFire 865x module (version 3.00 or later) before physically inserting the CrossFire 865x module. Otherwise, the switch will not recognize it and this main some cases corrupt the configuration.

Physical InstallationUse the following steps to install the CrossFire 865x module in a CrossFire 8Token-Ring Switch:

1. Power off the base switch by unplugging the power cord from the power ouIf the switch uses the optional CrossFire 8311 Redundant Power Unit, unpthe connector from the base switch as well.

2. Select an empty expansion module slot in which to install the CrossFire 8module. You can install the module in either or both of the slots.

3. Remove the blind plate covering the expansion module slot on the front ofCrossFire 8600 by loosening the two retaining thumb screws. See Figure below. Keep the plate for use in the event that the expansion module is rem


5

the

e into le is tch.

Fire

with

Figure 2. Removing the Expansion Slot Cover

➽ Warning: Expansion modules are not hot-swappable. If you install or remove expansion modules while the power to the switch is on, damage may occur toswitch and to the module.

4. Carefully insert the CrossFire 865x module into the rails on each side of thexpansion slot, sliding it back until the connector on the module is seated the connector at the back of the slot. See Figure 3 below. When the modufully seated, the module faceplate will be flush with the front of the base swi

Figure 3. Installing the CrossFire 865x module

5. Secure the CrossFire 865x module with the two attached thumb screws.

6. Reapply power to the CrossFire 8600.

Software InstallationBefore you can use your CrossFire 865x module, you have to install the Cross865x module software image. The software image can be downloaded to the CrossFire 865x module via TFTP or via a serial line. Search the disks suppliedthe module for a file named 865Xyyzz.BIN. The letters yyzz in the file name represent the version number of the software. For example, 865X0312.BIN is version 3.12 of the software image.

ERRDIAG

ACTIVITY1 2

HIGH-SPEED TOKEN-RING

LINK


6

ad

d

TFTP Download1. Copy the software image to a suitable directory on the TFTP server.

2. From the main menu in the console, select Download/Upload . The Download/Upload menu will be displayed.

3. Select TFTP Download/Upload . The TFTP Download/Upload menu will be displayed:

4. On this menu, set the IP address of the TFTP server. Also, set the downloVLAN (the BRF on which the TFTP server is located).

5. Select HSTR Firmware Download . The HSTR Firmware TFTP Download screen is displayed.

6. Select HSTR Firmware Download Filename and type the filename of the software image to download.

7. Select Execute HSTR Image Network Download to start the download.

The console will display the download activity while the software is transferreover the network. When the software has been transferred, you will see the following messages:

Network download complete. Now transferring to HSTR Module(s), please wait...

Download of HSTR firmware complete – HSTR module(s) being reinitialized...


7

Fire the nd

65x

Fire

u are

ngth

nto

r

e ”

The software image is then programmed into the FLASH memory on the Cross865x module. The software image remains in memory until it is replaced. Whensoftware installation is complete, the module is started for normal operation, athe following message is displayed:

Press <RETURN> to continue...

Serial Download1. From the main menu, select Download/Upload . The Download/

Upload menu is displayed.

2. Select Serial Link Download . The Serial Link Download screen is displayed.

3. Select HSTR Firmware Download .

4. Using your terminal software, transfer the software image to the CrossFire 8module with the X-Modem protocol. The transfer will take some minutes depending on your terminal emulator baud rate.

The software image is then programmed into the FLASH memory of the Cross865x module, and will remain there until it is replaced. When the software installation is complete, the module is started for normal operation, and the following message is displayed:

Press <RETURN> to continue...

CablingThe cabling used depends on which version of the CrossFire 865x module yoinstalling.

CrossFire 8650 2-port High-Speed Token-Ring UEM (UTP)The UTP module uses standard UTP-5 copper cables. The maximum cable leis 100 m (328 feet).

1. Insert the modular RJ-45 jack from either end of a standard UTP-5 cable ione of the connectors on the CrossFire 865x module front panel.

2. Connect the other end of the cable to either another HSTR switch port (foexample, another CrossFire 865x module) or an HSTR adapter.

3. If the default Auto port mode is in effect, the port will automatically open in thappropriate Port or Station mode. Refer to Chapter 3, “Console Configurationfor details on port mode configuration.


8

m

nt clean

r X to

e ”

. ate

CrossFire 8651 2-port High-Speed Token-Ring UEM (MMF)The MMF module uses multimode 62.5/125 micron fiber cables. The maximucable length is 2000 m (6560 feet).

1. Connect a SC-type optic fiber to the pair of SC-type connectors on the fropanel of the module. To ensure proper connection, it may be necessary to the fiber connectors with a soft tissue dipped in alcohol.

2. Connect the other end of the cable to either another HSTR switch port (foexample, another CrossFire 865x module) or an HSTR adapter. Connect RTX and TX to RX. If there is no connection it is safe to try swapping the RXand TX connectors at one end of the cable.

3. If the default Auto port mode is in effect, the port will automatically open in thappropriate Port or Station mode. Refer to Chapter 3, “Console Configurationfor details on port mode configuration.

LEDsThere are a total of six LEDs on the front panel of the CrossFire 865x moduleDuring normal operation, the two LEDs on the left side of the front panel indicthe module status:

LED Position State Meaning

DIAG (green) Top On Diagnostics are in process.

Off No diagnostics are in process.

ERR (yellow) Bottom On A module failure has occurred.

Off The module is working correctly.

Table 1. LEDs at the Left on the Front Panel


9

self will em.

s

e

tor

The two LEDs on the right of every port indicate the port status:

Table 2. LEDs at the Right of Every Port

Note that the ACTIVITY LED does not flash for MAC frames.

Power-On Self TestWhen the CrossFire 8600 Token-Ring Switch is booted, it will run a power-on test to ensure that all devices are working correctly. During this test, the switchdetect the CrossFire 865x modules in the expansion slots, if any, and boot th

The CrossFire 865x module will then perform an internal power-on self test. During the entire test, the DIAG and ERR LEDs will be lit while the other LEDmay turn on and off.

When the test is completed, after a few minutes, the DIAG and ERR LEDs arturned off and the CrossFire 865x module enters its normal operational state,providing no problems were found.

If a problem was detected, only the DIAG LED will turn off. Messages in the message log or on the console will indicate what the problem is.

ConfigurationThe CrossFire 865x module can be configured in two ways, either

• from the switch console, via Telnet or directly with a VT100 terminal emulaon the RS-232 port

or

• by the SNMP based graphical management application OC-8840.

LED Position State Meaning

LINK (green) Top On The port has link and is inserted.

Flashing The port is disabled.

Off The port is not inserted.

ACTIVITY (green)

Bottom Flashing The port is receiving and/or transmitting LLC frames.

Off Currently no LLC traffic on the port.


10

e

865x

he

ime,

TR ,

Console configuration is described in Chapter 3, “Console Configuration”. Thmanagement application is described in the online help.

All configuration parameters are stored by the switch and not by the CrossFire module. This means that CrossFire 865x modules can be exchanged withoutreconfiguring the switch.

Note, however, that the CrossFire 865x module software image is stored on tCrossFire 865x module itself and will follow the module when it is moved to another switch.

Default ConfigurationWhen a CrossFire 865x module is inserted into an expansion slot for the first tthe switch will generate a default configuration, as described below:

• Both HSTR ports are enabled.

• Both HSTR ports are set to Auto mode.

• Both HSTR ports have a single virtual port in the default CRF.

This configuration is suitable for connecting both HSTR adapters and other HSswitch ports to the default CRF. If more advanced configurations are requiredplease refer to the configuration chapter for details.

❏


11

65x 00

ork 8600

3. Console ConfigurationThis chapter explains how to view and edit the configuration of the CrossFire 8module using a VT100 terminal emulator attached directly to the CrossFire 86Token-Ring switch. The CrossFire 865x module configuration can also be modified from a remote VT100 console via a Telnet session. Connecting a netwmanagement console is explained in the manual supplied with the CrossFire Token-Ring Switch.

The following topics are explained in this chapter:

• Introduction

• General Guidelines

• VLAN Configuration

• Port Configuration—HSTR Ports

• Virtual Port Configuration

For more information on configuration, please see the CrossFire 8600 Token-Ring Switch Guide to Operations.

CrossFire 8650/51 High-Speed Token-Ring UEM v. 1.0, P/N: 710001605 Console Configuration

12

n- the x and ken-

e

s

hich

y re

idge

rent ted itched.

rcrf- is not be

t the an

IntroductionEach CrossFire 865x module has two 100 Mbit/s HSTR ports. In the console configuration, port numbers are used to refer to ports, with the ordinary TokeRing ports being numbered 1 to 20. If a CrossFire 865x module is inserted inleft expansion slot, the HSTR ports are number 21 and 22. If a CrossFire 865module is inserted in the right expansion slot, the HSTR ports are number 2526. Any number of CrossFire 865x modules may be inserted into a stack of ToRing switches.

The HSTR ports are configured much like ordinary Token-Ring ports, and generally appear in all tables where the ordinary Token-Ring ports appear.

Ports, Port Groups and VLANsThis section briefly describes the VLAN concept and switching modes of the CrossFire 8600 Token-Ring Switch. For more detailed information about thessubjects, please refer to the CrossFire 8600 Token-Ring Switch Guide to Operations.

The CrossFire 8600 Token-Ring Switch supports up to 63 VLANs. A VLAN forma single bridged domain and the visibility of MAC addresses, bridge and ring numbers as well as the scope of broadcast frames are limited to the VLAN in wthey origin. Frames must be routed to move between VLANs.

A VLAN consists of a number of port groups called CRFs (Concentrator RelaFunction). A CRF is conceptually equal to a ring. If a VLAN contains two or moCRFs they are conceptually connected by a multiport bridge called a BRF (BrRelay Function).

The BRF performs either source-route bridging (SRB) or source-route transpaswitching (SRT) between the CRFs depending on the CRF configuration. TheCRFs configured for SRT switching forms a SRT domain, in which source-rouframes are source routed and non-source-routed frames are transparently sw

Each ordinary Token-Ring port is assigned to a specific CRF, which also determines which VLAN it belongs to.

In the default configuration, all ordinary Token-Ring ports are assigned to the tdefault CRF, which belongs to the trbrf-default BRF. The only limitations to thisthat the names cannot be changed and the parent BRF of the default CRF canchanged.

HSTR Virtual Ports and VLAN TaggingThe HSTR ports behave much like ordinary Token-Ring ports. They implemenDTR TXI MAC layer protocol as specified in the IEEE 802.5t specification and c


13

he

can

TR

t

ly one is ual

ent

m

ort es

me stand

be configured for Port, Station or Auto sensing modes. Also, before a port is inserted, the MAC layer protocol must complete the lobe test, which verifies tcable connection.

As a significant difference from the ordinary Token-Ring ports, however, the HSTR ports has the capability to function as trunk ports, which means that theycarry traffic belonging to all possible 63 VLANs over the same physical cable connection.

Frames from different VLANs are distinguished by means of standard IEEE 802.1Q frame tags. A frame tag consists of an 8 byte SNAP protocol header followed by a 2 byte Tag Control Information (TCI) field. It is inserted in the Token-Ring frame after the route information field before transmission on HSand subsequently recognized and removed when the frame is received.

The TCI field identifies which VLAN the frame belongs to by means of a 12 biVLAN identifier. This VLAN identifier uniquely identifies the BRF. It also contains a 3 bit priority field, which is described below in section “Virtual Port Configuration” under subsection “FC Modification”.

Each HSTR port can be assigned to several CRFs, however, there can be onper BRF/VLAN. A virtual port is created for each CRF to which the HSTR portassigned. All virtual ports but one must be tagged, in other words a single virtport can be left untagged.

Note that a HSTR port with a single untagged virtual port is functionally equivalto an ordinary Token-Ring port. This is also the default configuration, with thevirtual port in trcrf-default.

Virtual Port RestrictionA HSTR port can only have one virtual port in each VLAN. This follows from the nature of VLAN tagging. It would not be possible to distinguish frames frotwo virtual ports in the same VLAN, since they would have the same VLAN identifier.

Ring Number RestrictionAll CRFs that a HSTR port has virtual ports in must have the same ring number. Thus, the ring number is a per port parameter and not a per virtual pparameter. This convention will also be implemented by Olicom HSTR switchand is expected to be adopted by IEEE. To see the importance of this, pleaseconsider the implication of not having this restriction. If it was not in effect, the meaning of the RIF would be ambiguous and depend on to which VLAN the frawas sent. It would thus be incomprehensible to equipment that does not underVLAN tags.


14

rtual

ing

e

en.

on

lay,

0.

return

will ster

s of e

This also means that when the HSTR module learns a ring number on one viport, it will automatically take effect on all the other virtual ports.

When a virtual port is created in a VLAN this restriction might in some cases require that a new CRF must be created in order to avoid changing existing rnumbers.

General GuidelinesTo work within the console menus, follow these guidelines:

• To select a menu item, use the arrow keys to move the “highlight” over thselection, then press Enter.

• If you need to specify additional information for any item—for example, selecting “Yes” or “No” or supplying a value—a prompt appears on the screIf you want to exit the prompt without changing the value, press Esc.

• In most cases, new values are saved when you select Return .

• The term “More” means there is more information than what is displayed that screen. Selecting More and pressing Enter.

• displays the next screen of information. If the screen is a one-screen dispselecting More will update the screen.

• The term “Port” refers to the number of a specific port on a CrossFire 860

• “Index” refers to the numerical order of a list.

• To return to the main menu from any screen within the menus, press Ctrl-P. Note that any changes made to the screen you were in are not saved. To to the greeting screen, press Ctrl-B from any screen.

• To refresh the console panel at any time, press Ctrl-L.

• To clear all queued messages, press Ctrl-D. The messages will still be in the message log.

• If you are administering switches in a stack, many of the console screensprompt for a box number. Enter the number of the box you want to adminito continue. The box that you are physically connected to is highlighted.

• The console automatically returns to the greeting screen after five minuteinactivity. Five minutes is the default value. The time can be changed at thConsole Configuration menu. The Console Configuration menu is within the Configuration menu, under the main menu.


15

n ting

r a

a

e way.

t in

e n”

• For protection against inadvertent or unauthorized access to configuratioscreens, you can establish a password that users must enter at the Greescreen. If no password is configured, just press Enter and the main menu is presented.

Navigating within the MenusUse the arrow keys (also referred to as cursor keys) to move the highlight oveselection. If the selection is a menu, pressing the Enter key displays a new screen ofinformation; if the selection is a command, such as Reset , pressing the Enter key initiates that function.

A heading with three “dots” after it means that when that heading is selected,submenu or screen is displayed.

Unless specified differently, all the screens or menus are accessed in the sam

Configuration OverviewExecute the following general steps to configure a CrossFire 865x module:

• Determine which VLANs the HSTR ports should connect.

• Determine which VLAN, if any, should be untagged.

• Configure the HSTR VLAN ID for all the BRFs that should be tagged.

• Make sure that each HSTR VLAN ID matches that of the HSTR equipmenthe other end.

• Assign CRFs to the HSTR port, thereby creating one virtual port in each VLAN. Possibly create new CRFs to make sure that the CRFs do not havconflicting ring numbers, as discussed in section “Ring Number Restrictioabove.

• Configure the HSTR port, in particular the operation mode.

• Configure the virtual ports, in particular the tagging mode. The relevant configuration menus are described in detail in the following sections.


16

. It

is s and e

VLAN ConfigurationFor general information about the configuration of VLANs, please refer to theCrossFire 8600 Token-Ring Switch Guide to Operations. Only issues relating to theconfiguration of HSTR ports are described here.

BRF ConfigurationAn additional parameter HSTR VLAN ID has been added to the BRF configuration:

The HSTR VLAN ID is the value that is inserted in the IEEE 802.1Q frame tagsis entered as a decimal value between 1 and 4094.

The HSTR VLAN ID should not be confused with the existing VLAN ID, which a number chosen by the user and used by the Token-Ring switch to index CRFBRFs. By default, however, the HSTR VLAN ID is set to the same value as thVLAN ID.


17

e

Local VLAN Port ConfigurationThe HSTR ports will appear as trunk ports in the Local VLAN Port Configuration . This means that more than one CRF can be assigned to thHSTR ports. Note, however, the virtual port restriction described above.


18

n the en

ing:

Port Configuration - HSTR PortsTo configure a HSTR port on the CrossFire 865x module, select Port Configuration from the Configuration menu and enter the port numberof the HSTR port (21, 22, 25 or 26). The following menu appears:

The following items are shown:

EnabledSets the administrative state of the port, possible values are Yes and No. Wheport is disabled, the LINK LED will blink. This is also the case, if the port has beauto-disabled, see sections “Cfg Loss Threshold” and ““Cfg Loss Sampling Interval“ below.

The default value is Yes.

StatusInformation only. Shows the current status of the port. Can be one of the follow

Value Meaning

Disabled The port has been autodisabled.

Down The port has been disabled and the MAC protocol is disconnected.

Table 3. HSTR Port Configuration: Status Values


19

other can

FDX

le s a e or

for

es are

Operation ModeSets the operation mode of the port, possible configured values are FDX port, FDX station and Auto. On a HSTR connection, one end must be a FDX port and the a FDX station. A HSTR adapter is always a FDX station, whereas a switch portbe both. The Auto mode will attempt to detect the port mode automatically byswitching between the two modes with a period of a few seconds.

When the port connects in the Auto mode, the detected mode is shown as A-port or A-FDX station.

The default value is Auto.

Cfg Loss ThresholdSets the number of configuration losses before the port auto-disables. Possibvalues are 0 to 100, with 0 disabling this feature. The MAC protocol generateconfiguration loss in case of lobe test failure, heartbeat failure, address changother MAC protocol error.

The default value is 8.

Cfg Loss Sampling IntervalSets the sampling interval in which the Cfg Loss threshold must be exceededthe port to autodisable. Possible values are 1 to 60 minutes.

The default value is 1.

Address Demand Aging LevelSets the threshold on the number of entries in the address table on which entriaged faster. Possible values are 50, 60, 70, 80 and 90 percent and Disabled.

Going Up The port is enabled and the MAC protocol is trying to connect.

Up The port is up and the MAC protocol has connected.

Going Down The port has been disabled and the MAC protocol is disconnecting.

Temporary Down The MAC protocol has disconnected, but is actively trying to connect again. The disconnect reason might be a wire fault or configuration change.

Value Meaning

Table 3. HSTR Port Configuration: Status Values


20

ainly

s ears:

he

The default value is 90 percent.

Trace MaskSets a bit mask for which messages are logged in the message log. This is mfor debugging purposes by Olicom support.

Virtual Port ConfigurationTo configure a virtual port on a HSTR port select Virtual Port Configuration on the Port Configuration menu of the HSTR port. If the HSTR port has more than one virtual port, a list of the corresponding CRFappears from which the virtual port must be selected. The following menu app

EnabledSets the administrative state of the virtual port, possible values are Yes and No. The default value is Yes.

StatusInformation only. Shows the current status of the virtual port. Can be one of tfollowing:

Value Meaning

Admin down The port or virtual port is disabled.

Table 4. Virtual Port Configuration: Status Values


21

472, on the ard

e n:

d.

MTUSets the maximum frame size for the virtual port, possible values are 1500, 48144, 17800, and Auto. These values correspond to the standard values usedordinary Token-Ring ports. Actually, slightly larger frame sizes are allowed toaccommodate the frame sizes defined by the ATM Forum LAN Emulation standand implemented by the CrossFire 832x ATM Uplink. Also, the IEEE 802.1Q frame tag adds another 10 bytes to each frame.

The following table shows the configured and actual frame size, as well as thcorresponding Largest Frame Size bits that are used in explorer RIF expansio

Also shown is the MTU for the BRF. If Auto is selected, the BRF value will beused. Otherwise, the lowest of the BRF MTU and port MTU values will be useThus, a port will never have a higher MTU than its BRF.

By default, the MTU is set to Auto.

Waiting for port up The virtual port is waiting for the port to come up.

Up The virtual port is up but not forwarding.

Forwarding The virtual port is up and forwarding.

Temporary down The virtual port is currently down because the port is temporary down.

MTU configured Actual HSTR frame size LF bits

1500 1558 001

4472 4556 011

8144 9246 100

17800 18202 110

Table 5. Virtual Port Configuration: Maximum Frame Size

Value Meaning

Table 4. Virtual Port Configuration: Status Values


22

sec or ed

nd t can ust

ing.

alues ins a in ot

the

s the Fire t

re 1 to dress

Max Explorer RateSets the maximum explorer frame rate, possible values are 0 to 5000 frames/Disabled. If enabled, this will limit the amount of explorer frames being forwardfrom the HSTR side of the virtual port to the switch.

The default value is Disabled.

VLAN Tagging ModeSets the VLAN tagging mode of the virtual port, possible values are Tagged aUntagged. As explained previously at most one virtual port on each HSTR porbe untagged. All other virtual ports must be tagged and the HSTR VLAN ID mbe the same in both ends.

Preferably, the VLAN which is expected to have the largest amount of traffic should be untagged, since VLAN tagging does impose a small overhead.

The default value is Untagged for the first virtual port and Tagged for the follow

FC ModificationEnables or disables FC modification when a frame tag is removed, possible vare Enabled and Disabled. As discussed earlier a VLAN frame tag also conta3 bit priority field. If FC modification is enabled, the Token-Ring frame priority the FC byte is overwritten with the frame tag priority, if the frame tag priority is nequal to zero. If FC modification is disabled, the FC priority is left as it is, and frame tag priority is discarded.

When the CrossFire 865x module inserts a frame tag in a frame, it always useFC priority as the frame tag priority, so for frames received from another Cross865x module, this option makes no difference. Other devices, however, mighrequire that the frame tag priority should take precedence, in which case FC modification should be enabled.

The default value is Disabled.

Address Aging TimeSets the aging time for addresses learned on an HSTR port. Possible value a9999 minutes or 0 to disable aging. When there has been no activity on an adfor the specified period of time it is deleted from the address tables.

The default value is 5 minutes.

❏


23

ch.

4. StatisticsA wide range of statistics is available for the CrossFire 8600 Token-Ring SwitThe following topics are discussed in this chapter:

• Statistics Menu

• Port Status

• Port Statistics

• General Statistics

• Virtual Port Statistics

• 802.5 MAC Information

CrossFire 8650/51 High-Speed Token-Ring UEM v. 1.0, P/N: 710001605 Statistics

24

rs:

e u

for

he

he

Statistics MenuWhen Statistics is selected from the main menu, the following menu appea

The menu items in the Statistics menu are all described in the manual for thCrossFire 8600 Token-Ring Switch. For general information about these menitems, please refer to that manual.

However, some of the menu items contain additional information that is specificthe CrossFire 865x module:

• Port Status —The CrossFire 865x module virtual ports are included in tport overview.

• Port Statistics —contains additional counters for HSTR ports.

• Address Tables —also contains addresses learned from HSTR ports.

• Message Log Information —also contains messages generated by tCrossFire 865x module.


25

STR

, 25

s not rt is ls.

ule n a

Port StatusWhen Port Status is selected on the Statistics menu, a table similar to the following appears:

Besides the ordinary Token-Ring ports, the table contains an entry for each Hvirtual port, along with its current status. The following items are displayed:

PortThe HSTR port for which the virtual port is defined. Possible values are: 21, 22and 26.

TrCRFThe name of the CRF in which the virtual port is defined.

TrBRFThe name of the BRF in which the virtual port is defined.

Enabled/InsFor ordinary Token-Ring ports, this is the enabled and inserted status. This doeapply to virtual ports on a HSTR port. Instead the current state of the virtual podisplayed. Please refer to the description of virtual port configuration for detai

SpdThe connect speed in Mbps, which is always displayed as 100 for HSTR modvirtual ports. Note that 100 Mbps full-duplex is the total bandwidth available o


26

idth al

is

HSTR port and is shared by all the virtual ports on that port. The actual bandwon a particular virtual port thus depends on the amount of traffic on other virtuports.

Oper ModeThe operation mode is always displayed as HSTR VLAN for virtual ports.

Fwd ModeThe forwarding mode is always displayed as Store-Fwd, since the CrossFire 865xmodule always operate in the store-and-forward switching mode.

Port StatisticsWhen Port Statistics is selected and the port number of a HSTR port entered, the following menu appears:

The available information is discussed in the following sections.


27

ts.

r is or t

General StatisticsWhen General Statistics is selected on the Port Statistics menu the following screen appears:

The screen shows the number of frames and bytes received, forwarded and transmitted on the HSTR port. These numbers include traffic for all virtual porThe screen will automatically update itself every 5 seconds.

Frame and Byte CountersThe following frame and byte counters are defined:

• ReceivedFrames received from HSTR, but not necessarily forwarded.

• ForwardedFrames received from HSTR and forwarded to other ports in the switch.

• TransmittedFrames transmitted to HSTR.

• FramesThe number of LLC frames received, forwarded or transmitted. The numbesubdivided into the NSR, SRF, STE and ARE frames, explained below. Freceived frames it is also subdivided into unicast, broadcast and multicasframes, explained below.


28

tes unt

e is

nt apter

• BytesThe total number of bytes in the LLC frames. The byte count includes all byfrom AC up to and including the FCS field. Note that the forwarded byte cocan be lower than the received byte count even though all frames are forwarded. This is because the VLAN frame tag is removed before a framforwarded.

• NSR FramesNumber of Non-Source Routed frames.

• SRF FramesNumber of Specifically Routed Frames.

• STE FramesNumber of Spanning Tree Explorers.

• ARE FramesNumber of All-Routes Explorers.

• MAC FramesNumber of MAC frames.

• Unicast FramesNumber of frames with a unicast MAC address as destination.

• Broadcast FramesNumber of frames with a Token-Ring broadcast address as destination.

• Multicast FramesNumber of frames with a Token-Ring functional or group address as destination.

Config LossThe Config Loss counter shows the number of config losses within the curreinterval. The config loss threshold and interval parameters are described in Ch3, “Console Configuration”. The Config Loss Reason can be one of these:

Wire Fault The port was closed due to a wire fault, perhaps because the cable was removed.

Lobe Test Fail The lobe test failed during the recovery after a beacon condition.

Heart Beat The port was closed after a failure of the heartbeat function.

Table 6. Config Loss Values


29

. The

s are

ResetWhen Reset is chosen, all frame, byte and discarded frame counters are resettime since last reset is shown on the screen.

Discarded FramesWhen Discarded Frames is chosen on the general statistics display, the following screen appears:

The screen shows the number of frames discarded on the HSTR port in bothinbound (from HSTR) and outbound (to HSTR) directions. The discard reasondescribed below.

Discarded Inbound FramesThe following discard reasons are defined for inbound frames:

TXI New Station The port was closed after receiving a MAC frame with a source address different from the stored Upstream Neighbor address.

TXI Protocol The port was closed due to a MAC TXI protocol error.

None The port has never failed.

Table 6. Config Loss Values


30

d

d

he e is gth

s g. ld. ys

last rer

his

rame a

ured e

the g

er.

• Invalid VLANA frame was received on an unknown VLAN. This is either a VLAN taggeframe containing an unknown VLAN ID, or an untagged frame when no untagged virtual ports are defined. Make sure that the HSTR VLAN ID anvirtual port tagging mode is set to the same value on both sides of the connection.

• Invalid RouteA frame with an invalid Route Information Field (RIF) was received. Either tRIF length is odd or zero, the frame too small to contain the RIF, the framan explorer frame with a backward RIF or is a non-explorer with a RIF lenof 4.

• Invalid VLAN Tag CFIA VLAN tagged frame with an invalid Canonical Format Indicator (CFI) wareceived. The CFI is a bit in the Tag Control Information field of a VLAN taThis bit indicates the bit order of any MAC addresses in the information fieIt is 0 for Ethernet format and 1 for Token-Ring format. It should thus alwabe 1 in received frames.

• Ring Number MismatchIn explorer frames, the ring number of the HSTR port should always be thering number in the RIF if the RIF length is larger than 2, and in non-explosource routed frames the HSTR port ring number should always appear somewhere in the RIF. It this is not the case, the frame is discarded and tcounter is incremented.

• Duplicate Ring NumberA source routed frame is discarded and this counter incremented when a fcontains the HSTR port ring number more than once. This could indicateloop in the spanning tree.

• Frame Too LargeThe frame is larger than the maximum frame size, which has been configfor the virtual port. Please refer to the table of maximum frame sizes in thdescription of virtual port configuration.

• Route Descriptor Too LargeThe frame is an explorer frame and the RIF length would exceed the configured maximum hop count limit if more hops were added. Thereforeframe is only forwarded to the other ports in the same ring as the receivinvirtual port.

• Filtered By Address FilterThe frame is discarded because of a MAC address filter.

• Filtered By DSAP FilterThe frame is discarded because of a protocol (DSAP or protocol type) filt


31

ion e

rror

rottle

nning logy

s the

bers bers RF

.

ove.

e)

ured pter

• CRF MismatchThe frame is discarded because the destination MAC address or destinatsource route hop is registered as local for the virtual port. That is, the framwould have to be forwarded back to same port. This might be due to an ein the configured HSTR VLAN ID for one or more VLANs.

• Explorer OverflowThe frame is an explorer frame and was discarded because the explorer thlimit has been exceeded.

• Blocked Virtual PortThe frame has been discarded because the virtual port is currently not inforwarding state. The blocked state may be permanent, because the spatree protocol has detected multiple parallel paths or transient during topochanges of the network.

Discarded Outbound FramesThe following discard reasons are defined for outbound frames:

• Invalid Frame Header TagA frame could not be transmitted because it has an invalid internal frame header tag (note that this internal frame header tag is not the same thing aVLAN tag).

• Unknown Ring NumberAn explorer frame could not be transmitted because one or two ring numare required for the RIF expansion and at least one of the required ring numis currently unknown. The ring number must either be configured for the Cor learned from an incoming explorer frame.

• Inactive Virtual PortThe frame is not transmitted because the virtual port is currently disabled

• Blocked Virtual PortThe frame is not transmitted because the virtual port is currently not in forwarding state. Refer to the comments for discarded inbound frames ab

• Filtered By DSAP FilterThe frame is not transmitted because of a protocol (DSAP or protocol typfilter.

• Frame Too LargeThe frame is larger than the maximum frame size, which has been configfor the virtual port. Please refer to the table of maximum frame sizes in Cha3 in the section “Virtual Port Configuration”.


32

port

ther

n is X

ted ng

ort

• Invalid RouteAn explorer frame is not transmitted because the ring number of the HSTRappears earlier than the last ring number in the RIF.

Note that for the following three error conditions the frame is not dropped but rathe transmission is aborted:

• Unknown Ring Number

• Frame Too Large

• Invalid Route

This is because transmission has already begun at the time the error conditiodetected. The receiver in the other end will therefore count these frames as Taborts.

Virtual Port StatisticsWhen Virtual Port Statistics is selected from the Port Statistics menu for an HSTR port some counters for the virtual ports are displayed. If more than one virtual port is defined for the HSTR port the requesvirtual port must first be selected by choosing from a list of CRFs. The followiscreen then appears:

The following items are displayed:

Virtual Port StateThis is the current state of the virtual port. Refer to Chapter 3, section “Virtual P


33

tual

ing s

Configuration” for details.

Frames ForwardedThe number of LLC frames received and forwarded on this virtual port.

Frames TransmittedThe number of LLC frame transmitted on this virtual port.

Frames ReceivedThe number of LLC frames received, but not necessarily forwarded on this virport.

ResetAlso shown is the time since the last reset of these counters. Select Reset to reset the counters on this screen.

802.5 MAC InformationThe following menu items in the Port Statistics menu for a HSTR port contain information about the Token-Ring MAC layer protocol:

• 802.5 Statistics

• 802.5 State

• 802.5 DTR MAC Information

The information in these menu items is similar to that for the ordinary Token-Rports. Please refer to the CrossFire 8600 Token-Ring Switch Guide to Operationfor details.

❏


34


35

any ted

our

r by

1)

)

o

a

5. Getting in Touch with Technical SupportIf support is not provided by your organization or the local vendor, you can at time relay information to or contact Olicom Technical Support via one of the lisservices. In addition, BBS, e-mail, FTP or WWW provide up-to-date software updates, application notes, quick fixes and various utilities which may solve yproblem.

Before You Contact Olicom Technical Support• Boot the switch to run the power-on diagnostics. Capture and print the

diagnostics (note that any traffic through the switch will be disrupted). .

• Enter the Statistics menu (see page 24) and select Display Summary. Make a screen dump of the screen that appears. . . . . . . .

• Print any messages in the Message Log Information screen . . .

• If possible, attach a display summary screen captured from the consoleor telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

• If possible, simplify the environment by removing other devices. . . . .

• Fill in as much as possible in the included Problem Report Form . . . .

• Contact your place of purchase . . . . . . . . . . . . . . . . . . . . . .

Hotline SupportCall the following numbers for help with any problem you may encounter when installing Olicom software and hardware products:

Fax Support

For assistance with any problem you may encounter when installing Olicom software and hardware products, Olicom’s Support department will reply eithe

Europe: (+45) 45 27 01 02 (Denmark, Monday to Friday, 8 am to 6 pm GMT +

(+48) 39 125 071 (Poland, Monday to Friday, 8 am to 6 pm GMT + 1

0 800 919 508 inside the UK or (+44) 1494 556 611 (UK, Monday tFriday, 9 am to 6 pm GMT)

USA: (+1) 1-800-OLICOM-1 or (+1) 972 516 4638 (24 hours a day, 7 daysweek)

CrossFire 8650/51 High-Speed Token-Ring UEM v. 1.0, P/N: 710001605 Getting in Touch with Technical Support

36

ng

ive

fax or by telephone within 24 hours, Monday to Friday. Use one of the followifax numbers:

Bulletin Board ServiceAll Olicom’s support services are available via our BBS: software updates, application notes, quick fixes, various utilities, etc. The Bulletin Board Service(BBS) can be contacted using either a standard modem or an ISDN modem.

Standard Modem RequirementsModem speed: 2400, 4800, 7200, 9600, 12000, 14400, 28800 bpsModem standard: CCITT V21/V22/V22bis/V32/V34/V42bis/HST/MNP5Parity: N (none)Databits: 8Stop bits: 1Transfer protocols: Xmodem, Ymodem, Zmodem, Kermit and Sealink.

Use one of the following numbers:

ISDN ModemUse the following number:

Internet E-MailOlicom customer support is available on e-mail through Internet. You will recea reply within 24 hours. Use one of the following e-mail addresses:

Europe: (+45) 45 27 02 40 (Denmark)

(+48) 58 346 1238 (Poland)

(+44) 1494 556 616 (UK)

USA: (+1) 972 516 0640

Europe: (+45) 45 27 01 00 (Denmark) (and create your own account)

USA: (+1) 972 422 9835

Europe: (+45) 45 96 32 48 (Denmark)

Europe: [email protected]

USA: [email protected]


37

er: P

cts, s and

b

e

Anonymous Internet FTP ServerAll Olicom’s support services can be obtained from our anonymous FTP servsoftware updates, application notes, quick fixes, etc. To connect, open an FTsession to:

Internet World Wide Web Server (WWW)The Olicom WWW server contains up-to-date information about Olicom produnewsletters and press releases. It also contains addresses of all Olicom officesupport centers worldwide. Our software library contains the latest driver andsoftware revisions. The WWW server can be accessed using the following weaddresses:

Olicom Support WEBThe Olicom Support WEB contains technical support hints, driver and softwarupdates, a problem report form and support news.

Select Services from the main menu.

Europe: ftp.olicom.dk

USA: ftp.olicom.com

Europe: http://www.olicom.dk

USA: http://www.olicom.com

Europe: http://www.olicom.dk


38

____

____

____

Problem Report Form

Fill in both sides of this Problem Report Form, print out the relevant system configuration files and fax or mail to Olicom Technical Support.

Company: ____________________________ Name: __________________

Address: ______________________________________________________

Country: _______________________ Phone/Fax: ____________________

E-mail: _____________________

Switch Information

Switch type:

Hardware revision:

Software version:

Switch Configuration

Port configuration:

Adapter Information

Adapter type:

Operating system:

Network OS:

Driver name:

Driver version:


39

Problem Description

Network Installation Sketch


40

❏


41

Appendix A. AbbreviationsAC Access Control

ARE All-Routes Explorer

ATM Asynchronous Transfer Mode

BRF Bridge Relay Function

CFI Canonical Format Indicator

CRC Cyclic Redundancy Check

CRF Concentrator Relay Function

DA Destination Address

DSAP Destination SAP

DTR Dedicated Token-Ring

ECO Engineering Check Order

FC Frame Control

FCS Frame Check Sequence

FDX Full Duplex

HDX Half Duplex

HSTR High-Speed Token-Ring

IP Internet Protocol

LAN Local Area Network

LED Light Emitting Diode

LLC Logical Link Control

MAC Media Access Control

Mbps MegaBit Per Second

MMF Multi Mode Fiber

MTU Maximum Transmission Unit

NSR Non-Source Routed

NVRAM Non-Volatile RAM

RAM Random Access Memory

CrossFire 8350/51 High-Speed Token-Ring UEM v. 1.0, P/N: 710001605 Abbreviations

42

RIF Route Information Field

RX Receive Data

SA Source Address

SAP Service Access Point

SNMP Simple Network Management Protocol

SR Source Routing

SRB Source Route Bridging

SRF Specifically Routed Frame

SRS Source Route Switching

SRT Source Route Transparent

SSAP Source SAP

STE Spanning Tree Explorer

TCI Tag Control Information

TFTP Trivial File Transfer Protocol

TR Token-Ring

TX Transmit Data

TXI Transmit Immediate

UEM Universal Expansion Module

UTP Unshielded Twisted Pair

VLAN Virtual LAN

❏

CrossFire 8350/51 High-Speed Token-Ring UEM v. 1.0, P/N: 710001605 Abbreviations

index-1

Index

Numerics802.5 MAC information 33

Aabbreviations 41

BBBS 36bulletin board service 36

Ccanceling a menu selection14configuration 9

console 11default 10

console configuration 11console, guidelines for using 14copyrights iiCrosFire 865x

two types 1

Ee-mail 36

Ffaxing Olicom 35FCC compliance iiFTP server 37

Hhotline support 35HSTR modules

configuration 9HSTR ports 12

restrictions 13

Iinstallation 3

cabling 7physical 4procedure for 3software 5

internete-mail 36FTP server 37WWW server 37

introduction 1

LLEDs 8

Mmenu navigation 15message log 24

Nnavigating in the menus 14, 15

Ppackage contents 3port groups 12port statistics menu 26port status screen 25problem report form 38

Rrefreshing the console panel14restrictions

ring number 13virtual ports 13

Sself-tests 9statistics 23

general 27virtual ports 32

statistics menu 24summary of contents visupport 35support web 37

Ttechnical support

e-mail 36fax 35hotline 35

CrossFire 8650/51 High-Speed Token-Ring UEM v. 1.0, P/N: 710001605 Index

index-2

WEB 37technical support, getting in touch with35three “dots” 15trademarks ii

Uusing the menus 14

Vvirtual ports

statistics 32VLANs 12

Wwww server 37

CrossFire 8650/51 High-Speed Token-Ring UEM v. 1.0, P/N: 710001605 Index

Olicom Enterprise Products, Inc. 450 Donald Lynch Boulevard Marlborough MA 01752

Tel: (+1) 508 481 4060 Fax: (+1) 508 229 5535

Olicom A/S Nybrovej 114 2800 Lyngby Denmark

Tel: (+45) 45 27 00 00 Fax: (+45) 45 27 01 01

Olicom, nc.1680 North Prospect DriveRichardson, TX 75081

Tel: (+1) 972 907 4600Fax: (+1) 972 671 7525

Olicom Singapore 10 Anson Road #15-12 International Plaza Singapore 079903

Tel: (+65) 324 5652 Fax: (+65) 324 7019

Olicom Japan 4F, Shin-yokohama Daisan Tosho Bldg. 3-5-9, Shin-yokohama Kohoku-ku Yokohama 222-0033

Tel: (+81) 45 477 3105 Fax: (+81) 45 477 3106

World Wide Web URLs http://www.olicom.com http://www.olicom.dk

Olicom Australia Level 6 73-79 Walker Street North Sydney, NSW 2060

Tel: (+61) 2 9955 1755 Fax: (+61) 2 9955 8488

Olicom France Immeuble Plein Ouest 177, Avenue G. Clemenceau 92024 Nanterre cedex

Tel: (+33) 01 41 91 17 17 Fax: (+33) 01 41 91 17 00

Olicom Germany FFFFrrrraaaannnnkkkkffffuuuurrrrt t t t OOOOffffffffiiiicccceeee:::: Hessenring 13a 64546 Mörfelden

Tel: (+49) 06 105 2892-0 Fax: (+49) 06 105 2892-10

MMMMuuuunnnniiiicccch h h h OOOOffffffffiiiicccceeee:::: Stefan-George-Ring 29 81929 Munich

Tel: (+49) 89 993 936-0 Fax: (+49) 89 993 936-27

Olicom Austria Mariahilfer Strasse 103/2/1/42a 1060 Vienna

Tel: (+43) 1 597 3131-0 Fax: (+43) 1 597 3131-31

Olicom Ibérica C/Basauri, 17 - 2° Drcha.A Edificio Valrealty A La Florida 28023 Madrid

Tel: (+34) 1 372 9814 Fax: (+34) 1 372 9645

Olicom Italy Via Rasori 13 20145 Milano

Tel: (+39) 2 4800 3661 Fax: (+39) 2 4800 5888

Olicom Africa JJJJoooohhhhaaaannnnnnnneeeessssbbbbuuuurrrrg g g g OOOOffffffffiiiicccceeee:::: 6th Floor, Nedbank House 12 Fredman Drive Sandown, Sandton

P.O. Box 785136 2146 Sandton

Tel: (+27) 11 784 8990 Fax: (+27) 11 784 9090

CCCCaaaappppe e e e TTTToooowwwwn n n n OOOOffffffffiiiicccceeee:::: 4 Docav Road Constantia Cape Town

P.O. Box 6196 8012 Roggebaai

Tel: (+27) 21 758 525 Fax: (+27) 21 758 527

Olicom Sweden Kanalvägen 10 C-12, 9 vån 194 61 Upplands Väsby

Tel: (+46) 8 590 041 94 Fax: (+46) 8 590 041 96

Olicom Enterprise Products (UK) Ltd Swan House Peregrine Business Park Gomm Road High Wycombe Bucks HP13 7DL

Tel: (+44) 1494 556 600 Fax: (+44) 1494 556 616

Olicom Poland Sp. z o.o. ul. Uphagena 27 80-237 Gdansk

Tel: (+48) 58 347 1451 Fax: (+48) 58 346 1238

Olicom Benelux Bolduc Office Centre Utopialaan 35-N 5232 CD ’s-Hertogenbosch

Tel: (+31) 73 6 49 15 46 Fax: (+31) 73 6 49 15 45

DOC-7016/1.0

* 710001605*

Documents

Guide to Operations