Warning: HWRM cmd error, cmd_type 0x90(HWRM_CFA_L2_FILTER_ALLOC) error 0x2(INVALID_PARAMS) seq <sequence number>
search cancel

Warning: HWRM cmd error, cmd_type 0x90(HWRM_CFA_L2_FILTER_ALLOC) error 0x2(INVALID_PARAMS) seq <sequence number>

book

Article ID: 395225

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • Host had unexpectedly starting facing connectivity issue resulting in it being reported as down.
  • Virtual machines also started reported connectivity issues.
  • The specific portgroup where the impacted host/VM were connected, has multiple physical adapters (vmnic) configured in active-active failover order.
  • VMs using either one of the active adapters reported connection loss.
  • In the ESXi host vmkernel file, firmware dumps are generated for the physical adapters.
  • Dumps generated are for all the vmnics configured as active-active.
  • Firmware trace reported is similar to below: 

/var/log/vmkernel.log: 

YYYY-MM-DDTHH:MM:SS.285Z Wa(180) vmkwarning: cpu46:2097517)WARNING: bnxtnet: hwrm_send_msg:441: [vmnic# : 0x431202e91680] HWRM cmd error, cmd_type 0x90(HWRM_CFA_L2_FILTER_ALLOC) error 0x2(INVALID_PARAMS) seq 17913
YYYY-MM-DDTHH:MM:SS.324Z In(182) vmkernel: cpu42:2097517)bnxtnet: dev_dump_fw_trace:154: [vmnic# : 0x431202e91680] Dumping FW Trace:
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel:
YYYY-MM-DDTHH:MM:SS.324Z In(182) vmkernel: cpu42:2097517)bnxtnet: dev_print_fw_data:124: [vmnic# : 0x431202e91680] == START OF TRACE ==
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel:
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 0.5:*** Start of Trace FW version 214.0.253.1 ***
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 0.5:invalid dyn min cfg, pf 0
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 0.5:invalid dyn max cfg, pf 0
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 0.5:invalid msix max cfg, pf 0
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 0.5:invalid vf res strat, pf 0
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 0.5:invalid dyn min cfg, pf 1
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 0.5:invalid dyn max cfg, pf 1
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 0.5:invalid msix max cfg, pf 1
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 0.5:invalid vf res strat, pf 1
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 0.5:falling back to symmetric allocation for dyn min, pf 0
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 0.5:falling back to symmetric allocation for dyn max, pf 0
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 0.5:falling back to symmetric allocation for cmpl/nq rings, pf 0
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 0.5:falling back to symmetric allocation for dyn min, pf 1
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 0.5:falling back to symmetric allocation for dyn max, pf 1
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 0.5:falling back to symmetric allocation for cmpl/nq rings, pf 1
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 1.0:kong start 3f4
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 16.8:PCIE rst (1)
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 16.8:invalid dyn min cfg, pf 0
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 16.8:invalid dyn max cfg, pf 0
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 16.8:invalid msix max cfg, pf 0
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 16.8:invalid vf res strat, pf 0
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 16.8:invalid dyn min cfg, pf 1
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 16.8:invalid dyn max cfg, pf 1
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 16.8:invalid msix max cfg, pf 1
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 16.8:invalid vf res strat, pf 1
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 16.8:falling back to symmetric allocation for dyn min, pf 0
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 16.8:falling back to symmetric allocation for dyn max, pf 0
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 16.8:falling back to symmetric allocation for cmpl/nq rings, pf 0
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 16.8:falling back to symmetric allocation for dyn min, pf 1
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 16.8:falling back to symmetric allocation for dyn max, pf 1
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 16.8:falling back to symmetric allocation for cmpl/nq rings, pf 1
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel: 18.0:kong start 4634
YYYY-MM-DDTHH:MM:SSZ In(182) vmkernel:
YYYY-MM-DDTHH:MM:SS.325Z In(182) vmkernel: cpu42:2097517)bnxtnet: dev_print_fw_data:136: [vmnic# : 0x431202e91680] == END OF TRACE ==

NOTE: The preceding log excerpts are only examples. Date, time and environmental variables may vary depending on your environment.

Environment

VMware vSphere ESXi

Cause

This is caused by a firmware error of the physical network card.

Resolution

Recommended Action

Please engage your hardware vendor to:

  • Validate the health of the physical NICs.

  • Review and, if necessary, update the NIC drivers and firmware to the latest supported versions.

  • Confirm network configuration settings are aligned with vendor and VMware best practices.

Additional Information

For validating the driver/firmware version of the adapters, please refer article: Determining Network/Storage firmware and driver version in ESXi

Also, kindly refer the Broadcom compatibility guide: Broadcom Compatibility Guide for IO devices

Powered by Wolken Software