Intel Quad Port GE NIC Issues

[Mudhoney]

Having some issues after installing an Intel Pro 1000 GT Quad port NIC in a FC11 box. There is also an onboard gigE port which I am no longer using. I have two ports connected on the Intel NIC to different switches in different MAC domains with different subnets (DHCP). When the machine starts, or I run the network script I get incorrect interface config:

/etc/init.d/network restart

# /etc/init.d/network restart
Shutting down interface eth1:                              [  OK  ]
Shutting down interface eth2:                              [  OK  ]
Shutting down loopback interface:                          [  OK  ]
Bringing up loopback interface:                            [  OK  ]
Bringing up interface eth1:                                [  OK  ]
Bringing up interface eth2:                                [  OK  ]

# ifconfig 
eth1      Link encap:Ethernet  HWaddr 00:1B:21:32:A2:94  
          inet addr:192.168.110.100  Bcast:192.168.110.255  Mask:255.255.255.0
          inet6 addr: fe80::21b:21ff:fe32:a294/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:21790 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3153 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:1948424 (1.8 MiB)  TX bytes:446567 (436.1 KiB)

eth2      Link encap:Ethernet  HWaddr 00:1B:21:32:A2:95  
          inet addr:192.168.110.100  Bcast:192.168.110.255  Mask:255.255.255.0
          inet6 addr: fe80::21b:21ff:fe32:a295/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:15138561 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29001929 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:4234764286 (3.9 GiB)  TX bytes:39732652545 (37.0 GiB)

After I run dhclient, it resets itself to the configuration I want:

dhclient
[root@fez]# ifconfig 
eth1      Link encap:Ethernet  HWaddr 00:1B:21:32:A2:94  
          inet addr:192.168.110.204  Bcast:192.168.110.255  Mask:255.255.255.0
          inet6 addr: fe80::21b:21ff:fe32:a294/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:21829 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3804 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:1952715 (1.8 MiB)  TX bytes:598630 (584.5 KiB)

eth2      Link encap:Ethernet  HWaddr 00:1B:21:32:A2:95  
          inet addr:192.168.0.236  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::21b:21ff:fe32:a295/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:15139059 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29002000 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:4234855871 (3.9 GiB)  TX bytes:39732661321 (37.0 GiB)

# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.0     *               255.255.255.0   U     0      0        0 eth2
192.168.110.0   *               255.255.255.0   U     0      0        0 eth1
default         192.168.0.1     0.0.0.0         UG    0      0        0 eth2

Stuff now works as it should, but why is it not getting the correct config on boot? I have tried manually compiling and installing the Intel 1000 Pro drivers. The /etc/sysconfig/network-scripts directory has entries for ifcfg-eth1 and -eth2 and they look right.

Other info:

# lsmod | grep e1000
e1000                 186120  0 

# lspci | grep Ethernet
08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
0a:04.0 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet Controller (Copper) (rev 03)
0a:04.1 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet Controller (Copper) (rev 03)
0a:06.0 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet Controller (Copper) (rev 03)
0a:06.1 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet Controller (Copper) (rev 03)

#dmesg
[snip]
ADDRCONF(NETDEV_UP): eth1: link is not ready
e1000: eth1: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
ADDRCONF(NETDEV_UP): eth2: link is not ready
e1000: eth2: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
eth1: no IPv6 routers present
eth2: no IPv6 routers present

Thanks,

Mud

[diamond_ramsey]

Mud, could you do the following:

cd /etc/sysconfig/network-scripts

could you do a ifdown eth1 ifup eth1 and ifdown eth2 ifup eth2

then do a network restart

compare the values for both the ifcfg-eth1 and ifcfg-eth2 files within

cd /etc/sysconfig/networking/profiles/

examine under devices and profiles/default

[Mudhoney]

thanks, Diamond. This is much the same as what I already did I think, and the result is the same; when I do the network restart I get the original incorrect config back (same IP addresses on both NIC ports). The contents of the ifcfg-eth1 and 2 files look ok, ie. they contain the correct values, not the spurious ones:

# cat ifcfg-eth1 
# Networking Interface
DEVICE=eth1
BOOTPROTO=none
ONBOOT=yes
TYPE=Ethernet
IPV6INIT=no
USERCTL=no
IPADDR=192.168.0.236
NETMASK=255.255.255.0
GATEWAY=192.168.0.1
PREFIX=24
NAME="System eth1"
UUID=9c92fad9-6ecb-3e6c-eb4d-8a47c6f50c04

# cat ifcfg-eth2
# Networking Interface
DEVICE=eth2
BOOTPROTO=none
ONBOOT=yes
TYPE=Ethernet
IPV6INIT=no
USERCTL=no
IPADDR=192.168.110.204
NETMASK=255.255.255.0
PREFIX=24
NAME="System eth2"
UUID=3a73717e-65ab-93e8-b518-24f5af32dc0d

These look like this even when ifconfig shows the duplicate address on the NIC ports. Weird eh? Again, when I run dhclient it all corrects itself, but I suspect even then everything may not be 100% since networked apps i was previously running under Wine no longer work.

[Mudhoney]

hm acutally, looking at that, should bootproto = "dhcp"?

[diamond_ramsey]

Originally Posted by Mudhoney

hm acutally, looking at that, should bootproto = "dhcp"?

BOOTPROTO=none

may be hmmh...

should probably be BOOTPROTO=dhcp for both.

[Mudhoney]

yeah that fixed it

but WoW still won't work under Wine

[stevea]

1/ It's really really dumb to manually edit anything under /etc/sysconfig. Almost every file there has a dedicated config app. If you botch those files your system breaks and you'll never know why - they were meant to be changed by the programs and the interpreters assume the syntax is always correct. The content chages from time to time too.

Use system-config-network.

2/ DO NOT execute the ifdown-eth0 type scripts diretly. Again this is a huge mistake. These were meant to be run using the /sbin/ifup and ifdown comman like "ifdown eth0". The ifdown command sets up environment, calls other initialization scripts and THEN runs ifdown-eth0 ((or other interface)).


3/ Yes you should set dhcp using system-config-network, and also remove the IP, mask & gateway terms.
==
Do you have any idea how both ifaces got the same IP = 192.168.110.100 ? That is creepy/strange and deserves investigation. Any old dhcp leases laying about ?

========
My question to Mud. Do your Intel 82546 interface support Jumbo packets ? If so how large. I seem to recall this being a problem with some 825XX parts.

[diamond_ramsey]

Originally Posted by Mudhoney

yeah that fixed it

but WoW still won't work under Wine

Mudhoney, if you have not seen, here's a useful this URL for WoW -

http://appdb.winehq.org/objectManage...sion&iId=17421

[Mudhoney]

Originally Posted by stevea

1/ It's really really dumb to manually edit anything under /etc/sysconfig. Almost every file there has a dedicated config app. If you botch those files your system breaks and you'll never know why - they were meant to be changed by the programs and the interpreters assume the syntax is always correct. The content chages from time to time too.

Use system-config-network.

2/ DO NOT execute the ifdown-eth0 type scripts diretly. Again this is a huge mistake. These were meant to be run using the /sbin/ifup and ifdown comman like "ifdown eth0". The ifdown command sets up environment, calls other initialization scripts and THEN runs ifdown-eth0 ((or other interface)).

ok thanks for the advice.

Originally Posted by stevea

3/ Yes you should set dhcp using system-config-network, and also remove the IP, mask & gateway terms.

done

Originally Posted by stevea

==
Do you have any idea how both ifaces got the same IP = 192.168.110.100 ? That is creepy/strange and deserves investigation. Any old dhcp leases laying about ?

========

I think you're onto something there. It could be because I swapped the cables between ports 1 and 2 on the NIC a few days ago, and maybe some old lease info was hanging around somewhere in there.

Originally Posted by stevea

My question to Mud. Do your Intel 82546 interface support Jumbo packets ? If so how large. I seem to recall this being a problem with some 825XX parts.

Hm not sure how to tell? ethtool doesn't seem to tell me. We use these cards at my work for performance testing as we have found they perform much better than the quad port D-links we used to use.

[diamond_ramsey]

Originally Posted by stevea

1/ It's really really dumb to manually edit anything under /etc/sysconfig. Almost every file there has a dedicated config app. If you botch those files your system breaks and you'll never know why - they were meant to be changed by the programs and the interpreters assume the syntax is always correct. The content chages from time to time too.

Use system-config-network.

2/ DO NOT execute the ifdown-eth0 type scripts diretly. Again this is a huge mistake. These were meant to be run using the /sbin/ifup and ifdown comman like "ifdown eth0". The ifdown command sets up environment, calls other initialization scripts and THEN runs ifdown-eth0 ((or other interface)).


3/ Yes you should set dhcp using system-config-network, and also remove the IP, mask & gateway terms.
==
Do you have any idea how both ifaces got the same IP = 192.168.110.100 ? That is creepy/strange and deserves investigation. Any old dhcp leases laying about ?

========
My question to Mud. Do your Intel 82546 interface support Jumbo packets ? If so how large. I seem to recall this being a problem with some 825XX parts.

stevea, you are correct about commands and files. Was trying to see where inconsistencies may exist.

[Mudhoney]

Originally Posted by diamond_ramsey

Mudhoney, if you have not seen, here's a useful this URL for WoW -

http://appdb.winehq.org/objectManage...sion&iId=17421

Thanks. It was working perfectly in the past but it looks like I'm getting an X11 error now, so most likely unrelated to the network problem. Could be caused by yum updates, wouldn't be the first time.

[diamond_ramsey]

Originally Posted by Mudhoney

Thanks. It was working perfectly in the past but it looks like I'm getting an X11 error now, so most likely unrelated to the network problem. Could be caused by yum updates, wouldn't be the first time.

Mudhoney, okay! May be create a separate post if things do not get better, that would be best.

[Mudhoney]

wow issue fixed by reinstalling xorg-x11-drv-ati

Probably belongs in a different thread but the problem's already solved so I won't start one.

[diamond_ramsey]

Originally Posted by Mudhoney

wow issue fixed by reinstalling xorg-x11-drv-ati

Probably belongs in a different thread but the problem's already solved so I won't start one.

Mudhoney, most excellent, good to hear!!!

I would like to see any of your results regarding performance testing "Intel Pro 1000 GT Quad port NIC" found versus the quad port D-links...

Have a great weekend.

[sej7278]

Originally Posted by stevea

1/ It's really really dumb to manually edit anything under /etc/sysconfig. Almost every file there has a dedicated config app.

woaaaaaaaaaaaah there big boy!

its not dumb, if you know what you're doing you can get a lot more out of editing the config files than using the system-config-* programs, many of which are way too simplified or plain broken.

back to the topic though, personally i'd not use dhcp and just manually configure each of the four nics with a fixed ip, binding to their mac addresses too (so the next upgrade of kuzdu or devmapper can't screw things up).