Release Notes 93000305_B2P for Digi DataFire SYNC 2000 UnixWare 7 Package Release v1.1.0 Release Date: 12/04/98 Please reference the following number(s) when searching the Digi International FTP/WWW site for the latest software package: Software Image P/N 400001831_B2P These numbers are for informational purposes only: CD-ROM Software Image P/N 400001625_B2P This Digi software package includes device drivers for the DataFire SYNC 2000 product supported under UnixWare 7.0.1. This release includes support for multiple Host Adapters per system, and a Graphical software configuration interface that operates under the X-Windows environment. The following Host Adapters are supported on this release: DataFire SYNC 2000 + 4P PCI P/N 77000641 DataFire SYNC 2000 4P PCI P/N 77000642 DataFire SYNC 2000 + 2P PCI P/N 77000643 DataFire SYNC 2000 2P PCI P/N 77000644 The following SCO Unixware patch(es) must be applied to the Unixware 7.0.1 Operating System in order to support this package: PTF7038 - Fixes DDI8 io driver problems PTF7053 - Fixes netcfg problems Software limitations: * DLCI's greater then 991 are not supported. Unless the dlci is being used for LMI (Line Management Interface). Additional Notes: * For SNA support, DataFire SYNC 2000 for UnixWare 7 uses the IBM eNetwork Communications package. * When configuring X.25 over SNA, if you do not set "Call User Data Matching" to your SNA CUD in the "QLLC port" Advanced screen, then X.25 over IP will fail as SNA is in a mode to attempt to receive all packets, which will include any sent from a different CUD. The current CUD can be determined from the "QLLC link station" Advanced screen. * For SNA over Frame Relay, DataFire SYNC 2000 for UnixWare 7 associates the IBM eNetwork Communications package Token Ring card MAC address with Frame Relay's combination of the Protocol ID, DLCI number, and Subnet ID. Using the lssnadev tool located in /opt/sna/bin, the following associations can be made: card_type adapter address MAC Address TOKEN_RING 0 444947490041 000500100041 TOKEN_RING 1 444947490042 000500100042 TOKEN_RING 2 444947490043 000500100043 TOKEN_RING 3 444947490044 000500100044 TOKEN_RING 4 444947490145 000500100145 TOKEN_RING 5 444947490146 000500100146 1) The final 4 digits for the address and the MAC address from wancfg, SFRE screen, will match. 2) These 4 digits are indicative of board number and subnet id as depicted within the /opt/snet/etc/syncconf file (see below). 3) All values related to SFRE are shown in hexidecimal. (eg. 0010 = 16 = DLCI number, 42 = 'B' = Subnet ID) 4) Example: IBM adapter 4 is associated with Adapter 1, Subnet ID 'E', protocol id 5 (TOKEN_RING), and DLCI 16. * An effort has been made to automate the 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 utilites: * (TCP/IP ONLY ) ping, netstat, route, ifconfig, slink, strcf * (IBM C/S) Refer to the SNA user's manual. * Your Frame Relay/X.25 network will attempt to come up on reboot. If this is undesirable, disable the start scripts via wancfg (GUI). * 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. * The easiest way to correlate adatper/port combinations with the Subnet ID is to view the /opt/snet/etc/syncconf file. wans 0 0 A def def stackA - SDLC wans 0 1 B WAN84 LC_LAPBDTE stackB 5551212 X25 wans 0 2 C WAN84 FR_DTE stackC 0 FRAME wans 0 3 D WAN84 FR_DTE stackD - FRAME wans 1 0 E def def stackE - SDLC wans 1 1 F WAN84 FR_DTE stackF 1 FRAME wans 1 2 G ? ? ? ? ? wans 1 3 H ? ? ? ? ? In the above example, a 4 port adapter is located as adapter 0. A 2 port adapter has been configured 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) SDLC is configured for Adapter 0, port 0, and is assigned Subnet ID 'A'. 2) SDLC is also configured for Adapter 1, port 0, and is assigned Subnet ID 'E'. 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 2 and 3, and assigned Subnet IDs 'C' and 'D', respectively. 5) Frame Relay is also configured for Adapter 1, port 1, and is assigned Subnet ID 'F'. 6) Furthermore, for Frame Relay, the eighth field indicates: '0' : only SFRE configured for that Subnet ID '-' : only IFRE configured for that Subnet ID '1' : both SFRE and IFRE configured for that Subnet ID 7) Assuming a 4 port adapter instead of a 2 port adapter, then Adapter 1 ports 2 and 3 would be unconfigured. Known Problems: * On some non-SCSI platforms, NETCFG will abort with Tcl errors when switching to the WAN view. This is caused by a SCO UnixWare 7 bug. To work around this problem, remove the following files from the /etc/inst/nd/mdi path that do not have installed adapters present. These files can be saved off to a temporary location. /etc/inst/nd/mdi/5ess/5ess-isa.bcfg /etc/inst/nd/mdi/atel/atel-isa.bcfg /etc/inst/nd/mdi/etsi/etsi-isa.bcfg /etc/inst/nd/mdi/japan/japan-isa.bcfg /etc/inst/nd/mdi/ni1/ni1-isa.bcfg