| Thanks for the response.
> That depends on how the FDDI server is configured. If it is
> configured for SNAP encapsulation, then it will not be able to
> communicate with the 802.2 clients.
The customer is in a state of transition going from 802.3 to 802.2. For
now, there will be both types of clients running. Eventually, all the
802.3 clients will disappear.
He will be using a DEFEA on the FDDI server. Assuming that he does not use
SNAP encapsulation, then he should be able to talk to both types of clients
(802.3 1nd 802.2) through a DECswitch 800EF, correct?
|
| Whatever format you pick for the server, whether 802.2 or SNAP,
it will not work with SNAP or 802.2 clients repectively. Unless the
adapter allows you to use multiple formats simultaneously which
I don't believe is possible. You might want to run this by
Larry Stefani (from Adapter Engineering).
Anil
|
|
Assuming I can bind multiple frame types to the adapter (I know we can do
this with the Ethernet adapters), will the DECswitch 900EF translate it
back properly?
Concern is :
Coming back from the server, the Translate function on the EF will just
translate all IPX into 802.3. In this case, the 802.2 clients will not
be able to receive anything back from the server.
Does anyone have any experience with this?
|
| From: YESWAY::stefani "Larry Stefani" 30-JUN-1995 08:30:03.31
To: trooa::leong
CC: netcad::anil, yesway::stefani
Subj: Re: Will the DEFEA support multiple formats
Leslie,
All of our ODI server drivers support loading the driver reentrantly for
multiple frame types. However, this is only a NetWare server supported
function. NetWare clients do NOT support multiple frame types for IPX. You
pick one and stick with it.
Based on the description you gave, your customer needs to
A. Enable the "raw 802.3 IPX" switch in the EF bridge. This will
make the bridge translate the ETHERNET_802.3 IPX packets into
standard FDDI_SNAP IPX packets (and vice-versa).
B. Load the DEFEA.LAN driver twice at the server and bind IPX twice.
For example your AUTOEXEC.NCF entries might look like this:
LOAD DEFEA.LAN SLOT=4 FRAME=FDDI_SNAP NAME=F_SNAP
LOAD DEFEA.LAN SLOT=4 FRAME=FDDI_802.2 NAME=F_8022
BIND IPX TO F_SNAP NET=01
BIND IPX TO F_8022 NET=02
The ETHERNET_802.3 IPX clients will communicate on IPX network 01
while the ETHERNET_802.2 IPX clients will communicate on IPX
network 02.
C. Only use ETHERNET_802.3 or ETHERNET_802.2 for IPX clients on the
Ethernet. Do NOT use ETHERNET_II for IPX clients.
The reason for Step C. is because once the "raw 802.3 IPX" switch is thrown,
all of the ETHERNET_802.3 IPX traffic and ETHERNET_II IPX traffic will go across
the EF bridge as FDDI_SNAP. BUT (!!) the bridge will translate it BACK as
ETHERNET_802.3, which means that any ETHERNET_II IPX traffic won't work once
the switch is thrown. You can still use ETHERNET_II for other protocols
(eg. TCP/IP), but not IPX once you throw the switch.
That should do it. Eventually, they can move all of the ETHERNET_802.3 IPX
clients over to ETHERNET_802.2, then either leave FDDI_SNAP loaded for other
protocols, remove it and only run FDDI_802.2, or simply unbind IPX from
FDDI_SNAP.
If you have any questions on this, please let me know.
Regards,
Larry
P.S. Make sure the customer uses the latest DEFEA driver diskette (v2.4) off
KALI::PCDRIVERS:[DEFEA.RELEASE]FEKIT240.ZIP.
|