Changes and New Features

• To ensure FRU device information is consistent across different system components, NVIDIA Networking is aligning the BlueField BMC FRU board product name with the system product name. This means that there would be two variations of BlueField BMC FRUs in the field. The following are the supported deviations:

  FRU Field	Rev-1 (Old)	Rev-2 (New)
  FRU Device Description	Nvidia-BMCMezz (ID 169)	BlueField-3 DPU (ID 243)
  Board Manufacturing Date	<Board-mfg-date>	<Board-mfg-date>
  Board Manufacturer	Nvidia	Nvidia
  Board Product	Nvidia-BMCMezz	BlueField-3 DPU
  Board Serial	<Board-serial>	<Board-serial>
  Board Part Number	<Board-part-number>	<Board-part-number>

• Security enhancements – Introduced a new BIOS option to disable the IPMI channel between the BlueField Arm cores and its BMC. By default, this interface is enabled. However, a new BIOS attribute accessible via Redfish now permits disabling this interface for enhanced security.

• IPMB channel relocation – The IPMB channel used by the BlueField BMC to retrieve data from the BlueField Arm is now utilizing a dedicated I2C interface. This change is aimed at improving the serviceability of the interface.

• Temperature monitoring – Added the BlueField Arm DDR sensor to the BlueField BMC sensor list. This addition enables the monitoring of DDR temperature (ddr_temp), ensuring better performance and reliability.

• Event logging enhancements – Introduced several new event alarms:

  • BlueField data port module over current event (Module Critical Power Consumption)

  • BlueField data port module temperature event (Module Temperature Going High/Low)

  • BlueField Arm frequency change event (Arm Frequency Change)

    Note

    These alarms are now logged to the BMC System Event Log (SEL) for better event tracking and system diagnostics.

• BIOS Debug Mode – An option has been added to enable BIOS debug mode, facilitating advanced troubleshooting and system analysis

The following changes in DOCA 2.9.0 (BSP 4.9.0) and BMC 24.10 break backward compatibility and therefore require customers to upgrade all DOCA software components to the latest available version to avoid anomalous behavior: