Page 1: User Guide
Frame Relay Access Products 4000 4000 6000 6000 Frame Relay Module For MMAC-Plus User Guide For Release 3.3.1 The Com plete Network ing Solution 09-41-06-109-04...
Page 3 Cabletron Systems reserves the right to make changes in specifications and other information contained in this document without prior notice. The reader should in all cases consult Cabletron Systems to determine whether any such changes have been made. The hardware, firmware, and/or software described in this manual is subject to change without notice.
Page 4: About This Manual
This digital apparatus does not exceed the Class A limits for radio noise emissions from digital apparatus set out in the Radio Interference Regulations of the Canadian Department of Com- munications. Le présent appareil numérique n’émet pas de bruits radioélectriques dépassant les limites applicables aux appareils numériques de la class A prescrites dans le Règlement sur le brouillage radioélectrique édicté...
Page 5: Table Of Contents
Table of Contents Section I Introduction 1 Chapter 1 Introduction to Netlink Frame Relay Access Devices Hardware Overview ... 1-6 Introduction to Menu Operations ... 1-15 Stopping Operation ... 1-20 Section II Configuration Chapter 2 Introduction to Database Configuration Database Setup Recommendations ... 2-2 Producing a Configuration Report ...
Page 6 Chapter 6 Configuring Frame Relay Configuring Bandwidth Allocation Groups... 6-6 Configuring Frame Relay Ports ... 6-9 Configuring a Logical Port... 6-21 Configuring Subscriber Addresses ... 6-29 Configuring Frame Relay PVCs Across the Node... 6-32 Configuring Frame Relay Backup Groups ... 6-35 Chapter 7 Configuring X.25 Configuring X.25 Ports...
Page 7 Configuring Async PAD Login Parameters ... 10-7 Login Parameters ... 10-8 Configuring Async Port Records ... 10-9 Async PAD Port Parameters ... 10-10 Configuring Subscriber Addresses ... 10-15 Subscriber Parameters ... 10-16 Configuring Abbreviated Addresses... 10-18 Configuring Async PVCs ... 10-19 Async PVC Parameters ...
Page 8 Section III Operation Chapter 15 Introduction to System Operation Chapter 16 On-line Operations On-Line Node Operations... 16-2 On-Line Port Operations... 16-9 On-Line Database Operations... 16-11 Reloading Auxiliary Console Initialization ... 16-14 IP Ping Connectivity Test... 16-15 On-Line SDLC PU Operations... 16-16 FRX4000 CSU/DSU Tests ...
Page 9 Frame Relay Utilization Statistics ... 17-44 Chapter 18 System Events Event Messages... 18-5 Section IV Appendices Appendix A Subscriber Addressing Appendix B Hunt Group Example Appendix C Async Terminal Operations Async Terminal Commands ... C-2 Placing a Call from an Async Terminal... C-3 Async PAD Service Signals...C-4 Error Codes Sent to Async PAD Port ...
Page 10 List of Figures 6-10 Network Example... 1-1 Ports on the Netlink FRX4000 ... 1-6 FRX6000 RLP, LICs, and Cables ... 1-9 LAN Card Interfaces... 1-10 FRX6000 Chassis... 1-10 Frame Relay Module... 1-12 Frame Relay Module with I/O Boxes and Cabling ... 1-13 Port Status Display ...
Page 11 7-10 X.25-to-X.25 PVC Screen ... 7-23 SNA Port Screen 1 ... 8-2 SDLC PU Subscriber Parameters Screen ... 8-3 Typical SVC Subscriber Screen ... 8-13 LLC2 Examples ... 8-18 LLC2 Defaults Configuration Screen... 8-19 LLC2 Originated Host Configuration Screen... 8-20 LLC2 Terminated Host Configuration Screen ...
Page 12 16-2 16-3 17-1 17-2 17-3 17-4 17-5 17-6 17-7 17-8 17-9 17-10 LP Statistics Display... 17-25 17-11 Port Statistics Display... 17-26 17-12 Frame-level Statistics Display ... 17-27 17-13 Port Statistics Configuration Menu ... 17-29 17-14 IP Statistics Display... 17-30 17-15 ICMP Statistics Display... 17-32 17-16 IP Interface Statistics Display...
Page 13 Logical Port Parameters... 6-22 Logical Port CUG Parameters ... 6-23 Subscriber Parameters ... 6-30 Frame Relay PVC Parameters ... 6-33 Frame Relay Backup Group Parameters... 6-35 X.25 Port Parameters ... 7-3 X.25 Port CUG Parameters... 7-10 X.25 Port Dial Parameters ... 7-12 Subscriber Parameters ...
Page 14 13-2 13-3 13-4 13-5 13-6 13-7 13-8 14-1 14-2 14-3 16-1 Bridge Generic Filter Parameters... 13-7 Bridge MAC Filter Parameters... 13-8 Bridge SAP Filter Parameters... 13-8 Bridge Protocol Filter Parameters ... 13-9 Bridge NetBIOS Filter Parameters... 13-9 Bridge Filter Applications Parameters ... 13-11 Bridge Port/LLC2 Interface Parameters...
Page 15: Section I
Section I Introduction...
Page 17: Chapter 1 Introduction To Netlink Frame Relay Access Devices
LAN-based systems and wide-area applications into a "blended" network. Ranging from the FRX4000 network access node to the FRX8000 backbone switch, each Netlink device can be a fully capable LAN router and a robust switch supporting multiple access and routing protocols. FRX7000 and FRX8000 are documented in separate manuals.
Page 18: Multiprotocol Support
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 relay services "Front end" network to larger frame relay switches X.25-to-frame relay gateway applications Multiprotocol Support FRX and FRM support the same protocols, listed below.
Page 19 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 SDLC-to-LLC2 and LLC2-to-SDLC conversion Autocall Request to Send (RTS) support SNA/LLC2 Supports both ends of PU2-to-PU2, PU2.1-to-PU2.1, and PU4-to-PU4 connec- tions...
Page 20 RIP versions 1 & 2 ICMP Standard NDIS interfaces for Ethernet, Token Ring, and 802.3 LANs RFC 1490 frame relay and RFC 1356 X.25 interfaces for WANs Ping Connection of LAN-attached workstation to remote router or server via X.25, frame relay, Ethernet, or Token Ring Filtering of certain types of traffic, for traffic control and access security Support of RIP, SAP, periodic RIP, periodic SAP Dynamic and static routing...
Page 21: Management Functions
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 ™ Network Manager with configuration abilities and status infor- mation on FRXs and FRMs NetView Service Point function Control of remote FRXs/FRMs...
Page 22: Hardware Overview
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. Options include: Serial expansion card, providing four more WAN ports (all four ports either RS- 232 or V.35.
Page 23: Wan Port Cables For Netlink Frx4000
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 Ethernet cable and, if AUI, the tranceiver, must be provided by the customer. The Token Ring model of FRX4000 contains a Token Ring interface, provided in RJ- 45 (for unshielded twisted pair) and 9-pin "D"...
Page 24: Frx6000
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 ASCII terminal.
Page 25: Frx6000 Rlp, Lics, And Cables
Switch settings assign each RLP in a unique ID within the node. 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: Lan Card Interfaces
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 Depending on the number of RLPs, an FRX6000 can contain one or two LAN cards (in any combination).
Page 27: Operator Interfaces
Operator Interfaces Installation of FRX6000 software into a node, generally done before the node ships to the customer, requires a directly connected keyboard and monitor. Once the node has been installed and configured, it can function with no operator interface. However, configuration, file copy (backup, restore, transfer, etc.), and monitoring operations require a keyboard and screen, which can be in any of several forms.
Page 28: Frame Relay Module
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 chassis (except the Ethernet interface module).
Page 29: Frame Relay Module With I/O Boxes And Cabling
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 signals to an I/O box assembly.
Page 30 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. However, config- uration, file copy (backup, restore, transfer, etc.), and monitoring operations require a keyboard and screen, which can be in any of several forms.
Page 31: Introduction To Menu Operations
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 only after the operator enters a password. When running outside the menu operations, a display will be similar to the following figure, and will show the current status of all ports on the node.
Page 32: Moving Through The Menus
After the operator presses (described on page 3-2), the Main Menu will appear: This is the starting point for all menu operations. The organization of the menus is shown in Appendix G. Moving Through the Menus To select a menu item, press the letter to the left of the item. To return to the next higher menu from a lower-level, press To move from operations under one Main Menu entry to operations under another entry, you must return to the Main Menu.
Page 33: On-Line Help
Throughout this manual are tables of valid and default values. To specify a default (if one exists), press On-Line Help Each screen menu displays the prompt will usually display a list of options. To make a selection, press either the function key shown preceding the desired option or the character preceding the desired menu item.
Page 34 F5: Copy 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 displayed, with the new database values. (The original record is automatically saved.) Press F6: Move Record deletes the original record.
Page 35 Function Keys on an ASCII Terminal Standard PC keyboard function keys are represented as follows on an ASCII terminal keyboard: Keyboard [F1] [F2] [F3] [F4] [F5] [F6] [F7] [F9] [F10] [PgUp] [PgDn] Introduction to Netlink Frame Relay Access Devices ASCII Keyboard Maps to: [PF1]...
Page 36: Stopping Operation
Shutting Down To shut down an FRX4000 or FRX6000, simply switch it off. A Frame Relay Module cannot be shut down without powering down the MMAC- PLUS chassis; however, the FRM can be unplugged and removed without disrupting operation of the MMAC-PLUS or the other modules in the MMAC-PLUS.
Page 37: Configuration
Section II Configuration...
Page 39: Chapter 2 Introduction To Database Configuration
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 contains defining parameters for a specific component; for example, physical ports, subscriber IDs, or IP interfaces.
Page 40: Database Setup Recommendations
Some things you must know before configuring the database are: (FRX6000 only) How many line processors (RLPs) are there in the node, and what is the LP number (ID) of each? (This is determined by switch settings – see Figure 4-4 on page 4-7.)
Page 41: Producing A Configuration Report
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 Main Menu) or Menu). The report is created and saved to the node's hard disk under the name REPORT.TXT.
Page 42: Where To Find Database Records
Where to Find Database Records The following shows where to find the various configuration files among the menus. (The first item, are the chapters/appendices in this manual where the items below those entries are described. Following most items in the lower tiers are descriptions of the associated database records.
Page 43 Introduction to Database Configuration Configure IPX Filter Applications filters to interfaces/filter types/directions. On-Line Update IPX Filter Definitions and Applications (Chapter 12) allows updating the FRX/FRM with any changes without rebooting. Review Bridge Filter Definitions Bridge filters (see next item) that have been configured on the FRX/FRM.
Page 44 Review X.25 Address Translation Templates Configure X.25 Address Translation Templates Test X.25 Address Translation Templates – (Chapter 6) specifies operating parameters Configure Logical Ports for logical ports residing on physical frame relay ports. Configure LAN Interfaces Review IP Interfaces – (Chapter 11) displays information on any IP interfaces (see below) configured in the FRX/FRM.
Page 45 Introduction to Database Configuration View Configuration Report above operation. Configure Frame Relay Backup Groups one or more frame relay ports/DLCIs that will act as backup(s) for a port. – (Chapter 2) displays the results of the – (Chapter 6) allows creation of...
Page 47: Chapter 3 Configuring Node Parameters
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 chapters.
Page 48: Changing The Login Password
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 words are case sensitive.) To change the password, press from the Main Menu). When prompted: 1.
Page 49: Setting The Date And Time
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 date and time as currently recognized by the FRX/FRM will be displayed, and you will be asked: leave it as is.
Page 50: Configuring Node Defaults
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. Press This is the first of three Node Defaults screens—pressing the display among the three screens.
Page 51: Node Defaults Parameters
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 values configured for some parameters, other parameters might not be displayed.
Page 52 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, Remote Control ID Remote Control ID is required if a remote FRX, FRM, or async terminal will be used to take control of the local FRX/FRM (via a physical or logical port in the local device).
Page 53 Primary Alarm Output ID 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 device. Primary Alarm Output Pwd is a password that will be used with the lecting node, the local FRX/FRM's the collecting node’s Secondary Alarm Output ID...
Page 54 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 (See that entry below and "Alarm Buffer" page 18-2.) Min Congestion is a percentage of the FRX/FRM alarm buffer.
Page 55: Netview Parameters
NetView Parameters Parameter Name Local Subscriber ID Remote Subscriber ID Maximum Bytes Per Frame Local SAP Address Local MAC Address IDBLK IDNUM Priority Bandwidth Allocation Group On-Line Temporary Changes Name is the VTAM PU name that will identify the FRX/FRM as a NetView Service Point. Local Subscriber ID is a subscriber address for the local end of an LLC2 session established for a NetView connection.
Page 56 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 over a native LLC2 frame relay interface, the parameter will be ignored.
Page 57 If acknowledgments/responses are still outstanding after station will declare the link inoperative. The value specified for layer (e.g., queuing). is the Receiver Acknowledgment Timer, used by the link station to delay sending an acknowledgment of a received Information LPDU. The timer is started when the LPDU is received and reset when the acknowledgment is sent.
Page 58: Warning Messages
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 output device is unable to output to the device.
Page 59: Configuring Cards And Protocols
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.
Page 60: Frx4000
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 loaded protocols. To access the LP screens, press To identify any installed Line Interface Card and display a list of configured and installed protocols, press...
Page 61: Lp Configuration Menu For Frx4000
To add or remove a protocol: 1. Press the letter corresponding to the protocol number. The protocol in the Configured 2. When finished configuring this screen, press 3. When asked: the FRX4000 software. Configuring Cards and Protocols Line Processor C onfiguration LP: 0 S tatus: I nstalled Memory Configuration: 8 Meg...
Page 62: Frx4000 Line Processor Parameters
FRX4000 LP Parameters Parameter Protocol "n" Protocol determines which protocols can run in the node. Although the FRX4000 contains a group of protocols in the software when shipped to the customer, they must be loaded into the operating software (by configuring them in the LP file, then rebooting the node).
Page 63: Lan Interface
LAN Interface Each FRX4000 contains a built-in LAN interface, either Ethernet or Token Ring (depending on the model). To configure the interface, press ration Menu. When prompted for an default of LAN Card Configuration * In terface Numb er: 0 * Type B Locally A dmin MA C A ddr C Ring Speed...
Page 64: Frx6000
If a record is configured for an RLP, and the RLP is then installed with a different configuration, the software will read the difference and change the record. . (LP numbers are determined by switch settings 0–7 from the Main Menu...
Page 65: Frx6000 Rlp, Lics, And Cables
Figure 4-4 FRX6000 RLP, LICs, and Cables Switch On On Off On Off On On Off Off Off On On Off On Off Off Off On Off Off Off * Switch 7 is Off for 8 MB RLP, On for 4 MB RLP. RLP Cable...
Page 66: Lp Configuration Menu For Frx6000
To add or remove a protocol: 1. Press the letter corresponding to the protocol number. The protocol in the Configured page 4-9. 2. Reboot the node as follows: a. Press b. When asked: c. Type Line Process or Con figu ration * LP: * S tatus: I nstalled * Memory Configuration: 8 Meg...
Page 67: Lp Parameters In An Frx6000
LP Parameters in an FRX6000 Parameter LP Type Line Interface Card "n" Protocol "n" LP Type Cannot be changed if the RLP is installed. If it is not installed, the value changes each time you press Line Interface Card 1, 2 contain the circuitry for the physical ports of an RLP.
Page 68: Lan Cards
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 no more than seven pro- tocols (including X.25) be configured on any one RLP.
Page 69: Lan Card Configuration Screen
To configure a record for a LAN card in an FRX6000, press ration Menu. (Unlike serial ports, there are not separate files for the cards and the ports.) When prompted for an responds to the card as defined in PROTOCOL.INI. Press [F7] LAN Card Parameters...
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 To access the LP screens, press To configure a protocol, press an LP number, type numbers in an FRX6000;...
Page 71: Frame Relay Module Rlp, Lics, And Cables
LIC 2 Connector LIC 1 Connector RLP Cable I/O Box LAN Card LAN Interface Cable Figure 4-7 Frame Relay Module RLP, LICs, and Cables Configuring Cards and Protocols 4-13...
Page 72: Lp Configuration Menu For Frame Relay Module
Figure 4-8 LP Configuration Menu for Frame Relay Module To add or remove a protocol: 1. Press the letter corresponding to the protocol number. The protocol in the Configured page 4-15. 2. Reboot the node as follows: a. Press b. When asked: c.
Page 73: Lp Parameters In A Frame Relay Module
LP Parameters in a Frame Relay Module Parameter LP Type Line Interface Card "n" Protocol "n" Line Interface Card 1, 2 contain the circuitry for the physical ports of an RLP. (LIC 1 contains ports 0–3, LIC 2 contains ports 4–7.) Protocol specifies which protocols will run on the RLP.
Page 74: Lan Cards
LAN Cards You can display a report that identifies the LAN card in the FRM. Press Configuration Menu (or tents of the file PROTOCOL.INI (which can also be printed from DOS or copied to a diskette—see "On-Line Database Operations" on page 16-11). One line of PRO- TOCOL.INI, as shown below.
Page 75: Lan Card Parameters On Frm
LAN Card Parameters Parameter Type Locally Admin MAC Addr Locally Admin. MAC Addr is a MAC address that will override the universally administered MAC address. If all zeros are specified, the universal address will be used. Configuring Cards and Protocols 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...
Page 76 4-18 FRX/FRM 3.3 User Guide, Rev 04...
Page 77: 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. FRX4000, FRX6000, and the Frame Relay Module support physical ports, as well as logical ports, which run on a physical frame relay port.
Page 78: Physical Ports On Frx6000 Rlp
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. LIC 1 LIC 2 I/O Box...
Page 79: Physical Ports On Frame Relay Module
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. Configuring Serial Ports LAN Card LAN Interface Cable...
Page 80: Database And System Memory Values
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 an entry called will affect the If you change On-Line System Memory Changes this parameter toggles the display between the...
Page 81: Configuring A Physical Port
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 Processor that contains the port, plus Line Interface Card that supports the port.
Page 82 The entry 0–3), and Link_disable IPL, or has not yet been established. Failed while a port is becoming enabled.) Link_down Disconnect Linkup To configure the port with the parameter values neccessary for your application, go to the appropriate chapter: Frame relay – Chapter 6 X.25 –...
Page 83: 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 DCE, connecting to end-user devices, or DTE, connecting to a network or frame relay PVC.
Page 84: Frame Relay Backup Examples
DLCIs used for backup on the initiating node are assigned to "backup groups," each of which can contain up to ten backup DLCIs. A backup group is then assigned to one or more "primary" DLCIs (the ones that will be backed up). The basic procedure for configuring backup DLCIs is: 1.
Page 85 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 automatically be established between Node 1/LP 2/Port 5/DLCI 72 and Node 2/Port 6/DLCI 19.
Page 86 On Node 2, configure the following (as well as other parameters necessary for oper- ation): 1. Port Configuration ( LP?: 0 RLP Port?: 5 O Additional Parameters 2. Port Configuration ( LP?: 0 RLP Port?: 6 O Additional Parameters Example 2 In Example 2, the primary link is between Node 1/LP 2/Port 4/DLCI 16 and Node 2/ Port 5/DLCI 18.
Page 87 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. Configuring Frame Relay...
Page 88: Configuring Bandwidth Allocation Groups
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 that response time-sensitive traffic gets access to the available frame relay bandwidth.
Page 89: Bandwidth Allocation Group Parameters
Pressing contains groups 9–12, and Page 4 contains groups 13–16. Bandwidth Allocation Group Parameters Explanations of the parameters follow the table. Parameter Dynamic Optimization Group "n" Percentage Group "n" Excess Priority Group "n" Use Excess Burst Group "n" Percentage is a percentage of bandwidth that will be dedicated to traffic in a group if necessary. If the traffic does not require the full allocation, unused bandwidth will be available to other groups.
Page 90 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; the higher the number, the higher the priority.
Page 91: Configuring Frame Relay Ports
Configuring Frame Relay Ports Once the necessary Node, Line Processor, and protocol parameters have been con- figured, press When prompted, enter: LP number of the RLP containing the port: FRX4000 or FRM. (The default is Port number (see port locations in Chapter 5): The display for an existing port will show the configured parameter values, while the display for a new port will show default database values.
Page 92: Frame Relay Port Screen 2
Reviewing DLCI Configuration (Figure 6-4, Item C) To display the current configured DLCIs on the port, press 6-4. A screen similar to the following information will be displayed for each con- figured DLCI. The first line of parameters applies to all DLCIs on the port (or in the node if pressed).
Page 93 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: ICIR OCIR BECN Proto The parameters in the second line are: RRLP RPrt RDLCI...
Page 94: Frame Relay Dlci Configuration Screen 1
Figure 6-6 Frame Relay DLCI Configuration Screen 1 6-12 Frame Relay DLC I C onfiguration (s creen 1 of 2) Port DLCI A Committed In formation Rate (I n) 2000 B Committed Burst Size (In) 2000 C Excess Burst Size (In) 1000 D Committed In formation Rate (Out) 2000...
Page 95: Frame Relay Dlci Configuration Screen 2
Figure 6-7 Frame Relay DLCI Configuration Screen 2 Viewing Learned DLCIs (Figure 6-4, Item E) If the port is a logical DTE, a list of all DLCIs (extracted from LMI/AnnexD frames) can be displayed by pressing by three columns:— Configuring Frame Relay Frame Relay DLC I C onfiguration (s creen 2 of 2) * LP * Port...
Page 96: Frame Relay Port Parameters
Frame Relay Port Parameters Parameter Port Type Physical Port Interface Blocked Port Flag Line Speed Maximum Bytes per Frame Logical DCE Generate Clock Rcv Clock (TT) from DTE CSU/DSU Operating Mode RTS Control Link Layer Management N1 Polling Count N2 Error Threshold N3 Monitored Events Count T1 Link Integr ity Timer T2 Polling Verification Timer...
Page 97: Frame Relay Dlci Parameters
Parameter Committed Info. Rate (In/Out) Committed Burst Size (In/Out) Excess Burst Size (In/Out) BECN Recovery Count Outgoing DLCI Pr iority Backup Group Number Enable Backup Protocol Remote RLP Remote Port Remote DLCI Switchover Timer Switchback Timer Time to Hold Data While Waiting 1 If rate control will not be used, configure the 2 CIR = Committed Information Rate.
Page 98 V.35, RS-449, 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 LIC, and only the valid interfaces will be displayed on the Port screen, among: V.35, RS-449, RS-530 RS-422 LIC.) FRM ports 0–7 are determined by the Line Interface Cards and attached I/O...
Page 99 Logical DCE defines the port as (if the opposite of the device at the other end of the connection. Logical and physical DCE/DTE are independent of each other (e.g., a port can be a physical DCE and logical DTE). Generate Clock specifies whether the port will generate the clock necessary to synchronize traffic over the link.
Page 100 declared active after that poll. (If the count, the DCE will be declared inactive, and the T1 Link Integrity Timer determines how often the logical DTE will initiate a Status Enquiry message to the DCE. T2 Polling Verification Timer indicates how long the logical DCE will wait between Status Enquiry messages from the DTE before recording an error.
Page 101 Excess Burst Size (In/Out) ) is the incoming or outgoing (depending on the parameter) maximum amount of data in excess of the during the time interval used for the value will be buffered in the FRX/FRM. BECN Recovery Count is a method of controlling the rate of return to maximum traffic flow after it has been reduced due to congestion.
Page 102 DLCI after the primary becomes active again. If set to the maximum of the backup will not switch to the primary unless it (the backup) fails. Time to Hold Data While Waiting is the time the node will queue data while waiting for a backup DLCI to become active.
Page 103: Configuring A Logical Port
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 either T1.617 Annex G (a.k.a. FRF 3 and 3.1) or T1.617 RFC1490.
Page 104: Logical Port Parameters
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, press at the third screen.
Page 105: Logical Port Cug Parameters
Parameter T22 Reset Timer T23 Clear Timer DTE Restar t Retry Count DTE Reset Retry Count DTE Clear Retry Count Parameter Prefer ential CUG Flag Prefer ential CUG Incoming Access Allowed Outgoing Access Allowed Add/Change CUG Delete CUG Display all CUGs Mapped DLCI Number is the Data Link Connection Identifier, which links the logical port to a logical con- nection on the physical frame relay port.
Page 106 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, SNA PU, LLC2 host, IP interface, IPX interface, SVC subscriber, and PVC connection.
Page 107 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.
Page 108 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 Throughput Class packet will be used. (If a class for either direction is not included, its default value will be used.) Local Charging Prevention prevents calls (if...
Page 109 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 enabled or if a throughput class is not requested in the Call Request.
Page 110 cation.) If the 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 other members, but access to and from network users outside that CUG may be denied (determined by Allowed packets, and is cross-referenced with the CUG Index in the FRX software.
Page 111: Configuring Subscriber Addresses
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 a list of current Subscriber IDs (addresses), press Routing Paths Menu (or To add or change a Subscriber ID, press...
Page 112: Subscriber Parameters
Subscriber Parameters Parameter Subscriber Name Routing Algorithm System atic Redirection Redir ect on Busy Redir ect on Out of Order Connection Priority 1st,2nd,etc. Path Configured Port Redir ection Address 0,1,etc. 1 The software does not verify that the specified LP/port exists. Make sure the specified Subscriber Name identifies the subscriber to the console operator.
Page 113 Systematic Redirection will redirect (if 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 redirect calls (if scriber device is busy. Redirect on Out of Order will redirect calls (if scriber device is out of order.
Page 114: Configuring Frame Relay Pvcs Across The Node
Configuring Frame Relay PVCs Across the Node An FRX4000 or FRX6000 PVC is a "permanent" connection between two physical ports in a node. This allows communication between the attached devices as soon as they are powered up, without the need to first establish a connection. To display a list of current PVCs, press from the Main Menu).
Page 115: Frame Relay Pvc Parameters
Frame Relay PVC Parameters Parameter Connection Priority Primary/Secondary Name Primary/Secondary DLCI Primary/Secondary LP Primary/Secondary Port Committed Inf. Rate Committed Burst Size Excess Burst Size 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: Connection Priority prioritizes this connection for intra-nodal traffic;...
Page 116 Committed Information Rate (CIR) is the data throughput that the network agrees to support under normal condi- tions. Committed Burst Size ) is the maximum amount of data that the network agrees to transfer under normal conditions within the time period defined by B will have the Discard Eligibility (DE) bit set, and will be tracked by the FRX/FRM statistic Excess Burst Size...
Page 117: Configuring Frame Relay Backup Groups
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 DLCI in the backup group configured for the primary DLCI, and will select the first available one as a backup.
Page 118 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 the backup does not become active before the timer expires, the software will search the backup group for the next available backup.
Page 119: 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 encapsulated in frame relay (per RFC 1490), see "Configuring a Logical Port"...
Page 120: Configuring X.25 Ports
Configuring X.25 Ports Once the necessary Node, Line Processor, and protocol parameters have been con- figured, press When prompted, enter: LP number of the RLP containing the port: FRX4000 or FRM. (The default is Port number (see port locations in Chapter 5): The display for an existing port will show the configured parameter values, while the display for a new port will show default database values (listed in tables on page 7-3 and page 7-12.) The following figure is an example of an existing port.
Page 121: X.25 Port Parameters
If this port will be connected to a dial modem, press Dial Port" on page 7-12.) If none of the above applies, press perform the next desired operation. X.25 Port Parameters The following table lists all parameters displayed on screens 1–3. (Some will or will not be displayed depending on whether the physical interface is DSU.) CUG, Network Trunk, and Dial Port screens and parameters are described later.
Page 122 Parameter Mask Link Alar ms Maximum Packet Size Default Window Size Default Packet Size Maximum Window Size Maximum Throughput Class Default Calling Address T20 Restart Timer (sec) T21 Incoming Call Timer (sec) T22 Reset Timer T23 Clear Tim er DTE Restart Retry Count DTE Reset Retry Count DTE Clear Retr y Count 2 This parameter is relevant only if...
Page 123 V.35, RS-449, RS-530 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 on the Port screen, among: RS-530 and X.21 are available through special order only.) Blocked Port Flag will cause the port to be enabled ( in that state until this parameter is changed or an on-line enable (...
Page 124 N2 Retransmit Count is X.25 value frame after a the probability 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 re-transmission of an I-frame if the previous transmission is not acknowledged.
Page 125 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 use for calls through this port.
Page 126 Mask Link Alarms prevents (if enabled) transmission to the collecting node of the link alarms 400-406 Link Enabled, Link Disabled Maximum Packet Size is the maximum data packet size that will be allowed to pass through this port. A packet size included in a call setup packet will be used, as long as it is smaller than the maximum specified here.
Page 127: Cug Management
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 be initiated. DTE Reset Retry Count is the number of times a Reset Request from the logical DTE will be transmitted.
Page 128: X.25 Port Cug Parameters
To configure a CUG, press CUG Index: CUG number: any other requested information. (See Table 8-2.) To delete a CUG, press Pressing associated indices. CUG Parameters Table Parameter Pr eferential CUG Flag Pr eferential CUG Incoming Access Allowed Outgoing Access Allowed Preferential CUG Flag specifies whether the port belongs to any CUGs.
Page 129: Configuring A Network Trunk
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- tional).
Page 130: Configuring A Dial Port
Configuring a Dial Port If the port will be connected to an auto-dial modem, configure the parameters on the following screen. Dial Port Parameters Parameter Dial Support Inactivity Timer Disconnect Timer Line Setup Timer Dial Support specifies whether this port is connected to a dial modem and, if so, whether connec- tions will be initiated through dial-in or dial-out calls.
Page 131 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 the Disconnect Timer Disconnect Timer is the length of time a dial-in port will remain disabled after expiration of the Inactivity...
Page 132: Configuring Subscriber Addresses
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 a list of current Subscriber IDs (addresses), press Routing Paths Menu (or To add or change a Subscriber ID, press...
Page 133: Subscriber Parameters
Subscriber Parameters Parameter Subscriber Name Routing Algorithm Systematic Redirection Redirect on Busy Redirect on Out of Order Connection Priority 1st,2nd,etc. Path Configured Por t Redirection Address 0,1,etc. Subscriber Name identifies the subscriber to the console operator. Routing Algorithm allows creation of a "hunt group" of ports (see example in Appendix B), for the purpose of routing per a pre-selected algorithm: = Round Robin –...
Page 134 Systematic Redirection will redirect (if 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 redirect calls (if scriber device is busy. Redirect on Out of Order will redirects calls (if scriber device is out of order.
Page 135: Configuring X.25 Address Translation Templates
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 data, and/or facilities fields of a Call Request packet as it passes into or out of the node.
Page 136: Address Translation Templates Display
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 translation template defined to intercept packets with the PDN-com- patible calling address for node 1.
Page 137: Translation Template Parameters
The fields must match the equivalent fields in the Call Request packet, but not neces- sarily literally—they can use wildcards. Translation Template Parameters Parameter Template Name Called Address Calling Address User Data Protocol ID Facilities If replacing all or part of a field, see "Replacing (field type)" over the next few pages. Configuring X.25 Translation Temp late Maintenance * LP...
Page 138 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 in the SVC routing table. The gateway also allows the data field operations. Replacing Called/Calling Address or User Data To replace all or part of any of these fields, press Maintenance Menu.
Page 139: Translation Examples
Type which positions of the twelve digits in the original user data are to replace the selected portion of the packet. = Text (valid for replacement of user data only). Type by the text that will replace the user data. Replacing Protocol ID Press string of up to four hex bytes.
Page 140: Testing A Translation Template
Testing a Translation Template Press Main Menu) or translation template you have created. When prompted, enter: Port. Direction: Called address to be translated. Calling address to be translated. Facility length + facility + user data. (The user data includes four bytes for pro- tocol ID, which must be entered as a hex string.) To specify only user data, at the above prompt enter desired user data, including the 4-byte protocol ID.
Page 141: Configuring X.25-To-X.25 Pvcs
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 includes X.25-to-X.25, async-to-X.25 (described in Chapter 10), and IP over X.25 (described in Chapter 11).To display a list of current PVCs (of all types), press at the PVC Configuration Menu (or...
Page 142: X.25 Pvc Parameters
X.25 PVC Parameters Parameter Connection Priority Subscriber Name Logical Channel Port Packet Size Window Siz e Connection Priority prioritizes this connection 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, SNA PU, LLC2 host, Bridge Port/LLC2 Interface, IP interface, IPX interface, and SVC subscriber.
Page 143: 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 interfaces (e.g., NPSI on IBM 3725/3745).
Page 144: Configuring An Sna Port
Configuring an SNA Port Once the necessary Node, Line Processor, and protocol parameters have been con- figured, press When prompted, enter: LP number of the RLP containing the port: FRX4000 or FRM. (The default is Port number (see port locations in Chapter 5): The display for an existing port will show the configured parameter values, while the display for a new port will show default database values.
Page 145: Sdlc Pu Subscriber Parameters Screen
Figure 8-2 SDLC PU Subscriber Parameters Screen If SDLC/LLC2 conversion will be done on the PU connection, specify in Figure 8-2, then press (If the PU is not part of an SDLC/LLC2 connection, you do not have to configure those parameters.) Configuring SNA SDLC PU Sub scriber Parameters (screen 1 of 2) * LP 1...
Page 146: Sna Port Parameters
SNA Port Parameters Parameter Port Type Name Physical Port Interface Blocked Port Flag Line Speed No Data Poll Period (ms) No Resp Poll Period (ms) Maximum Retransmissions Outstanding Frames Generate Clock Rcv Clock (TT) from DTE SNA Type Packet Size On-line Sys.
Page 147: Sna Port Pu Parameters
Parameter PU Name Local Subscriber ID Remote Subscriber ID Maxdata Autocall Autocall Retry Time Autocall Retry Count Istatus LPDA Resource ID LLC2 Connection L2 DatMode LLC2 Parameters Local SAP Address Local MAC Address IDBLK IDNUM (100 msec) (msec) (sec) Priority Bandwidth Allocation Group 1 If the PU will be used for SDLC-LLC2 conversion (at the local node, or at a remote node 2 In multiples of 4.
Page 148 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 FRX4000 port 1 is DSU card is installed. FRX4000 ports 2 and 3 are determined by the attached cables: RS-232, V.35, RS-449, or X.21.
Page 149 No Data Poll Period is the time between polls by this TPAD port of its PU (physical unit) when the PU has no data to send. This parameter has no relevance on an HPAD port. No Resp Poll Period is the time between polls by this TPAD port of its PU when the PU is not responding. The TPAD will continue to poll at this interval up to the number of times specified by Maximum Retransmissions Maximum Retransmissions...
Page 150 determines the level of data encoding: = NRZ (Non-Return to Zero) on, which means that = NRZ off, which means that Unless there is a site-specific configuration needing NRZI (Non-Return to Zero Inverted), always use NRZ for all SNA modes. (NRZ off = NRZI on.) Packet Size is the maximum packet size that will be transmitted on the port.
Page 151 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 remote end of an SNA connection.
Page 152 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 relevant only in a connection to a 3174 or AS/400-type setup where a specific source SAP address is required.
Page 153 expires and acknowledgments/responses are still outstanding, the link station will send one of the following, then restart A Supervisory LPDU with the P bit set to B'1,' to solicit remote link station status. Any Unnumbered LPDUs that were not responded to the first time they were sent.
Page 154 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 Bandwidth Allocation Groups" on page 6-6. 8-12 FRX/FRM 3.3 User Guide, Rev 04...
Page 155: Configuring Subscriber Addresses
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 a list of current Subscriber IDs (addresses), press Routing Paths Menu (or To add or change a Subscriber ID, press...
Page 156: Subscriber Parameters
Subscriber Parameters Parameter Subscriber Name Routing Algorithm System atic Redirection Redir ect on Busy Redir ect on Out of Order Connection Priority 1st,2nd,etc. Path Configured Port Redir ection Address 0,1,etc. 1 The software does not verify that the specified LP/port exists. Make sure the specified Subscriber Name identifies the subscriber to the console operator.
Page 157 Systematic Redirection will redirect (if 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 redirect calls (if scriber device is busy. Redirect on Out of Order will redirects calls (if scriber device is out of order.
Page 158: Configuring A Hunt Group For Sna Subscribers
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 routing table. Configure two ports as SNA HPADs, one (called HPAD1 for this list) with Round Robin specified and one or more routing paths configured, and the other port (HPAD2) with any routing algorithm but only one routing path.
Page 159: Configuring Llc2
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-compliant SNA/APPN device.
Page 160: 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 Card(s) supporting the ports that will be the inter- faces.
Page 161: Configuring A Virtual Lan Id
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 Menu (or Virtual LAN ID: If also configuring Bridging in the node, address the remaining parameters as...
Page 162: Configuring Llc2 Hosts
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 LAN Default Parameters Menu (or the hosts' MAC addresses and identify each LLC2 session as (In an Originated session, the host initiates LLC2 sessions;...
Page 163: Llc2 Terminated Host Configuration Screen
Figure 8-7 LLC2 Terminated Host Configuration Screen Configuring SNA SN A LLC 2 Termin ated Sess ion C onfiguration (Screen 1 of 2) Host Numb er: 1 A Host MA C Add ress 0C005A123402 B S es sion Typ e Terminated C T1 (100 ms ec) D T2 (msec)
Page 164: Llc2 Host Parameters
LLC2 Host Parameters Parameter Host MAC Address Session Type (100 msec) (msec) (sec) Pr iority Bandwidth Allocation Group Routing Subscriber ID Source MAC Addr Mask On-Line Tem porary Changes HSAP Type Local Subscriber ID Remote Subscriber ID IDBLK IDNUM MAXDATA MAXIN 8-22 Table 8-4 LLC2 Host Parameters...
Page 165 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 expecting.
Page 166 The node will reset A REJ (Reject) LPDU, provided a Command LPDU with the P bit set to not outstanding. A Response LPDU with the F bit set to An Information or Supervisory LPDU with an N received and less than or equal to the line station's V LPDU with the P bit set to If additional LPDUs are set from the remote station after the local node has reset the timer will be restarted if acknowledgments of or responses to those LPDUs are out-...
Page 167 will be reset whenever an Information or Supervisory acknowledgment LPDU is sent by the local node. is the maximum number of sequentially numbered Information LPDUs that the local node can have outstanding. If is the maximum number of times that an LPDU (including Information LPDUs resent after a checkpoint operation) will be sent following expiration of Priority prioritizes intra-nodal traffic;...
Page 168 connection, this address must match the 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 the figured in the SNA port record for the SDLC device. If configuring an LLC2-to-LLC2 connection, this address must match the Host record.
Page 169: Configuring Llc2 Interfaces
Configuring LLC2 Interfaces LLC2 Interfaces records define the types and locations of the interfaces that will carry LLC2 traffic to or from an FRX or FRM. To display configured interfaces, press To configure an interface, press prompted for an interface number (which is merely a sequential number to identify the interface): If modifying an existing record, enter the interface number: If creating a new record, press...
Page 170: Bridge Port/Llc2 Interface Record, Ethernet
Brid ge Port/LLC-2 Interface C onfiguration A I nterface Typ e B Blocked Port Flag C Port Priority D Path Cos t E Priority Option: Figure 8-10 Bridge Port/LLC2 Interface Record, Ethernet Figure 8-11 Bridge Port/LLC2 Interface Record, Frame Relay 8-28 Bridge Port/LLC 2 In terface Nu mb er: 0 Ethern et...
Page 171: Llc2 Interface Parameters
LLC2 Interface Parameters The following table lists parameters for all interface types. Explanations of some parameters follow the table. Parameter Interface Type Blocked Port Flag Por t Priority: Path Cost: Priority LAN Card Por t DLCI Format Bandwidth Allocation Group Host MAC Address Session Type LAN ID...
Page 172 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, the higher the priority. (This pri- ority has no effect on traffic exiting a node.) A priority is also configured in Node Defaults, as well as for each logical port, SNA PU, LLC2 host, IP interface, IPX interface, SVC subscriber, and PVC connection.
Page 173 Bandwidth Allocation Group assigns the interface to one of sixteen groups whose parameters regulate bandwidth usage. See "Configuring Bandwidth Allocation Groups" in on page 6-6. Host MAC Address is the MAC address of the host or workstation to which the remote device needs to connect.
Page 175: 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.25. BSC Batch ports are used to interconnect IBM 2780/3780 devices over frame relay or X.25.
Page 176: Configuring Bsc Interactive Port Records
Configuring BSC Interactive Port Records Once the necessary Node, Line Processor, and protocol parameters have been con- figured, press When prompted, enter: LP number of the RLP containing the port: FRX4000 or FRM. (The default is Port number (see port locations in Chapter 5): The display for an existing port will show the configured parameter values, while the display for a new port will show default database values.
Page 177: Bsc Interactive Port Parameters
A BSC 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. Each con- nection must be assigned a different local subscriber address.
Page 178 Parameter Generate Clock Rcv Clock (TT) from DTE BSC Type Answer Non-Configured Activate Connection w/o poll On-line Sys. Memory Changes EBCDIC Call Info in Call Request Packet Clear VC on Last Device Down Tr ansparent Text Supported End-to-End Acknowledgment Full Duplex Multidrop Slow Poll Retr y Count Slow Poll Retr y Frequency...
Page 179 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 FRX4000 port 1 is DSU card is installed. FRX4000 ports 2 and 3 are determined by the attached cables: RS-232, V.35, RS-449, or X.21.
Page 180 Retransmission Period is the length of time before the node will transmit an I-frame if the previous trans- mission is not acknowledged. If the period expires, the timer will be reset and a super- visory frame will be transmitted demanding immediate acknowledgement. The Maximum Retransmissions The default value of frames that have merely been delayed.
Page 181 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 Clear VC on Last Device Down , causes the virtual circuit to be cleared when no terminals are using it. Transparent Text Supported causes all characters transmitted, including control character sequences, to be treated as data.
Page 182: Subscriber Parameters
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 (accompanied by other condition checks). Error Retransmit Count specifies the number of times the node will resend a block of data after the receiving device has detected an error in that block.
Page 183: Configuring Bsc Batch Port Records
Configuring BSC Batch Port Records Once the necessary Node, Line Processor, and protocol parameters have been con- figured, press When prompted, enter: LP number of the RLP containing the port: FRX4000 or FRM. (The default is Port number (see port locations in Chapter 5): The display for an existing port will show the configured parameter values, while the display for a new port will show default database values.
Page 184: Bsc Batch Port Parameters
BSC Batch Port Parameters Parameter Port Type Physical Port Interface Blocked Port Flag Line Speed Retransmission Period Maximum Retransmissions Maximum Bytes per Frame Generate Clock Rcv Clock (TT) from DTE On-line Sys. Memory Changes EBCDIC Tr ansparent Text Supported Controller Type Full Duplex # of Beginning Sync Chars # of Trailing PAD Chars...
Page 185 Parameter No Response Retry Count Delay Timer Delay Retry Count NAK Retry Count VC to be Cleared after Disc. Idle Timer (sec) Subscriber Information (Sequence) Local Sub Remote Sub Atcl Rtytm Rty# Port Type defines the protocol the port will support. Selecting this parameter will display a list of valid protocols.
Page 186 V.35, RS-449, and X.21 LIC. Also, RS-530 and X.21 are available through special order only.) Blocked Port Flag will cause the port to be enabled ( in that state until this parameter is changed or an on-line enable ( Main Menu) or disable ( Line Speed is the data transmission rate in bits per second, and the clock speed on a serial port when the port is a physical DCE (i.e., the attached I/O cable is DCE).
Page 187 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 Rcv Clock (TT) from DTE allows the clock to be looped back from the DTE using the TT (Terminal Timing) signal, which can be helpful on high-speed lines.
Page 188: Subscriber Parameters
# 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 general poll or a data frame. On expiry, a NAK– EOT–General Poll sequence is transmitted, and the No Response Retry Count is incre- mented.
Page 189 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 indefinite retries. Delete lets you delete the remote subscriber that is currently highlighted. You will be prompted: line and move all entries below it up one sequence number.
Page 190: Configuring Subscriber Addresses
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 a list of current Subscriber IDs (addresses), press Routing Paths Menu (or To add or change a Subscriber ID, press...
Page 191: Subscriber Parameters
Subscriber Parameters Parameter Subscriber Name Routing Algorithm Systematic Redirection Redirect on Busy Redirect on Out of Order Connection Priority 1st,2nd,etc. Path Configured Por t Redirection Address 0,1,etc. 1 The software does not verify that the specified LP/port exists. Make sure the specified Subscriber Name identifies the subscriber to the console operator.
Page 192 Systematic Redirection will redirect (if 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 redirect calls (if scriber device is busy. Redirect on Out of Order will redirects calls (if scriber device is out of order.
Page 193: Configuring Bsc Interactive Devices
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 Menu (or To configure a device, press prompted, enter: LP ID: BSC Port:...
Page 194: Bsc Interactive Device Parameters
BSC Interactive Device Parameters Explanations of some parameters follow the table. Parameter Single User Virtual Circuit Tr ansparent Text Supported Pr inter Disable Status Response Single User Virtual Circuit specifies (if Device Type pair. Currently, this must be configured as Transparent Text Supported causes (if treated as data.
Page 195 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: = Normal Status. The port will report what the device reports. = No Status. The port will report status only if the device is active. = Always Active Status.
Page 197: 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 database: Node parameters.
Page 198: Configuring Async Pad Profiles
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 the values. To display a list of existing PAD profile names and descriptions, press PAD Configuration Menu (or database contains one profile,...
Page 199: Pad Profile Parameters
PAD Profile Parameters Parameter Profile Description 01–PAD Recall 02–Echo 03–Data Forwarding Char 04–Idle Timer Delay 05–Ancillary Device Control 06–PAD Service Signal 07–Receive Break Signal 08–Discard Output 09–Padding after <cr> 10–Line Folding 11–Speed 12–Flow Control 13–Insert <lf> after <cr> 14–Padding after <lf> 15–Editing 16–Character Delete 17–Line Delete...
Page 200 PAD and the user's device. The PAD indicates whether it is ready to accept characters from the user device by transmitting special characters that are used to switch DTE transmission on and off. = no use of XON/XOFF.
Page 201 = no action. = PAD will send an interrupt packet to the remote end but will remain in data = PAD will reset the virtual call and remain in data transfer mode. = PAD will send an indication of a Break message to the remote end and = PAD will escape from data transfer mode and enter command mode.
Page 202 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 contents of the PAD's buffer on a new line. The spec- ified number defines the ASCII character that will be used as the Line Display char- acter.
Page 203: Configuring Async Pad Login Parameters
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 Main Menu). To add or change login ID parameters, press Menu and enter a subscriber ID.
Page 204: Login Parameters
Login Parameters Parameter Login Password Profile Name Login Password interacts with the Login Required parameter in the Port record. If login is required, the user must log into the PAD in order to make a call through it. Profile Name is a name given to the async PAD's "profile,"...
Page 205: Configuring Async Port Records
Configuring Async Port Records Once the necessary Node, Line Processor, and protocol parameters have been con- figured, press When prompted, enter: LP number of the RLP containing the port: FRX4000 or FRM. (The default is Port number (see port locations in Chapter 5): The display for an existing port will show the configured parameter values, while the display for a new port will show default database values.
Page 206: Async Pad Port Parameters
Async PAD Port Parameters Parameter Port Type Physical Port Interface Blocked Port Flag X.3 Line Speed Initial Profile Nam e Login Required Parity DCE Cable Attached Mask Link Alar ms On-line Sys. Memory Changes Generate M-bit packets Default Calling Address Disable X.121 User Calls Autocall Autocall Delay...
Page 207 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 FRX4000 port 1 is DSU card is installed. FRX4000 ports 2 and 3 are determined by the attached cables: RS-232, V.35, RS-449, or X.21.
Page 208 Login Required determines whether or not async PAD users will be required to log in before con- necting with this port. If Login Password Parity determines the type of parity checking that will be used on incoming data. Pressing at the Port screen changes the value to the next one in the list: = None On-Line System Memory Changes/Database Display determines which set of values will change, as described under "Database and System...
Page 209 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 an outgoing Call Request packet.
Page 210 If the user logs out, the be disconnected. This parameter should be will periodically be output. (This is harmless, but unnecessary.) This parameter is automatically disabled on a PVC connection. Timeout if No Call if set to cleared, and the PAD is ready to receive commands from the user. The timer is reset every time the port receives or transmits a call.
Page 211: Configuring Subscriber Addresses
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 address). To display a list of current Subscriber IDs (addresses), press Routing Paths Menu (or To add or change a Subscriber record, press...
Page 212: Subscriber Parameters
Subscriber Parameters Parameter Subscriber Name Routing Algorithm System atic Redirection Redir ect on Busy Redir ect on Out of Order Connection Priority 1st,2nd,etc. Path Configured Port Redir ection Address 0,1,etc. 1 The software does not verify that the specified LP/port exists. Make sure the specified Subscriber Name identifies the subscriber to the console operator.
Page 213 Systematic Redirection will redirect (if 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 redirect calls (if scriber device is busy. Redirect on Out of Order will redirects calls (if scriber device is out of order.
Page 214: Configuring Abbreviated Addresses
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 existing abbreviated addresses and their associated subscriber IDs, press from the Main Menu).
Page 215: Configuring Async Pvcs
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 PVC support in FRX and FRM includes async-to-async and async-to-X.25.
Page 216: Async Pvc Parameters
Async PVC Parameters Parameter Connection Priority Subscriber Name Logical Channel Port Packet Size Window Siz e Connection Priority prioritizes this connection 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, SNA PU, LLC2 host, Bridge Port/LLC2 Interface, IP interface, IPX interface, and SVC subscriber.
Page 217: 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 routes can be configured.
Page 218: Using The Node As An Ip Gateway
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 first configure the following in the database: Node parameters, described in Chapter 3.
Page 219: Specifying A Rip Version
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 version 2, press from the Main Menu).
Page 220: Configuring Ip Interfaces
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 Interfaces Menu (or To configure an interface, press prompted, enter an interface number: identify the interface.) The display depends on the interface;...
Page 221: Ip Interface Parameters
IP Interface Parameters Explanations of most parameters follow the table. Parameter Maximum Transmission Unit Network Mask Routing Metric Count ICMP Redirects RIP Flash Updates RIP Full Updates Priority Bandwidth Allocation Group Interface Type Source IP Address Destination IP Address Broadcast Address LAN Card Number Source Subscriber Destination Subscriber...
Page 222 mediate routers or gateways, as well as the destination host. If the mission Unit automatically change to the minimal datagram size. Network Mask is used during routing to determine the portion of the address associated with the network. All network bits are set to Routing Metric Count is the number of network "hops"...
Page 223 LAN Card Number identifies the LAN card that contains the interface. (Only 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 configured in the SVC Subscriber record.) Destination Subscriber is a subscriber ID associated with the destination IP interface port.
Page 224: Configuring Static Ip Routes
Configuring Static IP Routes Routing of IP traffic is handled dynamically by such protocols as RIP, as well as via static routes configured in the FRX/FRM. To display configured static routes, press Menu (or To configure a route, press prompted, enter a 11-8 from the Main Menu).
Page 225: Ip Routing Parameters
IP Routing Parameters Parameter Router Metric Count Route Type Route Destination Destination Mask Router is the IP address of a router that can reach the route destination. Metric Count is the number of "hops" (network gateways in the overall path over the internet) from the source to the destination.
Page 226: Configuring Ip-To-X.25 Pvcs
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 connection. To display a list of current PVCs, press from the Main Menu).
Page 227: Ip-To-X.25 Pvc Parameters
IP-to-X.25 PVC Parameters Parameter Connection Priority Subscriber Name IP Interface ID Packet Size Window Size Logical Channel Por t Connection Priority prioritizes this connection 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, SNA PU, LLC2 host, Bridge Port/LLC2 Interface, IP interface, IPX interface, and SVC subscriber.
Page 228 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/Port specifies the LP and port at each end of the PVC.
Page 229: 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 of RIP (routing information protocol) and SAP (service advertising protocol), providing end-to-end compatibility over a LAN or frame relay network (via RFC 1490) with other IPX routers.
Page 230: Configuring Ipx Node Defaults
Configuring IPX Node Defaults Press Main Menu) to configure default IPX node parameters. IPX Node Defaults Parameters Parameter Internal Network Router Name Internal Network identifies the node to the IPX network. If fewer than 8 hex digits are entered, leading zeros will be added.
Page 231: Configuring Ipx Filter Definitions
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 filter permits or denies (depending on how it is configured) some or all of a specific type of IPX traffic across an interface.
Page 232: How Filter Masks Work
How Filter Masks Work Each IPX filter parameter except an associated mask. The mask determines (by the process described below) whether the filter will be applied to the packet. The binary bits of the mask will be "ANDed" (0+0=0, 0+1=0, 1+1=1) to the value, as in this example: Assume the value (hex) is follows:...
Page 233: Ipx Filter Parameters
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. Parameter Filter Name Network Address Value...
Page 234: Ipx Packet Filter Parameters
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 the node to which the filter will be applied. Socket Address Value is an IPX socket number that identifies a process or protocol.
Page 235: Ipx Rip Router Filter Parameters
= SAP packet = SPX (Sequenced Packet Exchange) packet = NCP (NetWare Core Protocol) packet = Propagated packet, used for NetBIOS (an IBM protocol that performs Destination Network Value is the network number of the destination node's network. The internetwork address is the network number followed by the socket number.
Page 236: Configuring Ipx Filter Applications
Configuring IPX Filter Applications IPX Filter Applications determine how filters will be used at the interface. To review existing applications, press Menu (or at the Configure Filter Definitions and Applications Menu. When prompted, enter: Interface number: Filter Category Direction Any other requested information, referring to Table 12-6. Figure 12-3 Typical IPX Filter Applications Record Up to 100 filters can be configured, displayed over 9 "pages"...
Page 237 Permit Determines whether the traffic defined by the denied passage across the interface. Filter "n" corresponds to the Configuring IPX Filter "n" s in the IPX Filter Definitions file. (See page 12-3.) Filter ID entries will be permitted or 12-9...
Page 238: Configuring Ipx Interfaces
Configuring IPX Interfaces An IPX interface allows an FRX/FRM to connect to a Novell IPX network. Press at the LAN Interfaces Configuration Menu (or display configured IPX interfaces. To configure an interface, press prompted, enter an identify the interface.) The display depends on the interface; the following figure shows an example, and Table 12-7 through Table 12-10 list the parameters for all interface types.
Page 239: Ipx Interface Parameters
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. Parameter Blocked Port Flag Interface Type Fr ame Type – Maximum Transmission Unit: IPX Networ k Address Priority...
Page 240 Interface Type: Supported types are: Ethernet, 802.5 (Token Ring) (FRX6000 only), X.25, and Frame Relay. Frame Type: TYPE_II SNAP Maximum Transmission Unit is the maximum frame size (in bytes) that can be transmitted or received over the IPX interface. Any frames larger than the Maximum Transmission Unit (MTU) will be dis- carded.
Page 241 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 between the periodic IPX RIP broadcasts from this interface. Periodic SAP Enabled determines whether the node will originate periodic IPX Service Advertising Protocol (SAP) messages from this interface (assuming SAP is enabled), to inform the network...
Page 242: Ipx Lan Interface Parameters
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 "keep- alive" messages on behalf of the client workstations. Novell servers periodically issue these messages to all clients, to determine whether each client is still available.
Page 243 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 is a period that an IPX connection can remain active with no traffic before the con- nection is cleared.
Page 244: Configuring Static Ipx Routes
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 Menu (or To configure a route, press prompted, enter: Type Route/Service Number...
Page 245 Network is the IPX network address of the network containing the node defined by Number Hops is the number of routers in a packet's path to the destination network. Transport Time is the time (in 55-millisecond units) that it will normally take a packet to reach the des- tination network if this route is used.
Page 246 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 the node address of the router that will forward a packet when this route is used.
Page 247: 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 Ethernet and Token Ring LANs. (For more infor- mation on bridging, refer to IEEE standard 802.1d.) Routing transmits each packet based on its level-3 address, while bridging transmits each frame based on its level-2 address.
Page 248: Required Configuration
Required Configuration To configure a Bridge in a Netlink FRX4000 or FRX6000, you must first configure the following in the node's database: Node parameters. See Chapter 3. This is general configuration that must be done no matter which protocols will be run in the node. Line Processor(s) that will contain the interface(s) to the user device(s), network and/or frame relay PVC, plus Line Interface Card(s) supporting the ports that will be the interfaces.
Page 249: Configuring Default Node-Wide Bridging Parameters
Configuring Default Node-Wide Bridging Parameters If one or more Bridge ports (interfaces) will be established in the local node, certain parameters must be configured to define bridge operation. Press LAN Default Parameters Menu (or prompted, enter: Virtual LAN ID Any remaining requested information, referring to Table 13-1 (on page 13-4). Con figu re Bridge/LLC 2 N ode Defaults A V irtual LA N ID B Bridge Enab led...
Page 250: Bridge Node Default Parameters
Bridge Node Default Parameters Parameter Virtual LAN ID Bridge Enabled Bridge Hello Time Bridge Max Age Bridge Forward Delay Bridge Aging Timer Bridge Priority Max Siz e Bridge Forwarding Table IP Bridging Enabled IPX Bridging Enabled SRB ID Default Ethernet Frame Type Bridge Enabled enables bridging in the node, implementing the spanning tree algorithm.
Page 251 Bridge Forward Delay is the time the bridge will wait after entering state, or after entering intended to assure that the tree topology is stable before it is put into use. The states are described under "Bridge Port Status" on page 17-15. Bridge Aging Timer determines how long learned addresses will be saved in the forwarding table before they are deleted.
Page 252: Configuring Bridge Filter Definitions
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. This can be helpful in such ways as limiting unwanted or inappropraite traffic onto LANs or WANs, or preventing access to certain devices for security purposes.
Page 253: How Filter Masks Work
How Filter Masks Work Most Bridge filter parameters are assigned values and associated "masks." The mask determines (by the process described below) whether the filter will be applied to the packet. The binary bits of the mask will be "ANDed" (0+0=0, 0+1=0, 1+1=1) to the value, as in this example: Assume the value (hex) is follows:...
Page 254: Bridge Mac Filter Parameters
Filter Name helps the user identify the filter. The name is not used by the software. 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.
Page 255: Bridge Protocol Filter Parameters
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. Parameter Filter Name Protocol ID Value Protocol ID Mask Filter Name helps the user identify the filter.
Page 256: Configuring Bridge Filter Applications
Configuring Bridge Filter Applications Bridge Filter Applications determine how filters will be used at the interface. To review existing applications, press figuration Menu (or cation, press prompted, enter: Bridge Port Number interface.) Filter Type Direction Any other requested information, referring to Table 13-7 (on page 13-11). Figure 13-3 Typical Bridge Filter Applications Record Up to 100 filters can be configured, displayed over ten "pages"...
Page 257: Bridge Filter Applications Parameters
Parameter Permit Filter "n" Permit Determines whether the traffic defined by the denied passage across the interface. Filter "n" corresponds to the Filter IDs in the Bridge Filter Definitions file (described earlier). Configuring Bridging Table 13-7 Bridge Filter Applications Parameters Valid Values 0–65535 Filter "n"...
Page 258: Configuring Bridge Ports
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 ports. To configure an interface, press prompted for an interface): If modifying an existing record, enter the interface number: If creating a new record, press available sequential interface number.
Page 259: Bridge Port Record Example
Configuring Bridging 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 C Port Priority D Path Cos t E Priority F LA N Card Option:: Figure 13-5 Bridge Port Record Example [A],[C],[F],[D] Nod e Name=nod e_xyz...
Page 260: Bridge Port Parameters
Bridge Port Parameters The following table lists parameters for all interface types. Explanations of some parameters follow the table. Parameter Interface Type Blocked Port Flag Port Priority: Path Cost: Pr iority LAN Card Port DLCI Format Bandwidth Allocation Group Host MAC Address Session Type LAN ID Interface Type...
Page 261 Port Priority will become the first octet of the lower the number, the higher the priority that the interface will be given among other interfaces in the spanning tree. Path Cost is the "cost" of transmitting a frame through the port onto the LAN. This cost, deter- mined by the speed of the LAN/port (the higher the speed, the lower the cost), will be added together with all other path costs on a specific link between source and desti- nation devices.
Page 262 DLCI matches the connection with an interface at the remote end of the link. Format is the RFC1490 encapsulation method used for bridged traffic. Note that specifying 8023_TB will add an Ethernet header to the frame, and 8025_SRB will add a Token Ring header.
Page 263: Chapter 14 Configuring Snmp
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 ports configured for IP, and LAN interfaces.
Page 264: Configuring Snmp System Defaults
Configuring SNMP System Defaults SNMP system defaults identify the local agent to the SNMP manager. Press SNMP Configuration menu to display the following screen: This information will be included in IPL messages to the SNMP agent, and will be stored for access via the MIB. 14-2 SN MP Defaults Menu A Sys tem Name...
Page 265: System Defaults Parameters
System Defaults Parameters Parameter System Name System Location System Contact System Name identifies the local FRX/FRM to the SNMP manager. System Location is generally the geographical address of the local node. System Contact identifies someone at the node site who can be contacted if there are issues. Configuring SNMP Table 14-1 SNMP System Defaults Parameters Although the SNMP standard for these fields is 256 characters, an FRX/FRM file length...
Page 266: Configuring A Community Table
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 included in each SNMP request that comes into a node.
Page 267: Community Table Parameters
Community Table Parameters Parameter Name Access Name is a community name, assigned by a network manager. Access determines what kind of access community members will have to SNMP messages. Configuring SNMP Table 14-2 Community Table Parameter Valid Values 0–24 characters Read only, Read/write Default Value none...
Page 268: Configuring Trap Routing
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 To configure an entry, press the corresponding " entry, select it, then press deleted one will move up one in the list.
Page 269: Trap Routing Parameters
Trap Routing Parameters Parameter Address Enabled Severity Address is an IP address to which all traps meeting the "enabled" and severity class criteria will be sent. Enabled determines whether or not traps meeting the severity class criterion will be sent to the specified address.
Page 270: Configuring A Model Number
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. To configure a model number, press from the Main Menu). The currently configured model will be displayed. If the [D], [D] value needs to be changed, press = FRX6000 Model 2...
Page 271: Operation
Section III Operation...
Page 273: Introduction To System Operation
Introduction to System Operation Once the database has been configured and the node has been brought on line, little operator intervention is generally necessary. The various functions that can be per- formed from the menus allow the operator to do such things as: Perform on-line software updates to nodes.
Page 274: 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 number is described in the chapter/appendix shown following the next higher level. B Operations A On-Line Node Operations A Remote Control...
Page 275 H Unquiesce a Range of Ports C On-Line Database Operations D Test X.25 Address Translation Templates E Re-Load Initialization to Async Console F IP Ping Connectivity Test G On-Line SDLC PU Operations A Disable an SDLC PU B Disable a Range of SDLC PUs C Enable an SDLC PU D Enable a Range of SDLC PUs H NetView Access...
Page 276 C SDLC PU Status D Bridge Status Displays E Frame Relay Backup Status F LLC/2 Session Status G IP Routing Table Display H IP ARP Table Display D Events E Statistics A Configure LP/Port Thresholds B Display LP/Port/Frame Statistics C Display IP Statistics D Display ICMP Statistics E Display IP Interface Statistics Display IPX Interface Statistics...
Page 277: 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 chapter describes these operations and more. Chapter 16 On-line Operations...
Page 278: On-Line Node Operations
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 async PAD port, through a network, into an X.25 port on the node to be controlled.
Page 279 Rebooting the Remote Node To reboot a node under remote control, follow this procedure at the controlling node: 1. Press 2. When asked: 3. Press Exiting Remote Control Press [F9] nodes will now be under local control. If either the controlling or the controlled node detects that the remote control link failed during a remote session, remote control will be terminated and each terminal's local main menu will be displayed.
Page 280: Remote File Transfer
Exiting Remote Control Press Node Name="NN" displayed in the upper right hand corner at the remote node, meaning that the remote node is now under local control (control at its own screen). If the controlled node detects that the remote control line failed during a remote control session, remote control will be terminated and the remote node's local Main Menu will be displayed on its screen.
Page 281: Remote Software Update
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. 1.
Page 282: Frx4000 Local File Backup
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;...
Page 283: Frx4000 Database Files
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 another selection or press File Name X25REC.DAT LPTYPE.DAT PROFILE.DAT ABVSUB.DAT APPDATA.BIN BRGFLTAP.DAT BRGFLTD.DAT BSCDSP.DAT COMPAR.DAT CUGPAR.DAT...
Page 284: Frx4000 Local File Restore
FRX4000 Local File Restore This operation copies files from the locally attached PC to the FRX4000. The pro- cedure can be used to install a software update into the FRX4000, or to restore database files that were backed up with the transfers one file at a time, and you must know the name(s) of the file(s) you want to transfer.
Page 285: On-Line Port Operations
On-Line Port Operations Press Disabling and Enabling Ports These operations disable or enable a single port or a sequential range of same-type ports (e.g., all SNA ports from LP 1, port 0 to LP 4, port 3). The operations can be useful for performing maintenance on ports without shutting down the node.
Page 286: Quiescing And Unquiescing Ports
Quiescing and Unquiescing Ports Quiesce ports (e.g., all async PAD ports from LP 1, port 0 to LP 4, port 3) to become disabled when there are no active connections on the port(s). Once disabled, the port(s) will remain disabled until enabled using the must be performed again if that feature is desired.
Page 287: On-Line Database Operations
On-Line Database Operations Press backup and restore operations. The list will differ among FRX/FRM devices. FRX4000 Options on an FRX4000 are: Remote Backup and Restore (Items A–C) Items A and B are used to back up a remote node’s database to a local FRX/FRM that has control of the remote node.
Page 288: Frx6000
FRX6000 Options on an FRX6000 are: Remote Backup and Restore (Items A–C) Item A is used to back up a remote node’s database to an FRX6000 that has control of the remote node. The operation requires first taking remote control ( Main Menu allows copying the database to a directory on the hard disk or a diskette.
Page 289: Frame Relay Module
Frame Relay Module Options on an FRM are: Remote Backup and Restore (Items A–C) Item A is used to back up a remote node’s database to an FRM that has control of the remote node. The operation requires first taking remote control ( Main Menu allows copying the database to a directory on the hard disk or a diskette.
Page 290: Reloading Auxiliary Console Initialization
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 is connected the Console/COM1 port, the initialization data will be sent. 16-14 at the Operations Menu (or [B], [E]...
Page 291: Ip Ping Connectivity Test
IP Ping Connectivity Test The IP Ping function sends packets to an IP host to determine whether the host is reachable. Press To begin the test: 1. Press 2. Make any desired change to the (seconds). This is an interval between transmission of packets. 3.
Page 292: On-Line Sdlc Pu Operations
On-Line SDLC PU Operations Press These operations disable or enable the link station connection between the node and a PU or a range of PUs (grouped by sequential port numbers). Select the desired operation from the menu. When prompted: If enabling or disabling a singl If enabling or disabling a range of PUs, enter: 16-16 at the Operations Menu to display the following:...
Page 293: Frx4000 Csu/Dsu Tests
FRX4000 CSU/DSU Tests To test the CSU/DSU port on an FRX4000, the port must first be disabled. If nec- essary, press the port. To run a CSU/DSU test, press sponding to the desired test: loop the pattern back to itself. test pattern to the remote device, which will loop the signals back.
Page 294: 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 primary becomes operational again. These automatic settings can be overridden via Frame Relay Backup Operations ( from the Main Menu).
Page 295: Chapter 17 Status And Statistics Displays
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
Displaying Node Status Press as well as most of the data shown on the Port Status Display (described on page 17-3). Information in this Display: Total Packets/Sec Total Connections Boot Time Status # of Ports 17-2 at the Status Displays Menu to display the overall performance of this node, Node Status Disp lay Pkt/Sec ^-----------^----------^-----------^----------^-----------^----------^-----------^-----------^ 384 512640...
Page 297: Displaying Port Status
Displaying Port Status Press Information in this Display are the LP and port numbers is the port type: Type 8023 is packets per second passing through the port. is the number of virtual connections currently in use. Conn# State Linkup Restarting Operational Disabled...
Page 298 Configured Dial Ready Quiesced Failed 17-4 The port is configured in the database, but the LP is not installed. The X.25 dial port is ready to transmit or receive calls. The port has been quiesced (described on page 16-10). Some modem controls are not present, and the physical link is down.
Page 299: Displaying Virtual Connections
Displaying Virtual Connections To display all physical and logical connections on a physical port, press 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 frame relay port. Figure 17-3 shows a frame relay port and Figure 17-4 shows a non-frame relay port.
Page 300: Virtual Connections Display On Non-Frame Relay Port
Undefined is the number of transmitted frames. Trans is the number of received frames. Recd is the number of discarded frames. Disc is the LP number (always tions), except for a remote control, file transfer, or alarm connection, in which case this number is always is the port number ( nection.
Page 301 Information in this Display State Subscriber Status and Statistics Displays is a sequence number used to identify the connection. is the logical interface: = PVC, is the direction of the connection related to the port: = Incoming, = Outgoing. is the logical channel number. means that call processing was successful and the connection Data_trans is in the data transmission state.
Page 302: Displaying Port Signals
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 The display will show the first four ports, and pressing four ports.
Page 303 , etc. TD(2) If displaying signal information for a remote subscriber, press (The display for a remote subscriber shows, by default, the current values at the time you entered the LP number.) On an FRX6000, pressing If the next LP is not configured, the message display.
Page 304: Monitoring A Line
Monitoring a Line The line monitor displays the control data and information data of traffic passing through a port. Press Port A message like the following will appear: Display Selection is: mode: Hexadecimal Level: 3, Selected Packets are: QData Call Clear Restart Reset Int Diag Unk only Options are F,H,L,M,S,D,Q,C,R,T,A,2,3,E and F3 to exit Press F to start Options...
Page 305: Line Monitor Display
[F3] The following figure shows an example of a display: On each line (see CCITT Recommendation X.25): The leftmost field shows the time, to hundredths of a second.The next field dis- plays reverse video.) The next field identifies the packet type. bit is turned on in the packet.
Page 306: Displaying Ipx Rip And Sap Tables
Displaying IPX RIP and SAP Tables RIP Table To display the contents of IPX RIP Table, press Menu (or Network Router Addr Hops TTime Intf SAP Table To display the contents of the SAP Table, press Menu (or Name Router Addr Type IntNw 17-12...
Page 307 12-16) will not age ( ). Interfaces with specified in TRUE their IPX Interface records for the will also be SAP Age Timer TRUE All others will be FALSE (Interface) is the time (in 55-millisecond units) that it will normally Intf take a packet to reach the destination network if this route is used.
Page 308: Displaying Sdlc Pu Status
Displaying SDLC PU Status To display the status of all PUs on an SNA port, press plays Menu. When prompted, enter the LP and port numbers. Possible states are: Active Inactive Never_Activated Pending_Contact Pending_Discontact Inoperational 17-14 SD LC PU Statu s Display for LP: 0 Port: 2 Station Ad dres sName State D1 Pud 1...
Page 309: Displaying Bridge Status
Displaying Bridge Status Bridge Port Status Press ational status of all Bridge ports in the node: If there are more Bridge ports than will fit on one screen, pressing will display other screens. Pressing for the ports on the above screen. Pressing screens (if there are more), and pressing Status and Statistics Displays at the Bridge Status Displays Menu to display the configurational and oper-...
Page 310 Information Shown on a Bridge Port Status Display Type/Format (if frame relay) frame format (Native LLC2, 8025_SRB, or 8023_TB, as configured in the Port record). Status Active status will be 6-16.) Bridge State state even if the physical port is inactive): Disabled leave this state through an operator re-enable or node IPL.
Page 311 Information Shown on a Bridge Port Statistics Display Type/Format DesignatedRoot DesignatedBridge DlyExceeded OutFrames InCfgShort OutCfgBPDU MTUExceeded InDiscards InTcnShort OutTcnBPDU FwdTrans OutCfgDrop InCfgBPDU OutOctets InFrames OutTcnDrops InTcnBPDU InOctets Status and Statistics Displays 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).
Page 312: Bridge Forwarding Table
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. As a frame is received, its source and destination MAC addresses will be added (if not already there) to the table.
Page 313 Possible Flags are: Static Dynamic LLC2 Native Discovery Pending Don't Forward Status and Statistics Displays The entry is fixed in the software. The entry was added when the address was received. The address is used for terminated LLC2 traffic. All SNA frames (identified by SAP multiples of 4) will be handled by LLC2, rather than bridged directly.
Page 314: Displaying Frame Relay Backup Status
Displaying Frame Relay Backup Status To display operational states of backup and backed-up frame relay DLCIs, press the Protocol Status Displays Menu (or from the following list and enter (when prompted) the RLP/port or group number: A Display States for all Backup DLCIs on a Port B Display States for all Primary DLCIs on a Port C Display States for all Backup DLCIs in a Group Possible states are:...
Page 315: Displaying Llc2 Session Status
Displaying LLC2 Session Status The status of any current LLC2 sessions can be displayed by pressing tocol Status Displays Menu (or following will be identified: SSAP DSAP SMAC HMAC State Call State SessType PUName Status and Statistics Displays from the Main Menu). For each session, the [C], [F], [F] SAP address of the source end.
Page 316: Displaying The Ip Routing Table
Displaying the IP Routing Table To display a list of active IP routes, press [C], [F], [G] route: Destination Gateway Netmask Flags Interface If the screen is filled with information, you will be asked whether you want to display more. 17-22 from the Main Menu).
Page 317: Displaying The Ip Arp Table
Displaying the IP ARP Table To display a list of active ARP (Address Resolution Protocol) table entries, press at the Protocol Status Displays Menu (or lowing will be displayed for each entry: IP Address MAC Address If the screen is filled with information, you will be asked whether you want to display more.
Page 318: Displaying Ip Interfaces
Displaying IP Interfaces To display a list of active IP interfaces, press [C], [F], [I] interface: Name Network Mask IP Address Rem Address Flags If the screen is filled with information, you will be asked whether you want to display more.
Page 319: Lp/Port/Frame Statistics Displays
LP/Port/Frame Statistics Displays Displaying LP Statistics Information in this Display Percentage of buffers in use Number of queued messages Received frames per sec (*10) Transmitted frames per sec (*10) Rejected frames per sec (*10) Status and Statistics Displays Although an FRX4000 has no LPs, LP functionality exists in the device. LP Statistics R ep ort LP: 0 Report I nterval (s ec): 5...
Page 320: Displaying Port Statistics
Retransmitted frames per sec (*10) Displaying Port Statistics Information in this Display Received frames per sec (*10) Transmitted frames per sec (*10) Retran frames per sec (*10) FCS errors/sec (*10) 17-26 is the number of frames retransmitted by the LP per second over the five-second reporting interval, multiplied by 10.
Page 321: Displaying Frame-Level Statistics
Logical rejects/sec (*10) Transmit error ratio Receive error ratio % Receive port util % Transmit port util Displaying Frame-level Statistics Frame-level statistics are frame relay (if the port is configured for frame relay) or X.25 level 2 statistics (per second, multiplied by 10). Status and Statistics Displays is the sum of Rejects and Frame Rejects received on the port per second over the five-second reporting interval,...
Page 322 Information in a Frame Relay Display DE/sec (*10) FECN/sec (*10) BECN/sec (*10) LMI/sec (*10) ANXD/sec (*10) Frames/sec (*10) DiscF/sec (*10) Information in a non-Frame Relay Display X.25 frame-level statistics are counts (per second, multiplied by 10) of these standard LAPB commands and responses: SABM DISC FRMR...
Page 323: Configuring Lp And Port Statistics Thresholds
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 Statistic level Port A menu like the following Port Statistics example will be displayed. A threshold is either a number or a percentage, depending on the statistic.
Page 324: Ip Statistics Displays
IP Statistics Displays Displaying IP Statistics IP statistics track traffic of IP datagrams through a node. Press Menu and, when prompted, enter a This is the frequency with which the screen will be redisplayed with the most recent values. Information in this Display Total Pkts Can't Forward Bad Checksum...
Page 325 Unkwn Protocol Pkt Too Small Pkts Delivered Bad Hdr Length Local Pkts Sent Bad Pkt Length Pkts Dropped Pkt Fragments Total Reasmbled Frag Time Out Pkts Fragmented Frag Dropped Frag Created Pkts Forwarded Can't Frag Status and Statistics Displays is the number of datagrams received using an unknown or unsup- ported protocol.
Page 326: Displaying Icmp Statistics
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 (seconds). (Default is Information in this Display ICMP Errors Pkt Too Short Old Too Short Bad Checksums Old ICMP...
Page 327 Responses Cnt Out Echo Reply In Echo Reply Out/In Dest Unrech Out/In Pkt Lost Out/In Redirect Out Echo In Echo Out/In Time Exceed Out/In Bad IP Hdr Out Time Req In Time Req Out Time Rsp Status and Statistics Displays is the total number of responses from this node to echoes and requests for timestamps, information, and address masks (all described later).
Page 328 In Time Rsp Out Info Req In Info Req Out Info Rsp In Info Rsp Out Mask Req In Mask Req Out Mask Rsp In Mask Rsp 17-34 is the number of responses received by this node to timestamp requests. is the number of requests to other entities in the IP path for the IP address of the network to which they are attached.
Page 329: Displaying Ip Interface Statistics
Displaying IP Interface Statistics IP Interface statistics track IP traffic over the node interface. Press Menu and, when prompted, enter: Interface Number Report Interval The display will be similar to the following figure, with left identifying the interface type. IP/WA N Statistics Disp lay Interface Numb er: 2 Report I nterval (s ec): 5 Curren t Time: 06/05/97 10:32:45...
Page 330: Ipx Statistics Displays
IPX Statistics Displays IPX statistics track IPX traffic through a node. Press when prompted, enter: Interface Number Report Interval There are three screens of IPX statistics. Pressing there is one), and pressing statistics are listed below. Information in this Display Pkts to Route Hops Too Large NetB Hops_2_Lrg...
Page 331 RIP G_Query Tx RIP N_Query Tx RIP G_Resp Tx RIP N_Resp Tx RIP Pkts Rcv RIP G_Query Rcv RIP N_Query Rcv RIP G_Resp Rcv RIP N_Resp Rcv RIP Aged Entries RIP Prd_Broadcasts RIP Upd_Broadcasts RIP INV Net Rcv RIP Worse Rt Rcv RIP Ukn G_Query RIP Ukn N_Query RIP Ukn G_Resp...
Page 332 SAP G_Resp Tx SAP N_Resp Tx SAP Pkts Rcv SAP G_Query Rcv SAP N_Query Rcv SAP G_Resp Rcv SAP N_Resp Rcv SAP Aged Entries SAP Prd_Broadcast SAP Upd_Broadcast SAP INV Net Rcv SAP Worse Rt Rcv SAP Ukn G_Query SAP Ukn N_Query SAP Ukn G_Resp SAP Ukn N_Resp NetB Pkts Rcv...
Page 333 WD Req Pkts Rcv WD Resp Pkts Rcv Serial Pkts Rcv Pkts Tx Tx Completions Pkts Rcv Tx Pkts Filtered Rcv Pkts Filtered Pkts Forwarded Echo Requests Rcv Echo Replies Rcv Err_Type Pkts Rcv Pkts Discarded Pkts_2_Large Rcv Major/Minor Version Rcv Header Error Ukn Sockets Rcv Rcv BSys Discard...
Page 334 R-SAP Ent Filter T-SAP Ent-Filter R-RIP Pkt-Filter T-RIP Pkt-Filter 17-40 is the number of received SAP entries discarded due to a filter. is the number of transmitted SAP entries discarded due to a filter. is the number of received RIP packets discarded due to a RIP router filter.
Page 335: Lan Card Statistics Displays
LAN Card Statistics Displays LAN Card statistics track traffic over the LAN interface. Press Menu and, when prompted, enter: LAN Card Number Report Interval Status and Statistics Displays on FRX4000 or FRM, . (Default is 5–65535 LA N C ard S tatis tics Display C ard Nu mber: 0 Type: Ethernet R ep ort Interval (sec): 5...
Page 336 Information in this Display Packets In/Out Bytes In/Out Multi-Cast In/Out Broadcast In/Out Frm Dropped In/Out Q Dropped In Dropped Timeout Errors In Ethernet-Specific Statistics Alignment Errors Xmt w/1 Coll Overrun Errors Xmt w/mul Coll Xmt/Deferral Xmt CD Heartbeat Not Xmt (Coll) Frm w/lost CS Late Collisions Underruns...
Page 337 Frequency Errors Frm with Aborts Act Mon Regen No Return Frms Underruns No Buff Avail A/C Errors Status and Statistics Displays is the number of frames received with signal frequency problems. is the number of frames that were aborted in mid transmission. is the number of times the active monitor is lost and regenerated.
Page 338: Frame Relay Utilization Statistics
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 Port DLCI Report Interval Figure 17-19 Frame Relay Utilization Statistics Display Information in this Display CIR In/Out Bc In/Out Be In/Out...
Page 339 Conf/Act Percentage Actual (bits/sec) Status and Statistics Displays Bandwidth Allocation Group. Configured and actual percentages of bandwidth used by traffic assigned to each group. Current bandwidth usage by traffic assigned to each group. 17-45...
Page 340 17-46 FRX/FRM 3.3 User Guide, Rev 04...
Page 341: 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 set in Node Defaults ( message file ERRMSG.TXT contains the format of events for message construction.
Page 342: Alarm Buffer
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 capacity specified by the parameter gestion , further events originating at that node are lost until the percentage of capacity specified by the parameter...
Page 343: Event Generation
Event Generation As soon as a message-generating event occurs, a Call Request is automatically sent to Alarm Output ID connection is activated.) All events are transmitted in raw data format to the collecting node, which constructs event messages and sends them to the display device(s). An internal timer limits the time events are kept in the system buffer if the system fails to bring the event connection up.
Page 344: Severity Levels For Snmp Trap Routing
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.
Page 345: Event Messages
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, FRM only) and port numbers.
Page 346 305. LP Msg Queued exceeded T:“n” C: “n” Severity: Meaning: Action: 306. LP Rcv Frm/Sec exceeded T:“n” C:“n” Severity: Meaning: Action: 307. LP Trn Frm/Sec exceeded T:“n” C:“n” Severity: Meaning: Action: 308. LP Rej Frm/Sec exceeded T:“n” C:“n” Severity: Meaning: Action: 309.
Page 347 311. Rcv Frm/Sec exceeded T:“n” C:“n” Severity: Meaning: Action: 312. Tran Frm/Sec exceeded T:“n” C:“n” Severity: Meaning: Action: 313. RTrn Frm/Sec exceeded T:“n” C:“n” Severity: Meaning: Action: 314. FCS Rej/Sec exceeded T:“n” C:“n” Severity: Meaning: Action: 315. Log Rej/Sec exceeded T:“n” C:“n” Severity: Meaning: Action:...
Page 348 317. Rcv Err Ratio exceeded T:“n” C:“n” Severity: Meaning: Action: 318. Rcv Port Usage exceeded T:“n” C:“n” Severity: Meaning: Action: 319. T rn Port Usage exceeded T:“n” C:“n” Severity: Meaning: Action: 377. LIC “n” Installed, Not Configured Severity: Meaning: Action: 378.
Page 349 400. Link Enabled Severity: Meaning: Action: 401. Link Disabled Severity: Meaning: Action: 402. Link Disconnected Severity: Meaning: Action: 403. Link Up Severity: Meaning: Action: 404. X.25 Link Failed Severity: Meaning: Action: 405. Restart with cc “n” dc “n” Severity: Meaning: Action: System Events The port has been enabled from the On-Line Port Operations Menu.
Page 350 406. Operational Severity: Meaning: Action: 407. Call Clr LCN = “n” cc = “n” dc = “n” Severity: Meaning: Action: 408. End of IPL Severity: Meaning: Action: 409. PVC is Up Severity: Meaning: Action: 410. PVC Reset Severity: Meaning: Action: 411.
Page 351 Meaning: Action: 413. PAD Link Failed Severity: Meaning: Action: 414. Beginning of Congestion Severity: Meaning: Action: 415. End of Congestion, “n” events lost Severity: Meaning: Action: 416. PAD Autocall Retries Exhausted Severity: Meaning: Action: 428. Duplicate of DLCI “n” on Port Severity: Meaning: Action:...
Page 352 Action: 432. Node Under Remote Control Severity: Meaning: Action: 433. Remote Control Released Severity: Meaning: Action: 434. Remote Control CXN Clr cc = “n” dc = “n” Severity: Meaning: Action: 435. LG Buffer MALLOC Problem PKTs Lost Severity: Meaning: Action: 436.
Page 353 439. Database Error, Access Restricted Severity: Meaning: Action: 440. Abrev Addr File Upd:ABVSUB.DAT Severity: Meaning: Action: 441. Async Init File Upd:ASYSETUP.DAT Severity: Meaning: Action: 442. BSC Device File Upd: BSCDSP.DAT Severity: Meaning: Action: 443. LP Config File Upd:LPTYPE.DAT Severity: Meaning: Action: 445.
Page 354 448. Rmt Subscriber File Upd:RSNSVC.DAT Severity: Meaning: Action: 449. Subscriber File Upd:SVCSUB.DAT Severity: Meaning: Action: 450. Statistic Def File Upd:STDPAR.DAT Severity: Meaning: Action: 451. Translation File Upd:XLTPAR.DAT Severity: Meaning: Action: 452. X.25 Default File Upd:X25REC.DAT Severity: Meaning: Action: 453. Alarm Enable File Upd:ERRMSG.TXT Severity: Meaning: Action:...
Page 355 456. Operator Logged into Node Severity: Meaning: Action: 457. Operator Logged out of Node Severity: Meaning: Action: 458. PAD Login File Upd:PADLOG.DAT Severity: Meaning: Action: 459. IP Route File Upd:IPRSUB.DAT Severity: Meaning: Action: 460. IP Interface File Upd:IPRSUB.DAT Severity: Meaning: Action: 461.
Page 356 464. LP Buf Usage Under Threshold Severity: Meaning: Action: 465. LP Msg Queued Under Threshold Severity: Meaning: Action: 466. LP Rcv Frm/Sec Under Threshold Severity: Meaning: Action: 467. LP Trn Frm/Sec Under Threshold Severity: Meaning: Action: 468. LP Rej Frm/Sec Under Threshold Severity: Meaning: Action:...
Page 357 472. Tran Frm/Sec Under Threshold Severity: Meaning: Action: 473. ReTran Frm/Sec Under Threshold Severity: Meaning: Action: 474. FCS Rej/Sec Under Threshold Severity: Meaning: Action: 475. Log Rej/Sec Under Threshold Severity: Meaning: Action: 476. Tran Err Ratio Under Threshold Severity: Meaning: Action: 477.
Page 358 480. Delete failed - nonexistent interface “n” Severity: Meaning: 481. No mem avail processing intface “n” Severity: Meaning: Action: 482. Can’t add interface “n” - IPadr err Severity: Meaning: Action: 483. Error adding interface “n” Severity: Meaning: Action: 484. Error modifying interface “n” Severity: Meaning: Action:...
Page 359 Action: 489. Route with destination “n,” mask “n,” router “n” deleted successfully Severity: Meaning: 490. Error adding route with destination “n,” mask “n,” router “n” Severity: Meaning: Action: 491. Route with destination “n,” mask “n,” router “n” added successfully Severity: Meaning: 500.
Page 360 505. LINK:Invalid MSG fc “n” - BPAD Severity: Meaning: Action: 513. BSCI:Invalid control block Severity: Meaning: Action: 514. BSCI:Invalid parameters Severity: Meaning: Action: 515. BSCI:Invalid port number or type Severity: Meaning: Action: 516. BSCI:Invalid message transfer Severity: Meaning: Action: 517. BSCI:Invalid circuit operations Severity: Meaning:...
Page 361 Action: 520. BSCI:Invalid CRC operations Severity: Meaning: Action: 521. BSCI:Invalid queue operations Severity: Meaning: Action: 522. BSCI:Invalid protocol operations Severity: Meaning: Action: 523. BSCI:Invalid CUA, DUA operations Severity: Meaning: Action: 524. Invalid Line Speed LP “n” Port “n” Severity: Meaning: Action: 530.
Page 362 Meaning: Action: 533. Exit Service Affecting Condition Severity: Meaning: Action: 534. DLCI “n” Frm Relay PVC Disconnected Severity: Meaning: Action: 535. DLCI “n” Received Bad Frame Severity: Meaning: Action: 536. DLCI “n” No Response to STATUS ENQ Severity: Meaning: Action: 537.
Page 363 540. DLCI “n” Not Configured Severity: Meaning: Action: 541. DLCI “n” Frame Relay Header Invalid Severity: Meaning: Action: 542. DLCI “n” PVC does not exist Severity: Meaning: Action: 543. DLCI “n” Frame Discarded - CIR Severity: Meaning: Action: 545. DLCI “n” frame relay PVC deleted Severity: Meaning: Action:...
Page 364 561. LLC Interface File Upd:LLC2IPAR.DAT Severity: Meaning: Action: 562. LLC Host File Upd:LLC2HPAR.DAT Severity: Meaning: Action: 563. LLC LAN Card File Upd:LANPAR.DAT Severity: Meaning: Action: 564. IPX Filter Def File Upd:IPXFPAR.DAT Severity: Meaning: Action: 565. IPX Filt App File Upd:IPXFLTAP.DAT Severity: Meaning: Action:...
Page 365 705. SDLC Stn rcvd FRMR, IFLD invalid Severity: Meaning: Action: 706. SDLC Stn rcvd FRMR, Nr invalid Severity: Meaning: Action: 707. SDLC Stn rcvd FRMR, Ifld too long Severity: Meaning: Action: 708. SDLC Rem Stn sent Invalid Command Severity: Meaning: Action: 709.
Page 366 Meaning: Action: 713. S DLC XID Retries exhausted Severity: Meaning: Action: 714. SDLC Rem Stn sent FRMR - no reason Severity: Meaning: Action: 715. SDLC Remote RNR limit exceeded Severity: Meaning: Action: 717. SDLC Rem Tx Frame exceeds MAXDATA Severity: Meaning: Action: 718.
Page 367 722. SDLC No External CLock Severity: Meaning: Action: 736. SDLC LLC/2 Remote Link Stn lost Severity: Meaning: Action: 737. LLC/2 DM Received Severity: Meaning: Action: 738. LLC/2 SABME Received when open Severity: Meaning: Action: 739. LLC/2 FRMR Rcvd, Invalid Command Severity: Meaning: Action:...
Page 368 742. LLC/2 FRMR Rcvd, IFLD too long Severity: Meaning: Action: 743. LLC/2 FRMR Rcvd, Invalid Command Severity: Meaning: Action: 744. LLC/2 FRMR Sent, IFLD not permitted Severity: Meaning: Action: 745. LLC/2 FRMR Sent, Invalid Nr Severity: Meaning: Action: 746. LLC/2 FRMR Sent, IFLD too long Severity: Meaning: Action:...
Page 369 Meaning: Action: 761. SDLC Transmit link error Severity: Meaning: Action: 762. SDLC Link Stn rcv FRMR, Unexp. IFLD Severity: Meaning: Action: System Events Self-explanatory. The line will be shut down and re-establishment will be re-tried one every minute. None. Self-explanatory. The line will be shut down and re-establishment will be re-tried later.
Page 371: Appendices
Section IV Appendices...
Page 373: Appendix A Subscriber Addressing
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 and acceptance of a Clear Request. A PVC is established auto- matically on power-up of both subscribers (assuming both subscribers' nodes are oper- ational).
Page 374: Search Order For Subscriber Addresses
The following figure shows an example of wildcard addressing. This configuration requires Port and Subscriber ID records in node 1 for: Subscriber Subscriber In node 2, LP, Port, and Subscriber records must be configured for: Subscriber Subscriber Subscriber Subscriber If subscriber , node 1 searches for a match, finds 12304 2, LP1, port 0, where node 2 reads the full called address in the packet and routes it...
Page 375: Appendix B Hunt Group Example
Here is an example of how the hunt group function works, using the algorithm . The routing path process will calculate a loading factor based on LCN With Thruput the number of LCNs in use and the line speeds for each Call Request received. The method is proprietary, but is described generally here.
Page 376 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 fill up their LCNs they are excluded from getting new calls. If all operational lines have all LCNs in use, new calls will be cleared.
Page 377: 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: 2. If the port is configured (in the Port record) to not require login, go to step 3. If login is required, enter (when prompted) the login password defined in the Async PAD Login record (described on page 10-7).
Page 378: Async Terminal Commands
Async Terminal Commands The following commands can be entered in type help [Enter] STAT PAR? n1,n2,n3 1st parameter, SET? n1:m1,n2:m2,n3:m3 parameter, PROF RESET SET n1:m1,n2:m2,n3:m3 1st parameter, HELP – Same as [Gnn], [Z], [Y], [R], [N] Request packets (unless they are specified in autocall Call Requests): [Gnn] Port and calling addresses.
Page 379: Placing A Call From An Async Terminal
Placing a Call from an Async Terminal One way to place a call is simply to enter the calling address (subscriber ID) of the destination DTE. (There must be a record for that subscriber ID.) User data and/or facilities (in any combination) can be included, as described below. To place a call using facilities and user data, enter the data in the format: f,f,f-addressDdata or f, f, f-addressPdata is the letter(s) representing the desired facility(s):...
Page 380: Async Pad Service Signals
Async PAD Service Signals (Asterisk) – is normally the PAD prompt character. “nnnnn” COM whose ID is ALREADY CONNECTED be made until the current call is cleared. AUTOCALL INITIATED BY SUBSCRIBER “nnnmm” AUTOCALL RETRIES EXHAUSTED-RETURN TO COMMAND STATE autocall retry timer has expired. CALL CLEARED CALL TIMED OUT call setup request within a certain time.
Page 381 OVERRUN ERROR characters are being received by the port, resulting in loss of characters. Enabling XON-XOFF flow control (async PAD profile parameter 5) usually corrects this error. – indicates that a “page wait” condition (async PAD profile parameter 22) has PAGE occurred.
Page 382: Error Codes Sent To Async Pad Port
Error Codes Sent to Async PAD Port Clearing Causes Reset Causes Number Busy Network Congestion Invalid Facility Access Barred Local Procedure Error Remote Procedure Error Not Obtainable Out of Order Invitation to Clear DTE Originated DTE Originated Out of Order Remote Procedure Error Local Procedure Error Network Congestion...
Page 383: Appendix D Cause And Diagnostic Codes
Appendix D Cause and Diagnostic Codes...
Page 384: Cause Codes
Cause Codes Clearing Causes The clearing cause recorded in a call packet provides a high-level indication of why the call was cleared and where the error occurred (e.g., error by the source user, or internal network error). For example, when the diagnostic code indicates that a pro- tocol error occurred, the clearing cause might indicate that the error was committed by the destination user (i.e., remote procedure error).
Page 385: Restart Causes
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 port was restarted. From DCE Hex. Cause and Diagnostic Codes Incompatible destination Network out of order (PVC only) From DTE...
Page 386: Diagnostic Codes
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 No additional Information Invalid P(s) Invalid P(r) Packet Type Invalid (Restart Transfer Phase) Packet type Invalid for State r1 Packet type Invalid for State r2...
Page 387: Sna Codes
Hex. Dec. Description SNA Codes Hex. Dec. Cause and Diagnostic Codes Call set up, call clearing or registration problem Facility/Registration code not allowed Facility parameter not allowed Invalid called address Invalid calling address Invalid facilty/registration length Incoming call barred No LCN available (might mean that maximum number of connections, 1024, was reached) Call collision Duplicate facility requested...
Page 388: Frx/Frm-Specific Codes
FRX/FRM-Specific Codes Hex. Dec. Description Call cleared because of call looping Call cleared because port is quiesced Connection rejected (transient condition) FRX/FRM 3.3 User Guide, Rev 04...
Page 389: 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 changing parameters in the node. The service point in the FRX/FRM connects to the NetView host via an LLC2 session (over LAN or frame relay), which is established at node IPL.
Page 390: Local Netview Access
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 NetView.
Page 391: Supported Commands
Supported Commands The syntax of a RUNCMP SP=OLXPu, APPL=NVOperid, command where: OLXPu NVOperid command command FRM operator performing local access operations. Supported commands are described over the next few pages. Display Commands DISPLAY ID Function: Displays the active/inactive status of specified PUs. Command: DISPLAY LINES Function: Displays the active/inactive status of specified lines.
Page 392: Vary Commands
Vary Commands VARY ACT Function: Changes the desired status of specified PUs to an active state. Command: VARY INACT Function: Changes the desired status of specified PUs to an inactive state. Command: Modify Commands MODIFY CONFIG Function: Modifies one or more configuration parameters for a specified PU, or Command: V NET,ACT, ID={linename[,A|U|C],puname} Options:...
Page 393 Command: NetView Management Corresponding Parameter Keyword(s) in FRX/FRM NODATA PAUSE No Data Poll Period NORESP ACTIVETO No Resp Poll Period GENCLCK CLOCKING Generate Clock RCVCLOCK Receive Clock (TT) from DTE Y/N ISTATUS Blocked Port Flag NRZI SPEED Line Speed Keywords when the PU is being modified are listed below. The parameters are described in Chapter 8.
Page 395: Appendix F Ascii Character Table
ASCII Decimal Character Value “ & (apostrophe) (asterisk) Appendix F ASCII Character Table Octal Ctrl Key Value Value Combination [Ctrl] [Space] [Ctrl] [A] [Ctrl] [B] [Ctrl] [C] [Ctrl] [D] [Ctrl] [E] [Ctrl] [F] [Ctrl] [G] [Ctrl] [H] [Ctrl] [I] [Ctrl] [J] [Ctrl] [K] [Ctrl] [L] [Ctrl] [M]...
Page 396 ASCII Character (comma) (hyphen) (period) < > (caret) (underline) (single quote) Decimal Octal Value Value Value FRX/FRM 3.3 User Guide, Rev 04...
Page 397 ASCII Character (pipe) (tilde) ASCII Character Table Decimal Octal Value Value Value...
Page 399: Appendix G Menu Structure
Items farthest to the left and underlined (e.g., entries on the Main Menu. Configuration Configure Node Configure Password Configure Time and Date Configure Node Defaults Configure SNMP Parameters Configure System Defaults Configure Community Table Configure Trap Routing Configure Model Number Configure LAN Default Parameters Configure IP Node Defaults Configure Bridge/LLC-2 Node Defaults...
Page 400 Operations Configure LAN Interfaces Review IP Interfaces Configure IP Interfaces Review Bridge Ports/LLC2 Interfaces Configure Bridge Ports/LLC2 Interfaces Review IPX Interfaces Configure IPX Interfaces Configure BSC Devices Review BSC Device Configuration Configure BSC Devices Configure Connections and Routing Paths Review Subscriber IDs Configure Subscriber IDs Review Abbreviated Addresses Configure Abbreviated Addresses...
Page 401: Port Status Display
Status Displays Events Statistics Reports Menu Structure CSU/DSU Tests Self Test Pattern Generation Test Frame Relay Backup Operations Initiate Switching Primary DLCI Over to its Backup Initiate Switching DLCI Back to the Primary Node Status Port Status Virtual Connections Port Signals Line Monitor Protocol Status IPX RIP Table Display...
Page 402 FRX/FRM 3.3 User Guide, Rev 04...
Page 403 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 shielded twisted pair and the MAC (medium access control) layer as Token Ring.
Page 404 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. stands for “bits per second,”...
Page 405 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. stands for “data circuit-terminating equipment,” which provides the functions nec- essary for communication operations between the end-user device (see “DTE”) and the network.
Page 406 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 “alarm.” Fragment is an IP datagram that is a piece of a larger datagram, the larger one having been seg- mented to allow it to pass through a network that did not support the larger datagram.
Page 407 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- porting the TCP/IP protocol.
Page 408 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 a type of LLC that requires establishment of a connection before information can be exchanged.
Page 409 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. stands for “packet assembler/disassembler,”...
Page 410 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. Router is a device that receives data and routes it based on decisions made concerning the most desirable path.
Page 411 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.
Page 412 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 data networks. XPAD is an integral (to an FRX/FRM) transparent SNA PAD.
Page 413 # of Beginning Sync Char ... 9-7 # of Beginning Sync Chars ... 9-13 # of Trailing Pad Characters ... 9-7 # of Trailing Pad Chars ... 9-14 1st/2nd/etc. Path Configured ... 6-31, 7-16, 8-15, 9-18, ... 10-17 Abbreviated Address, configuring ... 10-18 Abort (F10)...
Page 414 Clearing causes... D-2 async... C-6 Collecting Node... 3-7 Collecting Node ID ... 3-6 Collecting Node Pwd (password)... 3-6 Com. Port Parity ... 3-7 Com. Port Stopbit ... 3-7 Com. Port Thruput... 3-7 Command mode (async terminal) ... C-1 Committed Burst Size ... 6-34 Committed Burst Size (In/Out) ...
Page 415 Event collection, configuring ... 18-1 Event generation ... 18-3 Event messages ... 18-5 Events ... 18-1 severity levels... 18-4 Events, displaying ... 18-3 Excess Burst Size ... 6-34 Excess Burst Size (In/Out) ... 6-19 Exiting a menu ... 1-17 F1... 1-17 F10...
Page 416 Internal Network ... 12-2 Intervening Networks ... 12-18 IP addressing ... 11-1 IP ARP table, displaying ... 17-23 IP Bridging Enabled ... 13-5 IP gateway ... 11-2 IP Interface ID ... 11-11 IP Interface statistics, displaying ... 17-35 IP interfaces configuring ...
Page 417 MaxIn ... 8-26 Menu operations ... 1-15 Menu structure... G-1 Metric Count ... 11-9 Min Congestion ... 3-8 Model number, configuring... 14-8 Modulo ... 6-24, 7-5 Monitoring a line... 17-10 Moving a database record... 1-18 Multidrop... 9-7 N1 Polling Count... 6-17 N2 ...
Page 418 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 ... 10-8 Profile, async PAD... 10-2 ProtEnab ... 6-36 Protocol Frame Relay Module... 4-15 FRX4000 ... 4-4 FRX6000 ... 4-9 Protocol ID Value...
Page 419 Subscriber Name ... 6-30, 7-15, 7-24, 8-14, 9-17, 10-16, ... 10-20, 11-11 SVC Idle Timer ... 11-7, 12-15 SVC Retry Timer ... 11-7, 12-15 Switch settings on RLP ... 4-7, 4-13, 5-3 Switchback Timer ... 6-20 Switchover Timer ... 6-20 System Contact ... 14-3 System Defaults, SNMP...
Page 420 X.25 address translation templates... 7-17 X.25, configuring ... 7-1 X.3 Line Speed ... 10-11 ZMODEM ... 16-6 Index-8 FRX/FRM 3.3 User Guide, Rev 04...

This manual is also suitable for:

Frx4000 Frx6000 Mmac-plus 9f116-01 Mmac-plus 9w111-08 Mmac-plus 9g426-02 Mmac-plus 9t101-04 ... Show all

Cabletron Systems SmartSwitch 6000 User Manual

Section I

Introduction

Chapter 1 Introduction to Netlink Frame Relay Access Devices

Configuration

Chapter 2 Introduction to Database Configuration

Chapter 3 Configuring Node Parameters

Chapter 4 Configuring Cards and Protocols

Chapter 5 Configuring Serial Ports

Chapter 6 Configuring Frame Relay

Chapter 7 Configuring

Configuring X.25

Chapter 8 Configuring SNA

Chapter 9 Configuring BSC

Chapter 10 Configuring Async Ports

Chapter 11 Configuring IP

Chapter 12 Configuring IPX

Chapter 13 Configuring Bridging

Chapter 14 Configuring SNMP

Operation

Chapter 15 Introduction to System Operation

Chapter 16 On-Line Operations

Quick Links

User Guide

Related Manuals for Cabletron Systems SmartSwitch 6000

Summary of Contents for Cabletron Systems SmartSwitch 6000