redhat-list@redhat.com
[Top] [All Lists]

RE: NIC Duplex Settings RHEL 5.2 tg3

Subject: RE: NIC Duplex Settings RHEL 5.2 tg3
From: "Jeremey Wise"
Date: Wed, 17 Sep 2008 16:39:02 -0400
I was not very clear in my last response... 

The email was intended to say "thanks" and fyi it works.

I was also wondering if Ezra's NIC was Intel what his settings were...
so I could see if there is a way I can translate the settings to Intel
which is in some of the other servers in the lab.

Jeremey Wise
Senior Consultant
Arrow Enterprise Computing Solutions
RHCE,MCSE,CNE,PSE,TSM

-----Original Message-----
From: Jeremey Wise 
Sent: Wednesday, September 17, 2008 3:54 PM
To: 'General Red Hat Linux discussion list'
Subject: RE: NIC Duplex Settings RHEL 5.2 tg3

Thanks for the reply 

The options in each of the physical interfaces seemed to be ok the
settings post 'service network restart' were:
ETHTOOL_OPTS="speed 100 duplex full autoneg off"

[root@7969cle3 network-scripts]# ethtool eth0
Settings for eth0:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  Not reported
        Advertised auto-negotiation: No
        Speed: 100Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: off
        Supports Wake-on: g
        Wake-on: g
        Current message level: 0x000000ff (255)
        Link detected: yes
[root@7969cle3 network-scripts]# ethtool eth1
Settings for eth1:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  Not reported
        Advertised auto-negotiation: No
        Speed: 100Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: off
        Supports Wake-on: g
        Wake-on: g
        Current message level: 0x000000ff (255)
        Link detected: yes
[root@7969cle3 network-scripts]#


Does your system have Broadcom NICs vs Intel / other?
Is their a way to query the tg3 module to see if those parameters being
passed are valid? Their was no output into /var/log/messages to reflect
any error on the parameters:

Sep 17 15:44:23 7969cle3 avahi-daemon[4907]: Interface bond0.IPv6 no
longer relevant for mDNS.
Sep 17 15:44:23 7969cle3 kernel: ADDRCONF(NETDEV_UP): bond0: link is not
ready
Sep 17 15:44:23 7969cle3 kernel: bonding: bond0: Adding slave eth0.
Sep 17 15:44:23 7969cle3 kernel: ADDRCONF(NETDEV_UP): eth0: link is not
ready
Sep 17 15:44:23 7969cle3 kernel: bonding: bond0: enslaving eth0 as a
backup interface with a down link.
Sep 17 15:44:23 7969cle3 kernel: bonding: bond0: Adding slave eth1.
Sep 17 15:44:23 7969cle3 kernel: ADDRCONF(NETDEV_UP): eth1: link is not
ready
Sep 17 15:44:23 7969cle3 kernel: bonding: bond0: enslaving eth1 as a
backup interface with a down link.
Sep 17 15:44:24 7969cle3 kernel: tg3: eth0: Link is up at 100 Mbps, full
duplex.
Sep 17 15:44:24 7969cle3 kernel: tg3: eth0: Flow control is off for TX
and off for RX.
Sep 17 15:44:24 7969cle3 kernel: ADDRCONF(NETDEV_CHANGE): eth0: link
becomes ready
Sep 17 15:44:24 7969cle3 kernel: bonding: bond0: link status definitely
up for interface eth0.
Sep 17 15:44:24 7969cle3 kernel: bonding: bond0: making interface eth0
the new active one.
Sep 17 15:44:24 7969cle3 kernel: bonding: bond0: first active interface
up!
Sep 17 15:44:24 7969cle3 kernel: ADDRCONF(NETDEV_CHANGE): bond0: link
becomes ready
Sep 17 15:44:25 7969cle3 kernel: tg3: eth1: Link is up at 100 Mbps, full
duplex.
Sep 17 15:44:25 7969cle3 kernel: tg3: eth1: Flow control is off for TX
and off for RX.




Jeremey Wise
Senior Consultant
Arrow Enterprise Computing Solutions
RHCE,MCSE,CNE,PSE,TSM
JWise@xxxxxxxxx

-----Original Message-----
From: redhat-list-bounces@xxxxxxxxxx
[mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Ezra Taylor
Sent: Wednesday, September 17, 2008 2:47 PM
To: General Red Hat Linux discussion list
Subject: Re: NIC Duplex Settings RHEL 5.2 tg3

Jeremey:
               Put something similar to this in your
/etc/sysconfig/network-scripts/ifcfg-eth? file(s)


ETHTOOL_OPTS="speed 1000 duplex full autoneg off"

On Wed, Sep 17, 2008 at 8:21 AM, Jeremey Wise <jwise@xxxxxxxxx> wrote:
> I have a lab. I am building a RHEL 5.2 cluster. I am bringing up the
> nodes and need to get HA working for the network stack. I have
hardcoded
> each of the interface connections of the two CISCO 3548 switches at
> 100Mb Full Duplex.
>
>
>
> Hardware:
>
> IBM e326m
>
> Kernel: 2.6.18-92.el5
>
> NIC: tg3
>
>
>
> cat /etc/modprobe.conf
>
> alias eth0 tg3
>
> alias eth1 tg3
>
> alias bond0 bonding
>
> options bond0 mode=1 miimon=100 max_bonds=2
>
>
>
> [root@7969cle3 net]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
>
> MASTER=bond0
>
> SLAVE=yes
>
> TYPE=Ethernet
>
> DEVICE=eth0
>
> HWADDR=00:11:25:c4:93:c6
>
> BOOTPROTO=none
>
> ONBOOT=yes
>
> USERCTL=no
>
> IPV6INIT=no
>
> PEERDNS=yes
>
> [root@7969cle3 net]# cat /etc/sysconfig/network-scripts/ifcfg-eth1
>
> MASTER=bond0
>
> SLAVE=yes
>
> TYPE=Ethernet
>
> DEVICE=eth1
>
> HWADDR=00:11:25:c4:93:c7
>
> BOOTPROTO=none
>
> ONBOOT=yes
>
> USERCTL=no
>
> IPV6INIT=no
>
> PEERDNS=yes
>
> [root@7969cle3 net]# cat /etc/sysconfig/network-scripts/ifcfg-bond0
>
> DEVICE=bond0
>
> IPADDR=10.23.48.8
>
> NETMASK=255.255.255.0
>
> BROADCAST=10.23.48.255
>
> GATEWAY=10.23.48.1
>
> ONBOOT=yes
>
> BOOTPROT=none
>
> USERCTL=no
>
> PEERDNS=no
>
> # HWADDR=00:11:25:c4:93:c6
>
> # IPV6INIT=no
>
> [root@7969cle3 net]#
>
>
>
> [root@7969cle3 net]# ifconfig
>
> bond0     Link encap:Ethernet  HWaddr 00:11:25:C4:93:C6
>
>          inet addr:10.23.48.8  Bcast:10.23.48.255  Mask:255.255.255.0
>
>          inet6 addr: fe80::211:25ff:fec4:93c6/64 Scope:Link
>
>          UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
>
>          RX packets:110166 errors:0 dropped:0 overruns:0 frame:0
>
>          TX packets:24536 errors:0 dropped:0 overruns:0 carrier:0
>
>          collisions:1720 txqueuelen:0
>
>          RX bytes:16599941 (15.8 MiB)  TX bytes:11244999 (10.7 MiB)
>
>
>
> eth0      Link encap:Ethernet  HWaddr 00:11:25:C4:93:C6
>
>          inet6 addr: fe80::211:25ff:fec4:93c6/64 Scope:Link
>
>          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
>
>          RX packets:62430 errors:0 dropped:0 overruns:0 frame:0
>
>          TX packets:24512 errors:0 dropped:0 overruns:0 carrier:0
>
>          collisions:1720 txqueuelen:1000
>
>          RX bytes:9382249 (8.9 MiB)  TX bytes:11238386 (10.7 MiB)
>
>          Interrupt:177
>
>
>
> eth1      Link encap:Ethernet  HWaddr 00:11:25:C4:93:C6
>
>          inet6 addr: fe80::211:25ff:fec4:93c6/64 Scope:Link
>
>          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
>
>          RX packets:47736 errors:0 dropped:0 overruns:0 frame:0
>
>          TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
>
>          collisions:0 txqueuelen:1000
>
>          RX bytes:7217692 (6.8 MiB)  TX bytes:6613 (6.4 KiB)
>
>          Interrupt:185
>
>
>
> lo        Link encap:Local Loopback
>
>          inet addr:127.0.0.1  Mask:255.0.0.0
>
>          inet6 addr: ::1/128 Scope:Host
>
>          UP LOOPBACK RUNNING  MTU:16436  Metric:1
>
>          RX packets:11851 errors:0 dropped:0 overruns:0 frame:0
>
>          TX packets:11851 errors:0 dropped:0 overruns:0 carrier:0
>
>          collisions:0 txqueuelen:0
>
>          RX bytes:3847241 (3.6 MiB)  TX bytes:3847241 (3.6 MiB)
>
>
>
> [root@7969cle3 net]#
>
>
>
> [root@7969cle3 net]# ethtool eth0
>
> Settings for eth0:
>
>        Supported ports: [ TP ]
>
>        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: g
>
>        Current message level: 0x000000ff (255)
>
>        Link detected: yes
>
> [root@7969cle3 net]# ethtool eth1
>
> Settings for eth1:
>
>        Supported ports: [ TP ]
>
>        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: g
>
>        Current message level: 0x000000ff (255)
>
>        Link detected: yes
>
> [root@7969cle3 net]#
>
>
>
> ** Notice that the interfaces are Half Duplex
>
> [root@7969cle3 net]# mii-tool -v
>
> eth0: no autonegotiation, 100baseTx-HD, link ok
>
>  product info: vendor 00:08:18, model 53 rev 0
>
>  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
>
> eth1: no autonegotiation, 100baseTx-HD, link ok
>
>  product info: vendor 00:08:18, model 53 rev 0
>
>  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@7969cle3 net]#
>
>
>
> ** Mii-tool concurs the half duplex state
>
>
>
> I ran the command
>
> mii-tool -F 100baseTx-FD eth0
>
> mii-tool -F 100baseTx-FD eth1
>
>
>
> I did a diff of output above to output after running (it did
disconnect
> my ssh session as it renegotiated the links) but no difference.
>
>
>
> Tried to see what options I COULD set against the tg3 module:
>
> [root@7969cle3 net]# modinfo -p tg3
>
> tg3_debug:Tigon3 bitmapped debugging message enable value
>
>
>
> ????
>
>
>
>
>
> Questions:
>
> 1)       Where in /proc is duplex settings held
>
> 2)       Am I correct in my assumption that settings established via
> mii-tools or ethtools are NOT persistent across reboot and so settings
> must be established in /etc/modules.conf to be persistent.
>
> 3)       What module parameters do I set to force speed and duplex
with
> confidence it is correct?
>
>
>
> Thanks,
>
>
>
> Jeremey Wise
> Senior Consultant
> Arrow Enterprise Computing Solutions
> RHCE,MCSE,CNE,PSE,TSM
> JWise@xxxxxxxxx <mailto:JWise@xxxxxxxxx>
>
>
>
>
>
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subjectunsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
>



-- 
Ezra Taylor

-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

<Prev in Thread] Current Thread [Next in Thread>