BCM 57416 doesnot notify peer port PHY_DOWN

[Liushuang]

Shutdown  NIC  (10Gb 2-port Base-T BCM57416 OCP3 Adapter, mac : 0432-0105-1cf0),  current state of peer port is still UP. And local port doesn't notify peer port PHY_DOWN. 

Current driver and firmware is :

[root@localhost ~]# ethtool -i ens1f0np0
driver: bnxt_en
version: 5.10.0-60.18.0.50.3.hl202.x86_6
firmware-version: 222.0.138.0/pkg 222.1.68.0
expansion-rom-version:
bus-info: 0000:5f:00.0

Can we upgrade driver or firmware to solve this issue?  

Thanks. 

[Azr_geek]

Hello @Liushuang,

Check for driver/firmware updates:

Broadcom/Marvell frequently release driver and firmware updates addressing link state and PHY notification bugs. Visit HPE or Broadcom official sites for latest bnxt_en driver and BCM57416 firmware matching your OS/kernel version. HPE’s customized drivers often include fixes beyond the vanilla Linux driver.

Upgrade path:

Firmware upgrades typically require downtime and vendor-specific tools (e.g., bnxtfwloader or vendor-supplied utilities).

Upgrading to the latest supported firmware can fix PHY state synchronization issues.

Newer bnxt_en drivers (kernel 5.15+ or newer releases) may have fixes for better PHY event propagation.

Temporary Workarounds:

Sometimes, toggling link state manually (ethtool --change), or restarting the NIC interface after shutdown can propagate the state correctly.

If using switches, check if switch firmware supports Link State Propagation or similar features.

Regards,
Azr_geek

[support_s]

System recommended content:

1. Gen11 Service Pack for ProLiant 2025.09.00.00 Component Release Notes

2. Gen10/Gen10 Plus Service Pack for ProLiant 2024.09.00.00 Component Release Notes

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[Liushuang]

Thanks for your reply. The problem is that we need the firmware that is compatible with DPDK 20.08.  No such infomation is provided on HPE.com. So is it a  better choice to submit a case? 

[Azr_geek · Accepted solution]

Looks like I wasn't able to find anything as well.

I guess it's better to go with the support ticket.