Red HatThis forum is for the discussion of Red Hat Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
IBM x360 server: Ran fine for a year on Redhat AS2.1 on the same subnet it's on now. Re-installed to Redhat AS3.0 and after about a month, the NIC started to go offline once per day or so. At the console, we see:
You can bring the adapter back on-line by removing and re-inserting the ethernet cable, or by bringing the interface down and back up again. Originally running the e100 driver. Changed to eepro100 today as a test. Holding steady using the older eepro100 driver, but saw some "overruns" in ifconfig output.
Before the NIC goes off-line, we see a build up of "overruns" packets listed in "ifconfig eth0" output,such as the following:
RX packets:363057100 errors:0 dropped:0 overruns:452 frame:0
When the NIC goes off-line, that "overruns:" value may be around 12,000 packets.
Note also, that this same problem has happened on 4 servers, all identical hardware and software on the same subnet. Very random, but we've seen all four servers experience the problem at the same time a couple of times.