Cabletron Systems Netlink FRX4000, FRX6000, Netlink FRX6000 User Manual

Download

Page 1

The Complete Networking Solution

FRX

Frame Relay Access Products

FRX

4000

User Guide

FRX

For Release 4.0

6000

09-41-06-162-01

Page 2

Page 3

Cabletron Systems reserves the right to make changes in specifications an d other information contained in t his document without prior notice. The reader should in all cases consult Cabletron Systems to determine whether any such changes have been made.

The hardware, firmware , and/or softwa re described in this manual is s ubject 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.

All rights reserved. This Cabletron product includes softwar e dev eloped by the University of California, Berkeley, and its contributors. IP software is provided by the regents and contributors “as is” and any express or implied warranties, including, but not lim ited to, the implied warranties of merchantability a nd fitness for a parti cular purpose, are disclaimed. In no eve nt shall the regents or contributors be liable for any direct, indirect, incidental, special, exemplary, or consequen tial damages (inc luding, but not limi ted to, procurement of substit ute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (includi ng negligence or otherwise) ari si ng in any way out of the use of this software, even if advised of the possibility of such damage.

Gateway Daemon (GateD) software, Release 3.5.5, is maintained and developed by Cornell University and its collaborators. The version of GateD used with this Cabletron product has been modified.

Netlink is a trademark of Cabletron Systems, Inc. All other product designa tions are the property of their respective owners.

Statements of Compliance

FCC

This devi ce complies wit h Part 15 of the FCC rules. Operation is subject to the following t wo conditions : ( 1) this devic e ma y not c ause harmful int erferen ce, and (2) this devi ce m ust acc ept any interference received, includi ng interference that may cause undesired operati on.

This equipment has been tested and found to comply with the limits for a Class A digital device, pursua nt to P art 15 of the FCC rules. These limits are designed to provide rea s onable protection against harmful interference whe n the equipment is operated in a commercial environment. This equip ment uses, generates, and can radiate radio frequency energy and if not installed in accordance with the operator’s manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause interference in which case the user will be required to correct the interference at his own expense.

Changes or modificat ions made to this device which are not expressly approved by Ca bl etr o n Sys tem s co ul d vo id the us er ’s aut hori ty to operate the equipment.

iii

Page 4

DOC

About This Manual

Terminology and Conventions

This digit al apparatus does not exceed the Cla ss A limits for radi o noise emiss ions from digita l apparatus set out in the Radio Interference Regulations of the Canadian Depa rtment of Communicatio ns.

Le présent appareil numérique n’émet pas de bruits radioélectriques dépassant les limites applicables aux appareils numériques de la class A prescrites dans le Règlement sur le brouillage radioélectrique édicté par le ministère des Communications du Canada.

Rev Date Reason for Update 01 March 1998 General availability

This manual su pplem ents sc reen pro mpts and menus as an ai d in con figu ring t he dat abase a nd performing system operations on a Netlink FRX4000 or FRX6000. Before using the manual , you should be familiar with FRX hardware, as well as the protocol s (frame relay, IP, SNA, etc.) you will be using.

This typeface represent s general te xt.

(This text is dark cyan in on-screen versions of the manual, and black in paper versions.)

This typeface represents keyboard input and video output.

In on-screen versions of the manual, items in blue are links to other places in the manual.

This symbol points to a n infor mation al note re latin g to the te xt, ta ble, or fig ure tha t immediately precedes or follows it.

This symbol and t ext identif ies a caution ary n ote, t he conten t of whi ch is more critical to heed than an informational note.

The following reference s to keyboard keys appear in the manual and /or on the screen:

[N]

is a reference to a key on your keyboa rd (where “N” is the key).

Enter Type

typed (e.g., “type

Press

means that you should type in the information, then press the

is similar to

Enter

, except that the word “

n [Enter]

”).

means press (hit, strike) the key once. Pressing the

[Enter]

” follows the information to be

[Enter]

necessary.

[Ctrl]

followed by one or two other key designations, must be str uck s im ultaneously

with the other keys s hown.

If a stat emen t ends wi th a re feren ce to a key—for exampl e, “. ...t hen pr ess

is not part of the data to be entered. If a period should be entered, it will be shown as same applies to all other punc tuati on. When ins tructe d to, for exa mple, “ press Main Menu,” this means press

[A]

, then

[B]

[A] comma [B]

, not

[Enter]

key.

key afterwards is not

[Enter].

”—the period

[.]

[A], [B]

from the

. The

Screen Displays

Screen Displays are provide d to show the genera l appear ance of actua l scree ns. They are only examples—the in formation shown is not always repres entative of an operational system.

iv FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 5

Table of Contents

Section I Getting Started

Chapter 1 Product Overview

Introduction to Netl ink FRX4000 and FRX6000..................................... 1-1

Multiprotocol Support........................................................................ 1-2

Management Functions...................................................................... 1-2

Hardw a r e O v er v i ew .... .. ... ...... ... .. ....... .. ....... .. .. ....... .. .. ....... .. ....... .. ... ...... ... 1-3

FRX4000............................................................................................ 1-3

FRX6000............................................................................................ 1-4

Chap ter 2 Getting Starte d

Quick Start................................................................................................ 2-1

Port Assignment Worksheets................................................................... 2-2

FRX4000............................................................................................ 2-2

FRX6000............................................................................................ 2-3

Logging into the Main Menu...... ............. .................................. ............. .. 2-6

Reviewing Boot Messages................................................................. 2-7

Moving Through the Menus.... ....................... ........................ .......... . 2-8

Setting the Date and Time.............. .................................. ...................... 2-11

Changing the Login Password........ .................................. ............. ......... 2-11

Stopping Operation................................................................................. 2-12

Logging Out........... .................................. .................................. ...... 2-12

Rebooting......................................................................................... 2-12

Shutting Down............................ ............. ............. .......... .. ............... 2-12

What Next?............................................................................................. 2-12

Section II Configuration

Chapter 3 Introductio n to Databas e Configuration

Database Setup Recommendations .......................................................... 3-1

Configuration Examples.......... .......... .. ........................ ............................. 3-2

Legacy Protocols over Frame Rela y via Logica l Ports...................... 3-2

Frame Relay PVC Passthrough................ ............. .......... .. ................. 3-3

LLC2 PUs over Frame Relay to AS/400 ........................................... 3-3

3x74s/SDLC over Frame Relay to SNA Host ................................... 3-8

Producing a Configurati on Report ............. ............. ............. .......... ........ 3-10

Where to Find Configuration Inf ormation ......... ....................... ............. 3-10

Chapter 4 Configuring Node-Wide Default Parameters

Node Defaults................................................... .................................. ...... 4-1

Database and System Memory Values .............................................. 4-2

Node Defaults Parameters ................................................................. 4-3

Warning Messages .............................. ........................ .......... .. ............... 4-10

Chapter 5 Configuring Cards and Protocols

FRX4000.................................................................................................. 5-1

Protocols and LIC.............................................................................. 5-1

LAN Port................... ............. ............. .......... .. ........................ .......... . 5-6

Page 6

FRX6000.................................................................................................. 5-7

RLPs and Protocols............................................................................ 5-7

LAN Cards.......... .. .................................. ........................ ................. 5-14

Chapter 6 Configuring Physical Ports

Locations of Physical Ports...................................................................... 6-1

FRX4000............................................................................................ 6-1

FRX6000............................................................................................ 6-2

Database and System Memory Values..................................................... 6-3

Configuring a Physical Port............ .. .......... ............. ............. .......... ......... 6-3

Chapter 7 Configuring Frame Relay

Introduction.............................................................................................. 7-1

DLCI Sharing..................................................................................... 7-2

Frame Relay Backup.......................................................................... 7-2

Required Configuration ..................................................................... 7-5

Configuring Bandwidth Alloc ation Groups............... .............................. 7-6

Bandwidth Allocation Group Paramet ers............... ............. .............. 7-7

Configuration Example........................ .......... ............. ............. .......... 7-8

Configuring Frame Relay Ports................ .................................. ............. . 7-9

Reviewing DLCI Configuration (Figure 7-4, Item C)..................... 7-10

Configuring DLCI Parameters ( Figure 7-4, Item D)............. .......... 7-12

Viewing Learned DLCIs (Figure 7-4, Item E) ................................ 7-13

Frame Relay Port Parameters .......................................................... 7-14

Configuring Frame Relay PVCs Across the Node................................. 7-20

Frame Relay PVC Parameters ......................................................... 7-21

Configuring Frame Relay Backup Groups........................ ............. ........ 7-22

Backup Group Parameters................................................... ............ 7-23

Chapter 8 Configuring X.25

Introduction.............................................................................................. 8-1

Required Configuration ..................................................................... 8-2

Configuring a Physical X.25 Port ....................................... ..................... 8-2

Configuring Closed User Groups ...................................................... 8-4

Configuring a Network Trunk........... .................................. .............. 8-5

Configuring a Dial Port ........ ............. .................................. ............. . 8-6

Physical X.25 Port Parameters ............... ............. .............................. 8-6

Configuring Logical X.25 Ports............. ............. .......... .. ....................... 8-14

Logical Port Parameters................................................................... 8-15

Configuring Subscri ber IDs ....................................... ............................ 8-21

Subscriber Addressing....................... .................................. ............ 8-22

Hunt Group Example....................................................................... 8-24

Subscriber Parameters...................................................................... 8-25

Configuring X.25 Address Translation Templates ............... ................. 8-27

Translation Template Parameters . .... .. ....... .. ..... .... ..... .. ..... .... ..... .... .. 8 -30

Replacing Called/Calling Address or User Data ............... ............. . 8-30

Replacing Protocol ID ..................................................................... 8-31

Replacing Facilities ......................................................................... 8-31

Translation Examples ...................................................................... 8-32

Testing a Translation Templa te.................... .......... .. ....................... 8-32

Configuring X.25-to-X.25 PVCs .................. ........................ ................. 8-33

vi FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 7

X.25 PVC Parameters...................................................................... 8-34

Chapter 9 Configuring SNA

Introduction. ............................................................................................. 9-1

Required Configuration ..................................................................... 9-3

Configuring an SNA Port......................................................................... 9-4

SNA Po rt Pa r a m e t ers ..... .. ....... .. ... ...... ... ...... ... .. ....... .. .. ....... .. ....... .. .. ... 9-6

Configuring Subscri ber IDs. ............. .................................. .................... 9-14

Subscriber Parameters...................................................................... 9-15

Configuring a Hunt Group for SNA Subscribers............................. 9-17

Configuring LLC2........ .. .......... ............. ............. .......... .. ........................ 9-17

Configuring a Virtual LAN ID.................................... .................... 9-17

Configuring LLC2 Hosts................................................................. 9-18

Configuring LLC2 Interfaces........................................................... 9-26

Chapter 10 Configuring BSC Interactive

Introduction. ........................................................................................... 10-1

Configuring BSC Interactive Port Records........ ....................... ............. 10-2

BSC Interactive Port Parameters ..................................................... 10-4

Configuring Subscri ber IDs. ............. .................................. .................... 10-8

Subscriber Parameters...................................................................... 10-9

Configuring BSC Interactive Devices......................... .......... ............. .. 10-11

BSC Interactive Device Parameters............................................... 10-12

Chapter 11 Configuring BSC Batch

Introduction. ........................................................................................... 11-1

Configuring BSC Batch Port Records.......... ............. ............................. 11-2

BSC Batch Port Parameters ............................................................. 11-3

Configuring Subscri ber IDs. ............. .................................. .................... 11-8

Subscriber Parameters...................................................................... 11-9

Chapter 12 Configuring Async Ports

Introduction. ........................................................................................... 12-1

Configuring Async PAD Profiles.......... ............. .......... ............. ............. 12-2

PAD Pro file Pa ra m e t er s........ ....... .. ....... .. .. ....... .. ....... .. .. ....... .. ... ...... . 12-2

Configuring Async PAD Login Parameters.............. .. .......... ............. .... 12-6

PAD Login Parameters.................................................................... 12-7

Configuring Async Port Record s ..................................... ...................... 12-8

Async PAD Port Parameters............. ........................ ............................. 12-9

Configuring Subscri ber IDs. ............. .................................. .................. 12-15

Subscriber Parameters.................................................................... 12-16

Configuring Abbrevia ted Addresses......................... ........................... 12-17

Configuring Async PVCs........... ............. .................................. ........... 12-18

Async PVC Parameters.......... ............. .................................. ......... 12-19

Chapter 13 Configuring IP

Introduction. ........................................................................................... 13-1

IP Addressing................................................................................... 13-1

Using the Node as an IP Gateway ................................................... 13-3

Required Configuration ................................................................... 13-3

Configuring IP Node Defaults...... ............. .......... .. ........................ ......... 13-4

IP Node Defa ults Parameters.... ..... .. ....... .. ..... .... .. ..... .... ..... .... ..... .. ... 13-5

vii

Page 8

Configuring IP Interfa ces.......... ............. ............. .......... ............. ............ 13-5

IP Interface Parameters.................................................................... 13-8

Configuring Static IP Routes................................................................ 13-15

IP Routing Parameters................................................................... 13-16

Chapter 14 Configuring IPX

Introduction............................................................................................ 14-1

Required Configuration ................................................................... 14-1

Configuring IPX Node Defaults........................ .................................. ... 14-2

IPX Node Defaults Parameters......... ..... .... .. ..... .... ..... .. ....... .. ..... .... .. 14-2

Configuring IPX Filter s..................... .......... ............. ............. .......... ....... 14-3

Configuring Filter Definitions......................................................... 14-3

Configuring IPX Filter Applications ............... ............. ................... 14-8

IPX Filter Applications P ara meters..................... ............................ 14-9

Configuring IPX Interfa ces......... ............. .................................. ............ 14-9

IPX Interface Parameters............................................................... 14-10

Parameter Descriptions.................................................................. 14-13

Configuring Static IPX Routes............................... ........................ ...... 14-16

IPX RIP Static Route Parameters .................................................. 14-17

IPX SAP Static Route Parameters ................................................. 14-18

Chapter 15 Configuring Bridging

Introduction............................................................................................ 15-1

Required Configuration ................................................................... 15-2

Configuring Default Node-Wide Bridging Parameters.......................... 15-3

Bridge Node Default Parameters............ ........................ ................. 15-4

Configuring Bridge Filte rs .............................. ............. .......... ............. ... 15-6

Configuring Filter Definitions......................................................... 15-6

Configuring Bridge Filte r Applications........................ ................. 15-10

Configuring Bridge Port s................... ............. ............. .......... ............. . 15-12

Bridge Port Parameters .................................................................. 15-13

Chapter 16 Configuring SNMP

Introduction............................................................................................ 16-1

Configuring SNMP System Defaults.................................................. ... 16-2

System Defaults Parameters............................................................ 16-2

Configuring a Community Table ................ .. ........................ .......... .. ..... 16-3

Community Table Parameters . ........................................................ 16-4

Configuring Trap Routing...................................................................... 16-4

Trap Routing Parameters................................................................. 16-5

Configuring a Model Number................................................................ 16-6

Section III Operatio n

Chapter 17 Introduction to System Operation Chapter 18 On-line Operations

Remote Control...................................................................................... 18-1

Remote Control from an FRX4000/6000........................................ 18-2

Remote Control via an Async PAD Port............. ............................ 18-3

Transferring Files and Updating Software............................................. 18-4

Remote File Transfer ....................................................................... 18-4

viii FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 9

Remote Software Update................................................................. 18-5

Backing Up and Restoring Files............................................................. 18-6

Database Backup and Restore.............. ............. ............. .......... .. ...... 18-6

Copying an FRX4000 Directory to/from a PC................................ 18-8

FRX4000 Local File Backup and Restore....................................... 18-9

Enable/Disable Operations................................................................... 18-12

Disabling and Enabling Ports........................................................ 18-12

Quiescing and Unquiescing Ports............................ ............. ......... 18-13

Disabling and Enabling SDLC PUs.................................... ........... 18-14

Tests...... ........................ .................................. ............. .......... ............. .. 18-15

IP Ping Connectivity Test............................................ .................. 18-15

FRX4000 CSU/DSU Tests ............................................................ 18-16

Reloading Auxiliary Cons ole Initialization................................... ....... 18-16

Initiating Frame Rela y Backup Switchover/Switchback...................... 18-17

Chapter 19 Stat us Di spla ys

Displaying Node Status.......................................................................... 19-1

Displaying Port Status............................................................................ 19-2

Displaying Virtual Conn ections..................... .................................. ...... 19-3

Displaying Port Signals.......................................................................... 19-6

Monitoring Traffic.................................................................................. 19-7

Serial Ports....................................................................................... 19-7

Monitoring LAN Traffic................................................................ 19-17

Displaying Frame Relay Backup Stat us.............. ............. .................... 19-19

Displaying SDLC PU Status ................................................................ 19-20

Displaying LLC2 Session Statu s............................. ............. .......... .. .... 19-21

Bridge Status Displays....................................................... .................. 19-21

Bridge Port Status .......................................................................... 19-21

Bridge Forwarding Table............................................................... 19-23

IP Status Displays.................... .......... ............. ............. .......... .. ............. 19-24

IP Routing Table............................................................................ 19-24

ARP Table...................................................................................... 19-25

IP Interfaces ................................................................................... 19-25

IPX Status Displays................................................. ............. .......... ...... 19-27

RIP Table ....................................................................................... 19-27

SAP Table ...................................................................................... 19-27

Chapter 20 Statistics Displays

RLP Statistics........... ........................ .......... .. ........................ .................. 20-1

Configuring RLP Statistic s Thresholds ........................................... 20-2

Port St at i st i cs.... .. ....... .. .. ....... .. ... ...... ... ...... ... .. ....... .. ....... .. .. ....... .. .. ....... .. . 20-3

Configuring Port Statistics Thresholds............................................ 20-4

Frame-level Stati stics ................................................ ............................. 20-5

Frame Relay Utilizatio n Statistics............................................. ............. 20-6

LAN Card Statistics Displays................................................................. 20-8

Bridge Port Statistics............................................................................ 20-10

IP Statistics Displays............................................................................ 20-12

IP Statistics .................................................................................... 20-12

ICMP Statistics........... ........................ .......... .. ........................ ....... 20-13

IP Interface Statistics ........................................ ............. .......... .. .... 20-16

IPX Statistics Displa ys........................ ............. .................................. .. 20-17

Page 10

Chapter 21 Syst em Eve nts

Configuration ......................................................................................... 21-1

Alarm Buffer .......................................................................................... 21-2

Event Generation.............. ............. .................................. ....................... 21-3

Displaying Events ......... .................................. ............. .......... .. .............. 21-3

Severity Levels for SNMP Trap Routing.......... .................................. ... 21-4

Event Messages ...................................................................................... 21-4

Messa g e s............ .. .. ....... .. .. ....... .. ....... .. ... ...... ... ...... ... .. ....... .. .. ....... .. .. 21-4

Section IV Appendices

Appendix A Async Terminal Operations

Comman d and D at a Tran s fer M ode s ..... .. ..... .... ..... .... .. ..... .... ..... .. ....... .. ... A-1

Async Terminal Commands............................ .................................. ...... A-2

Placing a Call from an Async Terminal.................................................. A-2

Async PAD Service Signals....................... .......... .. ........................ ......... A-3

Error Codes Sent to Async PAD Port ..................................................... A-5

Appendix B Cause and Diagnostic Codes

Cause Codes ............................................................................................. B-1

Clearing Causes ................................................................................. B-1

Reset Causes ...................................................................................... B-2

Restart Causes.................................................................................... B-2

Diagnostic Codes...................................................................................... B-2

X.25 Codes ........................................................................................ B-2

SNA Codes ........................................................................................ B-4

Codes Specific to Cabletron Fra me Relay Access Devices............... B-4

Appendix C NetView Management

Local NetView Access............................................................................. C-2

Supported Commands............ .................................. ............. .......... .. ....... C-3

Display Commands............................................................................ C-3

Vary Commands ................................................................................ C-4

Modify Commands............................................................................ C-4

Appendix D ASCII Character Table Appendix E Menu Structure Glossary Index

x FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 11

List of Figures

1-1 Network Example............................ ........................ ............................. 1-1

2-1 Physical Ports on FRX4000........................ .................................. ........ 2-2

2-2 Physical Ports on an FRX6000 RLP ..................................................... 2-3

2-3 Port Status Display ............................................................................... 2-6

2-4 Main M en u ...... .. ... ...... ... ...... ... .. ....... .. .. ....... .. ....... .. .. ....... .. ... ...... ... ...... ... 2-7

3-1 Configuration Example 1...... ............. .................................. ................. 3-2

3-2 Configuration Example 2...... ............. .................................. ................. 3-3

3-3 Configuration Example 3...... ............. .................................. ................. 3-3

3-4 Local FRX4000/6000 in Configura tion Example 3........... ............. ...... 3-4

3-5 Remote FRX4000/6000 in Configurat ion Example 3.......................... 3-5

3-6 Configuration Example 4...... ............. .................................. ................. 3-8

4-1 Node Defaults Configurat ion Screen 1............................................. .... 4-1

5-1 Serial Ports on an FRX4000 ................................................................. 5-2

5-2 Protocol Configuration Menu for FRX4000......................................... 5-2

5-3 LAN Port Configuration Record ........................... ............................... 5-6

5-4 FRX6000 RLP, LICs, and Cables......................................................... 5-8

5-5 RLP Configuration Menu for FRX6000............................................... 5-9

5-6 LAN Card Configuration Screen................. ..... .... .. ..... .... ..... .. ....... .. ... 5-15

6-1 Physical Ports on FRX4000........................ .................................. ........ 6-1

6-2 Physical Ports on FRX6000 RLP ........ .................................. ............. .. 6-2

6-3 D ef a u lt Co n f i g u rat i on Scree n fo r N ew Po r t ........... ... .. ....... .. .. ....... .. ..... 6 -4

7-1 Frame Relay Backup Examples............................................................ 7-3

7-2 Bandwidth Allocation Group Menu......................... ............. ............. .. 7-7

7-3 Frame Relay Port Screen 1 ................................................................... 7-9

7-4 Frame Relay Port Screen 2 ................................................................. 7-10

7-5 DLCI Configuration Review Screen ................................................ .. 7-10

7-6 Frame Relay DLCI Configuration Scre en 1............... ........................ 7-12

7-7 Frame Relay DLCI Configuration Scre en 2............... ........................ 7-13

7-8 Frame Relay PVC Configuration.............. ............. ............................. 7-21

8-1 X.25 Port Screen 1................................................................................ 8-3

8-2 X.25 Port CUG Parameters................................................................... 8-4

8-3 X.25 Port Trunk Parameters................................................................. 8-5

8-4 X .2 5 D ia l Po r t Parame t er s ....... ....... .. .. ....... .. ....... .. .. ....... .. ....... .. ... ...... ... 8-6

8-5 Logical Port Screen 1.......................................................................... 8-14

8-6 Typical SVC Subscriber Screen ................ .... ..... .. ..... .... .. ....... .. ..... .... . 8 -2 2

8-7 W i ld c a rd A d dr e s s in g E xa mp l e .. ....... .. ....... .. .. ....... .. ....... .. ... ...... ... .. ..... 8 - 2 3

8-8 Backup Using Address Translat ion............................ ............. ........... 8-28

8-9 Address Translation Templa tes Display............ ............. .................... 8-28

8-10 Address Translation Templa te Screen...... ............. ............................. 8-29

Page 12

8-11 Address Translation Tes t Scree n............... .. .................................. ..... 8-33

8-12 X.25-to-X.25 PVC Screen .................................................................. 8-34

9-1 SDLC and LLC2 Examples.................................................................. 9-3

9-2 SN A P o rt Sc r e en 1.. ....... .. ....... .. .. ....... .. .. ....... .. ....... .. ... ...... ... .. ....... .. ...... 9-4

9-3 SDLC PU Subscriber Parameters Screen ............................................. 9-5

9-4 Typical SVC Subscriber Screen . ..... .... .. ....... .. ..... .... ..... .. ..... .... ..... .... .. 9-14

9-5 LLC2 Defaults Configurat ion Scr een.............................................. ... 9-18

9-6 LLC2 Originated Host Configuration Screen........ .. ..... .... ..... .... ..... .. .. 9-19

9-7 LLC2 Terminated Host Configuration Screen .................................. . 9-19

9-8 LLC2 Host Connections Screen......................................................... 9-20

9-9 LLC2 Interfaces Display .................................................................... 9-26

9-10 Bridge Port/LLC2 Interface Record , Et hern et.................. ..... .... ..... .. .. 9-27

9-11 Bridge Port/LLC2 Interface Record , Fr am e Rel ay.................... ..... .. .. 9-27

10-1 BSC In t eractiv e Po rt Rec o rd ...... .. ... ...... ... .. ....... .. .. ....... .. ....... .. .. ....... .. 10-2

10-2 BS C Int era ct ive Po r t Re cord , Sc reen 3 ............. .... .. ..... .... ..... .... ..... .. .. 10-3

10-3 Typical SVC Subscriber Screen . ..... .... .. ....... .. ..... .... ..... .. ..... .... ..... .... .. 10-8

10-4 BSC Interactive Devices Screen....................................................... 10-12

11-1 BSC Batch Port Record ...................................................................... 11-2

11-2 BSC Batch Port Record, Screen 3 ...................................................... 11-3

11-3 Typical SVC Subscriber Screen . ..... .... .. ....... .. ..... .... ..... .. ..... .... ..... .... .. 11-8

12-1 Async PAD Login Parameters Screen........................... ..................... 12-7

12-2 Async PAD Port Screen ............ ............. .................................. .......... 12-8

12-3 Typical SVC Subscriber Screen ....................................................... 12-15

12-4 Async-to-X.25 PVC Record.......................... .................................. . 12-18

13-1 IP Node Defa ults Menu......... ............. .................................. .............. 13-4

13-2 IP Interface Record – Frame Relay Example ..................................... 13-6

13-3 LAN IP Interface – Secondary Address Configuration...................... 13-7

13-4 IP Routing Record ............................................................................ 13-15

14-1 IPX Node Defaults Menu........................ ............. ............. .......... .. ..... 14-2

14-2 IPX SAP Filter Record ....................................................................... 14-4

14-3 Typical IPX Filter Applications Record............... ............. ................. 14-8

14-4 IPX Interface Record Example........................................................... 14-9

14-5 IPX RIP Route Record ............ ............. .................................. .......... 14-16

15-1 Bridge Node Defaults Configur at ion Screen................................... ... 15-3

15-2 Bridge MAC Filter Configuration Screen .......................................... 15-7

15-3 Typical Bridge Filter Applications Record .............. .......... ............. . 15-11

15-4 Bridge Ports Display...................... .......... .. ........................ ............... 15-12

15-5 Bridge Port Record Example............................................................ 15-13

16-1 SNMP System Defaults Menu............................................................ 16-2

16-2 SNMP Community Table Menu . ........................................................ 16-3

16-3 SNMP Trap Routing Menu................................................................. 16-4

x FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 13

17-1 Main Menu...... .. ... ...... ... ...... ... .. ....... .. .. ....... .. ....... .. .. ....... .. ... ...... ... ...... . 1 7 - 1

18-1 On-Line Port Operations Menu.................. ............. .......... ............. .. 18-12

18-2 On-Line SDLC PU Operations Menu.................. ............. .......... ...... 18-14

18-3 IP Ping Connectivity Test Menu.......................... ............. .......... ...... 18-15

18-4 Ping Example..................................... ............. .......... .. ...................... 18-16

19-1 Node Status Display ........................................................................... 19-1

19-2 Port Status Display ............................................................................. 19-2

19-3 Virtual Connections Display on Frame Relay Port ............................ 19-3

19-4 Virtual Connections Display on Non-Frame Relay Port......... ........... 19-5

19-5 Port Signals Display ........................................................................... 19-6

19-6 X.25 Line Monitor Display................................................................. 19-9

19-7 Frame Relay Line Monitor Display................ ....................... ........... 19-12

19-8 LAN Capture Status and Control Menu.................................... ....... 19-17

19-9 LAN Capture Display............. ............. .................................. ........... 19-18

19-10 SDLC PU Status Displa y................................ .................................. 19-20

19-11 Bridge Port Status Display................................................................ 19-21

19-12 Bridge Forwarding Table Display.................................................... 19-23

20-1 RLP Statistics Display......................... .................................. ............. 20-1

20-2 RLP Statistics Configur at ion Menu................................ .................... 20-2

20-3 Port Statistics Display......................................................................... 20-3

20-4 Port Statistics Configuration Menu .................................................... 20-4

20-5 Frame-level Stati stics Display........... .. .................................. ............. 20-5

20-6 Frame Relay Utilization Statistics Display......................................... 20-7

20-7 LAN Card Statistics Display . ............................................................. 20-8

20-8 Bridge Port Status Display................................................................ 20-10

20-9 IP Statistics Display.......................................................................... 20-12

20-10 ICMP Statistics Display..................... ............. .......... .. ...................... 20-13

20-11 IP Interface Statistics Display........................................................... 20-16

20-12 IPX Statistics Display........................ ............. .......... .. ...................... 20-17

21-1 Event Reporting Configuration Example ........................................... 21-2

C-1 NetView Access Options Menu................ ............. ............................... C-2

Page 14

List of Tables

2-1 FRX4000 Port Assignments................................................................. 2-2

2-2 FRX6000 Port Assignments................................................................. 2-4

2-3 Date and Time Parameters.................................................................. 2-11

3-1 MAC Address Conversion.................................................................... 3-6

4-1 Node Defaults Parameters.................................................................... 4-3

4-2 NetView Parameters......................... ............. ....................................... 4-7

5-1 FRX4000 Protocol Parameters............................................................. 5-3

5-2 LAN Card Parameters on FRX4000..................................................... 5-7

5-3 FRX6000 RLP Parameters ................................................................. 5-10

5-4 LAN Card Identification in FRX6000................................................ 5-14

5-5 LAN Card Parameters on FRX6000................................................... 5-15

7-1 Bandwidth Allocation Group Paramet ers............... .............................. 7-7

7-2 Bandwidth Allocation Example............................................................ 7-8

7-3 Frame Relay Port Parameters ............................................................. 7-14

7-4 Frame Relay DLCI Parameters........................................................... 7-15

7-5 Frame Relay PVC Parameters ............................................................ 7-21

7-6 Frame Relay Backup Group Parameters ..... .... ..... .... ..... .. ..... .... .. ....... .. 7-23

8-1 Physical X.25 Port Parameters ........................... ............. ..................... 8-6

8-2 X.25 Port CUG Parameters ................................................................ 8-12

8-3 X.25 Port Dial Parameters .................................................................. 8-13

8-4 Logical Port Parameters...................................................................... 8-15

8-5 Logical Port CUG Parameters............................................................ 8-16

8-6 Subscriber Parameters ........................................................................ 8-25

8-7 Translation Template Parameters ............... .. ..... .... .. ..... .... ..... .... ..... .. .. 8-30

8-8 X.25 PVC Parameters......................................................................... 8-34

9-1 SN A P o rt Pa r a m e t ers..... .. ....... .. .. ....... .. ....... .. .. ....... .. ... ...... ... ...... ... .. ...... 9-6

9-2 SNA Port PU Parameters...................................................................... 9-7

9-3 Subscriber Parameters ........................................................................ 9-15

9-4 L L C2 H o st Pa r a meters ............. .. ....... .. .. ....... .. ... ...... ... ...... ... .. ....... .. .. .. 9-21

9-5 L L C2 I n te r face Par a m e t ers....... .. ....... .. .. ....... .. ... ...... ... ...... ... .. ....... .. .. .. 9-28

10-1 BSC In t eractiv e Po rt Par ameters ......... .. ....... .. ... ...... ... .. ....... .. ....... .. .. .. 10-4

10-2 BSC In t eractiv e Po rt Sub s cri b e r Param et ers......... .. ... ...... ... ...... ... .. .... 1 0 -5

10-3 Subscriber Parameters ........................................................................ 10-9

10-4 Control and Device Unit Addressing................................................ 10-11

10-5 BSC Interactive Device Parameters.................................................. 10-12

11-1 BSC Batch Port Parameters................................................................ 11-3

11-2 Subscriber Parameters ........................................................................ 11-9

xii FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 15

12-1 Async PAD Profile Parameters ........................... ............. .......... ........ 12-2

12-2 Async PAD Login Parameters................ ............. ............. .......... .. ...... 12-7

12-3 Async Port Parameters.............................. ........................ .................. 12-9

12-4 Subscriber Parameters ...................................................................... 12-16

12-5 Async PVC Parameters.................... ............. .................................. .. 12-19

13-1 IP Defaults Parameters ....................................................................... 13-5

13-2 Frame Relay IP Interface Parameters ................................................. 13-8

13-3 X.25 IP In terface Param eters ... .... ..... .. ..... .... .. ..... .... ..... .... ..... .. ..... .... .. . 13-9

13-4 Ethernet/Token Ring IP Interface Parameters ............. .... ..... .... ..... .. . 13-1 0

13-5 IP Routing Parameters...................................................................... 13-16

14-1 IPX Node Defaults Parameters............. ..... .... ..... .. ..... .... .. ....... .. ..... .... . 1 4 -2

14-2 IPX RIP Filter Parameters .................................................................. 14-5

14-3 IPX SAP Filter Parameters................................................................. 14-5

14-4 IPX Packet Filter Parameters.............................................................. 14-6

14-5 IPX RIP Router Filter Parameters ...................................................... 14-7

14-6 IPX Filter Applications P ara meters....... .................................. ........... 14-9

14-7 IPX Frame Relay Interface Parameters ............................................ 14-10

14-8 IPX X.25 Int erfa ce Parameters .. ..... .... .. ..... .... ..... .... ..... .. ..... .... .. ..... ... 14-11

14-9 IPX LAN Interface Parameters......................................................... 14-12

14-10 IPX RIP Static Route Parameters ..................................................... 14-17

14-11 IPX SAP Static Route Parameters.................................................... 14-18

15-1 Bridge Node Default Parameters........................................... ............. 15-4

15-2 Bridge Generic Filter Parameters ....................................................... 15-8

15-3 Bridge MAC Filter Parameters........................................................... 15-8

15-4 Bridge SAP Filter Parameters............................................................. 15-9

15-5 Bridge Protocol Filter Parameters ...................................................... 15-9

15-6 Bridge NetBIOS Filter Parameters ................................................... 15-10

15-7 Bridge Filter Applications Parameters.............................................. 15-11

15-8 Bridge Port/LLC2 Interface Param eters ........... .... .. ..... .... ..... .. ....... .. . 15-1 3

16-1 SNMP System Defaults Parameters................................................... 16-2

16-2 Community Table Parameter.............................................................. 16-4

16-3 Trap Routing Parameters.................................................................... 16-5

18-1 FRX4000 Database Files.................................................................... 18-9

xiii

Page 16

xiv FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 17

Section I

Getting Started

Page 18

Page 19

Product Overview

FRX4000

Async BSC SDLC LLC2 IPX

FRX6000 with monitor & printer

SmartSwitch 9000

with FRM

Introduction to Netlink FRX4000 and FRX6000

Cabletron's frame relay access product family is designed to provide a comprehensive method of integrating LAN-based systems and wide-area applications into a "blended" network. Ea ch device in the family can be a fully capable LAN router and a robust switch supporting multiple access and routing protocols.

Cabletron’s frame relay access product family also includes the SmartSwitch 1800 and Frame Relay Module ( for SmartS witch 900 0). These produc ts are d ocumented in separate manuals.

Chapter 1

FRX4000 and FRX6000 are generally used to provide concentration and access to remote devices. FRX40 00 is a stand-a lone device use d where eight s erial interfa ces or

fewer are required. FRX6000 is a larger stand-alone device supporting up to sixt y-four serial interfac es, and can function as a central-site device for remote FRX4000s, Frame Relay Modules (FRMs), and/or SmartSwitch 1800s.

Figure 1-1 Network Example

Page 20

FRX4000s and FRX6000s feature (on devices with video interfaces) an intuitive, menu-based management structure that allows complete local and remote contr ol of other FRX4000s/6000s, SmartSwitch 1800s, and FRMs.

Some typical FRX4000/6000 applications are:

●

SDLC-to-LLC2 and LLC2-to-QLLC conversion over frame relay

●

SNA and TCP/IP LAN/WAN integration—with or without routers

●

Banking applications— LAN, SNA, TCP/IP, async

●

Traffic aggregation and concentration to public frame relay serv ices

●

"Front end" network to larger frame relay switches

●

X.25-to-frame relay gateway applications

Multiprotocol Support

The FRX4000 and FRX6000 support these protocols:

●

Frame Relay

●

X.25

●

SNA/SDLC

●

SNA/LLC2

●

Bridging

●

IPX

●

BSC

●

Async

Each FRX4000 includes frame relay, SDLC, and SNMP, plus whatever additional protocols were pur chased with the device. The software for a ll of the listed protocols is included with every FRX6000.

Management Functions

The FRX4000 and FRX6000 support the same management functions:

●

Local SNMP agent, with Sets from network manager on some MIB variables

●

Manageable via Cabletron’ s Spectrum® and SPEL

●

NetView Service Point funct ion

●

Control via local monitor, remote FRX4000/6000, or local/remote async terminal

●

File transfer, database backup/restore, and software updates between devices

●

Local configurati on

●

Centralized alarm routing

●

Statistics displays

●

Line monitor

1-2 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 21

Hardware Overview

FRX4000

The base model of a Netlink FRX4000 contains four serial ports for connection to a frame relay or X.25 network, us er devices, and/o r other Cabletron frame relay access devices. (One V.35 DTE interface cable is also included.) Each FRX4000 also contains one LAN interface, either Ethernet or Token Ring. An optional CSU/DSU interface is also a vailable. (I f the CSU/DSU option is used, one seria l port is disa bled.)

Serial Interfaces

In addition to the four built- in serial ports, an op tional expans ion ca rd provide s one of the following:

●

Four V.35 ports

●

Four RS-232 ports

●

One T1 port

●

One E1 port

●

Four RS-422 ports (available by special request), supporting RS-449 and X.21 interfaces, in any combination (via cables)

Each of the serial po rts supports any of the protocol s that are i nstalled in an FRX400 0. Each FRX4000 contains software for frame relay, SDL C, SN MP and an y ad ditional protocols that were purchased with the device.

LAN Interfaces

The Ethernet model of the FRX4000 contains an Ethernet interface, provided in RJ45 (for twiste d pair) and 1 5-pin " D" (AUI, f or Thi cknet) config urati ons. The Etherne t cable and, if AUI, the tranceiver, must be provided by the customer.

The Token Ring model of FRX4000 contains a Token Ring interface, provided in RJ45 (for unshielded twiste d pair) and 9-pin "D" (for shielded twisted pair) configurations. A Token Ring cable, part number FRX-TR-CAB, is available from Cabletron.

Operator Interfaces

After it ha s been inst alled a nd configured, an FRX4000 c an functio n with no keyboard or video devic e. (The refore, such devi ces ar e not st andard e quipment. ) However , configuration, fil e copy (backup, resto re, transfer, etc .), and monitoring o perations require a keyboard and screen, in one of several forms.

The typical method of connecting to an FRX4000 is via an ASCII (VT100-type) terminal (configured for 9600 bps, 8 data bits, 1 stop bit, no parity), or a terminal emulator on a PC running Procomm Plus for Windows. Each FRX4000 is shipped with cabling to support connec tion to an ASCII terminal or a PC.

Product Overview 1-3

Page 22

FRX6000

Cards

RLP

Hardware in the FRX6000 includes:

●

Three types of card: RLP (RISC-based line processor) (plus attached Line Interface Ca rd s), Et he rnet LAN adapter, and Token Ring LAN adapter. An FRX6000 supports up to 8 R LPS, or 7 RLPs and 1 LAN card, or 6 RLPs and 2 LAN cards.

●

I/O cables. (One V.35 DTE interface cable is included with the base model.)

●

Cabling for a local or remote Auxiliary Console (ASCII terminal).

●

A 19" rackmount chassis.

The FRX600 RLP, an i960 RISC-based line processor, pr ovides serial inte rfaces, connecting various synchr onous and asynchronous user devices to public or private networks. Each RLP supports up to se ven pr otocols and up to 10 24 simu ltaneous logi cal terminations. (A link into one physical/logical port on an RLP and out another port counts as two terminations .)

Each RLP supports up to two serial Line Interface Cards (LICs). The base model of FRX6000 contains two RLPs with one LIC. (The RLP without LICs is provided to maximize the number of protocols that can be loaded in the node; some protocols are loaded onto one RLP but shared by all others in a node.) Other available models include up to four LICs.

LAN Adapters

Chassis

The FRX6000 supports LAN (local-area network) interfaces via one or two of these adapters:

●

Ethernet (802.3) – 10baseT (RJ45 /twisted pair), 10base2 (BNC/coax) , or AUI (DB15/coax)

●

Token Ring (802.5) – RJ45 (twisted pair) or DB9

Depending on the number of RLPs, an FRX6000 can contain one or two LAN cards (in any combination). Each LAN card supports one LAN interface.

The 19-inch rackmount chassis includes:

●

1.2GB hard disk

●

3.5" high-density diskette drive

●

Two COM ports

●

Parallel port

●

VGA port

●

Keyboard port

1-4 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 23

Operator Interfaces

Installation of F RX6000 so ftware into a node, generall y don e be fore t he node ships to the customer, require s a directly c onnect ed keyboard an d monitor. Once the node has been installed and configured, it can function with no operator interface. However, configuration , fi le copy (backup, restore, transfer, etc.), and monitoring operations require a keyboard and screen, which can be in any of several forms.

Each FRX6000 is shippe d wit h cabling to suppo rt c onnection to an ASCI I ter minal or a PC.

Product Overview 1-5

Page 24

Page 25

Quick Start

Chapter 2

Getting Started

The installation doc umentati on that is shi pped with eac h unit descr ibes the procedure for connecting to an FRX4000/6000 from a local or remote keyboard and video device. Once this has been done, the FRX d evice must be customized for the devices to which it will connect, the traffic it will receive and transmit, and various ope rating parameters that can be set to your specific needs.

Much of the configuration can be performed from an existing central-site FRX6000 via remote control of the new FRX4000/6000. At a minimum, however, someone must configure a re mote control ID and a phys ical port on each new FRX, to allow the central-site FRX to gain access to the new FRX.

The basic steps you should take to get the new FRX up and running are:

1. Read the remainder of this chapter, as it explains the user int erface on an FRX4000/6000. This information will help you understand the menu operations that are necessary to configure the FRX for your application.

2. Review the default database parameter settings, listed in tables throughout Section II. (A list of tables can be found in the Table of Contents.) Many param- eters can be left at the default settings, but some must be reconfigured to match your specific needs.

3. Fill in Table 2-1 (on page 2-2 ) for FRX4000, or Table 2-2 (on page 2-4) for FRX6000, to identify the physical interface, protoc ol, and connected device on each physical port. You will need more infor mation when configuring database records, but these tables can be used as convenient references.

4. Log into the menu operations, if not already done. This is descri bed in the FRX6000 Installation & Setup Guide, as well as on page 2-6.

5. Set the correct date and time, as describ ed on page 2-11. Event messages, reports, and some displays include the current date and time as set in the FRX. They should be accurate, for prope r network monitoring and management.

6. Change the login password, if desired. The default pa ssword is change this to any password of up to 14 characters, as described on page 2-11.

7. Configure the necessary da tab as e records: Node (Chapter 4), SNMP param et er s (Chapter 16) if SNMP management will be performed, RLPs (FRX6000 only) and protocols ( Chapter 5), network ports (frame relay – Chapter 7) or X.25 – Chapter 8), plus LAN interfaces and legacy access ports (miscellaneous chapters in Section II).

NETLINK

. You can

Page 26

Port Assignment Worksheets

FRX4000

Ports 4–7 are on optional expansion card

CSU/DSU

4567

LAN Port

0123

Figure 2-1 Physical Ports on FRX4000

Table 2-1 lists all possible physical ports on the FRX4000.

Table 2-1 FRX4000 Port Assignments

Port

0RS-232 1 2 3 4 5 6 7 LAN

Interface

Physica l interfac e, as described below.

Port 0 is RS-232. Port 1 must be either RS-232 or DSU. Ports 2 and 3 are determined by the attached cable: V.35, RS-232, RS-449, or X.21. Ports 4–7 are also determined by the cables, which depend on the expans ion card.

Interfaces (with cards in parentheses) are: V.35 (V.35), RS-232 (RS-232), RS-449

(RS-422), or X.21 (RS-422). Each cabl e is physical DTE (male connect or) or DCE (female connector ). Add a the int erface type to record thi s information. (This doe s not apply to a DSU or LA N p ort.)

The proto cols that can be as signed to ports d epend on t he model of FRX4000 an d the optio ns that were purchased . A ll possibl e protocols are listed below:

Ports 0–7, CSU/DSU: Frame r elay, X.25, SDLC, BSC Inter acti ve, BSC Bat ch, Async . LAN Port: IP, IPX, Bridge, LLC2.

Note tha t LA N protocols (IP, IPX, Bri dge, LLC2) are a lso assigne d to physical frame relay ports vi a interface records th at map the protocols to the physical ports.

Protocol

Connected Device

or C to

2-2 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 27

FRX6000

RLP

LIC 1

RLP Cable

I/O Cables to Modems and User Devices

LIC 2

I/O Box

RJ45 Adapter on T1/E1 Port 4

Figure 2-2 shows the locations of the physi cal ports on an FRX6000 RLP. An FRX6000 can contain up to eight RLPs, numbered (via swit ches) 0–7. When an FRX6000 is shipped from Cabletron, all installed RLPs are numbered con secu t ive ly (starting with RLP 0), right to left, as viewed from the rear of the FRX6000.

The above example shows LIC 1 as V. 35, RS-232, or RS-422, and LI C 2 a s T1 or E1. The ports supported by each LIC type are:

LIC Type LIC 1 LIC 2 V.35 Ports 0-3 Ports 4-7 RS-232 Ports 0-3 Ports 4-7 RS-422 Ports 0-3 Ports 4-7 T1 Port 0 Port 4

Getting Started 2-3

E1 Port 0 Port 4

Figure 2-2 Physical Ports on an FRX6000 RLP

Page 28

Table 2-2 lists all possible physical ports on the FRX6000.

Table 2-2 FRX6000 Port Assignments

Card Port

RLP 0 0

RLP 1 0

RLP 2 0

RLP 3 0

RLP 4 0

continu ed on next page

Interface

1 2 3 4 5 6 7

1 2 3

Protocol

Connected Device

2-4 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 29

Table 2-2 FRX6000 Port Assignments

(continued)

Card Port

RLP4 4 (contd.) 5

6 7

RLP 5 0

1 2 3 4 5 6 7

RLP 6 0

1 2 3 4 5 6 7

RLP 7 0

1 2 3 4 5 6 7

LAN 0 LAN 1

n/a n/a

Interface

Protocol

Connected Device

Getting Started 2-5

Physic al inter fa ce , determ in ed by the LIC and at tached ca ble (except T1 an d E1 LI C s, w h ich do not include cables). Possible interfaces (with LICs in parentheses) are: V.35 (V.35), RS-232 (RS-232) , RS-449 (RS-422), X.21 (RS-422) , RS-530 (RS-422), T1 (T1), or E1 (E1). Each cabl e is physical DTE (male connect or) or DCE (female connector ). Add a

or C to the

interface type to record this information. All possi ble protocol s are listed below:

Ports 0–7 : Frame relay, X.25, SDLC, BSCI (Interactive), BSCB (Batch), Async. LAN Ports: IP, IPX, Bridge, LLC2.

Note that LA N protocols (IP , IPX, Bridge, LLC 2) are also assi gned to physical frame relay ports via interface records that map the protocol s to the physical ports.

If there is only one LAN card, it will always be card 0.

Page 30

Logging in to the Main Menu

Configuration (des cribed in Section II) and management (Section III) operations are accessed via a menu structure, using the keyboard and video device. Once the FRX has been configured and is operational, it does not need the keyboard and video device; however, they are nece ssary to get the unit up and running.

When running out side the menu operations, a display wi ll be similar to the following figure, and will show the current status of all ports on the node. (This display is described in detail on pa ge 19-2.)

Port Status Display (Page 1)

L P Type PPS Conn# State L P Type PPS Conn# State

0 0 FRL 62 4 Operational 0 1 SNA 127 12 Operational 0 2 FRL 112 7 Operational 0 3 SNA 60 6 Operational 0 4 SNA 110 3 Operational 0 5 X25 87 5 Operational 1 0 ASY 0 0 Link_disable 1 1 X25 88 4 Operational 0 Eth 0 0 Operational

F1: Login

Node Name=node_xyz

Figure 2-3 Port Status Display

This example shows an FRX6000 display. On an FRX4000 display, there

is no

column, since the FRX4000 has no RLPs.

Node Name

identifies the node under control of the keyboard and screen.

This will generally be a dire ctly connecte d node, in which case the ID will

Node Name

be the

configured in the Node Defaults file (described in Chapter 4). If an op erator ta kes Remo te Co nt rol of another node (d escribed on page 18-1),

Node Name

will become the

Remote Control ID

configured in Node Defaults on the controlled node. Any configuration or control operations will affec t that node rather than the local one. If the controlle d node has a display screen, the message

blocked by id="n"

will be displayed, where "n" is the

Unde r remot e c o ntrol . K ey board

Remote Control ID

the controlling node.

After the operator presses page 4-1), the Main Menu will appear.

2-6 FRX4000/FRX6000 4.0 User Guide, Rev 01

[F1]

at the screen in Figure 2-3 and enters a pa ss wor d (see

Page 31

Reviewing Boot Messages

Node Name=node_xyzl

Version "n.n.n "

M A I N M E N U

A Configuration

BOperations

C Status Displays

DEvents

E Statistics

FReports

Option:

Figure 2-4 Main Menu

This is the starting point for all menu operations. The organization of the menus is shown in Appendix E.

As an FRX4000/6000 boots, screen information tracks the loading of cards, verifies configuration file format, and displ ays any errors. This dat a is displayed only until the FRX software is running; however, it is s aved in a f ile named BOOTRPT. TXT, and the operator can later displ ay it i n a r eport. Th is ca n be use d as a t ool t o ver ify tha t sta rtup of the node proceeded without errors, or to remind the user of the number and types of RLPs in the node. If there is an error reported, the data may aid in fixing the problem.

If an FRX4000/6000 is sh ut down, then reboote d, the existing BOOTRPT.TXT fil e will be renamed BOOTBAK.TXT, and a new BOOTRPT.TXT will be created. BOOTRPT.TXT and BOOTBAK.TXT can be used as follows:

1. Display and review the data from the “current” boot of the device.

2. Address any reported problems.

3. Re-boot the device. (This copies the previous boot data to a backup fi le. )

4. Display the new boot data, and compare it to the previous data. This will show whether the problem was fixed. Also, a problem t hat occur red during the pr evious boot-up will often be cleared up by re-booting.

To display the data from the curre nt boot-up, press

[C]

from the Main Menu). To display the data from the previous boot -up (saved in a

file call ed BOOTBAK.TXT), press

[D]

at the Reports menu (or

[C]

at the Reports Menu (or

[F], [D]

from the Main

[F],

then

Menu).

Getting Started 2-7

Page 32

Moving Through the Menus

To select a menu item, press the letter to the left of the item. To return to the next higher menu from a lower-level, press To move from operations under one Main Menu entry to operations unde r another

entry, you must return to the Main Menu. The easiest way is to pres s until the Main Menu is displayed.

Prompts

Within the menu operations, there are two kinds of prompts:

●

Information prompts – respond by typing the requested information, then pressing

●

Yes/no prompts – respond by pressing

Throughout this manua l are table s of vali d and default va lues. To specify a de fault (if one exists), press

[Enter]

[Enter ]

[Y]

in response to a prompt.

[N]

[F3]

repeatedly

On-Line Help

Pressing

[Enter]

when it is not required may cause the next

prompt to automatically select the default choice.

Most screen menus display a prompt called

Option:

. Pressing prompt will usually displa y a list of options. To make a selection, press either the function key shown preceding the desired option or the character preceding the desired menu item. The list of options varies, depending on what menu is displayed; most of the options are describe d below. (Function key equivalents on an async ter- minal keypad are listed on page 2-10.)

F1: Select Another Record

Next Record

—displays the first prompt that appeared on your screen after you

Redisplay/Refresh

made your menu selection, so you can specify another record.

Redisplay/Refresh

F2: Next Record

Next Record

—refreshes a display with updated information.

Remote Refresh

—displays the nex t sequentia l record on you r scre en fo r verific ation,

modification, or deletion.

Remote Refresh

—refreshes a remote display.

[?]

in response to this

F3: Exit menu

2-8 FRX4000/FRX6000 4.0 User Guide, Rev 01

—returns you to the previo us menu, saving any change s you have made.

Some menus have two sets of values:

Database

Changes will affect only the database, unless you press pressing

[F3]

. (This will update the system memory.) Database and

System Memory

and

[F7]

before

System memory values are described on page 4-2 for Node Defaults and page 6-3 for Ports.

Page 33

F4: Exit menu

Delete Record

Clear Max Stats

Exit Menu

—appears at t he Main Menu, and exits to the Port Status displa y (Figure

2-3). To return to the menu, you must enter the node's password. (This fe at ure is

for security, to protect menu-level operations from unauthoriz ed access.)

Delete Record

—initiates the dele tion of the displayed record. A record for this

port number, containing all the default values, will remain in the databas e.

Deleting a port record for an existing port will immediately disable the port.

Clear Max Stats

from the display (restarting them at the current values).

F5: Copy Record

which can be convenient if several records in a node will have identical (or almost identical) conf igurations. After you pe rform this opera tion, the "copied to" r ecord will be displayed, with the new database values. (The original record is automatically saved.) Press

F6: Move Record

deletes the ori ginal reco r d . Afte r you perform this operation, the "moved to" record will be displayed, with t he new databa se valu es. (The ori ginal r ecord is auto matic ally saved.) Press

—on statistics displays, clears the maximum/cumulative values

—copies a Port record's database values to another port's record,

[F7]

to update the system memory values.

You cannot copy a physical port's recor d to a logica l port, or vice versa.

—copies a Port record's da tabase values to anothe r port's record, then

[F7]

to update the system memory values.

You cannot move a physical port's record to a logical port, or vice versa.

F7: On-line cha nge

Database

values to

—in Node Defaults or Physic al/Logical Port configuration, copies

System Memory

Database

. (

System Memory

and

values are described on page 4-2 for Node Defaults and page 6-3 for Ports.) In IPX and Bridge Filter Definiti ons and Applicati ons, all c hanges made on the sc reen affect only system memory, so

F9: Stop Remote

[F7]

must be pressed to update the database.

—terminates a remote control c onne ction, gives you the option of

rebooting the remote node, and returns control to the local operator.

F10: Abort

Abort Reboot Remote

must then press

Reboot Remote

—initiates a reboot of a local node.

—initiates a reboot of a remote node under local control. (You

[F9]

to exit remote control.)

Before aborting or rebooting a node, notify all users that the node will be going down.

Getting Started 2-9

Page 34

ESC: Quit

—abandons the cha nges you have made since the last save (via

and returns you to the previous menu.

[F3]

[F7]

)

Character: Select Option

Select Option Change Field

—appears if an option has not yet been selected.

—Press the letter cor responding to the field you want to change, then

Change Field

type in the new information and press

PgUp, PgDn

—allows you to displ ay multiple scr eens (one at a time) for a reco rd, if the

record has more than one.

Funct ion Keys on an ASCII Terminal

Standard PC keyboard function keys are represented as follows on an ASCII terminal keyboard. Note that uppercase letter O.

PC ASCII Keyboard

[F1] [PF1] ^[OP [F2] [PF2] ^[OQ [F3] [PF3] ^[OR [F4] [PF4] ^[OS [F5] [5] ^[Ou [F6] [6] ^[Ov [F7] [7] ^[Ow

[F9] [,] [F10] [.] [PgUp] [ ] ^[OA

[PgDn] [ ] ^[OB

^[O

(under "Maps to:") is an escape character followed by an

Keyboard Maps to:

(comma) (period)

^[Ol ^[On

[Enter]

2-10 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 35

Setting the Date and Time

Various operations and reports record the current date and time, as recognized by the originating devic e. This operation allows changing one or both, to assure that al l devices in a network are synchronized.

Press

[B]

at the Node Configuration Menu (or

[A], [A], [B]

from the Main Menu). The date and time as currently recognized by the FRX4000/6000 will be displayed, and you will be asked:

[Enter]

to leave it as is. If changing the date, enter the correct information, noting the

Do you want to change the date?

Press

[Y]

to change the date or

values in Table 2-3. After the date, change (or le ave) the time in the same way as the date.

Table 2-3 Date and Time Parameters

Param et er Valid Values Defau l t Value

Date Y/N N Month 1–12 1 Day 1–31 1 Year 1980–2099 1998 Time Y/N N Hour 0–23 0 Minute 0–59 0 Second 0–59 0

Changing the Login Password

The login password is used to gain access to menu operations. When software is shipped to the customer, the password is words are case sensitive.)

To change the password, press

[A]

at the Node Configuration Menu (or

from the Main Me n u) . When prompted:

1. Enter the old password.

2. Enter the new password, up to 14 characters (

3. Enter the new password again f or verif ication . If thi s password i s not the sa me as the entry in ste p 2, the system will r eject the new password (and the old one will remain valid).

Getting Started 2-11

NETLINK

. (Note the upper case—all pass-

[A], [A], [A]

A–Z, a–z, 0–9

Page 36

Stopping Operation

Loggi ng Out

Rebooting

Shutting Down

If you have been working wit hin menu operations and wish to log out, pr ess Main Menu. The Port Status Display screen will be displayed, with a ny updates. The software will continue to run, but only those who know the password will be able to gain access to the menus . You must press the Main Menu.

To reboot from within the menu level, press

You cannot reboot t he device from the initia l Port Status Display. You must first press

[F1]

and enter the password to get to the Main Menu.

[F1]

and enter the password to get bac k into

[F10]

. When asked:

Reboot?

[F4]

, press

at the

[Y]

Rebooting the device clears all connections. If you d o not want to do this, simply press

To shut down an FRX4000 or FRX6000, simply switch it off.

Make sure all users of the device are aware that it will be shut

[F4]

to log out, then leave the devic e running.

down.

What Next?

Once you are f amiliar with th e menus and h ow they work, pr oceed to S ection II to configure the database.

2-12 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 37

Section II

Configuration

Page 38

Page 39

Chapter 3

Introduction to Database Configura tion

Each FRX4000 and FRX6000 contains its own configuration database, which contains information identifying the hardware components, and defines the operating parameters of the hardware and software.

Each database file conta ins defining parameters for a specific compon ent ; for example, physical ports, subscriber IDs, or IP interfaces.

Before an FRX4000 or FRX6000 can properly operate , all nec essary data base parameters must be configured. The necessary configuration depends on the installed hardware, the routing and acc ess protocol s that will be used, and the devices tha t will be connected to ports in the FRX. Some helpful information can be found under "Database Setup Recommendations."

Database Setup Recommendations

Many database parameters are configur ed with default values, many of which may not need to be changed for your configur ation. Other parameters, however, define the specific configuration. For example, each device must have unique identifiers if the device will be used in remote control, file transfer, or alarm re porting operations . Also, each device will most likely differ in which ports will run which protocols, and what the physical interfaces on those ports wi ll be .

Before proceeding with your configuration, you shou ld be aware of all the parameters that must be, or can be, specifie d. You should first note the default val ues, since many may be correct as is. Tables of parameter s, inc luding their valid and default values, can be fo und throughout Section II. The Table of Contents conta ins a list of all tables.

You should also be familiar with all devices that will connect to FRX4000s/6000s; some have requirements or restrictions.

Some things you must know before configuring the dat abase are:

●

The information in Table 2-1 (on page 2-2) and Table 2-2 (on page 2-4).

●

Addresses that must be specifie d in various port and interface records. Each X.25 SVC subscribe r must be assi gned an ID ( describ ed on page 8-22) that will be used as a called or call ing a ddress in call setup packets. IP, I PX, LLC2, and SNMP also require addresses for identification of networks and devices.

●

Passwords. You must enter a password to remotely c ontrol another Cabletron frame relay access devic e, to perform software update s and file transf ers, and to configure alarm routing.

Introduction to Database Configuration 3-1

Page 40

Most parameters can be specified and/or changed using the operations described througho ut the configur ation por tion of this manual; others, such as RLP and port number, are defined by the hardware or speci fi ed during software in stall ation.

Configuration Exampl e s

Legacy Protocols over Frame Relay via Logical Ports

Below is a sample configuration and guidelines for configuring Logical Ports for Annex G or RFC 1490 transmission over frame relay.

SDLC

Async

BSCI

X.25

Sync passthru

FRX

Logical Ports

Frame

Relay

FRX

Figure 3-1 Configuration Example 1

Configure the following in each FRX4000/6000:

●

RLP parameters (Chapter 5), to configure the RLP(s) that con tain the ports over which the protocols will run. Each serial protocol (SNA, async, BSC, X.25, frame relay) must be configured on the RLP that conta ins the port.

●

Physical Port (Chapter 6 plus Chapter 7 [Frame Rel ay ], Chap t er 8 [X.25],

Chapter 9 [SNA], Chapter 10 [BSCI], and Chapter 12 [Async]).

●

Logical Port (Chapter 8) on the physical fram e relay p ort that connects to the network. (Note that logical ports are number ed 8–63, because 0–7 are the physical ports.)

●

SVC Subscriber (Chapter 7 [Frame Relay], Chapter 8 [X.25], Chapter 9 [SNA],

Chap ter 10 [BSCI], and Chapter 12 [Async]), which assign static address es used

to route the call request pac ket s of the physical access ports to the logical port and vice versa. Subscriber addresses are based on the X.121 Called Address field.

●

Optional SVC subscriber records (static routes) for any attached X.25 DTEs. These are needed to identif y the attached DTEs’ X.121 Calli ng Addresses. If an X.25 Call Request i s rece ived fr om the WAN li nk, the FRX4000/6000 ne eds to know where to route the call.

SDLC Async BSCI X.25 Sync passthru

3-2 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 41

Frame Rel ay P VC Pas sth r oug h

Frame Relay Switch or DCE FRAD

3174 Control Unit Running

IP & SNA

FRX

Fram e Relay PVC

Frame Relay PVC

AS/400

5494

Frame

Relay

Local

FRX

Remote

FRX

Figure 3-2 Configuration Example 2

Configure the following in each FRX4000/6000:

●

RLP parameters (Chapter 5), to configure the RLP(s) that contain the frame relay ports.

●

Physical frame relay port (Chapter 6 and Chapter 7) . Configure the FRX4000/ 6000 port to the 3174 as logical DCE, and the port to the frame relay switch as logical DTE.

●

Frame relay PVC (Chapter 7), which links the two frame relay p orts in t he FRX4000/6000. The DLCIs are define d in the PVC record; if rate contro l (CIR,

, BE) will be enforced, be sure to configure those parameters in the frame

relay Port recor d.

Make sure each DLCI is supported on the attached device.

LLC2 PUs over Frame Relay to AS/400

Figure 3-3 Configuration Example 3

Configure the following in the local FRX4000/6000:

●

RLP parameters (Chapter 5), to configure the RLP(s) that con tain the ports over which the protocols will run. Configure frame relay on the RLP containing the port to the network. If LLC2 is not already confi gured in the FRX4000/6000, configure it on the sam e RL P . (Fra me rela y must b e conf igu re d on each RLP that will use it, but LLC2 is configured on one RLP only. Performance may be enhanced if both pr otocols are on the same RLP, since t his e liminates the need to communicate via the bus in the FRX4000/6000.)

Introduction to Database Configuration 3-3

Page 42

●

LAN Card parameters (Chapter 5), to confi gu re the Eth ern et ad ap ter in the FRX4000/6000.

●

Physical Port parameter s (Chapter 6 and Chapter 7), to define the frame relay port.

●

Virtual LAN ID (Chapter 9), which identifie s a virtual bridge that connects the internal LLC2 function to the Ethern et interface.

●

Originated LLC2 Host (Chapter 9), which maps connectivity at the LLC level between the FRX4000/6000 and the AS/400. (The FRX4000/ 6000 initiates LLC sessions wi th the host.) For this example, assume the host number is can be same number as the LAN card number, which is always

●

Terminated LLC2 Host (Chapter 9), whose address must mat ch the frame relay

0–128

, but ide ntific ation can be e asier if the hos t o n th e LAN si de ha s the

or 1.)

interface t o which the 5494 d evice will t ransmit. Note that the remote FRX4000/ 6000 must have a corresponding origina te d LLC2 host. For this example, assume the host number is

●

Ethernet LLC2 Interface (Chapter 9), which defines an interface to the Ethernet LAN. For this example, assume the interface number is

. (It can be

0–95

, but as with the hosts, identification can be easier if the interfa ce on the LAN side has the same number as the LAN card number.)

●

Frame relay terminated LLC2 Interface (Chapter 9), which defines an LLC2 termination point at the frame rela y inte rface. Be sure to configure the format as 8025_SRB or 8023_TB (since the AS/400 needs to see the source MAC address, which is not passed in the third format, Native LLC2). For this example, assume the interface number is

. Note t hat the remote FRX4000/6000

must have a corresponding origina ted LLC2 Interface.

. (It

Interfa c e 0

Ethernet

Local FRX

Host 0

Originated

Host 2

Terminated

Interfa ce 2

Frame Relay

Terminated

Figure 3-4 Local FRX4000/6000 in Configuration Example 3

Some sample LLC2 parameter values to configure on the local FRX4000/6000 are:

●

Virtual LAN ID –

●

LLC2 Host 0:

◆

Host MAC Address –

007

(hex).

4000000000470

. This is the AS/400 tar geted a ddre ss.

(The 9th and 10th digits of the MAC address make up the host number.)

◆

Session Type –

Originated

. This host will initiate the LLC2 session to the

above MAC address.

3-4 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 43

◆

Remote FRX

Host 2

Originated

Host 0

Terminated

Interface 2

Frame Re lay

Originated

Interface 0

Token Ring

Routing Subscriber ID – all the digits of the Local Subscriber ID (shown later in this list).

◆

Source MAC Address Mask – the FRX4000/6000 will use to send frames to the AS/400. The last four digits are connect to the host. For subs equ ent SAPs, the la st four digit s will be incremented to SAP address in a frame received from the local LAN.)

◆

Host SAP –

◆

Local Subscriber –

◆

Remote Subscriber –

◆

Type –

●

LLC2 Host 2:

◆

Host MAC Address – (and is the same as the Host MAC Address configured on Host 0).

◆

Session Type – session to the above MAC address.

◆

Routing Subscr iber ID – all the digits of the Local Subscriber ID (shown later in this list).

◆

Host SAP –

◆

Local Subscriber –

◆

Remote Subscriber –

◆

Type –

99*

. This ID must end in an asterisk and contain

40000000

0000

for the first 57 Host SAPs (service access points) used to

0001, 0002

LLC2

, etc. (Each Host SAP addr ess must matc h th e Source

. (SAP addresses can be

990*

. This is the Remote Subscriber ID of Host 2.

1010*

. This is the Local Subscriber ID of Host 2.

4000000000470

Terminated

. This host will terminate the frame relay LLC2

101*

. This ID must end in an asterisk and c ontain

. (SAP addresses can be

990*

. This is the Remote Subscriber ID of Host 2.

1010*

. This is the Local Subscriber ID of Host 2.

. This is the source MAC address

04–fe

, hex, in multiples of four.)

. This is the AS/400 ta rg eted address

04–fe

, hex, in multiples of four.)

Introduction to Database Configuration 3-5

Figure 3-5 Remote FRX4000/6000 in Configuration Example 3

Page 44

Key Points

MAC Addresses

When entering a host MAC address in an LLC2 Host or Interface record, enter the address in non-canoni cal form unless the atta ched device is on an 802.3 LAN and the remote device is on an 8 02.5 LAN, or the attache d device is on an 802 .5 LAN and the remote device is on an 802.3 LAN. In these cases, the inc oming address will be "bitswapped" by the tr ansmitti ng host , and yo u must r e-swap the bits be fore t ransmiss ion to the remote device. Bit-swap ping is described on page 9-22.

For reference, the following table describes what happens to a MAC address at the FRX4000/6000 if the sending and receiving formats are different.

Table 3-1 MAC Addre ss Conversion

Received from: Forwarded to: Action taken:

802.3 802.5 Converts MAC header to LAN header (including cached RIF), and bit-swaps address

802.3 Native LLC2 Drops MAC header

802.5 8 02.3 Coverts LAN header to MAC header, and bit-swaps addr ess

802.5 Native LLC2 Drops LAN header

Native LLC2 802. 3 Adds MAC header Nativ e LLC2 802. 5 Adds LAN hea der (including cached RIF)

LAN IDs

LAN IDs can be configured in two places:

●

LLC2 node def aults, to identify a virtua l bridge tha t connect s the LLC 2 function to LAN interfaces.

●

LLC2 frame rel ay int er faces using 802.5 Source Route Bridge format, to identify the ring number used by a source-route bridge at the remote end. (This ID is normally assign ed by a system admin istrator.) Not e that the LAN ID on an originated LLC2 interface must match the LAN ID on the corresponding terminated interface.

Be aware that when configur ing these r ecords, LAN IDs m ust be ente red in he x. Also note that, other than the matching IDs on each originated/terminated interface pair, each LAN ID must be unique within the network on which the FRX4000/6000 will operate.

LLC2 Function

Internally, LLC2 connects to interfaces via the Bridge protocol. LLC2 Host and Interface rec o rds act as both origination and termination points for LLC2. For example, if you are configuring SDLC-to-LLC2 conversion to be transmitted over frame relay to a Token Ring host, the fol lowing is the logical LLC2 reco rd flow: SNA Port/PU reco rd (Chapter 9), with the parameter as the both the LLC2 Host and LLC2 Interface termination record). In addition, you must configure a n originated Host for t he target MAC addre ss, and an int erface for the physical connection.

LLC2 Connection

set to

Yes

. (This acts

3-6 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 45

Terminated LLC Host records always make the calls. Originated LLC Host records always expect to receive calls.

Only one Originated and one Terminated LLC Host reco rd can be configured fo r each MAC addres s.

RFC1490 Format

An RFC1490 format used for SNA traffic is configured in the frame relay LLC2 Interface/Bridge Port record. The options, in order of lowest overhead to highest overhead, are:

●

Native LLC2 (also known as BNN, or Boundary Network Node). When this format is used, no MAC addresses are transmit ted across the frame relay link.

●

802.5 SRB (source route bridge) (also known a s BAN, or Boundar y Access Node. (FRX4000/6000 devices support BAN type 1). This format is generally used for 3174 gateways and AS/400s, because the y need to see a MAC address) .

●

802.3 TB (transpare nt bridge), used when talking to routers tha t cannot do BAN or BNN.

Subscriber IDs

Subscriber IDs are only used locally within each FRX4000/6000 to link records (e.g. SDLC PU record to LLC host record), unless the device is running X.25, SDLC/LLC 2 primary (the FRX4000/ 6000 would be SDLC secondary to the FEP), or logical ports (i.e., QLLC), in which ca se the subscribe r IDs correlate to the static routes defined in the subscriber routi ng tables.

PU1 Devices

PU1 devices can not be defined as Token Ring attached to the AS/400. AS/400 programmers might try to get around this by defining different device types (i.e ., 5494/ PU 2.0 or PU 2.1) to 5294 and 5394 PU1 controllers. However, when this is done, the ACTPU is not spoofed in ternally, and is sent to the remote controller. The FRX4000/ 6000 cannot accept and respond, and the controller and AS/400 will go into error mode. The 5394 can be RPQed to act as a PU2.1 device (see IBM RPQ 8Q0775); 5294 contr ollers cannot be RPQed, and must be attached as SDLC de vices; there are no issues with the 5494, as it is a PU2.0/2.1 node. 5294s and 5394s can only be directly connec ted to FRX4000/6 000 devic es via SDLC or X.25 with spe eds up to 64 kbps. 5494s can be connected via SDLC or frame relay with spee d s to 128 kb ps, or by Token Ring or Ethernet/802.3.

Introduction to Database Configuration 3-7

Page 46

3x74s/SDLC over Frame Relay to SNA Host

Host

FEP/ NCP

Local

FRX

Frame

Relay

Remote

FRX

Figure 3-6 Configuration Example 4

Configure the following in the local FRX4000/6000:

●

RLP parameters (Chapter 5), to configure the RLP(s) that con tain the ports over which the protocols will run. Configure frame relay on the RLP containing the port to the network, and configure SNA on the RLP containing the port to the FEP.

If LLC2 is not already configured in the FRX4000/60 00, configure it on the same RLP. (Frame relay must be configured on each RLP that will use it, but LLC2 is configured on one RLP only. Performance may be enhanced if both protocols are on the same RLP, since this eliminate s the need to communicate via the bus in the FRX4000/6000.)

●

Virtual LAN ID (Chapter 9), which is necessary for LLC2 functionality.

●

Physical frame relay port (Chapter 6 and Chapter 7).

●

Physical SNA port (Chapter 6 and Chapter 9). The link station SDLC/LLC2 conversion point is also defined in this record, under SNA PU Parameters. (These parameters act as both LLC2 Originated Host and Originated Interface records.)

●

Terminated LLC2 Host (Chapter 9), which points to the frame relay interface. Note that the remote FRX4000/6000 must have an Originated LLC2 Host.

●

Terminated LLC2 Interface (C hap t er 9), which defines an LLC2 termination point at the frame relay interface. Note that the remote FRX4000/6000 must have an Originated LLC2 Interface.

●

SVC Subscriber (Chapter 7), to route the incoming c onnec tion r eques t from the frame relay LLC2 Terminated Host to the SDLC port. Note that this record is not required on the remote FRX4000/6000, because that device originates the connection (i.e. , it is not be ing called).

3X74

Key Points

LAN IDs

LAN IDs can be configured in two places:

●

LLC2 node def aults, to identify a virtua l bridge tha t connect s the LLC 2 function to LAN interfaces.

●

3-8 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 47

originated LLC2 interface must match the LAN ID on the corresponding terminated interface.

LLC2 Function

Internally, LLC2 connects to int erf aces via a virtua l bridge. LLC2 Host and Interface records act as both origination and termination points for LLC2. For example, if you are configuring SDLC-to- LLC2 conversion to be transmitted over frame relay to a Token Ring host, the followin g is t he logic al LLC2 record flow: SNA Port/PU record (Chapter 9), with the parameter LLC2 Host and LLC2 Interface termination record). In addition, you must configure an originated Host for the target MAC address, and an interface for the physical connection.

Terminated LLC Host records always make the calls. Originated LLC Host records always expect to receive calls.

Only one Originated and one Terminated LLC Host reco rd can be configured fo r each MAC addres s.

RFC1490 Format

An RFC1490 format used for SNA traffic is configured in the frame relay LLC2 Interface/Bridge Port record. The options, in order of lowest overhead to highest overhead, are:

LLC2 Connection

set to

Yes

. (This acts as the both the

●

Native LLC2 (also known as BNN, or Boundary Network Node). When this format is used, no MAC addresses are transmit ted across the frame relay link.

●

802.3 TB (transpare nt bridge), used when talking to routers tha t cannot do BAN or BNN.

Subscriber IDs

Introduction to Database Configuration 3-9

Page 48

Producing a Configuration Report

A configuration report c onta ins this information:

●

Software version number

●

Passwords

●

Boot time

●

Various database paramete r values

●

Line status for each port

To create a configuration report, press

[A]

at the Reports Menu (or Main Menu). The report is created and saved to the node 's hard disk under the name REPORT.TXT.

You cannot generate a configuration report while a file transfer is in progress.

To display the configur ation re port, p ress

[B]

at the Reports Menu (or

Main Menu).

Where to Find Configuration Information

The following shows wher e to find the various configur ation files among the menus. (The first item, are the chapters/appe ndices in this manual where the items below those entries are described. Following most items in the lower tiers are descriptions of the associated database records.

A Configuration

A Configure Node

A–Configuration

A Configure Password

, is an entry on the Main Menu.) Followi ng some items

– (Chapter 2) allows changing the default login

password.

B Configure Ti m e a nd Da t e

– (Chapter 2) allows setting a correct time/ date that will be displayed on some screens and reports, and will allow all FRX nodes on a network to be in sync, regarding reports an d alarm messages that include the date and time.

C Configure Node Defaults

– (Chapter 4) specifies IDs and passwords used for remote control, file transfer, and alarm routing and reporting operations.

D Configure SNMP Parameters

– (Chapter 16) identifies the SNMP manager; defines communities; SNMP trap routing, and hardware platforms (for identification by Netlink OmniView element manager).

A Configure System Defaults B Configure C o m m uni t y Ta b le C Configure Trap Rout in g D Configure Model Number

[F], [A]

[F], [B]

from the

3-10 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 49

E Configure IP/LLC2/BRIDGE/IPX Default Parameters

A Configure IP Node Defaults

– (Chapter 13) specifies whether the FRX4000/6000 will ac t as an IP gateway and which version of RIP will be used.

B Configure Bridge/LLC-2 Node Defaults

– (Chapter 9) specifies parameters that will be used internally by the node to identify a virtual bridge that will c onne ct the LLC2 function to LAN interfaces and fra me rel a y PVCs.

C Review SNA LLC2 Hosts

– (Chapter 9) displays any LLC2 hosts

(see below) that have been configured on the FRX4000/6000.

D Configure SNA LLC2 Hosts

– (Chapter 9) defines LLC2 hosts on the FRX4000/6000; includes se ssion type (originated or terminated), necessary addresses, timers.

E Configure IPX Node Defaults

– (Chapter 14) defines operation of the FRX4000/6000 when used as an interface to a Novell NetWare network.

F Configure Fil te r De f in iti ons and Applic at i on s

A Review IPX Filter Definitions

– (Chapter 14) dis plays any IPX

filters (see next ite m) that are configured on the FRX4000/6000.

B Configure IPX Filter Definitions

– (Chapter 14) specifies parameters for transmi ssion of RIP and SAP updates, and/or generic IPX packets, per interface and direction.

C Review IPX Filter Applications

– (Chapter 14) displays information on any IPX filter appli cations (see below) configured on the FRX4000/6000.

D Configure IPX Filter Applications

– (Chapter 14) applies IPX

filters to interf aces/filter types/directions.

E On-Li ne Update IPX Filter Definitions and Applications

(Chapter 14) allows updating the FRX4000/6000 with any changes without rebooting.

F Review Bridge Filter Definitions

– (Chapter 15) displays any Bridge filters (see next item) that have been configured on the FRX4000/6000.

G Configu re Bridge Filte r Definitions

– (Chapter 15) s p ecifi es

parameters for regula tion of bridge traffic by filtering MAC addresses, NetBIOS names, SAP updates, etc.

H Review Bridge Filter Applications

– (Chapter 15) displays information on any bridge filter applications (see below) configured on the FRX4000/6000.

I Configure Bridge Filter Applications

– (Chapter 15) applies

bridge filters to inte rfaces/filter types/dir ections.

J On-Li ne Update Brid ge Fi lter Definit io ns and Applic at i ons

(Chapter 15) allows updating the FRX4000/6000 with any changes without rebooting.

G On-Line Update Dynamic Routing Parameters

– (misc.) updates the system memory with any changes that have been made to routing parameters .

F Configure Async PAD Parameters

– (Chapter 12) defines operating

parameters for devices connected to FRX4000/6000 async PAD ports.

A Review Async PAD Profiles B Configure Async PAD Profiles C Review Async PAD Logins D Configure Async PAD Logins

–

Introduction to Database Configuration 3-11

Page 50

G Review Mode l Information

– displays the maximum number of logical connections allowed, and lists the protocols installed, on the FRX4000/6000.

H Configure Bandwidth Allocation Groups

to 16 groups that assign connect ion pri orities to various types of traffic.

B Configure RLPs

(FRX6000) or

Config ure P r otocols

(Chapter 5)

A ReviewRLP

Protocol) Configuration

(or any RLPs (see below) already configur ed in the node. On any node type , displays insta lled prot ocol s and identi fi es inst alled Line Inte rface Ca rds.

BConfigure RLP

(or

Protocol

) – on an FRX4000, allows specifying the type of serial expansion card. On an FRX6000, allows specifying the types of Line Interface Card and protocols installed.

C Display RLP

Protocol) Memory Status

(or available and used memory on each RLP (or in th e similar functiona lity in the FRX4000).

C Configure Ports

A Configure RLP Ports

– (Chapter 6 through Chapter 11) specifies each

serial port's type , physic al interface, and operating parameters.

B Configure LAN Ports

– (Chapter 5) specifies the type (Ethernet or Token Ring) and associated addresses for each LAN interface on an

FRX4000 or FRX6000.

C X.25 Address Translation Templates

and tests templates that are applied to incoming and outgoing call packets for the purpose of translatin g selected fields of a pa cket th at may not otherwise be in a compatible format.

A Review X.25 Address Translation Templates B Configure X.25 Address Translation Templates C Test X.25 Address Translation Templates

D Configure Logical Ports

– (Chapter 8) specifies operating parameters

for logical ports residing on physical frame relay ports.

E Configure IP/LLC2/BRIDG E/IPX Interfaces

A Review IP Interfaces

– (Chapter 13) displays information on any

IP interfaces (see below) configured in the FRX4000/6000.

B Configure IP Interfaces

– (Chapter 13) specifies addressing and

operating parameter s for IP interfaces (X.25, frame relay, or LAN).

C Review Bridge Ports / LLC2 Interfaces

displays information on any bridge or LLC2 interfaces (see below) configured in the FRX4000/6000.

DConfigure Bridge Ports / LLC2 Interfaces

Chapter 15) specifies loc at ion, type, and format of any bridge or LLC2 inter face s .

E Review IPX In terfaces

– (Chapter 14) displays information on

any IPX interfaces (see below) configured in the FRX4000/6000.

F Configure IPX Interfaces

– (Chapter 14) identifies any IPX interfaces. Identifies type (X.25, Ethernet, etc.) and operating parameters.

F Configure BSC Devices

A Review BSC Device Configuration

(Chapter 10)

BSC Interactive devices (see below) that are configured.

B Configure BSC Devices

– identifies de vices usi ng FRX4000/ 6000

ports configured as BSC Interactive.

– (Chapter 7) defines up

(FRX4000)

– on an FRX6000, identifies

– displays a table showing

– (Chapter 8) displays, spec ifies,

– (Chapter 9, Chapter 15)

– (Chapter 9,

– displays information on any

3-12 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 51

G Review LAN Card Configurati on

– (Chapter 5) on an FRX6000,

displays information on any installed LAN cards.

D Configure C o nnections a nd Ro ut i ng Pat h s

A Review Subscriber IDs

– (misc. chapters) displays information on

any subscriber IDs (see belo w) confi gured in the FRX4000/6000.

B Configure Subscriber IDs

– (misc. chapters) identifies end users of the FRX4000/6000, and specifies parameters for redirecting tr affic t o othe r port s.

C Review Abbreviated Addresses

– (Chapter 10) displays information

on any abbreviated addresse s (see below) that are configured.

D Configure Abbreviated Addresses

– (Chapter 10) specifi es short versions of subscriber IDs that can be used in place of the full addresses for async PAD subscribe rs.

E P VC C o nf ig uration

– (Chapter 7 [frame relay], Chapte r 8 [X.25], Chapter 12 [async]) displays/specifies "permanent" connections between ports on an FRX4000/6000.

A Review PVC Configuration B Configure PVCs

F Review IP Routing

– (Chapter 13) displays information on any IP

routes (see below) configured in the FRX4000/6000.

G Configure IP Routing

– (Chapter 13) defines routes for IP traffic

through the FRX4000/6000.

H Review IPX Routing

– (Chapter 14) displays information on any IPX

routes (see below) configured in the FRX4000/6000.

I Configure IPX Routing

– (Chapter 14) defi nes ro ute s for IPX traffic

through the FRX4000/6000.

E Configure Frame Relay Backup Groups

– (Chapter 7) allows creation of one or more frame relay ports/DLCIs that will act as backup(s) for a port.

A Review Frame Relay Backup Groups B Configure Frame Relay Backup Groups

Introduction to Database Configuration 3-13

Page 52

Page 53

Node Defaults

Node Name=node_xyz

Node Defaults Configuration (Screen 1 of 3)

Database System Memory

A Node Name node_xyz node_xyz B Remote Control ID C Remote Control Pwd D File Transfer ID E File Transfer Pwd F Collecting Node ID G Collecting Node Pwd H Primary Alarm Output ID I Primary Alarm Output Pwd J Secondary Alarm Output ID K Secondary Alarm Output Pwd

Option:

Chapter 4

Configuring Node-Wide Default Parameters

Node Defaults are a set of parameters that identify an FRX4000 or FRX6000 for purposes of remote control , sof twa re updates, file transfers, and/or alarm reporting to or from a remote FRX, SmartSwitch 18 00, or FRM. The Node Defaults file a lso contains information that define s a connection to a NetView manager device.

[C]

Press This is the first of three Node Defaults scree ns—pressing the display among the three screens.

The first two screens contain parameters that apply to all users. The third screen contains parameters used in sessions between a NetView host and the NetView service point function in the FRX4000/6000. If the NetView function will not be used, the third screen does not have to be configured.

at the Node Configuration Menu to display a screen similar to Figure 4-1.

[PgDn]

[PgUp]

will change

Figure 4-1 Node Defaults Configuration Screen 1

[A],[A],[C]

from Main Menu

Page 54

After making any changes, be sure to press

[F7]

to update the system memory. Otherwise, the changes will n ot take effect until the next re-boot of the FRX4000/6000.

Although the entries for the various passwords appear blank, default values exist; if you change one, be sure you do not duplicate an existing password.

If there is a error in the co nfigu ra t ion for ala rm reporting, a message will be displayed at the top or bottom of the screen. The possible messages are described on page 4-10.

Primary Output I D

and only) serial/parallel ports. If a serial port is specified, no associated password (

Pwd

) entry will be displayed for the ID. Instead, a group of oper-

ating parameters (listed in Table 4-1) for the port will be displayed.

Database and System Memory Values

Two sets of values exist for Node Defaults parameters: Database values exist in the software, and are recorded as System Memory values when the node is booted. I f the port type is the same in both sets of values, both set s will be displayed.

Any change you make will be recorded as a Database value, and will be copie d to the System Memory side only if you press saved to the database until you press

Secondary Output ID

[F7]

. Note that changes will not be actually be

[F3]

to exit the record.

can be addresses, or ( FRX6000

4-2 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 55

Node Defaults Parameters

All possible pa rameters o n the first two Node De fault s screens are liste d in Tabl e 4-1, and the NetView parameters on the third sc ree n are listed in Table 4-2. Descriptions of most parameters follow each table.

Parameter Valid Values Default Value

Node Name

Remote Control ID Remote Control Pwd

File Transfer ID File Transfer Pwd

Collecting Node ID Collecting Node Pwd Primary Alarm Output ID Primary Alarm Output Pwd Secondary Alarm Output ID Secondary Alarm Output Pwd

Com. Port Thru put A–H Com. Port Parity: 0, 1, 3

Com. Port Stopbit 1, 2 1 Bits per Character 7, 8 8 Collecting Node Y/N N Max Congestion Min Congestion

Periodic Status Timer Line Idle Timer

Alarm Autocall Timer Alarm Ma x Retrie s 0–99

Table 4-1 Node Defaults Parameters

up to 8 charac ters none 0–15 digits none

0–15 characters 0–15 digits none

0–15 characters see fo otnot e 0–15 characters see fo otnot e 0–15 characters

1–50

(%)

1–50

(%)

0–30

(min)

0–65535 5–3600

(sec)

remote

ftran

alarms

none

alarms

none

alarms H

(9600 bps)

(none)

50 25

0 60

(no max)

Footnotes for Table 4-1:

Node Name

is displayed at the uppe r r ight of the screen when the device is being controlled by the "local" keyboard and moni tor. (I f the lo cal operat or is control ling a remote FRX4000/

Configuring Node-Wide Default Parameters 4-3

Remember that the software sees uppercase as different from lowercase.

Can be:

a 1–15 digit number (address).

◆

(FRX6000 only) a COM port:

◆

(FRX6000 only) a parallel (LPT) port:

◆

A value of

If 0, the conn ection will remain acti ve continuously.

Continuous retries until connection is established.

means tha t no st atus wi ll b e se nt.

or C2, plus

P1, P2, P3.

if thos e por ts ex is t.

Page 56

6000/SmartSwitch 18 40, the

Node Name

local

Remote Control ID

is required i f a remote Cabletron fr ame relay access device, or async terminal will be used to take control of the local FRX4000/6000 (via a physical or logical port in the local device). The ID will be checked aga inst the called address fields of incoming Call Requests. The remote device can be a terminal con nected to an async PAD port on a remote Cabletron frame relay acc ess device, or the remote device itself.

Make sure that each Cabletron frame relay access device on the same network is assigned a different Remote Control ID.

Remote Control Pwd

is a password used in conjunction with the against the user data field of a Call Request pa cket. Both the the password must match what is expected, or the FRX4000/6000 will not accept a request for remote control.

File Transfer ID

is used for file transfers (see page 18-4) to or from this FRX4000/6000. The ID will be checked against the called addr ess field of a Call Request pa ckets coming int o this FRX4000/6000.

Remote Control ID

of that device will be displa yed as th e

Remote Control ID

, and will be checked

Remote Control ID

and

File Transfer Pwd

is a password used in conjunction with the and the

File Transf er Pw d

accept a reque st for file t ran sfer.

Collecting Node ID

is defined on a collecting no de (described la ter) for use by other Cable tron frame rela y access devices that send the ir alarms to that collecting node. This same ID must be configured on ea ch non-collect ing node as the

Node ID

Collecting Node Pwd

has no function on non-collecting nodes.

is a password that will be checked to verify that the used for alarms. Sinc e the same ID can be spec ified for s everal functions, the softwar e processes can use the pa sswo rd s to identify the di ffer en t functions.

Any non-alarm passwords must be different than any alarm passwords. Unless you are certain you are not duplicating a password, leave all passwords at the default settings.

Primary Alarm Output ID

specifies where alar ms will be sent. On a device configured as a collecting node, the ID is usually associated with a print er port (async PAD port on FRX4000; serial, parallel, or async PAD port on FRX6000 ); on non-col lecti ng nodes, t he ID is usually the

Primary Alarm Output ID

anteed delivery to the primar y output device, and out put to th e secondary devic e only

File Transfer ID

. Both the

File Transfer ID

must match what is expected, or the FRX4000/6000 will not

Primary Alarm Outp ut ID

Primary Alarm Output ID

. The

Collecting

is being

of a collecting node. The alarm system is designe d for gua r-

4-4 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 57

if it is available. Problems with the secondary device will not stop deliver y to the primary device.

If specifying an as ync por t to a print er, be sure to c onfigur e the async PAD

profile (see Chapt er 12) to match the line spee d of the print er. (Do not con-

figure the port for

Primary Alarm Output Pwd

is a password that will be used with the lecting node, the local FRX4000/6000's match the collecting node ’s

Secondary Alarm Output ID

is used for a collecting node to send alarms to a second location other than that specified by the

Primary Alarm Outpu t ID

nodes.

Secondary Alarm Output Pwd

is a password that will be used if the also associated with a passwor d. I f so, both passwords must match.

Com. Port Thruput

is the line speed (in bits per second) through the COM port:

Autobaud

Collecting Node Pwd

Primary Alarm Output ID

Primary Alarm Output Pwd

. This parameter has no function on non-collecting

Secondary Alarm Output ID

. If that ID is a col-

(Password) must

is an address that is

= 110 bps

= 1200 bps

Com. Port Parity :

sets the parity bit, which is used to det ect changes in bit structure of the data from origin to destination:

Com. Port Stopbit

sets 1 or 2 stopbits, which signal the end of a character.

Bits per Character

sets the bit value at 7 or 8 per character.

Collecting Node

is an FRX4000/6000 to which a larms are sent from other Cabletron frame relay access devices. Any of the se devices can be a c oll ecting nod e; which nodes s end the ir alarms to a collecting node is determined by the the other nodes; these must match the lecting node.

The number of nodes that can report to a collecting node depends on the number of connections that can exist on the collecting node. (An FRX4000 supports up to 512 connections; a n FRX6000 supports up to 512 per R LP. ) A connection on a collecting node is required for each reporting device.

= 150 bps

= 2400 bps

= None,1 = Odd,3 = Even.

= 300 bps

= 4800 bps

Primary Alarm Output ID

Collecting Node ID

= 600 bps

= 9600 bps

s and passwords of

and password of their col-

Configuring Node-Wide Default Parameters 4-5

Do not configure a collecting node to send its alarm s to anoth er collecting node. The alarms will be ignored, du e to a format mismatch.

Page 58

Max Congestion

is a percentag e of the FRX4000/6000 alarm buffer. If this level is exceeded, no more alarms will be put into the buffer until it has reached the specified (See that entry below and "Alarm Buffer" on page 21-2.)

Min Congestion

is a perc entage of t he FRX4000/6000 alarm buf fer. As long as the percent of the buffer that is full is below this level, alarms will always be placed into the buffer. (See "Alarm Bu f fer" on page 21-2.)

Periodic Status Timer

sets the frequency with which the FRX4000/6000 will send a "heartbeat" alarm message containing the dat e and time. The heartbeat serves as a verification tha t the FRX4000/6000 is operationa l.

Line Idle Timer

is a period tha t an SVC ala rm connecti on wil l remain a ctive afte r a n alarm messa ge is sent. If no alarm is generated during this time, the alarm connection is cleared. The

Periodic Status Timer

this FRX4000/6000 will be sent. On a repor ting (non-collecting) node, it is gener ally preferable to s et the to give the s ystem a chance to update i tself. The tim er is usually set to node.

Min Congestion

determines the frequenc y with whi ch routine status mes sages for

Line Idle Timer

to a period longer than the

Periodic Status Timer

on a collecti ng

Line Idle Timer

The

Alarm Autocall Timer

specifies the freq uency with whic h the FRX4000/6000 will attempt to establish an alarm connection with its previous alarm connection is cleared.

Alarm Max Retries

is the number of times the FRX4000/6000 will attempt to establish an alarm connection with its alarm conne cti on i s clear ed .

If the value specif ied is greater than maximum retry value is reached. If the connection is still not established, a retry will be made once every hour.

is also affected by the value of

Primary Alarm Output ID

during initial call setup or after the previous

, the

Max Congestion

during initial call setup or aft er the

Alarm Autocall Timer

will be used until the

4-6 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 59

NetView Parameters

Parameter Valid Values Default Value

Name Local Subscriber ID Remote Subscriber ID

Maxim um Bytes per Frame 25–4105 265

Local SAP Address Local MAC Address 0–ffffffffffff 000000000000 IDBLK 0–fff 000 IDNUM 0–fffff 00000 T1

T2 Ti N3 1–127 1 Tw 1–127 1 N2 0–255 8 Priority 0–9 0 Bandwidth Allocation Group 1–16 1

1 2

3 4

Table 4-2 NetView Parameters

(msec)

none

10 100

(1 sec)

up to 8 char acters 0–15 char acters none 0–15 char acters none

0–fc

(hex)

0–250

(x 100 msec)

100–5000 1–50

(sec)

Up to 10 characters can be entered, but only the first 8 will be recognized by NetView. Be aware that som e NVMTs are larger than 265 bytes, so you may wa nt to set the value

higher. In multiples of 4. Must be le ss tha n th e value for T1 to ensure that the remote link station will receive the

delayed acknowledgment before T1 expires .

Name

is the VTAM PU name that will identify the FRX4000/6000 as a NetView Service Point.

Local Subscriber ID

is a subscriber address for the local end of an LLC2 session establishe d for a NetView connection. An LLC2 Host record (see page 9-18) must be create d, with

Type = Termina ted

and the same

Local Subscrib er I D

Remote Subscriber ID

and

Session

as spec-

ified here in the NetView parameters.

Remote Subscriber ID

is a subscriber address for the remote end of an LLC2 session established for a NetView connection. An LLC2 Host record (described on page 9-18) must be created,

Session Type = Originated, Local Subscriber ID

with ified here in the NetView par ameters, and

specified in the NetView parameters.

Maximum Bytes per Frame

Remote Subscriber ID

= the

spec-

Local Subscriber

must correspond to the PIU size configured on the NetView host (parameter MAXDATA of macro PU in VTAM).

Configuring Node-Wide Default Parameters 4-7

Page 60

Local SAP Addr ess

is a service access point (SAP) address used to identify the FRX4000/6000 to a NetView host. This parameter is relevant only in a connection to a 3174 or AS/400type setup where a spec if ic source SAP address is required. If the session will be run over a native LL C2 frame relay inter face, the parame te r will be igno re d .

Local MAC Address

identifies the local FRX4000/6000 to a NetView host. Like the local SAP address, this parameter is r elevant only i n a connection to a 3174 or AS/4 00-type setup where a specific source MAC address is required. If the session will be run over a native LLC2 frame relay interface, the parameter will be ignored.

IDBLK

is used in conjunction with (format 0 or 3) to e stabli sh a link station c onnec tion to the host . A furthe r expla nation is provided under "

IDNUM

is used in conjuction wit h 0 or 3) to establi sh a link station c onnection t o the host. If

IDNUM

and

, the Node field of the XID will be provided by the attached device. (The

node will send an XID command to the remote node to indicate that the device should be polled for an XID.)

is the Reply Timer, which is used to detect the failur e to receive a required acknowledgment or response from the remote link station . The link stat ion will star t the timer when it transmits one of these:

IDNUM

in generating the Node field in an XID frame

IDBLK

in generating the Node fie ld in an XID frame (format

is specified for both

IDBLK

●

an Information LPDU (LLC protocol data unit).

●

a Command LPDU wit h the P bi t set to B'1.' (If this LPDU is sent while the timer is already running, the link station will reset and restart it.)

The link station will reset

●

A REJ (Reject) LPDU, provided a Command LPDU with P bit set to B'1' is not

when it receives one of these:

outstanding.

●

A Response LPDU with the F bit set to B '1.'

●

An Information or Supervisory LPDU with an N(R) greater than the last N(R) received and less than or equal to the line station's V(

B'1

LPDU with P bit set to

' is not outstanding.

), provided a Command

If additiona l LPDUs are s et fr om the remote link sta tion afte r the loc al stat ion has res et

, the timer will be restarted if acknowledgments of or res ponses to those LPDUs are outstanding. If no acknowledgments/responses are outstanding, the link station will start the inactivity timer (

expires and acknowledgments/responses are still outstanding, the link station

If will send one of the following, then resta rt

●

A Supervisory LPDU with the P bit set to B'1' (to solicit r emote link station

status).

●

Any Unnumbered LPDUs that were not responded to the first time they were sent.

4-8 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 61

If acknowledgm ents/responses are still outstanding after N2 tries, the link station will declare the link inoper ative.

The value specified for

should allow for any delays introduced by the MAC sub-

layer (e.g., queuing).

is the Receiver Acknowledgment Timer, used by the link station to delay sending an acknowledgment of a receive d Infor mation LPDU. The timer is started when the LPDU is received and reset when the acknowledgment is sent. If the timer expires before the acknowledgment is sent , it must be sent as soon as possible.

is the Inactivity Timer, used by the link station to detect an inoperative condition in either the remote link station or the tr a nsmission medium. The timer will be started if

has been reset (for one of the reasons listed unde r "T1"), and additional LP DUs have been sent by the remote link station, and there are no outstanding acknowledgments or responses from the local link station.

If the local sta tion does not receive an LPDU before an LPDU with the P bit set to proceeds as described unde r "

B'1

' to solici t the remote station' s status. Recovery then

expires, the station must send

is the number of Inf ormation LPDUs tha t wi ll be receive d bef ore send ing an ac knowledgment. This parameter is used in conjunc tion with

to allow stations to reduce traffic. A counter is initialized to N3, and will be decremente d by one each time a valid sequential Information LPDU is received. When the counter reaches

an acknowl-

edgment is sent.

is reset wheneve r an Infor mation or S upervisory ac knowledgment LPDU is sent by

the local station.

is the maximum number of sequentiall y numbered In formation LPDUs that the link station can have outstanding.

is the maxim um number o f times th at a n LPDU ( incl uding Informat ion LPDUs res ent after a checkpoint operation) will be sent following expiration of

Priority

prioritizes NetView traffic among all intra-nodal traffic; the higher the number, the higher the priority. (This priority has no effect on traffic exiting an FRX4000/6000.)

Priorities ar e configured on all logical interfaces that use a physical frame relay port . The device processor in the node uses these priorities to help determine the order in which it will process protoc ols.

Bandwidth Allocation Group

assigns NetView session s to one of sixte en groups whose parameters regulate bandwidth usage. See "Configuring Bandwidth Allocation Groups" on page 7-6.

Configuring Node-Wide Default Parameters 4-9

Page 62

Warning Messages

These messages may be displayed on some screens if there is a problem with the configuration for alarm reporting.

Primary Alarm Reporting Error

will appear at the top of all screens on a collecti ng node if the software that drives the alarm output device is unable to output to the device.

Primary NOT Configured

will be displayed at the bottom of both Node Defaults screens if a

Output ID

Primary/Secondary C/P"n" NOT installed

will be displayed at the bottom of both Node Defaults screens if a seri al (C) or parallel

(

) port is specified for the the port is either incorr ectly configured or is not installed. For a seria l port, this message will also be displaye d if the card is properly installed but the device at the other end is not.

Primary/Secondary Printer/Connection Problem

will be display ed at the bottom of both screens if a parallel (P) port is specifie d and the card containing th e port is inst alled but the devic e at the othe r end is not. Note that this will not be determined by the software until the first alarm is sent to the para lle l por t.

is not specified.

Primary/Secondary Alar m Output ID

Primary Alarm

, but the card containing

Primary/Secondary C/P"n" NOT Initialized

will be displayed at the bottom of all both screens if a serial or parallel port is specified, but ei ther the sof tware cannot find the specifi ed port or it is in use f or some other purpose.

Errmsg.txt Database Error

will be displayed if the file ERRMSG.TXT can not be found . (This may happen if a software update was not correctly installed.) To correct thi s on an FRX4000, the file can be transferre d from a remote FRX4000/6000 or copied from a locally a ttached PC (with Procomm), as described on page 18-10. On an FRX6000, t he fi le can be c reated with the following procedure:

1. Press

2. When asked:

[F10]

at the Main Men u.

Reboot the Netlink FRX6000?

3. As the node starts to boot, press

4. When asked:

5. At the DOS prompt, type

Terminate batch job?

generr.exe [Enter]

6. To restart the FRX6000, type

[Ctrl] [C]

omni4 [Enter]

, press

[Y]

, press

. . .

[Y]

4-10 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 63

Chapter 5

Configuring Cards and Protocols

The circuit ry that supports the serial I/O ports in an F RX600 0 resides on one or more RLPs (RISC-based line process or cards), and on one or two four-port Line Interface Cards (LICs) mounted on each RLP . In an FRX4000, the functional ity of one RLP and four serial ports is buil t into the system board (motherboard), and four (or one, if T1 or E1) more serial ports can be added by installing an LIC.

The FRX6000 uses the RLP file to identify installed RLPs. The FRX4000 and FRX6000 use the file to identify the type (s ) of installed LIC(s), amount of install ed memory, and installed routing a nd access protocols.

The FRX4000 and FRX6000 use the LAN Card file to identify installed LAN cards/interfaces. Each FRX6000 is shipped with one LAN card (Ethernet or Token Ring, depending on the mod el purchase d), Each FRX4000 is s hippe d with a n int egral LAN interface (Ethernet or Token Ring, depending on the model purchased).

FRX4000

Protoc ols and LIC

The Protocol Configuration scree ns cont ain this information for an FRX4000:

To access the Protocol scree ns, press To identify any install ed Line Interface Car d and display a list of configured and

installed protoc ols, press protocols available in the node, press

When an FRX4000 is booted, the software reads the configuration of any installed serial expansion car d, as well as the amount of DRAM. This information will then be read into the display.

●

Amount of DRAM memory installed.

●

Type of Line Interface Card. (The seria l expan sion card in an FRX4000 is i dentical to the FRX6000 Line Interface Card.)

●

Configured and loaded protocols. A newly added protocol is displayed as

figured

until the node is rebooted, at which time the pro tocol will be displayed

Loaded

X.25 is always loaded, and will not be displayed. The informatio n is taken from the conf iguration f il e, which doe s not all ow configur ing X.25. This pr events the pos siblilit y of deleti ng X. 25, whic h is a necessary protocol for use by internal FRX4000 traffic.

[A]

at the RLP Configuration Menu. (To display a list of all

[A]

, then

[B]

from the Main Menu.

[A]

, then

[G]

from the Main Menu.)

Con-

Page 64

For reference, the following figure shows the ports on an FRX4000.

Optional

CSU/DSU

Port

LAN Port

Ports 4–7 are on optional expansion module

WAN 4 WAN 5 WAN 6 WAN 7

Console

Port

WAN 0 WAN 1 WAN 2 WAN 3

Figure 5-1 Serial Ports on an FRX4000

The above example shows a V.35, RS-232, or RS-422 expansion car d. A T1 or E1 expansion card will contain Port 4 only.

[C]

To display a table of memory usage, press

at the RLP Configuration Menu. This information, in conjuction with inf ormatio n in the release notes, can help in planni ng the number of protocols to run.

To configure a protocol, pres s

RLP Configuration * RLP: 0 * Status: Installed * Memory Configuration: 8 Meg * RLP Type: RLP * Line Interface Card 1: UNIVERSAL * Line Interface Card 2: T1-DSX1 D Configure T1/E1 LIC2

F Protocol 1: FR FR G Protocol 2: IP IP H Protocol 3: Async Async I Protocol 4: SDLC SDLC J Protocol 5: BSCI BSCI K Protocol 6: None L Protocol 7: None M Protocol 8: None N Protocol 9: None

Option:

[B]

at the RLP Configuration Menu.

Node Name=nodexyz

Configured Loaded

Figure 5-2 Protocol Configuration Menu for FRX4000

RLP

above. The line Card is

5-2 FRX4000/FRX6000 4.0 User Guide, Rev 01

Status, RLP Type

Line Interf ace Card 2

Configure T1/E1 LI C 1

or E1.

[A],[B],[B]

Line Interface Card 1

, and

from Main Menu

will always be as shown

will be read from the installed card (if present) .

(or 2) is displayed if either Line Interface

Page 65

To add or remove a protocol, press the letter corr esponding to the protocol number. The protocol in the

Configured

column will change to the next valid one.

(See Table 5-1.)

[F3]

After all desired changes have be en made, press

to save the c hanges, then reboot

the FRX40004 as follows:

Rebooting will clear all connection s on th is devic e. However, the device must be rebooted to implement the change.

1. Press

2. When asked:

3. Type

[F10]

Reboot the Node?

restart [Enter ]

FRX4000 Protocol Parameters

Table 5-1 FRX4000 Protocol Parameters

Parameter Valid Values Default Value

Protocol "n"

T1 LIC Parameters

Line Coding B8ZS/AMI B8ZS Framing ESF, D4 ESF Line Service Fu ll, Fr ac tio na l Full

Line Build Out Clocking Master, Slave Slave Base Chl Speed 56K, 64K 64K

Starting Chl Number

Num of Chnls

E1 LIC Parameters

Line Coding HDB3 HDB3 Framing G.704 G.704 Line Service Fu ll, Fr ac tio na l Full Line Build Out G.703 G.703 Clocking Master, Slave Slave Base Chl Speed 64K 64K

Starting Chl Number

continued on next page

[Y]

, press

None, X.25, FR (frame relay), Async, SDLC, BSC-I, BSC-B, IP, SNMP, RIP, LLC2, IPX, NVSP (NetView Service

Point), BRIDGE

see foot note

Line Service

If Line Servi ce

Line Service

If Line Servi ce

Line Service

If Line Servi ce

Fractional: 1–24

Full: n/a

Fractional: 1–24

Full: n/a

Fractional: 1–30

Full: n/a

next in list not already co nfigured

0–133 ft. (0 dB)

(only if

1 vice

(only if

24 vice

(only if

1 vice

Line Ser-

Fractional)

Line Ser-

Fractional)

Line Ser-

Fractional)

Configuring Cards and Protocols 5-3

Page 66

Protocol

determines which protoc ols can run in the node. Although the FRX4000 contains a group of protoc ols in the s oftware whe n shipped to t he customer , the y must be loa ded into the operating software (by configuring them in the RLP file, then rebooting the node).

Table 5-1 FRX4000 Protocol Parameters

(continued)

Parameter Valid Values Default Value

Line Service

Num of Chnls

CRC-4 Disabled Y/N N Chnl Signalling Common, Associated Common Ntnl Use Bit "n" On, Off Off

IntNtnl Use Bit 0, 1 CAS X1/2/3 Bit On, Off Off

CAS A/B/C/D Bit

All of the se mi ght not be av ailab le on an FRX40 00. It depe nds on whi ch pr otocol s were

If Line Servi ce

On, Off On

On, Off Off

purchas ed. Also, note t he guideli nes in the exp lanatio n. X.25 i s alway s loaded, and is no t a configurable option. This prevents the possiblility of deleting X.25, which is a necessary protocol for use by internal SmartSwitch traffic.

Selecting this parameter changes the value to the next one in this list:

0–133 ft. 15 dB, minus 22.5 dB.

Display ed only if

133–266 ft., 266–399 ft., 399–533 ft., 533–655 ft., minus 7.5 dB, minus

(0 dB),

CRC-4 Disabled Chnl Signaling

Fractional: 1–30

Full: n/a

is N.

Associated

(only if

Fractional)

Line Ser-

30 vice

Follow these guidelines whe n configuring protocols:

●

RIP is a valid choice only if IP is already specified.

●

If SNMP is configured, IP must also be configured.

●

If LLC2 is configured, BRIDGE must also be configured.

●

If NVSP is configured, LLC2 and BRIDGE must also be configured.

T1 LIC Parameters

Line Codi ng

specifies t he physical line encoding technique used to carry clock signals, per AT&T ACCUNET T1.5 Service Description and Interface Specification. Note that B8ZS stands for Bipolar Eight Zero Code Substitution, and AMI is Alternate Mark Inversion.

Framing

specifies the T-1 framing format, per ANSI T1.403, 1995. Note that ESF stands for Extended Superframe Format.

Line Service

determines whether full or channelized T-1 will be run over the LIC port.

With the exception of X.25, protocols must be configured in the Protocol file before they can be configured on ports.

5-4 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 67

Line Build Out

is based on the dista nce from the FRX4000 to t he exter nal T1 devi ce, and is nor mally dictated by the telephon e company tha t supplies the line.

Clocking

determines whether cloc k will be generated by the FRX4000 T1 port ( remote device (

Base Chl Speed

determines the line speed ove r each channe l.

Starting Chl Number

determines the lowest channe l number that will be used.

Num of Chnls

is the number of channels that will be used on the T1 line.

E1 Parameters

Line Codi ng

is the line coding technique used to carry clock signals.

Framing

is the frame format. G.704 is a CEPT standard, with a set value.

Slave

Master

) or the

Line Service

determines whether full or channelized T-1 will be run over the LIC port.

Line Build Out

relates to t he distance from the FRX4000 to the external E1 device. G.703 is a CEPT standard, with a set value.

Clocking

determines whether cloc k will be generated by the E1 port ( device (

Base Chl Speed

Slave

determines the line speed ove r each channe l.

Starting Chl Number

determines the lowest channe l number that will be used.

Num of Chnls

is the number of channels that will be used on the T1 line.

CRC-4 Disabled

disables (if Y) the generation of CRC-4 (polynomial X4 + X + 1).

Chnl Signalling

is the mode of the CEPT interface.

Master

) or the remote

Configuring Cards and Protocols 5-5

Page 68

LAN Port

Ntnl Use Bit "n"

is the setting of the n ation al use bits in the non -fra me alignment signal. National use bits 1-5 correspond to data bits 4-8 in the non-frame alignment signal. National use bits are reserved for use within a country. If the signal will cross an international border, the national use bits should be Off.

IntNtnl Use Bit 0

is the setting of bit 0, which is transmi tted as the most significant bit of the frame alignment signal when CRC-4 is disabled.

IntNtnl Use Bit 1

is the settin g of bit 1, which is trans mitted as t he most signif ica nt bit of the non- frame alignment signal when CRC-4 is disabled.

CAS X1/2/3 Bit

determines whether spar e bits X1, X2, and/or X3 will be used.

CAS A/B/C/D Bit

determines whet her signaling bits A, B, C, and/or D will be used in timeslot 16 whe n

Chnl

(Channel)

Each FRX4000 conta ins a LAN port, either Ethe rnet or Tok en Ring (dep ending on the model). To configure the port, press

Signaling

Associated

[B]

at the Port Configuration Menu.

LAN Card Configuration * Interface Number: 0

*Type Token Ring B Locally Admin MAC Addr 400000000001 C Ring Speed 16 MBits/sec

Option:

Figure 5-3 LAN Port Configuration Record

[A],[C],[B]

Item C (

Ring Speed

) will not be displayed if

Node Name=nodexyz

from Main Menu

Type

Ethernet

5-6 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 69

This screen is called is shared with the FRX6000 and 9W004, both of which contain one or (FRX6000 only) two LAN cards.

LAN Card Parameters

Parameter Valid Values Default Value

Locally Admin. MAC Addr 000000000000–7fffffffffff f 000000000 000 Ring Speed

Token Ring FRX40 00 only.

Locally Admin. MAC Addr

is a MAC addre ss that will override the universally administered MAC address. If all zeros are speci fied, the universa l address wil l be used. Und er most circumstanc es, this parameter should be left at the default setting.

Ring Speed

specifies the speed of the ring to which the port will connect.

LAN "Card" Configuration

because the software code

Table 5-2 LAN Card Parameters on FRX4000

4 MBits/sec

16 MBit s/sec

16 MBits/sec

FRX6000

RLPs and Protocols

The RLP file contains this information for each RLP in an FRX6000:

●

To access the RLP screens, press To display a list of inst alled RLPs, int erface cards, and protocols, press

Configuration Menu. (If an RLP is displayed as for the RLP, but the car d does not ph ysical ly exist in the node .) When an FRX60 00 is booted, the software reads the configuration of all installed RLPs, Line Interface Cards, and on-board memory. This infor mation will then be read into the display.

To display a table of memor y usage by all R LPs in the node , pr ess figuration Menu. Th is information, in co njuction with informati on in the release not es, can help in planning the number of protocols to run.

RLP number and status (Install ed, Configur ed). Amount of memory installed (4MB or 8MB). Type(s) of Line Interface Card(s). Configured and loaded protocols. A newly added protocol is displayed as

figured

until the node is rebooted, at which time the pro tocol will be displayed

Loaded

[A]

, then

[B]

from the Main Menu.

Configured

, a database record exists

[A]

at the RLP

[C]

at the RLP Con-

Con-

Configuring Cards and Protocols 5-7

Page 70

To configure an RLP, LIC, or protocol, pres s When prompted, enter the RLP numb er:

[B]

at the RLP Configuration Menu.

0–7

. (RLP numbers are determined by switch settings on the cards—s ee Figure 5-4.) When an FRX6000 is shipped from Cabletron, any installed RLPs are configured to be numbered consecutively from right to left, starting with

, when the unit is viewed from the rear.

RLP

Off

LIC 1

LIC 2

RLP Switch

8 76 54 3 2 1 0OnOff 1 OnOnOff 2OnOffOn 3OnOffOff 4 Off On On 5 Off On Off 6OffOffOn 7 Off Off Off

T1 or E1 Converter

Off On Off On On On

Switch 7 is Off for 8 MB RLP, On for 4 MB RLP.

RLP Cable

Figure 5-4 FRX6000 RLP, LICs, and Cables

5-8 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 71

Figure 5-5 RLP Configuration Menu for FRX6000

Node Name=nodexyz

RLP Configuration

* RLP: 1 * Status: Installed * Memory Configuration: 8 Meg

* RLP Type: RLP B Line Interface Card 1: V.35 C Line Interface Card 2: T1-DSX1 D Configure T1/E1 LIC2

Configured Loaded F Protocol 1: X.25 X.25 G Protocol 2: FRL FRL H Protocol 3: Async Async I Protocol 4: SDLC SDLC J Protocol 5: IP IP K Protocol 6: None L Protocol 7: None M Protocol 8: None N Protocol 9: None

Option:

[A],[B],[B]

from Main Menu

To add or remove a protocol, press the letter corr esponding to the protocol number. The protocol in the (See Table 5-3.)

After all desired changes have be en made, press the 9W004 as follows:

1. Press

2. When asked:

3. Type

Configuring Cards and Protocols 5-9

The line Card is

Configure T1/E1 LI C 1

or E1.

(or 2) is displayed if either Line Interface

Although nine protocol entries are shown, a 4MB RLP supports a maximum of five.

Configured

column will change to the next valid one.

[F3]

to save the c hanges, then reboot

Rebooting will clear all connection s on th is devic e. However, the device must be rebooted to implement the change.

[F10]

Reboot the Node?

restart [Enter ]

, press

[Y]

Page 72

FRX6000 RLP Parameters

Parameter Valid Values Default Value

RLP Type None, RLP None Line Interface Card 1, 2

Protocol "n" None, X.25, Frame Relay, Async,

T1 LIC Parameters

Line Coding B8ZS/AMI B8ZS Framing ESF, D4 ESF Line Service Fu ll, Fr ac tio na l Full

Line Build Out Clocking Master, Slave Slave Base Chl Speed 56K, 64K 64K

Starting Chl Number

Num of Chnls

E1 LIC Parameters

Line Coding HDB3 HDB3 Framing G.704 G.704 Line Service Fu ll, Fr ac tio na l Full Line Build Out G.703 G.703 Clocking Master, Slave Slave Base Chl Speed 64K 64K

Starting Chl Number

Num of Chnls

CRC-4 Disabled Y/N N Chnl Signalling Common, Associated Common Ntnl Use Bit "n" On, Off Off

IntNtnl Use Bit 0, 1 CAS X1/2/3 Bit On, Off Off

CAS A/B/C/D Bit

T1 and E1 LICs are supported onl y on the 8-MB RLP.

The size of each protocol and the amount of RLP memory determine the combinations of proto cols that can be configured on an RLP. (See expla nation.)

Selecting this parameter changes the value to the next one in this list:

0–133 ft. 15 dB, minus 22.5 dB.

Display ed only if

Table 5-3 FRX6000 RLP Parameters

None, RS-232, RS-422, V.35, T1-DSX1, E1-75ohm, T1-RFU, E1-120oh m

SDLC, BSC-I, BSC-B, IP, SNMP, RIP, LLC2, IPX, NVSP, BRIDGE

see foot note

Line Service

If Line Servi ce

Line Service

If Line Servi ce

Line Service

If Line Servi ce

Line Service

If Line Servi ce

(0 dB),

On, Off On

On, Off Off

133–266 ft., 266–399 ft., 399–533 ft., 533–655 ft., minus 7.5 dB, minus

CRC-4 Disabled Chnl Signaling

Fractional: 1–24

Full: n/a

Fractional: 1–24

Full: n/a

Fractional: 1–30

Full: n/a

Fractional: 1–30

Full: n/a

is N.

Associated

None

next in list not alre a dy configured, among the

ones that w ill fit

0–133 ft. (0 dB)

(only if

vice 24

(only if

vice

(only if

vice 30

(only if

vice

Line Ser-

Fractional)

Line Ser-

Fractional)

Line Ser-

Fractional)

Line Ser-

Fractional)

5-10 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 73

RLP Type

Cannot be change d if th e RLP is i nstalle d. I f it is no t insta lled, the va lue chan ges each time you press

[A]

If you replace a Line Interface Card with one of a different type, any related port records will have some invalid values. Be sure to change them as needed.

Line Interface Card 1, 2

contain the circuit ry for the physical ports of an RLP. If the card is not installed, the value changes to the next one in the list each time you press Once the node is booted with the card installed, the software will read the LIC type, and this parameter cannot be changed.

to select the para meter.

[B]

to select the parameter.

Protocol

specifies which protocols will run on the RLP. When a new node is started up, X.25 will be loaded onto every RLP, and a software function called CONFI G will be loaded onto the lowest-number ed RLP in the node. When you configure a new record, X.25 (and possibly CONFIG ) will already be displayed as installed. For each remaining protocol, the available choices will be those protocols not alrea dy specified that will fit on the RLP. (If you create a new record later for a new RLP, X.25 will be the only available choice for Protocol 1.)

When configuring protocols, follow these guidelines:

LIC Type

LIC 1 LIC 2 RS-232 Ports 0-3 Ports 4-7 RS-422 Ports 0-3 Ports 4-7 V.35 Ports 0-3 Ports 4-7 T1 Port 0 Port 4 E1 Port 0 Port 4

Neither CONFIG nor RIP can be configured on a 4MB RLP.

●

All supported protocols will fit on one 8MB RLP; however, as an entire database (interfaces, subscribers, route tables, etc.) is configured, much more memory is used. For that r eason, it i s recommended t hat no more than seven p rotocols (including X.25) be configured on any one RLP.

●

RIP is a valid choice only if IP is already configured on the same RLP.

●

If SNMP is configured, IP must als o be configure d on one RLP. (SNMP and I P can be, but do not have to be, on the same RLP.)

●

If LLC2 is configured, BRIDGE must also be configure d in the node. Bot h protocols should be (for better perf ormance), but do not have to be, on the same RLP.

●

If NVSP is configured, LLC2 and BRIDGE must also be con figured in the node. (All three protocols can be, but do not have to be, on the same RLP.)

●

IP, SNMP, RIP, IPX, LLC2, NVSP, and BRIDGE cannot be configured on more than one RLP each. ( However, more than one of the se can be on th e same RLP.) Performance can be enhanced by c onfiguring the se prot ocols on th e same RLP(s) that contain the frame relay ports that will transport the protocols.

Configuring Cards and Protocols 5-11

Page 74

T1 LIC Parameters

Line Codi ng

Framing

specifies the T-1 framing format, per ANSI T1.403, 1995. Note that ESF stands for Extended Superframe Format.

Line Service

determines whether full or channelized T-1 will be run over the LIC port.

Line Build Out

is based on the distance from the RLP to the external T1 device, and is normally dictated by the telephone company tha t supplie s the line.

Clocking

determines whether cloc k will be generated by the T1 port ( device (

Base Chl Speed

Slave

determines the line speed ove r each channe l.

Master

) or the remote

Starting Chl Number

determines the lowest channe l number that will be used.

Num of Chnls

is the number of channels that will be used on the T1 line.

E1 Parameters

Line Codi ng

is the line coding technique used to carry clock signals.

Framing

is the frame format. G.704 is a CEPT standard, with a set value.

Line Service

determines whether full or channelized T-1 will be run over the LIC port.

Line Build Out

relates to the distance from the RLP to the externa l E1 devi ce. G.703 is a CEPT standard, with a set value.

Clocking

determines whether cloc k will be generated by the E1 port ( device (

Slave

Master

) or the remote

Base Chl Speed

determines the line speed ove r each channe l.

5-12 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 75

Starting Chl Number

determines the lowest channe l number that will be used.

Num of Chnls

is the number of channels that will be used on the T1 line.

CRC-4 Disabled

disables (if Y) the generation of CRC-4 (polynomial X4 + X + 1).

Chnl Signalling

is the mode of the CEPT interface.

Ntnl Use Bit "n"

IntNtnl Use Bit 0

is the setting of int ernatio nal use bit 0, which i s trans mitted as t he most signif icant bit of the frame alignment signal when CRC-4 is disabled.

IntNtnl Use Bit 1

is the setting of int ernatio nal use bit 1, which i s trans mitted as t he most signif icant bit of the non-fram e alignment signal when CRC-4 is disabled.

CAS X1/2/3 Bit

determines whether spar e bits X1, X2, and/or X3 will be used.

CAS A/B/C/D Bit

determines whet her signaling bits A, B, C, and/or D will be used in timeslot 16 whe n

Channel Signaling

Associated

Configuring Cards and Protocols 5-13

Page 76

LAN Cards

You can display a report that identif ies any LAN cards in the node. Press Port Configura tion Menu (or

[A], [C], [G]

from the Mai n Menu). The di splay will be the

[G]

at the

contents of the file PROTOCOL.INI (which can also be printed from DOS or copied to a diskette—see "Database Backup and Restore" on page 18-6). One line of PRO- TOCOL.INI,

Bindings = "nnn,"

can be r ead to easily identify the installed LAN cards,

as shown in the following table.

Table 5-4 LAN Card Identification in FRX6000

LAN Card 0 LAN Card 1 Bindings =

SMC Eth ernet no t in s ta lle d SMC Ethernet SMC Ethernet SMC Token Ring not installed SMC Token Ring SMC Token Ring SMC Token Ring SMC Ethernet SMC Ethernet SMC Token Ring IBM Token Ring not installed IBM Token Ring IBM Token Ring IBM Token Ring SMC Ethernet SMC Ethernet IBM Token Ring

SMCMAC8001 SMCMAC8001,SMCMAC8002 SMC8100_NIF SMC8100_NIF,SMC81002_NIF SMC8100_NIF,SMCMAC8001 SMCMAC8001,SMC8100_NIF NLK_TOK NLK_TOK,NLK_TOK2 NLK_TOK,SMCMAC8001 SMCMAC8001,NLK_TOK

The SMC cards are the current LAN cards available from Cabletr on. The IBM card is supported for existing customers.

The Netlink FRX60 00 Maintenance Gui de describes the complete contents of PROTOCOL.INI and the LAN configur ation part of CONFIG.SYS.

To configure a record for a LAN card in an FRX6000, press

[B]

at the Port Configuration Menu. (Unlike serial ports, there are not separate files for the cards and the ports.) When prompted for an

Interface Number

, type

[0] [Enter]

[1] [Ent er ]

whichever number corresponds to the card as defined in PROTOCOL.INI.

5-14 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 77

[F7]

Node Name=nodexyz LAN Card Configuration * Interface Number: 0

A Type Token Ring B Locally Admin MAC Addr 400000000001

Option:

Press

after making any changes, to send the configur ation to the LAN interface.

If the node is connected to a LAN after this record is created, or if the node becomes disconnected fr om the LAN, the LAN connection must be initialized/re-initialized by opening Lan Card Configuration, then pressing

[F7]

is connected to the LAN before performing this operation.)

LAN Card Parameters

Parameter Valid Values Default Value

Type Ethernet, Token Ring Locally Admin. MAC Addr 000000000000–7fffffffffff f 000000000 000

Must match the installed card th at corresponds to the spec ified

Figure 5-6 LAN Card Configuration Screen

[A],[C],[B]

from Main Menu

to send the configu ration to the LAN inter face. (Be sure the FRX6000

Table 5-5 LAN Card Parameters on FRX6000

Ethernet

Interface Number

Type

is the type of LAN card.

Locally Admin. MAC Addr

Configuring Cards and Protocols 5-15

Page 78

Page 79

Serial ports provide acc ess connections to non- LAN devices and routi ng connections

Ports 4–7 are on optional expansion module

4567

0123

to networks. Each port must be configured in the software to specify the operating parameters of the hardware and the protocol that will run on the port.

The FRX4000 and FRX6000 also support logical X.25 ports, which run on a physical frame relay port. Configuration of logical ports is described in

Chapter 8.

Locations of Physical Ports

FRX4000

Chapter 6

Configuring Physical Ports

Four serial connectors in the FRX4000 reside on the system board. An optional expansion card offers one or four more port s, de pen ding on the type of card.

Figure 6-1 Physical Ports on FRX4000

The physical interfac es are as follows:

●

Ports 0 and 1 are RS-232.

●

Ports 2 and 3 are determ i n ed by the at tach e d Ca b le tro n ca bles: RS- 2 32, V.3 5, RS-449, or X.21.

●

Ports 4–7 are determined by the expansion card (Line Interface Card ) and attached I/O c ables. The RLP record identifies the Line I nterface Card, and only the valid inter faces will be displayed in the Port record, among: RS-232, V.3 5, RS-449, X.21, T1, and E1. (RS-449 or X.21 requires an RS-422 LIC, which is available by special order.) Note that a T1 or E1 LIC supports one port (port 4).

Configuring Physical Ports 6-1

Page 80

FRX6000

The physical connectors in an FRX6000 reside on the RLPs, but the circuitry that defines the physical port types is on at tached Line Interface Card s (LIC s ). An RLP contains up to two LICs. LIC 1 supports ports 0–3, and LIC 2 supports ports 4–7.

RLP

LIC 1

LIC 2

RLP Cables

I/O Box

I/O Cables to Modems and User Devices

Figure 6-2 Physical Ports on FRX6000 RLP

The above figure shows an example of two four-port LICs. A T1 or E1 LIC provide s one port. The ports supported by each LIC type are:

LIC Type LIC 1 LIC 2 RS-232 Ports 0-3 Ports 4-7 RS-422 Ports 0-3 Ports 4-7 V.35 Ports 0-3 Ports 4-7 T1 Port 0 Port 4 E1 Port 0 Port 4

6-2 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 81

Database and System Memory Values

Two sets of values exist for Port parameters: Da tabase values exist in the software, and are recorded as System Memory values whe n the node is booted. If the port type is the same in both sets of values, both sets will be dis played.

Any change you make will be recorded as a Database value, and will be copie d to the System Memory side only if you press saved to the database until you press

[F7]

[F3]

. Note that changes will not be actually be

to exit the record.

Pressing you press you press

without disable?

[F7]

will display:

[Y]

, the link will be disabled, parameters c opied, and the link re-ena bled. If

[N]

, you will be prompted:

Pressing

not require disabling the link. Pressing

Configuring a Physical Port

Before configuring a physical port, make sure that the following have been properly configured:

●

Node parameters. See Chap ter 4. This is general config uration that must be done

no matter which protocols will be run in the node.

●

RLP that conta ins the port, plus Line Interface Card that supports the port. See

Chapter 5.

●

Protocol(s) tha t will be transmitted over the physical port and any logical ports

on the physical port. See Chapter 5.

Once these necessa ry records have been configur ed, press

Configure Ports

(

●

(FRX6000 only) are described in Chapter 5.)

Port

●

), then

(see Figure 6-1 or Figure 6-2):

On-line changes disable link, are you sure you want t o?

Do you want to change port parameters partially

[Y]

will propagate any changes to those parameters that do

[N]

will return you to the next higher screen.

[A] (Configuration

[A]

from the Main Menu. As prompted, enter:

RLP

containi ng the port:

0–7

. (The default is 0.) (RLP numbers

0–7

. (The default is 0.)

), then

[C]

The display for an existing recor d will show the configured parameter values, while the display for a new record will show values stored in a default database record. The following figure is an exampl e of a new record.

Configuring Physical Ports 6-3

Page 82

X.25 Port Parameters (screen 1 of 6) * RLP: 0 Port: 5 Link State: Link_disable *I/O:V.35

A Port Type X.25 X.25 B Physical Port Interface V.35 V.35 C Blocked Port Flag N N D Line Speed 9600 bps 9600 bps E Modulo 8 8 F Maximum LAPB Window Size 7 7 G N2 Retransmit Count 5 5 H T1 Retransmit Period (msec) 2000 2000 I T2 Wait Ack Period (msec) 1000 1000 J T3 Link Alive Period (sec) 10 10 K Logical DCE N N L Generate Clock N N M Rcv Clock (TT) from DTE N N

Option:

Database System Memory

Rmtid=nodexyz

Figure 6-3 Default Configuration Screen for New Port

[A],[C],[A]

from Main Menu

The entry 0–3), and

Link_disable

I/O

identifies the LIC containi ng the port (

Link State

will be one of these:

– The link was shut down by an on- line comma nd, is unde rgoing re-

UNIVERSAL

for FRX4000 ports

IPL, or has not yet been established.

Failed

– Some or all modem controls are missing. (This state is passe d through

while a port is becoming enabled.)

Link_down Disconnect Linkup

– The link was up, but has gone down.

– Level 2 cannot be established.

– The necessary level 1 modem signals are present, and the level 2 link is

up.

– Some state other than those above has been entered.

To configure the port with the parameter values neccessary for your application, g o to the approp riate chapter:

●

Frame relay – Chapter 7

●

X.25 – Chapter 8

●

SNA – Ch apte r 9

●

BSCI – Chapter 10

●

BSCB – Chapter 11

●

Async – Chapter 12

If configuring a physical port that will contain logical ports, configure the physical port as desc ribed in the appropria te chapter in the a bove list, then follow t he procedure under "Configuring Logical X.25 Ports" on page 8-14.

6-4 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 83

Introduction

Chapter 7

Configuring Frame Relay

Frame relay ports in t he FRX4000 a nd FRX6000 a re used t o carr y frame relay t raffi c, as well as othe r protocols enc apsulated in frame relay (per RFC 1490, via logical X. 25 ports over frame relay). A frame relay port can act as physical DCE (non-T1/E1 port only), connecting t o end-use r devices, or DTE, connecting to a network or f rame relay PVC.

Frame relay support includes:

●

RFC 1490 for HDLC, IP, IPX over frame relay

●

Line speeds up to 2.048 Mbps

●

LMI, Annex D link management

●

Annex F segmentation and re-assembly

●

Bandwidth allocation

●

Connection prioritization

●

Incoming and outgoing rate control (CIR)

●

Virtual circuit ba ckup for single or multiple PVCs/DLCIs, inc luding bandwidth allocation on backup circuits

A frame relay port can contain multiple logical ports or channels.

Port Type Maximum Logical Ports/Channels T1 24 channels per port E1 30 channels per port Other 56 logical ports in FRX4000, 56 per RLP in FRX6000. All 56

logical ports can r eside on one physical port, or be spread over se veral physical ports

Page 84

DLCI Sharing

Each logical connection on a physi cal f rame relay port is assigned a Data Link Connection Identifie r (DLCI), which identifies a point-to- point connection, as shown in the following example. (The numbers represent DLCIs.)

Multiple protoc ols can be passed over a single physical frame relay port by sharing a DLCI. Each node supports up to 976 user-conf igurable DLCIs. (Severa l more are supported, but are reserved for int ernal use .)

Frame Rel ay Ba c ku p

Frame relay virtual-c ir cuit backup in the FRX4000/FRX6000 provides frame relay DLCIs with automatic backup prote ct ion in the event of LMI loss or port failure. (A DLCI is considered do wn/inactive if le vel 1 is down . If LMI is use d, the DLCI is also considered inactive if not reported as active in a Full Status Message from the DCE.)

A physical frame relay port can be dedicated to providing backup DLCIs, or backups can co-exist with "regula r" DLCIs on a port.

In a backup configuration, one e nd is consi dered the "initiati ng" node a nd the ot her the "remote" node. The ini tiatin g end is the one t hat wil l esta blish th e backup link if it discovers that the primary link is down. (A node can be the initia ting node for some backup configurati ons and the remote node for others.)

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.

DLCIs used for backup on the initiating node are assigned to "bac kup groups," each of which can contain up t o ten ba ckup DLCIs. A ba ckup group is then a ssi gned to one or more "primary" DLCIs (the ones that will be backed up) .

The basic procedure for configuring backup DLCIs is:

1. Configure all DLCIs that will be backed up or used as backups. All parameters can be configured f or each DLCI exce pt spec ifying a

Backup Group Number

on a primary DLCI (that will be backed up) o n an "initiating" node (which will i nitiate the switchover to a backup DLCI).

2. Configure backup groups. A ba ck up group is one or more DLCIs that will act as backup if the primary goes down.

3. Configure

Backup Group Number

s and related information f or prim ary DLCIs.

This will assign a Backup Group to each primary DLCI.

For each examp le in Figure 7-1, assume that Node 1 is a remote site and Node 2 is a central site. Also assume that Node 1 will be the initiating node. On that node, the primary DLCI is on port 2 and the backup is on port 0.

7-2 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 85

Example 1 Node 1

Example 2 Node 1

Example 3 Node 1

2,16 0,17

0,0,18

0,4,17

Node 2

Port,DLCI

RLP,Port,DLCI

0,0,18

Node 2

2,16

0,17

2,16 0,17

0,0,18

0,4,17

Node 2

1,3,22 1,4,56

Other Device

Example 1

Figure 7-1 Frame Relay Backup Examples

Although each example shows an FRX4000-to- FRX6000 connection, connections can be between any two Cabletr on fra me relay access devices in the family of FRX, SmartSwitch 1840, and FRM. In an FRX6000, the primary and backup DLCIs must be on the same RLP, or a PVC must be configured between the DLCIs.

In Example 1, the primary link is between Node 1/Port 2/DLCI 16 and Node 2/RLP 0/Port 0/DLCI 18. The DLCIs should be configured as described below. (The parameters are described later in this chapter.) Then if the primary link goes down, a connection will automatically be established between Node 1/Port 0/DLCI 17 and Node 2/RLP 0/Port 4/DLCI 17.

On Node 1, configure the following (as well as oth er parameters necessary for operation—this section deals only with the frame relay backup function):

1. Port Configuration (

RLP: 0

Configuring Frame Relay 7-3

RLP Port: 2

[A], [C] , [A ]

O Additional Parameters

D Configure DLCI Parameters

DLCI ID: 16

E For Backup Use Only: N

I DLCI Backup Configuration

A Backup Group Number: 10 B Enable Backup Protocol?: N

from Main Menu) for the primary:

(or any unused number except 0)

Page 86

2. Port Configuration (

RLP: 0 RLP Port: 0

F Logical DCE: N

Configuring the central site as logical DCE allows the line monitor at that end to track incoming s tatus enquiries from the DTE end. )

O Additional Parameters

D Configure DLCI Parameters

DLCI ID: 17

I DLCI Backup Configuration

A Backup Group Number: 0 B Enable Backup Protocol?: N

E For Backup Use Only: Y

[A], [C] , [A ]

from Main Menu) for the backup:

(One end of the backup m ust be logic al DTE, and the other DCE.

(Not necessar y becaus e pr otocol is

enabled in Frame Relay Backup Group record.)

3. Frame Relay Backup Groups Configuration (

Frame Relay Backup Group Number: 10

ARLP:0 CPort:0 DDLCI:17 E WaitTimer: 60

should be reasona bly greater than th e

(seconds) (or any number i n range

[A], [F], [B]

Switchover Timer

from Main Menu):

0–65535

; however, the sett ing

on the primary {RLP 0/

Port 0/ DLCI 17 } being ba c k ed up)

F ProtEnab: Y

On Node 2, configure the following (as well as other parameters necessary for operation):

1. Port Configuration (

RLP?: 0 RLP Port?: 0

O Additional Parameters

D Configure DLCI Parameters

DLCI ID?: 18

E For Backup use Only: N

2. Port Configuration (

RLP?: 0 RLP Port?: 4

F Logical DCE: Y

Configuring the central site as logical DCE allows the line monitor at that end to track incoming s tatus enquiries from the DTE end. )

O Additional Parameters

D Configure DLCI Parameters

DLCI ID?: 17

E For Backup use Only: N

[A], [C] , [A ]

I DLCI Backup Configuration

A Backup Group Number: 0 B Enable Backup Protocol?: N

[A], [C] , [A ]

from Main Menu) for the primary:

from Main Menu) for the backup:

(One end of the back up must be log ical DTE, a nd the othe r DCE.

I DLCI Backup Configuration

A Backup Group Number: 0 B Enable Backup Protoc ol?: Y

7-4 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 87

Example 2

In Example 2, the primary link is between Node 1/Port 2/DLCI 16 and Node 2/RLP 0/Port 0/DLCI 18 . The DLCI s should be conf igured a s desc ribed f or Exa mple 1 (wi th the exception, naturally, of Node 2/RLP 0/Port 4/DLCI 17), with one difference— when configuring Backup Group 10 (see step 3 under example 1), set Then if the primary link goes down, a connection will automatically be established between Node 1/Port 0/DLCI 17 and the "Other Device."

Example 3

In Example 3, the configu ration between Node 1 and Node 2 is t he same as in example

1. The "Other Device" mu st be configured to recognize bo th the primary and backup connections.

Required Configuration

To run frame relay in an FRX4000 or FRX6000, make sure the fol lowing are properly configured:

●

Node parameters, which is general configuration that must be done no matter

which protocols will be run in the node. See Chapter 4.

●

RLPs that will contain the interface(s) to the user device(s), network and/or

frame relay PVC, plus Line Interfac e Card( s) supporting the ports that will be the interfaces. See Chapter 5.

●

Loaded Protocol( s): frame rela y and any others that will be transmitted over the

frame relay link. See Chapter 5.

●

Frame Relay Bandwidth Allocation Groups (page 7-6), if configuring mul tiple

protocols to ru n over a frame relay po rt.

●

Frame relay port(s) that will connect to the user device(s), network, and/or

PVC(s). See Ch ap ter 6 and t he remainder of Cha pter 7.

●

PVC connections (page 7-20), which define "permanent" circuits between

physical ports in the node.

●

Frame Relay Backup Groups (page 7-22), if configuring one or more backup

DLCIs.

●

Logical port(s), if used. See Chapter 8.

ProtEnab

to N.

Configuring Frame Relay 7-5

Page 88

Configuring Bandwidth Allocation Groups

To optimize frame relay bandwidth use, variou s types of interfaces can be assigned to one of sixt een Bandwidt h All ocati on Groups , eac h def ined by the p aramete rs li sted i n

Table 7-1. Bandwidth Allocation Groups can ensure that response time-sensitive

traffic gets access to the available frame relay bandwidth. Each of the following entiti es that use a frame relay port can be assigned (in the

database records) to a Bandwi dth Allocation Group:

●

Node (for use in sessions with a NetView host)

●

Logical port

●

SNA Port (LL C2 pa ram et er s)

●

IP interface

●

IPX interface

●

LLC2 host

●

LLC2 inter face

●

Bridge port

For further control, bandwidth allocation can be enabled or disabled on eac h frame relay port.

This feature is applied only when a line's available bandwidth is limited (i.e., packets must be queued befor e transmission).

Also note that bandwidth allocation is not applied in a frame relay passthrough configuration (frame relay PVCs into and out of the FRX node, internal PVC between the two frame relay ports). (Although the FRX4000 and FRX6000 support bandwidth alloca tion, routers and FRADs that initiate fram e rel ay pas s through do not.)

Be sure you fully understand the needs of the user s of the node before assigning allocation group s; this feature can show adverse effects if configured incorrectly.

Be sure to configure the same DLCI rate control (see page 7-12) and bandwidth allocation values at both ends of a connection between Cabletron frame relay access devices. The parameters should be configured to handle the he avier traff ic volume.

To configure a Bandwidth Allocation Group, press Menu (or displayed.

[A], [A], [H]

from the Main Menu). A screen similar to the following will be

[H]

at the Node Configuration

7-6 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 89

Figure 7-2 Bandwidth Allocation Group Menu

Node Name=node_xyz

Bandwidth Allocation Group (screen 1 of 4)

A Dynamic Optimization N B Group 1 Percentage 0 C Group 1 Excess Priority 1 D Group 1 Use Excess Burst Y E Group 2 Percentage 0 F Group 2 Excess Priority 1 G Group 2 Use Excess Burst Y H Group 3 Percentage 0 I Group 3 Excess Priority 1 J Group 3 Use Excess Burst Y K Group 4 Percentage 0 L Group 4 Excess Priority 1 M Group 4 Use Excess Burst Y NPage 2

Option:

[A],[A],[H]

from Main Menu

Pressing

[N]

will display Page 2, which contains parameters for groups 5–8. Page 3

contains groups 9–12, and Page 4 contains groups 13–16.

Bandwidth Allocation Group Parameters

Explanations of the parameters follow the table.

Table 7-1 Bandwidth Allocation Group Parameters

Parameter Valid Values Default Value

Dynamic Optimization Group "n" Percentage 0–100 100

Group "n" Excess Priority Group "n" Use Excess Burst Y/N N

Used only if

Configuring Frame Relay 7-7

is a percentage of bandwidth that will be dedicated to traffic in a group if necessary. If the traffic does not require th e full allocati on, unused bandwidth will be available to other groups.

The total percentage assigned to all sixteen groups can be greater than 100%. This allows allocat ing 100% to, for exa mple, f our or fi ve groups tha t wi ll be us ed for a particular type of traffic , and 100% to another few groups, and so on. Since usage obviously cannot exceed 100%, any allocation of greater than 100% will be treated as 100%, with the percentages assigned to the affected groups treated as relative percentages. For example, as sume tha t Group 1 is assigned 60% and Group 2 70%, and

Group " n" Perce ntage

Group "n" Use Excess Burst

is not curr ently supported

0–16 1

is Y.

Page 90

both groups are assigned to IP interfaces. Under a full traffic load, Group 1 will be allocated 60/130 (46%) of the available bandwidth, and Group 2 will be allocated 70/ 130 (54%).

Group "n" Excess Priority

determines the order in which groups are given their allocations of bandwidth; the higher the number, the higher the priority.

Group "n" Use Excess Burst

will (if Y) allow traffic that falls into the Excess Burst Size to be transmitted. Any packets exceeding B

Configuration Example

Here is an example of a typical Bandwidth Allocation Gro up configuration:

Group Used For Percentage Excess Priority Use Excess Burst

1 2 3 4

will be buffered in the FRX4000/6000.

Table 7-2 Bandwidth Allocation Example

SNA Logical Ports & Mgmt. IP IPX

30 16 N 20 15 Y 30 14 Y 20 13 Y

This configuration ensur es that SNA traffic, which is very time-sensitive, will be given top priority, and will all be transmitted within the guaranteed 30% of the bandwidth, eliminating the risk of discarded packets. Sequenced arrival of packets is not critical among the first three groups, so those types of traffic can be configured to allow transmission above the Committed Inf ormation Rate (CI R). (Traffic above CIR is transmitted with the Discard Eligibil ity bit set, which allows packets to be discarded if necessar y .)

7-8 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 91

Configuring Frame Relay Ports

Node Name=node_xyz Frame Relay Port Parameters (screen 1 of 2) * RLP: 0 Port: 0 Link State: Linkup *I/O:V.35

Database System Memory A Port Type Frame Relay Frame Relay B Physical Port Interface V.35 V.35 C Blocked Port Flag N N D Line Speed 64K bps 64K bps E Maxi m um By te s per Fram e 1600 1600 F L og i cal DC E N N G Generate Clock N N H Rcv Clock (TT) from DTE N N I Link Management 2 Annex D 2 Annex D J N1 Polling Count 6 6 K N2 Error Threshold 3 3 L N3 Monitored Events Count 4 4 M T1 Link Integrity Timer 10 10 N T2 Polling Verification Timer 15 15 O Additional Parameters

Option:

Once the necessary Node and RLP parameters have been configured, press Port Configurat ion Menu (or

●

(FRX6000 only) RLP containing the port:

[A], [C], [A]

from the Main Menu. When prom pted, ente r:

0–7

. (The default is 0.)

[A]

at the

(RLP numbers are descri b ed in Ch a pter 5.)

●

Port (see port locations in Chapter 6):

0–7

. (The default is 0.)

The display for an existing port will show the configured parame ter value s, while the display for a new por t will show default databa se values. (See Table 7-3 and Table 7-

4.) The following figure is an example of an existing port.

Configuring Frame Relay 7-9

Pressing

[O]

Figure 7-3 Frame Relay Port Screen 1

[A],[C],[A]

from Main Menu

The above is an example of an existing frame relay port. On an FRX4000

Physical Port Interface

with

(item B) c onfigured as

DSU

, items G and H will be

different.

After making any changes, be sure to press

to update the

[F7]

system memory. Otherwise, the changes will not take e ffect until the next re-boot of the FRX4000/6000.

will display a screen similar to the following.

Page 92

Frame Relay Port Parameters (screen 2 of 2) * RLP: 0 Port: 0 Link State: Linkup *I/O:V.35

A Enable Outgoing Rate Control Y Y B Enable Bandwidth Allocation Y Y C Review DLCI Configuration D Configure DLCI Parameters E View Learned DLCIs F For Backup Use Only N N G Automatic DCE N N

Option:

Database System Memory

Figure 7-4 Frame Relay Port Screen 2

Reviewing DLCI Configuration (Figure 7-4, Item C)

Node Name=node_xyz

To display the current configured DLCIs on the port, press

[C]

at the s creen in Figure 7-4. A screen similar to the following inf ormation will be displayed for each configured DLCI.

Node Name=node_xyz

RLP Port DLCI ICIR IBC IBE OCIR OBC OBE BECN Pri Proto (Primary Info) Grp RRLP RPrt RDLCI SOT SBT T TH 0216 00 00 000 0 N 0250 00 00 000 0 N

PgUp, PgDn, F2:Review All DLCIs, F3:Exit

10 050 25020

Figure 7-5 DLCI Configuration Review Screen

7-10 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 93

The first line of parameters applies to all DLCIs on the port (or in the node if

[F2]

is pressed). The second line exists only for DLCIs configured as primary DLCIs in backup configurati ons. In the example in Figure 7 -5, DLCI 50 is a primary. All the parameters are list ed in Table 7-4.

The parameters in the first line are :

● RLP

● ICIR

● IBC

● IBE

● OCIR

● OBC

● OBE

● BECN

● Pri

● Proto

Port, DLCI

Com mitted In fo r m a ti on R a te (In )

Committed Burst Size (In)

Excess Burst Size (In)

Committed Information Rate (Out)

Committed Burst Size (Out)

Excess Burst Size (Out)

BECN Recovery Count

Outgoing DLCI Priority

Enable BackupProtocol

are self-explanator y.

The parameters in the second line are:

● Grp

● RRLP

● RPrt

● RDLCI

● SOT

● SBT

● TTH

Backup Group Number

Remote RLP

Remote Port

Remote DLCI

Switchover Timer

Switchback Timer

Time to Hold Data While Waiting

Configuring Frame Relay 7-11

Page 94

Configuring DLCI Parameters (Figure 7-4, Item D)

To configure DLCI parameters (listed in Table 7 -4), press prompted, enter a

DLCI ID: 16–991

. (The default is 16.) This will display a screen

similar to the following.

Frame Relay DLCI Configuration (screen 1 of 2) *RLP 0 *Port 7 *DLCI 16

A Committed Information Rate (In) 2000 B Committe d Burst S iz e (In) 20 00 C Excess Burst Size (In) 1000 D Committed Inform a ti on Rate (Out) 20 00 E Committe d Burst S iz e (Out) 2000 F Excess Burst Size (Out) 1000 G BECN Recovery Count 8 H Outgoing DLCI Priority 0 I DLCI Backup Configuration

Option:

Node Name=node_xyz

Figure 7-6 Frame Relay DLCI Configuration Screen 1

[D]

at Figure 7-4 and, whe n

Pressing

[F4]

at this or the subsequent screen (Figure 7-7) will delete the DLCI rate control and backup conf iguration . (The port wil l not be del eted unless

[F4]

is pressed at one of the higher-level port screens—Figure 7-3

and Figure 7-4.) Note that the DLCI is not yet deleted. If it was create d solely for frame relay

backup, it will r emain in existence until t he node is rebooted. If the DLC I was created when configuring an IP, IPX, or LLC2 interf ace, it will remain unt il that interface is delete d and the node is rebooted.

If a primary DLCI is brought down, then deleted from the

database while the backup is operational, end-to-end connectivity over the backup will f ail. For this reason, a pr imary DLCI should never be deleted. (If there is a need to delete the DLCI, it should first be re-configured so that it is not part of a frame relay backup situation.)

7-12 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 95

Figure 7-7 Frame Relay DLCI Configuration Screen 2

Node Name=node_xyz Frame Relay DLCI Configuration (screen 2 of 2) *RLP 0 *Port 7 *DLCI 16

A B ackup Group Number 0 B Enable Backup Protocol N

Option:

Viewing Learne d DLCIs (Fi g ure 7-4, Item E)

If you configure a

Backup Group Number, Enable Backup Protocol

will be replaced by several pa rameters (l isted in Table 7-4) that dete rmine backup operation.

If you change

En able Backup Protoc ol

to Y, the

Backup Gro up Numb er

entry

will disappear.

If the port is a logical DTE, a list of all DLCIs (extracted from LMI/AnnexD f rames) can be displayed by pr essing by three columns:—

A:a

= active, i = inactive.

N:n

= new, o = old. (A newly learned DLCI will become "old" after the fir st

A, N

[E]

at Figure 7-4. Each displaye d DLCI will be f ollowed

, and C—with the following possible values:

Full Status Inquiry.

C:c

= configured via the DLCI configuration screen.

= learned through some other means (e.g., through link management

information).

Configuring Frame Relay 7-13

Page 96

Frame Relay Port Parameters

Parameter Valid Values Default Value

Port Type Frame Relay Physical Port Interface Blocked Port Flag Y/N Line Speed Maximum Bytes per Frame 16–4096 1600

Logical DCE Y/N Generate Clock Rcv Clock (TT) from DTE CSU/DSU Operating Mode RTS Control

Link Layer Management None, LMI, ANNEXD None N1 Polling Count

N2 Error Threshold

N3 Monitored Events Count T1 Link Integrity Timer T2 Polling Verification Timer

Enable Outgoing Rate Control Y/N N Enable Bandwidth Allocation Y/N N For Backup Use Only? Y/N N Automatic DCE Y/N N

10 11

(bits pe r sec) see explanation

If set to Y, no backup DLCIs on this port will be used (even if the port is en abled via on-line po rt enable).

If one physi cal frame relay port will connect to se veral remote sites, be sure the line speed is adequately higher that the sp eeds configured on the remote sites . A lso, this value does not apply t o a T1 or E1 port; on those p ort type s, the speed is p re-de termi ned.

If this port will connect to a frame relay network, set one end of a fra me relay backup connection mus t be configure d as logical DCE.

Not applicable to T1/E1 ports or FRX4000 DSU ports.

This parame ter is relevant only if

232

Applicabl e only to FRX4000 DSU ports.

These para met ers ar e r eleva nt onl y if

Logical DCE N3

8 9

agement

Generate Clock

and

should be greater than or equal to N2.

Link Layer Ma na ge me nt

is change d to none fr om som e other val ue, th e def aul t for

was before t he change.)

should be greater than or equal to T1.

This pa ra m e te r is re le v an t o nly if

Table 7-3 Frame Relay Port Parameters

see explanation see explanation

Y/N Y

is N.

4,5

(sec)

is Y.

Y/N N Normal/LDM Normal Constant/External Constant

1–6 6

1–10

5–30

none

5–30

Logical DCE

Physical Port Interface

Link Layer Management

, this parameter is irrelevant. (If

Logical DCE

is Y.

is something other than

not valid here

9600

LMI

Annex D

2 3

4 10 15

to N. Also note that

LMI

ANNEXD

Link Layer Man-

will be left as it

and

RS-

7-14 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 97

Table 7-4 Frame Relay DLCI Parameters

Parameter Valid Values Default Value

Committed Information Rate (In/Out) Committed Burst Size (In/Out) Excess Burst Size (In/Out)

0–2000

(Kbits/sec)

.08 CIR–16xCIR (in kbits) 2CIR

0–

{BC/CIR x (lin e sp ee d

minus CIR)}

BECN Recovery Count 1–255 Outgoing DLCI Priority 0–4 0

Backup Group Number Enable Backup Protocol? Y/N Remote RLP

Remote Port

Remote DLCI Switchover Timer Switchback Timer Time to Hold Data While Waiting

5,6

If the Committed Information Rate is set to 0 and the Excess Burst Size is set to a value greate r than or trans mitted (

CIR = Committed Information Rat e. (See first parameter in table. )

Applica ble only o n the i nitiat ing nod e. (See ex plana tion. ) If conf igur ing a DLCI that wi ll

, the DE (Discard Eligibility) bit will be turned on in all received (In) and/

Out

) frames.

(packets)

0–255 0

0–7 0

SmartSwitch 1800: Other node t ype:

16–991 16 0–65535 0–65535 0–65535

(seconds )

(seconds)

(seconds )

be backed up, you must leave this va lue at 0 until you have configured a back up group. Then re-en ter Por t Conf igura ti on on th is RLP/por t /DLCI and spe cif y th e desire d gro up. A value of

means that the DLCI will not be backed up; therefore, set the Group to 0 if

the DLCI wi ll be a backup.

Set to N for the initiating backup DLCI and Y for the re m ote backup DLCI.

Display ed only if

Valid onl y if the remote node is an FRX6000 or FRM. If set to

65535

Backup Group Number

is a value ot her than 0.

, switchback will not o ccur unless the backup fai ls.

0–3

0–7

0 8

0 5 30

Port Type

specifies the pr otocol the por t will suppo rt. S electi ng this parameter will displ ay a li st of valid protocol s. An FRX4000 port can be config ured as any WAN protocol l oaded in the device. An FRX6000 port can be configured as any WAN protocol configured on this port's RLP. (Protocol configuration is described in Chapter 5.)

Physical Port Interface

must be configured as follows. For reference, port locat ions are shown on page 6-1 (FRX4000) and page 6-2 (FRX6000) .

●

Configuring Frame Relay 7-15

FRX4000 port 0 is always FRX4000 port 1 is

RS-232

DSU

. , depending on whether the optional CSU/

DSU card is installed. FRX4000 ports 2 and 3 are det ermined by the attached c ables :

, or

449

X.21

RS-232, V.35, RS-

FRX4000 ports 4–7 a re de termine d by the expa nsion Line Inter face Card (LI C) and attached cables. RLP Configur ation identifies the LIC, and only the valid

Page 98

interfaces will be displayed on the Port screen, among :

X.21, T1

available by special order.) Note that a T1 or E1 LIC supports one port (port 4).

●

FRX6000 ports 0–7 on each RLP ar e determined by the Line Interface Card(s) and attached cables. The RLP record identif ies the LIC, and only the valid interfaces will be displayed on the Port scr een, among:

X.21, T1

Note that a T1 or E1 LIC supports one port (port 0 or 4).

Blocked Port Flag

will cause the port to be enabled (N) or disabled (Y) at node IPL. The port will remain in that state until this parameter is c hanged or an on-line enable ( Main Menu) or disable (

If set to

, no backup DLCIs on this port will be used (even if the port is enabled via

on-line port enable).

Line Spee d

is the data transmission rate in bits per second, and the clock speed on a non-T1/E1 serial port when the port is a physical DCE (i.e ., the attached I/ O cable is DCE). If this port is a physica l DTE, specify th e line speed that matches (as closely a s possible) that of the device connected direc tly to the port.

Selecting this parameter for an FRX4000 DSU por t will toggle betwe en the two valid values of

56K bps

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

, and E1. (RS-449 and X. 21 interfaces require an RS-422 LIC, which is

RS-232, V.35, RS-449, RS-530,

(RS-449, RS-530, and X.21 i

, and

[B], [B], [A]

64K Clear Channel

and

nterface s requ ire an RS -4 22 LIC.)

[B], [B], [C]

from the Main Menu) is performed.

from the

This parameter cannot be selected on a T1 or E1 port; rather, the line speed is determined by the port type and channel usage:

Full T1

Fractional T1

Full E1 Fractional E1

1.344M

1.536M 56K

64K

1.920M 64K

Base Channel Speed

per channel, per channel,

per channel,

1.344M

1.536M

1.920M

is is

max, if max, if

max

56K 64K

Base Channel Speed Base Channel Speed

is is

56K 64K

Selecting this parameter for any physical interface type except T1, E1, or FRX4000

DSU

will display a list of ranges. Press the letter corresponding to a range to display

the valid speeds within that r ange. All possible speeds are:

75 150 300 600 1200 2400 4800 9600 14.4K 19.2K 24K 28.8K 38.4K 48K 56K 64K 72K 112K 128K 168K 192K 224K 256K 280K 320K 336K 384K 392K 448K 504K 512K 560K 576K 616K 640K 672K 704K 728K 768K 784K 832K 840K 896K 952K 960K

1.008M 1.024M 1.064M 1.088M 1.12M

1.152M 1.176M 1.216M 1.232M 1.28M

1.288M 1.344M 1.4M 1.408M 1.456M

1.472M 1.512M 1.536M 1.568M 1.6M

1.624M 1.664M 1.668M 1.728M 1.792M

1.856M 1.92M 1.984M 2.048M

7-16 FRX4000/FRX6000 4.0 User Guide, Rev 01

Page 99

If an RS-232 DCE port is directly connected to the DTE via the standar d Cabletron cable, th e maximum supported speed is 64K. If longer cabling is used, the maximum speed is 19.2K. (The EIA standard for RS-232 addresses speeds up to 19.2 Kbps.)

Maximum Bytes per Frame

specifies the maximum size of any I-frame (Information frame) that can be transmitted or received on the port.

Logical DCE

defines the port as (if Y) logical DCE or (if N) DTE. The port must be configured as the opposite of the device at the other end of the connection.

Logical and physical DCE/DTE are independent of each other (e.g., a port can be a physical DCE and logical DTE).

Generate Clock

specifies whether the por t will ge nerate the clock necessary to synchronize traffic over the link. If the port is a physical DCE (determined by the port's I/O cable interface), set this parameter to the parameter to

Rcv Clock (TT) from DTE

allows the clock to be looped back from the DTE using the TT (Terminal Timing) signal, which can be helpful on high-speed lines. Generally, if the local interface is physical DCE an d the l ine spe ed i s above 256 Kbps, thi s parame ter should be set t o (Make sure the remote DTE is configured to provide the terminal timing.)

, since the phys ical DCE generat es cloc k. If t he por t is DTE, se t

CSU/DSU Operating Mode

determines whether the attached modem connection ca n be normal or limite d distance (LDM), where the distance depends on the wire gauge, num ber of spl ice points, and line speed. For exa mple, 26-g auge wire and a line s peed of 64K bps allo ws a di stance of 15000 feet. Lowering the speed to 56K increases the allowable distance to 18000 feet. If 19-gauge wire is used, the distances can be multiplied by three.

RTS Control

if configured a s if configured as

Link Laye r Managem ent

Constant

External,

determines whether , and what type of, confi gurable network manageme nt (e.g., status enquiries to the port) will be used: none, LMI (Local Management Interface), or ANSI T1.617 Annex D (an ANSI-standard LMI).

N1 Polling C o unt

specifies t he number of pol ling cycle s bet ween re quests for Full Stat us repor ts, whic h include status of all PVCs on the physical link. Every "

Integrity Timer

" on page 7-18), the logical DTE will send a Status Enquiry to the network, reque sting statu s of the ne twork link. Each e xcha nge of on e en quiry a nd one message (response) is a polling cycle. After every " Status report will be sent.

If this port is configur ed as logical DCE, status enquir ies will be initia ted at the DTE, and the local node will respond with status messages.

means that RTS (Request t o Send) will always be asserted;

the CSU/DSU will control RTS.

" seconds (see "

" cycles, an enquiry for a Full

T1 Link

Configuring Frame Relay 7-17

Page 100

N2 Error Thresh ol d

is the number of link reliabi lity and/or protocol e rrors that can occur during the period defined by

N3 Monitored Events Count

inactive.

N3 Monitored Events Count

is the number of error-free polling cycles after whic h the DCE wil l be declared active if the first poll resu lted i n an erro r. If the firs t po ll was error free, the DCE will be declared active aft er tha t poll. (If the count, the DCE will be declared inacti ve, and the N3 count will be restarted.)

T1 Link Integ r ity Ti m er

determines how often the logica l DTE will initiate a Status Enquiry message to the DCE.

T2 Polling Ver ifi c at io n Ti m er

indicates how long the logical DCE will wait betwe en Status Enquiry mes sages from the DTE before recording an error.

Enable Outgoing Rate Control

determines whether the rate parameters (CIR, BC, BE) will be enforced.

Enable Bandwidth Allocation

determines whether bandwidth allocation (see page 7-6) will be enforced.

before the logical DCE will be declared

N2 Error Threshold

is exceeded during the

For Backup Use Only?

determines whether all DLCIs on the port will be rese rved exclusiv ely as back ups for other DLCIs in the same node. See "Configuring Frame Relay Backup Groups" on page 7-22. If this parameter is set to backup.

Automatic DCE

enables (if Y) automatic detection by the software of whether the port is a physical DCE or DTE. This can be helpful in cases such as a connected backup CSU/DSU, which might be configured differently than the primary connection. The automatic DCE feature allows switchover to occur without reconfiguring the port.

DLCI Parameters

Committed Information Rate (In/Out)

(CIR) is the incoming or outgoing (depending on the parameter) data throughput that the network agrees to support under normal conditions. Outgoing throughpu t greater than CIR will be reduced to CIR if ( a) a packet is r eceived with the BECN (backwa rd explicit congest ion notification) bit set, and (b)

Committed Burst Size (In/Out)

(BC) is incoming or outgoing (depending on the parameter) the maximum amount of data that t he network agrees to transfer under normal conditions within the time period defined by B turned on, and will be tracked by the FRX4000/6000 statistic

, the port will remain disabled until needed for

If configuring the port f or backup use only, make sure no DLCIs on the port have been con fig ur ed on an IP, IP X , or LLC 2 inte rface.

Enable Outgoing Rate Control

/CIR. Any data exceeding BC will have the Discard Eligibility (DE) bit

DE/sec (*10)

is Y.

7-18 FRX4000/FRX6000 4.0 User Guide, Rev 01

Cabletron Systems Netlink FRX4000, FRX6000, Netlink FRX6000 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual