Bug 499109 (bonding, Bug, interface, multiple)

This was also reported in bug 498024, so I am going to close this as a duplicate of that bug.  Please post all comments there.

In the meantime, have you been able to try the latest 5.3 kernels or my test kernels here:

http://people.redhat.com/agospoda/#rhel5

Thanks!

*** This bug has been marked as a duplicate of bug 498024 ***

Dear Sirs, Hi,

I tried to configure bonding on Redhat Enterprise Linux 5.3 on a Dell PowerEdge 2950 server using Broadcom NICs BCM 5708 bnx2; 

please check the follwoing are the configuration details; 

/etc/sysconfig/netword-scripts/ifcfg-bond0
DEVICE=bond0
USERCTL=no
ONBOOT=yes
BROADCAST=10.x.y.255
NETWORK=10.x.y.0
NETMASK=255.255.255.0
GATEWAY=10.x.y.1
IPADDR=10.x.y.65

/etc/sysconfig/netword-scripts/ifcfg-eth0
DEVICE=eth0
USERCTL=no
ONBOOT=yes
MASTER=bond0
SLAVE=yes
BOOTPROTO=none

/etc/sysconfig/netword-scripts/ifcfg-eth1
DEVICE=eth1
USERCTL=no
ONBOOT=yes
MASTER=bond0
SLAVE=yes
BOOTPROTO=none


/etc/modprobe.conf
alias eth0 bnx2
alias eth1 bnx2
alias scsi_hostadapter megaraid_sas
alias scsi_hostadapter1 ata_piix
alias scsi_hostadapter2 qla2xxx
alias peth0 bnx2

alias bond0 bonding
options bonding miimon=100 mode=0


after the configuration, when I restart the network service, the following Messages are displays

# service network restart
Shutting down interface bond0:  bonding: bond0: Warning: the permanent HWaddr of eth0 - 00:24:E8:5E:8F:F3 - is still in use by bond0. Set the HWaddr of eth0 to
a different address to avoid conflicts.
                                                           [  OK  ]
Shutting down interface eth0:  bonding: bond0: Unable to update slaves because interface is down.
                                                           [  OK  ]
Shutting down loopback interface:                          [  OK  ]
Disabling IPv4 packet forwarding:  net.ipv4.ip_forward = 0
                                                           [  OK  ]
Bringing up loopback interface:                            [  OK  ]
Bringing up interface bond0:  bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full.
                                                           [  OK  ]
please advice me how can i solve this issue; 

your valuable Suggestions is highly appriciable on this .

Best Regards,
Salam

Dear Sirs, Hi,

I tried to configure bonding on Redhat Enterprise Linux 5.3 on a Dell PowerEdge 2950 server using Broadcom NICs BCM 5708 bnx2; 

please check the follwoing are the configuration details; 

/etc/sysconfig/netword-scripts/ifcfg-bond0
DEVICE=bond0
USERCTL=no
ONBOOT=yes
BROADCAST=10.x.y.255
NETWORK=10.x.y.0
NETMASK=255.255.255.0
GATEWAY=10.x.y.1
IPADDR=10.x.y.65

/etc/sysconfig/netword-scripts/ifcfg-eth0
DEVICE=eth0
USERCTL=no
ONBOOT=yes
MASTER=bond0
SLAVE=yes
BOOTPROTO=none

/etc/sysconfig/netword-scripts/ifcfg-eth1
DEVICE=eth1
USERCTL=no
ONBOOT=yes
MASTER=bond0
SLAVE=yes
BOOTPROTO=none


/etc/modprobe.conf
alias eth0 bnx2
alias eth1 bnx2
alias scsi_hostadapter megaraid_sas
alias scsi_hostadapter1 ata_piix
alias scsi_hostadapter2 qla2xxx
alias peth0 bnx2

alias bond0 bonding
options bonding miimon=100 mode=0


after the configuration, when I restart the network service, the following Messages are displays

# service network restart
Shutting down interface bond0:  bonding: bond0: Warning: the permanent HWaddr of eth0 - 00:24:E8:5E:8F:F3 - is still in use by bond0. Set the HWaddr of eth0 to
a different address to avoid conflicts.
                                                           [  OK  ]
Shutting down interface eth0:  bonding: bond0: Unable to update slaves because interface is down.
                                                           [  OK  ]
Shutting down loopback interface:                          [  OK  ]
Disabling IPv4 packet forwarding:  net.ipv4.ip_forward = 0
                                                           [  OK  ]
Bringing up loopback interface:                            [  OK  ]
Bringing up interface bond0:  bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full.
                                                           [  OK  ]
please advice me how can i solve this issue; 

your valuable Suggestions is highly appriciable on this .

Best Regards,
Salam

(In reply to comment #3)
> Dear Sirs, Hi,
> 
> I tried to configure bonding on Redhat Enterprise Linux 5.3 on a Dell PowerEdge
> 2950 server using Broadcom NICs BCM 5708 bnx2; 
> 
> please check the follwoing are the configuration details; 
> 
> /etc/sysconfig/netword-scripts/ifcfg-bond0
> DEVICE=bond0
> USERCTL=no
> ONBOOT=yes
> BROADCAST=10.x.y.255
> NETWORK=10.x.y.0
> NETMASK=255.255.255.0
> GATEWAY=10.x.y.1
> IPADDR=10.x.y.65
> 
> /etc/sysconfig/netword-scripts/ifcfg-eth0
> DEVICE=eth0
> USERCTL=no
> ONBOOT=yes
> MASTER=bond0
> SLAVE=yes
> BOOTPROTO=none
> 
> /etc/sysconfig/netword-scripts/ifcfg-eth1
> DEVICE=eth1
> USERCTL=no
> ONBOOT=yes
> MASTER=bond0
> SLAVE=yes
> BOOTPROTO=none
> 
> 
> /etc/modprobe.conf
> alias eth0 bnx2
> alias eth1 bnx2
> alias scsi_hostadapter megaraid_sas
> alias scsi_hostadapter1 ata_piix
> alias scsi_hostadapter2 qla2xxx
> alias peth0 bnx2
> 
> alias bond0 bonding
> options bonding miimon=100 mode=0
>

Please consider removing the line 'options bonding miimon=100 mode=0' from modprobe.conf and place this line in ifcfg-bond0

BONDING_OPTS="miimon=100 mode=0"

RHEL5 and later support setting the bonding options in the ifcfg-bondX file, not in modprobe.conf.

> 
> after the configuration, when I restart the network service, the following
> Messages are displays
> 
> # service network restart
> Shutting down interface bond0:  bonding: bond0: Warning: the permanent HWaddr
> of eth0 - 00:24:E8:5E:8F:F3 - is still in use by bond0. Set the HWaddr of eth0
> to
> a different address to avoid conflicts.

This message is not important unless you remove eth0 from bond0, but continue to use both.  You can ignore it when it appears when restarting the network or if you perform 'ifdown bond0'

> Bringing up interface bond0:  bonding: bond0: Warning: failed to get speed and
> duplex from eth0, assumed to be 100Mb/sec and Full.
>                                                            [  OK  ]

This message indicates that the link-speed detected does not match the limits of 10/100/1000Mbit that the bonding driver expects or the link is not up.  What speed is reported by the command 'ethtool eth0'?

If something other than 10, 100, or 1000Mbit is reported or the link is not UP this message is expected and can be ignored.

Welcome to Honestus! We specialize in Painting Services, General Contracting, Garage Flooring, Refinishing, Bathroom Renovation, Subcontracting, and Flooring Contracting. Serving Brampton, Barrie, Durham, and Hamilton, we're committed to transparency and quality in every project. Whether it's revamping your home or sprucing up your business space, count on us for honesty and excellence. Your satisfaction is our priority at Honestus.Visit us https://honestus.ca/