eth1 failure

mepefe · 10-24-2006, 01:28 PM

Hi there.

I have errors in the eth1 interface, my Linux server has 3 NICs, two 3com nics, and a realtek nic.
My question is:

How can i know wich one is my interface that is failure?

Thanks

Mepefe

farslayer · 10-24-2006, 02:30 PM

You can check the dmesg log to see what NIC has been assignet which designation (eth0, eth1, eth2)

IBM-300GL-1:~# cat /var/log/dmesg | grep eth
eth0: ADMtek Comet rev 17 at 00015400, 00:50:BF:96:B0:4D, IRQ 15.
eth1: ADMtek Comet rev 17 at 00015000, 00:50:BF:97:81:BA, IRQ 11.

If it's the realtek card with errors that should be a gimme to figure out which of the 3 cards it is..

Otherwise unplug the network cables from the NICs' one at a time, and check for a message in the Systems logs as you unplug the cable to identify which card is which.

If for some reason no message is generated, unplug one card, then ping something that should be on that segment..

Then you can take your Sharpie or P-Touch and label the NIC's so you will know for the future.

hockeyman_102 · 10-24-2006, 02:52 PM

How do you know you have a failure? If one is simply having a hardware failure - couln't you plug them into a switch or something and look for link lights on the actual port?

farslayer · 10-24-2006, 08:28 PM

By failure I don't think he means total failure no Link light.. more like Lots of errors you know like when you do ifconfig and it lists all that bonus information..

Code:

          RX packets:2904756 errors:0 dropped:0 overruns:0 frame:0
          TX packets:710292 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000

But with 3 cards if you didn't take the time to identify them initially, it's sometimes confusing to match the ethX designations to the physical hardware.

Also errors can be caused by misconfiguration of an interface. for instance if you FORCE a PC NIC to run at 100Mbps FULL-DUPLEX and plug it into a switch. Auto-negotiation will fail and the switch will default to 100Mbps Hafl-Duplex and you will tehn start to accumulate a lot of errors, since the 2 interfaces now have a duplex mismatch.

mepefe · 10-26-2006, 11:50 AM

Hi Farslayer.
You right,the light Link is On, but if i run ifconfig this is the output.

eth1 Link encap:Ethernet HWaddr 00:80:AD:88:39:F3 inet addr:165.98.138.97 Bcast:165.98.138.111 Mask:255.255.255.240 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:228 dropped:0 overruns:0 carrier:228 collisions:0 txqueuelen:100 Interrupt:10 Base address:0xflost of pcakets

Quote:

Originally Posted by farslayer

By failure I don't think he means total failure no Link light.. more like Lots of errors you know like when you do ifconfig and it lists all that bonus information..

Code:

          RX packets:2904756 errors:0 dropped:0 overruns:0 frame:0
          TX packets:710292 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000

But with 3 cards if you didn't take the time to identify them initially, it's sometimes confusing to match the ethX designations to the physical hardware.

Also errors can be caused by misconfiguration of an interface. for instance if you FORCE a PC NIC to run at 100Mbps FULL-DUPLEX and plug it into a switch. Auto-negotiation will fail and the switch will default to 100Mbps Hafl-Duplex and you will tehn start to accumulate a lot of errors, since the 2 interfaces now have a duplex mismatch.

farslayer · 10-27-2006, 07:22 PM

228 errors, carrier up/down 228 times..

yes something definately doesn't look right there..

Did checking dmesg help ? did eth1 turn out to be the realtek card ? if so that would be easy toID since it will look different than the other two cards..

If eth1 isnt the realtek card, then I would try unplugging the network cables from the other cards one at a time and see which is which..