| That's odd, why is the customer doing something (using raw 802.3 frame
type), that even Novell doesn't recommend anymore? Novell has mentioned
many times (publicly), that they do not recommend using this frame
format anymore because of its incompatibility, and interoperability
problems. Hmmmmm, maybe the customer isn't aware of Novell's
current stand on this.
Bob
|
| >>will use raw 802.3 frame for their Novell. As we know, Digital FDDI
>>devices do not support this frame type. Now, the customer will purchase
Have you read related Notes 1717, 1400, and 1596 in the RANGER::NETWARE
conference? There has already been long diatribes (mostly by me) on
why the ETHERNET_802.3 frame type is a bad idea in mixed FDDI/Ethernet
networks.
I believe 3Com uses MAC frames to "encapsulate" the raw 802.3 frames
from one Ethernet segment to another Ethernet segment across an FDDI
ring. I don't have first hand experience with this, however.
Bottom line is that Novell does *NOT* support anything but FDDI_802.2
and FDDI_SNAP for IPX. Your goal should be to get standard IPX frames
on the FDDI ring, any which way you can. Once that's accomplished
(either by routing or translation) you can safely connect to FDDI
servers and clients and also send those frames onto other network
segments.
- Larry
|
| P.S. If you read 269.2 in the SCHOOL::GIGASWITCH notes conference,
you'll find that if you are running the current release of
GIGAswitch/FDDI firmware, the "raw mode" frames should pass through the
GIGAswitch/FDDI system successfully regardless of how brain-dead an idea
it might be to use them.
MDL
|