Release Notes 93000386_1P Digi DataFire SYNC 2000 Driver Package for Red Hat Linux 6.2 Release v0.1-1 Supported Red Hat Distributions: Version 6.2 Supported OS Kernels: 2.2.14-5.0 Package Part Numbers: 40002161_1P (Uniprocessor) 04/04/2001 1. INTRODUCTION This Digi software package includes device drivers for the DataFire Sync 2000 PCI and cPCI families of adapters. It is currently supported on Intel x86 platforms with Red Hat release 6.2 with stock distribution kernel 2.2.14-5.0. This package requires that Linux Streams (LiS) 2.8 be installed and patched with the Digi supplied patch 40002163_1P. This package requires that an X-Windows environment be installed in order to run the DataFire Sync 2000 configuration tool "wancfg". Please reference the following number(s) when searching the Digi International web site (www.digi.com) or ftp site (ftp.digi.com) for the latest software package: Release Notes Part Number: 93000386_1P Package Binary RPM Part Number: 40002161_1P Linux Streams Patch Part Number: 40002163_1P Documentation Part Number: 92000412_A 2. SUPPORTED PRODUCTS DataFire SYNC 2000 4P+ PCI P/N 77000641 DataFire SYNC 2000 4P+ cPCI P/N 77000709 DataFire SYNC 2000 4P PCI P/N 77000642 DataFire SYNC 2000 4P cPCI P/N 77000711 DataFire SYNC 2000 2P+ PCI P/N 77000643 DataFire SYNC 2000 2P+ cPCI P/N 77000710 DataFire SYNC 2000 2P PCI P/N 77000644 DataFire SYNC 2000 2P cPCI P/N 77000712 3. ENHANCEMENTS * Initial beta release 4. BUG FIXES * Initial beta release 5. KNOWN LIMITATIONS * The user will be unable to configure an aggregate number of PPP links. Additionally, the user must ifconfig each PPP link. The user is encouraged to edit the script /opt/snet/etc/rc.d/init.d/dgmlp and alter the ifconfig command to reflect the appropriate destination address. * DLCI's greater then 991 are not supported unless the dlci is being used for LMI (Line Management Interface). * This beta version of the driver will only support one SYNC 2000 board installed in the computer. If more than one board is installed they may not function correctly. * This beta version does not yet support the DataFire SYNC 2000 PMC bus cards. * This beta version is only available for Linux uniprocessor kernels; multiprocessor support is not yet available. * For best operation, the IP addresses of the remote endpoints of connections over the Sync 2000 cards should be entered in the /etc/hosts file. * The ppptrace and frtrace utilities will shut themselves off if the trace messages fill their streams queue buffer--for example, if the trace utility cannot keep up with the volume of trace messages. If this happens, simply restart the trace utility. 6. ADDITIONAL INFORMATION * The latest version of this package, these release notes, documentation, and other information related to this product can be found at: http://support.digi.com/support or you can use the Digi ftp site at ftp.digi.com * Please read the documentation available on the Digi web site as part number 92000412_A. This describes installing and configuring the driver. * Prior to installing the Digi Sync 2000 driver package, you must install Linux Streams (LiS) 2.8 to your system and apply a Digi supplied patch. LiS 2.8 can be obtained by using ftp: ftp ftp.gcom.com (login as anonymous, passwd is email address) ftp> cd /pub/linux/src/LiS ftp> bin ftp> get LiS-2.8.tgz ftp> bye The Sync 2000 driver package requires a patch to the LiS software. The patch can be downloaded from the Digi International ftp site. The file name is: 40002163_1P To add LiS to your system and apply the Digi patch, perform the following steps: tar xzf LiS-2.8.tgz cd LiS-2.8 patch -p0 <40002163_1P make make install * The binary RPMs for this driver package can be downloaded from the Digi International ftp site. Download the RPM file 40002161_1P-0.1-1.i386.rpm (uniprocessor). Place the file in the directory "/usr/src/redhat/RPMS/i386" and install the package by entering: rpm -ivv --nodeps /usr/src/redhat/RPMS/i386/.i386.rpm * Man pages are installed for package utilities. They include wancfg, dgpppstat, dgppptrace, frstat, frtrace, wantrace, x25stat and x25trace. * An effort has been made to automate the X.25/Frame Relay configuration process. If problems exist when trying to connect to other hosts on the network, the user should be familiar with network trouble shooting methods. An example of this is the use and understanding of the following utilities: (TCP/IP ONLY ) ping, netstat, route, ifconfig * Your Frame Relay/X.25 network will attempt to come up on reboot. If this is undesirable, disable the start scripts via wancfg (GUI). * The easiest way to correlate adapter/port combinations with the Subnet ID is to view the /opt/snet/etc/syncconf file. wans 0 0 A WAN84 FR_DTE stackA - FRAME wans 0 1 B WAN84 LC_LAPBDTE stackB 5551212 X25 wans 0 2 C WAN84 FR_DTE stackC 0 FRAME wans 0 3 D def def stackD - PPP wans 1 0 E def def stackE - PPP wans 1 1 F def def stackF - PPP wans 1 2 G ? ? ? ? ? wans 1 3 H ? ? ? ? ? The format for each line in this file has adapter number in the second column and port number in the third. In the above example, two adapters have been configured. The first is a 4 port adapter, displayed as adapter 0, and the second is a 2 port adapter, displayed as adapter 1. Although the 2 port adapter is displayed for 4 ports within the syncconf file, the graphical interface only allows the administrator to configure two of those ports. 1) PPP is configured for Adapter 0, port 3, and is assigned Subnet ID 'D'. 2) PPP is also configured for Adapter 1, port 0, and is assigned Subnet ID 'E'. Note that port 1 is also a PPP link and assigned Subnet ID 'F'. 3) X.25 is configured for Adapter 0, port 1 and is assigned Subnet ID 'B'. 4) Frame Relay is configured for Adapter 0, ports 0 and 2, and assigned Subnet IDs 'A' and 'C', respectively. 5) If adapter 1 were a 4 port adapter instead of a 2 port adapter, the information displayed for ports 2 and 3 would show that Adapter 1 ports 2 and 3 are not configured, i.e., Connection Type is None. 7. HISTORY April 4, 2001 - Initial beta product release