Bug 718641 - Can't change lacp_rate in bonding mode=802.3ad
Summary: Can't change lacp_rate in bonding mode=802.3ad
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.7
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Jiri Pirko
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On: 707142
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-04 05:56 UTC by Liang Zheng
Modified: 2015-05-05 01:23 UTC (History)
7 users (show)

Fixed In Version: kernel-2.6.18-283.el5
Doc Type: Bug Fix
Doc Text:
Clone Of: 707142
Environment:
Last Closed: 2012-02-21 03:43:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:0150 0 normal SHIPPED_LIVE Moderate: Red Hat Enterprise Linux 5.8 kernel update 2012-02-21 07:35:24 UTC

Description Liang Zheng 2011-07-04 05:56:22 UTC
+++ This bug was initially created as a clone of Bug #707142 +++

Description of problem:
The bonding cannot change the LACPDU tx rate to request from 802.3ad partner when reset the parm:lacp_rate

Version-Release number of selected component (if applicable):
[root@hp-dl585g7-02 ~]# uname -r
2.6.32-131.0.15.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1.config switch to support 802.3ad
2.modprobe bonding mode=4 miimon=100 lacp_rate=1
3.ifconfig bond0 up
4.ifenslave bond0 eth1 eth7
5.tcpdump -p -e ether proto 0x8809 -i bond0 
  You can see request partner to transmit LACPDUs every 1 second
[root@hp-dl580g7-01 ~]# tcpdump -p ether proto 0x8809 -i bond0
tcpdump: WARNING: bond0: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on bond0, link-type EN10MB (Ethernet), capture size 65535 bytes
03:58:42.302350 LACPv1, length 110
03:58:43.312393 LACPv1, length 110
03:58:44.312413 LACPv1, length 110
03:58:45.312478 LACPv1, length 110

5.ifconfig bond0 down
6.echo 0 > /sys/class/net/bond0/bonding/lacp_rate
  cat /proc/net/bonding/bond0
[root@hp-dl580g7-01 ~]# cat /proc/net/bonding/bond0 
Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)

Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2 (0)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

802.3ad info
LACP rate: slow         <====================
Aggregator selection policy (ad_select): stable
Active Aggregator Info:
	Aggregator ID: 2
	Number of ports: 1
	Actor Key: 33
	Partner Key: 0
	Partner Mac Address: 00:05:73:dd:9a:3c

7.ifconfig bond0 up 
  tcpdump -p -e ether proto 0x8809 -i bond0
  It still request partner to transmit LACPDUs every 1 second,
  didnot change to slow in every 30 second.

  
Actual results:


Expected results:


Additional info:

Comment 1 RHEL Program Management 2011-08-12 08:29:42 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Comment 4 Jarod Wilson 2011-08-30 19:23:16 UTC
Patch(es) available in kernel-2.6.18-283.el5
You can download this test kernel (or newer) from http://people.redhat.com/jwilson/el5
Detailed testing feedback is always welcomed.

Comment 6 Liang Zheng 2011-10-14 06:42:01 UTC
On kernel 2.6.18-287.el5
After change lacp_rate=slow ,bonding receive lacp packets every 30s.
So set verified

Comment 7 errata-xmlrpc 2012-02-21 03:43:02 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2012-0150.html


Note You need to log in before you can comment on or make changes to this bug.