[Intel Navigation Header]

    TokenExpress(TM) Adapter: NetWare for SAA 1.3 - Sample Configuration

    
    

    NOVELL NETWARE FOR SAA 1.3 - SAMPLE CONFIGURATION (6244)

    
       Release 5.0 (and later) of the Intel drivers provides support for Novell
    
       NetWare for SAA, version 1.3.  NetWare for SAA provides communication
    
       between LANs and IBM hosts.  Use the drivers for NetWare 4.x on the
    
       Release 5.0 diskette.  The 4.x drivers are found in the NETWARE\NW4X
    
       directory of the driver diskette.  The Release 5.0 diskette is available
    
       as an archive on Intel's online services.
    
    
    
       Novell's NetWare for SAA v1.3 can be installed in three different server
    
       types:
    
    
    
            NetWare 3.1x Server  (runtime version-dedicated SAA server, or
    
            standard server)
    
    
    
            NetWare 4.x Server  (runtime version-dedicated SAA server, or
    
            standard server)
    
    
    
       Driver Names
    
       ---------------------
    
    
    
       For TokenExpress: ISA 16/s, MCA, EISA 16:
    
    
    
            Novell NetWare 4.X and 3.1x Server Driver: OCTOK162.LAN,  v 3.00 or
    
            later
    
    
    
       For TokenExpress: EISA/32:
    
    
    
            Novell NetWare 4.X and 3.1x Server Driver: OC32T164.LAN, v3.03 or
    
            later
    
    
    
       The Following are examples of STARTUP.NCF and AUTOEXEC.NCF file which
    
       loads the OCTOK161.LAN driver with the Novell NetWare SAA Gateway 1.3
    
       software on an existing NetWare 3.1x server.
    
    
    
       Sample STARTUP.NCF
    
    
    
       load isadisk port=1F0 int=E
    
       set minimum packet receive buffers=500
    
       set maximum physical receive packet size = 4202
    
    
    
       Add this line to startup.ncf if using an ISA board in an EISA system:
    
    
    
       set reserved buffers below 16 meg = 64.
    
    
    
       SET MINIMUM PACKET RECEIVE BUFFERS command can help prevent 3270
    
       workstations from receiving network disconnects (a 590 error) from
    
       NetWare on a network with heavy communication traffic. When you set this
    
       command, you determine the minimum number of packet receive buffers that
    
       the operating system can allocate. Rather than waiting for requests to
    
       come in, the operating system allocates the minimum number of buffers as
    
       soon as the server boots.
    
    
    
       SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE:  This setting corresponds to
    
    
    
       the "Maximum Frame Size to Transmit Inbound" setting in CSCON. The Frame
    
       Size is the number of bytes to be included in frames being sent to the
    
       host. The default is 265, but you can raise this value to 521, 1033,
    
       2048, or 4202 bytes if the host system supports larger frame sizes
    
       (performance improves with larger frame sizes). This matches the MAXDAT=
    
       value in the host definition.
    
    
    
       Sample AUTOEXEC.NCF 
    
    
    
       One TokenExpress Adapter for both Host and LAN:
    
    
    
       file server name INTEL_TEST
    
       ipx internal net 312
    
       load clib
    
       load spxs
    
       load btrieve -u=1 -p=4096 -f=20 -h=60 -l=20 -c
    
       load lslenh
    
       load spxfix2
    
       load octok162 port=A20  int=5 name=token1 node=70930004 saps=2 ls=16
    
       bind ipx to token1 net=30
    
       load commexec
    
    
    
       Two TokenExpress Adapters - one for the Host and one for the LAN:
    
    
    
       file server name INTEL_TEST
    
       ipx internal net 312
    
       load clib
    
       load spxs
    
       load btrieve -u=1 -p=4096 -f=20 -h=60 -l=20 -c
    
       load lslenh
    
       load spxfix2
    
       load octok162 port=A20  int=5 node=70930004 saps=2 ls=16
    
       load octok162 port=A50  int=3 name=token1
    
       bind ipx to token1 net=30
    
       load commexec
    
    
    
       Four TokenExpress Adapters - two for the Host and two for the LAN:
    
    
    
       file server name INTEL_TEST
    
       ipx internal net 312
    
       load clib
    
       load spxs
    
       load btrieve -u=1 -p=4096 -f=20 -h=60 -l=20 -c
    
       load lslenh
    
       load spxfix2
    
       load octok162 port=A20  int=5 node=70930004 saps=1 ls=8
    
       load octok162 port=A24  int=4 node=70930005 saps=1 ls=8
    
       load octok162 port=A50  int=3 name=token1
    
       load octok162 port=A54  int=9 name=token2
    
       bind ipx to token1 net=30
    
       bind ipx to token2 net=40
    
       load commexec
    
    
    
       Note:     It may be necessary, depending on what version of NetWare you
    
       have, to specify a 12 digit node address instead of 8 digits when you
    
    
    
       are using Locally Administered Addresses. 
    
    
    
       Example: 
    
    
    
       load octok162 port=A20  int=5 node=400070930004 saps=1 ls=8
    
    

    Trademark information