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

Conference turris::digital_unix

Title:DIGITAL UNIX(FORMERLY KNOWN AS DEC OSF/1)
Notice:Welcome to the Digital UNIX Conference
Moderator:SMURF::DENHAM
Created:Thu Mar 16 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:10068
Total number of notes:35879

9593.0. "netstat counter - receive failures" by SNOFS1::IPSSG_FL () Wed Apr 23 1997 06:26

    
    I have an AlphaWorkstation 255/233 and an Ethernet card as 
    tu0: DEC TULIP Ethernet Interface / DECchip 21040-AA: Revision: 2.4
    
    The box is running on Digital UNIX V4.0a.  When I did the command
    "netstat -i -s", I realised that the counter for "receive failures" was 
    keep increasing.  Can anyone explain to me what the error for ?  
    
    Thanks.........
    
    tu0 Ethernet counters at Wed Apr 23 19:21:53 1997
    
            1712 seconds since last zeroed
        10255702 bytes received
        10195809 bytes sent
           21702 data blocks received
           21190 data blocks sent
           75379 multicast bytes received
             434 multicast blocks received
             405 multicast bytes sent
               7 multicast blocks sent
             153 blocks sent, initially deferred
              88 blocks sent, single collision
              88 blocks sent, multiple collisions
               0 send failures
               0 collision detect check failure
            1471 receive failures, reasons include:   <-------
                    Block check error			<-----
               0 unrecognized frame destination
               0 data overruns
               0 system buffer unavailable
               0 user buffer unavailable
    
    
T.RTitleUserPersonal
Name
DateLines
9593.1alphy.lkg.dec.com::thomasThe Code WarriorWed Apr 23 1997 13:414
The CRC check on received Ethernet packets is failing.  You probably have
a bad cable or connector somewhere in your network.  (in other words, bits
on you ethernet are getting munged and the CRC check is catching most of
those packets with munged bits)
9593.2see if it's just youSMURF::DUSTINWed Apr 23 1997 15:069
    And you can compare other machines on the same segment with your
    machine, and if they are seeing input errors too, then it's not
    your specific network cable, it's something in the LAN wiring
    elsewhere.
    
    If it's only your system, check your own connection to the LAN.
    
    John