BCM57416 - Card not in operational state?

[Dave Seddon]

I'm trying to use BCM57416, but getting "Card not in operational state"

```

[das@l:~/Downloads/broadcom/niccli-234.0.151.0_linux/Linux/linux_x86_64/niccli-234.0.151.0-linux_x86_64]$ sudo ./niccli.x86_64

-------------------------------------------------------------------------------
NIC CLI v234.0.151.0 - Broadcom Inc. (c) 2025 (Bld-106.52.39.138.16.0)
-------------------------------------------------------------------------------

     BoardId(Rev)    MAC Address        FwVersion    PCIAddr        Type   Mode
  1) BCM57416(NA)    Card not in operational state   0000:41:00.0   NIC    PCI
  2) BCM57416(NA)    Card not in operational state   0000:41:00.1   NIC    PCI

Enter the target index to connect with : exit
ERROR: Invalid value specified. Specify valid input.
Enter the target index to connect with : ^C

[das@l:~/Downloads/broadcom/niccli-234.0.151.0_linux/Linux/linux_x86_64/niccli-234.0.151.0-linux_x86_64]$

[das@l:~/Downloads/broadcom/niccli-234.0.151.0_linux/Linux/linux_x86_64/niccli-234.0.151.0-linux_x86_64]$ uname -a
Linux l 6.16.5 #1-NixOS SMP PREEMPT_DYNAMIC Thu Sep  4 14:55:53 UTC 2025 x86_64 GNU/Linux

[das@l:~/Downloads/broadcom/niccli-234.0.151.0_linux/Linux/linux_x86_64/niccli-234.0.151.0-linux_x86_64]$

```

```

BCM57416(NA)> show
CRITICAL !! Card is in a bad state. Recover/Flash firmware on the controller

PCI Device ID                       : 0x16D8
PCI Vendor ID                       : 0x14E4
PCI Revison ID                      : 0x1
PCI Component ID                    : 0x16D8
PCI Subsys Device ID                : 0x4160
PCI Subsys Vendor ID                : 0x17AA
BCM57416(NA)>

```

-------------------------------------------

[ninjabrum]

Usually that's a sign of a driver / firmware mismatch or the card is not supported.  Please include environment details and what steps you've taken (ESXi version, troubleshooting steps, etc). Check the Broadcom Hardware Compatibility Guide to see if it's supported on whatever version of ESXi you're using.  A cursory glance shows it to be compatible with ESXi 8 and above (with the right driver / firmware).

-------------------------------------------

[bseklecki_ge]

Does your compute platform have an iLOM where you can make UEFI firmware upgrades at the pre-OS level? iDRAC / HP iLO / Cisco UCS Manager ?

Can you boot a USB/Live ISO for GNU/Linux and apply it from there?

-------------------------------------------

[Dave Seddon]

Thanks for the replies guys!

I did try to boot the UEFI version of the niccli, but I couldn't get it to boot.  Basically, I copied the files into a new folder in the fat32 UFI boot, and added the menu item.  It didn't seem to boot though.  I might try using USB key.

Here's a little video of what I see happening with the cards

https://youtu.be/mUrVC7oo2_g?si=FVQACO3eeX4XyAol&t=1378

[ninjabrum]

Hypervisor versions / hardware vendors / details will help immensely.  The info you e provided cannot be used to help resolve this issue.  Provide more details or we're done here.

-------------------------------------------

[bseklecki_ge]

Just to confirm: You're using a generic GNU/Linux Live CD (shown above) just for the purposes of comparing how ESXI/vSphere sees the NIC, and/or apply the firmware updates, so that you can eventually run ESXi/vSphere on this hardware platform?

-------------------------------------------

[bseklecki_ge]

Don't despaired about UEFI boot loaders: Since 15 years, they are the absolute wild west; with no established standards with which any OEM/vendor complies.  Every motherboard/OEM vendor makes the syntax and user interface a wee different.  I think that they're pining for the days of Sun OpenBoot PROM on the SunStation.   

Philosophically: "Document Nothing [Well ] == Job Security / Vendor Lock in"

Generic UEFI update process (For a RAID card, but adapt as needed for Broadcom HBA/NIC/CNA)

https://www.youtube.com/watch?v=A0qf4sl8eac
https://scalelogic.freshdesk.com/support/solutions/articles/62000230327-firmware-upgrade-using-uefi-for-broadcom-lsi-9400-and-9500-hbas

UEFI> map -b
UEFI> fs0:
UEFI> cd [ any sub-directories on fat32 filesystem ] 
UEFI> sas2flash.efi -c 1 -f 2108it.bin
 [ change this syntax to match whatever broadcom has published ]
UEFI> broadcom_boot.efi -f latest_firmwareware.bin

(For example only)

Some vendors make these .efi / .bin combos available in which to boot pre-OS; some still require you to upgrade the firmware using a binary-only CLI in the running userland of a kernel with driver support.

---

Another article covers your encountered error:

https://www.hardwareluxx.de/community/threads/proxmox-netzwerk-mit-broadcom-nic.1350545/

However, it was regarding the older "Sliff" not the more standard "bnxt_en" driver; it discusses neeidng to use an older version of  the ADMIN cli utility to accomplish firmware updates, etc.