TechNote: 0001 Date : 05/01/96 Cat/Sub : WANPIPE/UFPIPE Title : Upgrade #1 available for UFPIPE Rel2.0.1a Contact : Glenn Robins Related Files: /pub/updates/r201upd.tar /pub/updates/r201upd.txt ------------------------------------------------------------------------------ A patch to UFPIPE Rel2.0.1a is now available in the /pub/updates directory, called r201upd.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.0.2a. Read the following for a description of the patch. BUG FIXES ========= 1. Running UFDCFG -i on the S508 failed to reactivate receive interrupts, and so no packets could be received until the machine is rebooted. This also caused the Frame Relay link to go inoperative after a minute or so. 2. A potential stray interrupt handling problem is fixed for the S508. 3. UFDIAG misrepresented some error and global statistics for the S508. NEW FEATURES ============ 1. UFROUTE now supports the -i option, which presents a table of interrupt statistics for each card. An example is shown below: Card Type Pending Total Receive Spurious NoBinding NoFrame Unclaimed --------------------------------------------------------------------- 0 S508 0x00 78 78 0 0 0 0 1 Not loaded 2 Not loaded 3 Not loaded Under normal operating conditions, Pending must always be 0x00. If no packets are being received at the time this table is displayed, but it shows 0x01, a packet was received but the generated interrupt was not handled by the driver. The Total and Receive values must be equal. Any values other than zero under Spurious, NoFrame, or Unclaimed should not occur. If the link goes down and these values are non-zero, please inform a technical support person at Sangoma. The NoBinding value will increase for every received packet that has an unknown Frame Relay encapsulation, or one that is recognized but no protocol binding exists for it. If only IP is used, and no IP packets are received according to netstat -i, and this value increases, it is likely that the encapsulation used on the remote router is not RFC 1490-compliant. If no interrupts are recorded in this table when the DLCI statistics in UFDIAG reports that frames have been received, and that Pending is 0x01, it is likely that the IRQ is conflicted with another device or is somehow disabled. Try another IRQ if possible. 2. UFDIAG now reports the detected card type when selecting a card, or reports if the card was not loaded. FILES AND PATCH INSTRUCTIONS ============================ Download r201upd.tar along with r201upd.txt and follow the instructions. ------------------------------------------------------------------------------ This TechNote is Copyright (c) 1996 Sangoma Technologies Inc. All rights reserved.