Frank McConnell ([log in to unmask]) wrote:
: A while back, Rex Warren <[log in to unmask]> wrote:
: >We have an HP 3000 series 52 running MPE V P 2 or something like
: >that.  It has a lanic card but we are having trouble connecting to our
: >LAN.  We get a transport warning or error whenever a 802.3 packet is
: >sent over the net.  Considering we have just switched over to newer
: >banyan and novell on our lan for PC's we have a lot of 802.3 packets.
 
: Quite some time ago I ran across this and found that it had to do with
: PCs sending semi-bogus 802.3 broadcast packets on the LAN.  (I don't
: remember the details of the bogosity, but I think it was a feature of
: Netware.)  When the 3000 saw one of these it displayed a "TRANSLATOR
: ERROR #312" message on the console; this was particularly annoying
: because the message is about half a screenful.
 
- Just to shed some light...  the TRANSLATOR... as reported in the error
  message is a piece of code living on classic HP3000's that "translates"
  MPE's IOQ-elements (i/o requests) to internal port messages and back.
 
  Translator error 312 meant (hope I remember this right) that there was no
  upper level recepient to send the message to.  This can typically be
  caused by Ethernet broadcasts entering the system (every lanic has to
  pick up a broadcast packet)...  if the system does not talk Ethernet.
  (I.e. ethernet not enabled or so).   Given that,  now the system tries
  to decode the frame as an IEEE802.2 frame, pulls out the Ethernet TYPE
  field or so and tries to decode it as an IEEE802.2 SAP (upper layer
  protocol address) where to send the packet to...  since this will not
  fly => translator error.
 
 
:-) Eero Laurila - HP CSY Networking lab,  NS services.