Results 1 to 16 of 16
Thread: Force full duplex, this how?
-
12-23-2005, 11:41 AM #1Local tech for Los Angeles
- Join Date
- Feb 2003
- Location
- Panorama City, CA
- Posts
- 2,581
Force full duplex, this how?
ifcfg-eth0
ETHTOOL_OPTS="speed 100 duplex full autoneg off"
then restart the network?
For some reason i totally forgot.. I'm getting some slow speeds on a Cisco 2900 switch (on the switch).
-dmesg-
Code:eth0: network connection up using port A speed: 100 autonegotiation: yes duplex mode: half flowctrl: none irq moderation: disabled scatter-gather: enabled
-
12-23-2005, 02:53 PM #2Local tech for Los Angeles
- Join Date
- Feb 2003
- Location
- Panorama City, CA
- Posts
- 2,581
hmm well that didn't work..
I did a full reboot dmesg shows the same, any ideas?
logs say this..
Code:Dec 23 07:56:43 webby ifup: Cannot get current device settings: Operation not supported Dec 23 07:56:43 webby ifup: not setting speed Dec 23 07:56:43 webby ifup: not setting duplex Dec 23 07:56:43 webby ifup: not setting autoneg
MotherBoard Asus P4P-800-E DeluxeLast edited by Jeremy; 12-23-2005 at 03:00 PM.
-
12-23-2005, 08:14 PM #3Hosting provider
- Join Date
- May 2002
- Location
- Moscow
- Posts
- 1,602
on linux you can use mii-tools as i remember for check what happen with your nic (include his capabilities)
TK Rustelekom LLC Dedicated server since 2002, RIPE NCC member, LIR
-
12-23-2005, 09:55 PM #4Disabled
- Join Date
- Dec 2004
- Posts
- 229
You can either as someone suggested use mii-tool
# mii-tool
No opitions, tells you the status of the link
# mii-tool eth0 -F 100baseTx-FD
will force 100Mb Full Duplex .. won't always work though
# mii-tool eth0 -A 100baseTx
Will advertise both full and half duplex. If your switch link is locked at half duplex, then you need to make the switch port full duplex as well.
You can use ethtool from command line too
# ethtool -s eth0 speed 100 duplex full autoneg off
or
# ethtool eth0
to see the supported options, no need to restart the network when changing the interface via mii-tool or ethtool.
# mii-tool
Will tell you where you are at and where you finish up.Last edited by DigitalN; 12-23-2005 at 09:59 PM.
-
12-24-2005, 01:37 AM #5Web Hosting Master
- Join Date
- Feb 2003
- Location
- Detroit
- Posts
- 860
Both ends of the connection need to have the same setting. Set the switch to 100/full first then the machine. most of the time, auto does work well. If your switch is not set to auto right now try that first.
ManagedWay
Connecting people through technology
Cloud Computing | Fiber Optic Internet | Colocation
-
12-24-2005, 02:59 AM #6Predatory Poster
- Join Date
- Jul 2003
- Location
- Goleta, CA
- Posts
- 5,566
Auto negotiate can cause a lot of problems though. I agree with setting both sides as the above poster stated.
Patron: I'd like my free lunch please.
Cafe Manager: Free lunch? Did you read the fine print stating it was an April Fool's joke.
Patron: I read the same way I listen, I ignore the parts I don't agree with. I'm suing you for false advertising.
Cafe Owner: Is our lawyer still working pro bono?
-
12-24-2005, 03:17 AM #7Web Hosting Master
- Join Date
- Feb 2003
- Location
- Detroit
- Posts
- 860
Originally Posted by pixelized
You have a machine set to auto and the switch set to 100/full you may have problems.ManagedWay
Connecting people through technology
Cloud Computing | Fiber Optic Internet | Colocation
-
12-24-2005, 07:30 AM #8Disabled
- Join Date
- Dec 2004
- Posts
- 229
The problems I have seen setting network connection parameters with mii-tool has been due to a crappy switch, that advertises either half or full duplex.. no autoneg
In these cases, ethtool saves the day by making your interface not try to autonegotiate. (mii-tool does not work in these cases I find)
So imho, you really need to look at your switch first, as that is likely the cause of the problem.
-
12-24-2005, 07:51 AM #9Local tech for Los Angeles
- Join Date
- Feb 2003
- Location
- Panorama City, CA
- Posts
- 2,581
Hmmm the ports are forced 100mbps/fd.
i still get the error
Code:Dec 23 07:56:43 webby ifup: Cannot get current device settings: Operation not supported Dec 23 07:56:43 webby ifup: not setting speed Dec 23 07:56:43 webby ifup: not setting duplex Dec 23 07:56:43 webby ifup: not setting autoneg
-
12-24-2005, 07:57 AM #10Disabled
- Join Date
- Dec 2004
- Posts
- 229
What does
# mii-tool
reveal?
What is your switch set to?
-
12-24-2005, 11:26 AM #11Local tech for Los Angeles
- Join Date
- Feb 2003
- Location
- Panorama City, CA
- Posts
- 2,581
Code:[root@webby ~]# mii-tool eth0 SIOCGMIIPHY on 'eth0' failed: Bad address
Code:[root@webby ~]# mii-tool -F 100baseTx-FD eth0 SIOCGMIIPHY on 'eth0' failed: Bad address
my route table looks fine, i can shell in and out of it.
-
12-25-2005, 07:48 AM #12Local tech for Los Angeles
- Join Date
- Feb 2003
- Location
- Panorama City, CA
- Posts
- 2,581
Thank you all for your help so far.
on the switch the commandCode:show run
Code:interface FastEthernet0/9 description LAX09-DM duplex full speed 100 switchport access vlan 30 spanning-tree portfast
Code:eth0: network connection up using port A speed: 100 autonegotiation: yes duplex mode: half flowctrl: none irq moderation: disabled scatter-gather: enabled ------- divert: allocating divert_blk for eth0 eth0: Yukon Gigabit Ethernet 10/100/1000Base-T Adapter PrefPort:A RlmtMode:Check Link State
Code:[root@webby ~]# mii-tool SIOCGMIIPHY on 'eth0' failed: Bad address no MII interfaces found
-
12-27-2005, 04:44 AM #13Disabled
- Join Date
- Dec 2004
- Posts
- 229
Try
# ethtool -s eth0 speed 100 duplex full autoneg off
Does that work for you?
Failing that, I would look at changing the switch port and then the network card interface.
-
12-28-2005, 05:44 AM #14Local tech for Los Angeles
- Join Date
- Feb 2003
- Location
- Panorama City, CA
- Posts
- 2,581
Code:[root@webby ~]# ethtool -s eth0 speed 100 duplex full autoneg off Cannot get current device settings: Operation not supported not setting speed not setting duplex not setting autoneg
-
12-28-2005, 05:48 AM #15Disabled
- Join Date
- Dec 2004
- Posts
- 229
It might be best to try setting your switch to 'autonegotiate' rather than forcing full duplex, then set the interface to 'autonegotiate' too.
Try another network card if all fails, looks like your card doesn't want to be played around with, maybe a driver issue or just the card won't take the changes.
I'd try autonegotiate both ends, different switch port, then try another nic card.
-
12-28-2005, 05:53 AM #16Local tech for Los Angeles
- Join Date
- Feb 2003
- Location
- Panorama City, CA
- Posts
- 2,581
I was thinking this to, Dont know why this is such a pain.
Thanks for your help.