Cabletron Systems CSX400 User Manual

Download

Title Page

Portable Management Application

for the

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 anti-virus 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: 9032626-E1 April 1998

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

SPECTRUM , MiniMMAC , FNB , Multi Media Access Center , and DNI are registered trademarks,

and Portable Management Application , IRM , IRM2 , IRM3 , IRBM , ESXMIM , ETSMIM , EMME ,

EMM-E6 , ETWMIM , FDMMIM , FDCMIM , MicroMMAC , MRXI , MRXI-24 , NB20E , NB25E , NB30 , NB35E , NBR , SEHI , STHI , TRBMIM , TRMM , TRMM-2 , TRMM-4 , TRMMIM , TRXI , Media Interface Module , MIM , and Flexible Network Bus are trademarks of Cabletron Systems, Inc.

UNIX and OPENLOOK are trademarks of Unix System Laboratories, Inc. OSF/Motif and Motif are

trademarks of the Open Software Foundation, Inc. X Window System is a trademark of X Consortium, Inc. Ethernet and XNS are trademarks of Xerox Corporation. Apple and AppleTalk are registered trademarks of Apple Computer, Inc. Banyan is a registered trademark of Banyan Systems, Inc.

DECnet is a registered trademark of Digital Equipment Corporation. Novell is a registered trademark

of Novell, Inc. CompuServe is a registered trademark of CompuServe. Sun Microsystems is a registered trademark, and Sun , SunNet , and OpenWindows are trademarks of Sun Microsystems, 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.

Chapter 1 Introduction to SPMA

for the CSX200 and CSX400

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

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

WhatÕs NOT in the CSX UserÕs Guide . . ........................................................... 1-3

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

Screen Displays ......................................................................................................1-4

Using the Mouse ....................................................................................................1-6

Getting Help .................................................................................................................. 1-6

CSX200 and CSX400 Firmware ................................................................................... 1-7

Year 2000 Compliance ........................................................................................... 1-7

Chapter 2 Device Conﬁguration

About the CSX200 Series.............................................................................................. 2-1

Applications............................................................................................................ 2-2

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

Applications............................................................................................................ 2-3

WAN Redundancy................................................................................................. 2-4

CSX WPIMs.................................................................................................................... 2-4

Chapter 3 CSX Bridge View

Bridging Basics .............................................................................................................. 3-1

About Transparent Bridging ................................................................................ 3-2

Accessing the Bridge TrafÞc View Window .............................................................. 3-2

Navigating Through the Bridge TrafÞc View ....................................................3-3

Bridge TrafÞc View Front Panel........................................................................... 3-5

The Bridge Port Display........................................................................................ 3-7

Choosing Bridge TrafÞc Information: Bridge TrafÞc View Buttons................3-7

Using the Detail View Window .................................................................................. 3-9

Changing Ports in the Detail View.................................................................... 3-11

The Bridge Status Window........................................................................................3-12

The Bridge Statistics Window ................................................................................... 3-13

The Special Database Window.................................................................................. 3-15

Changing a Special Database Filter...................................................................3-18

Viewing the Filter List.........................................................................................3-19

Hex Values for Destination Ports ............................................................... 3-19

Deleting Special Database Filters ............................................................... 3-20

iii

Contents

The Filtering Database Window ...............................................................................3-20

Viewing the Filtering Database.......................................................................... 3-21

Changing the Filtering Database Dynamic Aging Time ................................ 3-25

Changing Forwarding and Static Database Entries........................................3-26

Deleting a Static Table Entry .......................................................................3-27

Finding a Filtering Database MAC Address.................................................... 3-27

The Spanning Tree Protocol Window....................................................................... 3-28

Changing Spanning Tree Parameters................................................................3-32

The Spanning Tree Port Parameters Window.........................................................3-32

Changing a PortÕs STA Parameters....................................................................3-34

Creating Bridge TrafÞc Charts, Graphs and Meters...............................................3-34

The Bridge Port Forwarding Statistics Window ..................................................... 3-35

Port Forwarding Statistics Window Fields....................................................... 3-36

Viewing Source Routing Frame Type Statistics ...............................................3-37

ConÞguring Forwarding Thresholds ....................................................................... 3-38

Viewing the Forwarding Log.....................................................................................3-41

Changing Polling Intervals ........................................................................................ 3-43

Enabling and Disabling Ports....................................................................................3-44

Enabling and Disabling a Transparent Bridge Port ........................................ 3-44

Chapter 4 CSX WAN Conﬁguration

Accessing the CSX WAN ConÞguration Window.................................................... 4-1

Synchronous Port ConÞguration ................................................................................ 4-5

ConÞguring the Synchronous Port...................................................................... 4-6

T1 Port ConÞguration...................................................................................................4-6

ConÞguring the T1 Port ........................................................................................4-8

Using the Fractional Table .................................................................................... 4-8

WPIM S/T ConÞguration ............................................................................................4-9

Interface ConÞguration Window................................................................................4-9

ConÞguring the WAN Interfaces ....................................................................... 4-11

ConÞguring the PPP Protocol....................................................................................4-12

PPP Link Control Protocol Status Fields...........................................................4-13

Link Control Protocol ConÞguration Fields.....................................................4-14

ConÞguring Link Control Protocol Options.............................................4-16

Viewing the PPP Bridge Network Control Protocol.......................................4-17

ConÞguring the Frame Relay Protocol.....................................................................4-18

ConÞguring the Frame Relay Protocol .............................................................4-20

Viewing the Circuit ConÞguration .................................................................... 4-22

ConÞguring the Circuits .............................................................................. 4-24

Adding Circuits....................................................................................................4-24

Checking Statistics ......................................................................................................4-25

PPP Link Control Protocol Errors......................................................................4-25

Frame Relay DLCMI Last Error.........................................................................4-27

Frame Relay Circuit Counters............................................................................4-28

Creating Meters............................................................................................. 4-29

Synchronous Port Errors.....................................................................................4-30

Synchronous Port Signals ................................................................................... 4-31

Chapter 1

Introduction to SPMA for the CSX200 and CSX400

How to use the CSX200 and CSX400 User’s Guide; manual conventions; contacting the Cabletron Systems Global Call Center; ﬁrmware versions supported by SPMA

Your SPMA for the CSX200 and CSX400 management modules 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 SPMA include T1 and synchronous. In the future E1, DDS, DI (Drop-andInsert), and HDSL will also be supported by SPMA. All of these WPIM options are discussed in Chapter 2, Device 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 SPMA can only manage a T1 or synchronous connection, but in the future WPIM options for SPMA will also include DDS, DI, E1, and HDSL connectivity. Each WPIM can act independently, allowing 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.

1-1

Introduction to SPMA for the CSX200 and CSX400

The CSX400 can support an ISDN connection with the WPIM-S/T. However, this

NOTES

connection is designed for WAN redundancy only. A primary ISDN WAN connection is not an option on the CSX400 at this time.

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/400 devices. QuickSET can also be used to conÞgure WPIM settings and routing-bridging protocols, including those WPIMs not currenlty supported by SPMA. 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 similar to the CSX200/400 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 SPMA as CSX-400s. Therefore, users of the HSIM-W6 and HSIM-W84 can also use this manual.

HSIM-W6 supports IP and IPX bridging or routing services, including IP RIP.

The 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 CSX200 and CSX400 User’s Guide

Your SPECTRUM Portable Management Application (SPMA) for the CSX200 and CSX400 consists of a number of different applications, each of which provides a portion of the overall management functionality. Each of these applications can be accessed from the icon menu (if you are using a management platform) and from the Stand-alone Launcher or the command line (if you are running in stand-alone mode).

This UserÕs Guide describes how to use the bridging and WAN conÞguration applications included with the module; note that the instructions provided in this guide apply to the CSX200 and CSX400 module regardless of the operating system or management platform you are using. Instructions for launching each individual function from the command line (stand-alone mode) are also included in each chapter. At times this manual may refer to the ÒCSX,Ó in which case the information pertains to both the CSX200 and CSX400.

1-2 HSIM-W6 and HSIM-W84

Introduction to SPMA for the CSX200 and CSX400

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, Device ConÞguration , describes the physical conÞguration of the

CSX 200/400 devices, including WPIM options and SPMA application

options.

¥ Chapter 3, Bridge View , discusses the Bridge TrafÞc and Bridge Detail views,

instructs you on conÞguring bridge parameters, and discusses the Bridge

Filtering and Special Databases.

¥ Chapter 4,

WAN interfaces, and how to conÞgure the Frame Relay or PPP protocol

supported on each WAN interface. You can access the CSX WAN

ConÞguration window from the icon menu or the command line.

CSX WAN ConÞguration , explains how to conÞgure the WPIMs as

What’s NOT in the CSX User’s Guide . . .

The following standard SPMA tools are available through the CSX200/400 module and are explained in the SPECTRUM Portable Management Application

Tools Guide :

¥ Charts, Graphs, and Meters

¥ Community Names

¥ MIB I, II

¥ MIBTree

¥ Telnet

¥ TFTP Download

¥ Trap Table

¥ Utilities (Global Community Names, Find MAC Address, and TFTP)

Charts, Graphs, and Meters are accessible from the command line; the Utilities and MIBTree applications are accessible from the platform console window Tools menu or the Stand-alone Launcher applications menu, and MIBTree can also be launched from the command line; and the rest of the tool applications are available from the icon menu or the command line.

For the CSX400, an additional application may also appear on the platform console window Tools menu or the Stand-alone Launcher applications menu:

¥ RMON ConÞguration

Using the CSX200 and CSX400 User’s Guide 1-3

Introduction to SPMA for the CSX200 and CSX400

Note that this application must be purchased separately, and is documented in its own UserÕs Guide .

If you are using SPMA in a stand-alone mode or in conjunction with the SunNet

NOTE

Manager or Solstice Enterprise Manager platforms, the RMON option will be available for all CSX400 devices whether or not you have purchased the RMON application module. If you are using SPMA in conjunction with HP Network Node Manager or IBM NetView AIX, however, the RMON option will only appear when the module has been purchased and installed. RMON is not supported on the CSX200 series.

Instructions on discovering Cabletron devices, creating icons, and accessing the icon menus within your management platform are included in your Installing

and Using SPECTRUM for... guide. If you are using SPMA for the CSX in

stand-alone mode Ñ that is, without beneÞt of a speciÞc network management system Ñ instructions for starting each application from the command line are included (as appropriate) in each chapter of this guide and the SPMA Tools

Guide .

Conventions

SPECTRUM Portable Management Applications Ñ including the CSX200 and CSX400 module Ñ can work with a number of different network management systems running on several different operating systems and graphical user interfaces. This versatility presents two documentation problems: Þrst, there is no standard terminology; and second, the appearance of the windows will differ based on the graphical interface in use. For the sake of consistency, the following conventions will be followed throughout this and other SPMA guides.

Screen Displays

SPMA runs under a variety of different operating systems and graphical user interfaces. To maintain a consistent presentation, screen displays in this and other SPMA guides show an OSF/Motif environment. If youÕre used to a different GUI, donÕt worry; the differences are minor. Buttons, boxes, borders, and menus displayed on your screen may look a bit different from what you see in the guide, but theyÕre organized and labelled the same, located in the same places, and perform the same functions in all screen environments.

Some windows within SPMA applications can be re-sized; those windows will display the standard window resizing handles employed by your windowing system. Re-sizing a window doesnÕt re-size the information in the window; it just changes the amount of information that can be displayed (see Figure 1-1). When you shrink a window, scroll bars will appear as necessary so that you can scroll to view all the information that is available.

1-4 Conventions

Introduction to SPMA for the CSX200 and CSX400

Use the scroll bars provided to choose what to display in a window that’s been resized

Click the Refresh button to re-poll the device for information contained in a window

Figure 1-1. Window Conventions

The Refresh button that appears in several windows allows you to poll the device to update information appearing in those windows.

Conventions 1-5

Introduction to SPMA for the CSX200 and CSX400

Using the Mouse

The UNIX mouse has three buttons. Procedures within the SPMA document set refer to these buttons as follows:

Button 1

Button 2

Button 3

If youÕre using a two-button mouse, donÕt worry. SPMA doesnÕt make use of mouse button 2. Just click the left button for button 1 and the right mouse button when instructed to use mouse button 3.

Whenever possible, we will instruct you on which mouse button to employ; however, menu buttons within SPMA applications will operate according to the convention employed by the active windowing system. By convention, menu buttons under the Motif windowing environment are activated by clicking the left mouse button (referred to as mouse button 1 in SPMA documentation), and there is no response to clicking the right button (mouse button 3). Under OpenWindows, menu buttons can be activated by clicking the right button, and convention dictates that the left button activates a default menu option; within SPMA, that default option will also display the entire menu. Because of this difference, references to activating a menu button will not include instructions about which mouse button to use. All other panels from which menus can be accessed, and all buttons which do not provide access to menus, will operate according to SPMA convention, as documented.

Getting Help

If you need technical support related to SPMA, 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. Before calling, please have the following information ready:

Figure 1-2. Mouse Buttons

1-6 Getting Help

Introduction to SPMA for the CSX200 and CSX400

¥ The product name and part number.

¥ The version number of the program that you need help with. SPMA is

modular, which means each application will have a speciÞc revision number.

Where applicable, an INFO button provides the version number; you can also

view the version number for any application by typing the command to start

the application followed by a -v .

You can contact Cabletron Systems Global Call Center via any of the following methods:

By phone: Monday through Friday between 8 AM and 8 PM

Eastern Standard Time at (603) 332-9400.

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)

Password

By BBS: (603) 335-3358

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

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

anonymous your email address

CSX200 and CSX400 Firmware

SPMA for the CSX200 has been beta-tested against released Þrmware version

1.02.08 only, and the CSX400 has been beta-tested again released Þrmware version

2.00.11 only. If you have a different version of Þrmware and experience problems running SPMA, contact Cabletron SystemsÕ Global Call Center for upgrade information.

As a general rule, Þrmware versions (and software support) for new products are liable to

TIP

change rapidly; contact Cabletron SystemsÕ Global Call Center for information about the latest customer release of Þrmware and software available.

Year 2000 Compliance

Previous users of SPMA will note a few display changes related to Year 2000 compliance. All SPMA applications now have the ability to display a four-digit year value where this information is available. For example, the Stand-alone

CSX200 and CSX400 Firmware 1-7

Introduction to SPMA for the CSX200 and CSX400

Launcher window Ñ which uses your workstationÕs system time value to display the time and date of the last contact change Ñ will now display these date values with eight digits (05/31/1998) instead of six (05/31/98).

Please keep in mind, however, that SPMAÕs ability to display a four-digit year value in device-speciÞc windows Ñ such as the Device Status window available from the Hub View or the Bridge View Ñ is dependent on the ÞrmwareÕs ability to provide a four-digit value. Not all Þrmware versions support this ability; contact Cabletron SystemsÕ Global Call Center for information speciÞc to your device Þrmware.

1-8 CSX200 and CSX400 Firmware

Chapter 2

Device Conﬁguration

Physical CSX device information; SPMA management applications for the CSX200 series and the CSX400; CSX WPIMs

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 how to access the SPMA utilities available to each CSX200/400 module.

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. QuickSET can also be used to conÞgure WPIM settings and routing/bridging protocols, including those WPIMs not currenlty supported by SPMA. See your QuickSET documentation for more information.

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 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

RS530)

CSX203 Provides a DDS WAN uplink

2-1

Device Conﬁguration

NOTE

NOTES

At the time of this release, SPMA does not support a DDS interface on a CSX device. This applies to both the CSX203 and a WPIM-DDS installed on a CSX-400. In addition, the WPIM-DI, WPIM-E1, and WPIM-HDSL are also not currently supported by SPMA, 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 2-4 for a description of the WPIM modules that are available for your CSX200 both currently and in the future.

The WPIM-DI and the WPIM-HDSL, which are both described later in this chapter, are supported by the CSX200 series, though they cannot be managed via SPMA at this time. While no speciÞc 200 device has been allocated for either of these WPIMs (i.e. 201, 202,

203), CSX200s with these WPIMs are available. Contact the Cabletron Systems Global Call Center for more information.

All CSX200 devices use the same Þrmware and the same sysObjectID (csx-200). Therefore, if you have two or more different CSX200 devices on your network, the only way to tell them apart is from their WAN interfaces.

Applications

You can use the following SPMA applications to manage your CSX200 devices:

Bridge View

The Bridge View application is described in Chapter 3, CSX Bridge View. The Bridge View allows you to conÞgure bridging and Þltering parameters, and to view statistics on your CSX200 bridge.

Router Conﬁguration

The Advanced and Basic Router ConÞguration applications are both detailed in your SPMA Routing Services ConÞguration Guide. Through Basic ConÞguration you can set and view routing parameters on each port. With Advanced ConÞguration you can conÞgure static routes and secondary addresses, monitor and control routing tables, and apply network security measures using access control lists.

WAN Conﬁguration

Chapter 4, CSX WAN ConÞguration, describes this application in detail. With the CSX200Õs WAN ConÞguration window, you can set wide-area protocols and conÞgure those settings, as well as conÞgure the WPIM installed on your device.

2-2 About the CSX200 Series

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 2-4.

Device Conﬁguration

Applications

You can use the following SPMA applications to manage your CSX400 device:

Bridge View

The Bridge View application is described in Chapter 3, CSX Bridge View. The Bridge View allows you to conÞgure bridging and Þltering parameters, and to view statistics on your CSX400 bridge.

Router Conﬁguration

WAN Conﬁguration

RMON Conﬁguration

The RMON application must be purchased separately, and is documented in its own UserÕs Guide.

About the CSX400 2-3

Device Conﬁguration

If you are using SPMA in a stand-alone mode or in conjunction with the SunNet

NOTE

Manager or Solstice Enterprise Manager platforms, the RMON option will be available for your CSX400, whether or not you have purchased the RMON application module. If you are using SPMA in conjunction with HP Network Node Manager or IBM NetView AIX, however, the RMON option will only appear when the module has been purchased and installed.

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 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

The following Cabletron WPIMs provide WAN connectivity for the CSX400, HSIM-W84, and the CSX200 series. Note that currently only the WPIM-SY and

WPIM-T1 can be managed on a CSX with SPMA. For all other WPIMs, conÞguration can be done with the QuickSET application that was shipped with your device. Consult your QuickSET documentation for more details.

Chapter 4, CSX WAN ConÞguration, describes how to conÞgure the T1 and synchronous WPIMs, including Frame Relay and PPP protocol conÞguration. 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

2-4 CSX WPIMs

Device Conﬁguration

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 Multiplexing (TDM) allows for the channelization of up to 31 links of a single physical interface. (CSX201)

WPIM-HDSL This WPIM is designed for campus environments and

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.

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

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.

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

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

CSX WPIMs 2-5

Device Conﬁguration

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 either QuickSET or SPMA. Currently, however, SPMA does not support a DDS interface on a CSX device.

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

2-6 CSX WPIMs

Chapter 3

CSX Bridge View

A brief explanation of bridging methods; a tour of the Bridge Trafﬁc View; using the Detail View; monitoring bridge operation; using the Special Database and the Filtering Database; conﬁguring bridge operating parameters; setting forwarding thresholds, statistics, and notiﬁcation options; setting polling parameters; enabling and disabling bridges

The SPECTRUM Portable Management Application (SPMA) Bridge View for the CSX200/400 presents a series of windows that describe the modulesÕ bridge and bridge ports. The Bridge View is supported by the dot1dBridge MIB. You can monitor bridge activity and performance and manage bridge conÞguration for Transparent bridging through the Bridge TrafÞc View and other related windows.

Bridging Basics

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. This is so that 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 CSX200/400 bridge uses to forward packets, choose a bridge path, and ensure that a sending stationÕs messages take only one bridge path is known as Transparent Bridging.

In many Bridge View windows you may see grayed out options for Source Routing.

NOTE

Source Routing is a different kind of bridging which does not apply to your CSX200/400 bridge.

3-1

CSX Bridge View

About T ransparent Bridging

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.

Accessing the Bridge Trafﬁc View Window

There are two ways to access the CSX Bridge View.

from the icon:

1. Click on the appropriate device icon to display the icon menu.

2. Drag down to Bridge-View and release.

from the command line (stand-alone mode):

1. From the appropriate directory type:

spmarun bridge <IP address> <community name>

3-2 Accessing the Bridge Trafﬁc View Window

NOTES

CSX Bridge View

The spmarun script invoked Þrst in the above command temporarily sets the environment variables SPMA needs to operate; be sure to use this command any time you launch an application from the command line. This script is automatically invoked when you launch an application from the icon menu or from within the Bridge TrafÞcView.

If there is a hostname mapped to your CSXÕs IP address, you can use <hostname> in place of <IP address> to launch the Bridge View. Please note, however, that the hostname is not the same as the device name which can be assigned via Local Management and/or SPMA; you cannot use the device name in place of the IP address.

The community name you use to start the Bridge application must have at least Read access; for full management functionality, you should use a community name that provides Read/Write or Superuser access. For more information on community names, consult the appropriate Installing and Using SPECTRUM for... guide, and/or the Community Names chapter in the SPMA Tools Guide.

The Bridge TrafÞc View is the heart of the Bridge application. The Þrst window to appear when you start the Bridge application, it contains a status display of the deviceÕs bridge ports and contains the buttons and menus that provide access to all bridge monitoring and management functions.

Navigating Through the Bridge Trafﬁc View

Within the Bridge TrafÞc View, you can click mouse buttons in different areas of the window to initiate management tasks. The following diagram shows you how to display the Bridge TrafÞc View Device and Port menus.

Accessing the Bridge Trafﬁc View Window 3-3

CSX Bridge View

Virtual Ports

Each list entry represents a bridge port. Click button 1 on a Bridge Port list entry to select it. Once a port is selected, click button 3 on the Port Menu button to display the Port menu. Click button 1 on a bridge port to select it for display in the Detail View (at least two must be selected to activate the Detail View button).

Figure 3-1. Mousing Around the CSX Bridge TrafÞc View

Depending on the type of WAN connection(s) you have on your CSX200/400, the Bridge

NOTE

TrafÞc View window may display a number of virtual bridge ports, for which only a port index is visible. The Bridge TrafÞc View window displays all of the virtual bridge ports available through your WAN interface(s). The virtual ports are not conÞgurable from this window Ñ nor will there be any visible information beyond port index Ñ unless they are in use.

To display the Device menu:

1. Click on in the Bridge Trafﬁc View front panel.

Click on the Device button to display the Device menu

The Front Panel shows device-level summary information.

3-4 Accessing the Bridge Trafﬁc View Window

To display a Port menu:

1. Click mouse button 1 on a Bridge Port entry to select it.

2. Click mouse button 3 on the Port Menu button.

Bridge Trafﬁc View Front Panel

The right side of the Bridge TrafÞc View displays device summary information:

Contact Status

Contact Status is a color code that shows the status of the connection between SPMA and the device:

¥ Green means a valid connection.

¥ Blue means that SPMA is trying to reach the device but doesnÕt yet know if the

connection will be successful.

¥ Red means that SPMA has lost contact with the device.

CSX Bridge View

NOTE

Uptime

The time that the device has been running without interruption. The counter resets to 0 days 00:00:00 (X days HH:MM:SS) when one of the following occurs:

¥ Power to the device is cycled.

¥ The device is reset manually.

Time and Date

The date and time are taken from the deviceÕs internal 24-hour clock, which you can set in the Bridge Status window; see The Bridge Status Window, page 3-12.

Device Name

This Þeld displays the name youÕve assigned to this device in the Bridge Status window; see The Bridge Status Window, page 3-12.

Device Location

This Þeld displays the location youÕve assigned to this device in the Bridge Status window; see The Bridge Status Window, page 3-12.

If you have assigned a device name or location that contains more than 18 characters, only the Þrst 18 will be displayed in the Bridge TrafÞc View. Check the Device Status window for the complete name and/or location, if necessary.

Accessing the Bridge Trafﬁc View Window 3-5

CSX Bridge View

IP Address

The deviceÕs Internet Protocol address. You cannot change the IP address from SPMA. For multi-interface devices, this will be the IP used to deÞne the device icon (if you are using a management platform) or the IP used to launch the application (if you are running in stand-alone mode).

MAC Address

The deviceÕs factory-set MAC hardware address.

Clicking on the Device button displays the Device menu. The Device menu lets you perform the following (depending on what is supported by your device):

¥ Open the Bridge Status window.

¥ Display a summary of bridge statistics.

¥ Open the Filtering Database window.

¥ Open the Find MAC Address window.

¥ Open the Special Database window.

NOTE

¥ Open the Spanning Tree Protocol window.

¥ Open the Polling Intervals window.

It is possible you may also see a menu selection for SmartTrunk. Please be aware that the SmartTrunking feature is not supported by the CSX200/400.

If you need to call CabletronÕs Global Call Center about a problem with the Bridge View, youÕll need the information provided in the Information window:

Bridge ﬁrmware revision

SPMA Bridge View version

Figure 3-2. Bridge Information Window

3-6 Accessing the Bridge Trafﬁc View Window

Clicking mouse button 1 on the Bridge TrafÞc View Quit button closes all Bridge View windows.

The Bridge Port Display

Each Bridge Port entry in the Bridge TrafÞc View displays information about its corresponding bridge port.

The Bridge Port entry numbers are color-coded, reßecting their current status. Bridge Port entries for disabled bridge ports are colored blue. Enabled bridge ports are colored green, yellow, or red, depending on the range in which the trafÞc volume through that port falls. See ConÞguring Forwarding Thresholds,

page 3-38, for complete instructions on assigning trafÞc ranges and their

corresponding Bridge Port entry colors.

Bridge Port entry Þelds are as follows:

Port #

The index number assigned to the bridge port. On CSX devices, index numbers are also assigned to every available virtual port. Virtual ports are detected on your WAN interface(s).

CSX Bridge View

Type

The bridge portÕs interface type (e.g. ethernet-csmacd, fddi, ppp, token ring, etc.).

MAC

The MAC address of the interface associated with the port.

The remaining information displayed in the Bridge Port entry depends on selections made using the buttons located at the bottom of the Bridge TrafÞc View. See the next section, Choosing Bridge TrafÞc Information: Bridge TrafÞc View

Buttons, for instructions on using these buttons.

Choosing Bridge Trafﬁc Information: Bridge Trafﬁc View Buttons

In addition to the Port Menu button, there are four buttons at the bottom of the Bridge TrafÞc View. These four control the type of information that appears in some of the Bridge Port entry Þelds. (The Port number, Type, and MAC address Þelds are not affected by any of these buttons.)

The Source Routing/Transparent Bridging button isnÕt applicable to CSX200/400

NOTE

devices, as only Transparent Bridging is supported. The Source Routing option will be grayed out.

Accessing the Bridge Trafﬁc View Window 3-7

CSX Bridge View

The Frames/Admin and Delta/Percentage buttons each let you choose one of the two display modes for the Bridge Port entries. The display mode visible on a button is the one not currently selected. Clicking on a button when the button displays the desired mode type chooses that mode type for the Bridge Port entries. For example, the Frames/Admin button will display Frames when the Admin display mode is in effect and Admin when the Frames display mode is in effect.

The Frames/Admin button allows you to change the information displayed in the Bridge Port entries between trafÞc statistics (when Frames is selected) and port state/status (when Admin is selected).

The Frames display mode shows the following Bridge Port information:

¥ Frms InÑDisplays the total number of frames, including BPDU frames,

received at this bridge port from its attached network segment during the last polling interval.

¥ Frms OutÑDisplays the total number of frames, including BPDU frames,

transmitted or forwarded through this port to its attached network segment during the last polling interval.

¥ ForwardedÑDisplays frames forwarded by this bridge port to another bridge

port on the device during the last polling interval. You can change this display using the Delta/Percentage button (described in this section). When Delta is selected, this Þeld displays the total number of frames forwarded by this bridge port to another port on the bridge during the last polling interval. When Percentage is selected, this Þeld displays the percentage of all frames received by the port from its network segment that were forwarded to another port on the bridge during the last polling interval.

When the Admin option is selected, the Bridge Port entries display port Status Ñ whether the port is enabled or disabled Ñ and port State.

Enabled The port is able to participate in bridging and the

Spanning Tree Algorithm.

Disabled The port cannot participate in bridging or Spanning Tree

operations.

Enabling and disabling a port changes its Port Status, not its Port State.

A portÕs State indicates whether or not the port is forwarding packets and participating in the exchange of BPDUs. The Spanning Tree Algorithm determines the state of each port in order to maintain an active topology with no data loops. As a port moves from the blocking to the forwarding state, it will remain in each state for the duration of the Forward Delay in order to prevent data loops while the active topology is changing. Possible port states are as follows:

Disabled The port has been disabled by management; it cannot

receive or forward trafÞc, and is not participating in the exchange of BPDUs.

3-8 Accessing the Bridge Trafﬁc View Window

CSX Bridge View

Blocking This port is not forwarding or receiving trafÞc (and

therefore no physical address information is added to the Filtering Database) nor is it sending or receiving BPDUs. A port will enter the blocking state for two reasons: if it receives information that another bridge is the designated bridge to the network segment to which this port is attached, or immediately after it has been enabled by management.

Listening This state is entered from the blocking state when the

STA determines that this port should participate in frame relay. The port is processing BPDUs, but is not yet forwarding or receiving trafÞc or adding information to the Filtering Database.

Learning The port is processing BPDUs, but is not yet relaying

packets. The port is adding address information to the Filtering Database.

Forwarding A port enters this state from the Learning state. The port

is relaying frames and processing BPDUs. A port in this state can enter the Disabled state by management.

Broken If the port is malfunctioning, this value will display in

the State Þeld.

This two-state button is active when you have bridge statistics displayed in the Bridge Port entries (i.e., when Frames is selected); otherwise, it is grayed. When you click on Delta, the Forward field in the Bridge Port entries displays the total number of frames forwarded by this bridge port to another port on the bridge during the last polling interval. When you click on Percentage, the Forward field in the Bridge Port entries displays the percentage of all frames received by the port from its network segment that were also forwarded to another port on the bridge during the last polling interval.

The Detail View button lets you take a closer look at trafÞc between two, three, or four selected bridge ports. The Detail View button is grayed unless you have at least two bridge ports selected. For complete instructions on how to use the Detail View, see the next section.

Using the Detail View Window

The Detail View provides port-level information on any two, three, or four ports.

To open the Detail View:

Using the Detail View Window 3-9

CSX Bridge View

1. In the Bridge Trafﬁc View, select two, three, or four ports by clicking mouse button 1 on the desired ports; the selected P ort entries will be highlighted. The Detail View button becomes active once you select at least two bridge ports.

2. Click on the Detail View button. The Detail View window appears, with the selected ports displayed as boxes.

Figure 3-3. Detail View Showing Four Ports

Due to Þrmware limitations, you may see a bridge port incorrectly identiÞed as Ò(FNB).Ó

NOTE

This can occur here in the Detail View window or in the Bridge Statistics window (see

page 3-13). In either case the port number is correct, but Ò(FNB)Ó should be disregarded.

3-10 Using the Detail View Window

Each port shows the total frames transmitted and received by the port.

Port summary information includes Port Index (at the top of the Bridge Port box), Port Status, Bridge Port State, and Frames Forwarded. You can display Frames Forwarded as a delta value (the total number of frames forwarded by this bridge port to any other port on the bridge during the last polling interval) or as a percentage value (showing the percentage of all frames received b y the port from its attached network segment during the last polling interval that were forwarded to another port on the bridge) by clicking the Delta/Percentage button at the bottom of the window (see Figure 3-3).

Each corner of the bridge port summarizes activity to another bridge port. You can display Forwarded To as a delta value (the total number of frames forwarded by this bridge port to the specified port on the bridge during the last polling interval) or as a percentage value (showing the percentage of all frames received by the port during the last polling interval that were forwarded to the speciﬁed port on the bridge) by clicking the Delta/Percentage button at the bottom of the window (see Figure 3-3).

CSX Bridge View

Figure 3-4. Port Boxes in the Detail View

The diagram in Figure 3-4 explains the Detail View bridge port information.

Changing Ports in the Detail View

The Detail View can display up to four ports at the same time. If the bridge has more than four ports, you can show other device ports by exchanging an existing port in the Detail View for a port that is not displayed.

To select a new port for the Detail View:

1. In the Detail Vie w, click mouse button 3 on the bridge port you want to replace

with another port. The Change Menu appears.

2. Select the range of bridge ports (e.g., Port 1-10) that includes the desired

port. A menu listing the individual ports included in the selected range (i.e., Port 1, Port 2, Port 3, and so on) will appear. Ports that are currently displayed in the Detail View are grayed in the menu.

Using the Detail View Window 3-11

CSX Bridge View

3. Select the desired Bridge Port index number from the list. The port entry will display information for the newly selected port.

The Bridge Status Window

You can set or change the device time, date, name, or locationÑall of which display in the Bridge TrafÞc View Front PanelÑin the Bridge Status window.

The Contact Þeld is the only Bridge Status window Þeld not displayed in the Bridge TrafÞc View Front Panel. Use the Contact box to record the name and phone number of the person responsible for the device.

To set or change information for any of the Bridge Status window Þelds:

1. Display the Device menu by clicking on the Front Panel button.

2. In the Device menu, drag down to Status and release.

3. In the Status window, highlight a text box, type in the new information; press Enter or Return on the keyboard to set your changes before selecting a new ﬁeld.

Figure 3-5. Bridge Status Window

3-12 The Bridge Status Window

If your device Þrmware can accept four-digit year values, the Date Þeld will allow you to

NOTE

enter the year portion in one-, two-, or four-digit format. If you choose to enter one or two digits for the year, any value greater than or equal to 88 will be presumed to be in the 1900s; a value of 87 or less is presumed to be in the 2000s. No matter which entry format you choose, the year will still be displayed and set as a four-digit value.

If your device Þrmware cannot accept four-digit year values, the Date Þeld will allow you to enter the year portion in one- or two-digit format (with leading zeros supplied automatically for single-digit entries). No presumption is made about the century, and any two-digit year value (from 00 to 99) will be accepted.

Attempts to set the date may result in one of three different error messages. Two of these messages will indicate that the wrong number of digits has been used for the year value, and will indicate the appropriate number of digits to use for the selected device; the third message will indicate that the entered date is invalid because it is not an actual calendar date (such as 02/29 in a non-leap year, any month value greater than 12, or any day value greater than 31).

The Bridge Statistics Window

CSX Bridge View

The Bridge Statistics window displays generic information about all ports associated with the device.

To open the Bridge Statistics window:

1. In the Bridge Trafﬁc View window, click on to display the Device

menu.

2. Drag down to Bridge Statistics and release. The Bridge Statistics window

appears.

Figure 3-6. Bridge Statistics Window

The Bridge Statistics Window 3-13

CSX Bridge View

The Bridge Statistics window displays the following information:

Bridging Type

CSX200/400 devices will always display transparent-only.

Total Ports

Shows the total number of bridge ports available on this device, including virtual ports available on the WAN interface(s).

Port

Displays each portÕs index number.

IfIndex

Interface index; a unique value for each network (interface) to which this port connects. Note that a WAN port will connect to more than one interface simultaneously, such as a T1 connection that occupies one physical port but can be divided into as many as 24 virtual ports.

PortCircuit

When dealing with X.25 virtual circuits, itÕs possible for two Port Indexes to have the same IfIndex. In such a case, Port Circuit contains the value of a MIB object instance unique to the port; otherwise, Port Circuit is equal to 0.0. For example, if Port 1 maps to IfIndex 1 and Port 2 maps to IÞndex 1, then the Port Circuits are 1.1 and 1.2 respectively.

NOTE

DelayExceedDiscard

The number of frames a port has discarded due to an excessive transit time through the bridge.

MtuExceedDiscard

Mtu stands for Òmaximum transfer unit;Ó it is the largest frame size that can be processed by a device. A port discards any received frames that are larger than the Mtu; this Þeld lists how many such frames were discarded.

The information in the Bridge Statistics window is a snapshot of the data. When you open the Bridge Statistics window, the application polls the devices for information. Devices are not polled again until you click mouse button 1 on the Update button, or close, then re-open the Statistics window.

When a device is reset, statistics windows and/or statistics displays in the Bridge View windows may display very large numbers for one polling interval. This is due to the resetting of counters.

3-14 The Bridge Statistics Window

The Special Database Window

Many Cabletron bridges incorporate a special database, which lets you create a customized set of Þlters that the bridge uses in Þlter/forward decisions. You can create, conÞgure, and enable Þlters in the special database. On receipt of a packet, the CSX will Þrst read the packet and check it against special Þlters.

When it receives a packet, the bridge Þrst checks the special database. 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: all, some, or none.

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, 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; see

The Filtering Database Window, page 3-20.

CSX Bridge View

To open the Special Database window:

1. Display the Device menu by clicking on the Front Panel button.

2. In the Device menu, drag down to Special Database and then right to

Ethernet and release (Token Ring will be grayed out).

The Special Database Window 3-15

CSX Bridge View

The information at the top of the window applies to all of the entries in the Special Database. When you make a change with the ﬁlter button, the change takes effect immediately.

Use the slide bar to select the Filter Number you want to view. The rest of the information in the window describes the ﬁlter you select with the slide bar.

Use the ﬁlter parameter ﬁelds to view or edit any ﬁlters based on source or destination address, or type or data ﬁeld information.

Use the Apply button to save an y edits that you make.

Figure 3-7. Special Database Window

The top of the Special Database window lists general information:

Total Filters

The number of Þlters available depends on the device. Each device has a Þxed number of Þlters which you can conÞgure and enable.

The No Match Process button lets you select the bridge action for received packets that do not match any Þlter:

¥ Þlter (the default value) ¥ forward ¥ searchFDB (i.e., use the contents of the Filtering Database as the basis for the

Forwarding or Filtering decision)

The rest of the information in the Special Database window describes a particular Þlter:

3-16 The Special Database Window

CSX Bridge View

Receive Port List Box

The receive ports available on the bridge are listed here. This box allows you to select the port at which a packet must be received in order for the Þlter in question to be applied. Selecting ÒAllÓ will allow the Þlter to be applied to packets at any receive port.

Destination Ports List Box

Use this box to select one or more ports to which any packets matching Þlter parameters will be forwarded.

Filter Number

Each Þlter has a unique identifying number. The rest of the information in the window describes the Þlter identiÞed by the displayed number. When the bridge uses the Special Database to make a forwarding decision, it starts with the lowest numbered enabled Þlter.

Filter State

Each Þlter in the Special Database can be enabled or disabled individually.

Offset

The Offset deÞnes the starting point of a 64 byte window in a received frameÕs data Þeld that is examined for a match to a Þlter entry. Offset Ò0Ó means that the comparison begins at the Þrst bit after the packetÕs header Þeld.

Destination Address

The bridge compares the Destination Address entered in this Þeld to the Destination Address of a received frame. An ÒXÓ in any position serves as a wildcard, forcing a match for that position.

Source Address

The bridge compares the Source Address entered in this Þeld to the Source Address of a received frame. An ÒXÓ in any position serves as a wildcard, forcing a match for that position.

Type

The Type Þeld (also known as the Length Þeld) identiÞes the packet type (Novell, AppleTalk, and so forth). The bridge compares this Type to the Type Þeld of a received frame. An ÒXÓ in any position serves as a wildcard, forcing a match for that position.

Data

The four lines of Data in the Special Database window show the values that the Þlter compares to a 64 bit window of the data Þeld of a received frame, beginning at the Offset. An ÒXÓ in any position serves as a wildcard, forcing a match for that position.

The Special Database Window 3-17

CSX Bridge View

Clicking the All Filters button opens a window that displays the Special Filters IO Table. The bridge uses this table to decide what to do with a frame that matches the information in a Þlter. If the frame information matches the Þlter information, and the frame was received at the port speciÞed in the table, the bridge forwards the frame to the bridge ports listed in the table. See Viewing the Filter List,

page 3-19.

The Apply button in the Filtering Database window lets you save changes to edited Þlter information. See the next section, Changing a Special Database

Filter, for Þlter editing procedures.

Changing a Special Database Filter

To enable, disable, or edit the contents of a Special Database entry:

1. In the Special Database window, use the slide bar to display the Filter Number you want to edit.

NOTE

2. In the Filter State ﬁeld, click in the appropriate check box to Enable or Disable the ﬁlter, as desired.

3. In the Receive Port list box, clic k to select the Port at which a pack et must be received in order for this ﬁlter to be applied. Selecting “All” will allow the ﬁlter to be applied to packets at any received port.

4. In the Destination Port list box, clic k to select one or more ports to which any packets matching ﬁlter parameters will be forwarded.

By using different combinations of Receive Port/Destination Ports, you can deÞne multiple conditions for a single Þlter. For example, you can conÞgure a Þlter so that a packet received at port 1 that matches the Þlter conditions is forwarded to port 2, and a packet received at port 2 that matches the Þlter conditions is forwarded to ports 3 and 4. To deÞne multiple port conditions, just change the Receive and Destination Port values for a deÞned Þlter and then click on the Apply button.

5. In the Offset ﬁeld, enter a value that determines where within the data portion of the packet the 64 byte window used for matching should begin.

6. Highlight and type Source and Destination Addresses. An X in an address position serves as a wildcard, forcing a match to any value in that position in the received packet’s address ﬁeld.

7. Highlight and type a 4-digit Type value in the T ype ﬁeld. The Type identiﬁes the packet type. For example, 8138 identiﬁes a Novell packet. An X in a Type ﬁeld serves as a wildcard, forcing a match to any value in that position in the received packet’s Type ﬁeld.

3-18 The Special Database Window

8. The four Data ﬁelds in the window show the 64 bytes of data the bridge will

compare to the data ﬁeld of an incoming packet. You deﬁne the data you w ant to match in 8-byte strings by placing the cursor in one of the four boxes and typing in the values you want to use. Valid characters are 0-9, A-F, and upper case X (wildcard). After you type 16 characters in the box, click on Apply to save the changes.

9. When you have set all desired parameters for a particular ﬁlter, click on the

Apply button.

Viewing the Filter List

To view a list of all enabled Þlters:

1. Open the Special Database window by selecting the Special Database

option on the Device menu.

2. Click on the All Filters button to open the Special Filters IO Table window.

CSX Bridge View

Figure 3-8. Special Database All Filters Window

Hex Values for Destination Ports

On a bridge with many ports, a Þlter can have more Destination Ports than the Destination Ports column is able to display. When this occurs, Destination Ports for that Þlter appear as a hex string that maps to actual port numbers.

If the Destination Ports list is too long to ﬁt in the column, the port numbers are represented by a hex bitmask.

The Special Database Window 3-19

CSX Bridge View

In Figure 3-8, Filter Number 3 shows the Destination Ports as B54180E0, which represents ports 1, 3, 4, 6, 8, 10, 16, 17, 25, 26, 27. HereÕs how to translate the hex string to port numbers:

1. Translate each hex integer into a four-digit binary value: B54180E 0

1011 0101 0100 0001 1000 0000 1110 0000 Each “1” in the binary bitmask represents a Destination Port number: B54180E 0

1011 0101 0100 0001 1000 0000 1110 0000 1,X,3,4 X,6,X,8 X,10,X,X X,X,X,1617,X,X,X X,X,X,X, 25,26,27,X X,X,X,X

Deleting Special Database Filters

To delete an enabled Special Database Þlter:

1. In the Special Filters IO Table, select a ﬁlter to delete by clicking mouse button 1 on the table entry.

2. Click mouse button 1 on the Delete button at the bottom of the window.

Deleting a Þlter doesnÕt ÒdeleteÓ the Þlter; it just clears all the entries you made for that

NOTE

instance of the Þlter. In the example shown above, if you deleted the last entry in the list (Filter Number 19, Receive Port 4, Destination Port 1) any other entries for Filter 19 would remain intact.

The Filtering Database Window

In Transparent bridging, each bridge port uses the deviceÕs Filtering Database to determine a packetÕs route through the bridge. The Filtering Database is created from permanent entries made via management, and from entries learned as the bridge collects and stores the source address and port association from each packet it receives.

When in the Forwarding state, the bridge examines each received packet and 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 isnÕt 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.

The Filtering Database has two types of entries: Forwarding and Static. The Forwarding view of the Filtering Database contain addresses that the bridge

3-20 The Filtering Database Window

learns from network trafÞc (also known as dynamic entries) as well as all the static entries. Learned entries are subject to the bridgeÕs Dynamic Aging Timer; entries that arenÕt accessed within the time speciÞed by the aging timer are purged. Static entries may be subject to the aging timer, depending on how the entries were added. Static entries enter the Filtering Database in two ways: either automatically, when permanent database entries are copied to the Filtering Database, or manually when you move a Forwarding entry to the Static Table.

Viewing the Filtering Database

To open the Filtering Database window:

1. Display the Device menu by clicking on the Front Panel button.

2. Drag down to Filtering Database, and release.

3. At the top of the Filtering Database window, click mouse button 1 on the

appropriate selection box to view either the Forwarding or Static database.

CSX Bridge View

The Filtering Database Window 3-21

CSX Bridge View

Click mouse button 1 on the type of entry you want to display, either

Forwarding

Static.

Figure 3-9. Filtering Database Window

Two Þelds at the top of the Filtering Database window provide information about the Filtering Database:

Aging Time (secs)

The current setting of the bridgeÕs Dynamic Aging Timer, used to purge Forwarding entries from the Filtering Database, or to purge static entries subject to the aging timer.

Learned Entry Discards

The number of database entries that never made it into the Filtering Database due to a lack of buffer space. Ideally, this number should be 0. If this number grows, it indicates a very busy network. A value other than 0 is acceptable as long as it isnÕt increasing, indicating that the lack of buffer space is sometimes causing problems, but that the condition is not persistent.

3-22 The Filtering Database Window

CSX Bridge View

For each entry in the Forwarding database, the window displays the following:

Source Address

Displays the MAC addresses of devices that have transmitted frames to the bridge.

Port

IdentiÞes the bridge port where frames from the noted source address are received. A value of 0 indicates that the address exists within the Filtering Database, but the database has not yet learned the corresponding port number.

Status

Indicates how the entry got into the database:

¥ learnedÑThe address was copied into the database from the source address

Þeld of a received frame.

¥ selfÑIdentiÞes one of the bridge ports.

¥ managementÑIndicates an entry that was entered into the database manually.

The status Þeld of all static entries in the Forwarding Table will display management.

¥ invalidÑThe entry is a learned entry that has aged out, but has not yet been

ßushed from the table.

¥ otherÑThe bridge is unable to determine the entryÕs status.

The information displayed for the Static database is somewhat different; for each entry, the window displays the following:

Source Address

Displays the MAC addresses of devices that have transmitted frames to the bridge.

Receive Port

Displays the port on which a packet with the speciÞed source address must be received in order for the Þltering actions speciÞed in the Destination Port Þeld to take place. A setting of 0 will apply the Þltering action anytime a packet with the speciÞed source address is received by any of the bridge ports.

Destination Port

Displays the port or ports to which frames that have the speciÞed source address and were received on the speciÞed port or ports will be forwarded. Note that packets with the speciÞed source address received on the speciÞed port or ports will be blocked from any ports not listed in this Þeld.

If the number of Destination Ports exceeds what the Destination Ports column is able to display, Destination Ports for that Þlter appear as a hex string that maps to actual port numbers.

The Filtering Database Window 3-23

CSX Bridge View

For example, a Destination Port entry of B54180E0 represents ports 1, 3, 4, 6, 8, 10, 16, 17, 25, 26, and 27. HereÕs how to translate the hex string to port numbers:

1. Translate each hex integer into a four-digit binary value: B54180E 0

1011 0101 0100 0001 1000 0000 1110 0000

2. Each “1” in the binary bitmask represents a Destination Port number: B54180E 0

1011 0101 0100 0001 1000 0000 1110 0000 1,X,3,4 X,6,X,8 X,10,X,X X,X,X,16 17,X,X,X X,X,X,X 25,26,27,X X,X,X,X

Status

Indicates the assigned permanence of the entry:

¥ permanentÑThe entry wonÕt be aged out or deleted on reset.

¥ deleteOnResetÑThe entry will be deleted when the bridge is reset.

¥ deleteOnTimeoutÑThe entry is subject to the aging timer.

The buttons at the bottom of the window provide the following functions:

The Delete button is only available when the Filtering Database window is showing Static entries and one entry in the list is selected. Use the Delete button to remove an entry from the Static Table; see Deleting a Static Table Entry,

page 3-27.

The Change button is only available when the Filtering Database window is showing Static entries and one entry in the list is selected. Use the Change button to change the selected portÕs receive port/destination ports settings; see Changing Forwarding and Static Database Entries, page 3-26.

Since the Forwarding table cannot be edited, you must add an entry to the Static Table in order to change or delete it, as desired. Use the Add to Static Table button to add a forwarding entry to the static database.

The Aging Time determines how long a Forwarding entry (or a Static entry with deleteOnTimeout status) is retained before being discarded due to inactivity. Use the Change Aging Time button to set a new Aging Time; see the following section for details.

Use the Find button to search the Filtering Database for a speciÞc MAC address; see Finding a Filtering Database MAC Address, page 3-27.

3-24 The Filtering Database Window

The Filtering Database window shows a snapshot of the database. Clicking mouse button 1 on the Update button displays the current database.

Changing the Filtering Database Dynamic Aging Time

The Dynamic Aging Time determines how long an entry remains in the Filtering Database before being purged due to inactivity. Purging older entries ensures that the Filtering Database is always using current information to make Þlter/forward decisions.

During a topology change, the Forward Delay is used as the Filtering Database Aging

NOTE

Time, which ensures that the Filtering Database will contain current topology information.

To change the Dynamic Aging Time:

CSX Bridge View

1. In the Filtering Database window, clic k mouse b utton 1 on the Change Aging

Time button to open the Change Aging Time window.

As you change the aging time, SPMA converts seconds to days:hours:minutes:seconds.

Figure 3-10. Changing the Filtering Database Aging Time

2. Highlight and edit the Aging Time (in seconds), and then click mouse button 1 on the Apply button.

3. Use mouse button 1 to drag the slide bar, then click Apply.

4. Click mouse button 1 ne xt to the slide to increment the time in 100 second jumps, then click Apply.

The Filtering Database Window 3-25

CSX Bridge View

Changing Forwarding and Static Database Entries

The only entries that can be changed or deleted in the Filtering Database are static entries. If the entry you wish to change or delete is a forwarding entry, you must add it to the Static Table. The Static Table (Figure 3-11) is used to change a forwarding entry to a static or permanent entry, or make changes to existing static entries. To open the Static Table window:

1. Open the Filtering Database window by clicking on the Front Panel button; drag down to Filtering Database to display the Filtering Database window.

2. If the Filtering Database window displays Forwarding entries, highlight the entry you want to change and click on the Add to Static Table button.

or If the Filtering Database window displays Static entries, highlight an entry and

click on the Change button.

It is also possible to open the Static Table in either case without highlighting an entry, by

NOTE

clicking on the Add To Static Table button. The static address Þeld will appear blank. Enter the MAC address that you want to add to the Static Table.

Figure 3-11. Static Table Window

Static Address

The Static Address Þeld will display the MAC address of the entry you highlighted in the Filtering Database window. If no entry was selected, the address Þeld will contain zeros, and a valid MAC address may be entered.

3-26 The Filtering Database Window

CSX Bridge View

Receive Port

The Receive Port list box speciÞes the port on which packets from the speciÞed static address must be received in order for the static database entry to apply. If All is selected, the entry will be applied to packets forwarded to any port.

Forward T o Ports

The Forward To Ports list box speciÞes the ports to which packets with the speciÞed source address received on the speciÞed ports will be forwarded. The port or ports selected in this list will be displayed in the Filtering Database window as the Destination Port.

To change an entry:

1. Click mouse button 1 on the port in the Receive Port list box that y ou want to

specify as the receive port for the entry in the Static Address ﬁeld (remember that if All is selected, the entry will be applied to packets received on any port).

2. Click mouse button 1 on any port or ports in the Forward T o Ports list that

you want to be displayed in the Filtering Database window as the destination port.

3. Click mouse button 1 on the Status button and choose one of the following:

permanent—The entry won’t be aged out or deleted on reset. deleteOnReset—The entry will deleted when the bridge is reset. deleteOnTimeout—The entry is subject to the Aging timer.

4. After you set the entry’s status, click mouse button 1 on the Apply button.

Deleting a Static Table Entry

To delete a Static Table entry:

1. In the Filtering Database window, click mouse button 1 in the appropriate

selection box to display the Static database.

2. Select the entry you want to delete by clicking it with mouse button 1.

3. Click on the Delete button.

Finding a Filtering Database MAC Address

To Þnd a source address in the Filtering Database:

1. In the Filtering Database window, click on the button to open the

Find MAC Address window.

The Filtering Database Window 3-27

CSX Bridge View

In the Bridge Trafﬁc View, display the Device menu by clicking on the Front Panel button. Drag down to Find MAC Address.

2. In the edit box, enter a valid MAC address and then press the Return key. If the address is found in the Filtering Database, its port location and status will appear in the list box. If it is not found, a separate window will appear with a “Not Found” message.

Figure 3-12. Find MAC Address Window

The Spanning Tree Protocol Window

Bridges in a network collectively implement a Spanning Tree Algorithm (STA) to detect and eliminate data loops in a network containing parallel bridges.

In a network designed with multiple bridges placed in parallel (i.e., attached to the same network segment), Spanning Tree selects a controlling Root Bridge and Port for the entire bridged local area network, and a Designated Bridge and Port for each individual network segment. The Root bridge is the one that selects one of two or more available bridge paths between two end stations, basing its decision on factors associated with each of the bridges in the path. A Designated Port/Bridge for a network segment relays frames toward the Root Bridge, or from the Root Bridge onto the network segment. When data passes from one end station to another across a bridged local area network, it is forwarded through the Designated Bridge/Port for each network 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). It is with BPDUs that the bridges collectively determine the current network topology and ensure that all bridges have current topology information.

The Spanning Tree Protocol window displays information used by the network bridges to select the Root Bridge and parameters that affect the bridgeÕs participation in Spanning Tree operations.

To open the Spanning Tree Protocol window:

1. Click on the Front Panel button.

2. Drag down to Spanning T ree and release.

3-28 The Spanning Tree Protocol Window

Figure 3-13. Spanning Tree Protocol Window

CSX Bridge View

CAUTION

The Spanning Tree Protocol window displays the following information:

Spanning T ree Version

The version shows the Spanning Tree Protocol type employed by this bridge:

¥ IEEE 802.1d ¥ DEC LAN 100 ¥ None

You must use either 802.1d or DEC to interconnect all bridges in a network using parallel bridges. By default, a Cabletron bridge turns on the 802.1d Spanning Tree. All of CabletronÕs bridge products have the ability to use either the 802.1d or DEC Spanning Tree version, or they can be set so that no version is in effect. (A bridge should be set to None if there are no redundant loops incorporated within the network.)

All bridges in a network must use the same Spanning Tree version. Mixing Spanning Tree Algorithm protocols will cause an unstable network.

Designated Root

This value represents the bridge that is the current Root Bridge as determined by the STA. The Designated Root value consists of the conÞgurable portion of the bridge ID (i.e., the Þrst two octets of the eight-octet-long bridge ID) and your deviceÕs MAC address (the last six octets of the bridge ID). This value is used as

The Spanning Tree Protocol Window 3-29

CSX Bridge View

the Root IdentiÞer parameter in all conÞguration BPDUs originated from this node.

Num. T opology Chgs.

Indicates the number of times the bridgeÕs Topology Change ßag has been changed since the bridge was powered up or initialized. The Topology Change ßag increments each time any of the networkÕs bridges enters or leaves the network or when the Root Bridge ID changes.

The values for the following three ÞeldsÑForward Delay, Max Age, and Hello TimeÑrepresent the values that are currently being used by all bridges, as dictated by the Root bridge. In the Spanning Tree Protocol window, you can view and set the valuesÑRoot Forward Delay, Root Max Age, Root Hello TimeÑthat will be in effect when the bridge for which you are setting the parameters becomes the Root Bridge.

Forward Delay

The length of time, in seconds, that controls how long a bridge port remains in each state (Forwarding, Learning, Listening, etc.) when moving toward the Forwarding state. During a topology change, the Forward Delay is also used as the Filtering Database Aging Time, which ensures that the Filtering Database will contain current topology information. The Root Bridge sets the Forward Delay.

Max Age

The current setting for the bridgeÕs BPDU aging timer, in seconds. The aging timer deÞnes the maximum number of seconds that a ConÞguration BPDU is retained by the bridge before it is discarded. During normal operation, each bridge in the network receives a new ConÞguration BPDU before the aging timer expires. If the timer expires before a new 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 Root Bridge determines the Max Age. The range for this Þeld is from 6 to 40 seconds, with a default value of 20 seconds.

Hello Time

Indicates, in seconds, the length of time the Root Bridge, or bridge attempting to become the Root, waits before resending a ConÞguration BPDU. The Root Bridge determines the Hello Time.

Priority

The Spanning Tree Algorithm assigns each bridge a unique identiÞer, which is derived from the individual portÕs MAC address and its priority as determined by the Spanning Tree Algorithm or your setting. 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.

Acceptable values range from 0-FFFF and can be edited to change the network topology, if needed. The default is 8000.

3-30 The Spanning Tree Protocol Window

CSX Bridge View

Root Port

The port identiÞer (i.e., the physical index number) for the port that provides the lowest cost path to the Root Bridge. The Root Port Þeld displays 0 if this bridging device is 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. This Þeld will read 0 if your device is the Root Bridge. See Changing a PortÕs STA Parameters, page 3-34, to Þnd out how to set a portÕs Path Cost.

Hold Time

The minimum time, in seconds, that can elapse between the transmission of ConÞguration BPDUs. The Hold Time ensures that ConÞguration BPDUs are not transmitted too frequently through any bridge port. Receipt of a ConÞguration BPDU starts the Hold Time count at a device. If the Hold Time expires, the port invokes the Transmit ConÞguration BPDU procedure, which sends conÞguration change information to the Root. The Hold Time is a Þxed value, as speciÞed by the IEEE 802.1d speciÞcation.

NOTE

TIP

The values for the Forward Delay, Max Age, Hold Time, and Hello Time Þelds are stored within the MIB in units of hundredths of a second rather than seconds; your Cabletron management application converts hundredths of a second to seconds for display purposes. You can use any SNMP Set Request tool to edit the values for these three Þelds; just remember that you must enter your values in hundredths of seconds, rather than in seconds.

Root Forward Delay

The Forward Delay (in seconds) that will be implemented by this bridge if it is the Root or becomes the Root. (The Root Bridge in the network sets the Forward Delay for all bridges in the Spanning Tree network.)

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 recommends that you always observe the following relationship between Forward Delay and Max Age:

2 x (Forward Delay - 1.0) > Max Age

Root Max Age

The Max Age value (in seconds) that will be implemented if this bridge is the Root or becomes the Root. (The Root Bridge in the network sets the Max Age for all bridges in the Spanning Tree network.)

The Spanning Tree Protocol Window 3-31

CSX Bridge View

The IEEE 802.1d speciÞcation recommends that Max Age = 20 seconds, with an allowable range of 6 to 40 seconds.

Root Hello Time

The Hello Time that will be implemented if this bridge is the Root or becomes the Root.

The IEEE 802.1d speciÞcation recommends that Hello Time = 2 seconds, with an allowable range of 1 to 10 seconds.

The Spanning Tree Port Table button opens the window in which you set Spanning Tree parameters for individual bridge ports; see The Spanning Tree

Port Parameters Window, page 3-32, for more information.

Changing Spanning Tree Parameters

To change the Bridge Priority, Root Forward Delay, Root Max Age, or Root Hello Time:

1. In the Spanning Tree Protocol window, highlight the current value of the ﬁeld you want to change.

2. Type the new value in the appropriate text box and press Enter or Return on the keyboard.

The Spanning Tree Port Parameters Window

The Spanning Tree Algorithm ensures that only a single bridge path exists between any two end stations in a network designed with multiple bridges placed in parallel; it also ensures that on any given bridge, only one port path exists between the bridge and any one network segment. In the Spanning Tree Port Table you can view and edit the Spanning Tree values for individual ports; the Spanning Tree Port parameters affect a portÕs participation in the Spanning Tree.

Setting Spanning Tree Port Parameters only affects port selection on a particular bridge;

NOTE

settings do not affect your deviceÕs device-level priority in the networkÕs Spanning Tree.

To open the Spanning Tree Port Table window:

1. Display the Device menu by clicking on the Front Panel button.

2. Drag down to Spanning T ree to open the Spanning Tree Protocol window.

3-32 The Spanning Tree Port Parameters Window

CSX Bridge View

3. In the Spanning Tree Protocol window, click on the Spanning Tree Port Table

button.

1. In the Bridge Trafﬁc View, click mouse button 3 on a port to display the Port

menu and drag down to Spanning T ree.

The scroll list at the top of the window lists each bridge port available on the device and its current port priority. Below the Port List, the window includes the following:

Priority (Port)

If two or more ports on the same bridge are connected to the same network segment, each port will receive the same device-level values for Root ID, Root Cost, and Bridge ID in ConÞguration BPDUs. In this case, the BPDUÕs port-level informationÑthe transmitting portÕs identiÞer and its manageable Priority componentÑ is used to determine which port on this bridge will be the Designated Port for that segment. A lower number indicates a higher priority; the default is 80. The allowable range is 0 to FF.

Path Cost

The portion of the total path cost associated with this port. Lowering a portÕs Path Cost makes a port more competitive in the selection of the Designated Port. The default value is 100 for Cabletron bridges. The allowable range is from 1 to 65535.

Figure 3-14. Spanning Tree Port Parameters Window

The Spanning Tree Port Parameters Window 3-33

CSX Bridge View

Designated Cost

The cost of the path from this port to the Root Bridge on the network. If the highlighted port is the Root Port, the Designated Cost is 0. If this bridge is the Root Bridge, all its bridge ports have a Designated Cost of 0. This value is compared to the Root Path Cost Þeld in received conÞguration BPDUs.

Designated Root

The unique Bridge IdentiÞer of the bridge that is assumed to be the Root Bridge on the network; this information is contained in the ConÞguration BPDUs.

Designated Bridge

Displays the MAC address and priority component of the Bridge ID for the bridge that is believed to be the Designated Bridge for the network segment 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 network segment to which it is attached.

Designated Port

The Port ID of the port on the Designated Bridge for this portÕs segment. The Designated Port is the bridge port that offers the lowest path cost to the Root Bridge.

Forward T ransitions

The number of times this port has moved from the Learning state to the Forwarding state since the device was started or since it was last reset.

Changing a Port’s STA Parameters

To change a portÕs Priority or Path Cost:

1. In the scroll list, click mouse button 1 on the port you want to change (use the scroll bar if necessary to display the desired port). You can only select one port at a time. The highlighted port’s Spanning Tree parameters appear in the boxes below the list.

2. Highlight and edit the Priority and Path Cost boxes as required. After you type in the new value in a box, press Enter or Return on the keyboard.

Creating Bridge Trafﬁc Charts, Graphs and Meters

The Bridge application uses the SPMA Charts, Graphs and Meters tools to depict bridge statistics describing activity at the bridge-port level. Once running, however, a pie chart, graph or meter is independent from the application where it was started. Although the windows you open to create pie charts, graphs and meters have unique variable lists, the procedures for creating a pie chart, a graph or a meter are the same.

3-34 Creating Bridge Trafﬁc Charts, Graphs and Meters

CSX Bridge View

To access the Pie Chart, Graph and Meters tools from the Bridge TrafÞc View Port menus:

1. Click mouse button 1 on a Bridge Port entry to select it.

2. Click button 3 on the Port Menu button to display the Bridge Port menu.

3. Drag down to select Pie Chart or Graphs/Meters—>Transparent.

Figure 3-15. Pie Chart Window

For complete descriptions of chart, graph and meter variables and details on how to create and control a pie chart, graph or meter, see the chapter on charts, graphs and meters in the SPMA Tools Guide.

The Bridge Port Forwarding Statistics Window

The procedures for viewing Transparent and Source Routing statistics are nearly identical, although graphically the windows for the two are slightly different. Both show you a breakdown of activity between the selected port and each of the other bridge ports.

To view statistics for a particular bridge port:

1. In the Bridge Trafﬁc View, click mouse button 3 on a bridge port to display the

Port menu.

The Bridge Port Forwarding Statistics Window 3-35

CSX Bridge View

2. Drag down to Forwarding Statistics —>Transparent and release to open the Statistics window.

Indicates the port from which the Statistics window was opened.

The two list boxes show forwarding activity between the selected port and each of the other bridge ports.

Port summary statistics. The Frame Type Breakdown

button is only available for bridges performing Source Routing.

Figure 3-16. Bridge Port Forwarding Statistics Window

Port Forwarding Statistics Window Fields

The Bridge Port Statistics window contains two list boxes detailing port forwarding activity to and from the currently selected port:

¥ The leftmost list box shows frames forwarded to each of the other bridge ports

from the currently selected port.

¥ The rightmost list box shows frames forwarded to the currently selected port

from each of the other bridge ports.

The list box detail Þelds are:

Port

The port number to/from which frames are being forwarded.

Frms Fwd

The total number of frames forwarded to/from the selected port to/from the other bridge ports during the last polling interval.

% of Total

In the Frames forwarded to each Bridge Port list box, this is the percentage of all frames forwarded to the selected port that were then forwarded to other bridge ports during the last polling interval. In the Frames forwarded from each Bridge Port list box, this is the percentage of all frames received by the selected bridge port that were forwarded to that port by other bridge ports.

3-36 The Bridge Port Forwarding Statistics Window

DeÞnitions for the port summary statistics are included in the next section, which deÞnes

NOTE

TIP

the types of frame statistics available via the Frame Type Breakdown button.

The statistics shown in the Bridge Port Statistics window reßect a ÒsnapshotÓ of the statistics from the time the window was opened. To refresh the statistics, you must close this window and open it again.

Viewing Source Routing Frame Type Statistics

A Source Routing bridge uses various broadcast messages to determine the optimum route for a frame, so there are a few more frame statistics to view. When displaying Source Routing rather than Transparent Bridging information, the Statistics window activates the Frame Breakdown button, which lets you view frame type statistics as either absolute values or as slices of a pie chart.

CSX Bridge View

To view Source Routing frame type statistics:

1. In the SR Statistics window, click mouse button 1 on the Frame T ype

Breakdown button.

SR Frame types include the following:

Total Frames Received

The total number of frames, of all types, received at the selected port.

Spec Frames

SpeciÞcally routed frames. These frames have data and routing information and are following a known route from source to destination.

APE Frames

When a sending station needs to determine the best route to an intended destination, it transmits an APE (All Paths Explorer) frame. The APE frame contains no routing information; it is propagated along all available paths to the destination station, which then sends speciÞcally routed frames as replies 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.

STE Frames

Spanning Tree Explorer frames, also known as Single Route Broadcast frames, follow the topology established by the Spanning Tree Algorithm. This speciÞcally routed frame can be used by end stations, instead of the APE frame.

The Bridge Port Forwarding Statistics Window 3-37

CSX Bridge View

Total Frames Transmitted

The total number of frames transmitted by the bridge.

Total Frames Filtered

Total Frames Filtered indicates the total number of frames that were not forwarded through the bridge to another segment.

Segment Mismatch

The routing information Þeld of a SpeciÞcally Routed frame contains LAN Segment In (Local Segment)ÑBridge NumberÑLAN Segment Out (Target Segment) information. If the bridgeÕs LAN Segment Out value does not match the LAN Segment Out speciÞed in the frameÕs Routing Information Þeld, the bridge logs a Segment Mismatch and discards the frame.

Duplicate Segment

A bridge discards a frame if the frameÕs Routing Information Þeld identiÞes a particular segment more than once.

Hop Count Exceeded

An All Paths Explorer frame is discarded when it exceeds the number of routing descriptors (bridge hops) speciÞed by the Hop Count Limit.

The Pie Chart button lets you select a predeÞned set of frame type statistics and display them as a pie chart. When you click on the Pie Chart button, a pop-up menu appears that lets you choose Received, Transmitted, or Filtered statistics. When you make your choice, the SR Pie Chart window opens with the appropriate set of variables already selected.

For complete descriptions of chart variables and details on pie charts, see Chapter 8, SPMA Charts, Graphs, and Meters.

Conﬁguring Forwarding Thresholds

You can deÞne notiÞcation thresholds for bridge port forwarding levels and then have SPMA use those thresholds to do one or more of the following:

¥ Color code the Bridge Port display entries

¥ Send Internet mail to a registered user

¥ Launch a program on your management workstation

To open the Forwarding Thresholds window:

1. Click button 1 on a Bridge Port display entry in the Bridge View to select it.

2. Click button 3 on the Port Menu button to display the Port menu.

3-38 Conﬁguring Forwarding Thresholds

CSX Bridge View

3. In the Port menu, click button 3 on Forwarding Thresholds —>T ransparent

to open the Forwarding Thresholds window.

A trafﬁc level is the speciﬁed value of forwarded frames as a percentage of total received frames.

You can specify trafﬁc levels that deﬁne the boundary between the low and medium ranges and between the medium and high ranges.

When SPMA polls the device and detects that the percentage of forwarded frames has mo ved into a new range, heading either up or down, the notiﬁcation options and conditions in use for that port take place.

Figure 3-17. Port Forwarding Thresholds Window

SPMA polls a bridge at preset intervals, as deÞned in the Polling Intervals window

NOTE

accessed from the Bridge View Device menu. A portÕs trafÞc level can pass from one range to the next and then back to the original level between polls from SPMA. When this occurs, SPMA wonÕt record that the threshold has been passed because the event was never observed.

To set bridge port thresholds, notiÞcation options, and notiÞcation conditions:

1. In the Forwarding Thresholds windo w , highlight the port where you want to set

thresholds. You can select multiple ports by clicking button 1 on each one. To deselect a port, click it again. To apply the settings to all bridge ports, you can use the options provided at the bottom of the screen rather than selecting all ports in the scroll list.

Conﬁguring Forwarding Thresholds 3-39

CSX Bridge View

2. In the Modify Range section of the Forwarding Thresholds window, you can

edit the line that displays the high end of the Low and Mid ranges, or you can use the slide bars to specify the thresholds. You can also assign a color to each of the three ranges. The Bridge Port entries on the Bridge Trafﬁc View will be colored according to the settings made here (i.e., if you assign the color red to the High trafﬁc range, then a Bridge P ort entry will be colored red when its trafﬁc range is High). To set the high end of the Low and Mid ranges, and assign color codes to all three ranges:

a. Change the upper limit of the Low and Mid trafﬁc ranges by highlighting

the value, typing the new value, and pressing Enter or Return. You may also change the value by moving the slide bar next to the value you wish to change until the desired range is reached.

b. By default, bridge ports are color coded in the Bridge Trafﬁc View

according to their trafﬁc level: Low range is green; Mid range is yellow; High range is red. To assign color codes to the three trafﬁc ranges, click on the Low, Mid, or High buttons to the left of the range ﬁelds, drag to highlight the desired color, and release. The selected color will be displayed on the button, and will be used in the Bridge Port entries when the color’s corresponding range is reached.

3. In the Notiﬁcation Options section, you can enable/disable threshold event

logging, enable/disable the Bridge Port entry colors, and assign threshold events (send mail or execute a program) to the different (or to all) threshold ranges. To do so:

a. To disable threshold event logging, deselect the Log Changes in State

checkbox. By default, all threshold events are logged. For more information about the Forwarding Log, see Vie wing the Forwarding Log on page 3-41.

b. To enable/disable the colors, click button 1 on the Color bo x. When colors

are disabled, the Bridge Port entry colors in the Bridge Trafﬁc Vie w remain as they were when the colors were last enabled.

c. To send mail or execute a program when a threshold range is reached,

ﬁrst click the Threshold Range button to which you want to apply the threshold event. To send mail for a threshold event, select the Send Mail box and enter the name of a registered mail user. To have a threshold event launch a program, select the Execute Program (Args) box and enter the name of an executable ﬁle, including required arguments.

4. Notiﬁcation Conditions make your Notiﬁcation Options subject to deﬁned

conditions: a. If you check the In—Out—In box, notiﬁcation takes place when the

threshold passes from one range to another and then back. The number in the Delay box speciﬁes the number of times this transition is to take place before notiﬁcation is launched. The Current box counts down the transitions.

b. If you select the Remain—In box, notiﬁcation takes place when the

Conﬁguring Forwarding Thresholds 3-40

CSX Bridge View

threshold passes from one range to another, and stays in that range for the number of polling cycles speciﬁed in the Delay box.

c. If you check the Once Only box, notiﬁcation only takes place the ﬁrst time

the Delay count is reached.

5. The Save option giv es you three choices as to ho w the options and conditions

you have selected will be saved. a. If you choose Disabled, none of the options and conditions you have

chosen will be saved to the bridge database.

b. If you select As Default, the chosen options and conditions will be sav ed

as default values . The saved information will be used for any IP not ha ving an entry in the bridge database.

c. If you select By IP, the options and conditions chosen for that IP will be

saved to the bridge database, and the next time the application is run for this device the saved values will be used.

6. When you’ re ﬁnished setting thresholds and notiﬁcation options, clic k b utton 3

on the Apply button and choose either Selected Only or All. Selected Only applies the selected Forwarding Thresholds settings to the ports that are highlighted in the scroll list near the top of the Forwarding Thresholds window.

Viewing the Forwarding Log

The Forwarding Log records an entry each time a bridge portÕs trafÞc passes a preset trafÞc threshold. By default, logging is enabled for all bridge ports.

To open the Forwarding Log window:

1. In the Bridge Trafﬁc View, click mouse button 3 in one of the bridge ports to

display the Port menu.

2. In the Port menu, click button 3 on Forwarding Log and then drag right to

Transparent.

Viewing the Forwarding Log 3-41

CSX Bridge View

NOTE

Figure 3-18. Sample Forwarding Log Window

To select a different Bridge Port log:

1. Use the slide bar at the top of the Forwarding Log window to select a different port.

To clear all logs or just the current log:

1. Click on the Clear button and then select the appropriate choice, either Current Log or All Logs.

To change the number of entries retained by the log:

1. Highlight the Max Number line, type a new number and press Return on the keyboard.

Log entries are stored in the SPMA software. When the maximum number of entries is reached, the entries get aged out as necessary, starting with the oldest entry Þrst.

3-42 Viewing the Forwarding Log

CSX Bridge View

To save log Þles:

1. Click on the Save button and select either Current Log or All Logs to open the Save Log window.

2. In the Save Log window, enter a ﬁle name for the ﬁle to be saved and then click on the OK button. The default directory for saved log ﬁles is the current directory. To specify a different directory, include the path name with the log ﬁle name.

To disable the Forwarding Log of all bridge ports or individual bridge ports:

1. Click button 1 on the appropriate Bridge Port entry to select it.

2. Click button 3 on the Port Menu button to display the Bridge Port menu.

3. In the Port menu, click button 3 on Forwar ding Thresholds and then drag right to either Transparent or Source Routing.

4. In the Forwarding Thresholds window, deselect the Log Changes in State box.

5. Click on the Apply button and then click on either Selected Only or All.

Changing Polling Intervals

Much of the information displayed in the Bridge TrafÞc View is gathered periodically rather than continuously. You can edit the times between these periodic polls.

To edit the polling times:

1. Display the Device menu by clicking on the Front Panel button.

2. Drag down to Polling Intervals and release. The Polling Intervals window displays.

Figure 3-19. The Polling Intervals Window

3. Highlight and edit the Device Info and Bridge Port Display Info boxes and then click on the Apply button to save changes.

Changing Polling Intervals 3-43

CSX Bridge View

You can change values for the following polling interval Þelds:

Device Info

SpeciÞes the time, in seconds, that SPMA waits before updating the Front Panel information (Uptime, Location, and so forth) in the Bridge TrafÞc View.

Bridge Port Display Info

SpeciÞes the time, in seconds, that SPMA waits before updating statistical and status information in the Bridge TrafÞc View port display entries.

Enabling and Disabling Ports

When you disable a bridge port, you disconnect that portÕs network from the bridge entirely. 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.

In Transparent bridges, the disabled port does not forward any packets, nor does it participate in Spanning Tree operations. When you enable a port on a Transparent bridge, the port moves from the Disabled state through the Blocking, Learning, and Listening states to the Forwarding state.

Enabling and Disabling a Transparent Bridge Port

To enable or disable a Transparent bridge port:

1. In the Bridge Trafﬁc View, select a bridge port by clicking mouse button 1on the entry for it. Select the port that connects to the network that you want to enable or disable.

2. Click button 3 on the Port Menu button to display the Bridge Port menu.

3. In the Port menu, click button 3 on Enable or Disable, drag right to Transparent, and release.

When you disable a Transparent bridge port, the portÕs display entry turns blue. When you enable a Transparent bridge port, the portÕs color changes to indicate the forwarding threshold range. (Port color codes are only active if the Color box is selected in the Forwarding Thresholds window. Color codes are on by default.)

3-44 Enabling and Disabling Ports

Chapter 4

CSX W AN Conﬁguration

Conﬁguring the physical ports; assigning protocols to the interfaces; conﬁguring the PPP protocol; conﬁguring the Frame Relay protocol; adding circuits to your Frame Relay protocol; checking statistics

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.

The WPIM-DDS, WPIM-DI, WPIM-E1, and WPIM-HDSL are not supported by

NOTE

SPMA at the time of this release. To conÞgure these WPIMs, use the QuickSET application that was shipped with your device. See your QuickSET documentation for more information.

You can use the WAN ConÞguration application to conÞgure your CSX200/400 WAN connections. Setting up WAN connections on these devices consists of conÞguring the WPIMs on the WAN ports, then conÞguring the protocols supported on the individual WAN interfaces.

Accessing the CSX WAN Conﬁguration Window

The CSX WAN ConÞguration application window varies according to the type of WPIM(s) installed in the device. The means of accessing the window, however, are the same for all CSX200s and the CSX400:

from the icon:

1. Click on the appropriate device icon to display the icon menu.

2. Drag down to Wan-Conﬁg and release.

4-1

CSX WAN Conﬁguration

from the command line (stand-alone mode)

1. From the appropriate directory type:

The spmarun script invoked Þrst in the above command temporarily sets the environment

NOTES

variables SPMA needs to operate; be sure to use this command any time you launch an application from the command line. This script is automatically invoked when you launch the application from the icon menu.

If you wish to change the conÞguration, be sure to use a community name with at least Read/Write access. If you only wish to view current settings, a community name with Read access will be sufÞcient.

If there is a hostname mapped to your CSXÕs IP address, you can use <hostname> in place of <IP address> to launch this application. Please note, however, that the hostname is not the same as the device name which can be assigned via Local Management and/or SPMA; you cannot use the device name in place of the IP address.

The WAN ConÞguration window will appear. Figure 4-1 shows a WAN ConÞguration window for a CSX400 that has two WPIM-T1s installed.

spmarun wancon <IP address> <community name>

4-2 Accessing the CSX WAN Conﬁguration Window

CSX WAN Conﬁguration

Figure 4-1. CSX400 WAN ConÞguration Window

The WAN ConÞguration window for the CSX400 is divided into two sections. The upper and lower portions display the conÞguration of the Þrst and second WAN ports, respectively.

Since all CSX200s contain only one WAN interface, the WAN ConÞguration window for the CSX200 series is half the size (Figure 4-2). Note that the CSX200 WAN ConÞguration window on the following page is displaying different information. This is because the content of a WAN ConÞguration window depends on the type of WPIM(s) installed.

Accessing the CSX WAN Conﬁguration Window 4-3

CSX WAN Conﬁguration

Figure 4-2. Typical CSX200 WAN ConÞguration Window

All CSX WAN ConÞguration windows contain the WAN Connection Þeld, which displays the connection number of the monitored wide area network connection. (Since the CSX200 has only one WAN connection, this will always display 1.)

In addition, all CSX200/400 WAN ConÞguration windows contain the following buttons:

Interfaces

Used to open the Interface ConÞguration Window, described on page 4-9. This window is used to conÞgure the individual interfaces provided by each WPIM.

Protocols

This button accesses conÞguration windows for the appropriate WAN protocol(s). ConÞguring PPP and Frame Relay protocols is discussed later in this chapter.

Statistics

The Statistics button accesses a number of windows containing statistics for PPP and Frame Relay protocols, and (where applicable) for Synchronous ports. See

Checking Statistics on page 4-25 for more information.

Apply

Puts into effect any changes you have made.

Refresh

Causes the application to re-request WAN conÞguration information from the device and thus update the window.

4-4 Accessing the CSX WAN Conﬁguration Window

Quit

Closes the WAN ConÞguration window.

Synchronous Port Conﬁguration

The WPIM-SY supports one physical serial interface on the CSX202 and the CSX400. Through the WAN ConÞguration window you can view the physical conÞguration of your synchronous port and change the In Speed, Out Speed, and Port Type displayed for your synchronous connection. The WAN ConÞguration window for the WPIM-SY is shown in Figure 4-2 on page 4-4.

In this window you will see the following Þelds:

Line Status

Displays the status of the port. The status can be one of the following:

¥ Inactive Ñ The connection through this port is not active.

¥ OK Ñ The port is the active port and the connection is operational.

¥ In Alarm Ñ The port is the active port, but the connection has experienced a

failure. When either the Cts (Clear to Send) or Dsr (Data Set Ready) signal is Off and the signal is enabled, the port will enter the state of In Alarm.

CSX WAN Conﬁguration

The left side of this portion of the window is color-coded to indicate the line status: Blue for Inactive; Green for OK; and Red for In Alarm.

Port 1

Displays the port type: Synchronous.

In Speed

Allows you to enter the speed of input communications of the synchronous port.

Out Speed

Allows you to enter the speed of output communications of the synchronous port.

Port T ype

Indicates the type of connection used at the port. The available connections are RS422, RS232, V.35, or None. You should set the port type to match the conÞguration of the connected equipment.

Cts Enable

This Þeld displays whether the Cts (Clear to Send) signal is enabled. If the Cts signal is enabled (Yes), the device will use it to determine the status of the connection. If the signal is disabled (No), it will be ignored.

Synchronous Port Conﬁguration 4-5

CSX WAN Conﬁguration

Dsr Enable

This Þeld displays whether the Dsr (Data Set Ready) signal is enabled. If the Dsr signal is enabled (Yes), the device will use it to determine the status of the connection. If the signal is disabled (No), it will be ignored.

Conﬁguring the Synchronous Port

You can conÞgure your synchronous port as follows:

1. To change the Port Type , click on the selection box and a pull down menu will appear. Select V.35, Rs422, Rs232, or None as appropriate, and release the mouse button.

2. To change the In Speed or Out Speed, highlight the current speed and type a new value in the text box.

3. Click on to save the changes or to go back to the original conﬁguration.

The new synchronous interface conÞguration will be displayed in the window.

T1 Port Conﬁguration

You can view the current conÞguration of a WPIM-T1 Ñ or the T1 interface on a WPIM-T1/DDS Ñ on your CSX201 or CSX400 from the WAN ConÞguration window (Figure 4-3). You can change the Circuit Id and Line Coding values, and conÞgure the Fractional Table to represent the use of the timeslots on the T1 line in relation to the interfaces on your connection.

Figure 4-3. WPIM-T1 ConÞguration

4-6 T1 Port Conﬁguration

CSX WAN Conﬁguration

In this window you will see the following Þelds:

Line Status

Displays the status of the port. The status can be one of the following:

¥ Inactive Ñ The connection through this port is not active.

¥ OK Ñ The port is the active port and the connection is operational.

¥ In Alarm Ñ The port is the active port and the connection has experienced a

failure.

The left side of this portion of the window is color-coded to indicate the line status: Blue for Inactive; Green for OK; and Red for In Alarm.

Port 1

Displays the port type, i.e., Fractional T1.

Circuit Id

The Circuit Id Þeld lets you enter a character string Ñ speciÞed by the circuit vendor as a circuit identiÞer Ñ for troubleshooting purposes.

NOTE

Line Code

Displays the line coding for the Full T1 line. The available selections are B8ZS and AMI. The default for this Þeld is B8ZS. If AMI is chosen, the line code selection on each active interface cannot be None (see ConÞguring the WAN Interfaces on

page 4-11 for more information). The line code should be set according to your

WAN service providerÕs instructions.

While it is possible for the next three Þelds Line Build Out, Framing Type, and Clock Source to be set remotely on a CSX, Cabletron recommends against it, as you may

inadvertently interrupt a working connection. All three should be set at the hardware level with switches on the device. For more information on how to set these switches, see your hardware documentation.

Line Build Out

Displays the value of the Line Build Out setting, which controls the amount of attenuation of the T1 signal. The possible values in this Þeld are 0 db, -7.5 db,

-15 db, and Unknown. You should set Line Build Out at the device according to your WAN service providerÕs instructions.

Framing Type

Displays the type of service you are using over your T1 line (i.e., ESF Ð Extended Super Frame DS1, or D4 Ð AT&T D4 format DS1). You should set the Framing Type at your device according to your WAN service providerÕs instructions.

Clock Source

Displays the T1 Transmit Clock Source. Loop Timing indicates that the recovered receive clock is used as the transmit clock. Local Timing indicates that an internal

T1 Port Conﬁguration 4-7

CSX WAN Conﬁguration

clock source is used. You should set the Clock Source at your device according to your WAN service providerÕs instructions.

Conﬁguring the T1 Port

1. To change the Line Code, click on the selection box and a pull down menu will appear. Select B8ZS or AMI as appropriate, and release the mouse button. The new conﬁguration will appear in the text box.

2. To change the Circuit Id, highlight the current entry in the text ﬁeld, and type a new value in the text box.

3. Click on to save the changes or to go back to the original conﬁguration.

The new T1 interface conÞguration will be displayed in the window. Remember, these conÞguration changes are for reference purposes only, and they will not be physically set at the device.

Using the Fractional Table

The Fractional Table graphically represents how your Fractional T1 line is divided for use among the virtual interfaces. The Fractional Table allows you to map timeslots on the T1 line to an individual interface or a group of interfaces. The timeslots should be used according to the mapping provided by your wide area carrier.

Figure 4-4 illustrates a sample conÞguration of a T1 connection that was set

according to the mapping provided by the WAN service provider.

Figure 4-4. Example Fractional Table ConÞguration

To conÞgure the Fractional Table:

1. Type the interface number into the boxes of the timeslots your wide area carrier has assigned. In the preceding illustration, the wide area carrier assigned timeslots 1-12 for use on interface 2, and 13-24 for interface 4.

2. When you are done assigning the timeslots, click on .

The Fractional Table will now display the timeslots assigned to your interfaces.

4-8 T1 Port Conﬁguration

WPIM S/T Conﬁguration

The WPIM-S/T provides an Integrated Services Digital Network (ISDN) Basic Rate Interface (BRI) for the CSX400 only. This link is intended as a backup for when the deviceÕs other WAN interface, the primary WPIM link, becomes disabled. For information on setting up an ISDN backup WAN link, consult your WPIM-S/T and CSX400 hardware documentation.

Interface Conﬁguration Window

After conÞguring the physical ports on your CSX, you must conÞgure the individual interfaces on the WAN ports. The WAN Interface ConÞguration window displays information about each WAN interface that is associated with the physical ports.

To open this window:

1. From the WAN Conﬁguration window click on . The WAN Interf ace

Conﬁguration window will appear. As an example, Figure 4-5 shows a WAN Interface Conﬁguration window for a CSX201, which has a WPIM-T1 with 24 interfaces.

CSX WAN Conﬁguration

The following information is displayed for each interface.

Conn#

Displays the number of the physical connection the interface is on.

Port# (Type)

Displays the number of the physical port on the CSX that this interface is on. This Þeld also displays the type of port, i.e., Synchronous (sync) or T1 (t1).

WanIf#

Displays the WAN Interface number or the ordered number of the interface on the port. A Synchronous Port will have one interface numbered 1, for example, and a T1 Port will have interfaces numbered 1-24.

WPIM S/T Conﬁguration 4-9

CSX WAN Conﬁguration

Figure 4-5. WAN Interface ConÞguration Window

NOTE

IfIndex#

Displays the interface index; a unique value for each logical interface on this device. This number is used when you map the interface on the fractional table of a T1 port.

Protocol

Displays the active Link Layer protocol. You can assign PPP (Point to Point Protocol), Frame Relay, or None as the protocol on the interface. An error message will appear if you choose a protocol which is not supported by the Þrmware.

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. The value in this Þeld must be between 128 and 8191.

Interfaces assigned Frame Relay protocol will have a default MTU value of 4095; interfaces assigned PPP protocol will have a default value of 8191.

Line Coding

Displays the line coding set for this interface. You can choose from JBZS, Inverted HDLC, or None. None (the default value) should not be selected when you are using AMI line coding on the interface. Set this value according to your WAN service providerÕs instructions.

4-10 Interface Conﬁguration Window

NOTE

CSX WAN Conﬁguration

Compression

Indicates whether data compression is activated or de-activated.You can choose ÔOnÕ to activate compression or ÔOffÕ to de-activate it.

Data compression is not supported by CSX Þrmware at this time; therefore, compression will always be de-activated or ÒOffÓ.

Lex Status

Indicates if the interface has connected to a Cisco router using the Lex protocol. If a connection has been made, the Þeld will display Bound; if a connection has not been made, the Þeld will display UnBound; if the interface does not support Lex Protocol the Þeld will display NotSupp.

The CSX does not currently support PPP/Lex protocol; therefore the Lex Status Þeld will always display NotSupp (Not Supported).

Conﬁguring the WAN Interfaces

You can conÞgure the WAN Interfaces as follows:

1. Use the Set Selection button to specify the scope of interfaces to which

conﬁguration changes will apply: a. Choose Selected Interfaces to apply changes only to those interfaces

highlighted in the scroll list. Click mouse button 1 to highlight one or more interfaces in the list. Use

the scroll bar, if necessary, to scroll through the available interfaces.

b. Choose All Interfaces to apply changes to all WAN interfaces on the

device.

2. To change the Protocol Selection, click on the selection box; a pull-down

menu will appear. Select None, PPP, or Frame Relay, as appropriate.

3. To alter the MTU, highlight the current MTU value, and type in a new value

from 128 to 8191 in the text box. Note that if you do not change the current MTU value, a default MTU will

appear in accordance with your Protocol Selection (4095 for Frame Relay; 8191 for PPP).

Interface Conﬁguration Window 4-11

CSX WAN Conﬁguration

4. To change the Line Coding, click on the selection box; a pull-down menu will appear. Select None, J8ZS, or Inverted HDLC, as appropriate. Remember that None (the default value) should not be selected when you are using AMI line coding on the interface

5. Click on to save the changes or to restore the original conﬁguration.

The saved conÞguration changes will appear in the WAN interface list.

Conﬁguring the PPP Protocol

After you have assigned protocols to your interfaces, you should conÞgure the protocols appropriately.

You use the PPP Link Control ConÞguration window to set up the Point-to-Point Protocol for use on your network interfaces on your WAN connection. This window also lets you access the Bridge Network Control Protocol ConÞguration window. As deÞned by RFC 1661, the Point-to-Point Protocol (PPP) is a standard method of transporting multi-protocol datagrams over point-to-point links. A PPP Link provides full-duplex communication between the endpoints, allowing a simultaneous bi-directional operation that should maintain the order in which data packets are transmitted.

There are three components to PPP:

¥ A method of encapsulating the datagrams to be transported. This

encapsulation allows different network-layer protocols to be simultaneously multiplexed over the same link, and is compatible with commonly used network hardware.

¥ The Link Control Protocol (LCP), which is used to establish, conÞgure, and test

the point-to-point data-link connection. The Link Control Protocol provides a mechanism for conÞguring and managing the link between the end point connections. LCP allows both endpoints to describe their capabilities and requirements to each other, and negotiate the encapsulation format and the maximum datagram size. LCP also detects common conÞguration errors, such as loopback conditions, and terminates the link when the communication is complete. Other management options provided by LCP include the authenticating of the peers on each end of the link, and determining whether the link is functioning properly or failing.

¥ A family of Network Control Protocols (NCP), used to establish and conÞgure

the different network-layer protocol datagrams that need to be transported.

To access the PPP Link Control Protocol ConÞguration window:

1. Click on . A pull-down menu will appear.

2. Drag down to PPP and release. The PPP Link Control Protocol Conﬁguration window will appear.

4-12 Conﬁguring the PPP Protocol

CSX WAN Conﬁguration

Figure 4-6. PPP Link Control Protocol ConÞguration Window

PPP Link Control Protocol Status Fields

The following information will appear for each interface conÞgured to use PPP:

If#

Displays the interface number. This number of logical interfaces will vary, depending on the WPIM installed.

PhysIf#

IdentiÞes the lower-level interface number over which this PPP link is operating.

Currently the PhysIf# is not supported by the CSX; therefore, this Þeld will always

NOTE

display zero.

Local MRU

The Local MRU Þeld displays the Maximum Receive Unit (MRU) currently conÞgured for the local WAN interface (the value that the remote entity is using when sending packets to the local PPP entity). The MRU is the maximum length of data information (including Ò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 8191 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).

Conﬁguring the PPP Protocol 4-13

CSX WAN Conﬁguration

Remote MRU

The Remote MRU Þeld displays the Maximum Receive Unit (MRU) established for the remote interface at the other end of the PPP Link (the value that the local entity is using when sending packets to the remote PPP entity).

Local —> Remote Comprs (Compression)

By default, a PPP link must be able to transmit packets with two-octet PPP Protocol Field values; however to conserve bandwidth on low speed links, PPP was designed to omit redundant data by allowing some PPP Protocol Field values to be compressed into a single octet that can be readily recognized from its twooctet form.

The LocalÐ>Remote Comprs conÞguration option indicates whether Protocol Field Compression (PFC) is Enabled or Disabled at the local PPP entity when it transmits packets to the remote PPP entity. Packets with compressed Protocol Field values must not be transmitted until this value has been negotiated between both PPP entities.

Remote —> Local Comprs (Compression)

This conÞguration option indicates whether Protocol Field Compression (PFC) is Enabled or Disabled at the remote PPP entity when it transmits packets to the local PPP entity. Packets with compressed Protocol Field values must not be transmitted until this value has been negotiated between both PPP entities.

Tx FCS Size

The size of the Frame Check Sequence (FCS) in bits that the local node will generate when sending packets to the remote node. The value of this object is meaningful only when the link has reached the open state. 16 bits is the only FCS size supported.

Rx FCS Size

The size of the Frame Check Sequence (FCS) in bits that the remote node will generate when sending packets to the local node. The value of this object is meaningful only when the link has reached the open state.

Link Control Protocol Conﬁguration Fields

The LCP ConÞguration section shows parameters which will be communicated by LCP during the link establishment phase between the CSXÕs local interfaces and the remote interfaces at the other end of the link, and lets you alter those parameters at the local interfaces, if necessary.

If#

The SNMP MIB-2 ifIndex of the physical interface on the CSX at which the PPPLink is conÞgured.

4-14 Conﬁguring the PPP Protocol

CSX WAN Conﬁguration

Initial MRU

The initial Maximum Receive Unit (MRU) that the local PPP entity will advertise to the remote entity. If the value of this variable is 0, then the local PPP entity will not advertise any MRU to the remote entity and the default MRU will be assumed. Changes to this object take effect when the link is next restarted.

The default MRU for the CSX is 8191.

Magic Num. Neg.

The Magic Number Negotiation Option enables the detection of looped-back links and other Data Link Layer anomalies.

If Magic Number Negotiation is set to True, the local node will attempt to perform Magic Number Negotiation with the remote node; if set to False, the negotiation is not performed by the local node. In any event, the local node will comply with any Magic Number negotiations attempted by the remote node, per the PPP speciÞcation. By default, the Magic Number is not negotiated, and zero is inserted where a Magic Number might otherwise be used. Changes to this object take effect when the link is next restarted.

The Magic Number is a number that should be selected randomly by the device implementing PPP (e.g., based on unique seed, such as a machine serial number, a network hardware address, a time-of-day clock, or the precise measurement of the inter-arrival time of physical events such as packet reception on other connected networks).

When a PPP peer has the Magic Number ConÞguration option enabled, and receives a ConÞgure-Request with a randomly generated Magic Number, it compares that number with that of the last ConÞgure-Request it received.

¥ If the two Magic Numbers are different, then the link is not looped-back, and

the Magic Number SHOULD be acknowledged.

¥ If the two Magic Numbers are equal, then it is possible (but not certain) that

the link is looped-back and that the ConÞgure-Request just received was actually the last one issued by the receiving peer. Further checks are carried out to determine whether a loopback condition exists.

The Magic Number also may be used to detect looped-back links during normal operation, as well as during ConÞguration Option negotiation. All LCP EchoRequest, Echo-Reply, and Discard-Request packets have a Magic Number Þeld. If a Magic Number has been successfully negotiated, an implementation MUST transmit these packets with the Magic Number Þeld set to its negotiated Magic Number. The Magic Number Þeld of these packets SHOULD be inspected on reception.

All received Magic Number Þelds MUST be equal to either zero or the peerÕs unique Magic Number, depending on whether or not the peer negotiated a Magic Number.

Conﬁguring the PPP Protocol 4-15

CSX WAN Conﬁguration

Reception of a Magic Number Þeld equal to the negotiated local Magic Number should indicate a looped-back link. Reception of a Magic Number other than the negotiated local Magic Number, the peerÕs negotiated Magic Number, or zero (if the peer didnÕt negotiate one), indicates a link which has been (mis)conÞgured for communications with a different peer.

Recovery procedures from a looped-back or misconÞgured PPP Link are unspeciÞed by the PPP protocol, and may vary from implementation to implementation. One recovery procedure is to assume a LCP Down event which requires a further Open event to begin re-establishing the link (an Open event canÕt complete until the looped-back condition is terminated, and Magic Numbers are successfully negotiated). A more optimistic procedure (in the case of a looped-back link) is to begin transmitting LCP Echo-Request packets until an appropriate Echo-Reply is received, indicating a termination of the looped- back condition.

FCS Size

The size of the FCS, in bits, the local node will attempt to negotiate for use with the remote node. Regardless of the value of this object, the local node will comply with any FCS size negotiations initiated by the remote node, per the PPP speciÞcation. Changing this object will have effect when the link is next restarted. Currently only a 16 bit FCS is supported.

Conﬁguring Link Control Protocol Options

You can use the PPP Link Control Protocol ConÞguration window to set the Initial MRU and enable or disable Magic Number Negotiation for the CSXÕs interfaces on which a PPP link has been established.

To establish the Initial MRU for a PPP Link:

1. Use the Set Selection button to specify the scope of interfaces to which conﬁguration changes will apply:

a. Choose Selected Interfaces to apply changes only to those interfaces

highlighted in the scroll list. Click mouse button 1 to highlight one or more interfaces in the Link

Control Protocol: Conﬁguration scroll list.

b. Choose All Interfaces to apply changes to all WAN interfaces on the

device that are conﬁgured for LCP.

2. Click mouse button 1 in the Initial MRU text ﬁeld, type in the MRU which you want to be negotiated for the local PPP peer(s) on the CSX, and press Enter or Return on the keyboard.

3. Click mouse button 1 on to save the changes or to restore the original conﬁguration.

To determine whether the local peer of a PPP Link will use Magic Number Negotiation to check for loop-back conditions or other Datalink Layer errors:

4-16 Conﬁguring the PPP Protocol

1. Use the Set Selection button to specify the scope of interfaces to which

conﬁguration changes will apply: a. Choose Selected Interfaces to apply changes only to those interfaces

highlighted in the scroll list. Click mouse button 1 to highlight one or more interfaces in the Link

Control Protocol: Conﬁguration scroll list.

b. Choose All Interfaces to apply changes to all WAN interfaces on the

device that are conﬁgured for LCP.

2. Click mouse button 1 on the Magic Num. Neg button. This is a toggle button

which will display True (if Magic Number Negotiation is to be enabled at the local peers) or False (if Magic Number Negotiation is to be disabled at the local PPP peers on the CSX).

3. Click mouse button 1 on to save the changes or to

restore the original conﬁguration.

Viewing the PPP Bridge Network Control Protocol

CSX WAN Conﬁguration

When you click on , the Bridge Network Control Protocol window will appear. Bridge Network Control Protocol is the PPP control protocol used to pass bridge packets over a PPP link.

Figure 4-7. PPP Bridge Network Control Protocol ConÞguration Window

You can view the following BNCP status Þelds from this window.

If#

Displays the virtual interface number.

Conﬁguring the PPP Protocol 4-17

CSX WAN Conﬁguration

Oper Status

The operational status of the bridge network protocol. Opened indicates that the interface is operational for bridging. Not Opened indicates that bridging is not operational on this interface.

Local LanId

Indicates if the local node will include the LAN IdentiÞcation Þeld in transmitted packets. If the value in this Þeld is True, then the Þeld will be transmitted with the packet. If the value in the Þeld is False, then the Þeld will not be transmitted.

Remote LanId

Indicates if the remote node will be including the LAN IdentiÞcation Þeld in transmitted packets. If the value is True, then the Þeld will be transmitted with the packet. If the value is False, then the Þeld will not be transmitted.

Local Media

Displays the media type(s) of packets that the local PPP bridging entity will accept. Possible media types are Enet Only, Token Only, and Enet/Token.

Remote Media

Displays the media type(s) of packets that the remote PPP bridging entity will accept. Possible media types are Enet Only, Token Only, and Enet/Token.

Conﬁguring the Frame Relay Protocol

When you use Frame Relay protocol on your interface(s) all the communication between the nodes goes through a switch before arriving at the destination node. If you are using Frame Relay Protocol on any of the interfaces on your WAN connection you should conÞgure this protocol to work within your speciÞc network parameters. The Protocols button on the CSX WAN ConÞguration window will bring up the Frame Relay ConÞguration window. From this window you can conÞgure the Frame Relay protocol and use the Circuits window to conÞgure the individual circuits on each interface.

To open the Frame Relay ConÞguration window:

1. Click on . A pull down menu will appear.

2. Drag down to Frame Relay and release. The Frame Relay Conﬁguration window will appear.

4-18 Conﬁguring the Frame Relay Protocol

CSX WAN Conﬁguration

Figure 4-8. The Frame Relay ConÞguration Window

You can view the following information for each interface assigned the Frame Relay Protocol. You can also change the State, Polling Interval, Full Enquiry Interval, Error Threshold, Monitored Events, and Max Virtual Circuits settings.

If#

Displays the interface number. The total number of interfaces on the device depends on the type of WPIM installed.

State

Displays the state of the local management interface that is running on the interface. Default is ansiT1-617-D. If the network carrier is not running an LMI (Local Management Interface) this can be changed to the other option, noLmiConÞgured.

Addr

Displays which address format is being used on the Frame Relay interface. The supported address format is q922.

Address Length (AddrLen)

Displays the address format in octets. The supported address length on a CSX is two-octets.

Conﬁguring the Frame Relay Protocol 4-19

CSX WAN Conﬁguration

Polling Interval (PollInt)

Displays the number of seconds between successive status enquiry messages. The polling interval can be from 5 to 30 seconds. The default polling interval is 10.

Full Enquiry Interval (FullEnqInt)

Displays the number of status enquiry intervals that pass before a full status enquiry message is issued. The value can be from 1 to 255. The default value is 6.

Error Threshold (ErrThresh)

Displays the maximum number of unanswered status enquiries the equipment shall accept before declaring the interface down. The threshold can be from 1 to 10 enquiries. The default value for this Þeld is 3.

Monitored Events (MonEvents)

Displays the number of status polling intervals over which the error threshold is counted. For example, if the station hits the error threshold number within a monitored events interval, the interface is displayed as down. The number can be from 1 to 10, with a default value of 4.

Max Virtual Circuits (NumVCs)

Displays the maximum number of Virtual Circuits allowed for this interface, which is 4 on a CSX200 and 32 on a CSX400.

Multicast Type

Indicates whether the Frame Relay interface is using a multicast service. This Þeld can be either nonBroadcast or Broadcast.

Currently, you cannot change the Multicast Type from this window.

NOTE

Conﬁguring the Frame Relay Protocol

You can change the conÞguration of the Frame Relay Protocol from this window. In order to change any information on an interface, that interface must be highlighted. The current conÞguration will appear in the Þelds next to the selection boxes under the interface list.

1. Use the Set Selection button to specify the scope of interfaces to which conﬁguration changes will apply:

a. Choose Selected Interfaces to apply changes only to those interfaces

highlighted in the scroll list. Click mouse button 1 to highlight one or more interfaces in the Frame

Relay DLCMl Conﬁguration scroll list.

4-20 Conﬁguring the Frame Relay Protocol

CSX WAN Conﬁguration

b. Choose All Interfaces to apply changes to all WAN interfaces on the

device that are conﬁgured for Frame Relay.

2. To change the State, click on the selection box and a pull down menu will

appear. Select either ansiT1-617-D or noLmiConﬁgured, and release the mouse button. The new conﬁguration will appear in the text box.

3. To change the Polling Interval, highlight the current value in the te xt box, type

a new value (from 5-30 seconds) in the text box, and press Enter/Return.

4. To change the Full Enquiry Interval, highlight the current value in the text

box, type a new v alue (from 1-255) f or the number of successiv e intervals that must pass before a Full Enquiry message is sent, and press Enter/Return.

5. To change the Error Threshold, highlight the current value in the text box,

type in a new value (from 1-10) for unanswered status enquiries that must pass before the interface is declared to be down, and press Enter/Return.

6. To change the Monitored Events, highlight the current value in the text box,

type a new value (from 1-10) for the number of status polling intervals over which the error threshold is counted, and press Enter/Return.

7. To change the Max Virtual Circuits, highlight the current value in the te xt bo x,

type a new value (between 1 and 4 on a CSX200 device, between 1 and 32 for each interface on a CSX400) in the text box, and press Enter/Return.

8. Click on to save the changes or to restore the original

conﬁguration.

Conﬁguring the Frame Relay Protocol 4-21

CSX WAN Conﬁguration

Viewing the Circuit Conﬁguration

The Frame Relay protocol can be set to two different states: ansiT1617 with LMI (Local Management Interface) or noLmiConÞgured. A frame relay network uses circuits as connections to the other points on the network. When an LMI is conÞgured for your interface, the circuits will automatically be listed in the Frame Relay Circuit Table. The switch will report the circuits to your device. If there is no LMI on your connection, you will have to manually add the circuits. The Frame Relay Circuit Table displays the circuits that are currently deÞned on all the frame relay interfaces conÞgured on the device.

To view the Frame Relay Circuit Table window:

1. From the F rame Rela y Protocol Conﬁgur ation window, click on . The Frame Relay Circuit Table, Figure 4-9, will be displayed.

Figure 4-9. The Frame Relay Circuit Table Window

The following Þelds are displayed in the Frame Relay Circuit Table. The State, Committed Burst, Excess Burst, and CIR Þelds are user-conÞgurable.

If#

Displays the number of the interface this virtual circuit is layered upon.

DLCI

The Data Link Connection IdentiÞer for the virtual circuit. This is a routing ID that links the logical port to a virtual connection on the physical frame relay port. This number is usually assigned by your frame relay provider. The CSX200 can support up to 4 virtual circuits and the CSX400 can support up to 32 per interface.

4-22 Conﬁguring the Frame Relay Protocol

CSX WAN Conﬁguration

State

Indicates whether the selected virtual circuit is operational. If the circuit is active, it is considered operational. If the circuit is labeled inactive then the circuit is temporarily disabled, but still has the capability of being active. If the state of the circuit is invalid, then the circuit is not operational. You can temporarily disable a circuit by changing the state to Ôinactive.Õ The default state is Ôactive.Õ

Create

Displays the value of the sysUpTime when the virtual circuit was created, whether by the Data Link Connection Management Interface or by a SetRequest.

LastChange

Display the value of sysUpTime when last there was a change in the virtual circuit state.

CommittedBurst (B

)

Indicates the maximum amount of data, in bits, that the network agrees to transfer under normal conditions, during the committed time interval Ñ Tc. You can change the value of this Þeld from this window. The default value is 0, which signiÞes no commitment.

ExcessBurst

Indicates the maximum amount of uncommitted data bits that the network will attempt to deliver over the committed time interval Tc. Excess burst data is eligible to be discarded if the network is experiencing congestion. You can change this value from this window. If you do not conÞgure this Þeld, the default is the value is ifSpeed.

CIR (Committed Information Rate)

The Committed Information Rate (CIR) is the subscriber data rate (expressed in bits/second) that the network commits to deliver under normal network conditions. CIR is averaged over the committed time interval Tc (CIR = Bc/Tc).

Conﬁguring the Frame Relay Protocol 4-23

CSX WAN Conﬁguration

Conﬁguring the Circuits

You can change the conÞguration of the circuits from this window, as follows:

1. Use the Set Selection button to specify the scope of interfaces to which

2. To change the State, click on the selection box and a pull down menu will

3. To change the Committed Burst, highlight the current value in the text box,

conﬁguration changes will apply: a. Choose Selected Interfaces to apply changes only to those interfaces

highlighted in the scroll list. Click mouse button 1 to highlight one or more interfaces in the Frame

Relay Circuits scroll list.

b. Choose All Interfaces to apply changes to all WAN interfaces on the

device that are conﬁgured for Frame Relay and that have deﬁned circuits.

appear. Select invalid, active, or inactive, and release the mouse button. The new conﬁguration will appear in the text box.

type in the maximum amount of data (in bits) that this circuit will agree to transfer under normal conditions during the committed time interval, and press Enter/Return.

4. To change the Excess Burst, highlight the current value in the text box, type

5. To change the Committed Information Rate (CIR), highlight the current value

6. Click on to save the changes or to restore the original

Adding Circuits

The Add Frame Relay Circuits window allows you to add circuits to a frame relay interface that does not support LMI (ansiT1617). To add a circuit:

1. From the Frame Relay Circuit Table, click on . The Add Frame

in the maximum amount of uncommitted data (in bits) that this circuit will make a best-effort attempt to deliver over the committed time interval, and press Enter/Return.

in the text box, type the average number data rate (in bits/second) that the network will agree to transfer across the User Network Interface in one direction over the committed time interval under normal circumstances, and press Enter/Return.

conﬁguration.

Relay Circuits window will be displayed.

4-24 Conﬁguring the Frame Relay Protocol

CSX WAN Conﬁguration

Figure 4-10. The Add Frame Relay Circuits Window

2. Enter the Interface Number of the circuit. This is the number of the interface

the circuit will reside on. Only interface numbers which have been assigned Frame Relay protocol will be accepted.

3. Enter the DLCI Number of the circuit.

4. Click on the State selection box to determine the operational state of the new

circuit: active (the default) or inactive.

5. Click on to add the circuit to the circuit table. Repeat these steps for

each circuit you want to add to the interface.

Checking Statistics

The Statistics windows contains various statistics for the PPP and Frame Relay Protocols and the Synchronous port you are using on your CSX. All Þve statistics windows Ñ described in the following sections Ñ are available from the CSX WAN ConÞguration windowÕs Statistics pull-down menu.

PPP Link Control Protocol Errors

The PPP Link Control Protocol Errors window (Figure 4-11) displays the error counts for each interface conÞgured to use the PPP Protocol. To open this window:

1. Click on . A pull-down menu will appear.

2. Drag down to Ppp Lcp Errors and release.

Checking Statistics 4-25

CSX WAN Conﬁguration

Figure 4-11. The PPP Link Control Protocol Errors Window

Following are descriptions of each of the errors which are recorded in this window.

If#

The interface number to which the collected statistics in the row are related.

Bad Addr

The number of packets received on the PPP Link with an incorrect address Þeld. This counter is a component of the ifInErrors variable that is associated with the interface that represents this PPP Link.

Bad Controls

The number of packets received on this link with an incorrect control Þeld. This counter is a component of the ifInErrors variable that is associated with the interface that represents this PPP Link.

Packet T oo Long

The number of received packets that have been discarded because their length exceeded the MRU. This counter is a component of the ifInErrors variable that is associated with the interface that represents this PPP Link.

Packets which are longer than the MRU but which are successfully received and processed are not included in the Packets Long count.

Frame Check Errors

The number of received packets that have been discarded because of an incorrect FCS. This counter is a component of the ifInErrors variable that is associated with the interface that represents this PPP Link.

4-26 Checking Statistics

Frame Relay DLCMI Last Error

The Frame Relay DLCMI Last Error window contains a line for each interface conÞgured to use the Frame Relay protocol. It displays the last error for each interface. To open this window:

1. Click on . A pull-down menu will appear.

2. Drag down to Frame Relay Dlcmi Errors and release. Figure 4-12 will

appear.

CSX WAN Conﬁguration

Figure 4-12. The Frame Relay DLCMI Last Error Window

Following are descriptions of each of the errors which are recorded in this window.

If#

The interface number to which the collected statistics in the row are related.

Type

Displays the type of the last error seen on this interface. The possible error types are:

¥ unknownError ¥ receiveShort ¥ receiveLong ¥ illegalDLCI ¥ unknownDLCI ¥ dlcmiProtoErr ¥ dlcmiUnknownIE ¥ dlcmiSequenceErr ¥ dlcmiUnknownReport ¥ noErrorSinceReset

Time

The sysUpTime at the time that the error was detected in hundredths of a second.

Checking Statistics 4-27

CSX WAN Conﬁguration

Data

Displays an octet string containing as much of the error packet as possible.

Frame Relay Circuit Counters

The Frame Relay Circuit Counters window contains a line for each frame relay circuit conÞgured. It displays the error counts for each circuit.

To open this window:

1. Click on . A pull-down menu will appear.

2. Drag down to Frame Relay Circuit and release. Figure 4-13 will appear.

Figure 4-13. The Frame Relay Circuit Counters Window

Following are descriptions of each of the errors which are recorded in this window.

If#

The interface number to which the collected statistics in the row are related.

DLCI

The Data Link Connection IdentiÞer for the virtual circuit. This uniquely identiÞes the end point of a PVC (Permanent Virtual Circuit), and only has relevance to that PVC.

RcvFECN

Displays the number of Forward Explicit Congestion NotiÞcation (FECN) frames received from the network indicating forward congestion since the virtual circuit was created. FECNs are sent by the network to notify the CSX that congestion avoidance procedures should be initiated when it is receiving data.

RcvBECN

Displays the number of Backward Explicit Congestion NotiÞcation (BECN) frames received from the network indicating backward congestion since the

4-28 Checking Statistics

CSX WAN Conﬁguration

virtual circuit was created. BECNs are sent by the network to notify the CSX that congestion avoidance procedures should be initiated when it is sending data.

XmtFrame

Displays the number of frames transmitted from this virtual circuit since it was created.

XmtOctets

Displays the number of octets transmitted from this virtual circuit since it was created.

RcvFrame

Displays the number of frames received over this virtual circuit since it was created.

RcvOctets

Displays the number of octets received over this virtual circuit since it was created.

Creating Meters

By clicking on from the Frame Relay Circuit Counters window, you can display a window containing a meter for each of its statistics. See Figure 4-14 on the following page for an example of the meters that you can create.

For more information on using meters and understanding how to read the information displayed, refer to the Charts, Graphs, and Meters chapter in the

SPMA Tools Guide.

Checking Statistics 4-29

CSX WAN Conﬁguration

Figure 4-14. Frame Relay Circuit Counters Meters

Synchronous Port Errors

The Synchronous Port Errors window contains a line for each synchronous port. The errors that the synchronous port has received are displayed.

To open this window:

1. Click on . A pull-down menu will appear.

2. Drag down to Synchronous Port Errors and release. Figure 4-15 will appear.

Figure 4-15. The Synchronous Port Errors Window

4-30 Checking Statistics

CSX WAN Conﬁguration

Following are descriptions of each of the errors which are recorded in this window.

RsPort#

A unique number assigned to the synchronous port.

FCS Err

Displays the total number of frames with an invalid frame check sequence that were input from the port while its state was up or test, since the system was last initialized.

Transmit Underrun

Displays the total number of frames that failed to be transmitted on the port because data was not available to the transmitter in time while its state was up or test, since the system was last initialized.

Receive Underrun

Displays the total number of frames that failed to be received on the port because the receiver did not accept the data in time while its state was up or test, since the system was last initialized.

Interrupted

Displays the total number of frames that failed to be received or transmitted on the port due to loss of modem signals while its state was up or test, since the system was last initialized.

Aborted

Displays the total number of frames aborted on the port due to receiving an abort sequence while its state was up or test, since the system was last initialized.

Synchronous Port Signals

The Synchronous Port Signals window contains a line for each input and output signal on each synchronous port. The information in this window includes the signal types that the synchronous port has received or sent, as well as the current state of each signal, and the number of state changes of each signal.

To open this window:

1. Click on . A pull-down menu will appear.

2. Drag down to Synchronous Port Signals and release. Figure 4-16 will

appear.

Checking Statistics 4-31

CSX WAN Conﬁguration

The information in this window includes:

RsPort#

A unique number assigned to the synchronous port.

Figure 4-16. The Synchronous Port Signals Window

SigName

IdentiÞes the type of input or output signal that has been received or transmitted. The types of signals are as follows:

rts Request to Send cts Clear to Send dsr Data Set Ready dtr Data Terminal Ready ri Ring Indicator dcd Received Line Signal Detector sq Signal Quality Detector srs Data Signaling Rate Selector srts Secondary Request to Send scts Secondary Clear to Send sdcd Secondary Received Line Signal Detector

State

Displays the current signal state: none, on, or off.

Changes

Displays the number of times the signal has changed from ÔonÕ to ÔoffÕ or ÔoffÕ to ÔonÕ.

4-32 Checking Statistics

Index

Add Circuits button 4-24 add circuits to a frame relay interface 4-24 Add Frame Relay Circuits window 4-25 Add to Static Table button 3-26 Addr 4-19 AddrLen 4-19 Admin button 3-8 Ageing Time 3-22, 3-24 All Filters button 3-18 All Paths Explorer (APE) packet 3-37 Apply button 3-18

BPDU ageing timer 3-30 Bridge Port box 3-7

color coding 3-7 bridge port Color codes 3-40 Bridge Port Display Info 3-44 bridge port state 3-8

blocking 3-9

broken 3-9

disabled 3-8

forwarding 3-9

learning 3-9

listening 3-9 bridge port status 3-8

disabled 3-8

enabled 3-8 bridge port TrafÞc levels 3-39 Bridge Protocol Data Units (BPDUs) 3-2, 3-28 Bridge Statistics window 3-13

accessing 3-13 Bridge Status window

setting and changing information 3-12 Bridge TrafÞc View buttons 3-7 Bridge View 2-2, 2-3

access levels 3-3

changing front panel information 3-12

launching 3-2 bridging type 3-14

transparent-only 3-14

change the Dynamic Ageing Time 3-25 Changing Polling Intervals 3-43 changing the Circuit ID 4-8 changing the Line Code 4-8 Charts, Graphs, and Meters 1-3 CIR (Committed Information Rate) 4-23 Circuit ID 4-7 clear network logs 3-42 Clock Source 4-7 Committed Burst 4-23 Community Names 1-3 Compression 4-11 ConÞguration BPDU 3-30, 3-31 ConÞguring the Circuits 4-24 ConÞguring the Frame Relay Protocol 4-20 conÞguring the interfaces on the

WAN port 4-9 ConÞguring the Synchronous Port 4-6 ConÞguring the T1 Port 4-8 ConÞguring the WAN Interfaces 4-11 Conn# 4-9 Contact Status 3-5 Create 4-23 CSX Bridge View 2-2, 2-3 CSX Þrmware versions 1-7 CSX200 family and CSX400, descriptions 1-1 CSX400, description 1-1 Cts Enable 4-5 Current box 3-40

decLb100 3-29 Delay box 3-40 DelayExceedDiscard 3-14 deleteOnReset entry status 3-24, 3-27 deleteOnTimeout entry status 3-24, 3-27 Delta button 3-8, 3-9 Designated Bridge 3-28, 3-34 Designated Cost 3-34 Designated Port 3-28, 3-34 Designated Root 3-29, 3-34

Index-1

Index

Destination Port 3-23 Destination Ports 3-23 Detail View 3-9

Change Menu 3-11

port summary information 3-11 Detail View bridge port info 3-11 Device button

bridge 3-6 Device Info 3-44 Device Location 3-5 Device menu

bridge 3-6 Device Name 3-5 disable a bridge network 3-44 disable the Forwarding Log 3-43 DLCI 4-22 Dsr Enable 4-6 Duplicate Segment 3-38 Dynamic Ageing Time 3-20, 3-25

Error Threshold 4-20 ExcessBurst 4-23 Execute Program 3-40

FCS Size 4-16 Filtering Database 3-2

accessing 3-21 Þlters

viewing 3-19 Þrmware version

bridge 3-6 Þrmware versions 1-7 Forward 3-8 Forward Delay 3-8, 3-25, 3-30 Forward Transitions 3-34 forwarding entry 3-20 Forwarding Log 3-41 Forwarding state 3-20 Forwarding Threshold Log window

accessing 3-41 Forwarding Thresholds window

accessing 3-38 Frame Relay Circuit 4-28 Frame Relay Circuit Counters 4-28

DLCI 4-28

RcvBECN 4-28

RcvFECN 4-28

RcvFrame 4-29 RcvOctets 4-29 XmtFrame 4-29

XmtOctets 4-29 Frame Relay Circuit Counters window 4-28 Frame Relay Circuit Table 4-22 Frame Relay ConÞguration window 4-19 Frame Relay DCLMI Last Error 4-27

Data 4-28

Time 4-27

Type 4-27 Frame Relay DCLMI Last Error window 4-27 Frame Relay Dlcmi Errors 4-27 Frame Type Breakdown button 3-37 Frames button 3-8 Framing Type 4-7 Frms In 3-8 Frms Out 3-8 Front Panel 3-4 Full Enquiry Interval 4-20

Global Community Names 1-3 Global Find MAC Address 1-3 Global TFTP 1-3

Hello Time 3-30 Hold Time 3-31 Hop Count Exceeded 3-38 hostname 3-3 HSIM-W6, description 1-2 HSIM-W84 1-2 HSIM-W84, WPIMs 2-4

If# 4-10 IfIndex 3-14 In Speed 4-5 Info button

bridge 3-6 Initial MRU 4-15, 4-16 InÑOutÑIn box 3-40 Interfaces button 4-9 invalid entry status 3-23 IP Address 3-6

Index-2

Index

LAN Segment In/Out 3-38 LastChange 4-23 LCP 4-12 LCP ConÞguration Table 4-14

FCS Size 4-16 If# 4-14 Initial MRU 4-15

Magic Num. Neg. 4-15 Learned Entry Discards 3-22 learned entry status 3-23 Line Build Out 4-7 Line Code 4-7 Line Coding 4-10 Line Status 4-5, 4-7

In Alarm 4-5, 4-7

Inactive 4-5, 4-7

OK 4-5, 4-7 Link Control Protocol 4-12 Local -> Remote Compression 4-14 Local LanID 4-18 Local Media 4-18 Local MRU 4-13 LocalÐ>Remote Cmprs 4-14 log Þles

saving 3-43

MAC Address 3-6 Magic Num. Neg. 4-15 Magic Number Neg. 4-16 management entry status 3-23 Max Age 3-30 Max Virtual Circuits 4-20 maximum log entries 3-42 maximum transfer unit 3-14 menu

Bridge Port 3-5

Device 3-4 Meters tool

accessing 3-35 MIB I, II 1-3 MIBTree 1-3 Monitored Events 4-20 MTU 4-10 MtuExceedDiscard 3-14 Multicast Type 4-20

NCP 4-12 Network Control Protocols 4-12 No Match Process 3-16 notiÞcation conditions 3-39 notiÞcation options 3-39 Number of Topology Changes 3-30

Offset 3-17 Once only 3-41 open the Filtering Database window 3-21 OperStatus 4-18 other entry status 3-23 Out Speed 4-5

Path Cost 3-33 Percentage button 3-8, 3-9 permanent entry status 3-24, 3-27 Pie Chart tool

accessing 3-35 Polling Interval 4-20 polling interval

editing 3-44 Port

Changing Path Cost 3-34

Changing Priority 3-34

Designated 3-34

Designated Cost 3-34

Path Cost 3-33 Port Type 4-5 Port#(Type) 4-9 PortCircuit 3-14 PPP 4-12 PPP Bridge Network Control Protocol

ConÞguration window 4-17 Ppp Lcp Errors 4-25 PPP Link Control Protocol ConÞguration

window 4-13 PPP Link Control Protocol Errors 4-25

Bad Addr 4-26 Bad Controls 4-26 Frame Check Errors 4-26 Packet Too Long 4-26

PPP Link Control Protocol Errors

window 4-26 Priority 3-30 Priority (Port) 3-33

Index-3

Index

Protocol 4-10

Quit button

bridge 3-7

Receive Port 3-23 Redundancy 2-4 RemainÑIn box 3-40 Remote -> Local Compression 4-14 Remote LanID 4-18 Remote Media 4-18 Remote MRU 4-14 RMON 1-3, 2-3 Root

Cost 3-31 Forward Delay 3-31 Hello Time 3-32 Max Age 3-31 Port 3-31

Root Bridge

selection process 3-28 Root bridge 3-28 Router ConÞguration 2-2, 2-3 Rx FCS Size 4-14

Segment Mismatch 3-38 self entry status 3-23 Send Mail 3-40 set bridge port thresholds 3-39 Source Address 3-23 Spanning Tree Algorithm (STA) 3-2, 3-28

version 3-29 Spanning Tree Explorer (STE) Frames 3-37 Spanning Tree Port Table 3-33

accessing 3-32 Spanning Tree Port Table button 3-32 Spanning Tree Protocol window 3-28

accessing 3-28 Spec Frames 3-37 Special Database 3-15 Special Database All Filters Window 3-19 Special Database window

accessing 3-15 special Þltering database 3-18 spmarun script 3-3

SR Frame types 3-37 State 4-19, 4-23 static entry 3-20 Statistics

Source Routing Frame Type 3-37

Synchronous Port Errors 4-30

Aborted 4-31 FCS Err 4-31 Interrupted 4-31 Receive Underrun 4-31 RsPort# 4-31

Transmit Underrun 4-31 Synchronous Port Errors window 4-30 Synchronous Port Signals 4-31

Changes 4-32

RSPort# 4-32

SigName 4-32

State 4-32 Synchronous Port Signals window 4-32

T1 Port ConÞguration 4-6 technical support 1-6 Telnet 1-3 TFTP Download 1-3 The Polling Intervals window 3-43 Topology Change ßag 3-30 Total Filters 3-16 Total Frames Filtered 3-38 Total Frames Transmitted 3-38 Trap Table 1-3 Tx FCS Size 4-14

Uptime 3-5 Using the Fractional Table 4-8 Utilities 1-3

WAN ConÞguration 2-2, 2-3 WAN Connection 4-4 WAN Interface Protocol ConÞguration

window 4-10 WAN Redundancy 2-4 WAN statistics windows 4-25 wancon 4-2 WanIf# 4-9 WPIM-DDS 2-4

Index-4

Cabletron Systems CSX400 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Title Page

Notice

Contents

Introduction to SPMA for the CSX200 and CSX400

HSIM-W6 and HSIM-W84

Using the CSX200 and CSX400 User’s Guide

What’s NOT in the CSX User’s Guide . . .

Conventions

Screen Displays

Using the Mouse

Getting Help

CSX200 and CSX400 Firmware

Year 2000 Compliance

About the CSX200 Series

Applications

About the CSX400

Applications

WAN Redundancy

CSX WPIMs

CSX Bridge View

Bridging Basics

About T ransparent Bridging

The Bridge Port Display

Using the Detail View Window

Changing Ports in the Detail View

The Bridge Status Window

The Bridge Statistics Window

The Special Database Window

Changing a Special Database Filter

Viewing the Filter List

Hex Values for Destination Ports

Deleting Special Database Filters

The Filtering Database Window

Viewing the Filtering Database

Changing Forwarding and Static Database Entries

Deleting a Static Table Entry

Finding a Filtering Database MAC Address

The Spanning Tree Protocol Window

Changing Spanning Tree Parameters

The Spanning Tree Port Parameters Window

Changing a Port’s STA Parameters

The Bridge Port Forwarding Statistics Window

Port Forwarding Statistics Window Fields

Viewing Source Routing Frame Type Statistics

Viewing the Forwarding Log

Changing Polling Intervals

Enabling and Disabling Ports

Enabling and Disabling a Transparent Bridge Port

Using the Fractional Table

PPP Link Control Protocol Status Fields

Viewing the PPP Bridge Network Control Protocol

Adding Circuits

Checking Statistics

PPP Link Control Protocol Errors

Frame Relay DLCMI Last Error

Frame Relay Circuit Counters

Creating Meters

Synchronous Port Errors

Synchronous Port Signals

Index