Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
01-11-2005, 03:40 PM
|
#1
|
Member
Registered: Jul 2004
Posts: 90
Rep:
|
nic failover help
I'm trying to get a nic failover type of situation on an IBM blade server running RHEL3. I've got two nics visible to the OS, both using the bcm5700 driver. They are statically assigned, and have all the correct info in their respective ifcfg files. But i am not getting what I expect out of the setup.
Normal boot, eth0 is set to come up and eth1 is set to stay off. It comes up without a problem and networking works great. If I change this by making eth0 stay off and eth1 come up on boot, things don't work. ifconfig shows eth1 assigned the right ip and everything, but the network just doesn't work. That is until I use ethtool to turn on auto-negotiation. As soon as I do that, it's fine. But that apparently isn't a static setting and rebooting puts us back at square one.
The odd thing about it is that eth0 doesn't seem to need auto negotation turned on for it to work properly. Just eth1. My modules.conf contains the following, in case this info is helpful:
alias eth0 bcm5700
alias eth1 bcm5700
options bcm5700 auto_speed=0,0 line_speed=100,100 full_duplex=1,1
ifcfg-eth0:
DEVICE=eth0
BOOTPROTO=static
HWADDR=00:00:00:00:00:00
IPADDR=x.x.x.x
NETMASK=x.x.x.x
ONBOOT=no
TYPE=Ethernet
ifcfg-eth1:
DEVICE=eth1
BOOTPROTO=static
HWADDR=00:00:00:00:00:00
IPADDR=x.x.x.x
NETMASK=x.x.x.x
ONBOOT=yes
TYPE=Ethernet
Obviously, the HWADDR has been changed, that's not what i've actually got the file. It is set correctly, as is the ipaddr and netmask. Can anyone else point to something i'm doing wrong? or some solution to this problem? i'm running out of ideas.
|
|
|
01-11-2005, 04:20 PM
|
#2
|
Moderator
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417
|
what do "route" and "ifconfig" say about the state of things? maybe the default gateway is trying to route through eth0 still?
|
|
|
01-12-2005, 09:41 AM
|
#3
|
Member
Registered: Jul 2004
Posts: 90
Original Poster
Rep:
|
everything looks ok in route and ifconfig. the only thing is that on boot when booting to eth1, the network doesn't come up and the route command shows the default route as the ip address. but when i turn autonegotiate on, and do route again, it shows the hostname of that ip address instead of just the ip address.
I don't get why simply turning autonegotiate on cures the problem right away. And why this doesn't seem to be neccessary on eth0.
|
|
|
All times are GMT -5. The time now is 03:56 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|