                  IBM ROUTEXPANDER/2 VERSION 2.0.2

  CONTENTS
  
  LICENSE INFORMATION and TRADEMARKS

  CHAPTER 1.  WHY README FIRST?

  CHAPTER 2.  NEW FEATURES IN ROUTEXPANDER/2 VERSION 2.0.2
              3 Port Bridge Support
              9 Port Bridge Support
              IBM Auto LANStreamer MC 32 Adapter
              Frame Relay Data Compression
              Remote Installation
              Enhanced Bridge Filters
              Tools

  CHAPTER 3.  INSTALLATION AND USAGE
              Installing a New Release of RouteXpander/2
              On-line Help Messages
              Sample Bridge Filter Files
              WAC Diagnostics Available on RouteXpander/2 3rd Base Diskette

  CHAPTER 4.  NEW TOOLS FOR PROBLEM DETERMINATION AND TRACING
              Wide Area Connector Adapter Status Display (WACSTAT.EXE)
              Frame Relay Status Display (NETSTATF.EXE and FRNOTEBK.EXE)
              Bridge Counter Display (BDMPCNT.EXE)
              IPX Router Status Display (NETSTATX.EXE)
              Token Ring Network Connectivity Test (OS2PING.EXE)
              Tracing for Troubleshooting and Filter Development (GSDTRACE.EXE)

  CHAPTER 5.  NOTES ON RELATED PRODUCTS
              PS/ValuePoint Flash PROM Levels
              IBM Token Ring 16/4 Shared RAM Adapter:  Use Size of 64K or 32K
              IBM 16/4 ISA Token Ring Network Adapter - Switch Settings
              IBM 16/4 ISA Token Ring Network Adapter - Example Configuration
              IBM Wide Area Connector for ISA Bus -  Switch Settings
              IBM Wide Area Connector for ISA Bus -  Example Configuration

  CHAPTER 6.  ROUTEXPANDER/2 KNOWN PROBLEMS
              OS/2 Warp
              MPTS/2
              WAC
              RouteXpander/2 Nodes with IPX Lockup using Novell Server 3.12
              RouteXpander/2 Remote Installs: SRVIFS Must Be LAST in CONFIG.SYS
              RouteXpander/2 Console's "Keys Help" Not Available
              RouteXpander/2 Console's Message Log's "Save as..." Unreliable
              RouteXpander LNM Support/2 Extraneous Alert

***********************************************************************
  LICENSE INFORMATION
  
  The licensed program described in this document and all licensed material
  available for it are provided by IBM under terms of the Agreement for IBM
  Licensed Programs.

  Any reference to an IBM licensed program in this document is not intended
  to state or imply that only IBM's program may be used.

  IBM may have patents or pending patent applications covering subject
  matter described in this document.  The furnishing of this document does
  not give you any license to these patents.  You can send inquiries, in
  writing, to the IBM Director of Commercial Relations, International
  Business Machines Corporation, Purchase, New York, 10577.

  References in this publication to IBM products, programs, or services do
  not imply that IBM intends to make them available in all countries in
  which IBM operates.

  This document is not intended for production use and is furnished as is
  without any warranty of any kind, and all warranties are hereby
  disclaimed including the warranties of merchantability and fitness for a
  particular purpose.

  TRADEMARKS
  
  The following terms, denoted by an asterisk (*) at their first
  occurrences in this publication, are trademarks of IBM Corporation in the
  United States or other countries:

  Ŀ
   IBM                  PS/2                 OS/2                
  Ĵ
   ValuePoint           Presentation         PS/2                
                        Manager                                  
  

  The following terms, denoted by a double asterisk (**) at their first
  occurrences in this publication, are trademarks of other companies:

  TRADEMARK                      OWNED BY
  NDIS                          3Com Corporation/Microsoft Corp.

************************************************************************
  CHAPTER 1.  WHY README FIRST?
  
  This document contains important information about the IBM(*)
  RouteXpander/2 Version 2.0.2 product.  Information that has become
  available since the production of the RouteXpander/2 User's Guide and
  Reference documents has been included in this README.TXT file.

  You should familiarize yourself with the contents of this document before
  attempting to install and use this product.

  This ASCII text version of this document, named README.TXT, is found
  in the \GSD directory on the disk drive upon which RouteXpander/2 is
  installed.

************************************************************************
  CHAPTER 2.  NEW FEATURES IN ROUTEXPANDER/2 VERSION 2.0.2
  
  RouteXpander/2 Version 2 Release 0.2 contains several enhancements to
  previous releases:

  3 Port Bridge Support
  
  The RouteXpander/2 Version 2.0.2 Base Program supports up to three ports
  for source-route bridging.  Previous releases supported two ports for
  source-route bridging.

  As in previous releases, the RouteXpander/2 Version 2.0.2 platform allows
  for multiport routing.  With the IPX Router provided with the IBM
  RouteXpander V2.0.2 Base Program, one can now configure up to nine ports
  for IPX routing.  With IBM's TCP/IP for OS/2 program, one can configure
  up to eight ports for IP routing.  And, with IBM's Communications
  Manager/2 (CM/2), one can configure SNA and APPN support for any
  combination of two WAN (frame-relay or leased-line or X.25) or LAN ports,
  plus two SDLC ports.  (The number of ports supported by these products
  may change in future releases.  Please contact your IBM representative
  for the latest information.)

  9 Port Bridge Support
  
  RouteXpander/2 Version 2.0.2 is the first release of the RouteXpander/2
  Base Program that can be used with the optional RouteXpander Multiport
  Support/2 program.  With the RouteXpander Multiport Support/2 program,
  RouteXpander/2 supports up to nine ports for source-route bridging.
  These nine ports can be composed of any combination of eight WAN ports
  and two LAN ports.

  IBM Auto LANStreamer MC 32 Adapter
  
  The IBM Auto LANStreamer MC 32 Adapter is supported for both bridging and
  routing with RouteXpander/2 Version 2.0.2.  RouteXpander/2 can share this
  high performance token-ring adapter with other programs such as the IBM
  LAN Server.

  Frame Relay Data Compression
  
  RouteXpander/2 Version 2.0.2 supports data compression for point-to-point
  leased lines and frame-relay networks.  (This is in addition to data
  compression for X.25 traffic, which first became available with
  RouteXpander/2 Version 2.0.)  See "Data Compression for Communications"
  in chapter 18 of the RouteXpander/2 User's Guide and Reference
  (SC30-3671-01) for an explanation of the data compression available for
  RouteXpander/2.

  Remote Installation
  
  A remote installation feature has been added to the RouteXpander/2
  install process which allows you to remotely install RouteXpander/2
  on your work stations.  Any OS/2 workstation that has NTS/2 NetBIOS
  support can be used as a data repository.  (Note that, contrary to what
  is written in the "IBM RouteXpander/2 Version 2 Release 0.2 User's Guide
  and Reference," you do NOT need to have IBM LAN Server installed.)

  Enhanced Bridge Filters
  
  The filtering capabilities of the source-route bridge have been enhanced
  with the addition of outbound filters and automatic filters.  Outbound
  filters provide control of frame forwarding with respect to the
  destination bridge port.  Automatic filters provide filtering of frames
  used by certain protocol routers, when those routers are present in the
  same node as the source-route bridge.  See the IBM RouteXpander/2 User's
  Guide and Reference, Chapter 15, "RouteXpander/2 Bridge Filters" on page
  15-1 for more information on this topic.

  Tools
  
  Several useful software tools are located in the \GSD\TOOLS subdirectory.
  These tools can provide real-time status information as well as assist in
  troubleshooting network and machine problems.  These tools are provided
  on an as-is basis.  See Chapter 3 of this README.TXT for a complete
  description.

**************************************************************************
  CHAPTER 2.  INSTALLATION AND USAGE

  Installing a New Release of RouteXpander/2
  
  Installing a new release of RouteXpander/2 is performed exactly like an
  initial installation of RouteXpander/2.  Insert the RouteXpander/2, Disk
  1, into the floppy drive, and type 'A:\INSTALL' from the 'C:\>' prompt.
  After the main panel is displayed, select the 'INSTALL' button to install
  the new release.  Ignore the 'SERVICE' button, this is used only for
  installing Corrective Service Diskette (CSD) patches.  (RouteXpander/2
  Version 2.0.2 is not considered a CSD of RouteXpander/2 Version 2.0.)
  After the 'INSTALL' button is pressed, a message will then appear:

     "A previous copy of RouteXpander/2 Install and Configuration
      initialization file was found.  Select 'Yes' to create a new
      configuration file, or 'No' to use the existing file, or
      'Cancel' to terminate the installation program."

  Unless you are changing the configuration of the RouteXpander/2, select
  'No' (which is the button highlighted by default) to use the existing
  initialization file.  If 'Yes' is selected, you will need to reset the
  Console options before rebooting the workstation.

  After all of the installation process is complete, reboot the
  workstation.

  Reconfiguration of RouteXpander/2 using LAPS, MPTS/2, or the X.25
  configuration program is not required.

  On-line Help Messages
  
  The RouteXpander/2 2.0.2 User's Guide and Reference's Chapter 17,
  "RouteXpander/2 Messages and SNA Alerts" (under the first subsection,
  "RouteXpander/2 Messages," starting on page 17-2), lists all of the
  RouteXpander/2 help messages known at the time of the document's
  production.  To receive the most up-to-date help for RouteXpander/2,
  three on-line facilities exist.  These on-line facilities supplement and
  provide alternatives to the hardcopy User's Guide and Reference that was
  supplied with your product:

    (1) For messages found in the "Message Log" window of the
        RouteXpander/2 Console, point to the displayed message for which
        you want more information and double-click the left mouse button.
        This will display a help window with information specific to the
        message to which the mouse is pointing.

    (2) Use the OS/2 HELP command.  Thus, for instance, if in LANTRAN.LOG
        or in the Console's Message Log you find a message with the message
        number "GSD1046," you can go to any OS/2 command-line prompt (in
        either an OS/2 full-screen session or an OS/2 window) and type:

               HELP GSD1046

        and information specific to the identified message will be
        displayed.  Note that this only works for warnings and error
        messages, not informational messages.

    (3) A list of all RouteXpander/2 messages has been provided and
        supersedes messages documented in the RouteXpander/2 User's Guide
        and Reference.  To view these message, you can double-click on
        the "RouteXpander/2 Messages" icon in the "RouteXpander/2"
        folder on your OS/2 Desktop (placed there during RouteXpander/2
        installation), or, at an OS/2 prompt, type:

               VIEW \GSD\GSDMSG.INF

        Use can use your mouse or keyboard or both to navigate through this
        RouteXpander/2 Message Reference.  The RouteXpander/2 Message
        Reference supplies help for all RouteXpander/2 messages, including
        informational, warning and error messages.

  Sample Bridge Filter Files
  
  In the User's Guide, Chapter 15, "RouteXpander/2 Bridge Filters", a
  number of example filters are shown and discussed.  Additional bridge
  filter files can be found in the subdirectory \GSD\SAMPLES\FILTER.  These
  filters provide helpful examples for understanding the basic types of
  bridge filters.

    GSDSRB.IP    IP filter (automatically installed if IP routing configured)
    GSDSRB.IPX   IPX filter (automatically installed if IPX routing configured)
    GSDSRB.MC1   Masking MAC addresses
    GSDSRB.MC2   Multiple source MAC addresses
    GSDSRB.MC3   Using the the same MAC address for source and destination
    GSDSRB.NB    Requester communication with specific LAN Servers
    GSDSRB.NB2   Generic NetBIOS names using wildcard '*'
    GSDSRB.NB3   Requester to server only communication
    GSDSRB.NB4   Only one requester allowed to cross bridge

  WAC Diagnostics Available on RouteXpander/2 3rd Base Diskette
  
  For ease of access, the latest WAC Diagnostics have been placed on the
  third diskette of the base RouteXpander/2 product.  If, after installing
  a WAC adapter, your machine traps on power-up, it may be due to a bad
  WAC card.  To check, insert the third RouteXpander/2 (WAC Diagnostics)
  diskette into your machine and reboot.  See the "Diagnostics" section of
  the "IBM Wide Area Connector: Installation and Testing Instructions"
  manual, which came with your WAC adapter, for more information.


  ***********************************************************
  CHAPTER 4.  NEW TOOLS FOR PROBLEM DETERMINATION AND TRACING

  RouteXpander/2 comes with the following software programs that are useful
  in displaying network status and problem determination.

     WACSTAT.EXE  - displays IBM WAC-adapter status in an OS/2 Window
     NETSTATF.EXE - displays frame-relay status in an OS/2 Window
     FRNOTEBK.EXE - displays frame-relay status in a PM Window
     BDMPCNT.EXE  - displays bridge counters in an OS/2 Window
     NETSTATX.EXE - displays IPX-router status in an OS/2 Window
     OS2PING.EXE  - tests connectivity of a bridged network (OS/2 Window)
     GSDTRACE.EXE - post-processor of OS/2 TRACEFMT output

  Aside:  These tools were found to be very useful during the development and
  testing of RouteXpander/2.  Therefore the developers of RouteXpander/2 felt
  that is was important to pass these applications onto you, the customer.
  These tools are provided as is.  No documentation is provided for these
  tools, except for the information contained within this README.TXT file.
  Reported problems pertaining to any of the above tools will be fixed on a
  "as time is available" basis.

  Tools that run in OS/2 Windows can be accessed from remote sites using
  telnet.  (TCP/IP for OS/2's telnetd must be installed and configured on the
  target RouteXpander/2 node for this capability.)

  When starting the following programs:  wacstat, netstatf, frnotebk, and
  netstatx, RouteXpander/2's Network Management Agent must not be running.  If
  the Network Managment Agent is running, one of the following messages will
  be displayed:

  "WARNING!!!
   The RouteXpander/2 Network Management Agent is currently running.
   Network Management Agent must be stopped before running <program>.  If
   you're running RouteXpander/2 V2.0, go to the 'Components' window and stop
   the Network Management Agent.  If you're running RouteXpander/2 V1.0, find
   the NMA window and stop it by typing Ctrl-C."

                     or if running a PM application

  "The WAN device driver has already been opened by another application."

  If either of these messages are displayed, stop the Network Management Agent
  and retry the command.

  If you do not require SNMP management, then you can configure your
  RouteXpander/2 node so that the RouteXpander/2 "Network Management Agent"
  component is not automatically started when your RouteXpander/2 Console is
  started.  (Disabling the automatic starting of the Network Management Agent
  facilitates the execution of various tools described in this section.)
  Double-click on the "RouteXpander/2 Configuration" icon located in the
  RouteXpander/2 folder.  Click on the "Configuration" button and then the
  "Console" button on the following screen.  A dialog window will appear with
  three autostart console check boxes:

               _  Bridge Manager
               _  X.25 Support
               _  Network Management Agent

  Deselect the "Network Managment Agent" check box and then exit.  The next
  time the RouteXpander/2 console is started, the Network Management Agent
  will not be automatically started.  See "Chapter 11.  The RouteXpander/2
  Console and Local Management" in the RouteXpander/2 User's Guide for more
  information.

  Wide Area Connector Adapter Status Display (WACSTAT.EXE)
  
  The Wide Area Connector (WAC) Adapter is the preferred adapter for
  interconnecting RouteXpander/2 with other bridge/routers over frame-relay or
  leased-line wide area networks.  WACSTAT provides a simple display of the
  WAC control lines and frame errors.  This information can be especially
  useful for diagnosing DSU/CSU or line quality related problems.  For
  example, if the WAC is detecting a large number of Frame Check Sequence
  packet errors ("FCS Errors"), this indicates that there could be a remote
  line quality problem.  The following sample WACSTAT output shows what
  information is available.

Sample WACSTAT output
  @ Copyright IBM 1994, All rights reserved.
  Networking Systems, Research Triangle Park, NC

  Number of WAC ports = 1

  Port Type  In Speed   Out Speed
  ==== ===== ========== ==========
   01  V35   0000065536 0000065536

  Port Clock FCS Errors Tx Underruns Rcv Overruns Int Frames Abort Frames
  ==== ===== ========== ============ ============ ========== ============
   01    Ext 0000000008   0000000000   0000000000 0000000000   0000000002

  Port Bits Stop  Parity Auto Baud Parity Errs Frame Errs Overrun Errs
  ==== ==== ===== ====== ========= =========== ========== ============

  Port  RTS  CTS  DSR  DTR  RI   DCD  SQ   SRS  SRTS SCTS SDCD
  ====  ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ====
   01    On   On   On   On  ---   On  ---  ---  ---  Off  Off
End sample WACSTAT output

  Transmit underruns, receive overruns, and interrupted frames are not
  currently detected.  Therefore, Tx Underruns, Rcv Overruns, and Int Frames
  counters are not updated.  Also, the output line showing "Port Bits Stop
  Parity..."  is used for displaying asynchronous dial line status.  Since
  asynchronous dial connections are currently not supported by RouteXpander/2,
  there is generally no information to display.

  Frame Relay Status Display (NETSTATF.EXE and FRNOTEBK.EXE)
  
  Frame-relay status can be displayed using one of two tools:  NETSTATF or
  FRNOTEBK.  NETSTATF is a character based application which dumps to the
  screen various frame-relay MIB variables.  FRNOTEBK is an OS/2 Presentation
  Manager program which provides the same information as NETSTATF plus
  displays "real-time" frame-relay line utilization status.

  The following output is a sample generated fron NETSTATF.

Sample NETSTATF output
  @ Copyright IBM 1994, All rights reserved.
  Networking Systems, Research Triangle Park, NC

  LA LMI T391 N391 N392 N393 Max VCs Multicast
  == === ==== ==== ==== ==== ======= =========
  01   3 0010 0006 0003 0004    0050 Non-BCast

  LA LINK S Sent Pkts  Rcv Pkts   Sent Bytes Rcv Bytes  Rcv FECNs  RCV BECNs
  == ==== = ========== ========== ========== ========== ========== ==========
  01 0032 A 0000000071 0000000342 0000003479 0000011569 0000000000 0000000000

  LA Error Type     Frame Data (in Hex)
  == ============== ===================
  01 No Errors      No Frame Data
End sample NETSTATF output-

  LA = Logical Adapter
  T391 = Polling Interval
  N391 = Full Inquiry Interval
  N392 = Error Threshold Timer
  N393 = Monitored Events Timer
  Max VCs = Maximum number of support DLCIs or Virtual Circuits
  LINK = DLCI or Virtual Circuit Number

  When invoking NETSTATF, one of the following parameters must be passed.

  -i = interface statistics
  -c = circuit statistics
  -e = last error reported status
  -a = all status information

  If no parameters are specified, a brief help screen will be displayed.

  FRNOTEBK provides most of the information NETSTATF displays, but in a more
  user-friendly interface.  Online help is not provided, but if you're
  familiar with frame-relay, the information displayed should be self
  explanatory.  If not, the following overview will help.

  FRNOTEBK screen layout resembles the following text diagram.

 Ŀ
  WAN Status Notebook                                                    
 Ĵ
   Main  Refresh                                                         
 ͻ
 WAN LMI TypeĿ                                          
  X LMI Rev1     X Annex D                  Maximum VCs       50       
                                           
 WAN LMI ParametersĿ
  Polling Interval (T391)       10     Error Threshold (N392)    3     
  Full Enqriry Interval (N391)   6     Monitored Events (N393)   4     
 ٺ
 Bandwidth UtilizationĿ
                                     Line UtilizationĿ 
  LineSpeed   64000  bps              Outbound:  4%   Inbound  23%   
                                      
 ٺ
 Ŀ
  Link Act Pckts Xmit Pckts Rcvd Bytes Xmit Bytes Rcvd Rcvd FECNs Rcvd 
  ---- --- ---------- ---------- ---------- ---------- ---------- -----
    32 Yes        235        112      11515       4327          0      
 ٺ
                                                          Ŀ
  Time: 17:06:47      Date: 1/5/95                           Refresh   
                                                          ٺ
 ͼ
   Adapter 1                                                           
                                                           
 

  Each configured adapter will have its statistics displayed on a separate
  notebook page.  In the above example, only one adapter is configured.  The
  adapter number is not arbitrary, but can be used to determine exactly which
  adapter is represented.  The adapter number displayed on the notebook page
  can be compared with the adapter numbers configured in LAPS.  The displayed
  frame-relay statistics represent the WAN Access for 802.5 Driver instance
  which has the same adapter number displayed on the notebook tab.  The
  corresponding physical port is then determined by viewing the WAC Device
  Driver MAC parameters of the WAC driver instance which is bound to this WAN
  Access for 802.5 Protocol Driver.  Please see "Chapter 7. Configuring Frame
  Relay" for more information on understanding LAPs, frame-relay, and the IBM
  Wide Area Connector Adapter.

  For the most part, FRNOTEBK is a "passive" status tool.  As of this release,
  FRNOTEBK cannot be used to set parameters or change configuration.  But,
  there are a few settings which can be customized for your particular
  configuration.  These settings can be saved by selecting the "Save Settings"
  menu item under the "Main" menu.  You'll hear a soft 'beep' after the
  settings are successfully saved.

  Line Speed should be configured to match the speed of the DSU/CSU that is
  attached to the RouteXpander/2.  The Line Speed setting is used to calculate
  the line utilization.  FRNOTEBK assumes that the line is full-duplex.  That
  is, if the line speed is 64kpbs, RouteXpander/2 can send 64 kbps and receive
  64kbps simultaneously across the WAN.  Utilization over 400% will display as
  "Err".

  The line utilization and frame and byte count statistics can be configured
  to refresh automatically or manually.  To set, select either "Auto Refresh
  On" or "Auto Refresh Off" under the "Refresh" menu.  If "Auto Refresh On" is
  selected, you can also select the auto refresh interval in seconds by
  selecting either 5, 10, 15, 30, or 60 from the cascaded menu "Refresh
  Interval ->".

  For an explanation of the WAN LMI Type and WAN LMI Parameters, see "Chapter
  20.  Frame Relay Concepts" in the RouteXpander/2 User's Guide.  The Maximum
  VCs represents the maximum number of DLCIs supported or if the WAN Access
  for 802.5 is bound to the X.25 MAC Driver represents the maximum number of
  virtual circuits supported.  This value can be changed via LAPs up to a
  maximum of 200.

  An icon is provided with FRNOTEBK but is not installed in the RouteXpander/2
  folder.  To create the FRNOTEBK icon, drag the "Program" icon out of the
  "Templates" folder (usually installed on the OS/2 desktop) into the
  RouteXpander/2 Folder.  A generic settings notebook will become viewable.
  On the "Program" page in the "Path and File name:"  entry field, type
  'C:\GSD\TOOLS\FRNOTEBK.EXE' (use the drive letter that RouteXpander/2 was
  installed).  Next, on the "General" page in the "Title:"  entry field, type
  "Frame Relay Notebook".  Now close the settings window by double clicking on
  the window's system icon or by selecting the window's system icon and then
  selecting "Close" from the system menu.  If you want FRNOTEBK to
  automatically start at system initialization, drag the Frame Relay Notebook
  icon into the "Startup" folder located in the "OS/2 System" folder.

  Bridge Counter Display (BDMPCNT.EXE)
  
  Bridge counters can be displayed using BDMPCNT.EXE.  Bdmpcnt has one
  parameter which specifies the number of bridge ports for which counter data
  is to be displayed.  These counters basically provide the same information
  that can be found on the port performance console screen.  This application
  becomes more useful if you want to gather bridge counter information
  remotely by telneting to the RouteXpander/2 PC.

  IPX Router Status Display (NETSTATX.EXE)
  
  IPX Router status can be displayed using NETSTATX.  NETSTATX is a character
  based application which displays to the screen various IPX Router MIB
  variables.

Sample NETSTATX output
  @ Copyright IBM 1994, All rights reserved.
  Networking Systems, Research Triangle Park, NC

  IPX System Statistics
  =====================
  Interface Name = IBM RouteXpander/2 IPX Router
  Maximum Hops = 16
  Packets Received = 14502
  Receive Packets Filtered = 0
  Receive Packet Errors = 0
  Receive Processing Errors = 3
  Packets Forwarded = 639
  Packets Transmitted = 639
  Transmit Packet Requests = 27152
  Transmit Packets Filtered = 0
  Transmit Packet Processing Errors = 0
  Hops Exceeded = 0
  No Destination Socket = 0
  No Out Routes = 0
  Resource Failures = 0
  Known Circuits = 2
  Known Destinations = 13
  Known Services = 14

  Circuit Name   E O LA Net Num  MT Type       Size  Delay Changes Througput
  ============   = = == ======== == ========== ===== ===== ======= =========
  Adapter 0      Y Y 00 00000170 TR  Broadcast 16384 00000 0000000  16000000
  Adapter 1      Y Y 01 0000ABCD TR  Broadcast 04516 00000 0000000  00009600

  Net Num   Next Net  NIC Address   Protocol  Type        Cost  HC  NI
  ========  ========  ============  ========  =========== ====  ==  ==
  0000000A  00000170  10005AACB908       RIP      Network   02  01  00
  00000170  00000170  08005A480197     Local      Network   01  00  00
  00001170  00000170  10005AACB908       RIP      Network   02  01  00
  0000ABCD  0000ABCD  4000638402E0     Local      Network   01  00  01
  95859585  0000ABCD  08005A22EC1E       RIP      Network   03  02  01

  Service Name                    Type Net Num  Node         Socket Protocol
  ==============================  ==== ======== ============ ====== ========
  8224-2-10005A79008B             0000 094323B4 000000000001   5050      SAP
  IBM8235_428500                  056A 000000FF 0001CB428500   4003      SAP
  LTLWCOM                         056B 0000ABCD 08005A1A026A   0452      SAP
  SERVERA                         0024 0000000A 000000000001   0451      SAP
  SVT-TREE______________________> 0004 2C03B845 000000000001   0040      SAP
  SVT-TREE______________________> 026B 2C03B845 000000000001   4005      SAP

  LA  RS RIP in Pkts  RIP out Pkts Size  SS SAP in Pkts  SAP out Pkts Size
  ==  == ============ ============ ====  == ============ ============ ====
  00   Y 000000003874 000000004026 0432   Y 000000004275 000000004112 0480
  01   Y 000000002396 000000002720 0432   Y 000000003318 000000002718 0480

End sample NETSTATX output

  Token Ring Network Connectivity Test (OS2PING.EXE)
  
  OS2PING can be used to test connectivity of a bridged token-ring network.
  OS2PING works by sending a TEST frame to the NULL SAP of one or more
  token-ring attached devices.  Most, but not all token-ring attached
  devices will respond to this test frame.  The following command will send
  an all routes explorer test frame from LAN adapter 0 of an OS/2 work
  station to the token-ring global address and record the routes to all the
  stations that respond.

  OS2PING /a=C000FFFFFFFF /r /l=0

  You can examine the output of OS2PING to determine what bridges and LAN
  segments can be reached from your work station.  Of course, if you have
  installed bridge filters on your bridges, some devices may be
  unreachable.

  OS2PING uses the IEEE802.2 software that is shipped with NTS/2.  You must
  install NTS/2 and bind the 808.2 protocol layer to your Token Ring
  Network Adapter or WAN Access for 802.5 Network Adapter prior to using
  OS2PING.  In installations where 802.2 resources are already being used
  (by CM/2 for example) you may need to increase the number of SAPs or
  STATIONS supported by 802.2.

  Type OS2PING with no parameters to get more help for this tool.

  Tracing for Troubleshooting and Filter Development (GSDTRACE.EXE)
  
  RouteXpander/2 tracing can be used to troubleshoot RouteXpander/2 or
  network-based problems and to help design bridge filters.  Below it is
  described how to activate RouteXpander/2 tracing and then how to
  interpret the trace information.

  A. Enabling RouteXpander/2 Tracing
  
  To enable RouteXpander/2 tracing, do the following:

    1. First make sure that you have the following OS/2 programs in the
       \OS2 directory of your boot drive:

            TRACE.EXE    in \OS2
            TRACEFMT.EXE in \OS2
            TRACEFMT.DLL in \OS2\DLL
            TRACEFMT.HLP in \OS2\HELP

       If you do not find these programs, then you will need to install them.
       To do so, do the following:

            a. At an OS/2 prompt, type:  INSTALL
            b. At the first panel ("System Configuration"), click on the "OK"
               button.
            c. On the next panel ("OS/2 Setup and Installation"), click on the
               box, "Serviceability and Diagnostics Aids".  Then click on the
               "Install" button to proceed with the installation.  (Note:
               you may be asked to insert different OS/2 installation
               diskettes into a diskette drive.)

       (These instructions are based on OS/2 V2.11's installation.  Other
       versions of OS/2 may have a slightly different installation process.)

    2. Edit \CONFIG.SYS to include the following statements (anywhere):

            TRACEBUF=63
            TRACE=ON 164

       For more information on these statements, you can use the OS/2 HELP
       facility (for instance, type at an OS/2 prompt:  "HELP TRACEBUF" and
       "HELP TRACE").

    3. If all you desire is frame tracing by the RouteXpander/2 IPX Router,
       then you can skip to step (4) below.  For tracing by the RouteXpander/2
       frame-relay component, continue with the next paragraph.

       Run LAPS and Edit (e.g., double-click on) an "RXR/2 WAN Access for
       802.5 Protocol" entry in your Current Configuration window.  At the
       very bottom of the list of parameters you will see:  "Allow tracing
       for this port?"  This parameter defaults to "NO".  Change this
       parameter's value to "YES" for each port (that is, in each "RXR/2 WAN
       Access for 802.5 Protocol" entry) on which you desire tracing.  After
       updating this parameter, exit LAPS.

    4. Reboot your RouteXpander/2 machine.  If you configured tracing for
       the RouteXpander/2 frame-relay component (as in step (3) above), then
       on your bootup display (and in \IBMCOM\LANTRAN.LOG), you may note the
       following message:

            "FRP0097:  OS/2 Tracing is allowed for Network Adapter #"

       This message is to alert you that frame-relay tracing is active for
       the configured port.  If at an OS/2 prompt you type "HELP FRP0097",
       the help text will remind you that tracing is useful for debugging
       but may impact performance and could present a security risk.

       You will now be tracing every frame sent through the frame-relay
       device driver.  To turn tracing off at any time, use the following
       OS/2 command:

            TRACE OFF

       To turn tracing (back) on, type:

            TRACE ON 164

       (The parameter "164" specifies that tracing should be turned on for
       certain data communications device drivers, including RouteXpander/2's
       frame-relay driver and RouteXpander/2's IPX router.)

       For more information on OS/2 Trace commands, type "HELP TRACE" at any
       OS/2 prompt.

    5. When you want to gather and store trace data (for instance, after a
       failure occurs that you want traced), type the following command at an
       OS/2 prompt:

            TRACEFMT

       This will bring up a PM session filled with a variety of data.  An
       example of the data you might see could be:

Sample TRACEFMT Display

OS/2 Version 2.0 System Trace Formatter Output
Formatted Events

Buffer size = 63 K Bytes


EVENT# [0001]  PID [000D]  MAJOR [A4]  MINOR [004B]  LENGTH [0020]  TIME:
08 00 12 56 0D 00 32 00 00 00 00 00 BA A6 01 00 08 09 0A 0B 0C 0D 0E 0F 10 11
12 13 14 15 16 17

EVENT# [0002]  PID [000D]  MAJOR [A4]  MINOR [004A]  LENGTH [0001]  TIME:
CC

EVENT# [0003]  PID [000D]  MAJOR [A4]  MINOR [004A]  LENGTH [0003]  TIME:
08 01 03


       You need to store this data for subsequent processing.  To store the
       data, click on the "File" pulldown menu item (or type ALT-F), then
       click on the "Save as ..." menu item (or type "S"), then click on
       the submenu item "Save formatted trace data" (or type "F").  This will
       present a popup menu which will allow you to specify a trace-file name.
       Choose any name you want (e.g., RXR1.TRC) and "Save" this file.  When
       the trace-file save has been completed (indicated by another popup),
       exit the OS/2 TRACEFMT program.

    6. You now have two options.  You can try to analyze the trace data
       yourself, or you contact IBM support to assist you in analyzing your
       trace, or both.  If you choose to contact IBM support, send them the
       formatted trace data you have just saved, as well as the following
       files:

          \CONFIG.SYS
          \IBMCOM\PROTOCOL.INI
          \IBMCOM\LANTRAN.LOG
          \GSD\GSDMSG.LOG
          \GSD\GSDARCH.LOG

       If you choose to analyze the formatted trace data yourself, then copy
       (or move) the formatted trace files to the \GSD\TOOLS directory (where
       the RouteXpander/2 GSDTRACE.EXE program is) and issue one of the
       following commands:

          GSDTRACE <filename>       - for a simplified ladder diagram
              or
          GSDTRACE <filename> /c    - for a more detailed ladder diagram

       where <filename> is the name of the file you created with the OS/2
       TRACEFMT program in step (5).  (For instance, you can issue the
       command "GSDTRACE RXR1.TRC /C".)

  B. Interpreting RouteXpander/2 Trace Output
  
  GSDTRACE will generate several output files.  The output files all use
  the same base filename as the input filename, but have different filename
  extensions.  The output files and their extensions are as follows:

    (1) The .ANA file protocol-ANALYZES each PDU.
    (2) The .LDR file LADDER-diagrams each PDU.
    (3) The .MAP file MAPS bridged routes with PDU statistics.

  The GSDTRACE output file that is most likely to be of use for
  troubleshooting ends with the suffix .LDR.  The output file that might be
  of most use in selecting Bridge Filters ends with the suffix .MAP.  In
  addition, the .LDR file can be used in tandem with the .ANA file, since
  the .LDR provides a high-level ladder diagram of network traffic whereas
  the .ANA file provides a more low-level data analysis.  The .LDR frames
  can be correlated to the appropriate .ANA frame by referencing their
  common "PDU #".

  Below are sample snippets from .LDR (ladder diagram), .ANA (protocol
  analysis), and .MAP (bridge mapping) files.

Sample .LDR output
RXR2IPX0.LDR
Rudimentary Ladder Diagram based on RXR2IPX0.TRC 

         Remote Node                                  Local Node            PDU#
        -------------                                -------------          ----
                                                    
                    Spanning Tree BPDU                                    0040
        08005A48018E------------------------------->C00000000100
                                                    
   FF.FF.FF.FF.FF.FF  IPX "RIP Response" [Broadcast]40.00.63.84.01.20     0041
        FFFFFFFFFFFF<Ĵ400063840120
                                                    
   FF.FF.FF.FF.FF.FF  IPX "RIP Response" [Broadcast]40.00.63.84.01.20     0042
                    <-------------------------------
                                                    
                      LMI(0) Status-Enq: Full-Status                      0043
                    <-------------------------------
                                                    
                    LMI(0) Status: 32                                    0044
                    ------------------------------->


  Note in the above trace that those frames whose reception or transmission
  are denoted by a dashed line (e.g., ---->) represent frames traced by the
  RouteXpander/2 frame-relay component, whereas those denoted by a solid
  line (e.g., >) represent frames traced by the RouteXpander/2 IPX
  Router.

  (The above trace was generated by GSDTRACE without using GSDTRACE's "/C"
  option.  If the "/C" option had also been used, then control information
  related to OS/2 NDIS** interfaces would be displayed.  This type of control
  information is particularly useful if your trace indicates that you are
  only transmitting frames but are not receiving any frames or if you
  believe that there may be a problem between RouteXpander/2's frame-relay
  component and the IBMWAC or RICDD device-drivers to which it is bound.)

Sample .ANA output
RXR2IPX0.ANA
Frame-by-Frame Protocol-Specific Byte Counts based on RXR2IPX0.TRC

                               *** PDU #0042 ***
------------------------------Original Trace Data-------------------------------
    08010380 00000081 37FFFF00 58000100 000931FF FFFFFFFF FF045300 00093140
    00638401 20045300 02000001 70000100 02000000 0A000200 03000011 70000200
    03000E11 70000200 03000E21 70000200 03000E31 70000200 03000E41 70000200
    03
----------------------------------PDU Summary-----------------------------------
200.21  PDU #0042. IPX "RIP Response" [Broadcast] <==
             Total bytes = 97
             Analysis of protocol-specific overhead in bytes:
                Frame Relay    = 2   (DLCI = 32) [FCS bytes not included]
                RFC-1490       = 7   (RFC-1490 "Novell IPX")
                IPX            = 30  (Packet Length       = 0058 [hex])
                                     (Transport Control   = 00)
                                     (Packet Type         = 01)
                                     (Destination Network = 0000 0931)
                                     (Destination Node    = FFFF FFFF FFFF)
                                     (Destination Socket  = 0453)
                                     (Source Network      = 0000 0940)
                                     (Source Node         = 4000 6384 0120)
                                     (Source Socket       = 0453)
                Novell RIP     = 58  (Operation = 0002)
                                     (Number of Entries = 4)
                                     (Entry   Network   Hops  Ticks)
                                     ( 001    00000170  0001  0002 )
                                     ( 002    0000000A  0002  0003 )
                                     ( 003    00001170  0002  0003 )
                                     ( 004    000E1170  0002  0003 )


  The above example gives some detailed protocol information about PDU
  number 42 from the preceding .LDR ladder diagram.  (While all the frames
  in the .LDR file are also in the .ANA file, this one PDU was excerpted
  for illustration purposes.)

Sample .MAP output
RXR2IPX0.MAP
Ring-Bridge mappings between nodes, based on RXR2IPX0.TRC 

Total  +-----Node1-----+ +-----Node2-----+
Frames |MAC Address SAP| |MAC Address SAP|   Route Designators (Ring-Bridge)
------ ------------ ---- ------------ ---- ------------------------------------
    99 4000FFFF0032  AA  400063840120  AA  011-3 018-0
------ ------------ ---- ------------ ---- ------------------------------------
          Lower-Layer Protocols:
             802.X bytes     =  1683 (23%)
             SNAP bytes      =   495 ( 6%)
          TCP/IP Protocols:
             IP bytes        =    40 ( 0%)
             UDP/IP bytes    =    16 ( 0%)
             RIP/IP bytes    =    88 ( 1%)
          Novell Protocols:
             IPX bytes       =  2910 (41%)
             RIP bytes       =    10 ( 0%)
             NCP bytes       =  1832 (25%)
          Total Bytes        =  7074
------ ------------ ---- ------------ ---- ------------------------------------
    96 08005A48018E  E0  10005AACB908  E0  011-3 012-1 070-2 075-0
------ ------------ ---- ------------ ---- ------------------------------------
          Lower-Layer Protocols:
             802.X bytes     =  1632 (25%)
          Novell Protocols:
             IPX bytes       =  2880 (45%)
             NCP bytes       =  1832 (28%)
          Total Bytes        =  6344
------ ------------ ---- ------------ ---- ------------------------------------
    26 4000FFFF0032  42  C00000000100  42
------ ------------ ---- ------------ ---- ------------------------------------
          Lower-Layer Protocols:
             802.X bytes     =   442 (32%)
          Bridge-Related Protocols:
             BPDU bytes      =   910 (67%)
          Total Bytes        =  1352


  The .MAP file provides information on:

      - which machines are sending bridged traffic to which machines
      - how much traffic is being transferred between these machines
      - the routes (ring-bridge pairs) this traffic is taking
      - the type of protocols being used between these machines

  This information can help you determine what kind of bridge filters you
  may need (if any).  For instance, looking at the above .MAP file, you may
  decide that you need to filter out IPX traffic and all data from MAC
  addresses 08005A48018E and 10005AACB908.  You may decide to put a "3-hop"
  limit on your bridge or increase timers associated with your IPX RIP
  broadcasts.  Careful analysis can lead to significant improvements in
  your WAN utilization.  Sometimes users are even surprised to learn the
  type of traffic their nodes are actually transferring.

  For related information on the output created by GSDTRACE, simply type at
  an OS/2 command prompt:

      GSDTRACE

  in the directory in which GSDTRACE.EXE is stored.  (Note that
  GSDTRACE.EXE's help message is formatted for a FULL-SCREEN OS/2 Session;
  if GSDTRACE is invoked from an OS/2 Window, its screen output may be
  displayed too quickly for user viewing.)

************************************************************************
  CHAPTER 5.  NOTES ON RELATED PRODUCTS

  PS/ValuePoint Flash PROM Levels
  
  When RouteXpander/2 is installed on a PS/ValuePoint, you must make sure
  that the PS/ValuePoint's Flash PROM's level is at L6ET58AUS or higher.
  With backlevel PROMs, intermittent errors may be observed.

  To check the Flash PROM level of you PS/ValuePoint, when your machine
  is powered on and is doing a memory check (indicated by the rapidly
  incrementing numbers on the monitor's upper left corner), press F1.
  This will display a configuration screen showing your current Flash
  PROM level.

  IBM Token Ring 16/4 Shared RAM Adapter:  Use Size of 64K or 32K
  
  It is strongly recommended that you set your Token Ring Shared RAM
  adapter's RAM window size to 64K bytes, for maximum performance.  If
  this is not possible due to configuration restraints of your system
  setup, then a 32K byte window size is recommended.  Anything less that
  32K bytes can lead to problems described in the following paragraphs.

  With a Shared RAM window size of 16K or fewer bytes, the Token Ring
  Shared RAM adapter's device driver must "page" the Shared RAM window
  in order to access all of the data and control buffers.  The mechanism
  for paging has proven to be error-prone in certain systems, thus
  leading to erroneous control and data processing.  Such behavior can
  significantly impact the performance and reliability of your
  RouteXpander/2.

  Only if you cannot set the shared RAM size to either 64K or 32K bytes,
  then the following considerations must be kept in mind:  In order to
  receive frames greater than 2K bytes in size, the minimum configured
  Shared RAM size for the IBM Token Ring 16/4 Adapters must be at least
  16K bytes;  that is, if 8K bytes of shared RAM are configured, the
  adapter automatically sets the maximum received frame size to 2K bytes.

  IBM 16/4 ISA Token Ring Adapter Switch Settings
  
  The switch settings for the 16/4 ISA-16 Adapter (short 16-bit ISA-bus
  adapter with 1 2-bit switch block and 1 12-bit switch block) are the same as
  those for the short 8-bit ISA-bus adapters.  The settings for the 2-bit
  switch block are as follows:

  * S1  - Cable Type
    
    on  = Shielded Twisted Pair (STP; "IBM cabling")
    off = Unshielded Twisted Pair (UTP; "telephone wire")

  * S2  - RPL (Remote Program Load)
    
    on  = Enabled
    off = Disabled

  IBM 16/4 ISA Token Ring Network Adapter - Switch Settings
  
  The following switch settings are for the short Token-Ring Network PC
  Adapter II and the Token-Ring Network 16/4 Adapter (the 8-bit ISA-bus
  adapters with one 12-bit switch block).

  These are also the settings for the 12-bit switch block on 16/4 ISA-16
  Adapter (16-bit ISA-bus).

  * S1  S2  S3  S4  S5  S6  - ROM Address
         
    off on  on  off off on  = X'CC000' (typical for "Primary" adapter)
    off on  off off off on  = X'DC000' (typical for "Secondary" adapter)

  The settings above are typical; other ROM Address values may be set.
  The ROM address is defined as follows:

                          B'1xxx xxx0 0000 0000 0000'
                              
         S1 ٳ   off=1, on=0
         S2 ٳ 
         S3  
         S4 ٳ
         S5 ٳ
         S6 

  * S7  S8  - Interrupt Level
     
    on  on  = 2 (first choice, conflicts with 3278/79 adapter)
    on  off = 3 (second choice, conflicts with COM2)
    off on  = 6 (do not use, conflicts with diskette adapter)
    off off = 7 (third choice, conflicts with some printer adapters)

  * S9  - I/O Address ("Primary/Secondary")
    
    off = X'0A20' ("Primary" adapter)
    on  = X'0A24' ("Secondary" adapter)

  * S10 S11 - RAM Size
     
    on  on  =  8 KB
    off on  = 16 KB
    on  off = 32 KB (16/4 adapters only)
    off off = 64 KB (16/4 adapters only)

  * S12 - Ring Speed
    
    on  =  4 Mbps
    off = 16 Mbps (16/4 adapters only)

  IBM 16/4 ISA Token Ring Network Adapter - Example Configuration
  
  The following configuration has been tested in a ValuePoint 466DX2/D:

  * S1  S2  S3  S4  S5  S6  - ROM Address
         
    off on  on  off on  on  = X'C8000'

  * S7  S8  - Interrupt Level
     
    off off = 7

  * S9  - I/O Address ("Primary/Secondary")
    
    off = X'0A20' ("Primary" adapter)

  * S10 S11 - RAM Size
     
    on  off = 32 KB

  NTS/2 Adapter Device Driver Parameters - Example

    IBM Token Ring Adapter For Bridge (GSDTOK.OS2)
       Adapter Mode          PRIMARY
       Shared RAM Address    D800

  IBM Wide Area Connector for ISA Bus -  Switch Settings
  
  The following switch settings are for the IBM Wide Area Connector Adapter
  for ISA Bus PCs.

  * S1  S2  S3   - IRQ used by the WAC Adapter
      
    on  on  on   = IRQ9
    off on  on   = IRQ5
    on  off on   = IRQ4
    off off on   = IRQ3
    on  on  off  = IRQ15
    off on  off  = IRQ14
    on  off off  = IRQ11
    off off off  = IRQ10

  * S4  S5  S6  S7   - I/O Address Range Used (in Hex)
       
    on  on  on  on   = 0120h - 013Fh
    off on  on  on   = 0140h - 015Fh
    on  off on  on   = 0180h - 019Fh
    off off on  on   = 01A0h - 01BFh
    on  on  off on   = 0220h - 023Fh
    off on  off on   = 0240h - 025Fh
    X   off off on   = 0280h - 029Fh  ('X' = can be ON or OFF [don't care])
    on  on  on  off  = 0520h - 053Fh
    off on  on  off  = 0540h - 055Fh
    on  off on  off  = 0580h - 059Fh
    off off on  off  = 05A0h - 05BFh
    on  on  off off  = 0620h - 063Fh
    off on  off off  = 0640h - 065Fh
    X   off off off  = 0680h - 069Fh  ('X' = can be ON or OFF [don't care])

  See the discussion of ISA WAC example configuration for related information.

  IBM Wide Area Connector for ISA Bus -  Example Configuration
  
  The following configuration has been tested in a ValuePoint 466DX2/D.
  Below is a sample \IBMCOM\PROTOCOL.INI module configuration.  An example of
  WAC switch settings that can be associated with this PROTOCOL.INI listing
  are as follows:

                        IRQ11           I/O=0120-013fh
                    Ŀ     Ŀ
                     S1  S2  S3         S4  S5  S6  S7
                     on  off off        on  on  on  on

  Note in these switch settings that the I/O Address range is associated with
  four "on" bits, which can be represented as binary '1111'b or hexadecimal
  '0F'x or decimal 15.  For ISA WACs, these I/O Address bits are interpreted
  as a decimal value to be used in the PROTOCOL.INI "WACCARDNUM" value (see
  below).  The WACCARDNUM can be configured using LAPS when editing the "IBM
  Wide Area Connector" configuration's parameter:

            "Slot number (MC-A) [1..8] or Card Number (ISA) [0..15]"

  Also note that both the above set IRQ and I/O Address values cannot conflict
  with those used by any other PC equipment, including other WAN adapters, LAN
  adapters, serial ports or parallel ports.  For the values used by LAN
  adapters, see previous sections.  For values used by serial and parallel
  ports, depress the CTRL-ALT-INSERT keys when "cold-booting" your machine.

Sample ISA WAC PROTOCOL.INI
[IBMWAC_nif]

   DriverName = IBMWAC$
   WACCARDNUM = 15
   WACPORTNUM = 1
   RAMADDRESS = 0x0D0000
   RTS = 0
   NRZI = 0
   RS232MODE = 0
   X21MODE = 1
   LINESPEED = "1.5M"
   MAXDATA = 4486
   MACTYPE = "HDLC"
   MAXTRANSMITS = 8
   PCMSUPPORT = 0
   CONNTYPE = 0
   FLAGS = 1


  Note that the "RAMADDRESS" value (addressed by the LAPS parameter ""16KB
  Shared memory addr. [0C0000-FE0000]") must not conflict with the memory
  (RAM or ROM) addresses used by other PC devices, such as Token-Ring Network
  Adapters.


************************************************************************
  CHAPTER 6.  RouteXpander/2 Known Problems

  This chapter contains information about known problems with either
  RouteXpander/2 or products associated with RouteXpander/2.  Over time, it
  is anticipated that many of these problems will be fixed with subsequent
  product releases or with Corrective Service Diskettes (CSDs).  (Some
  problems are expected to be fixed in early 1995.)  To obtain the latest
  information about product releases and CSDs, U.S.  customers should
  contact the "IBM Service Software Support Center" at 1-800-237-5511.
  When contacting the Support Center, your request will be expedited if you
  have the product number available for the product about which you are
  inquiring.

  OS/2 Warp
  
  At the time of this README.TXT's writing, OS/2 Warp has a certain problem
  with an application-level inter-process communication (IPC) device known
  as a "named pipe".  Some RouteXpander/2 applications use named pipes in a
  manner that subjects them to Warp's unexpected implementation.

  Because of this problem, RouteXpander/2's bridge support on OS/2 Warp
  cannot be started and managed from the Console.  Management (whether
  with a LAN Network Manager or with the RouteXpander/2 Console or with an
  SNMP based manager) does not work.  Bridging can be started
  independently of the console by issuing the following command in an OS/2
  Window:  "START C:\GSD\GSDBRMGR.EXE".  An OS/2 Warp problem (PMR) 3X339
  has been opened to track this incompatibility.  IPX routing works as
  documented.  X.25 support has not yet been tested.

  MPTS/2
  
  IBM's latest release of LAPS has been integrated into its "Multi-Protocol
  Transport Services" (MPTS/2) program.  MPTS/2 is installed with IBM's LAN
  Server 4.0, LAN Distance, and AnyNet products.  The following problems
  should only arise if you load RouteXpander/2 on a machine that currently
  has MPTS/2 installed.

  LAPS is used by the aforementioned products and RouteXpander/2 to install
  OS/2 device drivers.  An integral part of the device-driver installation
  involves "Network Information Files," also known as NIF files.  At this
  time, the MPTS/2 version of LAPS has a limitation on the number of NIF
  files it can manipulate, and MPTS/2 fails to operate when this limit is
  reached.  Unfortunately, if you try to install RouteXpander/2 on a
  a machine that has MPTS installed, its NIF file limit is exceeded.

  To avoid this problem, prior to installing RouteXpander/2, examine the *.NIF
  files (either by checking the file names or by editing the files) in your
  \IBMCOM\MACS and \IBMCOM\PROTOCOLS directories.  Select the .NIF files for
  several (five or so) of the device drivers that you do NOT intend to use and
  rename these files with a file extension other than .NIF.  Then install
  RouteXpander/2 2.0.2.

  In addition, when RouteXpander/2 and MPTS/2 are loaded on the same machine
  you may see the following message appear one or more times on your boot-up
  screen:

       Cannot open LANMSG$$

  To avoid this message, edit your \CONFIG.SYS so that DEVICE statements for
  RouteXpander/2 device drivers (GSD*.200 and IBMWAC.OS2) precede the
  following MPTS/2 DEVICE statement:

      DEVICE=C:\MPTN\PROTOCOL\MPTN.SYS

  Similarly, for remote installations to work, your RouteXpander/2 remote
  service device drivers (SRVIFS.SYS and SRVIFSC.IFS) need to precede the
  MPTN.SYS DEVICE statement in \CONFIG.SYS.

  WAC
  
  Below is the latest Engineering Change (EC) information available on IBM
  Wide Area Connector (WAC) adapters:

  Failure symptoms:  Machine NMI or data corruption problems related to use
  with WAC adapters.

  The following Part Numbers (P/N) should have an EC level of C41821 or
  higher:

  33G8465, 33G8466, 33G8467, 33G8468, 33G8469, 33G8470, 33G8471, 33G8472
  33G9171, 33G9172, 33G9173, 33G9174, 33G9175, 33G9176, 33G9177 and 33G9178.

  The EC level should be on the P/N label on the back side of the base card.

  Fix:

  EC levels C41111 and C41618 should be replaced with Microchannel base cards
  for P/Ns 33G8465-33G8468 and 33G9171-33G9174 with FRU 33G8453.  ISA base
  cards for P/Ns 33G8469-33G8472 and 33G9175-33G9178 should be replaced with
  FRU 33G8454.  Daughter cards (EIBs) at the above EC levels do NOT need
  to be replaced.

  RouteXpander/2 Nodes with IPX Lockup using Novell Server 3.12
  
  If your RouteXpander/2 node keyboard and mouse "lock up" (are unable to
  work) and your network contains a Novell 3.12 File Server, make sure all IPX
  Requesters have the Large Internet Packets (LIP) parameter turned off.

  RouteXpander/2 Remote Installs: SRVIFS Must Be LAST in CONFIG.SYS
  
  When you set up your RouteXpander/2 for remote installation the following
  statements are placed LAST in the \CONFIG.SYS file.

    DEVICE=C:\GSD\REMOTE\SRVIFS.SYS
    IFS=C:\GSD\REMOTE\SRVIFSC.IFS *

  With the exception of MPTS/2's MPTN.SYS driver (see "MPTS/2" above), these
  two statements must remain LAST for the system to work correctly.  If they
  are not last the system may hang during startup.  Unfortunately, when you
  modify your configuration using NTS/2 CSD WR07045 and earlier, other
  protocols or adapter device drivers may be added to CONFIG.SYS AFTER the
  SRVIFS statements.  Check your CONFIG.SYS each time after you modify your
  configuration using NTS/2.  NTS/2 CSD WR07060 will be available soon which
  should fix this problem.

  RouteXpander/2 Console's "Keys Help" Not Available
  
  When you click on the "Help" button on any RouteXpander/2 Console window,
  the "RouteXpander/2 Console Help" window will appear.  This latter window
  will have a "Help" pulldown menu.  This Help pulldown menu's "Keys Help"
  selection is unavailable at this time.

  RouteXpander/2 Console's Message Log's "Save as..." Unreliable
  
  If you desire to save (backup) your RouteXpander/2 Message Log files
  (GSDMSG.LOG and GSDARCH.LOG), it is recommended that you do not use the
  "Save as..."  button available on the RouteXpander/2's Bridge Message Log
  window.  Instead, close the Console (ALT+F4) and then go into an OS/2 window
  and type the following command:

       COPY \GSD\GSDARCH.LOG /B + \GSD\GSDMSG.LOG BACKUP.LOG

  where the filename "BACKUP.LOG" can be any filename you desire.

  RouteXpander LNM Support/2 Extraneous Alert
  
  Under certain conditions, when a wire fault occurs, the RouteXpander
  LNM Support/2 program may send a NAUN Change alert, in addition to
  an alert indicating that frame forwarding has stopped.  This
  extraneous NAUN Change (which indicates that the affected node's
  NAUN is itself) should be ignored.
