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 contributor 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, exempla 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 otherwise) 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 nvironment. 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 Communic 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.
RevDa teReason for Upda te
01August 1997General availability
02March 1998New 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).
Entermeans 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]”).
Pressmeans 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.
ivFR X8 000 3 .0 User Gu i de, Rev 02
Table of Contents
Section IGet t ing Started
C hapter 1Overview
Sum mary of Features ................................................................................ 1-2
Hard ware Overview ................................................................................. 1-5
C hapter 2Getting St arted
Using the INM Menu System................................................................... 2-1
20-1Alarms Report P arameters.................................................................. 20-2
21-1IP Ping Connectivity Test Parameter.................................................. 21-4
E-1LP Type Parameters.............................................................................. E-3
E-2Networ 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, connecting remote network sit es with a r obust switching technology that allows transmissi 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-2FR 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
Overview1-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 network 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-4FR 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 Parallel 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 interrelationships are shown in Table 1-1.
Device TypePlatf or mMax 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 terminati 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 networks to distribute database access and call setup, preventing setup delays caused by
long paths to distant INMs (described below).
Overview1-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 Auxiliary 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 nnect 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-6FR 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 customized 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-2FR 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-
AConfiguration
AConfigure Network
AConfigure Network De fau lt s
parameters the network needs for proper operation of FRX8000s.
Required.
BConfigure 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 .
CConfigure 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.
DConfigure Async PAD Logi n
used by a subscriber on an async PAD port. Required if login to the PAD
will be neces s ary.
EConfigure Async PAD Banner
displays on terminals connected to async PAD po rts.
FConfigure 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
BConfigure Node
AConfigure 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 .
BConfigure SNMP Parameters
– Chapter 16. Identifyin g informa tion on
the SNMP manager; definitions of communities; trap routing. Required if
using the SNMP agent.
CConfi gu r e Cards
AConfigure 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.
BConfigure 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.
DConfigure Por ts
AConfigure 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.
BConfigure Fra m e Rel ay DLCIs
B
, BE). Req uired for each frame relay DLCI.
C
CCUG Management
AConfigure 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.
BConfigure Internati onal CUG
DConfigure 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.
ECo 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.
FSNA PAD Mana g ement.
AConfigure 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).
BConfigure SNA 7000 TPAD -P U
– Identifying parameters for PUs
(physical units) in an N7000 TPAD mu ltidrop con figuration.
CConfigure 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.
AConfigure BSC Intera ctiv e Subscribers
BConfigure BSC Intera ctiv e Devices
– Ch a pter 9. Templates
– Identifying parameters for
3-2FR X8 000 3 .0 User Gu i de, Rev 02
EC onfi gur e LAN Interfaces
AConfigure 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.
BConfigure IPX Manage m ent
AConf 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.
BConf igure IPX Applicati ons
– a pplie s IPX filters to interfaces,
filter types, and/or dire ction s.
CSNA LLC2 Ma nagement
AConf 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.
BConfi gure S NA LLC2 Interface
– speci fies locatio n, type, and format
of any LLC 2 interfaces.
FConfigure Connec tions a nd Routing Paths
AConfigure 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.
BConfigure 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.
CConfigure 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.
DConfigure IP Route
EConfigure 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.
FConfigure 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.
HConfigure Telephone Number
– Cha pter 7 (trunk), Chapter 9 (X.25).
Numbers used by all V. 25bis mode ms on the networ k.
IConfigure 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.
HChange 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 Configuration3-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 configura 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 proceeding 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 connected 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-4FR X8 000 3 .0 User Gu i de, Rev 02
Not in Datab ase
. To minimize occur-
Loading...
+ 438 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.