Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When I tested ipv6 on bonding,I config bonding with mode=0 (balance-round-robin),
I can not use ping6 on that bonding interface.
I used two be2net NICs in bond0.
Version-Release number of selected component (if applicable):
2.6.32-202.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1.modprode bonding mode=0 miimon=100
2.ifconfig bond0 up
3.ifenslave bond0 eth6 eth7
4.ip a a fe01::2/64 dev bond0
5.ping6 fe01::3 or netperf -6 -H fe01::3
Actual results:
Can not ping successfully.
[root@hp-dl580g7-01 ~]# ping6 fe01::1
PING fe01::1(fe01::1) 56 data bytes
From ::1 icmp_seq=2 Destination unreachable: Address unreachable
From ::1 icmp_seq=3 Destination unreachable: Address unreachable
From ::1 icmp_seq=4 Destination unreachable: Address unreachable
Expected results:
Additional info:
[root@hp-dl580g7-01 ~]# ip -6 route
fe01::/64 dev bond0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
[root@hp-dl580g7-01 ~]# ip -6 a s
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
23: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500
inet6 fe01::2/64 scope global tentative dadfailed
valid_lft forever preferred_lft forever
[root@hp-dl580g7-01 ~]# dmesg | tail -n 20
ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
ixgbe 0000:11:00.1: eth5: NIC Link is Up 10 Gbps, Flow Control: RX/TX
bond0: link status definitely up for interface eth5, 10000 Mbps full duplex.
bond0: no IPv6 routers present
bonding: bond0: released all slaves
Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
bonding: MII link monitoring set to 100 ms
ADDRCONF(NETDEV_UP): bond0: link is not ready
8021q: adding VLAN 0 to HW filter on device bond0
eth6: Link up
8021q: adding VLAN 0 to HW filter on device eth6
New slave device eth6 does not support netpoll
Disabling netpoll support for bond0
bonding: bond0: enslaving eth6 as an active interface with an up link.
eth7: Link up
8021q: adding VLAN 0 to HW filter on device eth7
bonding: bond0: enslaving eth7 as an active interface with an up link.
ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
bond0: IPv6 duplicate address fe80::200:c9ff:feb1:eade detected!
bond0: IPv6 duplicate address fe01::2 detected!
(In reply to comment #6)
> Could be possible to use bonding setup with balance-rr mode and with one be2net
> and one non-be2net device?
okļ¼but our lab controller is broken for 2 weeks,I cannot provision my systems to rhel6.If the systems are available,I will give the test feedback asap.
Thanks.
Description of problem: When I tested ipv6 on bonding,I config bonding with mode=0 (balance-round-robin), I can not use ping6 on that bonding interface. I used two be2net NICs in bond0. Version-Release number of selected component (if applicable): 2.6.32-202.el6.x86_64 How reproducible: always Steps to Reproduce: 1.modprode bonding mode=0 miimon=100 2.ifconfig bond0 up 3.ifenslave bond0 eth6 eth7 4.ip a a fe01::2/64 dev bond0 5.ping6 fe01::3 or netperf -6 -H fe01::3 Actual results: Can not ping successfully. [root@hp-dl580g7-01 ~]# ping6 fe01::1 PING fe01::1(fe01::1) 56 data bytes From ::1 icmp_seq=2 Destination unreachable: Address unreachable From ::1 icmp_seq=3 Destination unreachable: Address unreachable From ::1 icmp_seq=4 Destination unreachable: Address unreachable Expected results: Additional info: [root@hp-dl580g7-01 ~]# ip -6 route fe01::/64 dev bond0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 [root@hp-dl580g7-01 ~]# ip -6 a s 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 23: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 inet6 fe01::2/64 scope global tentative dadfailed valid_lft forever preferred_lft forever [root@hp-dl580g7-01 ~]# dmesg | tail -n 20 ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready ixgbe 0000:11:00.1: eth5: NIC Link is Up 10 Gbps, Flow Control: RX/TX bond0: link status definitely up for interface eth5, 10000 Mbps full duplex. bond0: no IPv6 routers present bonding: bond0: released all slaves Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009) bonding: MII link monitoring set to 100 ms ADDRCONF(NETDEV_UP): bond0: link is not ready 8021q: adding VLAN 0 to HW filter on device bond0 eth6: Link up 8021q: adding VLAN 0 to HW filter on device eth6 New slave device eth6 does not support netpoll Disabling netpoll support for bond0 bonding: bond0: enslaving eth6 as an active interface with an up link. eth7: Link up 8021q: adding VLAN 0 to HW filter on device eth7 bonding: bond0: enslaving eth7 as an active interface with an up link. ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready bond0: IPv6 duplicate address fe80::200:c9ff:feb1:eade detected! bond0: IPv6 duplicate address fe01::2 detected!