Bug 236770

Summary: bonding driver fails to forward traffic after link down event
Product: Red Hat Enterprise Linux 4 Reporter: Jon Stanley <jon.stanley>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Martin Jenner <mjenner>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.2   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-06-15 19:06:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jon Stanley 2007-04-17 16:04:49 UTC
We are using NIC bonding under the following configuration: 
 
eth0 = first port of first Intel Quad port Gigabit Ethernet controller. 
eth4 = first port of second Intel Quad port Gigabit Ethernet controller. 
bond0 = bonded master interface for eth0+eth4. 
 
When eth0/eth4 cables were disconnected and reconnected to same ports on a 
running system, we experienced lost of network connectivity to the bond0 
interface. 
 
Upon cable reconnect, ethtool showed valid link status as well as correct speed 
& duplex settings for the slave interfaces. (1000/FDX). 
 
bond0 would not recognize a valid slave interface after reconnect. 
 
"grep 'Active Slave' /proc/net/bonding/bond0" produced the following result: 
Currently Active Slave: None. 
 
running "ifconfig <if> down" and "ifconfig <if> up" for each slave interface 
eth0 and eth4 failed to affect the result. 
 
"ifconfig bond0" showed the correct IP address assigned to the bond0 interface, 
but IP traffic failed to reach the system over bond0. 

A reboot of the servers restored service.

Comment 1 Jason Baron 2007-06-15 19:06:11 UTC

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