Release Notes PN 93000329_C1 for digiras Digi DataFire/AccelePort RAS and AccelePort Xp Release 1.2i for UnixWare 7.0.1 through 7.1.1 up to Maintenance Release Pack 2. Package Image PN 40001891_C DataFire Package PN 40001892_C AccelePort Package PN 40001893_C Source PN 81000097_C Release Date 07-12-00 CONTENTS Section Description 1 Introduction 2 Supported products 3 Software Limitations 4 Known Problems 5 History 1. INTRODUCTION This Digi software package includes device drivers for the AccelePort/DataFire RAS products supported under UnixWare 7.0.1 through 7.1.1 up to Maintenance Release Pack 2. This release includes support for multiple Host Adapters per system. Please reference the following number(s) when searching the Digi International FTP/WWW site for the latest software package: Package Image P/N 40001891_C 2. SUPPORTED PRODUCTS Digi AccelePort RAS Digi DataFire RAS Digi AccelePort Xp 3. SOFTWARE LIMITATIONS * The maximum number of Acceleport RAS and DataFire RAS adapters combined in one system is currently set to 8. * Async ports are configurable through the serial and modem managers. The system must be at revision 7.0.1 with ptf7053b applied in order for the serial manager to operate properly. * RULES FOR CONFIGURING AND UNCONFIGURING Multi-Line DataFire RAS ISDN adapters and multiple DataFire/AccelePort RAS adapters: Multiple AccelePort/DataFire RAS Adapters SCO's netcfg utility uses adapter configuration order to assign device names. DataFire RAS adapters and AccelePort adapters have three sets of devices added at netcfg configuration time. They are /dev/mdi/dgisdn for network (ISDN) access, /dev/term/dgasyn for asynchronous ports and /dev/dxbkme, /dev/dxbrasmon<1-6> and /dev/dxbutil for adapter utilities. In addition, netcfg also creates a /dev/net device for each /dev/mdi/dgisdn device. is assigned by netcfg based on adapter configuration order. The first configured adapter is 0, the second is 1 and so on. is port number and, depending on which adapter is being configured, can range from 0-8 to 0-60. is the netcfg network number and is determined by network configuration order for all defined network adapters. For example, if one ethernet adapter is configured followed by an ISDN adapter followed by another ethernet adapter, the first ethernet adapter is net0, the first ISDN adapter is net1 and the second ethernet adapter is net2. If you wish to remove ANY NETWORK ADAPTER via netcfg, it is necessary to remove ALL NETWORK ADAPTERS that were configured AFTER the targeted adapter, reboot the machine, and then re-configure the adapters that you wish to keep. Failure to do so can result in devices that no longer map to the correct adapter, loss of all network functionality and/or inability to start the desktop. Note that removing an adapter from the middle or start of a multiple adapter configuration will result in device name changes, even if you follow the above rules. The value is assigned by the OS and cannot be made static. Mult-Line DataFire RAS Adapters If configuring one or more adapters, any number of which are Multi-Line ISDN adapters, all first/only lines must be configured before any second, third or fourth lines on Multi-Line ISDN adapters can be configured. For example, if you have a four-line BRI adapter, a two-line T1 adapter and an AccelePort asynchronous adapter, you MUST configure the first line on the BRI adapter, the first line on the T1 adapter and the asynchronous adapter (in any order you choose) before configuring lines 2, 3, or 4 on the BRI adapter and line 2 on the T1 adapter (again, in any order). Failure to do so can result in devices that no longer map to the correct adapter, loss of all network functionality and/or inability to start the desktop. NOTE: Multi-Line adapters have their asynchronous devices and adapter utility devices built for the first line only. NOTE: Adapters can be modified at any time and in any order with no effect on other adapters. Changes made via netcfg modify will take affect after the next re-boot. Additional Notes: * The agent for Port Assist must be started manually by executing the following command: /etc/conf/inst/nd/mdi/dgdxb/agent & Or un-comment out the above line in the start up script /etc/rc2.d/S95mkstz. * There is a problem with 'netcfg' that will not allow both sync2000 and digiras adapters to be configured in the same system. You can get around this problem by having only the bcfg file present for the adapter you are configuring. * There is a memory leak that occurs when removing and re-installing the digiras package without rebooting the machine in between. * The program '/usr/local/bin/rasmon' can be run to monitor configured ISDN and async devices supported by this driver. * Only the first line of a multi line adapter will show up in netcfg until the first line is configured. * When configuring a mult-line adapter, the lines must be removed in the opposite order in which they were installed. * For AccelePort RAS adapters, you will get the following messages that are informational only and do not affect the operation of the adapter or the protocol stack. NOTE: dgisdn: Open to non-ISDN device (/dev/mdi/dgisdn) dlpid: Unable to open network adapter driver (/dev/mdi/dgisdn) dlpid: No such file or directory 4. KNOWN PROBLEMS 1 If you get an "net on /dev/mdi/dgisdn is inoperable See /etc/inst/nd/mdi/dgisdn/rnotes under Known Problems 1" message during re-boot, it is due to netcfg limitations for configuring Digi Multi-Line ISDN adapters. On a Multi- Line adapter (a two-line T1 or E1 or a four-line BRI adapter), netcfg is able automatically to detect only the first line. Once the first line has been configured, Digi scripts make the subsequent lines visible to netcfg for configuration. Because of the resmgr and netcfg limitations, it is ABSOLUTELY NECESSARY that ALL Digi DataFire/AccelePort RAS adapters have their first/only line configured via netcfg BEFORE ANY second, third or fourth lines on any multi-line adapters are configured. If an additional Digi DataFire/ AccelePort adapter is to be added to a system that already has a configured multi-line adapter, ALL Line TWO, THREE and FOUR configurations must be removed via netcfg prior to inserting the new adapter. After the new adapter has been configured via netcfg, all of the line two, three and four configurations can be re-done via netcfg. NOTE that all devices associated with re-added adapters will change, including the net device. 2 If you get an "net on /dev/mdi/dgisdn is inoperable See /etc/inst/nd/mdi/dgisdn/rnotes under Known Problems 2" message during re-boot, it is due to resmgr limitations for maintaining Digi Multi-Line ISDN adapters. On a Multi- Line adapter (a two-line T1 or E1 or a four-line BRI adapter), lines TWO, THREE and FOUR can be configured only after all Digi RAS line ONEs have been configured. Conversely, in order to remove a line ONE via netcfg for a Multi-Line adapter, it is necessary to first remove lines TWO, THREE and FOUR for that adapter. If you see the above error message, it means that a Multi-Line adapter line ONE has been removed via netcfg without first removing lines TWO, THREE, and FOUR for that adapter. Digi RAS shutdown and/or startup scripts detected the condition and have unconfigured and removed the netcfg entries as needed. In order to restore the ISDN lines affected, you must first configure the Multi-Line ISDN adapter's line ONE and then configure lines TWO, THREE and FOUR. * There is a creeping instance number problem that causes device names to change if removing and adding with netcfg without rebooting the system in between. The problem can also be caused if multiple adapters are configured and then removed in a different order than they were configured. If removing an adapter through netcfg, reboot the system before adding the adapter back into the system. * When configuring adapters, you must choose the correct adapter type in netcfg until netcfg is capable of properly detecting the adapter type. * When removing the last configured dgisdn adapter via netcfg, the following messages are displayed on the console. There is no obvious problem related to this error message, everything seems to work correctly. dlpid: StopInterface: Unable to find DLPI interface (net) in internal table dlpid: RemoveInterface: Unable to find DLPI Interface (net) in internal table * There is a bug in UnixWare 7.0.1 that causes kernel panics when disconnecting from a digiras async port. The patch ptf7096d will correct this problem. It can be found at ftp://ftp.sco.com/SLS or ftp://ftp.digi.com/support/drivers/unix_svr4/released/async * The netcfg program may abort if there are third party devices in /etc/uucp/Devices. Until a fix is provided by SCO for this problem, you must remove the third party devices from /etc/uucp/Devices before running netcfg. * After removing an adapter from NETCFG, the O.S. must be rebooted to complete the adapter's removal process. The networks will still be operational until after the reboot. * As of the date of this release, the serial manager will only set up ports for PPP with the flags 'oP'. If you want to run a standard login shell, execute the command /usr/local/bin/fixmon after the port is configured through the serial manager. This program will allow you to set or clear the 'oP' flags. If the 'oP' flags are set, the ttymon will not attach to the port (open it), and you will never get the modem to answer. * The modems associated with async ports supported by this driver are auto detectable through 'scoadmin modem'. You can modify the dialer script '/etc/uucp/default/RAS_modem_56000' to customize your initialization strings. * In release 7.0.1 of UnixWare, PPP configuration of ISDN lines through netcfg assumes BRI, causing only two B-channel links to be defined. To define the rest of the B-channel links and make them available for PPP configuration, you must define them via ppptalk. For ISDN PRI lines over T1, you can define up to 21 additional B-channel links and for ISDN PRI lines over E1, you can define up to 28 additional B-channel links. Note that before using ppptalk to add the additional B-channel links to your ISDN PRI PPP bundle, you must have first configured it via netcfg. To add links via ppptalk, type "ppptalk list bundle ". Choose one of the links listed in "links = link_". Then type "ppptalk copy link link_ ", once for each additional B-channel link you wish to add to the bundle. Note that must be unique for each link, but the same link_ can be used for all of the commands. When all of the desired links have been added type "ppptalk bundle links=old_link_1 old_link_2 new_link_name1 ..., INCLUDING ALL of the links in the bundle, old and new. You may wish to adjust minlinks and maxlinks at this time with "ppptalk bundle minlinks=x" and "ppptalk bundle maxlinks=y". At this point your changes are permanent but will take effect only at the next re-boot. To have them take effect immediately, you must type "ppptalk reset bundle ". This causes and all of its links to be reset. 5. HISTORY Changes in this release: * Added support for AccelePort Xp adapters. * Added transparent print support. * Added Port Assist Manager support. * Ported Linux tcl/tk/tix dm_gui GUI (using swig1p5, tcl7.6, tk4.2 and tix4.1). * Added fep tools support. * Bugs fixed: - ldterm is now pushed on top of Async driver. That fixed a lot of NIST test failures. - NIST test: The test does not hang any more. - tbench test: "No incomplete sequence number" fixed. - dpa showed up to eight configured boards. - Multiple instances of dpa open failed. - Fix GET_SERIAL_CHANNEL_MODE for PAM to show the right information. - PAM COMM agent failure is a SCO issue. To get around that the package is required to be built on a UnixWare 7.0.1 platform. * Switch from tcl7.6/tk4.2 to tcl8.0/tk8.0 for dm_gui. A copy of these release notes can be found in: /etc/inst/nd/mdi/dgisdn/rnotes