For known issues and limitations of the NVIDIA® BlueField® BSP, see BSP Known Issues.
|
Ref # |
Issue Details |
|---|---|
|
5393264 |
Description: The Redfish |
|
Workaround: N/A |
|
|
Reported in version: 26.10 |
|
|
5295459 |
Description: On BlueField-3, the Redfish |
|
Workaround: To reset |
|
|
Reported in version: 26.10 |
|
|
5302420 |
Description: On BlueField-3, the target path of the Redfish |
|
Workaround: Send the |
|
|
Reported in version: 26.10 |
|
|
5134017 |
Description: During |
|
Workaround: Wait a few minutes for the connection between the BlueField and the BMC to recover, then rerun the update flow or the version validation. |
|
|
Reported in version: 26.10 |
|
|
5234967 |
Description: On BlueField-2, a heavy load of certain IPMI commands might cause high CPU usage on the BMC because of hardware performance limitations. As a result, the BMC health monitor might generate CPU threshold alarms in the journal and event log. |
|
Workaround: N/A |
|
|
Reported in version: 26.10 |
|
|
5332103 |
Description: On BlueField-3, the Redfish |
|
Workaround: Use the |
|
|
Reported in version: 26.10 |
|
|
5039938 |
Description: During a BFB upgrade, the verification output might display a mismatch in the BMC firmware version strings. The offline target image reports the version normally (e.g., |
|
Workaround: Complete the update process by performing a full system power cycle. |
|
|
Reported in version: 26.04 |
|
|
4944048 |
Description: When upgrading from or downgrading to 25.10-LTSU2, repeated BMC reboots might, in rare cases, cause the |
|
Workaround: Perform a factory reset on the BMC. |
|
|
Reported in version: 25.10-LTSU2 |
|
|
4914053 |
Description: The BFB installer defaults to DHCP for the VLAN4040 interface. If no DHCP server is present, the request silently fails after a 300-second timeout, bypassing the static IP fallback and skipping all BMC-related firmware updates. |
|
Workaround: Ensure a DHCP server is accessible during installation, or manually configure a static IP for the VLAN4040 interface to prevent the timeout. If you use the updated installer script, static IP is the default, and you must explicitly enable DHCP by using |
|
|
Reported in version: 26.04 |
|
|
4931912 |
Description: Running |
|
Workaround: Clear the SEL before it reaches maximum capacity. |
|
|
Reported in version: 26.04 |
|
|
4995031 |
Description: After a firmware update through the |
|
Workaround: Perform a system reboot to clear the transient state and ensure all components accurately report their updated versions. |
|
|
Reported in version: 26.04 |
|
|
4994932 5086446 |
Description: In rare cases, the PLDM firmware update process in NIC mode might fail during the activation phase due to a transient communication error on the device. |
|
Workaround: Reset the BMC and retry the PLDM firmware update. |
|
|
Reported in version: 26.04 |
|
|
4882705 |
Description: The |
|
Workaround: Always perform a full cold boot of the host server or issue a complete DPU power cycle instead of relying on independent warm reboots of the subsystems. |
|
|
Reported in version: 26.01 |
|
|
4868713 |
Description: When a PLDM firmware update initiated from the host BMC is canceled or fails, the CEC firmware version might remain stuck in a pending state. |
|
Workaround: Perform a full power cycle of the card (power off the host, run |
|
|
Reported in version: 26.01 |
|
|
4870597 |
Description: When upgrading the BlueField-2 BMC from an earlier version that lacks Redfish Host Interface support (e.g., 2.8.2-x) to a later version that includes this feature (version 23.10 or later), the Redfish communication channel between the BlueField BIOS and the BMC Redfish server fails to initialize automatically. |
|
Workaround: Perform a BMC factory reset immediately following the firmware upgrade. |
|
|
Reported in version: 26.01 |
|
|
4876483 |
Description: When upgrading the BlueField firmware bundle (e.g., from 3.1.0 to 3.3.0), the |
|
Workaround: You can safely ignore this error. A standard system power cycle resolves the mismatch. |
|
|
Reported in version: 26.01 |
|
|
4885282 |
Description: When enabling Livefish mode from the DPU-BMC using |
|
Workaround: N/A |
|
|
Reported in version: 26.01 |
|
|
4857246 |
Description: The Redfish interface might list unsupported parameters (such as |
|
Workaround: Use only the diagnostic dump types listed in this guide (typically |
|
|
Reported in version: 26.01 |
|
|
4662191 |
Description: The BMC pending version might be displayed in a nonstandard format (e.g., version |
|
Workaround: N/A |
|
|
Reported in version: 26.01 |
|
|
4850556 |
Description: Performing a power reset of the DPU through the DPU-BMC might result in partial IP address information being displayed in |
|
Workaround: Reboot the DPU-BMC to refresh and display the full IP address information. |
|
|
Reported in version: 25.10 |
|
|
4877678 4240364 |
Description: Stress testing during upgrades and downgrades between BMC versions 25.01-1 and 24.10-17g might occasionally result in a loss of the BMC IP address. |
|
Workaround: N/A |
|
|
Reported in version: 25.10 |
|
|
4127100 |
Description: The BMC System Event Log (SEL) capacity calculation incorrectly excludes critical and warning events, counting only informational (debug) entries. As a result, the total number of SEL entries might exceed the configured maximum limit (e.g., exceeding a 600-entry limit), leading to inaccurate capacity reporting in tools like |
|
Workaround: Manually clear the SEL if it becomes too large. |
|
|
Reported in version: 25.10 |
|
|
4502081 |
Description: When the BMC SEL is full or contains a large number of entries, the BMC might require more than 110 seconds to fully initialize the SDR, sensor, and FRU information after a reboot. In rare cases (1-2%), this delay might exceed expected timeouts, taking up to about 112 seconds. |
|
Workaround: N/A |
|
|
Reported in version: 25.10 |
|
|
4793060 |
Description: Downgrading the BlueField-3 firmware bundle through PLDM is not supported in BMC 25.10-LTSU1. |
|
Workaround: N/A |
|
|
Reported in version: 25.10 |
|
|
N/A |
Description: The IP address range |
|
Workaround: N/A |
|
|
Reported in version: 25.10 |
|
|
4422284 |
Description: An eROT firmware update proceeds regardless of the |
|
Workaround: N/A |
|
|
Reported in version: 25.10 |
|
|
4650613 |
Description: On BlueField-2 DPUs, the BMC might not switch to the updated firmware image after a host power cycle during upgrade. This occurs because the ERoT (CEC) resets during the cycle, preventing the BMC flash from activating the new image. The update becomes effective only after the BMC itself is rebooted. |
|
Workaround: Reboot the BMC after the host power cycle to activate the new image. |
|
|
Reported in version: 25.10 |
|
|
4336172 |
Description: Pushing a PLDM package update to the BMC/CEC without rebooting the host causes the update process to fail. |
|
Workaround: N/A |
|
|
Reported in version: 25.07 |
|
|
4560376 |
Description: Performing a BMC factory reset without following up with a graceful reset leaves the BMC in an incomplete transitional state, resulting in undefined system behavior. |
|
Workaround: After you initiate a factory reset, perform a graceful reset to complete the process. If you skip the graceful reset, rerun the factory reset procedure and immediately follow it with a graceful reset. |
|
|
Reported in version: 25.07 |
|
|
4029375 |
Description: The Redfish schema for |
|
Workaround: N/A |
|
|
Reported in version: 25.04 |
|
|
4284756 |
Description: The UEFI re-enables a boot option after a power reset of the DPU. |
|
Workaround:
|
|
|
Reported in version: 25.01 |
|
|
4259780 |
Description: On BlueField-2, updating the BFB image over HTTPS without a CA fails and might not return the correct failure message. |
|
Workaround: N/A |
|
|
Reported in version: 25.01 |
|
|
4261446 |
Description: When the BlueField-2 SEL is full, loading the SEL database and initializing the log might take multiple attempts. |
|
Workaround: Retry the dump generation command. |
|
|
Reported in version: 25.01 |
|
|
4276783 |
Description: An orchestrated DPU-BMC reboot does not work after an upgrade if the CEC version has not changed. |
|
Workaround: N/A |
|
|
Reported in version: 25.01 |
|
|
4177391 |
Description: The BMC Redfish schema contains invalid attributes, which cause the Redfish Mockup Creator to return |
|
Workaround: N/A |
|
|
Reported in version: 25.01 |
|
|
4243159 |
Description: The BMC dump collection is missing the |
|
Workaround: N/A |
|
|
Reported in version: 25.01 |
|
|
4249132 |
Description: Copying a file that consumes space in the BMC |
|
Workaround: Do not copy any files to the BMC. If you do, you must replace the BlueField-3. |
|
|
Reported in version: 25.01 |
|
|
4178704 |
Description: When you delete an IPv4 or IPv6 static IP address through the Redfish interface, an unexpected failure message might appear even though the operation succeeded. Example for an IPv6 address:
|
|
Workaround: N/A |
|
|
Reported in version: 24.10-LTSU1 |
|
|
3922872 |
Description: In the |
|
Workaround: N/A |
|
|
Reported in version: 24.10 |
|
|
4123370 |
Description: When the BMC does not own RShim, the error notification for a BFB update is unclear. |
|
Workaround: N/A |
|
|
Reported in version: 24.10 |
|
|
4048673 |
Description: The BMC does not update the |
|
Workaround: N/A |
|
|
Reported in version: 24.10 |
|
|
4127461 |
Description: On BlueField-2, when the BMC comes up after a reboot and the SEL buffer is full, it takes about 30 seconds for the BMC to finish setting up all of the SEL entries. Until then, you cannot add entries or query existing ones. |
|
Workaround: N/A |
|
|
Reported in version: 24.10 |
|
|
N/A |
Description: When a new host forces RShim ownership, ownership might become ambiguous, and the resulting conflict causes several BMC features to stop working. |
|
Workaround: Reboot the BMC after moving RShim ownership to a new host. This ensures the BMC correctly synchronizes with the current RShim ownership status. |
|
|
Reported in version: 24.07 |
|
|
3877835 |
Description: |
|
Workaround: The supported management interfaces are |
|
|
Reported in version: 24.07 |
|
|
4027478 |
Description: The BMC IP aliasing feature lets you assign multiple IP addresses to a single network interface, so the interface can respond to different IP addresses. |
|
Workaround: N/A |
|
|
Reported in version: 24.07 |
|
|
3995907 |
Description: The Redfish schema for BlueField data ports ( |
|
Workaround: N/A |
|
|
Reported in version: 24.07 |
|
|
3899799 |
Description: The update to |
|
Workaround: N/A |
|
|
Reported in version: 24.07 |
|
|
3995899 |
Description: The DPU BMC detects ECC errors from the BlueField Arm system and records these errors in the BMC SEL. For SEL events related to single-bit ECC errors, the BMC does not recognize the resolution status on the BlueField Arm and consequently logs |
|
Workaround: N/A |
|
|
Reported in version: 24.07 |
|
|
3925815 |
Description: When you change the BMC IPv6 address configuration from static to DHCP, the static IP address in the IPv6 list is not disabled. |
|
Workaround: N/A |
|
|
Reported in version: 24.07 |
|
|
3899719 |
Description: After you run |
|
Workaround: N/A |
|
|
Reported in version: 24.07 |
|
|
4005373 |
Description: The DPU BMC does not support the following attributes and schemas within the |
|
Workaround: N/A |
|
|
Reported in version: 24.07 |
|
|
3995906 |
Description: The BlueField power cycle relies on the PCIe PERST/ALL_STANDBY. If the host does not disconnect the PCIe link, the DPU BMC cancels the power cycle request to avoid causing server errors. Because the power cycle command is asynchronous, it always returns success; however, if it fails, a new SEL entry is created to indicate that the command did not run. |
|
Workaround: Get the status from the BMC SEL. |
|
|
Reported in version: 24.07 |
|
|
3998661 |
Description: The |
|
Workaround: N/A |
|
|
Reported in version: 24.07 |
|
|
3914629 |
Description: If you set "Force PXE" right before installing a BFB image through the BMC RShim, the BlueField PXE boot fails to boot from NET-OOB-IPV4. |
|
Workaround: N/A |
|
|
Reported in version: 24.04 |
|
|
4064373 |
Description: The DPU BMC LLDP represents the |
|
Workaround: N/A |
|
|
Reported in version: 24.04 |
|
|
3994990 |
Description: During a power cycle of the BlueField, the |
|
Workaround: Reboot or reset the BlueField again. |
|
|
Reported in version: 24.01 |
|
|
3725502 |
Description: The BMC records user operations regardless of whether the action succeeds. |
|
Workaround: N/A |
|
|
Reported in version: 24.01 |
|
|
3598450 |
Description: The boot process might stall after a non-graceful reboot. |
|
Workaround: Do not perform a forced reboot of the BlueField BMC. |
|
|
Reported in version: 24.01 |
|
|
3664596 |
Description: If you configure only a secondary NTP server, that server acts as the primary server. |
|
Workaround: N/A |
|
|
Reported in version: 24.01 |
|
|
3747285 |
Description: The |
|
Workaround: If you need IPMI force PXE retry behavior, disable Redfish in UEFI. |
|
|
Reported in version: 24.01 |
|
|
3662417 |
Description: The Arm UEFI is crucial for rapid system booting, activating the NIC for host network communication. The Arm UEFI tries to fetch Redfish host credentials from the DPU BMC during boot. If it does not get them within a designated timeframe, the UEFI skips Redfish setup and boots the OS, ignoring any Redfish server settings or updates. |
|
Workaround: Reboot the BlueField Arm core again. |
|
|
Reported in version: 24.01 |
|
|
3668925 |
Description: If you need to set up a VLAN for a specific interface on the BMC, finish all other network configuration (such as DHCP or static) on the interface before you configure the VLAN, because the VLAN inherits all configuration from the existing interface. |
|
Workaround:
|
|
|
Reported in version: 23.10 |
|
|
3534150 |
Description: The BMC and BlueField use a shared IPMB channel for IPMI communication. If multiple requests coincide on this interface, you might encounter command failures with timeout indications. |
|
Workaround: Raise the retry counter for |
|
|
Reported in version: 23.10 |
|
|
3631199 |
Description: If Redfish is enabled in the UEFI menu (default), then Secure Boot configuration done from Redfish overrides Secure Boot configurationFactory Reset BMCdone from UEFI. |
|
Workaround: Disable Redfish in the UEFI menu, and then update the Secure Boot state. |
|
|
Reported in version: 23.10 |
|
|
3654930 |
Description: If the BlueField BMC firmware has been upgraded from version 2.8.2-x or earlier to version 23.03 or later, you must perform a factory reset of the BlueField BMC. |
|
Workaround: N/A |
|
|
Reported in version: 23.03 |
|
|
3637527 |
Description: The BlueField Redfish BIOS (UEFI) supports only UEFI mode for |
|
Workaround: Set |
|
|
Reported in version: 23.10 |
|
|
3634649 |
Description: In the Redfish |
|
Workaround: N/A |
|
|
Reported in version: 23.09 |
|
|
3634603 |
Description: When the BlueField operates in NIC mode, the Arm core does not load any OS. In this scenario, any BMC functionality that relies on extracting data from the OS through the IPMB channel is unavailable or limited, including:
|
|
Workaround: N/A |
|
|
Reported in version: 23.10 |
|
|
3609525 |
Description: After the BlueField BMC reboots, wait 30 seconds for all system services to load before you reboot the BlueField. |
|
Workaround: N/A |
|
|
Reported in version: 23.09 |
|
|
3590634 |
Description: When you update the BMC firmware, keep the system powered on until the update process finishes. |
|
Workaround: N/A |
|
|
Reported in version: 23.09 |
|
|
3599824 |
Description: In NIC mode, the BMC Redfish chassis schema contains only limited information about the BlueField because the OS is not available to supply the necessary information to the BMC. |
|
Workaround: N/A |
|
|
Reported in version: 23.09 |
|
|
3605254 |
Description: After a system power cycle, the BlueField and the BMC boot independently, so the BlueField UEFI boot process might finish before the BMC boot process. As a result, the BMC might not yet be ready to respond to Redfish communication attempts. |
|
Workaround: Wait until the BMC is done booting before issuing a reset command to the DPU. |
|
|
Reported in version: 23.09 |
|
|
3388059 |
Description: When BlueField-2 boots and loads its services, IPMI over RMCP might stop responding because the default command timeout is 1 second. |
|
Workaround: Increase the default timeout to 10 seconds when sending IPMI RMCP commands using the Bash
|
|
|
Reported in version: N/A |
Last updated: