Conference netcad::hub_mgnt

2605.0. "Probewatch Error Reporting...?" by RDGENG::GREID (All that is, was and will be...) Thu Aug 03 1995 14:06

    I have been investigating some network response problems on one 
    of our LAN segments recently and noticed that the Packetprobe 90
    and the HP Analyzer both report different findings for errors on the
    segment. 
    
    For instance, using the STATS package on the HP Analyzer which is as I 
    understand it, listening to every packet going by, one afternoon
    reported no errors other than 3 Jabbers.
    
    The PacketProbe 90 however reported at least one Jabber in every
    polling interval of 30 seconds for the same period. 
    
    So, who's telling the truth ??
    
    Also how do you get the Probe to zoom in on these errors so you can see
    who is responsible. The HP has a BAD Packet monitor which once invoked 
    will display the bad frame along with the physical address source.
    With the Segment Zoom window the Short Term History will say how many
    errors seen and what type but not from who ?
    
    Am I missing the point here, or do I need to turn something else on in
    Probewatch ?
    
    Giles.

>>   Also how do you get the Probe to zoom in on these errors so you can see
>>    who is responsible. The HP has a BAD Packet monitor which once invoked 
>>    will display the bad frame along with the physical address source.
>>    With the Segment Zoom window the Short Term History will say how many
>>    errors seen and what type but not from who ?

 You must define a new Domain using Domain editor application including
 only the bad Frame for capture.

  Jean-Yves

    Jean-Yves,
    
    	Ok I have done as you suggested, however on a Segment Zoom for this
    	new domain, the Short Term History is at the moment incrementing 
    	the collision counter but hasn't entered a single node in the top
        10 hosts collumn, so what tells you where the errors are from.?
    
    	Giles.

 use the data capture under this domain.

 JYP