network connection speed 100mbit instead of 1gbit

drickner · 2. August 2016

I have an HP Proliant DL380 G7 server with gbit broadcom cards in it running OMV 2.5 and it is refusing to connect faster than 100mbit. Here is the output of ethtool:

Settings for eth2:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
MDI-X: off
Supports Wake-on: g
Wake-on: g
Link detected: yes

sudo ethtool -i eth2:
driver: bnx2
version: 2.2.5
firmware-version: bc 5.2.3
bus-info: 0000:04:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no

It was working fine before I ran an omv-update, but now it won't connect any faster. I tried manually setting it with this:

ethtool -s eth2 speed 1000 duplex full autoneg on

That gives no errors, but it bumps me off the network, and issuing ifup eth2 doesn't get me back online (can't ping anything until I reset it to 100mbit).

I then thought maybe upgrading to version 3.0 would help, but it did not.

Suggestions?

Frogdaddy · 12. August 2016

I notice when you run your last ethtool command to force 1000 full you still specify autoneg on. In my experience autonegotiate can be somewhat temperamental. Meaning, don't use it if you don't have to.

Try turning auto-neg off, then set the nic to 1gbps. Also, you've confirmed on your router the port you're connected to is in fact 1gbps supported? For example, on my router the lights are amber signifying the device that is plugged into that port is 1gbps, versus being green at 100 Full. If this doesn't work for you, you may have to supply your syslog or messages from /var/log directory, it may show something. It may also be a driver issue, not sure.

Enra · 12. August 2016

Hi,

first I would check the cabling.
If your cable doe not meet the requirements, it is possible, that the link connects at 100 Mbit instead of 1GE.

Jetzt mitmachen!