topic Re: nic half to full duplex how to in Operating System - Linux

nic half to full duplex how to

ani007 — Tue, 15 Feb 2011 05:42:34 GMT

hi,
I want to change my lan card speed to full duplex. i tried the following but not working
[root@xxxx02 root]# ethtool -s eth0 speed 100 duplex full autoneg off
[root@xxxx02 root]# ethtool eth0
Settings for eth0:
Supported ports: [ MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Half
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: d
Current message level: 0x000000ff (255)
Link detected: yes

Red Hat Enterprise Linux ES release 3 (Taroon)
kernel version 2.4.21-4.ELsmp

Can u guys help?
REgards,
Ani

Re: nic half to full duplex how to

ani007 — Tue, 15 Feb 2011 06:22:19 GMT

ifconfig o/p

bond0 Link encap:Ethernet HWaddr 00:11:85:B7:8B:81
inet addr:138.35.252.97 Bcast:138.35.253.255 Mask:255.255.254.0
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:1633251 errors:0 dropped:0 overruns:0 frame:0
TX packets:113631 errors:1 dropped:0 overruns:0 carrier:0
collisions:1716 txqueuelen:0
RX bytes:349382988 (333.1 Mb) TX bytes:56275974 (53.6 Mb)

eth0 Link encap:Ethernet HWaddr 00:11:85:B7:8B:81
UP BROADCAST RUNNING NOARP SLAVE MULTICAST MTU:1500 Metric:1
RX packets:112927 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:17840369 (17.0 Mb) TX bytes:0 (0.0 b)
Interrupt:11

eth1 Link encap:Ethernet HWaddr 00:11:85:B7:8B:81
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:1520324 errors:0 dropped:0 overruns:0 frame:0
TX packets:113631 errors:1 dropped:0 overruns:0 carrier:0
collisions:1716 txqueuelen:1000
RX bytes:331542619 (316.1 Mb) TX bytes:56275974 (53.6 Mb)
Interrupt:15

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1745 errors:0 dropped:0 overruns:0 frame:0
TX packets:1745 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:327857 (320.1 Kb) TX bytes:327857 (320.1 Kb)

Re: nic half to full duplex how to

Hemmetter — Tue, 15 Feb 2011 09:35:41 GMT

Hi Ani,

ask your LAN guys about the settings of the corresponding switchports. They also have to setup to "100/full autoneg off".

What happens if you set
# ethtool -s eth0 autoneg on
# ethtool eth0

# ethtool -r eth0
# ethtool eth0

# ethtool -i eth0
rgds
HGH

Re: nic half to full duplex how to

ani007 — Tue, 15 Feb 2011 10:40:18 GMT

[root@xxxxx02 bond0]# ethtool -s eth0 autoneg on
[root@xxxxx02 bond0]# mii-tool -v eth0
eth0: no autonegotiation, 100baseTx-HD, link ok
product info: vendor 00:08:18, model 22 rev 2
basic mode: autonegotiation enabled
basic status: autonegotiation complete, link ok
capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
link partner: 100baseTx-HD
=======================================

[root@xxx02 network-scripts]# ethtool -i eth0
driver: tg3
version: 2.2
firmware-version:
bus-info: 02:01.0
[root@xxx02 network-scripts]#
====================================
[root@xxxxxxx02 network-scripts]# cat ifcfg-eth0
DEVICE=eth0
USERCTL=no
ONBOOT=yes
ETHTOOL_OPTS="speed 100 duplex full autoneg off"
MASTER=bond0
SLAVE=yes
BOOTPROTO=none
[root@xxxxxxx02 network-scripts]#
==================================
[root@xxxxxx02 network-scripts]# cat ifcfg-eth1
DEVICE=eth1
USERCTL=no
ONBOOT=yes
ETHTOOL_OPTS="speed 100 duplex full autoneg off"
MASTER=bond0
SLAVE=yes
BOOTPROTO=none

[root@xxxxxxxxxx02 network-scripts]# cat ifcfg-bond0
DEVICE=bond0
IPADDR=138.35.252.97
NETMASK=255.255.254.0
GATEWAY=138.35.252.1
USERCTL=no
BOOTPROTO=none
ONBOOT=yes
[root@xxxxxx02 network-scripts]#
=====================================

Re: nic half to full duplex how to

Matti_Kurkela — Tue, 15 Feb 2011 11:56:15 GMT

Your kernel version is 2.4.21-4.ELsmp, so your RHEL 3 installation has probably never received any security or bug-fix updates at all.

This is unfortunate, since the tg3 driver (which your NIC is using) contained multiple known bugs, which were fixed by RHEL 3 updates in 2004 or so. Your symptoms seem to match those bugs.

Please see:

https://bugzilla.redhat.com/show_bug.cgi?id=108115

https://bugzilla.redhat.com/show_bug.cgi?id=111250

https://bugzilla.redhat.com/show_bug.cgi?id=113982

There are other known bugs in RHEL 3's tg3 driver too:

https://bugzilla.redhat.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__all__&product=Red+Hat+Enterprise+Linux+3&content=tg3

Normally I would recommend you to install the necessary updates, but since RedHat has recently ended the support for RHEL 3, it may be difficult to get the updates.

MK