TechNote: 0005 Date : 05/27/96 Cat/Sub : WANPIPE/UFPIPE Title : Upgrade #2 available for UFPIPE Rel2.0.1a/2.0.2a Contact : Glenn Robins Related Files: /pub/updates/r202upd.tar /pub/updates/r202upd.txt ------------------------------------------------------------------------------ A patch to UFPIPE Rel2.0.2a is now available in the /pub/updates directory, called r202upd.tar. UFPIPE is the Frame Relay network driver implementation under SCO Unix as part of the WANPIPE product family. The equivalent distribution release is 2.1.0a. This patch may also be used to upgrade release 2.0.1a directly to 2.1.0a without requiring the r201upd patch. Read the following for a description of the patch. If you are upgrading from 2.0.1a, read TechNote #0001 for a description of the changes made up to 2.0.2a. BUG FIXES ========= 1. If more than one transmit request is made concurrently over different DLCIs, the board and/or driver will likely crash. The resulting crash may also cripple the operating system, requiring a cold restart. This may only happen on a multiprocessor machine. The fix rejects concurrent transmit requests, and may happen once every few hours, depending on activity. 2. The hardware timeout period in the driver is too long. If the board were to crash as in the case above, it is possible that by waiting too long before aborting the operation, the operating system or other attached devices may not recover from not being serviced during this period. The fix shortens this time, and also refuses any further attempts after three concurrent failures. This is indicated by Oerrors being incremented for each transmitted packet. A console message is also displayed if a hardware timeout occurs. NEW FEATURES ============ 1. This release now supports the S503 adapter type. 2. UFROUTE -i has an additional information byte, which is used for diagnostic purposes by Sangoma if a failure occurs. It is called Port. 3. There is a new option in UFDCFG: -d0 or -d1. The -d1 option turns on global debugging in the form of console messages for the specified card. The -d0 option turns it off. Run UFDCFG alone to display its usage. It should not be placed in /etc/rc.d/5/ufpipe as the configuration script does not expect its presence there. If it must be enabled automatically on bootup, place it in a script that will execute later. This option has the same effect as "ifconfig fpi# debug" in R3.2V4.2, which does not work in Release 5.0. Therefore, -d1 must be used in Release 5.0 to activate debugging messages. FILES AND PATCH INSTRUCTIONS ============================ Download r202upd.tar along with r202upd.txt and follow the instructions. ------------------------------------------------------------------------------ This TechNote is Copyright (c) 1996 Sangoma Technologies Inc. All rights reserved.