how big is my NIC?

bigearsbilly · 03-02-2012, 03:42 AM

I am no sysadmin but have inherited a back end.

Is there a way from the command line to figure out
what spec NIC I have, like is it 10Mb 100Mb etc?

acid_kewpie · 03-02-2012, 04:00 AM

ethtool would be my first port of call. ifconfig should show you this too in less detail

zhjim · 03-02-2012, 04:04 AM

Code:

dmesg | grep eth

Code:

lspci | grep Ether

bigearsbilly · 03-02-2012, 04:18 AM

Quote:

Originally Posted by acid_kewpie

ethtool would be my first port of call. ifconfig should show you this too in less detail

well, these are knackered old servers with 2.4 kernels!
installing stuff is a headache.

---------- Post added 03-02-12 at 10:18 AM ----------

Quote:

Originally Posted by zhjim

Code:

dmesg | grep eth

Code:

lspci | grep Ether

cheers, that'll do!

acid_kewpie · 03-02-2012, 04:24 AM

Remember not to mix what the nic reports as vs what it's actually running as.

bigearsbilly · 03-02-2012, 09:49 AM

Quote:

Originally Posted by acid_kewpie

Remember not to mix what the nic reports as vs what it's actually running as.

oh that's right confuse me why don't ya!

zhjim · 03-05-2012, 03:03 AM

Especially without giving ways to see the used speed.

acid_kewpie · 03-05-2012, 03:23 AM

Quote:

Originally Posted by zhjim

Especially without giving ways to see the used speed.

Hang on... let me just get my handbag...

I already advised using ethtool in my first reply.

zhjim · 03-05-2012, 04:51 AM

Just poking you... some more

As the op said that he does not have ethool I looked for the infos that ethtool prints out under /proc but could not find a file that holds the information and so was hopping that you'll might know.

bigearsbilly · 03-05-2012, 09:34 AM

hey guys, I found this great app called ethtool

;-)

As an explanation, I'm trying to find why a machine is slow.
I know collisions are "normal" in ethernet, but I have none logged at all:

Code:

 $ ethtool -S eth0
     tx_collisions: 0
     tx_single_collisions: 0
     tx_mult_collisions: 0
     tx_excessive_collisions: 0
     tx_late_collisions: 0

So I take it to mean that the network is not under any strain at all.
Which probably means the bottleneck is not in the network or NIC.
Which is what I suspect anyway.

acid_kewpie · 03-05-2012, 09:37 AM

Well in terms of network hardware, the biggest reason for things being slow is duplex mismatch on a given connection, so make sure they are the same at both ends.

bigearsbilly · 03-05-2012, 05:17 PM

Quote:

Originally Posted by acid_kewpie

Well in terms of network hardware, the biggest reason for things being slow is duplex mismatch on a given connection, so make sure they are the same at both ends.

oh crikey!

I never wanted to be a sysadmin.
(well I did but I've changed my mind now)