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:
I create bond0 with two slaves eth0 and eth1. the system has been running two month. Recently I found that when eth0 is active slave, eth0 doesn't broadcast arp and other machines cannot ping this server.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
cat /etc/modprobe.d/bonding.conf 
alias netdev-bond0 bonding
alias netdev-bond2 bonding

# cat ifcfg-bond0
DEVICE=bond0
BOOTPROTO=static
ONBOOT=yes
NM_CONTROLLED=no
IPADDR=172.16.200.15
NETMASK=255.255.255.128
BONDING_OPTS="mode=1 miimon=100"

# cat ifcfg-eth0
DEVICE=eth0
NM_CONTROLLED=no
BOOTPROTO=none
ONBOOT=yes
MASTER=bond0
SLAVE=yes
USERCTL=no

# cat ifcfg-eth1
DEVICE=eth1
NM_CONTROLLED=no
BOOTPROTO=none
ONBOOT=yes
MASTER=bond0
SLAVE=yes
USERCTL=no
  
Actual results:


Expected results:


Additional info:

Before this happenned, I have used ipmitool to set IP netmask and gateway of the ipmi interface. Could it be related to the ipmi settings?

ipmitool -I open lan set 1 ipsrc static
ipmitool -I open lan set 1 ipaddr 10.10.199.20
ipmitool -I open lan set 1 netmask 255.255.255.128
ipmitool -I open lan set 1 defgw ipaddr 10.10.199.1

It has been confirmed that there is something wrong with the adapter card. It is hardware problem.
I just shutdown the system and then unplug the power wire and plug it back. start the server and everyting is ok now.

my server is SOGUN A620R.

I like these kind of bugs. If it happens again and can't be cured with hardware stuff - feel free to reopen.

Closing as NOTABUG.

I found a case like this. I wonder if it is related to my case.

https://bugzilla.redhat.com/show_bug.cgi?id=808638
Bug 808638 - e1000e v1.4.4 with Intel 82579 chipset looses link

https://bugzilla.redhat.com/show_bug.cgi?id=770675

and today I found my server eth0 and eth1 are both down.
I update the e1000e-2.0.0.1.tar.gz driver and append pcie_aspm=off to kernel