Cabletron Systems FRX6000, FRX4000, 1800 User Manual 2

Title Page

®

Portable Management Application

for the

FRX4000, FRX6000, and SmartSwitch 1800

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.

Copyright © 1998 by Cabletron Systems, Inc. All rights reserved.

Printed in the United States of America.

Order Number: 9032412-E2 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.

i

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.

(c) Notwithstanding the foregoing, if this computer software is published copyrighted 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.

ii

Chapter 1 Introduction to SPMA

for the FRX4000, FRX6000,
and SmartSwitch 1800

Using this Guide............................................................................................................ 1-2

WhatÕs NOT in the FRX UserÕs Guide . . ........................................................... 1-4

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

Screen Displays ......................................................................................................1-5

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

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

FRX4000, FRX6000, and SmartSwitch 1800 Firmware............................................. 1-8

Year 2000 Compliance ........................................................................................... 1-8

Contents

Chapter 2 Using the FRX4000, FRX6000, and SmartSwitch 1800

Hub View

Using the Hub View ..................................................................................................... 2-1

Navigating Through the Hub View ....................................................................2-2

Port and Module Color Codes...................................................................... 2-4

Using the Mouse in a Hub View Module.................................................... 2-6

The Hub View Front Panel ................................................................................... 2-7

Monitoring Hub Performance................................................................................... 2-10

Selecting a Port Display Form............................................................................ 2-12

Viewing Device Information.............................................................................. 2-16

ConÞguring RLP Protocols................................................................................. 2-16

ConÞguring Serial Port Protocols...................................................................... 2-19

Viewing Serial Port Information........................................................................ 2-20

Serial Port Pin Status.................................................................................... 2-21

Viewing LAN Port Information......................................................................... 2-23

Viewing Statistics................................................................................................. 2-24

RLP Health..................................................................................................... 2-24

Serial Port Health.......................................................................................... 2-26

LAN Card Health .........................................................................................2-27

Viewing Statistics Thresholds ............................................................................2-29

RLP Statistics Thresholds ............................................................................2-29

Serial Port Statistics Thresholds ................................................................. 2-30

Managing the Hub...................................................................................................... 2-32

Setting the Polling Intervals ............................................................................... 2-32

Enabling and Disabling Serial Ports.................................................................. 2-34

Applying Port-level Changes............................................................................. 2-34

iii

Contents

Chapter 3 Configuring the Trap Table

About Traps.................................................................................................................... 3-1

Launching the Trap Table............................................................................................. 3-1

ConÞguring Traps .........................................................................................................3-3

Trap Messages................................................................................................................ 3-4

Chapter 4 Configuring the Subscriber Table

About Subscriber IDs.................................................................................................... 4-1

Accessing the Subscriber Table ................................................................................... 4-2

ConÞguring the Subscriber Table ............................................................................... 4-3

ConÞguring Routing Table Entries...................................................................... 4-5

ConÞguring Address Table Entries .....................................................................4-6

Adding or Modifying Subscriber Table Entries ........................................................4-6

Deleting Table Entries............................................................................................4-8

Chapter 5 Frame Relay Status and Configuration

ConÞguring Frame Relay Ports................................................................................... 5-2

Port ConÞguration ................................................................................................. 5-2

Changing ConÞguration Values ...................................................................5-8

Applying Port-level Changes........................................................................ 5-8

DLCI Rate ConÞguration...................................................................................... 5-8

Changing DLCI Rate Values........................................................................ 5-11

Applying Port-level Changes...................................................................... 5-12

Frame Relay Backup Groups..................................................................................... 5-12

ConÞguring Frame Relay Backup Groups....................................................... 5-13

Changing Backup Group Values ................................................................5-14

ConÞguring Logical Ports.......................................................................................... 5-15

Changing ConÞguration Values ........................................................................ 5-20

Applying Port-level Changes............................................................................. 5-20

Viewing Frame Relay Status...................................................................................... 5-20

Management Stats................................................................................................5-21

Congestion Stats................................................................................................... 5-22

Errors......................................................................................................................5-23

Chapter 6 X.25 Status and Configuration

ConÞguring X.25 Physical Ports .................................................................................6-2

Changing ConÞguration Values .......................................................................... 6-8

Applying Port-level Changes............................................................................... 6-8

Viewing X.25 Status ......................................................................................................6-8

Management Stats..................................................................................................6-8

Congestion Stats..................................................................................................... 6-9

Errors......................................................................................................................6-10

iv

Chapter 7 SNA Status and Configuration

ConÞguring SNA Ports ................................................................................................ 7-2

SDLC Port ConÞguration ..................................................................................... 7-2

Changing ConÞguration Values ...................................................................7-7

Applying Port-level Changes........................................................................ 7-7

SDLC PU ConÞguration .......................................................................................7-7

Changing SDLC PU Subscriber Values ..................................................... 7-10

Applying Port-level Changes...................................................................... 7-10

SDLC PU LLC2 ConÞguration........................................................................... 7-10

Changing SDLC PU LLC2 Values .............................................................. 7-14

Applying Port-level Changes...................................................................... 7-15

SDLC Link Station ConÞguration .....................................................................7-15

Changing SDLC Link Station Values ......................................................... 7-18

Applying Port-level Changes...................................................................... 7-18

ConÞguring LLC2 ....................................................................................................... 7-18

Changing ConÞguration Values .................................................................7-23

ConÞguring LLC2 Host Connections ...............................................................7-24

Changing Host Connections ....................................................................... 7-26

Viewing SDLC Status ................................................................................................. 7-26

SDLC Port Statistics............................................................................................. 7-26

SDLC Link Station General Statistics................................................................ 7-29

SDLC Link Station Rx and Tx Statistics............................................................ 7-30

Contents

Chapter 8 BSC Interactive Configuration

ConÞguring BSCI Ports................................................................................................ 8-1

Changing BSCI Port ConÞguration Values ........................................................ 8-6

Applying Port-level Changes............................................................................... 8-6

BSCI Subscriber ID Information ................................................................................. 8-7

Adding or Modifying BSCI Subscriber Information ........................................8-9

Applying Port-level Changes............................................................................... 8-9

ConÞguring BSCI Devices ...........................................................................................8-9

Adding or Modifying BSCI Device Information............................................. 8-11

Applying Port-level Changes............................................................................. 8-11

Chapter 9 IP Interface Configuration

ConÞguring IP Node Defaults ....................................................................................9-1

ConÞguring IP Interfaces............................................................................................. 9-2

ConÞguring IP Interface Secondary Addresses................................................. 9-9

Adding or Modifying IP Interfaces .......................................................................... 9-11

Adding or Modifying Secondary Addresses................................................... 9-12

v

Contents

Chapter 10 IPX Interface Configuration

ConÞguring IPX Node Defaults................................................................................10-1

ConÞguring IPX Interfaces ........................................................................................10-2

Adding or Modifying IPX Interfaces................................................................. 10-9

ConÞguring IPX Static Routes................................................................................. 10-10

IPX Static SAP ConÞguration...........................................................................10-10

Adding or Modifying Static SAP Routes................................................. 10-11

IPX Static Route ConÞguration........................................................................ 10-12

Adding or Modifying IPX Static Routes.................................................. 10-14

Chapter 11 Bridge Configuration

ConÞguring Device-Level Bridging Parameters .................................................... 11-1

Changing ConÞguration Values ........................................................................ 11-3

ConÞguring Bridge Ports ........................................................................................... 11-4

ConÞguring Frame Relay Bridge Ports............................................................. 11-4

Adding or Modifying Frame Relay Bridge Ports..................................... 11-7

ConÞguring LAN Bridge Ports.......................................................................... 11-7

Adding or Modifying LAN Bridge Ports .................................................. 11-9

Chapter 12 SmartSwitch 1800

Voice Configuration

ConÞguring System-Level Voice Parameters.......................................................... 12-2

Changing Parameter Values ...............................................................................12-5

Speed Dial ConÞguration...........................................................................................12-5

Adding or Modifying Speed Dial Numbers ....................................................12-7

ConÞguring Voice Ports .............................................................................................12-8

Changing Port ConÞguration Values ..............................................................12-15

Applying Port-level Changes........................................................................... 12-15

ConÞguring Voice Interfaces ...................................................................................12-15

Adding or Modifying Voice Interfaces............................................................ 12-17

Viewing Voice Statistics............................................................................................12-18

Appendix A FRX4000, FRX6000, and SmartSwitch 1800

MIB Components

IETF MIB Support ........................................................................................................A-1

CSI Netlink MIB Support ............................................................................................ A-2

Index

vi

Introduction to SPMA
for the FRX4000, FRX6000,
and SmartSwitch 1800

Chapter 1

Using this Guide; manual con v entions; contacting the Cabletron Systems’ Global Call Center; firmware
versions supported by SPMA

Your SPMA for the FRX4000, FRX6000, and the SmartSwitch 1800 management
module provides management support for the FRX4000 stand-alone frame relay
access device; its larger cousin, the FRX6000 scalable chassis; and the innovative
SmartSwitch 1800 frame relay access device. These devices are high-performance
Frame Relay products that combine the capabilities of a frame relay access device
(FRAD) and a router in one box.

The FRX4000 is designed for smaller branch ofÞces that require high performance
to integrate with larger networks over frame relay at access rates up to T1 and
beyond. It supports up to eight serial interfaces (RS232, V.35, or RS422) and one
LAN (Ethernet or Token Ring) interface, and is available in a variety of models
depending on the combination of LAN interface and serial protocols you need.

The FRX6000 is ideal for data centers and concentration sites because of its
scalable rackmount chassis. Its eight slots can support up to two LAN interface
cards and 48 serial interfaces, or as many as 56 (with a single LAN interface) or 64
(with no LAN interface) serial interfaces. Up to eight ports can operate at T1
speeds, and as many as six can operate at E1 speeds. Expansion cards are
available for Ethernet or Token Ring LAN support, and for RS232, V.35, or RS422
serial interfaces; a wide variety of protocol support is also provided.

The SmartSwitch 1800 is a high performance, multiprotocol frame relay access
device that provides multimedia support by adding voice technology to
traditional data applications. Designed for branch ofÞces, it supports four serial
interfaces for WAN and local connectivity (RS232, V.35, or RS422), two analog
RJ45 voice channels, and one LAN (Ethernet or Token Ring) interface.

1-1

Introduction to SPMA for the FRX4000, FRX6000, and SmartSwitch 1800

The protocol support functions which are available via your SPMA application will vary

NOTE

NOTE

depending on the protocol support you have purchased for your FRX or SmartSwitch
1800 device and the version of Þrmware you are running. For more information about
available protocols and the current availability of SPMA support for those protocols,
contact Cabletron SystemsÕ Global Call Center.

Note that because the FRX4000 and FRX6000 provide virtually the same
functionality, they will be referred to collectively throughout this manual as the
FRX. Where signiÞcant differences exist, they will be noted.

SPMA support for the FRX4000, FRX6000 and SmartSwitch 1800 can also be used to
manage new Frame Relay Modules for the SmartSwitch 9000 that are based on FRX
technology: the 9W410 (Ethernet) and the 9W450 (Token Ring). Please note, however,
that at the time of this SPMA release these Frame Relay modules were not yet available;
therefore, this software has not been tested against them, and supplied functionality will
be limited. Full SmartSwitch 9000 Frame Relay Module support will be included in a
future release of SPMA.

Using this Guide

Your SPECTRUM Portable Management Application (SPMA) for the FRX4000,
FRX6000, and SmartSwitch 1800 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); in addition, several applications can
also be accessed from within the Hub View, a graphical display of the device and
its installed interfaces.

This UserÕs Guide describes how to use most of the applications included with the
module; note that the instructions provided in this guide apply to the FRX or
SmartSwitch 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.

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, Token Ring, Frame Relay, and X.25 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, Using the Hub View , describes the visual display of each device

and explains how to use the mouse within the Hub View; some basic functions
(changing the Hub View display, opening menus and windows, enabling and

1-2 Using this Guide

TIP

Introduction to SPMA for the FRX4000, FRX6000, and SmartSwitch 1800

disabling serial ports, and so on) available only from within the Hub View are
also described. You can access the Hub View application from the icon menu
or the command line.

¥ Chapter 3, Trap Table , describes how to conÞgure the deviceÕs trap table,

which controls which management stations will receive traps from a selected
device. The Trap Table application is accessible from the Hub View.

Since these devicesÕ trap tables contain some additional functionality not found in other
Cabletron devices, its operation is described here. Note that the Trap Table chapter
included in the SPMA Tools Guide does not apply to these devices.

¥ Chapter 4, ConÞguring the Subscriber Table , describes how to add, modify,

and delete entries in the subscriber table, which controls the operation of
virtual circuits across the frame relay network. You can access the Subscriber
Table application from the Hub View.

¥ Chapter 5,

Frame Relay Status and ConÞguration , describes how to conÞgure

serial ports set to operate using the frame relay protocol (including DLCI
conÞguration); it also describes how to conÞgure logical ports and frame relay
backup groups. Frame relay-speciÞc management, congestion, and error
statistics are also described. Frame relay status and conÞguration options are
available from the Hub View.

¥ Chapter 6, X.25 Status and ConÞguration , describes how to conÞgure serial

ports for X.25 protocol support and provides detailed information about
management, congestion, and error statistics available on the ports. X.25 status
and conÞguration options are available from the Hub View.

¥ Chapter 7, SNA Status and ConÞguration , describes how to conÞgure SNA

ports and provides physical unit and link station parameters. SDLC-speciÞc
port and general statistics are also provided. SNA status and conÞguration
options are available from the Hub View.

¥ Chapter 8, BSC Interactive ConÞguration , describes how to conÞgure binary

synchronous communications (BSC) Interactive ports and provides BSCI
Subscriber and Device information. BSCI conÞguration options are available
from the Hub View.

¥ Chapter 9, IP Interface ConÞguration , describes how to conÞgure an IP

Interface to allow the Internet Protocol (IP) to be executed over a frame relay,
X.25, or LAN interface. IP Interface options are available from the Hub View.

¥ Chapter 10, IPX Interface ConÞguration , describes how to conÞgure an IPX

Interface to allow connections to Novell IPX networks. IPX Interface options
are available from the Hub View.

¥ Chapter 11, Bridge ConÞguration , describes how to set up a bridge interface

and provides detailed information on conÞguring device-level bridging
parameters. It also describes how to conÞgure frame relay and LAN bridge
ports. Bridging conÞguration options are available from the Hub View.

Using this Guide 1-3

Introduction to SPMA for the FRX4000, FRX6000, and SmartSwitch 1800

¥ Chapter 12, SmartSwitch 1800 Voice ConÞguration , describes how to

conÞgure the two voice ports on the SmartSwitch 1800 and provides statistical
information about voice trafÞc being transmitted across those ports.

¥ Appendix A, FRX4000, FRX6000, and SmartSwitch 1800 MIB Components ,

lists the IETF and proprietary MIBs supported by these devices.

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

The following standard SPMA tools are available through the FRX4000, FRX6000
and SmartSwitch 1800 modules and are explained in the SPECTRUM Portable

Management Application Tools Guide :

¥ Charts and Meters

¥ MIB I, II

¥ MIBTree

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

Charts, Graphs, and Meters are accessible from the Hub View and 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 MIB I, II is available
from the icon menu, the Hub View, or the command line.

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

and Using SPECTRUM for... guide. If you are using SPMA for the FRX or

SmartSwitch 1800 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 in each chapter of this guide and the SPMA Tools
Guide.

Conventions

SPECTRUM Portable Management Applications Ñ including the FRX and
SmartSwitch 1800 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.

Installing

1-4 Conventions

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 resized; those windows will
display the standard window resizing handles employed by your windowing
system. Resizing a window doesnÕt resize 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.

Introduction to SPMA for the FRX4000, FRX6000, and SmartSwitch 1800

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

Click here to
display footer
message history

Figure 1-1. Window Conventions

Some windows will also contain a button; selecting this button
launches a History window (Figure 1-2) which lists all footer messages that have
been displayed since the window was Þrst invoked. This window can help you
keep track of management actions you have taken since launching a management
application.

Conventions 1-5

Introduction to SPMA for the FRX4000, FRX6000, and SmartSwitch 1800

The FRX Hub View application currently prints few footer messages (most of which relate

TIP

to loss of contact with the device), so little information will typically be recorded in the
History window; future releases will expand this feature.

Using the Mouse

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

Figure 1-2. The History Window

Button 1

Button 2

Button 3

Figure 1-3. Mouse Buttons

1-6 Conventions

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

Introduction to SPMA for the FRX4000, FRX6000, and SmartSwitch 1800

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:

¥ 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 [phone].

By mail: Cabletron Systems, Inc.

PO Box 5005
Rochester, NH 03866-5005

By Internet mail: [e-mail]

FTP: ftp.ctron.com (134.141.197.25)

Login anonymous
Password your email address

By BBS: [phone]

Getting Help 1-7

Introduction to SPMA for the FRX4000, FRX6000, and SmartSwitch 1800

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.

FRX4000, FRX6000, and SmartSwitch 1800 Firmware

SPMA for the FRX4000, FRX6000, and the SmartSwitch 1800 has been beta-tested
against released Þrmware version 4.0 only; if you have a different version of
Þrmware and experience problems running SPMA, contact Cabletron SystemsÕ
Global Call Center for upgrade information.

This SPMA operates with FRX and SmartSwitch 1800 Þrmware versions 3.3 or
greater. However, due to SNMP limitations in Þrmware versions prior to 4.0, it is
recommended that this SPMA be used in conjunction with Þrmware 4.0 or
greater.

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.

SPMA support for the FRX4000, FRX6000 and SmartSwitch 1800 can also be used to

NOTE

manage new Frame Relay Modules for the SmartSwitch 9000 that are based on FRX
technology: the 9W410 (Ethernet) and the 9W450 (Token Ring). Please note, however,
that at the time of this SPMA release these Frame Relay modules were not yet available;
therefore, this software has not been tested against them, and supplied functionality will
be limited. Full SmartSwitch 9000 Frame Relay Module support will be included in a
future release of SPMA.

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
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 FRX4000, FRX6000, and SmartSwitch 1800 Firmware

Chapter 2

Using the FRX4000, FRX6000, and
SmartSwitch 1800 Hub View

Navigating through the Hub View; monitoring hub performance; managing the hub

The heart of the SPECTRUM Portable Management Application (SPMA) for the
FRX4000, FRX6000, and SmartSwitch 1800 is the Hub View, a graphical interface
that gives you access to many of the functions that provide control over the
selected FRX or SmartSwitch device and its installed interfaces.

Using the Hub View

There are two ways to launch the Hub View application: if you are working
within a network management system, you can select the Hub View option from
the icon menu; speciÞc directions for creating an FRX or SmartSwitch icon and
accessing the icon menu can be found in the appropriate Installing and Using...
guide. If you are running the module in a stand-alone mode, type the following at
the command line:

spmarun frx <IP address> <community name>

The community name you use to start the module must have at least Read access;
for full management functionality, you should use a community name that
provides Read/Write access. For more information on community names, consult
the appropriate hardware documentation.

2-1

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

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
an application from the icon menu or from within the Hub View.

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

Note that the community name required to launch the Hub View application (or add the
device to your management application or the stand-alone launcher database) is the same
as the Node Community Name you must assign when you Þrst conÞgure your device via
console management.

Navigating Through the Hub View

Within the Hub View, you can click mouse buttons in different areas of the
window to access various menus and initiate certain management tasks. The
following diagrams illustrate the information provided in the Hub View and
show you how to use the mouse to display the available menus.

Note that the Hub View display (Figure 2-1, page 2-3) for each device type mimics
that deviceÕs physical appearance: the FRX4000 and the SmartSwitch 1800 are
displayed horizontally, and each contains two ÒmoduleÓ slots (one for the LAN
interface, and one for the RLP card); the FRX6000 is displayed vertically, and
contains eight slots. The type of card (RLP or LAN) installed in each slot, along
with its index number, is indicated by the module title box.

For the FRX4000 and the SmartSwitch 1800, whose conÞgurations are Þxed, slot 1
will always contain the RLP card; slot 2, the selected LAN interface. Since thereÕs
only one of each, each will be indexed 0.

For the FRX6000, RLP indexing is determined by a switch setting on the card
itself; RLPs will be displayed in the Hub View in index order, regardless of their
actual physical placement in the chassis. LAN cards will also be displayed in
index order, after all conÞgured RLPs (again, regardless of actual physical
placement in the chassis).

2-2 Using the Hub View

Module Status

LIC Name

Port Status

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

FRX6000

FRX4000 or SmartSwitch 1800

Figure 2-1. The FRX4000, FRX6000 and the SmartSwitch 1800 Hub Views

LAN card indexing is determined simply by the order in which the installed LAN cards

NOTE

are identiÞed during the initial FRX6000 Þrmware installation. During the Þrmware
installation, you will be prompted to enter the number of LAN cards you have installed,
then prompted to supply their type. The order in which you enter the type information
determines the indexing.

If you have two cards of the same type, you will need to distinguish them by physical
address, as there is no way to control which index is assigned to which card. The physical
address is displayed in the LAN Port Information window, described on page 2-23.

Each module display contains individual port boxes that can display a variety of
information about each port (see Selecting a Port Display Form, page 2-12). For
an RLP, up to eight serial ports can be present (four on each of two possible Line
Interface Cards, or LICs); for a LAN card, only a single port interface is provided.
For the FRX4000 and the SmartSwitch 1800, the Base LIC and Exp (Expansion)
LIC correspond to LIC 1 and LIC 2 on each FRX6000 RLP card.

Using the Hub View 2-3

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

RLP information will only be displayed if the appropriate database record has
been conÞgured via console management (see your hardware documentation for
more information); for RLPs which have been conÞgured in the database but not
yet installed in the chassis, a blue module status will be displayed (see Port and
Module Color Codes, below). RLPs which are present in the chassis but which
have not been conÞgured in the database will not be displayed.

For each conÞgured RLP card, eight serial port status boxes will be displayed
(four for each of two possible LIC cards); however, serial port status information
will only be displayed for ports which are physically present (on an installed LIC
card) and have been conÞgured in the database. Ports which are present but not
conÞgured will display a blank status; if no LIC is present, the value [None] will
be displayed under the appropriate LIC title, and the associated ports will also
display a blank status.

LAN cards will only be displayed when they are both present and conÞgured, as
they are conÞgured during the initial Þrmware installation process, and cannot be
conÞgured unless they are present.

Port and Module Color Codes

Module Index boxes

Port Status
boxes

Both the module index boxes and the port status boxes are color-coded to indicate
status (see Figure 2-2, below).

Figure 2-2. Module and Port Color Codes

2-4 Using the Hub View

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

The module status color code indicates one of two conditions: if a module is both
present in the chassis and conÞgured in the database, its index box will be
color-coded green; if a module has been conÞgured in the database but is not
physically present in the chassis, its index box will be color-coded blue. Modules
which are physically present but not yet conÞgured in the database are not
displayed at all in the Hub View. (For LAN cards, the module status will always
display as green, since they cannot be conÞgured if they are not present.)

The color coding for both serial and LAN ports is based on a combination of
MIB II ifAdminStatus and ifOperStatus, as follows:

Green indicates that both ifAdminStatus and ifOperStatus are

UP.

Blue indicates that both ifAdminStatus and ifOperStatus are

DOWN.

Red indicates that there is a mismatch in states: one state is

UP, and the other is DOWN.

Magenta indicates that the ifOperStatus is testing, or that the

ifOperStatus is DOWN and the ifAdminStatus is testing.

Gray indicates that the device has returned a value for

ifOperStatus which was not understood by SPMA.

Blank indicates that no response was received from the port.

Ports which are not present, or present but not
conÞgured in the database, will also display a blank
status.

Using the Hub View 2-5

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

Using the Mouse in a Hub View Module

For each RLP and LAN card displayed in the Hub View (that is, those which are
at least conÞgured in the database), you can use the mouse to access various
module- and port-level menus and functions, as illustrated below.

When a LIC card is installed, the
current Port Display F orm selection is
shown here; a value of [None]
indicates that no LIC is present

Figure 2-3. Mousing Around a Module Display

2-6 Using the Hub View

The Hub View Front Panel

In addition to the graphical display of the RLP and LAN cards installed in your
device and/or conÞgured in its database, the Hub View gives you device level
summary information. The following Front Panel information appears to the right
of the module display (for the FRX6000) or below the module display (for the
FRX4000 and the SmartSwitch 1800):

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 is unable to contact or has lost contact with the device.

Uptime

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

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

NOTE

¥ Power to the device is cycled.

¥ The device is reset manually.

Name

A text Þeld that you can use to help identify the device; you can assign a device
name via the MIB I, II application (described in the SPMA Tools Guide). To view a
name which is longer than the Þeld, click to place your cursor in the text box, and
use the arrow keys to shift the display.

Location

A text Þeld that you can use to help identify the device; you can assign a device
location via the MIB I, II application (described in the SPMA Tools Guide). To
view a location which is longer than the Þeld, click to place your cursor in the text
box, and use the arrow keys to shift the display.

Although you can erase the current Name and Location values and enter new values in
the text Þelds, you cannot set these values from the Hub View. Any value you attempt to
set will remain in the text Þeld only until the Hub View is closed; to permanently change
the name or location, you must do so via the MIB I, II application (accessible from the
Device menu in the Hub View, from the icon menu, or from the command line). Note that
the footer message indicating that the Name or Location Þeld is read-only is in error; these
Þelds are settable, but they cannot be set from the Hub View.

Using the Hub View 2-7

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

IP Address

The deviceÕs Internet Protocol address; this Þeld will display the IP address you
have used to create the device icon (if you are running the Hub View from a
management platform) or the IP address you used to launch the Hub View
program (if you are running in stand-alone mode). You cannot change the IP
address from within SPMA.

For FRX Þrmware versions 3.3.0, 3.3.1, and 4.0, each installed LAN card can be assigned

TIP

an IP address. The IP address you use to communicate with the FRX devices via SNMP is
an IP address which has been assigned to a LAN card interface. For FRX6000s which have
two LAN cards installed, each can be assigned its own IP address, if desired; either of these
IP addresses can be used for SNMP communication.

For FRX6000s which do not have a LAN card installed, an IP address can be assigned to
any Frame Relay port which is also running the IP protocol; in this case, you would use
this IP address to communicate with the device via SNMP and SPMA.

2-8 Using the Hub View

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

Clicking the Device button displays the Device menu, Figure 2-4.

Figure 2-4. Hub View Device Menu

The Device menu lets you perform the following:

¥ Open the Device Information window (described in Viewing Device

Information, page 2-16).

¥ Open the Polling Intervals window (described beginning on page 2-32).

¥ Select a Port Display Form (described beginning on page 2-12).

¥ Launch the generic MIB I, II application (described in the SPMA Tools Guide).

¥ Open the Trap Table window (described in Chapter 3, ConÞguring the Trap

Table).

¥ Open the Subscriber Table window (described in Chapter 4, ConÞguring the

Subscriber Table).

Using the Hub View 2-9

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

¥ Open the Frame Relay Backup Group window (described in Chapter 5, Frame

Relay Status and ConÞguration).

¥ Open the IP, IPX, Bridge, and SNA conÞguration windows (described in

Chapters 7, 9, 10 and 11).

¥ Open the Voice ConÞguration windows (described in Chapter 12, Voice

ConÞguration).

Note that the Device menu does not provide access to all of the applications
which are available to the devices; additional applications are available from the
Module and Port menus in the Hub View, and some can only be accessed from the
icon menu (if you are running under a network management platform) and from
the command line (if you are running in stand-alone mode). See Chapter 1,
Introduction to SPMA for the FRX4000, FRX6000, and SmartSwitch 1800, for a
complete list of applications available to the devices and how to access each one.

Your Device Menu may not display all of the options listed here. Only those protocols and

NOTE

interface types for which your node has been conÞgured will be listed on the menu.

Only the SmartSwitch 1800 will display the Voice ConÞguration options.

Clicking mouse button 1 on the Quit button closes all Hub View application
windows; any open applications which can also be accessed from the command
line or from the icon menu will remain open.

Monitoring Hub Performance

The information displayed in the Hub View can give you a quick summary of
device activity, status, and conÞguration. SPMA can also provide further details
about hub performance via its three-level menu structure. The Device, Module,
and Port menus (Figure 2-5, below) give you control over the hub at three levels
and give you access to the tools, menus, and windows that let you monitor
speciÞc aspects of hub performance, change hub display options, and set some
operating and notiÞcation parameters.

2-10 Monitoring Hub Performance

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

Device Menu

LANCard and RLP

Module Menus

Frame Relay, X.25, LAN

and Unconfigured Port Menus

BSCI, Voice, and SDLC

Port Menus

Figure 2-5. The Device, Module, and Port Menus

Monitoring Hub Performance 2-11

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

Hub performance data available through these menus includes:

¥ Device, Module, and Port conÞguration information.

¥ Generic Module and Port health and threshold statistics.

¥ Serial Port pin status.

¥ Protocol-speciÞc Port-level statistics.

The health and protocol statistics are displayed via the SPMA Meters application; for

TIP

more information on how to manipulate meters, see the SPMA Tools Guide.

Selecting a Port Display Form

You can change the type of information displayed for each port in the hub by
using the Port Display Form options available via the Device menu. Changing the
port display form from the Device menu changes the port display for all ports in
the chassis.

To change the port display form:

1. Click on the button to display the Device menu.

2. Drag down to Port Display Form, then to the side as necessary to select one
of the port display options. The current selection will be displayed in the LIC
name box (for RLPs) or the Interface box (for LAN cards; see Figure 2-3,

page 2-6).

Note that the port color coding does not change based on the selected Port
Display Form; see page 2-4 for more information on color codes.

Port display forms are:

Operation Status

The Operation Status port display form indicates the current value of the
ifOperStatus OID:

UP operational status up

DOWN operational status down

TEST operational status testing

UNK unknown; device is returning a value that the software

does not recognize

--- the device is not responding to the request

2-12 Monitoring Hub Performance

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

Admin Status

The Admin Status port display form indicates the current value of the
ifAdminStatus OID:

UP the port has been administratively enabled

DOWN the port has been administratively disabled

TEST the port has been administratively placed in a test mode

UNK unknown; device is returning a value that the software

does not recognize

--- the device is not responding.

Port T ype

The Port Type port display form indicates the type of protocol the selected port
has been conÞgured to run, as deÞned by the OID nlIfType. Possible values for any
one port are limited to the protocols that have been installed on that portÕs RLP
card:

X25 indicates that the port has been conÞgured to run the

X.25 protocol -- either ddnX25 or rfc877x25.

sdlc indicates that the port has been conÞgured to run the

SDLC protocol.

frame indicates that the port has been conÞgured to run the

Frame Relay protocol.

async indicates that the port has been conÞgured to run the

asynchronous protocol.

bsci indicates that the port has been conÞgured to run the

bi-synchronous (two-directional) protocol.

ether (LAN only) indicates that the port is supporting an Ethernet

connection: either ethernetCsmacd, or iso88023Csmacd.

tr (LAN only) indicates that the port is supporting a Token Ring

connection.

voice indicates that the port is supporting a voice connection.

Port State

The Port State display indicates the portÕs readiness (or lack thereof) to establish a
connection and transmit data (as deÞned by the OID nlIfPortStatus):

linkup A physical electrical connection is present and working

(cable is connected at both ends and the two connected
ports are communicating), but some conÞguration
information is missing or there is a line speed or other
mismatch. This state is one step short of operational.

oper (operational) The port is functional and capable of data transmission.

Monitoring Hub Performance 2-13

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

disa (disabled) The port is operationally disabled.

disc (disconnect) One of the two endpoints connected via the port has

closed the connection.

conf (conÞgured) The port has been conÞgured in the database, but the

conÞgured protocol has not been installed on the
associated RLP card.

dial (dialReady) For a frame relay port, this state indicates that the port

has been conÞgured as a backup port, and it is ready to
be switched into use if needed; for an X.25 port, this state
indicates that the port is ready to transmit or receive
calls.

quies (quiesced) A port which has been quiesced will be disabled when all

active calls have been completed. No new calls can be
initiated during this delayed disable state. Once a
quiesced port is disabled, it will remain disabled until it
is enabled by management action.

fail (failed) The port has failed due to a broken cable or other wire

problem, either while moving to the operational state or
after achieving it.

fault (hardware fault) Indicates that the port has failed due to a hardware

problem on the serial port itself.

na Not applicable; this value displays for any LAN ports

installed in the device.

other The port status response received from the device was

not understood by SPMA.

ipl The port is in a booting state (initial program load). This

is a very brief transitional state that is unlikely to be
displayed.

restar (restarting) A very brief transitional state that occurs during boot up;

this state is unlikely to be displayed.

onhook Indicates there is no call in progress and the voice port is

able to accept an incoming call.

offhook Indicates there is a call in progress and the voice port is

not able to accept an incoming call.

dialing Indicates a call is being placed but has not been accepted

yet.

active Indicates a call has been placed and answered.

pending The device at the remote end has been placed onhook

while the call was still in progress.

2-14 Monitoring Hub Performance

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

Connector Type

This port display form indicates the connector type supported by the selected
port. This value (from the OID nlIfConnectorType) is determined by a combination
of cable and physical port type, as follows:

rs232 Indicates an RS232 serial port, which must always use an

RS232 cable.

v35 Indicates a v.35 serial port, which must always use a v.35

cable.

rs449 Indicates an RS422 serial port conÞgured for an RS449

cable.

rs530 Indicates an RS422 serial port conÞgured for an RS530

cable.

x21 Indicates an RS422 serial port conÞgured for an X21

cable.

csudsu (csu/dsu) Indicates a CSU/DSU interface.

none This value displays for LAN ports.

TIP

voice This value displays for voice channels.

Speed

Indicates the speed conÞgured for the selected port, as reported by the MIB II OID
ifSpeed. The speed conÞgured for a port must match the speed of the line which
will be connected to that interface, and the speed conÞgured for the port at the
other end of the connection.

Max Packet Size

Displays the size of largest datagram which can be sent or received on this port, in
octets (as reported by the MIB II OID ifMtu). This value is speciÞc to the protocol
running on the selected interface.

IF Index

Displays the MIB II ifIndex value assigned to each port. Note that the displayed
index values do not necessarily increment as you might expect Ñ as the FRX or
SmartSwitch 1800 device boots, each physical or logical port which is detected will
be incrementally assigned an index value, which may result in gaps between the
index values assigned to the physical ports displayed in the Hub View. Note that
the assigned ifIndex values are constant between bootups; however, once the
device reboots, the same ifIndex values will not necessarily be assigned to the
same physical or logical ports (if the deviceÕs conÞguration has changed).

To map logical ports to their physical port locations, use the OID nlIfPhyPort.

Monitoring Hub Performance 2-15

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

Viewing Device Information

The Device Information window provides some general descriptive information
about the FRX or SmartSwitch 1800 device you are modeling.

To access the window:

1. In the Hub View, click on to display the Device menu.

2. Drag down to Device Information, and release. The Device Information
window, Figure 2-6, will appear.

Figure 2-6. The Device Information Window

Device information includes:

System Description Displays the MIB II sysDescr for the selected device; this

System Contact Displays the MIB II sysContact value; this value is settable

Configuring RLP Protocols

The RLP ConÞguration window provides information about the status of each
displayed RLP and lets you view and conÞgure the protocols loaded onto the
selected RLP.

To access the window:

1. In the Hub View, click on the appropriate Module Index or Module Name text
box to display the RLP Menu (see Figure 2-3, page 2-6).

description typically includes information about the
Þrmware version currently running.

via the generic MIB I, II application (accessible from the
Device menu, the icon menu, or from the command line).
See the SPMA Tools Guide for a detailed description of
the MIB I, II application and how to set this value.

2. Drag down to Configuration, and release. The RLP Configuration window,

Figure 2-7, will appear.

2-16 Monitoring Hub Performance

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

Figure 2-7. The RLP ConÞguration Window and Protocol Menu

RLP status information includes:

Status A status of Installed indicates that the RLP is physically

present in the chassis, and has been conÞgured in the
database; a status of ConÞgured indicates that a database
record has been conÞgured, but the card is not physically
present in the hub.

Memory Displays the amount of memory installed on the selected

RLP, either 4 or 8 megabytes.

Monitoring Hub Performance 2-17

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

You must have 8 megabytes of memory installed on at least one RLP in the FRX to run

NOTE

Þrmware version 4.0. If you have RLPs with only 4 megabytes of memory and want to
upgrade them to 8 megabytes, contact CabletronÕs Global Call Center or your local service
representative for more information.

LIC 1 Type/LIC 2 Type Displays the type value for each Line Interface Card

(LIC) installed on the selected RLP: RS232, HS RS232,
v.35, RS422, Voice or Universal. The Universal LIC is
shipped as the Base LIC on the FRX4000 and the
SmartSwitch 1800. It has four ports: port 0 can be
conÞgured for RS232 operation; port 1 can be conÞgured
for RS232 and CSU/DSU operation; ports 2 and 3 can be
conÞgured for RS232, v.35, RS449, RS530, or x.21
operation (depending on the attached cable type).

Protocols Displays the protocols that have been loaded onto the

selected RLP. On the FRX4000 and SmartSwitch 1800, a
maximum of 11 protocols can be loaded on to RLP0. A
maximum of nine protocols can be loaded on to an FRX
6000 RLP. If less than the maximum number have been
loaded, some of the protocol Þelds will display None.
Only protocols which have been loaded onto the RLP can
be conÞgured to run over that RLPÕs serial ports. You can
change or add protocols for the selected RLP.

On

NOTE

WARNING

For the FRX4000 and the SmartSwitch 1800, the RLP ConÞguration window and
protocol menu will display all the protocols shown in Figure 2-7, but only those protocols
that were purchased will be conÞgurable.

For the FRX6000, all supported protocols will Þt on one 8-megabyte RLP; however, it is
recommended that no more than seven protocols be conÞgured on any one RLP.

The X.25 protocol is always loaded on every RLP; it is a necessary protocol for use by
internal FRX and SmartSwitch 1800 trafÞc and must not be deleted.

Follow these guidelines when conÞguring protocols:

¥ RIP is a valid choice only if IP is already conÞgured on the same RLP.

¥ If SNMP is conÞgured, IP must also be conÞgured. For the FRX6000, SNMP

and IP can be, but do not have to be, on the same RLP.

2-18 Monitoring Hub Performance

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

¥ If LLC2 is conÞgured, Bridge must also be conÞgured. For the FRX6000, both

protocols should be, but do not have to be, on the same RLP. Having them on
the same RLP should provide better performance.

¥ If NVSP is conÞgured, LLC2 and Bridge must also be conÞgured. For the

FRX6000, all three protocols can be, but do not have to be, on the same RLP.

¥ For the FRX6000, IP, SNMP, RIP, IPX, LLC2, NVSP, and Bridge cannot be

conÞgured on more than one RLP each. However, more than one of these can
be on the same RLP. Performance can be enhanced by conÞguring these
protocols on the same RLPs that contain the frame relay ports that will
transport the protocols.

To change or add protocols for the selected RLP:

1. Display the Configuration window f or the selected RLP. Each protocol field will

display either a configured protocol or None.

2. To change a protocol, click on the menu button to display a list of options, then

drag up or down to select the option you want.

3. Click on Apply to save your changes.

Changing the protocols in the RLP ConÞguration window will enable the protocols on

NOTE

that RLP, but to make the protocols actually operational you must reboot the device.

Configuring Serial Port Protocols

The Port ConÞguration window lets you conÞgure a protocol for the selected
port.

To access the window:

1. In the Hub View, click on the appropriate Port Index or Port Status text box to

display the Port Menu (see Figure 2-3, page 2-6).

2. Drag down to Configuration, and release. The Port Configuration window,

Figure 2-9, will appear.

Monitoring Hub Performance 2-19

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

Figure 2-8. The Port ConÞguration Window and Protocol Menu

To change or add a protocol for the selected port:

1. Display the Configuration window for the selected port. It will display either a
configured protocol or None.

2. To change a protocol, click on the menu button to display a list of options, then
drag up or down to select the option you want. The Protocol menu will only list
protocols that are supported on that RLP.

3. Click on Apply to save your changes.

Viewing Serial Port Information

The Port Information windows provide the same descriptive information for all
displayed serial ports, regardless of type. Note that this information is only
available for serial ports which are both conÞgured in the database and physically
present in the chassis.

To access serial port information:

1. In the Hub View, click on the appropriate Port Index or Port Status text box to
display the Port Menu (see Figure 2-3, page 2-6).

2. Drag down to Information, and release. The P ort Info window, Figure 2-9, will
appear.

Figure 2-9. The Serial Port Information Window

2-20 Monitoring Hub Performance

Interface Description: Displays a general description of the selected serial

Note that the index number assigned to the physical port interface is not the same as the

TIP

ifIndex assigned to that same physical interface. The physical port indices begin with 0;
the ifIndex values begin at 1.

Port Type: Displays the type of protocol the selected port has been

Serial Port Pin Status

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

interface (from the MIB II ifDescr), including the index
number assigned to the portÕs RLP; the physical number
assigned to the port interface itself (as designated in the
Port Index box in the Hub View), and a general text
description of the port, including the protocol currently
conÞgured to run over that port.

conÞgured to run, as deÞned by the OID nlIfType. Note
that this is the same information displayed by the Port
Type port display form (described on page 2-13).

NOTE

You can also view the electrical status of each pin on the cables attached to a serial
port; this information can be useful in tracking down connectivity problems,
especially those related to cable failure.

The current version of Þrmware for the SmartSwitch 1800 does not support the Serial
Port Pin Status function on its two voice ports.

To view serial port pin status:

1. In the Hub View, click on the appropriate Port Index or Port Status text box to

display the Port Menu (see Figure 2-3, page 2-6).

2. Drag down to Pin Status, and release. The Pin Status window, Figure 2-10,

will appear.

Monitoring Hub Performance 2-21

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

Figure 2-10. The Pin Status Window

Each cable pin is represented by a colored rectangle labeled with the pin name;
the color-coding tells you whether the pin is active (green; has voltage), inactive
(red; has no voltage), unused (tan, or no color), or its electrical status is unknown
(yellow). Each serial port provides information about the following pins:

TD (transmit data) Pin will be active when the connection is operational.

RD (receive data) Pin will be active when the connection is operational.

RTS (request to send) For some protocols, the pin will become active when the

device wishes to send some data, and become inactive
once the data is sent; for a point-to-point protocol,
however, the pin will always be active.

CTS (clear to send) The receiving device has responded to a request to send.

DSR (data set ready) When active, indicates that the remote data

communications equipment (DCE) has signalled that is it
ready.

CD (carrier detect) When active, indicates that the connected line is

operational (that is, a dial tone or similar indication is
present).

TC (transmit clocking) When active, indicates that clocking is occurring on the

link.

RC (receive clocking) When active, indicates that clocking is occurring on the

link.

DTR (data terminal When active, indicates that the data terminal equipment
ready) (DTE) is ready.

TTA (transmit timing) When active, indicates that timing frames are being

transmitted.

2-22 Monitoring Hub Performance

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

The pin names which end in ÒBÓ Ñ TDB, RDB, CTSB, DCDB, TCB, RCB, TTB, RTSB,

NOTE

and DSRB Ñ have the same deÞnitions as those listed above, but for the B channel signals
used by V.35 and RS449 interfaces.

Viewing LAN Port Information

The LAN Port Information windows also provide general descriptive information
about the selected port. To access LAN port information:

1. In the Hub View, click on the appropriate Port Index or Port Status text box to

display the Port Menu (see Figure 2-3, page 2-6).

2. Drag down to Information, and release. The Port Info window, Figure 2-11,

will appear.

Note that the Ethernet
and Token Ring port
information windows
contain different
address information

Figure 2-11. LAN Port Information Windows

The windows display the following information:

Interface Description: Displays a general description of the selected LAN

interface (from the MIB II ifDescr), including the index
number assigned to the portÕs LAN card (0 or 1), and a
general text description of the port (802.5 or Ethernet).

Port Type: Displays the LAN port type: iso88025 Token Ring, or

ethernet CSMACD.

Monitoring Hub Performance 2-23

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

Address: For Token Ring LAN cards, this Þeld displays the locally

administered physical address, if one has been assigned;
if none has been assigned, the Þeld (labeled Local Admin
Address) will displays all zeros. For Ethernet cards, the
factory-set physical address (labeled Physical Address)
will be displayed.

For an FRX6000 with two LAN cards of the same type, note that the only way to

TIP

distinguish between the two cards is via the physical address displayed here (since
indexing is unrelated to physical position in the chassis).

Viewing Statistics

The Hub View can provide a variety of statistics at the RLP, serial port, and LAN
card levels that give you an overview of the general health of your network
connections. These statistics are described in the following sections.

The statistics windows provided via the Hub View display data using the SPMA Meters

TIP

application; for more information on how to manipulate the meter display and change
meter settings, see the SPMA Tools Guide.

RLP Health

To access RLP Health statistics:

1. In the Hub View, click on the appropriate Module Index or Module Name text
box to display the RLP Menu (see Figure 2-3, page 2-6).

2. Drag down to Health, and release. The RLP Health Statistics window,

Figure 2-12, will appear.

2-24 Monitoring Hub Performance

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

Figure 2-12. The RLP Health Statistics Window

RLP Health statistics provide the following general usage information for all
ports on the selected card:

Frames Received The total number of frames received on all active serial

ports on the selected RLP, expressed as a rate
(frames/second).

Frames Transmitted The total number of frames transmitted by all active

serial ports on the selected RLP, expressed as a rate
(frames/second).

Frames Rejected The total number of frames rejected by all active serial

ports on the selected RLP, expressed as a rate
(frames/second). Each protocol handles rejected frames a
little differently; in general, however, frames are rejected
because the active protocol has detected an error in the
frame itself.

Frames Retransmitted The total number of frames retransmitted by all active

serial ports on the selected RLP, expressed as a rate
(frames/second). Frames are typically retransmitted to
correct errors or if the receiving device was too busy to
receive the original frames; a high retransmit rate can
indicate a noisy transmission line. If this value is
consistently above zero and there are no other problems,
you may want to increase the value assigned to the
Retransmission Timer in the port database record. (See
your hardware documentation for more information.)

Monitoring Hub Performance 2-25

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

Frames Queued The total number of frames from all active serial ports on

the selected RLP currently queued and waiting for
transmission, expressed as a raw value. Queued frames
will be transmitted as soon as device resources permit.

Used Buffers Displays the percentage of available buffers currently

being used by queued frames.

Serial Port Health

To access Serial Port Health statistics:

1. In the Hub View, click on the appropriate Port Index or Port Status text box to
display the Port Menu (see Figure 2-3, page 2-6).

2. Drag down to Health, and release. The Port Health Statistics window,

Figure 2-13, will appear.

Figure 2-13. The Port Health Statistics Window

The Serial Port Health Statistics windows display the same statistics for each
conÞgured serial port, regardless of type:

Frames Received The total number of frames received on the selected

serial port, expressed as a rate (frames/second).

Frames Transmitted The total number of frames transmitted on the selected

serial port, expressed as a rate (frames/second).

Frames Retransmitted The total number of frames retransmitted on the selected

serial port, expressed as a rate (frames/second). Frames
are typically retransmitted to correct errors or if the
receiving device was too busy to receive the original
frames; a high retransmit rate can indicate a noisy
transmission line.

FCS Errors The total number of frames received at the selected serial

port that contained a bad frame check sequence (FCS),
expressed as a rate (errors/second). The frame check

2-26 Monitoring Hub Performance

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

sequence (like the CRC, or cyclic redundancy check) is a
value computed at both the sending and receiving ends
of the connection; if the computed values donÕt match,
the frame is assumed to have been corrupted in transit. A
value consistently greater than zero indicates line
problems.

Logical Rejects The sum of frame rejects Ñ frames which are dropped due

to congestion or some other transmission problem Ñ and
reject frames Ñ protocol frames that notify the sender that
one or more packets is missing from a sequence. The total
is expressed as a rate (rejects/second); a value
consistently greater than zero indicates line problems.

Rx Utilization % The ratio of non-ßag characters (the space between

frames) to the total number of characters received on the
selected serial port; that is, the percentage of available
bandwidth being utilized.

Tx Utilization % The ratio of non-ßag characters (the space between

frames) to the total number of characters transmitted on
the selected serial port; that is, the percentage of available
bandwidth being utilized.

LAN Card Health

The LAN Card Health Statistics window provides standard MIB II stats for the
selected LAN interface; note that the same statistics are provided for both
Ethernet and Token Ring interfaces.

To access LAN Card Health statistics:

1. In the Hub View, click on the appropriate Module Index or Module Name text

box to display the LANCard Menu (see Figure 2-3, page 2-6).

2. Drag down to Health, and release. The LAN Health Statistics window,

Figure 2-14, will appear.

Monitoring Hub Performance 2-27

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

Figure 2-14. The LAN Health Statistics Window

MIB II statistics provided are:

In Octets (ifInOctets) The total number of octets (or bytes) of data

received at the selected LAN interface, expressed as a
rate (octets/second).

In Ucast (ifInUcastPkts) The total number of packets received at

the selected LAN interface that were destined for a single
address (unicast), expressed as a rate (packets/second).

In NUcast (ifInNUcastPkts) The total number of packets received at

the selected LAN interface that were destined for more
than one address (either broadcast or multicast),
expressed as a rate (packets/second).

In Discards (ifInDiscards) The total number of inbound packets which

were discarded even though no errors were detected,
expressed as a rate (packets/second); well-formed
packets are typically discarded in order to free up buffer
space.

In Errors (ifInErrors) The total number of inbound packets which

contained errors that prevented them from being
delivered, expressed as a rate (packets/second).

Out Octets (ifOutOctets) The total number of octets (or bytes) of data

transmitted by the selected LAN interface, expressed as a
rate (octets/second).

2-28 Monitoring Hub Performance

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

Out Ucast (ifOutUcastPkts) The total number of packets transmitted

Out NUcast (ifOutNUcastPkts) The total number of packets

Out Discards (ifOutDiscards) The total number of outbound packets

Out Errors (ifOutErrors) The total number of outbound packets

Viewing Statistics Thresholds

by the selected LAN interface that were destined for a
single address (unicast), expressed as a rate
(packets/second).

transmitted by the selected LAN interface that were
destined for more than one address (either broadcast or
multicast), expressed as a rate (packets/second).

which were discarded even though no errors were
detected, expressed as a rate (packets/second);
well-formed packets are typically discarded in order to
free up buffer space.

which contained errors that prevented them from being
delivered, expressed as a rate (packets/second).

The Hub View provides a way to view trap thresholds that have been set through
console management for RLP and port health statistics. For each RLP and port
statistic, you can specify a threshold that, when crossed, causes a trap to be sent to
a management workstation. A threshold is either a number or a percentage,
depending on the statistic. The valid range for any number threshold is 0 - 65535
with the default value being 0. When the measured value for the health statistic
crosses the threshold (in either direction), a trap is sent to the collecting
management workstation. (For information on designating workstations to accept
traps, see Chapter 3, ConÞguring the Trap Table. For deÞnitions of RLP and
Serial Port Health Statistics, see Viewing Statistics, page 2-24.)

RLP Statistics Thresholds

To view RLP Thresholds:

1. In the Hub View, click on the appropriate Module Index or Module Name text

box to display the RLP Menu (see Figure 2-3, page 2-6).

2. Drag down to Thresholds, and release. The RLP Statistics Thresholds

window, Figure 2-15, will appear.

Monitoring Hub Performance 2-29

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

Figure 2-15. The RLP Statistics Thresholds Window

The RLP Statistics Thresholds window shows the current threshold value (either a
number or a percentage) for the following RLP health statistics (for deÞnitions of
the RLP Health Statistics, see RLP Health, page 2-24):

Percentage of Buffers in Use Shows the threshold for the Used Buffers

Message Queue Length Shows the threshold for the Frames Queued

Received Frames Per Second Shows the threshold for the Frames Received

Transmitted Frames Per Second Shows the threshold for the Frames

Rejected Frames Per Second Shows the threshold for the Frames Rejected

Retransmitted Frames Per Second Shows the threshold for the Frames

Serial Port Statistics Thresholds

To view Serial Port Thresholds:

statistic.

statistic.

Statistic.

Transmitted Statistic.

statistic.

Retransmitted statistic.

1. In the Hub View, click on the appropriate Port Index or Port Status text box to
display the Port Menu (see Figure 2-3, page 2-6).

2-30 Monitoring Hub Performance

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

2. Drag down to Thresholds, and release. The Port Statistics Thresholds

window, Figure 2-16, will appear.

Figure 2-16. The Port Statistics Thresholds Window

The Port Statistics Thresholds window shows the current threshold value (either a
number or a percentage) for the following Port health statistics (for deÞnitions of
the Port Health Statistics, see Serial Port Health, page 2-26):

Received Frames Per Second Shows the threshold for the Frames Received

statistic.

Transmitted Frames Per Second Shows the threshold for the Frames

Transmitted statistic.

Retransmitted Frames Per Second Shows the threshold for the Frames

Retransmitted statistic.

FCS Errors Per Second Shows the threshold for the FCS Errors

statistic.

Logical Rejects Per Second Shows the threshold for the Logical Rejects

statistic.

Transmit Error Ratio Shows the threshold for the Transmit Error

Ratio statistic. This statistic is the ratio of
retransmitted frames per second to
successfully transmitted frames per second
on the port.

Monitoring Hub Performance 2-31

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

Receive Error Ratio Shows the threshold for the Receive Error

Ratio statistic. This statistic is the ratio of
frames rejected per second to frames
accepted per second on the port.

Transmit Percent Utilization Shows the threshold for the Tx Utilization %

statistic.

Receive Percent Utilization Shows the threshold for the Rx Utilization %

statistic.

Managing the Hub

In addition to the performance information described in the preceding sections,
the Hub View also provides you with the tools you need to conÞgure your device
and keep it operating properly. Hub management functions include setting the
polling intervals, and enabling and disabling serial ports.

Setting the Polling Intervals

To set the polling intervals used by SPMA and the FRX:

1. Click on to display the Device menu.

2. Drag down to Polling Intervals, and release.

Figure 2-17. FRX Hub View Polling Intervals

3. To activate the desired polling, click mouse button 1 on the selection box to
the right of each polling type field.

2-32 Managing the Hub

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

4. To change a polling interval, highlight the value you would like to change, and

enter a new value in seconds. Note that the Use Defaults option must

not

be

selected, or values will revert back to default levels when you click on

, and your changes will be ignored.

5. If you wish to use your new polling interval settings as the default values that

SPMA will use for each FRX or SmartSwitch 1800 you are managing, use
mouse button 1 to select the Save As Defaults option.

6. If you wish to replace existing v alues with the current set of default v alues, use

mouse button 1 to select the Use Defaults option.

7. Click mouse button 1 on once your changes are complete.

Changes take effect after the current polling cycle is complete.

You can set the update intervals for the following:

Contact Status

This polling interval controls how often the FRX or SmartSwitch 1800 is ÒpingedÓ
to check SPMAÕs ability to maintain a connection with the device.

NOTE

Device General Status

This polling interval controls how often the Hub View Front Panel Information Ñ
such as Uptime, Device Name, and so forth Ñ and some status information is
updated.

Device Configuration

This polling interval controls how often a survey is conducted of the type of
equipment installed in the FRX or SmartSwitch 1800; information from this poll
would change the Hub View to reßect the addition and/or removal of an RLP or
LAN card.

Port Operational State

This polling interval controls the update of the information displayed in the Port
Status boxes for each port in the hub. Port state information varies according to
the Port Display Form which is currently selected.

Statistics

This polling interval controls how often the information displayed in the Port
Status boxes is updated when the Port Display Form is set to a rate or percentage.

SPMA generates network trafÞc when it retrieves the above-described information; keep
in mind that shorter intervals mean increased network trafÞc. Range limits for these
polling times are 0-999,999 seconds; however, an entry of 0 will be treated as a 1.

Managing the Hub 2-33

Using the FRX4000, FRX6000, and SmartSwitch 1800 Hub View

Enabling and Disabling Serial Ports

You can use the Port Menu available for each conÞgured serial port and LAN port
to change the selected portÕs administrative status. To do so:

1. In the Hub View, click on the appropriate Port Index or Port Status text box to
display the Port Menu (see Figure 2-3, page 2-6).

2. Drag down to Enable or Disable, as desired, and release.

Applying Port-level Changes

After you have made any port-level conÞguration changes (such as conÞguring
an SNA or BSCI port), your changes will not take effect until you have done an
on-line update. To do so:

1. In the Hub View, click on the appropriate Port Index or Port Status text box to
display the Port Menu (see Figure 2-3, page 2-6).

2. Drag down to On-line Update and release.

NOTE

After you have made system-level changes (such as conÞguring an IP Interface), you
must apply those changes by rebooting the FRX or SmartSwitch 1800 device, or through
console management via the [F7] command.

2-34 Managing the Hub

Configuring the T rap Table

A few words about traps; accessing the Trap Table window; configuring the trap table

About T raps

The FRX4000, FRX6000, and the SmartSwitch 1800 have the ability to issue
unsolicited SNMP traps to notify management stations of unusual events. These
traps will not be issued, however, until the deviceÕs trap table has been properly
conÞgured, designating one or more workstations to receive the traps and
selecting the traps that will be sent. This conÞguration can be performed via the
Trap Table.

Chapter 3

SPMA does not accept the trap messages; that task is left to your network management

NOTES

platform. (See the appropriate network management system documentation for details
about viewing trap messages.) If you are using SPMA in a stand-alone mode, traps
directed to a workstation which does not have some facility for accepting them will be
ignored.

In addition, so that your network management platform can interpret the FRX trap
messages, you must have properly installed and conÞgured the Cabletron trap Þle
included with your software. This process should have occurred during installation; see
your Installing and Using... guide for details.

Launching the T rap Table

To launch the Trap Table:

1. Click on the button to display the Device menu.

2. Drag down to T rap T able, and release. The Trap T ab le window, Figure 3-1, will

appear.

3-1

Configuring the Trap Table

Figure 3-1. The Trap Table

The list box at the top of the window displays the trap table entries that have
already been conÞgured; the Þelds and buttons in the lower portion of the
window allow you to add new entries and modify or delete existing ones. Each
device can support up to 16 entries in its trap table.

Each trap table entry contains the following parameters:

IP Address

Indicates the IP address of the management workstation that will receive traps. Be
sure this is a management workstation which has some facility for accepting and
displaying traps, or traps sent there will be ignored.

Status

Each trap table entry can be either enabled or disabled; when enabled, the entry is
active and the designated traps will be sent when they occur. No traps are sent to
disabled entries.

Severity

Each trap issued by the FRX or SmartSwitch 1800 contains a severity designation,
indicating the importance of the event it is announcing; you can use these levels
to Þlter the traps you wish to send to each designated workstation. Only those

3-2 Launching the T rap Table

traps with a severity level equal to or greater than this severity setting will be
forwarded to the associated management workstation. Each trap is assigned one
of four severity levels:

Informational Indicates an informational event (no action generally

Minor Indicates a minor fault or trafÞc disturbance;

Major Indicates a major fault or link alarm; corrective action

Critical Indicates a serious fault or error that requires immediate

Configuring T raps

Configuring the Trap Table

required) or a small conÞguration error. This is a Level 4
severity.

recommended action typically involves clearing the fault
at the Þrst suitable occasion. This is a Level 3 severity.

should be taken as soon as possible. This is a Level 2
severity.

action. This is a Level 1 severity.

To add a trap table entry:

1. In the IP Address field, enter the IP address of the workstation to which you

wish to direct trap messages from the selected FRX or SmartSwitch 1800
device. Be sure this is a workstation with some facility for accepting and
displaying SNMP traps.

2. In the Status field, click to either enable or disable your new entry. If you

disable an entry, no traps will be sent to its designated workstation.

3. Use the Severity Level field to select which traps you wish to send to the

selected workstation: only those traps with severity levels equal to or
exceeding the level assigned here will be forwarded to the selected
workstation.

4. Click on to add your new entry.

To modify an existing entry:

1. In the list box, click to select the entry you wish to modify. The selected entry

will be highlighted. (Note that you can only modify one entry at a time.)

2. Edit the IP Address, Status, and/or Severity Level fields, as desired.

3. Click on to modify the selected entry.

Configuring T raps 3-3

Configuring the Trap Table

To delete an existing entry:

1. In the list box, click to select the entry you wish to delete. The selected entry
will be highlighted. (Note that you can only delete one entry at a time.)

2. Click on to delete the selected entry.

Trap Messages

Following are some general descriptions of traps that may be sent by your FRX or
SmartSwitch 1800 device, including the conditions or events they announce, the
level of severity assigned to those conditions or events, the numeric designation
assigned to the trap, and, where appropriate, suggestions for corrective action.

Transmitter Stuck 146

No clock is being generated.

Severity Informational (Level 4)

Action Check conÞgurations and set the clock.

Configured for extended sequence numbering, received SABM 181

The Port record is conÞgured for a maximum frame sequence number
(Outstanding Frames) greater than seven, but a command was received setting
the mode to allow a maximum of seven.

Severity Informational (Level 4)

Configured for normal sequence numbering,
received SABME 182

The Port record is conÞgured for a maximum frame sequence number
(Outstanding Frames) of seven or fewer, but a command was received setting the
mode to allow up to 127.

Severity Informational (Level 4)

Received FRMR, WXYZ=”n”, control field=”n”,
V(s)=”n”, V(r)=”n”, CMD/RSP=”n” 197

The RLP HDLC frame processor task received a frame reject (FRMR) response to a
previously transmitted frame.

Severity Major (Level 2)

Action The system recovers automatically from this error; however, if

the message is repeated, it may mean that you have a bad
communications line.

3-4 Trap Messages

Configuring the Trap Table

SABM/DISC with wrong link address 198

The HDLC frame processor task for the port has received an improperly
addressed frame from the subscriber. This situation usually occurs when the port
and subscriber devices are both conÞgured as logical DCEs or logical DTEs.

Severity Informational (Level 4)

Action Modify the Port record so that one end of the connection is a

logical DCE and the other is a logical DTE.

Illegal TC/Gen Clk Combination 219

The software has determined that a port is set to run at an illegal line speed
(throughput class).

Severity Critical (Level 1)

Action This is probably a conÞguration error. Check the Port record and

change the throughput class, if necessary.

Excessively noisy line 250

Self-explanatory.

Severity Minor (Level 3)

Action Check the communications line and cables.

LP Buf Usage exceeded T: “n” C: “n” 304

The RLP statistic Percentage of Buffers in Use has exceeded the threshold
(T: ÒnÓ) that was set by the user. (C: ÒnÓ is the current value.)

Severity Informational (Level 4)

Action If this happens frequently, you may need to reroute some trafÞc.

LP Msg Queued exceeded T: “n” C: “n” 305

The RLP statistic Number of Queued Messages has exceeded the threshold
(T: ÒnÓ) that was set by the user. (C: ÒnÓ is the current value.)

Severity Informational (Level 4)

Action If this happens frequently, you may need to reroute some trafÞc.

LP Rcv Frm/Sec exceeded T: “n” C: “n” 306

The RLP statistic Received Frames/Sec has exceeded the threshold (T: ÒnÓ) that
was set by the user. (C: ÒnÓ is the current value.)

Severity Informational (Level 4)

Action If this happens frequently, you may need to reroute some trafÞc.

Trap Messages 3-5

Configuring the Trap Table

LP Trn Frm/Sec exceeded T: “n” C: “n” 307

The RLP statistic Transmitted Frames/Sec has exceeded the threshold (T: ÒnÓ)
that was set by the user. (C: ÒnÓ is the current value.)

Severity Informational (Level 4)

Action If this happens frequently, you may need to reroute some trafÞc.

LP Rej Frm/Sec exceeded T: “n” C: “n” 308

The RLP statistic Rejected Frames/Sec has exceeded the threshold (T: ÒnÓ) that
was set by the user. (C: ÒnÓ is the current value.)

Severity Informational (Level 4)

Action If this happens frequently, check the line for noise and check for

LP Rtrn Frm/S exceeded T: “n” C: “n” 309

The RLP statistic Retransmitted Frames/Sec has exceeded the threshold (T: ÒnÓ)
that was set by the user. (C: ÒnÓ is the current value.)

conÞguration errors on both the FRX port and the connected user
device.

Severity Informational (Level 4)

Action If this happens frequently, check the line for noise and check for

conÞguration errors on both the FRX port and the connected user
device.

Rcv Frm/Sec exceeded T: “n” C: “n” 311

The port statistic Received Frames/Sec has exceeded the threshold (T: ÒnÓ) that
was set by the user. (C: ÒnÓ is the current value.)

Severity Informational (Level 4)

Action If this happens frequently, you may need to reroute some trafÞc.

Tran Frm/Sec exceeded T: “n” C: “n” 312

The port statistic Transmitted Frames/Sec has exceeded the threshold (T: ÒnÓ)
that was set by the user. (C: ÒnÓ is the current value.)

Severity Informational (Level 4)

Action If this happens frequently, you may need to reroute some trafÞc.

RTrn Frm/Sec exceeded T: “n” C: “n” 313

The port statistic Retran Frames/Sec has exceeded the threshold (T: ÒnÓ) that was
set by the user. (C: ÒnÓ is the current value.)

Severity Informational (Level 4)

Action If this happens frequently, check the line for noise, and check for

conÞguration errors on both the FRX port and the connected user
device.

3-6 Trap Messages

Configuring the Trap Table

FCS Rej/Sec exceeded T: “n” C: “n” 314

The port statistic FCS Errors/Sec has exceeded the threshold (T: ÒnÓ) that was set
by the user. (C: ÒnÓ is the current value.) A value consistently greater than zero
indicates line problems.

Severity Informational (Level 4)

Action If this happens frequently, check the line for noise, and check for

conÞguration errors on both the FRX port and the connected user
device.

Log Rej/Sec exceeded T: “n” C: “n” 315

The port statistic Logical Rejects/Sec has exceeded the threshold (T: ÒnÓ) that was
set by the user. (C: ÒnÓ is the current value.) A value consistently greater than zero
indicates line problems.

Severity Informational (Level 4)

Action If this happens frequently, check the line for noise, and check for

conÞguration errors on both the FRX port and the connected user
device.

Trn Err Ratio exceeded T: “n” C: “n” 316

The port statistic Transmit Error Ratio has exceeded the threshold (T: ÒnÓ) that
was set by the user. (C: ÒnÓ is the current value.)

Severity Informational (Level 4)

Action If this happens frequently, check the line for noise, and check for

conÞguration errors on both the FRX port and the connected user
device.

Rcv Err Ratio exceeded T: “n” C: “n” 317

The port statistic Receive Error Ratio has exceeded the threshold (T: ÒnÓ) that was
set by the user. (C: ÒnÓ is the current value.)

Severity Informational (Level 4)

Action If this happens frequently, check the line for noise, and check for

conÞguration errors on both the FRX port and the connected user
device.

Rcv Port Usage exceeded T: “n” C: “n” 318

The port statistic % Receive Port Utilization has exceeded the threshold (T: ÒnÓ)
that was set by the user. (C: ÒnÓ is the current value.)

Severity Informational (Level 4)

Action If this happens frequently, you may need to add ports or reroute

some trafÞc.

Trap Messages 3-7

Configuring the Trap Table

Trn Port Usage exceeded T: “n” C: “n” 319

The port statistic % Transmit Port Utilization has exceeded the threshold (T: ÒnÓ)
that was set by the user. (C: ÒnÓ is the current value.)

Severity Informational (Level 4)

Action If this happens frequently, you may need to add ports or reroute

Receive Yellow Alarm Condition Set 338

A Yellow Alarm was received.

Severity Major (Level 2)

Action Contact your T1 carrier.

Receive Yellow Alarm Condition Set 339

The condition that caused event 338 has been cleared

Severity Informational (Level 4)

LIC “n” Installed, Not Configured 377

The speciÞed Line Interface Card (LIC) exists in the node, but has not been
conÞgured in the Line Processor Þle.

some trafÞc.

Severity Minor (Level 3)

Action ConÞgure the LIC or remove it from the node.

LIC “n” Configured, Not Installed 378

The speciÞed Line Interface Card (LIC) has been conÞgured in the Line Processor
Þle, but does not exist in the node.

Severity Critical (Level 1)

Action Install the LIC or delete its record.

LIC “n” Config Mismatch—Type “n” 379

The interface type of the speciÞed Line Interface Card (LIC) installed in the node
is different from the interface type conÞgured in the Line Processor Þle. As a
result, the software does not load properly and will not operate.

Severity Major (Level 2)

Action Change either the card or the Þle.

Link Enabled 400

The port has been enabled from the On-Line Port Operations menu.

Severity Major (Level 2)

3-8 Trap Messages

Configuring the Trap Table

Link Disabled 401

The port has been disabled from the On-Line Port Operations menu.

Severity Major (Level 2)

Link Disconnected 402

For X.25, this means that the link is disconnected and level 2 cannot be
established.

For SNA TPAD, this means that an XID command frame has been issued by the
TPAD, but either there has been no response or the received XID data does not
match the XID data conÞgured for the TPAD subscriber.

For SNA HPAD, this means that no XID or SNRM command frame has been
received for any link address conÞgured for the HPAD subscriber.

Severity Major (Level 2)

Action Check the hardware at both ends to make sure the devices are

operational and cables are securely connected. For SNA, also
check the conÞguration records to make sure they match the
HPAD/TPAD.

Link Up 403

The level 2 link is up.

Severity Major (Level 2)

X.25 Link Failed 404

The link has failed; some modem controls are not present, and the physical link is
down.

Severity Major (Level 2)

Action Check the modem and cables for secure connections and proper

operation.

Restart with cc “n” dc “n” 405

A Restart has been issued, with the cause code (cc) and diagnostic code (dc)
shown.

Severity Informational (Level 4)

Action Depends on the cause. If necessary, contact your service

representative.

Trap Messages 3-9

Configuring the Trap Table

Operational 406

For all ports except those noted below, this means that the link is up.

For SNA TPAD, this means that the XID exchange has been performed, and the
XID data received in the response frame matches the XID data conÞgured for the
TPAD subscriber. The link is ready to establish an X.25 connection with the
remote HPAD.

For SNA HPAD, this means that an XID or SNRM command frame has been
received for at least one of the link addresses conÞgured for the HPAD subscriber.
The link is ready to establish an X.25 connection with the remote TPAD.

Severity Major (Level 2)

Call Clr LCN = “n” cc = “n” dc = “n” 407

Self-explanatory.

Severity Informational (Level 4)

Action Depends on the cause. If necessary, contact your service

representative.

End of IPL 408

Self-explanatory.

Severity Informational (Level 4)

PVC is Up 409

Self-explanatory.

Severity Informational (Level 4)

PVC Reset 410

A Reset was sent on the PVC.

Severity Informational (Level 4)

Received Reset LCN = “n”, cc = “n” dc = “n” 411

A Reset was received on the designated LCN, with the cause code cc and
diagnostic code dc.

Severity Informational (Level 4)

Received Reset Confirm 412

A Reset ConÞrmation was received.

Severity Informational (Level 4)

3-10 Trap Messages

Configuring the Trap Table

PAD Link Failed 413

Self-explanatory.

Severity Major (Level 2)

Action Check the async PAD port and its cables for proper operation and

secure connection.

Beginning of Congestion 414

The level of Maximum Congestion speciÞed in the Node Defaults record has been
exceeded, and no more events will be put into the event buffer until the Minimum
Congestion level (also speciÞed in the Node Defaults record) has been reached.

Severity Informational (Level 4)

Action If this occurs frequently, you may want to increase the level of

Maximum Congestion speciÞed in the Node Defaults record.

End of Congestion, “n” events lost 415

The Minimum Congestion level has been reached. (See event 414, above.)

Severity Informational (Level 4)

PAD Autocall Retries Exhausted 416

The async PAD retry timer has expired without a connection being established.

Severity Minor (Level 3)

Action None; however, if this occurs with any frequency, you may want

to increase the timer (Retry Count) or check the remote async
device for problems.

Frame Relay Link Failed 417

The physical link is down.

Severity Critical (Level 1)

Action Check the cables for secure connections and proper operation.

PU Status p = “n” stn = 0x”n” status = “n” 426

The SDLC PU status has changed.

Severity Major (Level 2)

Trap Messages 3-11

Configuring the Trap Table

Duplicate of DLCI “n” on Port 428

Each connection sharing a DLCI must be on a different logical port, and two
records have been conÞgured in the FRX specifying the same logical port on one
DLCI. (DLCIs are conÞgured in records for logical ports, IP/LLC2/IPX interfaces
over frame relay, and frame relay PVCs.) Only one of the duplicate connections
will come up.

Severity Minor (Level 3)

Action Check the database records for the duplicate conÞguration and

File Update: FRDLCI.DAT 429

The Frame Relay DLCI conÞguration Þle has been updated.

Severity Informational (Level 4)

Received Port Disable Request 430

Self-explanatory.

Severity Critical (Level 1)

change one (or more) of the records.

Action None; however, all users of this port should be made aware of the

disable.

Received Port Dump Request 431

The BSC device has experienced a problem that caused it to send a request to send
a dump to the port.

Severity Critical (Level 1)

Action Check the device.

Node Under Remote Control 432

Self-explanatory.

Severity Informational (Level 4)

Remote Control Released 433

Self-explanatory.

Severity Informational (Level 4)

Remote Control CXN Clr cc= “n” dc = “n” 434

A remote control connection was cleared.

Severity Informational (Level 4)

Action Depends on the cause.

3-12 Trap Messages

Configuring the Trap Table

LG Buffer MALLOC Problem PKTs Lost 435

This applies to a debug tool used by service personnel, and will not appear under
normal operation.

Severity Major (Level 2)

RCV Unknown Event Code from Net. 436

An unknown event was received from the network.

Severity Major (Level 2)

RCV Invalid Event Format from Net. 437

The node has received an event with an invalid format.

Severity Informational (Level 4)

DOS Error Handler Exceeded Limit 438

The FRX was performing a DOS operation and, for some reason, could not reach
DOS.

Severity Major (Level 2)

Action Reboot the node and watch for error messages during boot-up. If

the problem persists, contact your service representative.

Database Error, Access Restricted 439

The database is inconsistent with what the software expects.

Severity Critical (Level 1)

Action Contact your service representative.

Abrev Addr File Upd: ABVSUB.DAT 440

The Abbreviated Address Þle has been updated.

Severity Informational (Level 4)

Async Init File Upd: ASYSETUP.DAT 441

The Async Console Þle has been updated.

Severity Informational (Level 4)

BSC Device File Upd: BSCDSP.DAT 442

The BSC Interactive Devices Þle has been updated.

Severity Informational (Level 4)

LP Config File Upd: LPTYPE.DAT 443

The Line Processor conÞguration Þle has been updated.

Severity Informational (Level 4)

Trap Messages 3-13

Configuring the Trap Table

Port Config File Upd: PRTPAR.DAT 445

The Port conÞguration Þle has been updated.

Severity Informational (Level 4)

Pad Profile File Upd: PROFILE.DAT 446

The Async PAD ProÞle Þle has been updated.

Severity Informational (Level 4)

PVC Config File Upd: PVCSUB.DAT 447

The PVC Subscriber Þle has been updated.

Severity Informational (Level 4)

Rmt Subscriber File Upd: RSNSVC.DAT 448

The Remote Subscriber Þle has been updated.

Severity Informational (Level 4)

Subscriber File Upd: SVCSUB.DAT 449

The SVC Subscriber Þle has been updated.

Severity Informational (Level 4)

Statistic Def File Upd: STDPAR.DAT 450

The Default Statistics Parameters Þle has been updated.

Severity Informational (Level 4)

Translation File Upd: XLTPAR.DAT 451

The X.25 Address Translation Template Þle has been updated.

Severity Informational (Level 4)

X.25 Default File Upd: X25REC.DAT 452

The Node Þle has been updated.

Severity Informational (Level 4)

Alarm Enable File Upd: ERRMSG.TXT 453

The Alarms Þle has been updated.

Severity Informational (Level 4)

Remote Update File Upd: UPDATE.TXT 454

A software update has been sent.

Severity Informational (Level 4)

3-14 Trap Messages

Configuring the Trap Table

Login Password Changed 455

Self-explanatory.

Severity Informational (Level 4)

Operator Logged into Node 456

An async terminal operator has logged into the node via an async PAD port.

Severity Informational (Level 4)

Operator Logged out of Node 457

The async terminal operator has logged out of the node via the async PAD port.

Severity Informational (Level 4)

PAD Login File Upd: PADLOG.DAT 458

The Login Þle has been updated.

Severity Informational (Level 4)

IP Route File Upd: IPRSUB.DAT 459

The IP Routing Þle has been updated.

Severity Informational (Level 4)

IP Interface File Upd: IPRSUB.DAT 460

The IP Routing Þle has been updated.

Severity Informational (Level 4)

X.25 CUG File Updated: CUGPAR.DAT 461

The Closed User Group Þle has been updated.

Severity Informational (Level 4)

SNMP Trap File Upd: TRPPAR.DAT 462

The SNMP Trap Routing Þle has been updated.

Severity Informational (Level 4)

SNMP Community File Upd: COMPAR.DAT 463

The SNMP Community Table Þle has been updated.

Severity Informational (Level 4)

LP Buf Usage Under Threshold 464

The situation that caused event 304 has ended.

Severity Informational (Level 4)

Trap Messages 3-15

Configuring the Trap Table

LP Msg Queued Under Threshold 465

The situation that caused event 305 has ended.

Severity Informational (Level 4)

LP Rcv Frm/Sec Under Threshold 466

The situation that caused event 306 has ended.

Severity Informational (Level 4)

LP Trn Frm/Sec Under Threshold 467

The situation that caused event 307 has ended.

Severity Informational (Level 4)

LP Rej Frm/Sec Under Threshold 468

The situation that caused event 308 has ended.

Severity Informational (Level 4)

LP Rtrn Frm/S Under Threshold 469

The situation that caused event 309 has ended.

Severity Informational (Level 4)

Rcv Frm/Sec Under Threshold 471

The situation that caused event 311 has ended.

Severity Informational (Level 4)

Tran Frm/Sec Under Threshold 472

The situation that caused event 312 has ended.

Severity Informational (Level 4)

ReTran Frm/Sec Under Threshold 473

The situation that caused event 313 has ended.

Severity Informational (Level 4)

FCS Rej/Sec Under Threshold 474

The situation that caused event 314 has ended.

Severity Informational (Level 4)

Log Rej/Sec Under Threshold 475

The situation that caused event 315 has ended.

Severity Informational (Level 4)

Tran Err Ratio Under Threshold 476

The situation that caused event 316 has ended.

3-16 Trap Messages

Configuring the Trap Table

Severity Informational (Level 4)

Rcv Err Ratio Under Threshold 477

The situation that caused event 317 has ended.

Severity Informational (Level 4)

Port Rcv Usage Under Threshold 478

The situation that caused event 318 has ended.

Severity Informational (Level 4)

Port Trn Usage Under Threshold 479

The situation that caused event 319 has ended.

Severity Informational (Level 4)

Delete failed—nonexistent interface “n” 480

An IP Interface database record was created for a nonexistent interface. Someone
then deleted the record (using [F4]), which caused this message to be generated.

Severity Informational (Level 4)

No mem avail processing intface “n” 481

The FRX6000 RLP did not have enough available memory to add the speciÞed
interface.

Severity Minor (Level 3)

Action Contact Netlink Support.

Can’t add interface “n”—IPadr err 482

Self-explanatory.

Severity Minor (Level 3)

Action Double-check the conÞgured addresses.

Error adding interface “n” 483

Self-explanatory.

Severity Minor (Level 3)

Action Contact Netlink Support.

Error modifying interface “n” 484

Self-explanatory.

Severity Minor (Level 3)

Action Double-check the database record.

Trap Messages 3-17

Configuring the Trap Table

Interface “n” deleted successfully 485

Self-explanatory.

Severity Informational (Level 4)

Interface “n” added successfully 486

Self-explanatory.

Severity Informational (Level 4)

Interface “n” modified successfully 487

Self-explanatory.

Severity Informational (Level 4)

Error deleting route with destination “n,” mask “n,” router “n” 488

Self-explanatory.

Severity Minor (Level 3)

Action Contact Cabletron SystemsÕ Global Call Center.

Route with destination “n,” mask “n,” router “n” deleted successfully 489

Self-explanatory.

Severity Informational (Level 4)

Error adding route with destination “n,” mask “n,” router “n” 490

Self-explanatory.

Severity Minor (Level 3)

Action Cabletron SystemsÕ Global Call Center.

Route with destination “n,” mask “n,” router “n” added successfully 491

Self-explanatory.

Severity Informational (Level 4)

BAG “n” capped at “n” but trunk MAXDPS “n” 492

The data packet size (MAXDPS) on the trunk caused a greater trafÞc load than the
conÞgured Bandwidth Allocation Class (Group) would allow, so the software
adjusted the bandwidth allocated to this trunk.

Severity Minor (Level 3)

IPX Route File Upd: IPXRSUB.DAT 493

The IPX Route Þle has been updated.

Severity Informational (Level 4)

3-18 Trap Messages

Configuring the Trap Table

Alloc Error on Master SNMP Agent 494

A buffer could not be allocated to process an SNMP message.

Severity Critical (Level 1)

BPAD: Invalid Q Pkt “n”—PL 500

An invalid Q packet has been received, disabling the port.

Severity Minor (Level 3)

Action ConÞgure the LIC or remove it from the node.

BPAD: Invalid Pkt “n”—PL 501

An invalid packet has been received, disabling the port.

Severity Minor (Level 3)

Action Take the same action as for message 500.

BPAD: Invalid MSG “n”—Link 502

An invalid message has been received, disabling the port.

Severity Minor (Level 3)

Action Take the same action as for message 500.

BPAD: Invalid MSG “n”—Exchange 503

An invalid message has been received, disabling the port.

Severity Minor (Level 3)

Action Take the same action as for message 500.

BPAD: Invalid CUA “n” DUA “n” 504

An invalid message has been received, disabling the port.

Severity Minor (Level 3)

Action Take the same action as for message 500.

LINK: Invalid MSG fc “n”—BPAD 505

An invalid message has been received, disabling the port.

Severity Minor (Level 3)

Action Take the same action as for message 500.

BSCI: Invalid control block 513

An error has occurred and has disabled the port.

Severity Minor (Level 3)

Action Take the same action as for message 500.

Trap Messages 3-19

Configuring the Trap Table

BSCI: Invalid parameters 514

One or more parameters speciÞed in the Port Parameters record for this port is
invalid. This error disables the port.

Severity Minor (Level 3)

Action Correct the Port Parameters record, then reenable the port ([B],

BSCI: Invalid port number or type 515

The port number and/or type speciÞed in the Port record is not valid for BSC
Interactive.

Severity Minor (Level 3)

Action Check the Port record.

BSCI: Invalid message transfer 516

Self-explanatory. This error disables the port.

Severity Minor (Level 3)

[A], [C] from the Main Menu). If this doesnÕt work, take the same
action as for message 500.

Action Take the same action as for message 500.

BSCI: Invalid circuit operations 517

An invalid operation has occurred and has disabled the port.

Severity Minor (Level 3)

Action Take the same action as for message 500.

BSCI: Invalid state event action 518

An invalid operation has occurred and has disabled the port.

Severity Minor (Level 3)

Action Take the same action as for message 500.

BSCI: Invalid buffer operations 519

An invalid operation has occurred and has disabled the port.

Severity Minor (Level 3)

Action Take the same action as for message 500.

BSCI: Invalid CRC operations 520

An invalid operation has occurred and has disabled the port.

Severity Minor (Level 3)

Action Take the same action as for message 500.

3-20 Trap Messages

Configuring the Trap Table

BSCI: Invalid queue operations 521

An invalid operation has occurred and has disabled the port.

Severity Minor (Level 3)

Action Take the same action as for message 500.

BSCI: Invalid protocol operations 522

An invalid operation has occurred and has disabled the port.

Severity Minor (Level 3)

Action Take the same action as for message 500.

BSCI: Invalid CUA, DUA operations 523

An invalid operation has occurred and has disabled the port.

Severity Minor (Level 3)

Action Take the same action as for message 500.

Invalid Line Speed LP “n” Port “n” 524

Self-explanatory.

Severity Minor (Level 3)

Action Correct the line speed in the Port record.

I-FRM Blocked-Remote Busy Timeout 530

An RNR (Receive Not Ready) condition on the port has been cleared by
expiration of the Remote Busy Timer, which caused the port to be reset.

Severity Major (Level 2)

Action Check the user device for a problem that caused the RNR.

I-FRM Blocked-No Acks from Remote 531

The remote user device is not accepting transmission from the local device, and
the local port has been reset.

Severity Major (Level 2)

Action Check the remote device for a problem.

Enter Service Affecting Condition 532

The DTE and DCE exchange messages regularly so that each knows the other is
running and ready. If one end does not respond, this event message is sent and
the link goes down.

Severity Major (Level 2)

Action Check the equipment to see what caused the failure to respond.

Trap Messages 3-21

Configuring the Trap Table

Exit Service Affecting Condition 533

The situation that caused event 362 has ended.

Severity Major (Level 2)

DLCI “n” Frm Relay PVC Disconnected 534

Self-explanatory.

Severity Informational (Level 4)

DLCI “n” Received Bad Frame 535

Either the DLCI was not conÞgured or the frame was on an unavailable DLCI.

Severity Minor (Level 3)

Action ConÞgure the DLCI or resent the frame.

DLCI “n” No Response to STATUS ENQ 536

There was no response to a status enquiry from the DTE.

Severity Minor (Level 3)

Action Check the status of the DCE.

DLCI “n” Flow Control On 537

Flow control has been implemented on a frame relay port and data is queued.

Severity Minor (Level 3)

DLCI “n” Frame Discarded—Flow Ctl 538

Self-explanatory.

Severity Minor (Level 3)

Action The frame must be resent.

DLCI “n” Line does not exist 539

Self-explanatory.

Severity Minor (Level 3)

Action Check the conÞguration records for the node, LP and port.

DLCI “n” Not Configured 540

Self-explanatory.

Severity Minor (Level 3)

Action ConÞgure the DLCI in the portÕs database record.

3-22 Trap Messages

Configuring the Trap Table

DLCI “n” Frame Relay Header Invalid 541

The header contained an invalid DLCI.

Severity Minor (Level 3)

Action Check the conÞguration record for the port.

DLCI “n” PVC does not exist 542

Self-explanatory.

Severity Minor (Level 3)

Action Create a PVC record.

DLCI “n” Frame Discarded—CIR 543

A frame was discarded, probably because the excess burst size (BE) was exceeded.

Severity Minor (Level 3)

Action The frame must be resent.

DLCI “n” frame relay PVC deleted 545

Self-explanatory.

Severity Informational (Level 4)

DLCI “n” frame relay PVC connected 546

Self-explanatory.

Severity Informational (Level 4)

DLCI “n” Data Received on Inactive PVC 547

One end of the PVC is probably not up.

Severity Minor (Level 3)

Action Check both ends of the PVC.

DLCI “n” No STATUS ENQ Received 548

No Status Enquiry was received when one was expected.

Severity Minor (Level 3)

Action Check the remote device.

LLC Interface File Upd: LLC2IPAR.DAT 561

The LLC2 Interface Þle has been updated.

Severity Informational (Level 4)

Trap Messages 3-23

Configuring the Trap Table

LLC Host File Upd: LLC2HPAR.DAT 562

The LLC2 Host Þle has been updated.

Severity Informational (Level 4)

LLC LAN Card File Upd: LANPAR.DAT 563

The LLC2 LAN Card Þle has been updated.

Severity Informational (Level 4)

IPX Filter Def File Upd: IPXFPAR.DAT 564

The IPX Filter DeÞnitions Þle has been updated.

Severity Informational (Level 4)

IPX Filt App File Upd: IPXFLTAP.DAT 565

The IPX Filter Applications Þle has been updated.

Severity Informational (Level 4)

Bridge Filt Def File Upd: BRGFLTD.DAT 640

The Bridge Filter DeÞnitions Þle has been updated.

Severity Informational (Level 4)

Bridge Filt App File Upd: BRGFLTAP.DAT 641

The Bridge Filter Applications Þle has been updated.

Severity Informational (Level 4)

IPX Interface File Upd: IPXISUB.DAT 642

The IPX Interfaces Þle has been updated.

Severity Informational (Level 4)

Lan Card Number/Type Mismatch 643

A mismatch has occurred between the LAN card type and the requested interface
type when conÞguring a LAN-based IP or IPX interface.

Severity Minor (Level 3)

Action Change the requested LAN card number or LAN card type.

Fr RLP/PORT/DLCI Mismatch 644

A mismatch has occurred between the current conÞguration and the requested
RLP/Port/DLCI when conÞguring a frame relay based IP or IPX interface.

Severity Minor (Level 3)

Action Change the requested RLP/Port/DLCI.

3-24 Trap Messages

Configuring the Trap Table

Receive Loss of Sync condition Set 650

The receiving end of the connection has reported a loss of synchronization.

Severity Major (Level 2)

Action Check the T1/E1 cable at the local end of the connection. If it is

securely connected and everything else appears operational,
contact your carrier.

Receive Carrier Loss condition Set 651

The receiving end of the connection has reported that the signal from the carrier is
lost.

Severity Major (Level 2)

Action Check the T1/E1 cable at the local end of the connection. If it is

securely connected and everything else appears operational,
contact your carrier.

Receive Remote Alarm condition Set 652

The remote device is not receiving the signal from the local device.

Severity Major (Level 2)

Action Check the T1/E1 cable at the local end of the connection. If it is

securely connected and everything else appears operational,
contact your carrier.

Receive Loss of Sync condition Cleared 653

The situation that caused event 650 has been Þxed. However, the T1/E1
connection will not be operational if any of events 650-652 have been set but not
cleared.

Severity Informational (Level 4)

Receive Carrier Loss condition Cleared 654

The situation that caused event 651 has been Þxed. However, the T1/E1
connection will not be operational if any of events 650-652 have been set but not
cleared.

Severity Informational (Level 4)

Receive Remote Alarm condition Cleared 655

The situation that caused event 652 has been Þxed. However, the T1/E1
connection will not be operational if any of events 650-652 have been set but not
cleared.

Severity Informational (Level 4)

Trap Messages 3-25

Configuring the Trap Table

SDLC Rem. Link Stn Not Responding 701

Self-explanatory. (Rem Link Stn is the Remote Link Station.)

Severity Major (Level 2)

Action Check the PU to make sure it is operational.

SDLC Link Stn Sent DM 702

The link station sent a Disconnect Mode response, and the logical link is down.

Severity Major (Level 2)

SDLC Link Stn rcvd FRMR, Inv. cmd 704

The remote device received an invalid command and responded with a Frame
Reject.

Severity Major (Level 2)

SDLC Stn rcvd FRMR, IFLD invalid 705

The remote device received an unpermitted I frame and responded with a Frame
Reject.

Severity Major (Level 2)

SDLC Stn rcvd FRMR, Nr invalid 706

The remote device received a frame with an invalid N

and responded with a

(r)

Frame Reject.

Severity Major (Level 2)

SDLC Stn rcvd FRMR, Ifld too long 707

The remote device received an I frame that was too long and responded with a
Frame Reject.

Severity Major (Level 2)

SDLC Rem Stn sent Invalid Command 708

The remote device received an invalid or unsupported command.

Severity Major (Level 2)

SDLC Rem Stn sent unexpected IFLD 709

The remote device send an unpermitted I frame.

Severity Major (Level 2)

SDLC Rem Stn sent invalid Nr 710

The remote device sent a frame with an invalid N

(r)

.

Severity Major (Level 2)

3-26 Trap Messages

Configuring the Trap Table

SDLC Rem Stn Exceeded window size 711

The number of frames sent by the remote device has exceeded the window size.

Severity Major (Level 2)

SDLC Station Inactivity time exp 712

The timer deÞned by the parameters No Response Poll Period and Maximum
Retransmissions in the SNA Port record has expired.

Severity Major (Level 2)

Action Check the PU to make sure it is operational.

SDLC XID Retries exhausted 713

The retry limit for XID has been exceeded and link establishment has failed.

Severity Major (Level 2)

SDLC Rem Stn sent FRMR—no reason 714

The remote station sent a Frame Reject with no reason.

Severity Major (Level 2)

SDLC Remote RNR limit exceeded 715

The remote station is busy. This could be a hardware or buffer problem in the
remote device.

Severity Major (Level 2)

Action Check the hardware and conÞguration at the remote device.

SDLC Rem Tx Frame exceeds MAXDATA 717

A frame transmitted by the remote station exceeds the conÞgured value for

Maximum Bytes per Frame.

Severity Major (Level 2)

SDLC Rem sent UA in NRM 718

The remote station sent a UA while in Normal Response Mode, which is not
allowed.

Severity Major (Level 2)

SDLC No DSR on link 720

A necessary DSR was not received from the DCE.

Severity Major (Level 2)

Action Check the modem to make sure it is operational.

Trap Messages 3-27

Configuring the Trap Table

SDLC No CTS on link 721

A necessary CTS was not received from the DCE.

Severity Major (Level 2)

Action Check the modem to make sure it is operational.

SDLC No External Clock 722

The necessary clock is not being provided.

Severity Major (Level 2)

Action Check the modem to make sure it is operational.

SDLC LLC/2 Remote Link Stn lost 736

The remote station is not responding. Either the Inactivity Timer (Ti) or
Acknowledgment Timer (T2) has expired.

Severity Major (Level 2)

Action Check the remote station to make sure it is operational.

LLC/2 DM Received 737

The remote station sent a Disconnect Mode response and the logical link is down.

Severity Major (Level 2)

LLC/2 SABME Received when open 738

The remote station sent a SABME to the local station, but the local station had
already been initialized via a SABMEÑUA exchange.

Severity Major (Level 2)

Action None; however, if the problem persists, contact your support

representative.

LLC/2 FRMR Rcvd, Invalid Command 739

The remote device received an invalid or unsupported command, and returned a
Frame Reject.

Severity Major (Level 2)

LLC/2 FRMR Rcvd, IFLD not permitted 740

The remote device received an I-frame when it was not permitted, and returned a
Frame Reject.

Severity Major (Level 2)

LLC/2 FRMR Rcvd, Invalid Nr 741

The remote device received an invalid N

and returned a Frame Reject.

(R),

Severity Major (Level 2)

3-28 Trap Messages

Configuring the Trap Table

LLC/2 FRMR Rcvd, IFLD too long 742

The remote device received an I frame that was too long, and returned a Frame
Reject.

Severity Major (Level 2)

LLC/2 FRMR Rcvd, Invalid Command 743

The remote device received an invalid command or response, and returned a
Frame Reject.

Severity Major (Level 2)

LLC/2 FRMR Sent, IFLD not permitted 744

The remote device sent an I frame when it was not permitted, and a Frame Reject
was returned.

Severity Major (Level 2)

LLC/2 FRMR Sent, Invalid Nr 745

The remote device sent an invalid N

, and a Frame Reject was returned.

(R)

Severity Major (Level 2)

LLC/2 FRMR Sent, IFLD too long 746

The remote device sent an I frame that was too long, and a Frame Reject was
returned.

Severity Major (Level 2)

LLC/2 FRMR Sent, no reason 747

Self-explanatory.

Severity Major (Level 2)

LLC/2 FRMR Rcvd, no reason 748

Self-explanatory.

Severity Major (Level 2)

Excessive Link CRC errors 759

Self-explanatory. The line will be shut down and reestablishment will be retried
once every minute.

Severity Major (Level 2)

SDLC Transmit link error 761

Self-explanatory. The line will be shut down and reestablishment will be retried
later.

Severity Major (Level 2)

Trap Messages 3-29

Configuring the Trap Table

SDLC Link Stn rcv FRMR, Unexp. IFLD 762

The remote station received an S or U frame with an unexpected I frame attached.

Severity Major (Level 2)

3-30 Trap Messages

Chapter 4

Configuring the Subscriber Table

About the Subscriber Table and Subscriber IDs; accessing the Subscriber Table window; adding or
modifying a subscriber table entry; editing the Routing and Address tables

The Subscriber Table allows you to add or modify the entries your FRX or
SmartSwitch 1800 will use to establish virtual connections to end-user devices in
the network. These entries contain the assigned subscriber addresses, as well as
information that links those addresses to a speciÞc FRX or SmartSwitch 1800
physical or logical port (or ports). Entries also contain additional information
related to preferred delivery algorithms, alternate routing paths, and transmission
priority.

The Subscriber Table applies to all serial ports, regardless of protocol; however, it is only

TIP

available on devices running Þrmware version 3.3.0 or later.

About Subscriber IDs

Your FRX and SmartSwitch 1800 devices are designed to provide point-to-point
dedicated connections among the devices communicating through their serial
ports. There are two types of connections used to accomplish this: Permanent
Virtual Circuits, or PVCs, which deÞne permanent point-to-point connections
which are always available, even when they are not being used; and Switched
Virtual Circuits, or SVCs, which are established and broken in response to speciÞc
call requests.

Subscriber IDs are used to establish virtual connections between the FRX and
end-user devices (or subscribers) in the network. A Subscriber ID is associated
with at least one physical or logical port on your FRX or SmartSwitch 1800 device,
and includes a number of parameters related to how call requests are routed to
that subscriber. The Subscriber Table allows you to conÞgure this subscriber
information.

4-1

Configuring the Subscriber Table

Accessing the Subscriber Table

To launch the Subscriber Table:

1. In the Hub View, click on the button to display the Device menu.

2. Drag down to Subscriber T able, and release. The Subscriber Table window,

Figure 4-1, will appear.

Figure 4-1. The Subscriber Table Window

4-2 Accessing the Subscriber Table

The Subscriber Table window contains three main areas: the Subscriber Table
itself (in the top half of the window), which allows you to add, modify, or delete
subscriber entries; the Routing Table (on the lower left), which allows you to
assign one or more routing paths to a subscriber entry by associating that entry
with one or more physical or logical ports on your device; and the Address Table
(on the lower right), which allows you to assign the addresses that will be used
for call redirection (if those options are speciÞed in the table entry). Each of these
tables is described below.

If no Close button appears in your window, use the scroll bar to the right of the display to

TIP

access the button, which is at the bottom of the window.

Configuring the Subscriber Table

The Subscriber Table displayed at the top of the window is the main table that
allows you to deÞne the subscribers who will be communicating across your FRX
or SmartSwitch 1800 device. To conÞgure a Subscriber Table entry, you must set
the following parameters:

Configuring the Subscriber Table

Subscriber ID

Each subscriber is identiÞed by an ID, or address, of up to 15 digits. When
assigning or editing a Subscriber ID, keep the following in mind:

¥ Subscribers using a public data network (PDN) must conform to the format

used by the PDN. (A PDN is a network operated by common carriers or
telecommunications administrations for the purpose of providing data
transmission capabilities to the public.) For example, CCITT recommendation
X.121 speciÞes a format which includes a one-digit international code,
followed by a four-digit Data Network IdentiÞcation Code (DNIC), followed
by up to 10 digits of Network Terminal Number (NTN).

¥ A private network Ñ one that will not communicate with other networks Ñ

can create its own format, using any or all of the available digits as desired.

Since each FRX or SmartSwitch 1800 port can support multiple subscribers,
Subscriber IDs can also use wildcard characters so that all subscribers on a port
can be referenced with a single entry. Two wildcard characters are available:

¥ A question mark (?) in a subscriber ID matches any single digit. For example,

3110?????????? matches any 14-digit address that begins with 3110.

¥ An asterisk, or star (*), matches any combination of digits, including none at

all. For example, 3110*00 is any address that starts with 3110 and ends with 00,
including 311000 but excluding 31100 (overlapping is not allowed). An asterisk
by itself matches any address.

Wildcard characters can also be combined: the address 3110??* matches any
address that begins with 3110 and contains at least two more digits.

Configuring the Subscriber Table 4-3

Configuring the Subscriber Table

Algorithm

The algorithm Þeld allows you to select the means by which call requests are
forwarded to one of several routing paths assigned to the named subscriber. You
can select from among four options:

Round Robin As its name implies, this algorithm selects ports

Line Failed The Alternate Route on Line Failure algorithm selects the

Line Busy The Alternate Route on Line Busy algorithm selects the

Least LCN The Least LCN with Throughput algorithm selects the

cyclically in numeric order (as conÞgured in the Routing
Table). If a selected port is unreachable or congested, call
requests are forwarded on to the next port in sequence.

Þrst listed port that is not in a failed state. If the selected
port does not make the connection, the call request will
be cleared, even if other ports are available.

Þrst port that is not busy. If that port has failed, the next
available port will be selected.

line with the smallest load, calculated using the weight
(speed) and number of virtual circuits in use on that line.
(Weights are assigned to each line in proportion to their
throughput within the routing path.)

TIP

The alternate routes used by these algorithms are speciÞed in the Routing Table, described
beginning on page 4-5; if you do not wish to use a routing algorithm, simply accept the
default setting and enter only one routing path.

Systematic Redirect

The Systematic Redirect Þeld allows you to specify whether or not calls to the
named subscriber will be automatically redirected to the Þrst alternate subscriber
speciÞed in the Address Table (described beginning on page 4-6). If you select yes,
the original subscriber is skipped and all calls designated for that subscriber will
be redirected to the Þrst alternate address, regardless of the condition of either
path. Any additional conÞgured alternate addresses are ignored.

Redirect Busy

If you enable the Redirect Busy option, calls to the named subscriber will be
redirected to the alternates listed in the Address Table if the primary subscriber
device is busy. Again, be sure youÕve conÞgured the alternate addresses in the
Address Table.

Redirect Out-of-Order

The Redirect on Out-of-Order option allows you to specify that calls to the named
subscriber device will be redirected to the alternate subscribers if the primary
device is out of order.

4-4 Configuring the Subscriber Table

Priority

The Connection Priority Þeld allows you to conÞgure priorities for trafÞc within
the device: the higher the number assigned to the subscriber, the higher the
priority that subscriberÕs calls will receive relative to other intra-nodal trafÞc.
These priorities have no effect on trafÞc exiting the device.

TrafÞc priorities can also be conÞgured for SNA ports with LLC2 connections, logical

NOTE

ports, LLC2 hosts, LLC2 interfaces, IP interfaces, IPX interfaces, and PVC connections.
When conÞguring priorities, be sure to consider the types of trafÞc being routed on other
connections in the node.

Configuring Routing Table Entries

So that virtual connections can be established with and by each of the subscribers
deÞned in the Subscriber Table, you must associate each Subscriber ID with one
or more physical or logical ports on your FRX or SmartSwitch 1800 device so that
the call requests can be properly routed and the connection established. This is the
function of the Routing Table. Entries which appear in this table are associated
with the Subscriber ID currently selected in the Subscriber Table portion of the
window; each Subscriber ID must have at least one routing table entry, or it will
not function. If you conÞgure more than one routing path (youÕre allowed up to
eight), paths will be selected according to the algorithm speciÞed in the
Subscriber Table (see page 4-4 for more information on routing algorithms).

Configuring the Subscriber Table

ConÞguring a Routing Table entry requires the following information:

Path

Designates an index number assigned to the routing table entry; in some cases
(depending on the algorithm speciÞed for the selected subscriber table entry), this
index value will deÞne the order in which routing paths are selected when a call
request is received. You can designate up to eight alternate routes for each
subscriber entry; path values must be assigned sequentially.

LP

Designates the index number assigned to the RLP card which contains the
physical or logical port you wish to assign to the selected Subscriber ID.

Port

Designates the index number assigned to the physical or logical port you wish to
assign to the selected Subscriber ID. Indices 0-7 indicate physical ports; indices
8-63 indicate logical ports.

Configuring the Subscriber Table 4-5

Configuring the Subscriber Table

Configuring Address Table Entries

If you have selected any redirect parameters for a Subscriber Table entry, you
must use the Address Table to designate the alternate subscriber addresses that
will be used by the redirect option(s) you have selected (see page 4-4 for more
information on redirect options). You can designate up to Þve alternate addresses
for each subscriber table entry.

Each address table entry requires the following values:

Index

The index value assigned to the address table entry. Some redirect options use this
value to determine the order in which alternate addresses are selected. Allowable
values are 1 - 5; values need not be assigned sequentially.

Address

Use the address Þeld to enter the Subscriber ID for any alternate subscribers you
wish to associate with the selected subscriber table entry. These alternate
addresses will be used by any enabled redirect options to determine alternate
paths for call requests directed to the selected subscriber. Note that you cannot
use wildcard characters in this Þeld.

Adding or Modifying Subscriber Table Entries

To add or modify a subscriber table entry:

1. If you wish to modify an existing entry, be sure that entry is highlighted in the
Subscriber Table portion of the window.

Remember, any additions or deletions to the Routing Table or the Address Table actually

TIP

modify the selected Subscriber Table entry.

2. In the Subscriber T able portion of the window:
a. Enter the appropriate Subscriber ID value. You can use up to 15 digits,

including the question mark (?) and asterisk (*) wildcards. F or subscribers
using a Public Data Network (PDN), be sure the ID you assign follo ws the
code specifications for that network.

b. In the Algorithm field, select the means by which any alternate routing

paths assigned to this subscriber will be selected. (Alternate routing paths
are assigned via the Routing Table, as described in step 3.) If you do not
wish to employ one of the available algorithms, simply accept the default
value and assign only a single routing path.

4-6 Adding or Modifying Subscriber Table Entries

Configuring the Subscriber Table

c. Click Yes on the Systematic Redirect option if you wish all calls to this

subscriber to be redirected to the first alternate address defined in the
Address Table. If you select this option,
original subscriber, and only the first alternate subscriber will be used.
Select No if you do not wish to redirect calls in this way.

d. Click Yes on the Redirect Busy option if you wish calls to this subscriber

to be redirected to the defined alternate addresses when the original
subscriber device is busy. Select No if you do not wish to redirect calls in
this way.

e. Click Yes on the Redirect Out-of-Order option if you wish calls to this

subscriber to be redirected to the defined alternate addresses when the
original subscriber device is down. Select No if y ou do not wish to redirect
calls in this way.

f. Use the Priority field to configure the priority level that will be assigned to

this subscriber’s calls relative to other intra-nodal traffic. The higher the
priority value, the higher the priority assigned to that subscriber’s calls.
(Note that this value does not effect traffic exiting the device.)

g. Click on to create a new entry, or on to edit the entry

currently selected in the Subscriber Table list box.

no calls

will be received by the

3. In the Routing Table:

a. If you wish to modify an existing Routing Table entry, be sure that entry is

selected (and remember, any changes you make to the Routing Table
effect the Subscriber Table entry currently highlighted in the top portion of
the window).

b. In the Path field, enter the index number you wish to assign to the path

you are configuring. These index values will be used in some cases to
determine the order in which the routing paths will be selected; note that
these values must be assigned sequentially.

c. In the LP field, enter the index number of the RLP card which contains the

physical or logical port you wish to use to reach the subscriber device.
Note that, for an FRX4000 and SmartSwitch 1800, this value will always
be zero.

d. In the Port field, enter the index number of the physical or logical port you

wish to use to reach the subscriber device. Index values 0-7 refer to
physical ports on the selected RLP; values 8-63 denote logical ports.

e. Click on to create a new entry, or on to edit the entry

selected in the Routing Table list box. (Note that either adding or
modifying a Routing Table entry automatically modifies the Subscriber
Table entry highlighted in the Subscriber Table list box.)

Adding or Modifying Subscriber Table Entries 4-7

Configuring the Subscriber Table

4. In the Address Table:
a. If you wish to modify an existing Address T ab le entry, be sure that entry is

selected (and remember, any changes you make to the Address Table
effect the Subscriber Table entry currently highlighted in the top portion of
the window).

b. In the Index field, enter the index value you wish to assign to the entry

you are configuring. Allowable values are 1-5; these values need
assigned sequentially.

c. In the Address field, enter the Subscriber ID assigned to the subscriber

device you wish to use as a redirect option for the selected subscriber.
How these addresses are used is dependent upon the redirect options
selected for the Subscriber Table entry you’re modifying. Note that you
cannot use wildcards in this field.

d. Click on to create a new entry, or on to edit the entry

selected in the Address Table list box. (Note that either adding or
modifying an Address Table entry automatically modifies the Subscriber
Table entry highlighted in the Subscriber Table list box.)

5. Click on to exit the window.

not

be

Deleting T able Entries

You can delete individual entries from any of the three tables in the window; keep
in mind, however, that deleting a Routing Table or Address Table entry simply
modiÞes the selected Subscriber Table entry; deleting a Subscriber Table entry
also deletes all associated Routing Table and Address Table entries by default.

Remember, too, that deleting all Routing Table entries for a Subscriber Table entry
invalidates the entry (as no path to the subscriber device is provided); deleting all
Address Table entries for a Subscriber Table entry invalidates any enabled redirect
options, since no redirect addresses will be deÞned.

To delete an entry from any of the tables:

1. Click to select the entry you wish to delete.

2. Click on . The selected entry will be removed. If you have deleted a
Subscriber Table entry, all associated Routing Table and Address Table
entries will also be removed.

4-8 Adding or Modifying Subscriber Table Entries

Chapter 5

Frame Relay Status and
Configuration

About using the frame relay protocol; frame relay port and DLCI rate configuration; configuring frame
relay backup groups; logical port configuration; viewing frame relay management, congestion, and
error stats

FRX and SmartSwitch 1800 ports which have been conÞgured to use frame relay
as their layer 2 protocol can be used to carry both frame relay trafÞc and trafÞc
from other protocols which has been encapsulated in frame relay (per RFC 1490).

Each frame relay port can contain multiple logical ports Ñ up to 56 on an
FRX4000 and SmartSwitch 1800, and up to 56 per RLP on an FRX6000 Ñ and each
logical port is assigned a Data Link Connection IdentiÞer (or DLCI), which
identiÞes a point-to-point connection. All 56 logical ports can reside on one
physical port, or be spread among several ports, and each can be conÞgured to
run one or more layer 3 protocols.

For each physical port conÞgured to run frame relay, four conÞguration windows
and three statistical windows are provided:

¥ The Frame Relay Port ConÞguration window allows you to conÞgure basic

operational parameters related to the frame relay protocol, and displays some
general information about the serial port itself and the line to which it is
connected;

¥ The Frame Relay DLCI Rate ConÞguration window allows you to select the

data rate parameters for each DLCI conÞgured on the selected frame relay
port;

¥ The Frame Relay Backup Groups window allows you to conÞgure backup

groups for primary DLCI connections;

¥ The Logical Port ConÞguration window allows you to conÞgure basic

parameters related to logical port operation;

5-1

Frame Relay Status and Configuration

¥ Frame Relay Management Stats provide an overview of the frame

management (LMI or Annex D) in use on the selected port, displayed via
meters;

¥ Frame Relay Congestion Stats provide information about congestion

notiÞcation and discard eligibility frames being transmitted across the port,
also displayed in meters; and

¥ The Frame Relay Errors window provides a single meter, which displays the

current frame discard rate.

These windows and their functions are described in the following sections.

The statistical windows display their information via the SPMA Meters application; for

TIP

more information on how to manipulate and conÞgure these meters, see the SPMA Tools
Guide.

Configuring Frame Relay Ports

Two conÞguration windows allow you to set frame relay operational parameters
for physical ports and speciÞcations for any DLCI conÞgured for a selected frame
relay port: Frame Relay Port ConÞguration, described below, and Frame Relay
DLCI Rate ConÞguration, described beginning on page 5-8.

Port Configuration

Using the Frame Relay ConÞguration window, you can conÞgure some basic
operational parameters for each of your frame relay ports.

To access the window:

1. Click mouse button 3 on the frame relay port of interest to display the Port
Menu.

2. Drag down to Frame Relay Port Configuration, and release. The Frame
Relay Configuration window, Figure 5-1, will appear.

5-2 Configuring Frame Relay Ports

Frame Relay Status and Configuration

Figure 5-1. Frame Relay Port ConÞguration

The Frame Relay ConÞguration window provides the following information:

Max Bytes per Frame

This Þeld speciÞes the size (in bytes) of the largest frame that can be transmitted
across the port. This value is determined by your frame relay service provider.

Line Speed

This Þeld speciÞes the data transmission rate in bits per second. If this port is a
physical DTE, specify the line speed that matches the speed of the device
connected directly to the port. If the port is a physical DCE (i.e., the attached I/O
cable is DCE) specify the clock speed of the serial port you are conÞguring.

Configuring Frame Relay Ports 5-3

Frame Relay Status and Configuration

Possible line speed entries are:

75 64000 512000 1008000 1472000
150 72000 560000 1024000 1512000
300 112000 576000 1064000 1536000
600 128000 616000 1088000 1568000

1200 168000 640000 1120000 1600000
2400 192000 672000 1152000 1624000
4800 224000 704000 1176000 1664000

9600 256000 728000 1216000 1668000
14400 280000 768000 1232000 1728000
19200 320000 784000 1280000 1792000
24000 336000 832000 1288000 1856000
28800 384000 840000 1344000 1920000
38400 392000 896000 1400000 1984000
48000 448000 952000 1408000 2048000
56000 504000 960000 1456000

If you enter a value that is within the valid range but not equal to one of the
values listed above, the speed will be rounded up. If an RS-232 DCE port is
directly connected to the DTE via the standard Cabletron cable, the maximum
supported speed is 64000. If longer cabling is used, the maximum speed is 19200.

NOTE

N1 Polling Count

The Polling Count speciÞes the number of polling cycles that must pass between
requests for full status reports, which include the status of all PVCs conÞgured on
the physical link. At an interval speciÞed by the T1 Link Integrity Timer
(described below), the logical data terminal equipment (DTE, or user-side
equipment, typically a workstation or router) will send a status enquiry to its
attached DCE (or network-side equipment), requesting the status of the network
link. Each exchange of one enquiry and one response (or status message) deÞnes
one polling cycle. After the number of cycles speciÞed by this value, a request for
a full status report will be sent.

If this port is conÞgured as the logical data communications equipment (DCE), status
enquiries will be initiated at its attached DTE (or user-side equipment), and the local node
will respond with status messages. You can determine which link partner is the logical
DTE and which is the logical DCE (network-side equipment) by checking the Logical
DCE Þeld in this window (described below).

N2 Error Threshold

The error threshold deÞnes the number of link reliability and/or protocol errors
that can occur during the period deÞned by the N3 Monitored Events Count
(described below) before the logical DCE is declared inactive.

5-4 Configuring Frame Relay Ports

Frame Relay Status and Configuration

N3 Monitored Events Count

The monitored events count deÞnes the number of error-free polling cycles that
must occur before the DCE is declared active if the Þrst poll resulted in an error. If
the Þrst poll is error-free, the DCE is declared active immediately.

If the N2 Error Threshold is exceeded during the N3 count, the DCE will be
declared inactive, and the N3 count will be restarted.

T1 Link Integrity Timer

This value determines how often (in seconds) the logical DTE will initiate a status
enquiry to its connected DCE, checking the status of the network link. Note that
this value only has an effect when the selected port has been conÞgured as the
DTE (or user-side equipment); see N1 Polling Count, above, for more
information.

T2 Polling Verification Timer

The T2 Polling VeriÞcation Timer determines how long (in seconds) the logical
DCE will wait for a status enquiry from its attached DTE before recording an
error. This value only has an effect when the selected port has been conÞgured as
the DCE.

NOTE

Maximum Supported VCs

This value deÞnes the maximum number of virtual circuits (or DLCIs) that can be
supported by the selected serial port. This value is generally determined by your
frame relay service provider.

Physical Port Interface

The physical port interface is deÞned by the portÕs connector and cabling type,
and must be conÞgured as follows:

¥ For the FRX4000 and SmartSwitch 1800, port 0 and port 1 are always RS-232;

If you have installed the optional CSU/DSU card on an FRX4000 or SmartSwitch 1800,
it will logically take port 1, and you must conÞgure certain CSU/DSU parameters
through console management. Refer to your FRX or SmartSwitch 1800 hardware
documentation for more information.

¥ For the FRX4000, ports 2 and 3 are determined by the attached cables: RS-232,

V.35, RS-449, or X.21;

¥ For the SmartSwitch 1800, ports 2 and 3 are determined by the attached cables:

RS-232, V.35, or RS-449;

¥ For the FRX4000, ports 4-7 are determined by the expansion Line Interface

Card (LIC) and attached I/O cables. Only the valid interfaces will be listed
from the menu button. Possible interfaces are: RS-232, V.35, RS-449, and X.21.
(RS-449 and X.21 interfaces require an RS-422 LIC.)

Configuring Frame Relay Ports 5-5

Frame Relay Status and Configuration

¥ For the FRX6000, ports 0-7 on each RLP are determined by the Line Interface

Card (LIC) and attached I/O cables. Only the valid interfaces will be listed
from the menu button. Possible interfaces are: RS-232, V.35, RS-449, RS-530 and
X.21. (RS-449, RS-530, and X.21 interfaces require an RS-422 LIC.)

Blocked Flag

This value will cause the port to be enabled (if No) or disabled (if Yes ) when the
device is powered up or re-booted.Whichever state is selected, the port will
remain in that state until this value is changed or until an enable or disable action
is performed.

Logical DCE

This parameter deÞnes the portÕs role as logical DCE (if Yes ) or logical DTE (if
No). The port conÞgured as the DTE serves as the user-side equipment, sending

data to an interface device (DCE, or network-side equipment) for encapsulation in
a frame relay frame and transmission onto the frame relay network. The DTE also
receives de-encapsulated data from the DCE for transmission onto its local
network. Each port must be conÞgured for the opposite value of that conÞgured
for its link partner Ñ that is, a logical DCE must be connected to a logical DTE,
and vice versa.

NOTE

Note that logical and physical DCE and DTE settings are independent of one another; a
port can be both a logical DTE and a physical DCE.

Generate Clock

This setting speciÞes whether the port will generate the clock, or timing,
necessary to synchronize trafÞc over the link. If the port is a physical DCE (as
determined by the portÕs I/O cable interface), specify Yes, since the physical DCE
generates clock. If the port is a physical DTE, specify No.

Receive Clock from DTE

If this parameter is set to Yes, it allows the clock (timing) signal to be looped back
from the DTE using the Terminal Timing (TT) signal, which can be helpful on
high-speed lines. Generally, if the local interface is a physical DCE and the line
speed is above 256 Kbps, this parameter should be set to Yes ; however, make sure
the DTE is conÞgured to provide the terminal timing.

Link Layer Management

When Link Layer Management is active, the protocol in use will verify and
maintain the integrity of the link. The setting of this value determines whether
link status enquiries will be used, and what form they will take:

no LMI No Local Management Interface (LMI). No status

enquiries will be used; this setting essentially disables
frame relayÕs management abilities. LMI will prevent any

5-6 Configuring Frame Relay Ports

Frame Relay Status and Configuration

links from becoming operational unless all DLCI rate
settings match at both ends of the connection; without
LMI, mismatched links may become operational, but
they will behave unpredictably.

LMI rev 1 enquiries from the Local Management Interface (LMI)

will be used;

ansiT1 617 D enquiries in ANSI T1.617 Annex D format (an ANSI

standard LMI) will be used.

Outgoing Rate Control

This parameter determines whether the rate parameters (CIR, BC, and BE)
assigned to the physical link and/or its virtual circuits will be enforced: Yes or
No. Choosing not to enforce rate parameters allows trafÞc rates to exceed those
conÞgured for the selected circuits, possibly impacting performance. Exceeding
CIR may also lead to additional charges from your frame relay provider.

Bandwidth Allocation

If you have conÞgured Bandwidth Allocation Groups for the selected port (or any
logical ports conÞgured for that port), you can use this Þeld to enable (Yes ) or
disable (No) any conÞgured bandwidth allocation parameters. BAGs regulate
bandwidth usage by outgoing trafÞc on the physical link and can ensure that
response time-sensitive trafÞc gets access to the available frame relay bandwidth.
Up to 16 groups can be deÞned and conÞgured through console management
(refer to your FRX or SmartSwitch 1800 hardware documentation for more
information).

Bandwidth allocation groups cannot currently be conÞgured via SPMA; for more

NOTE

information on conÞguring these groups, see your FRX or SmartSwitch 1800 hardware
documentation.

Backup Use Only

This Þeld determines whether all DLCIs on the port will be reserved exclusively
as backups for other DLCIs in the same node. If you select Yes , this port will only
provide backup DLCIs; if you select No, it can provide backup and primary
DLCIs.

If you conÞgure the port for backup use only, make sure no DLCIs on the port
have been conÞgured on an IP, IPX, or LLC2 interface. If this parameter is set to
Yes, the port will remain disabled until needed for backup.

Configuring Frame Relay Ports 5-7

Frame Relay Status and Configuration

Changing Configuration Values

You can edit the values in any Þeld; to do so:

1. To edit a text field, remove the existing value and enter the new value.

2. To edit a field with a menu button, click on the button to display a list of
options, then drag down to select the option you want.

If you have made changes to the fields but would like to revert back to the
previous values, click on the Refresh button.

3. Click on to save your changes.

Applying Port-level Changes

After you have made any port-level conÞguration changes, your changes will not
take effect until you have done an on-line update. To do so:

1. Click mouse button 3 on the port you have been configuring to displa y the P ort
Menu.

2. Drag down to On-line Update and release.

DLCI Rate Configuration

The Frame Relay DLCI Rate ConÞguration window allows you to set
trafÞc-related operational parameters for each DLCI conÞgured for a selected
frame relay port. Note that the values for these parameters will typically be set by
your frame relay provider; they cannot be freely altered.

When conÞguring DLCI rate values in this window, be sure to use the DLCI identiÞers

NOTE

which apply to the logical ports conÞgured for the serial port youÕve selected.

To access the window:

1. Click mouse button 3 on the frame relay port of interest to display the Port
menu.

2. Drag down to Frame Relay DLCI Rate Configuration, and release. The
Frame Relay DLCI Table window, Figure 5-2, will appear.

5-8 Configuring Frame Relay Ports

Frame Relay Status and Configuration

NOTE

Figure 5-2. Frame Relay DLCI Table

The Frame Relay DLCI Table window allows you to conÞgure the following
parameters for each DLCI:

In the DLCI Table you can conÞgure Primary and Backup DLCIs. If you are conÞguring
a primary DLCI, there are six additional parameters that can only be conÞgured through
console management. They are: Remote RLP, Remote Port, Remote DLCI, Switchover
Timer, Switchback Timer, and Time to Hold Data While Waiting. For information on
conÞguring these parameters, refer to your FRX or SmartSwitch 1800 hardware
documentation.

DLCI

Use this Þeld to enter the identiÞer (16 - 991) for the DLCI whose trafÞc
parameters you wish to conÞgure. These DLCI numbers are typically assigned by
your frame relay service provider.

CIR (In/Out)

Use this Þeld to enter the Committed Information Rate (CIR) assigned to the
selected DLCI by your frame relay provider. This value deÞnes the amount of
data guaranteed to be transmitted over the carrierÕs network. Any burst of data

Configuring Frame Relay Ports 5-9

Frame Relay Status and Configuration

above the deÞned CIR can be marked as discard eligible (DE); frames with the DE
bit set are considered to be excess data, and will be discarded if the network
becomes congested.

If congestion occurs on the selected DLCI while throughput is greater than the CIR, and

TIP

the Outgoing Rate Control parameter (settable via the Frame Relay Port ConÞguration
window, described beginning on page 5-2) is set to Yes , the throughput will immediately
drop to the CIR level.

BC (In/Out)

Use this Þeld to enter the Committed Burst Size (BC) assigned to the selected
DLCI by your frame relay provider. The committed burst size deÞnes the
maximum amount of data (in bits) that the network agrees to transfer, under
normal conditions, during a time interval T
intervalÓ) is calculated by dividing the committed burst size (BC) by the
committed information rate (CIR); it deÞnes the time interval during which the
user can send only BC amount of data and BE excess data (see deÞnition of BE,
below). Any trafÞc which exceeds this burst rate will be marked discard eligible
(DE), and discarded if the network becomes too congested. While sustained BC
trafÞc rates are not guaranteed, BC trafÞc has a higher delivery probability than
BE (described below).

. TC (also called the Òbandwidth

C

TIP

You can view the amount of trafÞc on the selected physical interface which is marked as
discard eligible via the Frame Relay Congestion Stats window, described beginning on

page 5-22.

BE (In/Out)

Use this Þeld to enter the Excess Burst Size (BE) assigned to the selected DLCI by
your frame relay provider. The excess burst size deÞnes the amount of data (in
bits) over the committed burst size (BC) that the network will attempt to transfer
during the time interval TC (remember, TC is calculated by dividing the
committed burst size (BC) by the committed information rate (CIR)). Any data
exceeding this value will be buffered in the FRX device. Note that DE frames are
considered to be BE excess data.

BECN

The BECN Recovery Count provides a means for controlling the rate of return to
maximum trafÞc ßow after it has been reduced due to congestion. If a packet is
received on the selected DLCI with the BECN (backward explicit congestion
notiÞcation) bit set, the conÞgured BE Out value will be ignored and the effective
value will become zero (limiting trafÞc ßow to the value conÞgured for BC Out).
This limit will remain in place until the DLCI receives a speciÞed number of
sequential packets without the BECN bit set: the number speciÞed by the BECN
Recovery Count. Each time the conÞgured number of sequential packets is
received, the effective BE Out will be increased by one-eighth of the conÞgured
value.

5-10 Configuring Frame Relay Ports

NOTE

Frame Relay Status and Configuration

Priority

The Outgoing DLCI Priority value allows you to assign relative priority levels to
the DLCIs conÞgured on the selected physical port. The allowable range is 0-4,
with 0 being the lowest priority.

Backup Group Number

Use this Þeld to specify whether this DLCI is a primary or a backup DLCI. If it is a
primary DLCI, enter the number (1-255) that identiÞes the Frame Relay Backup
Group that will take over if this DLCI fails. If it is a backup DLCI, enter 0. A DLCI
cannot be both a backup and a primary DLCI.

If you are conÞguring a primary DLCI, you must set this value to 0 until you have
conÞgured a Frame Relay Backup Group (see ConÞguring a Frame Relay Backup Group,

page 5-13). Then, re-access the Frame Relay DLCI Table and specify the desired backup

group.

This parameter is applicable only on an initiating node, which is the node that
will initiate the switchover to a backup DLCI. At switchover, the initiating node
notiÞes the remote (non-initiating) node of the change. Do not conÞgure a Backup
Group Number on this DLCI at the remote (non-initiating) end.

Backup Protocol

This Þeld is only conÞgurable if the Backup Group Number is set to 0, indicating
that the DLCI being conÞgured is a backup DLCI. Set this Þeld to Enabled if this
DLCI will be used as a remote (non-initiating) backup. The DLCI will wait for a
backup protocol message from the initiating end, telling the backup where to
send the rest of the messages. Set this Þeld to Disabled if this DLCI is an initiating
backup.

State

Although it appears to be a settable parameter, the value displayed in the State
Þeld simply indicates the internal status of the entry you are conÞguring: active,
inactive, or invalid. The value displayed here indicates only the deviceÕs efforts to
add the entry to its MIB table.

Changing DLCI Rate Values

To edit the rate values assigned to each conÞgured DLCI:

1. If you wish to modify an existing entry, be sure that entry is highlighted in the

list box portion of the window.

2. Enter and/or edit the values displayed in the text boxes, as desired.

(Remember, some values which are settable from this window must mirror
values received from your service provider or configured elsewhere; be sure
these values match as necessary.)

Configuring Frame Relay Ports 5-11

Frame Relay Status and Configuration

3. Click on to create a new entry, or on to edit the entry
currently selected in the list box.

Applying Port-level Changes

After you have made any port-level conÞguration changes, your changes will not
take effect until you have done an on-line update. To do so:

1. Click mouse button 3 on the port you have been configuring to displa y the P ort
Menu.

2. Drag down to On-line Update and release.

Frame Relay Backup Groups

Frame Relay Backup Groups provide frame relay DLCIs with automatic backup
protection should a DLCI fail. DLCIs are conÞgured as either ÒprimaryÓ DLCIs or
ÒbackupÓ DLCIs. This is done either in console management (refer to your FRX or
SmartSwitch 1800 hardware documentation) or in the Frame Relay DLCI Rate
ConÞguration window (see DLCI Rate ConÞguration, page 5-8).

NOTE

In a backup conÞguration, one end of the link is considered the ÒinitiatingÓ node
and the other is the ÒremoteÓ, or non-initiating, node. The initiating end is the
node that will establish the backup DLCI if it discovers that the primary DLCI is
down. A node can be the initiating node for some backup conÞgurations, and the
remote node for others.

On the initiating node, backup DLCIs are assigned to backup groups. Each group
can contain up to ten backup DLCIs. A backup group is then assigned to one or
more primary DLCI; each DLCI can have just one backup group.

If a node detects a failure in a primary DLCI connection, it will search the backup
group assigned to that primary DLCI, and will select the Þrst available DLCI in
that group as a backup. The backup will become operational and will remain in
that state until the primary becomes active again. If the backup fails while in use,
the node will check the status of the primary, then (if necessary) search the
primaryÕs backup group for another backup.

Any sessions in progress when a primary DLCI goes down will not be transferred directly
to the backup DLCI, but will be reset, then established on the backup.

Before conÞguring Frame Relay Backup Groups, you should Þrst conÞgure all the
primary and backup DLCIs using either console management (refer to your FRX
or SmartSwitch 1800 hardware documentation) or the Frame Relay DLCI Rate
ConÞguration window (see DLCI Rate ConÞguration, page 5-8). All DLCI

5-12 Frame Relay Backup Groups