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

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
Created:Wed Nov 13 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4455
Total number of notes:16761

1725.0. "LAT decoding Questions" by PRIVAT::OTTO () Mon Nov 28 1994 10:48

Hello ,

I have a customer who uses a DECpacketprobe and probewatch V2.23
on a ultrix Workstation.
While trying to analyse a LAT problem the customer used the DATA CAPTURE
to capture Ethernet Frames with Protocol LAT.
While searching for specific information in the ethernet frames he discovered
the following:

whenever an ethernet frame contains more than one LAT message
the protocol decoder shows only the first message. To see the other
messages in the packet the customer has to decipher the frame 
by decoding the HEX values of the messages. This is very
unsatisfactory to the customer. (why using a protcol decoder when it doesn't
decode)

I have no experience in doing this kind of analysis (using a packetprobe)
Maybe someone more knowledgeable in the subject, is either able to 
tell that the customer has made a mistake /has overseen something, or
can tell whether, what the customer describes, is a fact/bug or product 
deviciency.



Thanks  OTTO
T.RTitleUserPersonal
Name
DateLines
1725.1will check outNAC::FORRESTFri Dec 02 1994 20:446
    I will follow up with the current Windows kit to see if this is the
    case. 
    
    Did the customer set a large enough "slice" size when setting up 
    the probe to capture data? The probe will only capture as far into 
    the packet as you instruct it to do.