[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

2138.0. "Lots of Collision Test Failed on DECbridge 900MX " by VAXSPO::INTERD_MARIO () Fri Mar 24 1995 10:43

    Hi,
    
    A DECbridge 900MX is showing a pretty high number of Collision Test
    Failed. I got the values bellow from Netview (MIB field
    private.dec.ema.decmibextetensions.elanext.ebridge.ebrinterfaces.
    ebrifethertable.ebrifetherentry.ebrifeth.CollisionTestFailed). These
    values were checked using Hubwatch.
    
    All the 6 Ethernet ports were showing the same value for Collision Test
    Failed (8,600,000), while the number o transmitted frames were
    different on each port: 
    port 2: 35,000,000 TX frames
    port 3: 22,000,000
    port 4: 27,000,000
    port 5:  9,000,000
    port 6:  1,000,000
    port 7:    853,000
    
    
    1) An ethernet interface can show a high number of collision detect failed
    if a transceiver doesn't have SQE set proprerly, but since the values
    are the same, I can't find which of the 4 10baseT / 2 AUI can be
    causing the problem. Can anybody explain why the numbers are equal???
    
    2) Can anyone explain in details how the bridge measures the collision
       test failed? 
    
    
    Another question, related to the above:
    
    	A DECrepeater 900TM (32 10baseT) connected to another hub, was
    showing sqeTestError on all 32 ports.  (MIb field is
    ...ema...dechub900.repeater.rptversion1...SQETestError).
    
    3) Since on the other end of a TP cable there's a station, I can't
    underestand the meaning of this flag...
    
    
    
    Any comment will be apreciated!
    Mario
T.RTitleUserPersonal
Name
DateLines