We've just moved one a new server from our sever room, where I built it, to the datacenter. We want to force autoneg off, and tell it gigabit and full duplex. Using ethtool, I get no errors setting the speed or duplex. HOWEVER, autoneg on works... and autoneg off utterly refuses to work, and gives: ethtool -s eth0 autoneg off Cannot set new settings: Invalid argument not setting autoneg
We're on the most current update of CentOS (ok, last kernel, that will come up on the reboot I'll do shortly), and it's a Broadcom Corporation NetXtreme II BCM5716 Gigabit Ethernet
Anyone have an idea what's going on here?
mark
On Tue, Sep 28, 2010 at 03:51:17PM -0400, m.roth@5-cent.us wrote:
We've just moved one a new server from our sever room, where I built it, to the datacenter. We want to force autoneg off, and tell it gigabit and full duplex. Using ethtool, I get no errors setting the speed or duplex.
Note that the gigabit over copper standard _requires_ autoneg on. If you do manage to turn it off then you might break things unexpectedly.
http://en.wikipedia.org/wiki/Autonegotiation
In 1999, the negotiation protocol was significantly extended by IEEE 802.3ab, which specified the protocol for gigabit Ethernet, making autonegotiation mandatory for 1000BASE-T gigabit Ethernet over copper. Specifically Section 28D.5 Extensions required for Clause40 (1000BASE-T)
Stephen Harris wrote:
On Tue, Sep 28, 2010 at 03:51:17PM -0400, m.roth@5-cent.us wrote:
We've just moved one a new server from our sever room, where I built it, to the datacenter. We want to force autoneg off, and tell it gigabit and full duplex. Using ethtool, I get no errors setting the speed or duplex.
Note that the gigabit over copper standard _requires_ autoneg on. If you do manage to turn it off then you might break things unexpectedly.
http://en.wikipedia.org/wiki/Autonegotiation
In 1999, the negotiation protocol was significantly extended by IEEE 802.3ab, which specified the protocol for gigabit Ethernet, making autonegotiation mandatory for 1000BASE-T gigabit Ethernet over copper. Specifically Section 28D.5 Extensions required for Clause40 (1000BASE-T)
Thanks, Stephen, that looks like my answer. That server, and the dhcpd server, are both fat and happy on gigabit pipes.
mark
On Tue, 28 Sep 2010, m.roth@5-cent.us wrote:
We've just moved one a new server from our sever room, where I built it, to the datacenter. We want to force autoneg off, and tell it gigabit and full duplex. Using ethtool, I get no errors setting the speed or duplex. HOWEVER, autoneg on works... and autoneg off utterly refuses to work, and gives:
ethtool -s eth0 autoneg off Cannot set new settings: Invalid argument not setting autoneg
Did you turning off autoneg at the same time you set the speed and duplex?
ethtool -s eth0 speed 1000 duplex full autoneg off
Paul Heinlein wrote:
On Tue, 28 Sep 2010, m.roth@5-cent.us wrote:
We've just moved one a new server from our sever room, where I built it, to the datacenter. We want to force autoneg off, and tell it gigabit and full duplex. Using ethtool, I get no errors setting the speed or duplex. HOWEVER, autoneg on works... and autoneg off utterly refuses to work, and gives:
ethtool -s eth0 autoneg off Cannot set new settings: Invalid argument not setting autoneg
Did you turning off autoneg at the same time you set the speed and duplex?
ethtool -s eth0 speed 1000 duplex full autoneg off
That was where I started. And I also tried putting autoneg off first....
mark
-
m.roth＠5-cent.us -
Paul Heinlein -
Stephen Harris