(C)Copyright 1998 SysKonnect,
a business unit of Schneider & Koch & Co. Datensysteme GmbH.
All rights reserved
============================================================================

skfp.README

Readme File for Driver.o:
	SK-NET FDDI PCI Network driver for SCO UnixWare 7

Jul 16, 1998

Version / Date of the referred subject:
	skfp v1.03b01 / 16-Jul-1998

This file contains :
(1) Overview
(2) Supported Adapters
(3) Installation instructions
(4) Removing the driver
(5) Configuration of an adapter
(6) Deconfigure an adapter
(7) Advanced Device Configuration Parameters
(8) History

============================================================================


(1) OVERVIEW
============

This README explains how to use the SCO UnixWare 7 driver  'skfp'  with your
network adapter.

Chapter 2 contains a list of all network adapters that are supported by this
driver.

Chapter 3 describes the installation process.

Chapter 4 explains how to remove the driver software package from the system.

Chapter 5 explains how to configure the adapter.

Chapter 6 explains how to remove a network adapter.

Chapter 7 contains a detailed description of all advanced device
	  configuration parameters.
***


(2) SUPPORTED ADAPTERS
======================

The network driver 'skfp' supports the following network adapters:

			SK-NET FDDI PCI series
***


(3) INSTALLATION INSTRUCTIONS
=============================

To install the MDI driver from the SCO graphical user interface follow these
steps:

Step 1: Start the System Administration tool 'scoamin'

Step 2: Select 'Software Managment' menue.

Step 3: Select 'Application Installer' menue.

Step 4: Select your source media that contains the network driver package:
	DISK_A or Other. If you are installing from an install image file
	enter the folder and press 'Return' e.g.:/usr/spool/pkg/skfp.image
	Then hit the 'Install' button for software installation.

NOTE:
- You can also run the "scoadmin" - utility from the console login.
- Please also refer to your system documentation.

***

(4) REMOVING THE DRIVER
=======================

Before you can remove the network driver package from the system you should
deconfigure any existing logical network that is connected to the NIC.

Follow the steps below to remove the network driver from your system:

Step 1: Start the System Administration tool 'scoamin'

Step 2: Select 'Software Managment' menue.

Step 3: Select 'Application Installer' menue.

Step 4: Select the software package 'skfp'  from the list of:
	'All Applications Currently Installed on .....'

Step 5: Hit the 'Remove' button and respond to the next question with 'y'.

NOTE:
- You can also run the "scoadmin" - utility from the console login.
- Please also refer to your system documentation.

***

(5) CONFIGURATION OF AN ADAPTER
===============================

To configure the MDI driver from the SCO graphical user interface follow the
steps below:

Step 1: Start a UnixWare Desktop session (CDE) by logging into your system.

Step 2: Start 'scoadmin' or 'netcfg' . If you start 'netcfg' you can proceed
        with step 5 .

Step 3: Double click to the 'Networking' menue.

Step 4: Double click to the 'Network Configuration Manager' menue item.

Step 5: Click to the 'Hardware' menue and select 'Add new LAN adapter...'

	The configuration manager will display a list of network drivers for
	selection.

NOTE: if no network adapter is displayed by the configuration manager there
      is no such network deivice present that matches one of the vendor and
      device IDs supported by the installed driver software.

      There is no manual selection possible for PCI network devices as for
      example for ISA devices.

Step 6: Select the network device driver and proceed with configuration.
	Click the 'continue' button.

Step 7: A basic configuration menue is displayed that allows you to enter at
	least the alternate MAC address.

	You do not need to specifiy any of the configuration paramaters . If
	you do not enter a valid configuration value  the default value will
	be used by the driver. If you do not enter a valid MAC address or if
	you enter an invalid address the driver will use the default factory
	address.

Step 8: If you want to specify more driver specific configuration values you
	may open the 'advanced configuration menu' by clicking to the menue:
	'Advanced Options' . Please refer also to chapter 7.

Step 9: Finish the driver configuration by clicking to the 'OK' button.

Step 10: The window 'Add protocol' appears for protocol selection.
	 Select the protocol you want to run on the network driver and click
	 to the 'Add' button.

Step 11: Complete the protocol configuration and follow further steps.
	 Please refer also to your SCO documentation.

NOTE:
- You can also run the "netcfg" - utility from the console login to perform
  the above steps.
- Please also refer to your system documentation.

***


(6) DECONFIGURE AN ADAPTER
==========================

To remove an existing network configuration, perform the following steps:

Step 1: Start a UnixWare Desktop session (CDE) by logging into your system.

Step 2: Start 'scoadmin' or 'netcfg' . If you start 'netcfg' you can proceed
        with step 5 .

Step 3: Double click to the 'Networking' menue.

Step 4: Double click to the 'Network Configuration Manager' menue item.

Step 5: If you have already configured a network device the next window will
	display the corresponding network configuration. Remove the existing
	network configuration by selecting the hardware device and click the
	'Remove network device' item of the 'Hardware' menu.

	Confirm the subsequent question with 'yes' to remove the network.

NOTE:
- You can also run the "netcfg" - utility from the console login to perform
  the above steps.
- Please also refer to your system documentation.

***


(7) ADVANCED DEVICE CONFIGURATION PARAMETERS
============================================

This driver release supports configuration parameters that may not appear in
the driver's 'Advanced Configuration Menue'.

The following shows a list of all user configurable configuration parameters
that may or may not be displayed in the 'Advanced Configuration Menue'.

However each of the configuration parameter can be specified with the resmgr
command manually: resmgr -k <resmgr-key> -p <parameter>,<type> -v <value>

<resmgr-key> - the resource manager key of the network device that can be
	       displayed by: resmgr

<parameter>  - the name of the parameter that the network driver expects in
	       the configuration manager database.

<type>	     - either 's' for a string or 'n' for a numeric value.

<value>	     - the configuration value either a "string" or numeric value.

Sample:	resmgr -k 57 -p USERDATA,s -v "strings_must_not_contain_spaces"

The name in brackets shows the name of the configuration parameter as it is
expected in the configuration manager database . 's' and 'n'  indicate that
the value must be specified as a string or numeric value.

If no or an invalid configuration value is given to the network driver  the
network driver will always use the default value.


USER Data [USERDATA,s]:
User data to be passed to the SMT.
	
PMF password [PMFPASSWD,s]:
Parameter Management Frame (PMF) password for the adapter. A nonzero PMF
password enables authorization checking of the adapter for remote change
requests. A PMF password of 0 disables the authorization checking of the
adapter.The PMF password consists of 16 hexadecimal digits.Default value
is 0.

SMT T-Req [TREQ,n]:
This parameter provides local write access to the T-Req value that is
registered as fddiMAC 51 in the SMT Standard . The value for T-Req is
specified in milliseconds. The valid range is between 5 ms and 165 ms.
If an invalid value is specified, the default value for T-Req (165 ms)
is used.

SMT TVX lower bound [TVX,n]:
 This parameter provides local write access to the TVX attribute registered
as fddiMAC 54 in the SMT Standard. This attribute provides local control of
the recovery time from transient ring errors.The value for TVX is specified
in microseconds.The valid range is between 2500 us and 10000 us.The default
value is 2700 us.

NOTE:  Due to hardware limitations the upper value for the TVX attribute is
restricted to 5200 us. It is recommended to set a value below this limit.

Alternate MAC/SMT Address [MACADDR,s]:
This parameter specifies the alternate MAC address that is used instead of
the adapter's default factory address . A valid MAC address consists of 12
hexadecimal digits. The default value is none, in which case the adapter's
factory address is used. The valid address format is: xx:xx:xx:xx:xx:xx or
x:x:x:x:x:x or xx:x:xx:x:x:x::

SBA Payload [SBAPAYLOAD,n]:
This parameter defines the requested synchronous bandwidth for manual static
allocations. The valid range is between 0 and 1562 bytes per 125 us.
For example : if the required bandwidth is 1 MBits/s (125,000 Bytes/s) , the
value of the payload is 125,000 * 125E-6 = 15.625 round up to 16.The default
value is zero which means no synchronous bandwidth is used . The user should
define the amount of bandwidth to be able to send synchronous frames.If this
parameter is not specified, the keywords SBA OverHead, MaxTneg, MinSegment -
Size and SBA Category take no effect.
The end station supports either the static allocation model if the requested
payload is specified by the parameter SBA_Payload  or the dynamic allocation
model . This means that the required synchronous bandwidth is allocated by a
multimedia application. If a multimedia application can dynamically allocate
bandwidth, the parameter SBA PayLoad should not be specified.

SBA Overhead [SBAOVERHEAD,n]:
This parameter defines the requested overhead for static allocations.
The valid range reaches from 0 to 5000 bytes . If a value is specified which
is outside the limits, the upper/lower limit is taken . The default value is
50 bytes . This parameter has no effect, unless the parameter SBA PayLoad is
specified.

MaxTneg [MAXTNEG,n]:
 This parameter defines the maximum token rotation delay  that is acceptable
to the application(s) using synchronous bandwidth.The valid range is between
5 ms and 165 ms . The default value is 25 ms. This parameter takes no effect
unless the parameter SBA PayLoad is specified.

MinSegmentSize [MINSEGMSIZE,n]:
This parameter defines the minimum synchronous segmentation size . The value
corresponds to the number of bytes that will be transmitted on a  per  token
opportunity. The valid range is between 1 and 4478 bytes.The parameter takesno effect unless the parameter SBA PayLoad is specified.

SBA Category [SBACATEGORY,n]:
This parameter defines the session ID of the SBA Category for the static
allocation . The valid range is between 0 and 65535. This parameter takes no
effect unless the parameter SBA PayLoad is specified.

Syncronous Transfer Mode [SYNCHTXMODE,n]:
This parameter defines the synchronous transmission mode . The default value
is "SPLIT" that is represented by a numeric value of 0. This means that only
synchronous packets will be transmitted via the synchronous queue. The other
value is "ALL" that is represented by a numeric value of 1 . This means that
all LLC packets  received from upper protocol layers are transmitted via the
synchronous queue.The keyword takes no effect unless the end station support
is able to get the required synchronous bandwidth from the SBA.

SBA Available [SBAAVAILABLE,n]:
The parameter specifies the maximum synchronous bandwidth in percent that is
available for the primary path. The valid range is 0-100 . The default value
is 50.


Trace ring state [TRACE_CMD:n]:

   The driver supports a configuration parameter that allows the customer to
trace certain events in the network driver.

The only event that can be traced is changing the ring state.If the customer
sets the configuration parameter to 8 (bit 3) the driver will display syslog
messages both to the system log and the system console if the ring state has
been changed e.g. 'ring down','wrapped'... The default value is 0 that means
no tracing is active.

***

(8) HISTORY
===========

v1.01b01
    New features:
	Hot Plug PCI support.

    Problems fixed:
	-
    Known limitations:
	-

v1.00b14 - first beta customer ship

    New features:
	-

    Problems fixed:
	-

    Known limitations:
	- Support for SMP (synchronous multiprocessing) has been implemented
	  but has not been verified yet . So there is no warranty for proper
	  exectution on SMP platforms.

	- There is no warranty that all SMT parameters that the customer may
	  set are working properly. Changing the MAC address has been tested
	  and is working well.

	- Only TCP/IP and NFS protocol stacks have been tested . There is no
	  guarantee that IPX/SPX or other protocol stacks are working well.

	- Autoconfiguration of more than one network adapter may fail due to
	  to problems in the system's  autoconfiguration manager of BL15.2 .
	  If you plug in more than one NIC only one adapter can be  seen  on
	  the network configuration window
	
v1.01b04 

    New features:

	- HotPlugPCI support has been implemented. There is no warranty that
	  HotPlugPCI is working correctly unless the feature has been tested
	  successfully and reported by SysKonnect.

    Problems fixed:
	-

    Known limitations:
	- Support for SMP (synchronous multiprocessing) has been implemented
	  but has not been verified unless reported otherwise by SysKonnect.
	  So there is no warranty for proper exectution on SMP platforms.

v1.02b01
v1.02b02 - first final 

    New features:
	-

    Problems fixed:
	- Bugs have been fixed in the IOCTL path of the driver:
	  The driver did not respond correctly to the ioctls MACIOC_GETSTAT,
	  MACIOC_GETRADDR and MACIOC_GETADDR. An invalid lenght field in the
	  ioctl - response has been returned . As a consequence the receiver
	  of the ioctl response may discard the reply  and indicate an ioctl
	  failure.

	- Bugs have been fixed in the loop-back path of the transmit side :
	  The driver did not loop back multicast frames correctly  addressed
	  to a registered multicast address. The driver did not loop back tx 
	  frames correctly addressed to the NIC's current mac address.

    Known limitations:
	See previous release.

    Known problems:
    
    "Ping to remote host fails" : on certain UW7 releases you may experience
    some trouble with the ping request although your NIC has been  installed
    and the device driver has been configured correctly.
    The first ping request from the UnixWare7 host to a remote host may fail
    although the NIC is attached to the network correctly. Whenever you ping
    the UnixWare7 host from the remote host first  and subsequent pings from
    the UnixWare 7 host to the remote host work only after a  reception of a
    remote ping request you should check your network configuration.
    It may happen that the protocol stack generates a FDDI frame with source
    routing information that is probably discarded by the remote host. If so
    source routing for the corresponding network device must be disabled  as
    follows:

    1) Unconfigure any existing network device.Then add a new network device
    as shown in (5). Set the 'Source Routing' configuration parameter in the
    network driver's advanced configuration menue to 0(this is the default).
    Proceed with configuration.

    2) Start the SCO system administration manager 'scoadmin' and select the
    menues 'System' -> 'System Tuner' . Select the system tunable parameters
    for 'net NETx Network Driver Parameters' where x stands for the  network
    device index of your FDDI network (starting at 0) . Among different NETx
    configuration parameters you will find the parameter 'NETxSRSRMODE' that
    is probably set to the default value of 1 . Change this value to '0' and
    restart your UW7 system after rebuilding the kernel.

    Please note that the problem is not related to the network device driver
    but depends on the network configuration of the upper protocol stack. So
    you do not need to upgrade your network driver package.

***