1. DL manuals
  2. Cabletron Systems
  3. Switch
  4. 9F426-02
  5. User Manual

Cabletron Systems 9F426-02 User Manual

Other manuals for 9F426-02: Appendix, User Manual
Manual is about: Frame relay module for MMAC-Plus

Summary of 9F426-02

  • Page 1

    User guide for release 3.3.1 09-41-06-109-04 for mmac-plus frx 4000 frame relay access products frame relay module frx 4000 tm tm frx 6000 frx 6000 the com plete network ing solution tm.

  • Page 3

    Iii rev date reason for update 01 april 1997 preliminary release 02 april 1997 general availability 03 july 1997 release 3.3.1 04 august 1997 frame relay module for mmac-plus™ cabletron systems reserves the right to make changes in specifications and other information contained in this document with...

  • Page 4

    Iv frx/frm 3. 3 user g uide, rev 04 changes or modifications made to this device which are not expressly approved by cabletron systems could void the user’s authority to operate the equipment. Doc this digital apparatus does not exceed the class a limits for radio noise emissions from digital appara...

  • Page 5: Table Of Contents

    V table of contents section i introduction 1 chapter 1 introduction to netlink frame relay access devices multiprotocol support .............................................................................. 1-2 management functions .......................................................................

  • Page 6

    Vi frx/frm 3. 3 user g uide, rev 04 chapter 6 configuring frame relay configuring bandwidth allocation groups..................................................... 6-6 bandwidth allocation group parameters ................................................ 6-7 configuring frame relay ports ...............

  • Page 7

    Vii configuring async pad login parameters .................................................. 10-7 login parameters .................................................................................... 10-8 configuring async port records ..................................................................

  • Page 8

    Viii frx/frm 3. 3 user g uide, rev 04 section iii operation chapter 15 introduction to system operation chapter 16 on-line operations on-line node operations.............................................................................. 16-2 remote control ...............................................

  • Page 9

    Ix frame relay utilization statistics ............................................................... 17-44 chapter 18 system events configuration .......................................................................................... 18-1 alarm buffer ...............................................

  • Page 10

    X frx/frm 3. 3 user g uide, rev 04 list of figures 1-1 network example.................................................................................. 1-1 1-2 ports on the netlink frx4000 .............................................................. 1-6 1-3 frx6000 rlp, lics, and cables ............

  • Page 11

    Xi 7-10 x.25-to-x.25 pvc screen ................................................................... 7-23 8-1 sna port screen 1 ................................................................................. 8-2 8-2 sdlc pu subscriber parameters screen .................................................

  • Page 12

    Xii frx/frm 3. 3 user g uide, rev 04 16-2 ip ping connectivity test menu ....................................................... 16-15 16-3 on-line sdlc pu operations menu ............................................... 16-16 17-1 node status display ....................................................

  • Page 13

    Xiii 6-4 logical port parameters....................................................................... 6-22 6-5 logical port cug parameters ............................................................. 6-23 6-6 subscriber parameters .....................................................................

  • Page 14

    Xiv frx/frm 3. 3 user g uide, rev 04 13-2 bridge generic filter parameters........................................................ 13-7 13-3 bridge mac filter parameters............................................................ 13-8 13-4 bridge sap filter parameters...................................

  • Page 15

    Section i introduction.

  • Page 17: Chapter 1

    Chapter 1 introduction to netlink frame relay access devices cabletron's netlink ™ family is designed to provide a comprehensive method of inte- grating lan-based systems and wide-area applications into a "blended" network. Ranging from the frx4000 network access node to the frx8000 backbone switch,...

  • Page 18: Multiprotocol Support

    1-2 frx/frm 3. 3 user g uide, rev 04 some typical frx/frm applications are: ● sdlc-to-llc2 and llc2-to-qllc conversion over frame relay ● sna and tcp/ip lan/wan integration—with or without routers ● banking applications—lan, sna, tcp/ip, async ● traffic aggregation and concentration to public frame ...

  • Page 19

    Introduction to netlink frame relay access devices 1-3 sna/sdlc ● configurable frame size ● configurable link addresses ● nrz/nrzi support ● compatible with qllc/npsi ● hpad (pu 2.1, 4.0), tpad (pu 1.0, 2.0, 2.1), npad, and xpad (transparent) modes ● point-to-point and multipoint configurations ● sd...

  • Page 20

    1-4 frx/frm 3. 3 user g uide, rev 04 ip ● rip versions 1 & 2 ● icmp ● arp ● standard ndis interfaces for ethernet, token ring, and 802.3 lans ● rfc 1490 frame relay and rfc 1356 x.25 interfaces for wans ● ping ipx ● connection of lan-attached workstation to remote router or server via x.25, frame re...

  • Page 21: Management Functions

    Introduction to netlink frame relay access devices 1-5 management functions frx and frm devices support the same management functions: ● local snmp agent, with "set" capability from network manager on some mib variables ● support for netlink omniview ™ network manager, providing an hp openview ™ net...

  • Page 22: Hardware Overview

    1-6 frx/frm 3. 3 user g uide, rev 04 hardware overview frx4000 the base model of a netlink frx4000 contains four serial ports for connection to a frame relay or x.25 network, user devices, and/or other frx-series devices. Each frx4000 also contains one lan interface, either ethernet or token ring. O...

  • Page 23

    Introduction to netlink frame relay access devices 1-7 cables serial port cables are shown in the following table. Lan interfaces the ethernet model of the netlink frx4000 contains an ethernet interface, provided in rj-45 (for twisted pair) and 15-pin "d" (aui, for thicknet) configurations. The ethe...

  • Page 24: Frx6000

    1-8 frx/frm 3. 3 user g uide, rev 04 the following items are shipped with each frx4000: ● cable, db9s to db9s, for connecting the node's console port directly to a pc with software emulating an ascii terminal. ● adapter, db9p to db25s, for connecting the node directly (via the above cable) to an asc...

  • Page 25

    Introduction to netlink frame relay access devices 1-9 figure 1-3 frx6000 rlp, lics, and cables as shown in figure 1-3, one or two line interface cards (lics) mount to an rlp and provide electrical interfaces to connectors on the rlp. Each lic supports four i/o ports, all of the same interface type....

  • Page 26

    1-10 frx/frm 3. 3 user g uide, rev 04 lan adapters the frx6000 supports lan (local-area network) interfaces via one or two of these adapters: ● ethernet (802.3) – 10baset (rj45/twisted pair), 10base2 (bnc/coax), or aui (db15/coax) ● token ring (802.5) – rj45 (twisted pair) or db9 figure 1-4 lan card...

  • Page 27

    Introduction to netlink frame relay access devices 1-11 operator interfaces installation of frx6000 software into a node, generally done before the node ships to the customer, requires a directly connected keyboard and monitor. Once the node has been installed and configured, it can function with no...

  • Page 28: Frame Relay Module

    1-12 frx/frm 3. 3 user g uide, rev 04 frame relay module the frame relay module mounts into an mmac-plus chassis, and connects to an ethernet module in the chassis via a cable from an ethernet port on the frm. The frm draws power from the chassis, but does not interact with other modules in the chas...

  • Page 29

    Introduction to netlink frame relay access devices 1-13 serial and lan interfaces figure 1-7 frame relay module with i/o boxes and cabling as shown in the figure, each 60-pin serial connector on the frm supports up to four i/o ports, all of the same interface type. A cable carries each connector’s s...

  • Page 30

    1-14 frx/frm 3. 3 user g uide, rev 04 operator interfaces installation of software into an frm, generally done before the node ships to the cus- tomer, requires a directly connected keyboard and monitor. Once the node has been installed and configured, it can function with no operator interface. How...

  • Page 31

    Introduction to netlink frame relay access devices 1-15 introduction to menu operations the frx/frm user interface consists of a series of menus and sub-menus that are used to configure, control, and monitor a node. To protect the system from unautho- rized access, menu operations are accessible onl...

  • Page 32: Moving Through The Menus

    1-16 frx/frm 3. 3 user g uide, rev 04 after the operator presses [f1] at the screen in figure 1-8 and enters a password (described on page 3-2), the main menu will appear: figure 1-9 main menu this is the starting point for all menu operations. The organization of the menus is shown in appendix g. M...

  • Page 33: On-Line Help

    Introduction to netlink frame relay access devices 1-17 throughout this manual are tables of valid and default values. To specify a default (if one exists), press [enter] in response to a prompt. Be careful; pressing [enter] when it is not required may cause the next prompt to automatically select t...

  • Page 34

    1-18 frx/frm 3. 3 user g uide, rev 04 f5: copy record —copies a port record's database values to another port's record, which can be convenient if several records in a node will have identical (or almost identical) configurations. After you perform this operation, the "copied to" record will be disp...

  • Page 35

    Introduction to netlink frame relay access devices 1-19 function keys on an ascii terminal standard pc keyboard function keys are represented as follows on an ascii terminal keyboard: pc ascii keyboard keyboard maps to: [f1] [pf1] ^[op [f2] [pf2] ^[oq [f3] [pf3] ^[or [f4] [pf4] ^[os [f5] [5] ^[ou [f...

  • Page 36: Stopping Operation

    1-20 frx/frm 3. 3 user g uide, rev 04 stopping operation logging out if you have been working with menu operations and wish to log out, press [f4] at the main menu. The port status display screen is displayed, with any updates. The software will continue to run, but only those who know the password ...

  • Page 37

    Section ii configuration.

  • Page 39: Chapter 2

    Chapter 2 introduction to database configuration each netlink frx4000, frx6000, and frame relay module contains its own config- uration database, which contains information identifying the hardware components, and defines the operating parameters of the hardware and software. Each database file cont...

  • Page 40

    2-2 frx/frm 3. 3 user g uide, rev 04 database setup recommendations to set up a configuration database, you must create records for all rlps (even on an frx4000 or frm, which must have rlp 0 configured), ports, and subscribers (users of the ports), as well as other records that define the configurat...

  • Page 41

    Introduction to database configuration 2-3 producing a configuration report a configuration report contains this information: ● software version number ● passwords ● boot time ● various database parameter values ● line status for each port to create a configuration report, press [a] at the reports m...

  • Page 42

    2-4 frx/frm 3. 3 user g uide, rev 04 where to find database records the following shows where to find the various configuration files among the menus. (the first item, a–configuration , is an entry on the main menu.) following some items are the chapters/appendices in this manual where the items bel...

  • Page 43

    Introduction to database configuration 2-5 d configure ipx filter applications – (chapter 12) applies ipx filters to interfaces/filter types/directions. E on-line update ipx filter definitions and applications – (chapter 12) allows updating the frx/frm with any changes without rebooting. F review br...

  • Page 44

    2-6 frx/frm 3. 3 user g uide, rev 04 a review x.25 address translation templates b configure x.25 address translation templates c test x.25 address translation templates e configure logical ports – (chapter 6) specifies operating parameters for logical ports residing on physical frame relay ports. F...

  • Page 45

    Introduction to database configuration 2-7 b view configuration report – (chapter 2) displays the results of the above operation. F configure frame relay backup groups – (chapter 6) allows creation of one or more frame relay ports/dlcis that will act as backup(s) for a port..

  • Page 47: Chapter 3

    Chapter 3 configuring node parameters some database parameters apply throughout an frx4000, frx6000, or frame relay module; for example, the password used to access menu operations, or the date and time. Some of these parameters are specific to certain protocols and are described in the appropriate ...

  • Page 48: Changing The Login Password

    3-2 frx/frm 3. 3 user g uide, rev 04 changing the login password the login password is used to gain access to menu operations. When software is shipped to the customer, the password is netlink . (note the upper case—all pass- words are case sensitive.) to change the password, press [a] at the node c...

  • Page 49

    Configuring node parameters 3-3 setting the date and time various operations and reports record the current date and time, as recognized by the originating device. This operation allows changing one or both, to assure that all devices in a network are synchronized. Press [b] at the node configuratio...

  • Page 50: Configuring Node Defaults

    3-4 frx/frm 3. 3 user g uide, rev 04 configuring node defaults node defaults are a set of parameters that identify an frx/frm for purposes of remote control, file transfers, and/or alarm reporting to or from other frxs or frms, and define connections between the frx/frm and a netview manager device....

  • Page 51: Node Defaults Parameters

    Configuring node parameters 3-5 node defaults parameters all possible parameters on the first two node defaults screens are listed in table 3-2, and the netview parameters on the third screen are listed in table 3-3 (on page 3-9). Descriptions of most parameters follow each table. Depending on the v...

  • Page 52

    3-6 frx/frm 3. 3 user g uide, rev 04 node name is displayed at the upper right of the screen when the device is being controlled by the "local" keyboard and monitor. (if the local operator is controlling a remote frx/frm, the remote control id of that device will be displayed as the local node name ...

  • Page 53

    Configuring node parameters 3-7 primary alarm output id of a collecting node. The alarm system is designed for guar- anteed delivery to the primary output device, and output to the secondary device only if it is available. Problems with the secondary device will not stop delivery to the primary devi...

  • Page 54

    3-8 frx/frm 3. 3 user g uide, rev 04 max congestion is a percentage of the frx/frm alarm buffer. If this level is exceeded, no more alarms will be put into the buffer until it has reached the specified min congestion . (see that entry below and "alarm buffer" page 18-2.) min congestion is a percenta...

  • Page 55

    Configuring node parameters 3-9 netview parameters 1 up to 10 characters can be entered, but only the first 8 will be recognized by netview. 2 be aware that some nvmts are larger than 265 bytes, so you may want to set the value higher. 3 in multiples of 4. 4 must be less than the value for t1 to ens...

  • Page 56

    3-10 frx/frm 3. 3 user g uide, rev 04 local sap address is a service access point (sap) address used to identify the frx/frm to a netview host. This parameter is relevant only in a connection to a 3174 or as/400-type setup where a specific source sap address is required. If the session will be run o...

  • Page 57

    Configuring node parameters 3-11 if acknowledgments/responses are still outstanding after n2 tries (see " n2 "), the link station will declare the link inoperative. The value specified for t1 should allow for any delays introduced by the mac sub- layer (e.G., queuing). T2 is the receiver acknowledgm...

  • Page 58: Warning Messages

    3-12 frx/frm 3. 3 user g uide, rev 04 warning messages these messages may be displayed on some screens if there is a problem with the con- figuration for alarm reporting. Primary alarm reporting error will appear at the top of all screens on a collecting node if the software that drives the alarm ou...

  • Page 59: Chapter 4

    Chapter 4 configuring cards and protocols the circuitry that supports the serial i/o ports in a netlink frx6000 or frame relay module (frm) resides on one or (frx6000 only) more risc-based line processor cards (rlps), and on one or two four-port line interface cards (lics) mounted on each rlp. (see ...

  • Page 60: Frx4000

    4-2 frx/frm 3. 3 user g uide, rev 04 frx4000 protocols the line processor file contains this information for an frx4000: ● amount of dram memory installed. ● type of line interface card. (the serial expansion card in an frx4000 is iden- tical to the frx6000 line interface card.) ● configured and loa...

  • Page 61

    Configuring cards and protocols 4-3 figure 4-2 lp configuration menu for frx4000 [a],[b],[b] from main menu lp, status, lp type, and line interface card 1 will always be as shown above. Line interface card 2 will be read from the installed card (if present). To add or remove a protocol: 1. Press the...

  • Page 62

    4-4 frx/frm 3. 3 user g uide, rev 04 frx4000 lp parameters 1 all of these might not be available on an frx4000. It depends on which protocols were purchased. Also, note the guidelines in the explanation. (note that nvsp is netview service point.) protocol determines which protocols can run in the no...

  • Page 63: Lan Interface

    Configuring cards and protocols 4-5 lan interface each frx4000 contains a built-in lan interface, either ethernet or token ring (depending on the model). To configure the interface, press [c] at the port configu- ration menu. When prompted for an interface number , press [enter] (accepting the defau...

  • Page 64: Frx6000

    4-6 frx/frm 3. 3 user g uide, rev 04 frx6000 rlps and protocols the line processor file contains this information for each rlp in an frx6000: ● rlp number and status (installed, configured) ● amount of memory installed (4mb or 8mb) ● type(s) of line interface card(s) ● configured and loaded protocol...

  • Page 65

    Configuring cards and protocols 4-7 figure 4-4 frx6000 rlp, lics, and cables lp switch 8 7 6 5 4 3 2 1 0 on off* off on off on on on 1 on on off 2 on off on 3 on off off 4 off on on 5 off on off 6 off off on 7 off off off lic 1 rlp on off 1 8 * switch 7 is off for 8 mb rlp, on for 4 mb rlp. Lic 2 rl...

  • Page 66

    4-8 frx/frm 3. 3 user g uide, rev 04 figure 4-5 lp configuration menu for frx6000 [a],[b],[b] from main menu on a new record for an rlp that is not installed, status and memory con- figuration will be blank until the record is saved. Although nine protocol entries are shown, a 4mb rlp supports a max...

  • Page 67

    Configuring cards and protocols 4-9 lp parameters in an frx6000 1 the size of each protocol and the amount of rlp memory determine the combinations of protocols that can be configured on an rlp. (see explanation.) lp type cannot be changed if the rlp is installed. If it is not installed, the value c...

  • Page 68: Lan Cards

    4-10 frx/frm 3. 3 user g uide, rev 04 when configuring protocols, follow these guidelines: ● all supported protocols will fit on one 8mb rlp; however, as an entire database (interfaces, subscribers, route tables, etc.) is configured, much more memory is used. For that reason, it is recommended that ...

  • Page 69

    Configuring cards and protocols 4-11 to configure a record for a lan card in an frx6000, press [c] at the port configu- ration menu. (unlike serial ports, there are not separate files for the cards and the ports.) when prompted for an interface number , press 0 or 1 , whichever number cor- responds ...

  • Page 70: Frame Relay Module

    Frame relay module rlp and protocols the line processor file contains this information for the rlp in an frm: ● status (installed, configured) ● amount of memory installed (always 8mb) ● type(s) of line interface cards ● configured and loaded protocols the terms "lp" and "rlp" are interchangeable. T...

  • Page 71

    Configuring cards and protocols 4-13 figure 4-7 frame relay module rlp, lics, and cables lic 1 connector frm lic 2 connector rlp cable i/o box 4 5 6 7 1 2 3 0 lan interface cable lan card.

  • Page 72

    4-14 frx/frm 3. 3 user g uide, rev 04 figure 4-8 lp configuration menu for frame relay module [a],[b],[b] from main menu to add or remove a protocol: 1. Press the letter corresponding to the protocol number. The protocol in the configured column will change to the next one in the list shown in table...

  • Page 73

    Configuring cards and protocols 4-15 lp parameters in a frame relay module 1 the size of each protocol determines the combinations that can be configured. (see explanation.) line interface card 1, 2 contain the circuitry for the physical ports of an rlp. (lic 1 contains ports 0–3, lic 2 contains por...

  • Page 74: Lan Cards

    4-16 frx/frm 3. 3 user g uide, rev 04 lan cards you can display a report that identifies the lan card in the frm. Press [b] at the port configuration menu (or [a], [c], [b] from the main menu). The display will be the con- tents of the file protocol.Ini (which can also be printed from dos or copied ...

  • Page 75

    Configuring cards and protocols 4-17 if the node is connected to a lan after this record is created, or if the node becomes disconnected from the lan, the lan connection must be ini- tialized/re-initialized by opening the lan card configuration record, then pressing [f7] to send the configuration to...

  • Page 76

    4-18 frx/frm 3. 3 user g uide, rev 04.

  • Page 77: Chapter 5

    Configuring serial port s 5-1 chapter 5 configuring serial ports serial ports provide access connections to non-lan devices and routing connections to networks. Each port must be configured in the software to specify the operating parameters of the hardware and the protocol that will run on the port...

  • Page 78

    5-2 frx/frm 3. 3 user g uide, rev 04 frx6000 the physical connectors in an frx6000 reside on the rlps, but the circuitry that defines the physical port types is on attached line interface cards (lics). An rlp contains up to two lics. Lic 1 supports ports 0–3, and lic 2 supports ports 4–7. Figure 5-2...

  • Page 79

    Configuring serial port s 5-3 frame relay module the physical connectors in an frm reside on the rlp, but the circuitry that defines the physical port types is on the attached line interface cards (lics). Lic 1 (see ) sup- ports ports 0–3, and lic 2 supports ports 4–7. Figure 5-3 physical ports on f...

  • Page 80

    5-4 frx/frm 3. 3 user g uide, rev 04 database and system memory values two sets of values exist for port and channel parameters: database values exist in the software, and are recorded as system memory values when the node is booted. If the parameter port type is the same in both sets of values, bot...

  • Page 81

    Configuring serial port s 5-5 configuring a physical port before configuring a physical port, make sure that the following have been properly configured: ● node parameters. See chapter 3. This is general configuration that must be done no matter which protocols will be run in the node. ● line proces...

  • Page 82

    5-6 frx/frm 3. 3 user g uide, rev 04 the entry i/o identifies the lic containing the port ( universal for frx4000 ports 0–3), and link state will be one of these: link_disable – the link was shut down by an on-line command, is undergoing re- ipl, or has not yet been established. Failed – some or all...

  • Page 83: Chapter 6

    Chapter 6 configuring frame relay frame relay ports in the netlink frx4000, frx6000, and frame relay module are used to carry frame relay traffic, as well as other protocols encapsulated in frame relay (per rfc 1490, via logical x.25 ports over frame relay). A frame relay port can act as physical dc...

  • Page 84

    6-2 frx/frm 3. 3 user g uide, rev 04 any sessions in progress when a primary dlci goes down will not be transferred directly to the backup dlci, but will be reset, then established on the backup. Dlcis used for backup on the initiating node are assigned to "backup groups," each of which can contain ...

  • Page 85

    Configuring frame relay 6-3 example 1 in example 1, the primary link is between node 1/lp 2/port 4/dlci 16 and node 2/ port 5/dlci 18. The dlcis should be configured as described below. (the param- eters are described later in this chapter.) then if the primary link goes down, a con- nection will au...

  • Page 86

    6-4 frx/frm 3. 3 user g uide, rev 04 on node 2, configure the following (as well as other parameters necessary for oper- ation): 1. Port configuration ( [a], [c], [a] from main menu): lp?: 0 rlp port?: 5 o additional parameters d configure dlci parameters dlci id?: 18 i dlci backup configuration a b...

  • Page 87

    Configuring frame relay 6-5 ● svc subscriber id(s) (described later in this chapter), which identifiy user devices to each other and the frx/frm. ● pvc connections (described later in this chapter), which define "permanent" circuits between physical ports in the node..

  • Page 88

    6-6 frx/frm 3. 3 user g uide, rev 04 configuring bandwidth allocation groups to optimize frame relay bandwidth use, various types of interfaces can be assigned to one of sixteen bandwidth allocation groups, each defined by the parameters listed in table 6-1. Bandwidth allocation groups can ensure th...

  • Page 89

    Configuring frame relay 6-7 figure 6-2 bandwidth allocation group menu [a],[a],[h] from main menu pressing [n] will display page 2, which contains parameters for groups 5–8. Page 3 contains groups 9–12, and page 4 contains groups 13–16. Bandwidth allocation group parameters explanations of the param...

  • Page 90

    6-8 frx/frm 3. 3 user g uide, rev 04 both groups are assigned to ip interfaces. Under a full traffic load, group 1 will be allocated 60/130 (46%) of the available bandwidth, and group 2 will be allocated 70/ 130 (54%). Group "n" excess priority allows setting a priority for traffic within each group...

  • Page 91

    Configuring frame relay 6-9 configuring frame relay ports once the necessary node, line processor, and protocol parameters have been con- figured, press [a] at the port configuration menu (or [a], [c], [a] from the main menu. When prompted, enter: ● lp number of the rlp containing the port: 0–7 for ...

  • Page 92

    6-10 frx/frm 3. 3 user g uide, rev 04 figure 6-4 frame relay port screen 2 reviewing dlci configuration (figure 6-4, item c) to display the current configured dlcis on the port, press [c] at the screen in figure 6-4. A screen similar to the following information will be displayed for each con- figur...

  • Page 93

    Configuring frame relay 6-11 backup configurations. In the example in figure 6-5, dlci 50 is a primary. All the parameters are listed in table 6-3 (on page 6-15). The parameters in the first line are: ● rlp , port , dlci are self-explanatory. ● icir = committed information rate (in) ● ibc = committe...

  • Page 94

    6-12 frx/frm 3. 3 user g uide, rev 04 figure 6-6 frame relay dlci configuration screen 1 pressing [f4] at this or the subsequent screen (figure 6-7) will delete the dlci rate control and backup configuration. (the port will not be deleted unless [f4] is pressed at one of the higher-level port screen...

  • Page 95

    Configuring frame relay 6-13 figure 6-7 frame relay dlci configuration screen 2 if you configure a backup group number , enable backup protocol will be replaced by several parameters (listed in table 6-3 on page 6-15) that determine backup operation. If you change enable backup protocol to y , the b...

  • Page 96: Frame Relay Port Parameters

    6-14 frx/frm 3. 3 user g uide, rev 04 frame relay port parameters 1 if set to y , no backup dlcis on this port will be used (even if the port is enabled via on- line port enable). 2 not applicable to frx4000 dsu ports. 3 this parameter is relevant only if physical port interface is something other t...

  • Page 97

    Configuring frame relay 6-15 1 if rate control will not be used, configure the committed information rate (cir) to match the line speed on the port. Otherwise, the de-bit will be set on all received frames. 2 cir = committed information rate. (see first parameter in table.) 3 applicable only on the ...

  • Page 98

    6-16 frx/frm 3. 3 user g uide, rev 04 v.35, rs-449, and x.21 . (rs-449 and x.21 interfaces require an rs-422 lic, which is available by special order.) ● frx6000 ports 0–7 on each rlp are determined by the line interface card(s) and attached i/o cables. Line processor configuration identifies the li...

  • Page 99

    Configuring frame relay 6-17 logical dce defines the port as (if y ) logical dce or (if n ) dte. The port must be configured as the opposite of the device at the other end of the connection. Logical and physical dce/dte are independent of each other (e.G., a port can be a physical dce and logical dt...

  • Page 100

    6-18 frx/frm 3. 3 user g uide, rev 04 declared active after that poll. (if the n2 error threshold is exceeded during the n3 count, the dce will be declared inactive, and the n3 count will be restarted.) t1 link integrity timer determines how often the logical dte will initiate a status enquiry messa...

  • Page 101

    Configuring frame relay 6-19 excess burst size (in/out) (b e ) is the incoming or outgoing (depending on the parameter) maximum amount of data in excess of the committed burst size that the network will attempt to transfer during the time interval used for the committed burst size . Any data exceedi...

  • Page 102

    6-20 frx/frm 3. 3 user g uide, rev 04 switchover timer is the time the initiating node will wait after detecting a primary dlci failure before it checks for available backups. Switchback timer is the time the initiating node will wait before switching from the backup to the primary dlci after the pr...

  • Page 103: Configuring A Logical Port

    Configuring frame relay 6-21 configuring a logical port configuration of logical ports in an frx/frm allow multiple legacy protocols (sdlc, async, bisync, etc.) to be encapsulated (via x.25) and transmitted over a single physical frame relay port. Some things to know are: ● encapsulation can be via ...

  • Page 104: Logical Port Parameters

    6-22 frx/frm 3. 3 user g uide, rev 04 any menu items preceded by asterisks instead of letters cannot be changed. These are displayed only because the software code for the menu is shared with physical port configuration. If you want to configure one or more closed user groups (cugs) for the port, pr...

  • Page 105

    Configuring frame relay 6-23 1 once this parameter has been selected for the first time, 1 becomes the default value. 2 1–7 if modulo 8, 1–127 if modulo 128. Changing this parameter will disable the link only if the new value changes the modulus. 3 maximum packet size values are 128, 256, 512, 1024,...

  • Page 106

    6-24 frx/frm 3. 3 user g uide, rev 04 connection priority prioritizes this logical port for intra-nodal traffic; the higher the number, the higher the priority. (this priority has no effect on traffic exiting a node.) a priority is also configured in node defaults, as well as for each logical port, ...

  • Page 107

    Configuring frame relay 6-25 bility of an eventual correct transfer between dte and dce, but a smaller value permits faster detection of a permanent error condition. T1 retransmit period is the length of time before transmission of an i-frame if the previous transmission is not acknowledged. If the ...

  • Page 108

    6-26 frx/frm 3. 3 user g uide, rev 04 throughput class negotiation is an optional x.25 facility that permits negotiation of the throughput classes for either direction of data transmission on a per call basis. If n is selected, the default ( maximum throughput class ) will be used. If y is selected,...

  • Page 109

    Configuring frame relay 6-27 default window size will be assigned to an incoming call setup packet if the packet does not include a window size. Maximum throughput class specifies the default throughput class that will be inserted into a call request packet if throughput class negotiation is not ena...

  • Page 110

    6-28 frx/frm 3. 3 user g uide, rev 04 cation.) if the clear retry count expires, restart and recovery procedures should be ini- tiated. Closed user group parameters the cug function is a privacy feature that allows creation of up to 100 groups of users per port. Members of a cug can communicate with...

  • Page 111

    Configuring frame relay 6-29 configuring subscriber addresses this operation configures the called and calling addresses that will be used in call setup. To complete the connection, the software must recognize where the call is coming from (calling address) and where it is going (called address). To...

  • Page 112: Subscriber Parameters

    6-30 frx/frm 3. 3 user g uide, rev 04 subscriber parameters 1 the software does not verify that the specified lp/port exists. Make sure the specified lps and ports are configured in the database, and that they actually exist. Subscriber name identifies the subscriber to the console operator. Routing...

  • Page 113

    Configuring frame relay 6-31 systematic redirection will redirect (if y ) all calls to the alternate subscribers specified by the redirection addresses. Consecutive attempts at call redirection will be made to each alternate sub- scriber in the list, until the call is completed. Redirect on busy wil...

  • Page 114

    6-32 frx/frm 3. 3 user g uide, rev 04 configuring frame relay pvcs across the node an frx4000 or frx6000 pvc is a "permanent" connection between two physical ports in a node. This allows communication between the attached devices as soon as they are powered up, without the need to first establish a ...

  • Page 115: Frame Relay Pvc Parameters

    Configuring frame relay 6-33 frame relay pvc parameters 1 the dlci must match the dlci configured at the remote end of the physical link. 2 some formulae that might help in determining these values are: b c >= 8 times maximum packet size. B e c multiplied by [(line speed/cir) minus 1]. Connection pr...

  • Page 116

    6-34 frx/frm 3. 3 user g uide, rev 04 committed information rate (cir) is the data throughput that the network agrees to support under normal condi- tions. Committed burst size (b c ) is the maximum amount of data that the network agrees to transfer under normal conditions within the time period def...

  • Page 117

    Configuring frame relay 6-35 configuring frame relay backup groups a frame relay backup group is one or more dlcis (on the same rlp) that can act as a backup for one or more "primary" dlcis (also on the same rlp). If a node detects a failure in a primary dlci connection, the software will search any...

  • Page 118

    6-36 frx/frm 3. 3 user g uide, rev 04 port is the physical port on which the backup dlci is being configured. Dlci is the backup being configured. Waittimer is the time after a primary dlci failure that the software will wait for this dlci to become active before checking the next backup dlci. If th...

  • Page 119: Chapter 7

    Chapter 7 configuring x.25 a netlink frx/frm x.25 port can connect to an x.25 dte or an x.25 network. This allows the node to transmit x.25 traffic, as well as ip and ipx (encapsulated per rfc 1356), and sna (per qllc). This chapter describes configuration of a physical x.25 port. If x.25 will be en...

  • Page 120: Configuring X.25 Ports

    7-2 frx/frm 3. 3 user g uide, rev 04 configuring x.25 ports once the necessary node, line processor, and protocol parameters have been con- figured, press [a] at the port configuration menu (or [a], [c], [a] from the main menu. When prompted, enter: ● lp number of the rlp containing the port: 0–7 fo...

  • Page 121: X.25 Port Parameters

    Configuring x.25 7-3 ● if this port will be connected to a dial modem, press [p] . (see "configuring a dial port" on page 7-12.) ● if none of the above applies, press [f3] twice to return to x.25 port screen 1, then perform the next desired operation. You cannot configure a port to be both a network...

  • Page 122

    7-4 frx/frm 3. 3 user g uide, rev 04 1 1–7 if modulo 8, 1–127 if modulo 128. 2 this parameter is relevant only if physical port interface is something other than rs- 232 and generate cl ock is y . 3 if sdlc-llc2 conversion is configured over the port, fast select acceptance must be y . Also, if the ...

  • Page 123

    Configuring x.25 7-5 v.35, rs-449, rs-530 , and x.21 . (rs-449, rs-530, and x.21 i nterfaces require an rs-422 lic.) ● frm ports 0–7 are determined by the line interface cards and attached i/o cables. Line processor configuration identifies the lics, and only the valid interfaces will be displayed o...

  • Page 124

    7-6 frx/frm 3. 3 user g uide, rev 04 n2 retransmit count is x.25 value n2 , the maximum number of times the node will attempt to send an i- frame after a retransmit period expiration. A larger value for this parameter increases the probability of an eventual correct transfer between dte and dce, but...

  • Page 125

    Configuring x.25 7-7 on-line system memory changes/database display determines which set of values will change, as described under "database and system memory values" on page 5-4. Lowest/highest incoming/two-way/outgoing channel are the ranges of logical channel numbers (lcns) that subscribers can u...

  • Page 126

    7-8 frx/frm 3. 3 user g uide, rev 04 mask link alarms prevents (if enabled) transmission to the collecting node of the link alarms 400-406 ( link enabled, link disabled , etc.) maximum packet size is the maximum data packet size that will be allowed to pass through this port. A packet size included ...

  • Page 127: Cug Management

    Configuring x.25 7-9 dte restart retry count is the number of times a restart request from the logical dte will be transmitted. (the dte will stop issuing the request on receipt of a restart confirmation or restart indication.) if the restart retry count expires, restart and recovery procedures shou...

  • Page 128

    7-10 frx/frm 3. 3 user g uide, rev 04 to configure a cug, press [e] and, when prompted, enter: ● cug index: 0-99 (the default is 0 ), which is simply a reference to the cug. ● cug number: 1-16383 (the default is 1 ), that will be associated with the index. ● any other requested information. (see tab...

  • Page 129

    Configuring x.25 7-11 configuring a network trunk a network trunk is a link between frx/frm nodes, over x.25. Other ports in the node can be assigned to a "trunk group," which will cause those ports to be disabled if the network trunk is not operational (and enabled when the trunk becomes opera- tio...

  • Page 130: Configuring A Dial Port

    7-12 frx/frm 3. 3 user g uide, rev 04 configuring a dial port if the port will be connected to an auto-dial modem, configure the parameters on the following screen. Figure 7-4 x.25 dial port parameters dial port parameters dial support specifies whether this port is connected to a dial modem and, if...

  • Page 131

    Configuring x.25 7-13 inactivity timer will be started as soon as there are no active connections on a dial port. (it has no function on a non-dial port.) if no new connections are established before the period expires, the port will be disabled until the next call is placed, if a dial-out port, or ...

  • Page 132

    7-14 frx/frm 3. 3 user g uide, rev 04 configuring subscriber addresses this operation configures the called and calling addresses that will be used in call setup. To complete the connection, the software must recognize where the call is coming from (calling address) and where it is going (called add...

  • Page 133: Subscriber Parameters

    Configuring x.25 7-15 subscriber parameters 1 the software does not verify that the specified lp/port exists. Make sure the specified lps and ports are configured in the database, and that they actually exist. Subscriber name identifies the subscriber to the console operator. Routing algorithm allow...

  • Page 134

    7-16 frx/frm 3. 3 user g uide, rev 04 systematic redirection will redirect (if y ) all calls to the alternate subscribers specified by the redirection addresses. Consecutive attempts at call redirection will be made to each alternate sub- scriber in the list, until the call is completed. Redirect on...

  • Page 135

    Configuring x.25 7-17 configuring x.25 address translation templates the frx/frm 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 d...

  • Page 136

    7-18 frx/frm 3. 3 user g uide, rev 04 to resolve any differences in addressing conventions, the backup path invokes a trans- lation of the called and calling addresses. The frx/frm-compatible called and calling addresses are translated into pdn-compatible called and calling addresses. Node 2 has a t...

  • Page 137

    Configuring x.25 7-19 the fields must match the equivalent fields in the call request packet, but not neces- sarily literally—they can use wildcards. Figure 7-8 address translation template screen [a],[c],[d],[b] from main menu translation template parameters 1 used simply for ease of identification...

  • Page 138

    7-20 frx/frm 3. 3 user g uide, rev 04 all wild cards are valid in the translation template, allowing one template to function for many calls. The frx/frm routes traffic based on the user data field if the u operator is present in the svc routing table. The gateway also allows the u operator, and can...

  • Page 139: Translation Examples

    Configuring x.25 7-21 type u followed (with no spaces) by the desired characters, 1–9 , a–c , indicating which positions of the twelve digits in the original user data are to replace the selected portion of the packet. If you are replacing called or calling address with original user data, all the r...

  • Page 140

    7-22 frx/frm 3. 3 user g uide, rev 04 testing a translation template press [c] at the x.25 address translation templates menu ( [a], [c], [d], [c] from the main menu) or [d] at the operations menu ( [b], [d] from the main menu) to test a translation template you have created. When prompted, enter: ●...

  • Page 141

    Configuring x.25 7-23 configuring x.25-to-x.25 pvcs an frx/frm pvc is a "permanent" connection between two physical ports in a node. This allows communication between the attached devices as soon as they are powered up, without having to first make a call to establish a connection. X.25 pvc support ...

  • Page 142: X.25 Pvc Parameters

    7-24 frx/frm 3. 3 user g uide, rev 04 x.25 pvc parameters 1 logical channels must be lower than the lowest lcns assigned to any subscribers on the ports in the pvc configuration. 2 16, 32, 64 ,128, 256, 512, 1024, 2048 , or 4096 . Cannot be greater than the smaller maximum packet size specified on t...

  • Page 143: Chapter 8

    Chapter 8 configuring sna sna ports in netlink frx/frm devices are used to connect ibm hosts with pus (physical units), over a frame relay (via rfc1490) or x.25 (via annex g) network. Devices attached to frx/frm sna ports can also communicate with any qllc- compatible devices that have integral x.25...

  • Page 144: Configuring An Sna Port

    8-2 frx/frm 3. 3 user g uide, rev 04 configuring an sna port once the necessary node, line processor, and protocol parameters have been con- figured, press [a] at the port configuration menu (or [a], [c], [a] from the main menu. When prompted, enter: ● lp number of the rlp containing the port: 0–7 f...

  • Page 145

    Configuring sna 8-3 figure 8-2 sdlc pu subscriber parameters screen an sna tpad subscriber can specify only one remote device, which can be an hpad or an x.25 connection to the host. An hpad subscriber can specify up to 16 remote devices, any of which can be a tpad or an x.25 connection to the host....

  • Page 146: Sna Port Parameters

    8-4 frx/frm 3. 3 user g uide, rev 04 sna port parameters 1 although 10 characters can be entered, only the first 8 will be recognized by some remote manager devices. 2 can sometimes be changed without disabling the link—see explanation. 3 this parameter is relevant only if physical port interface is...

  • Page 147

    Configuring sna 8-5 1 if the pu will be used for sdlc-llc2 conversion (at the local node, or at a remote node via a logical or physical x.25 port), this must be y . 2 in multiples of 4. 3 will override the value configured for the same parameter in the node defaults file, with two exceptions—if 0 is...

  • Page 148

    8-6 frx/frm 3. 3 user g uide, rev 04 physical port interface must be configured as follows. For reference, port locations are shown on page 5-1 (frx4000), page 5-2 (frx6000), and page 5-3 (frm). ● frx4000 port 0 is always rs-232 . ● frx4000 port 1 is rs-232 or dsu , depending on whether the optional...

  • Page 149

    Configuring sna 8-7 if an rs-232 dce port is directly connected to the dte via the standard cabletron cable, the maximum supported speed is 64k. If longer cabling is used, the maximum speed is 19.2k. (the eia standard for rs-232 addresses speeds up to 19.2 kbps.) no data poll period is the time betw...

  • Page 150

    8-8 frx/frm 3. 3 user g uide, rev 04 nrz determines the level of data encoding: y = nrz (non-return to zero) on, which means that 1 represents high-level encoding and 0 is low-level. N = nrz off, which means that 1 represents no change in level and 0 is a change. Unless there is a site-specific conf...

  • Page 151

    Configuring sna 8-9 pu subscriber parameters pu name identifies the pu to an snmp or netview host. Local subscriber id is the subscriber address of the local end of an sna connection. (a subscriber id— see page 8-13—must also be configured.) remote subscriber id is the subscriber address of the remo...

  • Page 152

    8-10 frx/frm 3. 3 user g uide, rev 04 l2datmode determines whether transmission can be in one (alternate) or two (simultaneous) direc- tions at the same time. Llc2 parameters local sap address is the remote service access point (sap) address used to connect the pu to the host. This parameter is rele...

  • Page 153

    Configuring sna 8-11 if t1 expires and acknowledgments/responses are still outstanding, the link station will send one of the following, then restart t1 : ● a supervisory lpdu with the p bit set to b'1,' to solicit remote link station status. ● any unnumbered lpdus that were not responded to the fir...

  • Page 154

    8-12 frx/frm 3. 3 user g uide, rev 04 nection. The device processor in the node uses these priorities to help determine the order in which it will process protocols. Bandwidth allocation group assigns the llc2 host to one of sixteen groups whose parameters regulate bandwidth usage. See "configuring ...

  • Page 155

    Configuring sna 8-13 configuring subscriber addresses this operation configures the called and calling addresses that will be used in call setup. To complete the connection, the software must recognize where the call is coming from (calling address) and where it is going (called address). To display...

  • Page 156: Subscriber Parameters

    8-14 frx/frm 3. 3 user g uide, rev 04 subscriber parameters 1 the software does not verify that the specified lp/port exists. Make sure the specified lps and ports are configured in the database, and that they actually exist. Subscriber name identifies the subscriber to the console operator. Routing...

  • Page 157

    Configuring sna 8-15 systematic redirection will redirect (if y ) all calls to the alternate subscribers specified by the redirection addresses. Consecutive attempts at call redirection will be made to each alternate sub- scriber in the list, until the call is completed. Redirect on busy will redire...

  • Page 158

    8-16 frx/frm 3. 3 user g uide, rev 04 configuring a hunt group for sna subscribers hunt groups are described in appendix b. The function has some special requirements for sna routing: ● each sna port in a routing path must have a unique network address, even if it will not be used explicitly by the ...

  • Page 159: Configuring Llc2

    Configuring sna 8-17 configuring llc2 llc2 (logical link control type 2) support in the frx/frm provides a local or remote connection over frame relay (via rfc1490) or x.25 (via qllc) between two sna devices, one attached to a lan and the other attached to either another lan or a frame relay-complia...

  • Page 160

    8-18 frx/frm 3. 3 user g uide, rev 04 figure 8-4 llc2 examples to run llc2 in an frx or frm, you must first configure the following in the database: ● node parameters. See chapter 3. ● line processor(s) that will contain the interface(s) to the network and/or frame relay pvc, plus line interface car...

  • Page 161

    Configuring sna 8-19 configuring a virtual lan id a virtual lan id is normally assigned by a system administrator. The id is used internally by the frx/frm to identify a virtual bridge that connects the llc2 function to lan interfaces. If llc2 will run in the local node, press [b] at the configure l...

  • Page 162: Configuring Llc2 Hosts

    8-20 frx/frm 3. 3 user g uide, rev 04 configuring llc2 hosts each sna/llc2 host device that will connect to an frx/frm running llc2 must be configured in the database. To display any llc2 hosts already configured for this node, press [c] at the configure lan default parameters menu (or [a], [a], [e]...

  • Page 163

    Configuring sna 8-21 figure 8-7 llc2 terminated host configuration screen [a],[a], [e],[d] from main menu pressing [m] will display a screen similar to figure 8-8. Figure 8-8 llc2 host connections screen this example shows a configuration for an originated session. A display for a terminated session...

  • Page 164: Llc2 Host Parameters

    8-22 frx/frm 3. 3 user g uide, rev 04 llc2 host parameters 1 except ffffffffffff. Must be in 802.5 (token ring) format, which may require "bit swapping" when entering the address. (see the explanation of host mac address .) 2 a host address can be configured for one originated and one terminated ses...

  • Page 165

    Configuring sna 8-23 host mac address is the 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 frx/frm, this address must be entered as a "bit-swapped" translation of the address that the node is expecti...

  • Page 166

    8-24 frx/frm 3. 3 user g uide, rev 04 the node will reset t1 when it receives one of these: ● a rej (reject) lpdu, provided a command lpdu with the p bit set to b'1' is not outstanding. ● a response lpdu with the f bit set to b '1.' ● an information or supervisory lpdu with an n r greater than the l...

  • Page 167

    Configuring sna 8-25 n3 will be reset whenever an information or supervisory acknowledgment lpdu is sent by the local node. Tw is the maximum number of sequentially numbered information lpdus that the local node can have outstanding. If tw is reached, and acknowledgment will be sent. N2 is the maxim...

  • Page 168

    8-26 frx/frm 3. 3 user g uide, rev 04 connection, this address must match the remote subscriber id in the remote node's llc2 host record. Remote subscriber id is the subscriber address assigned to the remote end of the sna connection. If config- uring an llc2-to-sdlc link, this address must match th...

  • Page 169: Configuring Llc2 Interfaces

    Configuring sna 8-27 configuring llc2 interfaces llc2 interfaces records define the types and locations of the interfaces that will carry llc2 traffic to or from an frx or frm. To display configured interfaces, press [c] at the lan interfaces configuration menu: figure 8-9 llc2 interfaces display [a...

  • Page 170

    8-28 frx/frm 3. 3 user g uide, rev 04 figure 8-10 bridge port/llc2 interface record, ethernet [a],[c], [f],[d] from main menu this example shows an ethernet configuration. A token ring configu- ration screen is similar. Figure 8-11 bridge port/llc2 interface record, frame relay [a],[c], [f],[d] from...

  • Page 171: Llc2 Interface Parameters

    Configuring sna 8-29 llc2 interface parameters the following table lists parameters for all interface types. Explanations of some parameters follow the table. 1 make sure the port is not configured for backup use only. (see chapter 6.) 2 make sure the dlci is not part of a frame relay dlci backup gr...

  • Page 172

    8-30 frx/frm 3. 3 user g uide, rev 04 path cost will be added together with all other path costs on a link between bridges. The total will then be compared to other total path costs to determine the least "expensive" end- to-end path. Priority prioritizes intra-nodal traffic; the higher the number, ...

  • Page 173

    Configuring sna 8-31 avoid configuring parallel bridge/llc2 frame relay links between two frx/frm devices if one path is in native llc2 format and the other in some other format. Since the same inter- faces are used for both protocols and the spanning tree will elim- inate dual paths for bridged tra...

  • Page 175: Chapter 9

    Chapter 9 configuring bsc frx4000, frx6000, and the frame relay module support bsc (binary synchronous communication) ports configured as interactive or batch. Bsc interactive ports are used to connect ibm 3270 hosts to remote cluster controllers (via hpad-tpad com- munication) over frame relay or x...

  • Page 176

    9-2 frx/frm 3. 3 user g uide, rev 04 configuring bsc interactive port records once the necessary node, line processor, and protocol parameters have been con- figured, press [a] at the port configuration menu (or [a], [c], [a] from the main menu. When prompted, enter: ● lp number of the rlp containin...

  • Page 177

    Configuring bsc 9-3 figure 9-2 bsc interactive port record, screen 3 del (item h) lets you delete the remote subscriber that is currently highlighted. You will be prompted: delete "n," where "n" is the sequence number. Pressing [y] will delete that line and move all entries below it up one sequence ...

  • Page 178

    9-4 frx/frm 3. 3 user g uide, rev 04 1 relevant only if physical port interface is other than rs-232 and generate clock is y . 2 see note under figure 9-1. Port type defines the protocol the port will support. Selecting this parameter will display a list of valid protocols. An frx4000 port can be co...

  • Page 179

    Configuring bsc 9-5 physical port interface must be configured as follows. For reference, port locations are shown on page 5-1 (frx4000), page 5-2 (frx6000), and page 5-3 (frm). ● frx4000 port 0 is always rs-232 . ● frx4000 port 1 is rs-232 or dsu , depending on whether the optional csu/ dsu card is...

  • Page 180

    9-6 frx/frm 3. 3 user g uide, rev 04 if an rs-232 dce port is directly connected to the dte via the standard cabletron cable, the maximum supported speed is 64k. If longer cabling is used, the maximum speed is 19.2k. (the eia standard for rs-232 addresses speeds up to 19.2 kbps.) retransmission peri...

  • Page 181

    Configuring bsc 9-7 call info in call request packet specifies whether the user will have the option of including call information in a call request packet. Currently, this must be configured as y . Clear vc on last device down if y , causes the virtual circuit to be cleared when no terminals are us...

  • Page 182

    9-8 frx/frm 3. 3 user g uide, rev 04 mented. The timer will be de-activated on reception of any valid frame from the line during link down . No response retry count specifies how many times the user device will be polled (if it is not responding) before control is passed on the next cluster (accompa...

  • Page 183

    Configuring bsc 9-9 configuring bsc batch port records once the necessary node, line processor, and protocol parameters have been con- figured, press [a] at the port configuration menu (or [a], [c], [a] from the main menu. When prompted, enter: ● lp number of the rlp containing the port: 0–7 for frx...

  • Page 184: Bsc Batch Port Parameters

    9-10 frx/frm 3. 3 user g uide, rev 04 figure 9-4 bsc batch port record, screen 3 bsc batch port parameters table 9-2 bsc batch port parameters parameter valid values default value port type bsc-b (not valid here) physical port interface see explanation see explanation blocked port flag y/n n line sp...

  • Page 185

    Configuring bsc 9-11 1 relevant only if physical port interface is something other than rs-232 and generate cl ock is y . Port type defines the protocol the port will support. Selecting this parameter will display a list of valid protocols. An frx4000 port can be configured as any wan protocol loade...

  • Page 186

    9-12 frx/frm 3. 3 user g uide, rev 04 v.35, rs-449, and x.21 . (rs-449, rs-530, and x.21 i nterfaces require an rs-422 lic. Also, rs-530 and x.21 are available through special order only.) blocked port flag will cause the port to be enabled ( n ) or disabled ( y ) at node ipl. The port will remain i...

  • Page 187

    Configuring bsc 9-13 generate clock specifies whether the port will generate the clock necessary to synchronize traffic over the link. If the port is a physical dce (determined by the port's i/o cable interface), specify y , since the physical dce generates clock. If the port is dte, specify n . Rcv...

  • Page 188

    9-14 frx/frm 3. 3 user g uide, rev 04 # of trailing pad chars specifies the number of padding characters that will be added to the end of each frame, to ensure that the last significant character is sent before the data transmitter switches off. No response timer is activated after transmission of a...

  • Page 189

    Configuring bsc 9-15 retry timer is the time between autocall retries. Retry number is the maximum number of times an autocall will be sent. Note that a value of 0 allows indefinite retries. Delete lets you delete the remote subscriber that is currently highlighted. You will be prompted: delete "n,"...

  • Page 190

    9-16 frx/frm 3. 3 user g uide, rev 04 configuring subscriber addresses this operation configures the called and calling addresses that will be used in call setup. To complete the connection, the software must recognize where the call is coming from (calling address) and where it is going (called add...

  • Page 191: Subscriber Parameters

    Configuring bsc 9-17 subscriber parameters 1 the software does not verify that the specified lp/port exists. Make sure the specified lps and ports are configured in the database, and that they actually exist. Subscriber name identifies the subscriber to the console operator. The frx/frm software doe...

  • Page 192

    9-18 frx/frm 3. 3 user g uide, rev 04 systematic redirection will redirect (if y ) all calls to the alternate subscribers specified by the redirection addresses. Consecutive attempts at call redirection will be made to each alternate sub- scriber in the list, until the call is completed. Redirect on...

  • Page 193

    Configuring bsc 9-19 configuring bsc interactive devices port records contain the information that identifies ports configured for bsc inter- active operation. You must also define the devices connected to those ports. To display a list of configured devices, press [a] at the bsc devices configurati...

  • Page 194

    9-20 frx/frm 3. 3 user g uide, rev 04 figure 9-6 bsc interactive devices screen [a],[c],[g],[b] from main menu pressing [e] displays a list of configured devices. Bsc interactive device parameters explanations of some parameters follow the table. Single user virtual circuit specifies (if n ) that ea...

  • Page 195

    Configuring bsc 9-21 printer specifies whether the device has an attached printer. Disable status response determines how the bsc port will report the status of the attached device: 0 = normal status. The port will report what the device reports. 1 = no status. The port will report status only if th...

  • Page 197: Chapter 10

    Chapter 10 configuring async ports the integral async pad function in the netlink frx4000, frx6000, and frame relay module allow asynchronous devices to connect to a frame relay or x.25 network. To run a port as an integral async pad in an frx or frm, you must first configure the following in the da...

  • Page 198

    10-2 frx/frm 3. 3 user g uide, rev 04 configuring async pad profiles an async pad profile is a specific set of x.3 parameters whose values define the oper- ation of the device connected to an async pad port on an frx or frm. Different pro- files contain the same parameters, but with difference(s) in...

  • Page 199: Pad Profile Parameters

    Configuring async ports 10-3 pad profile parameters the numbers preceding the parameter names correspond to ccitt x.3. Also, the default values make up ccitt profile 90. When specifying characters that will perform functions (i.E., data forwarding or character delete ), be sure to specify these as d...

  • Page 200

    10-4 frx/frm 3. 3 user g uide, rev 04 0 = escape is not allowed. 1 = escape will be initiated by [ctrl] [p] ( 1/0 ), data link escape . 32–126 = escape will be initiated by the character defined by this number. 02, echo provides for characters received from the user's device to be transmitted back t...

  • Page 201

    Configuring async ports 10-5 0 = no action. 1 = pad will send an interrupt packet to the remote end but will remain in data transfer mode. 2 = pad will reset the virtual call and remain in data transfer mode. 4 = pad will send an indication of a break message to the remote end and remain in data tra...

  • Page 202

    10-6 frx/frm 3. 3 user g uide, rev 04 previously stored character to be deleted at packet forwarding or if a line display is performed. 17, line delete is the ascii value of the character that will delete all characters stored in the editing buffer. 18, line display allows the dte to display the con...

  • Page 203

    Configuring async ports 10-7 configuring async pad login parameters if an async subscriber will be required to log into an frx/frm async pad, a login id must be assigned. To display a list of existing login ids and associated pad profile names, press [c] at the async pad configuration menu (or [a], ...

  • Page 204: Login Parameters

    10-8 frx/frm 3. 3 user g uide, rev 04 login parameters 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. Profile name is a name given to the async pad's "profile," described earlier ...

  • Page 205

    Configuring async ports 10-9 configuring async port records once the necessary node, line processor, and protocol parameters have been con- figured, press [a] at the port configuration menu (or [a], [c], [a] from the main menu. When prompted, enter: ● lp number of the rlp containing the port: 0–7 fo...

  • Page 206: Async Pad Port Parameters

    10-10 frx/frm 3. 3 user g uide, rev 04 async pad port parameters 1 at line speeds of 38.4k bps or higher, rts/cts h/w flow contr ol should be y . Port type defines the protocol the port will support. Selecting this parameter will display a list of valid protocols. An frx4000 port can be configured a...

  • Page 207

    Configuring async ports 10-11 physical port interface must be configured as follows. For reference, port locations are shown on page 5-1 (frx4000), page 5-2 (frx6000), and page 5-3 (frm). ● frx4000 port 0 is always rs-232 . ● frx4000 port 1 is rs-232 or dsu , depending on whether the optional csu/ d...

  • Page 208

    10-12 frx/frm 3. 3 user g uide, rev 04 login required determines whether or not async pad users will be required to log in before con- necting with this port. If y , the user will be prompted to log in, and must enter a login id and login password (see page 10-7) or an abbreviated address (see page ...

  • Page 209

    Configuring async ports 10-13 user data is an (optional) string of ascii characters that will be placed verbatim into the user data field of an outgoing call request packet. Facilities is an (optional) string of facility codes and related data that will be placed verbatim into the facility field of ...

  • Page 210

    10-14 frx/frm 3. 3 user g uide, rev 04 if the user logs out, the disconnect timer will be ignored, and the line will immediately be disconnected. This parameter should be n for a leased line; otherwise, the pad banner and prompt will periodically be output. (this is harmless, but unnecessary.) this ...

  • Page 211

    Configuring async ports 10-15 configuring subscriber addresses this operation creates records for the called and calling addresses that will be used in call setup. To complete the connection, the software must recognize where the call is coming from (calling address) and where it is going (called ad...

  • Page 212: Subscriber Parameters

    10-16 frx/frm 3. 3 user g uide, rev 04 subscriber parameters 1 the software does not verify that the specified lp/port exists. Make sure the specified lps and ports are configured in the database, and that they actually exist. Subscriber name identifies the subscriber to the console operator. The fr...

  • Page 213

    Configuring async ports 10-17 systematic redirection will redirect (if y ) all calls to the alternate subscribers specified by the redirection addresses. Consecutive attempts at call redirection will be made to each alternate sub- scriber in the list, until the call is completed. Redirect on busy wi...

  • Page 214

    10-18 frx/frm 3. 3 user g uide, rev 04 configuring abbreviated addresses the abbreviated address operation allows you to assign a short name or mnemonic to be used in place of the subscriber id when making x.25 calls from a terminal con- nected to an frx/frm async pad port. To display a list of exis...

  • Page 215: Configuring Async Pvcs

    Configuring async ports 10-19 configuring async pvcs an frx/frm pvc is a "permanent" connection between two physical/logical ports in a node. This allows communication between the attached devices as soon as they are powered up, without having to first make a call to establish a connection. Async pv...

  • Page 216: Async Pvc Parameters

    10-20 frx/frm 3. 3 user g uide, rev 04 async pvc parameters 1 16, 32, 64 ,128, 256, 512, 1024, 2048, or 4096 . Cannot be greater than the smaller maximum packet size specified in the port records for both ends of the connection. 2 cannot be greater than the smaller maximum window size specified in t...

  • Page 217: Chapter 11

    Chapter 11 configuring ip the ip functions in the netlink frx4000, frx6000, and frame relay module support routing of ip (internet protocol) traffic among ip devices on lans and routed subnetworks, via frame relay or x.25. Routing can be dynamic (rip versions 1 and 2 are supported), and static route...

  • Page 218: Required Configuration

    11-2 frx/frm 3. 3 user g uide, rev 04 using the node as an ip gateway an frx or frm can function as an ip gateway, and forward ip packets. This requires that ip (not ip-r) be configured (and loaded) in the lp file (described in chapter 4). Required configuration to run ip in an frx/frm, you must fir...

  • Page 219: Specifying A Rip Version

    Configuring ip 11-3 specifying a rip version frx and frm support two versions of rip (routing information protocol), the routing protocol used by ip. If you will be using rip version 1, you do not need to configure a version, since version 1 is the default in the database. If will be using rip versi...

  • Page 220: Configuring Ip Interfaces

    11-4 frx/frm 3. 3 user g uide, rev 04 configuring ip interfaces an ip interface allows the internet protocol to be executed over a frame relay, x.25, or lan port. To display all ip interfaces configured on the node, press [a] at the configure lan interfaces menu (or [a], [c], [f], [a] from the main ...

  • Page 221: Ip Interface Parameters

    Configuring ip 11-5 ip interface parameters explanations of most parameters follow the table. 1 these addresses must also be configured in subscriber records (described in chapter 7), and cannot contain wildcards. In the record for the source subscriber, do not configure any routing path. In the rec...

  • Page 222

    11-6 frx/frm 3. 3 user g uide, rev 04 mediate routers or gateways, as well as the destination host. If the maximum trans- mission unit value is less than the size of a minimal ip datagram, the value will automatically change to the minimal datagram size. Network mask is used during routing to determ...

  • Page 223

    Configuring ip 11-7 lan card number identifies the lan card that contains the interface. (only 0 is valid on frx4000 or frm, since frx4000 has no lan cards and frm has only one.) source subscriber is a subscriber id associated with the source ip interface port. (the port is the first routing path co...

  • Page 224

    11-8 frx/frm 3. 3 user g uide, rev 04 configuring static ip routes routing of ip traffic is handled dynamically by such protocols as rip, as well as via static routes configured in the frx/frm. To display configured static routes, press [f] at the connections and routing paths menu (or [a], [d], [f]...

  • Page 225: Ip Routing Parameters

    Configuring ip 11-9 ip routing parameters 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. Route type: network defines a route for a network. Ho...

  • Page 226

    11-10 frx/frm 3. 3 user g uide, rev 04 configuring ip-to-x.25 pvcs an frx/frm pvc is a "permanent" connection between two physical/logical ports in a node. This allows communication between the attached devices as soon as they are powered up, without having to first make a call to establish a connec...

  • Page 227: Ip-to-X.25 Pvc Parameters

    Configuring ip 11-11 ip-to-x.25 pvc parameters 1 16, 32, 64 , 128, 256, 512, 1024, 2048 , or 4096 . Cannot be greater than the smaller maxim um packet size specified in the port records for both ends of the connection. 2 cannot be greater than the smaller maximum window size specified in the port re...

  • Page 228

    11-12 frx/frm 3. 3 user g uide, rev 04 logical channel is a logical link between the node and the subscriber. The physical line may have a number of logical channels. 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. Lp/por...

  • Page 229: Chapter 12

    Chapter 12 configuring ipx the netlink frx4000, frx6000, and frame relay module support connections to novell ipx networks, for the purpose of routing traffic among lan-attached work- stations and local/remote servers, over frame relay or x.25, or between local lans. Frx and frm support ipx versions...

  • Page 230

    12-2 frx/frm 3. 3 user g uide, rev 04 configuring ipx node defaults press [e] at the configure lan default parameters menu (or [a], [a], [e], [e] from the main menu) to configure default ipx node parameters. Figure 12-1 ipx node defaults menu [a],[a], [e], [e] from main menu ipx node defaults parame...

  • Page 231

    Configuring ipx 12-3 configuring ipx filter definitions filtering is the method by which the network manager controls usage of a mixed network by connection-oriented and connectionless traffic. (connectionless traffic does not require establishment of a logical connection prior to data exchange.) a ...

  • Page 232: How Filter Masks Work

    12-4 frx/frm 3. 3 user g uide, rev 04 figure 12-2 ipx sap filter record [a], [a],[e], [f],[b] from main menu how filter masks work each ipx filter parameter except filter name and server name is assigned a value and an associated mask. The mask determines (by the process described below) whether the...

  • Page 233: Ipx Filter Parameters

    Configuring ipx 12-5 ipx filter parameters table 12-2 through table 12-5 list the various filter parameters. Explanations of some parameters follow the tables. Explanations of individual masks are not included below because they were described in general under "how filter masks work" on page 12-4. F...

  • Page 234

    12-6 frx/frm 3. 3 user g uide, rev 04 server name identifies a specific server whose incoming/outgoing packets will be affected by the sap filter. Network address value is an ipx network number assigned to the network containing the server identified by server name . Node address value identifies th...

  • Page 235

    Configuring ipx 12-7 04 = sap packet 05 = spx (sequenced packet exchange) packet 11 = ncp (netware core protocol) packet 14 = propagated packet, used for netbios (an ibm protocol that performs transport- and session-layer tasks) destination network value is the network number of the destination node...

  • Page 236

    12-8 frx/frm 3. 3 user g uide, rev 04 configuring ipx filter applications ipx filter applications determine how filters will be used at the interface. To review existing applications, press [c] at the configure filter definitions and applications menu (or [a], [a], [e], [f], [c] from the main menu)....

  • Page 237

    Configuring ipx 12-9 permit determines whether the traffic defined by the filter "n" entries will be permitted or denied passage across the interface. Filter "n" corresponds to the filter id s in the ipx filter definitions file. (see page 12-3.).

  • Page 238: Configuring Ipx Interfaces

    12-10 frx/frm 3. 3 user g uide, rev 04 configuring ipx interfaces an ipx interface allows an frx/frm to connect to a novell ipx network. Press [e] at the lan interfaces configuration menu (or [a], [c], [f], [e] from the main menu) to display configured ipx interfaces. To configure an interface, pres...

  • Page 239: Ipx Interface Parameters

    Configuring ipx 12-11 ipx interface parameters table 12-7 lists the parameters common to all interface types, and table 12-8 through table 12-10 list parameters specific to each interface type. Explanations of most parameters follow each table. 1 802.5 is not valid on frx4000. 2 frame size in bytes....

  • Page 240

    12-12 frx/frm 3. 3 user g uide, rev 04 interface type: supported types are: ethernet, 802.5 (token ring) (frx6000 only), x.25, and frame relay. Frame type: type_ii matches novell's ethernet_ii frame type. Raw matches novell's ethernet_802.3 frame type. Llc matches novell's ethernet_802.2 or token-ri...

  • Page 241

    Configuring ipx 12-13 periodic rip enabled determines whether the node will originate periodic ipx routing information pro- tocol (rip) messages from this interface (assuming rip is enabled), to inform the network that the route through this interface is viable. Periodic rip timer is the interval be...

  • Page 242

    12-14 frx/frm 3. 3 user g uide, rev 04 disabling serialization allows filtering of these broadcasts to reduce wan traffic, and is not intended to interfere with copyright-protection mechanisms. Watchdog spoofing enabled determines whether this interface will be used by the local node to respond to "...

  • Page 243

    Configuring ipx 12-15 destination subscriber is a subscriber id associated with the physical x.25 port that will be used for the ipx interface. (see the footnote following table 12-9.) svc retry timer is the frequency with which calls will be placed to try to establish a connection. Svc idle timer i...

  • Page 244

    12-16 frx/frm 3. 3 user g uide, rev 04 configuring static ipx routes routing of ipx traffic is handled dynamically by such protocols as rip and sap, as well as via static routes configured in the frx/frm. To display configured static routes, press [h] at the connections and routing paths menu (or [a...

  • Page 245

    Configuring ipx 12-17 network is the ipx network address of the network containing the node defined by node number . Hops is the number of routers in a packet's path to the destination network. Transport time is the time (in 55-millisecond units) that it will normally take a packet to reach the des-...

  • Page 246

    12-18 frx/frm 3. 3 user g uide, rev 04 server socket number is an ipx socket number that identifies the process. For example, the sap process is 0452 . Intervening networks is the number of routers that a packet must pass through to reach the server, if this route is used. Router is the hex value of...

  • Page 247: Chapter 13

    Chapter 13 configuring bridging the netlink frx4000 and frx6000 support transparent "spanning tree" bridging of non-routable lan traffic (e.G., netbios, decnet, appletalk) over frame relay between 802.3/ethernet or 802.5/token ring lans. Frx4000/6000 also support translational bridging between ether...

  • Page 248: Required Configuration

    13-2 frx/frm 3. 3 user g uide, rev 04 avoid configuring parallel bridge/llc2 frame relay links between two frx nodes if one path is in native llc2 format and the other in some other format. Since the same interfaces are used for both protocols and the spanning tree will eliminate dual paths for brid...

  • Page 249

    Configuring bridging 13-3 configuring default node-wide bridging parameters if one or more bridge ports (interfaces) will be established in the local node, certain parameters must be configured to define bridge operation. Press [b] at the configure lan default parameters menu (or [a], [a], [e], [b] ...

  • Page 250

    13-4 frx/frm 3. 3 user g uide, rev 04 bridge node default parameters 1 to assure correct operation of the spanning tree algorithm, follow these rules: a. Bri dge max age must be less than or equal to twice the value of { bridge forw ard delay minus 1 second}. B. Bri dge max age must be greater than ...

  • Page 251

    Configuring bridging 13-5 bridge forward delay is the time the bridge will wait after entering listening state before entering learning state, or after entering learning state before entering forwarding state this delay is intended to assure that the tree topology is stable before it is put into use...

  • Page 252

    13-6 frx/frm 3. 3 user g uide, rev 04 configuring bridge filter definitions filtering is the method by which the network manager controls usage of an inter- network. A filter permits or denies (depending on how it is configured) some or all of a specific type of bridged traffic across an interface. ...

  • Page 253: How Filter Masks Work

    Configuring bridging 13-7 how filter masks work most bridge filter parameters are assigned values and associated "masks." the mask determines (by the process described below) whether the filter will be applied to the packet. The binary bits of the mask will be "anded" (0+0=0, 0+1=0, 1+1=1) to the va...

  • Page 254

    13-8 frx/frm 3. 3 user g uide, rev 04 filter name helps the user identify the filter. The name is not used by the software. Sq is a sequence number to identify the entry. Offset is the number of octets into the frame to the octet that will be checked against the value and mask. Value is used in conj...

  • Page 255

    Configuring bridging 13-9 filter name helps the user identify the filter. The name is not used by the software. Ssap value identifies the source service advertising protocol (sap). Dsap value identifies the destination sap. Filter name helps the user identify the filter. The name is not used by the ...

  • Page 256

    13-10 frx/frm 3. 3 user g uide, rev 04 configuring bridge filter applications bridge filter applications determine how filters will be used at the interface. To review existing applications, press [h] at the filter definitions and applications con- figuration menu (or [a], [a], [e], [f], [h] from th...

  • Page 257

    Configuring bridging 13-11 permit determines whether the traffic defined by the filter "n" entries will be permitted or denied passage across the interface. Filter "n" corresponds to the filter ids in the bridge filter definitions file (described earlier). Table 13-7 bridge filter applications param...

  • Page 258: Configuring Bridge Ports

    13-12 frx/frm 3. 3 user g uide, rev 04 configuring bridge ports a bridge port is an frx/frm lan interface or frame relay port that will operate as a bridge connection to the lan or wan. Press [c] at the lan interfaces configuration menu to display configured bridge ports. Figure 13-4 bridge ports di...

  • Page 259

    Configuring bridging 13-13 figure 13-5 bridge port record example [a],[c],[f],[d] from main menu nod e name=nod e_xyz brid ge port/llc-2 interface configuration * bridge port/llc 2 in terface nu mber: 0 a i nterface typ e ethernet b blocked port flag n c port priority 128 d path cos t 100 e priority...

  • Page 260: Bridge Port Parameters

    13-14 frx/frm 3. 3 user g uide, rev 04 bridge port parameters the following table lists parameters for all interface types. Explanations of some parameters follow the table. 1 determined by line speed of frame relay port. 2 make sure the port is not configured (in the port record) for backup use onl...

  • Page 261

    Configuring bridging 13-15 port priority will become the first octet of the port id field in spanning tree protocol messages. The lower the number, the higher the priority that the interface will be given among other interfaces in the spanning tree. Path cost is the "cost" of transmitting a frame th...

  • Page 262

    13-16 frx/frm 3. 3 user g uide, rev 04 dlci matches the connection with an interface at the remote end of the link. Make sure the dlci is not part of a frame relay dlci backup group. (see chapter 7.) also make sure that the dlci is dif- ferent than the one configured for the physical port in the fra...

  • Page 263: Chapter 14

    Chapter 14 configuring snmp the snmp (simple network management protocol) agent allows a network man- agement station using internet protocol to obtain information from netlink frx4000s, frx6000s, and frame felay modules. Access to the agent is through any ip interface, including frame relay or x.25...

  • Page 264

    14-2 frx/frm 3. 3 user g uide, rev 04 configuring snmp system defaults snmp system defaults identify the local agent to the snmp manager. Press [a] at the snmp configuration menu to display the following screen: figure 14-1 snmp system defaults menu [a],[a],[d],[a] from main menu this information wi...

  • Page 265: System Defaults Parameters

    Configuring snmp 14-3 system defaults parameters 1 although the snmp standard for these fields is 256 characters, an frx/frm file length restriction limits the fields to 250 characters each. System name identifies the local frx/frm to the snmp manager. System location is generally the geographical a...

  • Page 266

    14-4 frx/frm 3. 3 user g uide, rev 04 configuring a community table up to 16 snmp manager devices can gain access to the agent running in an frx or frm. Each manager device has an associated "community" name, configured at that device, that identifies it to agents and other managers. That name is in...

  • Page 267: Community Table Parameters

    Configuring snmp 14-5 community table parameters name is a community name, assigned by a network manager. Access determines what kind of access community members will have to snmp messages. Table 14-2 community table parameter parameter valid values default value name 0–24 characters none access rea...

  • Page 268: Configuring Trap Routing

    14-6 frx/frm 3. 3 user g uide, rev 04 configuring trap routing the "trap" task allows the snmp manager to specify one or more ip addresses (up to sixteen) to which the node's events (alarms) will be sent (as snmp traps). To con- figure trap routing, press [c] at the snmp configuration menu. Figure 1...

  • Page 269: Trap Routing Parameters

    Configuring snmp 14-7 trap routing parameters address is an ip address to which all traps meeting the "enabled" and severity class criteria will be sent. Enabled determines whether or not traps meeting the severity class criterion will be sent to the specified address. Severity determines the lowest...

  • Page 270

    14-8 frx/frm 3. 3 user g uide, rev 04 configuring a model number identification of the hardware chassis is necessary if an omniview network manager device will access the node. Omniview displays a graphic representation of the con- figured chassis. If the node will not be accessed by omniview, confi...

  • Page 271

    Section iii operation.

  • Page 273: Chapter 15

    Chapter 15 introduction to system operation once the database has been configured and the node has been brought on line, little operator intervention is generally necessary. The various functions that can be per- formed from the menus allow the operator to do such things as: ● perform on-line softwa...

  • Page 274

    15-2 frx/frm 3. 3 user g uide, rev 04 figure 15-1 main menu menu items under entry a are described in chapter 2. The following shows where to find the remaining operations among the menus. The chapters where items are described are shown in parentheses. Any item not followed by a chapter/appendix nu...

  • Page 275

    Introduction to syst em operation 15-3 still active connections on the port). H unquiesce a range of ports – unquiesces a specified group of same-type ports. C on-line database operations – (chapter 16) backs up database and/or system files locally or remotely. A back up the current database to a re...

  • Page 276

    15-4 frx/frm 3. 3 user g uide, rev 04 c sdlc pu status – displays a list of configured station addresses for a specified sna port, including current active/inactive states. D bridge status displays a bridge port status display – displays a list of bridge ports, including type, active status, bridge ...

  • Page 277: Chapter 16

    Chapter 16 on-line operations numerous functions can be performed without disrupting normal operation of an frx/frm; for example: ● taking remote control of another frx/frm ● backing up, restoring, and transferring files ● enabling/disabling ports or sna pus ● running tests the remainder of this cha...

  • Page 278: On-Line Node Operations

    16-2 frx/frm 3. 3 user g uide, rev 04 on-line node operations remote control remote control allows an operator to control a remote frx/frm via: ● a connection through a network into a physical or logical (via frame relay) x.25 port on the node to be controlled, or ● an async terminal connected to an...

  • Page 279

    On-line operat ions 16-3 rebooting the remote node before rebooting, notify all users of this node, since all connec- tions on all ports will be cleared. To reboot a node under remote control, follow this procedure at the controlling node: 1. Press [f10] . 2. When asked: remote reboot the node? , pr...

  • Page 280: Remote File Transfer

    16-4 frx/frm 3. 3 user g uide, rev 04 exiting remote control press [,] (comma) to exit remote control. When asked: stop remote control? , press [y] . Node name="nn" (where "nn" is the node name configured in node defaults) will be displayed in the upper right hand corner at the remote node, meaning ...

  • Page 281: Remote Software Update

    On-line operat ions 16-5 remote software update this operation allows an operator to send a complete software update from one frx4000 to another, from one frx6000 to another, or between an frx6000 and an frm. The file update.Txt contains a list of the files that will be transferred. Before an update...

  • Page 282: Frx4000 Local File Backup

    16-6 frx/frm 3. 3 user g uide, rev 04 and receiving nodes are incompatible, the transfer will not occur, and an error message will be displayed. If this happens, contact your service representative. 2. The remote node will check to make sure there is enough disk space to accept the file; if not, the...

  • Page 283

    On-line operat ions 16-7 6. After the file has been received on the pc, the on-line node operations menu will be displayed. If you want to back up another file, press [d] ; otherwise, make another selection or press [f3] to exit the menu. Table 16-1 frx4000 database files file name description x25re...

  • Page 284

    16-8 frx/frm 3. 3 user g uide, rev 04 frx4000 local file restore this operation applies only to an frx4000 with a pc attached to the console port. The pc must be running procomm plus with zmodem. The procedure was tested using procomm plus 2.1 for windows, but other ver- sions containing zmodem shou...

  • Page 285: On-Line Port Operations

    On-line operat ions 16-9 on-line port operations press [b] at the operations menu to display the on-line port operations menu: figure 16-1 on-line port operations menu [b],[b] from main menu disabling and enabling ports these operations disable or enable a single port or a sequential range of same-t...

  • Page 286

    16-10 frx/frm 3. 3 user g uide, rev 04 a disabled port's state is reported as link_disabled on status displays, and the port can neither send nor receive packets. Quiescing and unquiescing ports quiesce operations allow you to cause a single port or a sequential range of same-type ports (e.G., all a...

  • Page 287: On-Line Database Operations

    On-line operat ions 16-11 on-line database operations press [c] at the operations menu (or [b], [c] from the main menu) to display a list of backup and restore operations. The list will differ among frx/frm devices. Frx4000 options on an frx4000 are: a back up the current database to a remote frx600...

  • Page 288: Frx6000

    16-12 frx/frm 3. 3 user g uide, rev 04 this procedure was tested using procomm plus 2.1 for windows, but other versions containing zmodem should also work. Frx6000 options on an frx6000 are: a back up the current database to a remote frx6000 b restore the backed-up database to a remote frx6000 c res...

  • Page 289: Frame Relay Module

    On-line operat ions 16-13 frame relay module options on an frm are: a back up the current database to a remote frm b restore the backed-up database to a remote frm c restore the backed-up database to a remote frx4000 d back up the current database to a local directory e restore the database to a loc...

  • Page 290

    16-14 frx/frm 3. 3 user g uide, rev 04 reloading auxiliary console initialization this operation reloads the terminal settings defined for an async terminal connected to the console port on an frx4000 or the com1 port on an frx6000 or frm. Press [e] at the operations menu (or [b], [e] from the main ...

  • Page 291: Ip Ping Connectivity Test

    On-line operat ions 16-15 ip ping connectivity test the ip ping function sends packets to an ip host to determine whether the host is reachable. Press [f] at the operations menu to display the following: figure 16-2 ip ping connectivity test menu [b],[f] from main menu to begin the test: 1. Press [a...

  • Page 292

    16-16 frx/frm 3. 3 user g uide, rev 04 on-line sdlc pu operations press [g] at the operations menu to display the following: figure 16-3 on-line sdlc pu operations menu [b],[g] from main menu these operations disable or enable the link station connection between the node and a pu or a range of pus (...

  • Page 293: Frx4000 Csu/dsu Tests

    On-line operat ions 16-17 frx4000 csu/dsu tests to test the csu/dsu port on an frx4000, the port must first be disabled. If nec- essary, press [a] at the operations menu (or [b], [a] from the main menu) to disable the port. To run a csu/dsu test, press [i] at the operations menu, then press the lett...

  • Page 294

    16-18 frx/frm 3. 3 user g uide, rev 04 initiating frame relay backup switchover/switchback frame relay backup dlcis can be configured (as described in chapter 6) to automat- ically become operational a set time after failure of a primary dlci, and to switch back to the primary a set time after the p...

  • Page 295: Chapter 17

    Chapter 17 status and statistics displays frx4000, frx6000, and the frame relay module provide several displays that can help monitor and analyze performance and operational status..

  • Page 296: Displaying Node Status

    17-2 frx/frm 3. 3 user g uide, rev 04 displaying node status press [a] at the status displays menu to display the overall performance of this node, as well as most of the data shown on the port status display (described on page 17-3). Figure 17-1 node status display [c],[a] from main menu informatio...

  • Page 297: Displaying Port Status

    St atus and statistics displays 17-3 displaying port status press [b] at the status displays menu to display the status of all lines on this node: figure 17-2 port status display [c],[b] from main menu if the node has more than 32 ports, some of them will be displayed on sub- sequent "pages" (up to ...

  • Page 298

    17-4 frx/frm 3. 3 user g uide, rev 04 configured the port is configured in the database, but the lp is not installed. Dial ready the x.25 dial port is ready to transmit or receive calls. Quiesced the port has been quiesced (described on page 16-10). Failed some modem controls are not present, and th...

  • Page 299

    St atus and statistics displays 17-5 displaying virtual connections to display all physical and logical connections on a physical port, press [c] at the status displays menu and, when prompted, enter the lp and physical port numbers. The display will differ depending on whether or not the port is a ...

  • Page 300

    17-6 frx/frm 3. 3 user g uide, rev 04 a frame relay dlci displaying this state might have a backup that is now in operation. To determine this, press [f3] to return to the status displays menu, then press [f] , [e] , [b] ( display states for all primary dlcis on a port ), and enter the port number. ...

  • Page 301

    St atus and statistics displays 17-7 information in this display seq is a sequence number used to identify the connection. I is the logical interface: p = pvc, s = svc d is the direction of the connection related to the port: i = incoming, o = outgoing. Lcn is the logical channel number. State : dat...

  • Page 302: Displaying Port Signals

    17-8 frx/frm 3. 3 user g uide, rev 04 displaying port signals this display lists basic configuration and line status for all serial ports on a specified lp, as well as signal states (on/off) at the physical interfaces. Press [d] at the status displays menu and, when prompted, enter an lp number: 0–7...

  • Page 303

    St atus and statistics displays 17-9 td(2) , etc. The signal names (with connector pin numbers in parentheses) are listed as on , off , or unk (unknown: non-functional, unused, or in transition between states). For different physical interfaces, the names remain the same, but the numbers change. If ...

  • Page 304: Monitoring A Line

    17-10 frx/frm 3. 3 user g uide, rev 04 monitoring a line the line monitor displays the control data and information data of traffic passing through a port. Running the line monitor on a frame relay port will degrade per- formance on the port. Press [e] at the status displays menu and, when prompted,...

  • Page 305

    St atus and statistics displays 17-11 [f3] exits line monitor mode. The following figure shows an example of a display: figure 17-6 line monitor display [c],[e] from main menu on each line (see ccitt recommendation x.25): ● the leftmost field shows the time, to hundredths of a second.The next field ...

  • Page 306: Rip Table

    17-12 frx/frm 3. 3 user g uide, rev 04 displaying ipx rip and sap tables rip table to display the contents of ipx rip table, press [a] at the protocol status displays menu (or [c], [f], [a] from the main menu). Each entry will contain the following: network is the ipx address of the network containi...

  • Page 307

    St atus and statistics displays 17-13 12-16) will not age ( dna = true ). Interfaces with 0 specified in their ipx interface records for the sap age timer will also be true . All others will be false . Intf (interface) is the time (in 55-millisecond units) that it will normally take a packet to reac...

  • Page 308: Displaying Sdlc Pu Status

    17-14 frx/frm 3. 3 user g uide, rev 04 displaying sdlc pu status to display the status of all pus on an sna port, press [c] at the protocol status dis- plays menu. When prompted, enter the lp and port numbers. Figure 17-7 sdlc pu status display [c], [f],[c] from main menu possible states are: active...

  • Page 309: Displaying Bridge Status

    St atus and statistics displays 17-15 displaying bridge status bridge port status press [a] at the bridge status displays menu to display the configurational and oper- ational status of all bridge ports in the node: figure 17-8 bridge port status display [c],[f],[d],[a] from main menu bridge id is i...

  • Page 310

    17-16 frx/frm 3. 3 user g uide, rev 04 information shown on a bridge port status display type/format – identifies the interface type (ethernet, token ring, or frame relay) and (if frame relay) frame format (native llc2, 8025_srb, or 8023_tb, as configured in the port record). Status ( active or inac...

  • Page 311

    St atus and statistics displays 17-17 information shown on a bridge port statistics display type/format identifies the interface type (ethernet, token ring, or frame relay) and (if frame relay) frame format (native llc2, 8025_srb, or 8023_tb, as configured in the port record). Designatedroot is the ...

  • Page 312: Bridge Forwarding Table

    17-18 frx/frm 3. 3 user g uide, rev 04 bridge forwarding table the bridge forwarding table is used to match mac addresses with bridge ports on which to forward frames. If an address is not found in the table, the frame will be for- warded out all bridge ports except those configured for native llc-2...

  • Page 313

    St atus and statistics displays 17-19 possible flags are: static the entry is fixed in the software. Dynamic the entry was added when the address was received. Llc2 the address is used for terminated llc2 traffic. All sna frames (identified by sap multiples of 4) will be handled by llc2, rather than...

  • Page 314

    17-20 frx/frm 3. 3 user g uide, rev 04 displaying frame relay backup status to display operational states of backup and backed-up frame relay dlcis, press [e] at the protocol status displays menu (or [c], [f], [e] from the main menu), then select from the following list and enter (when prompted) the...

  • Page 315

    St atus and statistics displays 17-21 displaying llc2 session status the status of any current llc2 sessions can be displayed by pressing [f] at the pro- tocol status displays menu (or [c], [f], [f] from the main menu). For each session, the following will be identified: ssap sap address of the sour...

  • Page 316

    17-22 frx/frm 3. 3 user g uide, rev 04 displaying the ip routing table to display a list of active ip routes, press [g] at the protocol status displays menu (or [c], [f], [g] from the main menu). The following will be displayed for each existing route: destination destination ip address. Gateway ip ...

  • Page 317

    St atus and statistics displays 17-23 displaying the ip arp table to display a list of active arp (address resolution protocol) table entries, press [h] at the protocol status displays menu (or [c], [f], [h] from the main menu). The fol- lowing will be displayed for each entry: ip address address of...

  • Page 318: Displaying Ip Interfaces

    17-24 frx/frm 3. 3 user g uide, rev 04 displaying ip interfaces to display a list of active ip interfaces, press [i] at the protocol status displays menu (or [c], [f], [i] from the main menu). The following will be displayed for each existing interface: name identifier used in the ip route display. ...

  • Page 319: Displaying Lp Statistics

    St atus and statistics displays 17-25 lp/port/frame statistics displays displaying lp statistics although an frx4000 has no lps, lp functionality exists in the device. Figure 17-10 lp statistics display [e],[b] from main menu pressing [f2] on an frx6000 display will show the next-higher-numbered lp ...

  • Page 320: Displaying Port Statistics

    17-26 frx/frm 3. 3 user g uide, rev 04 retransmitted frames is the number of frames retransmitted by the lp per second per sec (*10) over the five-second reporting interval, multiplied by 10. If the value is consistently greater than zero and there are no other problems, you should increase the t1 t...

  • Page 321

    St atus and statistics displays 17-27 logical rejects/sec (*10) is the sum of rejects and frame rejects received on the port per second over the five-second reporting interval, multiplied by 10. A value consistently greater than zero indicates line problems. Transmit error ratio is the ratio of retr...

  • Page 322

    17-28 frx/frm 3. 3 user g uide, rev 04 information in a frame relay display de/sec (*10) is the number of frames transmitted/received with the de (discard eligibility) bit set per second over the five-second reporting interval, multiplied by 10. Fecn/sec (*10) is the number of frames transmitted/rec...

  • Page 323

    St atus and statistics displays 17-29 configuring lp and port statistics thresholds for each lp and port statistic, you can specify a threshold that, when crossed, causes an alarm to be sent to the collecting node. Press [a] at the statistics menu. When prompted, enter: ● statistic level : l for lp ...

  • Page 324: Ip Statistics Displays

    17-30 frx/frm 3. 3 user g uide, rev 04 ip statistics displays displaying ip statistics ip statistics track traffic of ip datagrams through a node. Press [c] at the statistics menu and, when prompted, enter a report interval : 5–65535 (seconds). (default is 5 .) this is the frequency with which the s...

  • Page 325

    St atus and statistics displays 17-31 unkwn protocol is the number of datagrams received using an unknown or unsup- ported protocol. Pkt too small is the number of datagrams received that were discarded because the ip header would not fit into a single buffer. Pkts delivered is the number of datagra...

  • Page 326: Displaying Icmp Statistics

    17-32 frx/frm 3. 3 user g uide, rev 04 displaying icmp statistics icmp statistics track traffic of internet control message protocol messages through the node. (icmp messages are encapsulated with ip headers and transmitted with the ip traffic.) press [d] at the statistics menu and, when prompted, e...

  • Page 327

    St atus and statistics displays 17-33 responses cnt is the total number of responses from this node to echoes and requests for timestamps, information, and address masks (all described later). Out echo reply is the number of outgoing responses to icmp echo request data- grams, which are sent by othe...

  • Page 328

    17-34 frx/frm 3. 3 user g uide, rev 04 in time rsp is the number of responses received by this node to timestamp requests. Out info req is the number of requests to other entities in the ip path for the ip address of the network to which they are attached. In info req is the number of requests recei...

  • Page 329

    St atus and statistics displays 17-35 displaying ip interface statistics ip interface statistics track ip traffic over the node interface. Press [e] at the statistics menu and, when prompted, enter: ● interface number : 0–128 . ● report interval : 5–65535 . (default is 5 .) the display will be simil...

  • Page 330: Ipx Statistics Displays

    17-36 frx/frm 3. 3 user g uide, rev 04 ipx statistics displays ipx statistics track ipx traffic through a node. Press [f] at the statistics menu and, when prompted, enter: ● interface number : 0–63 . (default is 0 .) ● report interval : 5–65535 . (default is 5 .) figure 17-17 ipx statistics display ...

  • Page 331

    St atus and statistics displays 17-37 rip g_query tx is the number of rip general queries transmitted on the interface. Rip n_query tx is the number of rip nearest queries transmitted on the interface. Rip g_resp tx is the number of rip general responses (responses to general queries) transmitted on...

  • Page 332

    17-38 frx/frm 3. 3 user g uide, rev 04 sap g_resp tx is the number of sap general responses (responses to general queries) transmitted on the interface. Sap n_resp tx is the number of sap nearest responses (responses to nearest queries) transmitted on the interface. Sap pkts rcv is the number of sap...

  • Page 333

    St atus and statistics displays 17-39 wd req pkts rcv is the number of "watchdog," or "keep-alive," requests received from other servers. These are issued periodically to all clients, to determine whether each client is still available. Wd resp pkts rcv is the number of received responses to keep-al...

  • Page 334

    17-40 frx/frm 3. 3 user g uide, rev 04 r-sap ent filter is the number of received sap entries discarded due to a filter. T-sap ent-filter is the number of transmitted sap entries discarded due to a filter. R-rip pkt-filter is the number of received rip packets discarded due to a rip router filter. T...

  • Page 335

    St atus and statistics displays 17-41 lan card statistics displays lan card statistics track traffic over the lan interface. Press [g] at the statistics menu and, when prompted, enter: ● lan card number : 0 on frx4000 or frm, 0–1 on frx6000. (default is 0 .) ● report interval : 5–65535 . (default is...

  • Page 336

    17-42 frx/frm 3. 3 user g uide, rev 04 information in this display packets in/out is the number of packets received/transmitted over the interface. Bytes in/out is the number of bytes received/transmitted over the interface. Multi-cast in/out is the number of packets received/transmitted via a multi...

  • Page 337

    St atus and statistics displays 17-43 frequency errors is the number of frames received with signal frequency problems. Frm with aborts is the number of frames that were aborted in mid transmission. Act mon regen is the number of times the active monitor is lost and regenerated. No return frms is th...

  • Page 338

    17-44 frx/frm 3. 3 user g uide, rev 04 frame relay utilization statistics frame relay utilization statistics track traffic over a frame relay dlci, and monitor the usage by each configured group on that dlci. Press [h] at the statistics menu and, when prompted, enter: ● lp : 0 on frx4000 or frm, 0–7...

  • Page 339

    St atus and statistics displays 17-45 bag bandwidth allocation group. Conf/act percentage configured and actual percentages of bandwidth used by traffic assigned to each group. Actual (bits/sec) current bandwidth usage by traffic assigned to each group..

  • Page 340

    17-46 frx/frm 3. 3 user g uide, rev 04.

  • Page 341: Chapter 18

    Chapter 18 system events netlink frx/frm alarm, or event, messages can be displayed locally (see “dis- playing events” on page 18-3), as well as sent to an async terminal, a serial or parallel printer, another node, or any other device capable of interpreting event messages. Events parameters are se...

  • Page 342: Alarm Buffer

    18-2 frx/frm 3. 3 user g uide, rev 04 the following shows an example of a two-node event routing configuration. Figure 18-1 event reporting configuration example alarm buffer each node has a buffer where events are stored while waiting for transmission. When a buffer reaches the percentage of full c...

  • Page 343: Event Generation

    Syst em events 18-3 event generation as soon as a message-generating event occurs, a call request is automatically sent to the alarm output id . (the event is stored in the originating node's buffer until the event connection is activated.) all events are transmitted in raw data format to the collec...

  • Page 344

    18-4 frx/frm 3. 3 user g uide, rev 04 severity levels for snmp trap routing each event is assigned a severity level, which is used in snmp trap routing (described on page 14-6) to determine which level(s) will be sent to an snmp manager. There are four levels of severity: level 1 = serious fault. Th...

  • Page 345: Event Messages

    Syst em events 18-5 event messages a list of event messages follows, with each message's meaning and any action to be taken. The list is modified as necessary to include additional events. As shown in the example under “displaying events" (on page 18-3), each message is preceded by the lp (frx6000, ...

  • Page 346

    18-6 frx/frm 3. 3 user g uide, rev 04 305. Lp msg queued exceeded t:“n” c: “n” severity: 4 meaning: the lp statistic number of queued messages has exceeded the threshold ( t:“n” ) that was set by the user. ( c:“n” is the current value.) action: if this happens frequently, you may need to reroute som...

  • Page 347

    Syst em events 18-7 311. Rcv frm/sec exceeded t:“n” c:“n” severity: 4 meaning: the port statistic received frames/sec (*100) has exceeded the threshold ( t:“n” ) that was set by the user. ( c:“n” is the current value.) action: if this happens frequently, you may need to reroute some traffic. 312. Tr...

  • Page 348

    18-8 frx/frm 3. 3 user g uide, rev 04 317. Rcv err ratio exceeded t:“n” c:“n” severity: 4 meaning: the port statistic receive error ratio has exceeded the threshold ( t:“n” ) that was set by the user. ( c:“n” is the current value.) action: if this happens frequently, check the line for noise, and ch...

  • Page 349

    Syst em events 18-9 400. Link enabled severity: 2 meaning: the port has been enabled from the on-line port operations menu. Action: none. 401. Link disabled severity: 2 meaning: the port has been disabled from the on-line port operations menu. Action: none. 402. Link disconnected severity: 2 meaning...

  • Page 350

    18-10 frx/frm 3. 3 user g uide, rev 04 406. Operational severity: 2 meaning: for all ports except those noted below, this means that the link is up. For sna tpad, this means that the xid exchange has been per- formed, and the xid data received in the response frame matches the xid data configured fo...

  • Page 351

    Syst em events 18-11 meaning: a reset confirmation was received. Action: none. 413. Pad link failed severity: 2 meaning: self-explanatory. Action: check the async pad port and its cables for proper operation and secure connection. 414. Beginning of congestion severity: 4 meaning: the level of maximu...

  • Page 352

    18-12 frx/frm 3. 3 user g uide, rev 04 action: none; however, all users of this port should be made aware of the disable. 432. Node under remote control severity: 4 meaning: self-explanatory. Action: none. 433. Remote control released severity: 4 meaning: self-explanatory. Action: none. 434. Remote ...

  • Page 353

    Syst em events 18-13 439. Database error, access restricted severity: 1 meaning: the database is inconsistent with what the software expects. Action: contact cabletron systems technical support. (see page 18-5.) 440. Abrev addr file upd:abvsub.Dat severity: 4 meaning: the abbreviated address file ha...

  • Page 354

    18-14 frx/frm 3. 3 user g uide, rev 04 448. Rmt subscriber file upd:rsnsvc.Dat severity: 4 meaning: the remote subscriber file has been updated. Action: none. 449. Subscriber file upd:svcsub.Dat severity: 4 meaning: the svc subscriber file has been updated. Action: none. 450. Statistic def file upd:...

  • Page 355

    Syst em events 18-15 456. Operator logged into node severity: 4 meaning: an async terminal operator has logged into the node via an async pad port. Action: none. 457. Operator logged out of node severity: 4 meaning: the async terminal operator has logged out of the node via the async pad port. Actio...

  • Page 356

    18-16 frx/frm 3. 3 user g uide, rev 04 464. Lp buf usage under threshold severity: 4 meaning: the situation that caused event 304 has ended. Action: none. 465. Lp msg queued under threshold severity: 4 meaning: the situation that caused event 305 has ended. Action: none. 466. Lp rcv frm/sec under th...

  • Page 357

    Syst em events 18-17 472. Tran frm/sec under threshold severity: 4 meaning: the situation that caused event 312 has ended. Action: none. 473. Retran frm/sec under threshold severity: 4 meaning: the situation that caused event 313 has ended. Action: none. 474. Fcs rej/sec under threshold severity: 4 ...

  • Page 358

    18-18 frx/frm 3. 3 user g uide, rev 04 480. Delete failed - nonexistent interface “n” severity: 4 meaning: an ip interface database record was created for a non-existent interface. Someone then deleted the record (using [f4] ), which caused this message to be generated. 481. No mem avail processing ...

  • Page 359

    Syst em events 18-19 action: contact cabletron systems technical support. (see page 18-5.) 489. Route with destination “n,” mask “n,” router “n” deleted successfully severity: 4 meaning: self-explanatory. 490. Error adding route with destination “n,” mask “n,” router “n” severity: 3 meaning: self-ex...

  • Page 360

    18-20 frx/frm 3. 3 user g uide, rev 04 505. Link:invalid msg fc “n” - bpad severity: 3 meaning: an invalid message has been received, disabling the port. Action: take the same action as for message 500. 513. Bsci:invalid control block severity: 3 meaning: an error has occured, and has disabled the p...

  • Page 361

    Syst em events 18-21 action: take the same action as for message 500. 520. Bsci:invalid crc operations severity: 3 meaning: an invalid operation has occured, and has disabled the port. Action: take the same action as for message 500. 521. Bsci:invalid queue operations severity: 3 meaning: an invalid...

  • Page 362

    18-22 frx/frm 3. 3 user g uide, rev 04 meaning: the dte and dce exchange messages regularly so that each knows the other is running and ready. If one end does not respond, this event message is sent and the link goes down. Action: check the equipment to see what caused the failure to respond. 533. E...

  • Page 363

    Syst em events 18-23 540. Dlci “n” not configured severity: 3 meaning: self-explanatory. Action: configure the dlci in the port's database record. 541. Dlci “n” frame relay header invalid severity: 3 meaning: the header contained an invalid dlci. Action: check the configuration record for the port. ...

  • Page 364

    18-24 frx/frm 3. 3 user g uide, rev 04 561. Llc interface file upd:llc2ipar.Dat severity: 4 meaning: the llc2 interface file has been updated. Action: none. 562. Llc host file upd:llc2hpar.Dat severity: 4 meaning: the llc2 host file has been updated. Action: none. 563. Llc lan card file upd:lanpar.D...

  • Page 365

    Syst em events 18-25 705. Sdlc stn rcvd frmr, ifld invalid severity: 2 meaning: the remote device received an unpermitted i frame and responded with a frame reject. Action: none. 706. Sdlc stn rcvd frmr, nr invalid severity: 2 meaning: the remote device received a frame with an invalid n(r) and resp...

  • Page 366

    18-26 frx/frm 3. 3 user g uide, rev 04 meaning: the timer defined by the parameters no response poll period and maximum retransmissions in the sna port record (see chapter 8) has expired. Action: check the pu to make sure it is operational. 713. S dlc xid retries exhausted severity: 2 meaning: the r...

  • Page 367

    Syst em events 18-27 722. Sdlc no external clock severity: 2 meaning: the necessary clock is not being provided. Action: check the modem to make sure it is operational. 736. Sdlc llc/2 remote link stn lost severity: 2 meaning: the remote station is not responding. Either the inactivity timer ( ti ) ...

  • Page 368

    18-28 frx/frm 3. 3 user g uide, rev 04 742. Llc/2 frmr rcvd, ifld too long severity: 2 meaning: the remote device received an i frame that was too long, and returned a frame reject. Action: none. 743. Llc/2 frmr rcvd, invalid command severity: 2 meaning: the remote device received an invalid command...

  • Page 369

    Syst em events 18-29 meaning: self-explanatory. The line will be shut down and re-establishment will be re-tried one every minute. Action: none. 761. Sdlc transmit link error severity: 2 meaning: self-explanatory. The line will be shut down and re-establishment will be re-tried later. Action: none. ...

  • Page 371

    Section iv appendices.

  • Page 373: Appendix A

    Appendix a subscriber addressing connections between subscribers are made over either switched virtual circuits (svcs) or permanent virtual circuits (pvcs). An svc is established by successful transmission and acceptance between subscribers of a call request, and broken by successful transmission an...

  • Page 374

    A-2 frx/frm 3. 3 user g uide, rev 04 the following figure shows an example of wildcard addressing. Figure a-1 wildcard addressing example this configuration requires port and subscriber id records in node 1 for: ● subscriber 00100 on lp 0, port 1 ● subscriber 123* on lp 1, port 3 in node 2, lp, port...

  • Page 375: Appendix B

    Appendix b hunt group example here is an example of how the hunt group function works, using the algorithm least lcn with thruput . The routing path process will calculate a loading factor based on the number of lcns in use and the line speeds for each call request received. The method is proprietar...

  • Page 376

    B-2 frx/frm 3. 3 user g uide, rev 04 1,1 failed 1,2 2 if the database is changed and lines are added or deleted from the routing path config- uration, or if lines become operational or not operational, the next call request will trigger new u values based on the lines available at the moment. As ope...

  • Page 377: Appendix C

    Appendix c async terminal operations before establishing an end-to-end link, an async terminal must make a connection to the async pad, as follows: 1. Once the frx/frm, 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...

  • Page 378: Async Terminal Commands

    C-2 frx/frm 3. 3 user g uide, rev 04 async terminal commands the following commands can be entered in command mode. (for a list of commands, type help [enter] .) stat – get connection status. Clr – clear connection. Par? N1,n2,n3 – reads value of 1 or more async pad profile parameters ( n1 = 1st par...

  • Page 379

    Async terminal o perations c-3 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 ...

  • Page 380: Async Pad Service Signals

    C-4 frx/frm 3. 3 user g uide, rev 04 async pad service signals transmission of pad service signals is determined by async pad profile parameter 6. * (asterisk) – is normally the pad prompt character. “nnnnn” com – means that a vitual circuit has been established with a subscriber whose id is “nnnnn....

  • Page 381

    Async terminal o perations c-5 overrun error – indicates that the pad is unable to cope with the rate at which 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. Page – indicates that...

  • Page 382

    C-6 frx/frm 3. 3 user g uide, rev 04 error codes sent to async pad port clearing causes occ number busy nc network congestion inv invalid facility na access barred err local procedure error rpe remote procedure error np not obtainable der out of order pad invitation to clear dte dte originated reset...

  • Page 383: Appendix D

    Appendix d cause and diagnostic codes.

  • Page 384: Cause Codes

    D-2 frx/frm 3. 3 user g uide, rev 04 cause codes clearing causes the clearing cause recorded in a call packet provides a high-level indication of why the call was cleared and where the error occurred (e.G., error by the source user, or internal network error). For example, when the diagnostic code i...

  • Page 385: Restart Causes

    Cause and diagnost ic codes d-3 11 17 91 145 incompatible destination 1d 29 9d 157 network out of order (pvc only) restart causes when a port is restarted, all active svcs and pvcs through the port are cleared. The restart cause sent in a restart packet provides a high-level indication of why the po...

  • Page 386: Diagnostic Codes

    D-4 frx/frm 3. 3 user g uide, rev 04 diagnostic codes x.25 codes these diagnostic codes are generated by the x.25 network in clear, reset, and restart indication packets, as well as registration confirmation and diagnostic packets: hex. Dec. Description 00 00 no additional information 01 01 invalid ...

  • Page 387: Sna Codes

    Cause and diagnost ic codes d-5 hex. Dec. Description 40 64 call set up, call clearing or registration problem 41 65 facility/registration code not allowed 42 66 facility parameter not allowed 43 67 invalid called address 44 68 invalid calling address 45 69 invalid facilty/registration length 46 70 ...

  • Page 388: Frx/frm-Specific Codes

    D-6 frx/frm 3. 3 user g uide, rev 04 frx/frm-specific codes hex. Dec. Description 81 129 call cleared because of call looping 82 130 call cleared because port is quiesced f4 244 connection rejected (transient condition).

  • Page 389: Appendix E

    Appendix e netview management the netlink frx4000, frx6000, and frame relay module support a netview service point function, which allows a node to be configured and managed from a netview host. Netview support provides management access to downstream sdlc devices, and allows diagnosing problems and...

  • Page 390: Local Netview Access

    E-2 frx/frm 3. 3 user g uide, rev 04 local netview access the frx and frm support a local netview access function that allows the node operator to send commands from the node to lines and pus. This function is only between the node and lines/pus—the commands and responses are not transmitted to netv...

  • Page 391: Supported Commands

    Net view management e-3 supported commands the syntax of a runcmd from netview is generally as follows: runcmp sp=olxpu, appl=nvoperid, command where: olxpu is the vtam pu name of the frx/frm (netview sees the frx/frm as a pu), nvoperid is the id of the netview operator issuing the command, and comm...

  • Page 393

    Net view management e-5 corresponding parameter keyword(s) in frx/frm valid values nodata or pause no data poll period 0–125 (ms) noresp or activeto no resp poll period 40–9999 (ms) genclck or clocking generate clock y/n rcvclock receive clock (tt) from dte y/n istatus blocked port flag y/n nrzi nrz...

  • Page 395: Appendix F

    Appendix f ascii character table ascii decimal octal hex ctrl key character value value value combination nul 000 000 00 [ctrl] [space] soh 001 001 01 [ctrl] [a] stx 002 002 02 [ctrl] [b] etx 003 003 03 [ctrl] [c] eot 004 004 04 [ctrl] [d] enq 005 005 05 [ctrl] [e] ack 006 006 06 [ctrl] [f] bel 007 ...

  • Page 396

    F-2 frx/frm 3. 3 user g uide, rev 04 ascii decimal octal hex character value value value , (comma) 044 054 2c - (hyphen) 045 055 2d . (period) 046 056 2e / 047 057 2f 0 048 060 30 1 049 061 31 2 050 062 32 3 051 063 33 4 052 064 34 5 053 065 35 6 054 066 36 7 055 067 37 8 056 070 38 9 057 071 39 : 0...

  • Page 397

    Ascii character table f-3 ascii decimal octal hex character value value value g 103 147 67 h 104 150 68 i 105 151 69 j 106 152 6a k 107 153 6b l 108 154 6c m 109 155 6d n 110 156 6e o 111 157 6f p 112 160 70 q 113 161 71 r 114 162 72 s 115 163 73 t 116 164 74 u 117 165 75 v 118 166 76 w 119 167 77 x...

  • Page 399: Appendix G

    Appendix g menu structure items farthest to the left and underlined (e.G., a – configuration ) are the entries on the main menu. A configuration a configure node a configure password b configure time and date c configure node defaults d configure snmp parameters a configure system defaults b configu...

  • Page 400

    G-2 frx/frm 3. 3 user g uide, rev 04 f configure lan interfaces a review ip interfaces b configure ip interfaces c review bridge ports/llc2 interfaces d configure bridge ports/llc2 interfaces e review ipx interfaces f configure ipx interfaces g configure bsc devices a review bsc device configuration...

  • Page 401

    Menu structure g -3 i csu/dsu tests a self test b pattern generation test j frame relay backup operations a initiate switching primary dlci over to its backup b initiate switching dlci back to the primary c status displays a node status b port status c virtual connections d port signals e line monit...

  • Page 402

    G-4 frx/frm 3. 3 user g uide, rev 04.

  • Page 403: Glossary

    Glossary 802.3 is an ieee standard for lans, that defines the physical layer as coax or unshielded twisted pair and the mac (medium access control) layer as csma/cd (carrier-sense multiple access with collision detection). 802.5 is an ieee standard for lans, that defines the physical layer as shield...

  • Page 404

    Glossary-2 frx/frm 3. 3 user g uide, rev 04 b banner is the display area at the top of a screen that generally features product name, revision, etc. Bpdu stands for “bridge protocol data unit,” also called a “hello” message. Bridges peri- odically send bpdus to update each other on their status. Bps...

  • Page 405

    Glossary glossary-3 d database contains the files that define network configuration, subscribers, alarms and statistics. Datagram is the basic unit of information passed across the internet. It is the ip equivalent of a packet. Dce stands for “data circuit-terminating equipment,” which provides the ...

  • Page 406

    Glossary-4 frx/frm 3. 3 user g uide, rev 04 event is a change in status in software or hardware operation (e.G., configuration, function, operating state, performance, etc.), that is reported to automatic and specified destina- tions within the network the frx/frm is on. This term is synonymous with...

  • Page 407

    Glossary glossary-5 i icmp stands for “internet control message protocol,” which handles ip error and control messages. Gateways and hosts use icmp to report problems concerning datagrams back to the source. Internet is an interconnected group of packet-switching networks, joined by gateways sup- po...

  • Page 408

    Glossary-6 frx/frm 3. 3 user g uide, rev 04 llc stands for “logical link control,” which is the third layer in the three-layer iso lan protocol hierarchy. (the first two layers are physical and mac; mac is described in this glossary.) llc is responsible for addressing and data link control. Llc2 is ...

  • Page 409

    Glossary glossary-7 p packet is a group of data and control signals transmitted as a composite whole across a packet-switching network. Packet switching is the breaking up of data into smaller pieces and the transmission of these pieces over a network via x.25. Pad stands for “packet assembler/disas...

  • Page 410

    Glossary-8 frx/frm 3. 3 user g uide, rev 04 r rip stands for “routing information protocol,” which provides for dynamic routing in a tcp/ip implementation. Root is the bridge determined (by implementation of the spanning tree algorithm) to be the lowest-cost path between points in a bridged link. Ro...

  • Page 411

    Glossary glossary-9 sna stands for ibm's “systems network architecture.” spanning tree algorithm is a method employed in bridging that avoids closed loops in the data path by deter- mining the bridge with the lowest “path cost,” which is the cost of transmitting a frame onto the lan. Ssap stands for...

  • Page 412

    Glossary-10 frx/frm 3. 3 user g uide, rev 04 x x.3 is a ccitt recommendation that defines the service provided by an asynchronous pad to connect a character-mode terminal to an x.25 network. X.25 is a ccitt recommendation that specifies the dte/dce interface for “packet mode” operation in public dat...

  • Page 413: Index

    Index index-1 # of beginning sync char .......................................... 9-7 # of beginning sync chars ....................................... 9-13 # of trailing pad characters ....................................... 9-7 # of trailing pad chars ............................................ 9...

  • Page 414

    Index-2 frx/frm 3. 3 user g uide, rev 04 clearing causes.......................................................... D-2 async................................................................... C-6 collecting node.......................................................... 3-7 collecting node id ..........

  • Page 415

    Index index-3 event collection, configuring ................................... 18-1 event generation ....................................................... 18-3 event messages ........................................................ 18-5 events ........................................................

  • Page 416

    Index-4 frx/frm 3. 3 user g uide, rev 04 internal network ...................................................... 12-2 intervening networks ............................................. 12-18 ip addressing ............................................................ 11-1 ip arp table, displaying .......

  • Page 417

    Index index-5 maxin ....................................................................... 8-26 menu operations ....................................................... 1-15 menu structure........................................................... G-1 metric count ......................................

  • Page 418

    Index-6 frx/frm 3. 3 user g uide, rev 04 printer (bsc interactive devices)............................ 9-21 priority . 3-11, 8-11, 8-15, 8-25, 8-30, 9-18, 10-17, 13-15 profile description ................................................... 10-3 profile name .............................................

  • Page 419

    Index index-7 sna port, configuring ................................................ 8-2 sna type................................................................... 8-7 sna, configuring ....................................................... 8-1 snmp, configuring .......................................

  • Page 420

    Index-8 frx/frm 3. 3 user g uide, rev 04 x x.25 address translation templates........................... 7-17 x.25, configuring ....................................................... 7-1 x.3 line speed ....................................................... 10-11 z zmodem .............................