1. Manuals
  2. Brands
  3. Cabletron Systems Manuals
  4. Network Hardware
  5. Netlink FRX4000
  6. User manual

Cabletron Systems Netlink FRX4000 User Manual

Frame relay access products
Hide thumbs Also See for Netlink FRX4000:
1
2
3
4
Table Of Contents
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
Table of Contents

Advertisement

Quick Links

Download this manual See also: Reference Manual, Maintenance Manual
FRX
TM
Frame Relay Access Products
FRX
4000
FRX
6000

User Guide

For Release 4.0
The Complete Networking Solution
TM
09-41-06-162-01

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Netlink FRX4000 and is the answer not in the manual?

Questions and answers

Related Manuals for Cabletron Systems Netlink FRX4000

Summary of Contents for Cabletron Systems Netlink FRX4000

  • Page 1: User Guide

    Frame Relay Access Products 4000 6000 User Guide For Release 4.0 The Complete Networking Solution 09-41-06-162-01...

  • Page 3: Statements Of Compliance

    Cabletron Systems reserves the right to make changes in specifications and other information contained in this document without prior notice. The reader should in all cases consult Cabletron Systems to determine whether any such changes have been made. The hardware, firmware, and/or software described in this manual is subject to change without notice.

  • Page 4: About This Manual

    This manual supplements screen prompts and menus as an aid in configuring the database and performing system operations on a Netlink FRX4000 or FRX6000. Before using the manual, you should be familiar with FRX hardware, as well as the protocols (frame relay, IP, SNA, etc.) you will be using.

  • Page 5: Table Of Contents

    Chapter 3 Introduction to Database Configuration Chapter 4 Configuring Node-Wide Default Parameters Chapter 5 Configuring Cards and Protocols Introduction to Netlink FRX4000 and FRX6000... 1-1 Multiprotocol Support... 1-2 Management Functions... 1-2 Hardware Overview ... 1-3 FRX4000... 1-3 FRX6000... 1-4 Quick Start... 2-1 Port Assignment Worksheets ...
  • Page 6 Translation Template Parameters ... 8-30 Replacing Called/Calling Address or User Data ... 8-30 Replacing Protocol ID ... 8-31 Replacing Facilities ... 8-31 Translation Examples ... 8-32 Testing a Translation Template ... 8-32 Configuring X.25-to-X.25 PVCs ... 8-33 FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 7 X.25 PVC Parameters ... 8-34 Chapter 9 Configuring SNA Introduction ... 9-1 Required Configuration ... 9-3 Configuring an SNA Port ... 9-4 SNA Port Parameters ... 9-6 Configuring Subscriber IDs... 9-14 Subscriber Parameters... 9-15 Configuring a Hunt Group for SNA Subscribers... 9-17 Configuring LLC2...
  • Page 8 Trap Routing Parameters ... 16-5 Configuring a Model Number ... 16-6 Remote Control ... 18-1 Remote Control from an FRX4000/6000 ... 18-2 Remote Control via an Async PAD Port ... 18-3 Transferring Files and Updating Software ... 18-4 Remote File Transfer ... 18-4...
  • Page 9 Remote Software Update ... 18-5 Backing Up and Restoring Files... 18-6 Database Backup and Restore... 18-6 Copying an FRX4000 Directory to/from a PC ... 18-8 FRX4000 Local File Backup and Restore ... 18-9 Enable/Disable Operations ... 18-12 Disabling and Enabling Ports ... 18-12 Quiescing and Unquiescing Ports ...
  • Page 10 X.25 Codes ... B-2 SNA Codes ... B-4 Codes Specific to Cabletron Frame Relay Access Devices... B-4 Local NetView Access ... C-2 Supported Commands ... C-3 Display Commands... C-3 Vary Commands ... C-4 Modify Commands ... C-4 FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 11 Configuration Example 2... 3-3 Configuration Example 3... 3-3 Local FRX4000/6000 in Configuration Example 3... 3-4 Remote FRX4000/6000 in Configuration Example 3 ... 3-5 Configuration Example 4... 3-8 Node Defaults Configuration Screen 1... 4-1 Serial Ports on an FRX4000 ... 5-2 Protocol Configuration Menu for FRX4000...
  • Page 12 Bridge MAC Filter Configuration Screen ... 15-7 Typical Bridge Filter Applications Record ... 15-11 Bridge Ports Display... 15-12 Bridge Port Record Example ... 15-13 SNMP System Defaults Menu... 16-2 SNMP Community Table Menu... 16-3 SNMP Trap Routing Menu... 16-4 FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 13 17-1 Main Menu... 17-1 18-1 On-Line Port Operations Menu ... 18-12 18-2 On-Line SDLC PU Operations Menu... 18-14 18-3 IP Ping Connectivity Test Menu... 18-15 18-4 Ping Example... 18-16 19-1 Node Status Display ... 19-1 19-2 Port Status Display ... 19-2 19-3 Virtual Connections Display on Frame Relay Port ...
  • Page 14 MAC Address Conversion... 3-6 Node Defaults Parameters ... 4-3 NetView Parameters ... 4-7 FRX4000 Protocol Parameters ... 5-3 LAN Card Parameters on FRX4000... 5-7 FRX6000 RLP Parameters ... 5-10 LAN Card Identification in FRX6000... 5-14 LAN Card Parameters on FRX6000... 5-15 Bandwidth Allocation Group Parameters ...
  • Page 15 Bridge NetBIOS Filter Parameters ... 15-10 15-7 Bridge Filter Applications Parameters... 15-11 15-8 Bridge Port/LLC2 Interface Parameters ... 15-13 16-1 SNMP System Defaults Parameters ... 16-2 16-2 Community Table Parameter ... 16-4 16-3 Trap Routing Parameters ... 16-5 18-1 FRX4000 Database Files ... 18-9 xiii...
  • Page 16 FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 17: Section I

    Section I Getting Started...

  • Page 19: Chapter 1 Product Overview

    FRX4000 and FRX6000 are generally used to provide concentration and access to remote devices. FRX4000 is a stand-alone device used where eight serial interfaces or fewer are required. FRX6000 is a larger stand-alone device supporting up to sixty-four serial interfaces, and can function as a central-site device for remote FRX4000s, Frame Relay Modules (FRMs), and/or SmartSwitch 1800s.

  • Page 20: Multiprotocol Support

    SNA/SDLC SNA/LLC2 Bridging Async Each FRX4000 includes frame relay, SDLC, and SNMP, plus whatever additional protocols were purchased with the device. The software for all of the listed protocols is included with every FRX6000. Management Functions The FRX4000 and FRX6000 support the same management functions: Local SNMP agent, with Sets from network manager on some MIB variables Manageable via Cabletron’s Spectrum®...

  • Page 21: Hardware Overview

    Four RS-422 ports (available by special request), supporting RS-449 and X.21 interfaces, in any combination (via cables) Each of the serial ports supports any of the protocols that are installed in an FRX4000. Each FRX4000 contains software for frame relay, SDLC, SNMP and any additional protocols that were purchased with the device.

  • Page 22: Frx6000

    Depending on the number of RLPs, an FRX6000 can contain one or two LAN cards (in any combination). Each LAN card supports one LAN interface. Chassis The 19-inch rackmount chassis includes: 1.2GB hard disk 3.5" high-density diskette drive Two COM ports Parallel port VGA port Keyboard port FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 23: Operator Interfaces

    Operator Interfaces Installation of FRX6000 software into a node, generally done before the node ships to the customer, requires a directly connected keyboard and monitor. Once the node has been installed and configured, it can function with no operator interface. However, configuration, file copy (backup, restore, transfer, etc.), and monitoring operations require a keyboard and screen, which can be in any of several forms.

  • Page 25: Chapter 2 Getting Started

    The installation documentation that is shipped with each unit describes the procedure for connecting to an FRX4000/6000 from a local or remote keyboard and video device. Once this has been done, the FRX device must be customized for the devices to which it will connect, the traffic it will receive and transmit, and various operating parameters that can be set to your specific needs.

  • Page 26: Port Assignment Worksheets

    (This does not apply to a DSU or LAN port.) The protocols that can be assigned to ports depend on the model of FRX4000 and the options that were purchased. All possible protocols are listed below: Note that LAN protocols (IP, IPX, Bridge, LLC2) are also assigned to physical frame relay ports via interface records that map the protocols to the physical ports.

  • Page 27: Frx6000

    FRX6000 Figure 2-2 shows the locations of the physical ports on an FRX6000 RLP. An FRX6000 can contain up to eight RLPs, numbered (via switches) 0–7. When an FRX6000 is shipped from Cabletron, all installed RLPs are numbered consecutively (starting with RLP 0), right to left, as viewed from the rear of the FRX6000. The above example shows LIC 1 as V.35, RS-232, or RS-422, and LIC 2 as T1 or E1.

  • Page 28: Frx6000 Port Assignments

    Table 2-2 lists all possible physical ports on the FRX6000. Card RLP 0 RLP 1 RLP 2 RLP 3 RLP 4 continued on next page Table 2-2 FRX6000 Port Assignments Port Interface Protocol Connected Device FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 29 Card RLP4 (contd.) RLP 5 RLP 6 RLP 7 LAN 0 LAN 1 Physical interface, determined by the LIC and attached cable (except T1 and E1 LICs, which do not include cables). Possible interfaces (with LICs in parentheses) are: V.35 (V.35), RS-232 (RS-232), RS-449 (RS-422), X.21 (RS-422), RS-530 (RS-422), T1 (T1), or E1 (E1).

  • Page 30: Logging Into The Main Menu

    Link_disable Operational F1: Login Figure 2-3 Port Status Display This example shows an FRX6000 display. On an FRX4000 display, there is no column, since the FRX4000 has no RLPs. identifies the node under control of the keyboard and screen. Node Name...

  • Page 31: Reviewing Boot Messages

    RLPs in the node. If there is an error reported, the data may aid in fixing the problem. If an FRX4000/6000 is shut down, then rebooted, the existing BOOTRPT.TXT file will be renamed BOOTBAK.TXT, and a new BOOTRPT.TXT will be created.

  • Page 32: Moving Through The Menus

    System memory values are described on page 6-3 for Ports. [F3] repeatedly [F3] . Pressing in response to this Option: on an async ter- Database System Memory before [F7] page 4-2 for Node Defaults FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 33 F4: Exit menu Exit Menu 2-3). To return to the menu, you must enter the node's password. (This feature is for security, to protect menu-level operations from unauthorized access.) Delete Record port number, containing all the default values, will remain in the database. Clear Max Stats from the display (restarting them at the current values).

  • Page 34: Function Keys On An Ascii Terminal

    (under "Maps to:") is an escape character followed by an ASCII Keyboard Maps to: [PF1] ^[OP [PF2] ^[OQ [PF3] ^[OR [PF4] ^[OS ^[Ou ^[Ov ^[Ow (comma) ^[Ol (period) ^[On ^[OA ^[OB [F3] [Enter] FRX4000/FRX6000 4.0 User Guide, Rev 01 [F7]...

  • Page 35: Setting The Date And Time

    This operation allows changing one or both, to assure that all devices in a network are synchronized. Press date and time as currently recognized by the FRX4000/6000 will be displayed, and you will be asked: to leave it as is. If changing the date, enter the correct information, noting the [Enter] values in Table 2-3.

  • Page 36: Stopping Operation

    To reboot from within the menu level, press Shutting Down To shut down an FRX4000 or FRX6000, simply switch it off. What Next? Once you are familiar with the menus and how they work, proceed to Section II to con- figure the database.

  • Page 37: Configuration

    Section II Configuration...

  • Page 39: Introduction To Database Configuration

    Each database file contains defining parameters for a specific component; for example, physical ports, subscriber IDs, or IP interfaces. Before an FRX4000 or FRX6000 can properly operate, all necessary database param- eters must be configured. The necessary configuration depends on the installed hardware, the routing and access protocols that will be used, and the devices that will be connected to ports in the FRX.

  • Page 40: Configuration Examples

    Optional SVC subscriber records (static routes) for any attached X.25 DTEs. These are needed to identify the attached DTEs’ X.121 Calling Addresses. If an X.25 Call Request is received from the WAN link, the FRX4000/6000 needs to know where to route the call.

  • Page 41: Frame Relay Pvc Passthrough

    6000 port to the 3174 as logical DCE, and the port to the frame relay switch as logical DTE. Frame relay PVC FRX4000/6000. The DLCIs are defined in the PVC record; if rate control (CIR, relay Port record. LLC2 PUs over Frame Relay to AS/400...

  • Page 42: Local Frx4000/6000 In Configuration Example 3

    LAN card number, which is always Terminated LLC2 Host interface to which the 5494 device will transmit. Note that the remote FRX4000/ 6000 must have a corresponding originated LLC2 host. For this example, assume the host number is Ethernet LLC2 Interface LAN.

  • Page 43: Remote Frx4000/6000 In Configuration Example 3

    Local Subscriber ID (shown later in this list). Source MAC Address Mask – 40000000 the FRX4000/6000 will use to send frames to the AS/400. The last four digits are for the first 57 Host SAPs (service access points) used to 0000 connect to the host.

  • Page 44: Key Points

    Be aware that when configuring these records, LAN IDs must be entered in hex. Also note that, other than the matching IDs on each originated/terminated interface pair, each LAN ID must be unique within the network on which the FRX4000/6000 will operate.
  • Page 45 PU 2.0 or PU 2.1) to 5294 and 5394 PU1 controllers. However, when this is done, the ACTPU is not spoofed internally, and is sent to the remote controller. The FRX4000/ 6000 cannot accept and respond, and the controller and AS/400 will go into error mode.

  • Page 46: 3X74S/Sdlc Over Frame Relay To Sna Host

    SNA on the RLP containing the port to the FEP. If LLC2 is not already configured in the FRX4000/6000, configure it on the same RLP. (Frame relay must be configured on each RLP that will use it, but LLC2 is configured on one RLP only.
  • Page 47 Be aware that when configuring these records, LAN IDs must be entered in hex. Also note that, other than the matching IDs on each originated/terminated interface pair, each LAN ID must be unique within the network on which the FRX4000/6000 will operate.

  • Page 48: Producing A Configuration Report

    Configure Trap Routing Configure Model Number at the Reports Menu (or at the Reports Menu (or – (Chapter 2) allows setting a correct time/ – (Chapter 16) identifies the SNMP FRX4000/FRX6000 4.0 User Guide, Rev 01 from the from the...
  • Page 49 Introduction to Database Configuration Configure IP/LLC2/BRIDGE/IPX Default Parameters Configure IP Node Defaults FRX4000/6000 will act as an IP gateway and which version of RIP will be used. Configure Bridge/LLC-2 Node Defaults parameters that will be used internally by the node to identify a virtual bridge that will connect the LLC2 function to LAN interfaces and frame relay PVCs.
  • Page 50 Bridge Ports Chapter 15) specifies location, type, and format of any bridge or LLC2 interfaces. Review IPX Interfaces any IPX interfaces (see below) configured in the FRX4000/6000. Configure IPX Interfaces interfaces. Identifies type (X.25, Ethernet, etc.) and operating parameters. (Chapter 10)
  • Page 51 – (misc. chapters) displays information on any subscriber IDs (see below) configured in the FRX4000/6000. Configure Subscriber IDs identifies end users of the FRX4000/6000, and specifies parameters for redirecting traffic to other ports. Review Abbreviated Addresses on any abbreviated addresses (see below) that are configured.

  • Page 53: Chapter 4 Configuring Node-Wide Default Parameters

    Configuring Node-Wide Default Parameters Node Defaults Node Defaults are a set of parameters that identify an FRX4000 or FRX6000 for pur- poses of remote control, software updates, file transfers, and/or alarm reporting to or from a remote FRX, SmartSwitch 1800, or FRM. The Node Defaults file also contains information that defines a connection to a NetView manager device.

  • Page 54: Database And System Memory Values

    After making any changes, be sure to press system memory. Otherwise, the changes will not take effect until the next re-boot of the FRX4000/6000. Although the entries for the various passwords appear blank, default values exist; if you change one, be sure you do not duplicate an existing password.

  • Page 55: Node Defaults Parameters

    Node Name is displayed at the upper right of the screen when the device is being controlled by the "local" keyboard and monitor. (If the local operator is controlling a remote FRX4000/ Configuring Node-Wide Default Parameters Table 4-1 Node Defaults Parameters Remember that the software sees uppercase as different from lowercase.
  • Page 56 Cabletron frame relay access device, or async terminal will be used to take control of the local FRX4000/6000 (via a physical or logical port in the local device). The ID will be checked against the called address fields of incoming Call Requests.
  • Page 57 7 or 8 per character. Collecting Node is an FRX4000/6000 to which alarms are sent from other Cabletron frame relay access devices. Any of these devices can be a collecting node; which nodes send their alarms to a collecting node is determined by the the other nodes;...
  • Page 58 (See that entry below and Min Congestion is a percentage of the FRX4000/6000 alarm buffer. As long as the percent of the buffer that is full is below this level, alarms will always be placed into the buffer. (See "Alarm Periodic Status Timer sets the frequency with which the FRX4000/6000 will send a "heartbeat"...

  • Page 59: Netview Parameters

    IDNUM Priority Bandwidth Allocation Group Name is the VTAM PU name that will identify the FRX4000/6000 as a NetView Service Point. Local Subscriber ID is a subscriber address for the local end of an LLC2 session established for a NetView connection.
  • Page 60 Local SAP Address is a service access point (SAP) address used to identify the FRX4000/6000 to a NetView host. This parameter is relevant only in a connection to a 3174 or AS/400- type setup where a specific source SAP address is required. If the session will be run over a native LLC2 frame relay interface, the parameter will be ignored.
  • Page 61 Priority prioritizes NetView traffic among all intra-nodal traffic; the higher the number, the higher the priority. (This priority has no effect on traffic exiting an FRX4000/6000.) Priorities are configured on all logical interfaces that use a physical frame relay port.

  • Page 62: Warning Messages

    ERRMSG.TXT can not be found. (This may happen if a software update was not correctly installed.) To correct this on an FRX4000, the file can be transferred from a remote FRX4000/6000 or copied from a locally attached PC...

  • Page 63: Configuring Cards And Protocols

    RLPs (RISC-based line processor cards), and on one or two four-port Line Interface Cards (LICs) mounted on each RLP. In an FRX4000, the functionality of one RLP and four serial ports is built into the system board (motherboard), and four (or one, if T1 or E1) more serial ports can be added by installing an LIC.

  • Page 64: Serial Ports On An Frx4000

    For reference, the following figure shows the ports on an FRX4000. Optional CSU/DSU Port To display a table of memory usage, press information, in conjuction with information in the release notes, can help in planning the number of protocols to run.

  • Page 65: Frx4000 Protocol Parameters

    [F10] , press Reboot the Node? restart [Enter] Table 5-1 FRX4000 Protocol Parameters Valid Values None, X.25, FR (frame relay), Async, SDLC, BSC-I, BSC-B, IP, SNMP, RIP, LLC2, IPX, NVSP (NetView Service...
  • Page 66 On, Off On, Off All of these might not be available on an FRX4000. It depends on which protocols were purchased. Also, note the guidelines in the explanation. X.25 is always loaded, and is not a configurable option. This prevents the possiblility of deleting X.25, which is a nec- essary protocol for use by internal SmartSwitch traffic.
  • Page 67 Line Build Out is based on the distance from the FRX4000 to the external T1 device, and is normally dictated by the telephone company that supplies the line. Clocking determines whether clock will be generated by the FRX4000 T1 port (...

  • Page 68: Lan Port

    A, B, C, and/or D will be used in timeslot 16 when (Channel) Chnl LAN Port Each FRX4000 contains a LAN port, either Ethernet or Token Ring (depending on the model). To configure the port, press Signaling Associated at the Port Configuration Menu.

  • Page 69: Frx6000

    FRX6000 and 9W004, both of which contain one or (FRX6000 only) two LAN cards. Table 5-2 LAN Card Parameters on FRX4000 Token Ring FRX4000 only. until the node is rebooted, at which time the protocol will be displayed...

  • Page 70: Frx6000 Rlp, Lics, And Cables

    Figure 5-4 FRX6000 RLP, LICs, and Cables at the RLP Configuration Menu. (RLP numbers are determined by switch Switch Switch 7 is Off for 8 MB RLP, On for 4 MB RLP. RLP Cable FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 71: Rlp Configuration Menu For Frx6000

    To add or remove a protocol, press the letter corresponding to the protocol number. The protocol in the (See Table After all desired changes have been made, press the 9W004 as follows: 1. Press 2. When asked: 3. Type Configuring Cards and Protocols RLP Configuration RLP: * Status: Installed...

  • Page 72: Frx6000 Rlp Parameters

    (only if Line Ser- Full: n/a vice Fractional) HDB3 G.704 Full G.703 Slave (only if Fractional: 1–30 Line Ser- Full: n/a vice Fractional) (only if Fractional: 1–30 Line Ser- Full: n/a vice Fractional) Common FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 73 RLP Type Cannot be changed if the RLP is installed. If it is not installed, the value changes each time you press Line Interface Card 1, 2 contain the circuitry for the physical ports of an RLP. If the card is not installed, the value changes to the next one in the list each time you press Once the node is booted with the card installed, the software will read the LIC type, and this parameter cannot be changed.
  • Page 74 E1 port ( device ( Slave Base Chl Speed determines the line speed over each channel. 5-12 ) or the remote Master ) or the remote Master FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 75 Starting Chl Number determines the lowest channel number that will be used. Num of Chnls is the number of channels that will be used on the T1 line. CRC-4 Disabled disables (if Chnl Signalling is the mode of the CEPT interface. Ntnl Use Bit "n"...

  • Page 76: Lan Cards

    PROTOCOL.INI and the LAN configuration part of CONFIG.SYS. Interface Number at the Bindings = SMCMAC8001 SMCMAC8001,SMCMAC8002 SMC8100_NIF SMC8100_NIF,SMC81002_NIF SMC8100_NIF,SMCMAC8001 SMCMAC8001,SMC8100_NIF NLK_TOK NLK_TOK,NLK_TOK2 NLK_TOK,SMCMAC8001 SMCMAC8001,NLK_TOK at the Port Configu- , type [0] [Enter] [1] [Enter] FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 77: Lan Card Configuration Screen

    Press [F7] LAN Card Parameters Parameter Type Locally Admin. MAC Addr Type is the type of LAN card. Locally Admin. MAC Addr is a MAC address that will override the universally administered MAC address. If all zeros are specified, the universal address will be used. Under most circumstances, this parameter should be left at the default setting.

  • Page 79: Chapter 6 Configuring Physical Ports

    Locations of Physical Ports FRX4000 Four serial connectors in the FRX4000 reside on the system board. An optional expansion card offers one or four more ports, depending on the type of card. The physical interfaces are as follows: Ports 0 and 1 are RS-232.

  • Page 80: Frx6000

    I/O Cables to Modems and User Devices Figure 6-2 Physical Ports on FRX6000 RLP LIC 2 Ports 0-3 Ports 4-7 Ports 0-3 Ports 4-7 Ports 0-3 Ports 4-7 Port 0 Port 4 Port 0 Port 4 RLP Cables FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 81: Database And System Memory Values

    Database and System Memory Values Two sets of values exist for Port parameters: Database values exist in the software, and are recorded as System Memory values when the node is booted. If the port type is the same in both sets of values, both sets will be displayed. Any change you make will be recorded as a Database value, and will be copied to the System Memory side only if you press saved to the database until you press...

  • Page 82: Default Configuration Screen For New Port

    – Chapter 9 – Chapter 10 – Chapter 11 – Chapter 12 Ports" on page 8-14. Rmtid=nodexyz Link_disable System Memory X.25 V.35 9600 bps 2000 1000 from Main Menu [A],[C],[A] for FRX4000 ports UNIVERSAL FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 83: Chapter 7 Configuring Frame Relay

    Introduction Frame relay ports in the FRX4000 and FRX6000 are used to carry frame relay traffic, as well as other protocols encapsulated in frame relay (per RFC 1490, via logical X.25 ports over frame relay). A frame relay port can act as physical DCE (non-T1/E1 port only), connecting to end-user devices, or DTE, connecting to a network or frame relay PVC.

  • Page 84: Dlci Sharing

    Frame Relay Backup Frame relay virtual-circuit backup in the FRX4000/FRX6000 provides frame relay DLCIs with automatic backup protection in the event of LMI loss or port failure. (A DLCI is considered down/inactive if level 1 is down. If LMI is used, the DLCI is also considered inactive if not reported as active in a Full Status Message from the DCE.)

  • Page 85: Frame Relay Backup Examples

    Node 1 0,17 Figure 7-1 Frame Relay Backup Examples Although each example shows an FRX4000-to-FRX6000 connection, connections can be between any two Cabletron frame relay access devices in the family of FRX, SmartSwitch 1840, and FRM. In an FRX6000, the primary and backup DLCIs must be on the same RLP, or a PVC must be configured between the DLCIs.
  • Page 86 B Enable Backup Protocol?: Y E For Backup use Only: N (Not necessary because protocol is from Main Menu): [A], [F], [B] ; however, the setting 0–65535 on the primary {RLP 0/ Switchover Timer FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 87: Required Configuration

    1. The "Other Device" must be configured to recognize both the primary and backup connections. Required Configuration To run frame relay in an FRX4000 or FRX6000, make sure the following are properly configured: Node which protocols will be run in the node. See Chapter 4.

  • Page 88: Configuring Bandwidth Allocation Groups

    (frame relay PVCs into and out of the FRX node, internal PVC between the two frame relay ports). (Although the FRX4000 and FRX6000 support bandwidth allocation, routers and FRADs that initiate frame relay passthrough do not.) Be sure you fully understand the needs of the users of the node before assigning allocation groups;...

  • Page 89: Bandwidth Allocation Group Parameters

    Pressing contains groups 9–12, and Page 4 contains groups 13–16. Bandwidth Allocation Group Parameters Explanations of the parameters follow the table. Parameter Dynamic Optimization Group "n" Percentage Group "n" Excess Priority Group "n" Use Excess Burst Group "n" Percentage is a percentage of bandwidth that will be dedicated to traffic in a group if necessary. If the traffic does not require the full allocation, unused bandwidth will be available to other groups.

  • Page 90: Configuration Example

    Discard Eligibility bit set, which allows packets to be discarded if necessary.) ) allow traffic that falls into the will be buffered in the FRX4000/6000. Table 7-2 Bandwidth Allocation Example Percentage Excess Priority Use Excess Burst Logical Ports &...

  • Page 91: Configuring Frame Relay Ports

    M T1 Link Integrity Timer N T2 Polling Verification Timer O Additional Parameters Option: Figure 7-3 Frame Relay Port Screen 1 The above is an example of an existing frame relay port. On an FRX4000 with (item B) configured as Physical Port Interface different.

  • Page 92: Reviewing Dlci Configuration (Figure 7-4, Item C)

    RPrt RDLCI SOT PgUp, PgDn, F2:Review All DLCIs, F3:Exit Figure 7-5 DLCI Configuration Review Screen Node Name=node_xyz Linkup System Memory at the screen in Figure Node Name=node_xyz OBC OBE BECN Pri Proto SBT TTH FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 93 The first line of parameters applies to all DLCIs on the port (or in the node if pressed). The second line exists only for DLCIs configured as primary DLCIs in backup configurations. In the example in parameters are listed in The parameters in the first line are: ICIR OCIR...

  • Page 94: Configuring Dlci Parameters (Figure 7-4, Item D)

    7-4), press Figure 7-4 and, when .) This will display a screen Node Name=node_xyz (Figure 7-7) will delete the screens—Figure 7-3 FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 95: Viewing Learned Dlcis (Figure 7-4, Item E)

    Viewing Learned DLCIs (Figure 7-4, Item E) If the port is a logical DTE, a list of all DLCIs (extracted from LMI/AnnexD frames) can be displayed by pressing by three columns:— Configuring Frame Relay Frame Relay DLCI Configuration (screen 2 of 2) Port DLCI A Backup Group Number...

  • Page 96: Frame Relay Port Parameters

    If this port will connect to a frame relay network, set one end of a frame relay backup connection must be configured as logical DCE. Not applicable to T1/E1 ports or FRX4000 DSU ports. This parameter is relevant only if...

  • Page 97: Frame Relay Dlci Parameters

    Selecting this parameter will display a list of valid protocols. An FRX4000 port can be configured as any WAN protocol loaded in the device. An FRX6000 port can be configured as any WAN protocol configured on this port's RLP.
  • Page 98 DTE, specify the line speed that matches (as closely as possible) that of the device connected directly to the port. Selecting this parameter for an FRX4000 DSU port will toggle between the two valid values of This parameter cannot be selected on a T1 or E1 port;...
  • Page 99 Maximum Bytes per Frame specifies the maximum size of any I-frame (Information frame) that can be transmitted or received on the port. Logical DCE defines the port as (if the opposite of the device at the other end of the connection. Logical and physical DCE/DTE are independent of each other (e.g., a port can be a physical DCE and logical DTE).
  • Page 100 ) is incoming or outgoing (depending on the parameter) the maximum amount of data that the network agrees to transfer under normal conditions within the time period defined by B turned on, and will be tracked by the FRX4000/6000 statistic 7-18 before the logical DCE will be declared...
  • Page 101 ) is the incoming or outgoing (depending on the parameter) maximum amount of data in excess of the during the time interval used for the exceeding this value will be buffered in the FRX4000/6000, and any incoming data exceeding the value will be discarded. BECN Recovery Count is a method of controlling the rate of return to maximum traffic flow after it has been reduced due to congestion.

  • Page 102: Configuring Frame Relay Pvcs Across The Node

    Configuring Frame Relay PVCs Across the Node An FRX4000 or FRX6000 PVC is a "permanent" connection between two physical ports in a node. This allows communication between the attached devices as soon as they are powered up, without the need to first establish a connection.

  • Page 103: Frame Relay Pvc Parameters

    Primary/Secondary RLP It does not matter which end of the PVC is configured first. Table 7-5 Frame Relay PVC Parameters (FRX6000 only) Node Name=node_xyz from Main Menu [A],[D],[E],[B] entry on an FRX4000. Valid Values Default Value 0–9 0–31 characters none 16–991 0–7...

  • Page 104: Configuring Frame Relay Backup Groups

    Main Menu). [A], [E], [A] at the Frame Relay Backup Groups Configu- Frame Relay Backup Group Number ) will be enforced, frame relay Port record. at the Frame Relay Backup Groups Con- 1–255 FRX4000/FRX6000 4.0 User Guide, Rev 01 . (The...

  • Page 105: Backup Group Parameters

    ProtEnab enables (if only if) the remote device is an FRX4000/6000 with the backup protocol enabled on the remote DLCI connected to this backup group entry. The remote node must be the same one to which the primary DLCI was connected, and the remote node's backup DLCI must be on the same RLP as its primary DLCI.
  • Page 106 7-24 FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 107: Chapter 8 Configuring

    Introduction An FRX4000/6000 X.25 port can connect to an X.25 DTE or an X.25 network. This allows the node to transmit X.25 traffic, as well as IP and IPX (encapsulated per RFC 1356), and SNA (per QLLC). X.25 support includes: Full compliance with CCITT Recommendation X.25...

  • Page 108: Required Configuration

    8-13.) The following figure is an example of an existing port. (Chapter 5), and Protocol (Chapter at the Port Configuration Menu (or . (The default is 0–7 . (The default is 0–7 FRX4000/FRX6000 4.0 User Guide, Rev 01 [A], [C], page 8-6...

  • Page 109: X.25 Port Screen 1

    CSU/DSU Operating Mode After making any changes, be sure to press system memory. Otherwise, the changes will not take effect until the next re-boot of the FRX4000/6000. at the screen in Figure 8-1 will display a second screen, and pressing Table 8-1 (on page 8-6).

  • Page 110: X.25 Port Cug Parameters

    CUG to be deleted. will display a list of all CUGs configured for this port, along with their Incoming Access Allowed Node Name=nodexyz System Memory ), that will be associated with the index. Table 8-2.) FRX4000/FRX6000 4.0 User Guide, Rev 01 ). The...

  • Page 111: Configuring A Network Trunk

    Configuring a Network Trunk A network trunk is a link between Cabletron frame relay access devices (FRX4000, FRX6000, SmartSwitch 1800, FRM), over X.25. Other ports in the node can be assigned to a "trunk group," which will cause those ports to be disabled if the network trunk is not operational (and enabled when the trunk becomes operational).

  • Page 112: Configuring A Dial Port

    (sec) Node Name=nodexyz System Memory Dial In Table 8-3. Valid Values Default Value X.25 X.25 see explanation see explanation FRX4000 – see explanation FRX6000 – 9600 1–7 1–127 0–20 2000–15000 2000 0–5000 1000 1–60 FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 113 Selecting this parameter will display a list of valid protocols. An FRX4000 port can be configured as any WAN protocol loaded in the device. An FRX6000 port can be configured as any WAN protocol configured on this port's RLP.
  • Page 114 DTE, specify the line speed that matches (as closely as possible) that of the device connected directly to the port. Selecting this parameter for an FRX4000 CSU/DSU port will toggle between the two valid values of This parameter cannot be selected on a T1 or E1 port; rather, the line speed is deter-...
  • Page 115 T1 Retransmit Period is the length of time before re-transmission of an I-frame if the previous transmission is not acknowledged. If the period expires, the FRX4000/6000 software will reset the timer and transmit a supervisory frame demanding immediate acknowledgment. Also,...
  • Page 116 , the default packet and window sizes will be used. If set to ) will be used. If set to Maximum Throughput Class means that the External Lowest Incoming Lowest 2-Way through 4095 , any throughput class FRX4000/FRX6000 4.0 User Guide, Rev 01 , the...
  • Page 117 included in a call packet will be used. (If a class for either direction is not included, its default value will be used.) Local Charging Prevention prevents calls (if with Reverse Charging specified will be rejected; outgoing calls will have Reverse Charging inserted if it is not already in the call packet.

  • Page 118: X.25 Port Cug Parameters

    Restart Retry Count expires, restart and recovery procedures should be ini- Reset Retry Count expires, recovery procedures should be initiated. Clear Retry Count Table 8-2 X.25 Port CUG Parameters Valid Values 0–99 Default Value FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 119: Dial Port Parameters

    Preferential CUG is a default CUG for the port. Any calls that do not specify a CUG will default to this one if Preferential CUG Flag Incoming Access Allowed determines whether this port will be allowed to receive calls from outside its CUGs. Outgoing Access Allowed determines whether this port will be allowed to make calls outside its CUGs.

  • Page 120: Configuring Logical X.25 Ports

    Configuring Logical X.25 Ports To display all logical ports configured on the FRX4000/6000, press from the Main Menu. This will display a list of all PVCs and logical ports. To configure a logical port, press from the Main Menu. When prompted, enter:...

  • Page 121: Logical Port Parameters

    If you want to configure one or more closed user groups (CUGs) for the port, press at the third screen. (Otherwise, you do not need to configure anything on the fourth screen.) Logical Port Parameters Parameter Mapped DLCI Number Blocked Port Flag Priority Bandwidth Allocation Group Encapsulation Method...

  • Page 122: Logical Port Cug Parameters

    X.25 and frame 4096 will not cause a problem, since larger frames Valid Values Default Value 0–99 See explanation See explanation See explanation ) (only if the physical port is FRX4000/FRX6000 4.0 User Guide, Rev 01 [B], [B], [A]...
  • Page 123 Bandwidth Allocation Group assigns the logical port to one of sixteen groups whose parameters regulate bandwidth usage by outgoing traffic on the physical link. See cation Groups" on page 7-6. Encapsulation Method is the method by which traffic over the logical port will be enveloped within frame relay frames for transmission.
  • Page 124 Reverse Charging, the ) DTE. The other end of the connection Lowest Incoming Lowest 2-Way through 4095 is selected, a is selected, the default ( FRX4000/FRX6000 4.0 User Guide, Rev 01 Maximum...
  • Page 125 Fast Select Acceptance authorizes transmission of incoming calls that request the X.25 Fast Select facility. Incoming Calls Barred is an X.25 facility that prevents transmission of incoming calls to this port. Outgoing Calls Barred is an X.25 facility that prevents transmission of outgoing calls from this port. Maximum Packet Size is the maximum data packet size that will be allowed to pass through this port.
  • Page 126 Reset Retry Count expires, restart and recovery procedures should be ini- Clear Retry Count Outgoing Access Allowed . A new port has CUG ). The CUG Incoming Access Allowed specified here. FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 127: Configuring Subscriber Ids

    Incoming Access Allowed determines whether this port will be allowed to receive calls from outside its CUGs. Outgoing Access Allowed determines whether this port will be allowed to make calls outside its CUGs. Add/Change CUG To configure a CUG, select this entry and, when prompted, enter: CUG Index, CUG number, any other requested information.

  • Page 128: Subscriber Addressing

    Main Menu [A],[D],[B] on an IP (over X.25) Source Subscriber 13), accept the default values for all param- on an IP (over X.25) Subscriber , which must be configured as the node and Table FRX4000/FRX6000 4.0 User Guide, Rev 01 8-6.

  • Page 129: Wildcard Addressing Example

    Wildcards in Subscriber Addresses Each subscriber is assigned to an FRX4000/6000 port, and more than one subscriber device can use a port. To eliminate the need to specify the complete ID of every sub- scriber on the port, the question mark and the asterisk can be used as “wildcard” char- acters.

  • Page 130: Hunt Group Example

    Search Order for Subscriber Addresses A subscriber address that includes a wildcard potentially matches more addresses than one with no wildcards. For example, the address Without a checking mechanism an address with no wildcards could be read as a match for an address with a wildcard, and sent to the wrong place.

  • Page 131: Subscriber Parameters

    The software does not verify that a specified RLP and port exist. Make sure the RLP is installed, and that both the RLP and port are configured in the database. will be as follows, giving Valid Values Default Value 0–31 characters none 0–3 0–9 FRX4000: FRX6000: Physical port: 0–7 Logical port: 8-63 valid address none page...
  • Page 132 Redirection Address 0,1,etc. are up to five subscribers that will be called according to the specified redirection option. The FRX4000/6000 can redirect an X.25 call to an alternate subscriber if the 8-26 ) all calls to Redirection Address 0 instead of the primary address. If...

  • Page 133: Configuring X.25 Address Translation Templates

    (See " .") Order The FRX4000/6000 will call each address in the list until one is reached. If Redirection but will start immediately with the first subscriber in the redirection list. Configuring X.25 Address Translation Templates The X.25 address translation function in the FRX4000/6000 provides automatic trans-...

  • Page 134: Backup Using Address Translation

    PDN-compatible called and calling addresses. Node 2 has a translation template defined to intercept packets with the PDN-com- patible calling address for node 1. It translates these into the FRX4000/6000-com- patible calling address for node 2. (The backup routing is transparent.) To display existing translation templates, press Templates Menu.

  • Page 135: Address Translation Template Screen

    To add or change a translation template, press Templates menu and enter: (FRX6000 only) Port Direction Template ID below), in the format: where: The fields must match the equivalent fields in the Call Request packet, but not neces- sarily literally—they can use wildcards. Configuring X.25 .

  • Page 136: Translation Template Parameters

    All wild cards are valid in the translation template, allowing one template to function for many calls. The FRX4000/6000 routes traffic based on the user data field if the present in the SVC routing table. The gateway also allows the include user data field operations.

  • Page 137: Replacing Protocol Id

    The matching procedure is described in the following example. Assume: The translation inserts literal digits original called address that match the fifth, sixth, and seventh characters of the Template ID ( have not already been changed ( characters. Therefore, the translation result is = Calling address.

  • Page 138: Translation Examples

    4-byte protocol ID. After you enter this information, the FRX4000/6000 creates a test packet and sends it through the translation process, and displays the results, as shown in the following example.

  • Page 139: Configuring X.25-To-X.25 Pvcs

    Configuring X.25-to-X.25 PVCs An FRX4000/6000 PVC is a "permanent" connection between two physical ports in a node. This allows communication between the attached devices as soon as they are powered up, without having to first make a call to establish a connection. X.25 PVC support includes X.25-to-X.25, and async-to-X.25 (described in...

  • Page 140: X.25 Pvc Parameters

    Node Name=nodexyz from Main Menu [A],[D],[E],[B] Valid Values Default Value 0–9 0–31 characters none 1–255 FRX4000: FRX6000: 0–7 128–4096 1–7 . Cannot be greater than the smaller 4096 specified on the ports for FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 141 PVC. Generally the same window size will be configured on the port at each end, as well as in the PVC. Configuring X.25 When configuring priorities, be careful to consider the types of traffic being routed on other connections in the FRX4000/6000. 8-35...
  • Page 142 8-36 FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 143: Chapter 9 Configuring Sna

    Introduction SNA support in the FRX4000 and FRX6000 includes SDLC for serial lines and LLC2 for LAN connections. SNA ports connect IBM hosts with PUs (physical units), over a frame relay (via RFC1490) or X.25 (via Annex G) network. SDLC-to-LLC2 and LLC2-to-SDLC conversion are performed for transmission over frame relay.
  • Page 144 (XPAD), which supports HDLC and any of its subset protocols, such as SDLC (IBM), LAPB (ISO), and BSC (bisync). LLC2 (Logical Link Control type 2) support in the FRX4000/6000 provides a local or remote connection over frame relay (via RFC1490) or X.25 (via QLLC) between two SNA devices, one attached to a LAN and the other attached to either another LAN or a frame relay-compliant SNA/APPN device.

  • Page 145: Required Configuration

    Required Configuration To run SNA in an FRX4000 or FRX6000, make sure the following are correctly con- figured: Node which protocols will be run in the node. See Chapter 4. RLPs Card(s) supporting the ports that will be the interfaces. See Chapter 5.

  • Page 146: Configuring An Sna Port

    Figure 9-2 SNA Port Screen 1 After making any changes, be sure to press system memory. Otherwise, the changes will not take effect until the next re-boot of the FRX4000/6000. Table 9-1 Additional SNA Port Parameters to display a list of configured PUs, or for point-to-point SDLC lines, and in series from the Main Menu.

  • Page 147: Sdlc Pu Subscriber Parameters Screen

    After entering a station address, a screen similar to the following will be displayed. If SDLC/LLC2 conversion will be done on the PU connection, specify in Figure 9-3, then press (If the PU is not part of an SDLC/LLC2 connection, you do not have to configure those parameters.) Configuring SNA SDLC PU Subscriber Parameters (screen 1 of 2)

  • Page 148: Sna Port Parameters

    8 characters none see explanation see explanation see explanation none 1–500 40–9999 2000 0–99 1–128 0–3 16–4096 (bytes) 1024 (none) 0–2 0xFF, 0x7E 0xFF 15–250 Full/Half Full is something other than (HPAD). FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 149: Sna Port Pu Parameters

    Selecting this parameter will display a list of valid protocols. An FRX4000 port can be configured as any WAN protocol loaded in the device. An FRX6000 port can be configured as any WAN protocol configured on this port's RLP.
  • Page 150 FRX4000 port 0 is always FRX4000 port 1 is DSU card is installed. FRX4000 ports 2 and 3 are determined by the attached cables: RS-232, V.35, RS-449, or X.21. FRX4000 ports 4–7 are determined by the expansion Line Interface Card (LIC) and attached I/O cables.
  • Page 151 No Data Poll Period is the time between polls by this TPAD port of its PU (physical unit) when the PU has no data to send. This parameter has no relevance on an HPAD port. No Resp Poll Period is the time between polls by this TPAD port of its PU when the PU is not responding. The TPAD will continue to poll at this interval up to the number of times specified by Maximum Retransmissions Maximum Retransmissions...
  • Page 152 SNA link is idle. Inactivity Timer determines how long the FRX4000/6000 will wait with no activity on the HPAD port before it will declare the port down. L1-Duplex determines level-1 signal operation on RS-232 ports.
  • Page 153 Remote Subscriber ID identifies the remote device. A figured for this ID. If the PU is one end of a connection to a logical X.25 port in the FRX4000/6000, this address must match a Subscriber ID configured for the logical port. Maxdata must correspond to the PIU size configured on the host (parameter MAXDATA of macro PU in VTAM).
  • Page 154 (If this LPDU is sent while the timer B'1.' when it receives one of these: B '1.' is not outstanding. B'1' .") FRX4000/FRX6000 4.0 User Guide, Rev 01 IDBLK IDNUM is not B'1' greater than the last N , provided a Command...
  • Page 155 A Supervisory LPDU with the P bit set to B'1,' to solicit remote link station status. Any Unnumbered LPDUs that were not responded to the first time they were sent. If acknowledgments/responses are still outstanding after declare the link inoperative. The value specified for layer (e.g., queuing).

  • Page 156: Configuring Subscriber Ids

    Menu. When prompted, enter a Subscriber ID of up to 15 digits. (ID conventions are described on Pressing ports. Pressing 9-14 "Configuring Bandwidth Allocation ) the FRX4000/6000 from returning an XID in response to a null XID. from the Main Menu). [A], [D], [A] page 8-22.) SVC Subscriber Maintenance...

  • Page 157: Subscriber Parameters

    Table 9-3 Subscriber Parameters RLPs and ports are configured in the database, and that they actually exist. Table Valid Values Default Value 0–31 characters none 0–3 0–9 FRX4000: FRX6000: 0–7 Physical port: 0–7 Logical port: 8-63 valid address none page 8-24), for the purpose 9-3.
  • Page 158 Redirection Address 0,1,etc. are up to five subscribers that will be called according to the specified redirection option. The FRX4000/6000 can redirect an X.25 call to an alternate subscriber if the original subscriber cannot be reached. (See " .") Order The FRX4000/6000 will call each address in the list until one is reached.

  • Page 159: Configuring A Hunt Group For Sna Subscribers

    Configuring a Virtual LAN ID A virtual LAN ID is normally assigned by a system administrator. The ID is used internally by the FRX4000/6000 to identify a virtual bridge that connects the LLC2 function to LAN interfaces. If LLC2 will run in the local node, press...

  • Page 160: Configuring Llc2 Hosts

    Configuring LLC2 Hosts Each SNA/LLC2 host device that will connect to an FRX4000/6000 running LLC2 must be configured in the database. To display any LLC2 hosts already configured for this node, press IP/LLC2/BRIDGE/IPX Default Parameters Menu (or Menu). This will list the hosts' MAC addresses and identify each LLC2 session as Originated in a Terminated session, the host accepts sessions destined for the address.)

  • Page 161: Llc2 Originated Host Configuration Screen

    Configuring SNA SNA LLC2 Originated Session Configuration (Screen 1 of 2) Host Number: 1 A Host MAC Address 0C005A123402 B Session Type Originated C T1 (100 msec) D T2 (msec) E Ti F N3 G Tw H N2 Priority Bandwidth Allocation Group K Routing Subscriber ID 1121000000* L Source MAC Address Mask...

  • Page 162: Llc2 Host Connections Screen

    Terminated session will not have columns E–J as shown, but instead will simply have column E, . In either case, selecting a sequence ( ) number will delete that line. Node Name=nodexyz MaxData MaxIn Del 00001 4105 00002 4105 00003 after selecting FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 163: Llc2 Host Parameters

    LLC2 Host Parameters Parameter Host MAC Address Session Type (100 msec) (msec) (sec) Priority Bandwidth Allocation Group Routing Subscriber ID Source MAC Address Mask On-Line Temporary Changes Connections Parameters HSAP Type Local Subscriber ID Remote Subscriber ID IDBLK IDNUM Maxdata MaxIn Configuring SNA Table 9-4 LLC2 Host Parameters...
  • Page 164 MAC address of the host or workstation to which an SNA/LLC2 device needs to connect. If the host will be attached via an Ethernet interface in the FRX4000/6000 and the remote device is attached via a Token Ring, or vice versa, this MAC address will be "bit-swapped"...
  • Page 165 is the Reply Timer, which is used by the local node to detect a failure by the remote station to send a required acknowledgment or response. The local node will start the timer when it transmits one of these: an Information LPDU (LLC protocol data unit). a Command LPDU with the P bit set to is already running, the local node will reset and restart it.) The node will reset...
  • Page 166 IDs, all of which must begin with the Source MAC Address Mask is used to identify the FRX4000/6000 to inbound frames from a local LAN in an Orig- inated LLC2 session. Source address masks and host MAC addresses are placed in a forwarding list that is checked by the software when a frame is received.
  • Page 167 Connections Parameters is simply a sequence number to allow selection of a line in the display. HSAP is the service access point (SAP) address used to connect to the host. This must match the SSAP (source SAP) in a frame received from the local LAN or the DSAP (desti- nation SAP) in a frame from the remote link station.

  • Page 168: Configuring Llc2 Interfaces

    Configuring LLC2 Interfaces LLC2 Interfaces records define the types and locations of the interfaces that will carry LLC2 traffic to or from an FRX4000/6000. To display configured interfaces, press Configuration Menu: To configure an interface, press prompted for an interface number (which is merely a sequential number to identify the...

  • Page 169: Bridge Port/Llc2 Interface Record, Ethernet

    Configuring SNA Bridge Port/LLC-2 Interface Configuration Bridge Port/LLC2 Interface Number: 0 A Interface Type Ethernet B Blocked Port Flag C Port Priority D Path Cost E Priority F LAN Card Option: Figure 9-10 Bridge Port/LLC2 Interface Record, Ethernet This example shows an Ethernet configuration. A Token Ring configu- ration screen is similar.

  • Page 170: Llc2 Interface Parameters

    FRX4000: FRX6000: 0–7 0–7 16–991 Native LLC2,8025_SRB, 8023_TB Native LLC2 1–16 valid host address 400000000001 Originated, Terminated Originated (hex) 000–fff Chapter ) at node IPL. The interface will from the Main [B], [B], [A] FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 171 Port Priority will become the first octet of the lower the number, the higher the priority that the interface will be given among other interfaces in the spanning tree. Path Cost will be added together with all other path costs on a link between bridges. The total will then be compared to other total path costs to determine the least "expensive"...
  • Page 172 , means that LLC2 connections from the configured , connections to the configured address can use this Terminated Each LAN ID must be unique within the network on which this node will operate. Groups" on page 7-6. Host MAC Address FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 173: Chapter 10 Configuring Bsc Interactive

    Each BSC Interactive HPAD supports up to 16 remote TPADs simultaneously Each TPAD supports up to 32 CUs per multidrop line To run BSC Interactive in an FRX4000 or FRX6000, you must first configure the fol- lowing in the database: Node which protocols will be run in the node.

  • Page 174: Configuring Bsc Interactive Port Records

    BSC Type 2-HPAD After making any changes, be sure to press system memory. Otherwise, the changes will not take effect until the next re-boot of the FRX4000/6000. lists more parameters, and pressing from the Main Menu. [A], [C], [A] . (The default is 0–7...

  • Page 175: Bsc Interactive Port Record

    BSC Interactive Subscriber Information RLP: 0 Port: 5 Link State: Linkup I/O:–V.35 Sq Local Sub. Remote Sub. 01 100101000000000 200201000000000N 02 100101000000001 211020100000000N 03 100101000000002 212202010000000N 04 100101000000003 203301000000000N 05 100101000000004 231020100000000N Select Figure 10-2 BSC Interactive Port Record, Screen 3 (item H) lets you delete the remote subscriber that is currently highlighted.

  • Page 176: Bsc Interactive Port Parameters

    BSC Interactive Port Parameters Parameter Port Type Physical Port Interface Blocked Port Flag Line Speed Retransmission Period Maximum Retransmissions Maximum Bytes per Frame Generate Clock Rcv Clock (TT) from DTE BSC Type Answer Non-Configured Activate Connection w/o poll EBCDIC Call Info in Call Request Packet Clear VC on Last Device Down Transparent Text Supported End-to-End Acknowledgement...

  • Page 177: Bsc Interactive Port Subscriber Parameters

    Selecting this parameter will display a list of valid protocols. An FRX4000 port can be configured as any WAN protocol loaded in the device. An FRX6000 port can be configured as any WAN protocol configured on this port's RLP.
  • Page 178 Line Speed is the data transmission rate in bits per second, and the clock speed on a serial port when the port is a physical DCE (i.e., the attached I/O cable is DCE). If this port is a physical DTE, specify the line speed that matches (as closely as possible) that of the device connected directly to the port.
  • Page 179 A page 10-8) must also be configured for this address. If the BSC port is one end of a connection to a logical X.25 port in the FRX4000/6000, this address must match a Subscriber ID configured for the logical port.

  • Page 180: Configuring Subscriber Ids

    Atcl (Autocall) causes a BSC TPAD to automatically call its HPAD when the controller (identified by Link Address) becomes active. This parameter has no function if the port is an HPAD. Rtytm is the Retry Timer, which determines the time between autocall retries. Rty# is the maximum number of times an autocall will be sent.

  • Page 181: Subscriber Parameters

    1st, 2nd,etc. Path Configured Port Redirection Address 0,1,etc. Subscriber Name identifies the subscriber to the console operator. The FRX4000/6000 software does not use this information. Routing Algorithm allows creation of a "hunt group" of ports (see example on of routing per a pre-selected algorithm: = Round Robin –...
  • Page 182 Redirection Address 0,1,etc. are up to five subscribers that will be called according to the specified redirection option. The FRX4000/6000 can redirect an X.25 call to an alternate subscriber if the original subscriber cannot be reached. (See " .") Order The FRX4000/6000 will call each address in the list until one is reached.

  • Page 183: Configuring Bsc Interactive Devices

    Table 10-4 Control and Device Unit Addressing Ctrl Unit or EBCDIC Device No. (hex) from the Main Menu). [A], [C], [F], [A] at the BSC Devices Configuration Menu. When in an FRX4000, in an FRX6000. (Default is . (Default is 0–7 . (See Table 10-4.) 0–31 .

  • Page 184: Bsc Interactive Device Parameters

    BSC Interactive Device Parameters Explanations of some parameters follow the table. Parameter Connection ID Single User Virtual Circuit Transparent Text Supported Printer Disable Status Response Connection ID is an internal identifier that must match a Connection ID in the BSC Interactive Port record.
  • Page 185 Transparent Text Supported causes (if treated as data. This is useful for transmitting binary data, machine language computer programs, etc., without special coding. Data-link control character sequences transmitted during transparent mode must be preceded by character 1/0 (DLE) in order to be recognized as control characters. Printer specifies whether the device has an attached printer.

  • Page 187: Chapter 11 Configuring Bsc Batch

    Batch ports, used to interconnect IBM 2780/3780 devices over frame relay or X.25. IBM's DSP (Display System Protocol) allows a host-to-TPAD con- nection across the network. To run BSC Batch in an FRX4000 or FRX6000, make sure the following is properly configured: Node which protocols will be run in the node.

  • Page 188: Configuring Bsc Batch Port Records

    Figure 11-1 BSC Batch Port Record After making any changes, be sure to press system memory. Otherwise, the changes will not take effect until the next re-boot of the FRX4000/6000. lists more parameters, and pressing from the Main Menu. [A], [C], [A] .

  • Page 189: Bsc Batch Port Parameters

    BSC Batch Port Parameters Parameter Port Type Physical Port Interface Blocked Port Flag Line Speed Retransmission Period Maximum Retransmissions Maximum Bytes per Frame Generate Clock Rcv Clock (TT) from DTE EBCDIC Transparent Text Supported Controller Type Full Duplex # of Beginning Sync Chars # of Trailing Pad Chars No Response Timer No Response Retry Count...
  • Page 190 Selecting this parameter will display a list of valid protocols. An FRX4000 port can be configured as any WAN protocol loaded in the device. An FRX6000 port can be configured as any WAN protocol configured on this port's RLP.
  • Page 191 Blocked Port Flag will cause the port to be enabled ( in that state until this parameter is changed or an on-line enable ( Main Menu) or disable ( Line Speed is the data transmission rate in bits per second, and the clock speed on a serial port when the port is a physical DCE (i.e., the attached I/O cable is DCE).
  • Page 192 EOT and clear the virtual circuit. 11-6 end-to-end acknowledgement of text. and text. text. ETB = End of transmission block, ETX = End of text. = 3780 = 3740 = 2770 = 3770 FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 193: Subscriber Parameters

    A Subscriber ID (see 8) must also be configured for this address. If the BSC port is one end of a connection to a logical X.25 port in the FRX4000/6000, this address must match a Subscriber ID configured for the logical port.

  • Page 194: Configuring Subscriber Ids

    (These is specified for one or more of items C, D, and E on the at the Connections and at the Connections and Routing Paths Node Name=nodexyz [A],[D],[B] from Main Menu FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 195: Subscriber Parameters

    1st, 2nd,etc. Path Configured Port Redirection Address 0,1,etc. Subscriber Name identifies the subscriber to the console operator. The FRX4000/6000 software does not use this information. Routing Algorithm allows creation of a "hunt group" of ports (see example on of routing per a pre-selected algorithm: = Round Robin –...
  • Page 196 Redirection Address 0,1,etc. are up to five subscribers that will be called according to the specified redirection option. The FRX4000/6000 can redirect an X.25 call to an alternate subscriber if the original subscriber cannot be reached. (See " .") Order The FRX4000/6000 will call each address in the list until one is reached.

  • Page 197: Chapter 12 Configuring Async Ports

    X.29 support Abbreviated addressing RTS/CTS hardware flow control To run a port as an integral async PAD in an FRX4000 or FRX6000, make sure the following are configured: Node which protocols will be run in the node. See Chapter 4.

  • Page 198: Configuring Async Pad Profiles

    An async PAD profile is a specific set of X.3 parameters whose values define the oper- ation of the device connected to an async PAD port on an FRX4000 or FRX6000. Dif- ferent profiles contain the same parameters, but with difference(s) in the values.
  • Page 199 Parameter 13, Insert <lf> after <cr> 14, Padding after <lf> 15, Editing 16, Character Delete 17, Line Delete 18, Line Display 19, Edit Service Signal 20, Echo Mask 21, Parity 22, Page Wait Profile Description is used simply as an identifier. It is not an X.3 parameter. 01, PAD Recall allows the user's device to initiate an escape from data transfer or connection in progress state in order to send PAD command signals.
  • Page 200 10, Line Folding provides for automatic insertion of appropriate format "effectors" in the character stream transmitted to the user's device. The number indicates maximum characters per line. 12-4 transfer mode. remain in data transfer mode. Appendix FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 201 11, Speed is either the ified, the speed of the async device connected to the port. The speed cannot be changed in the PAD Profile record. 12, Flow Control allows XON/XOFF from the user's device to control the rate of data transfer from the PAD.

  • Page 202: Configuring Async Pad Login Parameters

    Configuring Async PAD Login Parameters If an async subscriber will be required to log into an FRX4000/6000 async PAD, a login ID must be assigned. To display a list of existing login IDs and associated PAD profile names, press from the Main Menu).

  • Page 203: Pad Login Parameters

    PAD Login Parameters Parameter Login Password Profile Name Login Password interacts with the user must log into the PAD in order to make a call through it. Profile Name is a name given to the async PAD's "profile," described earlier in this chapter. If login is not required (as determined in the Port record), the profile specified in Port record is always in effect.

  • Page 204: Configuring Async Port Records

    (See lowing figure is an example of an existing port. Pressing page 12-9). Pressing in this chapter) that are resident in the FRX4000/6000 software. 12-8 at the Port Configuration Menu (or are described in Chapter 5.)

  • Page 205: Async Pad Port Parameters

    Async PAD Port Parameters Parameter Port Type Physical Port Interface Blocked Port Flag X.3 Line Speed Initial Profile Name Login Required Parity DCE Cable Attached Mask Link Alarms X.25 Parameter Options Generate M-bit Packets Default Calling Address Disable X.121 User Calls Autocall Options Autocall Autocall Delay...
  • Page 206 Selecting this parameter will display a list of valid protocols. An FRX4000 port can be configured as any WAN protocol loaded in the device. An FRX6000 port can be configured as any WAN protocol configured on this port's RLP.
  • Page 207 (see page 12-6) or an = Auto-detect = Even The FRX4000 and FRX6000 support 8 data bits with no parity checking, or 7 data bits with even or odd parity checking. They also support 7 data bits with auto-detect parity checking if and PAD profile 21 is configured to check parity.
  • Page 208 X.28 interface or an abbreviated address. If the async port is one end of a connection to a logical X.25 port in the FRX4000/ 6000, the Called Address must match a Subscriber ID (see the logical port.
  • Page 209 RTS-CTS H/W Flow Control enables hardware flow control through stop/start of data using RTS (pin 4), CTS (pin 5), and CD (pin 8) on the RS-232 interface. Flow control is usually necessary to maintain communication without data loss between devices or channels with different throughput capabilities.
  • Page 210 ) incoming packets from the remote device (assuming M-bit is set) into This function works only if the M-bit is set in packets from the remote device. are set to values other than are set to values other than , the = TPAD for X.3 FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 211: Configuring Subscriber Ids

    Configuring Subscriber IDs This operation configures the called and calling addresses that will be used in X.25 call setup if SNA is being transported over a logical X.25 port. To complete the con- nection, the software must recognize where the call is coming from (calling address) and where it is going (called address).

  • Page 212: Subscriber Parameters

    , a call will be placed to Redirection Address 1, then (if necessary) Redi- Valid Values Default Value 0–31 characters none 0–3 0–9 FRX4000: FRX6000: 0–7 Physical port: 0–7 Logical port: 8-63 valid address none page 8-24), for the purpose and/or Redirect on Out of Order FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 213: Configuring Abbreviated Addresses

    Redirection Address 0,1,etc. are up to five subscribers that will be called according to the specified redirection option. The FRX4000/6000 can redirect an X.25 call to an alternate subscriber if the original subscriber cannot be reached. (See " .") Order The FRX4000/6000 will call each address in the list until one is reached.

  • Page 214: Configuring Async Pvcs

    Configuring Async PVCs An FRX4000/6000 PVC is a "permanent" connection between two physical/logical ports in a node. This allows communication between the attached devices as soon as they are powered up, without having to first make a call to establish a connection.

  • Page 215: Async Pvc Parameters

    When configuring priorities, be careful to consider the types of traffic being routed on other connections in the node. Valid Values Default Value 0–9 0–31 characters none FRX6000: 0–7 FRX4000: 0–63 128–4096 1–7 . Cannot be greater than the smaller specified in the Port records 12-19...

  • Page 217: Chapter 13 Configuring Ip

    The IP functions in the FRX4000 and FRX6000 support dynamic routing of IP (internet protocol) traffic among IP devices on LANs and routed subnetworks, via frame relay or X.25. An FRX4000 or FRX6000 can also be configured to act as a gateway, forwarding IP packets it receives.
  • Page 218 13-2 , bits 1–7 are the network identifier, and bits 8–31 are the node iden- Network .The valid range in FRX4000/6000 configuration is 126.255.255.255 128.0.0.0–191.255.255.255 Network , bits 3–23 are the network identifier, and bits 24–31 192.0.0.0–223.255.255.255...

  • Page 219: Subnet Addressing

    An FRX4000/6000 can function as an IP gateway, and forward IP packets. This requires that IP be configured (and loaded) in the Required Configuration To run IP in an FRX4000/6000, you must first configure the following in the database: Node which protocols will be run in the node. See Chapter 4.

  • Page 220: Configuring Ip Node Defaults

    Configuring IP Node Defaults Each FRX4000/6000 supports one of three versions of the Routing Information Pro- tocol (RIP), which used by IP to update routing tables. The device can be configured to support RIP Version 1, Version 2 Multicast, or Version 2 Broadcast. Updates in any of the three versions can be received;...

  • Page 221: Ip Node Defaults Parameters

    IP Node Defaults Parameters Parameter RIP Version RIP Version determines the version of RIP that will be supported in the FRX4000/6000. are incompatible with each other on the same network; however, each is com- RIPv2 patible with Version 2, reconfigure each device to...

  • Page 222: Ip Interface Record - Frame Relay Example

    Source IP Address Some changes to IP Interfaces and Static Routes (described later) require an extra step to update the FRX4000/6000 software. Changing certain parameters will generate the message: changed..Do you wish to update them at this time Y/N (N)?

  • Page 223: Lan Ip Interface - Secondary Address Configuration

    Figure 13-3 LAN IP Interface – Secondary Address Configuration Up to 15 secondary IP addresses can be configured on a LAN interface, providing support for multiple IP subnets on the same physical LAN segment. To configure a secondary address, press in reverse video.

  • Page 224: Ip Interface Parameters

    (frame relay) see note none see note none 255.0.0.0 backup use or intra-nodal Network Mask Source IP Network Mask will be taken from is specified/changed, the Network Mask Network Mask FRX4000/FRX6000 4.0 User Guide, Rev 01 only. frame will be Source...

  • Page 225: X.25 Ip Interface Parameters

    (min) 0–5 1–8 for new interfaces, N for interfaces already configured when the current release of FRX4000/6000 software is installed. is valid only on a point-to-point interface. 255.255.255.255 See the caution following these footnotes. The default value of configured automatically, to reflect the appropriate address class, after the Address is specified..

  • Page 226: Ethernet/Token Ring Ip Interface Parameters

    Network Mask .) If the interface is Sec. IP Addr Source IP Address is configured), the ) is specified/ is associated with Source IP is associated with Sec. IP Addr ) or Network Mask/Netmask FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 227: Parameter Descriptions

    Parameter Descriptions Maximum Transmission Unit is the maximum size (in bytes) of the data field that can be used to encapsulate an IP datagram for transmission over the interface. Any datagrams larger than the Transmission Unit mediate routers or gateways, as well as the destination host. If the mission Unit automatically change to the minimal datagram size.
  • Page 228 IP address. If address, but the number, in the range FRX4000/6000 is used as a default source IP address. (It does not matter what type that interface is.) All un-numbered interfaces on the FRX4000/6000 use the same default address.
  • Page 229 If the addresses do not match, and Proxy ARP is enabled, the IP function will check to see if the FRX4000/6000 has a route to the host or the host’s network. If there is a route, and the route is reachable, and the route is not on the same interface on which the ARP request was received, an ARP response will be sent.
  • Page 230 IP Node Defaults the Main Menu, or see page 13-4) will be transmitted. RIP messages will be accepted, but not transmitted. No RIP messages will be accepted or transmitted. page 13-1.) from [A], [A], [E], [A] FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 231: Configuring Static Ip Routes

    Configuring Static IP Routes Routing of IP traffic is handled dynamically by such protocols as RIP, as well as via static routes configured in the FRX4000/6000. Static routes are generally used for fixed paths with predictable traffic loads, such as inter-nodal management.

  • Page 232: Ip Routing Parameters

    IP address defines a route for a network. defines a route for a specific host. defines a route that will be used if no other route is found. Default Value 255.255.255.255 Network 0.0.0.0 255.255.255.255 FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 233: Chapter 14 Configuring Ipx

    Dynamic and static routing NetBIOS™ support RFC 1490 encapsulation Required Configuration To run IPX in an FRX4000 or FRX6000, make sure the following are configured: Node which protocols will be run in the node. See Chapter 4. RLPs Card(s) supporting the ports that will be the interfaces. See Chapter 5.

  • Page 234: Configuring Ipx Node Defaults

    Figure 14-1 IPX Node Defaults Menu Table 14-1 IPX Node Defaults Parameters (55 ms intervals) Node Name=nodexyz from Main Menu [A],[A],[E],[E] Valid Values Default Value (8 hex digits) 0–ffffffff 00000000 0–100 1–47 characters none FRX4000/FRX6000 4.0 User Guide, Rev 01 [A],...

  • Page 235: Configuring Ipx Filters

    Configuring IPX Filters Filtering is the method by which the network manager controls usage of a mixed network by connection-oriented and connectionless traffic. (Connectionless traffic does not require establishment of a logical connection prior to data exchange.) A filter permits or denies (depending on how it is configured) some or all of a specific type of IPX traffic across an interface.

  • Page 236: How Filter Masks Work

    Server Name . The binary "ANDing" is as 5678 . The binary "ANDing" is as F000 Packet field = , Mask = 1237 F000 Value: 0001001000110111 Mask: 1111000000000000 AND Result: 0001000000000000 FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 237: Ipx Rip Filter Parameters

    IPX Filter Parameters The four types of IPX filters are listed in separate tables: RIP filters – see Table 14-2. SAP filters – see Table 14-3. Packet filters – see RIP Router filters – see Explanations of some parameters follow the tables. Explanations of individual masks are not included below because they were described in general under Masks Work"...

  • Page 238: Ipx Packet Filter Parameters

    0–ffffffffffff ffffffffffff 0–ffff (2 bytes) ffff (2 bytes) 0–ffff ffff 0–ffffffff (4 bytes) ffffffff 0–ffffffff (4 bytes) ffffffff 0–ffffffffffff (6 bytes) ffffffffffff 0–ffffffffffff (6 bytes) ffffffffffff 0–ffff (2 bytes) 0451 0–ffff (2 bytes) 0451 FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 239: Ipx Rip Router Filter Parameters

    Packet Type Value identifies the packet type: = unknown packet type = RIP packet = SAP packet = SPX (Sequenced Packet Exchange) packet = NCP (NetWare Core Protocol) packet = Propagated packet, used for NetBIOS (an IBM protocol that performs Destination Network Value is the network number of the destination node's network.

  • Page 240: Configuring Ipx Filter Applications

    Page 2 Option: Figure 14-3 Typical IPX Filter Applications Record .) This identifies the virtual interface. = Packet, = RIP Router. (The default is Table 14-6. [A],[A],[E],[F],[D] from Main Menu at the Filter Definitions FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 241: Ipx Filter Applications Parameters

    Filter "n" corresponds to the Configuring IPX Interfaces An IPX interface allows an FRX4000/6000 to connect to a Novell IPX network. Press at the IP/LLC2/BRIDGE/IPX Interfaces Configuration Menu (or from the Main Menu) to display configured IPX interfaces. To configure an interface, press ration Menu.

  • Page 242: Ipx Interface Parameters

    1–fffffffe 00000000 0–9 1–16 0–255 1–65535 1–65535 0–65535 54–446 0–65535 1–255 FRX4000: FRX6000: 0–7 0–7 16–991 , and must be 3 times longer than Periodic SAP Timer backup use only. or intra-nodal FRX4000/FRX6000 4.0 User Guide, Rev 01 Periodic frame...

  • Page 243: Interface Parameters

    X.25 Interface Parameters Parameter Blocked Port Flag Interface Type Frame Type Maximum Transmission Unit IPX Network Address Priority Bandwidth Allocation Group Port Diagnostics Enabled NetBIOS Enabled NetBIOS Hops Periodic RIP Enabled Periodic RIP Timer Periodic SAP Enabled Periodic SAP Timer RIP Enabled RIP Age Timer RIP Maximum Size...

  • Page 244: Ipx Lan Interface Parameters

    802.5: 48–4096 4096 1–fffffffe 00000000 0–9 1–16 0–255 1–65535 1–65535 0–65535 54–446 0–65535 1–255 FRX4000: FRX6000: 0–1 Ethernet , and for Interface 1–63 must be 3 times longer than Periodic SAP Timer FRX4000/FRX6000 4.0 User Guide, Rev 01 802.5 Periodic...

  • Page 245: Parameter Descriptions

    Parameter Descriptions Descriptions of Parameters Common to All Interface Types Blocked Port Flag causes the IPX interface to be enabled ( remain in that state until this parameter is changed. Interface Type Supported types are: Ethernet, 802.5 (Token Ring), X.25, and Frame Relay. Frame Type TYPE_II SNAP...
  • Page 246 These broadcast frames are used by Novell to hold infor- mation regarding the licensing of the file server executables. 14-14 for LAN interfaces and will be overridden by the value calculated by Transport Time FRX4000/FRX6000 4.0 User Guide, Rev 01 for WAN inter- IPXWAN Enabled...
  • Page 247 Novell's IPXWAN protocol will be used on the interface. IPXWAN specifies a method for IPX routers to communicate across WAN links. The FRX4000 and FRX6000 implement IPXWAN running over RFC 1490-compliant frame relay and RFC1356-compliant X.25. Source Card/Port/DLCI identifies the location of this end of the frame relay IPX interface.

  • Page 248: Configuring Static Ipx Routes

    The display will be similar to the RIP example in the following figure. (A SAP record will display different parameters.) 14-16 . (Although the FRX4000 does not have a LAN card, it’s LAN from the Main Menu). [A], [D], [H] at the Connections and Routing Paths Menu.

  • Page 249: Ipx Rip Static Route Parameters

    IPX RIP Static Route Parameters Parameter Network Hops Transport Time Router Interface Network is the IPX network address of the network containing the node defined by Number Hops is the number of routers in a packet's path to the destination network. Transport Time is the time (in 55-millisecond units) that it will normally take a packet to reach the des- tination network if this route is used.

  • Page 250: Ipx Sap Static Route Parameters

    Valid Values Default Value 0–65535 1-48 characters asterisk (wildcard) (4 bytes) 1–fffffffe 00000001 (6 bytes) 1–fffffffffffe 000000000001 0–ffff 0000 1–65535 1–fffffffffffe (6 bytes) 000000000001 0–65535 = job server 0005 = remote bridge server 0024 FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 251: Chapter 15 Configuring Bridging

    Introduction The FRX4000 and FRX6000 support transparent "Spanning Tree" bridging of non- routable LAN traffic (e.g., NetBIOS, DECnet, AppleTalk) over frame relay between 802.3/Ethernet or 802.5/Token Ring LANs. FRX4000/6000 also support translational bridging between Ethernet and Token Ring LANs. (For more information on bridging, refer to IEEE standard 802.1d.)

  • Page 252: Required Configuration

    Bridging is supported on Ethernet, Token Ring, and frame relay interfaces. Required Configuration To configure a Bridge in a Netlink FRX4000 or FRX6000, you must first configure the following in the node's database: Node which protocols will be run in the node.

  • Page 253: Configuring Default Node-Wide Bridging Parameters

    Configuring Default Node-Wide Bridging Parameters If one or more Bridge ports (interfaces) will be established in the local node, certain parameters must be configured to define bridge operation. Press IP/LLC2/BRIDGE/IPX Default Parameters Menu (or Menu). When prompted, enter: Virtual LAN ID Any remaining requested information, referring to Configuring Bridging –...

  • Page 254: Bridge Node Default Parameters

    SRB ID must be if the Bridge port is on an IBM Token Ring card. This parameter is irrelevant on a a Token Ring FRX4000. If Bridging is disabled, all Bridge ports on the node will go into state (described under "Bridge Status...
  • Page 255 Bridge Aging Timer determines how long learned addresses will be saved in the forwarding table before they are deleted. Bridge Priority will become the first two octets of the Bridge ID, used to determine which bridge will be Root. Since the lowest Bridge ID becomes Root, a lower Bridge Priority increases the possibility of becoming Root.

  • Page 256: Configuring Bridge Filters

    = Bridged native NetBIOS. . (The default is .) This is simply a unique identifier. 1–65535 Table 15-6 (on page 15-10). (Press = LLC2 SAP Table 15-2 (on page 15- at a prompt to accept a [Enter] FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 257: Bridge Mac Filter Configuration Screen

    How Filter Masks Work Most Bridge filter parameters are assigned values and associated "masks." The mask determines (by the process described below) whether the filter will be applied to the packet. The binary bits of the mask will be "ANDed" (0+0=0, 0+1=0, 1+1=1) to the value, as in this example: Assume the value (hex) is follows:...

  • Page 258: Bridge Generic Filter Parameters

    Work" on page 15-7. Default Value none (octets) (hex) (hex) "How Filter Masks Work" on "How Filter Masks Work" on Default Value none (6 bytes) ffffffffff (6 bytes) ffffffffff (6 bytes) ffffffffff (6 bytes) ffffffffff FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 259: Bridge Sap Filter Parameters

    Filter Name helps the user identify the filter. The name is not used by the software. Source MAC Address Value is the MAC address in the source address field of the frame. Destination MAC Address Value is the MAC address in the destination address field of the frame. Parameter Filter Name SSAP Value...

  • Page 260: Configuring Bridge Filter Applications

    (in Bridge Node Defaults). Other filter types will be applied only if bridging is enabled. (inbound) or (outbound). (The default is Default Value none none none .) (This number simply identifies the = LLC2 SAP Table 15-7. FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 261: Typical Bridge Filter Applications Record

    Up to 100 filters can be configured, displayed over ten "pages" (screens). can be used to move through the screens. (At any screen, pressing [PgUp] the configuration for all ten screens and exit the display. Pressing will abandon the changes for all ten screens and exit.) When finished configuring filter definitions and applications, you must perform an on-line update to make the changes effective immediately.

  • Page 262: Configuring Bridge Ports

    Configuring Bridge Ports A Bridge port is an FRX4000/6000 LAN interface or frame relay port that will operate as a bridge connection to the LAN or WAN. Press figured Bridge ports. To configure an interface, press uration Menu. When prompted for an...

  • Page 263: Bridge Port Parameters

    Figure 15-5 Bridge Port Record Example Table 15-8 Bridge Port/LLC2 Interface Parameters Valid Values Ethernet, TokenRing, FRL Native LLC2 format: n/a All other formats: Native LLC2 format: n/a All other formats: 1/1000 0–9 FRX4000: FRX6000: FRX4000: FRX6000: 0–7 16–991 Native LLC2,8025_SRB, 8023_TB 1–16...
  • Page 264 LAN Card identifies the LAN card, as defined in the file PROTOCOL.INI ( Main Menu). (The LAN interface in an FRX4000 is seen as RLP/Port identifies the RLP and physical port containing the interface. 15-14 Determined by line speed of frame relay port.
  • Page 265 DLCI matches the connection with an interface at the remote end of the link. Format is the RFC1490 encapsulation method used for bridged traffic. Note that specifying 8023_TB will add an Ethernet header to the frame, and 8025_SRB will add a Token Ring header.

  • Page 267: Chapter 16 Configuring Snmp

    Chapter 16 Configuring SNMP Introduction The SNMP (Simple Network Management Protocol) agent allows a network man- agement station using internet protocol to obtain information from Cabletron frame relay access products. Access to the agent is through any IP interface, including frame relay or X.25 ports configured for IP, and LAN interfaces.

  • Page 268: Configuring Snmp System Defaults

    System Defaults Parameters Parameter System Name System Location System Contact System Name identifies the local FRX4000/6000 to the SNMP manager. System Location is generally the geographical address of the local node. 16-2 SNMP Defaults Menu A System Name B System Location...

  • Page 269: Configuring A Community Table

    Configuring a Community Table Up to 16 SNMP manager devices can gain access to the SNMP agent in an FRX4000 or FRX6000. Each manager device is configured with a community name, which identifies it to agents and other managers, and is included in SNMP requests to a node.

  • Page 270: Community Table Parameters

    0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 Option:: Figure 16-3 SNMP Trap Routing Menu Default Value none Read only Node Name=node_xyz D Severity E Delete from Main Menu [A],[A],[D],[C] FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 271: Trap Routing Parameters

    To configure an entry, press the corresponding " entry, select it, then press deleted one will move up one in the list. Trap Routing Parameters Parameter Address Enabled Severity Address is an IP address to which all traps meeting the "enabled" and severity class criteria will be sent.

  • Page 272: Configuring A Model Number

    OmniView is used at a later time. at the SNMP Configuration Menu (or , then enter the correct value: The Rackmount chassis is currently the only standard model of FRX6000; however, Model 2 is supported for existing customers. [A], [A], FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 273: Operation

    Section III Operation...

  • Page 275: Chapter 17 Introduction To System Operation

    Introduction to System Operation Once the database has been configured and the node has been brought on line, little operator intervention is generally necessary. The various functions that can be per- formed from the menus allow the operator to do such things as: Perform on-line software updates to nodes.
  • Page 276 Back Up the Current System Files to a Local Directory Restore the System Files from a Local Directory assure they were correctly created. settings to an Auxiliary Console on the node's Console port (FRX4000) or COM1 port (FRX6000). – (Chapter 18) Uses the Ping function to determine whether an IP host is reachable.
  • Page 277 NMVT commands or from files in the node database. – (Chapter 18) (valid only on an FRX4000 with the internal CSU/DSU port installed). – transmits a test pattern to the analog portion of the circuitry and loop the pattern back to itself.
  • Page 278 – (Chapter 2) produces a list of messages created during the previous boot-up of a node. – displays the supported statistics, – displays CIR, B , and B values for FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 279: Chapter 18 On-Line Operations

    X.25 port on the node to be controlled. These restrictions apply to the Remote Control operation: An FRX4000/6000 cannot be controlled by more than one device at a time. While remotely controlling one node, you cannot take remote control of another one.

  • Page 280: Remote Control From An Frx4000/6000

    Press [F9] nodes will now be under local control. The local FRX4000/6000, and the remote device (if it has a local video device), will be logged out to the Port Status Display. From there, the operator must log in to perform menu operations.

  • Page 281: Remote Control Via An Async Pad Port

    1234 y [Enter] Under remote control. Keyboard blocked by id = "n." Placing a call through the FRX4000/6000 is described in Before rebooting, notify all users of this node, since all connec- tions on all ports will be cleared. (period) to reboot the node. When asked: (comma) to exit remote control.

  • Page 282: Transferring Files And Updating Software

    Transferring Files and Updating Software Remote File Transfer This operation copies a file from one FRX4000/6000 to another. Press When prompted, enter: File Transfer ID you are copying the file. Source File Name Destination File Name The transfer process is as follows: 1.

  • Page 283: Remote Software Update

    This operation allows an operator to send a complete software update from one FRX4000 to another, from one FRX6000 to another, or between an FRX6000 and a FRM. The file UPDATE.TXT contains a list of the files that will be transferred.

  • Page 284: Backing Up And Restoring Files

    Options on an FRX4000 are: Remote Backup and Restore (Items A–C) Items A and B are used to back up a remote node’s database to a local FRX4000/6000 that has control of the remote node. Both operations require first taking (see page 18-1) ( backed up.
  • Page 285 Items F and G are used to back up a node’s operating files to a local backup directory, then restore the database into the original directory. These operations can be per- formed on a local or remote (via remote control) FRX4000, but in either case the oper- ations affect the node under operator control.

  • Page 286: Copying An Frx4000 Directory To/From A Pc

    This is useful for backing up the FRX4000's configuration database. Copying the Directory to the PC 1. Make sure a directory with the same name as the one in the FRX4000 exists in the PC. 2. In Procomm, use 3.

  • Page 287: Frx4000 Local File Backup And Restore

    FRX4000 Local File Backup and Restore Backup This operation copies files (one at a time) from an FRX4000 to the locally attached PC, and is useful for backing up the FRX4000's configuration database. You must know the name(s) of the file(s) you want to transfer. All possible database files are listed in undergone its initial IPL.

  • Page 288: Ip Interface Parameters

    Software release number X.25 Address translation templates This operation applies only to an FRX4000 with a PC attached to the Console port. The PC must be running Procomm Plus with ZMODEM. The procedure was tested using Procomm Plus 2.1 for Windows, but other ver- sions containing ZMODEM should also work.
  • Page 289 3. Enter the letter corresponding to the desired operation when asked: Are you: A Installing a Software File B Restoring a Database File This will ensure that the file(s) will be copied to the right place in the FRX4000. 4. Press Main Menu). 5. After reading the warning, press 6.

  • Page 290: Enable/Disable Operations

    (frame relay), Port Type (BSCB). on FRX4000, From RLP 0–7 From port 0–63 on FRX4000, on FRX6000. To RLP 0–7 To port 0–63 Node Name=node_xyz [B],[B] from Main Menu (async), (SNA), (BSCI), or on FRX6000. FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 291: Quiescing And Unquiescing Ports

    While an X.25 dialout port is quiesced, it cannot receive alarms or file transfers, or be used by another FRX4000/6000 to take remote control of the node. Also, quiescing a range of ports has no affect on any port types within that range other than the type specified.

  • Page 292: Disabling And Enabling Sdlc Pus

    Port 0–7 PU station address 0–ff on FRX4000, From RLP 0–7 From port 0–7 on FRX4000, on FRX6000. To RLP 0–7 To port 0–7 Node Name=node_xyz [B],[G] from Main Menu , enter: on FRX6000. FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 293: Tests

    Tests IP Ping Connectivity Test The IP Ping function sends packets to an IP host to determine whether the host is reachable. Press To begin the test: 1. Press 2. Make any desired change to the (seconds). This is an interval between transmission of packets. 3.

  • Page 294: Frx4000 Csu/Dsu Tests

    A should then ping interface 3, then (if a response is received) device B. FRX4000 CSU/DSU Tests To test the CSU/DSU port on an FRX4000, the port must first be disabled. If nec- essary, press the port.

  • Page 295: Initiating Frame Relay Backup Switchover/Switchback

    Initiating Frame Relay Backup Switchover/Switchback Frame relay backup ically become operational a set time after failure of a primary DLCI, and to switch back to the primary a set time after the primary becomes operational again. These automatic settings can be overridden via Frame Relay Backup Operations ( from the Main Menu).

  • Page 297: Chapter 19 Status Displays

    – is the sum of current packets per second through all physical – is the number of virtual connections (SVCs and PVCs) cur- – is the date/time the FRX4000/6000 software was last started. – lists the possible operational states that each port can be in. See "State"...

  • Page 298: Displaying Port Status

    Full Status Response Node Name=node_xyz Conn# State Operational Operational Operational Operational [C],[B] from Main Menu [PgDn] = SNA = Async PAD = 802.3 8023 FRX4000/FRX6000 4.0 User Guide, Rev 01 to display...

  • Page 299: Displaying Virtual Connections

    Status Displays from the DCE (frame relay switch), as a result of a Full Status Enquiry sent by the FRX4000/6000. On a frame relay logical DCE port, this state means that the port has received a Full Status Enquiry from the attached DTE.
  • Page 300 ), and enter the port number. If the DLCI is , note the backup DLCI, then press at the Status Displays menu, and verify that state. Data_trans on FRX4000, with the following excep- are logical ports), unless 8–63 = File transfer, FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 301: Virtual Connections Display On Non-Frame Relay Port

    RLP P State Subscriber 4095 Data_trans 120000110 Data_trans 111000120 Not_conect Data_trans 33333 from Main Menu [C],[C] = SVC = Incoming, = Outgoing. on FRX4000, with the following excep- are logical ports), unless 8–63 = File transfer, = Alarm con- 19-5...

  • Page 302: Displaying Port Signals

    ON \ [C],[D] from Main Menu , etc.) as configured in the Port is displayed on this No Config , as taken from the Port record. is displayed on this line and No Config FRX4000/FRX6000 4.0 User Guide, Rev 01 0–...

  • Page 303: Monitoring Traffic

    [F5] Running the traffic monitor on a frame relay port will degrade performance on the port. at the Traffic Monitor Menu (or on FRX4000, on FRX6000. 0–7 , or to monitor LLC2 sessions. 0–63 While remotely controlling a node, you cannot monitor the line to which you are connected.
  • Page 304 . (Stopping the scrolling first is not always necessary, but allows [F3] [F3] will display the message: :..." message (shown above). above) back to level 3 (i.e., Line Monitor Buffer is Full is pressed, especially from an async ter- FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 305: X.25 Line Monitor Display

    X.25 Line Monitor The X.25 line monitor is used to monitor X.25, SDLC, BSC, and async ports. The fol- lowing figure shows an example: On each line: The leftmost field shows the time, to hundredths of a second. The next field displays displayed in reverse video.) The next field identifies the packet type.
  • Page 306 N(R) 7 N(S) 5 (0014):2C00020000008B80008106200000 means Poll bit is set) means Final bit set/nothing to send, or done) ACTPU RU REQ ACTPU RU +RSP SNA ACT LU REQ'S ACTLU RU +RSP NOTIFY RU ENABLED FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 307 03 I 03 I 03 I 01 RR 01 RR 03 I 02 RR 02 RR 03 I 03 I 03 RR 03 I 03 I 03 RR 01 RR 01 RR 02 RR 02 RR 03 RR 03 RR 03 I 01 RR 01 RR...

  • Page 308: Frame Relay Line Monitor Display

    (new) or from the Main Menu) to [C], [C] from the Main Menu) to [C], [B] from Main Menu [C],[E] (active). A DLCI is reported as new if and the port Port Data_trans Operational FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 309 The format of status exchanges depends on the type of link management. Annex D frames always use DLCI both formats are shown below: Annex D 0000 Full Status Enquiry 001/000 0000 Full Status 001/001 016:N 017:N 0000 LIV Status Enquiry 002/001 0000 LIV Status 002/002 0000 LIV Status Enquiry 003/002 0000 LIV Status 003/003...
  • Page 310 (start of IP header 45..) 000000 8137 FCS Flag LAPB frame, X.25 packet 6780 7081 7082 7083 7084 7085 AA AA 03 81 37 AA AA 03 81 38 AA AA 03 80 9B FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 311 frame relay in RFC1490 format are known in IBM terminology as BAN Type 1 frames. Besides the encapsulation information, the main difference between BAN and BNN LLC2 frames is that BAN sends the MAC addresses across the WAN. BAN is usually used for connectivity to AS/400 hosts only.
  • Page 312 = Sender's hardware address (MAC address)| = Sender's protocol address (IP address) = Target hardware address (MAC address) = Target protocol address (IP address) 3.0.0.0 = ARP reply, = RARP request, FRX4000/FRX6000 4.0 User Guide, Rev 01 = RARP...

  • Page 313: Monitoring Lan Traffic

    Monitoring LAN Traffic Data for a LAN interface can be gathered by capturing current information and placing it into a buffer. This data can then be displayed. Configuring the Monitor To configure the parameters used in a capture, press [C], [E], [B] lowing: Information in this Display: Protocols...

  • Page 314: Lan Capture Display

    Trace Bridge Trace Unknown When Full IP, IPX, and Bridge can be set to (FRX6000) or in the device (FRX4000). in the buffer as necessary. (The first data in will be the first overwritten.) The function keys work as follows: [F1]...

  • Page 315: Displaying Frame Relay Backup Status

    The capture buffer can hold the first 76 bytes of each packet, up to 1000 packets. In an FRX4000, the data is captured to a packet buffer. In an FRX6000, the data is stored in a file named landata.out.

  • Page 316: Displaying Sdlc Pu Status

    – due to failure of a higher resource (e.g., port) Inoperational ) has not been received within at the Protocol Status Dis- Node Name=node_xyz [C],[F],[C] from Main Menu parameter set in the ADDR , etc. for multidrop lines.) C1, C2, C3 FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 317: Displaying Llc2 Session Status

    Displaying LLC2 Session Status The status of any current LLC2 sessions can be displayed by pressing tocol Status Displays Menu (or Information in this Display: SSAP DSAP SMAC HMAC State Call State SessType PUName Bridge Status Displays Bridge Port Status Press ational status of all Bridge ports in the node: Status Displays...
  • Page 318 Designated timer (described on page 15-4) expires. If port, it will enter Designated Forwarding port, it will enter Root Designated Root Designated state. FRX4000/FRX6000 4.0 User Guide, Rev 01 [PgDn] 20-11. state. If the state. , and...

  • Page 319: Bridge Forwarding Table

    (If received from a Token Ring, the addresses will be bit- swapped [described under table.) The FRX4000/6000 software contains a set of reserved MAC addresses that are considered "static," and will always be in the table. The remaining entries are con- sidered "dynamic,"...

  • Page 320: Ip Status Displays

    Information in this Display: Destination Gateway (This corresponds to the Routes. being used in the FRX4000/6000 software. The route cannot be removed if this count is greater than zero. Flags 19-24 – source or destination address received in a frame.

  • Page 321: Arp Table

    The address is added to the table after the FRX4000/6000 sends an ARP request for an IP address and receives a MAC address in response. The timer is reset if an IP frame is received from the either the IP or MAC address.
  • Page 322 – interface number of the primary interface. – secondary IP address. – broadcast address configured for the secondary address. – network mask configured for the secondary address. and the Mask on the second Mask IP Network FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 323: Ipx Status Displays

    Main Menu). Each entry will contain the following: [C], [F], [A] – IPX address of the network containing the FRX4000/6000 that con- – address of the router that will forward a packet when this route is – number of routers in a packet's path to the destination network.

  • Page 325: Rlp Statistics

    Percentage of buffers in use Number of queued messages Received frames per sec (*10) second over the five-second reporting interval, multiplied by 10. Although an FRX4000 has no RLPs, RLP functionality exists in the device. RLP Statistics Report RLP: 0 Report Interval (sec): 5...

  • Page 326: Configuring Rlp Statistics Thresholds

    Changing a threshold changes the database value. Press change to system memory. . (Default = 0–65535 ) in the Port record. Node Name=node_xyz System Memory from Main Menu [E],[A] to write the [F7] ) When the measured value for the sta- FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 327: Port Statistics

    Port Statistics Information in this Display: Received frames per sec (*10) second over the five-second reporting interval, multiplied by 10. Transmitted frames per sec (*10) second over the five-second reporting interval, multiplied by 10. Retran frames per sec (*10) second over the five-second reporting interval, multiplied by 10. FCS errors/sec (*10) Cyclic Redundancy Check) errors received on the port per second over the five- second reporting interval, multiplied by 10.

  • Page 328: Configuring Port Statistics Thresholds

    Changing a threshold changes the database value. Press change to system memory. (Default = 0–65535. Node Name=node_xyz System Memory from Main Menu [E],[A] to write the [F7] ) When the measured value for the sta- FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 329: Frame-Level Statistics

    Frame-level Statistics Frame-level statistics are frame relay (if the port is configured for frame relay) or X.25 level 2 statistics (per second, multiplied by 10). Information in a Frame Relay Display: DE/sec (*10) Elgibility) bit set per second over the five-second reporting interval, multiplied by 10.

  • Page 330: Frame Relay Utilization Statistics

    (receive not ready) (supervisory command or response) (information) (information transfer, command) at the Statistics Menu and, when prompted, enter: on FRX4000, on FRX6000. (Default is 0–7 . (Default is 0–7 . (Default is 16–991 (in seconds): 5–65535 . (Default is FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 331: Frame Relay Utilization Statistics Display

    Information in this Display: CIR In/Out Bc In/Out Be In/Out Committed Data In/Out Excess Data In/Out Frames Rcvd the node or enabling of the port. Disc or enabling of the port. Frames Xmit of the node or enabling of the port. Conf/Act Percentage traffic assigned to each group.

  • Page 332: Lan Card Statistics Displays

    – the OpenAdapter function, which activates the adapter's network Open connection, is enabled. at the Statistics on FRX6000. (Default is Node Name=node_xyz MTU: 1500 CURR CUMULATIVE 269420 8161 139822450 [E],[G] from Main Menu FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 333 Packet Filters packets that can be received on this interface (more than one category can be specified: Packets In/Out interface. Bytes In/Out Multi-Cast In/Out address over the interface. Broadcast In/Out address over the interface. Frm Dropped In/Out dropped. Q Dropped In Dropped Timeout to a timeout or reception of another frame.

  • Page 334: Bridge Port Statistics

    Disabled Token Ring Active Listening Frm/Nat LLC2 Active Learning Frm/8023/TB Active Blocking PgUp PgDn F2:More Info F3:Exit Figure 20-8 Bridge Port Status Display Node Name=node_xyz ReceiveXmit 42949672964294967296 46755612344675561234 45612300004562222100 45612311004561231100 from Main Menu [C],[F],[D],[A] FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 335 To display statistics for the Bridge ports on the above screen, press [PgUp] will return the display to Figure 20-8. [F2] Information on the Bridge Port Statistics Display: Type/Format relay) and (if frame relay) frame format (Native LLC2, 8025_SRB, or 8023_TB, as configured in the Port record).

  • Page 336: Ip Statistics Displays

    – is the number of datagrams delivered to an application (e.g., at the Statistics (seconds). (Default is 5–65535 Node Name=node_xyz CURR CUMULATIVE 1000000000 1000000000 1000000000 1000000000 1000000000 1000000000 1000000000 1000000000 1000000000 1000000000 [E],[C] from Main Menu is the total since the last IPL FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 337: Icmp Statistics Display

    Bad Hdr Length than the minimum IP header length. Local Pkts Sent Bad Pkt Length the length of the header. Pkts Dropped lack of buffers. Pkt Fragments Total Reasmbled at this node. Frag Time Out eouts. Pkts Fragmented Frag Dropped cation or lack of space.
  • Page 338 ") from this Out Echo if this Outgoing if the datagram origi- Incoming if this node is a point in the Outgoing if the Incoming if this node is a point in the Outgoing FRX4000/FRX6000 4.0 User Guide, Rev 01 Out-...
  • Page 339 Out/In Bad IP Hdr were discarded due to a header size less than was specified. The message text says the datagram originated at this node. Out Time Req tamps, which are a method of determining delay characteristics over the Internet. In Time Req for timestamps, which are a method of determining delay characteristics over the Internet.

  • Page 340: Ip Interface Statistics Display

    – is the number of transmitted frames that were involved in collisions. at the Statistics at the upper IP/LAN IP/WAN Node Name=node_xyz MTU: 4096 CURR CUMULATIVE 269420 8161 139822450 [E],[E] from Main Menu is the total since the last IPL CUMULATIVE FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 341: Ipx Statistics Displays

    15, the maximum allowable. NetB Hops_2_Lrg because the hop count exceeded the number of NetBIOS Hops specified in the IPX Interface record for the local FRX4000/6000 interface. RIP No Net Addr address. The network address configured for the interface will be used.
  • Page 342 – is the number of SAP Nearest Queries transmitted on the – is the number of SAP General Responses (responses to – is the number of SAP Nearest Responses (responses to Nearest FRX4000/FRX6000 4.0 User Guide, Rev 01 , configured in RIP Age Timer...
  • Page 343 SAP Age Timer, configured in the IPX Interface record. SAP Prd_Broadcast this node advertising the available servers (from the server table in the FRX4000/6000). SAP Upd_Broadcast to inform the network of changes to the server table. SAP INV Net Rcv network address (one that does not match the network address configured on the interface).
  • Page 344 0456 Rcv BSys Discard FRX4000/6000, but are included in the statistics list because it is part of the IPX MIB. The statistics in the list between the above two are: Local Rcv Pkts, Path_Not Found, Local Tx Pkts, Bad Local Tx Pkts, Tx BSys...

  • Page 345: Chapter 21 System Events

    Events parameters are set in message file ERRMSG.TXT contains the format of events for message construction. Configuration To configure an FRX4000/6000 to collect events from other Cabletron frame relay access devices (SmartSwitch 1800, FRM, FRX4000, FRX6000), do the following in Node Defaults: 1.

  • Page 346: Alarm Buffer

    Station with Address 12345 Printer Optional Monitor Optional Async Terminal Max Con- Beginning End of congestion, “n” events lost , events are held in the Max Congestion or the collecting Max Congestion FRX4000/FRX6000 4.0 User Guide, Rev 01 , is...

  • Page 347: Event Generation

    Event Generation As soon as a message-generating event occurs, a Call Request is automatically sent to Primary Alarm Output ID originating node's buffer until the event connection is activated.) All events are trans- mitted in raw data format to the collecting node, which constructs event messages and sends them to the display device(s).

  • Page 348: Severity Levels For Snmp Trap Routing

    Check configurations and set the clock. The Port record is configured for a maximum frame sequence number (Outstanding Frames) greater than 7, but a command was received setting the mode to allow a maximum of 7. None. FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 349 182. Configured for normal sequence numbering, received SABME Severity: Meaning: Action: 197. Received FRMR, WXYZ="n", control field="n", V(s)="n", V(r)="n", CMD/RSP="n" Severity: Meaning: Action: 198. SABM/DISC with wrong link address Severity: Meaning: Action: 219. Illegal TC/Gen Clk Combination Severity: Meaning: Action: 250.
  • Page 350 C:“n” has exceeded the is the current C:“n” has exceeded the is the current C:“n” has exceeded the is the current C:“n” has exceeded the is the current C:“n” FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 351 312. Tran Frm/Sec exceeded T:“n” C:“n” Severity: Meaning: Action: 313. RTrn Frm/Sec exceeded T:“n” C:“n” Severity: Meaning: Action: 314. FCS Rej/Sec exceeded T:“n” C:“n” Severity: Meaning: Action: 315. Log Rej/Sec exceeded T:“n” C:“n” Severity: Meaning: Action: 316. Trn Err Ratio exceeded T:“n” C:“n” Severity: Meaning: Action:...
  • Page 352 Line Processor file, but does not exist in the node. Install the LIC or delete its record. has exceeded the threshold is the current value.) The C:“n” (Utilization) has exceeded the is the current C:“n” (Utilization) has exceeded the is the current C:“n” FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 353 379. LIC “n” Config Mismatch - Type “n” Severity: Meaning: Action: 400. Link Enabled Severity: Meaning: Action: 401. Link Disabled Severity: Meaning: Action: 402. Link Disconnected Severity: Meaning: Action: 403. Link Up Severity: Meaning: Action: 404. X.25 Link Failed Severity: Meaning: Action: System Events...
  • Page 354 Depends on the cause. If necessary, contact Technical Support. (See page 21-4.) Self-explanatory. None. Self-explanatory. None. A Reset was sent on the PVC. None. ) and diagnostic Cabletron Systems for a list of cause codes ( ) and Cabletron Systems FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 355 411. Received Reset LCN = “n", cc = “n” dc = “n” Severity: Meaning: Action: 412. Received Reset Confirm Severity: Meaning: Action: 413. PAD Link Failed Severity: Meaning: Action: 414. Beginning of Congestion Severity: Meaning: Action: 415. End of Congestion, “n” events lost Severity: Meaning: Action:...
  • Page 356 None; however, all users of this port should be made aware of the disable. The BSC device has experienced a problem that caused it to send a request to send a dump to the port. Check the device. Self-explanatory. None. Self-explanatory. None. FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 357 434. Remote Control CXN Clr cc = “n” dc = “n” Severity: Meaning: Action: 435. LG Buffer MALLOC Problem PKTs Lost Severity: Meaning: Action: 436. RCV Unknown Event Code from Net. Severity: Meaning: Action: 437. RCV Invalid Event Format from Net. Severity: Meaning: Action:...
  • Page 358 None. The PVC Subscriber file has been updated. None. The Remote Subscriber file has been updated. None. The SVC Subscriber file has been updated. None. The Default Statistics Parameters file has been updated. None. FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 359 451. Translation File Upd:XLTPAR.DAT Severity: Meaning: Action: 452. X.25 Default File Upd:X25REC.DAT Severity: Meaning: Action: 453. Alarm Enable File Upd:ERRMSG.TXT Severity: Meaning: Action: 454. Remote Update File Upd:UPDATE.TXT Severity: Meaning: Action: 455. Login Password Changed Severity: Meaning: Action: 456. Operator Logged into Node Severity: Meaning: Action:...
  • Page 360 None. The SNMP Community Table file has been updated. None. The situation that caused event None. The situation that caused event None. The situation that caused event None. has ended. has ended. has ended. FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 361 467. RLP Trn Frm/Sec Under Threshold Severity: Meaning: Action: 468. RLP Rej Frm/Sec Under Threshold Severity: Meaning: Action: 469. RLP Rtrn Frm/S Under Threshold Severity: Meaning: Action: 471. Rcv Frm/Sec Under Threshold Severity: Meaning: Action: 472. Tran Frm/Sec Under Threshold Severity: Meaning: Action:...
  • Page 362 Contact Cabletron Systems Technical Self-explanatory. Double-check the configured addresses. Self-explanatory. Contact Cabletron Systems Technical has ended. has ended. has ended. has ended. ), which [F4] Support. (See page 21-4.) Support. (See page 21-4.) FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 363 484. Error modifying interface “n” Severity: Meaning: Action: 485. Interface “n” deleted successfully Severity: Meaning: 486. Interface “n” added successfully Severity: Meaning: 487. Interface “n” modified successfully Severity: Meaning: 488. Error deleting route with destination “n,” mask “n,” router “n” Severity: Meaning: Action:...
  • Page 364 Take the same action as for message 500. An invalid message has been received, disabling the port. Take the same action as for message 500. An invalid message has been received, disabling the port. Cabletron Systems Technical FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 365 Action: 513. BSCI:Invalid control block Severity: Meaning: Action: 514. BSCI:Invalid parameters Severity: Meaning: Action: 515. BSCI:Invalid port number or type Severity: Meaning: Action: 516. BSCI:Invalid message transfer Severity: Meaning: Action: 517. BSCI:Invalid circuit operations Severity: Meaning: Action: 518. BSCI:Invalid state event action Severity: Meaning: Action:...
  • Page 366 The DTE and DCE exchange messages regularly so that each knows the other is running and ready. If one end does not respond, this event message is sent and the link goes down. Check the equipment to see what caused the failure to respond. FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 367 533. Exit Service Affecting Condition Severity: Meaning: Action: 534. DLCI “n” Frm Relay PVC Disconnected Severity: Meaning: Action: 535. DLCI “n” Received Bad Frame Severity: Meaning: Action: 536. DLCI “n” No Response to STATUS ENQ Severity: Meaning: Action: 537. DLCI “n” Flow Control On Severity: Meaning: Action:...
  • Page 368 One end of the PVC is probably not up. Check both ends of the PVC. No Status Enquiry was received when one was expected. Check the remote device. The LLC2 Interface file has been updated. None. FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 369 562. LLC Host File Upd:LLC2HPAR.DAT Severity: Meaning: Action: 563. LLC LAN Card File Upd:LANPAR.DAT Severity: Meaning: Action: 564. IPX Filter Def File Upd:IPXFPAR.DAT Severity: Meaning: Action: 565. IPX Filt App File Upd:IPXFLTAP.DAT Severity: Meaning: Action: 640. Bridge Filt Def File Upd: BRGFLTD.DAT Severity: Meaning: Action:...
  • Page 370 The situation that caused event 652 has been fixed. However, the T1/E1 connection will not be operational if any of events 650-652 has been set but not cleared. FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 371 701. SDLC Rem. Link Stn Not Responding Severity: Meaning: Action: 702. SDLC Link Stn Sent DM Severity: Meaning: Action: 704. SDLC Link Stn rcvd FRMR, Inv. cmd Severity: Meaning: Action: 705. SDLC Stn rcvd FRMR, IFLD invalid Severity: Meaning: Action: 706.
  • Page 372 Check the hardware and configuration at the remote device. A frame transmitted by the remote station exceeds the configured value for Maximum Bytes per Frame None. No Resp Poll Period FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 373 718. SDLC Rem sent UA in NRM Severity: Meaning: Action: 720. SDLC No DSR on link Severity: Meaning: Action: 721. SDLC No CTS on link Severity: Meaning: Action: 722. SDLC No External CLock Severity: Meaning: Action: 736. SDLC LLC/2 Remote Link Stn lost Severity: Meaning: Action:...
  • Page 374 Meaning: The remote device received an invalid or unsupported command, and returned a Frame Reject. Action: None. 740. LLC/2 FRMR Rcvd, IFLD not permitted Severity: Meaning: The remote device received an I-frame when it was not permitted, and returned a Frame Reject. Action: None.
  • Page 375 Meaning: Action: 747. LLC/2 FRMR Sent, no reason Severity: Meaning: Action: 748. LLC/2 FRMR Rcvd, no reason Severity: Meaning: Action: 759. Excessive Link CRC errors Severity: Meaning: Action: 761. SDLC Transmit link error Severity: Meaning: Action: 762. SDLC Link Stn rcv FRMR, Unexp. IFLD Severity: Meaning: Action:...

  • Page 377: Appendices

    Section IV Appendices...

  • Page 379: Appendix A Async Terminal Operations

    Before establishing an end-to-end link, an async terminal must make a connection to the async PAD, as follows: 1. Once the FRX4000/6000, async terminal, and any modems in the link are powered on, do this at the terminal: 2. If the port is configured (in the Port record) to not require login, go to step 3. If...

  • Page 380: Async Terminal Commands

    = Group Send = Priority = Reverse Charging = NUI – is the called address, mode. (For a list of commands, Command async PAD profile parameters 1–22 is available. for that address.) User data FRX4000/FRX6000 4.0 User Guide, Rev 01 = 1st...

  • Page 381: Async Pad Service Signals

    data An example of a Call Request to called address facility plus user data “ If the Call Request is successful, the async PAD will receive a Call Accept packet from the device at the other end of the call. Connection is now established, and the terminal will display COM.
  • Page 382 – is a response to the command, indicating that no VC is currently STAT FREE Status set up on the port. – indicates a called DTE reselection by the PAD to TRANSFER “nnnn” COM “nnnn.” FRX4000/FRX6000 4.0 User Guide, Rev 01...

  • Page 383: Error Codes Sent To Async Pad Port

    FRX4000/6000 .n.n” Asynchronous PAD when the terminal is switched on and DSR and DCD become active. When the node boots, the software looks for a file named BANNER.TXT (which does not exist when the software is sent to the customer). If the file is not present, the default banner is dis- played.

  • Page 385: Appendix B Cause And Diagnostic Codes

    Cause Codes Clearing Causes The clearing cause recorded in a call packet provides a high-level indication of why the call was cleared and where the error occurred (e.g., error by the source user, or internal network error). For example, when the diagnostic code indicates that a pro- tocol error occurred, the clearing cause might indicate that the error was committed by the destination user (i.e., remote procedure error).

  • Page 386: Reset Causes

    Packet type Invalid for State r2 Packet type Invalid for State r3 (Call Setup Phase) Packet type Invalid for State p1 Packet type Invalid for State p2 Packet Level Ready DTE Restart Request DCE Restart Indication Ready DTE Waiting FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 387 Hex. Dec. Cause and Diagnostic Codes Description Packet type Invalid for State p3 Packet type Invalid for State p4 Packet type Invalid for State p5 (Call Clearing Phase) Packet type Invalid for State p6 Packet type Invalid for State p7 (Reset during data xfer) Packet type Invalid for State d1 Packet type Invalid for State d2...

  • Page 388: Sna Codes

    Out of resources, no memory for hash entry Out of resources, no more concatanations available dlger, logic error MAC Driver Deleted Received DISCONNECT Received FRMR Due to configuration change Received DISCONNECT No code, cleanup problem Timer Ti expired Timer T1 expired FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 389 Hex. Dec. Description Cause and Diagnostic Codes Timer TConn expired Invalid LPDU Connection rejected (transient condition)

  • Page 391: Appendix C Netview Management

    SDLC devices, and allows diagnosing problems and changing parameters in the node. The service point in the FRX4000/6000 connects to the NetView host via an LLC2 session (over LAN or frame relay), which is established at node IPL. LLC2 must be installed in either the service point node or another FRX4000/6000 that is connected to the service point node via X.25 (physical link or over frame relay per Annex G or...

  • Page 392: Local Netview Access

    Local NetView Access The FRX4000 and FRX6000 support a local NetView access function that allows the node operator to send commands from the node to lines and PUs. This function is only between the node and lines/PUs—the commands and responses are not transmitted to NetView.

  • Page 393: Supported Commands

    NetView Management from NetView is generally as follows: RUNCMD is the VTAM PU name of the FRX4000/6000 (NetView sees the FRX4000/6000 as a PU), is the ID of the NetView operator issuing the command, and is the text of command sent to the FRX4000/6000.

  • Page 394: Vary Commands

    System Memory value(s) F NET, CONFIG,ID=“nnnn” in the FRX4000/6000 record for the SNA Port or LLC2 Host (depending on the parameter). The changes will be in effect until an on-line database update or re-IPL of the node is performed, or an (see below) is sent.
  • Page 395 IPL. Unlike the on-line update of a database record as per- [F7] formed locally on an FRX4000/6000, sending a and a do not disable the port, since they update the COMMIT node’s system memory and database values separately, instead of writing one set of values to the other.

  • Page 397: Appendix Dascii Character Table

    ASCII Decimal Character Value “ & (apostrophe) (asterisk) Appendix D ASCII Character Table Octal Ctrl Key Value Value Combination [Ctrl] [Space] [Ctrl] [A] [Ctrl] [B] [Ctrl] [C] [Ctrl] [D] [Ctrl] [E] [Ctrl] [F] [Ctrl] [G] [Ctrl] [H] [Ctrl] [I] [Ctrl] [J] [Ctrl] [K] [Ctrl] [L] [Ctrl] [M]...
  • Page 398 ASCII Character (comma) (hyphen) (period) < > (caret) (underline) (single quote) Decimal Octal Value Value Value FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 399 ASCII Character (pipe) (tilde) ASCII Character Table Decimal Octal Value Value Value...

  • Page 401: Appendix E Menu Structure

    Review Async PAD Logins Configure Async PAD Logins Review Model Information Configure Bandwidth Allocation Groups Configure RLPs (FRX6000) or ReviewRLP Protocol Configure RLP Display RLP Protocol Appendix E Menu Structure – Configuration Configure Protocols Configuration Protocol Memory Status ) are the (FRX4000)
  • Page 402 Disable a Range of Ports Enable a Port Enable a Range of Ports Quiesce a Port Quiesce a Range of Ports Unquiesce a Port Unquiesce a Range of Ports (FRX6000) LLC2 Interfaces LLC2 Interfaces relay) (X.25) (async) FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 403 Back up the Current Database to a Remote FRX6000 Restore the Backed-Up Database to a Remote FRX6000 Restore the Backed-Up Database to a Remote FRX4000 Back up the Current Database to a Local Directory Restore the Database from a Local Directory...
  • Page 404 E Statistics A Configure RLP / Port Thresholds B Display RLP / Port/Frame Display IP Statistics Display ICMP Statistics Display IP Interface Statistics Display IIPX Interface Statistics Display ILAN Card Interface Statistics Display Frame Relay Utilization Statistics F Reports Create Configuration Report View Configuration Report View Initialization Report View Previous Initialization Report...
  • Page 405 Menu Structure...
  • Page 406 FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 407 Auxiliary Console is an async terminal connected to a serial port (configured as COM1) in an FRX6000 or Frame Relay Module, or the Console port in an FRX4000, acting as an operator console. Async terminal is a VT100 or compatible video display terminal.
  • Page 408 Configuration database see “Database.” Congestion is a local condition that occurs when there are too many packets to be queued in the node buffers, causing information transfer to be delayed. glos-2 FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 409 DCE, the other must be DTE, and vice versa. Designated Bridge, Designated Port is the bridge (and the FRX4000/6000 port on the bridge) on a LAN that provides the minimum-cost path to the root bridge (described later). Dial Port is an X.25 port connected to a dialup modem.
  • Page 410 (e.g., configuration, function, operating state, performance, etc.), that is reported to automatic and specified destina- tions within the network the FRX4000/6000 is on. This term is synonymous with “alarm.” Fragment is an IP datagram that is a piece of a larger datagram, the larger one having been seg- mented to allow it to pass through a network that did not support the larger datagram.
  • Page 411 Line Interface Card is a four-port “daughter” card attached to an FRX6000 RLP, or mounted in an FRX4000, and containing the components that support a hardware interface: RS-232/ V.28, V.35, or RS-422/V.11. stands for “logical link control,” which is the third layer in the three-layer ISO LAN protocol hierarchy.
  • Page 412 Packet Switching is the breaking up of data into smaller pieces and the transmission of these pieces over a network via X.25. glos-6 FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 413 “packet assembler/disassembler,” which allows a non-X.25 device to access an FRX4000 or FRX6000, by converting its protocol to the X.25 packet mode pro- tocol, and vice versa. The FRX4000 and FRX6000 support integral async, SNA, and BSC PADs.
  • Page 414 “path cost,” which is the cost of transmitting a frame onto the LAN. SSAP stands for “source service access point,” which is the address of the link service access point (LSAP) from which a link protocol data unit (LPDU) originates. glos-8 FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 415 Subscriber is a user of an FRX4000 or FRX6000. stands for “switched virtual circuit,” which is a temporary logical association between two subscribers connected to a network, analogous to connection by a dial-up line. stands for “transmission control protocol,” which is the Internet standard transport layer protocol.
  • Page 416 SNA PAD types. It can be considered a fully transparent PAD for synchronous protocols; however, it is not intended for this use, because special application programs would have to be resident on the host. glos-10 FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 417 # of Beginning Sync Char 10-7 # of Beginning Sync Chars 11-6 # of Trailing Pad Characters 10-7 # of Trailing Pad Chars 11-6 1st/2nd/etc. Path Configured 8-26, 9-16, 10-10, 11-10, 12-17 Abbreviated Address, configuring Abort (F10) Access (Community Table) 16-4 11-6 Activate Connection w/o poll...
  • Page 418 11-7 8-21 7-23 13-12 15-9 13-16 15-10 14-7 14-7 14-7 13-13, 14-15 12-14 8-13 9-10 10-13 12-12 12-4 12-13 12-14 12-14 12-13 8-21 7-10 7-12 7-13 13-1 15-9 18-16 8-20 8-20 8-20 12-12 12-14 FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 419 Excess Burst Size (In/Out) 7-19 Exiting a menu F7 2-9, 4-2, Facilities 12-12 Fast Select Acceptance 8-11, 8-19 File backup, FRX4000 to local PC 18-8, File restore, PC to FRX4000 18-11 File transfer 18-4 File Transfer ID File Transfer Pwd (password) Files, operating...
  • Page 420 7-13 5-12 5-12 12-5 12-5 12-4 5-11 19-7 5-12 8-13 11-5 7-17 9-11 9-18 9-26 19-21 8-18 9-12 9-12 11-7 9-25 5-15 2-12 12-19 8-18 12-7 12-11 8-18 8-18 8-18 20-1 9-11 9-10 FRX4000/FRX6000 4.0 User Guide, Rev 01...
  • Page 421 11-5 8-17 Offset 11-5 On-line change (F7) 8-19 On-Line Temporary Changes 14-13 Operator interfaces FRX4000 FRX6000 Outgoing Access Allowed 8-13, Outgoing Calls Barred 8-11, Outgoing DLCI Priority Outstanding Frames Packet Size 8-35, 9-10, Packet Type Value PAD Recall PAD Service Signal Padding After Padding after <lf>...
  • Page 422 12-12 12-12 11-7 11-7 8-18 14-14 14-14 13-11 13-11 14-14 13-11, 13-14 19-27 13-5 FRX4000 FRX6000 5-11 13-14 13-16 13-16 14-18 14-7 14-2 13-11 9-24 19-24 8-10 12-13 11-7 11-7 14-14 14-14 19-27 FRX4000/FRX6000 4.0 User Guide, Rev 01 12-16...
  • Page 423 SDLC PU disabling 18-14 enabling 18-14 status, displaying 19-20 Sec. IP Addr 13-14 Secondary Alarm Output ID Secondary Alarm Output Pwd (password) Secondary C"n" NOT Initialized Secondary C"n" NOT Installed 4-10 Secondary Connection Problem 4-10 Secondary DLCI 7-22 Secondary Name 7-22 Secondary P"n"...
  • Page 424 WaitTimer 7-23 Watchdog Spoofing Enabled 14-15 Wildcards in subscriber addresses Window Size 8-35, 12-19 X.25 address translation templates X.25, configuring X.3 Line Speed 12-11 ZMODEM 18-8, 18-9 Idx-8 20-4 8-18 7-20 11-5 8-23 8-27 FRX4000/FRX6000 4.0 User Guide, Rev 01...

This manual is also suitable for:

Frx6000Netlink frx6000

Table of Contents