[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::etherworks

Title:EtherWORKS Notes Conference
Notice:WWW server at http://ftp.digital.com/pub/DEC/adapters/
Moderator:NETCAD::STEFANI
Created:Wed Sep 01 1993
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1318
Total number of notes:5673

1272.0. "DEFPA,ODI 3.20" by SUTRA::sutra::zuntini (PCBU Support Europe) Thu Mar 06 1997 08:59

One of our reseller post the (1) and (2) following question, any help would 
be appreciated.

-armand.
========================================================================
Currently, we are using a DEFPA-AA FDDI controller in our Netware 3.11
fileserver (Pentium 100 MHz). Some DOS/Windows stations are directly
connected to the fileserver by SMC EtherPower boards, others are using
an Ethernet/FDDI bridge for connection. Unfortunately, we have found
network problems, immediately after installing DEFPA-AA.

(1) Stations connected through Ethernet/FDDI bridge obtain "General
    network error" when trying to attach to our server on FDDI. Numerous
    other servers in our campus are available, and work fine.
(2) Stations connected directly to SMC boards experience an extremely
    slow network, and repeaters in this segment show an almost continuous
    jam condition.

We have tried the following technics to overcome the problems:

 -- As a test, we installed DEFPA-AA in a DOS station, using DOS/ODI
    Netware drivers. Originally, we got "General network error" condition
    as a DOS station, too.
 -- Thereafter, we have upgraded the firmware with the latest
    3.10 version. Also, the latest DOSODI driver DEFPA.COM was applied
    from fpkit281.zip. Finally, this solved the problem on DOS level.

Unfortunately, I cannot follow the same method for Netware 3.11, as
I understood from the descriptions belonging to fpkit281, the new server
driver DEFPA.LAN uses ODI specification 3.30, consequently 3.11 servers
cannot support it.

So, please, send me information about the following questions:

(1)  What is the latest DEFPA.LAN supporting ODI 3.20, and where is it
     available. (Currently, we are using version 2.25 (941208).)
(2)  Is the following technics described by SMC in their latest driver
     kit applicable for using 3.12 DEFPA.LAN on a 3.11 server?

# NOTE: You can either use the above scheme or load the 3.12
#       files from the 3.12 directory on 3.11 to get the most
#       updated MSM and ETHERTSM.
# load patchman
# load lslenh
# load a3112
# load nbi31x
# load msm31x
# load ethertsm

T.RTitleUserPersonal
Name
DateLines
1272.1Try upgrading your server softwareNETCAD::THOMPSONThu Mar 06 1997 14:4631
    
    
Armand,

Novell has publicly stated that their current ODI specification v3.10 will only
support LAN operation on NetWare v3.12, NetWare v4.10 and NetWare v4.11 
(IntranetWare I).  Any LAN driver written to this specification will only
be supported on the above operating systems.

As a result, we have decided to drop support for any other NetWare operating
systems, since it would mean maintaining a separate driver to support these 
older, legacy versions like NetWare v3.11.

So you are right, you need a LAN driver written to a v3.2 ODI spec to be able
to operate correctly on your NetWare v3.11 server.  Currently, NPB/ELNAC does
not make any LAN drivers which support the v3.2 ODI spec available to the
world at large.  You *may* (and I emphasize may) be able to get such a driver 
written to the v3.2 spec if you were to be very, very nice to Larry...

However, a much cleaner fix would be to encourage your customer to upgrade 
their server to a more recent version of NetWare.  Frankly, v3.11 is very old,
and lots of improvements have been made to the operating system since then
which your customer would be able to take advantage of.  Your customer would
also be able to run the latest and greatest *fully supported* ODI LAN driver 
from our web site.  This would almost certainly get rid of any "general network 
error" messages that you may be seeing.

regards,
-Brenda

1272.2NETCAD::STEFANIFDDI Adapters R UsFri Mar 07 1997 08:5333
As a followup to others reading this thread.  I sent the older DEFPA SW kit
manufacturing release v2.70 to Armand.  This kit contains a certified ODI 3.2
AHSM spec driver which should work on NetWare 3.11.  I am NOT making this kit
publicly available on our SW electronic distribution sites, but if there are
other requests for it, please ask.

>>(2)  Is the following technics described by SMC in their latest driver
>>     kit applicable for using 3.12 DEFPA.LAN on a 3.11 server?
>>
>># NOTE: You can either use the above scheme or load the 3.12
>>#       files from the 3.12 directory on 3.11 to get the most
>>#       updated MSM and ETHERTSM.
>># load patchman
>># load lslenh
>># load a3112
>># load nbi31x
>># load msm31x
>># load ethertsm

The LSLENH patch is familiar to anyone who has written ODI drivers for NetWare
3.11, but I'm not familiar with A3112.  It sounds like a shim to allow
newer ODI 3.3 AHSM spec drivers to work on NetWare 3.11.  If that's the case,
you would load the latest DEFPA.LAN driver (v3.30 6/6/96) similar to the
above, just replace ETHERTSM with FDDITSM.

Novell Labs has previously told developers that they are not supporting 3.3
spec drivers under anything less than NetWare 3.12 and 4.10.  I'd be very
surprised to see them now making a patch to support NetWare 3.11.  Can you
type MODULES and tell me the version, name, date, and copyright information for
A3112.NLM?

Thanks,
   Larry