Cabletron Systems Netlink FRX8000 User Manual

User Guide

For Release 3.0

09-41-06-150-02

The Com plete N etwo rk ing Soluti on

TM

Cabletron Systems reserves the r ight to ma ke changes in specifica tions and other information
contained in this document without prior notice. The reader should in all cases consult
Cabletron Sys tems to determine whe ther any such changes have been made.

The hardware, firmware, and/or software described in this manual is subject to change w ithout
notice.

IN NO EVENT SHALL CABLETRON SYSTEMS BE LIABLE FOR ANY INCIDENTAL,
INDIRECT, SPECIAL, OR CONSEQUENTIAL DAMAGES WHATSOEVER
(I NC LUDING B UT NOT L IMITED TO LO ST PROF ITS ) AR ISI NG OUT OF OR
RELATED TO THIS MANUAL OR THE INFORMATION CONTAINED IN IT, EVEN IF
CAB LETR ON SYSTEMS HAS BEEN ADVISED OF, KN OWN , OR SH OULD HAV E
KNOWN, THE POSSIBILITY OF SUCH DAMAGES.

Copyright 1997, 1998 by Cabletron Sys tems, Inc. All ri ghts re served. Printed in the United
States of America. Order Number: FRX8-USR-DOC.

VxWorks is a copyright of Wind River Systems, Inc.
IP (Internet Protocol) code is copyright 1982, 1986 by Regents of the University of California.

All ri ghts re served. Thi s C abletron produc t i ncludes soft ware developed by the University of
California, Be rkeley, and its contributors. IP software is provided by the regent s and contrib­utor s “a s is” and any expr ess or implied warrantie s , inc lud ing , but no t limited to, the imp lie d
warranti es of mer cha ntability a nd f itness for a partic u la r pur po se, are disclai med. In no e vent
shall the regents or contributors be liable for any direct, i ndirect, incident al, s pecial, exem­pla ry, or conseque ntial dama g es (in c lu ding , b ut n ot limi ted to , p roc urement of su bs titute goods
or servi ces; loss of use, data, or profits; or business i nterruption) howe ver ca used and on a ny
theory of liability, whether in contract, strict liability, or tort (inc luding negligence or oth­erwise) arising in any way out of the use of this software, even if advised of the possibility of
such dama ge.

Gateway Da emon ( GateD) softwar e, Releas e 3.5. 5, is maintained and developed by Cornell
University and its collaborators. The vers ion of GateD used with this Cabletron produc t has
been modified.

Netlink is a tr ademark of Ca bletron S ystems, Inc. A ll other product designati ons a re the
property of their respect ive owners.

Statements of Compliance

FCC

This devi ce complies with Part 15 of the FCC rul es. Ope ration is subjec t t o the fol lowing two
conditions: (1) this device ma y not cause harmful interference, a nd (2) this device must ac c ept
any inter ference rec eived, including interference t hat may cause undesire d operation.

This e quipment has been teste d and found to comply with the limits for a Class A digital
device, pursuant to Part 15 of the FCC rul es. The se lim its are designed to provide reasonable
protection agai nst harmf ul interference when the e quipment is oper ated in a commercial e nvi­ronment. This equipment uses, generates, and can ra diate radio frequency energy and if not
insta lle d in acco r danc e w ith the op era to r ’s ma nual, may ca use harmfu l inte r fe ren c e to r a d io
communications. Operat ion of this equipm ent in a reside ntial area is l ikely to cause inter ­ference in whic h case the use r will be requir ed to correct the interference at his own expense.

Changes or modif ications mad e to this de vice whic h are n ot expressly
approved by Cab letron Systems could void the user’s authority t o operate the

equipment.

iii

DOC

About This Man ua l

Terminology a nd Conventions

This digital apparatus does not exceed the Class A limits for radio noise e missions from digital
apparatus se t out in the Radio Inter ference Re gulations of the Canadi an Departm ent of Com­munic ations.

Le prés ent appareil numé r iqu e n’éme t p as de bru its rad ioélec tr iqu e s dép as sant le s limites
applicables aux appareils numériques de la class A prescri tes da ns le Règlement sur le
brouilla ge radioé lectrique édic té par le mini stère des Communications du C anada.

Rev Da te Reason for Upda te
01 August 1997 General availability
02 March 1998 New format

This m anual supplements screen prompts and menus as an aid in configur ing the database and
per forming syst em operations on a Netlink FRX8000. Before using the manual, you should be
familiar with FR X8000 har dware, as well as the protocols (frame relay, SNA, etc.) you will be
usi ng.

This typeface represent s general t e xt. This type fa ce r epre se nts keyboard input and video outpu t.

( Thi s text is dark cyan in on-screen versi ons of the ma nual, and black in paper versi ons.)

In on-scr een versions of the manual, ite ms in bl ue are links to ot her plac es in the manual.

This symbol points to an i nformational note relating to the te xt, table, or figure that
immed ia tely pre ce des or f ollo ws it.

The following re ferences to keyboard keys a ppear in the manual a nd/ or on the scre en:

I f a state m ent end s with a re fe rence t o a k ey— fo r ex amp le, “. ...then p ress [En te r ]. ”—t he period

i s not part o f the data to be enter e d . If a pe riod should be ente re d, it will b e show n a s [.]. Th e
same applies to all other punctua tion. When i nstructed to, for example, “press [A] , [B] fro m t h e
Main Menu, ” this means press [A], the n [B ], not [A] comma [B].

Screen Displays

Scre en Displays are provided to show the general appearance of a ctual screens . They are only
examples—the informa tion shown is not always repres entative of an ope ra tional system .

This symbol and text identifies a cautionary note, the content of which is more

critical to he ed than an informat ional note.

[N] is a reference to a key on your keyboard (where “N” is the key).

Enter means that you should type in the information, then press the [Enter] key.
Type is similar to Enter, except that the word “[E nter]” follows the inf ormation to be

typed (e .g., “type n [Ente r]”).

Press means press (hit, st r ike) the ke y onc e. Pressing the [Enter] key a fterwards is not

necessary.

[Ctrl] followed by one or two othe r key designations , mus t be str uck simul taneously

with the other keys shown.

iv FR X8 000 3 .0 User Gu i de, Rev 02

Table of Contents

Section I Get t ing Started

C hapter 1 Overview

Sum mary of Features ................................................................................ 1-2

Hard ware Overview ................................................................................. 1-5

C hapter 2 Getting St arted

Using the INM Menu System................................................................... 2-1

Section II Configuration

Chapter 3 Introduction to Database Configuration

Database Setup Recommendations .......................................................... 3 -4

Conf iguration Operation s........................................................................ 3-5

Master Status.......................................................................................... 3-11

Pro ducing Configuration Reports........................................................... 3-12

C hapter 4 Confi gu ring Ne t wo rk Paramet ers

Conf iguring Network Defaults................................................................. 4-2

Creating a Networ k Representation ......................................................... 4 -9

Chapter 5 Configuring Node Records

Conf iguring Node Records....................................................................... 5-2

C hapter 6 Confi gu ring LP s and L AN Cards

FRX8000 RLP.......................................................................................... 6-1

N7 00 0 RL P... .... .... ........ .... .... ........ .... ....... .... .... ........ .... .... ........ .... .... ........ . 6-6

N7000 RLP Parameters............................................................................ 6-7

N7000 Standard LP.................................................................................. 6-8

N7 00 0 T1 LP .... .... .... ........ .... .... ........ .... ... ........ .... .... ........ .... .... ........ .... ... 6-1 0

N7 00 0 E1 LP .... .... .... ........ .... .... ........ .... ... ........ .... .... ........ .... .... ........ .... ... 6-1 2

Conf iguring T1/E1 Channel Maps......................................................... 6-16

Conf iguring LAN C ards......................................................................... 6-18

Chapter 7 Configuring Inter-Nodal Trunks

Parallel Trunks ......................................................................................... 7 -1

Required and Optional Con figuration...................................................... 7 -2

Conf iguring Tru nk Port Records .............................................................. 7-3

V.2 5bis Modem Operations ................................................................... 7-10

Conf iguring N74/7500 PDN Por ts......................................................... 7-11

Conf iguring Subscriber I Ds .................................................................... 7-17

Conf iguring a PVC for a Log ical X.25 Tru nk........................................ 7-20

Conf iguring Telephon e Numbers........................................................... 7-23

C hapter 8 Confi gu ring Frame Relay

DLCI Sharing........................................................................................... 8-1

Required and Optional Con figuration...................................................... 8 -1

Conf iguring Bandwidth Allocation Groups ............................................. 8-2

Conf iguring a Frame Relay Port Record .................................................. 8-4

v

Configuring PVCs .................................................................................... 8-8

Configuring Frame Relay DLCIs........................................................... 8-10

C ha pte r 9 C on f igu ri ng X .2 5

Required and Optional Configuration...................................................... 9-1

Configuring an X.25 Port Record............................................................ 9-2

Configuring X.25 Closed Us er Groups.................................................. 9-1 1

V.2 5b is M od em Oper at ion s........... .... .... ........ ... .... ........ .... .... ........ .... .... . 9-12

Configuring Subscriber IDs................................................................... 9-1 4

Configuring PVCs .................................................................................. 9-1 8

Configuring X.25 Address Translation Templates................................ 9-2 1

Configuring Group Send Groups........................................................... 9-2 6

Configuring Telephone Numbers........................................................... 9-2 7

C h a p t e r 10 C o nf i guri n g S NA

Required and Optional Configuration.................................................... 10-2

SNA Con figu rat io n Exam ple. .... ........ .... .... ....... .... ........ .... .... ........ .... .... . 10 -3

Configuring an SNA Port....................................................................... 10-4

Configuring Subscriber IDs................................................................... 10-9

Configuring SDLC PUs....................................................................... 10-1 2

SNA PU Parameters............................................................................ 10-15

Configuring LLC 2................................................................................ 10-1 9

C h a p t e r 11 C o nf i guri n g BS C

Required and Optional Configuration.................................................... 11-1

Configuration Examp le.......................................................................... 11- 2

Configuring a BSC Interactive Port Record........................................... 11-3

Configuring Subscriber IDs................................................................... 11-8

Configuring BSC Interactive Subscribers............................................ 11-10

Configuring BSC Interactive Devices.................................................. 11-1 2

Chapter 12 Configuring Async Pads

Required and Optional Configuration.................................................... 12-1

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

Conf igu ring PA D Log in Reco rds ... ........ .... ....... .... .... ........ .... .... ........ .... . 12-8

Configuring a P AD Banner.................................................................. 12-1 0

Configuring Ports as Async PADs....................................................... 12-1 0

Configuring Subscriber IDs................................................................. 12-1 7

Configuring Abbrev iated Addresses.................................................... 12-1 9

Configuring PVCs ................................................................................ 12-2 0

C ha pte r 13 C on f igu ri ng IP

IP Add ressing......................................................................................... 13-1

Required and Optional Configuration.................................................... 13-2

Configuring IP Network and Node Parameters...................................... 13-3

Conf igu ring I P Int erfac es... ........ .... .... ........ .... ... ........ .... .... ........ .... .... ..... 13 -4

Configuring a S tatic IP Route ................................................................ 13-8

Configuring IP-Over-X.2 5 PVCs......................................................... 13-1 0

C ha pte r 14 C on f igu ri ng IP X

Required and Optional Configuration.................................................... 14-1

Configuring IPX Network and Node Parameters................................... 14-2

Configuring IPX Interfaces.................................................................... 14-3

C onfiguring IPX Filter s........................................................................ 14-1 1

vi FRX8000 3 .0 User Gu i de, Rev 02

Conf iguring a Static IPX Route............................................................ 14-18

Chapter 15 Configuring SNMP

Required and Optional Con figuration.................................................... 15-1

Conf iguring SNMP Parameters.............................................................. 15-2

Sec tion III Operation

C hapter 16 Introdu ct ion to Sy st em Op eration
C hapter 17 On-lin e Op erati on s

Disabling and Enabling Ports................................................................. 17-1

V.2 5bis Modem Operations ................................................................... 17-2

Displaying Installed Line Interface Cards.............................................. 17-4

Restarting a Remote Node (Re-IPL) ...................................................... 17-4

Boot Disk Local Operations................................................................... 17-4

Boot Disk Download Operations ........................................................... 17-6

Call Accounting File Operations.......................................................... 17-13

Converting N70 00 5.0 Database Record s............................................ 17-18

Database Co ncurrency Operations....................................................... 1 7-19

File Tr ansfer ......................................................................................... 17-21

Remote Control .................................................................................... 17-22

Message Services ................................................................................. 1 7-23

Chap t e r 18 S t at us Disp l a ys

Menu-Level Status Displays .................................................................. 18-1

Displaying IPX RIP and SAP Tables..................................................... 18-9

Grap hics-level Status Displays ............................................................. 1 8-10

C hapter 19 Statis t ics Disp lays

Menu-Level Node/LP/Frame/Port Statistics Displays ........................... 19-1

IP Statis tics Displays............................................................................ 19-12

IPX Statistics Di splays......................................................................... 1 9-17

LAN Card Statistics Displays............................................................... 1 9-22

Grap hics-level Statistics Displays........................................................ 19-26

C hapter 20 A larms

Alarm Sev erity Levels............................................................................ 20-1

Alarm Messag es........... .... .... ........ .... .... ....... .... ........ .... .... ........ .... .... ....... 20- 6

C hapter 21 Tests

Tracing a Packet ..................................................................................... 21-1

M eas urin g Pac ket Del ay... .... ........ .... .... ....... .... .... ........ .... .... ........ .... .... ... 21- 2

Testing C onnectivity via IP Ping............................................................ 21-3

vii

Section IV Appendices

Appendix A Async Terminal Operations

Establishing a Connection to the Node................................................... A-1

Command and Data Tran sfer Modes....................................................... A-2

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

Placing a Call fr o m an Async Terminal .................................................. A-3

Async PAD Service Signals.................................................................... A-4

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

Function Keys on an ASCII Terminal..................................................... A-6

Appendix B Archiving and Restoring Database

Archiving the Database............................................................................ B-1

Restoring the Database............................................................................. B-1

Appendix C Passwords

Changing Password s ................................................................................ C-2

Appendix D Cause and Diagnostic Codes

Cause Codes............................................................................................ D-1

Diagno stic Codes..................................................................................... D-3

Appendix E System Files

Line Processor Type................................................................................. E-2

Netw or k Defau lt s........... .... .... ........ .... .... ........ ... .... ........ .... .... ........ .... .... ... E-4

Alarm Severity Level............................................................................... E-6

Appendix F INM/NMP Unix Operations

Changing the Time Zone, Date, o r Time ................................................. F-1

Displayi ng Variou s Data.......................................................................... F-1

Analyzing Routing Updates..................................................................... F-2

Changing the Cumu lative Statisti cs File Size.......................................... F-3

C onfiguring UNIX f or Multiple Users.. ................................................... F-4

Using the UNIX “vi” Editor..................................................................... F-5

Enabling/Disab ling Automatic Accounting File R ollover....................... F-6

Appendix G Starting and Stopping Nodes and NMPS

FRX8 000 Sw itc h.... .... ........ .... .... ........ .... .... ....... .... .... ........ .... .... ........ .... .. G-1

FRX8 000 IC P......... .... .... ........ .... .... ........ .... .... ....... .... .... ........ .... .... ........ .. G-2

FRX8 000 INM........... .... .... ........ .... .... ........ .... ... ........ .... .... ........ .... .... ...... G-4

FRX8 000 NMP.. .... ........ .... .... ........ .... .... ........ ... .... ........ .... .... ........ .... .... .. G-6

N74 00......... .... .... ........ .... .... ........ .... .... ........ .... ... ........ .... .... ........ .... .... ...... G-7

N7500, N75 00-ICP, or N75 00-INM ....................................................... G-8

Th e Initializatio n Report ....................................................................... G-10

Appendix H ASCII Character Table
Appendix I INM/NMP Menu Structure
Glossary
Index

viii FR X8 000 3 .0 User Gu i de, Rev 02

List of Figures

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

2-1 Main Menu ............................................................................................ 2-2

3-1 Operations Menu Example................................................................... 3-5

3-2 “Output to Terminal” Disp lay .............................................................. 3-8

3-3 “In quiry ” Examp le................................................................................ 3-9

3-4 “Maintenance” Example..................................................................... 3-10

4-1 Network Network Selection Menu....................................................... 4 -1

4-2 Network Defaults File Display ............................................................ 4-2

4-3 Network Representation Display.......................................................... 4-9

4-4 St atu s Disp lay Ico ns ......... .... .... ........ ... .... ........ .... .... ........ .... .... ........ ... 4 -1 0

5-1 Nodes Selection Menu.......................................................................... 5 -1

5-2 FRX8000 Nod e Record ........................................................................ 5-2

5-3 N7000 Node Record ............................................................................. 5-3

6-1 FRX8000 RLP...................................................................................... 6 -2

6-2 FRX8000 RLP Configu ration Menu .................................................... 6-3

6-3 N7 40 0/7 500 RL P Co nf igu rati o n Reco rd. ........ .... .... ........ .... .... ........ .... . 6- 6

6-4 N7400/75 00 “Standard” LP Conf iguration Record.............................. 6-8

6-5 T1 DSX-1 LP Configuration Record.................................................. 6-10

6-6 E1 LP Configuration Record .............................................................. 6-13

6-7 T1/E1 Channel Map Reco rd............................................................... 6-16

7-1 Exa mple s of Multiple Trunks............................................................... 7 -2

7-2 Phy sical Trunk Port R ecord for V.25bis Port ....................................... 7 -3

7-3 Phy sical Trunk Port R ecord for Non-V.25 bis Port............................... 7 -4

7-4 Logical Trunk Port Record................................................................... 7 -4

7-5 Phy sical PDN P ort Recor d .................................................................. 7-12

7-6 Logical PDN Port Record................................................................... 7-12

7-7 SVC Subscriber Record ...................................................................... 7-18

7-8 X.2 5 Trunk PVC Record Ex ample..................................................... 7-20

7-9 Telepho ne Num ber Record................................................................. 7-23

8-1 Bandwidth Allocation Group Menu ..................................................... 8-2

8-2 Frame Relay Port Record...................................................................... 8 -4

8-3 Frame Relay to Frame Relay P VC Record Example............................ 8 -8

8-4 Frame Relay DLCI R ecord................................................................. 8-11

9-1 Phy sical X.25 Port Record .................................................................... 9-2

9-2 Logical X.25 Port Record..................................................................... 9 -3

9-3 X.2 5 Cl osed Us er Group Recor d........................................................ 9-11

9-4 SVC Subscriber Record ...................................................................... 9-14

10-5 Wildcard Addr essing Example........................................................... 9-16

10-6 X.25-to-X.25 PVC Record Example .................................................. 9-18

ix

10-7 B ackup Using Address Translation.................................................... 9-22

10-8 Address Translation Templat e Record ............................................... 9-23

10-9 Telep hone N umber Re cor d. .... ........ .... .... ....... .... .... ........ .... ........ .... .... . 9- 27

11-1 SDLC and LLC 2 Examples................................................................ 10-1

11-2 Typ ic al SNA Conn ect ion s.. .... .... ........ .... .... ....... .... .... ........ .... .... ........ . 10-3

11-3 SNA Port Record ................................................................................ 10-4

11-4 SVC Subscriber Record...................................................................... 10- 9

11-5 N7000 SNA HPAD-PU Record ....................................................... 10-1 3

11-6 N7000 SNA TP AD-PU Record........................................................ 10-1 3

11-7 FRX8000 S DLC-PU Record ............................................................ 10-1 4

11-8 LLC2 Host Con fig ura t ion Screen ....... .... .... ....... .... .... ........ .... .... ....... 1 0-20

11-9 LLC2 Host Con fig ura t ion Screen ....... .... .... ....... .... .... ........ .... .... ....... 1 0-20

11-10 LLC2 LAN Inter face Record .. .......................................................... 10-26

11-11 LLC2 Frame Relay Interf ace Record............................................... 10-26

12-1 B SC Interactive Example................................................................... 11- 2

12-2 B SC Interactive Port Record.............................................................. 11-3

12-3 SVC Subscriber Record...................................................................... 11- 8

12-4 B SC Interactive Subscribers Record................................................ 11-1 1

12-5 B SC Interactive Devices Record ...................................................... 11-13

13-1 As ync PAD Profile Record................................................................. 12-3

13-2 As ync PAD Login Parameters Record............................................... 12-9

13-3 As ync PAD Port Screen ................................................................... 12-1 1

13-4 SVC Subscriber Record.................................................................... 12-1 7

13-5 As ync-to-X.25 PVC Record Example.............................................. 12-20

14-1 IP Interface Record Example.......... .... ........ ... .... ........ .... .... ........ .... .... . 13 -4

14-2 IP Route Record.................................................................................. 13-8

14-3 IP-over-X.25 PVC Record Example................................................ 13-10

15-1 Ty pical IPX Interface Record............................................................. 14- 3

15-2 IPX SA P Filter R ecord..................................................................... 14-1 2

15-3 Ty pical IPX Filter A pplic at ions Record........................................... 14-1 7

15-4 IPX RIP Rou te Record ..................................................................... 14-1 8

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

16-2 SNMP Co mmunity Table Menu......................................................... 15- 4

16-3 SNMP Trap Routing Menu................................................................. 15-5

17-1 FRX8000 S witch Main Menu............................................................. 16-1

18-1 On-Li ne Port Oper at ion s Menu...... ........ .... ... ........ .... .... ........ .... .... ..... 17-1

18-2 V.25bis Dial P ort Sta tus Scre en. ........ .... .... ....... .... .... ........ .... .... ........ . 17-2

18-3 Mod em Oper at ion s Screen. ........ .... .... ........ ... .... ........ .... .... ........ .... .... . 17 -3

18-4 Call Accou nti n g Fil e Disp lay..... ........ .... .... ....... .... .... ........ .... .... ....... 1 7-15

18-5 Call Accou nti n g Fil e St ruc ture... ........ .... .... ....... .... .... ........ .... .... ....... 17- 16

19-1 Node Status Di splay........................................................................... 18-1

19-2 Port Statu s Dis play. ........ .... .... ........ .... .... ....... .... .... ........ .... .... ........ .... . 18 -2

x FR X8 000 3 .0 User Gu i de, Rev 02

19-3 Trunk St atus Display.......................................................................... 18-3

19-4 Virtual Connections Display on Frame Relay Port ............................ 18-4

19-5 Virtual Connections Display, Non-Frame Relay Port........................ 18-5

19-6 Line Monitor Display, X.25 Example................................................ 18-7

19-7 Line Monitor Display, Trunk Example.............................................. 18-8

19-8 Networ k/Subnet Status Display........................................................ 18-10

19-9 Statu s Disp lay Ico ns . .... .... ........ .... .... ....... .... .... ........ .... .... ........ .... .... . 18 -1 2

19-10 Event Log Display ............................................................................ 18-13

19-11 Node Status Disp lay ......................................................................... 18-15

19-12 Trunk/X.25 Port Status Displ ay ........................................................ 18-16

20-1 Node Statistics Display....................................................................... 19-2

20-2 LP Statistics Disp lay........................................................................... 19-4

20-3 Port Statistics Display......................................................................... 19-5

20-4 Frame-lev el Statistics Display............................................................ 19-6

20-5 Port Statistics Configuration Menu .................................................... 19-8

20-6 Cumulative Statistics Menu................................................................ 19-9

20-7 Cumulative Statistics Report ............................................................ 19-11

20-8 IP Statistics Displ ay .......................................................................... 1 9-12

20-9 ICMP St ati stics Display.................................................................... 19-14

20-10 I P Interface St ati stic s Disp lay... ........ ... .... ........ .... .... ........ .... .... ........ . 19-1 6

20-11 IP X Statistics Display....................................................................... 19-17

20-12 Et hernet Card Statistics Display....................................................... 19-23

20-13 Token Ring Card Statistics Display.................................................. 1 9-23

20-14 Trunk/X.25 Port Status Displ ay ........................................................ 19-26

21-1 Alarms Report..................................................................................... 20-3

21-2 On-Line Alarm Routing Screen.......................................................... 20-5

22-1 IP Ping Connectivity Test Menu......................................................... 21-3

E-1 Sys tem File Type Selection Menu........................................................ E-1

E-2 LP Type Maintenance Menu ................................................................ E-2

E-3 Networ k Defaults Menu ....................................................................... E-4

G-1 FRX8000 Test Menu ........................................................................... G-1

G-2 FRX8000 INM Main Menu................................................................. G-5

G-3 Node Performance Display.................................................................. G-9

xi

List of Tables

1-1 Sup port ed Hard ware....... .... .... ........ .... .... ....... .... .... ........ .... ........ .... .... ... 1-5

4-1 Network Default Parameters................................................................. 4-4

5-1 Node Parameters................................................................................... 5-4

6-1 FRX8 000 RLP P aram ete rs......... .... .... ........ ... .... ........ .... .... ........ .... .... ... 6-4

6-2 N7000 RLP Parameters........................................................................ 6-7

6-3 N7400/7500 “Stand ard” LP Parameter................................................. 6-9

6-4 N74/7500 T1 LP Parameters.............................................................. 6-11

6-5 E1 LP Parameter s... .... ........ .... .... ........ .... .... ....... .... .... ........ .... .... ........ . 6-14

6-6 T1/E1 Chan nel Map Parameters ......................................................... 6-1 7

6-7 LAN Card Parameter.......................................................................... 6-18

6-8 PROTOC OL.INI Sample Report........................................................ 6-19

7-1 Trunk Port Parameters.......................................................................... 7-5

7-2 Modem In itial ization Pa ram eters .... ........ .... ... ........ .... .... ........ .... .... ..... 7-10

7-3 Physical PDN Port Parameters........................................................... 7-1 3

7-4 Subscriber Parameters........................................................................ 7-18

7-5 X.25 Trunk PVC Paramet ers .............................................................. 7-2 1

7-6 Telep ho ne N um ber Pa ram eters... ........ .... .... ....... .... ........ .... .... ........ .... . 7-24

8-1 Bandwi d th All ocati o n Group Parameters ... ... ........ .... .... ........ .... .... ....... 8-3

8-2 Frame R elay Port Parameters............................................................... 8-5

8-3 Frame R elay-to-Frame Relay PVC Parameter ..................................... 8-9

8-4 Frame R elay DLCI Parameters........................................................... 8-1 1

9-1 X.25 Port Parameters............................................................................ 9-4

9-2 X.25 CUG Param eter.......................................................................... 9-12

9-3 Modem In itial ization Pa ram eters .... ........ .... ... ........ .... .... ........ .... .... ..... 9-13

9-4 Subscriber Parameters........................................................................ 9-17

9-5 X.25 -to -X.2 5 PVC Pa rame ters... .... ........ .... ... ........ .... .... ........ .... .... ..... 9-19

9-6 Tran sl ati on Templa te Pa ram et ers........... .... ... ........ .... .... ........ .... .... ..... 9-23

9-7 Telep ho ne N um ber Pa ram eters... ........ .... .... ....... .... ........ .... .... ........ .... . 9-28

10-1 SNA Port Parameters.......................................................................... 10-6

10-2 Subscriber Parameters...................................................................... 10-1 0

10-3 SNA HPAD PU Parameters............................................................. 10-1 5

10-4 LLC2 Host Param eters..................................................................... 10-2 1

10-5 LLC2 Interface Parameters............................................................... 10-2 7

11-1 B SC Interactive Port Parameters........................................................ 11-4

11-2 Subscriber Parameter.......................................................................... 11-9

11-3 B SC Interactive Subscriber Parameters............................................ 11-1 1

11-4 C ontro l and Device Unit Addressi ng................................................ 11-13

11-5 B SC Interactive Device Par ameter................................................... 11-14

12-1 As ync PAD Profile Parameters.......................................................... 12-4

12-2 As ync PAD Login Parameters............................................................ 12-9

xii FR X8 000 3 .0 User Gu i de, Rev 02

12-3 Asy nc PA D Port P aram et ers......... .... ... ........ .... .... ........ .... .... ........ .... . 12 -1 1

12-4 Subs crib er Pa rame t ers .. .... .... ........ .... ... ........ .... .... ........ .... .... ........ .... . 12-1 8

12-5 Async PVC Parameters..................................................................... 12-21

13-1 IP Interface Parameters....................................................................... 13-5

13-2 IP Route P aram ete rs ......... .... .... ........ ... .... ........ .... .... ........ .... .... ........ ... 1 3- 9

13-3 IP-over-X.25 PVC Parameters.......................................................... 13-11

14-1 IPX L AN Interface Parameters........................................................... 14-4

14-2 IPX X. 25 Interf ace Parameters........................................................... 14-5

14-3 IPX Frame Relay Interface Parameters.............................................. 14-6

14-4 IPX Network In terface Parameters..................................................... 14-7

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

14-6 IPX SAP Filter Parame te rs............................................................... 14-14

14-7 IPX Packet Filter Parameters............................................................ 14-15

14-8 IPX RIP Ro uter Filte r Parameters .................................................... 14-16

14-9 IPX Filter A pplic a tions Parame te rs.................................................. 1 4-17

14-10 IP X R oute Parameters....................................................................... 14-19

15-1 SNMP Sys te m D efau l ts Pa rameters . ... .... ........ .... .... ........ .... .... ........ ... 1 5- 3

15-2 Commun ity Table Parameter .............................................................. 15-4

15-3 Trap R outing Parameters.................................................................... 15-5

18-1 Color Cod es for Subnet Di splay/Event Log ..................................... 18-11

18-2 Color Cod es for LP/LAN C ard/Port Status Display......................... 18-15

19-1 Cumulative Statistics Parameters ..................................................... 1 9-10

20-1 Alarms Report P arameters.................................................................. 20-2

21-1 IP Ping Connectivity Test Parameter.................................................. 21-4

E-1 LP Type Parameters.............................................................................. E-3

E-2 Networ k Defaults Parameters............................................................... E-4

xiii

Section I

Getting Started

Chapter 1

Overview

The NetlinkTM FRX8000 is a fully integrated LAN/WA N enterpris e switch, con­necting remote network sit es with a r obust switching technology that allows trans­missi on of LAN and W AN data tr affic over a s ingle acces s line. Th e FRX800 0 allows
the features of conventional m ulti-protocol rou te r s to be combined with those of fast
packet s witches, d eliverin g high perf ormanc e r egardless of the demands of th e access
pro tocols be ing used.

Some typical applications of the FRX8000:

●

SDLC-to-LLC2 and L LC2-to-QLLC con version over frame relay

●

SNA and TCP/IP LAN/WAN integration—w ith o r without router s.

●

Banking applications—LAN, SNA, TCP/ IP, asyn c.

●

Feeder networks to public frame relay services.

●

“Front end” network to larger frame relay switches.

●

Public and private access and backbone applications.

FRX8000 Switch

X.25, SDLC

FRX8000 INM

3174

FRX8000 Switch

Frame
Relay

FRX8000 Switch

IP

3174

Figure 1-1 Network Example

IBM
Host

3172

Summary of Features

Multi-protocol Support

Frame Re lay

●

LMI, Annex D local management

●

Annex F segmentation and re-assembly

●

Line s peeds up to 2.048 Mbps

●

FE CN and BE CN cou nt s

X.25

●

Compliance with 1988 CCITT X.25 Recommendation

●

Configurable as phys ical an d logical DCE/DTE

●

Line s peeds up to 2.048 Mbps

●

Clos ed user groups

●

Ad dress tra nsl ation over gatewa y

SNA/SDLC

SNA/LLC2

●

SDLC, X . 25 /QLLC

●

Configurable frame s ize, up to 4109 bytes

●

C onfigura ble lin k addres ses

●

DLC p oint-to-point and mu lti-point, with poll spoofing

●

NRZ/NRZI support

●

SDLC-to-LLC2 and LLC2-to-SDLC conversion

●

QLL C/NPSI c ompatib ility

●

Four modes: HPAD, TPAD (PU 1.0, 2.0), NPAD ( Hos t-to-host),
XPAD (tran sp arent)

●

Supports both e nds of P U2-to-P U2, P U2. 1-t o-P U2.1, and PU4-to-PU4
connect ion s

●

En d-to-e nd compatibility with SNA/A PPN dev ic e s over LANs

●

C ompatib ility o ver frame relay network with IB M FEP with NCP 7.1

●

MAC-le vel v irtual addressing

●

Token ring, Ethernet, or frame relay interface

●

SDLC-to-LLC2 and LLC2-to-SDLC conversion

●

RFC 1490 enc apsul ation in nati ve LLC2, 802.3, or 802.5 form at

●

QLL C/NPSI c ompatib ility

1-2 FR X8 000 3 .0 User Gu i de, Rev 02

IP

IPX

As ync

●

IP, ICMP, AR P

●

RIP ver s ions 1 & 2

●

St anda rd NDIS i nte rfa ce s for E the rne t, Token Ring, and 802. 3 LA Ns

●

RFC 1490 fram e relay and RFC 1356 X.25 interfaces for WANs

●

Support of Novell NetWare net works

●

Connection of LAN-attached w orkst ation to remote router or server via frame
relay, X.25, Ethernet, or Token Ring, or FRX8000 trunk

●

Filtering of certain types of traf fic, for traf fic co ntrol and access security

●

Support of RIP and SAP

●

Dynamic and static routing

●

Local login passwords

●

Autocall

●

Autobaud (automatic line sp eed configura tion)

●

Automatic discon nect on inactivity

●

X.29 support

●

Abb reviated addressing

●

R TS/ C TS hardware fl ow con t ro l

●

Configurable b anner message sent to async ter m inal

BSC

●

Interconnection of IBM 3270 (interactive) devices over X.25 or frame relay,
X.25, or FRX 8000 bac kbone ne t work

●

Full-dup lex line contr ol

●

Point-to-point and multi- po int operation on BSC Interactive p orts

●

Autoca ll from TPAD

●

Each HPAD su pp orts u p to 16 rem ote TPA Ds simultan eous ly

Overview 1-3

Versatile Management Functions

Connection Management

●

C onnection prioritiz ing and dy nami c bandwidth assignment

●

Mu ltiple tr ansport c lasses, con figurable p er connection

●

Protocol-indep e ndent SPF (s hortest pa th firs t) routing amo ng FRX80 00s

●

Dy namic load balancing

N etwork Manager

●

T wo types:

◆

FRX8000 INM (Integrated Network Manager) is an FRX8000 Switch and
network manager in the same box.

◆

NMP is a stand-alone manager, connected to the network v ia an attach ed
Nucleus 7000 (N 7400/N7500) node.

Nucleus 7000 Release 5.0 is supported in th e current release of
FRX80 00 , to allow a s mo oth tran sitio n of existing N7000 net­work s to FRX8000.

●

Intuitive, menu-based system that provides complete lo cal manageme nt (via
local VGA monitor or remote ASCII termin al) of network nodes

●

File transfer between INMs/ NMPs, and fro m an INM or NMP to an ICP. ( I CP
is an FRX8000 Switc h with all the functiona lity of the INM except the user
interface)

●

Remote software updates to FRX8000 Switch es

●

Self-lear ning route configu ratio n

●

Centralized alarm routing

●

Statistics display s

SNMP Man agement Su pport

●

Support of get, ge t_ne xt, and (for s ome fields) s et commands from SNM P
manage r, providi ng topology i nforma tion and node s t at us

●

FTP and telnet access to I CPs, INMs, and NMPs

●

MIB II (RFC 1213) S ystem & Interfaces Group, plus parts of frame relay
( R F C13 15) and SDL C (RFC1747) M IBs

●

En terp ris e network status inform ation via local MIB on no de

1-4 FR X8 000 3 .0 User Gu i de, Rev 02

Hardwar e Overvi ew

FRX8000 ha rdw are inc l udes:

●

T hree types of “device” : Switch , I CP, and INM. (A four th device, NMP, is sup ­ported in existing N7000 networks to facilitate migratio n to FRX8000 .)

●

Thr ee types of card: RLP (RISC-based line processo r), Ethernet L AN adapter ,
and Token Ring LAN adapter. (The NMP also supports the N7000 PIA, or Par­allel Interface Adapter .)

●

Two types of har dwar e chassis: Model 2 and Rackmount. (A High-Availability
chassis is available by special order.)

These components are all described in detail beginning on page 1-5. Their interrela­tionships are shown in Table 1-1.

Device Type Platf or m Max RLPs/LAN C ards/ PIA s
Switch

ICP, INM

NMP

1
2

3

Tabl e 1-1 Support ed Har dw are

1

2

2, 3

A PIA is used only if the Switch i s directly attached to an NMP.
A LAN card is supported in the ICP, IN M, and NMP for local FTP or Telnet file main-

tenance only.
Although the NMP is supported on these platforms, NMPs g eneral ly will be in existing

platforms in established N7000 networks.

Model 2
Rackmount

Model 2
Rackmount

Model 2
Rackmount

4/1/1 or 3/2/1
8/0/0 or 7/1/0 or 7/0/1 or 6/1/1 or 6/2/0 or 5/2/ 1

4/1/0
8/0/0 or 7/1/0

1/1/1
8/0/0 or 7/1/0 or 7/0/1

Device Types

FRX8000 Switc h

The FR X8000Switch, an MS-DOS®-b ased node, per forms swit ch i ng and routing.
E ac h S witc h support s fram e re l ay, X.25, SNA/SD LC/L LC2, BS C, async hronous, IP
( including R IP, ARP, ICMP), IP X, and SNMP protocols .

The base model of an FRX8000 Switch contains one RLP with one Line Interface
Card, providing four WAN ports, and supporting up to 512 simultaneous logical ter­minati ons . (Each lo gical interf ace into or out of an RLP p ort is one te rmination .) The
Switch is expandab le as shown in Table 1-1.

IC P

T he FR X8000 I C P is a UN IX®-based switch with call p rocessing capability plus all
functions of the Switch except L AN connectivity. Each ICP contains a copy of the
networ k datab ase (desc ribed in Chapter 3). ICPs are typical ly deploye d in large net­works to distribute database access and call setup, preventing setup delays caused by
long paths to distant INMs (described below).

Overview 1-5

Cards

INM

The FRX8000 INM is an ICP with add e d networ k management capabilities, used to
configure and control FRX8000 Switches throughout the network. Each INM has a
local key board an d VGA monitor, and can also b e controlled by a lo cal or remote Aux­iliary Console (ASCII t erminal or terminal em ulator) .

RLP

T he FRX80 0 RL P, an i960 RISC -bas ed line proc ess or, p rovides s erial inter faces, co n­nect i ng various s ynchro nous and a s ynchronous user devices t o publ ic or priva te net ­works. Each RLP supports up to 51 2 simultane ou s logical terminations. (A link into
one physical/logical port on an RLP and out another port counts as two terminations.)

LAN Adap t ers

An FRX800 0 supports LAN (local-area network) inter faces via th ese adapters:

●

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

●

T oken Ring (802.5) – RJ45 (tw ist ed pa i r) or D B9

Depending on the chassis model and number of RLPs, an FRX8000 Switch can
contain one o r two LAN cards (in any combination). Each LAN car d supp orts one
LAN interface.

The ICP and INM support one Ethernet in terface for FTP and telnet access.

Chassis

T here are two ch ass is u sed in th e FR X8 000 prod uct lin e, differ ing in size a nd ca pacity
(see Table 1-1.)

Operator Interfaces

●

●

●

Althoug h the FRX8000 Switch and ICP do not requir e an operato r interface fo r
normal operation, an o ptional locally attache d VGA mo nitor can be useful
du ri ng operati on f or di s pl ayin g perform anc e dat a. (A keyb oa r d i s a ls o nec es s a ry
any time a monitor is used.)

Each INM an d NMP has a local keyboard and VGA m onitor. The device can
also be controlled via an o ptional Auxiliary Conso le (ASCII te rminal/keyboard
or PC with terminal emulation so ftwar e), attached directly or via mode m to the
COM2 serial port in the INM/NMP.

Any INM or NMP with IP an d SNMP con figured can be accessed by
Cab l e tron’ s S pec trum ® m a n a gement pro du c t s .

Eve nt Logging Printer

Each INM, ICP, and NMP can have a local (via COM1) printer, t o which alarm mes ­sa ges ar e sent from the INM/IC P /NMP and a ny ot her node s tha t report to it. Seve ral
parameter s in Node records (see Chapter 5) d etermine where alarms are sent.

1-6 FR X8 000 3 .0 User Gu i de, Rev 02

The installation docum ent th at is sh ipped with each FRX8000 describes the procedure
for setting up a new node and configuring a connection to the operational networ k.
Before the node can become fully functio nal, howeve r, the software must be cus­tomized for the devices to which it will conn ect, the traffic it will receive and transmit,
and various operating parameter s that can be set to your specific needs.

This cus tomization is done via c onfiguration of database re cords (described in Section
II), which identify th e hardware componen ts and conne cted devices . Access to the
database records is through a system of screen menus on an INM on the operational
network.

Using the INM Menu System

Chapter 2

Getting Started

FRX 8000 netwo rk managem ent functio ns are carried out at one of three “lev els ” in an
INM or NMP:

●

Sys tem level – is where UNIX o perati ng system functions, as well as some
FRX8000 non-menu operations, ar e pe rformed. The s oft wa re enters this l eve l
during start up of an ICP/INM/NMP, and can b e accessed later by exiting the
menu level.

●

M e nu l eve l – i s wh e re m os t s oft w a r e c o nfi g urat i on i s p erform e d, by us ing men u
select io ns on an INM/ NMP s cr een to open and cha nge datab ase fil es (describ ed
in Ch a pter 3). Most monito ring and control operations can b e performed with
menu operations.

●

Graphics level – p rovides a visua l rep res entation of the netwo rk, and allows
many of t he monitor ing and cont rol operations ava ilable fro m the menus. T his
level is enter ed from th e menu level, an d is available o nly on a local VGA
monitor.

The men u level co nsis ts of a series o f menu s and su b-menus that ar e used t o confi gure,
contr ol, and mo nitor FR X 8000 s. The Main Men u is shown in Figure 2-1. The organi-
zation of the sub-menus under Main Menu item A is shown in Ch a pte r 3. O rg a ni za t ion
of sub-menus under Main Menu items B–H is shown in Chapter 17.

Netlin k FRX 8000

M A I N M E N U

A Configuration

B Operations

C Status Displays

DAlarms

ETests

F Statistics

G R eports

H Gr aphics-Level Status Display

R Exit to System Prompt

S elect:

Figure 2-1 Main Menu

Item

[H]

does not support graphics.)

Moving Through the Me nus

Follow these steps to maneuve r through the menu s:

●

To ente r an op er at i o n or a no t he r me n u from a m enu, p re s s ( on th e keyb oard) the
letter to the left of th e desired m enu item.

●

To exit an oper ation /menu, pr ess either
available choices.)

●

To display a list of function key operations at a menu, press

●

To aband on any current changes and exit an operation, press

Menu-Level Prompts

Within the menu operations, there are two kinds of prompts (displayed words that
req uire respon ses):

●

Inform a tion prompts – respond by typing the reques ted inform ation , then
pressing

●

Yes/no prompts – respond by pressing

[Enter]

is displayed only on a local VGA monitor. (Th e Aux iliary Co nsole

[R]

or

. (Both are not always

[F3]

.

[?]

[Esc].

.

or

[N]

.

[Y]

T hroughout this manual are tabl es of v alid and default valu es. To specif y a defau lt (if
one exists ), pres s

Be ca reful ; pr es sing
next prompt to automatically select the default choice.

2-2 FR X8 000 3 .0 User Gu i de, Rev 02

[Enter]

in re s pons e to a prompt.

[Enter]

w hen it is not required may caus e the

Section II

Configuration

Chapter 3

Introduction to Database Configuration

The FRX8000 database comprises records grouped into files. Each record co ntains
parameter s that define a specific compo nent; for example, RLP 3 in No de 12. E ach
file contain s all same-type records in the databa se. (The LP file contains all RLP
recor ds, the Node file all Node records, etc.) An identical database resides in each
FRX 8000 ICP and INM (and each N70 00/F RX NMP), allowing the entire netwo rk to
oper ate as a sing le e ntity.

The following shows wh ere to find the va rious c onfiguration database files among the
FRX8000 menus . (The first ite m,
lowing m ost items are descriptions of the associated database recor d s, statements as
to whether a reco rd is requir ed, and r efer ences to th e chapter s or appen dices whe re the
items are described.

Even if a re cord is required , configu ration of some parameters in that
record might be optional. Determination depends on the specific use of the
FRX8000 component (LP, port, etc.) being configured.

Configuration

, is an entry on the M a in Menu.) Fol-

A Configuration

A Configure Network

A Configure Network De fau lt s

parameters the network needs for proper operation of FRX8000s.
Required.

B Configure Network Re pr esentation

network, which will display icons representin g nodes or parts of the
network, plus color-code d oper ational sta tus. Will also display outstandin g
alarms and port st atu s .

C Configure Async PAD Profil e

dev ices co nnected to async P AD ports in FRX80 00s . Re qu ired if at taching
to any as ync de vic es a nd desi ring parameter values ot her than those i n
CCIT T profile ST D90 or 91, which are pa rt of the def ault da t aba s e.

D Configure Async PAD Logi n

used by a subscriber on an async PAD port. Required if login to the PAD
will be neces s ary.

E Configure Async PAD Banner

displays on terminals connected to async PAD po rts.

F Configure IPX Filter Def initions

tra ns missi on of RIP /SAP updates, and/or gener i c IPX packe ts, per
interface and direction.

G Configure Frame Relay Bandwidth Allocat ion

to 16 groups that assign connection priorities to va rious types of traffic.

– Cha pter 4. N o de and X.2 5 l e vel - 3

– Chapter 4. Graphic map of the

– Chapter 13. Operating parameters for

– Chapter 13. Profile and password to be

– Cha pter 13. Custom head ings for sc reen

– Chapter 15. Parameters that regu la te

– Chapter 8. Defines up

B Configure Node

A Configure No de

– Chapter 5. Definition of node type; specific ation of
alter nate INMs/NMPs tha t wi ll take o ver the local node’s fun ction s if it
loses contact with the networ k; routing for this node ’s alarm s. Requir ed f or
every no de .

B Configure SNMP Parameters

– Chapter 16. Identifyin g informa tion on
the SNMP manager; definitions of communities; trap routing. Required if
using the SNMP agent.

C Confi gu r e Cards

A Configure Line Processo r

– Chapter 6

– Identifying parameters for all LPs in
FRX 8 000 a nd N 70 00 no des on t h e n e tw ork. I nc ludes i d e nti fic at i on of Line
Interface Cards on RLPs, and installed protocols. Required for every LP.

B Configure LAN Card

– Identification of type s and lo cations of all Ethernet
and Tok en Ring cards in FRX8000s on the network. Required fo r each
Ethernet and Token Ring card.

D Configure Por ts

A Configure Por t

– Cha pter 7 (trunk), Chapter 8 (frame relay),
Chapter 9 (X.25), Chapter 11 (SN A), Chapter 12 (BSCI),
Chapter 13 (async). Identi fyi ng and oper ating parameters for a l l physi ca l
and logi cal LP ports o n the netwo rk. Specifies serial i nterface s, lin e speed ,
protocol-specific parameters . Required for every serial p ort.

B Configure Fra m e Rel ay DLCIs

B

, BE). Req uired for each frame relay DLCI.

C

C CUG Management

A Configure X.25 Port CUG

– Chapte r 8. Data rate parameters (CIR,

– Ch apte r 9. Allows creatio n of clo sed user
groups, to regulate which subscriber devices can r eceive and/or transmit
from/to other devices.

B Configure Internati onal CUG

D Configure X25 Address Transl ation Te m plate

– is not currently suppor ted.

that are appl ied to incomi ng and outgoing cal l packets for the purpose of
translating selected fields of a packet that may not otherwise be in a
co mpa tible format.

E Co nfigure Modem Initializat ion

– C hapte r 7 (Tru nk), Chapter 9 (X.25).

Cu stomized string of data that will be s ent to the modem on a V.25 bis p ort.

F SNA PAD Mana g ement.

A Configure SNA 7000 HPAD-PU

Chapte r 11.

– Ident i fying parameters for the
device s connected to SNA TPAD po rts on Netlink Nu cleus 7000s.
( This p r od uct is su pp orted f o r e x i sti n g c u st o me r s.) Re qu i re d for every
N7000 TPAD except the first one for each HPAD. (This is defined in
the Port file).

B Configure SNA 7000 TPAD -P U

– Identifying parameters for PUs

(physical units) in an N7000 TPAD mu ltidrop con figuration.

C Configure SNA FRX8000 SDLC-PU

the devices connected to FRX8000 SNA ports. Required for every
PU (phy sic al un i t ).

G BSC Interac tive PAD Management

– Chapter 12. Identifying parameters
f or subs cribers a nd device s us ing FRX8000 por ts c onfigur ed a s BSC
Interactive. Requ ired for every BSC Interact ive subscriber and device.

A Configure BSC Intera ctiv e Subscribers
B Configure BSC Intera ctiv e Devices

– Ch a pter 9. Templates

– Identifying parameters for

3-2 FR X8 000 3 .0 User Gu i de, Rev 02

E C onfi gur e LAN Interfaces

A Configure IP In terfaces

– Chapter 14. Identification of any IP in terfaces
in FRX8000s on the network. Identifies type (X.25, Ethe rne t, etc.) and
oper ating par a meter s. Requ ired for every IP interface.

B Configure IPX Manage m ent

A Conf igure IPX Interfac e

– C h a pte r 15.

– identification of any Novell® IPX
interfa ces in FRX8000s on the network. Identif ies type (X.25,
Ethernet, etc.) and operating p arameters . Required for every IPX
interfa ce.

B Conf igure IPX Applicati ons

– a pplie s IPX filters to interfaces,

filter types, and/or dire ction s.

C SNA LLC2 Ma nagement

A Conf igure SNA LLC2 Hosts

– Ch apt er 1 1.

– de fines LLC2 ho st s; i nc ludes session

type (originated or terminated), nece ssary addr esses, timers.

B Confi gure S NA LLC2 Interface

– speci fies locatio n, type, and format

of any LLC 2 interfaces.

F Configure Connec tions a nd Routing Paths

A Configure Subscri ber

– Ch apter 9 an d mis c. ot her chapt ers. Sp ecificati on
of s ubscriber IDs, used as called and calling address es in X.25 call setup;
algorithms for call routing; bandwidth allo cati on, redire ction addresses.
Required for all traffic being transporte d over a logical X. 25 po rt.

B Configure Abbreviat ed Addre ss

– Chapter 13. Cr eates a short name or

mnemonic that can be su bs tituted for an async PAD subscriber address.

C Configure PVC Connection

– C hapte r 7 (trunk), Chap t er 8 (frame rela y),
Chapte r 9 ( X. 25), Chapt er 13 (async), C hap te r 1 4 (IP). Creation of
“permanen t” connections between FRX8000 ports. Identifies location,
protocols at each end, operating parameters.

D Configure IP Route
E Configure IPX Route

– Cha pter 14. Cre ation of fi xed routes for I P tra ffic.

– Chapter 15. Creation of fixed routes for IP X

traffic.

F Configure Group Name

– Chapte r 9. Specifies a name to be used for

Group Send messages.

G Configure Group Send

– Ch apter 9. Allows an X.25 subscriber to
broadcast a message to a group of subscribers by sending a single Call
Request.

H Configure Telephone Number

– Cha pter 7 (trunk), Chapter 9 (X.25).

Numbers used by all V. 25bis mode ms on the networ k.

I Configure T1/E1 Channel Ma p

– Ch a pt e r 6 . DS0 ch annel as sign ments for

T1/E1 lines. Required for all T1/E1 car ds .

G Configuration Repor t

– page 3-12. Produces a summary of database records
for one or all FRX8000s on the network, listing database parameters and
values.

H Change Passwords

– App endix C . Al l ows ch anging se veral of th e p ass w o rds

used to access FRX8000 operations.

Introduction to Database Configuration 3-3

Data base Set up Rec ommen dation s

To set up a network databas e, you m ust create records for all nodes, LPs, ports, and
subscribers (users of the ports), as well as other records that define your network con­figura t ion. (Creating records is described under “Configuration Oper a tions” on
page 3-5.) It is a goo d idea to review the remaining chapters in Section II before pro­ceeding with your con figuration, to be awa re of all th e parameters that must be, or can
be specif ie d.

You should b e familia r with all devices that will connect to FRX8000s; some have
requirements or restrictio ns . It can also be help f ul to create a diagram or wr itte n
description of your entire network. Some things you must know before configuring the
dat abase are:

●

What is each node's type (Switch, ICP, etc.)?

●

What is each nod e’s ID? Each no de must be assigned a unique number (

●

How many line pr ocessors (LPs) are th ere in each node, and what is the L P
number (ID) of each ? (This is de te r min ed by switch settings on the board – see
the RLP configuration drawing in Chapter 6.)

●

W ill each LP port will be a p hy sical DCE or DTE (determined by cabling) and
wh at kind of device will be connected to the po rt?

●

W hich ports will be trunks to other nodes? ( For continu ed operation in case of
a trunk failure, you should have at least two trunks per node.)

●

W ill each port be direct-con nect, leased line, or dial-in line? The modem con­nected to a dial-in line must be config ured so DSR (Data Set Ready) is not
forced high. DSR should follow CD (Carrier Detect).

●

Are there any LAN (Ethernet or Token Ring) cards in the node? If so, which i s
card 0 and which is car d 1? (See Chapter 6.)

●

What netwo rk featur es/ser vices (Closed User Gr oup, Hu nt Group, Gro up Send ,
Fast Select, Reverse Charging, etc.) will each subscriber be allowed to use?

●

What are your passwords? You must enter a password to perform configuration
operations, to remotely IPL a node, and to perform a fe w other operations.

1–250

).

M os t paramet er s ca n be c onfi gured usi ng t he ope rations de s cribed
throughout Section II; others, such as LP or port number, are defined by the
ha rdwa re or specified during softwar e installation.

Setup Procedure

Mo st datab a se files contain informatio n used by other files. Entering undefined iden ­tifying information will produce the message:
rences of this, follow the sequence de fined by the chapters in the remainder o f Section
II when cr e ating a database. You will still see the error message when cre a ting some
records; howeve r, this will not cause a prob lem as lo ng a s all the n ecess ary reco rds ar e
created before attempting to bring the node on line on the network.

3-4 FR X8 000 3 .0 User Gu i de, Rev 02

Not in Datab ase

. To minimize occur-

Her e is the re com mended pr ocedu re for setting up or modifying the configu ration
database. Valid and defau lt values for configuration para meter s can be found in the
appropriate chapters.

1. Create or modify the necessary database re cords. (To do this you will need to
acquire master statu s— see page 3-11. )

2. Dow nload the updated records t o t he node . (M et hods of doing thi s are described
in the appropriate ch apters.)

3. Except in cases where an on-line u pdate is possible (identified in the appropriate
chapters), re- IPL th e node (described o n page 1 8-4).

Co nfigur ation O per ation s

Selecting most Configu ration items from the m enus will displa y another menu con ­sisting of four o per a tions that can be performed, as shown in this example.

Subscriber Operations

A Initialize File

B Inq ui ry

C Maintenance

D Lists

E Re t ur n t o Prev i o us M en u

Select:

Figure 3-1 Operations Menu Example

The operati ons are used as follo ws:

Init ial ize File

deletes an entire file, so you can replace it with a previously
saved one, or create a new one.

Inquiry

displays an individual re cord, inclu ding the current values for
the par a meter s that constitu te the record.

M ainte nance
List

allows you to add, delete, or modify records.
provides a summary of the records in a file.

Introduction to Database Configuration 3-5

Initialize File

In it ia lize File

and

Maintenance

re quire master st atus .

T he oper ations ar e described o ver the n ext few page s. T he ord er of the four operatio ns
on the screen is of no particular importance. Whe n creating a new database, only

tenance

wi l l pr ob a bly be used.

Main-

This op e r ation allow s you to append a p rev iously s aved file to an existing one, or to
delete the existing one so a n e w one can be bu ilt by creating new reco rds. The oper-

ation requires master status.

Th is ope rati on s hould be perform ed only by, or unde r t he direction of, a
system administrator or qualified service r eprese ntativ e, and only at an
INM that is not running in a network. Initializing a file deletes all re c ords
in that f ile.

1. At the Oper ations Men u, select

List

. U si ng

Output to Hardcopy Device

, p rint the

existing file (for refere nce) .

2. Using

3. Select

Output to Disk File

In it ialize Fi le

, sav e the existi ng file.

.

4. When prompted, enter your database maintenance or high-level operations
password (or press

5 . Y o u w ill be a sk ed:

going to append a saved file to the existin g one, press

6. Yo u are ask ed:

an d proc e ed with step 7. If you are not going to load a previously saved file,

[Y]

press

[N]

Initial File Load?

to e xit the operation .

to return to th e Operations Menu).

[Enter]

In it ialize Fi le ?

To delete the existing file, press

To load a previously saved f ile (see step 2), press

[N]

; if you a re

[Y]

.

If you initialized the existing file but did n ot p erform an initial file load,
you will have to bu ild a new file by creating new r ecords (using

operations).

nance

Mainte-

7. When asked for a file specification, enter the file name you saved in step 2.

8. As records are loaded into the file, the number of records added and number of
er rors (if any) ar e display ed. If there are e rrors , print the n ew file an d comp are the
printout to the printout of the saved file from ste p 1. Wh en you have iso lated the
erro rs, add or ch ange the necessary records. (See “Maintenance”on page 3-9.)

9. Press any key to r eturn to the Opera tions Menu.

3-6 FR X8 000 3 .0 User Gu i de, Rev 02

List

This operation displays , prints, or saves to disk, a summary o f the contents of a
dat abase file. B ecaus e a list co ntains p arameter v alues but not their n ames, sum maries
will be fairly cryptic a nd may require some interp retatio n, a s is evident in the example
in Figure 3-2. However, this information is not generally used by the sy stem operator,
but by Cablet ron S ystems Techni cal S upport .

To create a list:

1. Press

[D]

at t he O pe r a ti ons Me nu . (A n ot h e r m e nu ma y be d i sp la yed, al l o w ing yo u

to choose what info rmation will be included in the list.)

2. You may be prompted for a node ID. If so, enter a node number to list the records
f or components of that node, or press
network.

3. A menu will be display ed, allowing you to choose among sending the file to the
printe r , the screen , or the har d disk. These o ptio ns are described in the following
paragraphs.

Output to Hardcopy Device

[A]

Press

a t the Output Device Menu to print the infor matio n. Press
tru nca te the rep ort . (Pre ss
mes sage:

File List Terminated

Operations Me nu.
The format of the report is similar to the display in Figure 3-2.

Output to Disk File

1. At the Output Device Menu, press

2. W hen asked:

3. Wh en pro mpt ed for a fi le specifica tion, enter a file name, n otin g these r ecommen­dat ions:

[F3]

again to return to the Opera tion s Me nu.) When the

signals the end of the report, press

Formatted Output?

[B]

, press

[Enter]

.

[N]

.

to list records for all nodes on the

[F3]

at any time to

[F3]

to retur n to the

●

●

●

4. W hen the message:

[Enter]

5. Press

Introduction to Database Configuration 3-7

All ch aracte rs sh ould b e lo wer case, sin ce th e databas e file names are upp ercase,
and y ou don't want to write over them.

Sp ecify a nam e using a ny combi nation o f letters and numbers (but no spaces ) in
the format “filename. ext,” where “filename” is 1–8 characters and “ext ” is 3
chara ct ers. The fir st p art c an act as a sp ecific iden tif ier wit hi n a broade r categ or y
defi ned by t he second part.

Cho ose a name that h elps i dentify the file. For e xample, a n appropr iate na me for
the Por t Co nfiguration file is “portcon.fil.”

File list terminated

appears, the ou tput is finished. Press

to return to the Operations Menu.

[F3]

repeatedly to return to the Main Menu.

Output to Terminal

At the Output Device Me nu, press

. The inf ormation is displ aye d on your screen,

[C]

as shown in the following figure. The information is scrolled; i.e. , until the end is
reached, it pa sses by on the display to m ake r oom for more. To stop th e scrolling, press

[Scroll Lock]

. Pre ss

[Scroll Lock]

SNO RUD NAM DCE
00 N N 0000000000000 0 N 0 0 N 0

0100212345subc N 10 0 2 Y
3

0 99 2551 1 N N N 00 00 00 00 00 00
00
00 00 00 00 N N 393920202020202 20 N 32 32 N 8224

0100312345 subd N 10 0 3 N
3
0 10 10 4095 Y N N N 00 00 00 00 00 00 00 00
00 N N 0 N 1 0 Y 0

0110012345sube Y 5551234
00 N

N N Y00 00 00 00 00 00 00 00 00 00
N N 2020202020202 20 N 0 0 N 0

again to restart scrol ling .

Inquiry

Figure 3-2 “Output to Terminal” Display

This display is not generally used by the system operator. I f you need
to interpr et the format, c on tact Cabletron Systems Techni cal Support:

Phone:
E-mail:
FTP:

603-332-9400
support@ctr on.com
ctron.com (134.141.197.25

Monday–Friday, 8 AM–8 PM Eastern time

)
Login: anonymous
Passwo rd: Yo ur e-m ail add ress

Press

once to return to the p r evio us menu, or repeate dly to return to the Main

[F3]

Menu.

This o per ation lets you look at ea ch re cord in a file; however, no ch ang es can be made.
(Therefore, the operation can be p erformed without first acquiring master status.)

At the Opera tio ns Menu (Figure 3-1), press
appea r, de pending on the file being used . Figure 3-3 is an example of an

. Diff eren t prompts and/or display s will

[B]

Inquiry

display.

Port Inquiry
* Node ID 10 nod e10
* L P ID 0 RLP
*Port 1

Port Type 2 X. 25
Physic al Inter face 5 V. 35
Blocked port flag N
Line Speed Code 10 9600 bp s
Mod ul o 8
O utstanding Fr ames 2
N2 Maximum Retr ansmissions 5
T1 Retransmiss. P eriod-ms 2000
T2 Acknowledg. Del ay-ms 1000
T3 Link As sur ance Period-s 10
Logical DCE Y
Gener ate Clock Y
Rcv Clock (TT) from DTE N

Mask Link Al arms Y
1 X. 25/Level 3 - Part 1
2 X. 25/Level 3 - Part 2
3 X.25 CUG Man agement

Select:

Figure 3-3 “Inquiry” Example

Maintenance

The displays for

Inquiry

and

Maintenance

except for alphabet ical line iden tifiers on the

operations are identical

Maintenance

screen th at

allo w you to select items to ch a ng e.

For most operations, your options from here are:

●

To see another record, press

●

To see the next record, press

●

To return to the Opera tions Menu, p ress

●

To return to the Ma in Menu, press

Use

Maintenance

operations to add, modify, and delete records. (Since reco rd mainte-

[F1]

[F2]

.

.

[F3]

.

[F3]

repeatedly.

nance alters the database, you must fi rst acquire master status.)

1. A t the Op eratio ns Menu (Figure 3-1), pre ss

[C]

.

2. When asked for a password, enter your database maintenance or high-level oper­atio ns passwo rd (describe d in Append ix C).

3. Enter the r equest ed infor mation; fo r examp le, nod e ID, LP I D, etc. If the sof tware
finds a record that matches the entered inform ation, it will be displayed, similar
to Figure 3-4.

If no record is found, you will be asked to enter valu e s for the remaining parameter s
to create a new reco r d. Pressing

in response to a prompt selects the default

[Enter]

value, if there is one. (Def ault v alues can be found in tables throughout this manual.)
If a valu e is entered incorrectly, press

enter the value. You can back up several entries by pressing
You must, however, re-enter each value.

Introduction to Database Configuration 3-9

to re-display th e previous promp t, then re-

[F3]

once for each entry.

[F3]

Port Ma inte nan ce
* Node ID 10 node10
* L P ID 0 RLP
*Port 1

A Port Type 2 X.25
B Ph y si cal Int e r fa ce 5 V.35
C Blocked port flag N
D Lin e Speed Code 10 9600 bps
EModulo 8
F Outsta ndi ng F r a m es 2
G N2 Maximum Retransmissions 5
H T1 Retransmiss. Pe riod-ms 2000
I T2 Acknowledg. D elay-ms 1000
J T3 Link Assurance Per iod-s 10
K Logi cal DCE Y
L Generate Cloc k Y
M Rcv C lock (TT) from DTE N
N Mask Link Al arms Y
1 X.25/Level 3 - Part 1
2 X.25/Level 3 - Part 2
3 X.25 CUG Management

Select:

Figure 3- 4 “Mai ntenance” Example

4. Once the r ecord is dis played, the following optio ns are av ailable:
a. To exit

Maintenance

, press
b. T o disp la y the next sequential recor d in the file, press
c. T o display another record in the file (o ther than the next one), press

[F3]

.

.

[F2]

[F1]

enter new values.

d. To delete the record, pres s [

to delete, or

[Y]

to delete a nd display the next record (see option “b”), or

[F2]

to leave the record alone.

[N]

. When asked:

F4]

Delete?

, press:

If the record is deleted, the following alarm message will be sent to the
ev ent log (which will display and/or print it, depending on how certai n
parameter s are con figured):

(Date/Time) Database change #xxxx-x yyy initiated for (Filename)

where:
(

Date/Time

xxxx-x

is the type of change (

yyy

(

Filename

) is wh e n the change was made,

is the transact ion and node number,

ADD, UPD, or DEL

) is the name of the file changed.

), and

e. T o copy the record to another record in the same f ile (p ort to port, LP to

LP, etc.), press
be copied, and a

and enter the requested information. T he record will

[F5]

Database change

me ssag e like that in op tion “d” will be

printed.

, then

3-10 FR X8 000 3 .0 User Gu i de, Rev 02

You cannot copy a physical port’s record to a logical port, or vice
versa.

Maste r Status

f. To move the recor d (copy it to another r ec ord an d automatically de lete the

o rig in al re cord ), pre ss
be moved, and a

Database change

and enter the requested information. The record will

[F6]

me ssag e like that in op tion “d” will be

printed.

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

g. To send a Port record update to the port’s node (without disrupting node

operation), press

Continue?

Pr ess

operation after it starts by pressing

. You will be warned:

[F7]

[Y]

(or

if you c hange your mi nd). (You ca n abort t he

[N]

[F3]

Update will disable port/LP

.)

.

h. To change a value, enter the letter precedin g the entry, then enter the new

v al ue . Th e da ta ba s e w il l be up da t ed, an d a
that in o ptio n “

” will be printe d.

d

Database change

message like

Note that an entry preceded by an asteris k cann ot be chan ged, b ecause
tha t entry is part of the key to the reco rd.

“Database Master” status is a mechanism f o r assuring concurrence throughout the
networ k. A copy of the database resides in each FRX8000 ICP and INM, and each
N70 00/FRX NMP. For the network to operate pr operly, all copies must be identical.
To assu re this, database changes c an b e made o nly at the INM/NMP that currently has
master status. A ny change will then immediately and automatically be distributed to
all other operational INMs/NMPs on the network (unless the network has become par­titioned—see “Partitioned Network” on page 3-12).

How to Get Master Status

Any FRX800 0 IN M or NM P on t he n et w or k c an requ est ma st er s ta t u s. I f y ou att e mp t
an opera tion that require s mast er status and your INM/ NMP is no t master, you will
be asked:

Request master status?

master, one of these will happen:

●

If master status is available (not being used), your I NM/NMP will become
master and b e admitted to the operation.

●

If another INM /NMP is pe rforming an ope rati on requiri ng mast er status , your
request will be denied. Press

●

If the master is d own or in another part of a pa rtitioned network, you will b e
asked:

Initiate Elect Master procedure?

assigned to the INM/NMP with the lowest node ID currently running in “y ou r”
part of th e ne twork.

[Enter]

. When asked:

Press
will now beco me m aster.

When you leave an operation that requires mas ter status, your INM/NMP will retain
maste r status until anot her INM/NM P requests it.

Introduction to Database Configuration 3-11

Press

[Enter]

Request master status?

; de pen ding on the status of th e cur rent

[Y]

and try ag ain later.

Press

. Maste r Statu s will then be

[Y]

, pre ss

; your INM / NMP

[Y]

Partitioned Network

The network could become partitione d, creating a situation with more than one
database master and, consequentially, different databases. This can happen in two
ways :

●

●

A new INM might be added to the network improperly.
If an INM/NMP loses comm unic at ion with the network while that INM/NMP

has ma ster status , another INM/NM P can acq uir e master stat us. Wh en th e failed
INM /NMP com e s back into the network, it will see itself as master, as w ill any
nod es that report to it.

If a multiple master situation occurs, the alarm message

No de “n”

will be sent to the INMs/NMPs specified as “Primary” and “Secondary”

nodes in the Node Confi gura tion record for Node “ n.”

If the network has become partitioned, contact Cabletron

Systems Technical Support.

P ro ducing Confi gur at ion Repor t s

The Configuration Report shows current c onfigura tion par ameter s for any or all
FR X8000s on the n etwork. For each node, the report contai ns:

●

Node, LP, and port parameters and their config ured valu es.

●

An y error messages related to configur ation (e. g.,

●

A summary list of LP and port types, showing the total number of each.

●

The nu mber of SVC a nd PVC sub scriber s assig ned to the no de(s).

A cu rrent p rintout of the Configuration Rep ort sh ould always be available for ref­erence.

Multiple database master at

Il le gal LP ID

).

To produce a Configuration Re port :

1. Pr e ss

[G]

2. Whe n prompt ed, enter a node ID, or pr ess
3 . Yo u w ill be pr o mp t e d:

save the report to a file, type
specification.

4. Press

3-12 FR X8 000 3 .0 User Gu i de, Rev 02

[F3]

A C on figuration Report can be long; while it is pr inting, any status mes­sages will be held, then pr inted at the end of the rep ort. Select a time of rel­ative network inactivi ty to generate the report.

You can also create reports consisting of only the SVC Subscriber p aram­eters or PVC Connections. These are described page 3-1 3.

[A]

, then

from the Main Menu.

Display Opt. P or F

f [Enter]

and enter a file name when asked f or a file

[Enter]

to include all nodes.

. To p rint the report, typ e

p [Enter]

. To

at the Reports Menu to re turn to the Ma in Menu.

I f you experience probl ems on t he ne twork, the foll owing procedure might hel p so l ve
them:

1. R eview the status messages (d escribed in Cha pter 17) on the printer.

2. If the problem is no t apparent from the messages, print a con figura tion rep ort. It
might co nt ain warnings and errors cau sed by inaccuracies or incons istencies in
your database information. (Although the software notifies you when you make
invalid config ura tion entr ies, it sometimes accepts them. )

3. C heck all database parameters and make any necess ary changes.

4. Print an othe r configu ration report. Check it fo r warnings, and compa re it against
the fi rs t repo rt .

SVC Subscriber R epo rt

An SVC Subscribe r Report con sists of the configur ed values for all database param­eters for all Subscriber IDs associated with one or all nodes.

You can cre ate this report and d isplay it on the lo cal screen, print it, or save it to a file
for later use. To do so:

PVC Report

1. Press

[B]

a t t he Rep orts Menu (or

[G], [B]

fro m the Ma in M e nu ).

2. When prompted, enter the ID of the node whose subscribers you want in the

[Enter]

repo rt. Note that pressing

3. Y ou will be prompted :

●

To print the re port, ty pe

●

To save the r epo rt to a file, type

Display Opt. P, F, V

s e lects the default of All Nodes.

:

p [Enter]

.

f [Enter]

. When prompted fo r a file

specification, enter a file name for the r eport.

●

To disp la y the report on the scr e en, type

v [Enter]

.

A PVC Report consists o f the configured values for all database paramet ers for all
PVC s associated with one or all n odes. You ca n create th is re port and display it on the
local screen, print it, or save it to a file for la te r use.

1. Press

[C]

a t t he Rep orts Menu (or

[G], [C]

fro m the Ma in M e nu ).

2. When prompted, enter the ID of the node whose PVCs you want in the report.
Notice that pressing

[Enter]

3. Y ou will be prompted :

●

To print the re port, ty pe

●

To save the report to a file, type

selects the default of

Display Opt. P, F, V

p [Enter]

.

f [Enter]

:

. When prompted f or a fil e spec ificati on,

Al l Node s

.

enter a file name for the report.

●

To disp la y the report on the scr e en, type

v [Enter]

.

Introduction to Database Configuration 3-13

Press

Chapter 4

Configuring Network Parameters

[A]

at the Config ura tion Menu to displ ay the Network Selection Menu.

Network S election Menu

A Con figure N etwork Defaults

B Configure Ne twork Representation

C Con figure A sync PAD Profile

D Con figure A sync PAD Login

E Configure Asyn c PAD Banner

F Configure I PX Filter Definitions

G Configure Frame Relay Bandwidth Alloc.

R Re t ur n t o P re vi ous M en u

Select:

Figure 4-1 Network Network Selection Menu

[A],[A]

from Main Menu

Files co nfigured from this menu are:

●

Network Defaults (see page 4-2) – node and X.25 level-3 parameters that the

network needs for proper operation of FRX8000s.

●

Network Representation (see page 4-9) – allows creation of a graphic map of

your network.

●

Asy nc PAD par ame te rs (descr ibed in Chap ter 13) – us ed to defin e the opera tio n

of asyn c devices connected to async PAD ports in FR X8000s .

●

IPX Filter Def initions (descri bed in C hapter 15) – us ed to max imize effi ciency

on a WAN network connected via an FR X8000 t o a Novell Netware network.
Filters are applied to IPX traffic as defined by IPX A pplic a tions reco rds.

●

Frame Relay Bandwidth Allocation (describ ed on page 8-2) – optimizes fr ame

r elay band width use, ensur ing that respo nse time- sensi tive traf fic gets access to
the available bandwidth.

Configuring Network Defaults

The Network Defaults file contains one set of parameters whose values apply to all
FRX8000 and Nucleus 74/7500 nodes in the network. This differs from other database
files, which contain individual records for each component ty pe (nodes, LPs, ports,
etc.). This file also differs from other database files in that you cannot in itia liz e
(described in Chapter 3) the file, or add or delete reco rds.

To c onfigure Network Defaults, p res s
(F igure 4-1).

Net work De faults Maintenance

Current Node N umber 10 ABC Node

Database Master Node 10 ABCN ode
A Network Name “Your name here”
B ELP Page Size 62
C Output Leading 0s on ELP N
D Call Actg Timer (Hrs/10) 0
E Call Actg Seg. Size 128
F DN IC 0000
G Line Discnct Timeout (sec) 1
H Modem Discnct Ti meout 0
I I P Network A ddress 100.100.100.0
J IPX WAN Network Add ress 00000001

1 X.25/X.75 Parame ters
2 X.25 Databas e De faults
3 Bandwidth Configurati on

Se le ct:

Figure 4-2 Network Defaults File Display

[A]

, the n

[C]

from the Network Selection Menu

[A],[A],[A],[C]

from Main Menu

Pressing

[1], [2]

X.25 defaults are u se d to maintain c ompatibility am ong n odes; some values
will b e overridden by values in the Port file.

Although i tem 1 is X .25/ X.7 5 Parameters, F R X8000 does not currentl y
support X.75.

4-2 FR X8 000 3 .0 User Gu i de, Rev 02

[3]

, or

displays more parameters, listed in Table 4-1.

When Changes Take Effect

Change s to this file are written immediately to the database. You must then perform

Update Netw ork Defaults

to send the change to all the nodes in the network.

1. Press

[B]

2. W hen asked:

3. Y ou will be asked:

[G]

, t hen

Send update?

from the Main Menu.

, press

Update alarm severity tables?

[Y]

.

Alarms (also called “events,”
and descr ibed i n Cha pt er 21) have as sociated severi ty levels, which can be
changed as described under “Alarm Severity Levels” on page1. If the severity
le vel fil e ha s been c h anged, p res s
(Otherwise , press

4 . Pr ess

[Enter]

[N]

.)

to return to th e Oper ation s Menu.

[Y]

at t he p r o mpt t o send the up date t o a ll no de s .

Perform an on-line update of Network Defaults immediately
after the Network Defaults file is updated.

Co nfiguring Netw ork Paramete rs 4-3

Network Defa ult Pa ramete rs

Explanations of the parameter s f ollow the table. Note that pressing

[Enter]

to a pr ompt selects th e default value.

Table 4-1 Network Default Parameters

P a ra meter Val id V a l ues Defau l t Value

Ne tw o r k Name
ELP Page Size (

Output Leading 0 s on ELP Y/N N
Ca ll Actg Seg. Size (

Ca ll Actg Seg. Size 1–4096 128
DNIC 0–9999 0000

Line Dis connect Timeout (
Modem Di sc onnect Timeout (

IP Network Address
IPX WAN Netwo r k Add r ess 1–fffffffe 00000001

) 10– 99 62

lines

) 0–255 0

10ths/hr

) 0–254 1

sec

) 0–255 0 (

sec

0–20 characters

valid I P addr e ss

X.25/X.75 Parameters

DCE Resta r t Timeout (
DCE Incoming Call TO (

DCE Rese t Timeout (
DCE Clear Timeout (
DTE Resta r t Timeout (
DTE In coming Call TO (
DTE Reset Time out (
DTE Clear T imeout (

DTE Clea r Re- xmit Count 0–10 0
DTE Res et Re-xmit Count 0–10 0
DTE Res tart Re-xmi t Count 0–10 0

)

sec

) 5–360 180

sec

) 5–360 60

sec

) 5–360 60

sec

) 5–360 60

sec

) 5–360 180

sec

)

sec

)

sec

5–360 60

5–360 60
5–360 60

X. 25 Da taba se Defaul ts

Defa ult Low SVC LCN 1–4095 10
Default Packet Size (

Modulus
Defa ult Window Size (

I ncoming Address C heck Y/N N

bytes

packets

)

)

16–4096 128
8 or 128

1–7 2

Bandwidth Configuration Parameters

Pct of Ba ndw. – Grp (1–3) 1–100 1 3
Priority for Group (1–3) 0–9 0

1 Wi ll b e ignored if the protocol is not us ed in the network.
2 The defaults for the timeout parameters are the minimum values recommended by X.25.

Specifying a lower value will generate a caut ionary message.

3 The sum of values for grou ps 1 –3 sh ou ld b e les s than or equal to 100.

NETLI NK

192.0 .0.0

8

in response

disabled

1

1

2

2

2

2

2

2

2

2

)

4-4 FR X8 000 3 .0 User Gu i de, Rev 02

Network Name

will be displayed at the top of th e Main Menu.

ELP Page Size

is the number of lines that will be p rinte d on each page of the event logging printer
( ELP) bef ore a “t op of form ” i s s ent to the print er, s tart ing a new page . Ea ch Node
record (s ee Chapter 5) cont ains the para meter s
which specify an INM/ICP/NMP (each with an attached ELP) to which the node will
send its alarm (event) messages. (L evels 1–4 are described in Chapter 21.)

Output Leading 0s on ELP

ca uses (i f Y) all alarm numbers on prin touts to be three dig its, by inserting one o r two
zeroes at the beginning of each number that is fewer than th ree digits.

Call Actg Ti m er

is the time between reporting sess ions to the Call Accounting file (described in

Ch apter 18) with information on c alls in progress. The file is updated automatic a lly

when a call is cleare d; if this parameter is set to
calls are cleared.

Call Actg Seg. Size

is the numb er of bytes tha t will be reco rded as a segment, to allow data gathering and
billing by some grouping other than packets or bytes. The number of segments is
recor ded in the acco un ting file along with packet and byte totals.

Level 1/2/3/4 Primary/Secondary Node

, th e file will be updated only wh e n

0

,

DNIC

is a Data Network I den tif ic a tion Code, which conforms to CCITT Recommen datio n
X.121. The DNIC occupies digits 2–5 of an X.121 address. If you enter fewer than
four digits in the Network Defaults record, leading zeroes will be added.

If your networ k is a P D N, enter your assigned DNIC. (If not a PDN, this parameter
has no meaning.)

Line Di sconnect Timeout

is a timer that is started on receipt by level 3 of a lost Carrier Detect, Data Set Ready,
or Cle ar to Sen d mess age, and is sto pped wh en a ll lo s t signals ar e reg ained. If the tim er
expir es, the line will be disco nn ec te d and a reset initiated.

Mo dem Disconnect Timeout

is the period between the clearing of the last X.25 call on a V.25bis line and the
hanging up of the mo dem . If a ca ll comes in dur ing this period, the timer will be reset
and not restarted until the last call has been cleared.

IP Network Addr ess

identifies the FRX80 00 interface( s) to the I P networ k . This address must b e ass igned
by the Networ k Information Center (NIC) at Stanford Research Institute. (If the local
network does not use IP, this parameter will be ignored.) The node number of the
FRX8000 containing each interf ace will be ap pen ded to this address for furthe r iden­tificatio n. (IP configuration is described in Chap t er 14.)

IPX WAN Net work Addr ess

identif ies all FRX8000 IPX interfa ces on a Novell n e twork. ( If there is n o No vell
networ k in this configuration, the parameter will be ignored.)

Co nfiguring Netw ork Paramete rs 4-5

X.25/X.75 Parameters

DCE Res tart Timeout

is X.2 5 time r T10, which is started when the logical DCE issues a Restart Indication
(containing cause and diagnostic codes), an d is stopped (an d reset) wh en a Restart
Confirmation or Restart Requ est is received . If th e timer expires, the DCE will iss ue
another R estart Indication and reset the timer. If the timer expires a second time, the
DCE may issue a diag nostic packet.

DCE Incomin g Call TO

is X.25 timer T1 1, w hich is started when the logic al DCE issue s an Incoming Call, and
is stopped (and reset) when a Call R eques t, Cal l Accepted , or C lear Request is
r eceive d. If the tim er expire s, the DC E will iss ue a Clear Indication and reset th e timer.

DCE Res et Ti meou t

is X.2 5 time r T12, which is started when the logical DCE issues a Reset Indication
(containing cause and diag nostic codes ), and is st opped (and reset) when a Reset C on ­firmation or Reset Request is rece ived. If the timer expires, th e DCE will issue another
Reset In dication and reset th e timer. If the timer e xpires a second time, the DCE will
issue a Clear Indication.

DCE Clear T imeout

is X.25 timer T13, which is started when the logical DC E issues a Clear Indication
( c on t ai ni n g c au se and dia g no s t i c co des) , and is st o pped (a n d re s et ) wh e n a Cl ear Co n­f irmation o r Clear R equest is receive d. I f the timer ex pire s, the DCE w ill issu e another
Clear In dicatio n and r eset the timer. If th e tim er expires a second time, the DCE m ay
issue a diag nostic packet.

DTE Restar t Ti meout

is X.25 timer T2 0, w hich is started when the logic al DTE issues a Restar t Re quest, and
is stopped (and reset) when a Restart Confirmation or Rest art Indication is received.
If the timer e xpires, th e DTE should r etransmit the Restart Request.

DTE Incomi ng Call TO

is X.25 timer T2 1, w hich is started when the logic al DTE issues a Call Request packet,
and is stopped (and reset) wh en a Call Connected , Clear Indication, o r Incoming Call
is received. If the timer expires, the DTE should send a Clear Request.

DTE Reset Time out

is X .25 timer T22, which is star ted when the logical DTE issues a Reset Request, and
is stopped (and reset) when a Reset Confirmation or Reset In dication is receiv ed. If
the tim er expires, the DTE should retransmit the Reset Request or (SVC c alls only) a
Clear Re quest.

DTE Clear Time out

is X.25 timer T2 3, which is started when the logical DTE issues a Clear Request, and
is s topped (and re set) when a Cle ar Confirm ation or C lear Indicati on is received. If th e
timer expires, the DTE should retransmit the Clear Request.

DTE Clear Re-xmit Count

is the number of times a Clea r Reque st from the logical DTE will be transmitted. (The
DTE will stop issuing the request on receipt of a Clear Confirmation or Clear Indi-

4-6 FR X8 000 3 .0 User Gu i de, Rev 02

catio n.) If the Clear R etrans mit Count expires, rest art and rec overy p rocedures should
be initiated.

DTE Re set Re -xmit Count

is the number of times a Reset Request from the logical DTE will be transmitted. ( The
DTE will sto p issuing the request on re ceipt of a Reset Con firmation, Reset Indication,
or Clear Request.) If the Reset R etransmit Cou nt expires, restart and reco very proce­dure s should be initiated.

DTE Re st art Re-xmit Count

is the number of times a Restart Request from the logical DTE will be tran sm itte d.
(The DTE will stop issuing the request on receip t of a Resta rt Confirmation or Restart
Indication.) If the Restart Retransmit Count expires, restart and r ecovery procedures
should be initiate d.

X. 25 Datab ase D ef aults

Defa ul t Low SVC LCN

determines the default n umber to be used for the lowest v alue in the Lowest I ncoming/
Two-way /Outgoing Channel parameters in the Port file. LCN 0 is reserved for
network applicat ions. The range of vali d LCNs for a subscriber is also influenced by
the type of subscr iber device.

Default Packet Size

determ ines the default value for the Defau lt Packet Size param e ter in the Port Config­uratio n file.

Mo dulus

is a number for valu es used in X.2 5 level-2 sequenced packets . Th e actual frame num­beri ng is 0–7 for mo dulo 8 a nd 0–127 for modulo 128.

Defa ul t Window Size

determines the default value for the
uratio n file.

Inc om ing A ddr es s Check

is used to verify that th e calling address in an incomin g Call Request packet matches
an address spe cified in the database for the originating port. If set to
incom ing packet has an invalid calling addre ss, the call will be clea red.

Bandwitch Configuration Parameters

Pct of Bandw. - Grp “n”

is used in conjunctio n with
for regulation of trunk traffic and traffic sharing frame relay DLCIs. See “Bandwidth

Alloc ation Groups for Trunks” on page 4-8.

Priority for Group “n”

allo ws setting a priority for traffic within each of the bandwidth allocatio n group s
defin ed in this file; the higher the numbe r, the higher th e priority. T he priority is g e n­erally applied to traffic that exceeds the specified percent of bandwidth.

Priority for Group “n”

Default Window Size

to creat e ba n dw i d t h all o c at i o n g roups

parameter in the Port Co nfig-

and th e

Y

Co nfiguring Netw ork Paramete rs 4-7

Bandwidth Allocation Groups for Trunks

To optimi ze a trunk’s bandwidth us e, up to thre e ba ndwidth a l loc ation gr oups ca n
each be assigned a percentage of trunk bandwidth that will be dedicated to traffic if
necessary. Each I P and IPX network interface, SVC subs criber , and PVC is assigned
to a gr oup.

If traf f ic in one group does not re qu ir e the full allocation , unused bandwidth will b e
available to other groups. Allocation is applied only when availa ble band width is
limited (i.e., packets must be queued before transmis sion) .

Be sure you fully understand the needs of network users before
assigning bandwidth allocation groups; this feature can show
adverse effects if configured incorrectly.

Updating Network Defa ults On Line

Aft er you modify a ny Ne twork D efau l ts par ameter, you must use this operation to
send the change to all the nodes in the network.

1. Press

[B]

2. When asked:
3 . Yo u w i ll be a s ked:

[G]

, then

Send update?

from the Main Menu.

, press

Update alarm severity table?

[Y]

.

Alarms hav e associated severity
levels, which can be changed as described on page 21-1. If the seve rity level file
has been changed, press
erwise, press

4. Press

[Enter]

[N]

to retu rn to the Operations Menu.

.)

[Y]

at the prom pt to s end the upda te to all nodes. (Ot h-

4-8 FR X8 000 3 .0 User Gu i de, Rev 02

Creati ng a N etwor k Rep res entation

Network Representation main tenance o per ation s allow you to create a visual
descr iption of your network, with a geogr aphic outline and n etwor k co mponents. The
information ca n then be retrieved in the Graphics-L evel Status Display (s e e p a ge 19-

10), which shows on-line status for the comp onents you placed into the reco rd.

Inquiry

Maintenance

and

on the Network Re prese ntation fi le can be pe r-

formed only at an INM.

The components in a network display are represented by various icons, shown in

Figure 4-4. To simplify th e display for a large network, you can represent parts of it

as “subnet s” (sub network s), and create a separa t e di splay f or each subnetwo rk. A sub­network ca n contain nodes or other subnetwork s . Yo u ca n have as ma ny as 99
ne t w ork / s ubnet disp l a ys fo r a net w o rk, an d a s ma n y as 25 0 ob j ec ts i n a n y on e di s p l ay.
Each node, however, can exist o nly once in the netwo rk record, so the same node
cannot be in two subnets (unless one is within the other).

To configure a Network Representation r ecord, press

[B]

, t hen

[C]

at the Network
Selection Menu (Figu r e 4-1). The screen will go blank for a few seconds as th e
software enters graphics level. W hen pr ompted, enter:

Network/Subnetwork I D: 1-250

●

. (Default is 1.) (Although this is the sam e range a s

for node I Ds, there is no n ecessary correlation.)

Network/Subnetwork Name

●

F1 Vi ew F 2 Operations F3 En virons

(if a new record): up to 21 character s.

Subnet 1: Datanet 1

11

12

10

13

30

21

20

40

Figure 4- 3 Net work Repre sent at ion Display

[A],[A],[B],[C]

from Main Menu

This example shows an existing record; a new record has no background
or icons.

Co nfiguring Netw ork Paramete rs 4-9

Using the pu l l-down menus (described on page 4-11), configure your display. When
fini she d, press

[F3]

save the record and return to the Ma in Menu .

When Changes Take Effect

Additions or m odifications to this file will be present the next time the configured su b­network is called up in the Grap hics-Level Status Display.

Icons

Symbols used to represent components in displays are shown in Figure 4-4. These
icons are shown as s olid w hite objects on the Network Representation display, but will
be colo r coded according to status and/or outstanding alarms in Stat us Display
operations.

twice (accepting the default

f rom th e Environs Me nu) t o

Return

Cursor Movement

Com pone nts ar e p laced into and se lect ed within the n etwor k by movin g the cur sor to
the desired locations, then pressing
below. (If the numeric ke ypad a t the ri ght s ide of t he key board is used,
must b e O ff.)

FRX8000 Switch

FRX8000 with
attached NMP

N7400 DPPM N7500 DPPM

[], [], [], []

] = up and left.

[Home

= down a nd left .

[End]

FRX8000 or N7500
ICP/INM

N7400 with
attached NMP

F igure 4-4 St atus D isplay Ic ons

. Curs or movem ent is controlled as listed

[Enter]

= appr opriate direction.

N7500 with
attached NMP

Subnetwork

[Num Lock]

[PgUp]
[PgDn]

= on t he numeric keypad , c ontr ol s move ment by the cur s or when the above

[5]

keys are struck while movin g an object . Pr essin g
greater or lesser distance (depending on the current setting) when the o ther keys
are pressed.

= in an existing r ecor d only - to the next object, sequentia lly by ID n umber ,

[Tab]

ending at the subnet ID/name, then returning to lowest-number e d object.

(tilde) = in an existing r ec ord only - sequentially in rever se order of that

[~]

described for

4-10 FR X8 000 3 .0 User Gu i de, Rev 02

= up and right.
= down and right.

.

[Tab]

causes the cur sor to move a

[5]

Pull-down Menus

Each selection across the top of a screen has an associated p ull-down m enu that
appears when the selection is chosen. When a pu ll-d own menu appears, the default
select ion appears in whi te te xt on a black backgr ound. Ot her ite ms are in black tex t o n
a white background , unless they are not valid at th e curren t level or point, in which
case they ap pear in ligh t g ray text on a white bac kg round. The defaul t c an be selected
by pressing
a second time.

The pull-down menus for Network Representatio n maintenance are de scr ibed below.
No te that each menu has an entry:
allo ws you to make another selection. Pr essing

[F1] View

[Enter]

, or by pr e ss ing the s ame

[F“n ”]

key you struck (to display the menu)

Cancel

. Sele cting this ex its the current men u an d

[Esc]

will d o the same thing.

Ad d Re c
Delete Rec

network ID:
Next Rec

file, if one exists. If ther e is no next record, No next record is dis played, and pr essing
an y ke y r et ur ns you to t h e

Co py Re c
Cancel

[F2] Operations

Ad d Nod e

– leaves this menu and retur ns you to the choices at the top of the screen.

resentation. When prompted, enter a n ode ID; the node will be displayed at the cursor
location.

Ad d S ubn e t

resentatio n, unle ss a component of that subnetwork is already in this r epre sentation.

Move

– allows y ou to re locate compone nts on the display. Position the cursor over a
component and select
cursor to the desired location and press
and its color will return to white.

Delete

– allows y ou to d ele te any object from the displa y. Position the curso r over the
object and select
tation record, not from your database.)

– (default) allows you to add a new network/subnet record.

– allows y ou to delete the curre nt recor d and r eturn to the

pr ompt. F rom her e, ent er a new ID , or press

[Esc]

to e xit graphics level.

Network/Sub-

– saves the curr ent record, then display s the next netwo rk/ subnetwork in the

Network/Subnetwork ID:

prompt. From here, enter a new ID.

– cop ies the current reco rd to a ne w ID.

– (d e fault ) a ll ows y ou t o add any node i n yo ur dat abase t o you r n e tw or k r ep -

– al l ows you to a d d any subn et w or k i n yo ur d at a b a se to t h e Netw ork Rep-

Move

. The compo nent's colo r will change to red. Move the

[Enter]

. The component will be repositio ned

Delete

. ( T he object will be d e le ted only fr om the Network R epr esen-

Background

each of the fifty United States, several countries, the world, and several regions,
such as:

usa
usastate
usacon
usawest
nmidwest
smidwest
ns_america
w_europe
nordic

Co nfiguring Netw ork Paramete rs 4-11

– displays a list of geographic names. Available backgrounds include

United States, without state borders
Un ited Sta t es, wit h state bord ers
48 conti guous stat es, witho ut state border s
WA, OR, CA, NV
MT, WY, ND, SD, NE, MN, IA, WS
WY, NE, UT, CO, KS, MO, NM, OK, AK, TX, LA, MS
Nort h and South America
Western E urop e
Scandanavia, Denmar k

scandina
low_coun
fe_asia
me_asia

Scandinavia (similar to nordic)
B elgiu m, Nether land s, Luxembour g
Far East (shown in Figure 4-3)
Middle Eas t

Subnet Name
Cancel

[F3] Environs

– is not valid her e .

Help
Return

Operations Menu.

– wo rks the sa me as

Exit
Cancel

– allows you to change the name of the current subnetwork.

– leaves this menu and returns you to the choices at the to p of the screen .

– (default) exits Gr aph ics le vel and returns you to the Network Represen tation s

.

Return

– leaves this menu and retu r ns you to the choices at the top of the screen.

4-12 FR X8 000 3 .0 User Gu i de, Rev 02

Chapter 5

Configuring Node Records

The Node file contains the lo cations, node types, alternate nodes (for receiving
networ k data), and alarm routing informatio n for every n od e in the network.

Nodes Selection Menu

A Con figure Node

B Configure SNMP Parameter s

R Re t ur n to P re vi ous Me nu

Select:

Figure 5-1 Nodes Selection Menu

[A],[B]

from Main Menu

No de-w i de SNMP p ara meters, also acces sed from th is menu, are des cribed
in Chapter 16.

Be careful; pressing

[Enter]

w hen it is not req uired may cause th e

next prompt to automatically select the default choice.

Configuring Node Records

A Node record must be created for each FRX8000 Switch, ICP, an d INM, as well as
every N7400 and N 7500, i n t he ne twork. To confi gure a record, pres s
from the Nodes Selection Menu (Fi gure 5- 1). When pr ompt ed, ente r:

No de ID : 1–250

●

assign e d during software installa tion.

●

An y other requested information, noting the values in Table 5-1. (Press
at a prompt to accept the default.)

The resu lting display will dep end on whether the node is an FRX8000 (Figu re 5-2) or
N700 0 (74 / 75 00) (Fi gure 5 - 3 ).

Node Maintenance

* Node ID 100

A Description ABC
B Al ternate NM P Node 10 DEF
C 7000 Node N
D Node Type 1 DOS n ode
E 2n d Alternate NMP Node 11 GHI
F Le vel 1 Primary Node 10 DEF
G Le ve l 1 S econdary Node 11 GHI
H Le ve l 2 P rimary Node 10 D EF
I Le vel 2 S econdary Nod e 11 GH I
J Level 3 P rimary Node 10 D EF
K Le ve l 3 S econdary Node 11 GHI
L Leve l 4 P rimary Node 10 D EF
M Level 4 S econdary Node 11 GHI

1 8000 Node Info

Se l ect:

. (De fault is th e “loc al” no de.) Eac h nod e has a u nique ID th at was

[A]

, then

[Enter]

[C]

F igure 5-2 FR X8000 Node Record

[A],[B],[A],[C]

Item E is displayed only if

No de Ty pe

is 1.

The text fo llowin g each node’ s ID at items

Description

T he pa rameters displ aye d by pre ssing

5-2 FR X8 000 3 .0 User Gu i de, Rev 02

in that node’s Node r ecord.

[1]

from Main Menu

B

E–M

and

is the

are liste d in Table 5-1.

Node Maintenance

* Node ID 100

A Descrip tion ABC
B Alternate NMP Node 10 DEF
C 7000 Node? Y
D No de T y pe 1 DOS node
E 2 nd Al ter na te NM P Node 11 GH I
F Level 1 Primary Nod e 10 DEF
G Le vel 1 Secondary Node 11 GHI
H Le vel 2 Primary Node 10 DEF
I Level 2 Secondary Node 11 GHI
J Level 3 Primary Node 10 DEF
K Le vel 3 Secondary Node 11 GHI
L Level 4 Primary Node 10 D EF
M Level 4 Secondary Node 11 GHI
N Asy n c Term i na l Co nt r o l N
O Dos Exten ded Mode? N

Select:

Figure 5-3 N7000 Node Record

[A],[B],[A],[C]

from Main Menu

When Changes Take Effect

When you add a No de r ecor d, the change will be written to the database when you
enter the final parameter value. When you modify a parameter in an existing record,
the change will be written to the d a ta base im mediately.

Change s to the following parameter s can be implemente d without disrupting node
operation:

●

Alternate NMP Node

●

Level “n” Primary/Secondary Node

On Li ne” on page 4.

A change to any other parameter will take effect after th e next IPL of the configured
nod e, with the exception of
necessary changes have been made at the node to add/remove sys tem board memory
an d U N IX a n d FR X 8 000 sof twar e) by p erform i ng a

Download Operations

Item E is displayed only if
Item

is displayed on ly if

N

Item

is displayed only if

O

Node Type

No de Ty p

Node Type

is 1 or 3.

e is 0 or 1.

is 1.

T he text fol l ow i ng each node’ s ID at items B and
Descriptio n in that node’s Node record.

, described in the explanations following T abl e 5- 1 .

, described under “Changing Alarm Routing

No de Ty pe

(

[B], [B], [D], [D]

, whi ch must be impl emen ted (assumi ng the

Co nf igu ra t ion Updat e

from the Main Menu—described on page 18-6).

E–M

is the

in

Bo ot Disk

Configuring Node Records 5-3

Node De faults Paramete rs

The following table lists all possible param eters on the first two screens.
d ependi ng on t h e val ues configure d f o r s ome parame te rs, other parameters
might not be displayed.

Parameter Valid Values Default V alue

Description
Alternate NMP Node 1–250

7000 Node Y/N N
Node Type

2nd Alternate NMP Node 1–250
Level “n” Primar y Node 1–250
Leve l “n” Secondary Node 1–250

FR X8 000- s pe c i fic Pa ra me t e rs

IP Gateway? Y/N Y
RI P Vers io n 1, 2 1

IPX Router Name
IPX Router Network Address 1–fffffffe 00000001

IPX Gap Time 0–255
Connection Limit 0–3 0

SNA LLC2 Virtua l LA N ID 0–fff 000

N7000-specific Parameters

Async Termina l Control Y/N N
DOS Extended Mode Y/N N

If this value is changed, you must also change the LP type in all Line Processor records

1

for this node, as well as any Logical Trunk port records. (See explanation.)

If you try t o change the

2

activation key. (See explanation.)
Must be a value other than

3

Table 5-1 Node Parameters

0–30 characters none

0–4

N7000:
FRX8000

1–48 characters

C onnec tion Limit

000

if LLC2 will run in the node.

: 0, 1 , 4 0

(

55 ms units

)

, you will be asked t o enter a serial number and

local node

1

(

DO S n od e w/ NM P
local node
local node
local node

OL8000_

2

(

256

3

2

)

(

node ID

)

)

Description

is text that will f ollow the node number in various config uration record displays (a s
shown after the node numbers at items B and E–M

Alternate NMP Node

identifies an ICP, I NM, or N7000 NMP (via its attached node) th at will act as follo ws:

●

If the local nod e is an FRX8000 Switch o r N74/7500 without a locally attache d
NMP, the alternate NMP Node will provi de the local node with n etwork
defaults and other network data.

●

If the local ( FRX8 000 or N7 4/7500) node has a locally attach ed NMP, or is an
ICP o r INM, the alternate NMP Node will take ove r the local node’s man­agement functi ons (re ceivin g alar ms, upd ating param eters, etc.) if the lo cal no de
loses conta c t with the network.

5-4 FR X8 000 3 .0 User Gu i de, Rev 02

in Fi gure 5-2).

You can change

Alternate NMP No de

on li ne by pe rforming

Change Alternate Node

:

1. Press

2. Enter the ID of the node whose alternate you want to ch ange.

3. E nter the ID of the n e w alternate node.

4. Press

7000 Node

must be Y if t he node i s an N 7400 or N7 500, and N if FRX8000. Before changing a
Node record f rom N74/7500 t o FRX 8000, c ontact your Cabl etron re presen tative to
discuss re quired hardware upgrade s.

Afte r changing the value for
cessor r ecords for all LPs in the node, since the software differentiates between N7000
and FRX8000 RLPs. N7000 RLPs are type

I f any ports in the node are configured as
physical X.25 (FRX8000), thes e Port r ecords mu st al so be chan ged. The two are
equivalent, but are created diff erently. The lo gi cal trunk is defin ed entirely in one
PDN P ort rec ord i n t he N 7000, but in two record s —L ogical Trunk Port and unde r­lying physical X.25 Port—in the FRX8000.

, t hen

[B]

once to return to the Node Oper ations Menu or three tim es to re turn to

[F3]

[B]

, then

fr om the Main Menu.

[A]

the Main Menu.

7000 Node

, you must change the

, and FRX8000 RLPs are type 7.

6

PDN Trunk

(N7000) or

LP Ty pe

in Line Pro-

Lo gica l Trunk

Be sure to change the necessary records or the affected LPs and
ports will not operate correctly.

on

Node Type

depends on the settin g for

7000 Node

= N7400 with at tached NMP0 = FRX 8000 Switch with attac hed NMP

0

= N7400 with no NMP

1

= N7500 wi th attached NMP4 = FRX8000 ICP or INM

2

= N7500 with no NMP

3

= N7500-ICP or N7500-INM

4

2nd Al te rn ate NMP Node

Y 7000 Node

=

is the node that will take over if th e Altern ate NMP Node goes down. (This option
exists only for n od e types
INM with the lowest node ID o f all opera tiona l nodes in the network will take over.

Level “n” Primary Node

is an ICP, INM, or NMP that will receive alarm messages with severity level “n ”
(1–4) (see page 21-1) f rom this node. Ala rms are routed to printers as follows:

●

Node type 0 or

●

Node type 1 or 3 sends its alarms to its

●

Node type

●

Alar ms from an y node type ar e also printed at one or two ICPs , INMs, or NMPs

4

specified as

7000 Node

and 3.) If th e 2nd alternate node also goes down, the ICP/

1

sends its alarms to the printer at the attached NMP.

2

:

N

=

= FRX8000 Switch

1

Alternate NMP Node

sends its alarms to its printer (if present).

Level “n” Primary Node

and

Level “n” Secondary Node

.

.

Configuring Node Records 5-5

Level “n” Sec ondary Node

is another I CP/INM that (in addition to the “local” and Primar y nodes) will receive
alarm m essages with severity level “n” (1–4) fro m th is node.

FRX 8000 - specific Para met ers

IP Gat eway?

determines wheth er the node will act as a network gatewa y and try to forward IP
packets that have destinations unknown to the node.

RIP Versio n

specifies the version of RIP (Routing Inf ormatio n Proto c ol) that will be used, if that
protocol is used on this node.

IPX Router Name

is simply an identifier fo r the IPX network. It must be un ique within the network.

IPX Router Net work Address

is the IPX ne twork address for th e virtual L AN within the FRX8000.

IPX Gap Time

is the minimum d e la y, in 55-millis econd un its, betwee n consecutiv e RIP and SAP
(Service Advertising Protoco l) trans mis sions. This parameter prov ides compatibility
with older No vel l s erve rs.

Connection Limit

is the max imum number of simultaneo us logical connections su pp orted o n this node:

= 256

0

1

The va lid connectio n limits depend on th e platform on wh ic h the no de resi des and/or
which connection upgrade option has been purchased for this node.

●

A Model 2 can support 512 or 1024 connections with a purchased upgrade.

●

A R ac kmount node c an support 512 conne ct i ons by s pec if ying that value, then
entering a serial number and activation key (both supplied with the node). The
node can also support 1024 or 2048 connections with a purchased upgrade kit.

SNA LLC2 Virtual LAN I D

is used internally by th e FRX8000 to identif y a v irtual bridge that connects the LLC2
function to LAN interfaces. This ID is normally assigned by a system administrator.

N 7000-sp ecific P arame t ers

Async Termi nal Control

allows a VT1 00-type termin al to be connected to a C OM1 port on an N7400, and to
act as an operator console for the node.

DOS Extended Mode

allows use of an N7400 DPPM node 's e xpande d memory (2Mb must be insta lled) to
allow up to 264 simultan e ous connections on the node. (Witho ut this f eature, the
ma ximum is 80.)

= 512

= 1024

2

= 2048

3

5-6 FR X8 000 3 .0 User Gu i de, Rev 02

This function requires entry of a s e rial number and activatio n key, which will b e pro­vided by Cabletron on request. If it is desired that re-entry be required to re-enable the
parameter , the No de recor d must be deleted and a new one created, or the reco r d can
be copied to another record, then copied again from that record to the first one.

If a Nod e r ecord with DOS Exten ded m ode enabled is copied to another recor d us ing
the
record us ing

ke y, DOS Extend ed mode will be disabled in the new record. (Moving the

[F5]

will le ave DOS Extend ed mode enabled. )

[F6]

Configuring Node Records 5-7

Chapter 6

Configuring LPs and LAN Cards

Line Processors (LPs, RLPs) an d LAN cards (Ethernet and Token R ing) are th e com­munications cards i n FRX8000 and N74/7500 nodes, providing I/O for subscribers,
and tru nks to other nodes . LPs currently supported depe nd on the node type:

FRX8000 RL P

Node Ty pe (s )
FRX8000 FRX8000 RLP
N7400, 7500 486 N7000 RLP
N7400, 7500 286, 386 N 7000 RLP, AST (“ S tandard” ) LP, T1 LP, E1 LP

The maximum number of LPs a node can contain depends on the platform used and
any other card s present in the node. L Ps are numbered, 0–7, based on switch settings.
Eac h LP (regardless of type) in a nod e mu st have a unique n umber within its node.

This chapter d escribes configuration of L Ps and LAN cards, as well as channel map
records for T1/E1 LPs.

The FRX8 000 RLP is a mother ca rd with o ne or two attach ed four-p ort Line Inter face
Cards (LICs). The RLP supports all FRX8000 port types. Port I/O inter faces available
are RS -232-C /V.28, R S- 449/V. 36 , RS-5 30, X.2 1, and V.35. T he interfaces suppo rted
depend on the LIC(s)-all four ports on an LIC are the same, but two different LIC
types can reside on the same RLP, and some LIC types support more than o ne
interface (thr ough I/O box and cables ).

Supported LP(s)

RLP

8

Off

1

On

LP Switch

8 76 54 3 2 1
0 OnOnOffOnOffOnOnOn
1 OnOnOff
2OnOffOn
3 On Off Off
4 Off On On
5 Off On Off
6 Off Off On
7 Off Off Off

LIC 1

LIC 2

RLP Cable

I/O Box

6

4

2

0

7

5

3

1

Figu re 6-1 FRX8000 RLP

6-2 FR X8 000 3 .0 User Gu i de, Rev 02

To configure RLP parameters, pres s
(or

[A], [C], [C]

fr om t he M ai n Me nu). Whe n prompted, e nter:

[C], [C]

from the Configuration Se le ction Menu

●

No de ID

●

LP ID: 0–7

(t he node conta ini ng th e L P ) :

(Default is the “local” node).

1–250.

(default is 0). This is d e termined by switches 1–3 on the RLP’s

dipswitch.)

●

Any o ther requested informatio n, noting the values in T a bl e 5-1. (Press
at a pr om pt to s pe c i fy t he de f a ul t. )

Lin e Pro c es sor M a i nt e na nc e

* Node ID 10
*LP ID 1

LP Type 7 RLP
B Line Interface Car d 1: 1 RS--232
C Li ne In terface Card 2: 5 E1
D RLP Memory in Mgb 4
E Protocol #1: 1 X.25
F Protocol #2: 3 FRL
G Protocol #3: 4 S DLC
H Protocol #4: 7 IP
I Pr otocol #5: 11 Trunk

3 E1 LIC2 Parameters
4 E1 LIC2 Use Bits:

Select:

[Enter]

options 3 and 4 are displ ayed only if

E1

optio ns will be displayed as menu items

When Changes Take Effect

When you add a new LP re c ord, the ch a nge will be writt en to the database as soon as
you enter the final p arameter value. When you modify an existing record, the change
will be written to the database immedi ately.

The change will become effect ive at the RLP in one o f the followin g ways:

●

A change to an RLP in an ICP or INM is immediately ef fective when the
database record is changed.

●

A change to an RLP in an FRX8000 Switch can be implemented by performing
a

Configuration Update ([B], [B], [D], [A]

taining the LP.

Figure 6-2 FRX8000 RLP C onfigurat ion Menu

[A],[C],[C]

LIC2

and 2.

1

from Main Menu

is E1. If

fr om the Main Menu) to the no de con-

is E1, simila r

LIC1

Confi guring LPs and LAN C ards 6-3

FRX8000 RLP Parameters

P a ra meter Val id V a l ues Defau l t Value

LP Type 7 7
Line Interface Card 2 0–5 4

RLP Availab le Memory

Pro toc ol 1–5 0–12

E1-specific Parameters

Coding 33
Framing 22
Line Serv i ce 00
Line Bu ild Out 66
Clocking 0

CRC-4 Dis abled NN
Channel Signalling 00
National Use Bit “n” (1–5 ) Y/N

Internation al Use bit “n” (0,1)

An FRX8000 RLP always has 4MB.

1

One protocol on each RLP must be X.25 (type 1).

2

Table 6-1 FRX8000 RLP Parameters

(MB)

2

Master

On/Off

(

On/Off

(

1

, 1

Slave

)

(

)

)
)

4, 8

(

1

Y/N

HS RS-232

(

4
0 (

none

HDB3

(

G.704

(

Full

(

)

G.703

(

0

Common

(

N
Y

)

)

)

)

)

)

LP Type

Although press ing
FRX8000 node .

Line Inter fa ce Card 1

contains physical ports 0–3 for the RLP.

0

= not installe d

1

= RS-232 (used only on N7000 RLPs)

2

= RS-422 (supports RS-449/V.36, RS-530, or X.21 via I/O box and cable)

3

= V .35

4

= High-speed RS-232 (supports RS-232C/V.28 via I/O box and cable)

5

= E1

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 port records as needed.

Line Inter fa ce Card 2

contain the p hys ic al po rts 4-7 of th e LP. T he choices are the s ame as for Lin e Int erface
Card 1.

RLP Available Memo r y

is the amount of on-boa rd mem ory.

[?]

displa ys a r ange of

1–7

, only 7 (

RLP

) i s suppor t ed i n an

6-4 FR X8 000 3 .0 User Gu i de, Rev 02

Protocol 1–5

specif ies the protocols tha t will be loaded onto the L P so ftwar e on boot-up.

= N one

0

= A sy n c

3

= IP

7

= TRNK (T r unk)

11

Note these requiremen ts and recommendations:

●

Each RLP must have X.25 configured.

●

RIP is valid o nly if IP is already configured o n the RLP.

●

SNMP will not wo rk unless IP is also configured in the node. IP can be, but does
n ot have to be , on the s a me RLP.

●

IP, IPX, and SNMP should not be configured on more than one R LP each. (All
three can be configured on the same or di fferent RLPs.)

●

To configure a protocol on a port, the protocol must first be configured on the
L P cont aining the por t.

E1-specific Parameters

Coding

is the lin e coding technique used to carr y clock signals.

Framing

is the frame fo rmat. G.704 is a CEPT standard, with a s et v alue.

= X. 25

1

= SDL C

4

= SNM P

8

= IP X

12

= Frame Relay

2

= BSCI (BSC Interactive)

5

= RIP

9

Line Service

spec ifies (as configured) that the RLP will use all of the DS0 channels on the E1 line.

Line Bui ld Out

is the distance from the LP to the extern al T1/E1 device. G.703 is a CEPT standard,
with a set value.

Clock ing

is the clocking mode in which the LP ru ns: 0 = Ma ste r, 1 = Slave

CRC - 4 Di sab l ed

disabl es (a s configure d) t he ge neration of CRC -4 (polyn omi al X4 + X + 1).

Channel Signalling

is the mode of the CEPT inter face.

National Use Bit “n”

is the setting of the n a tiona l use bits in the non-frame align ment signal. National use
bits 1-5 correspond to data bits 4-8 in the n on-frame alignment signal. National use
bits are reserve d for use within a country. If th e signal will cross an international
border, the national use bits should be

International Use Bit 0

is the setting of bit 0, which is tra ns mitted as the most significant bit of the frame
alig nment signal when CRC-4 is disabled.

Off

.

Confi guring LPs and LAN C ards 6-5

International Use Bit 1

N7000 RLP

is the setting of bit 1, which is tran smitted as the most significant bit of the non- frame
alignment signal when CR C-4 is dis abled.

Th e N7 000 (N 7400/7500) RL P is support ed only in N7400 and N 7500
nodes .

The N7 00 0 R LP is nearly identical to the FRX8000 RLP, shown in F igure 5-1.
To configure an LP record, press

[A], [C], [C]

●

●

from the Main Menu). When prompted , enter:

No de ID
LP ID: 0–7

( the node c onta i ning the L P) :

(default is 0.), as d e t ermine d by sw i tc h e s 1– 3 on t he R LP ’ s d i ps w i tc h.

at the L ine P roces sor Configu ration M enu ( or

[C]

. (Def ault is the “lo cal” no de).

1–250

(See T abl e 5-1 .)

●

Any other requested information, noting the values in T a ble 5- 2. (Pres s
at a prompt to specify the default.)

Li ne Proc es sor Mainten ance

* Node ID 10
*LP ID 1

A LP Type 6 N74/7500 R LP
B Line I nterface Car d 1: 1 RS-232
C Line Inter face C ard 2: 1 RS -232

Select:

[Enter]

6-6 FR X8 000 3 .0 User Gu i de, Rev 02

F igure 6-3 N7400/7500 R L P Configuration Recor d

[A],[C],[C]

from Main Menu

When Changes Take Effect

When you add a new LP re c ord, the ch a nge will be writt en to the database as soon as
you enter the final p arameter value. When you modify an existing record, the change
will be written to the database immedi ately.

The change will become effe ctive at the LP in one of the following ways:

●

A change to an RLP in an ICP, INM, or NMP no de is immediately effective
when the database recor d is changed.

●

A change to LP 0–3 in a DPPM node, can be implemented by performin g a

Configuration Update

taining the LP.

Be sure to perform the update to a DP PM node be for e the node
undergoes a re-I PL.

●

A change to LP 4– 7 in a DPPM nod e will take effect at the next IPL of the no de
containin g the LP.

N 7000 RLP Para mete rs

[B], [B], [D], [A]

(

from the Main Menu) to th e node con-

Parameter Valid Values Default Value

LP Ty pe 6 6
Line Interface Card 1, 2 0–3

LP Type

Although pressing

3

= AST Ca rd

Line Int erface Card 1

contains physical ports 0–3 for the R LP:

0

= not installed

1

= RS-232 (supports RS-232C /V.28 through I/O box and cable)

2

= RS -422 (support s RS-4 49/V.36, RS-530, or X.21 t hrough I/O box a nd ca ble)

3

= V. 35

Line Int erface Card 2

contains physical ports 4–7 of th e LP. The choices are the same as for Line Interface
Card 1 .

Table 6-2 N7000 RLP Parameters

[?]

for help displays a range of

4

= T1/E 1

6

= RLP-7000 Node

1 (

1–6

, these are the suppor ted types:

RS-232

)

Confi guring LPs and LAN C ards 6-7

N7000 St andard LP

The AST LP p rovides four serial ports via a four-port splitter cable. A n additional four
async p orts can b e added to an y LP via a daughter card and async splitter cable.

Th e N7 000 S tandard ( AST) LP is supported only in N7400 and N 7500
286- and 386-bas ed nodes. (The 486 does not support thes e LP t ypes.)

T o con fig ure a re cor d for a stan dar d LP, pr ess

No de ID

●

LP ID: 0–7

●

[A], [C], [C]

fr om t he M ai n Me nu). Whe n prompted, e nter:

( the node c onta i ning the L P) :

(default is 0), as determined b y jump er and switch s etting s on the car d.

Menu (or

[C]

at the Line P rocesso r Configu ration

1–250

. (Def ault is the “lo cal” no de).

(See N7 000 user do cumentatio n if neces sary. )

●

An y other requested information, noting the values in Table 5-3. (Press
at a prompt to specify the default.)

Line Proc essor M aintenance

* Node ID 10nsn10
*LP ID 1

A LP Type 3 Stan dard
B Big Packet Supported Y

Select:

[Enter]

F igure 6-4 N7400/7500 “St andar d” LP Confi gurati on Re cord

6-8 FR X8 000 3 .0 User Gu i de, Rev 02

[A],[C],[C]

from Main Menu

When Changes Take Effect

When you add a new LP re c ord, the ch a nge will be writt en to the database as soon as
you enter the final p arameter value. When you modify an existing record, the change
will be written to the database immedi ately.

The change will become effe ctive at the LP in one of the following ways:

●

A ch ange to an LP i n an I CP, I NM, or NMP no de is i mmediate ly eff ective wh en
th e dat abase record is chan ged.

●

A change to LP 0–3 in a DPPM node, can be implemented by performin g a

Configuration Update ([B], [B], [D], [A]

taining the LP.

Be sure to perform the update to a DP PM node be for e the node
undergoes a re-I PL.

●

A change to LP 4– 7 in a DPPM nod e will take effect at the next IPL of the no de
containin g the LP.

Standard LP Pa ramet ers

from the Main Menu) to th e node con-

Parameter Valid Values Default Value

LP Ty pe 3 (
Bi g Packet Supported Y/ N Y

LP Type

Although pressing

3

= AST Ca rd

Big Pac ket S uppor ted

determ ines whether this LP will support packe t sizes up to 4 096 b ytes. I f this is not
neces sary, se l ect
some LP func tions .

Table 6-3 N7400/7500 “Standard” LP Parameter

not valid here

[?]

for help displays a range of

4

= T1/E 1

N

, which limits packet size to 512 bytes but incr eases eff iciency of

6

= RLP-7000 Node

1–6

, these are the suppor ted types:

)

Confi guring LPs and LAN C ards 6-9

N7000 T1 LP

The T1 LP is supported only in N7400 and N7500 286- and 386-based
nodes . (The 486 does not s upport these LP type s.).

Press

[C]

at the Line Processor Configuration Menu (or

[A], [C], [C]

M enu). When pro mpted, en te r:

No de ID

●

LP ID: 0–7

●

( the node c onta i ning the L P) :

(de fault is 0.) , as determined by switch settings on the card. (See

1–250

. (Def ault is the “lo cal” no de).

N7000 user doc umentation. )

●

An y other requested information, noting the values in Table 5-4. (Press
at a prompt to specify the default.)

Lin e Pro c es sor M a i nt e na nc e

* Node ID 10nsn10
*LP ID 1

A LP Type 4 N7400/7500 T1/E1 LP
B Mod el Type 1 Dsx-1
CCoding 2
D F rami ng 1
E L in e S e rv i c e 0
F Line Buil d Out 1 0-133 ft.

Unit Type 0 Primary
H Clocking 1 S la ve
I Expansion LP Attached Y

O Expansion LP Numbers

Select:

from t h e Main

[Enter]

6-10 FR X8 000 3 .0 User Gu i de, Rev 02

Figure 6- 5 T1 DSX-1 LP Configuration Re cord

[A],[C],[C]

Item F is not displa yed for a DSU LP.

from Main Menu

When Changes Take Effect

When you add a new LP re c ord, the ch a nge will be writt en to the database as soon as
you enter the final p arameter value. When you modify an existing record, the change
will be written to the database immedi ately.

The change will become effe ctive at the LP in one of the following ways:

●

A ch ange to an LP i n an I CP, I NM, or NMP no de is i mmediate ly eff ective wh en
th e dat abase record is chan ged.

●

A change to LP 0–3 in a DPPM node, can be implemented by performin g a

Configuration Update

taining the LP.

Be sure to perform the update to a DP PM node be for e the node
undergoes a re-I PL.

●

A change to LP 4– 7 in a DPPM nod e will take effect at the next IPL of the no de
containin g the LP.

T1 LP Parameters

[B], [B], [D], [A]

(

from the Main Menu) to th e node con-

LP Type

Although pressing

Mo del Type

Although pressing

Table 6-4 N74/7500 T1 LP Parameters

Parameter Valid Values Default Value

LP Ty pe 4
M odel T ype 0

Coding 0–2 2
Fr aming 0–1 1
Line Service 0–1 0
Line Build Out 1–5 1

Cloc king

Expansion LP A tta ched Y/N N

[?]

for help displays a range of

3

= AST Card4 = T1/E 1

[?]

for help displays a range of

0

= CSU

1

= DSX-1

CSU: 0
DSX-1:

6

= RLP-7000 Node

(CSU),

1

(DSX-1)

1

1–6

, the supported types are:

0–3

, th e valid types are:

(not va li d he r e)

0

0

(if CSU),

1

(if DSX-1)

Confi guring LPs and LAN C ards 6-11

Coding

is the lin e coding technique used to carry clock signals:

= AMI /Z CS (Al tern ate Mark Inversio n with Zero Code Substitu tion )

0

= AMI /No ZCS (A lterna te Mark Inversion with no Zero Code Substitu tion)

1

= B8ZS (Bipola r Eight Zero Code Substi tutio n)

2

Framing

is the frame format: 0 = D4, 1 = ESF (E xtend e d Su per frame Format)

Line Service

specifies whether the LP will use all (Fu ll) or some (Fract ional) of the DS0 channels
on a T1 lin e:

Line Build Out

is the di stance from the LP to the external T1 device:

= Full,

0

= Frac tiona l

1

Unit Type

Clocking

N7000 E1 LP

= 0-133 ft.

1

= 400-533 ft.

4

= Pri mary , 1 = Secondary

0

is the clocking mode in which the LP runs:

= 134-266 ft.

2

= 534-655 ft.

5

= 267-399 ft.

3

= Ma ste r, 1 = Slave

0

The E1 LP is supported only in N7400 and N7500 286- and 386-based
nodes . (The 486 does not s upport these LP type s.)

Press

at the Line Processor Configuration Menu (or

[C]

[A], [C], [C]

M enu). When pro mpted, en te r:

●

No de ID

●

LP ID: 0–7

( the node c onta i ning the L P) :

. (Def ault is the “lo cal” no de).

1–250

(default is 0.) , as determined by switch settings on the card. (See

N7000 user doc umentation if necessary. )

●

Any other requested information, noting the values in T a ble 5- 5. (Pres s
at a prompt to specify the default.)

from t h e Main

[Enter]

6-12 FR X8 000 3 .0 User Gu i de, Rev 02

Lin e Pro c es sor M a i nt e na nc e

* Node ID 10nsn10
*LP ID 1

A LP Type 4 N7400/7500 T1/E1 LP
B Mod el Typ e 2 E-1

Coding 3
Frami ng 2

E Lin e Se rv i c e 0

Line Build Out 6

Unit Type 0
H Clocking 0
I Expansion LP Attached Y

O Exp ansion LP Number s
1 S ig n a ling Pa rameters

Select:

F igure 6-6 E1 LP Conf igurat ion Record

[A],[C],[C]

from Main Menu

Pressing

will display the signaling parameters , all of which are lis te d in

[1]

T able 5-5. So me entries will or will not appear on that screen, depending on values

selected for other parameters.

When Changes Take Effect

When you add a new LP re c ord, the ch a nge will be writt en to the database as soon as
you enter the final p arameter value. When you modify an existing record, the change
will be written to the database immedi ately.

The change will become effe ctive at the LP in one of the following ways:

A ch ange to an LP i n an I CP, I NM, or NMP no de is i mmediate ly eff ective wh en

●

th e dat abase record is chan ged.
A change to LP 0–3 in a DPPM node, can be implemented by performin g a

●

Configuration Update ([B], [B], [D], [A]

taining the LP.

Be sure to perform the update to a DP PM node be for e the node
undergoes a re-I PL.

A change to LP 4– 7 in a DPPM nod e will take effect at the next IPL of the no de

●

containin g the LP.

from the Main Menu) to th e node con-

Confi guring LPs and LAN C ards 6-13

E1 LP Parameters

Tabl e 6-5 E 1 L P Parameter s

P a ra meter Val id V a l ues Defau l t Value

LP Type 4
Model Type 2
Coding 3 3
Framing 2 2

Line Serv i ce 0–1 0
Line Bu ild Out 6 6
Unit Type 0 0

Clocking 0–1 0

Expansion LP Attached Y/N N
LP “n” Y/N N

National Use Bit “n” Y/N
CRC-4 Dis abled ? Y/N N

Internation al Use bit "n"
Channel Signalling 0–1 0

X1,2,3 Bits Y/N (
A,B,C,D Bi ts Y/N (

Displayed only if CRC-4 is disabled.

1

1

Y/N (

On/Off

(

)

)N (

On/Off

)N (

On/Off

)N (

On/Off

not valid here
not valid here

HDB3

(

)

G.704

(

)

G.703

(

)

Primary

(

N

Off

(

Off

Off
Off

)

)

)

)
)

LP Type

Although press ing

3

= AST Card

Model Type

Although press ing

Coding

is the lin e coding technique used to carry clock signals.

Framing

is the frame format. G.704 is a CEPT stand ard, with a set value.

Line Service

specifies whether the LP will use all (Fu ll) or some (Fract ional) of the DS0 channels
on a T1/E1 line:

Line Build Out

is the di stance from the LP to the external T1/E1 device. G.703 is a CEPT standard,
with a set value.

Unit Type

0

= Pr ima ry, 1 = Secondary

[?]

f or help di s pla ys a ra nge of

4

= T1/E 1

[?]

f or help di s pla ys a ran ge of

0

= Full, 1 = Frac tional

6

1–6

, the su ppor t ed t yp e s are :

= RLP-7000 Node

0–3

, only 2 is valid for E1 LP.

6-14 FR X8 000 3 .0 User Gu i de, Rev 02

Clock ing

is the clocking mode in which the LP ru ns: 0 = Ma ste r,

National Use Bit “n”

is the setting of the n a tiona l use bits in the non-frame align ment signal. National use
bits 1-5 correspond to data bits 4-8 in the n on-frame alignment signal. National use
bits are reserve d for use within a country. If th e signal will cross an international
border, the national use bits should be

CRC - 4 Di sab l ed ?

spe cifi es whethe r t o disab le the gener ation of C RC-4 (pol ynomial X4 + X + 1).
Enablin g CRC-4 enh anc es error monitor ing and p rovid es add ed pr otectio n a gainst
simulation o f the frame alignmen t signal.

International Use Bit 0

is the setting of bit 0, which is tra ns mitted as the most significant bit of the frame
alig nment signal when CRC-4 is disabled.

International Use Bit "n" 1

is the setting of bit 1, whic h is tran smitt ed as the most signifi cant bit of the no n-frame
alig nment signal when CRC-4 is disabled.

Channel Signalling

is the mode of the CEPT inter face. 0 = Comm on, 1 = Associated.

Off

= S l a ve

1

.

The multiframe alignment signal is trans mitted in time slot 16 wh e n Chann el
Signallin g has a value of

X1,2,3 Bits

spec ify the settings of spare bits X1, X2, and X3.

A,B, C,D Bits

spec ify the settings of the signalling bits that are transmitted in time-slot 16 when
Channel Sig nallin g is value

(Associated) .

1

.

1

Confi guring LPs and LAN C ards 6-15

Configuring T1/ E1 Channel M aps

T he Channel Ma p file maint ains DS0 ch annel as signments for a T1/E1 line connected
to an N74/7500. Pr ess

[I]

Menu. Wh en prompted , enter:

, t h en

[C]

from the Connections and Routing Pa ths Selection

No de ID

●

of the node containing the T1/E1 Card:

1–250

. ( De f ault is the local

node.)

LP ID: 0–7

●

Group ID: 0–99

●

●

An y other requested information, noting the values in Table 5-6. (Press

. ( De fault is 0.)

.

at a prompt to specify the default.)

Channel Map Maintenance

* Node 10
*LP 1
*Group ID 0

A G roup N ame mapname

B Base Rate 1 64k
C Start DSO Chann el Number 4
D How Many DSOs 3
E Destination Type 0 LP Por t
F LP Number 1
G Port N umb er 1

I L in e Con di t ion in g 4 TRSP _ M UX

Select:

[Enter]

F igure 6-7 T1 /E 1 Channel M ap Re cord

Destination Type

If th e

Number

, and instead of ite m G the re is an item H,

Expansion LP Port

is 2 (

[A],[F],[I],[C]

from Main Menu

), item F is

Start DS0 Number

Secondary LP

.

When Changes Take Effect

When you add a n ew Channel Map record , the change is written to th e database as
soon as you en te r the final para meter valu e . Wh e n you mo dify an existing record, the
change is written to the database instantly.

To make the change effective at the LP, press
tions on the record. This will tem porarily d isable th e LP and write the change to the
software runnin g in the node. (If this is not done, the change will take effect at the next
IPL of the node c ontaining the LP .)

6-16 FR X8 000 3 .0 User Gu i de, Rev 02

[F7]

while still in Maintenan ce opera-

Channel Map Parameters

Parameter Valid Values Default Value

Group Na me
Base Rate 0–2 1

Start DS0 Channel Number 1–24 (
How many DSOs 1–24

D es ti nation Ty pe
LP Number 0–7 0

Data Card Num b er
Expansion LP N um ber 0–9 0
Por t Num be r 0– 3 0
Line Conditioning 1–6 4

1 T ype 1 is not supp orte d in th e curr ent FRX80 00 re lea se.

Group Name

is a description for the channel map .

Table 6-6 T1/E1 Channel Map Parameters

20 characters none

1–30

T1) or

(T1) or

1

0 or 2

n.a. (Data cards are not supported)

1–30

(E1)

(E1)

1
1

0

Base Rate

is the line speed of individual DS0 channels conf igured in this chan nel m a p.

0

= 56K

Start DS 0 Channel Number

1

= 6 4K

is the first channel number in a group of DS0 channels.

How many DSOs

is the number of DS0s in a group of conti guous DS0s .

Destination Type

is the destinati on LP type of a DS0 ch ann el: 0 = T1/E1 LP, 2 = Expansion LP

LP Number, Port Number

are the destina tion LP and port of a T1/E1 line.

Expansion LP Number

is an Expansion LP destinatio n for a T1/E1 lin e .

Line Conditioning

is the pattern to be pu t on the data path in the event a Carrier Fa ilure a la rm occurs
(when line synchronization is los t).

1

= TC (ijkl, mnop)IDEL2 = TC(ijkl,mnop)IWpq

4

= TRSP_MUX

2

= 64K Alter natin g

5

= TRSP, TRB

3

= TRSPZ

6

= TRSP, IWpq

Confi guring LPs and LAN C ards 6-17

Configuring LAN Cards

LAN cards are supported in the FRX8000 Enterp rise Switch for IP routing across the
network, and in the ICP, INM, and NMP for local FTP and telnet file operations.

To config ure a reco rd for a LAN car d, press

[C], [B]

from the Main Menu). When prompted, enter:

No de numbe r

●

Card nu m be r: 0

●

If one LAN card is installed, it is num ber
the first o ne in stalle d is 0. The file PROTOCOL.INI (described on
page 6 -19) contains information that identifies each card as 0 or 1.

A Model 2 pla tform canno t contain two I ntel Ethern et cards. Als o,
if t he node contains one Inte l Ethernet card and One SMC
Ethernet card, card

●

An y other request information , noting Table 5-7 .

When Changes Take Effect

When you add a n ew LAN card record, the change will be written to the database as
soon as you en te r the final para meter valu e . Wh e n you mo dify an existing record, the
change will b e written to the database immediately.

The chang e can be implement ed on th e card by performing a

[B], [B], [D], [A]

(

from the Main Menu) to the node containing the card.

[B]

at the Configu re Cards Menu (or

(of the node containing the LAN card):

or 1.

0

0

must be the Intel card.

[A],

1–250

.

. If two cards are pre sent,

Configuration Update

LAN Card Parameters

Table 6-7 LAN Card Parameter

P a ra meter Val id V a l ues Defau l t Value

Type 1– 4

Local MAC Address 000000000000–ffffffffffff 000000000000
LAN ID 000 –ff f (

1 A lthough pr e s si ng
2 Di splayed only if the c ard i s Token Ring, this must be uniq ue among all IDs on the

netwo rk.

[?]

displays a r ange of

Type

1

= Inte l Ethe rnet,2 = Intel Token Ring,3 = SMC Et h e r n e t ,4 = IBM Token Ring

T he Intel card s are n ot curren tly avai lable; h owever, they are s upported for
existing customers who have those cards.

6-18 FR X8 000 3 .0 User Gu i de, Rev 02

1

0–4

2

)

hex

0

, type

is not currently supported.

1

000

Local MAC Address

LAN ID

PROT OCOL.INI

is a MAC address that will override the universally administered MAC address. If all
zeros are specified, the univer sal address will be used.

ide ntifies the ring number used by a fra me relay-co mpl iant so urce-r out e bridg e at th e
other end of this PVC. The value is normally ass igned by a system ad ministrator .

Eac h LAN ID must be unique within the network o n which this no de will
operate.

The PROTOCOL.I NI file conta ins information th at identifies the type(s) and operating
parameters of any installed LAN card(s ) in an FRX8000 Switch, ICP, or INM. You
can create a Node L AN Card Configuration Report, wh ich contains the PRO-
TOCOL.INI information from one or all FRX8000 node s i n the net wor k. This report
can be displ ayed, printed, or s aved to a file for later use.

The file CONFIG.SY S a lso c onta i ns defini ng inform ation on L AN ca rds.
The contents of this file can be found in the (optional) Netl ink FRX8000
Mainten anc e Guide.

To create a PROTOCOL.INI report:

1 . Pr e ss

2. When prompted, enter the ID of the desired node, or press
defaul t of

3. Y ou will be prompted :

at the Reports Menu (or

[E]

Al l Nodes

●

To print the report, type

●

To save the report to a file , type

.

Display Opt. P, F, V

p [Enter]

[G], [E]

.

f [Enter]

from the Main Menu).

to specify the

[Enter]

:

. When pr o mpted fo r a file s pecifi-

cation, enter a fil e name for the report.

●

To display the report on the screen, type

v [Enter]

.

One line of PR OTOCOL.INI, Bindings = “nnn,” can be read to easily identify the
installe d LAN cards, as shown below.

Table 6-8 PROTOCOL.INI Sample R eport

Type of Card 1st/Only Card of This Type

Bindings =

Int el Ethernet
SMC Ethernet
Intel Token Ring
IBM Toke n Ri ng

EXP16 EXP16_2
SMCMAC8001 SMCMAC8002
OLIT OK OLITOK 2
NLK_ TOK NLK_ TO K2

2nd Card of This Type

Bindings =

Confi guring LPs and LAN C ards 6-19

Chapter 7

Configuring Inter-Nodal Trunks

A tru nk carri es traffic be tween t wo node s of any type among FRX8 000 (a ll node
types), N7400, and N 7500. The re are three t ypes of t runk:

●

Physical trunk

●

Logical trunk over physical frame relay link (FRX8000 o nly)

●

Lo gical tr unk over physi ca l X.25 l i nk

T o configure a logic al tr unk over physica l X.25 on an N7400 or 7500, c on­f igure a physi ca l PDN port (de s cribed on page 7-11), then a logical PDN
po rt on that ph ys i c al p ort.

An FRX8000 supports up to 64 trunks to up to 64 nodes. An N7400 or N 7500 supports
up t o 31 tr un ks t o up t o 20 n o des . A t runk b et w ee n an FR X 8 00 0 a n d a n N74/7 500 ca n
be c re at ed by con fi gu ri n g both e nd s as ph ys ic al t ru nk, o r by con fi guring th e F RX8 000
por t as logica l trunk over X. 25 and the N74/7500 port as a logi ca l PDN port.

Parallel Tr unks

Parallel trunks are two or more trunks between the same two nodes. The trunk process
in eac h node attempts to split the load across para lle l trunks proportional to th e speeds
of the in dividu al trunks. The node software examines each packet’s the queue length
on each paralle l trunk and, using the configured line speed and propagation delay,
computes the de livery tim e ov e r each trunk . Th e trunk with the sh orte st d e liver y time
is used. This process is called load balancing.

Parallel t r unks runn ing at differ ent spe eds ma ke lo ad balan cing difficult b ecau se of the
variability of predicted deliv ery times. T he node software do es not no rmally consider
any trunk that is less than half the speed of the fastest pa rallel tr unk.

Parallel trunks can incre ase reliability over a single trunk; however, more
proc essor time is required to determine which trunk to use, and the proba­bility of packe ts reaching the d estination node out of sequence is greatly
increased. Out-of- sequence packets must be held until the gaps are filled
in, causing increas ed buffer usage.

If circumstances dictate, all trunks can be reco gnized by enabling low
speed trunk balancing. However, this sh ould not be done unless absolutely
necessary. C ontact Cabletron Systems Technical Support for inf ormation.

Additional trunks can be better used to increase the connectivity and capacity of the
network, in ste ad of as parallel trunks. Fo r example, the configuration on the righ t side
of Figure 7-1 is a b etter use of trunks th a n the one on the left.

Node 1

Node 4

Node 2

Node 3

Figure 7-1 Examples of Multiple Trunk s

Required and Optional Configuration

To sup po r t a trunk, make su re th e following are correc tly configured in the databas e:

●

Network Defa ults, d escribe d in Chapte r 4. This file must be con figure d for a

new n etwork. After that, no further changes are g enerally necess ary.

●

Node parameters, described in Chapter 5. A record must exist for every node on

the network .

●

Line Processor, d escribed in Chapter 6. A reco rd must exist for every LP in

eve r y node o n t he ne t work.

●

Port, described on page 7-3. A record must exist for every port on every LP in

ev ery node. Each trunk port’s record will identify the trunk port and define its
oper ating parameters.

●

Modem Initia liz ation record, descr ibed on page 7-11, if t he (RS-232 physic al

interface only) p ort will be con necte d to a V.25bis modem.

●

Subscriber IDs, described on page 7-17. A reco rd must be created for each

called an d calling address s pecif ied in logical trunk record s.

●

P VC Conn e c t i on r ec ord, de s cribed on page 7-20. A re cord is nec essary if you

want to create a “permanent” co nnection between an FRX8000 logical trunk
por t and its underlyi ng physic al X. 25 port .

●

Telephone number, described page 7-23, if the port will b e connecte d to a

V.25bis modem.

Node 5 Node 6

Node 7Node 8

7-2 FR X8 000 3 .0 User Gu i de, Rev 02

Co nfigur ing Trunk Po rt Recor ds

To configu re an N74/750 0 po rt as a logical trunk, g o to “Configuring N7 4/ 75 00 PD N

Ports” on page 7-11. To configure any other trunk type, press

Ports Se lection Menu (or
enter:

[A], [D], [A], [C]

[A]

, then

[C]

fro m the

fr om t he M ai n Men u). Whe n prompt ed,

No de ID

●

LP ID

●

Port: 0–7

●

only),

(of the node containing the port):

(of the LP containin g the port):

f or a physi ca l port on an RLP,

8–63

for a logi cal port. (I f configurin g an FRX8 000 logical po rt, enter the

1–250

. (Default is the “local” node.)

0–7

. (Default is 0.)

0–3

for a port on an AST LP (N74/7500

associated physical X.25 or frame relay port numb er when asked.)

●

Any o ther requested informatio n, noting the values in Table 7-1. (Press

[Enter]

at a pr om pt to s pe c i fy t he de f a ul t va l ue . )

Th e d i s pl ay d epend s on whet h e r yo u a re c o nf igur i ng a t runk o n a ph ys i ca l po rt with a
V.25bi s modem connec ted (F igur e 7-2) , a physica l por t with no V.2 5bis mode m
(Figure 7 -3), or a l ogical port (Figur e 7-4).

Port Main tenance
* Node ID 10 node10
* LP ID 0 R LP
*Port 1

A Port Type 3 Trunk
B Physical Interface 4 V.25Bis_Dial
C Blocked Port Flag N
D Lin e Spee d Code 10 9600 bps

F Outsta ndi ng F rames 2
G N 2 Maximum Re transmissions 5
H T1 R etransmiss. P eriod-ms 2000
I T2 Acknowledg. Del ay-ms 1000
J T3 Link Assurance Period-s 10
K Propagation Delay-ms 0
L Logical DCE Y
M Generate Clock Y

O Lin e Se t up Re t rie s 5
P Remote Telephon e Numb er 8005551212
Q Mod em INI Stri ng Na m e

Se l ec t:

Co nfiguring I nt er-Nodal Trunk s 7-3

Fi gure 7- 2 Physic al Trunk Port R ecord for V.25bis P ort

[A],[D],[A],[C]

from Main Menu

P o rt Ma in t en a n ce
* Node ID 10 node10
* LP ID 0 RLP
*Port 1

A Port Type 3 Trunk
B P hy si c a l Inte r fa ce 5 V. 3 5
C B l ock ed P o rt Flag N
D Line Speed Code 10 9600 bps
E M o dul us 8
F Outstan di ng F rames 2
G N2 Maximum Retr ansmissions 5
H T1 Retransmiss. Pe riod-ms 2000
I T2 Ac knowledg. Delay-ms 1000
J T3 Link Assurance Per iod-s 10
K Pr opagation Delay-ms 0
L Logical DCE Y
M Ge nerate Clock Y
N Rcv Clock (TT) from DTE N
O Extra CRC N
1 Backup Trunk Parameters

Select:

Figure 7-3 Physical Tr unk Port Record for Non-V.25bis Port

[A],[D],[A],[C]

from Main Menu

Item N will be displayed only if the
is

RS-530, RS-422

Pressing

[1]

, or

V.35

, and

at the above scr een will display m ore parameters, listed in

Tab le 7-1.

P o rt Maintena n ce
* Node ID 10 node10
* LP ID 0 RLP
*Port 8
A U nd erlying Ph y s. Po rt 2
B Port Type 3 Tr unk
C B l ock ed P o rt Flag N
D Modulus 8
E O utstan ding Frames 2
F N2 Maximum Retr ansmissions 5
G T1 Retransmiss. Pe riod-ms 2000
H T2 Acknowledg. Delay-ms 1000
I T3 Link Assurance Per iod-s 10
J Propagation Delay-ms 0
K Logic al DCE Y
L Extra CRC N
1 Logical Trunk Parameters
2 Backup Trunk Parameters

Select:

is an

LP

RLP

Generate Clock

and

Physical Interface

is Y.

7-4 FR X8 000 3 .0 User Gu i de, Rev 02

Figure 7-4 Logical Trunk Port Record

Pressing

[1]

or

will display more param eters, all listed in Table 7-1.

[2]

[A],[D],[A],[C]

from Main Menu

When Changes Take Effect at the Port

When you add a ne w Po rt rec ord, it will be written to the databas e as soon as you enter
the final param eter value. When you modify a parameter in an existing record, the
change will be writte n to the database immediately.

The change will become effe ctive at the port in o ne of the follow ing ways:

●

Press
temporarily disable the port, then write the chan ge to the so ftware running in the
node.

●

Re-IPL the node containing the changed port.

Trunk Port Paramete rs

Table 7-1 lists the parameters f or all trunk types. Which parameters are displayed in a
record depends one or more of these factors:

●

Trunk type (and underlying port type if a logical trunk)

●

Whet her or not the port is configured for connection to a V.25bis modem

●

Whether or not the port is configured as a backup trunk

Parameter Valid Values Default Value

Por t Type

Physical Interface
Bl ocked Port Flag Y/N N

Line Speed Code

M odulus 8, 128 8
Outst anding Frames 1–127 7
N2 Ma ximu m Re t ran smissio ns 1–99 5
T1 Retransmi ssion Period 40–64000 2000
T2 Acknowle dgm ent Delay 0–32000 1000
T3 Link Assur ance Period 1–250 10
Pr opagati on Dela y 0–9999 0
Logical D CE Y/N Y
Generate Cl ock Y/N N
R cv Cl ock (TT) f r om DTE Y/ N N
Extra CRC Y/N N
Line Setu p Ret ries 0–99 5

R emote Telephone Number
M odem INI String Name

(continued on next page)

[F7]

while still in Maintenance operations on the record. Th is will

Tabl e 7-1 Trunk Port Parameter s

(Trunk) (not valid here)

3

(see explanation)

7–19, 21
7–85

1–12 digits
up to 10 characters none

(AST LP)

(RLP)

3

10

0

Co nfiguring I nt er-Nodal Trunk s 7-5

Table 7-1 Trunk Port Parameters

(continued)

P a ra meter Val id V a l ues Defau l t Value

Logical Trunk Parameters

Under l ying Physical Port
Ca lli n g Ad dre ss

Called Address
Number of Circuits 1–8
PVC Y/N

First PV C LCN

Mapped D LCI Num ber 16–991
Connection Priori ty 0–9 0

Ba cku p Tr un k Para me t e rs

This Trunk a Backup
De-Ac tivation Timer

This Trunk Backed Up
Backup LP ID 0-7 0
Ba ck u p Port No.0-30
Backup Logical Trunk 1-8 1

is frame relay, and is v alid only on FRX8000 ports.

1

FR

If

2

is Y, leave

PVC

5

(sec)

5

Called Address

valid X. 2 5 or FR po r t
valid subscriber ID

valid subscriber ID

3

2

(to be implemented in a future release)

4

Y/N N
1-300 20

Y/N N

and

Calling Address

other end of trunk will be an N74/7500.
Must be 1 if other end of trunk will be a n N74 /750 0. (See explanati on.)

3

The connection defined by the card, port, an d DLCI must be different for each logical

4

connection (logical port, IP or IPX interface over frame relay, an d frame relay-to-frame
relay PVC) i n this node.

5

This Trunk a Backu p

and

This Trunk Backed Up

cannot both be Y. If o ne is Y, changing

t he ot he r to Y will automatically change the first one to N.

1

2

2

blank. Also ,

none
none

none

1
N

none

must be N if

PVC

Physical Interface

is the hardware interface. On an AST LP, this is alway s RS-232. On an RLP, the
interface is determined by the associated L ine Interface Card (LIC) an d the cable
attach ed to the port's I/O box connector. Th e LP reco r d identifies the LI C, and only
th e val id interfaces will be displayed as choice s in the Port record. LICs are shown in
parentheses:

= RS-232 (RS-232)

3

= RS-449 (RS-422)

6

= E1 (E1)

9

Bl ocked Po r t Flag

causes the port to be enab led (N) or di s abled (Y) at node

= V.25Bis_Dial (RS-2 32)5 = V.35 (V.35 )

4

= RS -530 (RS -422)

7

= X.21 (RS-422)

8

. The port will remain in

IPL

that state until this p a rame te r is changed (and sent to th e node) or an o n-line en a ble/
disabl e is perfo rme d. (See " Dis abling and Enabli ng Ports" on page 18-1.)

Line Speed Code

specifies the data transmission r ate in bits per second, and the clock speed when the
port is a physical DCE. If this port is not configured to gen erate clock, spec ify the lin e
sp eed that corr es ponds (as clo sely as po ssibl e) to the configu ration of the dev ice co n­nected to th e port. Line speed codes are as foll ows. (So m e speeds have two cor r e-

7-6 FR X8 000 3 .0 User Gu i de, Rev 02

spond ing cod es because th ey a re defi ned in d ifferent p arts of th e softwa re. Eith er code
can be specified.)

= 75 4 = 1 50

3

= 24 00 9 = 48 00

8

= 56K

13

= 224K

18

= 38.4K

23

= 280K

28

= 560K

33

= 840K

38

= 1.1 2M

43

= 1.4 M

48

= 1.6 8M

53

= 320K

58

= 640K

63

= 960K

68

= 1.2 8M

73

= 1.6 M

78

= 1.9 2M

83

= 64K

14

= 256K

19

= 56K

24

= 336K

29

= 616K

34

= 896K

39

= 1.176M

44

= 1.456M

49

= 64K

54

= 384K

59

= 704K

64

= 1.024M

69

= 1.344M

74

= 1.664M

79

= 1.984M

84

The max imum for an RS-2 32 i nterface on an N7 400 or 7500 is 19. 2K.
The maximum f o r an RS-232 interface on an FRX8000 is 64K if the
port is directly connected to the user device via the 5-foot Cabletron
RS-232 cable. I f modems or longer cablin g are used, the r ecom­mended maximum speed is 19.2K. (The EIA RS-232 standard applies
to line speeds of 19.2K and lower.)

= 300

5

= 9600

10

= 72K

15

= 14.4K

20

= 112K

25

= 392K

30

= 672K

35

= 95 2K

40

= 1.232M

45

= 1.512M

50

= 128K

55

= 448K

60

= 76 8K

65

= 1.088M

70

= 1.408M

75

= 1.792M

80

= 2.048M

85

= 600

6

= 19.2K

11

= 112K

16

= 24K

21

= 168K

26

= 448K

31

= 728K

36

= 1.008M

41

= 1.288M

46

= 1.568M

51

= 19 2K

56

= 512K

61

= 832K

66

= 1.152M

71

= 1.472M

76

= 1.728M

81

= 1200

7

= 48K

12

= 128K

17

= 28.8K

22

= 224K

27

= 504K

32

= 78 4K

37

= 1.064M

42

= 1.344M

47

= 1.624M

52

= 256K

57

= 57 6K

62

= 896K

67

= 1.216M

72

= 1.536M

77

= 1.856M

82

Mo dulus

is a number for valu es used in X.2 5 level-2 sequenced packets . Th e actual frame num­beri ng is 0–7 for mo dulus 8 and 0–127 f or modul us 128.

Outstanding Frame s

is X.25 value K, the maximum number of sequentially numbered I-f r ames that can be
waitin g for acknowledgment. I f this number is exceed ed, no more frames will be
transmitted u ntil an acknowledgment is rec eived.

N2 Maximum Retransmissions

is X.25 value N2, the maximum n umber of times th e node will attempt to send an I­frame after a Retransmission Period expiration. A large r value for this parameter
increases the probability of an even tual correct transfer between DTE and DCE, but a
smaller va lue permits faster detection of a permanent error condition.

T1 Retransmissi on Per iod

is X. 25 timer T1, the length of time befo re the node will transmit an I-fra me if the pre­viou s transmissio n is not acknowledged. If the period expires , the timer will be reset
and a su per vis ory frame will be tr ansmitted demand ing immediate ackno wledgment.
The N2 counter will also be incremented (see the N2 entry on page 7-7) .

T he de fault value of 2000 ms a llows a voida nce of unnec essary r etransmission of
frames that hav e merely been delayed.

T2 Acknow ledgment Del ay

is X.25 timer T2, the len g th of time t he node wi ll d elay ac knowled gment o f a received
I -fra me if t here is no outgoing I- fra me to be sent. If duri ng this per iod the node

Co nfiguring I nt er-Nodal Trunk s 7-7

r eceive s an I -frame for tran smis sion , th e ackno wledgmen t will be sent with it, an d the
delay timer will be reset.

T3 Link Assurance P eriod

is X.2 5 time r T3, the length of time af te r whic h the logical DCE will poll its coun­terpart if there is n o dat a transfer. The value should be sufficie ntly larg er than the
DCE's T1 timer (Retra nsmission Period), to assure that the link is n ot o pera tiona l
before a poll is sen t.

Propaga tion Delay

tells the softwar e how long it will take a signal to travel from one point to another (e.g.,
from a s a tellite dish to a satellite). This helps the FRX8000 determine the fastest
routing. The valu e to be specified is normally determined by the signal car r ier.

Logical DCE

Selecting N defin es the po rt as logical DTE. The other end of the connection m ust b e
the opposite of this port. Logical DCE/DTE is independent of physical—either can be
eith er. A node connec tin g a subscriber devi ce into a netwo rk should n ormally be con­figured as logical DCE.

Generate Clock

If this port is a physical DCE (determined by LP jumpers and/or cable/converter
in terfa ce), sp ecify

Rcv Cloc k (TT) from DTE

Y

allows the clock to be lo ope d back from the DTE using the TT (Terminal Timing)
signal, which can be helpful on high-speed ports.

, s ince DCE g enerates clock. If the port is DTE, specify N.

Extra CRC

provides a second cy clical redundancy check (CRC), in addition to the two-byte CRC
in cluded in the fra me check sequence in a standard X.25 frame. Each CRC is a c al cu­lation t hat is placed in the field by the transmitting device, then r ecalculated at the
r eceiving d evic e to det ermine whe ther e rrors occu rred. On a nois y line th e sing le CRC
can miss er rors, but a second CRC greatly improves th e chances of catching errors.

Line Setup Ret r ies

is the number of times the node will attempt to initialize the V.25 mode m on this port
if the n ode does not receive an OK af te r sending a modem initializa tion str ing. (See
"V.25bis Modem Operations" on page 7-10.)

Remote Tel ephone Number

is used by the V.25bis dialer to call the oth er end of the con nection.

Modem IN I String Name

identifies a string of data that will be sent to the modem each time the connection is
initialized. The actual d ata is sp ecified in the M odem Initializa tion file (described on

page 7-10).

7-8 FR X8 000 3 .0 User Gu i de, Rev 02

Log ical Tr un k P arame t ers

Un d er lying P hysi cal Po rt

is the physical X.25 or frame relay port (whose record must be configured first) on
whic h this logical port is being c onfigured.

Cal ling Address

identifies the local end of the logical trun k. A reco rd for this address must e xist in the
Subscribe r file (see page 7-18), wit h the local lo gical p ort sp ecified as the only ro uting
path.

Called Address

identif ies the remot e end of the log ic al trunk . A record for this address must exist in
the Subscrib e r file, with the remote logical port specified as the o nly routin g pa th.

Number of Circuits

is the number of “paths” on the sin gle lo gical trunk ov e r which traffic will be trans­mitted in parallel, using different LCNs. Th is provides an eff ective w indow size larger
tha n a sin gle channe l would suppl y.

If the remote end of the trunk will be an N74/7500,
tiple channel s must be configured as separate logical ports (X.25 trunks on the
FRX8000, PDN on the N7 4/750 0), e ac h identifi ed by a unique addres s .

PVC

specifies whether this logical trunk is one end of a PVC to the underlying physical
X.25 port. If

, a PVC Connection record (see page 7-20) must be created for each

Y

circuit (determined by
type as

Mapp ed DLCI Nu m b er

X.25 Trunk

is the Data Link Con nection Identifier, a r outing ID that assigns a frame to a particular
logical conne ction . This ID is used o nly locally, a nd th e DLCI can b e differe nt at each
end of a logical connection.

Make sure that no more than one of any interface type (logical
port or frame relay IP/IPX/LLC2 interface) is assigned the same
DLCI.

Conn ectio n Priority

allo ws setting a priority for this logical connection relativ e to others on the physical
link; th e higher the number, the higher the priority.

Nu m be r of Circ uits

.)

Number of Circuits

mu st be 1. Mul -

) on th is logical tru nk. (Con figur e ea ch PVC

Backup Trunk Parameters

Th is Tr un k a Ba ck u p

specif ies whethe r the cu rrent tru nk is backin g up o ne or more other tr unks on th e same
nod e. A trunk spec ified as back up remai ns out of servic e if all trun ks it is backing u p
are operatio nal; there fore, d o no t co nfigur e two trunk s as backups for e ach other.

At node IPL , a ll trunks th at are not back ups are acti vated. Any back up trunks beg in in
a disable d state; howev er, th ey can accept request s for connecti on from the o ther end.
When the node determines that one of its trunks is down , it activates any backup trunk

Co nfiguring I nt er-Nodal Trunk s 7-9

specified in the disabled trunk’s Port record. When th e backup trunk receives the
enable request, it checks its internal counter to see how many trunks it is curr ently
backing up. If the counter is zero , the node enables the trunk, and increments the
counter to one. If the counter is not at zero, this means the trunk is alread y active, and
th e counte r is sim ply incre men ted by one. h en the fa ile d trunk is r e-activ ated , a disab le
request is sent to the b a ckup trunk. The backup trunk then decrements its counter by
one. I f the counter is now zero , the software waits for 65 seconds, then starts the
backup trunk’s de-activation tim er (con figured in the port record). Onc e the timer
expires, the backup trunk becomes disabled.

De-Acti vati on Ti m er

specifies the length of time that a b ackup trunk stays up afte r all of its primary trunks
have co me back u p.

This Trunk Backed Up

specifies wheth er the current trunk has a backup trunk.

Backup LP ID/Port No./Logi ca l Tr unk

identifies the port that will be the lo c al end of the backup trunk.

V.25bis M odem Operati ons

Creat ing a Modem Initialization Record

A record ca n be created that specifies a strin g of d ata to b e sen t out (verbat im) from a
V.25bis dial port to the modem each time the port is enabled (by node IPL or port
di sable/enable).

Press
prompted, enter:

Explanations of some parameter s follow the table.

at the Port C onfigura tion Me nu (o r

[E]

●

String Name

: up to 10 cha racter s. This must ma tch a

figured in the Port record. (See page 7-8.)

●

Any other re quest ed i nforma t ion, noting Ta bl e 7-2.

Table 7 -2 Mo dem Initia liza tion Parameters

P a ra meter Val id V a l ues Defau l t Value

De scr ipti on
Modem Pool ID 0–255 0

INI St ring

[A], [D], [E]

up to 24 characters none

up to 35 characters none

from the Main Menu). Wh en

Modem INI String Name

con-

Modem Pool ID

identifies a type of modem (determined by the user). More than one s tring can be
assigned to the same ID.

7-10 FR X8 000 3 .0 User Gu i de, Rev 02

INI St ring

will be sent verbatim to the modem d uring initializa tion. It is int ended to co ntain spe­cific information th at will be read by the mo dem (configu ration, ope ration, etc .).

Initializing a Modem

Her e is the n orm al sequence for initialization of a V.25bis modem:

1. After re cei vin g a Po rt Enable fro m t he FRX8 000 sof tw are, D TR wi ll be as s ert ed
on the port.

2. If the modem is p ower ed on and in AT mode, it will retu rn CTS.

3. T he node will sen d the modem initializatio n strin g.

4. The modem should return an OK or an error.

5. If the node r eceiv es an OK, it will send the string AT*V3, which will put the
modem int o V.25bis synchronous mode.

If the node does no t receiv e an OK, it will assume the m odem is already in V.25
mode . The node will then send a message to re set the mod em to AT m ode , and
will re peat steps 3–5 of this procedure, up to the number of times specified for

Line Setup Retries

If the modem still does respond , it will be pu t into

Do not include the string

AT*V3

, as this is sent by the node later.
Sending it too soon will lock up the LP and cause this procedure
to miss a step.

in the Port record. (See p age 7-8.)

state.

Failed

Configuri ng N74 /7500 PD N Ports

N74 /7500 ports configured as PDN support logical trunk connections over a public
data network to other N74/7500s and to FRX8000 Switches (via logical X.25 trunk
por ts on FR X8000) . To c onfi gure an N74/7500 port as PDN, you must c onfi gure two
rec ords: one for the physical port (u nless it alrea dy ex ists) and one for the log ical port
that will reside on the physical port and will b e the logical trunk.

Press
M ain Me nu). Whe n prompted, e nte r:

Co nfiguring I nt er-Nodal Trunk s 7-11

[A]

●

No de ID

●

LP ID

●

Port: 0–7

only),

, then

from the Ports Selection Menu (or

[C]

(of the node containing the port):

(of the LP containin g the port):

f or a physi ca l port on an RLP,

for a logical port. (If you specify a logical port, enter the number of

8–63

0–7

0–3

[A], [D], [A], [C]

. (Default is the “local” node.)

1–250

. ( De f ault is 0.)

for a port on an AST LP (N74/7500

from the

the associated physical PDN port when asked.

Up to eight logical ports can be con figured on a physical PDN port.

●

Any o ther requested informatio n, noting the values in T a bl e 7-3. (Press
at a pr om pt to s pe c i fy t he de f a ul t va l ue . )

[Enter]

T he di s p la y de p e n ds o n w h e the r th e po rt i s a ph ys i c al po r t ( Fi gu r e 7-5) o r logic al po rt
(Figure 7-6) .

Port Main tenance
* Node ID 10 node10
* LP ID 0 R LP - 7000 Node
*Port 1

A P ort Type 12 PDN X. 25
B Physical Interface 5 V .35
C Blocked Port Flag N
D Lin e Speed Code 10 9600 bps
E Out sta ndi ng F rames 2
F N2 Maximum Retransmissions 5
G T1 Retrans miss. P eriod-ms 2000
H T2 Acknowle dg. Del ay-ms 1000
I T3 Link Assu rance Pe riod-s 10
J Maximum P acket Siz e 128
K Logical DCE Y
L Generate Clock Y
M Rcv Clock (TT) from DTE N
N M ask Link A larms Y
O Propagation Delay (ms) 0

1 X.25 le vel 3 Info

Select:

Figure 7-5 Physical PDN Port Record

[A],[D],[A],[C]

from Main Menu

Item M w ill be displayed only if the LP is an
is

RS-530, RS-422

P o rt Ma i n t e n a n ce
* Node ID 10 node10
* LP ID 0 RLP - 7000 Nod e
* Port 10

A Underlying Ph ysical Port 1

Port Type 12 PDN X.25
B Blocked Port Fla g N
C Calling Add ress 12345
D Called Add ress 67890

Select:

, or

V.35

, a nd

Generate Clock

Figure 7-6 Logical PDN Port Record

RLP

[A],[D],[A],[C]

and

Physical I nterface

is Y.

from Main Menu

7-12 FR X8 000 3 .0 User Gu i de, Rev 02

PDN Port Parameters

Parameter Valid Values Default Value

Por t Type 12

Physical Interface
Bl ocked Port Flag Y/N N

Line Speed Code
Outst anding Frames 1–127 7
N2 Ma ximu m Re t ran smissio ns 1–99 5
T1 Retransmi ssion Period 40–64000 2000
T2 Acknowledgment Delay 0–32000 1000
T3 Link Assur ance Peri od 1–250 10

Maximum Pac ket Size
Logical D CE Y/N Y
Generate Cl ock Y/N N
Rcv Clock (TT) from DTE Y/N N
M as k Link Alarms Y/N Y

Pr opagati on Dela y

Level 3 Par ameters

Lowes t/Highest Incomin g C hann el
Lowest/Hi ghest Tw o-w ay Channel

Lowest/Hi ghest Outgoing Channel
Default Window Size 1–7

Def aul t Pa cket Size 16–Maximum Packet Size Max. Packet Size
Fl ow Cont rol Ne gotia ti on Y/N N
Thruput Cla ss Negotiation Y/N N
Local Charging Preve nti on Y/N N

D efault Call ing A ddr es s

U nderlying Physical P or t 0–7 0
Bl oc k ed Fl a g Y/ N N

C alling Address
C alled Addres s

Table 7-3 Physical PDN Port Parameters

(P D N) (no t va li d he r e)

(see explanation)

3–19,21
3–85

(bytes)

(ms)

Logical PDN Port Parameters

512

1

for AST LP not configured for Big Packet Supported.

2 Default Packet Size in Network Defaults, o r

is greater than

3 One higher than

D efault Low SVC LCN
D efault Windo w Siz e

4

512

and LP i s not co nfigured for Big Packet Supported.

Highe st Inc om ing Channel

in the Network Defaults file.

in Netwo rk Default s file.

12 8–1024

0–9999 0

(see explanation)
(see explanation) see note

(see explanation)

0–15 digits none

0–15 digits none
0–15 digits none

3

(AST LP)

(RLP)

1

512

if AST LP and Network Defaults value

10
10

2

0

(

not used)

0

(not used)

see note

3

4

. If that is not used, the va lue will be the

Co nfiguring I nt er-Nodal Trunk s 7-13

Physical Interface

is the hardware interface. On an AST LP, this is alway s RS-232. On an RLP, the
interface is determined by the associated L ine Interface Card (LIC) an d the cable
attach ed to the port's I/O box connector. Th e LP reco r d identifies the LI C, and only
th e val id interfaces will be displayed as choice s in the Port record. LICs are shown in
parentheses:

= RS-232 (RS-232)

3

= R S-449 (RS-42 2)7 = RS-530 (RS-422)

6

Bl ocked Po r t Flag

causes the port to be enab led (N) or dis able d (Y) at node IPL. The port will remain in
that state until this p a rame te r is changed (and sent to th e node) or an o n-line en a ble/
disabl e is perfo rme d. (See " Dis abling and Enabli ng Ports" on page 18-1.)

Line Speed Code

specifies the data transmission r ate in bits per second, and the clock speed when the
port is a physical DCE. If this port is not configured to gen erate clock, spec ify the lin e
sp eed that corr es ponds (as clo sely as po ssibl e) to the configu ration of the dev ice co n­nected to th e port. Line speed codes are as foll ows. (So m e speeds have two cor r e­sp onding cod es beca use they are defin ed in diff erent parts of the sof tware. E it her code
can be specif ied.)

= 7 5 4 = 150

3

= 2400 9 = 4800

8

= 56K

13

= 224K

18

= 38.4K

23

= 280K

28

= 56 0K

33

= 840K

38

= 1.12M

43

= 1.4M

48

= 1.68M

53

= 320K

58

= 640K

63

= 96 0K

68

= 1.28M

73

= 1.6M

78

= 1.92M

83

= 64K

14

= 25 6K

19

= 56K

24

= 33 6K

29

= 61 6K

34

= 89 6K

39

= 1. 176M

44

= 1.456M

49

= 64K

54

= 38 4K

59

= 70 4K

64

= 1.024M

69

= 1. 344M

74

= 1.664M

79

= 1. 984M

84

= (not current ly supported)5 = V.35 ( V.35)

4

= X.21 (RS-422)

8

= 300

5

= 96 00

10

= 72K

15

= 1 4.4K

20

= 11 2K

25

= 39 2K

30

= 67 2K

35

= 952K

40

= 1.232M

45

= 1.512M

50

= 12 8K

55

= 44 8K

60

= 768K

65

= 1. 088M

70

= 1.408M

75

= 1. 792M

80

= 2.048M

85

= 600

6

= 1 9.2K

11

= 11 2K

16

= 24K

21

= 16 8K

26

= 44 8K

31

= 72 8K

36

= 1. 008M

41

= 1.288M

46

= 1. 568M

51

= 192K

56

= 51 2K

61

= 83 2K

66

= 1. 152M

71

= 1. 472M

76

= 1. 728M

81

7
12
17
22
27
32
37
42
47
52
57
62
67
72
77
82

= 1200

= 48K
= 12 8K
= 2 8.8K
= 22 4K
= 50 4K

= 784K
= 1. 064M
= 1. 344M
= 1. 624M
= 25 6K

= 576K
= 89 6K
= 1. 216M
= 1. 536M
= 1. 856M

Outstandi ng Frames

is X.25 value K, th e max imum number of seq uent ially numbered I -frames that can be
waiting for acknowledgm ent. If this number is ex ceeded, no more frames will be
transmitted until an acknowled gm ent is received.

N 2 M aximum Retrans missions

is X.2 5 va lue N2, the maximum number of times the node will attempt to send an I­frame after a Retransmission Per iod expiration. A lar ger valu e for this parameter

7-14 FR X8 000 3 .0 User Gu i de, Rev 02

The maximum speed for an R S-232 interface on an N74/7500 port is

19.2K.

increases the probability of an even tual correct transfer between DTE and DCE, but a
smaller va lue permits faster detection of a permanent error condition.

T1 Retransmissi on Per iod

is X. 25 timer T1, the length of time befo re the node will transmit an I-fra me if the pre­viou s transmissio n is not acknowledged. If the period expires , the timer will be reset
and a su per vis ory frame will be tr ansmitted demand ing immediate ackno wledgment.
The N2 ( see that entry) counter will also be incremented.

T he de fault value of 2000 ms a llows a voida nce of unnec essary r etransmission of
frames that hav e merely been delayed.

T2 Acknow ledgment Del ay

is X.25 timer T2, the len g th of time t he node wi ll d elay ac knowled gment o f a received
I -fra me if t here is no outgoing I- fra me to be sent. If duri ng this per iod the node
receives an I-frame for transmission, the a ckn owledgment will be sent with it, and the
delay timer will be reset.

T3 Lin k Assurance Period

is X.25 timer T3, the length of time after which the logical D CE will po ll its coun­terpar t if there is no da ta transf er. The value should be sufficien tly larger than the
DCE's T1 timer (Retransmissio n Period ), to assure that the link is not operational
before a poll is sent .

Maximum Packet Size

is the maximum data packet size that will be allowed to pass through this port. A
packet size included in a call setup packe t will be us ed, as long as it is smaller than the
maximum specified here.

Logic al DCE

Selecting N defines the port as logical DTE. The other end of the connection must be
the o pposite of this port. Log ical DCE/DTE is independent of physical—either can be
eithe r. A node connecting a subscriber device into a network should normally be con­figured as logical DCE.

Generate Clock

If this port is a physical DCE (determined by LP jumpers and/or cable/co nverter
interface), specify

Rcv Cloc k ( TT) from DTE

allo ws the clock to be looped b a c k from the DTE using the TT (Term inal Timin g)
signal, which can be helpful on high-speed ports.

Mas k Link Ala r m s

determ ines whether an alarm will be gen e rated if the link goes up or down . If

Li nk Alarm s

Propagation Delay

is Y, thes e alarms will not be generated.

tells the software how long it will tak e a signal to travel from one po int to anot her
(e.g., f rom a satellite dish to a satellite). This helps the FRX8000 determine the fastest
routing. The value to be specified is normally determined by the signal carrier.

, since DCE generates clock. If the port is DTE, specify N.

Y

Mask

Co nfiguring I nt er-Nodal Trunk s 7-15

Lowest/Highest IncomingTwo-Way/ Outgoing Channel

are the ranges of logical channel numbers that subscribers can use for calls through
this port. Th e valid values for each parameter that is used are determined as fo llows:

Channel

Lowest Incoming 1
Highest Incoming
Lowest 2-Way
Highest 2-Way
Lowest Outgoing
Highest Outgoing Lowest Outgoing

Changing any p arameter to a value that violates this order automatically changes any
other values now in vio la tion, s pecif ying the first value(s) w ithin the valid range. If
any pair is not used, its constraints apply to the next higher or lower pair (whichever
is appropriate) in the above list.

Defaul t Window Size

will be assigned to an inco ming call setup packet if the packet does not request a
window s ize.

Defau lt Packet Size

will be assigned to an inco ming call setup packet if the packet does not request a
packet size.

Flow Control Ne gotiation

is an option a l X.25 faci lity that permits negotiatio n of the flow control parameters
(packet and window siz es for eithe r direction o f data tra nsmission) on a per call basis.
If

is selected, th e default packet and window sizes will be used. If Y is selected, a

N

packet an d/or window size inclu ded in a call packet, up to the
and/or

Maximum Window Size

not included, the def a ult for that p arameter will be used. )

Valid Values

thr o ug h
Gr eater than/equ al to
Gr eater than
Gr eater than/equ al to
Gr eater than

Highest Incoming

Lowest Incoming

Highest Incoming

Lowest 2-Way

Highest 2-Way

through

4095

Maximum Packet Size

con figured in this Po rt record, will be used. (If either is

Thruput Cla ss Negotiatio n

is an option a l X.25 faci lity that permits negotiatio n of the throughput classes (lin e
speeds) for either direction of data transmission on a per c all basis. If

Maximum Throughput Class

in cluded in a call pack et, up to th e
for either direction is not included, the

Local Cha rg ing Prev ention

value will be used. If Y is selected, any throughpu t clas s

Maximum Throughput Class

Maximum Throughput Class

, will be used. (If a class

is sele cted, the

N

valu e will be used.)

if Y is selected for this p a rame ter, no calls can be charged to th is por t. Incoming calls
from the network with Reverse Charging specif ie d will be rejected; outgoing calls will
have Reverse Charging inserted if it is not already in the call packet.

Defau lt Call i ng Addr ess

will be inse rted into to an incoming Call Request packet if the packet does not co ntain
a calling address.

7-16 FR X8 000 3 .0 User Gu i de, Rev 02

Log ical Port Paramet ers

Un d er lying P hysi cal Po rt

is the physical PDN port (whose re cor d mus t be configured first) on which this logical
port is being configured.

Bloc ked Flag

causes the logical port to be enabled (N) or di s abled (Y) at no de IPL. The port will
remain in that state until this p aram eter is changed (and sent to the nod e) or an on-line
enable/disab le is perfor med . (See "Disa bling and E nabl ing Por ts" on page 18-1.)

Cal ling Address

identif ies the local end of the logical trunk. This address does not need to b e con­figured in the Subsc riber file, but it must be unique amo ng addresses co nfigured in the
databas e.

Called Address

identif ies the remot e end of the log ic al trunk . This address does not need to be con­figured in the Subsc riber file, but it must be unique amo ng addresses co nfigured in the
databas e.

Co nfigur ing Subscr iber IDs

This operation creates rec ords for the called a nd calling addresses that will be used in
call setup on logical trunks. To complete the co nne ction , the softwar e mu st recognize
wh ere the call is coming fr om (ca lling addre ss) and wh ere it is going (calle d add ress ).

To configure an SVC Subscriber record , pres s
uration Menu (or

Subscriber ID

of up to 15 dig its. (Th e default is an asterisk, which is a u niv e rsal

[A], [F], [A], [C]

from the Main Menu). When prompted, ent er a

[A]

, then

at the S ubscriber Config-

[C]

wild card .)

Subscriber addressing is de s cribed on page 9-15.

If this is an existing r ec ord, a screen similar to Figure 7-7 will b e displayed . If this is
a new record, enter the remaining req uested information, noting the values in

T able 7-4.

Co nfiguring I nt er-Nodal Trunk s 7-17

Subscriber Maintenance

* Subscriber ID 10000100001

A Su bsc r ib er Nam e xsub 1
B Di a l up Su bsc r ib er N
C Routing Al gorithm 0 Round Robin
D Systematic Re direction Y
E Redirect on Busy N
F Redire ct on Out of Order N
G Band w. All ocation Group 1

1 Routing Paths
2 Re d i r ec t i o n A dd re s s es

Select:

Fi gure 7- 7 SVC Sub sc ri be r Record

[A],[F],[A],[C]

from Main Menu

T he p a ramet ers dis pl ayed by pre s sing

When Changes Take Effect

When you add a new Subscriber record, the change will be writte n to the database as
soon as you enter the final parameter value. When you modify a parameter in an
existing record, the change will be written to the database immediately .

The cha nge will become effective on the trunk as so on as the next call is placed. (The
change will n ot af fect a call in progress.)

Subsc rib er Paramete rs

P a ra meter Val id V a l ues Defau l t Value

Subscr iber Name

Dialup Subscriber

Routing Al gorithm 0–2 0
Sy st em ati c Red ir ec t io n Y/N N
Redi rect on Busy Y/N N
Redi rect on Out of Order Y/N N
Ba nd w. Al loc. Group 1–3 1

1st,2 nd,etc. Routing Path
1st,2nd ,etc. R edirected S ub N o.

Tabl e 7-4

or

[1]

Su bscr ib er Paramet er

are listed in Tab le 7-4.

[2]

s

0–24 characters none
n/a - not yet supported

valid node / LP / por t
valid a dd r e ss

N

Not used
Not used

7-18 FR X8 000 3 .0 User Gu i de, Rev 02

Sub scriber Name

ide ntifies the subscr iber to the console oper ator. The F RX8000 softwa re does no t u se
this inform at ion.

Routing Algori thm

allows creation of a “hunt group” of ports, for the purpose of routing per a pre-selected
algorith m:

=

0

Ro und R obin

to the Routin g Paths. If the selected port is unreachable or congested , the Call
R eques t will be sen t to th e next port. (If the po rt become s available again, it is
inc lude d in its assigned position.)

=

1

Li ne Fa ile d

port does not m ake a connection, the call is cleared , even if o ther ports are
available.

2 = Li ne Bus y

port has failed, the nex t available port is sel ected.

If use of a routin g algorith m is no t d esired , simply a ccept th e default, an d specif y only
one routing pa th.

Systematic Red irection

redirects al l calls to the alternate subscribers specified by the Redirection Addresses.
Con secutive attem pts at c all r edirect ion are made to each alter nate s ubscribe r in order
of the index numbers, until the call is completed.

Redi r ect on Bus y

redirects calls acco rding to t he Redir ection Add ress es if the p rimary su bscrib er device
is busy.

Redi r ect on O ut of Order

redirects calls acco rding to t he Redir ection Add ress es if the p rimary su bscrib er device
is out of or der.

– sele cts ports speci fie d cyclica lly in numeri cal o rder acco rding

– selects the first port that is no t in a failed state. I f the selected

– sele cts the first po rt tha t has LCNs available (is no t busy). If the

Band w. Allo c. Group

is a method o f prioritizing outgoing traffic over trunks . Each IP and IPX ne twork
interface, SVC Subscriber, an d PVC is assigned to a bandwidth allocation group
de f ine d by a

Percent of Bandwidth

val u e (

1–100

) and a

Priority (0–9

) specified in the

Network Defaults file. (See "Bandwidth Allocation Groups for Trunks" on page 4-8.)

When configuring priorities, be careful to consider the types of
traffic being routed on other connections in the node.

1st, 2nd,etc. Routi ng Path

assi gns ports to the subscriber's routing paths group.

1st ,2nd, etc. Redirected S ub No.

is a subscriber that will be called according to the specifie d redirection optio n.

Co nfiguring I nt er-Nodal Trunk s 7-19

Configuring a PVC for a Logical X.25 Trunk

A “permanent” connection can be co nfigured between an FR X8000 Switch logical
trunk and its underlying physical X.25 port. (N7400 and 7500 do not support trunk
PVCs.) This allows communication b etween remote devices as soon as the physical
link is up.

Do not configure a PVC on the physical X.25 link if you are cre­ating one on the logical link.

A separate record must b e created for each circuit (as determined by the value of

N um ber of Circu it s

in the logical p ort record).

To add o r change a PVC , press
Paths Selection Menu (or

[A], [F], [C], [C]

[C]

[C]

, t hen

ag a i n from the Co nn e ct i o ns and Ro uti n g

from the Mai n Menu ). Wh en promp ted,

ent er:

Connection ID: 0–9999

●

●

An y other requested infor matio n, referring to Ta ble 7-5.

, which is sim ply a number unique to this connection.

PVC Con nection Maintenan ce

* Connection ID 123

A P VC Type 7 X.25 Trunk
B Node 10
CLP 0
DPort 0
E Logical Channel Number 6
F Description
G Packet Si ze 128
H Win dow Si ze 2
I Logical Port Number 8

Select:

When Changes Take Effect

When you add a n e w PVC record, the change will be written to the database as soon
as you enter the fina l par ameter value. When you modify a parameter in an existing
record, the change will be written to the database instantly.

7-20 FR X8 000 3 .0 User Gu i de, Rev 02

Fig ure 7-8 X.25 Trunk PVC Rec ord Exa mple

[A],[F], [C],[C]

from Main Menu