Section 7.5. Network Errors


7.5. Network Errors

Errors can occur from network collisions and as such are a normal occurrence. With hubs they occurred so often that various rules were formulated to help us know what really was a problem (> 5% of packet counts).

Three types of errors are visible in the previous netstat -i output, examples are:

  • output:colls. Collisions. Normal in small doses.

  • input:errs. A frame failed its frame check sequence.

  • output:errs. Late collisions. A collision occurred after the first 64 bytes were sent.

The last two types of errors can be caused by bad wiring, faulty cards, auto-negotiation problems, and electromagnetic interference. If you are monitoring a microwave link, add "rain fade" and nesting pigeons to the list. And if your Solaris server happens to be on a satellite, you get to mention Solar winds as well.




Solaris Performance and Tools(c) Dtrace and Mdb Techniques for Solaris 10 and Opensolaris
Solaris Performance and Tools: DTrace and MDB Techniques for Solaris 10 and OpenSolaris
ISBN: 0131568191
EAN: 2147483647
Year: 2007
Pages: 180

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net