1. Manuals
  2. Brands
  3. Cabletron Systems Manuals
  4. Switch
  5. Netlink FRX8000
  6. User manual

Cabletron Systems Netlink FRX8000 User Manual

Fully integrated lan/wan enterprise switch
Hide thumbs Also See for Netlink FRX8000:
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
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
Table of Contents

Advertisement

Quick Links

Download this manual See also: Reference Manual

User Guide

For Release 3.0
The Com plete Network ing Solution
T M
09-41-06-150-02

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Related Manuals for Cabletron Systems Netlink FRX8000

Summary of Contents for Cabletron Systems Netlink FRX8000

  • Page 1: User Guide

    User Guide For Release 3.0 The Com plete Network ing Solution 09-41-06-150-02...
  • Page 3 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 FRX8000. Before using the manual, you should be familiar with FRX8000 hardware, as well as the protocols (frame relay, SNA, etc.) you will be using.

  • Page 5: Table Of Contents

    Producing Configuration Reports... 3-12 Configuring Network Defaults ... 4-2 Creating a Network Representation ... 4-9 Configuring Node Records... 5-2 FRX8000 RLP... 6-1 N7000 RLP... 6-6 N7000 RLP Parameters ... 6-7 N7000 Standard LP ... 6-8 N7000 T1 LP ... 6-10 N7000 E1 LP ...
  • Page 6 Configuring IP Interfaces... 13-4 Configuring a Static IP Route ... 13-8 Configuring IP-Over-X.25 PVCs... 13-10 Required and Optional Configuration ... 14-1 Configuring IPX Network and Node Parameters... 14-2 Configuring IPX Interfaces ... 14-3 Configuring IPX Filters... 14-11 FRX8000 3.0 User Guide, Rev 02...
  • Page 7 Chapter 15 Configuring SNMP Section III Operation Chapter 16 Introduction to System Operation Chapter 17 On-line Operations Chapter 18 Status Displays Chapter 19 Statistics Displays Chapter 20 Alarms Chapter 21 Tests Configuring a Static IPX Route... 14-18 Required and Optional Configuration ... 15-1 Configuring SNMP Parameters ...
  • Page 8 Enabling/Disabling Automatic Accounting File Rollover ... F-6 FRX8000 Switch ... G-1 FRX8000 ICP... G-2 FRX8000 INM ... G-4 FRX8000 NMP ... G-6 N7400... G-7 N7500, N7500-ICP, or N7500-INM ... G-8 The Initialization Report ... G-10 FRX8000 3.0 User Guide, Rev 02...
  • Page 9 FRX8000 Node Record ... 5-2 N7000 Node Record ... 5-3 FRX8000 RLP ... 6-2 FRX8000 RLP Configuration Menu ... 6-3 N7400/7500 RLP Configuration Record ... 6-6 N7400/7500 “Standard” LP Configuration Record ... 6-8 T1 DSX-1 LP Configuration Record ... 6-10 E1 LP Configuration Record ...
  • Page 10 On-Line Port Operations Menu... 17-1 V.25bis Dial Port Status Screen ... 17-2 Modem Operations Screen ... 17-3 Call Accounting File Display ... 17-15 Call Accounting File Structure... 17-16 Node Status Display ... 18-1 Port Status Display ... 18-2 FRX8000 3.0 User Guide, Rev 02...
  • Page 11 22-1 IP Ping Connectivity Test Menu... 21-3 System File Type Selection Menu ... E-1 LP Type Maintenance Menu ... E-2 Network Defaults Menu ... E-4 FRX8000 Test Menu ... G-1 FRX8000 INM Main Menu ... G-5 Node Performance Display... G-9...
  • Page 12 BSC Interactive Port Parameters ... 11-4 Subscriber Parameter... 11-9 BSC Interactive Subscriber Parameters... 11-11 Control and Device Unit Addressing... 11-13 BSC Interactive Device Parameter ... 11-14 Async PAD Profile Parameters ... 12-4 Async PAD Login Parameters... 12-9 FRX8000 3.0 User Guide, Rev 02...
  • Page 13 12-3 Async PAD Port Parameters... 12-11 12-4 Subscriber Parameters ... 12-18 12-5 Async PVC Parameters... 12-21 13-1 IP Interface Parameters... 13-5 13-2 IP Route Parameters ... 13-9 13-3 IP-over-X.25 PVC Parameters... 13-11 14-1 IPX LAN Interface Parameters... 14-4 14-2 IPX X.25 Interface Parameters ... 14-5 14-3 IPX Frame Relay Interface Parameters ...

  • Page 15: Section I

    Section I Getting Started...

  • Page 17: Chapter 1 Overview

    LAN and WAN data traffic over a single access line. The FRX8000 allows the features of conventional multi-protocol routers to be combined with those of fast packet switches, delivering high performance regardless of the demands of the access protocols being used.

  • Page 18: Summary Of Features

    Compatibility over frame relay network with IBM FEP with NCP 7.1 MAC-level virtual addressing Token ring, Ethernet, or frame relay interface SDLC-to-LLC2 and LLC2-to-SDLC conversion RFC1490 encapsulation in native LLC2, 802.3, or 802.5 format QLLC/NPSI compatibility FRX8000 3.0 User Guide, Rev 02...
  • Page 19 Support of Novell NetWare networks Connection of LAN-attached workstation to remote router or server via frame relay, X.25, Ethernet, or Token Ring, or FRX8000 trunk Filtering of certain types of traffic, for traffic control and access security Support of RIP and SAP...
  • Page 20 VGA monitor or remote ASCII terminal) of network nodes File transfer between INMs/NMPs, and from an INM or NMP to an ICP. (ICP is an FRX8000 Switch with all the functionality of the INM except the user interface) Remote software updates to FRX8000 Switches...

  • Page 21: Hardware Overview

    Each Switch supports frame relay, X.25, SNA/SDLC/LLC2, BSC, asynchronous, IP (including RIP, ARP, ICMP), IPX, and SNMP protocols. The base model of an FRX8000 Switch contains one RLP with one Line Interface Card, providing four WAN ports, and supporting up to 512 simultaneous logical ter- minations.

  • Page 22: Lan Adapters

    LAN cards (in any combination). Each LAN card supports one LAN interface. The ICP and INM support one Ethernet interface for FTP and telnet access. Chassis There are two chassis used in the FRX8000 product line, differing in size and capacity (see Table Operator Interfaces...

  • Page 23: Chapter 2 Getting Started

    INM on the operational network. Using the INM Menu System FRX8000 network management functions are carried out at one of three “levels” in an INM or NMP: System level – is where UNIX operating system functions, as well as some FRX8000 non-menu operations, are performed.

  • Page 24: Main Menu

    [Enter] in response to a prompt. [Enter] Be careful; pressing [Enter] next prompt to automatically select the default choice. . (Both are not always [F3] [Esc]. when it is not required may cause the FRX8000 3.0 User Guide, Rev 02...
  • Page 25 Section II Configuration...

  • Page 27: Chapter 3 Introduction To Database Configuration

    (The LP file contains all RLP records, the Node file all Node records, etc.) An identical database resides in each FRX8000 ICP and INM (and each N7000/FRX NMP), allowing the entire network to operate as a single entity.
  • Page 28 – Chapter 6 Configure Line Processor – Identifying parameters for all LPs in FRX8000 and N7000 nodes on the network. Includes identification of Line Interface Cards on RLPs, and installed protocols. Required for every LP. Configure LAN Card – Identification of types and locations of all Ethernet and Token Ring cards in FRX8000s on the network.
  • Page 29 – Chapter 7 (trunk), Chapter 8 Configure PVC Connection Chapter 9 (X.25), Chapter 13 (async), Chapter 14 (IP). Creation of “permanent” connections between FRX8000 ports. Identifies location, protocols at each end, operating parameters. Configure IP Route – Chapter 14. Creation of fixed routes for IP traffic.

  • Page 30: Database Setup Recommendations

    Most parameters can be configured using the operations described throughout Section II; others, such as LP or port number, are defined by the hardware or specified during software installation. “Configuration Operations” on 1–250 . To minimize occur- Not in Database FRX8000 3.0 User Guide, Rev 02...

  • Page 31: Configuration Operations

    Here is the recommended procedure for setting up or modifying the configuration database. Valid and default values for configuration parameters can be found in the appropriate chapters. 1. Create or modify the necessary database records. (To do this you will need to acquire 2.
  • Page 32 If you initialized the existing file but did not perform an initial file load, you will have to build a new file by creating new records (using operations). nance require master status. . Using Output to Hardcopy Device FRX8000 3.0 User Guide, Rev 02 Main- , print the ; if you are Mainte-...
  • Page 33 List This operation displays, prints, or saves to disk, a summary of the contents of a database file. Because a list contains parameter values but not their names, summaries will be fairly cryptic and may require some interpretation, as is evident in the example Figure but by Cabletron Systems Technical Support.

  • Page 34: Output To Terminal" Display

    Output to Terminal At the Output Device Menu, press as shown in the following figure. The information is scrolled; i.e., until the end is reached, it passes by on the display to make room for more. To stop the scrolling, press [Scroll Lock] Press [F3]...

  • Page 35: Inquiry" Example

    For most operations, your options from here are: To see another record, press To see the next record, press To return to the Operations Menu, press To return to the Main Menu, press Maintenance Maintenance nance alters the database, you must first acquire master status.) 1.

  • Page 36: Maintenance" Example

    You cannot copy a physical port’s record to a logical port, or vice versa. [F2] , press: Delete? ”), or ), and message like that in option “ ” will be FRX8000 3.0 User Guide, Rev 02 , then [F1]...

  • Page 37: Master Status

    Master Status “Database Master” status is a mechanism for assuring concurrence throughout the network. A copy of the database resides in each FRX8000 ICP and INM, and each N7000/FRX NMP. For the network to operate properly, all copies must be identical.

  • Page 38: Producing Configuration Reports

    Multiple database master at Cabletron Illegal LP ID page 3-13. to include all nodes. [Enter] . To print the report, type p [Enter] and enter a file name when asked for a file FRX8000 3.0 User Guide, Rev 02 . To...
  • Page 39 If you experience problems on the network, the following procedure might help solve them: 1. Review the status messages (described in 2. If the problem is not apparent from the messages, print a configuration report. It might contain warnings and errors caused by inaccuracies or inconsistencies in your database information.

  • Page 41: Chapter 4 Configuring Network Parameters

    IPX Filter Definitions (described in Chapter 15) – used to maximize efficiency on a WAN network connected via an FRX8000 to a Novell Netware network. Filters are applied to IPX traffic as defined by IPX Applications records. Frame Relay Bandwidth Allocation relay bandwidth use, ensuring that response time-sensitive traffic gets access to the available bandwidth.

  • Page 42: Configuring Network Defaults

    Configuring Network Defaults The Network Defaults file contains one set of parameters whose values apply to all FRX8000 and Nucleus 74/7500 nodes in the network. This differs from other database files, which contain individual records for each component type (nodes, LPs, ports, etc.).
  • Page 43 When Changes Take Effect Changes to this file are written immediately to the database. You must then perform Update Network Defaults 1. Press 2. When asked: 3. You will be asked: and described in changed as described under “Alarm Severity Levels” on page 1. If the severity level file has been changed, press (Otherwise, press 4.

  • Page 44: Network Default Parameters

    Default Value 0–20 characters NETLINK 10–99 0–255 1–4096 0–9999 0000 0–254 0–255 disabled valid IP address 192.0.0.0 1–fffffffe 00000001 5–360 5–360 5–360 5–360 5–360 5–360 5–360 5–360 0–10 0–10 0–10 1–4095 16–4096 1–7 1–100 0–9 FRX8000 3.0 User Guide, Rev 02...
  • Page 45 FRX8000 containing each interface will be appended to this address for further iden- tification. (IP configuration is described in IPX WAN Network Address identifies all FRX8000 IPX interfaces on a Novell network. (If there is no Novell network in this configuration, the parameter will be ignored.) Configuring Network Parameters...
  • Page 46 DTE Clear Re-xmit Count is the number of times a Clear Request from the logical DTE will be transmitted. (The DTE will stop issuing the request on receipt of a Clear Confirmation or Clear Indi- FRX8000 3.0 User Guide, Rev 02...
  • Page 47 cation.) If the Clear Retransmit Count expires, restart and recovery procedures should be initiated. DTE Reset Re-xmit Count is the number of times a Reset Request from the logical DTE will be transmitted. (The DTE will stop issuing the request on receipt of a Reset Confirmation, Reset Indication, or Clear Request.) If the Reset Retransmit Count expires, restart and recovery proce- dures should be initiated.
  • Page 48 Send update? Update alarm severity table? at the prompt to send the update to all nodes. (Oth- to return to the Operations Menu. [Enter] Alarms have associated severity page 21-1. If the severity level file FRX8000 3.0 User Guide, Rev 02...

  • Page 49: Creating A Network Representation

    Creating a Network Representation Network Representation maintenance operations allow you to create a visual description of your network, with a geographic outline and network components. The information can then be retrieved in the 10), which shows on-line status for the components you placed into the record. The components in a network display are represented by various icons, shown in Figure 4-4.

  • Page 50: Status Display Icons

    Environs Menu) to Return FRX8000 or N7500 ICP/INM N7400 with N7500 with attached NMP attached NMP N7500 DPPM Subnetwork . Cursor movement is controlled as listed [Num Lock] causes the cursor to move a FRX8000 3.0 User Guide, Rev 02...
  • Page 51 Pull-down Menus Each selection across the top of a screen has an associated pull-down menu that appears when the selection is chosen. When a pull-down menu appears, the default selection appears in white text on a black background. Other items are in black text on a white background, unless they are not valid at the current level or point, in which case they appear in light gray text on a white background.
  • Page 52 – leaves this menu and returns you to the choices at the top of the screen. Cancel 4-12 Scandinavia (similar to nordic) Belgium, Netherlands, Luxembourg Far East (shown in Figure 4-3) Middle East – allows you to change the name of the current subnetwork. Return FRX8000 3.0 User Guide, Rev 02...

  • Page 53: Configuring Node Records

    The Node file contains the locations, node types, alternate nodes (for receiving network data), and alarm routing information for every node in the network. N odes S election Menu A Configure Nod e B Configure SN MP Parameters R Return to Previous Menu S elect: Figure 5-1 Nodes Selection Menu Node-wide SNMP parameters, also accessed from this menu, are described...

  • Page 54: Frx8000 Node Record

    Configuring Node Records A Node record must be created for each FRX8000 Switch, ICP, and INM, as well as every N7400 and N7500, in the network. To configure a record, press from the Nodes Selection Menu Node assigned during software installation.

  • Page 55: N7000 Node Record

    A change to any other parameter will take effect after the next IPL of the configured node, with the exception of necessary changes have been made at the node to add/remove system board memory and UNIX and FRX8000 software) by performing a Download Operations Configuring Node Records...

  • Page 56: Node Parameters

    NMP, the alternate NMP Node will provide the local node with network defaults and other network data. If the local (FRX8000 or N74/7500) node has a locally attached NMP, or is an ICP or INM, the alternate NMP Node will take over the local node’s man- agement functions (receiving alarms, updating parameters, etc.) if the local node...
  • Page 57 FRX8000 RLPs. N7000 RLPs are type If any ports in the node are configured as physical X.25 (FRX8000), these Port records must also be changed. The two are equivalent, but are created differently. The logical trunk is defined entirely in one PDN Port record in the N7000, but in two records—Logical Trunk Port and under-...
  • Page 58 1024 or 2048 connections with a purchased upgrade kit. SNA LLC2 Virtual LAN ID is used internally by the FRX8000 to identify a virtual bridge that connects the LLC2 function to LAN interfaces. This ID is normally assigned by a system administrator.
  • Page 59 This function requires entry of a serial number and activation key, which will be pro- vided by Cabletron on request. If it is desired that re-entry be required to re-enable the parameter, the Node record must be deleted and a new one created, or the record can be copied to another record, then copied again from that record to the first one.

  • Page 61: Configuring Lps And Lan Cards

    T1/E1 LPs. FRX8000 RLP The FRX8000 RLP is a mother card with one or two attached four-port Line Interface Cards (LICs). The RLP supports all FRX8000 port types. Port I/O interfaces available are RS-232-C/V.28, RS-449/V.36, RS-530, X.21, and V.35. The interfaces supported...
  • Page 62 LIC 1 LIC 2 I/O Box Figure 6-1 FRX8000 RLP Switch On On Off On Off On On Off Off Off On On Off On Off Off Off On Off Off Off RLP Cable FRX8000 3.0 User Guide, Rev 02...

  • Page 63: Frx8000 Rlp Configuration Menu

    The change will become effective at the RLP in one of the following ways: A change to an RLP in an ICP or INM is immediately effective when the database record is changed. A change to an RLP in an FRX8000 Switch can be implemented by performing Configuration Update taining the LP.

  • Page 64: Frx8000 Rlp Parameters

    Table 6-1 FRX8000 RLP Parameters (1–5) (0,1) An FRX8000 RLP always has 4MB. One protocol on each RLP must be X.25 (type displays a range of 1–7 If you replace a Line Interface Card with one of a different type, any related port records will have some invalid values.
  • Page 65 Protocol 1–5 specifies the protocols that will be loaded onto the LP software on boot-up. = None = Async = IP = TRNK (Trunk) Note these requirements and recommendations: Each RLP must have X.25 configured. RIP is valid only if IP is already configured on the RLP. SNMP will not work unless IP is also configured in the node.

  • Page 66: N7000 Rlp

    1, which is transmitted as the most significant bit of the non-frame alignment signal when CRC-4 is disabled. N7000 RLP The N7000 RLP is nearly identical to the FRX8000 RLP, shown in To configure an LP record, press [A], [C], [C]...

  • Page 67: N7000 Rlp Parameters

    When Changes Take Effect When you add a new LP record, the change will be written to the database as soon as you enter the final parameter value. When you modify an existing record, the change will be written to the database immediately. The change will become effective at the LP in one of the following ways: A change to an RLP in an ICP, INM, or NMP node is immediately effective when the database record is changed.

  • Page 68: N7000 Standard Lp

    B Big Pack et Su pported Select: Figure 6-4 N7400/7500 “Standard” LP Configuration Record at the Line Processor Configuration . (Default is the “local” node). 1–250 Table 5-3. (Press [A],[C],[C] from Main Menu FRX8000 3.0 User Guide, Rev 02 [Enter]...

  • Page 69: N7400/7500 "Standard" Lp Parameter

    When Changes Take Effect When you add a new LP record, the change will be written to the database as soon as you enter the final parameter value. When you modify an existing record, the change will be written to the database immediately. The change will become effective at the LP in one of the following ways: A change to an LP in an ICP, INM, or NMP node is immediately effective when the database record is changed.

  • Page 70: N7000 T1 Lp

    Figure 6-5 T1 DSX-1 LP Configuration Record Item is not displayed for a DSU LP. from the Main [A], [C], [C] . (Default is the “local” node). 1–250 Table 5-4. (Press [A],[C],[C] from Main Menu FRX8000 3.0 User Guide, Rev 02 [Enter]...

  • Page 71: N74/7500 T1 Lp Parameters

    When Changes Take Effect When you add a new LP record, the change will be written to the database as soon as you enter the final parameter value. When you modify an existing record, the change will be written to the database immediately. The change will become effective at the LP in one of the following ways: A change to an LP in an ICP, INM, or NMP node is immediately effective when the database record is changed.

  • Page 72: N7000 E1 Lp

    .), as determined by switch settings on the card. (See 0–7 = 267-399 ft. = Master, = Slave from the Main [A], [C], [C] . (Default is the “local” node). 1–250 Table 5-5. (Press FRX8000 3.0 User Guide, Rev 02 [Enter]...

  • Page 73: E1 Lp Configuration Record

    Pressing Table 5-5. Some entries will or will not appear on that screen, depending on values selected for other parameters. When Changes Take Effect When you add a new LP record, the change will be written to the database as soon as you enter the final parameter value.

  • Page 74: E1 Lp Parameters

    HDB3 G.704 0–1 G.703 Primary 0–1 Y/N ( On/Off Y/N ( On/Off 0–1 Y/N ( On/Off Y/N ( On/Off , the supported types are: 1–6 , only is valid for E1 LP. 0–3 FRX8000 3.0 User Guide, Rev 02...
  • Page 75 Clocking is the clocking mode in which the LP runs: National Use Bit “n” is the setting of the national use bits in the non-frame alignment signal. National use bits 1-5 correspond to data bits 4-8 in the non-frame alignment signal. National use bits are reserved for use within a country.

  • Page 76: Configuring T1/E1 Channel Maps

    , and instead of item there is an item Number 1–250 . (Default is the local Table 5-6. (Press [A],[F],[I],[C] from Main Menu ), item Secondary LP Start DS0 Number while still in Maintenance opera- [F7] FRX8000 3.0 User Guide, Rev 02 [Enter]...

  • Page 77: T1/E1 Channel Map Parameters

    Data Card Number Expansion LP Number Por t Number Line Conditioning 1 Type 1 is not supported in the current FRX8000 release. Group Name is a description for the channel map. Base Rate is the line speed of individual DS0 channels configured in this channel map.

  • Page 78: Configuring Lan Cards

    Configuring LAN Cards LAN cards are supported in the FRX8000 Enterprise Switch for IP routing across the network, and in the ICP, INM, and NMP for local FTP and telnet file operations. To configure a record for a LAN card, press from the Main Menu).

  • Page 79: Protocol.ini Sample Report

    PROTOCOL.INI The PROTOCOL.INI file contains information that identifies the type(s) and operating parameters of any installed LAN card(s) in an FRX8000 Switch, ICP, or INM. You can create a Node LAN Card Configuration Report, which contains the PRO- TOCOL.INI information from one or all FRX8000 nodes in the network. This report can be displayed, printed, or saved to a file for later use.

  • Page 81: Chapter 7 Configuring Inter-Nodal Trunks

    An FRX8000 supports up to 64 trunks to up to 64 nodes. An N7400 or N7500 supports up to 31 trunks to up to 20 nodes. A trunk between an FRX8000 and an N74/7500 can be created by configuring both ends as physical trunk, or by configuring the FRX8000 port as logical trunk over X.25 and the N74/7500 port as a logical PDN port.

  • Page 82: Required And Optional Configuration

    V.25bis modem. Subscriber called and calling address specified in logical trunk records. PVC Connection want to create a “permanent” connection between an FRX8000 logical trunk port and its underlying physical X.25 port. Telephone V.25bis modem.

  • Page 83: Configuring Trunk Port Records

    [A], [D], [A], [C] (of the node containing the port): (of the LP containing the port): for a physical port on an RLP, 0–7 for a logical port. (If configuring an FRX8000 logical port, enter the 8–63 (Figure 7-4). Port Main ten ance...

  • Page 84: Physical Trunk Port Record For Non-V.25Bis Port

    2 Backup Trunk Parameters Select: Figure 7-4 Logical Trunk Port Record Pressing will display more parameters, all listed in from Main Menu [A],[D],[A],[C] is an Physical Interface , and Generate Clock from Main Menu [A],[D],[A],[C] FRX8000 3.0 User Guide, Rev 02 Table 7-1.

  • Page 85: Trunk Port Parameters

    When Changes Take Effect at the Port When you add a new Port record, it will be written to the database as soon as you enter the final parameter value. When you modify a parameter in an existing record, the change will be written to the database immediately.
  • Page 86 Line speed codes are as follows. (Some speeds have two corre- Table 7-1 Trunk Port Parameters (sec) is frame relay, and is valid only on FRX8000 ports. , leave Called Address other end of trunk will be an N74/7500.
  • Page 87 = 2.048M The maximum for an RS-232 interface on an N7400 or 7500 is 19.2K. The maximum for an RS-232 interface on an FRX8000 is 64K if the port is directly connected to the user device via the 5-foot Cabletron RS-232 cable.
  • Page 88 (e.g., from a satellite dish to a satellite). This helps the FRX8000 determine the fastest routing. The value to be specified is normally determined by the signal carrier.
  • Page 89 If the remote end of the trunk will be an N74/7500, tiple channels must be configured as separate logical ports (X.25 trunks on the FRX8000, PDN on the N74/7500), each identified by a unique address. specifies whether this logical trunk is one end of a PVC to the underlying physical X.25 port.

  • Page 90: V.25Bis Modem Operations

    : up to 10 characters. This must match a Table 7-2 Modem Initialization Parameters from the Main Menu). When [A], [D], [E] Modem INI String Name Valid Values Default Value up to 24 characters none 0–255 up to 35 characters none FRX8000 3.0 User Guide, Rev 02 con-...

  • Page 91: Configuring N74/7500 Pdn Ports

    Initializing a Modem Here is the normal sequence for initialization of a V.25bis modem: 1. After receiving a Port Enable from the FRX8000 software, DTR will be asserted on the port. 2. If the modem is powered on and in AT mode, it will return CTS.

  • Page 92: Physical Pdn Port Record

    B Blocked Port Flag C C alling A ddress 12345 D C alled A ddress 67890 Select: Figure 7-6 Logical PDN Port Record from Main Menu [A],[D],[A],[C] is an Physical Interface Generate Clock [A],[D],[A],[C] from Main Menu FRX8000 3.0 User Guide, Rev 02...

  • Page 93: Physical Pdn Port Parameters

    PDN Port Parameters Parameter Por t Type Physical Interface Blocked Port Flag Line Speed Code Outstanding Frames N2 Maximum Retransmissions T1 Retransmission Period T2 Acknowledgment Delay T3 Link Assurance Period Maximum Packet Size Logical DCE Generate Clock Rcv Clock (TT) from DTE Mask Link Alarms Propagation Delay Lowest/Highest Incoming Channel...
  • Page 94 = 1.064M = 1.288M = 1.344M = 1.568M = 1.624M = 192K = 256K = 512K = 576K = 832K = 896K = 1.152M = 1.216M = 1.472M = 1.536M = 1.728M = 1.856M FRX8000 3.0 User Guide, Rev 02...
  • Page 95 (e.g., from a satellite dish to a satellite). This helps the FRX8000 determine the fastest routing. The value to be specified is normally determined by the signal carrier.
  • Page 96 Port record, will be used. (If either is value will be used. If is selected, any throughput class Maximum Throughput Class Maximum Throughput Class FRX8000 3.0 User Guide, Rev 02 is selected, a Maximum Packet Size is selected, the , will be used. (If a class...

  • Page 97: Configuring Subscriber Ids

    Logical Port Parameters Underlying Physical Port is the physical PDN port (whose record must be configured first) on which this logical port is being configured. Blocked Flag causes the logical port to be enabled ( remain in that state until this parameter is changed (and sent to the node) or an on-line enable/disable is performed.

  • Page 98: Svc Subscriber Record

    Table 7-4 Subscriber Parameters Valid Values 0–24 characters n/a - not yet supported 0–2 1–3 valid node/LP/port valid address [A],[F],[A],[C] from Main Menu are listed in Table 7-4. Default Value none Not used Not used FRX8000 3.0 User Guide, Rev 02...
  • Page 99 Subscriber Name identifies the subscriber to the console operator. The FRX8000 software does not use this information. Routing Algorithm allows creation of a “hunt group” of ports, for the purpose of routing per a pre-selected algorithm: to the Routing Paths. If the selected port is unreachable or congested, the Call Request will be sent to the next port.

  • Page 100: Configuring A Pvc For A Logical X.25 Trunk

    Configuring a PVC for a Logical X.25 Trunk A “permanent” connection can be configured between an FRX8000 Switch logical trunk and its underlying physical X.25 port. (N7400 and 7500 do not support trunk PVCs.) This allows communication between remote devices as soon as the physical link is up.
  • Page 101 (LCNs) assigned to PVCs must be lower than the lowest LCN specified for any SVC subscriber IDs on the physical port. Description identifies this end of the logical connection to the console operator. The FRX8000 software does not use this information. Packet Size is the maximum packet size that will be transmitted on the PVC.
  • Page 102 Create rejected, reason “n,” ) or physical ( ) end was bad. or the LP/port was not operational. ) or physical ( where: Subscriber ID: FRX8000 3.0 User Guide, Rev 02 ) end.

  • Page 103: Configuring Telephone Numbers

    Configuring Telephone Numbers The Telephone Number file contains telephone numbers for any dial-up subscribers on the network (if the network is equipped with supported auto-dial hardware). Telephone numbers are used to place calls to other subscribers. Press from the Main Menu.) When prompted, enter: Telephone number Any other requested information, noting the values in at a prompt to specify the default.)

  • Page 104: Telephone Number Parameters

    = 112K Node ID . This way, if the primary node goes down, is replaced, then Default Value none = 600 = 2400 = 48K = 56K = 128K = 224K Alternate Node 1 FRX8000 3.0 User Guide, Rev 02...
  • Page 105 Facilities Parameters Preferential CUG Flag specifies whether the port belongs to any CUGs. Preferential CUG Index is a default Closed User Group for the port. Any calls that do not specify a CUG will default to this one. A new record has CUG 0 specified here; this is not a valid number, and signifies that the subscriber belongs to no CUGs.
  • Page 106 7-26 FRX8000 3.0 User Guide, Rev 02...

  • Page 107: Chapter 8 Configuring Frame Relay

    Frame relay ports in the FRX8000 are used to carry frame relay traffic, (over physical ports), as well as other protocols encapsulated in frame relay (per RFC 1490, over logical ports). A frame relay port can act as physical DCE, connecting to end-user devices, or DTE, connecting to a network or frame relay PVC.

  • Page 108: Configuring Bandwidth Allocation Groups

    U se Exces s: N U se Exces s: N U se Exces s: N U se Exces s: N U se Exces s: N U se Exces s: N [A],[A],[G],[C] from Main Menu FRX8000 3.0 User Guide, Rev 02...

  • Page 109: Bandwidth Allocation Group Parameters

    Use Excess will (if ) (configured in frame relay Port records) to be transmitted. Any packets exceeding will be buffered in the FRX8000. Configuring Frame Relay Table 8-1 Bandwidth Allocation Group Parameters ) allow traffic that falls between the Committed (B...

  • Page 110: Configuring A Frame Relay Port Record

    Main Menu). When prompted, 1–250 . (Default is the “local” node.) . (Default is 0–7 [A],[D],[A],[C] from Main Menu Physical Interface RS-530 RS-422 t is ) or Link Managemen FRX8000 3.0 User Guide, Rev 02 from the , or Annex-...

  • Page 111: Frame Relay Port Parameters

    When Changes Take Effect at the Port When you add a new Port record, it will be written to the database as soon as you enter the final parameter value. When you modify a parameter in an existing record, the change will be written to the database immediately.
  • Page 112 = 2.048M The maximum for an RS-232 interface on an N7400 or 7500 is 19.2K. The maximum for an RS-232 interface on an FRX8000 is 64K if the port is directly connected to the user device via the 5-foot Cabletron RS-232 cable.
  • Page 113 Mask Link Alarms determines whether an alarm (see down. If Link Management determines whether, and what type of, configurable network management will be allowed: = none = LMI (Local Management Interface) = ANSI T1.617 Annex D N1 Polling Count is the frequency with which the user device will request a Full Status Report, which shows frame relay PVC status and Keep Alive Sequence information.

  • Page 114: Configuring Pvcs

    Configuring PVCs An FRX8000 PVC is a “permanent” connection between two remote subscriber ports. 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. To add or change a PVC, press...

  • Page 115: Frame Relay-To-Frame Relay Pvc Parameter

    Percent of Bandwidth Defaults file. (See Primary/Secondary Name identifies each end of the connection to the console operator. The FRX8000 software does not use this information. Primary/Secondary DLCI is the Data Link Connection Identifier for each end of the connection. The DLCI is a routing ID that assigns a frame to a particular logical connection.

  • Page 116: Configuring Frame Relay Dlcis

    ) end was bad. ) or remote ( , reason “ ,” where: Subscriber ID [A], [D], [B, (Default is the 1–250. . (Default is 0–7 for a logical port. 8–63 FRX8000 3.0 User Guide, Rev 02 , reason ) end. [Enter]...

  • Page 117: Frame Relay Dlci Record

    When Changes Take Effect Changes to this file take effect when the associated physical port is updated by one of the methods described under in this chapter. A change can be implemented on line by exiting the record ( opening the associated physical Port record and pressing Parameter Committed Information Rate Committed Burst Size...
  • Page 118 ) is the maximum amount of data in excess of the network will attempt to transfer during the time period defined by B exceeding this value will be buffered in the FRX8000 node. Enable DE if Appropriate will cause (if (described earlier) is exceeded.

  • Page 119: Configuring X.25

    Ports configured as logical X.25 support logical X.25 links over a physical frame relay port. Required and Optional Configuration To run X.25 in an FRX8000 Switch or N74/7500, make sure the following are cor- rectly configured in the database: Network new network.

  • Page 120: Configuring An X.25 Port Record

    . (Default is the “local” node.) 1–250 . (Default is 0–7 for a port on an AST LP (N7400/ 0–3 Table 9-1. (Press [A],[D],[A],[C] from Main Menu is an Physical Interface Table FRX8000 3.0 User Guide, Rev 02 [A], [Enter] 9-1.

  • Page 121: Logical X.25 Port Record

    When you add a new Port record, it will be written to the database as soon as you enter the final parameter value. When you modify a parameter in an existing record, the change will be written to the database immediately. The change will become effective at the port in one of the following ways: Press rarily disable the port, then write the change to the software running in the node.

  • Page 122: X.25 Port Parameters

    0–15 digits (sec) 1–600 1–600 (sec) 1–600 (sec) 1–600 (sec) Default Value (AST LP (RLP 2000 1000 (not used) see note (not used) see note Max. Packet Size see note Max. Window Size none FRX8000 3.0 User Guide, Rev 02...
  • Page 123 Big Packet Supported Default Packet Size in Network Defaults, or is greater than and LP is not configured for FRX8000 Switch ports only. in Network Defaults file. Default Window Size N7000 V.25bis ports only. The connection defined by the card, port, and DLCI must be different for each logical connection (logical port, IP/IPX interface over frame relay) in this node.
  • Page 124 = 2.048M The maximum for an RS-232 interface on an N7400 or 7500 is 19.2K. The maximum for an RS-232 interface on an FRX8000 is 64K if the port is directly connected to the user device via the 5-foot Cabletron RS-232 cable.
  • Page 125 T2 Acknowledgment Delay is X.25 timer I-frame if there is no outgoing I-frame to be sent. If during this period the node receives an I-frame for transmission, the acknowledgment will be sent with it, and the delay timer will be reset. T3 Link Assurance Period is X.25 timer terpart if there is no data transfer.
  • Page 126 = 300 = 4800 = 9600 = 64K is selected, the is selected, any throughput class , will be used. (If a class value will be used.) = 600 = 1200 = 19.2K = 48K FRX8000 3.0 User Guide, Rev 02...
  • Page 127 Restart Timer will be started when the port issues a Restart Request, and stopped (and reset) when a Restart Confirmation or Restart Indication is received. If the timer expires, the port will retransmit the Restart Request. Incoming Call Timer will be started when the port issues a Call Request packet, and stopped (and reset) when a Call Connected, Clear Indication, or Incoming Call is received.

  • Page 128: Logical Port Parameters

    Allocation 9-10 Make sure no more than one of any interface type (logical port or frame relay IP/IPX/LLC2 interface) is assigned the same DLCI. relay) frame relay) Groups" on page 8-2. "Configuring Bandwidth FRX8000 3.0 User Guide, Rev 02...

  • Page 129: Configuring X.25 Closed User Groups

    CUG may be denied (determined by the Port record parameters CUG index number is included in call packets, and is cross-referenced with the CUG Index in the FRX8000 software. To configure a CUG, press prompted, enter: Node ID 1–250...

  • Page 130: V.25Bis Modem Operations

    ) transmission of outgoing calls within a specific at the Port Configuration Menu (or (specified in the Port record). Port” on page 9-3. A ), then opening the asso- [F3] Default Value from the Main Menu). When [A], [D, [E] FRX8000 3.0 User Guide, Rev 02...

  • Page 131: Modem Initialization Parameters

    Initializing a Modem Here is the normal sequence for initialization of a V.25bis modem: 1. After receiving a Port Enable from the FRX8000 software, DTR will be asserted on the port. 2. If the modem is powered on and in AT mode, it will return CTS.

  • Page 132: Configuring Subscriber Ids

    Routing Path s Redirection Ad dres ses S elect Figure 9-4 SVC Subscriber Record at the Subscriber Configuration Menu Subscriber ID [A], [F], [A], [C] from Main Menu are listed in Table 9-1. FRX8000 3.0 User Guide, Rev 02 , up to...

  • Page 133: Subscriber Addressing

    A Remote Control ID in a SmartSwitch 1800, FRX4000, FRX6000, or SmartSwitch 9000 Frame Relay Module can be used by an FRX8000 INM or NMP to take remote control of another Netlink device on the same network. Before this can be done, a Sub- scriber record must be created in the FRX8000 database, with the Remote Control ID of the remote device configured as an FRX8000 Subscriber ID.

  • Page 134: Wildcard Addressing Example

    Subscriber ID (described in the chapters that deal with specific protocols). Subscriber ID If subscriber ,the FRX8000 searches for a match, finds 12304 node 2, and out LP 0, port 0. Search Order for Subscriber Addresses A subscriber address that includes a wildcard potentially matches more addresses than one with no wildcards.

  • Page 135: Subscriber Parameters

    1st,2nd,etc. Routing Path 1st,2nd,etc. Redirected Sub No.. Subscriber Name identifies the subscriber to the console operator. The FRX8000 software does not use this information. Routing Algorithm allows creation of a “hunt group” of ports, for the purpose of routing per a pre-selected algorithm: to the list of Redirection Addresses.

  • Page 136: Configuring Pvcs

    A PVC is a “permanent” connection between two remote subscriber ports. 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. FRX8000 Switch and N7400/ 7500 support X.25-to-X.25 PVCs. FRX8000 also supports IP-over-X.25 PVCs...

  • Page 137: X.25-To-X.25 Pvc Parameters

    When Changes Take Effect When you add a new PVC record, the change will be written to the database as soon as you enter the final parameter value. When you modify a parameter in an existing record, the change will be written to the database instantly. The virtual connection will be established when the nodes at both ends undergo re-IPL.
  • Page 138 Primary/Secondary Subscriber Name identifies the subscribers to the console operator. The FRX8000 software does not use this information. Primary/Secondary Packet Size is the size of packets coming from each subscriber device. Primary/Secondary Window Size is the window size for packets coming from each subscriber device.

  • Page 139: Configuring X.25 Address Translation Templates

    Configuring X.25 Address Translation Templates The FRX8000's X.25 address translation feature provides automatic translation of selected fields within a Call Request packet, according to a previously defined “tem- plate.” You can change the called address, calling address, user data, and/or facilities fields of a Call Request packet as it passes into or out of the node.

  • Page 140: Backup Using Address Translation

    PDN-compatible called and calling addresses. Node 2 has a translation template defined to intercept packets with the PDN-compatible calling address for Node 1. It translates these into the FRX8000-compatible calling address for Node 2. (The backup routing is transparent.)

  • Page 141: Address Translation Template Record

    When Changes Take Effect Changes to this file will take effect when the associated port is updated by one of the methods described under change can be implemented on-line by exiting the record ( ciated Port record and pressing Translation Template Parameters Parameter Template ID Calling Address...
  • Page 142 L1234 [Enter] 1234 , indicating 1–9 A–F takes the first, second, third, X1234 [Enter] 31101234567800 , then takes the characters from the original 1–9 A–F 1–9 A–C FRX8000 3.0 User Guide, Rev 02 , indicating , indicating...

  • Page 143: Replacing Protocol Id

    = Text (valid for replacement of user data only). Type by the text that will replace the user data. Replacing Protocol ID Enter a string of up to four hex bytes. If fewer than four bytes are entered, the remaining field is filled with zeroes. Replacing Facilities Enter a string of up to 109 hex bytes.

  • Page 144: Configuring Group Send Groups

    Wildcards are not valid in the subscriber ID entered here. If you are creating a record for a subscriber ID that contains wildcards, substitute real characters. in the facility field. The Call Request is sent in 0901 FRX8000 3.0 User Guide, Rev 02...

  • Page 145: Configuring Telephone Numbers

    Producing a Group Send Report A Group Send report is really two reports in one. The first part lists the subscribers that belong to each defined Group Send group. The rest of the report lists the Group Send groups to which each subscriber belongs. The information in this report consists of the information in the Group Send file and the Group Name file.

  • Page 146: Telephone Number Parameters

    0–99 Modem Initialization file. (See page 9-12.) = 150 = 300 = 9600 = 19.2K = 72K = 112K Default Value none = 600 = 2400 = 48K = 56K = 128K = 224K FRX8000 3.0 User Guide, Rev 02...
  • Page 147 For an incoming call, if the primary node is not available, the subscriber calls another node, and that node becomes the new primary node in the Telephone Number record. It is recommended that when a Telephone Number record is created, be the same as comes back up, it will be the first alternate if the new primary goes down.
  • Page 148 9-30 FRX8000 3.0 User Guide, Rev 02...

  • Page 149: Chapter 10 Configuring Sna

    The SNA PAD function allows an SNA host to connect via an FRX8000 or N7000 HPAD to up to 16 TPAD devices (e.g., cluster controllers). HPAD and TPAD(s) can be in the same or separate FRX8000 nodes. Using QLLC (Qualified Logical Link Control), the host can connect directly to the X.25 network and the remote TPAD(s) without going through an HPAD.

  • Page 150: Required And Optional Configuration

    Required and Optional Configuration To run SNA on a port in an FRX8000 Switch or N7400/7500, make sure the following are correctly configured in the database: Network new network. After that, no further changes are generally necessary. Node FRX8000, N7400, and N7500 on the network.

  • Page 151: Sna Configuration Example

    SNA Configuration Example FRX8000 Node 1 HPAD SDLC X.25 In the example in Figure 11-2, the following records are necessary to configure SVCs (switched virtual circuits) from SNA host 1001 to PUs 2002 and 3003. (The port parameters are described on Node records for Nodes 1 and 2.

  • Page 152: Configuring An Sna Port

    Ports Selection Menu (or . (Default is the “local” node.) 1–250 . (Default is 0–7 Table 11-1. (Press [A],[C],[A] from Main Menu Physical Interfac Default Window Size FRX8000 3.0 User Guide, Rev 02 [A], [Enter] e is , and...
  • Page 153 If you are configuring an FRX8000 SNA port, the second screen will identify the PAD type and some of its operating parameters. (The physical devices con- nected to the PAD will be defined in the FRX8000 SDLC-PU file, described on page If you are configuring an N7000 HPAD, the second screen defines the first TPAD.

  • Page 154: Sna Port Parameters

    Table 11-1 lists all SNA Port parameters, and explanations of most parameters follow the table. Note that not all parameters will be displayed in any one record—some are FRX8000 only, some N7000 only. Also, some parameter values determine which other parameters will be displayed.
  • Page 155 = 2.048M The maximum for an RS-232 interface on an N7400 or 7500 is 19.2K. The maximum for an RS-232 interface on an FRX8000 is 64K if the port is directly connected to the user device via the 5-foot Cabletron RS-232 cable.
  • Page 156 , since DCE generates clock. If the port is DTE, specify Chapter 21) will be generated if the link goes up or = TPAD (Terminal) = HPAD (Host) , NRZI off), ; NRZI on). “NRZ” stands for FRX8000 3.0 User Guide, Rev 02...

  • Page 157: Configuring Subscriber Ids

    LPDA Support specifies the version (if any) of Link Problem Determination Aid that can be used by a host program (e.g., VTAM) or controller program (e.g., NCP) to test status and to control the line and remote interface. Configurable values are: Idle Fill Character specifies a character that will be inserted into the stream when the SNA link is idle.

  • Page 158: Subscriber Parameters

    1st,2nd,etc. Routing Path 1st,2nd,etc. Redirected Sub No. Subscriber Name identifies the subscriber to the console operator. The FRX8000 software does not use this information. Routing Algorithm allows creation of a “hunt group” of ports, for the purpose of routing per a pre-selected algorithm: = Round Robin –...
  • Page 159 Redirect on Busy redirects calls according to the Redirection Addresses if the primary subscriber device is busy. Redirect on Out of Order redirects calls according to the Redirection Addresses if the primary subscriber device is out of order. Bandw. Alloc. Group is a method of prioritizing outgoing traffic over trunks.

  • Page 160: Configuring Sdlc Pus

    FRX8000 HPAD and TPAD PUs N7000 HPAD PUs N7000 TPAD PUs HPAD PU configuration in both FRX8000 and N7000 defines the TPADs that will communicate with each HPAD. TPAD PU configuration defines the remote devices that will connect to each TPAD.

  • Page 161: N7000 Sna Hpad-Pu Record

    Configuring SNA S NA HPAD -PU Main ten ance * Node I D * LP ID * HPAD Port * PU _NO A Remote Sub scriber I D 2000020000 B SDLC Station Ad dres s C Autocall D Autocall Timer (s ec) E Maximum Retry Au tocall S elect: Figure 11-5 N7000 SNA HPAD-PU Record...

  • Page 162: Frx8000 Sdlc-Pu Record

    H, I configured as a TPAD. Items will be displayed only if “When Changes Take Effect at the from Main Menu [A],[D],[F],[C],[C] Autocall Port” on page 11-5. FRX8000 3.0 User Guide, Rev 02...

  • Page 163: Sna Pu Parameters

    SNA PU Parameters Table 11-3 lists all parameters for all HPAD/TPAD types, and explanations of some parameters follow the table. Note that some parameters may or may not be displayed, depending on the HPAD/TPAD types. Parameter PU Name Local Subscriber ID Remote Subscriber ID Maximum Bytes per Frame SDLC Station Address...
  • Page 164 ; otherwise, the PU will not re-activate properly after the session unless an on-line update ( the logical port record. in generating the Node field in an XID frame IDNUM ) is performed in [F7] FRX8000 3.0 User Guide, Rev 02...
  • Page 165 IDNUM is used in conjunction with IDBLK in generating the Node field in an XID frame (format both IDBLK and IDNUM, the Node field of the XID will be provided by the attached SDLC device. (The node will send an XID command to the remote node to indicate that the SDLC device should be polled for an XID.) Reply Timer - T1 is used to detect the failure to receive a required acknowledgment or response from...
  • Page 166 Recovery then B‘1’ .” Reply Timer - T1 to allow stations to reduce , and will be decremented by one each time a valid "Configuring Bandwidth Allocation Groups" on page 8-2. FRX8000 3.0 User Guide, Rev 02...

  • Page 167: Configuring Llc2

    A virtual LAN ID is normally assigned by a system administrator. The ID is used internally by the FRX8000 to identify a virtual bridge that connects the LLC2 function to LAN interfaces. If LLC2 will run in a node, this ID must be configured in the Node...

  • Page 168: Llc2 Host Configuration Screen

    Figure 11-9 LLC2 Host Configuration Screen Figure 11-8 for Type 1 Example 1 – Host Parameters from Main Menu [A],[E],[C],[A],[C] will be Access Types Allowed Example 2 – Host SVC Parameters [A],[E],[C],[A],[C] from Main Menu FRX8000 3.0 User Guide, Rev 02...

  • Page 169: Llc2 Host Parameters

    LLC2 Host Parameters Parameter Host MAC Address Session Type Reply Tim er - T1 Rcv Ack Timer - T2 Inactivity Timer - Ti LPDUs before Ack - N3 Outstanding LPDUs - Tw LPDUs if T1 Expir es - N2 Priority Bandwidth Alloc Group Routing Subscriber ID Source MAC Addr Mask...
  • Page 170 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 FRX8000, this address must be entered as a “bit-swapped” (or non-canonical) translation of the address that the node is expecting.
  • Page 171 The link station will reset A REJ (Reject) LPDU, provided a Command LPDU with P bit set to outstanding. A Response LPDU with the An Information or Supervisory LPDU with an N received and less than or equal to the line station’s V LPDU with If additional LPDUs are set from the remote link station after the local station has reset , the timer will be restarted if acknowledgments of or responses to those LPDUs are...
  • Page 172 IDs, all of which must begin with the Routing Subscriber ID. Source MAC Address Mask is used to identify the FRX8000 to inbound frames from a local LAN in an Originated LLC2 session. Source address masks and host MAC addresses are placed in a for- warding list that is checked by the software when a frame is received.

  • Page 173: Configuring Llc2 Interfaces

    SDLC device should be polled for an XID.) Configuring LLC2 Interfaces LLC2 Interfaces records define the types and locations of the interfaces that will carry LLC2 traffic to or from an FRX8000. To configure an interface, press [A], [E], [C], [B], [C]...

  • Page 174: Llc2 Frame Relay Interface Record

    LAN ID G–I. there are no items F–I from Main Menu [A],[E],[C],[B],[C] from Main Menu [A],[E],[C],[B],[C] is the default (source route bridge), item 802.5srb If item (transparent bridge), 802.3tb FRX8000 3.0 User Guide, Rev 02...

  • Page 175: Llc2 Interface Parameters

    LAN or a frame relay network. LAN Card identifies the LAN card in an FRX8000. When LAN cards are installed, the first one is card 0 and the second is card 1. LAN ID identifies the ring number used by a frame relay-compliant source-route bridge at the other end of this connection.
  • Page 176 Session Type Originated can use this interface. If interface. 11-28 Groups" on page 8-2. , means that LLC2 connections from the configured Host MAC Address , connections to the configured address can use this Terminated FRX8000 3.0 User Guide, Rev 02...

  • Page 177: Chapter 11 Configuring Bsc

    IBM’s DSP (Display System Protocol) allows connection between a host and a TPAD across the X.25 network. Required and Optional Configuration To run BSC Interactive in an FRX8000 Switch, the following files must be configured in the database: Network network.

  • Page 178: Configuration Example

    Node ID 2 LP ID 0 BSC Port 0 . Specify the Node ID 1 LP ID 0 BSC Port 1 Node ID 2 LP ID 0 BSC Port 0 . Specify the FRX8000 3.0 User Guide, Rev 02 , Con-...

  • Page 179: Configuring A Bsc Interactive Port Record

    Configuring a BSC Interactive Port Record To configure a record for a BSC Interactive port, press Selection Menu (or Node ID LP ID Port Any other requested information, noting the values in at a prompt to specify the default value.) Pressing When Changes Take Effect at the Port When you add a new Port record, it will be written to the database as soon as you enter...

  • Page 180: Bsc Interactive Port Parameters

    Valid Values Default Value (BSC Interactive) (not valid here) (see explanation) 3–85 0–9999 2000 1–99 25–4105 4105 2–10 1–10 100–1000 2–10 1–255 1–255 0–2 (CRC16) 0–2 (7 bit, Odd parity) (TPAD) (HPAD) 10–150 1–200 1–255 FRX8000 3.0 User Guide, Rev 02...
  • Page 181 = 1.984M = 2.048M The maximum for an RS-232 interface on an FRX8000 port is 64K if the port is directly connected to the user device via the 5-foot Cabletron RS- 232 cable. If modems or longer cabling are used, the recommended maximum speed is 19.2K.
  • Page 182 (accompanied by other condition checks). NAK Retry Count specifies the number of times the FRX8000 will send a frame when the receiving device is unable to acknowledge; that is, returns a NAK to the FRX8000.
  • Page 183 CUs will be polled between pollings of the CUs on the slow poll list. Error Retransmit Count specifies the number of times the FRX8000 will re-send a block of data after the receiving device has detected an error in that block. Configuring BSC...

  • Page 184: Configuring Subscriber Ids

    2 Redirection Add ress es Select: Figure 12-3 SVC Subscriber Record , then at the Subscriber Config- page 9-15). (The default is an asterisk, a [A],[F],[A],[C] from Main Menu are listed in Table 12-2. FRX8000 3.0 User Guide, Rev 02 Sub-...

  • Page 185: Subscriber Parameters

    1st/2nd/etc. Routing Path 1st/2nd/etc. Redirected Sub No. Subscriber Name identifies the subscriber to the console operator. The FRX8000 software does not use this information. Routing Algorithm allows creation of a “hunt group” of ports, for the purpose of routing per a pre-selected algorithm: = Round Robin –...

  • Page 186: Configuring Bsc Interactive Subscribers

    . This is an internal identifier that will link the subscriber 0–255 ) and a ) specified in the 1–100 Priority 0–9 Trunks" on page 4-8.) from the Main Menu). [A], [D], [G], [A], [C] Table 12-3. (Press FRX8000 3.0 User Guide, Rev 02 , then [Enter]...

  • Page 187: Bsc Interactive Subscribers Record

    When Changes Take Effect Changes to this file take effect when the associated port is updated by one of the methods described under BSC Interactive Subscriber Parameters Parameter Local Subscriber ID Remote Subscriber ID Autocall Autocall Timer Maximum Retr y Autocall Local Subscriber ID is an address for the local end of the BSC connection.

  • Page 188: Configuring Bsc Interactive Devices

    0–7 . This is an internal identifier that must match a Connection 0–255 (control unit) . (See Number 0–31 . (See Table 12-4.) 0–31 [A], [D], [G], [B], Table 12-4.) Table 12-5. (Press FRX8000 3.0 User Guide, Rev 02 [Enter]...

  • Page 189: Bsc Interactive Devices Record

    Ctrl Unit or Device No. Configuring BSC Table 12-4 Control and Device Unit Addressing EBCDIC ASCII (hex) (hex) BSC In teractive D evices Main ten ance Nod e ID LP I D BSC Port Con nection ID CU N umber Device Numb er A Single U ser Virtu al Cir.

  • Page 190: Bsc Interactive Device Parameter

    ) that each end of the connection is within a different Control Unit/ ) all characters transmitted, including control character sequences, to be Port” on page 12-3. Valid Values Default Value (terminal) (printer) (terminal) FRX8000 3.0 User Guide, Rev 02...

  • Page 191: Chapter 12 Configuring Async Pads

    The integral Async PAD function in the Netlink FRX8000 allow asynchronous devices to connect to a frame relay or X.25 network. Required and Optional Configuration To run a port as async in an FRX8000 Switch or N7400/7500, the following files must be configured in the database: Network new network.

  • Page 192: Configuring Async Pad Profiles

    Port record will be used. Two CCITT standard profiles, listed below, exist in the database when the FRX8000 software is shipped to the customer. If neither is suitable for your application, you can create a new one.

  • Page 193: Async Pad Profile Record

    Press Table 13-1.) When Changes Take Effect When you add a new profile record in database maintenance operations, the change will be written to the database as soon as you enter the final parameter value. When you change a parameter in an existing record, the change will be written to the database immediately.

  • Page 194: Async Pad Profile Parameters

    20 Echo Mask 21 Parity Treatment 22 Page Wait Usage is used as an identifier. It is not an X.3 parameter, and is not used by the FRX8000. 13-4 (where is a profile name) at the async terminal, the prof nnn [Enter]...
  • Page 195 1, PAD Recall Character allows the user's device to initiate an escape from data transfer state or connection in progress state in order to send PAD command signals. Values (can be added) are: = escape is not allowed. = escape will be initiated by 32–126 2, Echo provides for characters received from the user's device to be transmitted back to the...
  • Page 196 = PAD will send an indication of a Break message to the remote end and remain in data transfer mode. = PAD will escape from data transfer mode and enter command mode. = PAD will discard output. page A-4. FRX8000 3.0 User Guide, Rev 02...
  • Page 197 16, Character Delete is the ASCII value of the character that is used to delete characters. When this char- acter is received by the PAD, it will be stored in the editing buffer, and will cause the previously stored character to be deleted at packet forwarding or if a line display is performed.

  • Page 198: Configuring Pad Login Records

    After saving any changes as described, press ations Menu. Configuring PAD Login Records If an async PAD user will be required to log into an FRX8000 port, a login record must be configured. To add or change login ID parameters, press Network Selection Menu (or enter the Subscriber ID assigned to the async device.

  • Page 199: Async Pad Login Parameters Record

    When Changes Take Effect Changes to this file will take effect the next time the PAD user attempts to log in. Login Parameters Parameter Login Password Profile Name Login Password interacts with the Login Required parameter in the Port record. If login is required, the user must log into the PAD in order to make a call through it.

  • Page 200: Configuring A Pad Banner

    (of the LP containing the port): 0–7 , then from the Network = special use from the Ports Selection Menu (or . (Default is the “local” node.) 1–250 0–7 . (Default is Table 13-3. (Press FRX8000 3.0 User Guide, Rev 02 [A], [D], [Enter]...

  • Page 201: Async Pad Port Screen

    The parameters for all screens are all listed in When Changes Take Effect at the Port When you add a new Port record, it will be written to the database as soon as you enter the final parameter value. When you modify a parameter in an existing record, the change will be written to the database immediately.
  • Page 202 1–7 see note 16–256 0–15 digits none 0–255 valid subscriber ID none 0–10 0–255 0–12 characters none 0–28 hex characters none 0–5 0–60 0–300 RTS-CTS H/W Flow Control , whichever is smaller. FRX8000 3.0 User Guide, Rev 02 must be...
  • Page 203 13-10. = Auto-detect = Even FRX8000 8000 supports 8 data bits with no parity checking, or 7 data bits with even or odd parity checking. It also supports 7 data bits with auto- detect parity checking if X.3 Line Speed 21 is configured to check parity.
  • Page 204 ) cause the port to accept only those calls that substitute an (described on page 13-19) for the called address. (described on page 13-20) must also be configured. Autocall 21) will be generated if the link goes up or FRX8000 3.0 User Guide, Rev 02 [F7]...
  • Page 205 Called Address is the ID of the remote device, and is placed into the called address field of the Call Request. Retry Count is the number of times an autocall will be sent to the remote device. means indefinitely.) Retry Interval is the time between autocall attempts.
  • Page 206 , the modem signals will be dropped when the user is logged out. Disconnect Timer Disconnect is not , a physical disconnect is specified and the ), any data sent to [Ctrl] [P] are set to values other Disconnect Duration FRX8000 3.0 User Guide, Rev 02...

  • Page 207: Configuring Subscriber Ids

    Configuring Subscriber IDs This operation creates records for the called and calling addresses that will be used in X.25 call setup if async traffic will be transported over X.25 or (via an X.25 logical port) frame relay. To complete the connection, the software must recognize where the call is coming from (calling address) and where it is going (called address).

  • Page 208: Subscriber Parameters

    1st/2nd/etc. Routing Path 1st/2nd/etc. Redirected Sub No. Subscriber Name identifies the subscriber to the console operator. The FRX8000 software does not use this information. Routing Algorithm allows creation of a “hunt group” of ports, for the purpose of routing per a pre-selected algorithm: = Round Robin –...

  • Page 209: Configuring Abbreviated Addresses

    Bandw. Alloc. Group is a method of prioritizing outgoing traffic over trunks. Each IP and IPX network interface, SVC Subscriber, and PVC is assigned to a bandwidth allocation group defined by a Network Defaults file. (See 1st,2nd,etc. Routing Path assigns ports to the subscriber's routing paths group. 1st,2nd,etc.

  • Page 210: Configuring Pvcs

    Configuring PVCs An FRX8000 PVC is a “permanent” connection between two remote FRX8000 Switch subscriber ports. This allows communication between the attached devices as soon as they are powered up, without having to first make a call to establish a con- nection.

  • Page 211: Async Pvc Parameters

    An LCN assigned to a port in a PVC record must be lower than the lowest LCN specified for any SVC subscriber on the same port. Primary/Secondary Subscriber Name identifies the subscribers to the console operator. The FRX8000 software does not use this information. Configuring Async Pads at the Operations Menu (or “Creating/Deleting a PVC On...
  • Page 212 Main Menu). [B], [D] Table 13-5. to delete a connection. will be displayed. Create rejected, reason “n,” ) or remote ( ) end was bad. Either ) or remote ( where: Subscriber ID FRX8000 3.0 User Guide, Rev 02 ) end.

  • Page 213: Chapter 13 Configuring Ip

    Routing can be dynamic (RIP versions 1 and 2 are supported), and static routes can be configured. An FRX8000 can also be configured to act as a gateway, forwarding IP packets it receives. IP functionality also allows support of an SNMP agent. (SNMP is described in...

  • Page 214: Required And Optional Configuration

    Required and Optional Configuration To run IP in an FRX8000 Switch, you must configure the following files in the node's database: Network new network is set up. After that, no further changes are generally necessary. If IP will run on any FRX8000 nodes, an IP Network Address must be configured...

  • Page 215: Configuring Ip Network And Node Parameters

    Configuring IP Network and Node Parameters If any FRX8000 Switch nodes will run IP, a network address must be configured in the Network Defaults file. For each specific node that will run IP, additional param- eters must be configured in the Node file.

  • Page 216: Configuring Ip Interfaces

    Configuring IP Interfaces An IP interface allows the internet protocol to be executed over an FRX8000 Switch frame relay, X.25, LAN (Ethernet, 802.3, or 802.5), or network interface port. (N7000 nodes do not support routing via IP.) If this node will be running IP, press...

  • Page 217: Ip Interface Parameters

    IP Interface Parameters Parameter Maximum Transmission Unit Network Mask Routing Metric Count ICMP Redirects RIP Flash Updates RIP Full Updates Interface Type Source IP Address Destination IP Address Broadcast IP Address Source Subscriber Destination Subscriber SVC Retry Timer SVC Idle Timer Max VCs to Establish PVC Connection Source Card...
  • Page 218 = Ethernet = FRL (frame relay) = 802.3 = 802.5 (Token Ring) A network interface ties the local node to all other FRX8000 nodes in the network with IP interfaces. Table 14-1.) Table ). During routing, the interface with 14-1.)
  • Page 219 Source Card/Port/DLCI identifies the location of this end of the frame relay IP interface. Producing an IP Report An IP Report shows current configuration parameters for any or all FRX8000 IP Inter- faces. To produce a report: 1. Press 2. When prompted, enter a node ID, or press network.

  • Page 220: Configuring A Static Ip Route

    Configuring a Static IP Route Routing of IP traffic is handled dynamically by such protocols as RIP, as well as via static routes configured in the FRX8000. To configure a route, press the Connections and Routing Paths Selection Menu (or Menu).

  • Page 221: Ip Route Parameters

    IP Route Parameters Parameter Router Metric Count Route Type Route Destination Destination Mask Router is the IP address of a router that can reach the route destination. Metric Count is the number of “hops” (network gateways in the overall path over the internet) from the source to the destination.

  • Page 222: Configuring Ip-Over-X.25 Pvcs

    Figure 14-3 IP-over-X.25 PVC Record Example at the Operations Menu (or page 14-12.) again from the Connections and Routing Table 14-3. [A],[F],[C],[C] from Main Menu from the Main [B], [D] Table 14-3. (This is FRX8000 3.0 User Guide, Rev 02...

  • Page 223: Ip-Over-X.25 Pvc Parameters

    Pct of Bandw. - Grp “n” the Network Defaults file. Primary/Secondary Subscriber Name identifies the subscribers to the console operator. The FRX8000 software does not use this information. IP Interface ID is the IP interface at the primary end of the PVC.
  • Page 224 Main Menu). Table 14-3. to delete a connection. will be displayed. ) or remote ( ) end was bad. or the LP/port was not operational. ) or remote ( ,” where: Subscriber ID: FRX8000 3.0 User Guide, Rev 02 ) end.

  • Page 225: Chapter 14 Configuring Ipx

    FRX8000 Switch support of the Internetwork Packet Exchange (IPX) protocol allows an FRX8000 to connect to a Novell Netware network, and appear to the network as a LAN. Required and Optional Configuration To run IPX in an FRX8000 Switch, the following records must be configured in the...

  • Page 226: Configuring Ipx Network And Node Parameters

    Configuring IPX Network and Node Parameters If any FRX8000 Switches will run IPX, a network address must be configured in the Network Defaults file, to identify the FRX8000 part of the internetwork. For each spe- cific node that will run IPX, additional parameters must be configured in the Node file.

  • Page 227: Configuring Ipx Interfaces

    FRX8000 frame relay, X.25, Ethernet, 802.5 (Token Ring), or network interface port. (N7000 nodes do not support IPX routing.) The IPX function is used to connect an FRX8000 to a Novell NetWare network. If this node will be running IPX, press [B], [A], [C] from the Main Menu) to configure an interface.

  • Page 228: Ipx Lan Interface Parameters

    2–3 802.5: Ethernet: 48–4096 802.5: 0–255 1–65535 (seconds) 1–65535 (seconds) 0–65535 (seconds) 54–446 (bytes) (seconds) 0–65535 (55ms ticks) 0–255 0–1 1–fffffffe disables aging. Default Value 1 (Ethernet) 0–3 (TYPE_II) (LLC) 45–1518 1518 4096 00000001 FRX8000 3.0 User Guide, Rev 02...

  • Page 229: Ipx X.25 Interface Parameters

    Parameters Blocked Port Flag Interface Type Fr ame Type Maximum Transmission Unit Por t Diagnostics Enabled NetBIOS Enabled NetBIOS Hops RIP Enabled SAP Enabled Periodic RIP Enabled Periodic RIP Timer Periodic SAP Enabled Periodic SAP Timer RIP Age Timer RIP Maximum Size SAP Age Timer Transpor t Time Serialization Enabled...

  • Page 230: Ipx Frame Relay Interface Parameters

    Valid Values Default Value (Ethernet) 0–5 (TYPE_II) 31–4096 4096 0–255 1–65535 1–65535 0–65535 54–446 0–65535 0–255 1–fffffffe 00000001 0–fffffffffffe 000000000001 0–7 0–63 16–991 0–16 3 must be specified. only if is specified for all connec- FRX8000 3.0 User Guide, Rev 02...

  • Page 231: Ipx Network Interface Parameters

    = 802.5 (Token Ring) A network interface ties the local node (via any available trunk) to all other FRX8000 nodes in the network with IPX interfaces. A node should not have more than one network interface. matches Novell’s Ethernet_802.3 frame type.
  • Page 232 If the timer expires, the router will assume that the entry is no longer valid (due to hardware failure, power outage, etc.), and the entry will be deleted from the table. 15-8 Static routes (described on page 15-18) are never aged. FRX8000 3.0 User Guide, Rev 02...
  • Page 233 RIP Maximum Size is the maximum possible RIP packet size, including the IPX header (30 bytes) and the LAN MAC header (if transmitted on a LAN port). SAP Age Timer is used to delete route entries in the server information table (assuming SAP is enabled).
  • Page 234 IPXWAN Enabled determines whether Novell’s IPXWAN protocol will be used on the interface. IPXWAN specifies a method for IPX routers to communicate across WAN links. FRX8000 Switch implements IPXWAN running over RFC 1490-compliant frame relay and RFC1356-compliant X.25. PVC Connection identifies this interface as one end of a PVC.

  • 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 connection-less traffic. (Connection-less 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: Ipx Sap Filter Record

    001001000110000 from Main Menu [A],[A],[F],[C] from the Main Menu). [B], [B], [G] to select all nodes). [Enter] is assigned a Server Name Value . The binary “ANDing” is as Mask 5678 FRX8000 3.0 User Guide, Rev 02 , as Value...

  • Page 237: Ipx Rip Filter Parameters

    The mask will also be ANDed to its corresponding field in each IPX packet as deter- mined by IPX Filter Applications (described on pared to the AND result of the configured value and mask. If the two results match, the filter will be applied. This process allows a number of packet field values to match the AND result of the mask and value;...

  • Page 238: Ipx Sap Filter Parameters

    (4 bytes) ffffffff 0–ffffffffffff (6 bytes) ffffffffffff 0–ffffffffffff (6 bytes) ffffffffffff (2 bytes) 0–ffff ffff (2 bytes) 0–ffff ffff = job server 0005 = remote bridge server 0024 Server Name = RIP Process 0453 FRX8000 3.0 User Guide, Rev 02...

  • Page 239: Ipx Packet Filter Parameters

    Packet Filter Parameters Parameter Filter Name Packet Type Value Packet Type Mask Destination Network Value Destination Network Mask Destination Node Value Destination Node Mask Destination Socket Value Destination Socket Mask Source Network Value Source Network Mask Source Node Value Source Node Mask Source Socket Value Source Socket Mask Filter Name...

  • Page 240: Ipx Rip Router Filter Parameters

    (outbound). (The default is Default Value none 000000000000 00000000 from the Main Menu). [B], [B], [G] to select all nodes). [Enter] (Default is the local node.) 1–250. . (Default is 0–65535 = RIP Router. (The default is FRX8000 3.0 User Guide, Rev 02...

  • Page 241: Typical Ipx Filter Applications Record

    Up to 100 filters can be configured, displayed over 9 “pages” (screens). Parameter Permit Filter Application “n” Permit Determines whether the traffic defined by the denied passage across the interface. Filter Application “n” corresponds to the Configuring IPX IPX Filter A pplications Main ten ance * Node * Interface N umber * Filter C ategory...

  • Page 242: Configuring A Static Ipx Route

    Configuring a Static IPX Route Routing of IPX traffic is handled dynamically by such protocols as RIP and SAP, as well as via static routes configured in the FRX8000. To configure a static route, press then [E], from the Main Menu). When prompted, enter: Type Node: 1–250...

  • Page 243: Ipx Route Parameters

    IPX Route Parameters Parameter Node Number Route Number Network Address Hops Transpor t Time Router Interface Service Number Service Type Server Name Server Network Address Server Node Address Server Socket Number Intervening Networks Router Interface 1 The highest interface configured in the IPX Interface file. Node Number is the node associated with the router.
  • Page 244 IPX network number assigned to the interface used to send packets that are des- tined for this server. 15-20 = print queue = file server 0004 = print server = archive server 0009 = job server 0005 = remote bridge server 0024 FRX8000 3.0 User Guide, Rev 02...

  • Page 245: Chapter 15 Configuring Snmp

    MIB prefix codes and tree structures are described in the MIB reference guide, Cabletron part number 09-41-06-149. Required and Optional Configuration To support SNMP in an FRX8000 Switch, the following files must be configured in the database: Network new network is set up. After that, no further changes are generally necessary.

  • Page 246: Configuring Snmp Parameters

    Configuring SNMP Parameters To configure SNMP parameters for the FRX8000 node, press Node Selection Menu (or enter: Node number: 1–250 Parameter Type Any other requested information, as described in the following paragraphs. System Defaults System defaults are entries that will be included in IPL messages to the SNMP agent, and will be stored for access via the MIB.

  • Page 247: Snmp System Defaults Parameters

    System Location is generally the geographical address of the local node. System Contact identifies a person at the FRX8000 site who can be contacted if there are issues to discuss. Community Parameters “Communities” are groups of SNMP manager devices that have access to agents configured to recognize those communities.

  • Page 248: Snmp Community Table Menu

    A C ommunity Namename1 B A ccess1 Read_w rite S elect: Figure 16-2 SNMP Community Table Menu Table 16-2 Community Table Parameter Valid Values 0–24 characters = Read/write from Main Menu [A],[B],[B],[C] Default Value none FRX8000 3.0 User Guide, Rev 02...

  • Page 249: Snmp Trap Routing Menu

    Trap Parameters Trap routing allows the SNMP manager to specify one or more IP addresses (up to sixteen) to which the FRX8000’s alarms will be sent (as SNMP traps). was specified for (when prompted) an index number: Parameter Address Enabled...
  • Page 250 = High-Availability Node 16-6 after selecting Parameter Type Model High-Availability Node are supported for existing customers. is specified, traps of severity levels 1, 2, Chapter Configure SNMP Parameters are not standard platforms, but FRX8000 3.0 User Guide, Rev 02 , enter...

  • Page 251: Operation

    Section III Operation...

  • Page 253: Chapter 16 Introduction To System Operation

    F S tatis tics G R ep orts H Graphics-Level S tatus Disp lay R Exit to System Prompt Select: Figure 17-1 FRX8000 Switch Main Menu Item will be displayed only on a local VGA monitor. Item is documented in Section II.
  • Page 254 Boot Disk Local Operations – creates an installation disk set that is used to install the necessary software into an FRX8000 Switch, N7400, or N7500. Chapter Boot Disk Download Operations N74/7500 with some or all configuration and operating software.
  • Page 255 – sends one or more files to a remote INM/NMP. – allows the operator at an INM or NMP to take control of any other FRX8000 Switch on the same network. – sends changes in the Network Defaults file to all INMs/NMPs in the network.
  • Page 256 – displays the supported statistics, – allows collecting values for a – displays, prints, or saves cumulative – allows temporarily changing – overwrites any on-line changes that – Contents of PROTOCOL.INI, – Contents of BOOTBAK.TXT, which FRX8000 3.0 User Guide, Rev 02...

  • Page 257: Chapter 17 On-Line Operations

    R Return to Previous Men u Select: Figure 18-1 On-Line Port Operations Menu from the On-Line Port Operations Menu. When prompted, enter the Items are not supported in the current FRX8000 release. D–I Chapter 18 On-line Operations [B],[A] from Main Menu...

  • Page 258: V.25Bis Modem Operations

    C all in Progress 1122000 Select Port: Figure 18-2 V.25bis Dial Port Status Screen [F2] on status displays, and Link_Disabled on status displays, and Link_Disabled [B],[A],[K] from Main Menu will display [F2] will display page 1.) FRX8000 3.0 User Guide, Rev 02...

  • Page 259: Modem Operations Screen

    Pressing (if there is one). Pressing the first port in the list. Disconnect Calls To abort all calls on this port, press Modem Interactive Mode To send data to the modem, press prompted to disconnect the call. Do this in “Disconnect Calls.”) You will be prompted for a command.

  • Page 260: Displaying Installed Line Interface Cards

    To display the type(s) of Line Interface Cards(s) installed on an RLP, press On-Line Port Operations Menu (or enter a node and LP number. Restarting a Remote Node (Re-IPL) With this operation, you can re-IPL (restart) any FRX8000 or N74/7500 node in the network. Press prompted, enter: Your low-level operations password (described in The ID of the node to undergo re-IPL.
  • Page 261 . If creating a Node Update Disk or Boot Disk, go to step 9. If creating [Enter] Node Update Disk into an FRX8000 – insert the disk into the node and switch it on, or press [Ctrl] [Alt] [Del] files will be copied to the node’s disk.

  • Page 262: Boot Disk Download Operations

    NMP in one of the following ways: Configuration Update etc.) relative to a remote FRX8000, or LP and Port records for LPs 0–3 to a remote N74/7500. (An N74/7500 DPPM node gets these records from its local disk, so those local records must be kept current.) All Software Update network.
  • Page 263 To perform an section below. Remote FRX8000/N7400 DPPM Updating an FRX8000 Enterprise Switch or N7400 DPPM involves performing the Software Update 1. After selecting [Enter] File names will be displayed as the files are downloaded. When the operation is finished, 2.
  • Page 264 , and repeat steps [Enter] to destination file name to return to the [Enter] . (Ignore the warnings that say: , type y [Enter] is “zero.”) , type y [Enter] , press any key. FRX8000 3.0 User Guide, Rev 02 rc.once...
  • Page 265 Remote N7500 DPPM Updating an N7500 DPPM node involves performing an downloading three single files, and performing a remote IPL of the node. If the node has an attached monitor, a local re-IPL must also be performed at the node at some convenient time, to enable access to the performance display.
  • Page 266 Boot Disk [Enter] to perform [R], [R], [F] Transfer File NMP/pia.o [Enter] pia.o [Enter] , then , and repeat steps [Enter] to return to the Network Oper- [Enter] . (Ignore the warnings that say: FRX8000 3.0 User Guide, Rev 02...
  • Page 267 10. When asked: 11. At the 12. When asked: 13. When prompted: 14. At the 15. When prompted to type [Ctrl] [D] 16. At the login prompt, enter your login name and, if requested, login password. 17. At the 18. At the node, if the screen is blank or is displaying: If the 19.
  • Page 268 UNIX prompt, type [NETLINK] gcon [Enter] , downloading three n [Enter] , downloading three All Software Update y [Enter] , do the following at the gcon FRX8000 3.0 User Guide, Rev 02...

  • Page 269: Call Accounting File Operations

    ( is two lowercase Ls.) If a file named ACCNT is present, call The FRX8000 software can be modified to enable automatic rollover of the call accounting file; however, this should be done only by a qualified system manager or administrator. Instructions can be found on page F-6.
  • Page 270 Stop NMP processes to Call Accounting y [Enter] prompt. from Main Menu) to send [B], [G] free % used 62016 75-80 at the Main Menu to exit caf [Enter] to cancel the operation, or [Del] FRX8000 3.0 User Guide, Rev 02...

  • Page 271: Call Accounting File Display

    You can also display all records in the file from the beginning of the file to the present. To display raw (unformatted) data, type: display will be a string of data, similar to this: Figure 18-4 unformatted display. To return to the INM menu level, type (if at an Auxiliary Console).

  • Page 272: Call Accounting File Structure

    Remote to Remote to Remote Local Local Local P means PV C was removed. from the Main Menu). When [B], [B], [E] FRX8000 3.0 User Guide, Rev 02 To P ath A or B below Call Reverse S etup Charge Priority...
  • Page 273 FRX8000 software was installed by Cabletron), press from the Main Menu).When prompted, enter: [B], [B], [F]...

  • Page 274: Converting N7000 5.0 Database Records

    Converting N7000 5.0 Database Records Certain database files (described later) contain parameters that differ between records for an FRX8000 node and a Nucleus 7000 (Release 5.0) node. Updating an N7000 to be an FRX8000 requires a database conversion operation to change the incompatible parameters.

  • Page 275: Database Concurrency Operations

    Logical PDN Port * New parameters will be set at their default values. 4. After the conversion, perform a Main Menu) to each affected node, then re-IPL the node ( Main Menu). Database Concurrency Operations "Partitioned can come to exist in a network. Depending on the changes made while the network was partitioned, databases in all ICPs, INMs, and NMPs may not automatically syn- chronize when the network is reconnected.
  • Page 276 Database Concurrency Operations Menu, or three [F3] at the Database Concurrency Operations Menu. Type y [Enter] [F3] once to return to the Database Concurrency Operations Menu, or three “ ” Node Start FRX8000 3.0 User Guide, Rev 02...

  • Page 277: File Transfer

    File Transfer This operation lets you transfer a file between any two ICPs/INMsNMPs. The transfer does not have to be initiated from either of the two devices involved. Press enter: Source node ID. (Pressing Source file name, including any necessary path names. Destination node ID.

  • Page 278: Remote Control

    INM/NMP video screen will display the Main Menu of the controlled node. If you take remote control of an FRX8000 INM or NMP node, only the node software will be under remote control. NMP management functions will still be under the control of the remote operator.

  • Page 279: Message Services

    On-line Operations [N] [Enter] FRX8000 – NETLINK Other device – Login password configured at the remote device displayed at the upper right. If the controlled node is a non-FRX8000 will be the Remote Control ID will be , where 999999xxx7 “...

  • Page 280: Answering A Call

    . When the subscriber/INM/NMP ends the call, an end [F3] once to return to the Message Services Menu, or twice to return to [Enter] , or twice to return to the at the Message Services FRX8000 3.0 User Guide, Rev 02...

  • Page 281: Chapter 18 Status Displays

    The FRX8000 software provides real-time status information on nodes, RLPs, frames, and ports, as well as the IPX RIP and SAP tables. Displays and some operations can be accessed from both the menu level and graphics level. Menu-Level Status Displays...

  • Page 282: Port Status Display

    (SVCs and PVCs) currently in use in this node, divided by two. is the date/time the FRX8000 software was last started. lists the possible operational states that each port can be in. See “...

  • Page 283: Trunk Status Display

    Information in this Display are the RLP and port numbers is the port type: Type is packets per second passing through the port. is the number of virtual connections currently in use. Conn# State Linkup Restarting Operational Disabled Disconnect Configured Failed Hardware Fault Trunks...

  • Page 284: Virtual Connections Display On Frame Relay Port

    19-4 (intentionally) (if link is still in process of being established) to return to the Status Displays Menu. [F3] FRX8000 Con nection Status D is play Men u (Page 1) Node: 10 LP: 0 From: Seq DLC I State Trans...

  • Page 285: Virtual Connections Display, Non-Frame Relay Port

    Resetting Port_down Connected Not_conect Undefined is the number of transmitted frames. Trans is the number of received frames. Recd is the number of discarded frames. Disc is the node number is the LP number, except for a file transfer connection, in which case this number is always is the port number ( Figure 19-5 Virtual Connections Display, Non-Frame Relay Port...
  • Page 286 Enables/disables display of all/no packets. Exits Line Monitor mode. , in which case the port number is from the Main Menu) and, when [C], [D] LCN: All for Node: 10 LP: 2 Port: 2 “data (shown above). FRX8000 3.0 User Guide, Rev 02...

  • Page 287: Line Monitor Display, X.25 Example

    Figure 19-6 shows an example of a display of RR and Data packets on an X.25 line, and Figure 19-7 shows routing updates on a trunk. Information in this Display On each line (see CCITT Recommendation X.25) in the above display: The left most field shows the time, to hundredths of a second.

  • Page 288: Line Monitor Display, Trunk Example

    Routing Update packet contains serial number information to stop the display from scrolling (assuming it is . (Stopping the scrolling first is not always necessary, but allows [F3] [F3] from Main Menu [C],[D] is pressed, especially from an ASCII FRX8000 3.0 User Guide, Rev 02...

  • Page 289: Displaying Ipx Rip And Sap Tables

    Status Displays –is the IPX address of the network containing the FRX8000 node that –is the address of the router that will forward a packet when this – is the number of routers in a packet's path to the destination network.

  • Page 290: Graphics-Level Status Displays

    Waiting node/NMP, but has not yet been accepted. F4 Operation s Events:24 Call Waiting from Main Menu ” on page 19-13.) If [F2] – Events Table 19-1, to show whether they are FRX8000 3.0 User Guide, Rev 02 Call...

  • Page 291: Color Codes For Subnet Display/Event Log

    Black White Green Yellow Magenta Cursor Movement Components are placed into and selected within the network representation by moving the cursor to the desired locations. Cursor movement is controlled as listed below. (If the numeric keypad at the right side of the keyboard is used, On network/subnet displays, right/down.

  • Page 292: Status Display Icons

    FRX 8000 or N7500 ICP/INM N7500 with N7400 with attached NMP attached NMP N7500 DPPM Subnetwork Events , discussed on . Selecting Cancel exits the current menu will do the same thing. [Esc] FRX8000 3.0 User Guide, Rev 02 , or [Enter]...

  • Page 293: Event Log Display

    Interfaces Logical Ports PDN Trunks Cancel [F2] – Events Selecting this item prompts you for a subnetwork or node ID (the default is the local node), then displays a list of events for that subnetwork/node, as shown in Figure 19-10. Entering When you list a node’s events, you are acknowledging any events on that node, and Events: Status Displays...
  • Page 294 (subnet, node; default for subnet) updates the network defaults. (See Chapter 4.) is not supported in the current FRX8000 release. (all; default for port) leaves this pull-down menu and returns you to the choices at the top of the screen.

  • Page 295: Node Status Display

    Displaying Node Status At the network/subnetwork display, position the cursor on a node, press select Zoom In Each LP number, LAN card number, and port description will be color coded as described in Table 19-2. Table 19-2 Color Codes for LP/LAN Card/Port Status Display LP/LAN Status Black Yellow...

  • Page 296: Trunk/X.25 Port Status Display

    (the default) displays all port [F5] Next F5 Next Events: 24 Port 3 Lin k U p X.25 Su bscrib er 9600 bp s 1000 2000 4096 V.35 7480 6600 5860 6680 FRX8000 3.0 User Guide, Rev 02 , which...

  • Page 297: Chapter 19 Statistics Displays

    The FRX8000 software provides real-time statistical information on nodes, RLPs, frames, and ports, as well as IP and IPX interfaces. The network automatically rechecks and updates all statistics data every five seconds. Some displays can be accessed from both the menu level and graphics level.

  • Page 298: Node Statistics Display

    Node Statistics Node statistics differ for FRX8000 and N74/7500 nodes. The following screen shows an FRX8000. FRX8000 Packets per Second Total Connections Idle Time Boot Time Outstanding Memory Requests Memory in Use Connection Limit 20-2 N ode Statistics R ep ort...
  • Page 299 N74/7500 Packets per Second Bytes per Second Congested Calls per Second (*100) Call Requests Rcv’d per Second (*100) Conn’s Allocated per Second (*100) Connections Deleted per Second (*100) % of Queue Elements in Use % of PPM Application Run Time Connection Resources in Use % Common Memory...

  • Page 300: Lp Statistics Display

    Retransmission Period DA TE TIME 1/21/1998 09:45:19 1/21/1998 09:45:19 1/21/1998 09:45:19 1/21/1998 09:45:19 1/21/1998 09:45:19 1/21/1998 09:45:19 [F],[B] from Main Menu (maximum) values to the CURR timer ) in the Port record. FRX8000 3.0 User Guide, Rev 02 (current)

  • Page 301: Port Statistics Display

    Port Statistics Information in this Display Received frames per sec (*10) Transmitted frames per sec (*10) Retran frames per sec (*10) FCS errors/sec (*10) Logical rejects/sec (*10) Transmit error ratio Receive error ratio Statistics Displays Port Statistics R ep ort Nod e: 10 LP: 0 Port: 1...

  • Page 302: Frame-Level Statistics Display

    (reject) (supervisory command or response) (receive ready) (supervisory command or response) (receive not ready) (supervisory command or response) (information) (information transfer, command) 0 D ays 1 Hrs 4 Mins [F],[B] from Main Menu Start Time FRX8000 3.0 User Guide, Rev 02...
  • Page 303 Frame Relay DE/sec (*10) FECN/sec (*10) BECN/sec (*10) LMI/sec (*10) ANXD/sec (*10) Frames/sec (*10) DiscF/sec (*10) Configuring Statistics Thresholds For each node (N74/7500 only), RLP, and port statistic, you can specify a threshold that, when crossed (in either direction), causes an alarm to be generated. Thresholds are configured in the database, and can also be changed temporarily on line.

  • Page 304: Port Statistics Configuration Menu

    (described on page 20-26). from Main Menu [F],[A],[C] [F],[G] after completing the changes, to [F1] to cancel. at the Statistics for Port. (Default is from the Main Menu), then enter the desired Graphics-level Sta- FRX8000 3.0 User Guide, Rev 02...

  • Page 305: Cumulative Statistics Menu

    Cumulative Statistics The LP software collects seconds. Cumulative Statistics operations accumulate these values at selected intervals and write the totals to a file at an ICP, INM, or NMP. You can produce a report listing those totals at each interval within a selected period. To create or modify a Cumulative Statistics record (you must have master status), press LP, and port numbers.

  • Page 306: Cumulative Statistics Parameters

    , which specifies the time of the latest report to the ICP/ Valid Values Default Value local node 1–250 1–1440 (off) (on) or 1 Size” on page F-3. at the Cumulative Sta- to write to a file. = Day ( 01–12) 01–31 00–59 FRX8000 3.0 User Guide, Rev 02...

  • Page 307: Cumulative Statistics Report

    The report contains a set of values for each time the statistics were sent to the current CSTAT.DAT file in the ICP/INM/NMP within the time frame you specified. The report starts with the latest set of values. On a display, as shown in Figure 20-7, pressing Statistics Displays displays the next older set of values.

  • Page 308: Ip Statistics Displays

    Statistics C URR C UMULATI VE 1000000000 1000000000 1000000000 1000000000 1000000000 1000000000 1000000000 1000000000 1000000000 1000000000 [F],[C],[A] from Main Menu FRX8000 3.0 User Guide, Rev 02...

  • Page 309: Icmp Statistics

    Unkwn Protocol Pkt Too Small Pkts Delivered Bad Hdr Length Local Pkts Sent Bad Pkt Length Pkts Dropped Pkt Fragments Total Reasmbled Frag Time Out Pkts Fragmented Frag Dropped Frag Created Pkts Forwarded Can't Frag ICMP Statistics ICMP statistics track traffic of Internet Control Message Protocol messages through the node.

  • Page 310: Icmp Statistics Display

    (due to the “don't frag” flag being set). The CU MU LATIV E 1000000000 1000000000 1000000000 1000000000 1000000000 1000000000 1000000000 1000000000 1000000000 1000000000 1000000000 1000000000 1000000000 1000000000 1000000000 1000000000 1000000000 from Main Menu [F],[C],[B] FRX8000 3.0 User Guide, Rev 02...
  • Page 311 Out/In Pkt Lost Out/In Redirect Out Echo In Echo Out/In Time Exceed Out/In Bad IP Hdr Out Time Req In Time Req Out Time Rsp In Time Rsp Out Info Req In Info Req Out Info Rsp In Info Rsp Out Mask Req Statistics Displays message text says...

  • Page 312: Ip Interface Statistics Display

    Statistics at the upper left IP/LAN IP/WAN MTU: 4096 CUR R CUMULA TIVE 269420 8161 139822450 from Main Menu [F],[C],[C] FRX8000 3.0 User Guide, Rev 02...

  • Page 313: Ipx Statistics Displays

    Errors In Errors Out Q Dropped In Unknwn Protocol Collisions IPX Statistics Displays IPX statistics track IPX traffic through a node. Press when prompted, enter: Node Interface Number Report Interval There are three screens of IPX statistics. Pressing there is one), and pressing statistics are listed below.
  • Page 314 NetBIOS packets that were discarded because the hop count exceeded the number of the IPX Interface record for the local FRX8000 interface. is the number of RIP entries received with no network address. The network address configured for the interface will be used.
  • Page 315 SAP messages broadcast from this node advertising the available servers (from the server table in the FRX8000). is the number of SAP messages broadcast from this node to inform the network of changes to the server table.
  • Page 316 Echo Requests received on the interface. is the number of Novell error packets received on the interface. is the number of packets discarded because the interface was down. FRX8000 3.0 User Guide, Rev 02...
  • Page 317 0453 = Diagnostics Process 0456 through are not monitored by the FRX8000/, but R_Decomp Errors are included in the statistics list because it is part of the IPX MIB. The statistics in the list between the above two are: Bad Checksum Rcv...

  • Page 318: Lan Card Statistics Displays

    (more than one category can be specified): Directed and Multicast or Group and Functional Broadcast Promiscuous (any packet on the LAN) (any source routing packet on the LAN) Any Source Packet at the Statistics (Figure 20-12) or Token FRX8000 3.0 User Guide, Rev 02...

  • Page 319: Ethernet Card Statistics Display

    Statistics Displays LAN Card Statistics D is play Nod e: 10 Card Numb er: 0 Typ e: Eth ernet Report I nterval (sec): 5 Cu rrent Time: 1/05/98 10:32:45 Hard ware Status : Fu lly Op erational MAC Status : Bound , Op en Pack et Filters: D irected/Multicast or Grou p/Fu nction al, Broadcast STA TISTI C C URR...
  • Page 320 DMA (direct memory access) under run errors. FRX8000 3.0 User Guide, Rev 02...
  • Page 321 Token Ring-Specific Statistics FCS Violations Copy Errors Trans Absences Frequency Errors Frm with Aborts Act Mon Regen No Return Frms Underruns No Buff Avail A/C Errors Statistics Displays is the number of frames received that have failed the Frame Check Sequence (FCS) cyclic redundancy check (CRC). is the number of frames received with duplicate addresses.

  • Page 322: Graphics-Level Statistics Displays

    LP and node levels, the [F4] page 19-10). F5 Next Events: 24 Port 3 Lin k U p X.25 Su bscrib er 9600 bp s 1000 2000 4096 V.35 7480 6600 5860 6680 FRX8000 3.0 User Guide, Rev 02...

  • Page 323: Chapter 20 Alarms

    Alarm messages are reported to the disk and printer, at the originating node and up to two other nodes (specified in the Node record as “Primary” and “Secondary”). Most alarm operations are accessible from the Alarms Menu ( Alarm Severity Levels There are four levels of severity: Level 1 = Serious Fault.

  • Page 324: Alarms Report Parameters

    (see explanation) file start (see explanation) file end D, L, P, F (display) = day ( 01-12 01-31 00-59 to return to the [F3] Node ID: : prompt will reappear when the report FRX8000 3.0 User Guide, Rev 02 prompt.

  • Page 325: Alarms Report

    The format for all four options is the same. Table 21-1 shows a sample display. The content of the report is described under Although printed and displayed reports are structured differently, the information is the same. Displaying Alarms Alarms can be displayed in two operations. One is accessed in graphics mode, and is described under from the menu level, and is described here.
  • Page 326 Primary Node for each level is an ICP/INM/NMP to which all alarms of that Secondary Node An FRX8000 cannot send its alarms to an N7000 device, but an N74/ 7500 can send its alarms to an FRX8000 device. Primary Node...

  • Page 327: On-Line Alarm Routing Screen

    After making your changes, press change your mind before pressing prompt. The change(s) will remain in effect until the next IPL or until you make sub- sequent on-line changes to the same parameters. Press [F3] Loading Default Routing Values With this operation, you can restore the default alarm routing parameters defined in the Node record (see Chapter 5) without waiting to re-IPL a node.

  • Page 328: Alarm Messages

    ). Ignore 304–332 ), PVC status ( 57–60, 400–406 107, 108, 224, 225, 228, 229, 248, 249, 299, 300, 367, 388 181, 182, 197, if they appear with ), and 111, 118, 119, 215, 216 FRX8000 3.0 User Guide, Rev 02...

  • Page 329: Frx8000 Rlp

    “n”: 3 = N74/7500 T1/E1 LP = N74/7500 RLP = FRX8000 RLP The executable program for PPM type 1 (the only type currently used) has been loaded to memory during node IPL. The executable programs for the LPs and PPM have been sent to the packet processing system.
  • Page 330 The packet processing system has found an LP that has no record in the database. Create an LP record for this LP, then implement the change at the node by one of the methods described in under “When Changes Take Effect“on page 6-3. Cabletron Systems FRX8000 3.0 User Guide, Rev 02...
  • Page 331 Check the LP file for the correct LP ID and type: = N74/7500 AST card = N74/7500 T1/E1 LP = N74/7500 RLP = FRX8000 RLP A re-IPL message has been sent, by operator request, to node “n.” The Call Request processor cannot access one of the necessary database files.
  • Page 332 IPL. An automatic re-IPL will be initiated. If this message occurs again, contact Support. (See page 21-7.) Cabletron Systems Cabletron Systems Support. Cabletron Systems Technical FRX8000 3.0 User Guide, Rev 02...
  • Page 333 LP image file not loading Severity: Meaning: Action: Cumulative Statistics file rollover request sent to Node “n” Severity: Meaning: New Cumulative Statistics file has been created for Node “n” Severity: Meaning: Cannot Create Cumulative Statistics file for Node “n” Severity: Meaning: Action: Unknown message type “n”...
  • Page 334 An operator has stopped Cumulative Statistics gathering for the specified port. Cumulative Statistics gathering has begun for the specified port, either by operator request or node IPL. page 18-19), enable backouts FRX8000 3.0 User Guide, Rev 02...
  • Page 335 Reset Update requested for Node “n” while Cum. Stats. are inactive Severity: Meaning: LP “n” Port “n” disconnected successfully Severity: Meaning: LP “n” Port “n” disconnect failed Severity: Meaning: Action: LP “n” Port “n” already disconnected Severity: Meaning: Action: LP “n” Port “n” already connected Severity: Meaning: NMP disk space exhausted.
  • Page 336 When the NMP processes have stopped, type [NETLINK] . If you see the message again, call nmpini [Enter] Technical Support. (See page 21-7.) at the prompt. [NETLINK] Support. (See page 21-7.) Recovery” on page 18-20.) stop [Enter] Cabletron Systems FRX8000 3.0 User Guide, Rev 02...
  • Page 337 Group “n” Subscriber “n” not in Subscriber file Severity: Meaning: Action: EVENTL can't open the alarm log file Severity: Meaning: Action: LOGTSK database recovery required for Node “n” Severity: Meaning: Action: On-line parameter change initiated for Node “n” LP “n” Port “n” Severity: Meaning: Database change “n”...
  • Page 338 Check the Node file. Self-explanatory. Self-explanatory. Self-explanatory. Self-explanatory. The file transfer was not successful. Either one of the nodes could not be reached, there was a timeout, or a disk error occurred. Retry the transfer. Self-explanatory. FRX8000 3.0 User Guide, Rev 02...
  • Page 339 Port stat. parameter update initiated–Node “n” LP “n” Port “n” type “n” Severity: Meaning: 101. No ports defined in database for Node “n” LP “n.” Parameters not sent Severity: Meaning: Action: 107. Node “n” is reachable Severity: Meaning: 108. Node “n” is not reachable Severity: Meaning: Action:...
  • Page 340 Subscriber record. If these are all right, check the hardware configuration. in the node's “x”–“y” ) or remote ( ) end was bad. or the specified ) or remote ( ) end with the FRX8000 3.0 User Guide, Rev 02...
  • Page 341 118. PVC removed–Node “n” Line “n” LCN “n” to Node “n” Line “n” LCN “n” Severity: Meaning: 119. PVC remove failure-Node “n” Line “n” LCN “n” to Node “n” Line “n” LCN “n” - Reason “n” Severity: Meaning: Action: 120. Illegal Subscriber configured for Node “n”...
  • Page 342 The Integrated Call Processing (ICP) function at the specified node is inaccessible. None. An internal error has occurred in the graphics-mode software. Contact Cabletron Systems Technical Self-explanatory. Cabletron Support. (See page 21-7.) FRX8000 3.0 User Guide, Rev 02...
  • Page 343 Action: 138. Node “n” terminated due to SW protection violation with node “n” Severity: Meaning: Action: 139. LP “n” Port “n” received invalid configuration for big packet Severity: Meaning: Action: 146. LP “n” Port “n” – Transmitter stuck Severity: Meaning: Action: 147.
  • Page 344 – QLLC received a message from the SDLC with a facility of aa13 UA Signal form Link to QLLC (LPQUA) with a VC ID greater than or equal to to the maximum number of allowed remote controllers. FRX8000 3.0 User Guide, Rev 02...
  • Page 345 Alarms – the count of Remote SAPs has exceeded the maximum VCs b001 allowed. (Generated during processing of the IPL parameter packet (spcfg_iplparm().) – the PAD type is unknown. (Generated during processing of b002 spcfg_iplparm(). – the IPL state (iplstate) is not set. (Generated during pro- b003 cessing of the EX–IPL parameter packet (spcfg_exiplparm().) –...
  • Page 346 (pl_lldata()), the facility was LPCA and the VC ID was invalid. – during the link layer–to–PL message Main routine b713 (pl_lldata()), the facility was LPSVCD (Terminate QLLC) and the VC ID was invalid. FRX8000 3.0 User Guide, Rev 02...
  • Page 347 Alarms – during the link layer–to–PL message Main routine b714 (pl_lldata()), the facility was LPRSDM (Reset Slowdown Mode). – during the link layer–to–PL message Main routine b715 (pl_lldata()), the facility was LPSSDM (Set Slowdown Mode) and the VC ID was invalid. –...
  • Page 348 Check the Port record, and change the configuration if necessary. There was a checksum error at the packet level while running the load generator. There is a serious problem in the operating system. Cabletron Systems FRX8000 3.0 User Guide, Rev 02...
  • Page 349 Action: 171. ** SHELL Error Function “n” Error “n” from “n:n” Severity: Meaning: Action: 172. Node “n” LP “n” Port “n” logical trunk “n” established to Node “n” Severity: Meaning: 173. Node “n” LP “n” Port “n” logical trunk “n” down – cause “n” Severity: Meaning: Action:...
  • Page 350 The download indicated in message 183 has been completed. The download indicated in message 183 failed. The Call Accounting file is taking up a lot of disk space, which may run out if something is not done. FRX8000 3.0 User Guide, Rev 02...
  • Page 351 187. Enable autocall on Node “n” LP “n” Port “n” SNA PAD initiated. Severity: Meaning: 188. Upgrade in Progress is set but node “n” is an FRX8000. Severity: Meaning: Action: 189. LP “n” Port “n” Duplicate Terminal “n” from (Subscriber ID)
  • Page 352 Try the download again. If it still does not work, contact Systems Technical Support. (See page 21-7.) Self-explanatory. Try the download again. If it still does not work, contact Systems Technical Support. (See page 21-7.) Self-explanatory. Cabletron Cabletron FRX8000 3.0 User Guide, Rev 02...
  • Page 353 Meaning: 208. Cannot access /u/netlink/acnt on node “n” Severity: Meaning: Action: 209. Backup call accounting file deleted on node “n” Severity: Meaning: 210. Checksum error in load generation message to this node Severity: Meaning: 215. PVC connected from LP “n” Port “n” LCN “n” to Node “n” LP “n” Port “n” LCN “n” Severity: Meaning: 216.
  • Page 354 X.25 codes. (See Appendix The PIA link between the 7400/7500 and its attached NMP is up. The PIA link between the 7400/7500 and its attached NMP is down. Check the hardware. FRX8000 3.0 User Guide, Rev 02...
  • Page 355 230. V25bis, Node “n” LP “n” Port “n” Modem Failed - Cause “n” Severity: Meaning: Cause Action: 231. V25bis, Node “n” LP “n” Port “n” Out of Order (CFI DT) Severity: Meaning: Action: 232. V25bis, Node “n” LP “n” Port “n” ATL “n” Dial Out Failed Severity: Meaning: Action:...
  • Page 356 Database Recovery has been initiated, and how many files it expects to copy. This node is requesting that the file be replaced as part of Recovery. Database Recovery. The node's Database FRX8000 3.0 User Guide, Rev 02...
  • Page 357 257. Database recovery error replacing (filename) Severity: Meaning: Action: 258. Database recovery complete Severity: Meaning: 259. Database recovery complete but failed to replace all required files Severity: Meaning: Action: 264. Master status cleared by Node “n” Severity: Meaning: 265. Request to clear master status sent to Node “n” Severity: Meaning: 266.
  • Page 358 “n” be closed and a new one created. Self-explanatory. Self-explanatory. Contact Cabletron Systems Technical Self-explanatory—the disk is probably full. Contact Cabletron Systems Technical (as specified in its Node (as specified in its Node Support. (See page 21-7.) Support. (See page 21-7.) FRX8000 3.0 User Guide, Rev 02...
  • Page 359 291. Node “n”, Type “n”, LP “n” in database but does not exist Severity: Meaning: Action: 292. Node “n” LP “n” exists but not loaded due to mismatch with database Severity: Meaning: Action: 293. Node “n”, LP “n” exists but is not in database Severity: Meaning: Action:...
  • Page 360 The statistic has crossed the threshold. The statistic has crossed the threshold. The statistic has crossed the threshold. The statistic has crossed the threshold. The statistic has crossed the threshold. The statistic has crossed the threshold. FRX8000 3.0 User Guide, Rev 02...
  • Page 361 317. LP “n” Port “n” Threshold violation Port Receive Error Ratio Threshold “n”, Current value “n” Severity: Meaning: 318. LP “n” Port “n” Threshold violation Port Percent Xmit Port Utilization Threshold “n”, Current value “n” Severity: Meaning: 319. LP “n” Port “n” Threshold violation Port Percent Rcv Port Utilization Threshold “n”, Current value “n”...
  • Page 362 The statistic has crossed the threshold. The statistic has crossed the threshold. The statistic has crossed the threshold. The statistic has crossed the threshold. The statistic has crossed the threshold. Self-explanatory. Contact your T1 carrier Self-explanatory. FRX8000 3.0 User Guide, Rev 02...
  • Page 363 336. LP “n” T1 Frame Synchronization Lost – Red Event ON Severity: Meaning: Action: 337. LP “n” T1 Frame Synchronization Regained – Red Event OFF Severity: Meaning: 338. LP “n” T1 Remote Frame Synchronization Lost – Yellow Event ON Severity: Meaning: Action: 339.
  • Page 364 Router statistic parameter update initiated for Node “n” Type “n” Severity: Meaning: 21-42 Self-explanatory. Self-explanatory. Contact your T1 carrier Self-explanatory. Self-explanatory. Contact your T1 carrier Self-explanatory. Self-explanatory. Contact your T1 carrier Self-explanatory. Self-explanatory. Contact your T1 carrier Self-explanatory. Self-explanatory. FRX8000 3.0 User Guide, Rev 02...
  • Page 365 354. Node “n” Threshold violation IPX Xmit Packets/Sec Threshold “n”, Current value “n” Severity: Meaning: 355. Node “n” Threshold violation IPX Rec Packets/Sec Threshold “n”, Current value “n” Severity: Meaning: 356. Node “n” Threshold violation No Router Buffers Threshold “n”, Current value “n”...
  • Page 366 Check the configuration records for the node, LP, and port, and create records where necessary The specified DLCI has not been configured on the port. Configure the DLCI in the port record The header contained an invalid DLCI. FRX8000 3.0 User Guide, Rev 02...
  • Page 367 Action: 372. Node “n” LP “n” Port “n” DLCI “n” PVC does not exist Severity: Meaning: Action: 373. FR LP “n” Port “n” DLCI “n” frame discarded–congestion Severity: Meaning: Action: 374. Node “n” LP “n” Port “n” DLCI “n” frame relay logical trunk configured on a DCE port Severity: Meaning:...
  • Page 368 A physical connection has been established between the specified port and a neighboring node. After an initialization period, used to collect routing information, the trunk will be used to route traffic. Initialize File Maintenance Initialize File FRX8000 3.0 User Guide, Rev 02...
  • Page 369 388. LP “n” Port “n” Trunk down – cause “n” Severity: Meaning: Action: 390. LP “n” LIC “n” loaded with type “n,” mismatch with database Severity: Meaning: Action: 391. Node “n” – Node type mismatch with LP “n,” IPL terminated Severity: Meaning: Action:...
  • Page 370 Self-explanatory. The reason is probably an invalid PVC type or port. Review and change the configuration. Self-explanatory. Each FRX8000 node can connect, via trunks, to up to 64 “neighbor” nodes. (A neighbor is the closest node in a path from the “home” node.) Remove the necessary number of trunks from the node.
  • Page 371 Meaning: Action: 402. Link Disconnected Severity: Meaning: Action: 403. Link Up Severity: Meaning: Action: 404. X.25 Link Failed Severity: Meaning: Action: 405. Restart with cc “n” dc “n” Severity: Meaning: Action: 406. Operational Severity: Meaning: Alarms The port has been disabled from the On-Line Port Operations Menu. None.
  • Page 372 Check the PAD port and its cables for proper operation and secure connection. Traffic has become congested, and flow control procedures may be implemented. for a list of cause codes ( ) and Appendix D for a list of codes.) FRX8000 3.0 User Guide, Rev 02...
  • Page 373 415. End of Congestion, “n” events lost Severity: Meaning: 416. PAD Autocall Retries Exhausted Severity: Meaning: Action: 417. Frame Relay Link Failed Severity: Meaning: Action: 418. LP “n” Port “n” Configuration Change Request Failed Severity: Meaning: Action: 419. LP “n” Port “n” Get Configuration Request Failed Severity: Meaning: Action:...
  • Page 374 An operator at an INM or NMP has taken remote control of another FRX node connected to the network via the specified LP and port in the remote node. or re-IPLing the node. [F7] FRX8000 3.0 User Guide, Rev 02...
  • Page 375 A remote control connection to the specified LP and port in another FRX node was cleared, with the specified cause code (cc) and diag- nostic code (dc). (See Appendix There is an internal FRX8000 software problem. Contact Cabletron Systems Technical An unknown alarm was received from the network.
  • Page 376 The Remote Subscriber file has been updated. None. The SVC Subscriber file has been updated. The Default Statistics Parameters file has been updated. The X.25 Address Translation Template file has been updated. The Node file has been updated. FRX8000 3.0 User Guide, Rev 02...
  • Page 377 Meaning: 454. Remote Update File Upd:UPDATE.TXT Severity: Meaning: 455. Login Password Changed Severity: Meaning: 456. Operator Logged into Node Severity: Meaning: 457. Operator Logged out of Node Severity: Meaning: 458. PAD Login File Upd:PADLOG.DAT Severity: Meaning: 459. IP Route File Upd:IPRSUB.DAT Severity: Meaning: 460.
  • Page 378 The situation that caused alarm 310 has ended. The situation that caused alarm 311 has ended. None. The situation that caused alarm 312 has ended. None. The situation that caused alarm 313 has ended. FRX8000 3.0 User Guide, Rev 02...
  • Page 379 474. FCS Rej/Sec Under Threshold Severity: Meaning: 475. Log Rej/Sec Under Threshold Severity: Meaning: 476. Tran Err Ratio Under Threshold Severity: Meaning: 477. Rcv Err Ratio Under Threshold Severity: Meaning: 478. Port Rvc Usage Under Threshold Severity: Meaning: 479. Port Trn Usage Under Threshold Severity: Meaning: 480.
  • Page 380 Self-explanatory. The data packet size (MAXDPS) on the trunk caused a greater traffic load than the configured Bandwidth Allocation Group would allow, so the FRX8000 adjusted the bandwidth allocated to this trunk. Support. (See page 21-7.) Support. (See page 21-7.) Support.
  • Page 381 Action: 500. BPAD:Invalid Q Pkt “n” - PL Severity: Meaning: Action: 501. BPAD:Invalid Pkt “n” - PL Severity: Meaning: Action: 502. BPAD:Invalid MSG “n” - Link Severity: Meaning: Action: 503. BPAD:Invalid MSG “n” - Exchange Severity: Meaning: Action: 504. BPAD:Invalid CUA “n” DUA “n” Severity: Meaning: Action:...
  • Page 382 An invalid operation has occurred, and has disabled the port. Take the same action as for message 500. An invalid operation has occurred, and has disabled the port. Take the same action as for message 500. from the [B], [A], [C] FRX8000 3.0 User Guide, Rev 02...
  • Page 383 522. BSCI:Invalid protocol operations Severity: Meaning: Action: 523. BSCI:Invalid CUA, DUA operations Severity: Meaning: Action: 524. Invalid Line Speed LP “n” Port “n” Severity: Meaning: Action: 530. I-FRM Blocked-Remote Busy Timeout Severity: Meaning: Action: 531. I-FRM Blocked-No Acks from Remote Severity: Meaning: Action:...
  • Page 384 There was no response to a status enquiry. Contact your frame relay service provider. Self-explanatory. None. Self-explanatory. None. Self-explanatory. Configure the port, if desired. Self-explanatory. Configure the DLCI. Self-explanatory. Contact your frame relay service provider. Self-explanatory. Configure the frame relay PVC. FRX8000 3.0 User Guide, Rev 02...
  • Page 385 543. DLCI “n” Frame Discarded - CIR Severity: Meaning: Action: 544. DLCI “n” Invalid trunk port Severity: Meaning: Action: 545. DLCI “n” frame relay PVC deleted Severity: Meaning: 546. DLCI “n” frame relay PVC connected Severity: Meaning: 547. DLCI “n” Data Received on Inactive PVC Severity: Meaning: Action:...
  • Page 386 The link station sent a Disconnect Mode response, and the logical link is down. None. The remote device received an invalid command and responded with a Frame Reject. None. is the Secondary Link Station.) FRX8000 3.0 User Guide, Rev 02...
  • Page 387 Meaning: Action: 706. SDLC Stn rcvd FRMR, Nr invalid Severity: Meaning: Action: 707. SDLC Stn rcvd FRMR, Ifld too long Severity: Meaning: Action: 708. SDLC Sec. Stn sent Invalid Command Severity: Meaning: Action: 709. SDLC Sec. Stn sent unexpected IFLD Severity: Meaning: Action:...
  • Page 388 Check the modem to make sure it is operational. A necessary CTS was not received from the DCE. Check the modem to make sure it is operational. The necessary clock is not being provided. FRX8000 3.0 User Guide, Rev 02...
  • Page 389 Action: 736. SDLC LLC/2 Remote Link Stn lost Severity: Meaning: Action: 737. LLC/2 DM Received Severity: Meaning: Action: 738. LLC/2 SABME Received when open Severity: Meaning: Action: 739. LLC/2 FRMR Rcvd, Invalid Command Severity: Meaning: Action: 740. LLC/2 FRMR Rcvd, IFLD not permitted Severity: Meaning: Action:...
  • Page 390 The remote device sent an I frame that was too long, and a Frame Reject was returned. None. Self-explanatory. None. Self-explanatory. None. Self-explanatory. The line will be shut down and re-establishment will be re-tried one every minute. None. FRX8000 3.0 User Guide, Rev 02...
  • Page 391 760. Abnormal Termination Severity: Meaning: Action: 761. SDLC Transmit link error Severity: Meaning: Action: 762. SDLC Link Stn rcv FRMR, Unexp. IFLD Severity: Meaning: Action: Alarms Self-explanatory. Check the devices at both ends of the connection. Self-explanatory. The line will be shut down and re-establishment will be re-tried later.

  • Page 393: Chapter 21 Tests

    Tracing a Packet This operation traces the path a packet takes through the network. The procedure sends one or more trace packets from a source node to a destination node. Event log mes- sages tell you which intermediate nodes each packet passes through as it travels to its final destination.

  • Page 394: Measuring Packet Delay

    Packet Size 6–256 (sec). (Entering Frequency 0–32767 twice to return to the Tests Menu. (The printer [F3] runs the trace once.) [F3] at the Tests Menu (or [E], [E] runs the FRX8000 3.0 User Guide, Rev 02...

  • Page 395: Testing Connectivity Via Ip Ping

    Testing Connectivity via IP Ping The IP Ping function sends packets to an IP host to determine whether the host is reachable. Press To begin the test: 1. If a node other than the local one will generate the pings, press node number: be skipped.) 2.

  • Page 396: Ip Ping Connectivity Test Parameter

    Flooding can be hard on the network and should be used only if necessary, and only during a period of relative network inac- tivity. Valid Values Default Value none 1–250 valid address none 0–999 * 1–65535 1–256 FRX8000 3.0 User Guide, Rev 02...

  • Page 397: Appendices

    Section IV Appendices...

  • Page 399: Appendix A Async Terminal Operations

    Establishing a Connection to the Node Before establishing an end-to-end link, an async terminal must make a connection to the async PAD, as follows: 1. Once the node, async terminal, and any modems in the link are powered on, do this at the terminal: If a specific line speed is configured in the Port record, go to step 2.

  • Page 400: Command And Data Transfer Modes

    – displays the LP and port number to which you are connected, and the called mode from Data Transfer Command page A-3.) Either mode. (For a list of commands, Command = 1st parameter, = 2nd, etc.). = 1st parameter, is available. FRX8000 3.0 User Guide, Rev 02 mode Data...

  • Page 401: Placing A Call From An Async Terminal

    Placing a Call from an Async Terminal One way to place a call is simply to enter the calling address (subscriber ID) of the destination DTE. (There must be a record for that subscriber ID.) User data and/or facilities (in any combination) can be included, as described below. To place a call using facilities and user data, enter the data in the format: f,f,f-addressDdata or f, f, f-addressPdata is the letter(s) representing the desired facility(s):...

  • Page 402: Async Pad Service Signals

    – is displayed when the PAD accepts a logout command. – is displayed when the user attempts to log out, but either the Port – is self-explanatory. – means that the – is displayed when the call is cleared. FRX8000 3.0 User Guide, Rev 02...
  • Page 403 OVERRUN ERROR characters are being received by the port, resulting in loss of characters. Enabling XON-XOFF flow control (async PAD profile parameter 5) usually corrects this error. – indicates that a “page wait” condition (async PAD profile parameter 22) has PAGE occurred.

  • Page 404: Error Codes Sent To Async Pad Port

    DTE Operational Network Operational (under "Maps to:") is an escape character followed by an ASCII Keyboard [PF1] [PF2] [PF3] [PF4] (comma) (period) Maps to: ^[OP ^[OQ ^[OR ^[OS ^[Ou ^[Ov ^[Ow ^[Ol ^[On ^[OA ^[OB FRX8000 3.0 User Guide, Rev 02...

  • Page 405: Appendix B Archiving And Restoring Database

    Archiving the Database To back up a copy of the current database, you must have one or more 3½-inch 1.44MB diskettes, UNIX-formatted. 1. Press prompt. 2. Insert the diskette into the drive. If you need to format it, type is already formatted, or when the format is complete, go to step 3. 3.
  • Page 406 FRX8000 release, go to step 6. If you are loading an archived database into the same ICP/INM/NMP (whether to the same or a new hard disk) running the same FRX8000 release, go to step 7. If you are upgrading an ICP/INM/NMP to a new FRX8000 release, go to step 7.

  • Page 407: Appendix C Passwords

    The remote control password – allows the operator at an INM or NMP to take control of a remote FRX8000. The operation can also be used to take control of the local node attached to an NMP, for the purpose of accessing the local line monitor.

  • Page 408: Changing Passwords

    Main Menu; described in [B], [G] nodes of the change immediately. netlink omnili netlink aaaaaa [Del] [BackSpace] , where is your login name. (name) prompt. Update Network Defaults Chapter 18), to inform all the FRX8000 3.0 User Guide, Rev 02...
  • Page 409 You must have database master status to perform this operation. Then follow this procedure: 1. From the Main Menu, press 2. Enter your high-level password to display a menu of choices. 3. Press the letter corresponding to the password you want to change. If you select the Remote Control Password, enter the desired node number when prompted.

  • Page 411: Appendix D Cause And Diagnostic Codes

    Cause Codes Clearing Causes The cause recorded in a Clear 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 protocol error occurred, the clearing cause might indicate that the error was committed by the destination user (i.e., remote procedure error).

  • Page 412: Restart Causes

    Local procedure error Network congestion Remote DTE operational * Network operational * Incompatible destination Network out of order * PVC only From DTE Dec. Hex. Dec. Description Local procedure error Network congestion Network operational Registration/cancellation confirmed FRX8000 3.0 User Guide, Rev 02...

  • Page 413: Diagnostic Codes

    Diagnostic Codes Network-Generated Codes These diagnostic codes are generated by the network in Clear, Reset, and Restart Indi- cation packets, as well as Registration Confirmation and diagnostic packets: Hex. Dec. Description Cause and Diagnostic Codes No additional Information Invalid P(s) Invalid P(r) Packet Type Invalid (Restart Transfer Phase)
  • Page 414 Transit network facility problem * Remote network facility problem * International routing problem * Temporary routing problem * Unknown called DNIC * Maintenance action * Normal ISO IP/X.25 disconnect Connection rejection, transient condition Passed unchanged by the FRX8000. FRX8000 3.0 User Guide, Rev 02...
  • Page 415 SNA Codes Hex. Dec. Cabletron-Specific Codes Hex. Dec. Description Cause and Diagnostic Codes Description General protocol error Invalid command Unexpected command PDU reject Invalid header Invalid data International/inter-network problem Remote network problem International/inter-network protocol problem International/inter-network link out of order Invalid frame Oversized frame Sequence error...

  • Page 416: Frx8000 3.0 User Guide, Rev

    Hex. Dec. Description Facility field out of order in original translation request Duplicate facility found in original translation request Disconnect X.25/PDN trunk Connection rejected (transient condition) Connection rejected (transient condition) FRX8000 3.0 User Guide, Rev 02...

  • Page 417: Appendix E System Files

    System files contain network-wide parameters that have been configured by Cabletron, and generally should not be changed. Warning! These operations should be performed only by, or under the direction of, a person familiar with the FRX8000 source code. Improper use can cause your network to mal- function.

  • Page 418: Line Processor Type

    Applications/Statistics Type requires changing the source code. Initialize File, Inquiry, Maintenance, Contact Cabletron Systems Technical Support before changing a description, since there may be ramifications in the FRX8000 software. , then from the System File Type Selection Menu (N7000 “Standard” LP)

  • Page 419: Lp Type Parameters

    LP Type Parameters Explanations of some parameters follow the table. (Press the default.) Parameter Description Number of Ports: Aggregate Thruput: PVC Support SVC Support Trunk Support APAD Suppor t Autodialer Support LP Hardware Type Aggregate Thruput is the total line speed (in bits per second) supported by this LP type. The sum of the thruputs for all ports on an LP cannot exceed this number.

  • Page 420: Network Defaults

    These values, usually measured in bytes, are determined by a number of factors, and should not be changed from the values set in the database as shipped from Cabletron. (Figure E-1). Valid Values Default Value 1–127 1–99 2–20 1–99 1–99 0–65535 0–65535 1–255 0–255 FRX8000 3.0 User Guide, Rev 02 , then...
  • Page 421 Nucleus 7000 network to Release 5.0 from an earlier release. (Release 5.0 is necessary for N7000 compatibility with FRX8000.) If the network has Release 5.0 and pre-5.0 nodes, this parameter must be set to...

  • Page 422: Alarm Severity Level

    Release 5.0, the parameter must be reset to the nodes compatible with FRX8000 nodes, which can then be added to the network. This parameter has no function on FRX8000s. BAG Param 1 stands for Bandwidth Allocation Group Parameter 1, and determines an increment by...

  • Page 423: Appendix F Inm/Nmp Unix Operations

    Changing the Time Zone, Date, or Time When the FRX8000 software is installed, a certain time zone is specified when setting the date and time. If you wish to change this or the UNIX date and time, follow this procedure: 1.

  • Page 424: Analyzing Routing Updates

    Displaying Software Release Numbers To display the release number of the FRX8000 management (INM/NMP) software, at [NETLINK] To display the UNIX software release number, at the type uname -X [Enter] Displaying Active Processes To display all active FRX8000 processes, at the...

  • Page 425: Changing The Cumulative Statistics File Size

    Output is displayed and sent to a UNIX file “stdout,” and can be redirected or filtered using normal UNIX commands. Changing the Cumulative Statistics File Size Cumulative Statistics operations (described in cumulative data up to a file size limit set at 1MB. This limit can be changed by editing the file named .cshrc, using the UNIX vi text editor.

  • Page 426: Configuring Unix For Multiple Users

    11. Another menu will be displayed. For press This operation should be performed only by someone with a clear understanding of UNIX and of its use with the FRX8000 software. nmpini (NMP) or start -icp (ICP/INM) should be started only by the “primary”...

  • Page 427: Using The Unix "Vi" Editor

    12. Another menu will be displayed, with the choices: 1. Pick your own password 2. Pronounceable password will be generated for you Press This is where you specify a login password for the new user. When prompted for New Password choose not to require a password, press When prompted, enter the password again.

  • Page 428: Enabling/Disabling Automatic Accounting File Rollover

    L's, and stands for “Log and follow the prompts. When done, , to perform an on-line update of the twice to return to the Main [F3] prompt. [NETLINK] ), where “ ” is the desired file [Enter] FRX8000 3.0 User Guide, Rev 02 text...
  • Page 429 7. Type Enable the Change Since the software reads the .cshrc file at login, you must log out, then in again: 1. At the 2. At the UNIX login prompt, type necessary. Turn On Call Accounting 1. At the 2. From the NMP Utilities Menu, follow the procedure described earlier for Off Call another on-line update of the Network Defaults file.) Automatic rollover is now enabled and saved in the system software, and will...
  • Page 430 NMP Utilities Menu Accounting”on page F-6, this time turn it on. (Be sure to perform another on- , then type to save the [Esc] :x [Enter] . Enter your login password, if “Turn Off FRX8000 3.0 User Guide, Rev 02...

  • Page 431: Appendix G Starting And Stopping Nodes And Nmps

    FRX8000 Switch Starting a Switch To start an FRX8000, power the node on. The software will load, and the FRX8000 Test Menu (Figure G-1) will eventually be displayed. (This menu is described in the FRX8000 Installation & Setup Guide.) Starting and Stopping Nodes and NMPS Before shutting down any device, make sure all users are aware that the device will be shutting down.

  • Page 432: Frx8000 Icp

    [Enter] to accept the dis- [Enter] YYMMDDhhmm = day ( 01 to 12 01 to 31 00 to 59 Check protected subsystem netlink [Enter] . The ICP software will start, and FRX8000 3.0 User Guide, Rev 02 , where:...
  • Page 433 8. Messages will be displayed, ending with: ** Safe to Power Off ** **Press any key to Reboot** 9. Switch the unit off. Rebooting an ICP To reboot an FRX8000 ICP: 1. Press 2. When prompted: reboot. Starting and Stopping Nodes and NMPS If the following steps are not followed accurately, file corruption can occur.

  • Page 434: Frx8000 Inm

    5. Various messages will be displayed, ending with: database (y/n)? scosysv!login: 7. When asked for a password, type 8. At the The ICP software will start, and the FRX8000 Test Menu displayed. If you want to access the INM menus: 1. Press 2. At the 3.

  • Page 435: Frx8000 Inm Main Menu

    VGA monitor. If the following steps are not followed accurately, file corruption can occur. If the FRX8000 Test Menu (or one of its sub-menus) is displayed, go to step 2. If the Main Menu (or one of its sub-menus) is displayed, then go to step 2.

  • Page 436: Frx8000 Nmp

    ** Safe to Power Off ** - or - **Press any key to Reboot** If the FRX8000 Test Menu (or one of its sub-menus) is displayed, go to step 2. If the Main Menu (or one of its sub-menus) is displayed, press to step 2.

  • Page 437: N7400

    8. At the If you want to access the NMP menus: If at a VGA monitor, type If at an Auxiliary Console, type Either way, the Main Menu Stopping an NMP 1. Press 2. At the 3. At the 4. When asked for a password, type 5.

  • Page 438: N7500, N7500-Icp, Or N7500-Inm

    [Enter] to accept the dis- [Enter] YYMMDDhhmm 01 to 12 = day (01 to 31 00 to 59 Check protected subsystem netlink [Enter] -icp [Enter] start -icp [Enter] Node is Operational FRX8000 3.0 User Guide, Rev 02 , where:...

  • Page 439: Node Performance Display

    [Enter] If the following steps are not followed accurately, file corruption can occur. to display a blank screen, then press [F1] FRX8000 8000 Performance Disp lay Trans mit R eceive Trans fers/Sec ^______^______^______^______^______^______^______^______^ Figure G-3 Node Performance Display Reboot (Y to reboot, T to terminate)

  • Page 440: The Initialization Report

    , press . If the Perfor- Node is Operational twice. at the Main Menu, , press from the Main Menu). to specify the [Enter] . When prompted for a file f [Enter] v [Enter] FRX8000 3.0 User Guide, Rev 02...

  • Page 441: Appendix Hascii Character Table

    ASCII Decimal Character Value “ & (apostrophe) (asterisk) Appendix H 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 442 ASCII Character (comma) (hyphen) (period) < > (caret) (underline) (single quote) Decimal Octal Value Value Value FRX8000 3.0 User Guide, Rev 02...
  • Page 443 ASCII Character (pipe) (tilde) ASCII Character Table Decimal Octal Value Value Value...

  • Page 445: Appendix Iinm/Nmp Menu Structure

    Configure Modem Initialization SNA PAD Management. A Configure SNA 7000 HPAD-PU B Configure SNA 7000 TPAD-PU C Configure SNA FRX8000 SDLC-PU G BSC Interactive PAD Management Configure BSC Interactive Subscribers Configure BSC Interactive Devices Configure LAN Interfaces Configure IP Interfaces...
  • Page 446 D Node Software Update (N74/7500 only) E Single File Update Rollover Accounting Information File Display/Delete Call Accounting File Download Filter Definitions Convert 5.0 Node Database (trunk) (frame relay) (X.25) (async) (IP) (trunk) (X.25) (frame relay) (X.25) (async) (IP) FRX8000 3.0 User Guide, Rev 02...
  • Page 447 D Alarms Alarms Report Change Alarm Level to be Printed Display Alarms on Console Change Default Routin Load Default Routing E Tests Packet Trace Packet Delay Measurement IP Ping Connectivity Test F Statistics Configure Statistics Thresholds (Node/LP/Port) Display Statistics (Node/LP/Port/FR C IP Statistics Display IPX Statistics Clear Maximum Values...
  • Page 449 (e.g., configuration, function, operating state, performance, etc.), that is reported to automatic and specified FRX8000 or N7000 devices. An alarm is sometimes called an “event,” and alarms are sent to the “event log,” which sends them to screens, printers, and/or files (depending on how some parameters are configured).
  • Page 450 INM/NMP through an Auxiliary Console has access only to consol. Cluster controller is a device that controls input/output of a group of devices (terminals, printers, PCs, etc.) attached to it, and linking these devices to a mainframe. glo-2 FRX8000 3.0 User Guide, Rev 02...
  • Page 451 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. stands for “central processing unit.” Database contains the files that define network configuration, subscribers, alarms and statistics. Datagram is the basic unit of information passed across the Internet.
  • Page 452 Event see “Alarm.” Event log is a mechanism in the FRX8000/N7000 software that passes alarms on to screens, printers, and/or files, depending on how alarm reporting is configured in the Node file. 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 453 Display operations. The other is consol, which is identical to “gcon,” except that it does not have access to graphics mode. HPAD is an integral (to an FRX8000 or N7000 node) SNA or BSC PAD connected to a host device. Hunt group is a designated group of ports that share incoming calls according to a pre-defined algorithm.
  • Page 454 “daughter” card attached to an RLP and containing the components that support a hardware interface: RS-232/V.28, V.35, or RS-422/V.11. Line Processor is the module in an FRX8000 or N74/7500 node that provides the input/output ports to wide-area network (WAN) interfaces and internodal trunk links. stands for “line processor.”...
  • Page 455 Nucleus 7000, 7400, 7500, 7500-ICP, 7500-INM is the network switch family that is supported by the current release of FRX8000, to allow a smooth transition from an N7000 network to FRX8000. Nucleus 7000 (also called N7000) is the general product name. N7400 is a DOS-based node and N7500 is a UNIX-based node.
  • Page 456 “DCE” and “DTE.” Port is an entry or exit point for node and NMP data transmission. Each FRX8000 LP (line processor) has four or eight physical ports, depending on the number of attached Line Interface Cards. Additionally, each physical X.25 or frame relay port supports up to 56 logical ports.
  • Page 457 QLLC stands for “qualified logical link control.” stands for “Routing Information Protocol,” which provides for dynamic exchange of routing information between routers in a TCP/IP implementation. is the RISC-based line processor card, which is a “mother” card with one or two attached Line Interface cards.
  • Page 458 -icp is the executable that starts the management processes in an FRX8000 or N7500 INM. Subscriber is a user device accessing the network. 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.
  • Page 459 “token” that is passed around the ring until taken by a station, which inserts a packet, then retransmits the token. TPAD is an integral (to an FRX8000 or N74/7500 node) SNA or BSC Interactive PAD con- nected to a terminal. Trunk is an internodal link.
  • Page 460 PAD and a packet-mode DTE or another PAD. XPAD is an integral (to an FRX8000 or N74/7500 node) transparent PAD. It can be used to network any SNA device that can be networked using any of the other SNA PAD types.
  • Page 461 Many entries are screen prompts, commands, or are listed as displayed. 1490 Encapsulation 10-27 1st,2nd,etc. Redirected Sub No. 1st,2nd,etc. Routing Path 9-18 5.0 database, converting 17-18 A,B,C,D Bits 6-15 Abbreviated Address, configuring Access (Community Table) 15-4 Active processes, displaying Additional BSC Parameters 11-6 Address 15-5...
  • Page 462 Enable Bandwidth Alloc? 7-10 4-7, 7-16, 9-8, 10-8, 12-14 4-7, 7-16, 9-8, 10-8, 7-21 13-6 13-9 14-15 14-15 14-15 13-6 10-8 12-14 12-6 12-16 12-16 12-16 12-15 12-15 8-10 12-15 11-6 12-7 12-7 12-6 17-20 FRX8000 3.0 User Guide, Rev 02 12-14...
  • Page 463 Frame relay DLCIs, configuring Frame relay utilization statistics, displaying Frame relay, configuring Frame Type 14-7 Frame-level statistics 19-6 Framing , 6-12, 6-14 FRX8000 Switch starting stopping Full Duplex 11-7 Generate 11-6 Generate Clock 7-15, 8-6, 9-7, 10-8 Generate M-bit Packets...
  • Page 464 10-16 10-16 11-11 7-21 12-9 12-13 12-8 7-16 7-16 6-12 6-10 19-4 6-14 6-11 10-9 10-23 10-24 3-5, 9-10 7-15, 8-7, 9-7, 10-8, 11-6, 3-11 13-7 11-6 7-15, 11-5 10-7 11-12 19-8 FRX8000 3.0 User Guide, Rev 02 12-14 12-14...
  • Page 465 Maximum Throughput Class Maximum Transmission Unit 13-5, Maximum Window Size Menu levels Menu structure Menus in graphics-level status displays Menus, negotiating Message Services 17-23 Metric Count 13-9 Model number, configuring 15-6 Model Type 6-11, 6-14 Modem Disconnect Timeout Modem INI Name Modem initialization 7-10 Modem Initialization record...
  • Page 466 17-4 17-22 10-25 17-6 11-11 10-22 11-5 12-15 12-15 7-25, 9-8, 9-29 14-8 14-8 14-13 13-6 13-6 14-9 14-16 18-9 18-9 10-27 13-9 14-19 13-9 14-20 14-16 13-6 10-24 12-15 FRX8000 3.0 User Guide, Rev 02 11-6 12-18 12-18 12-18...
  • Page 467 Source Network Value 14-15 Source Node Value 14-16 Source Socket Value 14-16 Source Subscriber 13-6 Speed (in async PAD profile) 12-6 Starting FRX8000 ICP FRX8000 INM FRX8000 Switch N7400 N7500 N7500 ICP N7500 INM Index Static routes Statistics clearing maximum values...
  • Page 468 Watchdog Spoofing Enabled 14-9 Weight Wildcards in subscriber addresses Window Size 7-21 X.25 19-6 X.25 translation templates 9-21 X.25, configuring X.3 Line Speed Code 12-13 X1,2,3 Bits 6-15 Idx-8 19-7 19-25 17-2 18-4 9-15 FRX8000 3.0 User Guide, Rev 02...

Table of Contents