Cabletron Systems FDMMIM, FDMMIM-24 Installation And User Manual

FDMMIM, FDMMIM-04,

FDMMIM-24, and FDMMIM-30

FDDI CONCENTRATOR

ETHERNET to FDDI

BRIDGE MODULES

INSTALLATION and

USER’S GUIDE

The Complete Networking Solution

Cabletron Systems, P. O. Box 5005, Rochester, NH 03867-0505

NOTICE

NOTICE

Cabletron Systems reserves the right to make changes in specifications, hardware, firmware, software, and other information contained in this document without prior notice. The reader should in all cases consult Cabletron Systems to determine whether any such changes have been made.

IN NO EVENT SHALL CABLETRON SYSTEMS BE LIABLE FOR ANY

INCIDENTAL, INDIRECT, SPECIAL, OR CONSEQUENTIAL

DAMAGES WHATSOEVER (INCLUDING BUT NOT LIMITED TO

LOST PROFITS) ARISING OUT OF OR RELATED TO THIS MANUAL

OR THE INFORMATION CONTAINED IN IT, EVEN IF CABLETRON

SYSTEMS HAS BEEN ADVISED OF, KNOWN, OR SHOULD HAVE

KNOWN, THE POSSIBILITY OF SUCH DAMAGES.



Copyright July 1994

Cabletron Systems, Inc

P.O. Box 5005

Rochester, NH 03867-0505

All Rights Reserved

Printed in the United States of America

Part number: 9030670-03 July 1994

Multi Media Access Center, SPECTRUM, Remote LANVIEW, and LANVIEW are registered trademarks and FDMMIM,

FDMMIM-04, FDMMIM-24, FDMMIM-30, FDCMIM-04,

FDCMIM-08, FDCMIM-24, FDCMIM-28, IRM, IRM-2, IRM-3,

IRBM, EMME, TRMM, CXRMIM, TPRMIM, FORMIM, Flexible

Network Bus, MMAC-3FNB, MMAC-5FNB, MMAC-8FNB, and

MMAC-M8FNB are trademarks of Cabletron Systems, Inc.

CompuServe is a registered trademark of CompuServe.

Ethernet is a trademark of Xerox, Inc.

IBM is a registered trademark of International Business Machines Corp.

UNIX is a registered trademark of Unix System Laboratories, Inc.

VT-220 and VT-320 are trademarks of Digital Equipment Corp.

Windows is a registered trademark of Microsoft Corp.

i

FCC NOTICE

FCC NOTICE

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 any interference received, including interference that may cause undesired operation.

NOTE: 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 when the equipment is operated in a commercial environment. This equipment uses, generates, and can radiate radio frequency energy and if not installed in accordance with the operator’s manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause interference in which case the user will be required to correct the interference at his own expense.

WARNING: Changes or modifications made to this device which are not expressly approved by the party responsible for compliance could void the user’s authority to operate the equipment.

DOC NOTICE

This digital apparatus does not exceed the Class A limits for radio noise emissions from digital apparatus set out in the Radio

Interference Regulations of the Canadian Department of

Communications.

Le présent appareil numérique n’émet pas de bruits radioélectriques dépassant les limites applicables aux appareils numériques de la class A prescrites dans le Règlement sur le brouillage radioélectrique

édicté par le ministère des Communications du Canada.

recycled paper Printed on ii

SAFETY INFORMATION

CLASS 1 LASER TRANSCEIVERS

NOTICE

CLASS 1

LASER PRODUCT

Class 1 Laser Products

The FDMMIM-30 connectors use Class 1 Laser transceivers. Read the following safety information before installing or operating the

FDMMIM-30.

The Class 1 laser transceivers use an optical feedback loop to maintain Class 1 operation limits. This control loop eliminates the need for maintenance checks or adjustments. The output is factory set, and does not allow any user adjustment. Class 1 Laser transceivers comply with the following safety standards:

• 21 CFR 1040.10 and 1040.11 U.S. Department of Health and

Human Services (FDA).

• IEC Publication 825 (International Electrotechnical

Commission).

• CENELEC EN 60825 (European Committee for

Electrotechnical Standardization).

When operating within their performance limitations, laser transceiver output meets the Class 1 accessible emission limit of all three standards. Class 1 levels of laser radiation are not considered hazardous.

iii

FCC NOTICE

SAFETY INFORMATION

CLASS 1 LASER TRANSCEIVERS

Laser Radiation and Connectors

When the connector is in place, all laser radiation remains within the fiber. The maximum amount of radiant power exiting the fiber

(under normal conditions) is -12.6dBm or 55x10 -6 watts.

Removing the optical connector from the transceiver allows laser radiation to emit directly from the optical port. The maximum radiance from the optical port (under worst case conditions) is 0.8 W cm-2 or 8x10 3 W m-2 sr-1.

Do not use optical instruments to view the laser output. The use of optical instruments to view laser output increases eye hazard. When viewing the output optical port, you must remove power from the network adapter.

iv

CONTENTS

CONTENTS

CHAPTER 1 INTRODUCTION

1.1 Using this Manual ........................................................................1-2

1.2 Getting Help ..................................................................................1-4

1.3 The FDMMIM FDDI Concentrator and Ethernet to FDDI

Bridging Modules ..........................................................................1-4

1.4 FDMMIM Features .......................................................................1-7

CHAPTER 2 INSTALLING THE FDMMIM

2.1 Before you Install the FDMMIM . . . ............................................2-1

2.1.1 Adding MIMs to an MMAC .................................................2-2

2.1.2 MMAC Configurations ........................................................2-4

2.1.3 IRM-3 and Ethernet MIMs with FDMMIMs .....................2-4

2.1.4 EMME and RMIMs with an FDMMIM ..............................2-5

2.2 Installing the FDMMIM ...............................................................2-6

2.2.1 Setting Jumpers ..................................................................2-6

2.2.2 Setting Configuration Switches ..........................................2-7

2.2.3 Installing into the MMAC ...................................................2-9

2.3 Connecting Fiber Optic Cabling .................................................2-10

2.4 FDMMIM-04 and FDMMIM-24 Master Port

Cable Connections .......................................................................2-13

2.5 Twisted Pair Pinout Configuration ............................................2-13

2.6 Master Ports and LANVIEW ......................................................2-14

2.7 FDMMIM and LANVIEW ..........................................................2-15

2.7.1 Ethernet LEDs ...................................................................2-15

2.7.2 FDDI LEDs ........................................................................2-17

CHAPTER 3 CONNECTING TO LOCAL MANAGEMENT

3.1 Connecting a Console ....................................................................3-1

3.2 Powering-up the FDMMIM: Diagnostic Tests ............................. 3-4

3.3 Manually Resetting the FDMMIM ...............................................3-6

CHAPTER 4 GETTING STARTED WITH FDMMIM

LOCAL MANAGEMENT

4.1 Understanding the Screens and Commands ...............................4-1

4.2 Using the Management Keyboard................................................ 4-2

4.3 Navigating through Local Management ......................................4-2 v

CONTENTS

4.4 Screen Organization ......................................................................4-4

4.4.1 Screen Header and Message Bar Section ........................... 4-4

4.4.2 Data Sections and Command Menus .................................4-7

4.5 Setting FDMMIM Operating Parameters ...................................4-7

CHAPTER 5 USING THE INFORMATION SCREENS

5.1 The System Information Screen ...................................................5-1

5.1.1 NETWORK TRAFFIC Data ................................................ 5-2

5.1.2 FDDI Data ...........................................................................5-3

5.1.3 FILTER DATABASE Data..................................................5-5

5.1.4 BRIDGE PROTOCOL Data ................................................ 5-6

5.1.5 System Information Screen Commands ............................. 5-8

5.2 The Network Traffic Screen .........................................................5-9

5.2.1 Network Traffic Screen Data ............................................5-10

5.2.2 Network Traffic Screen Commands .................................5-12

5.3 The Ring Map Screen ..................................................................5-13

5.3.1 Ring Map Screen Data ......................................................5-14

5.3.2 Ring Map Screen Commands ...........................................5-15

5.3.3 Adjusting the Scroll Number (n) ......................................5-15

5.4 The Node Information Screen ....................................................5-16

5.5 The Message Log Screen .............................................................5-18

5.5.1 Message Log Data .............................................................5-20

5.5.2 Message Log Screen Commands .......................................5-20

CHAPTER 6 SETTING UP THE FDMMIM

6.1 The Setup Screen ..........................................................................6-1

6.1.1 Setup Screen Data ...............................................................6-2

6.1.2 Setup Screen Commands ....................................................6-6

6.2 The Community Names Table Screen ......................................... 6-7

6.2.1 Community Names Table Screen Data ..............................6-8

6.2.2 Community Names Table Screen Commands ...................6-9

6.3 TFTP Code Download Setup Screen ............................................6-9

6.3.1 TFTP Code Download Setup Screen Data .......................6-10

6.3.2 TFTP Code Download Setup Screen Commands .............6-10

6.4 Image File Download with UNIX ...............................................6-11

6.5 Forcing an Image File Download ...............................................6-13

6.5.1 Forcing a Download with FDMMIM/LM ..........................6-13

6.5.2 Forcing a Download with BOOTP .................................... 6-14 vi

CONTENTS

CHAPTER 7 SPANNING TREE

7.1 The Bridge Protocol Screen ..........................................................7-1

7.1.1 Bridge Protocol Screen Data ...............................................7-2

7.1.2 Bridge Protocol Screen Commands .................................... 7-5

7.2 The Bridge Port Parameters Screen ............................................7-5

7.2.1 Bridge Port Parameters Screen Data .................................7-6

7.2.2 Bridge Port Parameter Screen Commands ........................ 7-7

CHAPTER 8 THE FILTERING DATABASES

8.1 Bridge Operation ...........................................................................8-1

8.2 The Filter Database Screen ..........................................................8-2

8.2.1 Filter Database Screen Data .............................................. 8-3

8.2.2 Filter Database Screen Commands .................................... 8-4

8.3 Display Filter Entries Screen .......................................................8-5

8.3.1 Display Filter Entries Screen Data .................................... 8-6

8.3.2 Display Filter Entries Screen Commands .........................8-7

8.4 Create Filter Entry Screen ...........................................................8-7

8.4.1 Create Filter Entry Screen Data ........................................8-8

8.4.2 Create Filter Entry Screen Commands ..............................8-9

8.5 Delete Filter Entry Screen............................................................ 8-9

8.5.1 Delete Filter Entry Screen Data .......................................8-10

8.5.2 Delete Filter Entry Screen Commands ............................8-10

8.6 Special Database Screen .............................................................8-11

8.6.1 Special Database Screen Data ..........................................8-12

8.6.2 Special Database Screen Commands ...............................8-13

CHAPTER 9 CONTROLLING CONCENTRATOR

MODULES AND PORTS

9.1 The FDDI Configuration Screen ..................................................9-1

9.1.1 FDDI Configuration Screen Data .......................................9-2

9.1.2 FDDI Configuration Screen Commands ............................9-4

9.2 Concentrator Status and Bridge Operations ...............................9-4 vii

CONTENTS

APPENDIX A FDMMIM/LM MESSAGES

Information Messages .........................................................................A-1

Warning Messages ..............................................................................A-1

Error Messages ...................................................................................A-9

APPENDIX B SPECIFICATIONS

APPENDIX C BASIC FDDI NETWORKS

Basic FDDI Concepts ..........................................................................C-1

FDDI Media Access Protocol ........................................................C-1

Reliability .....................................................................................C-3

ANSI Standard X3T9.5 ................................................................C-4

FDDI Connection Rules ................................................................C-8

FDDI Devices ......................................................................................C-9

Design Considerations for FDDI Networks .....................................C-14

Ring Length ................................................................................C-14

Drive Distance ............................................................................C-14

Attenuation .................................................................................C-15

Bandwidth ...................................................................................C-15

Number of Stations ...........................................................................C-15

INDEX viii

INTRODUCTION

CHAPTER 1

INTRODUCTION

The FDMMIM, FDMMIM-04, FDMMIM-24, and FDMMIM-30 combine the functions of an FDDI concentrator with those of an

Ethernet/802.3 to FDDI bridge. When distinguishing one module from the other, keep the following in mind:

• All modules contain FDDI A and B ports which bridge to a

Multi Media Access Center

 hub Ethernet bus.

• The FDMMIM-04 and FDMMIM-24 also contain four M type concentrator ports.

• The master ports of the FDMMIM-24 are unshielded twisted pair connections.

• The FDMMIM, FDMMIM-04, and the FDMMIM-24 A and B ports are multimode fiber optic devices.

• The FDMMIM-30 is a single mode fiber optic module that uses a class 1 laser. This laser increases the link length from the multimode maximum drive distance of 2 kilometers (km) to a single mode maximum of 40 km.

This manual describes how to install the FDMMIM, FDMMIM-04,

FDMMIM-24, and FDMMIM-30 and explains how to use the onboard management tool, FDMMIM Local Management, to configure, monitor, and control the bridge/concentrator.

Unless otherwise noted, the term FDMMIM refers to the FDMMIM,

FDMMIM-04, FDMMIM-24, and FDMMIM-30. In addition, the terms FDMMIM/LM, Local Management, and LM refer to FDMMIM

Local Management.

1-1

INTRODUCTION

1.1

USING THIS MANUAL

You should have a general working knowledge of FDDI networks and the ANSI X3T9.5 standard prior to installing the FDMMIM. (If you need a review of FDDI, see Appendix C.) The following summarizes the organization of this manual.

Chapter 1, Introduction, describes the FDMMIM and its features.

Chapter 2, Installing the FDMMIM, explains how to configure and install the FDMMIM in a Multi Media Access Center chassis. This chapter also explains each LANVIEW



indicator.

Chapter 3, Connecting to Local Management, explains how to connect to, and begin using, FDMMIM Local Management. This chapter also explains the power-up diagnostic tests.

Chapter 4, Getting Started with FDMMIM Local Management, explains conventions used in this manual to describe the Local

Management screens, and summarizes the organization of Local

Management.

Chapter 5, Using the Information Screens, describes the following Local Management screens:

System Information

Network Traffic

Ring Map

Node Information

Message Log

Displays system status information and contains the menu choices that provide access to all Local

Management screens.

Displays detailed information about network traffic loads at both the

Ethernet and FDDI ports.

Displays the logical topography of the

FDDI ring.

Displays detailed information specific to a selected node on the Ring Map.

Displays the history file that keeps track of information, warning, and error messages generated by Local

Management.

1-2

INTRODUCTION

Chapter 6, Setting Up the FDMMIM, explains the following Local

Management screens:

Setup

Community

Names Table

Controls FDMMIM parameters.

Set permissions for remote access to the FDMMIM, and create Local

Management passwords.

TFTP Code

Download Setup

Set conditions for updating the

FDMMIM firmware.

This chapter also provides basic TFTP code downloading instructions, and guidelines for setting up a UNIX workstation to handle an image file download.

Chapter 7, Spanning Tree, explains the Bridge Protocol screen and the Port Parameters screen, which let you control the participation of the FDMMIM in the Spanning Tree Algorithm.

Chapter 8, The Filtering Databases, explains the purpose of the

Acquired, Permanent, and Special Databases, and how to view/ manipulate their contents.

Chapter 9, Controlling Concentrator Modules and Ports, explains how to enable/disable FDDI concentrator modules and ports through the FDDI Configuration screen.

Appendix A, FDMMIM/LM Messages, lists each message that you can encounter in Local Management, the probable cause of the message, and some possible solutions.

Appendix B, Specifications, lists the electrical, physical, and environmental specifications of the FDMMIM bridge/concentrator.

Appendix C, Basic FDDI Networks, covers basic concepts of FDDI networks, FDDI devices, and design/installation considerations.

1-3

INTRODUCTION

1.2

GETTING HELP

If you have any questions, comments or suggestions related to the

FDMMIM or this manual, you can contact Cabletron Systems

Technical Support by any of the following methods:

By phone:

By CompuServe



By Internet mail:

:

Monday through Friday between

8 A.M. and 8 P.M. Eastern Standard

Time at (603) 332-9400.

GO CTRON from any ! prompt [email protected]

Before calling, please have the product serial number (located on the

FDMMIM front panel) and product type (FDMMIM, FDMMIM-04,

FDMMIM-24, FDMMIM-30) ready.

1.3

THE FDMMIM FDDI CONCENTRATOR AND ETHERNET

TO FDDI BRIDGING MODULES

The FDMMIM provides an ANSI X3T9.5 and IEEE 802.1d compliant media interface that connects an Ethernet and FDDI network using translation bridging. It contains the A and B ports of a modular

Dual Attached Station (DAS) or Dual Attached Concentrator (DAC).

The FDMMIM works in conjunction with the FDCMIM family of

Cabletron Systems FDDI Concentrator Modules. These devices provide 4 or 8 M-type port connections for various cable types.

The FDCMIM-04 and FDCMIM-08 have FDDI multi-mode connector ports. The FDCMIM-24 and FDCMIM-28 have unshielded twisted pair connector ports. The FDCMIM-34 and FDCMIM-38 have single mode fiber connector ports. The FDCMIM-44 and FDCMIM-48 have shielded twisted pair connector ports. All of these devices reside in a

Multi Media Access Center (MMAC).

You can manage the FDMMIM remotely through an SNMP management tool such as Cabletron Systems’ SPECTRUM

Remote LANVIEW



 or

/Windows, or locally through an RS-232 console port with the on-board management tool called FDMMIM Local

Management.

1-4

INTRODUCTION

FDMMIM

SN

RESET

ENET

FDDI

PWR

TWR

XMT

RCV

WRP

ROP

B

Y

P

A

S

S

STBY

SYOK

XMT

RCV

CLN

POK

F

D

D

I

A

LINK

O

L

E

C

O

N

S

M

O

D

E

M

F

D

D

I

B

FDMMIM-04

SN

PST

PST

RESET

ENET

FDDI

LNK

1

PWR

TWR

XMT

RCV

WRP

ROP

LNK

2

B

Y

P

A

S

S

STBY

SYOK

XMT

RCV

CLN

POK

F

D

D

I

A

LINK

PST LNK

3

F

D

D

I

B

PST LNK

4

O

L

E

C

O

N

S

M

O

D

E

M

FDDI FDDI

FDMMIM-24

SN

PST

PST

PST

PST

RESET

ENET

FDDI

PWR

TWR

XMT

RCV

WRP

ROP

LNK

1

LNK

B

Y

P

A

S

S

STBY

SYOK

XMT

RCV

CLN

POK

F

D

D

I

A

2

LINK

LNK

3

F

D

D

I

B

LNK

4

C

O

N

S

O

L

E

M

O

D

E

M

UTP-PMD

FDDI

FDMMIM-30

SN

RESET

ENET

FDDI

PWR

TWR

XMT

RCV

WRP

ROP

B

Y

P

A

S

S

STBY

SYOK

XMT

RCV

CLN

POK

F

D

D

I

A

LINK

SMF-PMD

FDDI

O

L

E

C

O

N

S

M

O

D

E

M

F

D

D

I

B

Figure 1-1. FDMMIM Modules

Local Management for the FDMMIM provides module and network information such as frame counts, error breakdowns, and bridge information. You can view LM on a Digital Equipment Corporation

VT220



or VT320



terminal, or a PC with terminal emulation software. Since the FDMMIM is ANSI X3T9.5 compliant, FDMMIM

Local Management can provide Station Management (SMT) information such as ring state, station state, and ring configuration.

1-5

INTRODUCTION

The FDMMIM can accept an Optical Bypass Switch (Figure 1-2). If you use this optional device, the fiber optic connections pass through the switch, automatically switching to a bypass mode. This feature maintains ring continuity, if the bridge module loses power.

The MMAC Ethernet “A” Bus provides the Ethernet interface.

Ethernet traffic accesses the bus through the EMME (Ethernet

Management Module with Ethernet), IRM (Intelligent Repeater

Module) series, or any Cabletron Ethernet Management Module.

Figure 1-3 represents a typical FDDI to Ethernet bridge.

Figure 1-2. Optical Bypass Switch

1-6

INTRODUCTION

FDCMIM FDMMIM

MMAC

FDDI

BUS

FDDI Ring

Connections

A B

MMAC

ETHERNET

BUS

IRM3

ETHERNET

NETWORK

FIGURE 1-3. Bridging FDDI to Ethernet with the FDMMIM

1.4

FDMMIM FEATURES

LANVIEW

LANVIEW is a visual diagnostic and status monitoring system developed by Cabletron Systems. LEDs on the FDMMIM front panel indicate the status of the FDMMIM and can help identify module and physical layer problems.

Hot Swapping

Like all Cabletron Systems Media Interface Modules, you can remove the FDMMIM from, and insert it into, an MMAC without turning off the power to the rest of the modules in the hub.

1-7

INTRODUCTION

Management

An RS-232 console port gives you direct access to FDMMIM Local

Management. Here you can check bridge statistics, and control the bridge and FDDI port configuration. The FDMMIM also supports

SNMP network management tools such as Cabletron Systems’

SPECTRUM products.

Shared Memory

The FDMMIM has 4 Mbytes of DRAM buffer memory which it uses for storing data frames. The on-board processor and other support logic also use this memory.

Local Memory

In addition to the buffer memory, the FDMMIM CPU operates with

4 Mbytes of DRAM, and uses 512 Kbytes of FLASH memory to store its on-board software.

Battery Back-up RAM

The FDMMIM saves its Local Management statistics and operating parameters in battery backed up RAM. The battery retains userconfigured settings, when the FDMMIM loses power or is turned off.

Source Address Table Size

The FDMMIM uses a learning and filtering algorithm and can retain up to 8,192 source address static or dynamic table entries.

Spanning Tree Algorithm

The FDMMIM supports both 802.1d and DEC Spanning Tree

Algorithm (STA) protocols.

FlASH EEPROM Memory Support

As Cabletron Systems makes enhancements to Local Management, you can upgrade your FDMMIM by downloading new software images into the FDMMIM FLASH EEPROM (electrically erasable programmable read only memory).

Through Local Management, you can control the download path of an image file between your FDMMIM and a network server, such as a remote network management tool like Remote LANVIEW/Windows or even a UNIX workstation. The FDMMIM also provides a way to broadcast a request for an image file using the BOOTP switch.

Chapter 6 provides more information regarding image file download using FDMMIM Local Management or the BOOTP switch.

1-8

INSTALLING THE FDMMIM

CHAPTER 2


The FDMMIM is a media interface module (MIM) that fits into a

Cabletron Systems MMAC network hub. You can install the

FDMMIM in any MMAC slot except for slot 1 (the right-most slot).

This chapter describes:

• Configuring your MMAC hub

• Setting the FDMMIM hardware configuration switch

• Activating the battery

• Installing the FDMMIM into the MMAC

• Connecting the fiber optic cables

Connecting to the Console port is described in Chapter 3,

Connecting to Local Management.

Note: Be sure to activate the battery before you install the FDMMIM.

The battery is disabled for shipment. If you do not activate the battery, all bridge configuration settings reset to default values when you turn off the power.

2.1

BEFORE YOU INSTALL THE FDMMIM . . .

Installing an FDMMIM is a simple process of setting the switches and battery jumper, sliding the module into an MMAC slot, and connecting the fiber optic cables. But before you start the installation, you should decide how you want to configure the

MMAC. The location of an FDMMIM in an MMAC can affect communication between MIMs and your ability to manage MIMs. To help you properly configure your MMAC, this section lists MMAC configuration guidelines, and then explains how an FDMMIM can reside in an MMAC that also holds Ethernet or Token Ring MIMs.

2-1


2.1.1 Adding MIMs to an MMAC

The following examples provide only a sampling of possible MIM and

MMAC combinations. Refer to Appendix B for a list of FDMMIM and

FDCMIM power requirements. In addition, when configuring an

MMAC, remember the following:

• MMAC-3FNB board slot numbers increment from bottom to top. MMAC-5FNB, MMAC-8FNB and MMAC-M8FNB board slot numbers increment from right to left.

• The first slot in every MMAC is a narrow slot reserved for a half-width management module, such as the TRMM, IRM-3 or EMME. Do not place full-width modules in the first slot of an MMAC. When not using half-width management modules, leave the first slot empty.

• An MMAC-5FNB can hold four MIMs, one management module, and two power supplies. By removing one power supply, the MMAC-5FNB can hold an extra MIM, assuming that the remaining power supply has enough capacity to handle the combined load of the resident MIMs.

• FDDI MIMs consume more power than other MIMs. Some of the older MMACs may not have enough power available to support a planned configuration. For example, the combined load of an FDCMIM-08 and an FDMMIM exceeds the available power of an MMAC-3FNB (Figure 2-1).

11.8 amps

FDCMIM-08

8.0 amps

FDMMIM

12.0 amps

(MMAC-3FNB

Power Suppy

Output)

Figure 2-1. FDDI MIMs in an MMAC-3FNB

2-2


Figure 2-2 represents an MMAC-5FNB equipped with dual power supplies, two FDCMIM-08s and an FDMMIM-04. The

MMAC has enough power to support the configuration.

However, the combined load of the modules exceeds the output of a single power supply. This means that the hub does not have redundant power (the ability of one power supply to assume the entire load if one supply fails).

11.8 amps

FDCMIM-08

11.8 amps

FDCMIM-08

12.5 amps

FDMMIM-04

48.0 amps

(MMAC-5FNB

Dual Power

Supply Output)

Figure 2-2. FDDI MIMs in an MMAC-5FNB

Figure 2-3 represents an MMAC-M8FNB equipped with a full complement of power supplies, two FDCMIM-08s, and one FDMMIM-04. The MMAC power supplies produce up to

80 amps of power, providing more than double the power necessary for operation. This configuration provides redundant power to the hub.

11.8 amps

FDCMIM-08

11.8 amps

FDCMIM-08

12.5 amps

FDMMIM-04

80.0 amps

(MMAC-M8FNB

Dual Power

Supply Output)

Figure 2-3. FDDI MIMs in an MMAC-M8FNB

When unsure of a hub’s ability to support a planned MIM configuration, check the appropriate manuals to determine the amount of power consumed by each MIM (amps at 5 Vdc), and then check your MMAC power supply configuration

(single or multiple power supplies) to determine if you have sufficient power available to support the configuration.

2-3


2.1.2 MMAC Configurations

The FDMMIM can bridge FDDI and Ethernet. Since the Ethernet interface to the FDMMIM is through an MMAC Ethernet bus, the bridging function requires that you have both Ethernet and FDDI modules in the same MMAC. To help you configure your MMAC, consider two common MMAC configurations:

• An IRM-3 Ethernet management module, Ethernet MIMs, an

FDMMIM, and an FDCMIM

• An EMME Ethernet management module, at least one

Ethernet Repeater MIM, an FDMMIM, and an FDCMIM.

The examples in this section include both an FDMMIM and an

FDCMIM. An FDCMIM is not required; it merely adds master ports to the FDMMIM concentrator.

2.1.3 IRM-3 and Ethernet MIMs with FDMMIMs

This example uses the IRM-3, but the same guidelines apply if you are using an IRM, IRM-2, or IRBM.

In the example configuration shown in Figure 2-4, the MMAC-5FNB has an IRM-3 in slot 1 and TPMIM-22s in slots 2 and 3. Slot 4 holds an FDMMIM-04 and slot 5 holds an FDCMIM-04.

The IRM-3, designed to reside in slot 1, lets you manage the

Ethernet side of the hub network. The FDMMIM-04, manages the

FDDI side of the network and controls the bridging functions.

The FDMMIM-04 in slot 4 connects to the:

• Ethernet network through the MMAC Ethernet bus

• FDCMIM through the MMAC FDDI bus

• FDDI ring through its A and B ports.

2-4


POWER

FAIL OK SN

MMAC - 5PSM

OFF

ON

FDCMIM-04

SN

FNB

PST

PST

PWR

LNK POK

1

2

FDMMIM-04

SN

LNK POK

RESET

ENET

FDDI

LNK PWR

TWR

XMT

1

RCV

WRP

ROP

LNK

STBY

SYOK

XMT

RCV

CLN

POK

B

Y

P

A

S

S

2

D

I

A

F

D

PST

PST

FDDI

LNK POK

3

LNK POK

4

LNK

3

LNK

4

FDDI

LINK

D

I

F

D

B

C

O

N

S

L

E

O

D

E

M

TPMIM-22

SN

3

X

4

X

1

X

2

X

5

X

6

X

RCV

LNK

ERR

4

5

6

7

1

2

3

8

9

10

11

12

7

X

8

X

11

X

12

X

9

X

10

X

10BASE-T

ETHERNET

TPMIM-22 IRM3

SN

10BASE-T

ETHERNET

7

X

8

X

11

X

12

X

9

X

10

X

3

X

4

X

1

X

2

X

5

X

6

X

RCV

LNK

ERR

4

5

6

7

1

2

3

8

9

10

11

12

SN

RESET

PWR

MGMT

CLN

ON

BOK

RCV

POK

OFF

C

O

N

S

O

L

E

T

X

R

X

M

O

D

E

M

ETHERNET

POWER

FAIL SN

MMAC - 5PSM

OFF

ON

OK

Figure 2-4. FDDI and Ethernet MIMs in the Same Hub

2.1.4 EMME and RMIMs with an FDMMIM

The EMME, a narrow Ethernet management module, works with the repeater interface controller family of MIMs (RMIM): TPRMIM,

CXRMIM, and FORMIM. RMIMs can take full advantage of the

MMAC’s Flexible Network Bus (FNB), making them unique. You can configure the RMIMs to use either the B or C bus of the FNB. This means that an RMIM can put Ethernet traffic on MMAC buses that normally see Token Ring and FDDI traffic. The EMME can manage

Ethernet traffic on the A bus (the dedicated Ethernet bus), either

FNB data bus, the D bus (accessed through the front panel), and can bridge traffic among the A, B, C, and D networks.

Even though RMIMs can place Ethernet traffic on the bus that normally handles FDDI traffic, FDDI MIMs can still reside in the same hub with RMIMs. RMIMs determine whether or not the MIM that resides in the next higher numbered MMAC slot is an Ethernet

MIM. If the next MIM is not an Ethernet MIM, the RMIM activates relays that, in effect, terminate the B and C buses. To eliminate potential problems, we recommend installing the RMIMs in lower numbered slots and the FDDI MIMs in higher numbered slots.

2-5


To demonstrate this MIM interaction, assume that we have an

MMAC-5FNB configuration as follows:

Slot 1 - EMME

Slot 2 - TPRMIM-36

Slot 3 - FDMMIM

Slot 4 - FDCMIM-04

After turning on the MMAC, the TPRMIM checks the MIM in slot 3.

When it determines that slot 3 does not hold an Ethernet MIM, it activates the relays that terminate the Ethernet section of the B and

C buses. The FDDI MIMs can put FDDI frames on the C bus because the FDDI portion of the C bus is physically isolated from the

Ethernet portion. This example uses the TPRMIM, but the same would be true if you were using any of the other RMIMs as well.

For a more thorough description of the RMIMs and how they use the

MMAC buses, see your RMIM documentation.

2.2


Caution: Observe all static precautions when handling boards.

Always leave the FDMMIM inside the protective bag when the MIM is not installed in an MMAC. If you need to set the MIM down during installation, set it on a clean, non-conducting surface.

Before you actually install the FDMMIM into the MMAC, you must activate the battery and set any bridge configuration switches.

2.2.1 Setting Jumpers

Your FDMMIM uses a Nicad battery to maintain power to the RAM in the event of power loss. The RAM holds all bridge configuration data. To prevent the battery from discharging during shipment, the factory sets the battery jumper to the disabled position. You must enable the battery before you install the FDMMIM. Figure 2-5 shows the location of the three pin battery jumper. To activate the battery:

• Position the plastic jumper so that it connects the right two pins of JP1.

2-6


Jumper JP6 (Figure 2-5) is a laser jumper. This jumper has no affect on FDMMIM operation; it simply indicates to non-FDDI management modules that it is an FDDI single mode or multimode board.

This jumper is set at the factory; you need not change its position.

2.2.2 Setting Configuration Switches

Before installing your FDMMIM, you must set the bridge configuration switches to select initial configuration options. Though the modular switch bank holds eight switches, the FDMMIM utilizes only a few of them. (See Figure 2-6.)

Note: At power-up, configuration switch settings override Local

Management settings. This means that when you cycle MMAC power or reset the FDMMIM, LM settings default to their corresponding configuration switch settings.

Locate the switch bank along the top edge of the FDMMIM and

FDMMIM-30 (Figure 2-5). On the FDMMIM-04 and FDMMIM-24, the switch bank resides just below the daughter board containing the

M type ports.

LASER

Configuration

Switch

Set to LASER (on

FDMMIM-30 only)

LASER

Laser

Jumper (JP6)

FDMMIM

Front Panel

Battery

OFF

JP1

ON

B

A

P

L

AI

NVIE

W

PMB 3.6B

T

T E R I

E

S

Battery

ON

OFF ON

JP1

Battery

Jumper (JP1)

Figure 2-5. Battery Activation/Switch Bank Location

2-7


Figure 2-6 shows the general location of the switch bank and the configuration switch options.

Note: The FDMMIM is shipped with all switches in the ON position.

1. ON - Forward broadcast packets

OFF - Filter broadcast packets

2. Not used

3. Not used

4. ON - Multimode Fiber

OFF - Single Mode Fiber

Note: Switch #4 does not affect

operation; this switch simply tells

LM whether it is a Multimode

or Single Mode board.

ON 1 2 3 4 5 6 7 8

8. ON - Normal

OFF - Manufacturing use only

7. BOOTP toggle switch

(for emergency boot-up, and

download use only -- see Chapter 6)

6. Not used

5. Not used

Figure 2-6. Configuration Switch Settings

2-8


2.2.3 Installing into the MMAC

After configuring your MIMs, activating the FDMMIM battery, and setting any FDMMIM configuration switches, proceed as follows:

Note: We recommend powering-down your MMAC before removing

FDMMIMs, even though these modules have “hot swap” capabilities.

1.

Turn off the power to the MMAC. Remember that MMACs with multiple power supplies have an On/Off switch for each supply.

2.

Holding the FDMMIM by the front panel or by the edges of the circuit board, align the bottom and top edges of the card with the slot guides in the MMAC chassis. Be sure that both the bottom and top edges of the card rest in the guide slots. (See Figure 2-7.)

3.

Slide the FDMMIM into the MMAC until you feel it meet the backplane. At this point, the front panel should be about 1/2 inch from being flush with the rest of the modules in the MMAC.

4.

Press gently to seat the module into the backplane. Do not try to force the module into place or use the knurled knobs to draw the module into the backplane. Forcing a misaligned module into place can damage the FDMMIM or the MMAC backplane.

5.

Once the module seats in the backplane, tighten the two knurled knobs. This step is important. If you do not tighten the knurled knobs, vibration can cause the module to lose contact with the backplane and disrupt your network.

2-9


POWER

FAIL OK SN

MMAC - 5PSM

OFF

ON

FOMIM-22

FDMMIM-04

SN

SN

POK

POK

RESET

ENET

FDDI

LNK

PWR

TWR

XMT

1

WRP

RX

TX

LNK

RX

PWR

B

Y

P

A

S

S

STBY

SYOK

XMT

RCV

CLN

POK

SN

IRM3

RESET

PWR

MGMT

CLN

ON

BOK

RCV

POK

OFF

POK

2

TX

RX

D

I

F

D

A

O

L

E

C

O

N

S

POK

LNK

TX

RX

LINK

3

TX

RX

LNK

TX

M

O

D

E

M

4

RX

C

O

N

S

O

L

ETHERNET

4

D

I

B

F

D

T

X

R

X

M

O

D

E

M

ETHERNET

FDDI

FAIL

OFF

POWER

OK SN

MMAC - 5PSM

ON

Figure 2-7. Installing the FDMMIM into the MMAC

2.3

CONNECTING FIBER OPTIC CABLING

You can install the FDMMIM as a Dual Attached Station (DAS), with or without an optical bypass switch. Figure 2-8 illustrates the main ring cabling to the FDDI A and B ports on the FDMMIM.

Figure 2-9 shows the duplex cable connections to the A and B ports.

When installed, the optical bypass switch connects in series between the main ring connections and the FDMMIM. (For a summary of

FDDI connection rules, see Appendix C.)

2-10


Primary In

Red Key

F

D

D

I

A

Secondary

Out

Secondary

In

Blue Key

F

D

D

I

B

Primary

Out

Figure 2-8. FDMMIM Duplex Fiber Optic Receptacles

The Optical Bypass Switch (also known as a Station Bypass Switch or a Bypass Relay) is an X3T9.5 compliant device that automatically isolates the FDMMIM from the ring if the FDMMIM fails or the

FDMMIM power source fails. The bypass switch is optional. If you use this optional device, you should remember the following:

• A bypass switch causes some signal loss which may cause you to exceed the maximum allowable loss between stations.

• Bypass technology can protect only a small number of consecutive bypassed stations. The exact number varies but in a typical building environment, the maximum is three.

2-11


Secondary

Ring

Primary

Ring

Optical

Bypass

Secondary

Ring

Primary

Ring

BYPASS FDDI A FDDI B

FDMMIM

Figure 2-9. FDMMIM Dual Ring Connections

Through a Bypass Switch

When installing an optical bypass switch, begin with steps 1 and 2 below to attach the duplex main ring cabling to the switch.

Otherwise, begin with step 3.

Note: If you install the bypass switch with the FDMMIM powered-up, it can take up to five seconds before the FDMMIM recognizes the switch.

1.

Attach the main ring cables to the optical bypass switch by inserting the A and B duplex connectors into their respective keyed receptacles on the optical bypass switch.

2.

Attach the small bypass cable connector at the FDMMIM Bypass receptacle. Figure 2-10 shows the bypass switch cable configuration.

3.

Attach the Type A and Type B duplex connectors at their respective FDDI receptacles (FDDI A and FDDI B) on the

FDMMIM front panel.

2-12


Enable-A

1

Enable-B 2

Ground

Ground

3

4

Bypass Present 5

Ground

6

Figure 2-10. Bypass Switch Cable Configuration

2.4

FDMMIM-04 AND FDMMIM-24 MASTER PORT CABLE

CONNECTIONS

The FDMMIM-04 and FDMMIM-24 have four M type concentrator ports. The FDMMIM-04 ports are fiber connections (keyed green), and the FDMMIM-24 ports are Unshielded Twisted Pair connections.

You can use these ports, to connect FDDI nodes, such as workstations, to the dual ring. You can also attach M ports to the A and B ports of another concentrator, to create a dual homing

(redundant concentrator) configuration (Refer to Appendix C, Basic

FDDI Networks, for additional information on dual homing).

2.5

TWISTED PAIR PINOUT CONFIGURATION

This section provides the RJ-45 pinout configuration for Unshielded

Twisted Pair (UTP) and Shielded Twisted Pair (STP) Physical Layer

Medium Dependent (PMD) ports. See Figure 2-11.

Note: When connecting two twisted pair ports together (e.g., an M type port on an FDCMIM-24 to an F7069 Desktop Network Interface

(DNI) card.), a transmit and receive cross-over must occur between the two devices (i.e., within the cable).

2-13


Pin 1

RJ-45 TP-PMD PORT

Contact

1

2

3

4

5

6

7

8

Signal

Transmit +

Transmit —

N/A

N/A

N/A

N/A

Receive +

Receive —

Caution: Ground only one end of an

STP segment. For Cabletron TP-PMD products, the port casing is grounded.

Figure 2-11. TP-PMD Port Pinouts

2.6

MASTER PORTS AND LANVIEW

Each master port has two LEDs — PST and LNK. These LEDs show the status of that M type port.

PST (PORT STATUS)

This multi-state LED can indicate the following:

Green The station attached to the port is connected to the network.

2-14


Amber

Red or

Flashing Red

LED off

Management has disabled this port.

The port has failed.

The port has no valid connector attached.

LNK (MEDIA LINK OK)

When ON, this green LED indicates that a connection exists between the M type port and the node at the other end of the port cable segment. To ensure you maintain the link, the port generates an idle signal when not transmitting data.

2.7

FDMMIM AND LANVIEW

LANVIEW gives you a window into the physical layer of your network. The FDMMIM has two sets of system/bridge LEDs. One set indicates activity on the Ethernet side of the bridge, the other set of

LANVIEW LEDs shows FDDI information.

2.7.1 Ethernet LEDs

Figure 2-11 shows the six Ethernet LEDs, identified as ‘ENET,’ on the front panel of the FDMMIM.

ENET

FDDI

PWR

TWR

XMT

STBY

SYOK

XMT

RCV

RCV

WRP

CLN

ROP

POK

Figure 3-2. Ethernet

Figure 2-11. LANVIEW Ethernet LEDs

2-15


STBY (STANDBY)

When ON, this amber LED indicates that the FDMMIM is in

Standby mode. During power-up with STA disabled, the FDMMIM is in Standby mode for approximately 15 seconds, learning addresses, before going on line. During power-up with STA enabled, the bridge progresses through the Listening state (sending and receiving

BPDUs), the Learning state (learning network addresses), and then into the Forwarding state (receiving and forwarding data frames).

When the bridge goes to the Forwarding state, the STBY light is turned OFF. STBY remains ON, and the bridge remains in the

Learning state, if there is at least one other parallel bridge in the network serving as the root bridge.

SYOK (SYSTEM OK)

When ON, this green LED indicates that the FDMMIM has passed all self tests.

XMT (TRANSMIT)

When ON, this green LED indicates that the bridge is transmitting traffic to the Ethernet network. On a network with average traffic, the XMT LED normally flashes.

RCV (RECEIVE)

When ON, this amber LED indicates that the bridge is receiving

Ethernet traffic. On a network with average traffic, the RCV LED normally flashes.

CLN (COLLISION)

This red LED flashes when the bridge detects a collision or a jabber packet on the Ethernet network.

POK (PORT OK)

When ON, this green LED indicates that the FDMMIM has passed all of its Ethernet power-up diagnostic tests.

2-16


2.7.2 FDDI LEDs

Figure 2-12 shows the six FDDI LEDs on the front of the FDMMIM.

ENET

FDDI

PWR

TWR

XMT

RCV

WRP

ROP

STBY

SYOK

XMT

RCV

CLN

POK

Figure 2-12. LANVIEW FDDI LEDs

PWR (POWER)

When ON, this green LED indicates that the FDMMIM is receiving power from the MMAC.

TWR (TWISTED RING )

When ON, this red LED indicates an undesirable cable connection.

TWR illuminates when you connect A to A or B to B instead of A to B and B to A. The FDMMIM supports undesirable configurations.

(Appendix C summarizes FDDI connection rules.)

XMT (TRANSMIT)

When ON, this green LED indicates that the FDMMIM is transmitting traffic to the FDDI network. On a network with average traffic, the XMT LED normally flashes.

RCV (RECEIVE)

When ON, this amber LED indicates that the FDMMIM is receiving

FDDI traffic. On a network with average traffic, the RCV LED normally flashes.

2-17


WRP (WRAP)

This red LED illuminates when the FDMMIM detects an FDDI ring wrap, meaning that there is a break in the ring, and the system has combined the primary and secondary rings into one ring.

ROP (RING OP)

When ON, this green LED indicates that the Token Claim Process has completed successfully and the FDDI ring is operational.

2-18

CONNECTING TO LOCAL MANAGEMENT

CHAPTER 3


Out-of-band management for the FDMMIM is called FDMMIM Local

Management. You can access this management tool by connecting a terminal to the FDMMIM. This chapter explains:

• Connecting to Local Management with a terminal

• Logging-in to Local Management

• Monitoring the power-up diagnostic tests

• Manually resetting the FDMMIM.

3.1

CONNECTING A CONSOLE

Access LM through the RJ-45 CONSOLE port on the FDMMIM front panel. This port supports asynchronous communication through a

Digital Equipment Corporation (DEC) VT220 or VT320 terminal, or a PC emulation of one of these terminals.

A Console Cable Kit, included with your FDMMIM, contains cables and adapters to connect the RJ-45 CONSOLE port to another RJ-45 port, a DB-9 port, or a DB-25 port of a terminal. Figure 3-1 shows the pin configuration required for the console port.

You must properly configure your terminal to communicate with

Local Management. The following list provides the necessary setup information for a VT220 or VT320 terminal. For more detailed setup information, the keyboard map, or information on setting up a PC emulation, refer to your specific terminal manual.

3-1


If you have a VT220 or VT320 series terminal, press F3 (Set-Up) to access the Setup Directory and set the options as follows:

Display Set-Up Menu

Columns

Controls

Auto Wrap

Text Cursor

General Set-Up Menu

Mode

80 Columns

Interpret Controls

No Auto Wrap

No Cursor

Cursor Keys

VT220, 7 Bit Control

VT320, 7 Bit Control

Normal Cursor Keys

Communications Set-Up Menu

Transmit Transmit = 9600

Receive

XOFF

Receive = Transmit

XOFF at 64

Bits Parity

Stop Bit

Local Echo

Port

Transmit

Auto Answerback

8 Bits, No Parity

1 Stop Bit

No Local Echo

VT220 — EIA Port, Data Leads Only

VT320 — DEC-423, Data Leads Only

Any option

No Auto Answerback

Keyboard Set-Up Menu

Keys

Auto Repeat

Keyclick

Margin Bell

Warning Bell

Typewriter Keys

Any option

Any option

No Margin Bell

Warning Bell

3-2


FDDI

C

O

N

S

O

L

E

1

4

5

6

7

8

2

3

CONSOLE PORT

Pin 1 Transmit data (XMT) from CONSOLE port

Pin 2 Data set ready (DSR) to CONSOLE port

Pin 3 Not used

Pin 4 Receive data (RCV) to CONSOLE port

Pin 5 Signal ground (GND)

Pin 6 Data terminal ready (DTR) from CONSOLE port

Pin 7 Not used

Pin 8 Not used

Figure 3-1. CONSOLE Port Pin Configuration

To access Local Management:

1.

Using the components of the Console Cable Kit, connect the

RJ-45 end of the RS-232 cable to the port labeled CONSOLE on the FDMMIM.

2.

Connect the other end of the RS-232 cable into the COMM port on the terminal or a communication port on a PC. The

Console Cable Kit contains adapters to connect to either a

DB-9 or DB-25 port.

3.

Turn on the terminal. After it warms up, press the RETURN key. If you are connecting to a PC, load and run the terminal emulation software. Start the program and press RETURN.

3-3


Note If you turn on the FDMMIM while you are viewing Local

Management, you first see the FDMMIM power-up diagnostics, and then the Password screen appears. If the FDMMIM is already on, the

Password screen appears.

4. Enter your password. (The default password is the RETURN key. Section 6.2, The Community Names Table Screen, explains how to change your password.)

5. Press the RETURN key. The System Information screen appears. The System information screen is the starting point for all Local Management functions.

3.2

POWERING-UP THE FDMMIM: DIAGNOSTIC TESTS

When you turn on the power to the MMAC, or press RESET on the

FDMMIM front panel, the FDMMIM runs thirteen diagnostic tests.

If your Local Management console is on, the FDMMIM displays the results of each test. If a test fails, Local Management stores that result in the Message Log. If any test fails, you should contact

Cabletron Systems Technical Support. Here is a brief description of each FDMMIM diagnostic test.

CHECKSUM TEST

When you power-up the FDMMIM, the code downloads from Flash memory to local RAM memory. While downloading, the FDMMIM adds up all of the bytes of code and saves them as a 32 bit checksum.

The checksum test essentially compares this calculated 32 bit checksum with the factory embedded checksum. Any difference between the two sums flags the code as corrupted, and the test fails.

LOCAL RAM/SHARED RAM TESTS

The FDMMIM generates an extensive series of data patterns to fully test the on-board memory chips.

3-4


FDDI PORT A/B TESTS

When the FDMMIM transmits or receives frames via the primary or secondary FDDI network ring, the frames must pass through the

FDMMIM A or B ports. The FDDI A and B tests check the hardware components that control communications through the FDMMIM A and B ports. No signals are transmitted to the network dual ring.

FNB TEST

FNB is the Flexible Network Bus, the data pathway within the

MMAC hub. This test checks the FDMMIM hardware components that handle communications with the FNB. No signals are actually transmitted to the FNB.

FDDI TESTS

After a frame enters the FDMMIM Port A, Port B, or the FNB, it enters the Media Access Control (MAC) circuitry. The FDDI tests (1,

2, 3, and Loopback) check the FDMMIM internal data paths.

ETHERNET PORT SELF TEST

This test checks the internal data paths used by a frame that enters the FDMMIM through the Ethernet port. This test does not transmit any signal onto the network.

HARDWARE FILTER TEST

The bridge filter functions are rooted in hardware components to maximize bridge performance. The hardware filter test checks these filtering components.

INLINE FILTER TEST

When the inline filter receives frames on the FDDI port that require filtering, it uses the other FDMMIM filtering components to accomplish the task. This test generates several frames to test the filtering function of the hardware components.

3-5


3.3

MANUALLY RESETTING THE FDMMIM

In the event your device is not operating properly, or you want to clear and reload RAM with the code in FLASH memory, you may want to reset the FDMMIM. To accomplish this:

1) Take a paper clip (the 2 inch type works best).

2) Bend one length so that it sticks out. (See Figure 3-2.)

3) Press the straightened paper clip end into the RESET hole at the top of the FDMMIM front panel.

After depressing the microswitch in the RESET hole, the FDMMIM:

• Ceases operation

• Clears the contents of RAM

• Downloads the code in FLASH memory to RAM

• Runs its power-up diagnostic tests.

Resetting the FDMMIM has the same effect as turning the MMAC power off and on, except that it does not affect any of the other modules in the MMAC.

FDMMIM

SN

RESET

STBY

?

XMT

RCV

WRP

?

STBY

SYOK

XMT

RCV

CLN

POK

Figure 3-2. Resetting the

FDMMIM

3-6

GETTING STARTED WITH FDMMIM/LM

CHAPTER 4

GETTING STARTED WITH FDMMIM

LOCAL MANAGEMENT

This chapter explains:

• Format conventions used in this manual

• The organization of Local Management screens

• Screen header fields, and what special header fields exist in certain Local Management screens

• Local Management default values, and where you can change these values.

4.1

UNDERSTANDING THE SCREENS AND COMMANDS

Local Management lets you control FDMMIM bridge parameters and ports of adjacent FDDI modules. To change a setting:

• Open the appropriate screen

• Highlight a field

• Type in the new information, or use the RETURN key to toggle between available field choices.

Local Management screens displayed in this manual use the following format conventions:

• Menu choices and commands appear UPPER CASE BOLD.

Note: Fully underlined words indicate a title or category.

They are not menu choices or commands.

• Fields that you can alter appear shaded.

4-1


4.2

USING THE MANAGEMENT KEYBOARD

Use the keyboard arrows (up, down, left, and right) to highlight a command or field (you can only highlight changeable fields). Local

Management rejects an incorrect entry, and displays a message that explains the problem. (Refer to Appendix A for explanations of specific Warning and Error Messages.)

To make a menu selection:

• Highlight the menu selection, and then press the RETURN key on the keyboard.

To alter a field:

• Highlight the field, type the new information, and then press the RETURN key on the keyboard.

To toggle a field (choose an alternate selection for a field):

• Highlight the field, and then press the RETURN key on the keyboard until the selection you want appears.

Note: When you make changes to screen fields, be sure to execute the

SAVE command before you exit from the screen.

Here are a few navigation hints to remember.

• The TAB key performs the same function as the right arrow.

• Backspace permits correction of entries.

• Most screens present RETURN as a command selection to return to the previous screen. RETURN is normally highlighted as the default command choice in a screen.

4.3

NAVIGATING THROUGH LOCAL MANAGEMENT

The first screen you see after you log on to Local Management is the

SYSTEM INFORMATION screen. The SYSTEM INFORMATION screen is the main menu and starting point for all other screens and commands. Figure 4-1 shows the organization of Local Management.

4-2


PASSWORD SCREEN Access FDMMIM Local Management screens.

SYSTEM INFORMATION View FDMMIM status and network activity; Access all major LM screens.

MESSAGE LOG History log showing warning and error messages reported by LM.

NETWORK TRAFFIC Ethernet and FDDI packet counters. Editing limited to resetting counters.

FDDI CONFIGURATION Display and control FDDI modules within the hub.

FILTERING DATABASE Display/Create/Delete acquired and permanent database entries.

SPECIAL DATABASE Store up to 10 additional filter entries.

BRIDGE PROTOCOL Set Spanning Tree Algorithm bridge parameters.

BRIDGE PORT PARAMETERS View port-specific parameters; Adjust Port Priority/ Path Cost.

RING MAP View logical map of active FDDI addresses.

NODE INFORMATION View parameters for individual nodes on the FDDI ring.

SETUP Set FDMMIM operating parameters; Enable or disable bridge; Reset databases.

COMMUNITY NAMES Set permission levels for local and remote access.

TFTP DOWNLOAD Set conditions for updating

LM firmware.

TRAP TABLE Send trap information to specific

IP addresses.

Figure 4-1. FDMMIM Local Management Structure

4-3

4.4

SCREEN ORGANIZATION


Note: Other chapters that refer to specific screens do not repeat this information.

Appearing in All Screens

Date and time displays the FDMMIM date and time. To change the date and time, go to the Setup screen.

Title describes the screen purpose, such as SETUP, or the type of information that the screen provides, such as NETWORK TRAFFIC.

Just below the title line is an unlabeled blank line called the

Message Bar. The Message Bar is empty unless Local Management is displaying a message, warning, or error. (Chapter 5, Using the

Information Screens, describes Messages, Warnings, and Errors in detail. Appendix A explains each Local Management Warning and

Error.) The Message bar display remains on the screen for a short period and then disappears. (You can edit the Message Bar display duration in the Setup screen.) All Error and Warning messages not relating to station management are saved in the Message log.

Appearing in Most Screens

The Ethernet Address is a unique factory set address for the

FDMMIM Ethernet Port, shown in canonical format.

The FDDI Address is a unique factory-set address for the

FDMMIM’s FDDI port, shown in MAC format.

Uptime shows the elapsed time since the bridge was last turned on

(MMAC power cycled) or restarted using the RESET button.

Ring State indicates the status of the FDDI ring. The possible ring state conditions are:

Ring-Op

Isolated

Non-Op

The ring is functioning correctly.

The bridge is not attached to the ring.

The bridge is attempting to enter the ring.

4-4

Detect

Non-Op-Dup

Ring-Op-Dup

Directed

Trace


The claim (beacon) process of the

FDDI ring protocol has exceeded 1 second. There may be a problem.

The ring failed to complete the claim

(beacon) process. This usually indicates a duplicate FDDI address.

The ring is operational, but a duplicate FDDI address may be present somewhere on the network.

The claim (beacon) process did not complete within 10 seconds. The bridge is sending directed beacons to indicate a problem.

A problem has been detected with the

FDMMIM or its nearest upstream neighbor. A trace is being sent to notify the nearest upstream neighbor of the problem.

Status/Bridge Status indicates the current status of the FDMMIM.

Three potential status conditions could appear in this field:

On-Line

Standby

Disabled

The FDMMIM is fully operational.

In Standby with STA enabled, the

FDMMIM bridge is learning address information but is not forwarding frames. Standby usually indicates that the bridge is not the root bridge in a parallel bridge network.

The bridge is disabled (refer to Setup screen, ENABLE/DISABLE command). While disabled, the bridge is not learning address information and no traffic is being forwarded.

4-5


Appearing in the System Information Screen Only

FW Version refers to the version of Local Management software currently installed on the FDMMIM. The Local Management software is stored in FDMMIM FLASH memory. FLASH memory allows you to download new software using the FDMMIM/LM TFTP

Download screen or a remote management tool such as Cabletron

Systems Remote LANVIEW/Windows.

The IP Address is the Internet Protocol address. The default is

0.0.0.0. You can edit the IP address in the Setup screen.

Message Log displays how many Errors the Message Log currently holds. If the Message Log contains any Errors, the Message Log field blinks.

Caution: Errors are the most severe class of message. They usually indicate a hardware malfunction or some condition impacting network service.

Appearing in the Setup Screen Only

Bridge Name, a changeable text field, shows the user-assigned name for the bridge. The bridge name helps a network manager identify the bridge using a remote management tool. The default bridge name is Cabletron Enet - FDDI Bridge.

Location, a changeable text field, shows a user-defined description of the bridge’s physical location. The Location helps a network manager identify bridge location using a remote management tool.

The default location is Local.

Last Reset provides the date and time the FDMMIM was last reset.

Restarts provides the number of times the FDMMIM has experienced a restart/power cycle since its battery was enabled.

4.4.2 Data Sections and Command Menus

Each Local Management screen contains data and commands specific to the function of that screen. Refer to specific screen chapters for detailed data and command information.

4-6


4.5

SETTING FDMMIM OPERATING PARAMETERS

Tables 4-1 and 4-2 list, in alphabetical order, each changeable

FDMMIM parameter. In addition, the tables also provide the default setting, allowed range, and name of the Local Management screen where you can edit the parameter.

The parameters in Table 4-1 all reset to their default values when you execute the RESTORE DEFAULT SETTINGS command in the

Setup screen. The parameters in Table 4-2 remain unchanged when you restore defaults.

Parameter

Bridge Forward Delay

Bridge Hello Time

Bridge Max. Age

Bridge Name

Default (Range) Edit Screen

15 seconds (4 to 30 sec.) Bridge Protocol



Bridge Priority

Chassis Type

Dynamic Ageing Time

Port Name

Port Priority

Cabletron Enet-FDDI

Bridge (up to 32 chars.)

Setup

8000 (0 to FFFF) Bridge Protocol

MMAC 8 (MMAC 3, 5, 8) Setup

300 seconds

(10 to 1000000 sec.)

Slot 2 (Slot 2 through 8)

Filtering

Database

Setup FDMMIM Slot Location

Location Local (up to 32 chars.) Setup

Message Duration Time 2 seconds (1 to 999 sec.) Setup

Net Name LAN_1 (up to 32

LAN_2 chars.)

Setup

Path Cost Enet Port - 100 (1 to 65535) Bridge Port

FDDI Port - 10 (1 to 65535) Parameters

Ethernet Port (up to 32

FDDI Port chars.)

Setup

Enet port - 80 (0 to FF) Bridge Port

4-7


Screen Refresh Time

Type of STA Protocol

FDDI port - 80 (0 to FF) Parameters

2 seconds (1 to 999 sec.) Setup

802.1 (802.1, DEC, None) Setup

Parameter

Community Names

Date

IP Address

Password

Subnet Mask

Time

Table 4-1. FDMMIM Defaults

Default (Range) Edit Screen

Basic Read - public

Read Only - public

Read Write - public

Superuser - RETURN key

(up to 32 chars.)

Community

Names

None (MM/DD/YY) Setup

0.0.0.0

(0.0.0.0 to 255.255.255.255)

Setup

RETURN key

(up to 32 chars.)

Community

Names

255.255.0.0

(0.0.0.0 to 255.255.255.255)

Setup

None (HH:MM:SS) Setup

Table 4-2. FDMMIM Defaults

4-8

USING THE INFORMATION SCREENS

CHAPTER 5

USING THE

INFORMATION SCREENS

This chapter concentrates on the data sections and command menus of the Local Management information screens. These screens provide status information on FDMMIM functions. This chapter includes data and command information on the following screens:

• System Information

• Network Traffic

• Ring Map

• Node Information

• Message Log

You can reset port counters and delete the message log, but you cannot edit any of the individual fields in the information screens.

5.1

THE SYSTEM INFORMATION SCREEN

The System Information screen is the first screen you see after you successfully log on to Local Management. This screen does not have any fields that you can update. It is strictly a status screen, an overview of general settings and network activity. However, the

System Information screen provides the starting point for access to all other FDMMIM/LM screen displays and commands.

Four blocks of data, NETWORK TRAFFIC, FDDI, FILTER

DATABASE, and BRIDGE PROTOCOL, make up the data section of the System Information screen. The title of each section is a part of the Command Menu, providing access to their associated screens.

(See Figure 5-1.)

5-1


04/02/94 08:43:18 SYSTEM INFORMATION FW Version: 3.00.00

Ethernet Address: 00-00-1D-06-F9-C2 Bridge Status: On-Line

FDDI Address: 00-00-B8-60-9F-C3 Uptime: 10 Days 12 Hours 23 Minutes

IP Address: 134.141.30.14 MESSAGE LOG: 22

NETWORK TRAFFIC FILTER DATABASE

Frames Received: 1257 Type of Filtering: IEEE

Frames Filtered: 1258 Dynamic Ageing Time: 300

Frames Forwarded: 1257 Dynamics: 7652

Frames Transmitted: 0 Statics: 1134

Frame Errors: 0

FDDI BRIDGE PROTOCOL

Ring State: Ring-Op Type of STA Protocol: 802.1

Ring Op Count: 1 Ethernet Port: FORWARDING

MAC Configuration: Through-A FDDI Port: FORWARDING

Tneg: 83 Bridge Priority: 8000

Tnotify: 30 Desig. Root: 80-00-00-00-1D-06-A4-D2

Master Port Count: 4

RING MAP SETUP EXIT

Figure 5-1. System Information Screen

5.1.1 NETWORK TRAFFIC Data

NETWORK TRAFFIC gives you a summary of frame activity since the last time the FDMMIM was reset or the counters cleared. Traffic statistics ignore frame type (Ethernet or FDDI). See section 5.2 for information on the Network Traffic screen.

The System Information screen provides the following NETWORK

TRAFFIC information:

Frames Received displays the total number of frames received by the FDMMIM at both the FDDI and Ethernet ports.

Frames Filtered displays the total number of frames that were not passed from one bridge port to the other because the frame’s destination was located on the same network as its source.

Frames Forwarded displays the total number of frames that have been forwarded from one network to the other (FDDI to Ethernet and Ethernet to FDDI).

5-2


Frames Transmitted displays the total number of frames transmitted by the FDMMIM (for example, Bridge Protocol Data

Unit (BPDU) frames, FDDI SMT frames, etc.).

Frame Errors is the total number of errors detected by the

FDMMIM at both ports. The individual errors that comprise this total are displayed in the Network Traffic screen.

5.1.2 FDDI Data

The System Information screen displays top level information about the FDMMIM FDDI concentrator. See Chapter 9, Controlling

Concentrator Modules and Ports, for information on the FDDI

Configuration screen. The System Information screen provides the following FDDI information:

Ring State shows the current ring state. Refer to Chapter 4,

Getting Started with FDMMIM/LM, for possible ring state conditions and their definitions.

Ring Op Count keeps track of the number of times the FDDI ring has initialized since the last time the FDMMIM was reset. If this number grows steadily, it means that the ring is unstable.

MAC Configuration describes the current configuration of the

MAC and physical layers of the A and B ports. Here are the possible port configurations:

Through-A

Note: Dotted line indicates unused path or connection.

The primary ring is connected to the

MAC (from PHY-A/Primary In to

MAC to Primary Out/PHY-B). The secondary ring is isolated from the

MAC (from PHY-B Secondary In to

PHY-A Primary Out).

THROUGH-A

PRIMARY

IN

FDDI-A

SECONDARY

OUT

MAC

PRIMARY

OUT

FDDI-B

SECONDARY

IN

5-3


Wrap-A PHY-A is wrapped via the MAC

(from PHY-A/Primary In to MAC to

Secondary Out/PHY-A). PHY-B is disconnected.

WRAP-A


PRIMARY

IN

FDDI-A

SECONDARY

OUT

MAC

PRIMARY

OUT

FDDI-B

SECONDARY

IN

Wrap-B


PHY-B is wrapped via the MAC (from

PHY-B/Secondary In to MAC to

Primary Out/PHY-B). PHY-A is disconnected.

WRAP-B

PRIMARY

IN

FDDI-A

SECONDARY

OUT

MAC

PRIMARY

OUT

FDDI-B

SECONDARY

IN

Isolated


Both PHY-A and PHY-B are isolated from the ring.

ISOLATED

PRIMARY

IN

FDDI-A

SECONDARY

OUT

MAC

PRIMARY

OUT

FDDI-B

SECONDARY

IN

5-4

Wrap-AB


PHY-B is connected to the MAC (from

PHY-B/ Secondary In to MAC to

Primary Out/PHY-B). PHY-A is wrapped Primary In to Secondary

Out), isolating PHY-A from the MAC.

WRAP-AB

PRIMARY

IN

FDDI-A

SECONDARY

OUT

MAC

PRIMARY

OUT

FDDI-B

SECONDARY

IN

Tneg (Time Negotiated) is the negotiated token rotation time (in milliseconds) that devices on the ring establish through the token claiming process.

Tnotify is the interval (in seconds) at which an FDMMIM transmits

Neighbor Information Frames (NIFs). The station uses NIFs to periodically announce its address and basic station description.

Master Port Count shows the number of available M type ports.

5.1.3 FILTER DATABASE Data

The FILTER DATABASE section of the System Information screen describes the Acquired and Permanent Database. In addition, this screen provides access to the Filter Database screen, Create Filter

Entry screen, Delete Filter Entry screen, and Special Database screen. The FILTER DATABASE section of the System Information screen displays the following information:

Type of Filtering is IEEE, Special, or Both. The bridge reads each packet’s source address and adds it to the Acquired Database (if it is not already there). Next, the bridge checks the packet’s destination address to determine whether or not to forward the packet.

5-5


Dynamic Ageing Time is the length of time that the Acquired

Database retains an address before purging it. You can set the

Dynamic Ageing Time in the Filter Database screen to any value between 10 and 1 million seconds.

Dynamics are those addresses that the bridge learns from network traffic. The FDMMIM does not retain Dynamic entries in its memory, in the event it loses power, is turned off, or is reset.

Statics are addresses that the FDMMIM copies from the Permanent

Database to the Acquired Database when the Acquired Database initializes. Static entries remain in memory when the FDMMIM loses power, is turned off, or is reset.

5.1.4 BRIDGE PROTOCOL Data

The BRIDGE PROTOCOL section of the System Information screen describes the Spanning Tree Algorithm (STA). This section also provides access to the Bridge Protocol screen and Port Parameters screen where you can edit the Spanning Tree settings.

STA is the method that bridges use to decide which bridge is the controlling (Root) bridge when 2 or more bridges exist in parallel.

You can control STA through the Setup screen and the Bridge

Protocol screen.

The following lists information in the BRIDGE PROTOCOL section:

Type of STA Protocol choices (IEEE 802.1, DEC, or None). You can select the STA protocol type in the Setup screen. (Default =

IEEE 802.1.)

Caution: All bridges in a network must use the same Spanning Tree protocol. The 802.1 and DEC protocols have unique formats for their

Bridge Protocol Data Units (BPDU). Trying to mix STA protocols results in an unstable network.

5-6


Ethernet Port and FDDI Port display the port state of the respective bridge ports. The possible port states include:

DISABLED

LEARNING

LISTENING

FORWARDING

BLOCKING


No traffic can be received or forwarded while the port is disabled.

The bridge is learning network addresses. The bridge enters the

Learning state when the Acquired

Database is being created (during start-up or after being deleted), or when the Spanning Tree Algorithm detects a network topology change.

The bridge is not adding information to the Filtering Database. The bridge is monitoring BPDU traffic while preparing to move from the Learning to the Forwarding state.

The bridge is on-line and this port is forwarding traffic.

The port will not forward any traffic through the bridge.

Bridge Priority displays the part of the bridge address containing the identifier. Spanning Tree uses this identifier for priority comparisons. You can adjust the bridge priority in the Setup screen.

The lower the number, the higher the priority. (Default = 8000.

Allowable range = 0 - FFFF.)

Desig. Root displays the unique bridge identifier for the bridge that is assumed to be the Root. The bridge identifier value is computed from the bridge’s address and its bridge priority value.

5-7


5.1.5 System Information Screen Commands

The System Information screen is the starting point for any activity in Local Management. The System Information screen contains the following commands:

MESSAGE LOG opens the Message Log screen to display all messages, warnings, and errors reported by Local Management. The

Message Log can hold up to 10 messages. Editing is limited to deleting all existing log entries.

NETWORK TRAFFIC opens the Network Traffic screen to display information about both the Ethernet and FDDI bridge ports. This screen provides a complete breakdown of the data displayed in the

NETWORK TRAFFIC section of the System Information screen.

Editing is limited to resetting the counters.

FDDI opens the FDDI Configuration screen to display a graphic representation of the FDDI concentrator ports, including other FDDI concentrator modules (FDCMIMs) that reside in adjacent MMAC slots. The FDDI Configuration screen lets you enable and disable concentrator modules and individual M type ports.

FILTER DATABASE gives access to the screen where you display entries in the Acquired, Permanent, and Special Databases.

BRIDGE PROTOCOL gives access to the Bridge Protocol and Port

Parameters screens, where you control the Spanning Tree Algorithm operational parameters.

RING MAP displays a graphic representation of the FDDI ring topology. The map shows the address, device type, and cable configuration of each station on the ring. The RING MAP screen also provides access to a NODE INFORMATION screen for each device on the ring.

SETUP is where you set general bridge configuration parameters.

This screen also provides access to the Community Names Table screen, Trap Table screen, and TFTP Code Download Setup screen.

EXIT ends the Local Management session, and returns you to the

Password screen.

5-8


5.2

THE NETWORK TRAFFIC SCREEN

The Network Traffic screen provides a detailed breakdown of the information provided in the Network Traffic section of the System

Information screen.

Below the header information (described in Chapter 4), the Network

Traffic screen data section shows frames and error counts for both the Ethernet port and the FDDI port.

To display the Network Traffic screen:

• Highlight the NETWORK TRAFFIC command in the System

Information screen, and press RETURN.

04/02/94 08:43:23 NETWORK TRAFFIC

Ethernet Address: 00-00-1D-06-F9-C2 Ring State: Ring-Op

FDDI Address: 00-00-B8-60-9F-C3 Status: On-Line

ETHERNET FDDI

% FRAMES % BRIDGE MGMT SMT

Received 204451 1728 0 0

Filtered 53 109214 100 1728 + 0

Forwarded 93134 0 0

Transmitted 2 71521 1846

Ethernet Exceptions FDDI Exceptions

Rx CRC 0 Rx Errors 0 0 0

Rx Overflow 0 Rx Overflow 0 0 0

Rx Oversize 0 Rx IP Frag Err 0 0 0

Rx Alignment 0

Tx Abort 0 Tx Abort 0 0

Tx Overflow 0 Tx Overflow 0 0

TX Collision 0 Tx Ring Down 27871 757

RETURN RESET COUNTERS

Figure 5-2. Network Traffic Screen

5-9


5.2.1 Network Traffic Screen Data

The Network Traffic screen displays the following:

Received shows the total number of frames received by the

FDMMIM at each bridge port. The totals include both data and

Bridge Protocol Data Unit (BPDU) frames.

Filtered shows the total number of frames NOT passed from one bridge port to the other, because the frame’s destination was located on the same network as its source. If a bridge port is not in the

Forwarding state, it filters all data frames it receives at that port.

A small plus sign (+) may appear just to the right of the FDDI filtered frame number for the FDDI bridge (see Figure 5-1). This sign indicates the FDMMIM software, while performing other functions, may have lost track of the total number of filtered frames. The

FDMMIM displays a continuation from the last “known” number of filtered frames. To clear the plus sign, reset the counters.

Forwarded shows the total number of frames forwarded from one network to the other (Ethernet to FDDI or FDDI to Ethernet).

Transmitted shows the total number of SMT and BPDU frames sent by the FDMMIM from each port.

Ethernet/FDDI Exceptions shows the total number of frames discarded by the bridge for any reason. The following describes exception frames further:

Rx CRC

(Ethernet only)

Rx Errors

(FDDI only)

Shows the number of frames received at the Ethernet port with a bad

Cyclical Redundancy Check (CRC) field. A frame with a bad CRC field usually indicates that the frame was damaged in transmission.

Combines the number of frames with a bad Cyclical Redundancy Check

(CRC) and misaligned packets received at the FDDI port.

5-10

Rx Overflow

Rx Oversized

(Ethernet only)

Rx IP Frag Err

(FDDI only)

Rx Alignment

(Ethernet only)

Tx Abort

Tx Collision

(Ethernet only)


Shows the number of frames lost due to a lack of buffer memory space. An overflow condition is usually due to a high traffic level and collision rate on the Ethernet network. The bridge’s buffer memory space fills while the bridge is waiting to make valid transmissions to the Ethernet or

FDDI LAN. The only remedy is reducing the collision rate on the

Ethernet LAN.

Shows the number of received frames that have more than 1,518 data bytes

(not including the preamble), the

IEEE 802.3 maximum.

Shows the number of frames the

FDDI port could not fragment for transfer to Ethernet. Possible causes:

• The frame was too large for unfragmented transfer, and was not using IP network protocol.

• Fragmentation was not allowed.

• The IP frame header failed its

checksum test prior to attempting

fragmentation.

Shows the number of misaligned frames received by the Ethernet port.

Shows the number of transmissions that were aborted because of a transmit error.

Shows the number of collisions detected at the Ethernet port.

5-11


Tx Overflow

Tx Ring Down

(FDDI only)

Shows the number of frames lost at transmission, due to a lack of transmit queue memory space. An overflow condition is usually due to a high traffic level and collision rate at the Ethernet interface, or a problem on the FDDI ring.

Shows the number of frames lost from the inability of the bridge to transmit frames onto a non-operating

FDDI ring.

5.2.2 Network Traffic Screen Commands

RETURN closes the Network Traffic screen, and returns you to the

System Information screen.

RESET COUNTERS sets all counters within the bridge to zero.

Note: When you reset the counters, you reset ALL Local Management counters to zero, including those displayed on the System Information screen. This also affects the information displayed by an SNMP remote management tool, since the FDMMIM is the source for MMAC

FDDI information.

5-12


5.3

THE RING MAP SCREEN

The FDDI Ring Map screen shows FDDI formatted addresses of ring stations in a graphic illustration of the FDDI ring topology, and provides access to a Node Information screen for each device.

To display the Ring Map:

• Highlight RING MAP in the System Information screen, and press RETURN.

04/02/94 08:44:34 FDDI RING MAP

Ethernet Address: 00-00-1D-06-F9-D6 Ring State: Ring-Op

FDDI Address: 00-00-B8-60-9F-EB Status: On-Line

Uptime: 10 Days 22 Hours 01 Minutes

FDDI Port: 00-00-B8-60-9F-EB Address Mode: MAC MAC Count: 3

00-00-B8-60-9F-EC (DAC) <<<<<<<<<<<<<<<<< (DAC) 00-00-B8-40-02-92

00-00-B8-C0-E1-F0 (DAS) >>>>>>>>>>>>>>>>^

RETURN CHANGE ADDRESS MODE SCROLL DOWNSTREAM 1 SCROLL UPSTREAM 1

Figure 5-3. FDDI Ring Map Screen

Under some conditions the display must remain on the screen for at least 30 seconds to accurately reflect ring configuration. A neighbor time-out can take as long as 228 seconds to update on the ring map.

5-13


5.3.1 Ring Map Screen Data

The FDDI Ring Map shows the address and sequence of each FDDI device attached to the ring. When first displayed, the station at the upper left corner of the ring is this station (FDMMIM). The screen displays node class, node address, and twisted and/or wrapped conditions (T for twisted and/or W for wrapped) in parentheses. The following lists the node class possibilities:

NAS

DAS

DAC

SAS

(Null Attached Station) Isolated station; station not connected to an

FDDI ring.

(Dual Attached Station) Station that does not support M ports, but connects directly to an FDDI primary and secondary ring using A and B ports.

(Dual Attached Concentrator) Station that supports M ports and connects directly to an FDDI primary and secondary ring using A and B ports.

(Single Attached Station) Station that accesses the main ring through a concentrator, creating a ring of trees topology.

SAC (Single Attached Concentrator)

Station that accesses the main ring through another concentrator and, in turn, allows the connection of more devices. SACs provide the same connections as DACs, without attaching to the dual ring.

While LM updates the map, for example, during a ring topology change, the screen shows ??-??-??-??-??-??

to illustrate an undetermined address. You cannot use the scroll commands until

LM finishes rebuilding the map.

Note: The Ring Map display stops at the first occurrence of an undetermined address, and does not display any known information beyond this point.

5-14


5.3.2 Ring Map Screen Commands

RETURN closes the Ring Map screen, and returns you to the


CHANGE ADDRESS MODE lets you switch between canonical or

MAC format addresses. The Address Mode toggles each time you execute this command.

SCROLL DOWNSTREAM n rotates the ring display, so that the station addresses shift around the ring in a clockwise direction. The

n controls the number of shifts upstream. If the Ring Map contains only one node, scroll commands are not displayed.

SCROLL UPSTREAM n rotates the ring display, so that the station addresses shift around the ring in a counterclockwise direction. The n controls the number of shifts upstream. If the Ring

Map contains only one node, scroll commands are not displayed.

5.3.3 Adjusting the Scroll Number (n)

When using the Scroll Upstream n or Scroll Downstream n commands, the n allows you to control the number of shifts made with each command execution.

Note: You need a minimum of four FDMMIMs or nodes to use this option.

To set the n:

1.

Using the Arrow keys, highlight the Scroll Upstream n or

Scroll Downstream n command.

2.

Press the shift and + keys (to increment), or the

-

key (to decrement), until the number of shifts you want appears.

3.

Press RETURN. The Ring Map scrolls n number of shifts.

The scroll number remains the same until you change it, or leave and re-enter FDMMIM Local Management.

5-15


5.4 THE NODE INFORMATION SCREEN

The Node Information screen provides information for each selected node on the FDDI Ring Map.

Note: The Node Information screen reflects node status at the time the node was selected. The Node Information screen does not change dynamically with network adjustments.

To display the Node Information screen:

• Highlight any node illustrated on the ring in the Ring Map screen, and press RETURN.

04/02/94 08:44:34 NODE INFORMATION




Selected Node

Address: 00-00-B8-60-9F-EC

Upstream Address: 00-00-B8-40-02-92

Node Class: DAS

MAC Count: 1

Non-Master Count: 2

Master Count: 0

Peer Wrap: NO

Unattached Conc: NO

Twisted A-A: NO

Twisted B-B: NO

Synchronous Service: NO

Rooted: YES

RETURN

Figure 5-4. Node Information Screen

The Node Information screen displays the following:

Address shows the address of the selected node.

Upstream Address shows the address of the node immediately upstream from the selected node.

5-16


Node Class shows the class (NAS, DAS, DAC, SAS, or SAC) of the selected node.

MAC Count shows the number of MACs (Media Access Controllers) physically housed in the selected node.

Non-Master Count shows the number of A and B ports on the selected node.

Master Count shows the number of master ports controlled by the selected node. This number includes any master ports on the selected node (i.e., FDMMIM-04) as well as the ports of all contiguous FDCMIMs that reside to the left of the selected node in the MMAC.

Peer Wrap indicates a wrapped condition in the selected node. A

Peer Wrap only occurs when a wrap A, wrap B, or wrap AB condition exists, and neither of the wrapped ports connects to an M port.

Unattached Conc (DAC only) indicates the selected node has no active A or B port.

Twisted A-A indicates the A port of the selected node connects to the A port of another node — an undesirable configuration. The

FDMMIM accepts undesirable configurations. (Appendix C summarizes FDDI connection rules.)

Twisted B-B indicates the B port of the selected node connects to the B port of another node — an undesirable configuration. The

FDMMIM accepts undesirable configurations. (Appendix C summarizes FDDI connection rules.)

Synchronous Service indicates the use of synchronous bandwidth by the selected node. Using synchronous service guarantees a certain percentage of the total FDDI bandwidth for real time applications (e.g., voice or video). This percentage is determined by the node and the Synchronous Bandwidth Allocation Protocol (SBA).

Rooted indicates the selected node does not have an active A or B port in tree mode. Tree mode occurs when one (and only one) end of a fiber link connects to an M port. This mode of connection exists within a concentrator tree.

5-17


5.5

THE MESSAGE LOG SCREEN

The FDMMIM displays messages, warnings, and errors as they occur but only for a short period of time. (You can adjust the message duration in the Setup screen.) LM records messages and warnings not relating to station management, and all errors, in the Message

Log. The log allows you to review messages, warnings, and errors at your convenience. The following describes each message type:

Message

Warning

Error

Another name might be confirmation message. After you perform an action, such as saving new parameters or deleting a database, Local

Management verifies that the action has taken place.

When you request an action that

Local Management cannot complete, a

Warning explains the problem. For example, if you enter text into a field that can only accept numeric data, a

Warning appears. Warnings can also indicate a problem that could affect some aspect of bridge operation, or eventually escalate into an error. For example, the FDMMIM produces a

Warning if it receives a BPDU that it cannot recognize.

An Error flags an occurrence that may cause an interruption in FDMMIM operation, possibly causing the

FDMMIM to reset.

The Message Log is non-volatile; the FDMMIM retains log entries even if you reset the FDMMIM or turn off the power. This function makes it possible to see the log recording of an error that caused the

FDMMIM to reset.

5-18


The Message Log can hold a maximum of 10 messages. After reaching the maximum limit, LM stops adding any new messages to the log until you delete the current log file.

To open the Message Log screen:

• Highlight MESSAGE LOG in the System Information screen, and press RETURN.

04/02/94 08:43:57 MESSAGE LOG

Total Messages: 10

# Date Time Message

10 07/04/94 08:43:11 WARNING: A-A connection accepted

9 07/04/94 08:43:00 MESSAGE: FDMMIM Selftest Complete

8 07/04/94 08:42:22 WARNING: A-A connection accepted


6 07/04/94 08:34:29 WARNING: M-M connection rejected

5 07/04/94 08:32:27 WARNING: B-B connection rejected

4 07/04/94 08:31:34 WARNING: Bridge restarting

3 07/04/94 08:31:23 WARNING: NO HARDWARE FILTER

2 07/04/94 08:30:01 WARNING: Bridge restarting


RETURN NEXT PREVIOUS DELETE

Figure 5-5. Message Log Screen

5-19


5.5.1 Message Log Data

The Message Log screen displays the following information:

Total Messages is a counter that indicates the number of entries currently held in the log. The log can hold up to 10 messages.

The Message Log screen displays up to 10 log entries. If more than

10 entries exist in the log, the Command Menu displays NEXT and

PREVIOUS commands, as appropriate, to let you page through the list. A log entry has four categories:

#

Date

Time

Message

Each log entry has a sequence number, with the most recent entry

(highest number) listed first.

The date of the log entry.

The time of the log entry.

The text of the Message, Error, or

Warning. Local Management highlights Errors by displaying them in bright blinking text.

See Appendix A for complete descriptions of each Local Management

Warning and Error message, along with probable causes and recommended actions.

5.5.2 Message Log Screen Commands

RETURN, the default selection, closes the Message Log screen and returns you to the System Information screen.

PREVIOUS and NEXT let you page through the Message Log. The screen displays a block of 16 entries at a time.

DELETE purges the Message Log. Choosing DELETE purges the list immediately. Local Management does not ask for you to confirm your choice.

5-20

SETTING UP THE FDMMIM

CHAPTER 6


This chapter explains the screens that let you customize FDMMIM default settings:

• Setup

• Community Names Table

• TFTP Code Download Setup

In addition to explaining the TFTP Code Download Setup screen, this chapter provides basic downloading instructions, and guidelines for setting up a UNIX workstation to handle an image file download.

6.1

THE SETUP SCREEN

The Setup screen is where you access the Community Names Table and TFTP Code Download Setup screens, and where you set the following general FDMMIM parameters:

• Bridge Name

• Location

• Port Name (Ethernet and FDDI ports)

• Network Name (Ethernet and FDDI)

• Message Duration Time

• Screen Refresh Time

• Date and Time

• IP Address

• Subnet Mask

• MMAC Chassis Type

• FDMMIM Slot Location

• Type of STA Protocol

6-1


To open the Setup screen:

• Highlight SETUP in the System Information screen, and press RETURN.

04/02/94 08:44:42 SETUP

Ethernet Address: 00-00-1D-06-F9-C2 Last Reset: 06/26/93 18:34:39

FDDI Address: 00-00-B8-60-9F-C3 Restarts: 19

Bridge Name: Cabletron Enet-FDDI bridge

Location: Local

Ethernet: FDDI:

Port Name: Ethernet port FDDI port

Net. Name: LAN_2 LAN_1

RESTART BRIDGE Message Duration: 2 Seconds

ENABLE BRIDGE DISABLE BRIDGE Set Refresh Time: 100 Seconds

RESTORE DEFAULT SETTINGS Set Date: 09/27/91

ERASE SPECIAL DATABASE Set Time: 08:44:42

ERASE ACQUIRED DATABASE Set IP Address: 0.0.0.0

ERASE PERMANENT DATABASE Set Subnet Mask: 255.255.0.0

Chassis Type: MMAC 8

FDMMIM Slot Location: SLOT 1

Type of STA Protocol: 802.1

RETURN COMMUNITY TABLE TRAP TABLE SAVE DOWNLOAD

Figure 6-1. Setup Screen

6.1.1 Setup Screen Data

The Setup screen contains the following information:

Last Reset indicates how long the FDMMIM has been running since the last power interruption. The Last Reset field defaults to the current date and time under the following conditions:

• MMAC power is cycled.

• The RESET button on the FDMMIM front panel is pressed.

• The Setup screen RESTART BRIDGE command is executed.

• The TFTP Code Download Setup screen COLD BOOT command is executed.

6-2

• A hardware problem causes the FDMMIM to reset itself.


Restarts is a counter that tracks the number of times that the

FDMMIM has been reset since the last time FDMMIM was poweredup. If this number grows steadily, it may indicate a hardware problem with the FDMMIM or the MMAC.

Bridge Name is a text field that shows an assigned name for the bridge. The Bridge Name helps to identify the bridge to someone using a remote management tool. (Default = Cabletron Enet - FDDI

Bridge. You can create a Bridge Name that contains up to 32 keyboard characters, including spaces.)

Location is a text field that shows an assigned description of the bridge location. The Location helps to identify the bridge to someone using a remote management tool. (Default = Local. A Location can contain up to 32 keyboard characters, including spaces.)

Port Name is a text field that shows the names assigned to the

Ethernet and FDDI ports. A Port Name helps identify a bridge port to someone using a remote management tool. (Defaults = FDDI Port

and Ethernet Port. You can create a Port Name that contains up to

32 keyboard characters, including spaces.)

Network Name is a text field that shows the names assigned to the

Ethernet and FDDI networks. A Net Name helps identify the network to someone using a remote management tool. (Defaults =

LAN_2 for the Ethernet network and LAN_1 for the FDDI network. A

Net Name can have up to 32 keyboard characters, including spaces.)

Message Duration sets the length of time (in seconds) that

FDMMIM/LM messages are displayed in the message bar in all

Local Management screens. (Default = 2. The allowable range is 1 -

999 seconds.)

Set Refresh Time sets the refresh rate for Local Management screens. This setting determines how frequently (in seconds) information is updated on the screen. (Default = 2. The allowable range is 1 - 999 seconds.)

6-3


Set Time/Date lets you enter the current time and date. Highlight the field and enter the date and time using the following formats:

Date - MM/DD/YY

Time - HH:MM:SS

(The default settings are indeterminate. The internal calendar and clock begin running as soon as you activate the FDMMIM battery during installation.)

Set IP Address shows the Internet Protocol address currently assigned to the bridge. You can set this field according to your network requirements. Highlight the Set IP Address field and enter the desired IP address using dotted decimal notation (4 decimal values between 1 and 255 separated by periods) as follows:

255.255.255.255

(Default = 0.0.0.0. 255 is the maximum number that can be entered in any of the four fields.)

Set Subnet Mask lets you define the portions of the received IP addresses that will be interpreted as network identifiers and the portions that will be interpreted as host identifiers. The default subnet mask uses the first two portions of the IP address to identify the net id, leaving the rest of the IP address to identify specific nodes. (Default = 255.255.0.0. 255 is the maximum number that can be entered in any of the four fields.)

Chassis Type is a toggle field that lets you define, to Local

Management, the type of MMAC that holds the FDMMIM. The setting of this field determines the MMAC image presented in the

FDDI Configuration screen. (Default = MMAC 8. The available toggle choices are MMAC 8, MMAC 5, and MMAC 3.)

6-4


FDMMIM Slot Location is a toggle choice that lets you define, to

Local Management, the MMAC slot location of the FDMMIM.

(Default = SLOT 2. Slot 1, the farthest right MMAC slot, houses only half-width management modules. Available toggle choices depend on the Chassis Type field setting. If Chassis Type = MMAC 8, the choices

= Slot 2 to Slot 8. If Chassis Type = MMAC 5, the choices = Slot 2 to

Slot 5. If Chassis Type = MMAC 3, the choices = Slot 2 or Slot 3.)

When you enter the correct Chassis Type and FDMMIM Slot

Location, the FDDI Configuration screen illustrates the appropriate

MMAC, with the FDDI MIMs shown in their true locations.

The Chassis Type and FDMMIM Slot Location fields have no affect on FDMMIM operation; they only enhance the FDDI Configuration screen display. If you have Chassis Type and Slot Location set to an impossible configuration, the chassis type takes precedence over the

Slot Location. For example, if you have your FDMMIM physically installed in Slot 4 of an MMAC 8, but you have Chassis Type set to

MMAC 3, the FDDI Configuration screen depicts an MMAC 3, with the FDMMIM in the slot 2 default position.

Type of STA Protocol lets you choose the type of Spanning Tree

Protocol employed by the bridge. (Default = 802.1. Available toggle choices are IEEE 802.1, DEC, and None.)

Caution: All network bridges must employ the same type of

Spanning Tree Protocol. Mixing protocols results in an unstable network.

6-5


6.1.2 Setup Screen Commands

The Setup screen contains the following commands:

RESTART BRIDGE simulates turning the bridge off and on. The

FDMMIM:

• Deletes the Acquired database

• Executes all of its self-tests

• Increments the Restarts counter.

After you select RESTART BRIDGE, and press the RETURN key,

Local Management requests confirmation before executing the command.

ENABLE BRIDGE enables the bridging function of the FDMMIM.

DISABLE BRIDGE lets you disable the bridge function of the

FDMMIM. The FDMMIM still functions as an FDDI DAS or DAC, but does not pass data between the two bridge ports.

Note: Disabling and then enabling the bridge with STA running, causes STA to start over in Listening mode. See section 5.1.4,

BRIDGE PROTOCOL Data, for additional information.

ERASE SPECIAL DATABASE erases all special database entries.

(See Chapter 8, The Filtering Databases, for additional information regarding the Special Database.)

ERASE ACQUIRED DATABASE erases all acquired database entries. (See Chapter 8, The Filtering Databases, for additional information regarding the Acquired Database.)

ERASE PERMANENT DATABASE erases all permanent database entries. (See Chapter 8, The Filtering Databases, for additional information regarding the Permanent Database.)

RESTORE DEFAULT SETTINGS restores the default values to all FDMMIM operating parameters. Table 4-1 summarizes the

FDMMIM/LM default settings. After you select RESTORE

DEFAULT SETTINGS, and press the RETURN key, Local

Management requests confirmation before executing the command.

6-6


RETURN closes the Setup screen and returns you to the System

Information screen. If you choose RETURN without saving changes, you lose any edits you made to Setup screen fields.

SAVE saves the setup information currently displayed.

6.2

THE COMMUNITY NAMES TABLE SCREEN

The Community Names Table screen allows you to set access privileges for local and remote management access to the FDMMIM.

The SUPER-USER community name acts as the Local Management password. BASIC READ/READ ONLY, and READ-WRITE/SUPER-

USER Community names provide different access privileges in remote management.

Note: Make sure to remember the SUPER-USER (SU) community name. This name acts as the ONLY Local Management password.

To open the Community Names Table screen:

• In the Setup screen, highlight COMMUNITY TABLE, and press RETURN.

04/02/94 08:43:23 COMMUNITY NAMES TABLE




Community Names Access

public BASIC READ

public READ ONLY

public READ-WRITE

super SUPER-USER

Please Note: SU names are local Passwords

RETURN SAVE

Figure 6-2. Community Names Table Screen

6-7


6.2.1 Community Names Table Data

The FDMMIM has four remote access levels:

READ ONLY

BASIC READ

You may view, but not alter, any agent accessible data. At this time,

BASIC READ and READ ONLY have identical access privileges. In future implementations of Local

Management, views will be defined within the FDMMIM’s Management

Information Bases (MIBs) that are specific to each access level.

READ-WRITE

SUPER-USER

You may view and alter agentaccessible data. At this time, READ-

WRITE and SUPER-USER have identical operation privileges. In future implementations of Local

Management, views will be defined within the FDMMIM’s MIBs that are specific to each access level.

To control remote access to the FDMMIM, edit the Community

Names list. Each of the four Community Names is a password that you must enter into a remote access tool before it can gain access to the FDMMIM information and management functions. By default, the Community Name public has READ-WRITE access.

To edit a Community Name:

1.

Highlight one of the four Community Names.

2.

Type the new name, and then press the RETURN key.

3.

Execute the SAVE command.

6-8


6.2.2 Community Names Screen Commands

RETURN closes the Community Names Table screen, and returns you to the Setup screen.

SAVE saves the information currently displayed on the Community

Names screen.

6.3

TFTP CODE DOWNLOAD SETUP SCREEN

The FDMMIM/LM software resides in a FLASH EEPROM, which means that you can update the software via Trivial File Transfer

Protocol (TFTP). The TFTP Code Download Setup screen lets you define the location of the system that holds the download file and direct the download to place the new code into the FDMMIM’s RAM, the FLASH EEPROM, or both. (Refer to section 6.4, Image File

Download with UNIX, or to your specific remote management documentation for downloading instructions/guidelines.)

To open the TFTP Code Download screen:

• Highlight DOWNLOAD from the Setup screen command menu, and press RETURN.

04/02/94 08:43:23 TFTP CODE DOWNLOAD SETUP

Force Download: NO

Commit Download to Flash: NO

Server IP Address 123.123.123.123

Filename: C:\PATH\TO\FILE\FDM.HEX

RETURN SAVE PARAMETERS COLD BOOT

FIGURE 6-3. TFTP Code Download Setup Screen

6-9


6.3.1 TFTP Code Download Setup Screen Data

The TFTP Code Download Setup screen has four fields:

Force Download is a YES/NO toggle selection. When set to YES, the downloaded code is loaded into the FDMMIM’s RAM, replacing the current FDMMIM/LM software. The download occurs the next time the FDMMIM is rebooted (reset).

Commit Download to Flash is a YES/NO toggle selection. When set to YES, the downloaded code is written into the FLASH

EEPROM, replacing the FDMMIM/LM software. The download occurs the next time the FDMMIM is rebooted (reset).

Server IP Address is the IP address of the networked server that holds the file to be downloaded.

Filename is a text field where you specify the pathname to and the file name of the new FDMMIM software. The Filename field can hold up to 69 characters.

6.3.2 TFTP Code Download Setup Screen Commands

RETURN closes the TFTP Code Download screen, and returns you to the Setup screen.

SAVE PARAMETERS saves the information currently displayed on the TFTP Code Download Setup screen.

COLD BOOT provides the option of rebooting your FDMMIM from

Local Management. (Refer to section 6.5.1, Forcing a Download

with FDMMIM/LM, for more information.)

6-10


6.4 IMAGE FILE DOWNLOAD WITH UNIX

Downloading an FDMMIM image file with a UNIX workstation requires 1) setting up a management station, and 2) forcing the download. You can use either FDMMIM/LM or the BOOTP switch to force the download.

Note: You can also download with other UNIX or DOS remote management packages. Refer to specific package documentation for image file download procedures.

Due to variations between UNIX systems, and individual configurations, this section provides only GUIDELINES for configuring a UNIX workstation to perform an image file download.

The instructions include command examples, where appropriate.

Bold lettering in examples indicates operator entry.

Caution: If unsure how to properly configure your UNIX workstation using these guidelines, contact your Systems Administrator or local

UNIX wizard.

Before you start:

• Editing ethers or hosts files requires Root/Superuser access.

• Downloading an image file requires setting up your UNIX workstation as a RARP server.

To set up a UNIX workstation:

1.

Edit the /etc/ethers file by adding the FDMMIM Ethernet address, followed by a unique name (e.g., 00:00:1d:12:12:ce fdm).

Note: Colons replace dashes in the ethernet address.

2.

Edit the /etc/hosts file by adding the FDMMIM IP address and follow it with the same unique name you used in step #1 (e.g.,

132.177.118.24 fdm).

6-11


3.

If you already have a /tftpboot directory, confirm the RARP setup of your workstation as follows:

Request a process status and grep for rarpd

(e.g., unix% ps -aux | grep rarpd). The following information represents a typical output: user 161 7.7 1.2 32 184 p3 S 12:00 grep rarpd root 87 0.0 0.9 48 136 ? S 11:05 rarpd -a root 88 0.0 0.0 24 0 ? IW 11:05 rarpd -a

The term rarpd -a, located at the end of the root string, indicates rarp is active. If rarp is not running, only the grep process appears.

4.

If you do NOT have a /tftpboot directory, then you must create one (e.g., unix% mkdir tftpboot), and start the rarp daemon

(e.g., unix% rarpd -a).

5.

Ensure that the /tftpboot directory is not owned

(e.g., unix% chown nobody tftpboot).

6. Store the hex image file in the /tftpboot directory as fdm.hex.

Note: This step requires decompression of the zipped image file. If you do not have a UNIX unzip utility, access to a PC with pkunzip, or a way to FTP the decompressed image to your UNIX workstation, contact Cabletron Technical Support.

7. Edit the /etc/inetd.conf file by removing anything prior to the tftpboot daemon (e.g., the # sign) that comments-out the line.

8. Kill the inetd process (e.g., unix% kill -HUP ‘process ID

number’), and then restart it (e.g., unix% inetd), to enable the revised inetd.conf file.

Note: You must request a process status and grep for inetd to obtain the process ID number (see step 3 above).

9. Force the download using either FDMMIM/Local Management, or the FDMMIM BOOTP switch.

6-12


6.5

FORCING AN IMAGE FILE DOWNLOAD

The following two sections provide instructions / guidelines on how to force the download of an image file after setting up your management station.

Note: You can also force a download with other UNIX or DOS remote management packages. Refer to specific package documentation for image file download procedures.

6.5.1 Forcing a Download with FDMMIM/LM

Use the following instructions to force a download through FDMMIM

Local Management.

Using a VT220/VT320 (or emulator), access FDMMIM/LM:

1. Highlight the Setup screen Download option and press Enter.

The TFTP CODE DOWNLOAD SETUP screen appears.

2. Highlight and set the following parameters on the TFTP CODE

DOWNLOAD SETUP screen:

Force Download: Yes

Commit to Flash: Yes

Server IP Address: IP address of management station

Filename: Path to management station

( for example, fdm.hex for UNIX)

4. Highlight the Save Parameters option and press RETURN.

5. Highlight the Cold Boot option, and press RETURN. The following message appears:

Rebooting FDMMIM. Are you sure? Yes No

6.

Highlight Yes, and then press RETURN.

Image file download takes several minutes. Following the download, access the FDMMIM/LM Message Log to ensure no CHECKSUM error occurred. If it has, repeat steps 1-6 again. If the CHECKSUM test continues to fail, contact Cabletron Technical Support. If the

CHECKSUM passes, you may use the FDMMIM.

6-13


6.5.2 Forcing a Download with BOOTP

In order to force a download using the BOOTP switch, you must remove the FDMMIM, and change the switch position.

To force a download using the BOOTP switch:

Note: We recommend powering-down your MMAC



before removing

FDMMIMs, even though these modules have “hot swap” capabilities.

1. Unscrew the knurled knobs at the top and bottom of the

FDMMIM front panel.

2. Slide the MIM out of the chassis until you can easily access the

FDMMIM switch panel located at the top of the mother board.

(See Figure 6-4.)

FDMMIM Switch Top of Module

Switch 7

6-14

ON 1 2 3 4 5 6 7 8

FDM 01.02.00

© CABLETRON 199X

CABLETRON SYSTEMS, INC. © PN 9000618-XX FDM-MIM REV: X MADE IN USA 199X

Mother Board

E

W

B

A

Top of Module

Figure 6-4. BOOTP Switch

3. Flip switch number seven (7) in one direction. For example, if the switch is in the ‘on’ position, switch it to the ‘off’ position and leave it there. This change in position activates

BOOTP after reinstalling the board.


Note: The FDMMIM boot PROM must recognize the switch position change to use BOOTP. This means, you must power-up the

FDMMIM at least one time (i.e., since taking it out of the shipping package), with its battery enabled, for the device to load initial switch positions into memory.

4. Slide the FDMMIM back into position.

5. Screw in the knurled knobs.

6. Power-up the MMAC.

Image file download takes several minutes. Following the download, access the FDMMIM/LM Message Log to ensure no CHECKSUM error occurred. If it has, repeat steps 1-6 again. If the CHECKSUM test continues to fail, contact Cabletron Technical Support. If the

CHECKSUM passes, you may use the FDMMIM.

6-15

SPANNING TREE

CHAPTER 7

SPANNING TREE

The Spanning Tree Algorithm (STA) is the method by which multiple bridges in a network coordinate their activities. This chapter explains how you can control FDMMIM participation in the network

STA operation. The two Local Management screens that affect

Spanning Tree activities are:

• Bridge Protocol

• Bridge Port Parameters

7.1

THE BRIDGE PROTOCOL SCREEN

The Bridge Protocol screen displays the current STA operating parameters and lets you change the following:

• Bridge Max Age

• Bridge Forward Delay

• Bridge Hello Time

• Bridge Priority

To open the Bridge Protocol screen:

• Highlight the BRIDGE PROTOCOL command in the System

Information screen, and press RETURN.

7-1

SPANNING TREE

04/02/94 08:44:34 BRIDGE PROTOCOL




Bridge ID: 80-00-00-B8-60-9F-EB Time Since Topology Change: 3450

Topology Change Count: 2 Topology Change: 0

Root Cost: 0 Desig. Root: 80-00-00-B8-60-9F-EB

Root Port: 0 Max Age: 20 Hold Time: 1

Hello Time: 2 Forward Delay: 15

Bridge Max Age: 20 Bridge Hello Time: 2

Bridge Forward Delay: 15 Bridge Priority: 8000

RETURN SAVE PORT PARAMETERS

Figure 7-1. Bridge Protocol Screen

7.1.1 Bridge Protocol Screen Data

The Bridge Protocol screen contains information about the network’s

Root bridge and about the FDMMIM.

Bridge ID is the unique bridge identifier for the FDMMIM. The

Bridge ID is computed from the bridge address and the bridge priority, which is explained later in this section. STA compares

Bridge IDs to determine the relative priority of the bridges in the network when selecting a Root bridge.

Topology Change Count indicates the number of times the bridge’s Topology Change flag has been changed since the bridge was powered-up. The Topology Change Flag changes each time a bridge enters or leaves the network, or the Root bridge ID changes.

7-2

SPANNING TREE

Root Cost indicates the cost (value), of the data path from the

FDMMIM to the Root bridge. The Root Cost value does not represent a particular type of unit. It is simply a value that is compared to the

Root Cost value of other bridges in the network. The Root Cost is used by STA when choosing a Root bridge. By editing the Path Cost parameter in the Port Parameters screen, you can influence the selection of the Root bridge. The Root bridge’s Root Path Cost is 0.

Root Port displays the port identifier for the port that provides the lowest cost path to the Root.

Hello Time indicates, in seconds, the length of time the Root bridge, or bridge attempting to become the Root, waits before resending a

Configuration BPDU. The Hello Time is set by the Root bridge.

Bridge Max Age shows the setting for the FDMMIM’s BPDU ageing timer. The ageing timer defines the maximum length of time that a Configuration BPDU is retained by the bridge before it is discarded. During normal operation, each bridge in the network receives a new Configuration BPDU before the ageing timer expires.

If the timer expires before a new Configuration BPDU is received, it indicates that the former Root is no longer active. The remaining bridges begin Spanning Tree operation to select a new Root. The

Bridge Max Age is set by the Root bridge. You can edit the Bridge

Max Age value but, unless the FDMMIM is the Root bridge, the new value has no effect. The new value becomes effective only when the

FDMMIM becomes the Root. (Default = 20 seconds. The allowable range is 6 to 40 seconds.)

Bridge Forward Delay is the length of time that the FDMMIM spends in the Listening or Learning state (listening to Topology

Change BPDU activity on the network) when moving toward the

Forwarding state. The Bridge Forward Delay is set by the Root bridge in the network. You can edit the Bridge Forward Delay value but, unless the FDMMIM is the Root bridge, the new value has no effect. The new value becomes effective only when the FDMMIM becomes the Root. (Default = 15 seconds. The allowable range is 4 to

30 seconds.)

Time Since Topology Change indicates the elapsed time (in seconds) since the last change to the bridge Topology Change Flag.

7-3

SPANNING TREE

Topology Change indicates the value of the Topology Change Flag.

If this bridge is the Root bridge, the value of the Topology Change

Flag is transmitted via Configuration BPDUs to the other bridges in the network. This field can contain the following: one (1) zero (0)

A change is occurring. The Dynamic

Ageing Time of the Acquired

Database equals the Bridge Forward

Delay time. The Acquired Database purges old address information and begins learning the new network topology.

Indicates that no topology change is in progress. Network topology is stable.

Desig. Root displays the Ethernet address and bridge priority of the bridge that is assumed to be the Root.

Hold Time displays, in seconds, the minimum time period that elapses between the transmission of Configuration BPDUs through the bridge port to ensure that Configuration BPDUs are not transmitted too frequently through any bridge port. Receiving a

Configuration BPDU starts the Hold Timer. If the Hold Timer expires, the port invokes the Transmit Configuration BPDU procedure, which sends configuration change information to the

Root. The Hold Time value is a fixed value, as specified by the IEEE

802.1d specification.

Bridge Hello Time indicates, in seconds, the length of time the

Root bridge waits before resending a Configuration BPDU. You can edit the Bridge Hello Time but, unless the FDMMIM is the Root bridge, the new value has no effect. The new value becomes effective only when the FDMMIM becomes the Root. (Default = 2 seconds. The allowable range is 1 to 4 seconds.)

Bridge Priority displays the part of the bridge address that contains the identifier used by Spanning Tree for priority comparisons. (Default = 8000. The allowable range is 0 to FFFF.)

7-4

SPANNING TREE

7.1.2 Bridge Protocol Screen Commands

RETURN closes the Bridge Protocol screen, and returns you to the


SAVE saves the STA operating parameters currently displayed on the Bridge Protocol screen.

PORT PARAMETERS opens the Port Parameters screen.

7.2

THE BRIDGE PORT PARAMETERS SCREEN

The Bridge Port Parameters screen shows the port-specific parameters related to the Spanning Tree protocol, and lets you change the Port Priority and Path Cost. This screen displays two columns for the port-specific protocol parameters, one for each of the bridge ports (Ethernet and FDDI).

To open the Bridge Port Parameters screen:

• In the Bridge Protocol screen, highlight the PORT

PARAMETERS command, and press RETURN.

04/02/94 08:44:34 BRIDGE PORT PARAMETERS




Ethernet Port FDDI Port

Port Priority: 80 80

Uptime: 5807 5807

Port State: Forwarding Forwarding

Path Cost: 100 10

Desig. Root: 00-00-1D-06-F9-D6 00-00-1D-06-F9-D6

Designated Cost: 0 0

Designated Bridge: 00-00-1D-06-F9-D6 00-00-1D-06-F9-D6

Designated Port: 8001 8002

Topology Change

Acknowledge: 0 0

RETURN SAVE

Figure 7-2. Port Parameters Screen

7-5

SPANNING TREE

7.2.1 Bridge Port Parameters Screen Data

Port-specific Spanning Tree information includes:

Port Priority shows the port priority portion of the port identifier.

The port priority is one of the values used by STA to choose a Root port for the bridge. A lower number indicates a higher priority.

(Default = 80. The allowable range is 0 to FF.)

Uptime displays the elapsed time (in seconds) since the respective port was last reset or initialized.

Port State indicates the current state of the port. Five states are possible:

DISABLED

LEARNING

LISTENING

FORWARDING

BLOCKING


No traffic can be received or forwarded while the port is disabled.

The bridge is learning network addresses. The bridge enters the

Learning state (during start-up), or when the STA executes due to a network topology change.

The bridge is monitoring BPDU traffic while preparing to move from the

Learning to the Forwarding state.

The bridge is on-line and this port is forwarding traffic.

The port will not forward any traffic through the bridge.

7-6

SPANNING TREE

Path Cost displays the portion of the total path cost associated with this port. In a parallel bridge network, the Spanning Tree Algorithm selects the bridge with the lowest path cost as the Root bridge.

Changing a port’s path cost can affect the selection of the Root bridge. You can lower a port’s path cost to make a bridge more competitive in the Root selection process. (Default - FDDI = 10,

Ethernet = 100. Allowable range for both Ethernet and FDDI is 1 to

65535.)

Designated Root displays the unique bridge identifier of the bridge that is assumed to be the Root bridge on the network.

Designated Cost shows the cost of the path from this port to the

Root bridge on the network.

Designated Bridge displays the Bridge ID of the bridge that is assumed to be the Root bridge on the network.

Designated Port displays Port ID for the bridge port that is assumed to be the designated port.

Topology Change Acknowledge indicates the new value of the

Topology Change Acknowledgment flag that will be transmitted by the designated bridge in the next Configuration BPDU on the associated port. This field displays 0 or 1. A zero indicates that no change is occurring; a one indicates that a change is occurring.

7.2.2 Bridge Port Parameter Screen Commands

RETURN closes the Bridge Port Parameters screen and returns you to the Bridge Protocol screen.

SAVE causes the bridge to retain the currently displayed parameters and apply them to bridge operations. If you close the

Bridge Protocol screen without first saving changes, Local

Management retains the previous settings.

7-7

THE FILTERING DATABASES

CHAPTER 8


FDMMIM/LM lets you examine entries in the Acquired, Permanent, and Special Databases. This chapter explains how the FDMMIM bridge uses these databases and how you can view their contents.

Local Management gives you access to the Filtering Database through five screens:

• Filter Database

• Display Filter Entries

• Create Filter Entry

• Delete Filter Entry

• Special Database

8.1

BRIDGE OPERATION

When filtering, the bridge uses the contents of the Acquired and/or

Special Databases to decide whether or not to forward a frame.

When forwarding, the bridge translates (from FDDI to Ethernet, or from Ethernet to FDDI) and sends all frames it receives.

The bridge initializes the Acquired Database at start-up time by copying the contents of the Permanent Database, from non-volatile memory, to the Acquired Database.

In the Learning or the Forwarding state:

• The bridge adds the source address of a frame it receives to the Acquired Database, and associates that address with the receiving port.

8-1


• The bridge checks the destination address of the frame to determine how to treat it. If the bridge finds the destination address in its Acquired Database, it knows the frame’s destination network (port). At this point the bridge decides whether to filter or forward the frame:

— If the Acquired Database indicates that the destination of the frame resides on the same network as the receiving port, the bridge filters the frame.

— If the destination of the frame resides on the other side of the bridge, opposite the receiving port, the bridge translates the frame (FDDI to Ethernet or Ethernet to

FDDI), and then forwards it.

• In the event the bridge cannot locate the destination address in its Acquired Database, the bridge forwards the frame.

If the bridge does not use a Database entry during a fixed length of time (the Dynamic Ageing Time), it purges the entry from the database. This action keeps entries current.

8.2

THE FILTER DATABASE SCREEN

The Filter Database screen displays current information about the

Permanent and Acquired Databases and gives access to the Display

Entries, Create Entry, Delete Entry, and Special Database screens where you can examine and modify database contents. Database entries define what action (either filtering or forwarding) a bridge takes on certain frames.

To open the Filtering Database screen:

• Highlight FILTER DATABASE in the System Information screen, and press RETURN.

8-2


04/02/94 05:14:34 Filter Database




Acquired Database Permanent Database

Maximum Entries: 8191 Maximum Entries: 2047

Current Entries: 20 Current Entries: 17

Dynamics: 3

Statics: 17

Dynamic Ageing Time: 300

Type of Filtering: IEEE 802.1

RETURN SAVE DISPLAY ENTRIES

CREATE ENTRY DELETE ENTRY SPECIAL DATABASE

Figure 8-1. Filtering Database Screen

8.2.1 Filter Database Screen Data

The Filter Database screen data section displays status information about the databases, and lets you change both the database Dynamic

Ageing Time and the type of filtering (IEEE 802.1, Special DB, or

Both).

Maximum Entries is the maximum number of entries that the

Acquired or Permanent Databases can retain.

Current Entries is the number of entries the Acquired and

Permanent Databases currently hold. In the Acquired Database column, the current entries total equals the sum of the Dynamics and Statics.

Dynamics provides the number of dynamic (volatile) addresses within the bridge’s Acquired Database. The bridge learns these addresses from network traffic.

Statics provides the number of addresses entered into the Acquired

Database using database commands and/or the Permanent Database

8-3

THE FILTERING DATABASES addresses that the bridge loads at start-up. The count never drops below the 17 Permanent Database entries.

Dynamic Ageing Time is the length of time, in seconds, that the

Acquired Database retains a Dynamic entry. To set the Dynamic

Ageing time, highlight the Dynamic Ageing Time field and type a new value. (Default = 000300. The allowable range is 10 to 1000000

seconds.)

Type of Filtering lets you change the type of filtering the bridge uses. This field can contain the following:

IEEE 802.1

Special DB

Both

Uses the contents of the Acquired

Database for filter/forward decisions.

Uses the contents of the Special

Database for filter/forward decisions.

Uses the contents of both the

Acquired Database and Special

Database. First, the bridge applies the Acquired Database to the frame. If the frame does not get filtered, the bridge applies the Special Database for filter/forward decisions.

8.2.2 Filter Database Screen Commands

RETURN closes the Filter Database screen and returns you to the


SAVE makes your changes permanent. If you close the Filter

Database screen without first saving, you lose all changes.

DISPLAY ENTRIES opens the Display Filter Entries screen, where you can view all or just selected ranges of database entries.

CREATE ENTRY displays the Create Filter Entry screen.

DELETE ENTRY displays the Delete Filter Entry screen.

SPECIAL DATABASE displays the Special Database screen.

8-4


8.3

DISPLAY FILTER ENTRIES SCREEN

The Display Filter Entries screen lets you examine the contents of the Acquired and Permanent Databases.

To open the Display Filter Entries screen:

• Highlight the DISPLAY ENTRIES command in the Filter

Database screen, and press RETURN.

04/02/94 05:14:34 Display Filter Entries




Database Address Type Total Entries Found

Acquired XXXXXXXXXXXX Dynamic 3

Index Address Type Enet Port FDDI Port

1 00001D07007B Dynamic Forward Filter

2 000010148BCA Dynamic Forward Filter

3 0000100765DF Dynamic Filter Forward

RETURN DISPLAY ENTRIES

Figure 8-2. Display Filter Entries Screen

To view database entries:

1.

Select the database that you want to view by highlighting the

Database field and pressing RETURN to toggle between

Acquired and Permanent.

2.

Select the address range that you want to view by highlighting the Address field, and entering an Ethernet address. Do not include dashes in the address, just the 12 hex integers that make up the address. You can enter an X as a wildcard integer. A wildcard forces a match for that integer position. Enter all Xs to select the entire database.

8-5


3.

Select the type of entry to display by highlighting the Type field and pressing RETURN to toggle between Dynamic and Static.

4.

Highlight the DISPLAY ENTRIES command at the bottom of the screen, and press RETURN.

The screen lists up to the first ten addresses that match the selected parameters. When more than ten matches exist, paging commands

(NEXT and PREVIOUS) let you display additional matches.

8.3.1 Display Filter Entries Screen Data

The lower half of the Display Filter Entries screen displays the requested filter information; the top section of the screen retains the parameter selection fields. This feature lets you refine your address mask to reduce the number of addresses the screen displays, or to easily make another selection.

After entering new parameters, you can use the DISPLAY ENTRIES command to display the new filter matches. PREVIOUS and NEXT commands let you display succeeding blocks of addresses, when the list contains more than ten entries.

Note: When you select the Display Entries command, the screen displays a snapshot of the database contents. Since the Acquired

Database constantly changes, the screen cannot continuously display the current Acquired Database.

Displaying Filter entries provides the following information:

Index is a sequential reference to the captured database contents.

Address is the device address.

Type is either Dynamic or Static.

8-6


Enet Port defines the action the bridge takes on frames entering the

Ethernet port:

Relay

Filter

Forward frames with this destination address.

Do not forward frames with this destination address.

FDDI Port defines the action the bridge takes on frames entering the FDDI port:

Relay

Filter

Forward frames with this destination address.

Do not forward frames with this destination address.

8.3.2 Display Filter Entries Screen Commands

RETURN closes the Display Filter Entries screen, and returns you to the Filter Database screen.

NEXT displays subsequent blocks of filter information. This command appears when more than 10 entries exist.

PREVIOUS displays preceding blocks of filter information. This command appears when more than 10 entries exist.

DISPLAY ENTRIES displays filter entries that match the currently defined type and address mask within the selected database.

8.4

CREATE FILTER ENTRY SCREEN

This screen retains most of the Filter Database screen information.

Several fields on the lower half of the screen let you create entries for either the Acquired or Permanent Databases. After you select the database, and define the new address and its attributes, create the entry by selecting the CREATE ENTRY command.

8-7


To open the Create Filter Entry screen:

• Highlight the CREATE ENTRY command in the Filter


04/02/94 05:14:34 Create Filter Entry







Dynamics: 3

Statics: 17

Create Entry in Database: Permanent

Destination Address: 00-00-00-00-00-00

Action on frame entering Enet Port: Filter

Action on frame entering FDDI Port: Filter

RETURN CREATE

Figure 8-3. Create Filter Entry Screen

8.4.1 Create Filter Entry Screen Data

Create Entry in Database selects the database where you want to store the address. Highlight this field and use the RETURN key to toggle between Permanent and Acquired.

Destination Address defines the address you want to create.

Highlight this field and enter the address in the hex format

XX-XX-XX-XX-XX-XX (where XX = a value between 00 and FF).

8-8


Action on frame entering Enet Port defines the action the bridge takes on packets entering the Ethernet port. Use the RETURN key to toggle between Forward and Filter:

Relay

Filter

Forward traffic destined for this address.

Filter traffic destined for this address.

Action on frame entering FDDI Port defines the effect on packets entering the FDDI port. Use the RETURN key to toggle between Forward and Filter:

Relay

Filter

Forward traffic destined for this address.

Filter traffic destined for this address.

8.4.2 Create Filter Entry Screen Commands

RETURN closes the Create Filter Entry screen, and returns you to the Filter Database screen.

CREATE ENTRY creates the currently defined address entry. You can repeat this command to create another entry.

8.5

DELETE FILTER ENTRY SCREEN

This screen retains most of the Filter Database screen information.

Several fields on the lower half of the screen let you delete entries for either the Acquired or Permanent Databases. After you select the database, and define the new address, delete the entry by selecting the DELETE ENTRY command.

To open the Delete Filter Entry screen:

• Highlight the DELETE ENTRY command in the Filter


8-9


04/02/94 05:14:34 Delete Filter Entry







Dynamics: 3

Statics: 17

Database: Permanent

Address: 00-00-00-00-00-00

RETURN DELETE

Figure 8-4. Delete Filter Entry Screen

8.5.1 Delete Filter Entry Screen Data

Database selects the database containing the entry you want to delete. Highlight this field and press RETURN to toggle between

Permanent and Acquired.

Address defines the address you want to delete. Highlight this field and enter the address in the hex format XX-XX-XX-XX-XX-XX

(where XX = a value between 00 and FF).

8.5.2 Delete Filter Entry Screen Commands

RETURN closes the Delete Filter Entry screen, and returns you to the Filter Database screen.

DELETE ENTRY deletes the currently defined address entry. You can repeat this command to delete another entry.

8-10


8.6

SPECIAL DATABASE SCREEN

You can store up to ten filter entries in the Special Database. These filters, like those in the Acquired Database, determine if the bridge filters or forwards certain frames. However, the Special Database allows you to define one or more fields to participate in the filter/ forward decision.

Each entry can specify the Destination Address, Source Address, frame type, and up to 16 hex integers of a data field (to assist you in precisely defining frames). After defining frames, save the screen contents using the SAVE FILTER command.

To open the Special Database screen:

• Highlight the SPECIAL DATABASE command in the Filter


04/02/94 05:14:34 Special Database




# Enable Enet FDDI Dest Address Source Addr. Type Data Field

1 No Filter Filter XXXXXXXXXXXX XXXXXXXXXXXX XXXX XXXXXXXXXXXXXXXX










Default Action: Forward

RETURN SAVE FILTER

Figure 8-5. Special Database Screen

The Special Database screen displays the entire contents of the database at one time and lets you change the definition and action for each entry. Entry numbers reside on the left side of the display

(under the # column heading).

8-11


8.6.1 Special Database Screen Data

Enable shows whether or not the associated entry is enabled

(filtering frames). Highlight this field and use the RETURN key to toggle between Yes (apply the filter) and No (do not apply the filter).

Enet defines the action the bridge takes on frames entering the

Ethernet port. Highlight this field and use the RETURN key to toggle between Forward and Filter:

Forward

Filter

Forward packets that match the respective filter information.

Filter packets that match the respective filter information.

FDDI defines the action the bridge takes on packets entering the

FDDI port. Highlight this field and use the RETURN key to toggle between Forward and Filter:

Forward

Filter

Forward packets that match the respective filter information.

Filter packets that match the respective filter information.

Dest Address provides the bridge with a destination address to compare with the Destination Address of incoming frames. Highlight this field and enter the desired address in the hex integer format

XXXXXXXXXXXX (where X = a value between 0 and F). Keeping an

X (wildcard) in any integer position forces a match for that integer.

Source Addr. provides the bridge with a source address to compare with the Source Address (SA) of incoming frames. Highlight this field and enter the desired address in the hex integer format

XXXXXXXXXXXX (where X = a value between 0 and F). An X

(wildcard) in any integer position forces a match for that integer.

Type provides the bridge with an Ethernet Protocol Type to compare with the Type field of incoming frames. Highlight this field and enter the desired Type in the hex format XXXX (where X = a value between 0 and F). An X (wildcard) in any integer position forces a match for that integer.

8-12


Data Field provides the bridge with 16 hex integers to compare to the first 16 hex integers of an incoming frame’s information field.

Highlight this field and enter the desired 16 hex integers. An X

(wildcard) in any integer position forces a match for that integer.

Default Action provides the bridge with an action to take, in the event it cannot find a match within the Special Database. For example, if the bridge encounters a frame that does not meet any of the Special Database criteria, it looks to the default action setting to determine whether to filter or forward the frame.

8.6.2 Special Database Screen Commands

RETURN closes the Special Database screen, and returns you to the

Filter Database screen.

SAVE FILTER stores the currently defined filter entries in the

Special Database.

8-13

CONTROLLING CONCENTRATOR MODULES AND PORTS

CHAPTER 9

CONTROLLING CONCENTRATOR

MODULES AND PORTS

The FDMMIM, and adjacent FDCMIMs, make up a modular dualattached FDDI Concentrator. This chapter explains how to use the

FDDI Configuration screen to enable and disable the FDMMIM concentrator and FDCMIM modules and ports.

9.1

THE FDDI CONFIGURATION SCREEN

The FDDI Configuration screen is where you control the FDDI concentrator functions of the FDMMIM.

To open the FDDI Configuration screen:

• Highlight FDDI in the System Information screen, and press

RETURN.

04/02/94 08:44:22 FDDI CONFIGURATION




FDCMIM-04 FDCMIM-04 FDCMIM-04 FDCMIM-04 FDMMIM-04

ENABLED ENABLED ENABLED ENABLED ENABLED

1 ERR 1 ON 5 ON 1 ON 1 ON 1 ON A-B

2 ERR 2 ON 6 ON 2 ON 2 ON 2 ON ON

3 ERR 3 ON 7 OFF 3 ON 3 ON 3 ON

4 ERR 4 ON 8 OFF 4 ON 4 ON 4 ON

2.01.03

2.01.03

2.01.03

2.01.03

RETURN EXECUTE

Figure 9-1. FDDI Configuration Screen

9-1


Below the screen header information, the FDDI Configuration screen displays a representation of the FDMMIM and any FDCMIMs located in higher numbered slots. The Configuration screen shows only one FDMMIM, even if more FDMMIMs reside in the hub.

The FDDI Configuration screen does its best to display its location in the MMAC the way you define it in the Setup screen. However, no matter what the physical position or slot location, the Chassis Type in the Setup screen takes precedence. For example, if your

FDMMIM is physically installed in Slot 7 of an MMAC 8, but you have the Chassis type set to MMAC 3 with a Slot 2 location, the configuration screen shows the FDMMIM in Slot 2 of an MMAC 3.

9.1.1 FDDI Configuration Screen Data

Each FDCMIM slot shown in the FDDI Configuration screen displays the configuration of the resident FDCMIM-04 or FDCMIM-

08. (The FDCMIM provides M ports for the FDMMIM. By itself, an

FDCMIM cannot connect to the FDDI dual ring, so it does not show an FDDI Ring Connection Status field.)

Figure 9-2 shows the fields within a single configuration slot. The

Concentrator Connection Status field, the ENA/DIS-BOARD field, and the port status fields only appear on MIMs that have concentrator (M type) ports.

Concentrator Connection Status when ON, indicates M ports connect to the MMAC FDDI bus, and to each other. When OFF, the module becomes a stand alone concentrator; M ports do not connect to the MMAC, but ports where Port Status = ON can still pass packets among themselves.

To change the board status:

1.

Highlight the ENA/DIS-BOARD command below the module.

2.

Press RETURN on the keyboard to toggle the selection.

3.

Highlight the EXECUTE command at the bottom of the screen, and press RETURN.

9-2


FDDI Ring Connection Status, when ON, indicates that the

FDMMIM is connected to the FDDI ring. When OFF, the FDMMIM is isolated from the ring. (FDCMIMs do not have A and B connectors.) To connect/disconnect the FDMMIM from the FDDI ring:

1.

Highlight the status line.

2.


3.


Concentrator Ports Status, when ON, indicates that the port is connected to the FNB. When OFF, the port is isolated. ERR indicates that the MIM has failed. To change a port’s status:

1.

Highlight the port status (ON or OFF) next to the port number.

2.


3.


Concentrator Connection Status

Indicates whether or not the M ports are connected to the MMAC FDDI bus.

FDMMIM-04

ENABLED

1 ON A-B

FDDI Ring Connection Status

Indicates whether or not the FDDI A and B ports are connected to the FDDI dual ring.

2 ON ON

3 ON

4 ON

Concentrator Ports Status

Indicates the status of each M type port: ON

(enabled) or OFF (disabled).

Firmware Revision

Indicates the firmware revision of the conentrator board.

2.01.03

Figure 9-2. FDDI MIM Configuration Fields

9-3


If you close the FDDI Configuration screen without using the

EXECUTE command, you lose all changes. You only need to use

EXECUTE once. You can move the cursor around the screen, turning ports and modules on and off, and then EXECUTE to make all your changes effective.

9.1.2 FDDI Configuration Screen Commands

The FDDI Configuration screen contains the following commands:

RETURN closes the FDDI Configuration screen and returns you to the System Information screen.

EXECUTE performs and saves the current port and board configuration on the screen. Closing the FDDI Configuration screen without first using the EXECUTE command, voids any changes.

9.2

CONCENTRATOR STATUS AND BRIDGE OPERATION

Changing FDMMIM concentrator fields does not change bridge operation. Turning the concentrator OFF, only disconnects M ports.

The FDMMIM can still pass packets between the FDDI ring and the

Ethernet port. The bridge still participates in Spanning Tree

Algorithm functions and is still part of the network.

9-4

FDMMIM/LM MESSAGES

APPENDIX A


This appendix lists each warning and error message that can occur in

FDMMIM/LM, describes potential causes for each message, and suggests corrective actions where appropriate. Within each category, messages are listed alphabetically.

INFORMATION MESSAGES

Information messages require no user action. They simply verify that a user initiated action is complete. Information messages are self explanatory and do not require detailed descriptions.

WARNING MESSAGES

Warning messages tell you that the action you requested did not complete successfully or that a condition exists that you may want to know about. Usually, the condition requires no response.

A-A connection accepted

Cause: Connecting an FDDI A port to another A port is undesirable. The FDMMIM supports A-A connections unless your Connection Policy specifies otherwise.

Action: If possible, reconnect the FDMMIM’s A port cable to a B port. The FDMMIM supports an A-A connection.

A-A connection rejected

Cause: Connecting an FDDI A port to another A port is undesirable. The FDMMIM rejects A-A connections when directed to do so by your Connection Policy.

Action: Reconnect the FDMMIM’s A port cable so that it connects to a B port.

A-1


A-S connection accepted

Cause: Connecting an FDDI A port to an S port is an undesirable connection. The FDMMIM supports A-S connections.

Action: If possible, reconnect the FDMMIM’s A port cable so that it connects to a B port.

A-S connection rejected

Cause: Connecting an FDDI A port to an S port is an undesirable connection. The FDMMIM rejects A-S connections when directed to do so by your Connection Policy.

Action: Reconnect the FDMMIM’s A port cable so that it connects to a B port.

B-B connection accepted

Cause: Connecting an FDDI B port to a B port is an undesirable connection. The FDMMIM supports B-B connections.

Action: If possible, reconnect the FDMMIM’s B port cable so that it connects to an A port.

B-B connection rejected

Cause: Connecting an FDDI B port to a B port is an undesirable connection. The FDMMIM rejects B-B connections when directed to do so by your Connection Policy.

Action: Reconnect the FDMMIM’s B port cable so that it connects to an A port.

B-S connection accepted

Cause: Connecting an FDDI B port to an S port is an undesirable connection. The FDMMIM supports B-S connection.


A-2


B-S connection rejected

Cause: Connecting an FDDI B port to an S port is an undesirable connection. The FDMMIM rejects B-S connection when directed to do so by your Connection Policy.


Ageing Time must be greater than or equal to 0 and less than or equal to 1,000,000

Cause: The Ageing time determines how long an address remains in the Acquired database before being purged.

Action: Enter a valid number.

All characters in this field must be entered

Cause: You are editing a field that requires all positions in the field to contain a valid character. For example, if you are creating an IP address, make sure that you have four groups of characters, each separated by a period.

Action: Re-type the entry.

Bridge restarting

Cause: The FDMMIM has been restarted, either through management action or by pressing the RESET switch on the front of the module.

Action: No action required. The bridge goes through its power up diagnostics.

A-3

FDMMIM/LM MESSAGES send_config_bpdu ( ) port (1, 2) took too long

Cause: The port could not transmit a configuration bridge protocol data unit on schedule.

Action: If the message states that the problem is on port 1, the cause could be that the ring is down. If this is an isolated incident, no action is required. If this warning continues, reset Spanning Tree as follows:

1.

Open the FDMMIM/LM Setup screen.

2.

Highlight Type of STA Protocol and press RETURN until the toggle select NONE appears.

3.

Execute the SAVE command at the bottom of the screen.

4.

Highlight Type of STA Protocol and select the original setting

(either 802.1 or DEC).

5.

Execute the SAVE command.

Remember, while you have STA disabled, the bridge is in

Standby mode and no packets are forwarded.

FDDI Trace initiated

Cause: The FDDI ring is attempting to repair an interruption.

Action: No action required. The FDDI ring should find and adjust to the condition.

FDDI Trace received

Cause: The FDDI ring is attempting to repair an interruption.

Action: No action required. The FDDI ring should find and adjust to the condition.

A-4


Illegal date entered

Cause: The date you entered is not a valid date or you used the wrong format.

Action: Retype the date. Use all numerical values in the format:

MM/DD/YY.

Illegal BPDU type

Cause: The FDMMIM has received a Bridge Protocol Data Unit of an unknown type. Not all bridges on the network are using the same Spanning Tree Algorithm protocol.

Action: Check each bridge in the network. Every bridge must use the same STA protocol. Mixing protocols causes an unstable network.

Illegal FDM location in MMAC

Cause: You specified an MMAC configuration that cannot exist.

Action: Check the FDMMIM installation to determine the MMAC type (MMAC3, MMAC5, or MMAC8). Determine the slot number where the FDMMIM resides and enter it into the

Setup screen. The right-most slot (bottom in the MMAC3) is slot 1, and reserved for dedicated management modules.

Illegal network address entered

Cause: The address you entered is not legal, or you used the wrong format.

Action: Retype the entry.

Illegal numeric value entered

Cause: You entered a non-numeric value in a field that can accept only numeric values.


A-5


Illegal password entered

Cause: You typed the wrong password.


Illegal time entered

Cause: The time you entered was not a valid time or you used the wrong format.

Action: Retype the time. Use 24-hour clock notation in the format:

HH:MM:SS.

Link error estimate exceeds alarm threshold

Cause: The port failed to receive a valid link signal.

Action: Clean your fiber optic cable connectors.

Link error estimate returned below alarm threshold

Cause: This indicates that you have a valid link.

Action: No action required.

M-M connection rejected

Cause: Connecting an M port to an M port is an illegal connection.

Action: Reconnect the M port cable to an S port.

Message history full

Cause: The FDMMIM has 100 entries, the maximum, in the

Message log. No more entries can be added.

Action: Delete the Message log. Open the Message Log screen and execute the DELETE command.

Mib return error (2, 3, 4)

Cause: Internal error.

Action: Contact Cabletron Systems Technical Support.

A-6


NO HARDWARE FILTER

Cause: During the power-up diagnostics, the FDMMIM was unable to find the components that comprise the bridge filter. The bridge is inoperative. It can receive configuration and management packets, but it cannot forward packets.

Action: Restart the bridge. If restarting does not resolve the problem, contact Cabletron Systems Technical Support.

NVRAM Management Failure. Restored defaults.

Cause: The board was left without power for an extended amount of time with the batter enabled. All default settings were restored to the module.

Action: Re-enter the desired settings. If the board remains without power, be sure to disable the battery.

Permanent DB, illegal port ID specified

Cause: Remote management requested an action and named a port that does not exist.

Action: No action required.

set_port_name ( ) - illegal port id



set_port_name_net ( ) - illegal port id



Received BPDU not a (DEC IEEE) BPDU type

Cause: The FDMMIM has received a Bridge Protocol Data Unit of an unknown type. Not all bridges on the network are using the same Spanning Tree Algorithm protocol.

Action: Check each bridge in the network. Every bridge must use the same STA protocol. Mixing protocols causes an unstable network.

A-7

FDMMIM/LM MESSAGES smt_mib_set (hex address) failed for this instance



This entry must be greater than or equal to . . .

Cause: You entered a number that is smaller than the numbers that this field can accept.


This entry must be less than or equal to . . .

Cause: You entered a number that is greater than the numbers that this field can accept.


tick ( ) took longer than 1 second

Cause: Spanning Tree error.


Too many characters entered

Cause: You typed more characters than the field can accept.


Unknown address selected for ring map start

Cause: To display a ring map, you must start with a valid address.

The starting address is no longer present on the ring.

Action: Execute the SCROLL command to select a different address for the Ring Map start.

A-8


ERROR MESSAGES

FDDI Error Messages indicate that FDDI ring operations or

FDMMIM operations have been interrupted. These errors usually result in disconnecting one or both bridge ports from the network and require that someone fix the problem condition before the FDMMIM can reconnect. Here is a list of potential messages and recommended resolution actions.

BSI BAD_CNF_REQ_STATUS



BSI BAD_RINGOP_REQ_STATUS



BSI COMPLETED_BEACON_REQ_STATUS



BSI CONSISTENCY_FAILURE_REQ_STATUS



BSI ERROR. UID Mismatch



BSI HOST_ABORT_REQ_STATUS



BSI INTERNAL_OR_FATAL_ABUS_REQ_STATUS



A-9


BSI MAC_DEVICE_ABORT_REQ_STATUS



BSI MAC_RESET_REQ_STATUS



BSI NO_REQ_STATUS



BSI PART_NONE_REQ_STATUS



BSI PREEMPT REQ_STATUS



BSI RESERVED_REQ_STATUS



BSI SERVICE_LOSS_REQ_STATUS



BSI TIMEOUT_REQ_STATUS



A-10


BSI UNDERRUN_REQ_STATUS



Comparison Error



Downloading to daughter board unsuccessful

Cause: The M ports could not be initialized. The bridge should be

OK, but the concentrator’s M ports are inoperative.


Duplicate FDDI address detected

Cause: There is another station on the ring with the same address as the FDMMIM.

Action: Find the station with the duplicate address and remove it from the ring. Next, reset the FDMMIM.

Ethernet port failed self test

Cause: The FDMMIM Ethernet port has an internal circuit failure that prevents it from connecting to the MMAC Ethernet bus.


EXT LOOPBACK (INJ LS) ERROR



FDDI Port A failed self test

Cause: The FDMMIM A port has an internal circuit failure that prevents it from connecting to the ring.


A-11


FDDI Port B failed self test

Cause: The FDMMIM B port has an internal circuit failure that prevents it from connecting to the ring.


FDDI Test 1 failed self test

Cause: The FDMMIM has an internal circuit failure that prevents it from connecting to the ring.








FDDI failed self test



FDDI Max fragment count exceeded

Cause: Packet buffering error.

Action: The FDMMIM should recover by itself. If this message continues to occur, reset the FDMMIM.

FIBER LS ERROR



A-12


FNB failed self test

Cause: The FDMMIM has an internal circuit failure that prevents it from connecting to the MMAC buses.


Hardware filter ‘display counter’ timeout

Cause: A request to the bridge’s filter database hardware could not be completed.

Action: Reset the FDMMIM.

Hardware filter ‘display first’ timeout



Hardware filter ‘search address’ timeout



Hardware filter not installed



Hardware filter test failed

Cause: There is a problem with the bridge’s hardware filter.

Action: It is likely that the FDDI concentrator functions are unaffected but, the FDMMIM cannot use its Filtering

Database. Contact Cabletron Systems Technical Support.

ILB_injection error



A-13


ILB_LS_error



Interrupt error



Invalid FDDI receive descriptor

Cause: Packet buffering error.

Action: No action required. The FDMMIM should discard the packet and continue operation. If this error becomes persistent, contact Cabletron Systems Technical Support.

Invalid hardware filter ‘display counter’ response



Invalid hardware filter ‘search address’ response



Local RAM failed self test

Cause: FDMMIM internal memory has been corrupted.


lmram_rd ( ) time out/ lmram_wr ( ) time out



MIB return 1



A-14

FDMMIM/LM MESSAGES on call to ret idud( ) in recv_fddi_pkt( )



Read_write error



Received POST/GET/SET cmd while FNB protocol locked

Cause: The communication between the FDMMIM and an

FDCMIM has been unexpectedly interrupted.


Reset error



Shared RAM failed self test

Cause: FDMMIM internal memory has been corrupted.


smt_mib_get (hex address) failed for this instance



Software reset



Unexpected interrupt, hardware filter



A-15


Unexpected interrupt, IRM backplane



Unexpected interrupt, spurious



Unknown type



A-16

SPECIFICATIONS

APPENDIX B

SPECIFICATIONS

OPERATING SPECIFICATIONS

This section lists the operating specifications for all of the FDMMIMs.

Cabletron Systems reserves the right to change these specifications at any time, without notice.

Fiber Optic Interface

Depending on the FDMMIM, interfaces have the following characteristics:

Multimode Transmitter

Optical wavelength: 1330 nm typical

Optical output: -20.0 dBm minimum

-14.0 dBm maximum

Optical rise time:

Optical fall time:

Spectral width:

Supply current:

3.5 nsec maximum

3.5 nsec maximum

110 nm maximum

150 mAmps maximum

Multimode Receiver (Signal Detect)


Optical input: -31.0 dBm minimum

-14.0 dBm maximum

Optical rise time:

Optical fall time:

Supply current:

5 nsec maximum

5 nsec maximum

115 mAmps maximum

B-1

SPECIFICATIONS

Unshielded Twisted Pair Transmitter

Amplitude: 1.080 Vpk maximum

0.920 Vpk minimum

Rise time:

Fall time:

2 nsec minimum

4 nsec maximum

2 nsec minimum

4 nsec maximum

Rise/Fall variation: 0.5 nsec maximum

Overshoot: 5% maximum

Droop(14 symbols): 3% maximum

Unshielded Twisted Pair Receiver (Signal Detect)

Assert Time:

Deassert Time:

10

µ sec typical

100

µ sec maximum

10

µ sec typical

350

µ sec maximum

Single Mode Transmitter


Optical output: -19.0 dBm minimum

-14.0 dBm maximum

Optical rise time:

Optical fall time:

Spectral width:

Supply current:

3.5 nsec maximum

3.5 nsec maximum

15 nm maximum

150 mAmps maximum

Single Mode Receiver (Signal Detect)


Optical input: -31.0 dBm minimum

-14.0 dBm maximum

Optical rise time:

Optical fall time:

Supply current:

5 nsec maximum

5 nsec maximum

115 mAmps maximum

B-2

SPECIFICATIONS

Cable Types

The FDDI Multimode Fiber Physical Layer Medium Dependent

(MMF-PMD), Twisted Pair Physical Layer Medium Dependent

(TP-PMD), and Single Mode Fiber Physical Medium Dependent

(SMF-PMD) standards define FDDI cable requirements as follows:

Multimode Fiber (as specified in X3T9.5 / 48 - 84 section 7.1):

Core diameter:

Cladding diameter:

Cable attenuation:

62.5

µ m nominal

128.0

µ m maximum

122.0

µ m minimum

≤

2.5 dB/km typical

Unshielded Twisted Pair (as specified in EIA/TIA TSB-36 / TSB-40):

Cable / Connector: Category 5

Single Mode Fiber (as specified in X3T9.5 / 88 - 155 section 7.1):

Core diameter:

Cladding diameter:

8.7

µ m +/- 0.5

µ m

127.0

µ m maximum

Cable attenuation:

≤

0.5 dB/km typical

Cable Length

The FDDI standard specifies the following cable lengths:

Maximum total cable length: 100 km (62 miles) — dual ring

200 km (124 miles) — wrapped

Maximum multimode cable length between adjacent nodes:

Maximum UTP

2 km (1.2 miles)

B-3

SPECIFICATIONS cable length between adjacent nodes: 100 m (328.1 feet)

Single mode cable length between adjacent nodes: 40 km (24 miles) maximum

25 km (15 miles) typical

FDDI Ring Connections

You can attach the FDMMIM to the ring as a Dual Attached Station

(DAS). The two duplex receptacles (FDDI A and FDDI B) on the front of the FDMMIM are keyed to accept Type A (Primary In/Secondary

Out) and Type B (Secondary In/Primary Out) Media Interface

Connectors.

Forwarding and Filtering

Forwarding

Ethernet to/from FDDI: 14,880 packets/sec

Filtering

Ethernet:

FDDI:

14,880 packets/sec

446,429 packets/sec

Power Requirements

To move data at the FDDI data rate of 100 Mb/sec requires that

FDDI modules consume more power than Ethernet or Token Ring modules. Power requirements vary slightly from one FDMMIM to another, depending on the FDMMIM mother board you have.

To determine your FDMMIM power requirements:

• Locate the serial number on the front panel of the FDMMIM

• Match the beginning of the serial number on the FDMMIM with one of the following numbers.

Note: Depending on your FDMMIM version, you may have to preface

B-4

SPECIFICATIONS serial numbers with number 940. In other words, a serial number beginning with 0671 is the same as one starting with 9400671.

Use the following power consumption numbers to help plan your chassis / MIM configuration. Refer to Chapter 2, Installing the

FDMMIM, for information on adding MIMs to an MMAC, and configuring your MMAC with FDDI modules.

FDMMIM (SN 0671):

FDMMIM (SN 0710):

10.5 Amp at 5 Vdc

8.0 Amp at 5 Vdc

FDMMIM (SN 0737): 6.0 Amp at 5 Vdc

FDMMIM-04 (SN 0565): 15.3 Amp at 5 Vdc



FDMMIM-24:

FDMMIM-30:

10.5 Amp at 5 Vdc

15.3 Amp at 5 Vdc

Bridge Database

Acquired database capacity: 8191 static or dynamic entries

MIBs

FDDI MIB - RFC 1285

MIB II - RFC 1213

Bridge - MIB RFC 1286

Cabletron FDDI MIB (ctsmt- mib)

Cabletron Bridge MIB (ctbridge-mib)

Cabletron Common MIB (common-mib)

Cabletron Chassis MIB (ctchassis-mib)

Cabletron Download MIB (ctdownload-mib)

B-5

SPECIFICATIONS

Environmental

Storage temperature: -40

°

C minimum

85

°

C maximum

Operating temperature: 5

°

C minimum

40

°

C maximum

Operating humidity: 5% to 95% non-condensing

Optical Bypass Switch Interface

Optical bypass devices attached to the FDMMIM must meet the following requirements for attenuation and interchannel isolation:

Attenuation:

Interchannel isolation:

1.0 dB typical; 2.5 dB worst case

50 dB

Safety

This unit meets the safety requirements of UL 1950, CSA C22.2

No. 950, and EN 60950; the EMI requirements of FCC Class A and

EN 55022 Class A; and the EMC requirements of EN 50082-1.

Note: It is the responsibility of the person who sells the system to which the FDMMIM will be a part to ensure that the total system meets allowed limits of conducted and radiated emissions.

B-6

BASIC FDDI NETWORKS

APPENDIX C


This Appendix covers basic Fiber Distributed Data Interface (FDDI) network operation and concepts that are critical to FDDI network design and installation. ANSI Standard X3T9.5 provides greater detail on FDDI access methods and should be referenced whenever more complete information is needed. Specific areas that are presented here include:

• Basic FDDI Concepts

• FDDI Devices

• Design and Installation Considerations

BASIC FDDI CONCEPTS

An FDDI network is a high-speed network (100 Mbit/sec.) capable of reliable data transmission using fiber optic cabling. The fiber optic media provides increased bandwidth, immunity from electrical noise, security, and permits the use of longer cable segments making FDDI a feasible alternative in LAN backbone applications, or as a back-end or front-end network between processors.

FDDI Media Access Protocol

The FDDI standard X3T9.5 describes the media access and token passing protocol for FDDI networks. Each station attached to an

FDDI ring is identified by a unique station address, differentiating it from all other stations. Transmission is controlled through the use of a special frame called a token.

The token holder is the only station that can transmit. The token circulates around the ring from station to station. Each station receives the token from the station preceding it on the ring, retains it while transmitting data (frames) and then passes (transmits) the token on to the next active station on the ring.

C-1


When a station has a frame waiting to transmit, the station captures the token at the next opportunity, transmits the data frame, and then reissues the token. (A Token Holding Timer (THT) controls the maximum length of time that any station may retain the token.) As the data frame circulates around the ring, it is received and repeated by each station on the ring. When the frame arrives at the station defined by the destination address, the frame is copied into the receiving station’s buffer and forwarded with information reflecting the receipt of the frame and related frame status. When the data frame has circulated completely around the ring, the source station strips the data frame from the ring.

FDDI networks use duplex fiber optic cable for point-to-point connections between a number of stations to form two closed loops.

The two rings serve as redundant (primary and secondary) data paths that operate as counter-rotating rings. Redundant rings facilitate recovery procedures in the event of a ring segment failure. This recovery is similar to Token Ring/IEEE 802.5 networks and is discussed in greater detail later in this section.

The FDDI standard defines two ring access methods, single

attachment and dual attachment (see Figure C-1). Dual attached

stations (DAS) and dual attached concentrators (DAC) connect to both primary and secondary rings and are capable of restoring ring continuity in the event of a segment failure. Single attached

stations (SAS) and single attached concentrators (SAC) are incapable of restoring ring continuity and therefore cannot be installed on the main ring path. Instead, single attached devices access the main ring through a DAC and duplex fiber optic cable connections that form branches extending from the DAC out to each of the attached SASs to create a Ring of Trees topology. The DAC controls main ring access to the attached SASs, restoring the continuity of the ring whenever an attached SAS fails or is disconnected or turned-off.

C-2


Ethernet/802.3

Network

Ethernet/802.3

Network

ETHERNET to

FDDI BRIDGE

Ethernet to FDDI

Bridge

ETHERNET to FDDI

BRIDGE

FDDI

NETWORK

DUAL

ATTACHED

STATION

File

Server

DUAL ATTACHED

CONCENTRATOR

Single Attached

Stations

SINGLE ATTACHED

CONCENTRATOR

Figure C-1. Typical FDDI Physical Installation

Reliability

Since FDDI networks employ a ring topology, the entire network is vulnerable to the frailties of each ring segment and failures of the individual stations. The ring of trees topology reduces the risk of a single node bringing the entire network down. To further reduce this vulnerability, a redundant data path is provided in the main ring trunk cabling. In theory, the ring topology requires media that is capable of only one-way traffic to achieve the circular flow of data. In practice, an FDDI ring uses media that provides two fiber optic ring paths, a primary ring and a secondary ring. The secondary ring is used to restore the continuity of the ring in the event of a failed node or trunk segment (broken trunk cable). Figure C-2 illustrates how the open ends of the primary ring are wrapped into the secondary ring, restoring continuity through the creation of a new ring.

C-3


CONCENTRATOR 3

PRIMARY

RING

A B

B

SECONDARY

RING

CONCENTRATOR 2

A

B

WRAP

B A

CONCENTRATOR 1

Figure C-2. Wrapping a Broken Ring

ANSI Standard X3T9.5

The X3T9.5 standard is divided into five sections: Station

Management (SMT), Media Access Control (MAC), two Physical

Layer Medium Dependent (PMD) standards (one for multimode fiber and another, SMF-PMD, for single mode fiber) and a Physical Layer

Protocol (PHY). Each section defines a unique entity of the FDDI station architecture and its operation.

Note: Single mode operation is very similar to multimode operation.

Since the principle difference is the characteristics of the optic transceivers and fiber optic medium, only the multimode PMD is discussed here.

The entities described by X3T9.5 perform many of the functions required in the lower layers of the OSI network model Data Link and

Physical Layers (Figure C-3).

C-4


Application

Presentation

Session

Transport

Network

Data Link

Physical

Data Link

LLC

MAC

Media Access Control

• Medium Addressing

• Data Checking

• Data Framing

Physical

PHY

Physical Layer Protocol

• Symbol Coding/Decoding

• Symbol Framing

• Clock Rate

PMD or SMF-PMD

Physical Layer Medium Dependent

• Power Levels

• Transmitter

• Receiver

• Optical Interface

• Connector Types

SMT

Station Management

• Fault Isolation and

Recovery

• Station Configuration

• Scheduling Procedures

Figure C-3. FDDI Structure and the OSI Network Model

The PMD standard establishes the physical characteristics of the network connection, including the fiber optic transmitter power levels, receiver sensitivity, the fiber optic cable type, the type of connectors, and acceptable losses between nodes. Optically encoded information that is received by the PMD at the fiber optic media connection is converted to electrically encoded information and presented to the PHY sublayer. Information that is transmitted from the station reverses this process.

The PHY entity implements the physical layer protocol. The PHY receives data frames from the MAC as a series of 4-bit symbols and encodes each 4-bit MAC symbol as a 5-bit symbol for transmission.

The 5-bit symbols are encoded so that each symbol has at least two bit transitions to assure bit-cell synchronization at the remote receiver. Decoding reverses this process for the received frames.

Other functions of the PHY include generation of a 125 Mhz transmit clock, synchronization of the receive clock with an upstream transmitter, encoding and decoding for media control symbols, and in some applications, buffering for the incoming bit stream.

C-5


The MAC entity is the lower sublayer of the Data Link layer. The upper sublayer, Logical Link Control (LLC) serves as an interface between the OSI model and the FDDI network. The MAC element, under control of Station Management, performs many of the tasks associated with frame preparation and media access: ring scheduling, token generation, timers that monitor ring activity, ring initialization, and beaconing. Other tasks for the MAC entity include assembling data frames, maintaining medium addressing, and generating and checking data check bytes.

The MAC generates two basic message formats, tokens and frames.

Figure C-4 shows the layout for each message. Control and format bits within the header define specific types of frames and classes of tokens. Data frames to be transmitted are received at the MAC sublayer from the LLC as Service Data Units (SDUs). MAC uses these SDUs to construct Protocol Data Units (PDUs) that are passed on to PHY. The PDUs consists of a MAC header, the encapsulated

SDU, and a Frame Check Sequence (FCS). The FCS is generated by the MAC during transmission.

TOKEN

FRAME

Preamble

≥

16 Symbols

Starting

Delimiter

2 Symbols

Frame

Control

2 Symbols

Ending

Delimiter

2 Symbols

J K

T T

Frame Check

Sequence Coverage

T

Preamble

≥

16 Symbols

Starting

Delimiter

2 Symbols

Frame

Control

2 Symbols

Destination Address

4 or 12 Symbols

Source Address

4 or 12 Symbols

Information

≥

0 Symbol Pairs

Frame Check

Sequence

8 Symbols

Ending

Delimiter

1 Symbol

Frame Status

≥

3 Symbols

Maximum - 9000 symbols

Figure C-4. Token and Frame Formats

SMT (Station Management) manages the FDDI station. It controls internal FDDI station processes and protocol compliance and provides an interface for human intervention. Internal SMT management functions are divided into three major categories: SMT Frame

Services, Ring Management (RMT), and Connection Management

(CMT). Interfaces from SMT to each of these station components permit monitoring and control for a variety of station functions (see

Figure C-5).

C-6


LLC

MAC

Configuration Path

Switch

PHY

In

PMD

Bypass Switch

(optional)

Out

FDDI STATION

SMT

SMT Frame

Services

Ring Management

Configuration Management

Physical Connection

Management

Bypass Switch

Control

LAN

Management

(Agent)

Figure C-5. SMT Management Organization

SMT Frame Services generates and interprets special FDDI frames that are used to control and monitor the network.

Ring Management (RMT) monitors status information from the

MAC and Configuration Management and controls several functions related to the health of the ring.

C-7


Connection Management (CMT) controls physical layer insertion and removal of stations. CMT has three main components:

• Entity Coordination Management (ECM) controls bypass switches and coordinates trace (recovery) functions.

• Configuration Management (CFM) controls how the PHY and MAC entities are configured within a node. Attaching or removing a station from the ring changes the logical structure of the ring.

• Physical Connection Management (PCM) controls the physical connection between adjacent PHYs. It tests the quality of the link and enforces connection rules, screens marginal connections, and supports maintenance activities.

FDDI Connection Rules

One of the primary functions of SMT Connection Management is to control physical connections among A, B, M, and S type ports. The following table summarizes the FDDI connection rules.

A

B

S

M

A

V,U

V

V,U

V

B

V

V,U

V,U

V

S

V,U

V,U

V

V

M

V,P

V,P

V

X

V - valid connection

X - illegal connection

U - undesirable connection

P - valid, but when both A and B are connected to M ports, only the B connection is used. Connecting A and B to M ports creates a dual homing configuration. Dual homing is a method of configuring concentrators with a redundant topology. Figure C-6 illustrates how to configure three concentrators into dual homing configuration.

C-8


Port A

1

Port B

Port M Port M

Port A Port B

Port M

2

Port M

Backup

Connection Port A Port B

Primary

Connection

3

Figure C-6. Dual Homing Topology

Concentrator 3 in Figure C-6 has redundant connections to the main ring through either concentrator 1 or 2. The FDDI connection rules only permit one active connection, Port B. If a cable failure severs concentrator 3’s connection to concentrator 2, CFM will activate the

Port A connection.

FDDI DEVICES

There are four valid station configurations (SAS, DAS, DAC, and

SAC). These are characterized by the mix of FDDI entities within the station (see Figure C-7). All stations must have an SMT, and at least one MAC, one PMD and one PHY. Each physical ring connection requires one PMD and one PHY. A SAS consists of one each, SMT,

MAC, PMD, and PHY while a DAS has two PMDs and two PHYs.

C-9


Single Attached

Concentrator

PMD-3

PHY-3

PMD-2

PHY-2

PMD-1

PHY-1

MAC

SMT

PHY

PMD

In Out

MAC

PHY

PMD

Single Attached

Station

SMT

In Out

MAC MAC PMD-3

PHY-3

PMD-2

PHY-2

PMD-1

PHY-1

Dual Attached

Concentrator

SMT

PHY-A

PMD-A

Primary

In

Secondary

Out

PHY-B

PMD-B

Secondary

In

Primary

Out

MAC MAC

SMT

Primary

In

PHY-A

PMD-A

Secondary

Out

Secondary

In

PHY-B

PMD-B

Dual Attached

Station

Primary

Out

Figure C-7. Valid Station Configurations

FDDI devices are physically attached to the ring using Fixed Shroud

Duplex (FSD) media interface connectors. Four connectors are defined in the X3T9.5 Physical Layer, PMD standard (see Figure

C-7). They provide proper alignment of the trunk fibers for each of the valid configurations. Types A, B, and M are precision connectors, mechanically keyed to assure proper connections to Primary-In and

Primary-Out fibers. Types A and B provide dual attachment to the primary and secondary data paths of the main ring. Type M is used for single attachment stations, at a concentrator end of the SAS lobe.

The Type S connector has a wide, centrally located, keyway and is considered a non-precision connector for use at the station end of a

SAS lobe cable.

C-10

FDDI RECEPTACLES

PRIMARY IN SECONDARY OUT

TYPE A

DUAL

ATTACHMENT SECONDARY IN

TYPE B

PRIMARY OUT

SINGLE

ATTACHMENT

IN

TYPE M

OUT

IN

TYPE S

OUT


FDDI CONNECTORS

Type A

Type B

Type M

Type S

Figure C-8. Duplex Fiber Optic Receptacles and Connectors

Optical bypass switches, concentrators, and bridges are found throughout FDDI networks. These devices are used to create ring topologies to meet the specific needs of different network applications.

Repeaters, often found in other network topologies, are not defined as an entity for FDDI networks. This is because all devices attached to the FDDI main ring must be capable of compliance with the FDDI protocol. They must be dual attached devices, having, as a minimum, two PMD and PHY entities and one MAC and SMT entity. Since, this is the valid configuration for a DAS or DAC, either could serve as a repeater when a main ring segment must be extended beyond the 2 km maximum between nodes. Together with Figure C-10, the following descriptions provide a brief introduction to these components and their network functions. In many cases the specific functions are combined in a single device.

C-11


An optical bypass switch is a device that can be inserted between a station and the FDDI ring connections that lets you remove the station from the ring without disturbing ring continuity. They are usually electrically actuated and provide passive optical switching of both the primary and secondary ring cables. Figure C-9 shows the data paths through the switch in both the bypass and operational

(non-bypassed) states.

BYPASS STATE

Station Power Off

OPERATIONAL STATE

Station Power On

Station Station

FDDI Dual

Optical Bypass

Switch

FDDI

Ring

FDDI Dual

Optical Bypass

Switch

FDDI

Ring

Figure C-9. Optical Bypass Switch

A concentrator is a hub. It provides connections to the dual ring for single attached stations and controls their access to the ring. Each main ring connection port can be optically bypassed when the attached station is disabled or when the branch cable is disconnected.

C-12


Bridging devices for FDDI connect multiple FDDI networks and link an FDDI ring to a network that uses a different MAC layer protocol

(Token Ring or Ethernet). A bridge does not expand an existing FDDI ring, it connects rings. Bridges used to link two different MAC layer protocols, such as FDDI and Ethernet, typically use one of two bridging techniques, encapsulation or translation.

Translation bridges translate packets from a non-FDDI MAC layer protocol to FDDI, allowing, for instance, an Ethernet station to talk to an FDDI station. Encapsulation bridges enclose the non-FDDI frames within the FDDI protocol and therefore must be installed in pairs.

The sending bridge encapsulates the message and the receiving bridge strips the FDDI protocol, restoring the original frame. The bridge maintains routing information used to filter (prevent frames from crossing the bridge) or forward messages across the bridge.

Ethernet/802.3

Network

Ethernet/802.3

Network

ETHERNET to

FDDI BRIDGE

Single Attached

Stations

DUAL ATTACHED

CONCENTRATOR

File

Server

ETHERNET to FDDI

BRIDGE

FDDI

NETWORK

FDDI to

FDDI

BRIDGE

DAS

FDDI

NETWORK

DUAL

ATTACHED

STATION

Ethernet/802.3

Network

DUAL ATTACHED

CONCENTRATOR

DUAL ATTACHED

CONCENTRATOR

ETHERNET to

FDDI BRIDGE

Single Attached

Stations

SINGLE ATTACHED

CONCENTRATOR

Figure C-10. FDDI Devices

C-13


DESIGN CONSIDERATIONS FOR FDDI NETWORKS

The main variables that are of interest to the FDDI network designer are ring length, drive distance (distance between nodes), and the maximum number of stations. While there are many factors that determine the limits set for these design elements, this section examines the ANSI standard and focuses on those factors that you can control in your network.

Ring Length

The maximum FDDI Ring Length is 100 km, a limit that is indirectly set by ANSI standard X3T9.5. It is indirectly set, because the ANSI standard does not specify ring length, rather it defines default design parameters that are based on a total fiber path length of 200 km. To translate fiber path to ring length, remember that there are two counter-rotating rings in an FDDI network. Under normal conditions

(no failed segment), the ring length is the same as the fiber path length, but if a wrap occurs, the length of the fiber path length could nearly double. So a safe formula to establish the maximum ring length is to divide the fiber length by two. This yields a maximum ring length 100 km (one-half of the 200 km fiber path length). In designing your network, you must add up the lengths of the fiber optic cables in your network to determine the total ring length. This includes main ring cables and branch cables that reach from concentrators to its SASs.

Drive Distance

Drive distance is the limit of reliable signal propagation around the ring. It is the greatest distance that a signal can travel on the ring and still be reliably received. For FDDI networks using multimode fiber as defined by the FDDI standard, the maximum drive distance is 2 km. For networks using single mode fiber, the maximum drive distance is 40 km (25 km typical). To the network designer, this means that the maximum cable length between any two network nodes must not exceed the drive distance limit (2 km for multimode;

25 km for single mode).

C-14


In some multimode applications, existing 50/125

µ m or 100/140

µ m fiber can be used over longer distances. However, the cable must conform to the FDDI standard for bandwidth and attenuation to remain compliant with the FDDI standard.

Attenuation

The maximum attenuation (attenuation budget) between any two active connections to the ring, as defined by the FDDI standard, is 11 dB. The budget includes the attenuation of the cabling, splices, connections, and optical bypass switches. The attenuation of the typical multimode fiber optic cable used in FDDI networks is 2.5 dB/ km or 5 dB for the 2 km maximum node separation. When optical bypass switches are installed, each switch could add 2.5 dB to the attenuation. With an 11 dB budget to work with, and 5 dB expended on the cable, the maximum number of bypass switches is two.

Bandwidth

The minimum modal bandwidth of fiber optic cable used in an FDDI network is 500 Mhz at 1300 nm.

Number of Stations

The maximum number of devices in a single FDDI ring is 500. This limit is determined by the propagation delay from 1000 physical connections. With the exception of optical bypass switches, all FDDI devices are counted as two connections against the 1000 physical connection budget. It is easy to see how connections are counted when only dual attached stations are used (1000 divided by 2 connections for each DAS = 500 nodes), but to understand how connections are counted for other device types, refer to Figure C-11. A DAC without attached devices is counted as two connections (main ring connections), the same as a DAS. As each SAS or SAC is attached to the DAC, two connections must be counted against the budget, one for the concentrator port and one for the attached device. This same logic applies to counting connections for a SAC. The multiple ports of the concentrator are not counted until a device is attached.

C-15


1

+ 1

2

SAC

2

DAS

2

16 PHYSICAL CONNECTIONS

DAC

2

SAS

2

SAS

2

SAS

2

SAS

2

SAS

2

Figure C-11. Physical Device Connections

C-16

INDEX

A

access levels 6-8

Alignment Errors 5-11

B

Basic Read 6-8 battery 2-6 back-up RAM 1-8 jumper location 2-7

BLOCKING 5-7, 7-6 bridge configuration switches 2-7

Bridge

Forward Delay 7-3

Hello Time 7-3

ID 7-2

Max Age 7-3

Name 4-7, 6-3

Operation 8-1

Priority 5-7, 7-4

Protocol Data

Unit 5-3, 5-10

Protocol screen 7-2

BOOTP 6-14 switch 6-14

BPDU 5-3, 5-10 bypass relay 2-11 switch cable 2-13

C

Changing Passwords 6-7

CLN 2-16

Collision 2-16

Collisions, TX 5-11

Community Names Table screen 6-7

INDEX

Concentrator Connection

Status 9-2

Concentrator Ports Status 9-3

Configuration

BPDU 5-3, 5-10

MAC 3-5

MMAC 1-1, 1-4 options 2-8 switch location 2-7 switch settings 2-8 confirmation message 5-18

CONSOLE port 3-1 port pin

configuration 3-3 conventions 4-1

CRC Errors 5-10

Current Entries 8-3

D

DAC 5-14

DAS 5-14

DEC 5-6 default password 3-4

Delete Filter Entry screen 8-10

Desig. Root 5-7, 7-4

Designated

Bridge 7-7

Cost 7-7

Port 7-7

Root 5-7, 7-4, 7-7

Detect 4-5 diagnostic tests 3-4

Directed 4-6

DISABLE BRIDGE command 6-6

DISABLED 7-6

I-1

INDEX

Disabled 4-6

Display Filter Entries

Screen 8-5 downloading 6-9, 6-11 dual attached concentrator 5-14 station 5-14 duplex cable connections 2-11

Dynamic Ageing Time 5-6, 8-4

Dynamics 5-6

E

EMME 2-5

ENABLE BRIDGE command 6-6

EEPROM, FLASH 1-8

Error 5-18

Errors, Rx 5-10

Ethernet

Address 4-5 interface 1-6

F

FDCMIM 9-2

FDDI

A and B ports 2-10

Address 4-5

Configuration screen 9-1

Ring Connection

Status 9-3

Slot Location 6-5

Filtered 5-10

Filtering Database screen 8-3

FLASH EEPROM 1-8 format conventions 4-1 forcing a download 6-13

Forwarded 5-10

FORWARDING 7-6

Frame Errors 5-3

Frames

Filtered 5-2

Forwarded 5-2

Received 5-2

Transmitted 5-3

FW version 4-6

Firmware Version 4-6

H

Hello Time 7-3

Hold Time 7-4

Hot Swapping 1-7

I

IEEE 5-6

IEEE 802.1

5-6

IP Address 4-7

IRBM 2-4

IRM 2-4

IRM-2 2-4

IRM-3 2-4

Isolated 4-5, 5-4

J

JP1 2-6

JP6 2-7

L

LANVIEW 1-7, 2-14, 2-15 laser 1-1

Last Reset 6-2

LEARNING 7-6

LISTENING 7-6

Local Memory 1-8

Location 4-7, 6-3

M

M ports 2-13

Management 1-8 station setup 3-1, 6-11

Manual reset 3-6

Maximum Entries 8-3

I-2

memory

Flash EEPROM 1-8 local 1-8

RAM 1-8 shared 1-8

Message 5-18

Bar 4-5

Duration 6-3

Log 4-7

Log capacity 5-19

Log screen 5-19

N

NAS 5-14

Neighbor Information

Frames 5-5

Network Name 6-3

Network Traffic screen 5-1, 5-9

NIF 5-5

Non-Op 4-5

Non-Op-Dup 4-6

None 5-6

Null Attached Station 5-14

O

On-Line 4-6 optical bypass switch 2-11

Overflow, Rx 5-11

Oversized, Rx 5-11

P

passwords 3-4, 6-7

Path Cost 7-3, 7-7

POK 2-16

Port

Name 6-3

OK 2-16

Priority 7-6

State 7-6

Power 2-17

PWR 2-17

INDEX

R

RCV 2-16, 2-17

Rx

Alignment 5-11

CRC 5-10

Errors 5-10

IP Frag Err 5-11

Overflow 5-11

Oversized 5-11

Read-Write 6-8

Receive 2-16, 2-17

Received 5-10

Overflow 5-11

Reset, manual 3-6

RESTART BRIDGE command 6-6

Restarts 6-3

RESTORE DEFAULT

SETTINGS command 6-6

Ring Down, Tx 5-12

Ring Map screen 5-13

Ring Op 2-18, 4-5

Ring Op Count 5-3

Ring State 4-5

Ring-Op-Dup 4-6

RMIM 2-5

Root

Cost 7-3

Port 7-3

ROP 2-18

S

SAC 5-14

SAS 5-14

SAS Port Count 5-5

Set

Date 6-4

IP Address 6-4

Refresh Time 6-3

Time 6-4

Setup screen 6-2 shared memory 1-8

I-3

INDEX single attached concentrator 5-14 station 5-14

Slot Location 6-5

SMT 1-5

SNMP 1-4

Source Address Table size 1-8

Spanning Tree

Algorithm 5-6, 7-1

Special Database screen 8-11

STA 5-6

Standby 2-16, 4-6

Statics 5-6 station bypass switch 2-12 management 1-5 setup 6-11

Status 4-6

STBY 2-16 switch bank 2-7, 2-8

SYOK 2-16

System

Information screen 5-1

OK 2-16

T

terminal configurations 3-2

TFTP Download 6-9

Through-A 5-3

Time

Negotiated 5-5

Since Topology

Change 7-3

Tneg 5-5

Tnotify 5-5

Topology

Change 7-4

Change

Acknowledge 7-7

Change Count 7-2

Total Messages 5-19

Trace 4-6 translation bridging 1-4

Transmissions Aborted 5-11

Transmit 2-14, 2-16

Transmitted 5-10

Twisted Ring 2-17 twisted stations 5-14

TWR 2-17

Tx

Abort 5-11

Collisions 5-11

Overflow 5-12

Ring Down 5-12

Type of

Filtering 5-5, 8-4

STA Protocol 5-6, 6-5

U

UNIX

Download 6-11

Workstation 1-8, 6-11

Uptime 4-5, 7-6

V

VT220 3-1

VT320 3-1

W

Warning 5-18

Wrap 2-18

Wrap-A 5-4

Wrap-AB 5-5

Wrap-B 5-4

WRP 2-18

X

XMT 2-16, 2-17

I-4

No results