Ref # |
Issue |
3560559 |
Description: If the DPU OS's OOB interface is disabled, it may lead to an issue that results in the DPU BMC losing network connectivity. This problem arises when the UEFI enables the OOB port (e.g., PXE, Redfish), but the OS does not load the necessary services and OOB kernel driver. In this scenario, the physical link remains active despite the OS driver not functioning, causing the hardware queue to become filled. Consequently, flow control pause packets are sent to the onboard 3-port switch, which may eventually lead to the DPU BMC losing its network connectivity. |
Workaround: Configure the 3-port switch to disable flow control support by running the following from the DPU BMC shell:
|
|
Discovered in version: 23.07-3 |
|
3566036 |
Description: After performing BF BMC factory reset, the /home/root/.ssh directory is deleted which causes the first attempt to confirm the host identity and initiate a BFB update procedure to fail while displaying the error message:
|
Workaround: Reattempt confirming the host identity and initiating the BFB update procedure. |
|
Discovered in version: 23.07-3 |
|
N/A |
Description: If the NIC BMC boots with non-default network configuration under /run/initramfs/rw/cow/etc/systemd/network/*, then the dedicated VLAN 4040 which supports the Redfish host interface with the UEFI BIOS device is not created. |
Workaround: Remove the network configuration files and reboot the system by running the following:
|
|
Discovered in version: 23.07-3 |
|
3561677 |
Description: It is not possible to modify the values of the BootOrder, BootOverride, and Secure Boot attributes from the UEFI menu because they are set by default to be configured from Redfish interface. |
Workaround: To directly modify these attributes from the UEFI menu, the user must disable the Redfish option in the UEFI menu. |
|
Discovered in version: 23.07-3 |
|
3388059 |
Description: When BlueField-2 boots and its services are loaded, there is a possibility that the IPMI over RMCP may become unresponsive due to the default timeout for commands being set to 1 second. |
Workaround: Increase the default timeout to 4 seconds when sending IPMI RMCP commands using the -N option. Example command:
|
|
Discovered in version: N/A |