Cabletron Systems CSX400, CSX200 User Manual

Download

Title Page

CSX200 and CSX400

User’s Guide

Notice

Cabletron Systems reserves the right to make changes in speciÞcations 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.

The hardware, Þrmware, or software described in this manual is subject to change without notice.

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.

Virus Disclaimer

Cabletron has tested its software with current virus checking technologies. However, because no antivirus system is 100% reliable, we strongly caution you to write protect and then verify that the Licensed Software, prior to installing it, is virus-free with an anti-virus system in which you have conÞdence.

Cabletron Systems makes no representations or warranties to the effect that the Licensed Software is virus-free.

Printed in the United States of America.

Order Number: 9032723 July 1998

Cabletron Systems, Inc. P.O. Box 5005 Rochester, NH 03866-5005

Cabletron Systems , SPECTRUM , BRIM , DNI , FNB , INA , Integrated Network Architecture , LANVIEW , LANVIEW Secure , Multi Media Access Center , MiniMMAC , and TRMM are registered

trademarks, and Bridge/Router Interface Modules , BRIM-A100 , CRBRIM-W/E , CRXMIM ,

CXRMIM , Desktop Network Interface , Distributed LAN Monitoring , Distributed Network Server , DLM , DNSMIM , E1000 , E2000 , E3000 , EFDMIM , EMM-E6 , EMME , EPIM , EPIM-3PS , EPIM-A , EPIM-C , EPIM-F1 , EPIM-F2 , EPIM-F3 , EPIM-T , EPIM-T1 , EPIM-X , ESXMIM , ETSMIM , ETWMIM , FDCMIM-04 , FDCMIM-08 , FDMMIM , FDMMIM-04 , Flexible Network Bus , FOMIM , FORMIM , HubSTACK , IRBM , IRM , IRM-2 , IRM-3 , Media Interface Module , MicroMMAC , MIM , MMAC , MMAC-3 , MMAC-3FNB , MMAC-5 , MMAC-5FNB , MMAC-8 , MMAC-8FNB , MMAC-M8FNB , MMAC-Plus , MRX , MRXI , MRXI-24 , MultiChannel , NB20E , NB25E , NB30 , NB35 , NBR-220/420/620 , RMIM , SecureFast Switch, SecureFast Packet Switching , SFS, SFPS , SPECTRUM Element Manager , SPECTRUM for Open Systems , SPIM-A , SPIM-C , SPIM-F1 , SPIM-F2 , SPIM-T , SPIM-T1 , TPMIM , TPMIM-22 , TPMIM-T1 , TPRMIM , TPRMIM-36 , TPT-T , TRBMIM , TRMM-2 , TRMMIM ,

and TRXI are trademarks of Cabletron Systems, Inc.



AppleTalk, Apple, Macintosh, and TokenTalk are registered trademarks; and Apple Remote Access and EtherTalk are trademarks of Apple Computer, Inc.

SmartBoost is a trademark of American Power Conversion

ST is a registered trademark and C++ is a trademark of AT&T

Banyan and VINES are registered trademarks of Banyan Systems, Inc.

cisco, ciscoSystems, and AGS+ are registered trademarks; and cBus, cisco Router, CRM, IGS, and MGS are trademarks of cisco Systems, Inc.

GatorBox is a registered trademark; and GatorMail, GatorMIM, GatorPrint, GatorShare, GatorStar, GatorStar GX-M, and XGator are trademarks of Cayman Systems, Inc.

CompuServe is a registered trademark of CompuServe Incorporated

X Window System is a trademark of Consortium, Inc.

CTERM, DECnet, and ULTRIX are registered trademarks; and DEC, DEC C++, DECnet-DOS, DECstation, VAX DOCUMENT, VMA, and VT are trademarks of Digital Equipment Corporation

Fore Systems, ForeRunner, and ForeRunner ASX-100 are trademarks of Fore Systems, Inc.

PC/TCP is a registered trademark of FTP Software, Inc.

HP OpenView is a registered trademark of Hewlett-Packard, Inc.

AIX, IBM, OS/2, NetView, and PS/2 are registered trademarks; and AT, Micro Channel, PC, PC-DOS, PC/XT, Personal Computer AT, Operating System/2, Personal System/2, RISC System/6000, and Workplace Shell are trademarks of International Business Machines Corporation

i960 microprocessor is a registered trademark; and Intel and Multichannel are trademarks of Intel Corporation

Microsoft, MS-DOS, and Windows are registered trademarks of Microsoft Corporation

Chameleon, ChameleonNFS, Chameleon 32, IPX/link, and NEWT are trademarks of NETMANAGE, Inc.

NetWare and Novell are registered trademarks; and Internetwork Packet Exchange (IPX), IPX, and Network File System (NFS) are trademarks of Novell, Inc.

Motif and MS are registered trademarks; and Open Software Foundation, OSF, OSF/1, and OSF/Motif are trademarks of The Open Software Foundation, Inc.

Silicon Graphics and IRIS are registered trademarks; and Indigo and IRIX are trademarks of Silicon Graphics, Inc.

NFS, PC-NFS, SPARC, Sun Microsystems, and Sun Workstation are registered trademarks; and OpenWindows, SPARCstation, SPARCstation IPC, SPARCstation IPX, Sun, Sun-2, Sun-3, Sun-4, Sun386i, SunNet, SunOS, SunSPARC, and SunView are trademarks of Sun Microsystems, Inc.

OPEN LOOK and UNIX are registered trademarks of Unix System Laboratories, Inc.

Ethernet, NS, Xerox Network Systems and XNS are trademarks of Xerox Corporation

ANNEX, ANNEX-II, ANNEX-IIe, ANNEX-3, ANNEX-802.5, MICRO-ANNEX-XL, and MICROANNEX-ELS are trademarks of Xylogics, Inc.

MAXserver and Xyplex are trademarks of Xyplex, Inc.

Restricted Rights Notice

(Applicable to licenses to the United States Government only.)

1. Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS

252.227-7013.

Cabletron Systems, Inc., 35 Industrial Way, Rochester, New Hampshire 03867-0505.

2. (a) This computer software is submitted with restricted rights. It may not be used, reproduced, or

disclosed by the Government except as provided in paragraph (b) of this Notice or as otherwise expressly stated in the contract.

(b) This computer software may be:

(1) Used or copied for use in or with the computer or computers for which it was acquired,

including use at any Government installation to which such computer or computers may be transferred;

(2) Used or copied for use in a backup computer if any computer for which it was acquired

is inoperative;

(3) Reproduced for safekeeping (archives) or backup purposes;

(4) Modified, adapted, or combined with other computer software, provided that the

modified, combined, or adapted portions of the derivative software incorporating restricted computer software are made subject to the same restricted rights;

(5) Disclosed to and reproduced for use by support service contractors in accordance with

subparagraphs (b) (1) through (4) of this clause, provided the Government makes such disclosure or reproduction subject to these restricted rights; and

(6) Used or copied for use in or transferred to a replacement computer.

software, it is licensed to the Government, without disclosure prohibitions, with the minimum rights set forth in paragraph (b) of this clause.

(d) Any other rights or limitations regarding the use, duplication, or disclosure of this computer

software are to be expressly stated in, or incorporated in, the contract.

(e) This Notice shall be marked on any reproduction of this computer software, in whole or in part.

iii

Chapter 1 Introduction

HSIM-W6 and HSIM-W84........................................................................................... 1-2

Using the CSX 200 and CSX400 UserÕs Guide .......................................................... 1-2

Related Manuals............................................................................................................ 1-3

Software Conventions .................................................................................................. 1-4

Common Window Fields...................................................................................... 1-4

Using the Mouse ....................................................................................................1-5

Using Window Buttons......................................................................................... 1-6

Getting Help .................................................................................................................. 1-7

Using On-line Help................................................................................................ 1-7

Getting Help from the Cabletron Systems Global Call Center .......................1-7

CSX200 and CSX400 Firmware ................................................................................... 1-8

Chapter 2 CSX200 and 400 Chassis View

Viewing Chassis Information...................................................................................... 2-2

Front Panel Information........................................................................................ 2-3

Menu Structure....................................................................................................... 2-4

The CSX200/400 Port Status Displays................................................................ 2-7

Selecting a Port Status View.......................................................................... 2-7

Port Status Color Codes................................................................................. 2-9

The Chassis Manager Window............................................................................ 2-9

Viewing Hardware Types ...................................................................................2-10

Device Type ................................................................................................... 2-10

Viewing the Port Description...................................................................... 2-11

Managing the Device.................................................................................................. 2-11

Using the Find Source Address Feature ........................................................... 2-12

Viewing I/F Summary Information.................................................................. 2-12

Interface Performance Statistics/Bar Graphs ........................................... 2-14

Viewing Interface Detail.............................................................................. 2-16

Making Sense of Detail Statistics......................................................... 2-18

Enabling and Disabling Ports ............................................................................ 2-18

Chapter 3 CSX200 and CSX400 WAN Conﬁguration

About the CSX200 Series.............................................................................................. 3-1

About the CSX400 ......................................................................................................... 3-2

WAN Redundancy................................................................................................. 3-2

CSX WPIMs.................................................................................................................... 3-3

WAN Logical View ....................................................................................................... 3-5

Contents

WAN Logical View Window Fields.....................................................................3-6

Changing WAN Logical Settings ......................................................................... 3-6

Chapter 4 Bridging

Bridging Basics ..............................................................................................................4-1

About Transparent Bridging................................................................................. 4-2

About Source Route Bridging ..............................................................................4-2

About Source Route-Transparent Bridges .......................................................... 4-4

About Source Route-Translational Bridges ........................................................4-4

Viewing and Managing Bridging Interfaces .............................................................4-6

The Bridge Status Window.......................................................................................... 4-8

Bridge Status Window Information Fields......................................................... 4-8

Accessing Other Options from the Bridge Status Window ...........................4-10

Enabling and Disabling Bridging .............................................................................4-14

Enabling and Disabling Individual Interfaces................................................. 4-14

Enabling and Disabling All Installed Interfaces..............................................4-15

Bridge Statistics ...........................................................................................................4-15

Performance Graphs............................................................................................ 4-15

Bridge Performance Graph Window Fields.............................................. 4-17

ConÞguring the Bridge Performance Graphs........................................... 4-18

The Bridge Detail Breakdown Window..................................................... 4-18

The Bridge Port Detail Breakdown Window ............................................4-20

The Interface Statistics Window.........................................................................4-21

Statistics Window Fields.............................................................................. 4-22

The CSMACD Statistics Window ......................................................................4-23

Receive Errors................................................................................................ 4-24

Transmission Errors...................................................................................... 4-25

Collision Errors .............................................................................................4-26

The PPP Link Statistics Window........................................................................ 4-26

Errors ..............................................................................................................4-27

Statistics..........................................................................................................4-28

The Dot5 Errors Statistics Window....................................................................4-29

Source Route Statistics.........................................................................................4-32

Bridge Source Routing Window Fields......................................................4-33

Received Frames ...........................................................................................4-33

Transmitted Frames ...................................................................................... 4-34

Discards..........................................................................................................4-34

Bridge Spanning Tree..................................................................................................4-35

ConÞguring the Bridge Spanning Tree Window............................................. 4-36

Bridge Level Fields ..............................................................................................4-36

Bridge Port Level Fields...................................................................................... 4-38

Changing Bridge Spanning Tree Parameters ................................................... 4-40

Changing Bridge Priority ............................................................................4-40

Changing the Spanning Tree Algorithm Protocol Type ..........................4-40

Changing Hello Time ................................................................................... 4-41

Changing Max Age Time .............................................................................4-41

Changing Forwarding Delay Time............................................................. 4-41

Changing Port Priority.................................................................................4-42

Contents

Changing Path Cost...................................................................................... 4-42

Filtering Database ....................................................................................................... 4-42

Filtering Database Window Fields.................................................................... 4-45

ConÞguring the Filtering Database................................................................... 4-46

Altering the Aging Time ..............................................................................4-47

Changing the Type of Entry ........................................................................4-47

Changing the Receive Port.......................................................................... 4-48

Changing the Port Filtering Action............................................................ 4-48

Adding or Deleting Individual Entries ..................................................... 4-48

Clearing All Permanent, Static, or Dynamic Entries ............................... 4-49

Ethernet and Token Ring Special Filter Databases................................................. 4-49

Ethernet Special Filter Database Window........................................................ 4-50

Token Ring Special Filter Database Window................................................... 4-51

Special Filter Database Window Fields ............................................................ 4-52

DeÞning and Editing Filters in the Special Database ..................................... 4-53

Changing the Receive Ports................................................................................ 4-55

Changing the Port Filtering Action................................................................... 4-55

Setting the Port Filtering Action................................................................. 4-55

Clearing the Port Filtering Action.............................................................. 4-56

Enabling and Disabling a Filter .........................................................................4-56

Saving a Set of Filters to a File ........................................................................... 4-56

Source Route ConÞguration ...................................................................................... 4-57

Information on Source Routing .........................................................................4-58

The Source Route ConÞguration Window ....................................................... 4-59

Source Route ConÞguration Fields ............................................................ 4-59

Making and Setting Changes ............................................................................. 4-63

Using the Find Source Address Feature .................................................................. 4-63

The Port Source Addresses Window........................................................................ 4-64

Setting the Aging Time........................................................................................ 4-65

Duplex Modes ............................................................................................................. 4-66

The Duplex Modes Window .............................................................................. 4-67

Duplex Modes Window Fields................................................................... 4-67

Setting the Duplex Mode............................................................................. 4-68

Ethernet Port ConÞguration Window...............................................................4-69

Fast Ethernet Port ConÞguration.............................................................................. 4-70

Setting the Desired Operational Mode for the FE-100TX ..............................4-73

Setting the Desired Operational Mode for the FE-100FX............................... 4-73

SONET Port ConÞguration........................................................................................ 4-74

SONET/SDH ConÞguration.............................................................................. 4-74

SONET/SDH Statistics Window....................................................................... 4-76

Errors .............................................................................................................. 4-78

Statistics.......................................................................................................... 4-80

ConÞguring Broadcast Suppression......................................................................... 4-82

Token Ring Bridge Mode ........................................................................................... 4-83

DeÞning the Bridge Modes ................................................................................ 4-84

Setting The Token Ring Bridge Mode ...............................................................4-84

Using the Physical View Windows........................................................................... 4-85

ETWMIM Ethernet Port Physical View............................................................ 4-85

Ethernet Port Physical Status Fields ..........................................................4-85

ETWMIM Token Ring Port Physical View ....................................................... 4-86

vii

Contents

Index

Token Ring Physical Status Fields .............................................................. 4-87

Using the Interface ConÞguration Window............................................................ 4-89

DeÞning the Bridge Method............................................................................... 4-90

Setting the Bridge Method.................................................................................. 4-91

DeÞning the Protocol Transmission ..................................................................4-91

Using the Bridge and Port ConÞguration Windows..............................................4-92

ConÞguring SmartTrunking ......................................................................................4-96

viii

Chapter 1

Introduction

How to use this guide; related guides; software conventions; getting help; CSX200 and CSX400 ﬁrmware versions

Welcome to the Cabletron SystemsÕ SPECTRUM Element Manager for the

CSX200 and CSX400 UserÕs Guide. We have designed this guide to serve as a

simple reference for using SPECTRUM Element Manager for the CSX200 and

CSX400.

SPECTRUM Element Manager provides management support for both the

CyberSWITCH CSX200 and CyberSWITCH CSX400 stand-alone LAN-to-WAN

access devices. Both the CSX200 series and the CSX400 device support PPP and

Frame Relay WAN protocols, as well as multiprotocol bridging and IP/IPX

routing.

The CSX200 series (CSX 201, 202, and 203) is designed for smaller branch ofÞces

who need up to twelve Ethernet ports connected to a corporate WAN or ISP. Each

CSX200 device has twelve RJ-45 ports and one WAN interface. Before shipping,

the proper Wide Area Port Interface Module (WPIM) is installed in your device,

depending on the technology you need. WPIM connections currently supported

by SPEL include T1 and synchronous. In the future E1, DDS, DI (Drop-and-

Insert), and HDSL will also be supported by SPECTRUM Element Manager. All of

these WPIM options are discussed in Chapter 3, CSX200 and CSX400 WAN

ConÞguration. The CSX200 also supports Point to Point Protocol (PPP), leased

lines, and Frame Relay (RFC1490), providing up to four Permanent Virtual

Connections (PVCs) to corporate ofÞces or the Internet.

The CSX400 is ideal for corporate ofÞces or larger branch sites that require two

individual Ethernet LAN segments with single or dual WAN connectivity. The

two Ethernet ports can be conÞgured with any available EPIM media, while the

two WAN ports can be occupied by any swappable combination of Cabletron

WPIMs. Currently SPECTRUM Element Manager can only manage a T1 or

synchronous connection, but in the future WPIM options will also include DDS,

DI, E1, and HDSL connectivity. Each WPIM can act independently, allowing

1-1

Introduction

NOTES

simultaneous communication, or the pair can be conÞgured to provide redundant channels if desired. Connectivity is available for Point to Point Protocol (PPP), as well as Frame Relay and leased lines.

It is also important to note a Windows 95- and NT-based utility called QuickSET was shipped with your CyberSwitch. This program is designed for point-and-click installation and set-up of CSX200 and CSX400 devices. QuickSET can also be used to conÞgure WPIM settings and routing-bridging protocols, including those WPIMs not currently supported by SPECTRUM Element Manager.

The CSX400 can support an ISDN connection with the WPIM-S/T. However, this connection is designed for WAN redundancy only. A primary ISDN WAN connection is not an option on the CSX400 at this time. See your CSX400 UserÕs Guide or your QuickSET documentation for more information.

If you launch Chassis Manager for a CyberSwitch device and have QuickSET installed, your Utilities menu will display a menu pick for launching QuickSET. See your QuickSET documentation for more information.

HSIM-W6 and HSIM-W84

The HSIM-W6 and HSIM-W84 are Wide Area Networking HSIMs (High Speed Interface Modules), which are functionally identical to the CSX200 and CSX400 in that they provide LAN to WAN switching. They can be installed in SmartSwitch 2000, 6000, and 9000 modules to uplink to WANs. These HSIMs are intelligent modules with their own IP addresses, and are managed separately through SPECTRUM Element Manager. Therefore, users of the HSIM-W6 and HSIM-W84 should also use this manual.

The HSIM-W6 supports IP and IPX bridging or routing services, including IP RIP. Multiple WAN connectivity is similar to that of the CSX400, with the use of two conÞgurable WAN WPIMs. WPIM options are discussed in Chapter 2, Device ConÞguration. Each WPIM on the HSIM-W6 can act independently, allowing simultaneous communication, or the pair can be conÞgured to provide redundant channels if desired.

The HSIM-W84 provides a Þxed conÞguration of four RJ45 ports for four active T1 interfaces.

Using the CSX 200 and CSX400 User’s Guide

This guide describes a number of different applications, each of which provides a portion of the overall management functionality for the CSX200 and CSX400 Cyberswitch devices. This guide contains information about software functions which are accessed directly from the device icon; for information about management functions which are accessed via the SPECTRUM Element Manager

1-2 HSIM-W6 and HSIM-W84

Introduction

primary window menus, consult the SPECTRUM Element Manager UserÕs Guide

and the SPECTRUM Element Manager Tools Guide.

Following is a description of the applications covered in this guide. While we

provide as much background information as we can, we do assume that youÕre

familiar with Ethernet, Frame Relay, and WAN networks, and with general

network management concepts:

¥ Chapter 1, Introduction, provides a list of related documentation, describes

certain software conventions, and shows you how to contact the Cabletron Systems Global Call Center.

¥ Chapter 2, CSX200 and CSX400 Chassis Views, describes the visual displays

of the CSX200 and CSX400 devices and how to use the mouse with the Chassis Views. Also described are some basic functions available only from within the Chassis Views (changing the port display, opening menus and windows, enabling and disabling ports, checking device and port status, and so on).

¥ Chapter 3, CSX200 and CSX400 WAN ConÞguration, describes the physical

conÞguration of the CSX200 and CSX400 devices, including WPIM options, and explains the WAN Logical View window.

¥ Chapter 4, Bridging, discusses the Bridge Status window, instructs you on

conÞguring bridge parameters, and discusses the Bridge Filtering and Special Databases.

In places where information applies to both the CSX200 and CSX400 devices, this

NOTE

manual may make reference to the ÒCSX200/400,Ó or simply the ÒCSX.Ó

Related Manuals

The CSX200 and CSX400 UserÕs Guide is only part of a complete document set

designed to provide comprehensive information about the features available to

you through SPECTRUM Element Manager. Other guides which supply

important information related to managing the CSX200 and CSX400 include:

Cabletron SystemsÕ SPECTRUM Element Manager UserÕs Guide

Cabletron SystemsÕ SPECTRUM Element Manager Tools Guide

Cabletron SystemsÕ SPECTRUM Element Manager Remote Administration Tools

UserÕs Guide

Cabletron SystemsÕ SPECTRUM Element Manager Remote Monitoring (RMON)

UserÕs Guide

Cabletron SystemsÕ Network Troubleshooting Guide

Microsoft CorporationÕs Microsoft Windows UserÕs Guide

Related Manuals 1-3

Introduction

For more information about the capabilities of the CSX200 and CSX400 management modules, consult the appropriate hardware documentation.

Software Conventions

SPECTRUM Element ManagerÕs device user interface contains a number of elements which are common to most windows and which operate the same regardless of which window they appear in. A brief description of some of the most common elements appears below; note that the information provided here is not repeated in the descriptions of speciÞc windows and/or functions.

Common Window Fields

Similar descriptive information is displayed in boxes at the top of most device-speciÞc windows in SPECTRUM Element Manager, as illustrated in

Figure 1-1.

IP Address

Figure 1-1. Sample Window Showing Group Boxes

Device Name

Location

MAC Address

Device Name

Displays the user-deÞned name of the device. The device name can be changed via the System Group window; see the Generic SNMP UserÕs Guide for details.

1-4 Software Conventions

IP Address

Displays the deviceÕs IP (Internet Protocol) Address; this will be the IP address

used to deÞne the device icon. The IP address is assigned via Local Management

to the CSXÕs internal Host interface; it cannot be changed via SPECTRUM

Element Manager.

Location

Displays the user-deÞned location of the device. The location is entered through

the System Group window; see the Generic SNMP UserÕs Guide for details.

MAC Address

Displays the manufacturer-set MAC address associated with the IP address used

to deÞne the device icon; this will be the MAC address assigned to the CSXÕs

internal Host interface. Note that each physical interface in the CSX has its own

MAC address; these addresses are factory-set and cannot be altered.

Using the Mouse

This document assumes you are using a Windows-compatible mouse with two

buttons; if you are using a three button mouse, you should ignore the operation of

the middle button when following procedures in this document. Procedures

within the SPECTRUM Element Manager document set refer to these buttons as

follows:

Introduction

Left Mouse Button

Right Mouse Button

Figure 1-2. Mouse Buttons

For many mouse operations, this document assumes that the left (primary) mouse

button is to be used, and references to activating a menu or button will not

include instructions about which mouse button to use.

However, in instances in which right (secondary) mouse button functionality is

available, instructions will explicitly refer to right mouse button usage. Also, in

situations where you may be switching between mouse buttons in the same area

or window, instructions may also explicitly refer to both left and right mouse

buttons.

Software Conventions 1-5

Introduction

Instructions to perform a mouse operation include the following terms:

¥ Pointing means to position the mouse cursor over an area without pressing

either mouse button.

¥ Clicking means to position the mouse pointer over the indicated target, then

press and release the appropriate mouse button. This is most commonly used

to select or activate objects, such as menus or buttons.

¥ Double-clicking means to position the mouse pointer over the indicated

target, then press and release the mouse button two times in rapid succession.

This is commonly used to activate an objectÕs default operation, such as

opening a window from an icon. Note that there is a distinction made between

Òclick twiceÓ and Òdouble-click,Ó since Òclick twiceÓ implies a slower motion.

¥ Pressing means to position the mouse pointer over the indicated target, then

press and hold the mouse button until the described action is completed. It is

often a pre-cursor to Drag operations.

¥ Dragging means to move the mouse pointer across the screen while holding

the mouse button down. It is often used for drag-and-drop operations to copy

information from one window of the screen into another, and to highlight

editable text.

Using Window Buttons

The button that appears at the bottom of most windows allows you to exit a window and terminate any unsaved changes you have made. You may also have to use this button to close a window after you have made any necessary changes and set them by clicking on an , , or button.

An , , or button appears in windows that have conÞgurable values; it allows you to conÞrm and SET changes you have made to those values. In some windows, you may have to use this button to conÞrm each individual set; in other windows, you can set several values at once and conÞrm the sets with one click on the button.

The button brings up a Help text box with information speciÞc to the current window. For more information concerning Help buttons, see Getting Help, page 1-7.

The command buttons, for example , call up a menu listing the windows, screens, or commands available for that topic.

Any menu topic followed by ... (three dots) Ñ for example Statistics... Ñ calls up a window or screen associated with that topic.

1-6 Software Conventions

Getting Help

This section describes two different methods of getting help for questions or

concerns you may have while using SPECTRUM Element Manager.

Using On-line Help

You can use the buttons to obtain information speciÞc to a particular

window. When you click on a Help button, a window will appear which contains

context-sensitive on-screen documentation that will assist you in the use of the

windows and their associated command and menu options. Note that if a Help

button is grayed out, on-line help has not yet been implemented for the associated

window.

From the Help menu accessed from the Chassis View window menu bar, you can

access on-line Help speciÞc to the Chassis View window, as well as bring up the

Chassis Manager window for reference. Refer to Chapter 2 for information on the

Chassis View and Chassis Manager windows.

Introduction

All of the online help windows use the standard Microsoft Windows help facility. If you

NOTE

are unfamiliar with this feature of Windows, you can select Help from the menu, or Help Ñ>How to Use Help from the primary SPECTRUM Element Manager window, or consult your Microsoft Windows product UserÕs Guide.

Getting Help from the Cabletron Systems Global Call Center

If you need technical support related to SPECTRUM Element Manager, or if you

have any questions, comments, or suggestions related to this manual or any of

our products, please feel free to contact the Cabletron Systems Global Call Center

via one of the following methods:

By phone: (603) 332-9400

24 hours a day, 365 days a year

By mail: Cabletron Systems, Inc.

PO Box 5005 Rochester, NH 03866-5005

By Internet mail: support@ctron.com

FTP: ftp.ctron.com (134.141.197.25)

By BBS: (603) 335-3358

Modem Setting 8N1: 8 data bits, 1 stop bit, No parity

Getting Help 1-7

Introduction

For additional information about Cabletron Systems products, visit our World Wide Web site: http://www.cabletron.com/. For technical support, select Service and Support.

CSX200 and CSX400 Firmware

SPECTRUM Element Manager support for the CSX200 has been tested against Þrmware version 1.02.06. The CSX400 has been tested against Þrmware version

2.00.11. If you have an earlier version of Þrmware and experience problems, contact Cabletron Systems Global Call Center for upgrade information.

As a general rule, Þrmware versions for new products are liable to change rapidly; contact

NOTE

Cabletron Systems Global Call Center for upgrade information for the latest customer release of Þrmware.

1-8 CSX200 and CSX400 Firmware

Chapter 2

CSX200 and 400 Chassis View

Information displayed in the Chassis View window; the Chassis Manager window; Hub management functions

The CSX200/400 Chassis View window is the main screen that immediately

informs you of the current condition of individual ports on your switch via a

graphical display. The Chassis View window also serves as a single point of access

to all other CSX windows and screens, which are discussed throughout this

manual.

It is important to note a Windows 95- and NT-based utility called QuickSET was shipped

NOTE

with your device. This program is designed for point-and-click installation and set-up of CSX200/400 devices. If you launch Chassis Manager for a CyberSWITCH device and have QuickSET installed, your Utilities menu will display a menu pick for launching QuickSET. See your QuickSET documentation for more information.

To access the CSX Chassis View window, use one of the following options:

1. In any map, list, or tree view, double-click on the CSX200 or CSX400 you wish to manage.

1. In any map, list, or tree view, click the left mouse button once to select the

CSX you wish to manage.

2. Select Manage—>Node from the primary window menu bar, or select the Manage Node toolbar button.

1. In any map, list, or tree view, click the right mouse button once to select the

CSX200/400 you wish to manage.

2. On the resulting menu, click to select Manage.

2-1

CSX200 and 400 Chassis View

Viewing Chassis Information

The desired CSX200/400 Chassis View window (Figure 2-1) provides a graphical representation of the device, including a color-coded port display which immediately informs you of the current conÞguration and status of the switch and its ports.

Figure 2-1. CSX200 and CSX400 Chassis View Windows

At the time of this release, the Chassis View windows will only display the bridge ports on

NOTES

TIP

a CSX device.

See your QuickSET documentation for information on managing your Ethernet ports.

Bridging capabilities are discussed in Chapter 4 of this manual.

By clicking in designated areas of the chassis graphical display (as detailed later in this chapter), or by using the menu bar at the top of the Chassis View window, you can access all of the menus that lead to more detailed device- and port-level windows.

When you move the mouse cursor over a management Òhot spotÓ the cursor icon will change into a ÒhandÓ to indicate that clicking in the current location will bring up a management option.

2-2 Viewing Chassis Information

Front Panel Information

The areas surrounding the main chassis area provide the following device information:

The Internet Protocol address assigned to the CSX appears in the title bar of the Chassis View window. IP addresses are assigned via Local Management.

Connection Status

This color-coded area indicates the current state of communication between SPECTRUM Element Manager and the CSX200/400.

¥ Green indicates the CSX200/400 is responding to device polls (valid

connection).

¥ Magenta indicates that the CSX200/400 is in a temporary stand-by mode

while it responds to a physical change in the switch; note that board and port menus are inactive during this stand-by state.

¥ Blue indicates an unknown contact status Ñ polling has not yet been

established with the CSX200/400.

CSX200 and 400 Chassis View

¥ Red indicates the CSX200/400 is not responding to device polls (device is off

line, or device polling has failed across the network for some other reason).

UpTime

The amount of time, in a X day(s) hh:mm:ss format, that the CSX200/400 has been running since the last start-up.

Port Status

If management for your device supports a variable port display (detailed in The

CSX200/400 Port Status Displays later in this chapter), this Þeld will show the

display currently in effect. If only a single port display is available Ñ or if the default view is in effect Ñ this Þeld will state Default.

MAC

Displays the physical layer address assigned to the interface associated with the IP Address used to deÞne the device icon when it was added to SPECTRUM Element Manager. MAC addresses are hard-coded in the device, and are not conÞgurable.

Boot Prom

The revision of BOOT PROM installed in the CSX200/400.

Firmware

The revision of device Þrmware stored in the CSX200/400Õs FLASH PROMs.

Viewing Chassis Information 2-3

CSX200 and 400 Chassis View

Time

The current time, in a 24-hour hh:mm:ss format, set in the CSX200/400Õs internal clock.

Date

The current date, in an mm/dd/yy format, set in the CSX200/400Õs internal clock.

In accordance with Year 2000 compliance requirements, SPECTRUM Element Manager

NOTE

now displays and allows you to set all dates with four-digit year values.

Menu Structure

By clicking on various areas of the CSX200/400 Chassis View display, you can access menus with device- and port-level options, as well as utility applications which apply to the device. The following illustration displays the menu structure and indicates how to use the mouse to access the various menus:

Clicking the on the module index will bring up the Bridge menu, described in Chapter 4.

If QuickSET is installed on your workstation, it will also appear in the Utilities menu.

Figure 2-2. CSX200/400 Chassis View Menu Structure

2-4 Viewing Chassis Information

CSX200 and 400 Chassis View

The Device Menu

From the Device Menu at the Chassis View window menu bar, you can access the following selections:

¥ Device Type..., which displays a window containing a description of the

device being modeled: CSX200/400 - CyberSWITCH.

¥ Edit Device Time/Edit Device Date..., which allows you set the deviceÕs

internal clock.

¥ System Group..., which allows you to manage the CSX200/400 via SNMP MIB

II. Refer to the Generic SNMP Guide for further information.

¥ I/F Summary, which allows you to view statistics (displayed both graphically

and numerically) for the trafÞc processed by each network interface on your CSX200/400. See Viewing I/F Summary Information on page 2-12 for more information.

ridge Status..., which opens a window that provides an overview of bridging

¥ B

information for each interface, and allows you to access all other bridgerelated options. Refer to Chapter 4 of this manual for more information.

¥ Find Source Address...,which opens a window that allows you to search the

802.1d Filtering Database of the CSX200/400 to determine which bridging interface a speciÞed source MAC address is communicating through. If the MAC address is detected as communicating through the switch, the port display will ßash to indicate the bridge interface of interest. Refer to Using the

Find Source Address Feature on page 2-12 for more information.

¥ WAN Status..., which accesses the WAN Logical View window of your device.

See Chapter 3 for more information.

¥ Exit, which closes the CSX200/400 Chassis View window.

The Port Status Menu

The Port Status Menu allows you to select the status information that will be displayed in the port text boxes in the Chassis View window:

¥ Status allows you to select one of four status type displays: Bridge, Bridge

Mapping, Admin, or Operator.

¥ Load will display the portion of network load processed per polling interval

by each interface as a percentage of the theoretical maximum load (10 or 100 Mbits/sec).

¥ Errors allows you to display the number of errors detected per polling interval

by each interface as a percentage of the total number of valid packets processed by the interface.

¥ I/F Mapping will display the interface (if) index associated with each port on

your CSX200/400 switch.

Viewing Chassis Information 2-5

CSX200 and 400 Chassis View

¥ I/F Speed will display the speed (10 or 100 Mbits/sec) of the network segment

attached to each port. The speed of the network management port will be displayed in Kbits/sec.

¥ I/F Type will display the interface type of each port in the CSX200/400 Ñ i.e.,

Eth (ethernet-csmacd) for the bridging interfaces, and PPP for the network management port.

For more information on the port display options available via this menu, see The

CSX200/400 Port Status Displays, later in this chapter.

The Utilities Menu

From the Utilities menu you can select:

¥ MIB Tools, a utility provided by SPECTRUM Element Manager for use with

the CSX200/400. The MIB Tools utility provides direct access to the CSX200/400Õs MIB information. This selection is also available from the T menu at the top of SPECTRUM Element ManagerÕs main window. Refer to your SPECTRUM Element Manager Tools Guide for more information on the MIB Tools utility.

¥ Router ConÞg, for launching the Basic Router application. Basic routing is

described in its own UserÕs Guide, and can also be launched from the Tools menu.

ools

NOTE

¥ RMON, for launching the Remote Network Monitoring application. RMON is

described in its own UserÕs Guide. Like MIB Tools and Basic Router, RMON can also be launched from the Tools menu at the top of SPECTRUM Element ManagerÕs main window. RMON is supported by the CSX400 only.

You will be able to launch the QuickSET application from the Utilities menu, provided it is installed on your machine. See your QuickSET documentation for more information.

The Help Menu

The Help Menu has three selections:

¥ MIBs Supported, which brings up the Chassis Manager window, described

later in this chapter.

¥ Chassis Manager Help, which brings up a help window with information

speciÞcally related to using the Chassis Manager and Chassis View windows.

¥ About Chassis Manager..., which brings up a version window for the Chassis

Manager application in use.

The Port Menus

The menu for bridging ports offers the following selections:

2-6 Viewing Chassis Information

CSX200 and 400 Chassis View

¥ Connection Type... opens a window displaying a description of the

connection type of the selected bridge interface. This description is comprised of text based on the ctIfConnectionType MIB.

¥ Description..., which brings up a window describing the selected port; see

Viewing the Port Description, later in this chapter.

¥ Performance Graph..., which allows you to view the trafÞc going through a

selected bridge. This information is displayed both numerically and graphically, as described in Chapter 4, Bridging.

¥ Source Addressing..., which displays a list of MAC Addresses that

communicate through the selected bridge port.

¥ I/F Statistics..., which allows you to view color-coded statistical information

about the selected bridge port; see Viewing Interface Detail later in this chapter.

¥ Alarm ConÞguration..., which opens the Basic Alarm ConÞguration window.

See Basic Alarm ConÞguration in Chapter 4, RMON Alarms and Events, in your RMON UserÕs Guide for more information. RMON is only supported by the CSX400. A CSX200 device will allow you to open this window, but alarm conÞguration will not be possible.

¥ Statistics... see I/F Statistics, above.

¥ Enable/Disable, which administratively turns the selected bridging port on or

off; see Enabling and Disabling Ports on page 2-18 for more information.

The CSX200/400 Port Status Displays

When you open the Chassis View window, each port on the CSX200/400 will display its Admin status (deÞned below). To change this status display, select one of the options on the Port Status menu, as described in the following sections.

Selecting a Port Status View

To change the status of your ports:

1. Click on Port Status on the menu bar at the top of the Chassis View window; a menu will appear.

2. Drag down (and to the right, if necessary) to select the status information you want to display. The port text boxes will display the appropriate status information.

Port status view options are:

Status

You can view four port Status categories, as follows:

Viewing Chassis Information 2-7

CSX200 and 400 Chassis View

¥ Bridge Ñ FWD, DIS, LRN, LIS, BLK, BRK, or UNK ¥ Bridge Mapping Ñ bridge interface index numbers ¥ Admin Ñ ON or OFF ¥ Operator Ñ ON or OFF

If you have selected the Bridge status mode, a port is considered:

¥ FWD (Forwarding) if the port is on-line and forwarding packets across the

CSX200/400 from one network segment to another.

¥ DIS (Disabled) if bridging at the port has been disabled by management; no

trafÞc can be received or forwarded on this port, including conÞguration information for the bridged topology.

¥ LRN (Learning) if the Forwarding database is being created, or the Spanning

Tree Algorithm is being executed because of a network topology change. The port is monitoring network trafÞc, and learning network addresses.

¥ LIS (Listening) if the port is not adding information to the Þltering database. It

is monitoring Bridge Protocol Data Unit (BPDU) trafÞc while preparing to move to the forwarding state.

¥ BLK (Blocking) if the port is on-line, but Þltering trafÞc from going across the

CSX200/400 from one network segment to another. Bridge topology information will be forwarded by the port.

¥ BRK (Broken) if the physical interface has malfunctioned.

¥ UNK (Unknown) if the interfaceÕs status cannot be determined.

If you have selected Bridge Mapping, the port status boxes will display the bridge interface index numbers assigned to each interface (which may or may not match the ifIndex values displayed via the I/F Mapping option described below).

If you have selected the Ad

¥ ON if the port is enabled by management and has a valid link.

¥ OFF if it has not been enabled or if it has been disabled through management

action.

If you have selected the Operator status mode, a port is considered:

¥ ON if the port is currently forwarding packets.

¥ OFF if the port is not currently forwarding packets.

min status mode, a port is considered:

Load

If you choose Load, the interface text boxes will display the percentage of network load processed by each port during the last polling interval. This percentage reßects the network load generated per polling interval by devices

2-8 Viewing Chassis Information

NOTE

CSX200 and 400 Chassis View

connected to the port compared to the theoretical maximum load (10 or 100 Mbits/sec) of an Ethernet network.

Errors

If you choose the Errors mode, the interface boxes will display the percentage of the total number of valid packets processed by each port during the last polling interval that were error packets. This percentage reßects the number of errors generated during the last polling interval by devices connected to that port compared to the total number of valid packets processed by the port.

In SPECTRUM Element Manager, the polling interval is set via the Tools Ñ> Options...Ñ>Polling option from the main windowÕs menu bar. Refer to the Installing and Using SPECTRUM Element Manager guide for full information on setting device

polling intervals.

I/F Mapping

If you choose the I/F Mapping mode, the interface boxes will display the interface number (IfIndex) associated with each port on the CSX200/400.

I/F Speed

If you choose the I/F Speed mode, the port text boxes will display the speed of the network segment connected to each port. The speed of the network management port will be displayed in Kbits/sec.

I/F Type

If you choose the I/F Type mode, the interface boxes will display the interface type of each port on the CSX200/400 (e.g., Eth, PPP, other).

Port Status Color Codes

The Port Status display options Ñ Bridge, Admin, and Operator Ñ incorporate color coding schemes. For the Admin and Operator Status display options, green = ON, red = OFF, and blue = N/A (not available). For the Bridge Status display option, green = forwarding, blue = disabled, magenta = learning and listening, orange = blocking, red = broken, and gray = unknown.

For all other Port Status selections Ñ Load, Errors, I/F Port Mapping, Speed, and Type Ñ color codes will continue to reßect the most recently selected mode which incorporates its own color coding scheme.

The Chassis Manager Window

Like most networking devices, the CSX200/400 draws its functionality from a collection of proprietary MIBs and IETF RFCs. In addition, the CSX200/400 organizes its MIB data into a series of Òcomponents.Ó A MIB component is a logical grouping of MIB data, and each group controls a deÞned set of objects. For

Viewing Chassis Information 2-9

CSX200 and 400 Chassis View

example, CSX200/400 bridging information is organized into its own component. Note, too, that there is no one-to-one correspondence between MIBs and MIB components. A single MIB component might contain objects from several different proprietary MIBs and RFCs.

The Chassis Manager window, Figure 2-3, is a read-only window that displays the MIBs and the MIB components Ñ and, therefore, the functionality Ñ supported by the currently monitored device.

To view the Chassis Manager window:

1. Click on Help on the menu bar at the top of the Chassis View window.

2. Drag down to MIBs Supported, and release.

The MIBs which provide the CSX200/400’s functionality — both proprietary MIBs and IETF RFCs — are listed here.

MIB Components are listed

here. Remember, there’s no one-to-one correspondence between MIBs and MIB Components.

Figure 2-3. Chassis Manager Window

Viewing Hardware Types

In addition to the graphical displays described above, menu options available at several levels provide speciÞc information about the physical characteristics of the CSX200/400 and its ports.

Device T ype

Choosing the Device Type... option on the Device menu brings up a window that describes the management device being modeled:

2-10 Viewing Chassis Information

Viewing the Port Description

Choosing the Description... option on the individual port interface menus brings up a window that describes the interface you have selected. This description is based on a value returned by the ifDescr MIB. Two possibilities for a CSX interface description are shown in Figure 2-5.

CSX200 and 400 Chassis View

Figure 2-4. Device Type Windows

Figure 2-5. Interface Description Windows

Managing the Device

The Chassis View provides you with the basic tools available to conÞgure your device and keep it operating properly.

Until future releases of SPECTRUM Element Manager provide more comprehensive

NOTE

Managing the Device 2-11

support of the CSX200 and CSX400 CyberSWITCHes, Cabletron recommends that anything beyond the basic conÞguration options described in this section be handled with the QuickSET utility. See your QuickSET documentation for more information.

CSX200 and 400 Chassis View

Management for the CSX200/400 through SPELÕs Chassis View is comprised of source address location, viewing interface statistics, and enabling and disabling ports.

Using the Find Source Address Feature

You can select the Find Source Address option to discover which bridging interface a speciÞed source MAC address is communicating through. When you select the Find Source Address option, a search is made of the 802.1d Bridge Filtering Database to discover the bridge interface associated with the address that you specify. If the search is successful, the corresponding interface will ßash in the Chassis View window. For more information on the Filtering Database and bridging in general, refer to the bridging chapter in your SPECTRUM Element Manager Tools Guide.

Use the Find Source Address feature as follows:

1. Click to display the D

2. Drag to Find Source Address.... The following window will appear.

Figure 2-6. Find Source Address Window

3. In the text ﬁeld in the middle of the window, enter a valid MAC address in Hex format and then click OK.

If the address is found in the 802.1d Bridge Filtering Database, the port through which the address is communicating will ßash in the front panel Chassis View display.

If the address is not found in the Filtering Database, a separate window will appear with a ÒCanÕt Find Source AddressÓ message.

evice pull-down menu.

Viewing I/F Summary Information

The I/F Summary menu option available from the Device menu lets you view statistics for the trafÞc processed by each network interface on your device. The

2-12 Managing the Device

CSX200 and 400 Chassis View

window also provides access to a detailed statistics window that breaks down Transmit and Receive trafÞc for each interface.

To access the I/F Summary window:

1. From the Module View, click on the Device option from the menu bar.

2. Click again to select I/F Summary, and release. The I/F Summary window,

Figure 2-7, will appear.

Figure 2-7. I/F Summary Window

When you open the I/F Summary window, you will see Þelds which describe each interface on your device, as well as a bar graph and statistics which display each interfaceÕs performance.

The following descriptive information is provided for each interface:

UpTime

The UpTime Þeld lists the amount of time, in a days, hh:mm:ss format, that the device has been running since the last start-up.

Index

The index value assigned to each interface on the device.

Type

The type of the interface, distinguished by the physical/link protocol(s) running immediately below the network layer.

Description

A text description of the interface.

Managing the Device 2-13

CSX200 and 400 Chassis View

Physical Status

Displays the current physical status Ñ or operational state Ñ of the interface: Online or Ofßine.

Logical Status

Displays the current logical status Ñ or administrative state Ñ of the interface: Up or Down.

Interface Performance Statistics/Bar Graphs

The statistical values (and, where available, the accompanying bar graphs) in the far-right columns of the I/F Summary window provide a quick summary of interface performance. You can select the statistical value you want to display and the units in which you want those values displayed by using the two menu Þelds directly above the interface display area, as follows:

1. In the right-most menu ﬁeld, click on the down arrow and select the unit in which you wish to display the selected statistic: Load, Raw Counts, or Rate.

NOTE

Bar graphs are only available when Load is the selected base unit; if you select Raw Counts or Rate, the Bar Graph column will be removed from the interface display.

2. Once you have selected the base unit, clic k on the down arro w in the left-most ﬁeld to specify the statistic you’ d lik e to displa y. Note that the options a v ailab le from this menu will vary depending on the base unit you have selected.

After you select a new display mode, the statistics (and graphs, where applicable) will refresh to reßect the current choice, as described below.

Raw Counts

The total count of network trafÞc received or transmitted on the indicated interface since device counters were last reset. Raw counts are provided for the following parameters:

In Octets Octets received on the interface, including framing

characters.

In Packets Packets (both unicast and non-unicast) received by the

device interface and delivered to a higher-layer protocol.

In Discards Packets received by the device interface that were

discarded even though no errors prevented them from being delivered to a higher layer protocol (e.g., to free up buffer space in the device).

2-14 Managing the Device

CSX200 and 400 Chassis View

In Errors Packets received by the device interface that contained

errors that prevented them from being delivered to a higher-layer protocol.

In Unknown Packets received by the device interface that were

discarded because of an unknown or unsupported protocol.

Out Octets Octets transmitted by the interface, including framing

characters.

Out Packets Packets transmitted, at the request of a higher level

protocol, by the device interface to a subnetwork address (both unicast and non-unicast).

Out Discards Outbound packets that were discarded by the device

interface even though no errors were detected that would prevent them from being transmitted. A possible reason for discard would be to free up buffer space in the device.

Out Errors Outbound packets that could not be transmitted by the

device interface because they contained errors.

Load

The number of bytes processed by the indicated interface during the last poll interval in comparison to the theoretical maximum load for that interface type (10 Mbps for standard Ethernet; 100 Mbps for Fast Ethernet). Load is further deÞned by the following parameters:

In Octets The number of bytes received by this interface, expressed

as a percentage of the theoretical maximum load.

Out Octets The number of bytes transmitted by this interface,

expressed as a percentage of the theoretical maximum load.

When you select this option, a Bar Graph Þeld will be added to the interface display area; this Þeld is only available when Load is the selected base unit.

Rate

The count for the selected statistic during the last poll interval. The available parameters are the same as those provided for Raw Counts. Refer to the Raw Counts section, above, for a complete description of each parameter.

Managing the Device 2-15

CSX200 and 400 Chassis View

Viewing Interface Detail

The Interface Statistics window (Figure 2-8) provides detailed MIB-II interface statistical information Ñ including counts for both transmit and receive packets, and error and buffering information Ñ for each individual port interface. Colorcoded pie charts also let you graphically view statistics for both received and transmitted Unicast, Multicast, Discarded, and Error packets.

To open the Interface Statistics window:

1. In the I/F Summary window, click to select the interface for which you’d lik e to view more detailed statistics.

2. Click on Detail. The appropriate I/F Statistics window, Figure 2-8, will appear.

Figure 2-8. Detail Interface Statistics

You can also access this information via the I/F Statistics option available on the

TIP

individual port menus.

Three informational Þelds appear in the upper portion of the window:

Description

Displays the interface description for the currently selected interface: Ethernet, Host, SMB 1, SMB 10, or INB.

2-16 Managing the Device

CSX200 and 400 Chassis View

Address

Displays the MAC (physical) address of the selected interface.

Type

Displays the interface type of the selected port: ethernet-csmacd, sdlc, or other.

The lower portion of the window provides the following transmit and receive statistics (the Þrst four statistics are also graphically displayed in the pie charts).

Unicast

Displays the number of packets transmitted to or received from this interface that had a single, unique destination address. These statistics are displayed in the pie chart, color-coded green.

Non-Unicast

Displays the number of packets transmitted to or received from this interface that had a destination address that is recognized by more than one device on the network segment. The multicast Þeld includes a count of broadcast packets Ñ those that are recognized by all devices on a segment. These statistics are displayed in the pie chart, color-coded dark blue.

Discarded

Displays the number of packets which were discarded even though they contained no errors that would prevent transmission. Good packets are typically discarded to free up buffer space when the network becomes very busy; if this is occurring routinely, it usually means that network trafÞc is overwhelming the device. To solve this problem, you may need to re-conÞgure your bridging parameters, or perhaps re-conÞgure your network to add additional bridges or switches. Consult the Cabletron Systems Network Troubleshooting Guide for more information.

These statistics are displayed in the pie chart, color-coded magenta.

Error

Displays the number of packets received or transmitted that contained errors. These statistics are displayed in the pie chart, color-coded red.

Unknown Protocol

Displays the number of packets received which were discarded because they were created under an unknown or unsupported protocol.

Packets Received

Displays the number of packets received by the selected interface.

Transmit Queue Size

Displays the number of packets currently queued for transmission from this interface. The amount of device memory devoted to buffer space, and the trafÞc level on the target network, determine how large the output packet queue can grow before the device will begin to discard packets.

(Received only)

(Transmit only)

Managing the Device 2-17

CSX200 and 400 Chassis View

Packets T ransmitted

Displays the number of packets transmitted by this interface.

Making Sense of Detail Statistics

The statistics available in this window can give you an idea of how an interface is performing; by using the statistics in a few simple calculations, itÕs also possible to get a sense of an interfaceÕs activity level:

To calculate the percentage of input errors:

Received Errors /Packets Received

To calculate the percentage of output errors:

Transmitted Errors /Packets Transmitted

To calculate the total number of inbound and outbound discards:

Received Discards + Transmitted Discards

To calculate the percentage of inbound packets that were discarded:

Received Discards /Packets Received

To calculate the percentage of outbound packets that were discarded:

(Transmit only)

Transmit Discards /Packets Transmitted

Unlike the Interface Detail window, which this window replaces, the Interface Statistics

NOTE

window does not offer Disable or Test options. These options are available in the Interface Group window, which can be accessed via the System Group window (select System Group... from the Device menu). Refer to your Generic SNMP UserÕs Guide for further information on the System Group and Interface Group windows.

Enabling and Disabling Ports

From the Port menus on the CSX200/400 Chassis View window, you can administratively enable and disable the ports.

When you administratively disable a bridge port, you disconnect that portÕs network from the bridge entirely. The port does not forward any packets, nor does it participate in Spanning Tree operations. Nodes connected to the network can still communicate with each other, but they canÕt communicate with the bridge or with other networks connected to the bridge. When you enable a port, the port moves from the Disabled state, through the Learning and Listening states, to the Forwarding state; bridge port state color codes will change accordingly.

To enable or disable a bridge port:

2-18 Managing the Device

NOTE

CSX200 and 400 Chassis View

1. Click on the desired Port index. The Port menu will appear.

2. Click on Enable to enable the port, or Disable to disable the port. Your port

will now be enabled or disabled as desired.

For more information about bridging functions and how to determine the current state of each bridge port, see Chapter 4 of this manual.

Managing the Device 2-19

CSX200 and 400 Chassis View

2-20 Managing the Device

CSX200 and CSX400 WAN Conﬁguration

Physical CSX device information; CSX WPIMs; the WAN Logical View window

The CSX200 devices have one WAN interface, a Cabletron Wide Area Port Interface Module (WPIM) installed at the factory. The CSX400 has two swappable WAN interfaces, which can currently consist of any combination of CabletronÕs T1/E1/DI, HDSL, DDS, or synchronous WPIMs.

Chapter 3

ItÕs important to note that a Windows 95- and NT-based utility called QuickSET was

NOTE

shipped with your CyberSWITCH. This program is designed for point-and-click installation and set-up of CSX200/400 devices. Currently, QuickSET should be used to conÞgure all WPIM settings and routing/bridging protocols, including those WPIMs not currently supported by Spectrum Element Manager. See your QuickSET documentation for more information. Future releases of SPECTRUM Element Manager will support the CSX200/400 more comprehensively.

The CSX200 series (201, 202, and 203) and the CSX 400 come with a variety of Ethernet LAN and WAN connectivity options. The WPIMs which provide the WAN connection(s) are discussed in this chapter, along with EPIM possibilities for the CSX400.

WAN Logical View on page 3-5 discusses how to access the WAN Logical View

window through SPECTRUM Element ManagerÕs Chassis View. There, you can view your WAN interface settings.

About the CSX200 Series

There are three devices in the CSX200 family: the CSX201, CSX202, and CSX203. Each has twelve RJ-45 Ethernet ports for LAN connection via 10BaseT twisted

3-1

CSX200 and CSX400 WAN Conﬁguration

pair cable, along with a WPIM slot to provide one WAN interface. The model number depends on the type of Wide Area Networking interface installed:

CSX201 Provides a T1/E1 Wide Area uplink

CSX202 Provides a Serial interface (V.35, X.21, RS449, RS232. or

CSX203 Provides a DDS WAN uplink

At the time of this release, SPECTRUM Element Manager does not support a DDS

NOTE

interface on a CSX device. This applies to both the CSX203 and a WPIM-DDS installed on a CSX400. In addition, the WPIM-DI, WPIM-E1, and WPIM-HDSL are also not currently supported by SPECTRUM Element Manager but will be in the future. The Windows 95- and NT-based utility QuickSET, which was shipped with your CSX200/400 device, can be used to conÞgure these WPIMs. See your QuickSET documentation for more information.

See CSX WPIMs on page 3-3 for a description of the WPIM modules that are available for your CSX200.

RS530)

About the CSX400

The CSX400 supports multiple LAN options through two Ethernet ports. These ports can be conÞgured with any combination of the following Cabletron EPIM connections:

EPIM-A Female AUI interface with DB-15 connector

EPIM-C 10Base-2 coaxial port, BNC connectors

EPIM-T 10Base-T twisted pair port with RJ45 connector

EPIM-F1 10BaseFL multi-mode Þber port with SMA connectors

EPIM-F2 10Base-FL multi-mode Þber port with ST connectors

EPIM-F3 802.3 single-mode Þber port with ST connectors

For more information on these EPIMs, consult your hardware documentation.

The CSX400 also consists of two WAN interfaces, which can currently be conÞgured with any combination of Cabletron WPIMs, which are described in

CSX WPIMs on page 3-3.

WAN Redundancy

For a redundant wide-area connection, one of the WAN interfaces on your CSX400 can be conÞgured as a primary link, with the other interface designated

3-2 About the CSX400

as the backup. If the primary link should fail for some reason, the other WAN interface will take over as the wide area link until the primary is restored.

When a WPIM-S/T is installed as the backup interface, that connection will activate and provide an ISDN connection to the wide area network, if the primary WAN link fails. The ISDN WPIM can also provide backup for single or multiple Data Link Connection Interfaces (DLCIs). If a leased line loses a DLCI or a remote ofÞce, for example, the WPIM-S/T will restore a 64K connection for that site while the rest of the connections remain on the leased line. For more information on WAN redundancy and the WPIM-S/T, consult your QuickSET documentation or your hardware documentation.

The WPIM-S/T is designed for WAN ISDN redundancy only and is not intended to be

NOTE

used for a primary WAN connection at this time.

CSX WPIMs

CSX200 and CSX400 WAN Conﬁguration

The following Cabletron WPIMs provide WAN connectivity for the CSX400, HSIM-W84, and the CSX200 series. Currently Cabletron recommends that all

WPIM conÞguration be done through the QuickSET application that was shipped with your device. Consult your QuickSET documentation for more details.

If there is a speciÞc device from the CSX200 series that supports the WPIM, it is noted below. Otherwise, the WPIM can be special-ordered and installed in a general CSX200 (contact the Cabletron Systems Global Call Center for more information).

WPIM-DDS DDS is Digital Data Services, a digital network that

supports data rates of 56Kbps or 64Kbps. The DDS service provides users with dedicated, two-way simultaneous transmission capabilities operating at transfer rates up to 64 Kbps. This WPIM comes with a built-in CSX/DSU. (CSX203)

WPIM-DI The DI (Drop-and-Insert) WPIM provides a T1 interface

through a front-panel RJ45 port and includes a built-in CSU/DSU for direct connection to a T1 line. The WPIMDI provides Full T1 or Fractional T1 using 56 or 64 Kbps Time Slots. It also provides a second Drop-and-Insert interface that allows more than one device, such as a PBX, to share a single T1 connection. (CSX201)

WPIM-E1 This WPIM provides an E1 interface through a front-

panel RJ-45 port and includes a built-in CSU/DSU for direct connection to an E1 line. This WPIM provides Full E1 or Fractional E1 using 56 or 64 Kbps Time Slots with a total throughput of up to 2 Mbps. Time Division

CSX WPIMs 3-3

CSX200 and CSX400 WAN Conﬁguration

WPIM-HDSL This WPIM is designed for campus environments and

WPIM-S/T For the CSX400 only. This WPIM provides an ISDN 128

WPIM-SY Provides a synchronous serial connection of up to 2.048

Multiplexing (TDM) allows for the channelization of up to 31 links of a single physical interface. (CSX201)

provides a connection for sending LAN trafÞc over existing telephone lines at rates up to 1.544Mbps. It can communicate reliably up to a distance of 12,000 feet over Unshielded Twisted Pair (UTP) cabling.

Kbps Basic Rate Interface (BRI) and is designed for an ISDN back-up link for a frame relay or leased line. In the United States and Canada, Network Terminator equipment (NT1) is required to provide an interface between the WPIM-S/T and the ISDN line.

Mbps to external communications equipment (an external CSU/DSU is required). For the CSX202. The following electrical interfaces are supported. An external CSU/DSU is required (consult your hardware documentation for cable pinout information):

EIA-RS449

V.35

EIA-RS232D

X.21

EIA-RS530

EIA-530A

RS530 ALT A

RS530A ALT A

WPIM-T1 Provides a T1 interface through a front-panel RJ45 port

and includes a built-in CSU/DSU for direct connection to a T1 line. The WPIM-T1 provides both Full T1 or Fractional T1 using 56 or 64 Kbps Time Slots, with a total throughput of up to 1.544 Mbps. Time Division Multiplexing (TDM) allows for channelization of up to 24 links over a single physical T1/FT1 interface. CSX201

WPIM-T1/DDS This WPIM provides both a T1 and DDS interface that

allows you to easily switch between the two interfaces by changing the physical cabling and reconÞguring the desired interface with QuickSET or SPEL. Currently, however, SPECTRUM Element Manager does not support a DDS interface on a CSX device.

3-4 CSX WPIMs

For more information on these WPIMs, consult the appropriate hardware documentation or your QuickSET documentation.

WAN Logical View

The WAN Logical View window displays information about the interfaces that are part of your physical port. The windows are identical for the T1 and the Synchronous ports. The number of entries is dependent on the type of port. The T1 port, for example, will have 24 entries.

To open this window:

1. Click on Device on the Chassis View menu bar; the device menu will appear.

2. Drag down to the WAN Status..., then right to Logical View ... and release.

The WAN Logical View window, Figure 3-1, will appear.

CSX200 and CSX400 WAN Conﬁguration

Figure 3-1. WAN Logical View Window

The information in this window is static; use the Refresh button to view updated logical

NOTE

WAN Logical View 3-5

settings and statistics.

CSX200 and CSX400 WAN Conﬁguration

W AN Logical View Window Fields

Displays the interface index; a unique value for each interface that this device connects to.

Protocol

Displays the active Link Layer protocol. This Þeld displays PPP (Point to Point), Frame Relay, or Other.

Compression

Indicates whether data compression is activated or de-activated.

Data compression is not supported by the CSX at this time; therefore, compression will

NOTE

always be de-activated or ÒOffÓ.

MTU

Displays the MTU (Maximum Transfer Unit) for this interface. The MTU is the largest packet size that can be transmitted on the selected interface.

Line Coding

Displays the line coding set for this interface. The Þeld displays INV-HDLC, JBZS, or None. None (the default value) is displayed when the line coding being used on the interface is B8ZS.

CRC Length

The length of the CRC (Cyclical Redundancy Check) for this interface.

Changing WAN Logical Settings

You can change the protocol setting, from your WAN Logical View window.

To do so:

1. Click anywhere on the line of the interface of interest, and the WAN Logical Settings window (Figure 3-2) will appear.

3-6 WAN Logical View

CSX200 and CSX400 WAN Conﬁguration

Figure 3-2. WAN Logical Settings Window

2. Click on the Protocol button to select PPP, Frame Relay, or None. LEX (LAN

Extender) may also appear in the Protocol menu, but it is not applicable to a CSX device.

3. After making your changes, click on OK to exit the window and save the

changes, or Cancel to exit the window without saving the changes.

Note that this window also displays the state of compression on the interface.

NOTE

After exiting the Logical Settings window, the WAN Logical View window will update with the changes you made.

If you do make any conÞguration changes through the WAN Logical Settings window, make sure they donÕt conßict with other conÞgurations made through the QuickSET application.

WAN Logical View 3-7

CSX200 and CSX400 WAN Conﬁguration

3-8 WAN Logical View

Chapter 4

Bridging

A brief explanation of bridging methods; viewing and managing bridging interfaces; using the Bridge Status window; enabling and disabling bridging; viewing bridge statistics; using Spanning Tree; using the Filtering Database; using the Source Route Conﬁguration window; using the Find Source Address feature; using the Port Source Addresses window; conﬁguring duplex modes; using SONET port conﬁguration options; conﬁguring broadcast suppression; using the Token Ring Bridge Mode window; using the Physical View windows; using the Interface Conﬁguration window; using the Bridge Conﬁguration and Port Conﬁguration windows; and conﬁguring SmartTrunking

Bridging Basics

NOTE

Bridges are used in local area networks to connect two or more network segments and to control the ßow of packets between the segments. Ideally, bridges forward packets to another network segment only when necessary.

Bridges are also used to increase the fault tolerance in a local area network by creating redundant bridge paths between network segments. In the event of a bridge or bridge segment failure, an alternate bridge path will be available to network trafÞc, without signiÞcant interruption to its ßow.

The method a bridge uses to forward packets, choose a bridge path, and ensure that a sending stationÕs messages take only one bridge path depends on the bridgeÕs type: Transparent (generally used in Ethernet or FDDI environments) or Source Routing (generally used in Token Ring environments), source routing-transparent, or source route-transparentÑthe two latter being combinations that are found in a mixed network environment.

Not all of the sections in this chapter Ñ Source Routing and Token Ring information, for example Ñ are applicable to your CSX200/400 device.

4-1

Bridging

About T ransparent Bridging

Transparent bridges are most common in Ethernet networks. Individual Transparent bridges monitor packet trafÞc on attached network segments to learn where end stations reside in relation to each segment by mapping the Source Address of each received frame to the port (and segment) it was detected on. This information gets stored in the bridgeÕs Filtering Database.

When in the Forwarding state, the bridge compares a packetÕs destination address to the information in the Filtering Database to determine if the packet should be forwarded to another network segment or Þltered (i.e., not forwarded). A bridge Þlters a packet if it determines that the packetÕs destination address exists on the same side of the bridge as the source address.

If two or more bridges are connected to the same Ethernet LAN segmentÑplaced in parallelÑonly a single bridge must be allowed to forward data frames onto that segment. If two or more bridges were forwarding data frames onto the same Ethernet segment, the network would soon be ßooded.

With a data loop in the topology, bridges would erroneously associate a single source address with multiple bridge ports, and keep proliferating data by forwarding packets in response to the ever-changing (but incorrect) information stored in their Filtering Database.

To avoid such data storms, Transparent bridges communicate with one another on the network by exchanging Bridge Protocol Data Units (BPDUs) to determine the network topology and collectively implement a Spanning Tree Algorithm (STA) that selects a controlling bridge for each LAN segment; this ensures that only a single data route exists between any two end stations and that topology information remains current.

About Source Route Bridging

Source Routing is typically used to connect two or more Token Ring network segments. Source Route bridges differ from Transparent bridges in that they do not build and then use a physical address database to make forwarding decisions. Instead, the source end station transmits packets with a header that contains routing information (added by bridges in the network topology during a route discovery process between end stations); once a route has been determined, a Source Route bridge simply reads the header of a source routed packet to determine whether it is a participant in routing the packet.

In Source Routing, sending and receiving devices employ broadcast packetsÑknown as explorer packetsÑto determine the most efÞcient route for a message to travel. Generally, before a station sends a message, it will Þrst send a test packet to all stations on the same ring; if the sending station receives a response to this packet, it assumes that the destination station is on the same ring and therefore it will not include routing information in frames sent to that station in the future. Any further packets issued between stations will appear to be transparent-style frames without embedded routing information.

4-2 Bridging Basics

Bridging

If the sending station does not receive a response to the test packet, it will send explorer packets to the destination; the explorer packets will be propagated by the networkÕs bridges as either All Paths Explorer (APE) packets or as Spanning Tree Explorer (STE) packets. The task of both packet types is to get the destination station to return speciÞc route information to the sending station (by including an identiÞer for each ring the explorer packet traversed and for each bridge between any rings).

Since the data ßow on a Source Routed network is determined by end stations (unlike a Transparently bridged network), a looped bridge topology is not an issue for data ßow. APE packets are sent from the source station over every possible bridge path to the end station. The original APE frame contains no routing information (e.g., bridge numbers and ring numbers). As the frame is propagated along all available paths to the destination station, each bridge along the way adds its own bridge and ring numbers to the packetÕs RIF before forwarding it, thereby providing route information.

In response to each received APE packet, the destination station directs a reply to the sending station. On receiving the replies, the sending station ideally assumes that the Þrst returned reply contains the most efÞcient route. The sending station then stores the route information and uses it to send subsequent transmissions to the same station.

Because APE frames do increase network trafÞc, some sites may use STE explorer frames as an alternate method of route discovery. With STE exploration, a Spanning Tree Algorithm (either conÞgured automatically via BPDUs or manually via management) is maintained for the sole purpose of determining how to direct an explorer frame during route discovery.

During the discovery process, a source station will send out STE explorer frames into a bridged topology. If a bridge is in a forwarding state according to Spanning Tree, it will forward an explorer frame onto its attached LAN segment (appending the Bridge and LAN Segment IdentiÞers in the appropriate area of the RIF); if the bridge is Þltering, it will discard the explorer frames. In this fashion, only a single explorer frame will reach each individual LAN segment.

Ultimately, the destination station will receive only a single STE packet, and will respond with APE packets (that return to the sending station on all possible bridge paths) or an STE packet (that returns to the sending station via in the reverse route of the STE explorer packet).

Although the Spanning Tree Algorithm determines the bridge path an STE takes to the destination station, during future communication between the stations, bridges along the route will use Source Routing to forward the packet (i.e., the bridges will read the Routing Information Field in the header of speciÞcally routed frames to decide whether to forward them).

Bridging Basics 4-3

Bridging

About Source Route-Transparent Bridges

Because network topologies have developed in which bridges must be able to handle network trafÞc from end stations which support source routing and others which do not, a hybrid type of bridgeÑSource Route-Transparent (SRT)Ñcombines elements of both bridging methods.

An end stationÕs network drivers can be conÞgured in software to use a bit setting in the source address portion of a data frame to indicate whether the station is to operate in a Source Route or Transparently bridged network environment. The Routing Information Indicator (RII) bit of the source address is set to 1 if the station is to use Source Routing; if the station is to operate in a Transparently bridged environment, the RII bit is left unchanged (i.e., at 0).

Not all end stations in a Token Ring environment have network drivers which support Source RoutingÑwhether the drivers are improperly conÞgured via management or they simply are not source-route capable.

In a network with a mix of Source Route and Transparent end stations, data frames from both station types must be bridged correctly. An SRT bridge inspects the RII bit setting of incoming frames to determine whether they should be Transparently bridged (if the RII bit was at 0) or Source Routed (if the RII bit was set to 1) to their destination and will use the appropriate bridge method to forward the frame.

Cabletron has extended the functionality of Ethernet ports on translational bridges, so the

NOTE

ports can be set to Source Route mode.

When an Ethernet port is in Source Route mode, on receipt of an SR packet from a Token Ring port, it will save the Source Routing information and send out the packet transparently. When the response comes back, the source routing information will be restored and sent to the Token Ring port.

About Source Route-Translational Bridges

Because SmartSwitch 2000, 6000 and 9000 modules have the ability to combine mixed network topologies, yet another hybrid bridge methodÑcalled a Source Route Translational bridge (SR-TB)Ñis used by a number of these SmartSwitch modules.

An SR-TB bridge supports both Source Routing and Transparent bridging capabilities, with the added requirement of maintaining Source Route information across an FDDI interfaceÑeither the SmartSwitch 9000 FNB backplane, or an installed FDDI High Speed Interface Module (HSIM).

An SR-TB bridge does this by ÒtranslatingÓ the Token Ring physical frame format (by stripping out routing information, if necessary) so that the frameÕs source address can be recognized on an FDDI, Ethernet, or ATM segment; and then, when data is returned to the source, restoring the necessary route information to forward it along a bridged Token Ring environment.

4-4 Bridging Basics

Bridging

For data that is restricted to the Token Ring networks available from the SR-TB bridgeÕs front panel, the bridging method used is user-conÞgurable via local management to be Source Route-only (bridged packets must include RIF information and will be source routed; no transparent bridging is enabled), Source Route-Transparent (bridging method will be determined by whether the RII bit is set), or Transparent only (no source routed packets will be bridged). Remote management of these interfaces is based upon their current mode (as set through local management).

For data that will ultimately be sent across an FDDI interface to an ATM, Ethernet, FDDI, or another Token Ring segment, the Routing Information Field will be stripped from the packet so the packet can be transparently bridged onto Ethernet or FDDI media; however, the RIF information as well as the source address of the packet is stored in a RIF cache of the SR-TB bridge. When data is returned to that source address, the SR-TB bridge can look up the address information in its RIF cache, append the proper Routing Information onto the packet, and then forward the data to the Token Ring segment.

The RIF cache is a software table that can store up to 8192 entries. An SR-TB bridge updates its RIF cache much like a Transparent bridge dynamically updates its Filtering Database: it learns new address information by listening to incoming packets on each port, saves that information to an Address Database, andÑif the address was learned to be Source-Route capableÑupdates routing information for that source address in the RIF cache. Every time a packet arrives from an FDDI interface for a MAC address that is communicating through the SR-TB bridgeÕs front panel, the RIF cache table is searched for an address/RIF match.

There are conÞguration issues when a Token Ring module receives a packet from an FDDI interface for a destination address that is unknown, and not in its Address Database or RIF cache. You must conÞgure your SR-TB bridge to treat incoming packets with an unknown destination address as either a Source Route or Transparently bridged packet (since Token Ring end stations attached to the module may or may not support Source Routing).

If the bridge is conÞgured to treat an incoming packet with unknown addresses as a Source Routed frame, it will forward it using either STE or ARE frames. If the bridge is conÞgured to treat an incoming packet with an unknown destination as a Transparently bridged frame, it simply forwards the frame.

After a packet with a previously unknown destination has been bridged successfully, and communication begins between the two end nodes, the RIF cache will be updated and packets will be translated as described previously.

Bridging Basics 4-5

Bridging

Viewing and Managing Bridging Interfaces

With SPECTRUM Element Manager, you can view and manage each bridging interface supported by your device, including any installed interface modules, such as BRIMs (Bridge/Router Interface Modules) and HSIMs (High Speed Interface Modules).

You can manage your bridge by using the following windows:

¥ The Bridge Status window provide you with basic information about the

current status of the deviceÕs bridging interfaces, and allow you to enable or disable bridging at each interface of the bridge. The Bridge Status window also lets you access further windows to conÞgure bridging at the device (see The

Bridge Status Window, page 4-8).

¥ Bridge statisticsÑincluding the Performance Graph, Interface Statistics,

CSMACD Statistics, PPP Link Statistics, Dot5 Error Statistics, and Source Route Statistics windowsÑgraphically display the trafÞc passing between

your bridged networks, and let you compare and contrast trafÞc and errors processed by each interface (see Bridge Statistics, page 4-15).

¥ The Spanning Tree window shows bridge port information and protocol

parameters relating to the Spanning Tree AlgorithmÑthe method of determining the controlling bridge when a series of bridges are placed in parallel (see Bridge Spanning Tree, page 4-35).

¥ With the Filtering Database window, you can see the contents of the Static and

Learned databasesÑthe two address databases which construct the IEEE 802.1 Source Address Table. The bridge uses the contents of these databases to make its packet Þltering and forwarding decisions. You can conÞgure entries in these databases to increase bridging efÞciency across your network (see Filtering

Database, page 4-42).

¥ The Ethernet Special Filter Database and Token Ring Special Filter Database

windows let you conÞgure a special Þltering scheme at your bridge. With this scheme, you can enter Þlter parameters for a frame based on the contents of its source or destination address Þeld, type Þeld, or data Þeld (with offset)Ñthen specify the bridging action to take place at each port when a frame matching your speciÞcations is encountered (see Ethernet and Token Ring Special

Filter Databases, page 4-49).

¥ The Duplex Modes window lists each interface on your device and whether

or not it is using Full Duplex mode. The window allows you to switch full duplex mode on and off for each interface on the device. Full Duplex Switched Ethernet (FDSE) mode allows the interface to transmit and receive information simultaneously, effectively doubling the available bandwidth (see Duplex

Modes, page 4-66).

¥ The Broadcast Suppression window enables you to monitor the number of

broadcast packets received by each interface of a selected device, and conÞgure the maximum number of broadcast packets that will be forwarded to other interfaces (see ConÞguring Broadcast Suppression, page 4-82).

4-6 Viewing and Managing Bridging Interfaces

Bridging

¥ The SmartTrunk option invokes the SmartTrunk ConÞguration and Status

window, which enables you to group interfaces logically to achieve greater bandwidth between devices, if both devices support the SmartTrunk feature. There is no limit to the number of ports that can be included in a single Òtrunk,Ó nor is there a limit to the number of trunked ÒinstancesÓ that can be supported (see ConÞguring SmartTrunking, page 4-96).

¥ The Token Ring Bridge Mode window lets you select which type of bridging

that will be used by the Token Ring bridging deviceÑTransparent, Source Routing, or Source Route Transparent (see Token Ring Bridge Mode,

page 4-83).

¥ The Bridge ConÞguration option opens a window that allows you to set

address and routing information for all interfaces on a Token Ring bridging device, including the Bridge Number and the Virtual Ring Number. It also allows you to set source route bridging parameters at the device level (see

Using the Bridge and Port ConÞguration Windows, page 4-92).

¥ The Port ConÞguration option opens a window that allows you to view the

address and routing information for an individual Token Ring bridging interface. This window displays information that is set at the device level via the Bridge ConÞguration window, such as the Bridge Number and the Virtual Ring Number. It also allows you to set source route bridging parameters for that port (see Using the Bridge and Port ConÞguration Windows, page 4-92).

NOTE

¥ The I/F ConÞguration port-level menu option invokes the Interface

ConÞguration window, which allows you to select a bridging method for a Token Ring bridging interface. This window also allows you to select one of three transmission methods that should be used when unknown addresses are received from end stations attached to the selected bridge port (see Using the

Interface ConÞguration Window, page 4-89).

¥ The Source Route ConÞguration option enables you to conÞgure source

routed trafÞc passing between bridge ports (see Source Route ConÞguration,

page 4-57).

The menu options that are available will vary depending on the type of device you are monitoring, and on the type of bridge interfaces supported by the device.

The following sections detail how to use each of the bridge management windows.

Viewing and Managing Bridging Interfaces 4-7

Bridging

The Bridge Status Window

The Bridge Status window provides you with basic information about the current status of bridging across your device. Color-coding of each port display allows you to quickly ascertain the status of each interface. The Bridge Status window also lets you access further windows to control bridging at your device.

To access the Bridge Status window from the Chassis View window:

1. Click on the Device selection in the menu bar. A pull-down menu will appear.

2. Click on Bridge Status…. The Bridge Status window, Figure 4-1, will appear.

Bridge Status Window Information Fields

The following information is provided by the Bridge Status window for the monitored device as a whole and for each individual bridging interface. Since the Bridge Status window can only display four interfaces simultaneously, the and buttons are activated when a device supports over four bridge interfaces, so that you can scroll the display to show all interfaces.

NOTE

When you Þrst open the Bridge Status window the Prev and Next buttons will be grayed out, and a message will appear stating that the application is initializing and processing each interface. You will not be able to scroll the display until after all the bridging interfaces have been processed.

4-8 The Bridge Status Window

Bridging

Figure 4-1. The Bridge Status Window

Up Time

At the top of the Bridge Status window, you can see the time period (in a days, hours, minutes, seconds format) that has elapsed since the device was last reset or initialized.

Bridge State on Interface

Indicates the state of bridging over the port interface. Possible bridge states and their corresponding colors are:

¥ Forwarding (green)ÑThe port is on-line and forwarding packets across the

bridge from one network segment to another.

¥ Disabled (blue)ÑBridging at the port has been disabled by management; no

trafÞc can be received or forwarded on this port, including conÞguration information for the bridged topology.

¥ Listening (magenta)ÑThe port is not adding information to the Þltering

database. It is monitoring Bridge Protocol Data Unit (BPDU) trafÞc while preparing to move to the forwarding state.

¥ Learning (magenta)ÑThe Forwarding database is being created, or the

Spanning Tree Algorithm is being executed because of a network topology change. The port is monitoring network trafÞc, and learning network addresses.

The Bridge Status Window 4-9

Bridging

¥ Blocking (orange)ÑThe port is on-line, but Þltering trafÞc from going across

the bridge from one network segment to another. Bridge topology information will be forwarded by the port.

Interface Type

Indicates the interface type which applies to each device bridging port interface (e.g., ethernet). The interface type (ifType) is a mandatory object type from the SNMP MIB II Interface (if) Group.

Bridge Address

Indicates the physical address of the bridge interface.

Speed

Indicates the speed of the interface in Mb/s or Gb/s.

Accessing Other Options from the Bridge Status Window

At the top of the Bridge Status window, you can click to access a menu that provides other bridge management options. Depending on which device you are monitoring via SPECTRUM Element Manager, the following bridge management options will be available:

¥ The Module TypeÉ window displays a description of the device that is

currently being monitored.

¥ The Find Source AddressÉ window allows you to discover the bridge

interface through which a particular MAC address is communicating (see

Using the Find Source Address Feature, page 4-63).

¥ The Performance GraphÉ window displays statistics for trafÞc across the

entire bridge (see Performance Graphs, page 4-15).

¥ The Spanning TreeÉ window allows you to set the Spanning Tree Algorithm

parameters for bridging on your device (see Bridge Spanning Tree,

page 4-35).

¥ The SmartTrunkÉ option invokes the SmartTrunk ConÞguration and Status

¥ The Filtering DatabaseÉ window lets you see the contents of the Static and

Learned databasesÑthe two address databases which construct the IEEE 802.1 Source Address Table. The bridge uses the contents of these databases to make its packet Þltering and forwarding decisions. You can conÞgure the bridgeÕs acquired and permanent Þltering databases to Þlter or forward trafÞc across the device (see Filtering Database, page 4-42).

4-10 The Bridge Status Window

Bridging

¥ The Ethernet Special Filter DatabaseÉ window lets you conÞgure a special

Þltering scheme at your bridge. With this scheme, you can enter Þlter parameters for a frame based on the contents of its source or destination address Þeld, type Þeld, or data Þeld (with offset)Ñthen specify the bridging action to take place at each port when a frame matching your speciÞcations is encountered (see Ethernet and Token Ring Special Filter Databases,

page 4-49).

¥ The Token Ring Special Filter DatabaseÉ window enables you to deÞne

complex Þlters for transparently bridged Token Ring frames based upon receive port, source or destination MAC address, Token Ring data type, or data Þeld information (up to 64 bytes) (see Ethernet and Token Ring Special Filter

Databases, page 4-49).

¥ The Token Ring Bridge ModeÉ window lets you select which type of

bridging that will be used by the Token Ring bridging deviceÑTransparent, Source Routing, or Source Route Transparent (see Token Ring Bridge Mode,

page 4-83).

¥ The Duplex ModesÉ window allows you to conÞgure duplex mode (on or

off) for supporting interfaces on the device (see Duplex Modes, page 4-66).

¥ Enable Bridge and Disable Bridge options allow you to administratively

activate or deactivate bridging at the device level see (Enabling and Disabling

Bridging, page 4-14).

¥ The Bridge ConÞgurationÉ option opens a window that allows you to set

Using the Bridge and Port ConÞguration Windows, page 4-92).

The individual bridge port index ( ) menu that you can access from the Bridge Status window will provide the following options, depending on which device you are monitoring through SPECTRUM Element Manager:

¥ The Connection TypeÉ window displays a text description of the connection

type of the selected bridge interface.

¥ The DescriptionÉ option displays a text description of a bridge interface from

the ifDescr value of the ifIndex related to the selected port.

¥ The Performance GraphÉ window graphically displays the trafÞc passing

between your bridged networks, and lets you compare and contrast trafÞc processed by each interface (see Performance Graphs, page 4-15).

¥ The Source AddressingÉ window displays the contents of the deviceÕs

Filtering Database with respect to a selected port. This will display the source MAC addresses that have been detected by the port as it forwards data across the network. The window also lets you set the aging timer that controls how long an inactive MAC address will continue to be stored in the Source Address Database before being aged out (see Source Route ConÞguration, page 4-63).

The Bridge Status Window 4-11

Bridging

¥ The PPP Link StatusÉoption invokes the PPP Link Statistics Window, which

enables you to view color-coded statistics related to the PPP (Point-to-Point Protocol) link at the selected interface (see The PPP Link Statistics Window,

page 4-26).

¥ The Source Route StatisticsÉ option opens a window that allows you to view

statistics for source routed trafÞc passing between bridging ports. The window enables you to view the frames that were received, transmitted, and discarded by the bridge (see Source Route Statistics, page 4-32).

¥ The I/F ConÞguration port-level menu option invokes the Interface

Interface ConÞguration Window, page 4-89).

¥ The Source Route ConÞgurationÉ option opens a window that enables you

to conÞgure source routed trafÞc passing between bridging ports (see Source

Route ConÞguration, page 4-57).

¥ The Port ConÞgurationÉ option opens a window that allows you to view the

¥ The Dot5 ErrorsÉ invokes a window that enables you to view 802.5 statistics

for the selected bridging interface on a Token Ring bridging device (see The

Dot5 Errors Statistics Window, page 4-29).

¥ The RMON MAC LayerÉ option opens the Token Ring Statistics window for

Token Ring devices that support RMON, which enables you to view a statistical breakdown of trafÞc on the monitored Token Ring interface (network segment). Note that if the RMON default MIB component is disabled, the RMON MAC Layer menu option will launch the Interface Statistics window. Refer to the SPECTRUM Element Manager Remote Monitoring (RMON) UserÕs Guide for more information on how to enable and disable RMON MIB components. For more information about this menu option, refer to the Statistics chapter in the SPECTRUM Element Manager Remote Monitoring (RMON) UserÕs Guide, and/or the appropriate device-speciÞc UserÕs Guide.

¥ The RMON Promiscuous StatsÉ option opens the Token Ring Promiscuous

Statistics window, which allows you to view statistical information on those packets that carry the normal data ßow across a bridging interface (network segment). Note that if the RMON default MIB component is disabled, the RMON Promiscuous Stats menu option will launch the Interface Statistics window. Refer to the SPECTRUM Element Manager Remote Monitoring (RMON) UserÕs Guide for more information on how to enable and disable RMON MIB components. For more information about this menu option, refer

4-12 The Bridge Status Window

Bridging

to the Statistics chapter in the SPECTRUM Element Manager Remote Monitoring (RMON) UserÕs Guide, and/or the appropriate device-speciÞc UserÕs Guide.

¥ The RMON Alarm ConÞgurationÉ invokes the Basic Alarm ConÞguration

window that enables you to create alarms or actions at a speciÞc bridge interface based on rising and falling thresholds for Kilobits, Broadcast/Multicast packets, or Total Errors. Note that if the RMON default MIB component is disabled, the RMON Alarm ConÞguration menu option will still appear and the window will still display; however, you will not have the ability to set anything. Refer to the SPECTRUM Element Manager Remote Monitoring (RMON) UserÕs Guide for more information on how to enable and disable RMON MIB components. For more information about this menu option, refer to the RMON Alarms and Events chapter in the SPECTRUM Element Manager Remote Monitoring (RMON) UserÕs Guide, and/or the appropriate device-speciÞc UserÕs Guide.

¥ The I/F StatisticsÉ option activates the Interface Statistics Port window,

which allows you to view color-coded statistical information about each individual bridge port on the currently monitored device (see The Interface

Statistics Window, page 4-21).

¥ The ConÞgurationÉ option opens a window that enables you to conÞgure the

selected bridge interface for either full duplex or standard mode (see Ethernet

Port ConÞguration Window, page 4-69).

¥ The Alarm ConÞgurationÉ option appears as a menu choice for Ethernet

devices which support RMON, and invokes the RMON Basic Alarm ConÞguration window that enables you to create alarms or actions at a speciÞc bridge interface based on rising and falling thresholds for Kilobits, Broadcast/Multicast packets, or Total Errors. Note that if the RMON default MIB component is disabled, the Alarm ConÞguration menu option will still appear and the window will still display; however, you will not have the ability to set anything. Refer to the SPECTRUM Element Manager Remote Monitoring (RMON) UserÕs Guide for more information on how to enable and disable RMON MIB components. For more information about this window, refer to the RMON Alarms and Events chapter in the SPECTRUM Element Manager Remote Monitoring (RMON) UserÕs Guide, and/or the appropriate device-speciÞc UserÕs Guide.

¥ The StatisticsÉ option appears as a menu choice for Ethernet devices which

support RMON, and it opens the Ethernet Statistics window, which enables you to view a statistical breakdown of trafÞc at the monitored Ethernet network segment. Note that if the RMON default MIB component is disabled, the Statistics menu option will launch the Interface Statistics window. Refer to the SPECTRUM Element Manager Remote Monitoring (RMON) UserÕs Guide for more information on how to enable and disable RMON MIB components. For more information about this menu option, refer to the Statistics chapter in the SPECTRUM Element Manager Remote Monitoring (RMON) User Õs Guide, and/or the appropriate device-speciÞc UserÕs Guide.

The Bridge Status Window 4-13

Bridging

¥ The Sonet/SDH ConÞgurationÉ window enables you to determine whether

any installed FE-100Sx Fast Ethernet Port Interface Modules or APIM-2x ATM Port Interface Modules, both of which provide direct access to SONET (Synchronous Optical Network) networks, will operate according to SONET or SDH (Synchronous Digital Hierarchy) standards (see SONET/SDH

ConÞguration, page 4-74).

¥ The Sonet StatisticsÉ option opens a window that will let you view some of

the statistical information related to any installed FE100-Sx Fast Ethernet Port Interface Modules or APIM-2x ATM Port Interface Modules (see SONET/SDH

Statistics Window, page 4-76).

¥ The Physical ViewÉ option allows you to view the physical state of the

Ethernet bridge port through the ETW EtherPhysStatus window and the Token Ring bridge port through the Token Ring Phys Status window when you are monitoring an ETWMIM via SPECTRUM Element Manager (see

Using the Physical View Windows, page 4-85).

¥ The CSMACD StatsÉ option opens a window that enables you to view

color-coded statistical information for some Ethernet bridging interfaces, including receive errors, transmission errors, and collision errors (see The

CSMACD Statistics Window, page 4-23).

¥ Enable and Disable options allow you to administratively enable or disable

bridging at the selected interface (see Enabling and Disabling Bridging,

page 4-14).

Enabling and Disabling Bridging

When you disable a bridge port, you disconnect that portÕs network from the bridge entirely. The port does not forward any packets, nor does it participate in Spanning Tree operations. Nodes connected to the network can still communicate with each other, but they canÕt communicate with the bridge and other networks connected to the bridge. When you enable a port, the port moves from the Disabled state through the Learning and Listening states to the Forwarding or Blocking state (as determined by Spanning Tree).

Enabling and Disabling Individual Interfaces

There are two ways to disable an individual port interface:

from the Bridge Status window:

1. Click on the desired Port button ( ) to display the port menu.

2. Drag down to Enable to restart bridging on the selected interface, or Disable to halt bridging across the selected interface.

4-14 Enabling and Disabling Bridging

from the Chassis View window:

1. Click on the appropriate port index to access the Port menu.

2. Drag down to Enable to restart bridging on the selected interface, or Disable

to halt bridging across the selected interface.

Enabling and Disabling All Installed Interfaces

Similarly, there are two ways to disable bridging across all interfaces installed in a device:

from the Bridge Status window:

1. Click on to display the Bridge menu.

2. Drag down to Enable Bridge to enable bridging across all installed interf aces,

or to Disable Bridge to disable bridging across all installed interfaces.

from the Chassis View window:

Bridging

1. Click on the Board Index of the device of interest; the Board menu will

appear.

2. Drag down to Enable Bridge to enable bridging across all installed interfaces ,

or to Disable Bridge to disable bridging across all installed interfaces.

Bridge Statistics

The following sections describe Statistics windows that are available for the bridge that is being monitored via SPECTRUM Element Manager, both at the device and port levels.

Performance Graphs

You use Bridge Performance Graphs to view a color-coded strip chart that shows you the trafÞc being bridged through all networks or an individual network supported by your device. You can conÞgure the display to show frames Þltered, forwarded, or transmitted across the device or its individual bridging interfaces, as well as the number of errors experienced at both levels. The graph has an X axis that indicates the 60-second interval over which charting occurs continuously, while its Y axis measures the number of packets or errors that are processed by the device or its bridging interfaces.

You can select the type of errors you wish to monitor by using the available menu buttons. When you click on the error type you wish to view, the name of that error will appear in the button, and the Performance Graph will refresh. The graph will now generate a strip chart based on the newly deÞned parameters.

Bridge Statistics 4-15

Bridging

At the device level, a Detail button on the window allows you to compare the packets forwarded, Þltered, or transmitted on all networks supported by the device, as well as errors on all networks.

For a selected bridged network, the Detail button allows you to view the number of packets forwarded to, or received from, each other network supported by the device.

To access the device-level Bridge Performance Graph window

from the Bridge Status window:

1. Click on to display the Bridge menu.

2. Drag down to select Performance Graph…. The device Bridge Performance Graph window, Figure 4-2, will appear. (The individual port Bridge Performance Graph windows are similar, except that they display a graph applicable to the selected interface.)

from the Chassis View window:

1. Click on the Board Index of the device of interest; the Board menu will appear.

NOTE

2. Drag down to select Performance Graph…. The device Bridge Performance Graph window, Figure 4-2, will appear.

To access the port-level Bridge Performance Graph window

from the Bridge Status window:

1. Click on the desired Port button ( ) to display the port menu.

2. Drag down to select Performance Graph…. The port Bridge Performance Graph window, Figure 4-2, will appear.

from the Chassis View window:

1. Click on the appropriate port index to access the Port menu.

2. Drag down to select Performance Graph…. The port Bridge Performance Graph window, Figure 4-2, will appear.

The displayed graphic in Figure 2-2 is a device-level window; the window that is displayed at the port level is virtually identical to the one at the device level.

4-16 Bridge Statistics

Figure 4-2. Bridge Performance Graph

Bridge Performance Graph Window Fields

You can select the following statistics to display in the Bridge Performance Graph or Bridge Port Performance Graph. Statistics are provided numerically (as an average or peak value) and graphically. The device is polled for the graphed information every 2 seconds, and numeric values are updated based on this poll.

Bridging

The graph updates at the Þxed two second interval. For the Þrst 60 seconds of graphing, you will note the graph lines extending as each intervalÕs data is added to the graph. Once the Þrst 60 seconds has passed, the newest data is added at the right edge of the graph, and the oldest data is scrolled off to the left.

Peak statistics are based on the peak level of activity returned from a single poll since the Performance Graph window was invoked. A date and time is provided for peak levels.

The Average statistics are updated every two seconds as averaged over the previous four poll intervals (i.e., averaged over a sliding eight second time window).

Frames Forwarded (Green)

Forwarded The number of frames forwarded by the deviceÕs bridge,

at the device or port level.

Nothing The Frames Forwarded function is currently not

measuring any statistics.

Filtered (Magenta)

Filtered The total number of frames Þltered by the deviceÕs

bridge, at the device or port level.

Nothing The Filtered scale is not currently measuring the number

of packets Þltered by the bridge at the device or port level.

Bridge Statistics 4-17

Bridging

Errors (Red)

Total Errors The total number of errors that all bridging interfaces on

the device, or an individual bridge interface, has experienced during bridging.

Nothing The Errors scale is currently not measuring any type of

error packets coming through the device or port.

Xmitted (Blue)

Xmitted The total number of frames transmitted by the selected

bridge interface, or all bridge interfaces.

Nothing The Xmitted scale is not currently measuring the number

of packets Þltered by the bridge or the individual interface.

Conﬁguring the Bridge Performance Graphs

To conÞgure the Bridge Performance Graph:

1. Using the mouse, click on (with green statistics to the right). The Forwarded menu will appear. Click on the desired mode.

2. Click on (with magenta statistics to the right). The Filtered menu will appear. Click on the desired mode.

3. Click on (with red statistics to the right). The Errors menu will appear. Click on the desired mode.

4. Click on (with blue statistics to the right). The Xmitted menu will appear. Click on the desired mode.

Once you have selected a new mode, it will appear in its respective button, and after the next poll the Performance Graph will refresh and begin to measure using the new mode.

The Bridge Detail Breakdown Window

The Bridge Detail Breakdown window allows you to compare the number of frames forwarded, Þltered, and transmitted on the network segments connected to each interface of your device bridge, as well as the number of errors experienced on each interface.

The Bridge Detail Breakdown window will not be available if your device has more than

NOTE

13 bridge ports.

4-18 Bridge Statistics

Bridging

To access this window from the Bridge performance graph, click on . The Bridge Detail Breakdown window, Figure 4-3, will appear.

Figure 4-3. The Bridge Detail Breakdown Window

The following information is available for the network segments connected to

each of the bridge ports on the device, and any installed BRIM or HSIM port. The information is expressed both numerically and in pie charts. Each portÕs

network segment has a corresponding color for its statistics or pie chart segments. Depending on your particular bridge and its conÞguration, the segments are color-coded as follows: light red = LAN 1, light green = LAN 2, yellow = LAN 3,

light gray = LAN 4, light cyan = LAN 5, light blue = LAN 6, green = LAN 7, red = LAN 8, hot pink = LAN 9, light magenta = LAN 10, blue = LAN 11, cyan = LAN 12, black = LAN 13.

The values given in these Þelds are cumulative totals.

Frames Forwarded

The total number of frames forwarded on each portÕs network segment, as read from the device after each poll interval.

Filtered

The total number of frames Þltered on each portÕs network segment, as read from the device after each poll interval.

Errors

The total number of frames (either inbound or outbound) containing errors which prevented them from being processed by each bridge interface, as reported from the device during the last poll interval.

Bridge Statistics 4-19

Bridging

Xmitted

The total number of frames transmitted over each portÕs network segment, as read from the device after each poll interval.

The Bridge Port Detail Breakdown Window

For the selected bridge interface, the Bridge Port Detail Breakdown window allows you to view the number of packets forwarded to or received from each of the other interfaces on your device.

To access the Bridge Port Detail Breakdown window from the port Bridge performance graph, click . The Bridge Port Detail Breakdown window,

Figure 4-4, will appear.

Figure 4-4. The Bridge Port Detail Breakdown Window

The following information is available for each bridge interface on the device. The information is expressed both numerically and in pie charts. The colors corresponding to the forwarding interfaces will vary, depending on which interface is selected.

Forwarded to

The number of frames forwarded by the selected bridge interface to each other interface on the bridge, as read from the device after each poll interval.

Forwarded from

The total number of frames received by the selected bridge interface from each of the other bridge interfaces, as read from the device after each poll interval.

4-20 Bridge Statistics

The Interface Statistics Window

You can use the interface Statistics window to view color-coded statistical information for each individual bridge port on your device. Statistics are provided for both transmit and receive packets at each port, as well as error and buffering information.

Color-coded pie charts in the middle of the window lets you graphically view statistics for Unicast, Non-Unicast, Discarded and Error packets.

To access the Statistics window

from the Bridge Status window:

1. Click on the desired Port button ( ) to display the port menu.

2. Drag down to select I/F Statistics…. The device port I/F Statistics window,

Figure 4-5, will appear.

from the Chassis View window:

1. Click on the appropriate port index to access the Port menu.

Bridging

2. Drag down to select I/F Statistics…. The device port I/F Statistics window,

Figure 4-5, will appear.

Figure 4-5. I/F Statistics Window

Bridge Statistics 4-21

Bridging

Statistics Window Fields

The following informational and statistics Þelds appear in the interface Statistics window.

Three informational Þelds appear in the upper portion of the window:

Description

Describes the interface description for the currently selected port.

Address

Displays the MAC (physical) address of the selected port.

Type

Displays the interface type of the selected port.

The following transmit and receive statistics Þelds are displayed in the lower portion of the window. The Þrst four statistics are also graphically displayed in a pie chart. The statistics are read directly from the device, and are updated with each poll from SPECTRUM Element Manager to the device.

Unicast

Displays the number of packets transmitted to, or received from, this interface that had a single, unique source or destination address. These statistics are displayed in the pie chart (color-coded green).

Non-Unicast

Displays the number of packets transmitted to, or received from, this interface that had a source or destination address that is recognized by more than one device on the network segment. The non-unicast Þeld includes a count of broadcast packetsÑthose that are recognized by all devices on a segment. These statistics are displayed in the pie chart (color-coded dark blue).

Discarded

Displays the number of packets which were discarded even though no errors were detected to prevent transmission. One possible reason for discarding such a packet could be to free up buffer space.

Discarding good packets indicates a very busy network. If a device routinely discards packets, it usually means that network trafÞc is overwhelming the device, perhaps because the device is performing poorly.

These statistics are displayed in the pie chart (color-coded hot pink).

Error

Displays the number of packets received or transmitted that contained errors. These statistics are displayed in the pie chart (color-coded red).

4-22 Bridge Statistics

Unknown Protocol

Displays the number of packets received which were discarded because of an unknown or unsupported protocol. The device bridge interface will discard the packet and increment this counter if it canÕt recognize the packet.

Packets Received

Displays the number of packets received by this interface.

Transmit Queue Size

The number of packets currently queued by the device for transmission from this interface. The amount of device memory devoted to buffer space, and the trafÞc level on the target network, determine how large the output packet queue can grow before the device begins to discard packets.

Packets T ransmitted

Displays the number of packets transmitted by this interface.

The CSMACD Statistics Window

Bridging

The CSCMACD Statistics Windows display statistics for some Ethernet bridging interfaces. Receive errors, transmission errors, and collision errors are displayed in this window.

Three color-coded pie charts allow you to graphically view the breakdowns of each statistics group.

To access the CSMACD Statistics window

from the Bridge Status window:

1. Click on the desired Port button ( ) to display the port menu.

2. Drag down to select CSMACD Stats…. The device port CSMACD Statistics

window, Figure 4-6, will appear.

from the Chassis View window:

1. Click on the appropriate port index to access the Port menu.

2. Drag down to select CSMACD Stats…. The device port CSMACD Statistics

window, Figure 4-6, will appear.

Bridge Statistics 4-23

Bridging

Receive Errors

Figure 4-6. CSMACD Statistics Window

Each of the receive, transmission, and collision errors are described in detail below.

Alignment

The number of frames received on a particular interface that contain a nonintegral number of bytes (color-coded green). Misaligned packets can result from a MAC layer packet formation problem, or from a cabling problem that is corrupting or losing data.

FCS

The number of frames received on a particular interface that are an integral number of bytes in length, but do not pass the FCS (Frame Check Sequence) check.

FCS, or Frame Check Sequence, errors occur when packets are somehow damaged on transit. When each packet is transmitted, the transmitting interface computes a frame check sequence (FCS) value based on the contents of the packet, and appends that value to the packet. The receiving interface performs the same computation; if the FCS values differ, the packet is assumed to have been corrupted and is counted as an FCS error.

4-24 Bridge Statistics

Bridging

SQE Test

Displays the number of times that the SQE Test Error message is generated by the PLS sublayer on the selected interface.

The SQE (Signal Quality Error) Test tests the collision detect circuitry after each transmission. If the SQE Test fails, a SQE Test Error is sent to the interface to indicate that the collision detect circuitry is malfunctioning.

Carrier Sense

Displays the number of times that the carrier sense condition was lost or never asserted when attempting to transmit a frame on a particular interface.

Carrier sense describes the action an interface desiring to transmit will take to listen to the communication channel to see if any other interface is transmitting. If a Òcarrier is sensed,Ó the sensing interface will wait a random length of time, and then attempt to transmit.

Frame T oo Long

Displays the amount of frames received on this interface that exceed the maximum permitted frame size.

Transmission Errors

Internal MAC

The number of frames that failed to be received by the interface due to an internal MAC sublayer receive error. These errors are only counted if a Frame Too Long, Alignment, or FCS Error did not occur along with the internal MAC error.

Receive Errors

Displays the total number of receive errors of all types that were detected by the selected interface while it was receiving a transmission.

Deferred

Displays the number of frames for which the Þrst transmission attempt on this interface is delayed because the medium is busy.

Internal MAC

The number of frames for which transmission fails due to an internal MAC sublayer transmit error. This error is only counted in this window if there have not been corresponding Late Collisions, Excessive Collisions, or Carrier Sense Errors.

Transmit Errors

The total of transmission errors of all types that occurred while the selected interface was attempting to transmit frames.

Bridge Statistics 4-25

Bridging

Collision Errors

Single

Displays the number of successfully transmitted frames on the selected interface for which transmission was prevented by one collision.

Multiple

Displays the number of successfully transmitted frames on the selected interface for which transmission was prevented by more than one collision.

Late

Displays the number of times that a collision has been detected on this interface later than 51.2 microseconds into the transmission of the packet on a 10 Mbit/s system or later than 5.12 microseconds on a 100 Mbit/s system.

Excessive

Displays the number of frames from this interface for which transmission was not complete due to excessive collisions.

Collision Errors

Displays the total number of collision errors of all types that occurred during transmission from this interface.

The PPP Link Statistics Window

The PPP Link Status menu option opens the PPP Link Statistics window, which enables you to view color-coded statistics related to the PPP (Point-to-Point Protocol) link at the selected interface.

The Point-to-Point Protocol is a standard method of transporting multiprotocol datagrams over point-to-point links. A PPP Link provides full-duplex communication between the endpoints, allowing a simultaneous bidirectional operation that should maintain the order in which data packets are transmitted.

To access the PPP Link Statistics window

from the Bridge Status window:

1. Click on the desired Port button ( ) to display the port menu.

2. Drag down to select PPP Link Status…. The device port PPP Link Statistics window, Figure 4-7, will appear.

from the Chassis View window:

1. Click on the appropriate port index to access the Port menu.

2. Drag down to select PPP Link Status…. The device port PPP Link Statistics window, Figure 4-7, will appear.

4-26 Bridge Statistics

Bridging

Errors

Figure 4-7. PPP Link Statistics Window

Each of the errors and statistics related to the PPP Link at the selected bridging interface is described in detail below.

Bad Addresses

The Bad Addresses Þeld displays the number of packets received with an incorrect Address Þeld.

Bad Controls

The Bad Controls Þeld displays the number of packets received on the selected interface that have an incorrect Control Þeld.

Packets T oo Long

The Packets Too Long Þeld displays the number of received packets that were discarded because their length exceeded the MRU (Maximum Receive Unit). Note that packets that are longer than the MRU and that are successfully received and processed are not included in the count.

Bridge Statistics 4-27

Bridging

Statistics

Bad FCSs

The Bad FCSs Þeld displays the number of received packets that were discarded due to having an incorrect FCS (Frame Check Sequence) value.

Total Errors

The Total Errors Þeld displays the total number of errors of all types: Bad Addresses, Bad Controls, Packets Too Long, and Bad FCSs.

Local MRU

The Local MRU Þeld displays the current value of the MRU (Maximum Receive Unit) for the local PPP entity. This value is the MRU that the remote entity uses when sending packets to the local PPP entity. The MRU is the maximum length of data information (included ÒpaddedÓ data octets, but excluding the Protocol Þeld which identiÞes the datagramÕs protocol type) that can be received by this interface. The default MRU size is 1500 octets. The auto-negotiation process may establish another value for MRU if consent is given at both ends of the PPP link (if either the local or remote PPP entity informs the other that larger packets can be sent, or requests that smaller packets be sent).

Remote MRU

The Remote MRU Þeld displays the current value of the MRU (Maximum Receive Unit) established for the remote interface at the other end of the PPP Link. This value is the MRU that the local entity uses when sending packets to the remote PPP entity.

Local to Peer ACC Map

The Local to Peer ACC Map Þeld displays the current value of the Asynchronous Control Character (ACC) Map used for sending packets from the local PPP entity to the remote PPP entity. In effect, this is the ACC Map that is required in order to ensure that all characters can be successfully transmitted through the local modem. The actual ACC Map used on the transmit side of the link will be a combination of the local nodeÕs pppLinkConÞgTransmitACCMap and the remote nodeÕs pppLinkConÞgReceiveACCMap.

Peer to Local ACC Map

The Peer to Local ACC Map Þeld displays the Asynchronous Control Character (ACC) Map used by the remote PPP entity when transmitting packets to the local PPP entity. In effect, this is the ACC Map that is required in order to ensure that the local modem will successfully receive all characters. The actual ACC Map used on the receive side of the link will be a combination of the local nodeÕs pppLinkConÞgReceiveACCMap and the remote nodeÕs pppLinkConÞgTransmitACCMap.

4-28 Bridge Statistics

Bridging

Local to Remote Protocol Compression

The Local to Remote Protocol Compression Þeld determines whether or not the local PPP entity uses Protocol Compression when transmitting packets to the remote PPP entity.

Remote to Local Protocol Compression

The Remote to Local Protocol Compression Þeld determines whether or not the remote PPP entity uses Protocol Compression when transmitting packets to the local PPP entity.

Local to Remote AC Compression

The Local to Remote AC Compression Þeld determines whether or not the local PPP entity uses Address and Control (AC) Compression when transmitting packets to the remote PPP entity.

Remote to Local AC Compression

The Remote to Local AC Compression Þeld determines whether or not the remote PPP entity uses Address and Control (AC) Compression when transmitting packets to the local PPP entity.

Transmit FCS Size

The Transmit FCS Size Þeld displays the size of the Frame Check Sequence (FCS), in bits, that the local node generates when sending packets to the remote node. Currently, only a 16 bit FCS is supported.

Receive FCS Size

The Receive FCS Size Þeld displays the size of the Frame Check Sequence (FCS), in bits, that the remote node generates when sending packets to the local node. Currently, only a 16 bit FCS is supported.

The Dot5 Errors Statistics Window

The Dot5 Errors menu option invokes the Dot5 Errors Statistics window, which enables you to view IEEE 802.5 error statistics reported for a Token Ring bridge interface.

To access the Dot5 Errors Statistics window

from the Bridge Status window:

1. Click on the desired Port button ( ) to display the port menu.

2. Drag down to select Dot5 Errors…. The device port Dot5 Errors Statistics

window, Figure 4-8, will appear.

Bridge Statistics 4-29

Bridging

from the Chassis View window:

1. Click on the appropriate port index to access the Port menu.

2. Drag down to select Dot5 Errors…. The device port Dot5 Errors Statistics window, Figure 4-8, will appear.

Figure 4-8. Dot5 Errors Statistics Window

Each type of IETF 802.5 error detected by the selected station port is described in detail below.

Line Errors

The Line Errors Þeld displays the number of the line errors detected by the selected port. This error indicates a nondata bit between the starting and ending delimiters of data or a frame check sequence (FCS) error.

Burst Errors

The Burst Errors Þeld displays the number of burst errors detected by the selected port. This error indicates a bit information encoding error when there are no transitions between 0 and 1 over Þve half-bit times.

4-30 Bridge Statistics

Bridging

A. C. Errors

The A. C. Errors Þeld displays the number of A. C. errors detected by the selected port. These errors count protocol data units (PDUs) that contain errors in the A or C bits.

Abort Sequences

The Abort Sequences Þeld displays the number of abort sequences transmitted by the selected port.

Internal Errors

The Internal Errors Þeld displays the number of recoverable internal errors detected by the selected port.

Lost Frames

The Lost Frames Þeld displays the number of lost frames transmitted by the selected port that have not returned because the Timer Return to Repeat (TRR) expired.

Congestion Errors

The Congestion Errors Þeld displays the number of times the selected port has not been able to copy a protocol data unit (PDU) addressed to it because of a lack of internal buffering.

F. C. Errors

The F. C. Errors Þeld displays the number of protocol data units (PDUs) addressed to the selected station with the A bits already set to 1. This error indicates that a possible electrical line disturbance or a duplicate address has occurred on the ring.

Token Errors

The Token Errors Þeld displays the number of times that the selected station, acting as the active monitor, detected an error condition that needed a token transmitted.

Soft Errors

The Soft Errors Þeld displays the number of soft errors detected by the selected port.

Hard Errors

The Hard Errors Þeld displays the number of immediately recoverable fatal errors detected by the selected port.

Signal Loss

The Signal Loss Þeld displays the number of times that the selected port has detected the loss of a signal condition from the ring.

Bridge Statistics 4-31

Bridging

Transmit Beacons

The Transmit Beacons Þeld displays the number of beacon frames transmitted by the selected station.

Recoveries

The Recoveries Þeld displays the number of frames the ring has been purged and recovered into a normal operating state.

Lobe Wires

The Lobe Wires Þeld displays the number of open or short circuits detected in the lobe data path.

Removes

The Removes Þeld displays the number of Remove Ring Station MAC frame requests detected by the selected port.

Singles

The Singles Þeld displays the number of times the selected station has detected that it is the only station on the ring. This error may indicate that the station is the Þrst on the ring or that there is a hardware problem.

Frequency Errors

The Frequency Errors Þeld displays the number of times that the selected station detected a larger-than-allowed difference between the incoming frequency and the expected frequency.

Source Route Statistics

The Source Route Statistics menu option invokes the Bridge Source Routing window, which allows you to compare the statistics on frames received, transmitted, and discarded at the Token Ring interfaces of devices that are bridging from a source routing network to a transparent network.

To access the Bridge Source Routing window

from the Bridge Status window:

1. Click on the desired Port button ( ) to display the port menu.

2. Drag down to select Source Route Statistics…. The Bridge Source Routing window, Figure 4-9, will appear.

from the Chassis View window:

1. Click on the appropriate port index to access the Port menu.

2. Drag down to select Source Route Statistics…. The Bridge Source Routing window, Figure 4-9, will appear.

4-32 Bridge Statistics

Bridging

Figure 4-9. The Bridge Source Routing Window

Bridge Source Routing Window Fields

The Bridge Source Routing window provides basic statistics for source routed trafÞc passing between the bridging ports. Pie charts graphically break down the statistical information.

The following frame types are provided for frames transmitted, received, and discarded by the bridge ports. All statistics are calculated since the device was last reset or powered up.

Received Frames

Specif. Routed

Displays the total number of SpeciÞcally Routed Explorer frames received by the indicated port from its attached segment.

These frames have data and routing information and are following a known route from source to destination.

All Paths Expl.

Displays the total number of All Path Explorer frames received by the indicated port from its attached segment.

Bridge Statistics 4-33

Bridging

Transmitted Frames

When a sending station needs to determine the best route to an intended destination, it transmits an All Paths Explorer (APE) frame. The APE frame contains no routing information; it is propagated along all available paths to the destination station, which then directs a reply back to the source. The Þrst reply received by the original sending station is considered the most efÞcient route and is used in subsequent transmissions.

Span. T ree Expl.

Displays the total number of Spanning Tree Explorer (STE) frames received by the indicated port from its attached segment.

STE frames, also known as Single Route Broadcast frames, follow the topology established by the Spanning Tree Algorithm.

Specif. Routed

Displays the total number of SpeciÞcally Routed Frames transmitted by the indicated port onto its attached segment.

Discards

All Paths Expl.

Displays the total number of All Path Explorer frames transmitted by the indicated port onto its attached segment.

Span T ree Expl.

Displays the total number of Spanning Tree Explorer (STE) frames transmitted by the indicated port onto its attached segment.

Segment Mismatch

Displays the number of explorer frames discarded because their routing descriptor Þeld contained an invalid value for a segment attached to the port.

The routing information Þeld of a SpeciÞcally Routed frame contains LAN Segment In (Ring In)ÐBridge NumberÐLAN Segment Out (Ring Out) information. If the bridgeÕs LAN Segment Out value does not match the LAN Segment Out speciÞed in the frameÕs Routing Information Field, the bridge logs a Segment Mismatch and discards the frame.

Duplicate Segment

Displays the number of frames discarded because the frameÕs Routing Information Field identiÞes a particular segment more than once.

4-34 Bridge Statistics

Hop Cnt. Exceeded

Displays the number of All Paths Explorer frames discarded at the speciÞed port because they exceeded the number of routing descriptors (bridge hops) speciÞed by the Hop Count Limit.

Bridge Spanning Tree

The Bridge Spanning Tree window allows you to display and modify the deviceÕs bridge port information and protocol parameters relating to the Spanning Tree Algorithm.

In a network design with multiple bridges placed in parallel (i.e, attached to the same LAN), data loops must be prevented. The Spanning Tree Algorithm (STA) is the method that bridges use to communicate with each other to ensure that only a single data route exists between any two end stations.

On a LAN interconnected by multiple bridges, Spanning Tree selects a controlling Root Bridge and Port for the entire bridged LAN, and a Designated Bridge and Port for each individual LAN segment. A Designated Port/Bridge for a LAN segment forwards frames from that LAN towards the Root Bridge, or from the Root Bridge onto the LAN. All other bridge ports attached to that LAN are conÞgured to Þlter (block) frames.

Bridging

When data passes from one end station to another across a bridged LAN, it is forwarded through the Designated Bridge/Port for each LAN segment towards the Root Bridge, which in turn forwards frames towards Designated Bridges/Ports on its opposite side.

During the Root Bridge Selection process, all bridges on the network communicate STA information via Bridge Protocol Data Units (BPDUs). With BPDUs, all network bridges collectively determine the current network topology and communicate with each other to ensure that the topology information is kept current.

To access the Bridge Spanning Tree window

from the Bridge Status window:

1. Click on to display the Bridge menu.

2. Drag down to select Spanning T ree…. The Bridge Spanning Tree window,

Figure 4-10, will appear.

from the Chassis View window:

1. Click on the Board Index of the device of interest; the Board menu will

appear.

2. Drag down to select Spanning T ree…. The Bridge Spanning Tree window,

Figure 4-10, will appear.

Bridge Spanning Tree 4-35

Bridging

Figure 4-10. Bridge Spanning Tree Window

Conﬁguring the Bridge Spanning Tree Window

The Bridge Spanning Tree window displays STA parameters and allows you to alter parameters for the device bridge as a whole, and for each individual bridging interface.

The currently selected bridging interface is highlighted in the lower right quadrant of the window. To alter the parameters of another interface, click on the appropriate Port X name listed in the quadrant.

Bridge Level Fields

Bridge Priority

This Þeld displays the ÒpriorityÓ component of the deviceÕs unique bridge identiÞer. The Spanning Tree Algorithm assigns each bridge a unique identiÞer, which is derived from the bridgeÕs MAC address and the Priority. The bridge with the lowest value of bridge identiÞer is selected as the Root. A lower priority number indicates a higher priority; a higher priority enhances a bridgeÕs chance of being selected as the Root.

You can edit this text box to change network topology, if needed. The default value is 8000; the range is 0ÑFFFF hexadecimal.

4-36 Bridge Spanning Tree

TIP

Bridging

Part of a bridgeÕs IdentiÞer is based on its MAC address. In most network installations, performance differences between bridges may be negligible. You may, however, Þnd your data bottle-necked in installations where both a low-performance bridge and a high-performance bridge are attached to the same LAN segment and the two (or more) bridges have the same Priority component set (e.g., at the default 8000 Hex). In such a scenario you may want to alter the Priority component of the higher performance bridge to ensure that it becomes root for the segment (or overall root). Remember, if Priority components are equal, the bridge on the segment with the lowest MAC address would have a better chance of being selected as the root bridgeÑas it would have a lower Bridge IdentiÞer. If your bridges come from multiple vendors, they will have different MAC address values (e.g., Cabletron devices have a lower MAC address than 3Com devices); if they come from the same vendor, the bridge with the earlier manufacture date will have the lower MAC address value.

Root Bridge

Displays the MAC address of the bridge that is currently functioning as the Root Bridge.

Root Cost

Indicates the cost of the data path from this bridge to the Root Bridge. Each port on each bridge adds a ÒcostÓ to a particular path that a frame must travel. For example, if each port in a particular path has a Path Cost of 1, the Root Cost would be a count of the number of bridges along the path. (You can edit the Path Cost of bridge ports as described later.) The Root BridgeÕs Root Cost is 0.

Root Port

This Þeld displays the identiÞer (the physical index number) of the device bridge port that has the lowest cost path to the Root Bridge on the network. If the device is currently the Root Bridge, this Þeld will read 0.

Protocol

Displays the Spanning Tree Algorithm Protocol type the device is currently using. The choices are:

¥ 802.1 ¥ DEC (DEC Lanbridge 100) ¥ None

The following four Þelds display values used for various Spanning Tree timers that are set at the Root Bridge and this bridge. In Spanning Tree operations, the value used for the tree is the one set at the Root Bridge (with the exception of Hold Time, which is a Þxed value); but you can change the value for each bridge on your network in the event that it becomes Root.

Bridge Spanning Tree 4-37

Bridging

Hello Time

This parameter indicates, in seconds, the length of time the Root Bridge (or bridge attempting to become the Root) waits before resending ConÞguration BPDUs. The range for this Þeld is 1 to 10 seconds, with a default value of 2 seconds. The Root Bridge sets the Hello Time.

Max Age

This parameter displays the bridgeÕs BPDU aging timer. This controls the maximum time a BPDU can be retained by the bridge before it is discarded. During normal operation, each bridge in the network receives a new ConÞguration BPDU before the timer expires. If the timer expires before a ConÞguration 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 current Root Bridge on the network sets the Max Age time. The range for this Þeld is 6 to 40 seconds, with a default value of 20 seconds.

Forwarding Delay

This parameter displays the time period which elapses between states while the bridge is moving to the Forwarding state. For example, while moving from a Blocking to a Forwarding state, the port Þrst moves from Blocking to Listening to BPDU activity on the network, remains there for the Forward Delay period, then moves to the Learning State (and remains in it for the Forward Delay period), and Þnally moves into a Forwarding state. This timer is set by the Root Bridge. During a topology change, the Forward Delay is also used as the Filtering Database Aging Time, which ensures that the Filtering Database maintains current topology information.

Hold Time

This parameter displays, in seconds, the minimum time that can elapse between the transmission of ConÞguration BPDUs through a bridge port. The Hold Time ensures that ConÞguration BPDUs are not transmitted too frequently through any bridge port. Receiving a BPDU starts the Hold Timer. After the Hold Timer expires, the port transmits its ConÞguration BPDU to send conÞguration information to the Root. The Hold Time is a Þxed value, as speciÞed by the IEEE

802.1d speciÞcation.

Bridge Port Level Fields

The following Þelds are applicable to each bridge port on the device.

Priority

If two or more ports on the same bridge are connected to the same LAN segment, they will receive the same Root ID/Root Cost/Bridge ID information in ConÞguration BPDUs received at each port. In this case, the BPDUÕs Port ID informationÑthe transmitting portÕs identiÞer and its manageable Priority componentÑis used to determine which is the Designated Port for that segment.

4-38 Bridge Spanning Tree

Bridging

A lower assigned value gives the port a higher Priority when BPDUs are compared. The allowable range is 0ÑFF hexadecimal (0Ñ255 decimal); the default is 80 hexadecimal.

Path Cost

Displays the cost that this port will contribute to the calculation of the overall Root path cost in a ConÞguration BPDU transmitted by this bridge port. You can lower a portÕs Path Cost to make the port more competitive in the selection of the Designated PortÑfor example, you may want to assign a lower path cost to a port on a higher performance bridge. The allowable range is 1 to 65,535.

Designated Cost

Displays the cost of the path to the Root Bridge of the Designated Port on the LAN to which this port is attached. This cost is added to the Path Cost to test the value of the Root Path Cost parameter received in ConÞguration BPDUs.

Designated Root

Displays the unique bridge identiÞer of the bridge that is assumed to be the Root Bridge.

Designated Bridge

Displays the network address portion of the Bridge ID (MAC address/priority component) for the bridge that is believed to be the Designated Bridge for the LAN associated with this port.

The Designated Bridge ID, along with the Designated Port and Port IdentiÞer parameters for the port, is used to determine whether this port should be the Designated Port for the LAN to which it is attached. The Designated Bridge ID is also used to test the value of the Bridge IdentiÞer parameter in received BPDUs.

Designated Port

Displays the network address portion of the Port ID (which includes a manageable priority component) of the port believed to be the Designated Port for the LAN associated with this port.

The Designated Port ID, along with the Designated Bridge and Port IdentiÞer parameters for the port, is used to determine whether this port should be the Designated Port for the LAN to which it is attached. Management also uses it to determine the Bridged LAN topology.

Topology

This indicates how many times the bridgeÕs Topology Change ßag has been changed since the device was last powered up or initialized. It also indicates the time elapsed since the topology last changed. The Topology Change ßag increments each time a bridge enters or leaves the network, or when the Root Bridge ID changes.

Bridge Spanning Tree 4-39

Bridging

Changing Bridge Spanning Tree Parameters

The Bridge Spanning Tree window allows you to update the following parameters for your device bridge. When you have Þnished making changes to the following individual parameters, you must click on at the bottom of the Spanning Tree window to write the changes to the device.

Any values you set at the bridge will cause a Topology Change ßag to be issued in the next

NOTE

Changing Bridge Priority

ConÞguration BPDUs it transmits. This will cause the bridged network to immediately recalculate Spanning Tree and change topology accordingly.

To change the part of the bridge address that contains the identiÞer used in the Spanning Tree Algorithm for priority comparisons:

1. Highlight the Bridge Priority ﬁeld.

2. Enter the new identiﬁer, in hexadecimal format; the allowed range is 0-FFFF hexadecimal.

3. Click on .

The selected Bridge Priority will be applied to the bridge (a lower number indicates a higher priority in the root selection process).

Changing the Spanning Tree Algorithm Protocol Type

To change the type of protocol used in Spanning Tree:

1. Click the mouse on the appropriate option button: 802.1, DEC, or None.

2. Click on .

The selected Spanning Tree Algorithm protocol type will be applied to the bridge. If you selected None, the Spanning Tree Algorithm will be disabled (if it already was enabled). If STA Protocol Type was changed from None to IEEE 802.1 or DEC, you must restart the bridge for the newly selected STA protocol to be applied.

All bridges in a network must use the same Spanning Tree version. Mixing Spanning Tree

CAUTION

Algorithm protocols will cause an unstable network.

4-40 Bridge Spanning Tree

Changing Hello Time

If the bridge is the Root Bridge, or is attempting to become the Root, and you want to change the length of time the bridge waits between sending conÞguration BPDUs:

1. Highlight the Hello Time ﬁeld, and type in a new value.

2. Click on .

The IEEE 802.1d speciÞcation recommends that Hello Time = 2 seconds, with an allowable range of 1 to 10 seconds.

Changing Max Age Time

If the device is the Root Bridge or attempting to become the Root, and you want to change the maximum time that bridge protocol information will be kept before it is discarded:

1. Highlight the Max Age ﬁeld, and type in a new value.

2. Click on .

Bridging

The IEEE 802.1d speciÞcation recommends that Max Age = 20 seconds, with an allowable range of 6 to 40 seconds.

Changing Forwarding Delay Time

If the device is the Root Bridge or attempting to become the Root, and you want to change the time period the bridge will spend in the Listening state (e.g. either listening to BPDU activity on the network while moving from the Blocking to the Learning state or in the Learning state while the bridge is moving from the Listening to the Forwarding state):

1. Highlight the Forwarding Delay ﬁeld, and type in a new value.

2. Click on .

The IEEE 802.1d speciÞcation recommends that Forward Delay = 15 seconds, with an allowable range of 4 to 30 seconds.

To ensure proper operation of the Spanning Tree Algorithm, the IEEE 802.1d speciÞcation

NOTE

recommends that you always observe the following relationship between Forwarding Delay, Max Age, and Hello Time:

2 x (Forwarding Delay - 1.0) > Max Age > 2 x (Hello Time +1.0)

Bridge Spanning Tree 4-41

Bridging

Changing Port Priority

To change the part of the Port Priority used in priority comparisons:

1. If necessary , select the desired port by clicking the mouse to highlight the port

2. Highlight the port Priority ﬁeld, and enter the new priority identiﬁer. Only valid

3. Click on . The new port priority will be saved.

Changing Path Cost

To change the Path Cost:

1. If necessary , select the desired port by clicking the mouse to highlight the port

in the lower right quadrant of the window. The lower left quadrant of the window will now allow you to edit parameters for the selected port.

hexadecimal numbers (0 to FF) are allowed in this ﬁeld. The default is 80 hexadecimal.

in the lower right quadrant of the window. The lower left quadrant of the window will now allow you to edit parameters for the selected port.

2. Highlight the Path Cost ﬁeld, and type in a new v alue from 1 to 65535 decimal (default is 100 decimal).

3. Click on .

The new path cost will be applied to the port.

Filtering Database

The Filtering Database, which makes up the IEEE 802.1 Source Address Table, is used to determine which frames will be forwarded or Þltered across the deviceÕs bridging ports.

During initialization, the bridge copies the contents of its Permanent Database to the Filtering Database. Next, the bridge learns network addresses by entering the source address and port association of each received packet into the Filtering Database. When in the Forwarding state, the bridge examines each received packet, checks it against the Special Database (refer to Ethernet and Token Ring

Special Filter Databases, page 4-49), and then (if no special Þltering applies)

compares the destination address to the contents of the Filtering Database.

If the destination address is located on the network from which the packet was received, the bridge Þlters (does not forward) the packet. If the destination address is located on a different network, the bridge forwards the packet to the appropriate network. If the destination address is not found in the Filtering Database, the bridge forwards the packet to all networks. To keep Filtering Database entries current, older entries are purged after a period of time, which is called the Dynamic Aging Time.

4-42 Filtering Database

Bridging

The Filtering Database consists of two separate databases: the Static and the

Learned Databases.

The Static Database contains addresses that are entered by a network administrator. You add these addresses directly to the database while the bridge is powered up, or to the deviceÕs battery-backed RAM so that they are stored on shutdown until the next power-up.

The Learned Database consists of addresses that accumulate as part of the bridgeÕs learning process as it is up and running. These do not remain in the Source Address Table when the system is shut down. The Learned Database also contains the addresses that are in the Static Database upon start-up of the bridge.

Entries to the Source Address Table are one of four types: Permanent, Static, Dynamic, or Learned.

¥ Permanent entries are addresses that you add to the Static Database (via the

Filtering Database window) that are stored in the deviceÕs battery-backed RAM. Since they remain in the device on shutdown or restart, they are considered ÒPermanent.Ó

¥ Static entries are addresses that you add to the Static Database (via the

Filtering Database window). These entries remain in the device until it is shut down.

NOTE

¥ Dynamic entries are addresses that you add to the Static Database (via the

Filtering Database window). With the Aging Time feature, you set the time period that these addresses are saved in the Source Address Table. Addresses that have not transmitted a packet during one complete cycle of the aging timer are deleted from the database.

¥ Learned entries are addresses that are added to the Learned Database through

the bridgeÕs learning process. With the Aging Time feature, you set the time period that these addresses are saved in the Source Address Table. Addresses which are inactive within a cycle of the aging timer are dropped from the database.

Learned address entries are divided into two types, Learned and Self. Address entries classiÞed as Learned have transmitted frames destined for a device attached to a device portÕs connected segment. Address entries classiÞed as Self are those that have sent a frame with a destination address of one of the deviceÕs bridging ports.

At the Filtering Database window (Figure 4-11, page 4-45), you can view the number of entries of each type: Permanent, Static, Dynamic, or Learned.

Even though new entries into the Filtering Database are added as Static entries by default, note that some devices, including the FN100, do not support Static entries. For these devices, once you add an entry into the Filtering Database, it must be changed to a Permanent type before clicking on OK to apply the change. If the entry is not changed to a Permanent type before clicking on OK, you will receive a Set Failed message.

Filtering Database 4-43

Bridging

A scrollable Address Entry panel allows you to:

¥ View the address entries in the Filtering Database.

¥ Alter an entryÕs type (e.g., from Learned to Permanent, Dynamic, or Static).

¥ View and conÞgure the bridging action taking place on the packets entering

each of the bridging ports.

In addition, you can use buttons to add individual addresses to, or delete them from, these databases, or clear all Permanent, Static, or Dynamic entries in the database.

To access the Filtering Database window

from the Bridge Status window:

1. Click on to display the Bridge menu.

2. Drag down to select Filtering Database…. The Filtering Database window,

Figure 4-11, will appear.

from the Chassis View window:

1. Click on the Board Index of the device of interest; the Board menu will appear.

2. Drag down to Filtering Database…. The Filtering Database window,

Figure 4-11, will appear.

4-44 Filtering Database

Bridging

Figure 4-11. The Filtering Database Window

Filtering Database Window Fields

The following Þelds are listed in the top portion of the Filtering Database window.

List

The List checkboxes indicate whether the associated entry type (Permanent, Static, Dynamic, or Learned) will be displayed in the scrollable table of address entries. A check next to the entry type indicates that it will be displayed.

Type

Indicates the type of entry in the database.

Number

Displays the current number of Permanent, Static, Dynamic, and Learned Address entries.

Capacity

Indicates the total capacity of each entry type in the Static and Learned databases.

Filtering Database 4-45

Bridging

Aging Time

Indicates the length of time, in seconds, that Dynamic and Learned Addresses in the Source Address Table are allowed to remain inactive before they are dropped from the database. The allowable time range for these entries is 10 to 1,000,000 seconds. Aging time is not applicable to Static or Permanent entries. You can conÞgure this Þeld, as described in the next section.

The following Þelds are applicable to the scrollable Address Entry panel of Filtering Database entries.

Address

Lists the addresses for which the bridgeÕs Filtering Database has forwarding and/or Þltering information.

Type

Indicates the type of an entry in the database. The possible types are Static, Dynamic, Learned, Self, or Permanent. You can alter the entry type, as described in the next section.

Source Port

Indicates the port number on which the address entry was Þrst detected. A question mark (?) indicates that the address entry was not a learned entry, but Port Filtering information applies to it (i.e., the entry is a created Permanent, Dynamic, or Static entry and has corresponding Þltering information).

Receive Port

Indicates the number of the port on which a frame must be received in order for the entryÕs Port Filtering information to apply. An asterisk (*) indicates that the receive port is promiscuous, and applies to all ports of the bridge (assuming no conßicting entry applies). You can change the receive port, as described in the following section.

Port Filtering

Indicates the action that will take place at each bridge port when it receives frames from the selected address entry. A green arrow indicates that the frames received from the address will be forwarded to the portÕs associated segment ( ). A red circle indicates that frames will be Þltered (blocked) from the portÕs associated segment ( ). You can change the Port Filtering action, as described in the next section. (Note that port Þltering is scrollable among all the potential ports; however, only two consecutive ports can be viewed simultaneously.)

Conﬁguring the Filtering Database

You can conÞgure the Filtering Database by:

¥ Altering the Aging Time for Dynamic and Learned entries.

¥ Changing the type of entry with the Type buttons.

4-46 Filtering Database

NOTE

Bridging

¥ Changing the Receive port for the Þlter.

¥ Changing the Port Filtering action at each bridge port.

¥ Adding or deleting individual Filtering Database entries.

¥ Clearing all Permanent, Static, or Dynamic entries from the Filtering Database.

Note that although conÞguration changes will appear in the window, no action actually takes place in the bridgeÕs Filtering Database until you click on the OK button in the bottom right of the window. This saves the new conÞguration.

When you reconÞgure the Filtering Database and click OK, the screen will clear temporarily and a message will appear to indicate that the information is being updated. When the changes have been successfully set and the Filtering Database has updated, the screen information will be refreshed.

If you change the window without clicking on OK, then attempt to exit the window by clicking on Cancel, a text box will appear stating ÒChanges have been made. Cancel them?Ó. Click on Yes to exit the window without changing the Filtering Database, or select No to return to the window.

Altering the Aging Time

To alter the Aging Time for Dynamic and Learned entries:

1. Highlight the Aging Time ﬁeld with the cursor.

2. Type in the new Aging Time (allowable range is 10 to 1,000,000 seconds).

Note that the Filtering Database Aging Time is the same as the Aging Time displayed

NOTE

(and conÞgured) via the Port X Source Addresses window. Setting the Aging Time in the Filtering Database window also changes the time in the Source Addresses window, and vice versa.

Changing the Type of Entry

You can change any entry type from its current type (Learned, Self, Permanent, Static, or Dynamic) to either a Permanent, Static, or Dynamic entry. To do so:

1. Click on the shadowed Type button. A menu will appear with the three types

to which the entry can be changed.

2. Highlight the desired type.

Filtering Database 4-47

Bridging

Changing the Receive Port

You can change the Receive port of an address entry in the scrollable panel, so that a frame must be received at the speciÞed port for the Þltering action to apply. To do so, click on the Receive port in the panel. With each click, the Receive port will cycle to the next port (e.g., from * (promiscuous), to 1, to 2, to 3, to 4, to 5, up to 32, back to *).

Changing the Port Filtering Action

You can change the Port Filtering action at each bridge port from its current action to the opposing action.

1. Maneuver the scroll bar until the desired port is in the Port Filtering panel.

2. Click on the port to alter its ﬁltering action from forwarding frames from the associated address (), to ﬁltering frames ( ) (or vice versa).

Adding or Deleting Individual Entries

You can add or delete entries individually from the Filtering Database.

To add an address:

1. Click on the New button in the lower left of the window. A window (Figure 4-12) will appear.

Figure 4-12. Filter DatabaseÑNew Filter Window

2. In the Filter Address ﬁeld, type in the address (Hex format) for which you desire bridging. Be sure to add “-” as a separator between each byte in the address.

3. In the Receive Port ﬁeld, type in the port at which the address must be detected for bridging to take place. If you enter a value of 0 in this ﬁeld, the

Receive Port is considered promiscuous (i.e., any port), and will be

designated by an “

in the Address Entry panel.

*”

4. Click on .

5. Specify the Port Filtering action on the address entry as described in the previous section.

4-48 Filtering Database

Bridging

To delete an address:

1. Click to highlight the address entry in the Address Entry panel that you wish to

delete from the ﬁltering database.

2. Click on .

Clearing All Permanent, Static, or Dynamic Entries

To erase all Permanent, Static, or Dynamic entries from the Filtering Database, click on the associated button in the upper portion of the window.

Ethernet and Token Ring Special Filter Databases

While the Filtering Database deÞnes Þlters for all packets from a particular source address, the Ethernet Special Filter Database and the Token Ring Special Filtering Databases allow you to Þlter packets through an Ethernet or a Token Ring bridge, respectively, using a special Þltering scheme.

When a packet is received at an Ethernet bridging interface, it is Þrst checked against the Ethernet Special Filter Database to see if any Þltering action applies to it. Because of this, an entry in the Ethernet Special Filter Database takes precedence over a Þlter entry in the Filtering Database that would otherwise apply to the packet.

The Ethernet Special Filter Database allows you to:

¥ DeÞne and save a Þlter based on a combination of Source Address, Destination

Address, Ethernet Data Type and Data (including the offset).

¥ Specify the receive ports at which the Þlter will take effect.

¥ Specify the forwarding/Þltering action at each bridging port of the device.

When checking for Transparent Þltering information, the bridge Þrst checks the Token Ring Special Filter Database to see if any Þltering action applies to it. Because of this, a Þlter entry in the Token Ring Special Filter Database takes precedence over a Þlter entry in the Filtering Database that would otherwise apply to the packet.

Looking at each enabled Þlter, starting with the lowest numbered Þlter, the bridge compares the following Þelds to the corresponding Þelds in the received packet:

¥ Destination address ¥ Source address ¥ Ethernet or Token Ring data type ¥ Up to 16 hex integers (64 bytes) of the data Þeld

In addition, a Þlter can also specify at which port or ports the packet must be received for the Þlter to be applicable. If a received packet matches all the contents of an enabled Þlter, the bridge forwards the packet to the deÞned set of ports.

Ethernet and Token Ring Special Filter Databases 4-49

Bridging

Filters provide broad conÞguration ßexibility. For example, you can deÞne multiple scenarios for a single Þlter by specifying different combinations of receive port/destination port. You can use wildcard characters in Þlter Þelds to force a match with particular bits of the received packetÕs destination address, source address, type, or data. You can specify an offset for the data Þeld, to specify the starting point in the data where the bridge looks for the match. For entries that donÕt match any of the enabled Þlters, you can conÞgure the bridge to Þlter or forward the entry or pass the Þlter/forward decision to the Filtering Database.

Ethernet Special Filter Database Window

At the Ethernet Special Filter Database window, Figure 4-13, you can view a list of the special Þlters for the selected bridge. There are 19 available Þlters in the Special Filter Database. You can not add any additional Þlters. You can view Þve of these Þlters at a time in the Special Filter Database window. Use the scroll bars to view the other fourteen Þlters.

When you Þrst open the window, all Þlters will be undeÞned. (See Figure 4-13, on the following page; Þlters 2 through 5 are undeÞned.) For each Þeld, bytes will be initialized with Òmatch-anyÓ characters (xx) for each digit. Any hexadecimal byte will be accepted as valid for the corresponding wildcard (xx) characters. For example, a Source Address Þlter deÞned as Òxx-xx-xx-xx-bf-coÓ will pass the Þrst four bytes of a frameÕs source address unconditionally, but the last two bytes must match the Òbf-coÓ Þlter.

To access the Ethernet Special Filter Database window

from the Bridge Status window:

1. Click on to display the Bridge menu.

2. Drag down to select Ethernet Special Filter Database…. The Ethernet Special Filter Database window, Figure 4-13, will appear.

from the Chassis View window:

1. Click on the Board Index of the device of interest; the Board menu will appear.

2. Drag down to select Ethernet Special Filter Database…. The Ethernet Special Filter Database window, Figure 4-13, will appear.

4-50 Ethernet and Token Ring Special Filter Databases

Figure 4-13. Ethernet Special Filter Database Window

Bridging

Token Ring Special Filter Database Window

At the Token Ring Special Filter Database window, Figure 4-14, you can view a list of the special Þlters for the selected bridge. There are 19 available Þlters in the Token Ring Special Filter Database. You can not add any additional Þlters. You can view Þve of these Þlters at a time in the Token Ring Special Filter Database window. Use the scroll bars to view the other fourteen Þlters.

When you Þrst open the window, all Þlters will be undeÞned. For each Þeld, bytes will be initialized with match any characters (xx) for each digit. Any hexadecimal byte will be accepted as valid for the corresponding wildcard (xx) characters. For example, a Source Address Þlter deÞned as Òxx-xx-xx-xx-bf-coÓ will pass the Þrst four bytes of a frameÕs source address unconditionally, but the last two bytes must match the Òbf-coÓ Þlter.

To access the Token Ring Special Filter Database window

from the Bridge Status window:

1. Click on to display the Bridge menu.

2. Drag down to select Token Ring Special Filter Database…. The T ok en Ring

Special Filter Database window, Figure 4-14, will appear.

Ethernet and Token Ring Special Filter Databases 4-51

Bridging

from the Chassis View window:

1. Click on the Board Index of the device of interest; the Board menu will appear.

2. Drag down to select Token Ring Special Filter Database…. The T ok en Ring Special Filter Database window, Figure 4-14, will appear.

Figure 4-14. Token Ring Special Filter Database Window

Special Filter Database Window Fields

File

An X in this checkbox indicates that the Þlter is associated with the Þle name shown in the title bar of the window. If a Þle has not yet been saved, the title bar will not display any Þlter name. A saved Þle name is only displayed in the title bar after you have opened a saved Þlter Þle or saved your current Þlters.

Enable

A Þlled-in circle indicates the Þlter is enabled.

Destination Address

Displays a six-byte hexadecimal Þeld for the Þlter which can be used to mask out Destination Addresses.

Source Address

Displays a six-byte hexadecimal Þeld for the Þlter which can be used to mask out Source Addresses.

4-52 Ethernet and Token Ring Special Filter Databases

Bridging

Data Type

Displays the hexadecimal two-byte Þeld for the Þlter which can be used to mask out a speciÞed protocol type Þeld. Examples of protocol type are:

¥ 0800 = IP ¥ 8137 = Novell ¥ 0bad = Banyan ¥ 80f3 = AppletalkARP

Data Offset

Indicates the offset (in bytes, from the beginning of the data in the packet) where the Data Mask will be applied. The default for this Þeld is 0000 (no data offset). An example of a valid offset to enter into this Þeld is 0016 (16 bytes).

Data Mask

Displays the 64-byte overlay used to Þlter packets. The Data Mask is applied to the packet after the Þxed part of the packet, which includes Source Address, Destination Address, and Type Þelds. The Þlter applies the mask directly at the start of the data portion of the packet unless there is a Data Offset. If a Data Offset has been deÞned, the mask will apply to the data that comes after the speciÞed offset in the packet.

Receive Port(s)

Indicates the ports at which the packet must be received for Þltering information to be applied. Note that you can only immediately see one receive port per Þlter, even though you can set more than one receive port for the Þltering action to apply. The receive port Þeld can display each device bridge port, BRIM port, or Ò*Ó. The Ò*Ó indicates that a packet can be received at any port for the Þlter to apply (i.e., the port is promiscuous).

Port Filtering

forwarding Indicates the forwarding/blocking information for the

Þlter at each port on the device. Note that you can only view two ports at a time.

blocking Use the scroll bar at the top of the column to view the

hidden ports.

Selected Filter

This Þeld, visible at the bottom of the window, displays the number of the Þlter that is currently highlighted. The possible range is from 01-19.

Deﬁning and Editing Filters in the Special Database

You can edit an existing Þlter or deÞne a new Þlter using the following steps:

1. Click to select the ﬁlter you wish to edit. (The ﬁlter is selected when it is

highlighted. When the bridge uses the Special Database, it starts with the lowest numbered enabled ﬁlter.)

Ethernet and Token Ring Special Filter Databases 4-53

Bridging

2. Click . The Special Database Filter window, Figure 4-15, will appear with the following ﬁelds:

• Destination Address (six-byte hexadecimal ﬁeld)

• Source Address (six-byte hexadecimal ﬁeld)

• Type (two-byte hexadecimal ﬁeld)

• Data Offset (decimal ﬁeld)

• Data Mask (64-byte hexadecimal data mask)

NOTE

Figure 4-15. The Special Database Filter Window

3. If you are editing an existing ﬁlter, the ﬁelds will reﬂect the current conﬁguration. A ﬁlter that has not yet been deﬁned will ha ve wildcards in e v ery ﬁeld.

If you want to completely reconﬁgure an existing ﬁlter, click on . This will revert all the ﬁelds to all xx’s.

4. Highlight the ﬁeld which you want to deﬁne, and enter the appropriate information.

5. When you have ﬁnished deﬁning the ﬁlter, click on . This will save the ﬁlter you created and return you to the Special Filter Database window , where the conﬁgured ﬁlter will be displayed.

If you do not wish to save what you have entered in the Special Database Filter Window, click on the Cancel button. This will cancel what you have entered into this window and return you to the Ethernet Special Filter Database window.

4-54 Ethernet and Token Ring Special Filter Databases

Cabletron Systems CSX400, CSX200 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Title Page

Notice

Contents

Introduction

HSIM-W6 and HSIM-W84

Using the CSX 200 and CSX400 User’s Guide

Related Manuals

Software Conventions

Common Window Fields

Using the Mouse

Using Window Buttons

Getting Help

Using On-line Help

CSX200 and CSX400 Firmware

CSX200 and 400 Chassis View

Viewing Chassis Information

Front Panel Information

Menu Structure

The CSX200/400 Port Status Displays

Selecting a Port Status View

Port Status Color Codes

The Chassis Manager Window

Viewing Hardware Types

Device T ype

Viewing the Port Description

Managing the Device

Using the Find Source Address Feature

Viewing I/F Summary Information

Interface Performance Statistics/Bar Graphs

Viewing Interface Detail

Making Sense of Detail Statistics

Enabling and Disabling Ports

About the CSX200 Series

About the CSX400

WAN Redundancy

CSX WPIMs

WAN Logical View

W AN Logical View Window Fields

Changing WAN Logical Settings

Bridging

Bridging Basics

About T ransparent Bridging

About Source Route Bridging

About Source Route-Transparent Bridges

About Source Route-Translational Bridges

Viewing and Managing Bridging Interfaces

The Bridge Status Window

Bridge Status Window Information Fields

Accessing Other Options from the Bridge Status Window

Enabling and Disabling Bridging

Enabling and Disabling Individual Interfaces

Enabling and Disabling All Installed Interfaces

Bridge Statistics

Performance Graphs

Bridge Performance Graph Window Fields

The Bridge Detail Breakdown Window

The Bridge Port Detail Breakdown Window

The Interface Statistics Window

Statistics Window Fields

The CSMACD Statistics Window

Receive Errors

Transmission Errors

Collision Errors

The PPP Link Statistics Window

Errors

Statistics

The Dot5 Errors Statistics Window

Source Route Statistics

Bridge Source Routing Window Fields

Received Frames

Transmitted Frames

Discards

Bridge Spanning Tree

Bridge Level Fields

Bridge Port Level Fields

Changing Bridge Spanning Tree Parameters